Try it now Login

Message type

UN/EDIFACT PAYORD

Payment order message. It is published in 60 directory versions of the UN/EDIFACT standard, each defining its own segment structure.

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

Sending and receiving

Exchange PAYORD with your trading partners

The specification tells you what a valid PAYORD 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 PAYORD to your ERP, WMS or accounting system Find your trading partner Document requirements by partner Talk to an EDI specialist Scope a PAYORD flow with us

Specifications

PAYORD in every directory version

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

60 directory versions

Related messages

Messages in the PAY set

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

PAYDUC Deferred payment advice (due check). PAYEXT Payment execution message. PAYMUL Multiple payment advice message.

Frequently asked questions

What is the PAYORD message?

Payment order message. It is one of the UN/EDIFACT message types, identified by the six-letter name PAYORD in every directory version that publishes it.

Which directory version of PAYORD do I need?

The one your trading partner specifies. PAYORD 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 PAYORD 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