972-836-7750 Request a demo Talk to an expert
Talk to an expert Request a demo Call sales 972-836-7750

EDIFACT message guide · Finance

DIRDEB Direct debit

The UN/EDIFACT message a creditor sends its bank to collect amounts from debtors' accounts under prior direct debit agreements.

Sent by
Creditor
Received by
Creditor's bank
Standard
UN/EDIFACT · Batch message
X12 equivalent
No direct equivalent

What is the EDIFACT DIRDEB message?

DIRDEB is the UN/EDIFACT direct debit message. A creditor sends it to its bank to request collection of amounts from debtors' accounts. The directory notes that agreements are usually in place first: between the creditor and its bank, setting the conditions of the direct debit service, and between the debtor and the debtor's bank, pre-authorizing the debits.

Direct debits suit recurring collections such as subscriptions, utility bills and insurance premiums. The bank collects the funds through the clearing system and reports results, including returned debits, back to the creditor.

How the EDIFACT DIRDEB message worksDiagram of the UN/EDIFACT DIRDEB Direct debit message. Creditor sends it to creditor's bank. It usually starts the exchange. It is usually followed by BANSTA and CREMUL. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message) and DTM (Date/time/period) and body and segment groups: the required SG4 loop with LIN (Line item), the required SG6 loop with FII (Financial institution information) and the required SG11 loop with SEQ (Sequence details) and MOA (Monetary amount). 14 conditional segment groups are listed by their trigger segment.How the EDIFACT DIRDEB message worksDirect debit: who sends it, where it fits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeDIRDEBSENDERCreditorRECEIVERCreditor's bankCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYBANSTABanking statusCREMULMultiple credit advice2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDsUNB … UNZMessage DIRDEBUNH … UNTSTART OF MESSAGEBGMBeginning of messageDTMDate/time/periodBODY AND SEGMENT GROUPSMandatory group SG4 · repeats up to 9,999LINLine itemMandatory group SG6 · repeats up to 1FIIFinancial institution informationMandatory group SG11 · repeats many timesSEQSequence detailsMOAMonetary amount+ 14 conditional groups, starting with:RFFFIINADMOAINPGEIPRCAUTBlue box: mandatory segment group. Conditional groups are listed by the trigger segment that starts them; a group is sent only when its data applies.Conditional segments outside groups are not drawn.Structure: mandatory segments and groups in the UN/EDIFACT directory D.21A listing for DIRDEB. Your trading partner's implementation guide adds itsown requirements.
How the EDIFACT DIRDEB message worksDiagram of the UN/EDIFACT DIRDEB Direct debit message. Creditor sends it to creditor's bank. It usually starts the exchange. It is usually followed by BANSTA and CREMUL. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message) and DTM (Date/time/period) and body and segment groups: the required SG4 loop with LIN (Line item), the required SG6 loop with FII (Financial institution information) and the required SG11 loop with SEQ (Sequence details) and MOA (Monetary amount). 14 conditional segment groups are listed by their trigger segment.How the EDIFACT DIRDEBmessage worksDirect debit: who sends it, where it fits andwhat the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeDIRDEBSENDERCreditorRECEIVERCreditor's bankCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYBANSTABanking statusCREMULMultiple credit advice2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDs(UNB … UNZ)Message DIRDEB (UNH … UNT)START OF MESSAGEBGMBeginning of messageDTMDate/time/periodBODY AND SEGMENT GROUPSMandatory group SG4 · repeats upto 9,999LINLine itemMandatory group SG6 · repeatsup to 1FIIFinancial institutioninformationMandatory group SG11 · repeatsmany timesSEQSequence detailsMOAMonetary amount+ 14 conditional groups, starting with:RFFFIINADMOAINPGEIPRCAUTBlue box: mandatory segment group. Conditionalgroups are listed by the trigger segment thatstarts them; a group is sent only when its dataapplies. Conditional segments outside groups arenot drawn.Structure: mandatory segments and groups in theUN/EDIFACT directory D.21A listing for DIRDEB.Your trading partner's implementation guide adds itsown requirements.

How to read this diagram: the top row shows who sends DIRDEB, to whom, and which messages usually come before and after it. The lower part shows what the directory D.21A itself requires: the envelopes around DIRDEB and the segments and segment groups it marks mandatory. Conditional groups are listed by their trigger segment rather than drawn in full. This is the directory's minimum, not a trading partner's requirement: a message implementation guide, such as an industry subset or a partner’s own guide, usually makes some conditional groups mandatory, restricts the codes and may use an older directory.

Expand diagram Download SVG

When it is used

  • Collecting recurring payments from customers
  • Collecting invoice amounts under a direct debit agreement
  • Resubmitting collections after returns

Where it fits in the message flow

This message DIRDEB Direct debit
Usually followed by BANSTA Banking statusCREMUL Multiple credit advice

Structure

Mandatory segments in DIRDEB (directory D.21A)

In UN/EDIFACT directory D.21A, the DIRDEB message has 89 segment positions arranged in 24 segment groups. These are the segments and segment groups marked mandatory at message level, in order; a mandatory group is shown with the segment that starts it. Segments inside conditional groups are needed only when the group is used. This is the directory’s requirement, not your trading partner’s: each partner’s message implementation guide names the directory it uses, often an older one such as D.96A or D.01B where the structure can differ, makes some conditional segments mandatory and restricts the codes.

  • UNH
  • BGM
  • DTM
  • SG4 (LIN)
  • UNT

Practical example

DIRDEB in practice

A gym chain collects monthly membership fees by direct debit. On the first of each month its billing system sends its bank a DIRDEB with each member's account, the amount and the mandate reference. The bank collects the funds, reports rejected debits, and credits the total, which the chain reconciles with a CREMUL.

Implementation

Implementation considerations for DIRDEB

  • Hold valid mandates or authorizations for every debtor.
  • Follow the scheme rules and timelines of the local clearing system.
  • Process returned or rejected debits promptly.
  • Check whether the bank expects DIRDEB or an ISO 20022 direct debit format.

How ECOM helps

Automate DIRDEB with ECOM

Solution

Financial Document Automation

Automate invoices, remittances, payment files and bank statements from capture to posting.

Industry

Financial Services

Secure file transfer and B2B integration for banks and financial institutions.

Solution

Order-to-Cash Automation

Automate the flow from purchase order to payment across every customer channel.

Compare X12 and EDIFACT, or see answers to general questions in the EDI FAQ.

Related messages

Related finance messages

All 37 finance messages

Need help with DIRDEB?

ECOM maps, tests and monitors EDIFACT messages for your trading partners and integrates them with your ERP.

Request a Demo Contact us