Release Notification System (RNS) (Customs Glossary Guide): Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
{{note|This article is part of the [[Customs_Glossary_Guide|Customs Glossary Guide]]|info}} | {{note|This article is part of the [[Customs_Glossary_Guide|Customs Glossary Guide]]|info}} | ||
<div class="bc-wrap"> | |||
= | <div class="bc-article-hero"> | ||
<h1>Release Notification System (RNS)</h1> | |||
<p>The automated messaging system used by the CBSA to notify brokers, carriers, and warehouses of release decisions.</p> | |||
<div class="bc-article-meta"> | |||
<span class="bc-article-pill"><i class="fas fa-rss"></i> Type: Electronic Messaging</span> | |||
<span class="bc-article-pill"><i class="fas fa-flag-canada"></i> Region: Canada (CBSA)</span> | |||
</div> | |||
</div> | |||
<div class="bc-card"> | |||
= | <h2 style="margin-top: 0;">Overview</h2> | ||
<p>The **Release Notification System (RNS)** is a critical electronic data interchange (EDI) service provided by the **Canada Border Services Agency (CBSA)**. It acts as the "official notification channel" that tells trade chain partners when goods have been legally released by Customs.</p> | |||
<p>While systems like **[[ACI_eManifest_Software_User_Guide_(CBSA)|ACI eManifest]]** are used to *submit* data to the CBSA, the RNS is used by the CBSA to *reply* with status updates. It automatically transmits release decisions to:</p> | |||
<div class="bc-cleanlist"> | |||
* **Customs Brokers** (to confirm their entry was accepted). | |||
* **Carriers** (to confirm they can deliver the goods). | |||
* **Warehouse Operators** (to confirm they can release the freight from their bond). | |||
</div> | |||
<div class="bc-did-you-know" style="margin-top: 15px;"> | |||
<strong>The "RNS" vs. "WACM" Connection:</strong> RNS is often paired with the **Warehouse Arrival Certification Message (WACM)**. When a warehouse operator scans a shipment as "Arrived," the RNS system instantly triggers a release message if the broker's entry is already on file. | |||
</div> | |||
<div style="clear: both;"></div> | |||
</div> | |||
<h2 style="margin-top: 40px; border-bottom: 2px solid #eee; padding-bottom: 10px;">How RNS Works</h2> | |||
<div class="bc-card"> | |||
<p>The RNS cycle ensures that goods do not move into the Canadian economy until duties are accounted for and security risks are assessed.</p> | |||
<h3>1. The Setup</h3> | |||
<p>Carriers, brokers, and warehouses register with the CBSA to receive RNS messages. They are assigned a participant ID.</p> | |||
<h3>2. The Link</h3> | |||
<p>The link between the physical goods and the release decision is the **Transaction Number** (e.g., the PARS number). | |||
* The **Carrier** submits the PARS on their manifest. | |||
* The **Broker** submits the PARS on their entry (B3/CADEX). | |||
* The **CBSA** system matches them.</p> | |||
<h3>3. The Notification</h3> | |||
<p>Once the CBSA officer (or the automated system) makes a decision, an RNS message is broadcast to all relevant parties. This eliminates the need for phone calls or physical stamps on paperwork.</p> | |||
</div> | |||
<h2 style="margin-top: 40px; border-bottom: 2px solid #eee; padding-bottom: 10px;">Common RNS Status Codes</h2> | |||
<div class="bc-card"> | |||
<p>Participants receive specific codes indicating the status of the shipment. Understanding these is vital for avoiding penalties (like delivering unreleased goods).</p> | |||
<table class="wikitable" style="width: 100%;"> | |||
<tr> | |||
<th style="width: 20%;">Status Code</th> | |||
<th>Description</th> | |||
<th>Action Required</th> | |||
</tr> | |||
<tr> | |||
<td><strong>Released</strong></td> | |||
<td>The goods have been released by the CBSA.</td> | |||
<td>The carrier may deliver the goods to the consignee.</td> | |||
</tr> | |||
<tr> | |||
<td><strong>Refer to Secondary</strong></td> | |||
<td>The goods have been selected for examination (VACIS, offload, or document review).</td> | |||
<td>Do <strong>not</strong> deliver. The driver must report to the examination area or warehouse immediately.</td> | |||
</tr> | |||
<tr> | |||
<td><strong>Authorized to Deliver</strong></td> | |||
<td>Used for <strong>In-Bond</strong> movements. The goods are not released into the economy, but are allowed to move to a bonded warehouse or another port.</td> | |||
<td>Move the goods to the specified inland warehouse.</td> | |||
</tr> | |||
<tr> | |||
<td><strong>Reject</strong></td> | |||
<td>The entry or manifest data contains an error (e.g., invalid Cargo Control Number).</td> | |||
<td>The broker or carrier must correct the data and resubmit.</td> | |||
</tr> | |||
</table> | |||
</div> | |||
<h2 style="margin-top: 40px; border-bottom: 2px solid #eee; padding-bottom: 10px;">Usage Scenarios</h2> | |||
<div class="bc-card"> | |||
<p>RNS streamlines operations in three distinct scenarios:</p> | |||
The | <h3>1. The Highway Border Crossing (PARS)</h3> | ||
<div class="bc-cleanlist"> | |||
* <strong>Scenario:</strong> A truck arrives at the Windsor-Detroit border. | |||
* <strong>RNS Usage:</strong> As the truck crosses the sensor, the CBSA officer accepts the declaration. An **RNS Release Message** is instantly sent to the Broker and the Carrier's dispatch system. The dispatcher knows the truck is clear before the driver even calls in. | |||
</div> | |||
= | <h3>2. The Sufferance Warehouse (WACM)</h3> | ||
<div class="bc-cleanlist"> | |||
* <strong>Scenario:</strong> Goods are moved in-bond to a warehouse in Toronto to await clearance. | |||
* <strong>RNS Usage:</strong> The warehouse operator sends a **WACM** (Arrival Message) to CBSA. This triggers the RNS system to check for the broker's entry. If found, an **RNS Release** is sent back to the warehouse, allowing the driver to pick up the freight. | |||
</div> | |||
The | <h3>3. The Exam</h3> | ||
<div class="bc-cleanlist"> | |||
* <strong>Scenario:</strong> A shipment is flagged for a soil inspection (CFIA). | |||
* <strong>RNS Usage:</strong> An RNS **"Refer to Secondary"** message is broadcast. The warehouse operator locks the shipment in the system, preventing it from being gated out until a subsequent "Released" message is received. | |||
</div> | |||
</div> | |||
<h2 style="margin-top: 40px; border-bottom: 2px solid #eee; padding-bottom: 10px;">Usage in BorderConnect</h2> | |||
<div class="bc-card"> | |||
<p>BorderConnect is fully integrated with the RNS system, providing carriers with real-time visibility.</p> | |||
<h3>PARS Tracker</h3> | |||
<p>BorderConnect's **PARS Application** listens for RNS messages 24/7. | |||
* <strong>Auto-Status:</strong> When an RNS release is received, the shipment status in BorderConnect updates from "On File" to "Released." | |||
* <strong>Driver Alerts:</strong> The system can automatically SMS or email the driver to let them know they are clear to cross or leave the warehouse.</p> | |||
<h3>WACM (Warehouse)</h3> | |||
<p>For warehouse operators using BorderConnect, the software automatically generates the WACM upon arrival scan and processes the incoming RNS release to update inventory.</p> | |||
</div> | |||
<h2 style="margin-top: 40px; border-bottom: 2px solid #eee; padding-bottom: 10px;">Official Resources</h2> | |||
<div class="bc-card"> | |||
<div class="bc-cleanlist"> | |||
* <strong>CBSA Technical Guide:</strong> [https://www.cbsa-asfc.gc.ca/eservices/eccrd-excc-eng.html Electronic Commerce Client Requirements Document (ECCRD)] | |||
* <strong>RNS Participants:</strong> [https://www.cbsa-asfc.gc.ca/eservices/rns-snml-eng.html Release Notification System (RNS) Overview] | |||
* <strong>Memorandum D17-1-4:</strong> [https://www.cbsa-asfc.gc.ca/publications/dm-md/d17/d17-1-4-eng.html Release of Commercial Goods] | |||
</div> | |||
</div> | |||
{{AppPromo}} | |||
</div> | |||
[[Category:Customs Glossary Guide]] | [[Category:Customs Glossary Guide]] | ||