Try it now Login

Message type

UN/EDIFACT BOPDIR

Bank-to-customer direct debit message. It is published in 60 directory versions of the UN/EDIFACT standard, each defining its own segment structure.

Open the D24A BOPDIR specification
Message
BOPDIR
Directory versions
60
Latest
D24A

Sending and receiving

Exchange BOPDIR with your trading partners

The specification tells you what a valid BOPDIR looks like. Sending and receiving one means mapping it to the system that holds the data, agreeing the format with each partner, and handling the messages that come back when something is rejected. XEDI does the mapping, validation and transport.

Browse integrations Connect BOPDIR to your ERP, WMS or accounting system Find your trading partner Document requirements by partner Talk to an EDI specialist Scope a BOPDIR flow with us

Specifications

BOPDIR in every directory version

A trading partner names both the message and the directory, for example D00A BOPDIR, because the segments differ between versions. Open the one your partner specified.

60 directory versions

Related messages

Messages in the BOP set

UN/EDIFACT groups related documents under a shared three-letter stem. These usually appear together in one trading flow.

BOPBNK Bank-to-bank payment initiation message. BOPCUS Bank-to-customer payment message. BOPINF Bank operation information message.

Frequently asked questions

What is the BOPDIR message?

Bank-to-customer direct debit message. It is one of the UN/EDIFACT message types, identified by the six-letter name BOPDIR in every directory version that publishes it.

Which directory version of BOPDIR do I need?

The one your trading partner specifies. BOPDIR is published in 60 directory versions and the segment detail differs between them, so a mapping built for one version is not automatically valid for another.

How do I send a BOPDIR message?

Map the data from the system that holds it into the segment structure the agreed directory version defines, then transport it by the route the partner uses, commonly AS2 or SFTP. XEDI handles the mapping, validation and transport, and surfaces the acknowledgements and errors that come back.

Sources and further reading