Jump to content
🚛
Streamline your cross-border operation. From ACE & ACI eManifests to PARS tracking and U.S. In-Bond filing, BorderConnect is the fastest way to cross.
Start Free Trial

Warehouse Arrival Certification Message (WACM) Guide (CBSA): Difference between revisions

From BorderConnect Wiki
← Older edit
No edit summary
No edit summary
 
(3 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}}


{{#ev:youtube|J6ny2lShlqU|960|center|Sending Warehouse Arrival Certification Messages (WACM) in BorderConnect.}}
<div class="bc-wrap">


[[File:Send-wacm-rns-arrival-menu.jpg|thumb|right|400px|Selecting '''Send RNS Arrival''' from the PARS Shipments menu]]
<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>


This guide provides instructions for using BorderConnect to transmit '''Warehouse Arrival Certification Messages (WACM)''' through the CBSA '''Release Notification System (RNS)'''. This guide assumes you have an active subscription and your RNS/WACM onboarding is complete.
<div class="bc-card">


A '''Warehouse Arrival Certification Message (WACM)''' is an electronic arrival message sent by a sufferance warehouse operator to CBSA when '''unreleased cargo physically arrives''' 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>
<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>


== Regulatory background (CBSA) ==
<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>


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


CBSA introduced the mandatory electronic arrival requirement via regulatory amendments (May 6, 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>
<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>


== Who must transmit WACM (and how) ==
<div style="clear: both;"></div>
</div>


A WACM must be transmitted by registered participants in CBSA’s '''Release Notification System (RNS)''' using '''Electronic Data Interchange (EDI)'''. Clients and/or their authorized third-party service providers must register and undergo system testing with CBSA’s '''Technical Commercial Client Unit (TCCU)'''. <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>
<h2 style="margin-top: 40px; border-bottom: 2px solid #eee; padding-bottom: 10px;">Regulatory Background</h2>


CBSA also notes that WACM (and other EDI functions) are part of the commercial reporting framework for warehouse operators. <ref>CBSA – Commercial reporting requirements (Warehouse operators / regulatory requirements). https://www.cbsa-asfc.gc.ca/prog/aci-manif-ipec/req-exig-eng.html</ref>
<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>


== When to send WACM (consolidated vs non-consolidated) ==
<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>


CBSA guidance:
<h3>Who Must Transmit?</h3>
* If the shipment is '''consolidated''', only a WACM on the '''primary (consolidated) CCN''' is required (including a consolidated electronic house bill CCN). CBSA will cascade arrival to lower-level electronic house bills destined to the same warehouse. 
<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>
* If the shipment is '''not consolidated''', a WACM is required on '''each non-consolidated CCN'''. 
</div>
* A WACM must be transmitted for cargo arriving at a sufferance warehouse '''regardless of the carrier code on the CCN'''. <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>


== Getting Started (BorderConnect) ==
<h2 style="margin-top: 40px; border-bottom: 2px solid #eee; padding-bottom: 10px;">When to Send WACM</h2>


{{#ev:youtube|VgW2NUClVA8|360|right|BorderConnect Virtual Workshop - RNS-PARS Software & RNS Arrivals (WACM)}}
<div class="bc-card">
<p>CBSA guidance dictates specific rules based on consolidation:</p>


If you have not already done so, the easiest way to start transmitting WACM to CBSA using BorderConnect RNS is to contact BorderConnect.
<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>


Or, if you haven't registered to use RNS with BorderConnect and you'd like to add this feature yourself:
<h2 style="margin-top: 40px; border-bottom: 2px solid #eee; padding-bottom: 10px;">Getting Started (Registration)</h2>
# Navigate to '''Account''' (top right) → '''Company Details'''.
# Locate your warehouse '''Sub-location Code'''.
# Click '''RNS Registration''' and print the document.
# If your sub-location code isn't listed, use the '''New Sub Location''' button to add it, or contact BorderConnect for assistance.
# A person with signing authority must print and sign the document and send it back to BorderConnect (fax or email).
# BorderConnect submits the registration details required for onboarding.


'''Note:''' CBSA onboarding timelines can vary because participation requires registration and, in many cases, testing with the TCCU. <ref>CBSA Customs Notice 22-17 – TCCU registration/testing. https://www.cbsa-asfc.gc.ca/publications/cn-ad/cn22-17-eng.html</ref>
<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>


== Sending a WACM to CBSA ==
<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>


Once your warehouse is registered and enabled to transmit WACM via RNS/EDI, you can begin sending arrival messages.
<h2 style="margin-top: 40px; border-bottom: 2px solid #eee; padding-bottom: 10px;">Sending a WACM to CBSA</h2>


When unreleased shipments physically arrive at your warehouse, you must transmit a WACM for the applicable Cargo Control Number(s) according to CBSA consolidation rules. <ref>CBSA Customs Notice 22-17 – WACM obligation + consolidation rules. https://www.cbsa-asfc.gc.ca/publications/cn-ad/cn22-17-eng.html</ref>
<div class="bc-card">
<p>Once your warehouse is registered, you can begin sending arrival messages when unreleased shipments physically arrive.</p>


To send an arrival message in BorderConnect:
[[File:Send-wacm-rns-arrival-menu.jpg|thumb|center|800px|Selecting Send RNS Arrival from the PARS Shipments menu]]
# Log in to BorderConnect
# Go to '''PARS Shipments'''
# Select '''Send New RNS Arrival'''
This opens the '''Send RNS Arrival Request for Canadian Shipment''' page.


[[File:Send-wacm-rns-arrival.png|800px]]
<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>


Enter:
[[File:Send-wacm-rns-arrival.png|800px|thumb|center|Sending an RNS Arrival Request (WACM)]]
* Cargo Control Number (CCN)
* Warehouse Sub-location Code
* Arrival Date and Arrival Time


Click '''Send Arrival Request to CBSA'''. Response timing can vary (especially during outages or peak periods).
<p>Enter the following details:</p>
<div class="bc-cleanlist">
* <strong>Cargo Control Number (CCN):</strong> The unique identifier for the cargo.
* <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>


== WACM response messages (practical guidance) ==
<p>Click <strong>Send Arrival Request to CBSA</strong>. Response timing can vary.</p>
</div>


BorderConnect displays CBSA acknowledgements / responses to help you identify next steps.
<h2 style="margin-top: 40px; border-bottom: 2px solid #eee; padding-bottom: 10px;">Understanding Responses</h2>


'''Important:''' CBSA maintains official EDI response/error code references separately. Message text can vary by workflow and system changes; treat the table below as common operational guidance rather than an official CBSA “meaning table.” <ref>CBSA EDI/Portal Clients – Frequently Asked Questions (references official error code resources and TCCU support). https://www.cbsa-asfc.gc.ca/eservices/faq-eng.html</ref>
<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>


The table below outlines common outcomes and suggested actions:
<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>


{| class="wikitable"
<h2 style="margin-top: 40px; border-bottom: 2px solid #eee; padding-bottom: 10px;">WACM Search & History</h2>
|-
! WACM Response
! Meaning (typical)
! Action To Be Taken
|-
| style="background: #bcf5bc;"| '''RELEASED'''
| Arrival accepted and the related release transaction is in released status.
| No further action required. Follow your internal release/exit controls.
|-
| style="background: #bcf5bc;"| '''ARRIVED*'''
| Arrival accepted, but release request/entry may not yet be on file or in good standing.
| No further action required for arrival reporting; monitor for release/held notices.
|-
| style="background: #e6e600;"| '''HELD FOR EXAM''' / Examination Required
| Shipment is referred for examination.
| Follow CBSA instructions and local examination process for your warehouse/port.
|-
| style="background: #bcf5bc;"| '''ERROR''' / already released / acquitted
| WACM rejected because the CCN is already in a terminal state (already arrived/released/acquitted).
| Typically no further action required; validate status in your records.
|-
| style="background: #ff8080;"| '''ERROR''' arrival office does not match release office
| Port/work location mismatch between the arrival being reported and the related trade document.
| Validate the sub-location/port used. If correct, contact the filing party to correct the destination/port on the trade document.
|-
| style="background: #e6e600;"| '''ERROR''' related conveyance must be arrived...
| The linked conveyance/cargo is not yet in arrived status in CBSA systems.
| Do not send WACM before physical arrival. If the goods are physically present, the carrier may need to update arrival reporting; coordinate with the carrier.
|}


'''Why “arrived status” matters:''' CBSA implemented an arrival processing approach where shipments are eligible for release only after related cargo documents attain “arrived” status, which is why some WACMs are rejected if the related conveyance/cargo has not arrived in CBSA systems. <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>
<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>


{| class="wikitable"
{{Promo
|-
| icon = 🏭
| style="background: #bcf5bc;"| '''No Further Action Required'''
| text = '''Operating a Sufferance Warehouse?''' Easily report WACM arrivals and releases to CBSA with BorderConnect Warehouse Software.
| style="background: #e6e600;"| '''Minor Action Required'''
| link = https://www.borderconnect.com/warehouse-arrivals/index.htm
| style="background: #ff8080;"| '''Action Needs To Be Taken'''
| button = View Features
|-
}}
|}


== Warehouse Arrival Search Page ==
<div class="bc-references">
 
<references/>
[[File:Wacm-search-page.png|800px]]
</div>
 
Use the WACM search/history page to confirm:
* Whether CBSA accepted your arrival
* The latest status/result
* Any error messaging that indicates a mismatch (port/sublocation/conveyance arrival)


== References ==
</div>
<references/>


[[Category:PARS Software Guide]]
[[Category:PARS Software Guide]]

Latest revision as of 12:55, 11 February 2026

🔖 This article is part of the BorderConnect PARS Software Guide

Sending Warehouse Arrival Certification Messages (WACM)

Instructions for sufferance warehouse operators to report cargo arrivals to CBSA via RNS.

Type: Compliance Reporting System: CBSA RNS

Overview

This guide provides instructions for using BorderConnect to transmit Warehouse Arrival Certification Messages (WACM) through the CBSA Release Notification System (RNS).

A Warehouse Arrival Certification Message (WACM) is an electronic arrival message sent by a sufferance warehouse operator to CBSA when unreleased cargo physically arrives at the sufferance warehouse, and liability transfers from the carrier to the warehouse.[1]

Prerequisite: This guide assumes you have an active subscription and your RNS/WACM onboarding with CBSA is complete.

Regulatory Background

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).[2]

CBSA introduced the mandatory electronic arrival requirement via regulatory amendments in May 2015.[3]

Who Must Transmit?

A WACM must be transmitted by registered participants in CBSA’s Release Notification System (RNS) using Electronic Data Interchange (EDI). Clients and/or their authorized third-party service providers must register and undergo system testing with CBSA’s Technical Commercial Client Unit (TCCU).[4]

When to Send WACM

CBSA guidance dictates specific rules based on consolidation:

  • Consolidated Shipments: A WACM is required only on the primary (consolidated) CCN (including a consolidated electronic house bill CCN). CBSA will cascade arrival to lower-level electronic house bills destined to the same warehouse.
  • Non-Consolidated Shipments: A WACM is required on each non-consolidated CCN.
  • Carrier Code Agnostic: A WACM must be transmitted for cargo arriving at a sufferance warehouse regardless of the carrier code on the CCN.[5]

Getting Started (Registration)

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:

1. Navigate to Account (top right) → Company Details. 2. Locate your warehouse Sub-location Code. 3. Click RNS Registration and print the document. (If your sub-location code isn't listed, use the New Sub Location 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.

Sending a WACM to CBSA

Once your warehouse is registered, you can begin sending arrival messages when unreleased shipments physically arrive.

Selecting Send RNS Arrival from the PARS Shipments menu

1. Log in to BorderConnect. 2. Go to PARS Shipments. 3. Select Send New RNS Arrival.

Sending an RNS Arrival Request (WACM)

Enter the following details:

  • Cargo Control Number (CCN): The unique identifier for the cargo.
  • Warehouse Sub-location Code: The code of the facility where goods arrived.
  • Arrival Date and Time: The actual time of physical arrival.

Click Send Arrival Request to CBSA. Response timing can vary.

Understanding Responses

BorderConnect displays CBSA responses to help you identify next steps. Note: This table is operational guidance, not an official CBSA meaning table.

Response Meaning (Typical) Action To Be Taken
RELEASED Arrival accepted; transaction is released. No further action. Follow internal release controls.
ARRIVED* Arrival accepted; release not yet on file. No further action for arrival. Monitor for release.
HELD FOR EXAM Shipment referred for examination. Follow CBSA instructions and local exam process.
ERROR (Already Released) Rejected because CCN is already in a terminal state. Typically no action; validate status in records.
ERROR (Office Mismatch) Arrival office does not match release office on trade doc. Validate your sub-location. If correct, contact filing party to correct destination.
ERROR (Conveyance Not Arrived) Linked conveyance/cargo is not "Arrived" in CBSA system. Do not send WACM before physical arrival. Coordinate with carrier to update arrival reporting.[6]

WACM Search & History

Searching WACM history

Use the WACM search page to confirm whether CBSA accepted your arrival, check the latest status, or investigate error messages indicating mismatches.


🏭
Operating a Sufferance Warehouse? Easily report WACM arrivals and releases to CBSA with BorderConnect Warehouse Software.

View Features


  1. ↑ 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
  2. ↑ 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
  3. ↑ 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
  4. ↑ 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
  5. ↑ 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
  6. ↑ CBSA – FAQ: Release Time Frames (arrival processing model; release eligibility after arrived status). https://www.cbsa-asfc.gc.ca/import/rtf-dm-eng.html
Retrieved from "https://wiki.borderconnect.com/index.php?title=Warehouse_Arrival_Certification_Message_(WACM)_Guide_(CBSA)&oldid=3305"