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

CODENO Permit expiration/clearance ready notice

The UN/EDIFACT message giving notice of cargo whose permits or customs documents are about to expire, or for which clearance is complete.

Sent by
Terminal, shipping line or customs-related party
Received by
Shipping line, consignee, forwarder or inland carrier
Standard
UN/EDIFACT · Batch message
X12 equivalent
No direct equivalent

What is the EDIFACT CODENO message?

CODENO is the UN/EDIFACT permit expiration/clearance ready notice. The directory defines it as a notice specifying the cargo for which either the validity of permits or customs documents expires at short notice, or for which regulatory customs clearance has taken place. It is part of the family of container messages for intermodal handling.

For importers and carriers, the notice is a prompt: an expiring permit needs action before the cargo becomes non-compliant, and a clearance-ready notice means containers can be collected.

How the EDIFACT CODENO message worksDiagram of the UN/EDIFACT CODENO Permit expiration/clearance ready notice message. Terminal, shipping line or customs-related party sends it to shipping line, consignee, forwarder or inland carrier. It usually starts the exchange. It is usually followed by COREOR. 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: the required SG2 loop with TDT (Transport information), the required SG4 loop with NAD (Name and address) and the required SG11 loop with EQD (Equipment details). 6 conditional segment groups are listed by their trigger segment.How the EDIFACT CODENO message worksPermit expiration/clearance ready notice: who sends it, where it fits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeCODENOSENDERTerminal, shipping lineor customs-relatedpartyRECEIVERShipping line,consignee, forwarderor inland carrierCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYCOREORContainer release order2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDsUNB … UNZMessage CODENOUNH … UNTSTART OF MESSAGEBGMBeginning of messageBODY AND SEGMENT GROUPSMandatory group SG2 · repeats up to 1TDTTransport informationMandatory group SG4 · repeats up to 9NADName and addressMandatory group SG11 · repeats up to 999EQDEquipment details+ 6 conditional groups, starting with:RFFLOCCTAGIDDGSTMPBlue 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 CODENO. Your trading partner's implementation guide adds itsown requirements.
How the EDIFACT CODENO message worksDiagram of the UN/EDIFACT CODENO Permit expiration/clearance ready notice message. Terminal, shipping line or customs-related party sends it to shipping line, consignee, forwarder or inland carrier. It usually starts the exchange. It is usually followed by COREOR. 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: the required SG2 loop with TDT (Transport information), the required SG4 loop with NAD (Name and address) and the required SG11 loop with EQD (Equipment details). 6 conditional segment groups are listed by their trigger segment.How the EDIFACT CODENOmessage worksPermit expiration/clearance ready notice: whosends it, where it fits and what the directorymarks mandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeCODENOSENDERTerminal,shipping line orcustoms-relatedpartyRECEIVERShipping line,consignee,forwarder orinland carrierCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYCOREORContainer release order2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDs(UNB … UNZ)Message CODENO (UNH … UNT)START OF MESSAGEBGMBeginning of messageBODY AND SEGMENT GROUPSMandatory group SG2 · repeats upto 1TDTTransport informationMandatory group SG4 · repeats upto 9NADName and addressMandatory group SG11 · repeats upto 999EQDEquipment details+ 6 conditional groups, starting with:RFFLOCCTAGIDDGSTMPBlue 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 CODENO.Your trading partner's implementation guide adds itsown requirements.

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

  • Warning that a customs permit or document is about to expire
  • Notifying that customs clearance is complete
  • Prompting collection of cleared containers

Where it fits in the message flow

This message CODENO Permit expiration/clearance ready notice
Usually followed by COREOR Container release order

Structure

Mandatory segments in CODENO (directory D.21A)

In UN/EDIFACT directory D.21A, the CODENO message has 37 segment positions arranged in 14 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
  • SG2 (TDT)
  • SG4 (NAD)
  • SG11 (EQD)
  • UNT

Practical example

CODENO in practice

Import containers at a terminal have been cleared by customs. The terminal sends the shipping line and the consignee's forwarder a CODENO reporting the containers as cleared and ready. The forwarder books trucks for collection, and the line issues the release order.

Implementation

Implementation considerations for CODENO

  • Route expiry warnings to the people who can renew permits.
  • Use clearance notices to trigger pickup planning.
  • Match notices to containers and customs references exactly.
  • Follow local port community specifications.

How ECOM helps

Automate CODENO with ECOM

Industry

Trucking and Transportation

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

Solution

Supply Chain Visibility

Track orders, shipments and invoices across partners and catch exceptions early.

Solution

Logistics Automation

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

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 CODENO?

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

Request a Demo Contact us