Jump to content
🚛
Streamline your cross-border operation. From ACE & ACI eManifests to PARS tracking and U.S. In-Bond filing, BorderConnect is the fastest way to cross.
Start Free Trial

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

From BorderConnect Wiki
← Older edit
No edit summary
Tag: Manual revert
No edit summary
 
(3 intermediate revisions by the same user not shown)
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">


{{#ev:youtube|yOfHR_quIpY|960|center|How to Make Changes and Correct Your ACI eManifest}}
<div class="bc-article-hero">
<h1>Correcting Rejected ACI eManifests</h1>
<p>A troubleshooting guide for resolving "CBSA Returned Error" statuses and getting your manifest accepted.</p>
<div class="bc-article-meta">
<span class="bc-article-pill"><i class="fas fa-tools"></i> Type: Troubleshooting</span>
<span class="bc-article-pill"><i class="far fa-clock"></i> Time: Varies</span>
</div>
</div>


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].
<div class="bc-card">


When CBSA rejects a Trip or Shipment:
<div class="bc-float-video">
* The '''Current Status''' will show '''CBSA Returned Error'''
  <div class="bc-video-trigger" data-video-id="yOfHR_quIpY">
* A '''CBSA Response''' line appears in '''History/Status Messages''' with the reject reason
    <div class="bc-play-icon"><i class="fas fa-play-circle"></i></div>
  </div>
</div>


To fix the reject, you must locate the CBSA reject response and follow the appropriate steps for that specific message.
<h2 style="margin-top: 0;">Overview</h2>
<p>When [[Canada_Border_Services_Agency_-_General_Information|CBSA]] rejects a Trip or Shipment, the <strong>Current Status</strong> updates to <strong>CBSA Returned Error</strong>, and a specific error message appears in the <strong>History/Status Messages</strong> section.</p>


{{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.}}
<p>To fix the reject, you must locate the CBSA response message and follow the appropriate steps for that specific error.</p>


== Quick Workflow: How to Fix Most CBSA Rejects ==
<div class="bc-warning" style="margin-top: 20px;">
<strong>Support Note:</strong> This guide covers common rejects. Complex scenarios involving multiple carriers or edge cases may require assistance. If unsure, contact [https://borderconnect.com/contact-us.htm BorderConnect Support] at 800-596-5176.
</div>


Use this checklist in order:
<div style="clear: both;"></div>
</div>


# '''Open the Trip or Shipment''' showing status '''CBSA Returned Error'''
<h2 style="margin-top: 40px; border-bottom: 2px solid #eee; padding-bottom: 10px;">Quick Fix Workflow</h2>
# 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 ==
<div class="bc-card">
<h3><span class="bc-step-circle">1</span> Identify the Error</h3>
<div class="bc-cleanlist">
* Open the Trip or Shipment showing <strong>CBSA Returned Error</strong>.
* Scroll to <strong>History/Status Messages</strong>.
* Locate the <strong>CBSA Response</strong> line.
* Note the <strong>Key Phrase</strong> (e.g., "Duplicate", "Shipment Not On File") and the <strong>Reference Number</strong> (e.g., CCN or Trip Number).
</div>
</div>


Use the table below to quickly find the reject you received and the typical fix.
<div class="bc-card" style="margin-top: 20px;">
<h3><span class="bc-step-circle">2</span> Apply the Fix</h3>
<p>Find your error message in the sections below and apply the specific solution. Then, re-transmit:</p>
<div class="bc-cleanlist">
* <strong>For Trip Rejects:</strong> Click <strong>Sync with CBSA</strong> on the eManifest Details page.
* <strong>For Shipment Rejects:</strong> Use <strong>Send New Shipment Request</strong> (if needed), then <strong>Sync with CBSA</strong> on the Trip.
</div>
</div>


{| class="wikitable"
<div class="bc-card" style="margin-top: 30px;">
! Reject message (key phrase) !! Usually means !! Typical fix
<h3>🔍 Common Rejects at a Glance</h3>
|-
<table class="wikitable" style="width:100%; margin-bottom:0;">
| 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
<tr>
|-
<th>Reject Message</th>
| Duplicate || Trip number and CCN are conflicting/previously used as each other || Change Trip number or CCN, then re-send
<th>Typical Meaning</th>
|-
</tr>
| 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
<tr>
|-
<td><strong>Shipment Linked to Another Trip</strong></td>
| Shipment Not On File || One Shipment on the Trip is not accepted/on file || Send the missing Shipment first, then Sync Trip
<td>The shipment is already attached to a different manifest.</td>
|-
</tr>
| 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
<tr>
|-
<td><strong>Duplicate</strong></td>
| 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)
<td>The Trip Number or CCN has already been used.</td>
|-
</tr>
| 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
<tr>
|-
<td><strong>Shipment Not On File</strong></td>
| 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
<td>A shipment listed on the trip hasn't been accepted yet.</td>
|}
</tr>
<tr>
<td><strong>Invalid Status of Request</strong></td>
<td>Trying to send a "New" request for something already on file.</td>
</tr>
<tr>
<td><strong>Trip Port Does Not Match</strong></td>
<td>Trip port differs from the shipment port.</td>
</tr>
<tr>
<td><strong>Already Used</strong></td>
<td>The number has been processed and cannot be reused.</td>
</tr>
</table>
</div>


== Shipment Linked to Another Trip ==
<h2 style="margin-top: 40px; border-bottom: 2px solid #eee; padding-bottom: 10px;">Detailed Solutions</h2>


;Example
<div class="bc-card">
<pre style="white-space: pre-wrap; word-wrap: break-word;">
<h3>❌ Reject: Shipment Linked to Another Trip</h3>
CBSA Response: Trip [12340009189] Rejected Cargo Control Number: Shipment Linked to Another Trip on 1234PARS008698
<p><strong>What it means:</strong> The Cargo Control Number (CCN) listed in the error is currently attached to a <em>different</em> trip in CBSA's system.</p>
</pre>


'''What it means'''
<div class="bc-subtle">
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'''.
<strong>Example:</strong> <code>Trip [12340009189] Rejected Cargo Control Number: Shipment Linked to Another Trip on 1234PARS008698</code>
</div>


'''How to fix it (most common scenario)'''
<h4>How to Fix:</h4>
# Locate the original trip where CBSA has that shipment linked
<div class="bc-cleanlist">
# On the original trip, ensure CBSA receives an update so the shipment is de-linked
* <strong>Step 1:</strong> Locate the <strong>original trip</strong> where this shipment was previously linked.
#* Click '''Sync with CBSA''' (preferred), or
* <strong>Step 2:</strong> On that original trip, click <strong>Sync with CBSA</strong> to update it (this tells CBSA the shipment is no longer there).
#* Use the legacy option under '''Send to CBSA''' to send a change request (for example, '''Change Trip Only''') if required for that workflow
* <strong>Step 3:</strong> Once the original trip update is accepted, return to your <strong>current (rejected) trip</strong>.
# Wait for the change request on the original trip to be accepted
* <strong>Step 4:</strong> Click <strong>Sync with CBSA</strong> to successfully link the shipment.
# Return to the rejected trip and click '''Sync with CBSA''' (or legacy '''Change Trip Only''') to re-link the shipment successfully
</div>


'''If the original trip has already been arrived/released'''
<div class="bc-warning" style="margin-top: 15px;">
If the original trip is already arrived/released, it cannot be updated and the shipment may not be reusable.
<strong>If Original Trip is Arrived:</strong> If the old trip is already released, you cannot update it. You must assign a <strong>New CCN</strong> to the shipment on the new trip and re-send it as a new shipment.
# Assign a new Cargo Control Number to replace the rejected CCN
</div>
# From the ACI Shipment Details page, send the shipment using '''Send New Shipment Request'''
</div>
# Once accepted, send the trip update using '''Sync with CBSA''' (or legacy '''Change Trip Only''')


{{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.}}
<div class="bc-card" style="margin-top: 30px;">
<h3>❌ Reject: Duplicate / Number Already Used</h3>
<p><strong>What it means:</strong> 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.</p>


== Duplicate ==
<div class="bc-subtle">
<strong>Example:</strong> <code>Trip [1234114000] Rejected Client Supplied Request Id: Duplicate on 1234114000</code>
</div>


;Examples
<h4>How to Fix:</h4>
<pre style="white-space: pre-wrap; word-wrap: break-word;">
<div class="bc-cleanlist">
CBSA Response: Trip [1234114000] Rejected Client Supplied Request Id: Duplicate on 1234114000
* <strong>Step 1:</strong> Change the conflicting <strong>Trip Number</strong> or <strong>Cargo Control Number</strong> to a new, unique value.
CBSA Response: Shipment [1234PARS006351] Rejected Client Supplied Request Id: Duplicate on 1234PARS006351
* <strong>Step 2:</strong> Re-transmit.
</pre>
    * <strong>Trip Reject:</strong> Click <strong>Sync with CBSA</strong>.
    * <strong>Shipment Reject:</strong> Click <strong>Send New Shipment Request</strong> inside the shipment, then Sync the trip.
</div>
</div>


'''What it means'''
<div class="bc-card" style="margin-top: 30px;">
CBSA detected a conflict where:
<h3>❌ Reject: Cannot Cancel, Shipment Is Linked to a Trip</h3>
* A Trip number has already been used as a Cargo Control Number, or
<p><strong>What it means:</strong> You tried to cancel a shipment, but CBSA still sees it attached to a trip.</p>
* A Cargo Control Number has already been used as a Trip number


CBSA does not allow this.
<h4>How to Fix:</h4>
<div class="bc-cleanlist">
* <strong>Scenario A (Cancelling Manifest):</strong> The Trip cancel likely worked, but the shipment didn't. Simply go to the <strong>Shipment Details</strong> page and click <strong>Send Cancel/Delete Shipment Request</strong> again.
* <strong>Scenario B (Removing Shipment):</strong> You must remove the shipment from the trip profile first, send the trip update, <em>then</em> cancel the shipment.
</div>
</div>


'''How to fix it'''
<div class="bc-card" style="margin-top: 30px;">
# Change the conflicting Trip number or Cargo Control Number to a new, unique value
<h3>❌ Reject: Shipment Not On File</h3>
# Re-send:
<p><strong>What it means:</strong> The Trip is trying to link to a shipment that CBSA doesn't have yet.</p>
#* 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 ==
<div class="bc-subtle">
<strong>Example:</strong> <code>Trip [123400104] Rejected Cargo Control Number: Shipment Not On File on 1234PARS108098</code>
</div>


;Example
<h4>How to Fix:</h4>
<pre style="white-space: pre-wrap; word-wrap: break-word;">
<div class="bc-cleanlist">
CBSA Response: Shipment [1234PARS006793] Rejected Cancel Request Reason: Cannot Cancel, Shipment Is Linked to a Trip on 1234PARS006793
* <strong>Step 1:</strong> Check the status of the shipment referenced in the error.
</pre>
* <strong>Step 2:</strong> If it is <strong>Draft</strong> or <strong>Rejected</strong>, open the shipment and click <strong>Send New Shipment Request</strong>.
* <strong>Step 3:</strong> Once the shipment is accepted, return to the trip and click <strong>Sync with CBSA</strong>.
</div>
</div>


'''What it means'''
<div class="bc-card" style="margin-top: 30px;">
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.
<h3>❌ Reject: Invalid Status of Request</h3>
<p><strong>What it means:</strong> 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.</p>


'''How to fix it'''
<h4>Common Scenarios & Fixes:</h4>
*'''If you were canceling the entire eManifest:'''
<table class="wikitable" style="width:100%; margin-bottom:0;">
# The Trip cancel may have processed, but the Shipment cancel did not
<tr>
# Open the ACI Shipment Details page for the rejected shipment
<th>Scenario</th>
# Under '''Send to CBSA''', select '''Send Cancel/Delete Shipment Request''' again
<th>Fix</th>
# The shipment cancel typically succeeds the second time once the Trip cancel is already processed
</tr>
<tr>
<td><strong>Re-sending an accepted manifest</strong></td>
<td>No action needed. CBSA already has it. If you made changes, use <strong>Sync with CBSA</strong> instead.</td>
</tr>
<tr>
<td><strong>Updating a Cancelled item</strong></td>
<td>CBSA won't update cancelled items. You must re-send it as <strong>New</strong> (Sync with CBSA).</td>
</tr>
<tr>
<td><strong>First time sending</strong></td>
<td>The number may exist in another system (Portal). Assign a new Trip/CCN and re-send.</td>
</tr>
</table>
</div>


*'''If you were trying to remove a shipment from a Trip:'''
<div class="bc-card" style="margin-top: 30px;">
Follow the procedures in [[Updating_or_Correcting_an_Accepted_ACI_eManifest_(ACI_eManifest)|Updating or Correcting an Accepted ACI eManifest]] for removing shipments correctly.
<h3>❌ Reject: Trip Port Does Not Match Shipment Port</h3>
<p><strong>What it means:</strong> The Trip's "First Canadian Port of Entry" is different from the Port listed on one of the shipments. They must match.</p>


== Shipment Not On File ==
<h4>How to Fix:</h4>
<div class="bc-cleanlist">
* <strong>Step 1:</strong> Edit the Trip and ensure the Port is correct.
* <strong>Step 2:</strong> Edit all Shipments and ensure their Port matches the Trip.
* <strong>Step 3:</strong> Click <strong>Sync with CBSA</strong>. (Do <strong>not</strong> use legacy "Change Trip Only" as it won't update the shipments).
</div>
</div>


;Example
<div class="bc-card" style="margin-top: 30px;">
<pre style="white-space: pre-wrap; word-wrap: break-word;">
<h3>❌ Reject: Not On File</h3>
CBSA Response: Trip [123400104] Rejected Cargo Control Number: Shipment Not On File on 1234PARS108098
<p><strong>What it means:</strong> You tried to Cancel or Change something that CBSA says doesn't exist.</p>
</pre>


'''What it means'''
<h4>How to Fix:</h4>
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''').
<div class="bc-cleanlist">
* <strong>If Cancelling:</strong> No action needed. CBSA confirms it's not there.
* <strong>If Changing:</strong> Re-send the data as <strong>New</strong> (Sync with CBSA).
* <strong>If Renumbering:</strong> 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.
</div>
</div>


'''How to fix it'''
{{AppPromo}}
# 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 ==
</div> [[Category:ACI eManifest Guide]]
 
;Examples
<pre style="white-space: pre-wrap; 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>
 
'''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
 
{{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 ==
 
;Example
<pre style="white-space: pre-wrap; word-wrap: break-word;">
CBSA Response: Trip [123400763] Rejected Cargo Control Number: Trip Port Does Not Match Shipment Port on 1234PARS001549
</pre>
 
'''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
<pre style="white-space: pre-wrap; 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>
 
'''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
<pre style="white-space: pre-wrap; 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 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_(ACI_eManifest)|Updating or Correcting an Accepted ACI eManifest]]
 
[[Category:ACI eManifest Guide]]

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.

Type: Troubleshooting Time: Varies

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.
📱

eManifesting in your pocket. Process ACE & ACI eManifests, track shipments in real-time, and upload documents instantly—anytime, anywhere.

Download on theApp Store GET IT ONGoogle Play

Retrieved from "https://wiki.borderconnect.com/index.php?title=Correcting_Rejected_ACI_eManifests_(ACI_eManifest)&oldid=3645"