Message type
UN/EDIFACT RECORD
RECORD is a UN/EDIFACT message published in 49 directory versions of the standard. A written summary of its purpose has not been added to this library yet; the segment structure for each version is complete and linked below.
Open the D24A RECORD specification- Message
- RECORD
- Directory versions
- 49
- Latest
- D24A
Sending and receiving
Exchange RECORD with your trading partners
The specification tells you what a valid RECORD 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.
Specifications
RECORD in every directory version
A trading partner names both the message and the directory, for example D00A RECORD, because the segments differ between versions. Open the one your partner specified.
49 directory versions
- D00A RECORD segment structure, data elements and codes for D00A
- D00B RECORD segment structure, data elements and codes for D00B
- D01A RECORD segment structure, data elements and codes for D01A
- D01B RECORD segment structure, data elements and codes for D01B
- D01C RECORD segment structure, data elements and codes for D01C
- D02A RECORD segment structure, data elements and codes for D02A
- D02B RECORD segment structure, data elements and codes for D02B
- D03A RECORD segment structure, data elements and codes for D03A
- D03B RECORD segment structure, data elements and codes for D03B
- D04A RECORD segment structure, data elements and codes for D04A
- D04B RECORD segment structure, data elements and codes for D04B
- D05A RECORD segment structure, data elements and codes for D05A
- D05B RECORD segment structure, data elements and codes for D05B
- D06A RECORD segment structure, data elements and codes for D06A
- D06B RECORD segment structure, data elements and codes for D06B
- D07A RECORD segment structure, data elements and codes for D07A
- D07B RECORD segment structure, data elements and codes for D07B
- D08A RECORD segment structure, data elements and codes for D08A
- D08B RECORD segment structure, data elements and codes for D08B
- D09A RECORD segment structure, data elements and codes for D09A
- D09B RECORD segment structure, data elements and codes for D09B
- D10A RECORD segment structure, data elements and codes for D10A
- D10B RECORD segment structure, data elements and codes for D10B
- D11A RECORD segment structure, data elements and codes for D11A
- D11B RECORD segment structure, data elements and codes for D11B
- D12A RECORD segment structure, data elements and codes for D12A
- D12B RECORD segment structure, data elements and codes for D12B
- D13A RECORD segment structure, data elements and codes for D13A
- D13B RECORD segment structure, data elements and codes for D13B
- D14A RECORD segment structure, data elements and codes for D14A
- D14B RECORD segment structure, data elements and codes for D14B
- D15A RECORD segment structure, data elements and codes for D15A
- D15B RECORD segment structure, data elements and codes for D15B
- D16A RECORD segment structure, data elements and codes for D16A
- D16B RECORD segment structure, data elements and codes for D16B
- D17A RECORD segment structure, data elements and codes for D17A
- D17B RECORD segment structure, data elements and codes for D17B
- D18A RECORD segment structure, data elements and codes for D18A
- D18B RECORD segment structure, data elements and codes for D18B
- D19A RECORD segment structure, data elements and codes for D19A
- D19B RECORD segment structure, data elements and codes for D19B
- D20A RECORD segment structure, data elements and codes for D20A
- D20B RECORD segment structure, data elements and codes for D20B
- D21A RECORD segment structure, data elements and codes for D21A
- D21B RECORD segment structure, data elements and codes for D21B
- D22A RECORD segment structure, data elements and codes for D22A
- D22B RECORD segment structure, data elements and codes for D22B
- D23A RECORD segment structure, data elements and codes for D23A
- D24A RECORD segment structure, data elements and codes for D24A
Related messages
Messages in the REC set
UN/EDIFACT groups related documents under a shared three-letter stem. These usually appear together in one trading flow.
Frequently asked questions
Which directory version of RECORD do I need?
The one your trading partner specifies. RECORD is published in 49 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 RECORD 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
- GS1 EDI standards GS1 guidance on EDI standards used for supply-chain document exchange.
- UNECE introduction to UN/EDIFACT United Nations guidance on UN/EDIFACT for structured business data exchange.
- X12 EDI standards Official X12 standards body for North American EDI transaction standards.
- OpenPeppol post-award specifications OpenPeppol documentation for e-procurement and e-invoicing specifications.