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
No edit summary
 
(7 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|gaeX5kPJJ40|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.
<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 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.
<div class="bc-card">


=== Shipment Linked to Another Trip ===
<div class="bc-float-video">
;Example
  <div class="bc-video-trigger" data-video-id="yOfHR_quIpY">
<pre style="white-space: pre-wrap;
    <div class="bc-play-icon"><i class="fas fa-play-circle"></i></div>
white-space: -moz-pre-wrap;
  </div>
white-space: -pre-wrap;
</div>
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>


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


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


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


== Duplicate ==
<div style="clear: both;"></div>
;Examples
</div>
<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
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.
<h2 style="margin-top: 40px; border-bottom: 2px solid #eee; padding-bottom: 10px;">Quick Fix Workflow</h2>


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


== Cannot Cancel, Shipment Is Linked to a Trip ==
<div class="bc-card" style="margin-top: 20px;">
;Example
<h3><span class="bc-step-circle">2</span> Apply the Fix</h3>
<pre style="white-space: pre-wrap;  
<p>Find your error message in the sections below and apply the specific solution. Then, re-transmit:</p>
white-space: -moz-pre-wrap;
<div class="bc-cleanlist">
white-space: -pre-wrap;
* <strong>For Trip Rejects:</strong> Click <strong>Sync with CBSA</strong> on the eManifest Details page.
white-space: -o-pre-wrap;
* <strong>For Shipment Rejects:</strong> Use <strong>Send New Shipment Request</strong> (if needed), then <strong>Sync with CBSA</strong> on the Trip.
word-wrap: break-word;">CBSA Response: Shipment [1234PARS006793] Rejected Cancel Request Reason: Cannot Cancel, Shipment Is Linked to a Trip on 1234PARS006793</pre>
</div>
</div>


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.
<div class="bc-card" style="margin-top: 30px;">
<h3>🔍 Common Rejects at a Glance</h3>
<table class="wikitable" style="width:100%; margin-bottom:0;">
<tr>
<th>Reject Message</th>
<th>Typical Meaning</th>
</tr>
<tr>
<td><strong>Shipment Linked to Another Trip</strong></td>
<td>The shipment is already attached to a different manifest.</td>
</tr>
<tr>
<td><strong>Duplicate</strong></td>
<td>The Trip Number or CCN has already been used.</td>
</tr>
<tr>
<td><strong>Shipment Not On File</strong></td>
<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>


*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.
<h2 style="margin-top: 40px; border-bottom: 2px solid #eee; padding-bottom: 10px;">Detailed Solutions</h2>


*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]].
<div class="bc-card">
<h3>❌ Reject: Shipment Linked to Another Trip</h3>
<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>


== Shipment Not On File ==
<div class="bc-subtle">
<strong>Example:</strong> <code>Trip [12340009189] Rejected Cargo Control Number: Shipment Linked to Another Trip on 1234PARS008698</code>
</div>


;Example
<h4>How to Fix:</h4>
<pre style="white-space: pre-wrap;
<div class="bc-cleanlist">
white-space: -moz-pre-wrap;
* <strong>Step 1:</strong> Locate the <strong>original trip</strong> where this shipment was previously linked.
white-space: -pre-wrap;
* <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).
white-space: -o-pre-wrap;
* <strong>Step 3:</strong> Once the original trip update is accepted, return to your <strong>current (rejected) trip</strong>.
word-wrap: break-word;">CBSA Response: Trip [123400104] Rejected Cargo Control Number: Shipment Not On File on 1234PARS108098</pre>
* <strong>Step 4:</strong> Click <strong>Sync with CBSA</strong> to successfully link the shipment.
</div>


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.
<div class="bc-warning" style="margin-top: 15px;">
<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.
</div>
</div>


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


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


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.
<h4>How to Fix:</h4>
<div class="bc-cleanlist">
* <strong>Step 1:</strong> Change the conflicting <strong>Trip Number</strong> or <strong>Cargo Control Number</strong> to a new, unique value.
* <strong>Step 2:</strong> Re-transmit.
    * <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>


== Invalid Status of Request ==
<div class="bc-card" style="margin-top: 30px;">
<h3>❌ Reject: Cannot Cancel, Shipment Is Linked to a Trip</h3>
<p><strong>What it means:</strong> You tried to cancel a shipment, but CBSA still sees it attached to a trip.</p>


;Examples
<h4>How to Fix:</h4>
<pre style="white-space: pre-wrap;
<div class="bc-cleanlist">
white-space: -moz-pre-wrap;
* <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.
white-space: -pre-wrap;
* <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.
white-space: -o-pre-wrap;
</div>
word-wrap: break-word;">CBSA Response: Trip [123400104] Rejected Reason: Invalid status of request on 123400104
</div>
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:
<div class="bc-card" style="margin-top: 30px;">
<h3>❌ Reject: Shipment Not On File</h3>
<p><strong>What it means:</strong> The Trip is trying to link to a shipment that CBSA doesn't have yet.</p>


*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.
<div class="bc-subtle">
<strong>Example:</strong> <code>Trip [123400104] Rejected Cargo Control Number: Shipment Not On File on 1234PARS108098</code>
</div>


*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.
<h4>How to Fix:</h4>
<div class="bc-cleanlist">
* <strong>Step 1:</strong> Check the status of the shipment referenced in the error.
* <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>


*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.
<div class="bc-card" style="margin-top: 30px;">
<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>


*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.
<h4>Common Scenarios & Fixes:</h4>
<table class="wikitable" style="width:100%; margin-bottom:0;">
<tr>
<th>Scenario</th>
<th>Fix</th>
</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>


== Trip Port Does Not Match Shipment Port ==
<div class="bc-card" style="margin-top: 30px;">
;Example
<h3>❌ Reject: Trip Port Does Not Match Shipment Port</h3>
<pre style="white-space: pre-wrap;  
<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>
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
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.
<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>


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.
<div class="bc-card" style="margin-top: 30px;">
<h3>❌ Reject: Not On File</h3>
<p><strong>What it means:</strong> You tried to Cancel or Change something that CBSA says doesn't exist.</p>


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.
<h4>How to Fix:</h4>
<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>


== Already Used ==
{{AppPromo}}
;Examples
<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-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>


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.
</div> [[Category:ACI eManifest Guide]]
 
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.
 
== Not On File ==
 
;Examples
<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-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>
 
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.
 
*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.
 
*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.
 
*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]].
 
[[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"