Electronic Data Interchange (EDI)
|
🔖 This article is part of the Customs Glossary Guide |
Electronic Data Interchange (EDI) Explained
The digital language that allows carriers, brokers, and customs agencies to communicate trade data instantly and without paper.
What is EDI?
Electronic Data Interchange (EDI) is the computer-to-computer exchange of business documents in a standard electronic format between business partners. In the context of cross-border logistics, it replaces paper manifests, invoices, and release documents with digital messages.
Before EDI, a carrier would arrive at the border with a stack of paper. The officer would have to manually type that information into their system. With EDI, the data is transmitted, processed, and risk-assessed long before the truck arrives.
The "Language" of Trade
Just as humans speak English or French, computers speak in EDI standards. The two most common "languages" used in North American customs are:
- ANSI X12: The standard predominantly used in the United States by CBP (e.g., The "309" Manifest transaction).
- UN/EDIFACT: The international standard used by CBSA in Canada (e.g., The "CUSCAR" Customs Cargo message).
EDI in Customs: A History
Customs agencies were among the earliest adopters of EDI technology to manage the growing volume of international trade.
🇺🇸 CBP (USA)
1984 - ACS: CBP (then U.S. Customs Service) launched the Automated Commercial System (ACS). This was the first major EDI system allowing brokers to transmit entry data electronically.
2001 - ACE: CBP began developing the Automated Commercial Environment (ACE) to replace ACS. This modernized system became the "Single Window" for all trade data.
2015 - Mandatory eManifest: The use of EDI for all electronic import manifests became mandatory, officially ending the era of paper processing for major commercial flows.
🇨🇦 CBSA (Canada)
1988 - CADEX: Canada introduced CADEX (Customs Automated Data Exchange), allowing importers and brokers to send accounting documents electronically.
2004 - ACI (Marine): The Advance Commercial Information (ACI) program launched, requiring marine carriers to transmit EDI data 24 hours before loading.
2011/2012 - eManifest (Highway): ACI was expanded to highway carriers, requiring truck manifests to be sent via EDI at least one hour before arrival at the border.
How It Works: The Data Loop
An EDI transmission follows a strict "Request and Response" cycle. This ensures that the sender knows exactly what the receiver (Customs) did with the data.
| Step | Action | Example Status |
|---|---|---|
| 1. Transmission | The Carrier (via BorderConnect) sends the Manifest Data to Customs. | "Sent to CBP" |
| 2. Acknowledgment | Customs receives the file and checks for syntax errors. | "Accepted" or "Rejected" |
| 3. Status Update | Customs processes the data and sends a status update back to the carrier. | "Entry Numbers on File" |
| 4. Release/Hold | A final EDI message is sent when the goods are released or held for inspection. | "Release Notification" |
The Role of BorderConnect
Most trucking companies do not employ computer programmers to write raw ANSI X12 or EDIFACT code. This is where BorderConnect fits in.
The "Translator"
BorderConnect acts as a Value-Added Network (VAN) and software provider.
- User Input: You type "100 Boxes of Auto Parts" into the BorderConnect webpage.
- Translation: BorderConnect's engine converts that into the complex EDI string (e.g.,
N1*CN*BORDERCONNECT*92...). - Transmission: We transmit that code securely to CBP or CBSA via a direct line.
- Decoding: When Customs sends a reply code (e.g.,
4C), we translate that back into plain English: "Shipment Released."
RNS Integration:
BorderConnect also uses EDI to connect with Customs Brokers via the Release Notification System (RNS). This allows carriers to see exactly when a broker has submitted their entry, automatically updating the manifest status from "Draft" to "On File."