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

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