EANCOM® 2002 S3 Part II
DIRDEB Direct debit message
1. Introduction

Status

MESSAGE TYPE : DIRDEB
REFERENCE DIRECTORY : D.01B
EANCOM® SUBSET VERSION : 003

Definition

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).

Note: Throughout this document the term 'Creditor' refers to either a Beneficiary, Payee or Supplier, likewise the term 'Debtor' refers to either an Ordering Customer, Payor, or Buyer.

Prior to the Direct Debit procedure, some agreement(s) would usually have been concluded :

The term 'pre-authorisation' refers to an agreement between a Creditor and a Debtor for:

The agreement can also be made between the debtor and his bank, independently of the amount of the DIRDEB.

Principles

*           Notes.

The Multiple Direct Debit message is structured in three levels: A, B, and C.

Level A

Header Section - This section, A, contains general data related to the whole message and is contained in Segment Groups 1, 2, 3 and 24.

Level B

Credit Side Detail - This section, B, contains batches of data. Each batch is organised from the credit side’s perspective, i.e. one credit account, one currency, one execution day and one credit batch total amount. Each batch then contains detailed data which applies to all the dependent C levels, i.e. the individual direct debit transactions, and is contained in Segment Group 4 through Segment Group 10.

Level C

Direct Debit Detail - This section, C, contains data related to the debit side, i.e. the individual direct debit transactions. The data is a unique set for each direct debit transaction and is contained in Segment Group 11 through Segment Group 23. There can be one or many individual transactions within each batch.

The structure of the message is designed to allow several B level batches, each being followed by one or more related C level transactions. Each C level is followed by its associated remittance details.

*           Scenario.

While the Direct Debit message is similar in content to the Multiple Payment Order (PAYMUL) message, it is very different in application. The Multiple Payment Order message is sent by an ordering party (normally the payer or buyer) to instruct it’s bank to effect a payment to a names beneficiary or beneficiaries (payee or supplier). The Direct Debit message is almost a complete inversion of this scenario.

The Direct Debit message is sent by a Creditor (beneficiary/payee/supplier) to its bank instructing the bank to collect funds from the account of a Debtor (payer/buyer). The Direct Debit message will normally be subject to a Direct Debit Mandate. A Direct Debit Mandate is an agreement between the Creditor and the Debtor, which allows the Creditor to demand payment from the bank of the Debtor.

 

wpe8.jpg (29199 Byte)

 

The processes which follow the Direct Debit are the same as those which occur after a Multiple Payment Order message, i.e., debiting of the debtors account is reported to the debtor using the Multiple Debit Advice (DEBMUL) message, crediting of the Creditor’s account is reported to the creditor using the Multiple Credit Advice (WREMUL) message, etc.

© Copyright GS1 Edition 2016