972-836-7750 Request a demo Talk to an expert
Talk to an expert Request a demo Call sales 972-836-7750

EDIFACT message guide · Customs and regulatory

CUSDEC Customs declaration

The UN/EDIFACT message declarants use to submit customs declarations for import, export or transit to a customs administration.

Sent by
Declarant, such as an importer, exporter or customs broker
Received by
Customs administration
Standard
UN/EDIFACT · Batch message
X12 equivalent
No direct equivalent

What is the EDIFACT CUSDEC message?

CUSDEC is the UN/EDIFACT customs declaration message. It transfers data from a declarant to a customs administration to meet legislative and operational requirements for declaring goods for import, export or transit. The directory notes other uses too, such as passing consignment data from an exporter to an importer, or between customs administrations.

A declaration carries the parties, the customs procedure, the goods with their tariff classification, origin, value and quantities, and the duties and taxes. Customs answers with CUSRES. Each administration publishes its own implementation, and some are moving to newer formats, so declarants must follow the national specification in force.

How the EDIFACT CUSDEC message worksDiagram of the UN/EDIFACT CUSDEC Customs declaration message. Declarant, such as an importer, exporter or customs broker sends it to customs administration. It usually starts the exchange. It is usually followed by CUSRES. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message) and body and segment groups: UNS (Section control) and UNS (Section control). 11 conditional segment groups are listed by their trigger segment.How the EDIFACT CUSDEC message worksCustoms declaration: who sends it, where it fits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeCUSDECSENDERDeclarant, such as animporter, exporter orcustoms brokerRECEIVERCustomsadministrationCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYCUSRESCustoms response2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDsUNB … UNZMessage CUSDECUNH … UNTSTART OF MESSAGEBGMBeginning of messageBODY AND SEGMENT GROUPSUNSSection controlUNSSection control+ 11 conditional groups, starting with:RFFTDTDOCNADTODMOAEFIDMSCSTTAXAUTBlue box: mandatory segment group. Conditional groups are listed by the trigger segment that starts them; a group is sent only when its data applies.Conditional segments outside groups are not drawn.Structure: mandatory segments and groups in the UN/EDIFACT directory D.21A listing for CUSDEC. Your trading partner's implementation guide adds itsown requirements.
How the EDIFACT CUSDEC message worksDiagram of the UN/EDIFACT CUSDEC Customs declaration message. Declarant, such as an importer, exporter or customs broker sends it to customs administration. It usually starts the exchange. It is usually followed by CUSRES. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message) and body and segment groups: UNS (Section control) and UNS (Section control). 11 conditional segment groups are listed by their trigger segment.How the EDIFACT CUSDECmessage worksCustoms declaration: who sends it, where it fitsand what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeCUSDECSENDERDeclarant, suchas an importer,exporter orcustoms brokerRECEIVERCustomsadministrationCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYCUSRESCustoms response2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDs(UNB … UNZ)Message CUSDEC (UNH … UNT)START OF MESSAGEBGMBeginning of messageBODY AND SEGMENT GROUPSUNSSection controlUNSSection control+ 11 conditional groups, starting with:RFFTDTDOCNADTODMOAEFIDMSCSTTAXAUTBlue box: mandatory segment group. Conditionalgroups are listed by the trigger segment thatstarts them; a group is sent only when its dataapplies. Conditional segments outside groups arenot drawn.Structure: mandatory segments and groups in theUN/EDIFACT directory D.21A listing for CUSDEC.Your trading partner's implementation guide adds itsown requirements.

How to read this diagram: the top row shows who sends CUSDEC, to whom, and which messages usually come before and after it. The lower part shows what the directory D.21A itself requires: the envelopes around CUSDEC and the segments and segment groups it marks mandatory. Conditional groups are listed by their trigger segment rather than drawn in full. This is the directory's minimum, not a trading partner's requirement: a message implementation guide, such as an industry subset or a partner’s own guide, usually makes some conditional groups mandatory, restricts the codes and may use an older directory.

Expand diagram Download SVG

When it is used

  • Declaring imported goods for release into free circulation
  • Lodging export declarations
  • Declaring goods for transit

Where it fits in the message flow

This message CUSDEC Customs declaration
Usually followed by CUSRES Customs response

Structure

Mandatory segments in CUSDEC (directory D.21A)

In UN/EDIFACT directory D.21A, the CUSDEC message has 165 segment positions arranged in 52 segment groups. These are the segments and segment groups marked mandatory at message level, in order; a mandatory group is shown with the segment that starts it. Segments inside conditional groups are needed only when the group is used. This is the directory’s requirement, not your trading partner’s: each partner’s message implementation guide names the directory it uses, often an older one such as D.96A or D.01B where the structure can differ, makes some conditional segments mandatory and restricts the codes.

  • UNH
  • BGM
  • UNS
  • UNS
  • UNT

Practical example

CUSDEC in practice

A customs broker clears a container of machine parts for an importer. Its declaration software sends a CUSDEC with the importer, the supplier, each item's tariff code, origin and customs value, and the duties calculated. The customs administration replies with a CUSRES accepting the declaration and releasing the goods.

Implementation

Implementation considerations for CUSDEC

  • Follow the national customs specification, which defines the CUSDEC subset and codes.
  • Check whether the administration has moved to a newer declaration format.
  • Validate tariff codes and values before submission to avoid penalties.
  • Process CUSRES responses promptly, since they control release.

How ECOM helps

Automate CUSDEC with ECOM

Industry

Trucking and Transportation

Load tenders, responses, status and freight invoices for carriers, brokers and shippers, integrated with the TMS.

Solution

Logistics Automation

Automate tenders, status updates, freight invoices and warehouse orders with logistics partners.

Solution

EDI Integration

Exchange X12 and EDIFACT documents with partners and integrate them directly with your ERP.

Compare X12 and EDIFACT, or see answers to general questions in the EDI FAQ.

Related messages

Related customs and regulatory messages

All 14 customs and regulatory messages

Need help with CUSDEC?

ECOM maps, tests and monitors EDIFACT messages for your trading partners and integrates them with your ERP.

Request a Demo Contact us