Correcting Rejected ACI eManifests (ACI eManifest): Difference between revisions
No edit summary |
No edit summary Β |
||
| Line 1: | Line 1: | ||
{{#seo: | |||
|title=How to Fix CBSA Rejected ACI eManifests {{!}} BorderConnect Support Wiki | |||
|title_mode=replace | |||
|keywords=CBSA returned error, ACI eManifest rejected, shipment linked to another trip, invalid status of request CBSA, shipment not on file, trip port does not match, fix CBSA reject codes, BorderConnect troubleshooting | |||
|description=Troubleshooting guide for fixing CBSA rejected ACI eManifests. Learn how to resolve common errors like "Shipment Linked to Another Trip", "Duplicate", and "Invalid Status of Request". | |||
}} | |||
{{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-wrap"> | ||
Latest revision as of 17:08, 24 February 2026
|
π This article is part of the BorderConnect ACI eManifest Guide |
Correcting Rejected ACI eManifests
A troubleshooting guide for resolving "CBSA Returned Error" statuses and getting your manifest accepted.
Overview
When CBSA rejects a Trip or Shipment, the Current Status updates to CBSA Returned Error, and a specific error message appears in the History/Status Messages section.
To fix the reject, you must locate the CBSA response message and follow the appropriate steps for that specific error.
Support Note: This guide covers common rejects. Complex scenarios involving multiple carriers or edge cases may require assistance. If unsure, contact BorderConnect Support at 800-596-5176.
Quick Fix Workflow
1 Identify the Error
- Open the Trip or Shipment showing CBSA Returned Error.
- Scroll to History/Status Messages.
- Locate the CBSA Response line.
- Note the Key Phrase (e.g., "Duplicate", "Shipment Not On File") and the Reference Number (e.g., CCN or Trip Number).
2 Apply the Fix
Find your error message in the sections below and apply the specific solution. Then, re-transmit:
- For Trip Rejects: Click Sync with CBSA on the eManifest Details page.
- For Shipment Rejects: Use Send New Shipment Request (if needed), then Sync with CBSA on the Trip.
π Common Rejects at a Glance
| Reject Message | Typical Meaning |
|---|---|
| Shipment Linked to Another Trip | The shipment is already attached to a different manifest. |
| Duplicate | The Trip Number or CCN has already been used. |
| Shipment Not On File | A shipment listed on the trip hasn't been accepted yet. |
| Invalid Status of Request | Trying to send a "New" request for something already on file. |
| Trip Port Does Not Match | Trip port differs from the shipment port. |
| Already Used | The number has been processed and cannot be reused. |
Detailed Solutions
β Reject: Shipment Linked to Another Trip
What it means: The Cargo Control Number (CCN) listed in the error is currently attached to a different trip in CBSA's system.
Example: Trip [12340009189] Rejected Cargo Control Number: Shipment Linked to Another Trip on 1234PARS008698
How to Fix:
- Step 1: Locate the original trip where this shipment was previously linked.
- Step 2: On that original trip, click Sync with CBSA to update it (this tells CBSA the shipment is no longer there).
- Step 3: Once the original trip update is accepted, return to your current (rejected) trip.
- Step 4: Click Sync with CBSA to successfully link the shipment.
If Original Trip is Arrived: If the old trip is already released, you cannot update it. You must assign a New CCN to the shipment on the new trip and re-send it as a new shipment.
β Reject: Duplicate / Number Already Used
What it means: CBSA detected a conflict. A Trip Number cannot be used as a CCN, and a CCN cannot be used as a Trip Number. Or, the number simply exists already.
Example: Trip [1234114000] Rejected Client Supplied Request Id: Duplicate on 1234114000
How to Fix:
- Step 1: Change the conflicting Trip Number or Cargo Control Number to a new, unique value.
- Step 2: Re-transmit.
* Trip Reject: Click Sync with CBSA. * Shipment Reject: Click Send New Shipment Request inside the shipment, then Sync the trip.
β Reject: Cannot Cancel, Shipment Is Linked to a Trip
What it means: You tried to cancel a shipment, but CBSA still sees it attached to a trip.
How to Fix:
- Scenario A (Cancelling Manifest): The Trip cancel likely worked, but the shipment didn't. Simply go to the Shipment Details page and click Send Cancel/Delete Shipment Request again.
- Scenario B (Removing Shipment): You must remove the shipment from the trip profile first, send the trip update, then cancel the shipment.
β Reject: Shipment Not On File
What it means: The Trip is trying to link to a shipment that CBSA doesn't have yet.
Example: Trip [123400104] Rejected Cargo Control Number: Shipment Not On File on 1234PARS108098
How to Fix:
- Step 1: Check the status of the shipment referenced in the error.
- Step 2: If it is Draft or Rejected, open the shipment and click Send New Shipment Request.
- Step 3: Once the shipment is accepted, return to the trip and click Sync with CBSA.
β Reject: Invalid Status of Request
What it means: You tried to send a request type (like "New" or "Cancel") that isn't allowed for the manifest's current state in CBSA's system.
Common Scenarios & Fixes:
| Scenario | Fix |
|---|---|
| Re-sending an accepted manifest | No action needed. CBSA already has it. If you made changes, use Sync with CBSA instead. |
| Updating a Cancelled item | CBSA won't update cancelled items. You must re-send it as New (Sync with CBSA). |
| First time sending | The number may exist in another system (Portal). Assign a new Trip/CCN and re-send. |
β Reject: Trip Port Does Not Match Shipment Port
What it means: The Trip's "First Canadian Port of Entry" is different from the Port listed on one of the shipments. They must match.
How to Fix:
- Step 1: Edit the Trip and ensure the Port is correct.
- Step 2: Edit all Shipments and ensure their Port matches the Trip.
- Step 3: Click Sync with CBSA. (Do not use legacy "Change Trip Only" as it won't update the shipments).
β Reject: Not On File
What it means: You tried to Cancel or Change something that CBSA says doesn't exist.
How to Fix:
- If Cancelling: No action needed. CBSA confirms it's not there.
- If Changing: Re-send the data as New (Sync with CBSA).
- If Renumbering: You likely changed a number and tried to send a "Change". You must revert the number, cancel the old one, create a new one, and send that as New.