View source for Electronic Data Interchange (EDI)

{{note|This article is part of the [[Customs_Glossary_Guide|Customs Glossary Guide]]|info}}
<div class="bc-wrap">

<div class="bc-article-hero">
<h1>Electronic Data Interchange (EDI) Explained</h1>
<p>The digital language that allows carriers, brokers, and customs agencies to communicate trade data instantly and without paper.</p>
<div class="bc-article-meta">
<span class="bc-article-pill"><i class="fas fa-network-wired"></i> Type: Data Protocol</span>
<span class="bc-article-pill"><i class="fas fa-server"></i> Standards: ANSI X12 / EDIFACT</span>
<span class="bc-article-pill"><i class="fas fa-exchange-alt"></i> Usage: ACE & ACI</span>
</div>
</div>

<div class="bc-card">
<h2 style="margin-top: 0;">What is EDI?</h2>

<p><strong>Electronic Data Interchange (EDI)</strong> 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.</p>

<p>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.</p>

[[Image:Edi-customs-workflow.jpg|800px|center|Customs EDI Workflow]]

<h3>The "Language" of Trade</h3>
<p>Just as humans speak English or French, computers speak in EDI standards. The two most common "languages" used in North American customs are:</p>
<div class="bc-cleanlist">
* <strong>ANSI X12:</strong> The standard predominantly used in the United States by CBP (e.g., The "309" Manifest transaction).
* <strong>UN/EDIFACT:</strong> The international standard used by CBSA in Canada (e.g., The "CUSCAR" Customs Cargo message).
</div>
</div>

<h2 style="margin-top: 40px; border-bottom: 2px solid #eee; padding-bottom: 10px;">EDI in Customs: A History</h2>

<div class="bc-card">
<p>Customs agencies were among the earliest adopters of EDI technology to manage the growing volume of international trade.</p>

<div class="bc-grid bc-2col">
<div class="bc-card" style="border-top: 3px solid #003366;">
<h3>🇺🇸 CBP (USA)</h3>
<p><strong>1984 - ACS:</strong> CBP (then U.S. Customs Service) launched the <strong>Automated Commercial System (ACS)</strong>. This was the first major EDI system allowing brokers to transmit entry data electronically.</p>

<p><strong>2001 - ACE:</strong> CBP began developing the <strong>Automated Commercial Environment (ACE)</strong> to replace ACS. This modernized system became the "Single Window" for all trade data.</p>

<p><strong>2015 - Mandatory eManifest:</strong> The use of EDI for all electronic import manifests became mandatory, officially ending the era of paper processing for major commercial flows.</p>
</div>

<div class="bc-card" style="border-top: 3px solid #d80621;">
<h3>🇨🇦 CBSA (Canada)</h3>
<p><strong>1988 - CADEX:</strong> Canada introduced <strong>CADEX</strong> (Customs Automated Data Exchange), allowing importers and brokers to send accounting documents electronically.</p>

<p><strong>2004 - ACI (Marine):</strong> The <strong>Advance Commercial Information (ACI)</strong> program launched, requiring marine carriers to transmit EDI data 24 hours before loading.</p>

<p><strong>2011/2012 - eManifest (Highway):</strong> ACI was expanded to highway carriers, requiring truck manifests to be sent via EDI at least one hour before arrival at the border.</p>
</div>
</div>
</div>

<h2 style="margin-top: 40px; border-bottom: 2px solid #eee; padding-bottom: 10px;">How It Works: The Data Loop</h2>

<div class="bc-card">

<p>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.</p>

<table class="wikitable" style="width: 100%;">
<tr>
<th style="width: 25%;">Step</th>
<th>Action</th>
<th>Example Status</th>
</tr>
<tr>
<td><strong>1. Transmission</strong></td>
<td>The Carrier (via BorderConnect) sends the <strong>Manifest Data</strong> to Customs.</td>
<td><em>"Sent to CBP"</em></td>
</tr>
<tr>
<td><strong>2. Acknowledgment</strong></td>
<td>Customs receives the file and checks for syntax errors.</td>
<td><em>"Accepted"</em> or <em>"Rejected"</em></td>
</tr>
<tr>
<td><strong>3. Status Update</strong></td>
<td>Customs processes the data and sends a status update back to the carrier.</td>
<td><em>"Entry Numbers on File"</em></td>
</tr>
<tr>
<td><strong>4. Release/Hold</strong></td>
<td>A final EDI message is sent when the goods are released or held for inspection.</td>
<td><em>"Release Notification"</em></td>
</tr>
</table>
</div>

<h2 style="margin-top: 40px; border-bottom: 2px solid #eee; padding-bottom: 10px;">The Role of BorderConnect</h2>

<div class="bc-card">

<p>Most trucking companies do not employ computer programmers to write raw ANSI X12 or EDIFACT code. This is where <strong>BorderConnect</strong> fits in.</p>

<h3>The "Translator"</h3>
<p>BorderConnect acts as a <strong>Value-Added Network (VAN)</strong> and software provider.</p>
<div class="bc-cleanlist">
* <strong>User Input:</strong> You type "100 Boxes of Auto Parts" into the BorderConnect webpage.
* <strong>Translation:</strong> BorderConnect's engine converts that into the complex EDI string (e.g., <code>N1*CN*BORDERCONNECT*92...</code>).
* <strong>Transmission:</strong> We transmit that code securely to CBP or CBSA via a direct line.
* <strong>Decoding:</strong> When Customs sends a reply code (e.g., <code>4C</code>), we translate that back into plain English: "Shipment Released."
</div>

<div class="bc-did-you-know">
<strong>RNS Integration:</strong><br>
BorderConnect also uses EDI to connect with Customs Brokers via the <strong>Release Notification System (RNS)</strong>. This allows carriers to see exactly when a broker has submitted their entry, automatically updating the manifest status from "Draft" to "On File."
</div>
</div>

</div>

[[Category:Definitions]]
[[Category:Customs Technology]]