Correcting Rejected ACI eManifests (ACI eManifest)

🔖 This article is part of the BorderConnect ACI eManifest Guide

How to Make Changes and Correct Your ACI eManifest

This guide explains how to correct an ACI eManifest that receives a reject response from CBSA when using BorderConnect ACI eManifest software.

When CBSA rejects a Trip or Shipment:

The Current Status will show CBSA Returned Error
A CBSA Response line appears in History/Status Messages with the reject reason

To fix the reject, you must locate the CBSA reject response and follow the appropriate steps for that specific message.

⚠️ This guide covers common reject scenarios and basic solutions. Some combinations of rejects or edge cases may require additional troubleshooting. If you are unsure, contact BorderConnect support: Support or call 800-596-5176.

Quick Workflow: How to Fix Most CBSA Rejects

Use this checklist in order:

Open the Trip or Shipment showing status CBSA Returned Error
In History/Status Messages, locate the CBSA Response that contains the reject
Identify:
- Whether the reject is for a Trip or a Shipment
- The number referenced at the end of the message (often the Trip number or Cargo Control Number)
Apply the fix from the matching section in this guide
Re-send appropriately:
- For Trip-level fixes: click Sync with CBSA on the eManifest
- For Shipment-level fixes: use Send New Shipment Request (if needed), then Sync with CBSA on the Trip

Common CBSA Rejects at a Glance

Use the table below to quickly find the reject you received and the typical fix.

Reject message (key phrase)	Usually means	Typical fix
Shipment Linked to Another Trip	CCN is already attached to a different Trip on file	De-link shipment from original Trip, then re-sync rejected Trip
Duplicate	Trip number and CCN are conflicting/previously used as each other	Change Trip number or CCN, then re-send
Cannot Cancel, Shipment Is Linked to a Trip	Attempted to cancel a Shipment still attached to a Trip	Cancel Trip first (or remove shipment properly), then cancel Shipment again
Shipment Not On File	One Shipment on the Trip is not accepted/on file	Send the missing Shipment first, then Sync Trip
Invalid Status of Request	Trying to re-send or change something in a status CBSA will not accept	Use Sync for changes; if already on file, no action; if used elsewhere, renumber/cancel in other system
Trip Port Does Not Match Shipment Port	Trip First Canadian Port differs from one or more Shipments	Fix ports on Trip and Shipments, then Sync (not legacy Change Trip Only)
Already Used / Number Already Used	Trip number or CCN has already been processed and cannot be reused	Assign a new Trip number or CCN, then re-send
Not On File	Cancel/change request sent for something CBSA does not have	Often no action needed; send as new via Sync/Send New Shipment Request

Shipment Linked to Another Trip

Example

CBSA Response: Trip [12340009189] Rejected Cargo Control Number: Shipment Linked to Another Trip on 1234PARS008698

What it means One of the shipments on the trip (the Cargo Control Number shown at the end of the message) is already linked to a different trip in CBSA's system. In the example, the shipment is 1234PARS008698.

How to fix it (most common scenario)

Locate the original trip where CBSA has that shipment linked
On the original trip, ensure CBSA receives an update so the shipment is de-linked
- Click Sync with CBSA (preferred), or
- Use the legacy option under Send to CBSA to send a change request (for example, Change Trip Only) if required for that workflow
Wait for the change request on the original trip to be accepted
Return to the rejected trip and click Sync with CBSA (or legacy Change Trip Only) to re-link the shipment successfully

If the original trip has already been arrived/released If the original trip is already arrived/released, it cannot be updated and the shipment may not be reusable.

Assign a new Cargo Control Number to replace the rejected CCN
From the ACI Shipment Details page, send the shipment using Send New Shipment Request
Once accepted, send the trip update using Sync with CBSA (or legacy Change Trip Only)

🔖 Depending on the situation, CBSA may also require cancelling the rejected shipment using Form BSF673 and coordination with the customs broker. If you are unsure, contact BorderConnect support.

Duplicate

Examples

CBSA Response: Trip [1234114000] Rejected Client Supplied Request Id: Duplicate on 1234114000
CBSA Response: Shipment [1234PARS006351] Rejected Client Supplied Request Id: Duplicate on 1234PARS006351

What it means CBSA detected a conflict where:

A Trip number has already been used as a Cargo Control Number, or
A Cargo Control Number has already been used as a Trip number

CBSA does not allow this.

How to fix it

Change the conflicting Trip number or Cargo Control Number to a new, unique value
Re-send:
- For a Trip reject: click Sync with CBSA
- For a Shipment reject: use Send New Shipment Request from the ACI Shipment Details page, then Sync with CBSA on the Trip if needed

Cannot Cancel, Shipment Is Linked to a Trip

Example

CBSA Response: Shipment [1234PARS006793] Rejected Cancel Request Reason: Cannot Cancel, Shipment Is Linked to a Trip on 1234PARS006793

