Referencing Another Carriers ACI Shipment (ACI eManifest): Difference between revisions
No edit summary Tag: Reverted |
m Admin moved page Preparing Partial ACI eManifests in Two Carrier Scenarios (ACI eManifest) to Referencing Another Carriers ACI Shipment (ACI eManifest) without leaving a redirect Β |
||
| (4 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
{{note|This article is part of the [[ACI_eManifest_Software_User_Guide_(CBSA)|BorderConnect ACI eManifest Guide]]|info}} | {{note|This article is part of the [[ACI_eManifest_Software_User_Guide_(CBSA)|BorderConnect ACI eManifest Guide]]|info}} | ||
<div class="bc-wrap"> | |||
<div class="bc-article-hero"> | |||
<h1>Preparing ACI eManifests (Two-Carrier Scenarios)</h1> | |||
<p>A guide to handling "Referenced Shipments" when one carrier contracts another to transport goods into Canada.</p> | |||
<div class="bc-article-meta"> | |||
<span class="bc-article-pill"><i class="fas fa-handshake"></i> Type: Tutorial</span> | |||
<span class="bc-article-pill"><i class="far fa-clock"></i> Time: 15 Minutes</span> | |||
</div> | |||
</div> | |||
<div class="bc-card"> | |||
<div class="bc-float-video"> | |||
Β <div class="bc-video-trigger" data-video-id="TdyeyrvPf1s"> | |||
Β Β <div class="bc-play-icon"><i class="fas fa-play-circle"></i></div> | |||
Β </div> | |||
</div> | |||
<h2 style="margin-top: 0;">Overview</h2> | |||
<p>In ACI eManifest, a <strong>Referenced Shipment</strong> occurs when a primary carrier hires a secondary carrier to physically transport goods into Canada.</p> | |||
* | <p>This process requires two separate filings that link together in CBSA's system:</p> | ||
* | <div class="bc-cleanlist"> | ||
* <strong>Primary Carrier:</strong> Owns the shipment and submits the <strong>Cargo Data</strong>. | |||
* <strong>Secondary Carrier:</strong> Transports the goods and submits the <strong>Conveyance (Trip) Data</strong>. | |||
</div> | |||
<div class="bc-did-you-know" style="margin-top: 15px;"> | |||
<strong>Authorization:</strong> No formal authorization letter is required for this specific linkage; the electronic link between the Trip Number and Cargo Control Number (CCN) serves as the authorization. | |||
</div> | |||
<div style="clear: both;"></div> | |||
</div> | |||
== | <div class="bc-card" style="margin-top: 30px;"> | ||
<h3>π€ Roles & Responsibilities</h3> | |||
<table class="wikitable" style="width:100%; margin-bottom:0;"> | |||
<tr> | |||
<th style="width: 30%;">Role</th> | |||
<th>Responsible For</th> | |||
<th>Carrier Code Used</th> | |||
</tr> | |||
<tr> | |||
<td><strong>Primary Carrier</strong></td> | |||
<td>Shipment (Cargo) Information</td> | |||
<td>Used in the <strong>Cargo Control Number (CCN)</strong></td> | |||
</tr> | |||
<tr> | |||
<td><strong>Secondary Carrier</strong></td> | |||
<td>Trip (Conveyance) Information</td> | |||
<td>Used in the <strong>Trip Number</strong></td> | |||
</tr> | |||
</table> | |||
</div> | |||
<h2 style="margin-top: 40px; border-bottom: 2px solid #eee; padding-bottom: 10px;">Role 1: The Primary Carrier</h2> | |||
<p>The Primary Carrier must submit the shipment data <strong>without</strong> attaching it to a trip.</p> | |||
<div class="bc-card"> | |||
<h3><span class="bc-step-circle">1</span> Create Unassociated Shipment</h3> | |||
<div class="bc-cleanlist"> | |||
* Navigate to <strong>ACI eManifests</strong> → <strong>Start New ACI Shipment</strong>. | |||
* <strong>Crucial:</strong> Leave "Attached to Trip Number" <strong>BLANK</strong>. | |||
* Enter the <strong>Port of Entry</strong> where the Secondary Carrier will cross. | |||
* Complete all Shipper, Consignee, and Commodity details normally. | |||
* Click <strong>Save</strong>. | |||
</div> | |||
[[File:Acishipmentunattached1.png|thumb|center|800px|Leaving Trip Number Blank]] | |||
</div> | |||
<div class="bc-card" style="margin-top: 20px;"> | |||
<h3><span class="bc-step-circle">2</span> Transmit to CBSA</h3> | |||
<div class="bc-cleanlist"> | |||
* Inside the shipment, locate the <strong>Send to CBSA</strong> menu. | |||
* Select <strong>Send New Shipment Request</strong>. | |||
* Wait for the status to change to <strong>On File with CBSA</strong>. | |||
</div> | |||
[[File:SendNewShipmentRequest.jpg|thumb|center|Sending the Shipment]] | |||
</div> | |||
== | <div class="bc-warning" style="margin-top: 20px;"> | ||
<strong>Next Step:</strong> You must provide the <strong>Secondary Carrier</strong> with the <strong>Cargo Control Number (CCN)</strong> and the <strong>Port of Entry</strong> you used. | |||
</div> | |||
The Primary Carrier | <h2 style="margin-top: 40px; border-bottom: 2px solid #eee; padding-bottom: 10px;">Role 2: The Secondary Carrier</h2> | ||
<p>The Secondary Carrier creates the trip and links to the Primary Carrier's existing shipment.</p> | |||
<div class="bc-card"> | |||
* | <h3><span class="bc-step-circle">1</span> One-Time Setup</h3> | ||
* | <p>Before starting, ensure your account is configured to allow this.</p> | ||
* | <div class="bc-cleanlist"> | ||
* Go to <strong>Account → Company Settings</strong>. | |||
* Under <strong>ACI eManifest Settings</strong>, set <strong>Allow ACI "Reference Only" Shipments</strong> to <strong>Yes</strong>. | |||
* Go to <strong>Account → Canadian Carrier Codes</strong> and add the Primary Carrier's code (so the system recognizes it). | |||
</div> | |||
</div> | |||
<div class="bc-card" style="margin-top: 20px;"> | |||
<h3><span class="bc-step-circle">2</span> Create the Trip</h3> | |||
<div class="bc-cleanlist"> | |||
* Navigate to <strong>ACI eManifests</strong> → <strong>Start New ACI eManifest</strong>. | |||
* Enter your Trip Number, Driver, Truck, and Trailer. | |||
* <strong>Crucial:</strong> Ensure the <strong>Port of Entry</strong> matches the Primary Carrier's shipment exactly. | |||
* Click <strong>Save</strong>. | |||
</div> | |||
[[File:Acidetailsdiff1.png|thumb|center|Trip Details]] | |||
</div> | |||
== | <div class="bc-card" style="margin-top: 20px;"> | ||
<h3><span class="bc-step-circle">3</span> Link the Shipment</h3> | |||
<div class="bc-cleanlist"> | |||
* Click <strong>Create New Shipment</strong>. | |||
* Check the box: β <strong>Shipment Reference Only</strong>. | |||
* Enter the <strong>Cargo Control Number (CCN)</strong> provided by the Primary Carrier. | |||
* Click <strong>Save</strong>. | |||
</div> | |||
[[File:Acishipmentattached1.png|thumb|center|Linking Referenced Shipment]] | |||
</div> | |||
<div class="bc-card" style="margin-top: 20px;"> | |||
<h3><span class="bc-step-circle">4</span> Transmit</h3> | |||
<div class="bc-cleanlist"> | |||
* Click <strong>Sync with CBSA</strong> on the manifest page. | |||
* Once accepted, the status will update to <strong>On File with CBSA</strong>. | |||
</div> | |||
[[File:Acishipmentaccepted1.png|thumb|center|Accepted Status]] | |||
</div> | |||
<h2 style="margin-top: 40px; border-bottom: 2px solid #eee; padding-bottom: 10px;">Verifying Release (PARS)</h2> | |||
<div class="bc-card"> | |||
<h3>Using Status Queries</h3> | |||
<p>Because the shipment uses another carrier's code, transaction numbers (PARS updates) will not auto-populate on your board. You must request them manually.</p> | |||
<div class="bc-cleanlist"> | |||
* Open the <strong>Shipment Details Page</strong>. | |||
* Click <strong>Send Status Query</strong>. | |||
* CBSA will return the current status (e.g., Transaction Number) if available. | |||
</div> | |||
<div class="bc-subtle" style="margin-top: 15px;"> | |||
See: [[Status_Query_Feature_(CBSA_Shipments)|Status Query Guide]] | |||
</div> | |||
</div> | |||
== | <div class="bc-card" style="margin-top: 30px;"> | ||
<h3>β Common Rejects</h3> | |||
<table class="wikitable" style="width:100%; margin-bottom:0;"> | |||
<tr> | |||
<th>Reject Message</th> | |||
<th>Meaning / Fix</th> | |||
</tr> | |||
<tr> | |||
<td><strong>Invalid Status of Related Request</strong></td> | |||
<td>The Shipment is not on file yet. Confirm the Primary Carrier has accepted their shipment first.</td> | |||
</tr> | |||
<tr> | |||
<td><strong>CCN Cannot Be Related to 2 Conveyances</strong></td> | |||
<td>The shipment is already linked to another trip. Ask the Primary Carrier to "De-link" it from any previous trips.</td> | |||
</tr> | |||
<tr> | |||
<td><strong>Port Code Must Match</strong></td> | |||
<td>The Trip Port differs from the Shipment Port. Correct your trip port or ask the Primary Carrier to update the shipment port.</td> | |||
</tr> | |||
</table> | |||
</div> | |||
{{AppPromo}} | |||
</div> [[Category:ACI eManifest Guide]] | |||
Β | |||
Β | |||
Β | |||
Β | |||
Β | |||
Β | |||
Β | |||
Β | |||
Β | |||
Β | |||
Β | |||
Β | |||
Β | |||
Β | |||
Β | |||
Β | |||
Β | |||
Β | |||
Β | |||
Β | |||
Β | |||
Β | |||
Β | |||
Β | |||
Β | |||
Β | |||
Β | |||
Β | |||
Β | |||
Β | |||
Β | |||
Β | |||
Β | |||
Β | |||
Β | |||
Β | |||
Β | |||
Β | |||
Β | |||
Β | |||
Β | |||
Β | |||
Β | |||
Β | |||
[[Category:ACI eManifest Guide]] | |||
Latest revision as of 15:05, 9 March 2026
|
π This article is part of the BorderConnect ACI eManifest Guide |
Preparing ACI eManifests (Two-Carrier Scenarios)
A guide to handling "Referenced Shipments" when one carrier contracts another to transport goods into Canada.
Overview
In ACI eManifest, a Referenced Shipment occurs when a primary carrier hires a secondary carrier to physically transport goods into Canada.
This process requires two separate filings that link together in CBSA's system:
- Primary Carrier: Owns the shipment and submits the Cargo Data.
- Secondary Carrier: Transports the goods and submits the Conveyance (Trip) Data.
Authorization: No formal authorization letter is required for this specific linkage; the electronic link between the Trip Number and Cargo Control Number (CCN) serves as the authorization.
π€ Roles & Responsibilities
| Role | Responsible For | Carrier Code Used |
|---|---|---|
| Primary Carrier | Shipment (Cargo) Information | Used in the Cargo Control Number (CCN) |
| Secondary Carrier | Trip (Conveyance) Information | Used in the Trip Number |
Role 1: The Primary Carrier
The Primary Carrier must submit the shipment data without attaching it to a trip.
1 Create Unassociated Shipment
- Navigate to ACI eManifests → Start New ACI Shipment.
- Crucial: Leave "Attached to Trip Number" BLANK.
- Enter the Port of Entry where the Secondary Carrier will cross.
- Complete all Shipper, Consignee, and Commodity details normally.
- Click Save.

2 Transmit to CBSA
- Inside the shipment, locate the Send to CBSA menu.
- Select Send New Shipment Request.
- Wait for the status to change to On File with CBSA.

Next Step: You must provide the Secondary Carrier with the Cargo Control Number (CCN) and the Port of Entry you used.
Role 2: The Secondary Carrier
The Secondary Carrier creates the trip and links to the Primary Carrier's existing shipment.
1 One-Time Setup
Before starting, ensure your account is configured to allow this.
- Go to Account → Company Settings.
- Under ACI eManifest Settings, set Allow ACI "Reference Only" Shipments to Yes.
- Go to Account → Canadian Carrier Codes and add the Primary Carrier's code (so the system recognizes it).
2 Create the Trip
- Navigate to ACI eManifests → Start New ACI eManifest.
- Enter your Trip Number, Driver, Truck, and Trailer.
- Crucial: Ensure the Port of Entry matches the Primary Carrier's shipment exactly.
- Click Save.

3 Link the Shipment
- Click Create New Shipment.
- Check the box: β Shipment Reference Only.
- Enter the Cargo Control Number (CCN) provided by the Primary Carrier.
- Click Save.

4 Transmit
- Click Sync with CBSA on the manifest page.
- Once accepted, the status will update to On File with CBSA.

Verifying Release (PARS)
Using Status Queries
Because the shipment uses another carrier's code, transaction numbers (PARS updates) will not auto-populate on your board. You must request them manually.
- Open the Shipment Details Page.
- Click Send Status Query.
- CBSA will return the current status (e.g., Transaction Number) if available.
See: Status Query Guide
β Common Rejects
| Reject Message | Meaning / Fix |
|---|---|
| Invalid Status of Related Request | The Shipment is not on file yet. Confirm the Primary Carrier has accepted their shipment first. |
| CCN Cannot Be Related to 2 Conveyances | The shipment is already linked to another trip. Ask the Primary Carrier to "De-link" it from any previous trips. |
| Port Code Must Match | The Trip Port differs from the Shipment Port. Correct your trip port or ask the Primary Carrier to update the shipment port. |