BorderConnect Onboarding and Readiness Guide: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
{{note|This article is part of the [[BorderConnect_Software_User_Guide|BorderConnect Software User Guide]] and the [[Customs_Compliance_Guide_(CBP_and_CBSA)|Customs Compliance Guide]]|info}} | |||
= Onboarding for BorderConnect: Be Ready to File ACI (Canada) and/or ACE (U.S.) = | |||
This guide prepares highway carriers and dispatch teams to complete the government registrations and setup steps required before using BorderConnect to create and transmit: | |||
* '''ACI eManifest''' (Canada – CBSA) | |||
* | * '''ACE Truck e-Manifest''' (United States – CBP) | ||
* | |||
The goal is to ensure your manifests can be submitted, accepted, and time-stamped early enough that drivers arrive at the border compliant and ready. | |||
__TOC__ | |||
CBSA ACI | == Crossing into Canada (CBSA ACI eManifest & CARM Client Portal) == | ||
CBSA’s highway ACI/eManifest guidance states that the Highway Cargo Document (and Combined Highway Document) may be submitted up to 30 days in advance, but must be received and validated at least '''one hour prior to arrival''' at the First Port of Arrival (FPOA).<ref>CBSA. "Advance Commercial Information (ACI)/eManifest Highway: Electronic Commerce Client Requirements Document (ECCRD) – Highway Mode." https://www.cbsa-asfc.gc.ca/prog/manif/eccrdhi-deccerout-eng.html</ref> | |||
CBSA’s eManifest Portal User Guide also states that trade documents must be received and validated at least one hour prior to arrival at the FPOA.<ref>CBSA. "eManifest Portal User Guide." https://www.cbsa-asfc.gc.ca/prog/manif/portal-portail/guide-eng.html</ref> | |||
=== Step 1: Obtain a CBSA Carrier Code === | |||
A CBSA carrier code is a four-character unique identifier required to transact business with CBSA (highway, marine, air, rail).<ref>CBSA. "Commercial carrier and freight forwarder identification and eligibility." https://www.cbsa-asfc.gc.ca/services/carrier-transporteur/menu-eng.html</ref> | |||
CBSA’s Highway Carrier Code Application guidance explains the process: | |||
# Create an account in the CARM Client Portal (CCP) | |||
# Complete the carrier code application in the CCP | |||
# After receiving the carrier code, apply to transmit ACI and complete any required testing<ref>CBSA. "CBSA Guidelines – Highway Carrier Code Application Process." https://www.cbsa-asfc.gc.ca/services/carrier-transporteur/hccap-ddctr-eng.html</ref> | |||
CBSA also notes that new carriers can request a carrier code when registering in the CARM Client Portal.<ref>CBSA. "Get started with CARM." https://www.cbsa-asfc.gc.ca/services/carm-gcra/start-passer-eng.html</ref> | |||
=== Step 2: Set up your CARM Client Portal access === | |||
The CARM Client Portal is CBSA’s official platform for business enrollment, user access, and program enrolment workflows.<ref>CARM Client Portal login. https://ccp-pcc.cbsa-asfc.cloud-nuage.canada.ca/</ref> | |||
CBSA provides onboarding documentation and user guides for portal processes.<ref>CBSA. "CARM Client Portal onboarding documentation." https://ccp-pcc.cbsa-asfc.cloud-nuage.canada.ca/en/onboarding-documentation</ref> | |||
Within the portal you must: | |||
# Create and link your business profile | |||
# Assign internal roles and permissions | |||
# Complete program enrolments required for carrier operations | |||
CBSA publishes a specific user guide for enrolling in the Carrier program.<ref>CBSA. "User Guide – Enrol in the Carrier program." https://ccp-pcc.cbsa-asfc.cloud-nuage.canada.ca/en/assets/pdfs/onboarding/en/User%20Guide%20-%20Enrol%20in%20the%20Carrier%20program.pdf</ref> | |||
=== Step 3: Delegation of Authority (brokers and service providers) === | |||
If a customs broker or third-party service provider will act on your behalf, CBSA requires Delegation of Authority to be managed inside the CARM Client Portal. | |||
CBSA guidance includes: | |||
* Delegation of Authority user guide (PDF)<ref>CBSA. "User Guide – Delegation of Authority in the CARM Client Portal." https://ccp-pcc.cbsa-asfc.cloud-nuage.canada.ca/en/assets/pdfs/onboarding/en/User%20Guide%20-%20Delegation%20of%20Authority%20in%20the%20CARM%20Client%20Portal.pdf</ref> | |||
* Official walkthrough for delegating authority to a third party service provider<ref>CBSA. "How to set up a delegation of authority for a third party service provider in the CARM Client Portal." https://www.cbsa-asfc.gc.ca/multimedia/carm-gcra/portal-portail-r1-4-eng.html</ref> | |||
=== Step 4: Meet the ACI highway timing requirement === | |||
CBSA requires highway cargo and conveyance data to be received and validated at least one hour prior to arrival at the FPOA.<ref>CBSA. "Advance Commercial Information (ACI)/eManifest Highway: ECCRD – Highway Mode." https://www.cbsa-asfc.gc.ca/prog/manif/eccrdhi-deccerout-eng.html</ref> | |||
CBSA Memorandum D3-4-2 explains that submissions with insufficient review time may trigger warnings and possible AMPS enforcement.<ref>CBSA. "Memorandum D3-4-2: Highway pre-arrival and reporting requirements." https://www.cbsa-asfc.gc.ca/publications/dm-md/d3/d3-4-2-eng.html</ref> | |||
=== Step 5: Broker coordination (PARS shipments) === | |||
Many Canadian imports require broker clearance prior to release. Confirm that: | |||
* Brokers have your correct CBSA carrier code | |||
* Shipment identifiers align between ACI filings and broker entries | |||
* Clearance timing supports arrival schedules | |||
=== Step 6: Driver and equipment requirements (Canada) === | |||
==== Driver requirements ==== | |||
Before a driver crosses commercially into Canada, ensure: | |||
* Valid passport or approved travel document | |||
* Shipment paperwork (BOL, invoice references, PARS numbers where applicable) | |||
* Internal trip or manifest reference | |||
Drivers should: | |||
* Know the port of entry | |||
* Arrive only after ACI acceptance and broker clearance are confirmed | |||
==== Equipment requirements ==== | |||
ACI eManifest requires accurate conveyance data including: | |||
* Tractor (power unit) number | |||
* Trailer number(s) | |||
* Mode of transport (highway) | |||
* Port of entry | |||
Best practices: | |||
* Use consistent numbering formats | |||
* Match physical equipment markings exactly | |||
* Update manifests if equipment changes | |||
--- | |||
== Crossing into the United States (CBP ACE Truck e-Manifest) == | |||
CBP requires carriers to submit the ACE Truck Manifest at least one hour prior to arrival into the United States.<ref>CBP. "ACE Truck Manifest User Guide (PDF)." https://www.cbp.gov/sites/default/files/documents/ACE%20Truck%20Manifest%20User%20Guide.pdf</ref> | |||
CBP maintains official guidance for the Truck e-Manifest program.<ref>CBP. "e-Manifest: Trucks User Guide." https://www.cbp.gov/document/guidance/e-manifest-trucks-user-guide</ref> | |||
=== Step 1: Understand the CBP one-hour prior submission rule === | |||
Carriers must submit and receive acceptance of the ACE Manifest no later than one hour prior to arrival at the U.S. border.<ref>CBP. "ACE Truck Manifest User Guide (PDF)." https://www.cbp.gov/sites/default/files/documents/ACE%20Truck%20Manifest%20User%20Guide.pdf</ref> | |||
=== Step 2: Prepare consistent trip and equipment data === | |||
Before using BorderConnect: | |||
* Standardize tractor numbers | |||
* Standardize trailer numbers | |||
* Define trip/manifest reference formats | |||
* Confirm shipment reference workflows with brokers | |||
=== Step 3: Broker coordination (entries / PAPS workflows) === | |||
Ensure broker entry data aligns with manifest submissions to avoid delays or rejection. | |||
=== Step 4: Driver and equipment requirements (United States) === | |||
==== Driver requirements ==== | |||
Before a driver crosses commercially into the United States, ensure: | |||
* Valid passport or approved travel document | |||
* Commercial driver’s license (CDL) as required | |||
* Shipment paperwork (BOL, invoice references, PAPS numbers) | |||
* Internal trip or manifest reference | |||
Drivers should: | |||
* Know their tractor and trailer numbers | |||
* Arrive only after ACE acceptance is confirmed | |||
==== Equipment requirements ==== | |||
ACE Manifests require accurate conveyance data including: | |||
* Tractor number | |||
* Trailer number(s) | |||
* Trip/manifest reference | |||
* Port of arrival | |||
Best practices: | |||
* Keep identifiers consistent | |||
* Match physical equipment markings | |||
* Update trips immediately if equipment changes | |||
--- | |||
== BorderConnect Go-Live Readiness Checklist == | |||
=== Canada === | |||
✔ CBSA carrier code issued<ref>CBSA. "CBSA Guidelines – Highway Carrier Code Application Process." https://www.cbsa-asfc.gc.ca/services/carrier-transporteur/hccap-ddctr-eng.html</ref> | |||
✔ CARM Client Portal enrolment complete<ref>CBSA. "User Guide – Enrol in the Carrier program." https://ccp-pcc.cbsa-asfc.cloud-nuage.canada.ca/en/assets/pdfs/onboarding/en/User%20Guide%20-%20Enrol%20in%20the%20Carrier%20program.pdf</ref> | |||
✔ Delegation of Authority handled where required<ref>CBSA. "User Guide – Delegation of Authority in the CARM Client Portal." https://ccp-pcc.cbsa-asfc.cloud-nuage.canada.ca/en/assets/pdfs/onboarding/en/User%20Guide%20-%20Delegation%20of%20Authority%20in%20the%20CARM%20Client%20Portal.pdf</ref> | |||
✔ Ability to meet ACI one-hour requirement<ref>CBSA. "Advance Commercial Information (ACI)/eManifest Highway: ECCRD – Highway Mode." https://www.cbsa-asfc.gc.ca/prog/manif/eccrdhi-deccerout-eng.html</ref> | |||
=== United States === | |||
✔ Ability to meet CBP one-hour ACE Manifest requirement<ref>CBP. "ACE Truck Manifest User Guide (PDF)." https://www.cbp.gov/sites/default/files/documents/ACE%20Truck%20Manifest%20User%20Guide.pdf</ref> | |||
✔ Trip/equipment data standards defined | |||
== Next Steps in BorderConnect == | |||
* [[Creating_and_Submitting_a_New_ACI_eManifest_(ACI_eManifest)|Create your first ACI eManifest]] | |||
* [[Creating_and_Submitting_a_New_ACE_Manifest_(ACE_Manifest)|Create your first ACE Manifest]] | |||
* [[EManifest_Processing_Guide_(ACE_and_ACI_eManifest)|eManifest Processing Guide]] | |||
== References == | |||
<references/> | |||