What it means You attempted to cancel a shipment that CBSA still shows as linked to a trip. CBSA will not cancel a shipment while it is attached to a trip.

How to fix it

If you were canceling the entire eManifest:

The Trip cancel may have processed, but the Shipment cancel did not
Open the ACI Shipment Details page for the rejected shipment
Under Send to CBSA, select Send Cancel/Delete Shipment Request again
The shipment cancel typically succeeds the second time once the Trip cancel is already processed

If you were trying to remove a shipment from a Trip:

Follow the procedures in Updating or Correcting an Accepted ACI eManifest for removing shipments correctly.

Shipment Not On File

Example

CBSA Response: Trip [123400104] Rejected Cargo Control Number: Shipment Not On File on 1234PARS108098

What it means A shipment listed on your trip is not accepted/on file in CBSA's system (or is currently rejected). The CCN is shown at the end of the message (example: 1234PARS108098).

How to fix it

Make sure the shipment causing the error is accepted/on file first:
- If it is Draft or Cancelled: open the ACI Shipment Details page and use Send New Shipment Request
- If it belongs to another carrier: the other carrier must transmit it using their own ACI software
If the shipment is rejected, resolve the shipment reject first
Once the shipment is accepted/on file, return to the trip and click Sync with CBSA

Invalid Status of Request

Examples

CBSA Response: Trip [123400104] Rejected Reason: Invalid status of request on 123400104
CBSA Response: Shipment [1234PARS108098] Rejected Reason: Invalid status of request on 1234PARS108098

What it means This reject generally indicates CBSA cannot accept the request in the way it was sent, most commonly because:

The Trip/Shipment is already on file and you attempted to re-send it as if it were new, or
A change/amend was attempted on an item that was previously cancelled using legacy options

How to fix it (based on what happened)

You made changes and want CBSA to receive the update:

Click Sync with CBSA (this is the correct method to update)
Avoid re-sending an already accepted manifest as if it were new

You re-sent by mistake and made no changes:

No action is required (CBSA still has the original accepted submission)

You attempted to update something that was previously cancelled:

CBSA does not allow changes to cancelled items
Re-send appropriately:
- For Trip: click Sync with CBSA
- For Shipment: use Send New Shipment Request from the ACI Shipment Details page

This is the first time you are sending, but CBSA says invalid status:

The Trip/Shipment may already exist in another system (CBSA Portal or another service provider).

Use the manifest prepared in that system, OR have it cancelled there before syncing in BorderConnect
If the number is being used for a different load, assign a new Trip number or CCN

🔖 If the Trip/Shipment was previously created, then renumbered in BorderConnect but CBSA never processed the change, support may need to help locate and clear the original record.

Trip Port Does Not Match Shipment Port

Example

CBSA Response: Trip [123400763] Rejected Cargo Control Number: Trip Port Does Not Match Shipment Port on 1234PARS001549

What it means The Trip First Canadian Port of Entry does not match the First Canadian Port of Entry on one or more attached shipments. CBSA requires the Trip and all shipments on the trip to use the same port.

Common cause This often occurs when the Trip port is changed using legacy Change Trip Only while shipments are present (the shipment ports do not get updated in CBSA).

How to fix it

Edit the Trip port and all attached shipment ports so they match and are correct
Click Sync with CBSA (do not use legacy Change Trip Only when shipments are on the Trip)

Already Used / Number Already Used

Examples

CBSA Response: Trip [123400811] Rejected Cargo Control Number: Already Used on 1234PARS002237
CBSA Response: Shipment [1234PARS002237] Rejected Reason: Number Already Used on 1234PARS002237

What it means The Trip number or Cargo Control Number has already been processed by CBSA and cannot be reused.

How to fix it

Assign a new Trip number or a new Cargo Control Number to replace the rejected one
Re-send:
- For Trip: click Sync with CBSA
- For Shipment: use Send New Shipment Request
If a Shipment was re-sent, wait for it to be accepted and then Sync with CBSA on the Trip

Not On File

Examples

CBSA Response: Trip [12340218] Rejected Cancel Request Reason: Not On File on 12340218
CBSA Response: Shipment [1234PARS0112] Rejected Cancel Request Reason: Not On File on 1234PARS0112

What it means A cancel request or legacy change request was submitted for a Trip/Shipment that CBSA does not have on file.

This can occur if:

The Trip/Shipment was never transmitted, OR
A number was edited and a legacy change was sent (CBSA cannot determine the "old" number to update)

How to fix it

You were trying to cancel using legacy options:

No action is required (CBSA confirms it is not on file)

You were trying to change something (not Trip number or CCN) using legacy options:

Re-send using:
- Sync with CBSA (Trip-level), or
- Send New Shipment Request (Shipment-level)

You were trying to change a Trip number or Cargo Control Number:

Set the Trip number or CCN back to the original value
Follow the proper renumbering procedures in Updating or Correcting an Accepted ACI eManifest