United Nations Directories
for Electronic Data Interchange for
Administration, Commerce and Transport



 UN/EDIFACT

Message Type : DIRDEB Version : D Release : 18A Contr. Agency: UN Revision : 6 Date : 2018-05-04 SOURCE: TBG5 Finance CONTENTS Direct debit message 0. INTRODUCTION 1. SCOPE 1.1 Functional definition 1.2 Field of application 1.3 Principles 2. REFERENCES 3. TERMS AND DEFINITIONS 3.1 Standard terms and definitions 4. MESSAGE DEFINITION 4.1 Segment clarification 4.2 Segment index (alphabetical sequence by tag) 4.3 Message structure 4.3.1 Segment table --------------------------------------------------------------------------- For general information on UN standard message types see UN Trade Data Interchange Directory, UNTDID, Part 4, Section 2.3, UN/ECE UNSM General Introduction --------------------------------------------------------------------------- 0. INTRODUCTION This specification provides the definition of the Direct debit message (DIRDEB) to be used in Electronic Data Interchange (EDI) between trading partners involved in administration, commerce and transport. 1. SCOPE 1.1 Functional definition Prior to the Direct Debit procedure, some agreement(s) would usually have been concluded : - agreement between the Creditor and his Bank (mainly to specify the conditions of credit and the kind of direct debit). - agreement between the Debtor and the Debtor's Bank (i.e. pre- authorization and condition of debit), or between the Creditor and the Debtor. A Direct Debit is sent by the Creditor to the Creditor's Bank instructing it to claim specified amount(s) from the Debtor(s) and to credit the amount(s) to an account specified in the message, which the Creditor's Bank services for the Creditor in settlement of the referenced transaction(s). Throughout this document the term 'Creditor' refers to either a Beneficiary or a Payee, likewise the term 'Debtor' refers to either an Ordering Customer or a Payor. The term 'Bank' may be interpreted as any financial institution. The term 'pre-authorization' refers to an agreement between a Creditor and a Debtor for - either automatic debiting, as required, - or for debiting unless rejected by the debtor in a period of time. The agreement can also be made between the debtor and his bank, independently of the amount of the DIRDEB. 1.2 Field of application The Direct debit message may be used for both national and international applications. It is based on universal practice related to administration, commerce and transport, and is not dependent on the type of business or industry. This message type may be applied, for both national and international settlements, but it is based on the national existing rules of the debit side. 1.3 Principles - A Direct Debit may cover the financial settlement(s) of one or more commercial trade transactions, such as invoices, credit notes, debit notes, etc. It is not intended for use in securities trading. - Several credit accounts, execution dates and currencies may be specified. - Charges may be borne on account(s) different of the account(s) held by the Creditor. - The Creditor's Bank may need a confirmation/authorization (AUTHOR) from the creditor to be able to process the Direct Debit Message. - Pre-authorized and non pre-authorized direct debits shall not be mixed within the same message. - The only way to modify a Direct Debit message is to cancel the whole message or a transaction thereof (e.g. by the use of the FINCAN message). In that respect, one to many order(s) could be cancelled within the message, avoiding to be obliged to cancel the whole message. The cancellation of a message can only be effected by the originator of the message. The kind of cancellation is dependent upon the process of the message or a transaction of it. 2. REFERENCES See UNTDID, Part 4, Chapter 2.3 UN/ECE UNSM - General Introduction, Section 1. 3. TERMS AND DEFINITIONS 3.1 Standard terms and definitions See UNTDID, Part 4, Chapter 2.3 UN/ECE UNSM - General Introduction, Section 2. 4. MESSAGE DEFINITION 4.1 Segment clarification This section should be read in conjunction with the segment table which indicates mandatory, conditional and repeating requirements. The following semantic principles applying to the message are intended to facilitate the understanding of the message: The Direct Debit message is structured in three levels: A, B and C. - Level A contains general data related to the whole message and is contained in Segment Groups 1, 2, 3 and 24. - Level B contains data from the credit side (one credit account, one currency, one execution day) and data which applies to all the dependent C levels and is contained in Segment Group 4 through Segment Group 10. - Level C contains mainly data related to the debit side and, may contain remittance information. This data is considered as unique for each debit transaction and is contained in Segment Group 11 through Segment Group 23. The structure of the message is designed to allow several B levels, each B level being followed by its related C levels. 00010 UNH, Message header A service segment starting and uniquely identifying a message. The message type code for the Direct debit message is DIRDEB. Note: Direct debit messages conforming to this document must contain the following data in segment UNH, composite S009: Data element 0065 DIRDEB 0052 D 0054 18A 0051 UN 00020 BGM, Beginning of message A segment by means of which the sender must uniquely identify the DIRDEB message using its type (e.g., kind of pre-authorized instructions or not pre-authorized) and number and its function. The requirement for a response, e.g., related credit advices, may be indicated. Note: The identification of the DIRDEB will be passed back to the creditor for reconciliation purposes. 00030 DTM, Date/time/period A segment specifying the date and/or time the message is created. 00040 BUS, Business function A segment identifying certain characteristics of the DIRDEB, such as, its business function. In so doing, it provides information about the message that may be used to route the message within an institution, for tariffing, or for the provision of some statistical information. 00050 Segment group 1: RFF-DTM A group of segments identifying a previously sent message. 00060 RFF, Reference A segment identifying a previously sent message. 00070 DTM, Date/time/period A segment identifying the date/time of the previously sent message. 00080 Segment group 2: FII-CTA-COM A group of segments identifying the financial institutions involved in the direct debit, their functions and their contacts. 00090 FII, Financial institution information A segment identifying the financial institution associated with the transaction and their functions. 00100 CTA, Contact information A segment identifying a person or a department for the party specified in the leading FII segment to whom communication should be directed. 00110 COM, Communication contact A segment identifying communication type(s) and number(s) of person(s) or department(s) specified in the associated CTA segment. 00120 Segment group 3: NAD-CTA-COM A group of segments identifying the name(s) and address(es) of each non-financial party involved in the transaction, their functions and their contacts. 00130 NAD, Name and address A segment identifying names and addresses of the parties associated with the direct debit, in coded or uncoded form, and their functions. 00140 CTA, Contact information A segment identifying a person or a department for the party specified in the leading NAD segment and to whom communication should be directed. 00150 COM, Communication contact A segment identifying communication type(s) and number(s) of person(s) or department(s) specified in the associated CTA segment. 00160 Segment group 4: LIN-DTM-RFF-BUS-FCA-SG5-SG6-SG7-SG8-SG9-SG10-SG11 A group of segments containing information regarding the credit side of the transaction and details which are pertinent to all direct debits specified within the group. Certain payment details may be provided either in segment group 4 or in segment group 11, but not in both. 00170 LIN, Line item A segment identifying the beginning of the credit side of the transaction (B level) by a sequential line number, which may also be used for reconciliation purposes. 00180 DTM, Date/time/period A segment identifying the date, at which an order has been requested to be executed or acted upon. 00190 RFF, Reference A segment specifying reference of the single credit amount on the credit side of the transaction (B level). Note: The identification will be passed back to the creditor for reconciliation purposes. 00200 BUS, Business function A segment identifying certain characteristics of the direct debits stored on the debit side of the transaction (C level), such as business function. 00210 FCA, Financial charges allocation A segment specifying the method for allocation of charges and allowances and identifying the creditor'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 is mutually exclusive with the FCA segment in Segment Group 11. 00220 Segment group 5: MOA-CUX-DTM-RFF A group of segments containing the currency of the single amounts on the debit side of the transaction (C level), currency to be collected, plus the total of all single amounts of the debit side of the transaction (C level). 00230 MOA, Monetary amount A segment specifying the total amount and the cu