Jump to content

Correcting Rejected ACI eManifests (ACI eManifest): Difference between revisions

From BorderConnect Wiki
← Older edit
No edit summary
No edit summary
 
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}}


{{#ev:youtube|yOfHR_quIpY|960|center|How to Make Changes and Correct Your ACI eManifest}}This guide offers instructions on '''correcting an [[ACI_eManifest_Software_User_Guide_(CBSA)|ACI eManifest]] that has received a reject response''' from [[Canada_Border_Services_Agency_-_General_Information|CBSA]] in BorderConnect [https://www.borderconnect.com/aci-e-manifest/index.htm ACI eManifest software]. If rejected, your trip or shipment's current status will show as CBSA Returned Error, and there will be a CBSA Response under your History/Status Messages showing a reject and the reason for it. In order to resolve the problem, you will need to locate that reject response, and follow the specific instructions for that reject.
{{#ev:youtube|yOfHR_quIpY|960|center|How to Make Changes and Correct Your ACI eManifest}}


This guide is not intended to replace BorderConnect [https://borderconnect.com/contact-us.htm support]. It may be that a combination of rejects or events create a situation for which the solution is too complicated to elaborate on here. This will only cover the basics of what each rejection message means, and the solution to the simple situations where it might be encountered.
This guide explains how to '''correct an [[ACI_eManifest_Software_User_Guide_(CBSA)|ACI eManifest]] that receives a reject response''' from [[Canada_Border_Services_Agency_-_General_Information|CBSA]] when using BorderConnect [https://www.borderconnect.com/aci-e-manifest/index.htm 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.
 
{{warning|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: [https://borderconnect.com/contact-us.htm 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.
 
{| class="wikitable"
! 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 ==


=== Shipment Linked to Another Trip ===
;Example
;Example
<pre style="white-space: pre-wrap;  
<pre style="white-space: pre-wrap; word-wrap: break-word;">
white-space: -moz-pre-wrap;
CBSA Response: Trip [12340009189] Rejected Cargo Control Number: Shipment Linked to Another Trip on 1234PARS008698
white-space: -pre-wrap;
</pre>
white-space: -o-pre-wrap;
 
word-wrap: break-word;">CBSA Response: Trip [12340009189] Rejected Cargo Control Number: Shipment Linked to Another Trip on 1234PARS008698</pre>
'''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'''.


This reject comes up when one of the shipments on the manifest you are trying to submit is already linked to a different manifest in CBSA's system. It will tell you which shipment is causing the problem at the end of the response. i.e. from the example the shipment 1234PARS008698 is the one that CBSA shows listed on another trip.
'''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


In order to resolve this problem, you will have to locate the original manifest that the shipment was listed on first. Once this has been found, you will need to click Sync with CBSA (if it has not been done already), or by using the legacy options such as sending a change request for that manifest by selecting Change Trip Only under Send to CBSA. This will make sure that the shipment is de-linked from that manifest in CBSA's system. Once this change request is accepted, you can return to your rejected manifest and click Sync with CBSA, or by using the legacy option, Change Trip Only. This will link the shipment and resolve the reject.
'''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''')


If you should find that the original manifest has already been arrived or released, you won't be able to update it. In this case the shipment will already be marked as arrived and won't be able to be reused. Instead you would need to assign a new cargo control number to the shipment, and send the shipment to CBSA using the option Send New Shipment Request. Once that is accepted, send a Change Trip Only for the manifest to resolve the reject. It is recommend that you also call BorderConnect support at 800-596-5176 for guidance, as depending on the situation it may also be necessary to cancel the rejected shipment using [http://www.cbsa-asfc.gc.ca/publications/forms-formulaires/bsf673.pdf Form BSF673] and contact the customs broker.
{{note|Depending on the situation, CBSA may also require cancelling the rejected shipment using [http://www.cbsa-asfc.gc.ca/publications/forms-formulaires/bsf673.pdf Form BSF673] and coordination with the customs broker. If you are unsure, contact BorderConnect support.}}


== Duplicate ==
== Duplicate ==
;Examples
;Examples
<pre style="white-space: pre-wrap;  
<pre style="white-space: pre-wrap; word-wrap: break-word;">
white-space: -moz-pre-wrap;
CBSA Response: Trip [1234114000] Rejected Client Supplied Request Id: Duplicate on 1234114000
white-space: -pre-wrap;
CBSA Response: Shipment [1234PARS006351] Rejected Client Supplied Request Id: Duplicate on 1234PARS006351
white-space: -o-pre-wrap;
</pre>
word-wrap: break-word;">CBSA Response: Trip [1234114000] Rejected Client Supplied Request Id: Duplicate on 1234114000
CBSA Response: Shipment [1234PARS006351] Rejected Client Supplied Request Id: Duplicate on 1234PARS006351</pre>


This reject comes up when the trip number you are using has already been used as a cargo control number, or when the cargo control number you are using has already been used as a trip number. CBSA's system does not allow this to take place.
'''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


In order to resolve the problem, you will most likely need to change the trip number or cargo control to a new one and resend the trip or shipment that was rejected, using the option 'Sync with CBSA' or 'Send New Shipment Request' under 'Send to CBSA' from the ACI Shipment Details page.
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 ==
== Cannot Cancel, Shipment Is Linked to a Trip ==
;Example
;Example
<pre style="white-space: pre-wrap;  
<pre style="white-space: pre-wrap; word-wrap: break-word;">
white-space: -moz-pre-wrap;
CBSA Response: Shipment [1234PARS006793] Rejected Cancel Request Reason: Cannot Cancel, Shipment Is Linked to a Trip on 1234PARS006793
white-space: -pre-wrap;
</pre>
white-space: -o-pre-wrap;
word-wrap: break-word;">CBSA Response: Shipment [1234PARS006793] Rejected Cancel Request Reason: Cannot Cancel, Shipment Is Linked to a Trip on 1234PARS006793</pre>


This a reject that occurs when you try to cancel a shipment that is linked to a trip in CBSA's system. A shipment can't be cancelled if CBSA has it listed on a manifest. You must first either de-link the shipment from the manifest in their system or cancel the manifest before the shipment cancel can be processed. The most common place for this reject to come up is when you try to cancel the eManifest. Because CBSA cannot guarantee the trip cancel gets processed first, shipments may fail to cancel.
'''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.


*If you were trying cancel the eManifest, you can resolve it by sending an extra cancel for the shipment(s) that got this reject. In the ACI Shipment Details page, under Send to CBSA, select Send Cancel/Delete Shipment Request. Because the cancel request for the trip will now have been processed, your shipment cancel will go through this time.
'''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 cancel just the shipment because you wanted to remove it from a manifest, you should now follow the instructions for removing shipments from an eManifest in the [[Updating_or_Correcting_an_Accepted_ACI_eManifest_(ACI_eManifest)|changes guide]].
*'''If you were trying to remove a shipment from a Trip:'''
Follow the procedures in [[Updating_or_Correcting_an_Accepted_ACI_eManifest_(ACI_eManifest)|Updating or Correcting an Accepted ACI eManifest]] for removing shipments correctly.


== Shipment Not On File ==
== Shipment Not On File ==


;Example
;Example
<pre style="white-space: pre-wrap;  
<pre style="white-space: pre-wrap; word-wrap: break-word;">
white-space: -moz-pre-wrap;
CBSA Response: Trip [123400104] Rejected Cargo Control Number: Shipment Not On File on 1234PARS108098
white-space: -pre-wrap;
</pre>
white-space: -o-pre-wrap;
word-wrap: break-word;">CBSA Response: Trip [123400104] Rejected Cargo Control Number: Shipment Not On File on 1234PARS108098</pre>
 
This reject means that one of the shipments on the manifest you are trying to submit is either not on file or in rejected status. It will tell you which shipment is causing the problem at the end of the response. i.e. from the example the shipment 1234PARS108098 is either not on file or rejected.
 
To correct the issue, you will first have to make sure the shipment that caused the reject gets into accepted status. If it is currently not on file, i.e. in draft or cancelled status, you will want to send it to CBSA using the option Send New Shipment Request from the ACI Shipment Details page. Or if it is a shipment that you picked up from another carrier, you will need to make sure that they send the shipment using their own ACI software.


If the shipment is in rejected status you will need to resolve that reject before proceeding with your trip fixing your trip. You will want to consult the guide on how to fix the shipment's reject before returning here.
'''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''').


Once the shipment that caused the reject is in accepted status, all you need to do to fix the trip is to click Sync with CBSA. The manifest will come back accepted and link successfully with the shipment.
'''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 ==
== Invalid Status of Request ==


;Examples
;Examples
<pre style="white-space: pre-wrap;  
<pre style="white-space: pre-wrap; word-wrap: break-word;">
white-space: -moz-pre-wrap;
CBSA Response: Trip [123400104] Rejected Reason: Invalid status of request on 123400104
white-space: -pre-wrap;
CBSA Response: Shipment [1234PARS108098] Rejected Reason: Invalid status of request on 1234PARS108098
white-space: -o-pre-wrap;
</pre>
word-wrap: break-word;">CBSA Response: Trip [123400104] Rejected Reason: Invalid status of request on 123400104
CBSA Response: Shipment [1234PARS108098] Rejected Reason: Invalid status of request on 1234PARS108098</pre>


Invalid status of request is a reject that basically means that your trip or shipment cannot be accepted again because it is already on file, or that you are trying to send a change or amend for a shipment that has been cancelled using the legacy options. It most commonly occurs when a manifest that you've previously sent to CBSA is then sent again. Your response to this reject will depend on your situation:
'''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


*If you resent your manifest because you made changes to it and wanted to update the manifest with CBSA, you should now click Sync with CBSA. This will allow CBSA to see your updates, and will bring the manifest out of rejected status. Please note also that clicking Sync with CBSA or sending change requests using the legacy options are the correct way to update your manifest with CBSA. Resending or re-syncing a manifest that is already accepted will always result in this error.
'''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


*If you resent your manifest by mistake, and had not made any changes to it, you do not need to take any action to correct it. CBSA still has your manifest from the first time it was sent, and the reject is only for the resend.
*'''You re-sent by mistake and made no changes:'''
# No action is required (CBSA still has the original accepted submission)


*If you sent a Synced or sent a change request using the legacy options on a manifest that you had previously cancelled, it is not going through because CBSA does not allow changes to cancelled manifests. From here, all you will need to do to correct it is click Sync with CBSA, or Send New Shipment Request from the ACI Shipment Details page, depending on whether the trip, shipment or both are rejected.
*'''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


*If this is the first time you've sent this manifest and you receive this response, i.e. it is not a resend, it means that the trip or shipment has already been used. This may be because the manifest was set up in another system, such as the CBSA Portal or through another service provider. In this case you can either use the manifest prepared in that system or have it cancelled from there before Syncing it with CBSA in BorderConnect. Or if you determine that the trip number or cargo control number is being used for a different load, you will need to assign a new trip number or cargo control number. <br />It could also be that the trip or shipment was set up previously in BorderConnect, then the trip number or cargo control number was changed but that change was not processed by CBSA. In this case you are best to contact our support to help you determine where it was used so that it can be cancelled out properly. Again, if it has already crossed the border, you will need to assign a new trip number or cargo control number.
*'''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
 
{{note|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 ==
== Trip Port Does Not Match Shipment Port ==
;Example
;Example
<pre style="white-space: pre-wrap;  
<pre style="white-space: pre-wrap; word-wrap: break-word;">
white-space: -moz-pre-wrap;
CBSA Response: Trip [123400763] Rejected Cargo Control Number: Trip Port Does Not Match Shipment Port on 1234PARS001549
white-space: -pre-wrap;
</pre>
white-space: -o-pre-wrap;
word-wrap: break-word;">CBSA Response: Trip [123400763] Rejected Cargo Control Number: Trip Port Does Not Match Shipment Port on 1234PARS001549</pre>


This reject comes up when you are trying to submit a manifest on which the trip and one of the attached shipments have a different First Canadian Port of Entry. The trip and all attached shipments must have the same port in order for the manifest to be accepted.
'''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.


This rejected commonly comes up when you update the port for the manifest and select 'Change Trip Only' using the legacy send options. If your manifest has shipments on it, then you must click Sync with CBSA, because the shipment ports must also be updated in CBSA's system.
'''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).


To resolve this reject, you must first edit the ports for the trip and all attached shipments to make sure they are correct Once this is done, click Sync with 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 ==


== Already Used ==
;Examples
;Examples
<pre style="white-space: pre-wrap;  
<pre style="white-space: pre-wrap; word-wrap: break-word;">
white-space: -moz-pre-wrap;
CBSA Response: Trip [123400811] Rejected Cargo Control Number: Already Used on 1234PARS002237
white-space: -pre-wrap;
CBSA Response: Shipment [1234PARS002237] Rejected Reason: Number Already Used on 1234PARS002237
white-space: -o-pre-wrap;
</pre>
word-wrap: break-word;">CBSA Response: Trip [123400811] Rejected Cargo Control Number: Already Used on 1234PARS002237
CBSA Response: Shipment [1234PARS002237] Rejected Reason: Number Already Used on 1234PARS002237</pre>


This reject means that the trip number or cargo control number that you're trying to submit has already been processed by CBSA, and cannot be reused again. The end of the reject message will tell you the trip number or cargo control number that has been used in the past. In our examples, it is the cargo control number 1234PARS002237.
'''What it means'''
The Trip number or Cargo Control Number has already been processed by CBSA and cannot be reused.


To resolve this reject, you will need to assign a new trip number or cargo control number to replace the rejected one. Once you have edited the number in BorderConnect, you will need to click Sync with CBSA or Send New Shipment Request for a shipment. In the case where you are resending a shipment, you will also need to wait for that to be accepted and then click Sync with CBSA.
'''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 ==
== Not On File ==


;Examples
;Examples
<pre style="white-space: pre-wrap;  
<pre style="white-space: pre-wrap; word-wrap: break-word;">
white-space: -moz-pre-wrap;
CBSA Response: Trip [12340218] Rejected Cancel Request Reason: Not On File on 12340218
white-space: -pre-wrap;
CBSA Response: Shipment [1234PARS0112] Rejected Cancel Request Reason: Not On File on 1234PARS0112
white-space: -o-pre-wrap;
</pre>
word-wrap: break-word;">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</pre>
'''What it means'''
A cancel request or legacy change request was submitted for a Trip/Shipment that CBSA does not have on file.


This is a reject that comes up when you try to send a cancel request or change request for a trip using the legacy send options for a shipment that is not in CBSA's system. e.g. you send a cancel for a trip but that trip was never sent in the first place. A common occurrence for this reject is if you were to edit a cargo control number in BorderConnect and send a change request for it. This will not be successful because CBSA will not be able to tell what the old cargo control number was that you are trying to update.
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)


*If you encounter this reject when you were trying to cancel a trip or a shipment using the legacy send options, you should not need to do anything else because the response confirms that it is not on file with CBSA. It is now free to be left cancelled or modified and resent.
'''How to fix it'''
*'''You were trying to cancel using legacy options:'''
# No action is required (CBSA confirms it is not on file)


*If you encounter this reject when you were trying to change something using the legacy send options '''other than trip number or cargo control number''', the rejected trip or shipment will need to be sent instead. i.e. by clicking Sync with CBSA or Send New Shipment Request.
*'''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)


*If you were trying to change your trip number or cargo control number, you should set the trip number or cargo control number back to what it was originally, and follow the procedures in for making those changes in the [[Updating_or_Correcting_an_Accepted_ACI_eManifest_(ACI_eManifest)|changes guide]].
*'''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_(ACI_eManifest)|Updating or Correcting an Accepted ACI eManifest]]


[[Category:ACI eManifest Guide]]
[[Category:ACI eManifest Guide]]

Latest revision as of 12:33, 22 January 2026

🔖 This article is part of the BorderConnect ACI eManifest Guide

Load video
YouTube
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:

  1. Open the Trip or Shipment showing status CBSA Returned Error
  2. In History/Status Messages, locate the CBSA Response that contains the reject
  3. 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)
  4. Apply the fix from the matching section in this guide
  5. 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)

  1. Locate the original trip where CBSA has that shipment linked
  2. 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
  3. Wait for the change request on the original trip to be accepted
  4. 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.

  1. Assign a new Cargo Control Number to replace the rejected CCN
  2. From the ACI Shipment Details page, send the shipment using Send New Shipment Request
  3. 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

  1. Change the conflicting Trip number or Cargo Control Number to a new, unique value
  2. 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:
  1. The Trip cancel may have processed, but the Shipment cancel did not
  2. Open the ACI Shipment Details page for the rejected shipment
  3. Under Send to CBSA, select Send Cancel/Delete Shipment Request again
  4. 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

  1. 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
  2. If the shipment is rejected, resolve the shipment reject first
  3. 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:
  1. Click Sync with CBSA (this is the correct method to update)
  2. Avoid re-sending an already accepted manifest as if it were new
  • You re-sent by mistake and made no changes:
  1. No action is required (CBSA still has the original accepted submission)
  • You attempted to update something that was previously cancelled:
  1. CBSA does not allow changes to cancelled items
  2. 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).

  1. Use the manifest prepared in that system, OR have it cancelled there before syncing in BorderConnect
  2. 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

  1. Edit the Trip port and all attached shipment ports so they match and are correct
  2. 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

  1. Assign a new Trip number or a new Cargo Control Number to replace the rejected one
  2. Re-send:
    • For Trip: click Sync with CBSA
    • For Shipment: use Send New Shipment Request
  3. 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:
  1. 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:
  1. 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:
  1. Set the Trip number or CCN back to the original value
  2. Follow the proper renumbering procedures in Updating or Correcting an Accepted ACI eManifest
Retrieved from "https://wiki.borderconnect.com/index.php?title=Correcting_Rejected_ACI_eManifests_(ACI_eManifest)&oldid=2236"