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

CUSPED Periodic customs declaration

The UN/EDIFACT message a declarant uses to submit a periodic declaration of goods imported or exported over a period.

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

What is the EDIFACT CUSPED message?

CUSPED is the UN/EDIFACT periodic customs declaration. The directory defines it as a message that transfers data from a declarant to a customs administration to meet legislative and operational requirements for the periodic declaration of goods for import or export.

Under simplified procedures, authorized traders can move goods with minimal data at the time of crossing and declare them in full afterwards, for example monthly. CUSPED carries that supplementary or periodic declaration, with the goods, values and duties for the period.

How the EDIFACT CUSPED message worksDiagram of the UN/EDIFACT CUSPED Periodic customs declaration message. Declarant, such as an authorized trader or 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). 6 conditional segment groups are listed by their trigger segment.How the EDIFACT CUSPED message worksPeriodic customs declaration: who sends it, where it fits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeCUSPEDSENDERDeclarant, such as anauthorized trader orbrokerRECEIVERCustomsadministrationCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYCUSRESCustoms response2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDsUNB … UNZMessage CUSPEDUNH … UNTSTART OF MESSAGEBGMBeginning of messageBODY AND SEGMENT GROUPS+ 6 conditional groups, starting with:RFFNADMOATAXDMSAUTBlue 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 CUSPED. Your trading partner's implementation guide adds itsown requirements.
How the EDIFACT CUSPED message worksDiagram of the UN/EDIFACT CUSPED Periodic customs declaration message. Declarant, such as an authorized trader or 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). 6 conditional segment groups are listed by their trigger segment.How the EDIFACT CUSPEDmessage worksPeriodic customs declaration: who sends it,where it fits and what the directory marksmandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeCUSPEDSENDERDeclarant, suchas an authorizedtrader or brokerRECEIVERCustomsadministrationCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYCUSRESCustoms response2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDs(UNB … UNZ)Message CUSPED (UNH … UNT)START OF MESSAGEBGMBeginning of messageBODY AND SEGMENT GROUPS+ 6 conditional groups, starting with:RFFNADMOATAXDMSAUTBlue 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 CUSPED.Your trading partner's implementation guide adds itsown requirements.

How to read this diagram: the top row shows who sends CUSPED, 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 CUSPED 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

  • Submitting supplementary declarations under simplified procedures
  • Declaring a month's imports or exports in one submission
  • Reporting duties due for the period

Where it fits in the message flow

This message CUSPED Periodic customs declaration
Usually followed by CUSRES Customs response

Structure

Mandatory segments in CUSPED (directory D.21A)

In UN/EDIFACT directory D.21A, the CUSPED message has 102 segment positions arranged in 34 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
  • UNT

Practical example

CUSPED in practice

An authorized importer clears goods at the border with simplified entries during the month. At month end it sends customs a CUSPED with every import line for the month, the tariff classifications, values and duties. Customs validates the declaration and debits the duties from the importer's deferment account.

Implementation

Implementation considerations for CUSPED

  • Hold the customs authorization for simplified or periodic declarations.
  • Reconcile periodic declarations with simplified entries made during the period.
  • Meet the submission deadline for each period.
  • Follow the national specification in force.

How ECOM helps

Automate CUSPED 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 CUSPED?

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

Request a Demo Contact us