Jump to content

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

From BorderConnect Wiki
No edit summary
No edit summary
 
(One intermediate revision by the same user not shown)
Line 3: Line 3:
{{#ev:youtube|J6ny2lShlqU|960|center|Sending Warehouse Arrival Certification Messages (WACM) in BorderConnect.}}
{{#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]]This guide offers instructions on using BorderConnect's '''Warehouse Arrival Certification Message (WACM)''' feature using the [https://www.borderconnect.com/pars-check/index.htm Release Notification System (RNS)]. This guide assumes that you have an active software subscription and that your RNS registration is complete. If you are not yet registered, please refer to the registration instructions below under 'Getting Started'.
[[File:Send-wacm-rns-arrival-menu.jpg|thumb|right|400px|Selecting '''Send RNS Arrival''' from the PARS Shipments menu]]


Warehouse Arrival Certification Message (WACM) is a notification that is sent by a Canadian Sufferance Warehouse when unreleased inland cargo arrives at their facility. WACM became mandatory on May 6, 2015, under an amendment to the Customs Sufferance Warehouse Regulations. This electronic requirement replaced the previous method of manual arrivals and the transfer of liability process at inland destinations.<ref>CBSA - Warehouse Arrival Certification Message (WACM) Questions and Answers https://www.cbsa-asfc.gc.ca/import/codes/wacm-eng.html</ref>
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 operators or owners who receive unreleased goods into their sufferance warehouses must transmit WACM. Warehouse operators must be registered participants in CBSA's Release Notification System (RNS) using an Electronic Data Interchange (EDI). Operators may also use a third-party service provider to transmit their arrival messages, such as BorderConnect.<ref>Customs Notice 17-28 https://www.cbsa-asfc.gc.ca/publications/cn-ad/cn17-28-eng.html</ref>
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>


On August 14, 2020, Canada Border Services Agency announced changes to address eManifest house bill issues with Customs Notice 20-28. These changes, starting November 1, 2020 include changes to all Warehouse Arrival Certification Messages (WACM). Starting on this date all Warehouse Arrival Certification Messages must include a warehouse sub-location code as part of their electronic submission to CBSA.<ref>Customs Notice 20-28 https://www.cbsa-asfc.gc.ca/publications/cn-ad/cn20-28-eng.html</ref>
== Regulatory background (CBSA) ==


== Getting Started ==
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, navigate to the 'Account' menu option on the top right and then click 'Company Details'. Where your warehouse sublocation code is listed, click 'RNS Registration' and print the document. If your sublocation code isn't listed, you can use the New Sub Location button to add it, or contact BorderConnect for assistance. A person with signing authority must then print and sign the document and send it back to BorderConnect by fax or email. We will then send to CBSA on your behalf and in approximately 1-2 weeks your RNS subscription will be active.
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 ==


'''Sending an Arrival Message to CBSA'''
Once your warehouse is registered and enabled to transmit WACM via RNS/EDI, you can begin sending arrival messages.


Once your Warehouse RNS application has been approved by CBSA, you can start sending Warehouse Arrival Certification Messages (WACM) using RNS. When unreleased shipments arrive at your warehouse, you will need to send an arrival message for each cargo control number corresponding to each of the shipments.
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, log in to BorderConnect and navigate to the menu option 'PARS Shipments' and select the option 'Send New RNS Arrival'. This will bring you to the 'Send RNS Arrival Request for Canadian Shipment' page.
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]]


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


Once on the 'Send RNS Arrival Request for Canadian Shipment' page, enter the Cargo Control Number, your Warehouse Sublocation Code, and the Arrival Date and Arrival Time, then send 'Send Arrival Request to CBSA' and in approximately 5-10 minutes CBSA will provide a response to your WACM on BorderConnect's RNS Arrival Search page.
== WACM response messages (practical guidance) ==


== WACM Response Messages ==
BorderConnect displays CBSA acknowledgements / responses to help you identify next steps.


The table below outlines the most common responses to an arrival message.
'''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'''
| The cargo control number has successfully arrived, and is now in released status.
| Arrival accepted and the related release transaction is in released status.
| No further action is required. The goods can now exit the warehouse and are no longer considered in-bond.
| No further action required. Follow your internal release/exit controls.
|-
|-
| style="background: #bcf5bc;"| '''ARRIVED*'''
| style="background: #bcf5bc;"| '''ARRIVED*'''
| CBSA has accepted your WACM but there is no entry on file by a customs broker yet.
| Arrival accepted, but release request/entry may not yet be on file or in good standing.
| No further action is required. The goods are not released yet, but you have met your arrival reporting requirement.
| No further action required for arrival reporting; monitor for release/held notices.
|-
| style="background: #e6e600;"| '''HELD FOR EXAM''' "Examination Required"
| Your WACM is successfully accepted, but an examination for the shipment is required.
| You should contact CBSA to schedule an examination. Please note it is also possible to receive a Held notice at a later date. Held notices are not restricted to WACM responses.
|-
| style="background: #bcf5bc;"| '''ERROR''' "Cannot arrive, goods already released and acquitted"
| The WACM was rejected, but the cargo control number is already released.
| No further action is required. The cargo control number has attained released status, which means it is already arrived. The goods can now exit the warehouse and are no longer considered in-bond.
|-
| style="background: #ff8080;"| '''ERROR''' "Arrival office does not match release office"
| The WACM was rejected because the port on the WACM doesn't match the port the customs broker used on their entry.
| First verify that your WACM used the correct sublocation code for the warehouse you are trying to arrive the goods at. If this was incorrect, send a new arrival message for the cargo control number with the correct sublocation code. If your WACM was correct, contact the customs broker who filed the entry and ask them to revise the port they are using.
|-
| style="background: #bcf5bc;"| '''ERROR''' "Request ID already in arrived status"
| The WACM was rejected, but the cargo control number is already in arrived status.
| No further action is required. The goods are not released yet, but you have met your arrival reporting requirement.
|-
|-
| 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''' "Arrival is already on file with matching Port and Warehouse"
| style="background: #bcf5bc;"| '''ERROR''' / already released / acquitted
| The WACM was rejected, but the cargo control number is already in arrived status with the corresponding port and warehouse.
| WACM rejected because the CCN is already in a terminal state (already arrived/released/acquitted).
| No further action is required. The arrival is already on file with the same port and warehouse.
| Typically no further action required; validate status in your records.
|-
|-
| style="background: #bcf5bc;"| '''ERROR''' "Cannot arrive CCN if acquitted"
| style="background: #ff8080;"| '''ERROR''' arrival office does not match release office
| The WACM was rejected, but the cargo control number is already released.
| Port/work location mismatch between the arrival being reported and the related trade document.
| No further action is required. The cargo control number has attained released status, which means it is already arrived. The goods can now exit the warehouse and are no longer considered in-bond.
| 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 and in good final decision status"
| style="background: #e6e600;"| '''ERROR''' related conveyance must be arrived...
| This shipment is currently linked to an ACI eManifest that is still in a pre-arrival state and not yet in Canada.
| The linked conveyance/cargo is not yet in arrived status in CBSA systems.
| Make sure you are not sending the WACM before the shipment physically arrives at your bonded warehouse. If you get this response when the goods are already there, you should contact the carrier. The carrier will need to update their eManifest to reflect their arrival in Canada. You can then resend the WACM.
| 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.
|-
| style="background: #e6e600;"| '''ERROR''' "Related conveyance must be authorized to move and arrive"
| Same as above
| Same as above
|-
| style="background: #ff8080;"| '''ERROR''' "Arrival work location code must be the same as the port of destination on House Bill"
| The WACM was rejected because the port on the WACM doesn't match the port the freight forwarder used on their House Bill.
| First verify that your WACM used the correct sublocation code for the warehouse you are trying to arrive the goods at. If this was incorrect, send a new arrival message for the cargo control number with the correct sublocation code. If your WACM was correct, contact the freight forwarder and ask them to revise the port they are using on the House Bill.
|}
|}
'''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

Sending Warehouse Arrival Certification Messages (WACM) in BorderConnect.
Selecting Send RNS Arrival from the PARS Shipments menu

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)

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:

  1. Navigate to Account (top right) → Company Details.
  2. Locate your warehouse Sub-location Code.
  3. Click RNS Registration and print the document.
  4. If your sub-location code isn't listed, use the New Sub Location button to add it, or contact BorderConnect for assistance.
  5. A person with signing authority must print and sign the document and send it back to BorderConnect (fax or email).
  6. 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:

  1. Log in to BorderConnect
  2. Go to PARS Shipments
  3. 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

  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 – Commercial reporting requirements (Warehouse operators / regulatory requirements). https://www.cbsa-asfc.gc.ca/prog/aci-manif-ipec/req-exig-eng.html
  6. 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
  7. CBSA Customs Notice 22-17 – TCCU registration/testing. https://www.cbsa-asfc.gc.ca/publications/cn-ad/cn22-17-eng.html
  8. CBSA Customs Notice 22-17 – WACM obligation + consolidation rules. https://www.cbsa-asfc.gc.ca/publications/cn-ad/cn22-17-eng.html
  9. 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
  10. CBSA – FAQ: Release Time Frames (arrival processing model; release eligibility after arrived status). https://www.cbsa-asfc.gc.ca/import/rtf-dm-eng.html