Warehouse Arrival Certification Message (WACM) Guide (CBSA): Difference between revisions
No edit summary |
No edit summary Β |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
{{note|This article is part of the [[PARS_Checking_Software_User_Guide_(CBSA_Shipments)|BorderConnect PARS Software Guide]]|info}} | {{note|This article is part of the [[PARS_Checking_Software_User_Guide_(CBSA_Shipments)|BorderConnect PARS Software Guide]]|info}} | ||
<div class="bc-wrap"> | |||
<div class="bc-article-hero"> | |||
<h1>Sending Warehouse Arrival Certification Messages (WACM)</h1> | |||
<p>Instructions for sufferance warehouse operators to report cargo arrivals to CBSA via RNS.</p> | |||
<div class="bc-article-meta"> | |||
<span class="bc-article-pill"><i class="fas fa-warehouse"></i> Type: Compliance Reporting</span> | |||
<span class="bc-article-pill"><i class="fas fa-flag-canada"></i> System: CBSA RNS</span> | |||
</div> | |||
</div> | |||
<div class="bc-card"> | |||
<div class="bc-float-video" style="margin-top: 0;"> | |||
Β <div class="bc-video-trigger" data-video-id="J6ny2lShlqU"> | |||
Β Β <div class="bc-play-icon"><i class="fas fa-play-circle"></i></div> | |||
Β </div> | |||
</div> | |||
<h2 style="margin-top: 0;">Overview</h2> | |||
<p>This guide provides instructions for using BorderConnect to transmit <strong>Warehouse Arrival Certification Messages (WACM)</strong> through the CBSA <strong>Release Notification System (RNS)</strong>.</p> | |||
<p>A <strong>Warehouse Arrival Certification Message (WACM)</strong> is an electronic arrival message sent by a sufferance warehouse operator to CBSA when <strong>unreleased cargo physically arrives</strong> at the sufferance warehouse, and liability transfers from the carrier to the warehouse.<ref>CBSA Memorandum D3-4-2 β Highway pre-arrival and reporting requirements (Definitions β WACM). https://www.cbsa-asfc.gc.ca/publications/dm-md/d3/d3-4-2-eng.html</ref></p> | |||
<div class="bc-did-you-know" style="margin-top: 15px;"> | |||
<strong>Prerequisite:</strong> This guide assumes you have an active subscription and your RNS/WACM onboarding with CBSA is complete. | |||
</div> | |||
<div style="clear: both;"></div> | |||
</div> | |||
= | <h2 style="margin-top: 40px; border-bottom: 2px solid #eee; padding-bottom: 10px;">Regulatory Background</h2> | ||
<div class="bc-card"> | |||
<p>Sufferance warehouse operators are required to transmit a WACM when unreleased goods physically arrive at the warehouse to which they are destined (Customs Sufferance Warehouse Regulations, section 14).<ref>CBSA Customs Notice 22-17 β Mandatory electronic notification of cargo at sufferance warehouses. https://www.cbsa-asfc.gc.ca/publications/cn-ad/cn22-17-eng.html</ref></p> | |||
CBSA | <p>CBSA introduced the mandatory electronic arrival requirement via regulatory amendments in May 2015.<ref>Canada Gazette β Regulations Amending Certain Regulations Made Under the Customs Act (May 6, 2015). https://gazette.gc.ca/rp-pr/p2/2015/2015-05-06/html/sor-dors90-eng.html</ref></p> | ||
<h3>Who Must Transmit?</h3> | |||
<p>A WACM must be transmitted by registered participants in CBSAβs <strong>Release Notification System (RNS)</strong> using <strong>Electronic Data Interchange (EDI)</strong>. Clients and/or their authorized third-party service providers must register and undergo system testing with CBSAβs <strong>Technical Commercial Client Unit (TCCU)</strong>.<ref>CBSA Customs Notice 22-17 β Mandatory electronic notification of cargo at sufferance warehouses (RNS/EDI/TCCU testing). https://www.cbsa-asfc.gc.ca/publications/cn-ad/cn22-17-eng.html</ref></p> | |||
</div> | |||
<h2 style="margin-top: 40px; border-bottom: 2px solid #eee; padding-bottom: 10px;">When to Send WACM</h2> | |||
= | <div class="bc-card"> | ||
<p>CBSA guidance dictates specific rules based on consolidation:</p> | |||
<div class="bc-cleanlist"> | |||
* <strong>Consolidated Shipments:</strong> A WACM is required only on the <strong>primary (consolidated) CCN</strong> (including a consolidated electronic house bill CCN). CBSA will cascade arrival to lower-level electronic house bills destined to the same warehouse. | |||
* <strong>Non-Consolidated Shipments:</strong> A WACM is required on <strong>each non-consolidated CCN</strong>. | |||
* <strong>Carrier Code Agnostic:</strong> A WACM must be transmitted for cargo arriving at a sufferance warehouse <strong>regardless of the carrier code on the CCN</strong>.<ref>CBSA Customs Notice 22-17 β Mandatory electronic notification of cargo at sufferance warehouses (rules + examples). https://www.cbsa-asfc.gc.ca/publications/cn-ad/cn22-17-eng.html</ref> | |||
</div> | |||
</div> | |||
<h2 style="margin-top: 40px; border-bottom: 2px solid #eee; padding-bottom: 10px;">Getting Started (Registration)</h2> | |||
<div class="bc-card"> | |||
<div class="bc-float-video" style="margin-top: 0;"> | |||
Β <div class="bc-video-trigger" data-video-id="VgW2NUClVA8"> | |||
Β Β <div class="bc-play-icon"><i class="fas fa-play-circle"></i></div> | |||
Β </div> | |||
</div> | |||
<p>If you have not already done so, the easiest way to start transmitting WACM to CBSA using BorderConnect RNS is to contact BorderConnect Support. However, you can also initiate registration yourself:</p> | |||
<div class="bc-cleanlist"> | |||
1. Navigate to <strong>Account</strong> (top right) β <strong>Company Details</strong>. | |||
2. Locate your warehouse <strong>Sub-location Code</strong>. | |||
3. Click <strong>RNS Registration</strong> and print the document. (If your sub-location code isn't listed, use the <strong>New Sub Location</strong> button to add it). | |||
4. Have a person with signing authority sign the document and return it to BorderConnect (fax/email). | |||
5. BorderConnect submits the registration details required for TCCU onboarding. | |||
</div> | |||
</div> | |||
= | <h2 style="margin-top: 40px; border-bottom: 2px solid #eee; padding-bottom: 10px;">Sending a WACM to CBSA</h2> | ||
Once your warehouse is registered | <div class="bc-card"> | ||
<p>Once your warehouse is registered, you can begin sending arrival messages when unreleased shipments physically arrive.</p> | |||
[[File:Send-wacm-rns-arrival-menu.jpg|thumb|center|800px|Selecting Send RNS Arrival from the PARS Shipments menu]] | |||
<div class="bc-cleanlist"> | |||
1. Log in to BorderConnect. | |||
2. Go to <strong>PARS Shipments</strong>. | |||
3. Select <strong>Send New RNS Arrival</strong>. | |||
</div> | |||
[[File:Send-wacm-rns-arrival.png|800px]] | [[File:Send-wacm-rns-arrival.png|800px|thumb|center|Sending an RNS Arrival Request (WACM)]] | ||
Enter: | <p>Enter the following details:</p> | ||
* Cargo Control Number (CCN) | <div class="bc-cleanlist"> | ||
* Warehouse Sub-location Code | * <strong>Cargo Control Number (CCN):</strong> The unique identifier for the cargo. | ||
* Arrival Date and | * <strong>Warehouse Sub-location Code:</strong> The code of the facility where goods arrived. | ||
* <strong>Arrival Date and Time:</strong> The actual time of physical arrival. | |||
</div> | |||
Click | <p>Click <strong>Send Arrival Request to CBSA</strong>. Response timing can vary.</p> | ||
</div> | |||
= | <h2 style="margin-top: 40px; border-bottom: 2px solid #eee; padding-bottom: 10px;">Understanding Responses</h2> | ||
BorderConnect displays CBSA | <div class="bc-card"> | ||
<p>BorderConnect displays CBSA responses to help you identify next steps. <em>Note: This table is operational guidance, not an official CBSA meaning table.</em></p> | |||
<table class="wikitable" style="width: 100%;"> | |||
<tr> | |||
<th style="width: 25%;">Response</th> | |||
<th>Meaning (Typical)</th> | |||
<th>Action To Be Taken</th> | |||
</tr> | |||
<tr> | |||
<td style="background: #dff0d8;"><strong>RELEASED</strong></td> | |||
<td>Arrival accepted; transaction is released.</td> | |||
<td>No further action. Follow internal release controls.</td> | |||
</tr> | |||
<tr> | |||
<td style="background: #dff0d8;"><strong>ARRIVED*</strong></td> | |||
<td>Arrival accepted; release not yet on file.</td> | |||
<td>No further action for arrival. Monitor for release.</td> | |||
</tr> | |||
<tr> | |||
<td style="background: #fcf8e3;"><strong>HELD FOR EXAM</strong></td> | |||
<td>Shipment referred for examination.</td> | |||
<td>Follow CBSA instructions and local exam process.</td> | |||
</tr> | |||
<tr> | |||
<td style="background: #dff0d8;"><strong>ERROR (Already Released)</strong></td> | |||
<td>Rejected because CCN is already in a terminal state.</td> | |||
<td>Typically no action; validate status in records.</td> | |||
</tr> | |||
<tr> | |||
<td style="background: #f2dede;"><strong>ERROR (Office Mismatch)</strong></td> | |||
<td>Arrival office does not match release office on trade doc.</td> | |||
<td>Validate your sub-location. If correct, contact filing party to correct destination.</td> | |||
</tr> | |||
<tr> | |||
<td style="background: #fcf8e3;"><strong>ERROR (Conveyance Not Arrived)</strong></td> | |||
<td>Linked conveyance/cargo is not "Arrived" in CBSA system.</td> | |||
<td>Do not send WACM before physical arrival. Coordinate with carrier to update arrival reporting.<ref>CBSA β FAQ: Release Time Frames (arrival processing model; release eligibility after arrived status). https://www.cbsa-asfc.gc.ca/import/rtf-dm-eng.html</ref></td> | |||
</tr> | |||
</table> | |||
</div> | |||
<h2 style="margin-top: 40px; border-bottom: 2px solid #eee; padding-bottom: 10px;">WACM Search & History</h2> | |||
<div class="bc-card"> | |||
[[File:Wacm-search-page.png|800px|thumb|center|Searching WACM history]] | |||
<p>Use the WACM search page to confirm whether CBSA accepted your arrival, check the latest status, or investigate error messages indicating mismatches.</p> | |||
</div> | |||
| | |||
| | |||
| | |||
''' | {{Promo | ||
| icon = π | |||
| text = '''Operating a Sufferance Warehouse?''' Easily report WACM arrivals and releases to CBSA with BorderConnect Warehouse Software. | |||
| link = https://www.borderconnect.com/warehouse-arrivals/index.htm | |||
| button = View Features | |||
}} | |||
<div class="bc-references"> | |||
<references/> | |||
</div> | |||
Β | |||
Β | |||
Β | |||
</div> | |||
< | |||
[[Category:PARS Software Guide]] | [[Category:PARS Software Guide]] | ||