Try it now Login

Message type

UN/EDIFACT CUSPED

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

Sending and receiving

Exchange CUSPED with your trading partners

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

Specifications

CUSPED in every directory version

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

54 directory versions

Related messages

Messages in the CUS set

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

CUSCAR Customs cargo report (arrival). CUSDEC Customs declaration message. CUSEXP Customs export declaration message. CUSREP Customs report (status and queries). CUSRES Customs response to declaration.

Frequently asked questions

Which directory version of CUSPED do I need?

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