Try it now Login

Message type

UN/EDIFACT ISENDS

ISENDS is a UN/EDIFACT message published in 48 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 ISENDS specification
Message
ISENDS
Directory versions
48
Latest
D24A

Sending and receiving

Exchange ISENDS with your trading partners

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

Specifications

ISENDS in every directory version

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

48 directory versions

Frequently asked questions

Which directory version of ISENDS do I need?

The one your trading partner specifies. ISENDS is published in 48 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 ISENDS 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