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}} | ||
{{#ev:youtube|J6ny2lShlqU|960|center|Sending Warehouse Arrival Certification Messages (WACM).}} | {{#ev:youtube|J6ny2lShlqU|960|center|Sending Warehouse Arrival Certification Messages (WACM) in BorderConnect.}} | ||
[[File:Send-wacm-rns-arrival-menu.jpg|thumb|right|400px|Selecting '''Send RNS Arrival''' from the PARS Shipments menu]] | [[File:Send-wacm-rns-arrival-menu.jpg|thumb|right|400px|Selecting '''Send RNS Arrival''' from the PARS Shipments menu]] | ||
Warehouse Arrival Certification | 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. | ||
Warehouse | 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> | ||
== Regulatory background (CBSA) == | |||
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> | |||
If you have not already done so, the easiest way to start transmitting WACM to CBSA using BorderConnect RNS is to contact BorderConnect. Or if you haven't registered to use RNS with BorderConnect and you'd like to add this feature yourself | 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> | ||
== Who must transmit WACM (and how) == | |||
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> | |||
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> | |||
== When to send WACM (consolidated vs non-consolidated) == | |||
CBSA guidance: | |||
* 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. | |||
* If the shipment is '''not consolidated''', a WACM is required on '''each non-consolidated CCN'''. | |||
* 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) == | |||
{{#ev:youtube|VgW2NUClVA8|360|right|BorderConnect Virtual Workshop - RNS-PARS Software & RNS Arrivals (WACM)}} | |||
If you have not already done so, the easiest way to start transmitting WACM to CBSA using BorderConnect RNS is to contact BorderConnect. | |||
Or, if you haven't registered to use RNS with BorderConnect and you'd like to add this feature yourself: | |||
# 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> | |||
== Sending a WACM to CBSA == | == Sending a WACM to CBSA == | ||
Once your warehouse is registered and enabled to transmit WACM via RNS/EDI, you can begin sending arrival messages. | |||
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> | |||
To send an arrival message | To send an arrival message in BorderConnect: | ||
# 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]] | |||
Enter: | |||
* 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). | |||
== WACM response messages (practical guidance) == | |||
BorderConnect displays CBSA acknowledgements / responses to help you identify next steps. | |||
'''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> | |||
The table below outlines common outcomes and suggested actions: | |||
{| class="wikitable" | {| class="wikitable" | ||
|- | |- | ||
! WACM Response | ! WACM Response | ||
! Meaning | ! Meaning (typical) | ||
! Action To Be Taken | ! Action To Be Taken | ||
|- | |- | ||
| style="background: #bcf5bc;"| '''RELEASED''' | | style="background: #bcf5bc;"| '''RELEASED''' | ||
| | | Arrival accepted and the related release transaction is in released status. | ||
| No further action | | No further action required. Follow your internal release/exit controls. | ||
|- | |- | ||
| style="background: #bcf5bc;"| '''ARRIVED*''' | | style="background: #bcf5bc;"| '''ARRIVED*''' | ||
| | | Arrival accepted, but release request/entry may not yet be on file or in good standing. | ||
| No further action | | 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''' | | 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: # | | 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''' | | 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> | |||
{| class="wikitable" | {| class="wikitable" | ||
|- | |- | ||
| style="background: #bcf5bc;"| '''No Further Action Required''' | | style="background: #bcf5bc;"| '''No Further Action Required''' | ||
| style="background: #e6e600;"| '''Minor Action Required''' | | style="background: #e6e600;"| '''Minor Action Required''' | ||
| style="background: #ff8080;"| '''Action Needs To Be Taken''' | | style="background: #ff8080;"| '''Action Needs To Be Taken''' | ||
| Line 97: | Line 117: | ||
[[File:Wacm-search-page.png|800px]] | [[File:Wacm-search-page.png|800px]] | ||
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 == | == References == | ||
Latest revision as of 16:47, 21 January 2026
|
🔖 This article is part of the BorderConnect PARS Software Guide |

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.
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]
Regulatory background (CBSA)
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 (May 6, 2015). [3]
Who must transmit WACM (and how)
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]
CBSA also notes that WACM (and other EDI functions) are part of the commercial reporting framework for warehouse operators. [5]
When to send WACM (consolidated vs non-consolidated)
CBSA guidance:
- 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.
- If the shipment is not consolidated, a WACM is required on each non-consolidated CCN.
- A WACM must be transmitted for cargo arriving at a sufferance warehouse regardless of the carrier code on the CCN. [6]
Getting Started (BorderConnect)
If you have not already done so, the easiest way to start transmitting WACM to CBSA using BorderConnect RNS is to contact BorderConnect.
Or, if you haven't registered to use RNS with BorderConnect and you'd like to add this feature yourself:
- 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. [7]
Sending a WACM to CBSA
Once your warehouse is registered and enabled to transmit WACM via RNS/EDI, you can begin sending arrival messages.
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. [8]
To send an arrival message in BorderConnect:
- Log in to BorderConnect
- Go to PARS Shipments
- Select Send New RNS Arrival
This opens the Send RNS Arrival Request for Canadian Shipment page.
Enter:
- 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).
WACM response messages (practical guidance)
BorderConnect displays CBSA acknowledgements / responses to help you identify next steps.
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.” [9]
The table below outlines common outcomes and suggested actions:
| WACM Response | Meaning (typical) | Action To Be Taken |
|---|---|---|
| RELEASED | Arrival accepted and the related release transaction is in released status. | No further action required. Follow your internal release/exit controls. |
| 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. |
| HELD FOR EXAM / Examination Required | Shipment is referred for examination. | Follow CBSA instructions and local examination process for your warehouse/port. |
| 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. |
| 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. |
| 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. [10]
| No Further Action Required | Minor Action Required | Action Needs To Be Taken |
Warehouse Arrival Search Page
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
- ↑ 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
- ↑ 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
- ↑ 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
- ↑ 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
- ↑ CBSA – Commercial reporting requirements (Warehouse operators / regulatory requirements). https://www.cbsa-asfc.gc.ca/prog/aci-manif-ipec/req-exig-eng.html
- ↑ 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
- ↑ CBSA Customs Notice 22-17 – TCCU registration/testing. https://www.cbsa-asfc.gc.ca/publications/cn-ad/cn22-17-eng.html
- ↑ CBSA Customs Notice 22-17 – WACM obligation + consolidation rules. https://www.cbsa-asfc.gc.ca/publications/cn-ad/cn22-17-eng.html
- ↑ 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
- ↑ CBSA – FAQ: Release Time Frames (arrival processing model; release eligibility after arrived status). https://www.cbsa-asfc.gc.ca/import/rtf-dm-eng.html