EDIFACT/PAYMUL -- Technical Manual Edifact/PAYMUL English version December 2006 A Payments and Cash Management solution from
Edifact/PAYMUL A payment order is sent by the ordering customer to instruct the ordered bank to debit its account, and to arrange for the payment of specified amounts to several beneficiaries in settlement of the referenced business transaction(s). This message may be applied for both national and international settlements, single or multiple transactions. Several credit accounts, value dates, entry dates and currencies may be specified. This document provides companies with guidelines in such a way that they can implement in their own systems a layout to be sent to ING Group via one of the available channels in the Netherlands, in this case specifically ING Finstream and Electronic Banking (EB). The present layout is based on PAYMUL UN/EDIFACT directory D.96A. Edifact/PAYMUL, English version, December 2006 -
Contents 1. Introduction................................................ 5 2. Message Structure Chart...................................... 7 3. Segment Description........................................ 11 4. Segments Layout........................................... 16 4.1 UNB: Interchange message header........................... 18 4.2 UNH: Message header................................... 19 4.3 BGM: Beginning of message.............................. 20 4.4 DTM: Date/time/period.................................. 21 4.5 SG3-D: and address.............................. 22 4.6 SG4-LIN: Line item..................................... 24 4.7 SG4-DTM: Date/time/period.............................. 25 4.8 SG4-RFF: Reference..................................... 26 4.9 SG4-BUS: Business function............................... 27 4.10 SG4-FCA: Financial charges allocation....................... 29 4.11 SG5-MOA: Monetary amount............................. 30 4.12 SG6-FII: Financial institution information...................... 31 4.13 SG7-D: and address.............................. 32 4.14 SG9-GIS: General indicator............................... 34 4.15 SG9-FTX: Free text..................................... 35 4.16 SG10-PRC: Process identification........................... 36 4.17 SG10-FTX: Free text.................................... 37 4.18 SG11-SEQ: Sequence details............................... 39 4.19 SG11-MOA: Monetary amount............................. 40 4.20 SG11-RFF: Reference.................................... 41 4.21 SG11-FCA: Financial charges allocation....................... 42 4.22 SG12-FII: Financial institution information..................... 43 4.23 SG13-D: and address............................. 45 4.24 SG15-GIS: General indicator............................... 47 4.25 SG15-FTX: Free text..................................... 48 4.26 SG16-PRC: Process identification........................... 49 4.27 SG16-FTX: Free text.................................... 50 4.28 CNT: Control total...................................... 52 4.29 UNT: Message trailer.................................... 53 4.30 UNZ: Interchange message trailer........................... 54 Edifact/PAYMUL, English version, December 2006 -
Annex A : EXAMPLES OF EACH PAYMENT ORDER.................... 55 Annex B : PAYMUL CHARACTER SET............................... 57 Annex C : ENGLISH CURRENCY MES AND CODE ELEMENTS........... 58 Annex D : ENGLISH COUNTRY MES AND CODE ELEMENTS........... 62 Annex E : COUNTRY SPECIFICS................................... 65 1. Austria................................................... 66 2. Belgium................................................... 69 3. Bulgaria.................................................. 73 4. Czech Republic............................................. 77 5. Denmark.................................................. 81 6. Finland................................................... 84 7. France.................................................... 87 7.1 Economic codes for France.................................... 90 8. Germany.................................................. 91 9. Hungary.................................................. 94 10. Ireland................................................... 98 11. Italy................................................... 101 12. Luxemburg.............................................. 104 12.1 Economic codes for Luxemburg............................... 108 13. Netherlands.............................................. 111 14. Norway.................................................. 118 15. Poland.................................................. 121 16. Portugal................................................ 125 17. Romania................................................ 129 18. Slovak Republic........................................... 132 19. Spain................................................... 136 20. Sweden................................................. 140 21. Switzerland.............................................. 143 22. United Kingdom.......................................... 144 Annex F : CHANNEL SPECIFICS.................................. 147 Annex G : RULES TO DETERMINE TRANSACTION TYPE................ 150 Annex H : PAYMENT PRODUCTS SUPPORTED BY PAYMUL............. 153 Contact information.......................................... 154 Edifact/PAYMUL, English version, December 2006 -
1. Introduction Product & channels information With regard to the Netherlands, this format can be sent to ING via the ING Finstream and EB channels. Although some key information is provided in Annex F, please refer to the respective user documentation provided with the software for the specific handling of Paymul files. Remarks with regard to the document The document focuses on the ING PAYMUL format description: this contains the basis and the framework within a payment order is to be defined specifically for the Dutch payment channels; you ll find the detailed format description in chapter 2. The annexes provide examples of payment orders (Annex A) and lists of the PAYMUL charter set (Annex B), English currency names and code elements (Annex C) and English country names and code element (Annex D). Please note that the country specifics are described in a separate annex (E). This annex defines for each country and transaction type which data is to be specifically supplied. The country specific annex is required for the reason that each local clearing practice differs in each country, for example the length of the payment details in Ireland equals one line of 18 positions; in the Netherlands payment details equals three lines of 32 positions. Annex F provides information on the software package or channel specifics: this defines characteristics of the software package (representing the channel), that have consequences for how the customer should supply the PAYMUL message; the software package is used by the customer for initiating payment orders. The packages currently in scope are ING Electronic Banking (EB) and ING Finstream (FS). Definition A Multiple Payment order is sent by the Ordering Customer (or Payer or Agent on behalf of the Ordering Customer) to the Ordered Bank, to instruct the Ordered Bank to debit an account it services for the Ordering Customer, and to arrange for the payment of specified amounts to several Beneficiaries (or Payees) in settlement of the referenced business transaction(s). Throughout this document, the term Ordering Customer refers to either an Ordering Customer, or a Payor or Agent acting (sending) on behalf of the Ordering Customer; likewise the term Beneficiary refers to either a Beneficiary, or a Payee or Agent acting on behalf of the Beneficiary. This message may be applied for both national and international settlements. It is based on universal practice and is not dependent on the type of business or industry. Principles a Multiple Payment Order may cover the financial settlement of one or more commercial trade transactions such as invoices credit notes, debit notes etc. It is not intended for use in securities trading Edifact/PAYMUL, English version, December 2006 -
several debit accounts, execution dates and currencies may be specified several credit accounts, value dates, entry dates and currencies may be specified The Multiple Payment Order message is structured in three levels: A, B, and C. level A contains data related to the whole message and is contained in Segment Group 1 and Segment Group 2 and the Heading section level B contains data from the debit side (one debit account, one currency, one execution date) and data which applies to all further details of level(s) C and is contained in Segment Group 3 through Segment Group 9 level C contains mainly data related to the credit side, and this data is considered as unique for each payment transaction and is contained in Segment Group 10 through Segment Group 21 The structure of the message is designed to allow several levels B, each level B being followed by its related levels C. Where a choice of code or text is given only the code element should be used wherever possible. Validation The PAYMUL file is validated on three levels: I) format: the file must be compliant with the PAYMUL layout and the record data must be complete and correct II) product: all relevant data for affecting the requested type of payment order must be available III) country: the payment must comply with the requirements applicable in the country in which the payment is to be effected. Any payment order is rejected that fail the above requirements. In the case of inadequate data, however, dependent on the software package, the software package will try to deduce the order by having PAYMUL ignore any superfluous read information and use data contained in the database to compose the required information, such as SWIFT address (only EB not ING Finstream). If the software package is still unable to process the file or parts of the file, an error message will be reported to the customer stating the cause of the problem. Please refer to the user documentation for more specific information on error handling Annex A gives a number of correct examples of each kind of PAYMUL payment order. Edifact/PAYMUL, English version, December 2006 -
2. Message Structure Chart Tag Status/Repeat EDIFACT ING Interchange Message Heading Section U O1 O1 UNB Interchange message header M1 M1 Multiple Payment Order Heading Section UNH Message header M1 M1 BGM Beginning of message M1 M1 DTM Date/time/period M1 M1 BUS Business function C1 - +-------- -------- Segment group 1 C2 - RFF Reference M1 - +-------- DTM Date/time/period C1 - +-------- -------- Segment group 2 C5 - FII Financial institution information M1 - CTA Contact information C1 - +-------- COM Communication contact C5 - +-------- Segment group 3 C3 D3 D and address M1 M1 CTA Contact information C1 - +-------- COM Communication contact C5 - Multiple Payment Order Detail Section +-------- Segment group 4 M9999 M9999 LIN Line item M1 M1 DTM Date/time/period C1 M1 RFF Reference C2 O1 BUS Business function C1 O1 FCA Financial charges allocation C1 O1 +------ -------- Segment group 5 C1 R1 MOA Monetary amount M1 M1 CUX Currencies C1 - DTM Date/time/period C2 - +------ RFF Reference C1 - +------ -------- Segment group 6 M1 M1 FII Financial institution information M1 M1 CTA Contact information C1 - +------ COM Communication contact C5 - +------ -------- Segment group 7 C3 D3 D and address M1 M1 CTA Contact information C1 - Edifact/PAYMUL, English version, December 2006 -
+------ COM Communication contact C5 - +------ -------- Segment group 8 C1 - INP Parties to instruction M1 - FTX Free text C1 - +------ DTM Date/time/period C2 - +------ -------- Segment group 9 C10 O10 GIS General indicator M1 M1 MOA Monetary amount C1 - LOC Place/location identification C2 - D and address C1 - RCS Requirements and conditions C1 - +------ FTX Free text C10 O10 +------ -------- Segment group 10 C1 O1 PRC Process identification M1 M1 +------ FTX Free text M1 M1 +------ -------- Segment group 11 M9999 M9999 SEQ Sequence details M1 M1 MOA Monetary amount M1 M1 DTM Date/time/period C1 - RFF Reference C3 O2 PAI Payment instructions C1 - FCA Financial charges allocation C1 O1 +----- -------- Segment group 12 C3 R1 FII Financial institution information M1 M1 CTA Contact information C1 - +----- COM Communication contact C5 - +----- -------- Segment group 13 C3 O2 D and address M1 M1 CTA Contact information C1 - +----- COM Communication contact C5 - +----- -------- Segment group 14 C3 - INP Parties to instruction M1 - FTX Free text C1 - +----- DTM Date/time/period C2 - +----- -------- Segment group 15 C10 O1 GIS General indicator M1 M1 MOA Monetary amount C1 - LOC Place/location identification C2 - D and address C1 - RCS Requirements and conditions C1 - +----- FTX Free text C10 O10 +----- -------- Segment group 16 C1 O1 Edifact/PAYMUL, English version, December 2006 -
PRC Process identification M1 M1 FTX Free text C5 O5 +--- -------- Segment group 17 See Note 1 C9999 O9999 DOC Document/message details M1 M1 MOA Monetary amount C5 O5 DTM Date/time/period C5 O5 RFF Reference C5 O5 D and address C2 O2 +--- -------- Segment group 18 See Note 1 C5 O5 CUX Currencies M1 M1 +--- DTM Date/time/period C1 O1 +--- -------- Segment group 19 See Note 1 C100 O100 AJT Adjustment details M1 M1 MOA Monetary amount M1 M1 RFF Reference C1 O1 +--- FTX Free text C5 O5 +--- -------- Segment group 20 See Note 1 C1000 O1000 DLI Document line identification M1 M1 MOA Monetary amount M5 M5 PIA Additional product id C5 O1 +--- DTM Date/time/period C5 O5 +--- -------- Segment group 21 See Note 1 C5 O5 CUX Currencies M1 M1 +--- DTM Date/time/period C1 O1 +--- -------- Segment group 22 See Note 1 C10 O10 AJT Adjustment details M1 M1 MOA Monetary amount M1 M1 RFF Reference C1 O1 +--- FTX Free text C5 O5 +--- -------- Segment group 23 See Note 1 C1 O1 GIS General indicator M1 M1 +------- MOA Monetary amount C5 O5 Multiple Payment Order Summary Section CNT Control total C5 R1 +-------- -------- Segment group 24 C5 - AUT Authentication result M1 - +-------- DTM Date/time/period C1 - UNT Message trailer M1 M1 UNZ Interchange message trailer M1 M1 Edifact/PAYMUL, English version, December 2006 -
Note 1 Segment group 17 until segment group 23 (DOC Group) are reserved for the extended payment details. The usage of the DOC group is dependent on country and branch specific mutually agreements. At the moment the Dutch channels do not support extended payment details functionality. ING Finstream and EB only check the DOC group for syntax errors (or completely ignore it). For this reason this document does not describe these segment groups. Edifact/PAYMUL, English version, December 2006-10
3. Segment Description Heading Section U, A service segment identifying the used separators. UNB, Interchange message header A service segment starting and identifying an interchange message. UNH, Message header A service segment starting and uniquely identifying a message. The message type code for the Multiple payment order message is PAYMUL. BGM, Beginning of message A segment by means of which the sender must uniquely identify the PAYMUL message using its type and number and when necessary its function. Note: The identification will be passed back to the ordering customer for reconciliation purposes, if a reference is not quoted in the B- level. DTM, Date/time/period A segment specifying the date and if required the time when the message is created. Segment group 3: D-CTA-COM A group of segments identifying the ordering party, which is valid for all payment orders. D, and address and address for the ordering customer. Detail Section Segment group 4: LIN-DTM-RFF-BUS-FCA-SG5-SG6-SG7-SG8-SG9-SG10- SG11 This segment group contains information regarding the debit side of this transaction and details that are pertinent to all payments specified in the message. Certain payment details may be provided either in segment group 4 or in segment group 11, but not in both. LIN, Line item A segment identifying the line item by a current line number. DTM, Date/time/period A segment identifying the date, at which an order has been requested to be executed or acted upon. RFF, Reference A segment specifying the reference of the single debit amount on the debit side of the Transaction (level B). Note: The identification will be passed back to the Ordering Customer for reconciliation purposes. Edifact/PAYMUL, English version, December 2006-11
BUS, Business function A segment identifying certain characteristics of the payment orders stored on level C, such as business function. FCA, Financial charges allocation A segment specifying the method for allocation of charges and allowances (e.g. charges to be borne by the ordering customer), and identifying the ordering customer s account to which such charges or allowances should be directed where it is different from the principal account. This constitutes a default specification and may be overridden at detail level. Segment group 5: MOA-CUX-DTM-RFF A group of segments containing the currency of the single amounts in level C, currency to be transferred, plus the total of all single amounts of level C. MOA, Monetary amount A segment specifies the total amount and the currency to be transferred. Segment group 6: FII-CTA-COM A group of segments containing the account servicing bank including the account to be debited. If the ordering party is not quoted separately in the D-segment on level B or level A, then this group also contains the information of the ordering party. FII, Financial institution information A segment identifying the financial institution and relevant account number with the currency. Segment group 7: D-CTA-COM A group of segments identifying the ordering party mutually exclusive with D-segment on level A for the ordering party (Ordering customer and payer). Furthermore, one contact party can also be quoted in this group. D, and address A segment identifying the name and address of the non-financial institutions associated with the PAYMUL. Segment group 9: GIS-MOA-LOC-D-RCS-FTX A group of segments providing information for subsequent use by regulatory authorities requiring statistical and other types of data. It also identifies the regulatory authority for which the information is intended followed by the information itself. Edifact/PAYMUL, English version, December 2006-12
This group is mutually exclusive with Segment Group 15. GIS, General indicator A segment identifying what processing should be completed by regulatory authorities. FTX, Free text A segment giving information in coded or in clear form to provide information relevant to regulatory authorities requirements. Segment group 10: PRC-FTX A group of segments: mutually exclusive with level -C- containing the details of payment, which are determined for all payments on level C. PRC, Process identification A segment identifying the kind of free text follows this segment. FTX, Free text A segment for information in coded or in clear form to provide information from the ordering customer to the beneficiary. Segment group 11: SEQ-MOA-DTM-RFF-PAI-FCA-SG12-SG13-SG14-SG15-SG16 This segment group contains information regarding the Beneficiaries of the payments. Certain payment details may be provided either in segment group 11 or in segment group 4, but not in both. SEQ, Sequence details A segment identifying the beginning of the credit side of the transaction (level C) by a sequential number, which may also be used for reconciliation purposes. MOA, Monetary amount A segment giving the amount value of the payment. It is the amount to be transferred. The currency is quoted on the debit side of the transaction (level B). RFF, Reference A segment identifying a transaction from the ordering customer to the beneficiary and/or from the ordering customer to the ordered bank. FCA, Financial charges allocation A segment specifying the method for allocation of charges and allowances and identifying the ordering customer s account to which such charges or allowances should be directed where it is different from the principal amount. This segment is mutually exclusive with the FCA segment in Segment Group 4. Segment group 12: FII-CTA-COM A group of segments containing the beneficiary s bank and the account and if necessary up to two intermediary banks. Edifact/PAYMUL, English version, December 2006-13
FII, Financial institution information A segment identifying the financial institution and relevant account number with the currency. Segment group 13: D-CTA-COM A group of segments identifying the name and address of the beneficiary and one contact party. D, and address A segment identifying the name and address of the nonfinancial institutions associated with the payment on the beneficiary s side. Segment group 15: GIS-MOA-LOC-D-RCS-FTX A group of segments providing information for subsequent use by regulatory authorities requiring statistical and other types of data. It also identifies the regulatory authority for which the information is intended followed by the information itself. GIS, General indicator A segment identifying what processing should be completed by regulatory authorities. FTX, Free text A segment giving information in coded or in clear form to provide information relevant to regulatory authorities requirements. Segment group 16: PRC-FTX-SG17-SG23 A group of segments containing the details of payment. The content of these segments is passed through the banking chain from the ordering customer to the beneficiary. PRC, Process identification A segment identifying the kind of payment details. FTX, Free text A segment providing free text instruction relating to the payment details. Summary Section CNT, Control total A segment identifying the kind of control-checks for the payment orders contained in the PAYMUL and identifying the totals according to the coded form. Segment group 24: AUT-DTM A group of segments specifying the details of any authentication (validation) procedure applied to the PAYMUL message. Edifact/PAYMUL, English version, December 2006-14
AUT, Authentication result A segment specifying details of any authentication (validation) procedures applied to the PAYMUL message. DTM, Date/time/period A segment identifying the validation date/time. UNT, Message trailer A service segment ending a message, giving the total number of segments in the message and the control reference number of the message. UNZ, Interchange message trailer A service segment ending an interchange message. Edifact/PAYMUL, English version, December 2006-15
4. Segments Layout This section describes each segment used in the ING Multiple Payment order message. The original UN/EDIFACT segment layout is listed. The appropriate comments relevant to the ING subset are indicated. Notes 1. the segments are presented in the sequence in which they appear in the message. The segment or segment group tag is followed by the (M)andatory/(C)onditional indicator, the maximum number of occurrences and the segment description 2. reading from left to right, in column one, the data element tags and descriptions are shown, followed by in the second column the EDIFACT status (M or C), the field format, and the picture of the data elements. These first pieces of information constitute the original EDIFACT segment layout. Following the EDIFACT information, ING specific information is provided in the third, fourth, and fifth columns. In the third column a status indicator for the use of (C)onditional EDIFACT data elements (see 2.1 through 2.3 below), in the fourth column the restricted indicator (see point 3), and in the fifth column notes and code values used for specific data elements in the message 2.1 (M)andatory data elements in EDIFACT segments retain their status in the ING-subset. 2.2 Additionally, there are five types of status for data elements with a (C)onditional EDIFACT status, whether for simple, component or composite data elements. These are listed below and can be identified when relevant by the following abbreviations: REQUIRED R Indicates that the entity is required and must be sent. ADVISED A Indicates that the entity is advised or recommended. DEPENDENT D Indicates that the entity must be sent in certain conditions, as defined by the relevant explanatory note. OPTIOL O Indicates that the entity is optional and may be sent at the discretion of the user. NOT USED N Indicates that the entity is not used and should be omitted. 2.3 If a composite is flagged as N, NOT USED, all data elements within that composite will have blank status indicators assigned to them. Edifact/PAYMUL, English version, December 2006-16
3. Status indicators detailed in the fourth column, which directly relate to the code values detailed in the fifth column may have two values: RESTRICTED* A data element marked with an asterisk (*) in the fourth column indicates that the listed codes in column five are the only codes available for use with this data element, in this segment, in this message. OPEN All data elements where coded representation of data is possible and a restricted set of code values is not indicated are open (no asterisk in fourth column). The available codes are listed in the UN/EDIFACT Data Elements and Code Sets Directory. Code values may be given as examples or there may be a note on the format or type of code to be used. 4. You may come across the following abbreviations followed by a figure indicating the number of positions. a9 alpha (letters) with exact length a..9 alpha with length up to maximum an9 alphanumeric with exact length an..9 alphanumeric with length up to maximum n9 numeric with exact length n..9 numeric with length up to maximum 5. Additional information: The tables are followed by Segment Notes at segment level, which give examples of the segment described. Edifact/PAYMUL, English version, December 2006-17
1. UNB: Interchange message header UNB - M 1 - INTERCHANGE MESSAGE HEADER Function A service segment starting and identifying an interchange message EDIFACT ING * Description S001 Syntax identifier M M 0001 Syntax identifier M an4 M * UNOA 0002 Syntax identifier number M an1 M * 2 S002 Interchange sender M M 0004 Sender identification M an..35 M 0007 Partner identification code qualifier O an..4 R * ZZ S003 Interchange recipient M M 0010 Interchange recipient identification M an..35 M Swiftadres 0007 Partner identification code qualifier O an..4 R * 55 S004 Date/time of preparation M M 0017 Date M n6 M YYMMDD 0019 Time M n4 M HHMM 0020 Interchange control reference M an..14 M Identical to element UNZ-0020 S005 Recipient s reference, password C N 0022 Recipient s reference/password M an..14 0025 Recipient s reference/password qualifier C an2 0026 Application reference C an..14 N 0029 Processing priority code C an1 N 0031 Acknowledgement request C n1 N 0032 Communications agreement id C an..35 N 0035 Test indicator C n1 N Segment Notes The combination of the values in data elements S002, S003 and 0020 shall be used to identify uniquely the interchange, for the purpose of acknowledgement. Example: UNB+UNOA:2+CLIENTIDENTIFICATION:ZZ+INGBNL2A:55+060915:1255+0000000235 UNB Segment tag UNOA:2 Syntax identifier and syntax version CLIENTIDENTIFICATION Sender identification ZZ Mutually agreed code a.o.t specific codelist INGBNL2A Recipient identification 55 Bank identifier code 060915:1255 Date/time of preparation of interchange 0000000235 Interchange control reference number (unique in database) Edifact/PAYMUL, English version, December 2006-18
2. UNH: Message header UNH - M 1 - Function MESSAGE HEADER A service segment starting and uniquely identifying a message EDIFACT ING * Description 0062 Message reference number M an..14 M Sender s unique message reference. Sequence S009 MESSAGE IDENTIFIER M M number of messages in the interchange. Generated by the sender 0065 Message type identifier M an..6 M * PAYMUL = Multiple Payment order message 0052 Message type version number M an..3 M * D = Draft directory 0054 Message type release number M an..3 M * 96A = Version 96A 0051 Controlling agency M an..2 M * UN = UN/ECE/TRADE/WP.4, United Nations Standard Messages (UNSM) 0057 Association assigned code C an..6 O ING0.5 0068 Common access reference C an..35 N S010 STATUS OF THE TRANSFER C N 0070 Sequence message transfer number M n..2 0073 First/last sequence message transfer indication C a1 Segment Notes DE s 0065, 0052, 0054 and 0051: Indicate that the message is a UNSM Multiple Payment order message based on the D.96A directory under the control of the United Nations. Example: UNH+3436D22SQ+PAYMUL:D:96A:UN:ING0.5 UNH Segment tag 3436D22SQ Message reference number PAYMUL Message type D Draft 96A Release number UN Controlling agency ING0.5 ING, version 0.5 Edifact/PAYMUL, English version, December 2006-19
3. BGM: Beginning of message BGM - M 1 - Function Beginning of message A segment by means of which the sender must uniquely identify the PAYMUL message using its type and number and when necessary its function EDIFACT ING * Description C002 DOCUMENT/MESSAGE ME C R 1001 Document/message name, coded C an..3 R * 452 = Multiple payment order 1131 Code list qualifier C an..3 N 3055 Code list responsible agency, coded C an..3 N 1000 Document/message name C an..35 N 1004 Document/message number C an..35 R Multiple payment order number assigned by document sender. See Note 1 1225 Message function, coded C an..3 R * 9 = Original 4343 Response type, coded C an..3 N Response wishes of the customer are registered in the contract registration. See Note 1 Segment Notes DE 1225: A message is marked as copy when a duplicate has to be send because the original message is lost. C002-1001: The code 452 identifies the PAYMUL message, but is not related to the products within the message. Note 1: The usage of this element is dependent on the software package used. Please check the Software Specific Annex F. Example: BGM+452+00000032565+9 BGM Segment tag 452 Message type coded (=PAYMUL) 00000032565 Document number (unique in database) 9 Original message Edifact/PAYMUL, English version, December 2006-20
4. DTM: Date/time/period DTM - M 1- Function Date/time/period A segment specifying the date and if required the time when the message is created EDIFACT ING * Description C507 DATE/TIME/PERIOD M M 2005 Date/time/period qualifier M an..3 M * 137 = Document/message date/time 2380 Date/time/period C an..35 R Multiple Payment order creation date 2379 Date/time/period format qualifier C an..3 R * 203 = CCYYMMDDHHMM Segment Notes Example: DTM+137:200002170805:203 DTM Segment tag 137 Document message creation date coded 200609151255 Sept. 15th 2006, 12:55 203 Format qualifier: CCYYMMDDHHMM Edifact/PAYMUL, English version, December 2006-21
5. SG3-D: and address SG3 - D 3 - D - M 1 - Function D and address A segment identifying the name and address of the non-financial institutions associated with the PAYMUL, either by CO82 only and/or structured by CO80 thru 3207 EDIFACT ING * Description 3035 Party qualifier M an..3 M * HQ = Account owner C082 PARTY IDENTIFICATION DETAILS 3039 Party id. Identification M an..35 1131 Code list qualifier C an..3 3055 Code list responsible agency, coded C an..3 C058 ME AND ADDRESS C N 3124 and address line M an..35 3124 and address line C an..35 3124 and address line C an..35 3124 and address line C an..35 3124 and address line C an..35 C080 PARTY ME C R See note 2 3036 Party name M an..35 M Party name in clear text 3036 Party name C an..35 O 3036 Party name C an..35 O 3036 Party name C an..35 O 3036 Party name C an..35 O 3045 Party name format, coded C an..3 N C059 STREET C D See note 2 3042 Street and number/p.o. box M an..35 M Street and number 3042 Street and number/p.o. box C an..35 O 3042 Street and number/p.o. box C an..35 N 3042 Street and number/p.o. box C an..35 N C 3164 name C an..35 D name See note 2 3229 Country sub-entity identification C an..9 N 3251 Postcode identification C an..9 D Postal code See note 2 3207 Country, coded C an..3 R ISO-country code 2 positions See note 2 D Edifact/PAYMUL, English version, December 2006-22
Segment Notes This segment is used to identify the ordering party. Dependency Notes: This segment group is to be used if extended information concerning the ordering party is to be supplied. Only by this segment (data element 3207: Country, coded) it can be determined whether the originating party is non-resident or resident. If this segment group is not used, it is assumed that the originator is resident. Only structured use of this segment is allowed. C080-3036 Party name C059-3042 Street and number or PO BOX 3164 3251 Postcode identification 3207 Country, coded The segment D ( and address) related to the ordering party is supported in two segment groups: either in SG3 or in SG7; in case D is supplied in SG3 the values apply for all multiple payment instructions (batches) within the message. In case D is supplied in SG7 the values apply for the multiple payment instruction only. SG3 and SG7 are mutually exclusive. Note 2: The usage of this element is country specific. Please check the Country Specific Annex E. Example: D+HQ+++JOHNSON+DELFTSTRAAT 78+BURGERDAM+++NL D Segment tag HQ Account owner identification JOHNSON Account owner name DELFSTRAAT 78 Account owner address BURGERDAM Account owner domicile NL Account owner country Edifact/PAYMUL, English version, December 2006-23
6. SG4-LIN: Line item SG4 - M 9999 - LIN-DTM-RFF-BUS-FCA-SG5-SG6-SG7-SG8-SG9-SG10-SG11 LIN - M 1 - Line item Function A segment identifying the line item by a current line number EDIFACT ING * Description 1082 Line item number C n..6 R Application generated unique sequence number of 1229 Action request/notification, C212 coded ITEM NUMBER C an..3 IDENTIFICATION 7140 Item number C an..35 7143 Item number type, coded C an..3 1131 Code list qualifier C an..3 3055 Code list responsible agency, coded C an..3 C829 SUB-LINE INFORMATION C N 5495 Sub-line indicator, coded C an..3 1082 Line item number C n..6 1222 Configuration level C n..2 N 7083 Configuration, coded C an..3 N C N N the lines (individual debit orders) in this multiple payment order message, starting at 1 with increments of 1 Segment Notes Example: LIN+1 LIN Segment tag 1 Line item no 1 (first debit order in this message) Edifact/PAYMUL, English version, December 2006-24
7. SG4-DTM: Date/time/period SG4 - M 9999 - LIN-DTM-RFF-BUS-FCA-SG5-SG6-SG7-SG8-SG9-SG10-SG11 DTM - M 1 - Date/time/period Function A segment identifying the date, at which an order has been requested to be executed or acted upon EDIFACT ING * Description C507 DATE/TIME/PERIOD M M 2005 Date/time/period qualifier M an..3 M * 203 = execution date 2380 Date/time/period C an..35 R Execution date of the payment 2379 Date/time/period format qualifier C an..3 R * 102 = CCYYMMDD Segment Notes This segment is used to specify the execution date of the payment. Example: DTM+203:20060915:102 DTM Segment tag 203 Execution date 20000218 Sept 15th 2006 102 Date format specification: CCYYMMDD Edifact/PAYMUL, English version, December 2006-25
8. SG4-RFF: Reference SG4 - M 9999 - LIN-DTM-RFF-BUS-FCA-SG5-SG6-SG7-SG8-SG9-SG10-SG11 RFF - O 1 - Reference Function A segment specifying the reference of the single debit amount on the debit side of the Transaction (level B) EDIFACT ING * Description C506 REFERENCE M M 1153 Reference qualifier M an..3 M * CR = Customer Reference 1154 Reference number C an..35 R Reference 1156 Line number C an..6 N 4000 Reference version number C an..35 N Segment Notes This segment is used to provide any references relevant to the current payment. Example: RFF+CR: SAL. AFDELING INKOOP RFF Segment tag CR Specification of reference type SAL. AFDELING INKOOP Reference Edifact/PAYMUL, English version, December 2006-26
9. SG4-BUS: Business function SG4 - M 9999 - LIN-DTM-RFF-BUS-FCA-SG5-SG6-SG7-SG8-SG9-SG10-SG11 BUS - O 1 - Business function Function A segment identifying certain characteristics of the payment orders stored on level C, such as business function EDIFACT ING * Description C521 BUSINESS FUNCTION C - 4027 Business function qualifier M an..3-4025 Business function, coded M an..3-1131 Code list qualifier C an..3-3055 Code list responsible agency, coded C an..3-4022 Business description C an..70-3279 Geographic environment, coded C an..3 R * - DO : Domestic - DR : Domestic regulatory - IN : International - IR : International regulatory - IS : European Union This code is not required by the customer; if not supplied type is traced back from payment. See Note 1 4487 Type of financial transaction, C an..3 O 1 = Clean payment Coded C551 BANK OPERATION C D 4383 Bank operation, coded M an..3 M UGI = Urgent payment DDT = Direct debit 1131 Code list qualifier C an..3 N 3055 Code list responsible agency, coded C an..3 N 4463 Intra-company payment, coded C an..3 O 1 = Intra-company See note 1 and 2 Edifact/PAYMUL, English version, December 2006-27
Segment Notes This segment is used to provide information related to the transaction type for the current level B payment orders. Note 1: The usage of this element is dependent on the software package used. Please check the Software Specific Annex F and Annex G Rules to determine transaction type, on how the transaction type (product) can be traced back from the contents of the payment. Note 2: The usage of this element is country specific. Please check the Country Specific Annex E. Domestic account Credit Debit Legacy currency or EUR Resident Non-resident Foreign currency account Foreign currency Foreign account Domestic account Resident DO DO/DR IN/IR IN/IR IN/IR Non-resident DO/DR DO/DR IN/IR IN/IR IN/IR Foreign currency account IN/IR IN/IR IN/IR IN/IR IN/IR DO = Domestic IN = Cross border DR = Domestic with regulatory reporting, country specific IR = Cross border with regulatory reporting, country specific Regulatory reporting is to be supplied by: the ordering customer and/or the beneficiary and/or the receiving financial institution and/or the beneficiary financial institution Which party has to supply, is country specific. Please check the Country Specific Annex E. Example : BUS++IN+1+UGI BUS Segment tag IN International payment (cross border) 1 Clean payment UGI Urgent (cf. BGI: Normal) Edifact/PAYMUL, English version, December 2006-28
10. SG4-FCA: Financial charges allocation SG4 - M 9999 - FCA - O 1 - Function LIN-DTM-RFF-BUS-FCA-SG5-SG6-SG7-SG8-SG9-SG10-SG11 Financial charges allocation A segment specifying the method for allocation of charges and allowances and identifying the ordering customer s account to which such charges or allowances should be directed where it is different from the principal amount EDIFACT ING * Description 4471 Settlement, coded M an..3 M * 13 = All charges borne by payee C878 CHARGE/ALLOWANCE ACCOUNT C D 3434 Institution branch number M an..17 R See Note 1131 Code list qualifier C an..3-25 3055 Code list responsible agency, coded C an..3-5 3194 Account holder number C an..35 O See Note 1 6345 Currency, coded C an..3 D See Note 1 14 = Each pay own cost 15 = All charges borne by payer Segment Notes When this segment is not used, the default is used (14 = Each pay own cost). The segment FCA (Financial charges allocation) is supported in two segment groups: either in SG4 or in SG11; in case FCA is supplied in SG4 the values apply for all payments within the multiple payment, in case FCA is supplied in SG11 the values apply for the current payment within the multiple payment. SG4 and SG11 are mutually exclusive. Note: The usage of the institution branch number is mandatory. ING will not validate or process this element. Note 1: The usage of this element is dependent on the software package used. Please check the Software Specific Annex F. Example: FCA+13+123456789::::EUR FCA Segment tag 13 All charges borne by payee 123456789 Institution branch number EUR ISO currency code (Euro) Edifact/PAYMUL, English version, December 2006-29
11. SG5-MOA: Monetary amount SG4 - M 9999 - LIN-DTM-RFF-BUS-FCA-SG5-SG6-SG7-SG8-SG9-SG10-SG11 SG5 - R 1 - MOA-CUX-DTM-RFF MOA - M 1 - Monetary amount Function A segment specifying the total debit amount and the currency to be transferred EDIFACT ING * Description C516 MONETARY AMOUNT M M 5025 Monetary amount type qualifier M an..3 M * 9 = Amount due/payable 5004 Monetary amount C n..18 R Debit amount 6345 Currency, coded C an..3 R ISO 4217 three alpha codes, refer to Annex C 6343 Currency qualifier C an..3 N 4405 Status, coded C an..3 N Segment Notes This segment is used to specify the total amount and the currency of the transactions on the level C. Example: MOA+9:452317,45:EUR MOA Segment tag 9 Total amount of this debit order 452317,45 Amount EUR Currency ISO code Edifact/PAYMUL, English version, December 2006-30
12. SG6-FII: Financial institution information SG4 - M 9999 - SG6 - M 1 - FII - M 1 - Function LIN-DTM-RFF-BUS-FCA-SG5-SG6-SG7-SG8-SG9-SG10-SG11 FII-CTA-COM Financial institution information A segment identifying the financial institution and relevant account number with the currency EDIFACT ING * Description 3035 Party qualifier M an..3 M * OR = Ordered Bank C078 ACCOUNT IDENTIFICATION C R 3194 Account holder number C an..35 R Account. See Note 1 3192 Account holder name C an..35 O. See Note 2 3192 Account holder name C an..35 O 6345 Currency, coded C an..3 R ISO 4217 three alpha codes. Refer to Annex C C088 INSTITUTION IDENTIFICATION C D 3433 Institution name identification C an..11 R BIC-code (Bank Identification Code = Swift) See Note 1 1131 Code list qualifier C an..3 R * 25 = Bank identification 3055 Code list responsible agency, coded C an..3 R * 5 = ISO 3434 Institution branch number C an..17 D See Note 1 and 2 1131 Code list qualifier C an..3 D 3055 Code list responsible agency, coded C an..3 D 3432 Institution name C an..70 D 3436 Institution branch place C an..70 N 3207 Country, coded C an..3 D ISO 3166 two alpha codes (either this or the BIC must be available) See Note 1 and 2 Segment Notes This segment is used to identify the account to be debited and the bank where the account is held. The preferred format of the account for international payments should be the IBAN-format 1. If the account is in IBAN-format it is put in field 3194. If not, the way to fill in this segment is country-dependent. If not specified in the table below, the entire account is also put in field 3194. Note 1: The usage of this element is dependent on the software package used. Please check the Software Specific Annex F. Note 2: The usage of this element is country specific 1. Please check the Country Specific Annex E. If an IBAN account is used the elements: 6345 (Currency, coded), 3433 (Institution name identification), 3434 (Institution branch number) and 3207 (Country, coded) are optional. Example : FII+OR+0987654321:SMIT:AMSTERDAM+:::987654 FII Segment tag OR Partner indicator (ordered bank) 0987654321 Account holder number SMIT:AMSTERDAM and domicile of account holder 987654 Branch number of ordered bank 1 The IBAN will become the standard in the future (see ECBS for more explanation). If the IBAN check-digit is not yet known, it should be left blank; also for the bank code preceding the account for some countries. Edifact/PAYMUL, English version, December 2006-31
13. SG7-D: and address SG4 - M 9999 - SG7 - D 3 - D - M 1 - Function LIN-DTM-RFF-BUS-FCA-SG5-SG6-SG7-SG8-SG9-SG10-SG11 D-CTA-COM and address A segment identifying the name and address of the non-financial institutions associated with the PAYMUL, either by CO82 only and/or structured by CO80 thru 3207 EDIFACT ING * Description 3035 Party qualifier M an..3 M * HQ = Account owner C082 PARTY IDENTIFICATION DETAILS C D 3039 Party id. identification M an..35 1131 Code list qualifier C an..3 3055 Code list responsible agency, coded C an..3 C058 ME AND ADDRESS C N 3124 and address line M an..35 3124 and address line C an..35 3124 and address line C an..35 3124 and address line C an..35 3124 and address line C an..35 C080 PARTY ME C O See Note 2 3036 Party name M an..35 M Party name in clear text. 3036 Party name C an..35 O 3036 Party name C an..35 O 3036 Party name C an..35 O 3036 Party name C an..35 O 3045 Party name format, coded C an..3 N C059 STREET C O See Note 2 3042 Street and number/p.o. box M an..35 M Street and number. 3042 Street and number/p.o. box C an..35 O 3042 Street and number/p.o. box C an..35 N 3042 Street and number/p.o. box C an..35 N 3164 name C an..35 D name. See Note 2 3229 Country sub-entity identification C an..9 N 3251 Postcode identification C an..9 D Postal code. See Note 2 3207 Country, coded C an..3 R ISO-country code 2 positions. See Note 2 Edifact/PAYMUL, English version, December 2006-32
Segment Notes This segment group is to be used if extended information concerning the ordering party is to be supplied. Only by this segment (data element 3207: Country, coded) it can be determined whether the originating party is non-resident or resident. If this segment group is not used, it is assumed that the originator is resident. Only structured use of this segment is allowed. C080-3036 Party name C059-3042 Street and number or PO BOX 3164 3251 Postcode identification 3207 Country, coded The segment D ( and address) related to the ordering party is supported in two segment groups: either in SG3 or in SG7; in case D is supplied in SG3 the values apply for all multiple payment instructions (batches) within the message. In case D is supplied in SG7 the values apply for the multiple payment instruction only. SG3 and SG7 are mutually exclusive. Note 2: The usage of this element is country specific. Please check the Country Specific Annex E. Example: D+HQ+++JOHNSON+DELFTSTRAAT 78+BURGERDAM+++NL D Segment tag HQ Account owner identification JOHNSON Account owner name DELFSTRAAT 78 Account owner address BURGERDAM Account owner domicile NL Account owner country Edifact/PAYMUL, English version, December 2006-33
14. SG9-GIS: General indicator SG4 - M 9999 - LIN-DTM-RFF-BUS-FCA-SG5-SG6-SG7-SG8-SG9-SG10-SG11 SG9 - O 10 - GIS-MOA-LOC-D-RCS-FTX GIS - M 1 - General indicator Function A segment group used for regulatory information EDIFACT ING * Description C529 Processing indicator M M 7365 Processing indicator, coded M an..3 M * See Note 1 and 2 1131 Code list qualifier C an..3 N 3055 Code list responsible agency, coded C an..3 N 7187 Process type identification C an..17 N Segment Notes The segment GIS (General indicator) is supported in two segment groups: either in SG9 or in SG15; in case GIS is supplied in SG9 the values apply for all payments within the multiple payment, in case GIS is supplied in SG15 the values apply for the current payment within the multiple payment. SG9 and SG15 are mutually exclusive. Note 1: The usage of this element is dependent on the software package used. Please check the Software Specific Annex F. Note 2: The usage of this element is country specific. Please check the Country Specific Annex E. Example: GIS+63 GIS Segment tag 63 Reporting via a bank with forwarding abroad denied Edifact/PAYMUL, English version, December 2006-34
15. SG9-FTX: Free text SG4 - M 9999 - LIN-DTM-RFF-BUS-FCA-SG5-SG6-SG7-SG8-SG9-SG10-SG11 SG9 - O 10 - GIS-MOA-LOC-D-RCS-FTX FTX - M 10 - Free text Function A segment used for Central Bank Reporting information EDIFACT ING * Description 4451 Text subject qualifier M an..3 M * REG = Regulatory information 4453 Text function, coded C an..3 N C107 TEXT REFERENCE C N 4441 Free text, coded M an..3 1131 Code list qualifier C an..3 3055 Code list responsible agency, coded C an..3 C108 TEXT LITERAL C R See Note 2 4440 Free text M an..70 M 4440 Free text C an..70 O 4440 Free text C an..70 O 4440 Free text C an..70 O 4440 Free text C an..70 O 3453 Language, coded C an..3 N Segment Notes This segment is used to provide Central Bank Reporting information. If this segment is used, the Central Bank Reporting is valid for all transactions of level C. This segment is mutually exclusive with SG15-FTX. Note 2: The usage of this element is country specific. Please check the Country Specific Annex E. Example: FTX+REG+++INVOICE LINE 1:INVOICE LINE 2:87654321:02:4321 FTX Segment tag REG Regulatory information INVOICE LINE 1 Line 1 of information INVOICE LINE 2 Line 2 of information 87654321:02:4321 Reg.No., Article No and Trader No. Edifact/PAYMUL, English version, December 2006-35
16. SG10-PRC: Process identification SG4 - M 9999 - LIN-DTM-RFF-BUS-FCA-SG5-SG6-SG7-SG8-SG9-SG10-SG11 SG10 - O 1 - PRC-FTX PRC - M 1 - Process identification Function A segment identifying the kind of payment details EDIFACT ING * Description C242 PROCESS TYPE AND DESCRIPTION M M 7187 Process type identification M an..17 M * 11 = Processing of unstructured information 1131 Code list qualifier C an..3 N 3055 Code s list responsible agency, coded C an..3 N 7186 Process type C an..35 N 7186 Process type C an..35 N Segment Notes The segment PRC (Process identification) is supported in two segment groups: either in SG10 or in SG16; in case PRC is supplied in SG10 the values apply for all payments within the multiple payment, in case PRC is supplied in SG16 the values apply for the current payment within the multiple payment. Example : PRC+11 PRC Segment tag 11 Unstructured information Edifact/PAYMUL, English version, December 2006-36
17. SG10-FTX: Free text SG4 - M 9999 - LIN-DTM-RFF-BUS-FCA-SG5-SG6-SG7-SG8-SG9-SG10-SG11 SG10 - O 1 - PRC-FTX FTX - M 1 - Free text Function EDIFACT ING * Description 4451 Text subject qualifier M an..3 M * PMD = Payment detail/remittance information 4453 Text function, coded C an..3 N C107 TEXT REFERENCE C N 4441 Free text, coded M an..3 1131 Code list qualifier C an..3 3055 Code list responsible agency, coded C an..3 C108 TEXT LITERAL C R See Note 4440 Free text M an..70 M 4440 Free text C an..70 O 4440 Free text C an..70 O 4440 Free text C an..70 O 4440 Free text C an..70 O 3453 Language, coded C an..3 N Edifact/PAYMUL, English version, December 2006-37