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 ACE Manifests (ACE Manifest): Difference between revisions

From BorderConnect Wiki
← Older edit
No edit summary
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{#seo:
|title=How to Fix CBP Rejected ACE Manifests {{!}} BorderConnect Support Wiki
|title_mode=replace
|keywords=CBP reject codes, ACE manifest rejected, shipment already on file, manifest already on file do not resend, invalid trailer ACE ID, inv travel doc number FAST card, no person in charge, fix ACE manifest errors, BorderConnect troubleshooting
|description=Troubleshooting guide for fixing CBP rejected ACE Manifests. Learn how to resolve common U.S. customs errors like "Shipment Already On File" and "Invalid Travel Doc Number".
}}
{{note|This article is part of the [[ACE_Manifest_Software_User_Guide_(CBP)|BorderConnect ACE Manifest Guide]]|info}}
{{note|This article is part of the [[ACE_Manifest_Software_User_Guide_(CBP)|BorderConnect ACE Manifest Guide]]|info}}
<div class="bc-wrap">


{{#ev:youtube|zhNVv23LBAc|960|center|How to Make Changes and Cancel an ACE Manifest in BorderConnect.}}
<div class="bc-article-hero">
<h1>Correcting Rejected ACE Manifests</h1>
<p>A troubleshooting guide for resolving "Man Returned to Preliminary" statuses and specific CBP reject codes.</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 troubleshoot and correct an '''ACE eManifest''' that has been '''rejected by CBP''' in BorderConnect [https://www.borderconnect.com/ace-e-manifest/index.htm ACE Manifest software].
<div class="bc-card">


When CBP rejects a manifest or shipment, you will see:
<div class="bc-float-video">
* The manifest status move back (often to a preliminary/returned state), and
  <div class="bc-video-trigger" data-video-id="zhNVv23LBAc">
* A '''CBP Response''' message in '''History/Status Messages''' explaining the reason.
    <div class="bc-play-icon"><i class="fas fa-play-circle"></i></div>
  </div>
</div>


{{reminder|This guide covers common reject scenarios and the most straightforward fixes. Some situations involve multiple rejects or unusual workflows (unassociated shipments, advanced attach/detach actions, or port arrival mismatches). If you are unsure, contact BorderConnect [https://borderconnect.com/contact-us.htm Support].}}
<h2 style="margin-top: 0;">Overview</h2>
<p>When [[US Customs and Border Protection - General Information|CBP]] rejects a manifest or shipment, the status typically reverts to a preliminary state, and a specific <strong>CBP Response</strong> message appears in the <strong>History/Status Messages</strong> section.</p>


__TOC__
<p>To fix the reject, you must identify the specific error code and apply the correct fix before re-transmitting.</p>


== Before you start: the fast troubleshooting workflow ==
<div class="bc-warning" style="margin-top: 20px;">
<strong>Support Note:</strong> This guide covers common rejects. Complex scenarios involving unassociated shipments, port mismatches, or multi-carrier consolidations may require assistance. If unsure, contact [https://borderconnect.com/contact-us.htm BorderConnect Support].
</div>


Use this quick sequence before diving into a specific reject:
<div style="clear: both;"></div>
</div>


# Open the '''ACE eManifest Details''' page
<h2 style="margin-top: 40px; border-bottom: 2px solid #eee; padding-bottom: 10px;">Quick Troubleshooting Workflow</h2>
# In '''History/Status Messages''', locate the most recent '''CBP Response''' that contains the word '''Rejected'''
# Note the '''Trip Number''' and (if applicable) the '''Shipment Control Number'''
# Make the correction in the appropriate place:
#* Trip-level issue → Trip/Manifest page
#* Shipment issue → Shipment Details page
#* Driver/Trailer issue → Driver/Trailer profile
# Re-send using the correct action:
#* '''Sync with CBP''' (standard)
#* '''Cancel eManifest''' (to clear a rejected/preliminary version in CBP)
#* Shipment-only actions (advanced): '''Detach Shipment Message''' / '''Cancel Shipment Message''' (use carefully)


=== Visual decision guide (quick) ===
<div class="bc-card">
<h3><span class="bc-step-circle">1</span> Diagnosis</h3>
<div class="bc-cleanlist">
* Open the <strong>ACE eManifest Details</strong> page.
* Scroll to <strong>History/Status Messages</strong>.
* Locate the most recent <strong>CBP Response</strong> containing "Rejected".
* Note if the error refers to the <strong>Trip</strong> (Manifest) or a specific <strong>Shipment</strong>.
</div>
</div>


{| class="wikitable"
<div class="bc-card" style="margin-top: 20px;">
! What does the reject mention? !! Most likely fix location !! Most likely action
<h3><span class="bc-step-circle">2</span> Decision Guide</h3>
|-
<table class="wikitable" style="width:100%; margin-bottom:0;">
| Trip / Manifest || ACE eManifest Details (trip) || Sync with CBP (or Cancel eManifest → Sync)
<tr>
|-
<th>Reject Location</th>
| Shipment / Bill || ACE Shipment Details || Fix shipment data → Sync with CBP
<th>Likely Fix</th>
|-
</tr>
| Driver / Passenger || Driver profile || Fix/remove invalid ACE ID or FAST info → Sync with CBP
<tr>
|-
<td><strong>Trip / Manifest</strong></td>
| Trailer || Trailer profile || Fix/remove invalid ACE ID / plate format → Sync with CBP
<td>Fix Trip data &rarr; <strong>Sync with CBP</strong> (or Cancel eManifest first).</td>
|-
</tr>
| No reason specified || Check ETA / trailer (if empty) / advanced attach cases || Fix likely cause → Sync with CBP
<tr>
|}
<td><strong>Shipment / Bill</strong></td>
<td>Fix Shipment data &rarr; <strong>Sync with CBP</strong>.</td>
</tr>
<tr>
<td><strong>Driver / Passenger</strong></td>
<td>Fix Profile (ACE ID/FAST) &rarr; <strong>Sync with CBP</strong>.</td>
</tr>
<tr>
<td><strong>Trailer</strong></td>
<td>Fix Profile (Plate/ACE ID) &rarr; <strong>Sync with CBP</strong>.</td>
</tr>
</table>
</div>


== Common reject messages and how to fix them ==
<h2 style="margin-top: 40px; border-bottom: 2px solid #eee; padding-bottom: 10px;">Common Reject Solutions</h2>


== Shipment Already On File ==
<div class="bc-card">
<h3>❌ Shipment Already On File</h3>
<p><strong>What it means:</strong> The Shipment Control Number (SCN) is already active in CBP's system, likely under a different trip or date.</p>


;Example
<div class="bc-subtle">
<pre style="white-space: pre-wrap; word-wrap: break-word;">
<strong>Scenario A: You changed Trip Number or ETA</strong><br>
CBP Response: Man Returned to Preliminary, Trip [ABCD028321]
CBP sees the new Trip # as a "New" manifest, but the shipment is still stuck on the "Old" one.
CBP Response: Shipment Already on File, Shipment [ABCD0092355]
<div class="bc-cleanlist">
CBP Response: XXXX Bill Rejected XXXX, Shipment [ABCD0092355]
1. Click <strong>Cancel eManifest</strong>.
CBP Response: Shipments Rejected [1], Shipments Accepted [0] for Complete Manifest
2. Change the Trip # or ETA <strong>back to the original values</strong>.
</pre>
3. Click <strong>Cancel eManifest</strong> again (clearing the old record).
4. Update to your desired Trip #/ETA.
5. Click <strong>Sync with CBP</strong>.
</div>
</div>


'''What it means'''
<div class="bc-subtle" style="margin-top: 15px;">
One of the shipments on your manifest already exists in CBP’s system. CBP will not accept the manifest because the shipment control number is already on file.
<strong>Scenario B: Unassociated Shipment</strong><br>
The shipment was sent independently before the manifest.
<div class="bc-cleanlist">
1. Click <strong>Cancel eManifest</strong>.
2. Open the shipment and click <strong>Detach Shipment Message</strong>.
3. Once processed, click <strong>Cancel Shipment Message</strong>.
4. Return to the manifest and click <strong>Sync with CBP</strong>.
</div>
</div>
</div>


'''What to do'''
<div class="bc-card" style="margin-top: 30px;">
Start by identifying why CBP already has the shipment:
<h3>❌ Shipment Not On File</h3>
<p><strong>What it means:</strong> You tried to Amend or Cancel a shipment that CBP does not have.</p>
<div class="bc-cleanlist">
* <strong>Common Cause:</strong> Changing an SCN on an accepted manifest and sending an "Amend", or adding a new shipment and sending an "Amend".
* <strong>The Fix:</strong> Click <strong>Cancel eManifest</strong> (to clear the confusion), wait for acceptance, then click <strong>Sync with CBP</strong> to send a fresh copy.
</div>
</div>


=== Scenario A: You changed the trip number or ETA date and resent ===
<div class="bc-card" style="margin-top: 30px;">
This is common. CBP treats it as a different manifest, but the shipment still exists under the original trip/date context.
<h3>❌ Manifest Already On File, Do Not Resend</h3>
<p><strong>What it means:</strong> CBP already has this exact manifest.</p>
<div class="bc-cleanlist">
* <strong>If you made changes:</strong> Click <strong>Sync with CBP</strong> (this sends an update, not a new creation).
* <strong>If you made no changes:</strong> No action needed. It is already on file.
* <strong>If this is your first attempt:</strong> The Trip Number is likely used by another provider or portal. You must cancel it there or use a new Trip Number.
</div>
</div>


# Click '''Cancel eManifest''' on the ACE eManifest Details page
<div class="bc-card" style="margin-top: 30px;">
# Wait for CBP to accept the cancellation
<h3>❌ Data Validation Errors</h3>
# Change the trip number or ETA date back to the original values
<p>Specific data fields that failed CBP checks.</p>
# Click '''Cancel eManifest''' again to clear the original version in CBP
# Once accepted, set the trip number/ETA to the correct (desired) values again
# Click '''Sync with CBP'''


=== Scenario B: Shipment was previously sent as an unassociated shipment ===
<table class="wikitable" style="width:100%; margin-bottom:0;">
CBP already has the shipment, then the complete manifest attempt fails.
<tr>
<th>Error</th>
<th>Solution</th>
</tr>
<tr>
<td><strong>Incorrect Harmonized #</strong></td>
<td>Open the shipment, edit the Commodity, and ensure the HS Code is a valid <strong>6-digit number</strong>.</td>
</tr>
<tr>
<td><strong>Invalid Trailer ACE ID</strong></td>
<td>Open the Trailer Profile. Verify the ACE ID is correct or <strong>remove it</strong> if unknown.</td>
</tr>
<tr>
<td><strong>Inv Travel Doc Number</strong></td>
<td>The FAST Card number is invalid or inactive. Update the Driver Profile or temporarily remove the FAST card to file as a standard driver.</td>
</tr>
<tr>
<td><strong>Invalid Driver/Passenger ACE ID</strong></td>
<td>Open the Driver/Passenger Profile. Remove or correct the ACE ID field.</td>
</tr>
</table>
</div>


# From the ACE eManifest Details page, click '''Cancel eManifest'''
<div class="bc-card" style="margin-top: 30px;">
# Open the shipment and use '''Detach Shipment Message''' (Shipment Only Send to CBP)
<h3>❌ Operational Rejects</h3>
# After detach is processed, use '''Cancel Shipment Message''' (Send to CBP)
# Once both cancels are accepted, return to the eManifest and click '''Sync with CBP'''


=== Scenario C: Shipment was used on another manifest and moved without clearing the original ===
<div class="bc-subtle">
# Cancel the current manifest ('''Cancel eManifest''')
<strong>Error: Invalid Filing Status</strong><br>
# Locate and cancel the original manifest containing that shipment
You tried to amend a manifest that is already rejected.
# Detach and cancel the shipment message if needed
<br><strong>Fix:</strong> Click <strong>Cancel eManifest</strong>, wait for acceptance, fix the original error, then <strong>Sync with CBP</strong>.
# Re-submit cleanly using '''Sync with CBP'''
</div>


=== Scenario D: The shipment control number was used previously (reused number) ===
<div class="bc-subtle" style="margin-top: 15px;">
If none of the above applies, the shipment control number may have historical reuse.
<strong>Error: No Person in Charge</strong><br>
No driver is designated as the captain.
<br><strong>Fix:</strong> Edit the driver on the manifest and set "Driver's Role" to <strong>Person in Charge</strong>.
</div>


# Click '''Cancel eManifest'''
<div class="bc-subtle" style="margin-top: 15px;">
# Update the shipment control number to a new unique value
<strong>Error: Trip Number Does Not Exist</strong><br>
# Click '''Sync with CBP'''
You tried to cancel/amend a trip CBP doesn't have (often after changing the Trip #).
<br><strong>Fix:</strong> If cancelling, no action needed. If updating, use <strong>Sync with CBP</strong>.
</div>
</div>


----
<div class="bc-card" style="margin-top: 30px;">
<h3>❌ No Reason Specified</h3>
<p>CBP rejected the filing but provided no specific error text.</p>
<div class="bc-cleanlist">
* <strong>Check ETA:</strong> Ensure the date isn't too far in the future (over 30 days).
* <strong>Check Empty Trailers:</strong> If it's an empty manifest, check the trailer plate format and ACE ID.
* <strong>Advanced:</strong> Could be a Port of Arrival mismatch if the trip was previously arrived.
</div>
</div>


== Shipment Not On File ==
{{AppPromo}}


;Example
</div> [[Category:ACE Manifest Guide]]
<pre style="white-space: pre-wrap; word-wrap: break-word;">
CBP Response: Manifest Rejected, Trip [ABCD009616]
CBP Response: Shipment Not On File, Shipment [ABCD474439]
CBP Response: XXXX Bill Rejected XXXX, Shipment [ABCD474439]
CBP Response: Shipments Failed Amend [1], Shipments Sucessfully Amended [0] for Amendment Request
</pre>
 
'''What it means'''
CBP does not have the shipment you are trying to amend/cancel. This often happens when using legacy amend actions in situations where CBP cannot match what changed.
 
'''Most common causes'''
* Changing a shipment control number on an accepted manifest and attempting a legacy amend
* Adding a new shipment and attempting a legacy amend (CBP treats it as an update to a shipment that does not exist)
 
'''Fix (recommended)'''
# Click '''Cancel eManifest''' on the ACE eManifest Details page
# Wait for CBP to accept the cancel
# Click '''Sync with CBP''' to submit the current version as a clean replacement
 
{{tip|If you encountered this after using advanced shipment-only actions (Attach/Detach/Cancel Shipment Message), contact BorderConnect support if you are unsure how to proceed.}}
 
----
 
== Manifest Already On File, Do Not Resend ==
 
;Example
<pre style="white-space: pre-wrap; word-wrap: break-word;">
CBP Response: Manifest Already On File, Do Not Resend, Trip [ABCD002001]
CBP Response: Manifest Rejected, Trip [ABCD002001]
CBP Response: Shipments Rejected [1], Shipments Accepted [0] for Complete Manifest
</pre>
 
'''What it means'''
CBP already has this manifest. Re-sending the same complete manifest is rejected.
 
'''What to do'''
* If you made changes and want CBP to see them: click '''Sync with CBP''' (do not “resend” as a new filing).
* If you resent by mistake and nothing changed: no action required; CBP still has the accepted copy.
* If this was truly your first submission: the trip number may already be used in another system (another provider/portal) or was previously used in BorderConnect and not properly cleared. You may need a new trip number or to cancel the other filing first.
 
----
 
== Incorrect Harmonized # ==
 
;Example
<pre style="white-space: pre-wrap; word-wrap: break-word;">
CBP Response: Man Returned to Preliminary, Trip [ABCD18245]
CBP Response: XXXX Bill Rejected XXXX, Shipment [ABCD0012120]
CBP Response: Incorrect Harmonized #, Commodity [Frog Suits]
CBP Response: Shipments Rejected [1], Shipments Accepted [0] for Complete Manifest
</pre>
 
'''What it means'''
An ACE In-Bond shipment contains an invalid Harmonized System (HS) code.
 
'''Fix'''
# Open the shipment listed in the reject (example: ABCD0012120)
# Edit the commodity identified in the message
# Enter a valid HS code in '''6-digit format'''
# Return to the ACE eManifest Details page and click '''Sync with CBP'''
 
----
 
== Invalid Trailer ACE ID ==
 
;Example
<pre style="white-space: pre-wrap; word-wrap: break-word;">
CBP Response: Man Returned to Preliminary, Trip [ABCD0015064]
CBP Response: XXXX Bill Rejected XXXX, Shipment [ABCD0035711]
CBP Response: Invalid Trailer ACE ID, Trailer [0108]
CBP Response: Shipments Rejected [1], Shipments Accepted [0] for Complete Manifest
</pre>
 
'''What it means'''
The trailer has an ACE ID on file in BorderConnect that CBP does not recognize.
 
'''Fix'''
# Open the trailer profile for the trailer listed
# Verify the ACE ID is correct, or remove it entirely if not required/unknown
# Save the trailer profile
# Return to the manifest and click '''Sync with CBP'''
 
----
 
== Inv Travel Doc Number ==
 
;Example
<pre style="white-space: pre-wrap; word-wrap: break-word;">
CBP Response: Manifest Rejected, Trip [ABCD1933]
CBP Response: Inv Travel Doc Number
CBP Response: Shipments Rejected [1], Shipments Accepted [0] for Complete Manifest
</pre>
 
'''What it means'''
This reject refers to a FAST card number that CBP/ACE considers invalid.
 
'''Fix options'''
* If the FAST number is entered incorrectly:
# Update the driver profile with the correct FAST ID
# Click '''Sync with CBP'''
 
* If the FAST number is correct but still rejected:
The FAST credential may be inactive or not valid in ACE.
# Driver should verify/resolve FAST credential status (TTP/FAST program support)
# If time-sensitive, temporarily remove FAST from the driver profile and enter the required non-FAST driver details
# Click '''Sync with CBP'''
# Re-enter FAST once resolved (recommended)
 
----
 
== Invalid Driver/Passenger ACE ID ==
 
;Example
<pre style="white-space: pre-wrap; word-wrap: break-word;">
CBP Response: Manifest Rejected, Trip [ABCD000469]
CBP Response: Invalid Driver/Passenger ACE ID, Driver [JOHN DOGGETT]
CBP Response: Shipments Rejected [1], Shipments Accepted [0] for Complete Manifest
</pre>
 
'''What it means'''
A driver or passenger profile includes an ACE ID that CBP does not recognize.
 
'''Fix'''
# Open the driver profile listed
# Verify the ACE ID or remove it if incorrect
# Ensure the driver profile contains the required identity details for ACE filing
# Click '''Sync with CBP'''
 
----
 
== Invalid Filing Status ==
 
;Example
<pre style="white-space: pre-wrap; word-wrap: break-word;">
CBP Response: Invalid Filing Status, Trip [ABCD46121]
CBP Response: Manifest Rejected, Trip [ABCD46121]
CBP Response: Inv Amend Code for Trip, Truck [AR1234 ON]
CBP Response: Shipments Failed Amend [1], Shipments Sucessfully Amended [0] for Amendment Request
</pre>
 
'''What it means'''
You tried to amend a manifest that is still in preliminary/rejected status. CBP will not accept an amendment until the rejected copy is cleared.
 
'''Fix'''
# Click '''Cancel eManifest'''
# Wait for accepted cancellation
# Fix the original reject cause (if not already fixed)
# Click '''Sync with CBP'''
 
----
 
== No Person in Charge ==
 
;Example
<pre style="white-space: pre-wrap; word-wrap: break-word;">
CBP Response: No Person in Charge, Trip [ABCD15920]
CBP Response: Manifest Rejected, Trip [ABCD15920]
CBP Response: Shipments Failed Amend [1], Shipments Sucessfully Amended [0] for Amendment Request
</pre>
 
'''What it means'''
No driver on the manifest is assigned the role '''Person in Charge'''.
 
'''Fix'''
# On the ACE eManifest Details page, locate the driver list
# Use the driver menu (three dots) → '''Edit Driver'''
# Set '''Driver’s Role on Trip''' to '''Person in Charge''' for at least one driver
# Save, return to the eManifest, and click '''Sync with CBP'''
 
----
 
== No Reason Specified ==
 
;Example
<pre style="white-space: pre-wrap; word-wrap: break-word;">
CBP Response: Manifest Rejected, Trip [ABCD0025]
CBP Response: Shipments Rejected [1], Shipments Accepted [0] for Complete Manifest
</pre>
 
'''What it means'''
CBP rejected the filing but did not include a specific reason in the response.
 
'''Most common known causes and what to check'''
 
{| class="wikitable"
! Common cause !! How to identify it !! Fix
|-
| ETA is too far in the future || Date accidentally set weeks/months ahead || Correct ETA (generally not more than ~30 days out) → Sync with CBP
|-
| Trailer profile issue on an empty/IIT manifest || No shipments on the trip; trailer data can trigger rejects with no detail || Check trailer ACE ID / plate formatting → Save trailer → Sync with CBP
|-
| Advanced attach/port mismatch scenario || Usually after Arrived status or advanced attach/detach workflows || Update port to match actual arrival or correct in-bond port details (advanced) → Contact support recommended
|}
 
{{note|If you have confirmed the ETA is valid and trailer data looks clean, this can indicate an advanced scenario. Contact BorderConnect support for help interpreting the CBP filing context.}}
 
----
 
== Trip Number Does Not Exist ==
 
;Example
<pre style="white-space: pre-wrap; word-wrap: break-word;">
CBP Response: Trip Number does not Exist, Trip [ABCD00122012]
CBP Response: Manifest Rejected, Trip [ABCD00122012]
CBP Response: Shipments Failed Delete [1], Shipments Deleted [0] for Delete Request
</pre>
 
'''What it means'''
You attempted to cancel or amend a trip that CBP does not have on file.
 
'''Common cause'''
Changing the trip number or ETA date and then trying to send a legacy amend/cancel. CBP cannot interpret what “old” record you intended to update.
 
'''What to do'''
* If you were cancelling: no further action required (it is not on file).
* If you were updating something other than trip number/ETA: submit normally by using '''Sync with CBP'''.
* If you were changing trip number or ETA date: revert to the original values and follow the proper procedure in the [[Updating_or_Correcting_an_Accepted_ACE_Manifest_(ACE_Manifest)|changes guide]].
 
[[Category:ACE Manifest Guide]]

Latest revision as of 17:32, 24 February 2026

🔖 This article is part of the BorderConnect ACE Manifest Guide

Correcting Rejected ACE Manifests

A troubleshooting guide for resolving "Man Returned to Preliminary" statuses and specific CBP reject codes.

Type: Troubleshooting Time: Varies

Overview

When CBP rejects a manifest or shipment, the status typically reverts to a preliminary state, and a specific CBP Response message appears in the History/Status Messages section.

To fix the reject, you must identify the specific error code and apply the correct fix before re-transmitting.

Support Note: This guide covers common rejects. Complex scenarios involving unassociated shipments, port mismatches, or multi-carrier consolidations may require assistance. If unsure, contact BorderConnect Support.

Quick Troubleshooting Workflow

1 Diagnosis

  • Open the ACE eManifest Details page.
  • Scroll to History/Status Messages.
  • Locate the most recent CBP Response containing "Rejected".
  • Note if the error refers to the Trip (Manifest) or a specific Shipment.

2 Decision Guide

Reject Location Likely Fix
Trip / Manifest Fix Trip data → Sync with CBP (or Cancel eManifest first).
Shipment / Bill Fix Shipment data → Sync with CBP.
Driver / Passenger Fix Profile (ACE ID/FAST) → Sync with CBP.
Trailer Fix Profile (Plate/ACE ID) → Sync with CBP.

Common Reject Solutions

❌ Shipment Already On File

What it means: The Shipment Control Number (SCN) is already active in CBP's system, likely under a different trip or date.

Scenario A: You changed Trip Number or ETA
CBP sees the new Trip # as a "New" manifest, but the shipment is still stuck on the "Old" one.

1. Click Cancel eManifest. 2. Change the Trip # or ETA back to the original values. 3. Click Cancel eManifest again (clearing the old record). 4. Update to your desired Trip #/ETA. 5. Click Sync with CBP.

Scenario B: Unassociated Shipment
The shipment was sent independently before the manifest.

1. Click Cancel eManifest. 2. Open the shipment and click Detach Shipment Message. 3. Once processed, click Cancel Shipment Message. 4. Return to the manifest and click Sync with CBP.

❌ Shipment Not On File

What it means: You tried to Amend or Cancel a shipment that CBP does not have.

  • Common Cause: Changing an SCN on an accepted manifest and sending an "Amend", or adding a new shipment and sending an "Amend".
  • The Fix: Click Cancel eManifest (to clear the confusion), wait for acceptance, then click Sync with CBP to send a fresh copy.

❌ Manifest Already On File, Do Not Resend

What it means: CBP already has this exact manifest.

  • If you made changes: Click Sync with CBP (this sends an update, not a new creation).
  • If you made no changes: No action needed. It is already on file.
  • If this is your first attempt: The Trip Number is likely used by another provider or portal. You must cancel it there or use a new Trip Number.

❌ Data Validation Errors

Specific data fields that failed CBP checks.

Error Solution
Incorrect Harmonized # Open the shipment, edit the Commodity, and ensure the HS Code is a valid 6-digit number.
Invalid Trailer ACE ID Open the Trailer Profile. Verify the ACE ID is correct or remove it if unknown.
Inv Travel Doc Number The FAST Card number is invalid or inactive. Update the Driver Profile or temporarily remove the FAST card to file as a standard driver.
Invalid Driver/Passenger ACE ID Open the Driver/Passenger Profile. Remove or correct the ACE ID field.

❌ Operational Rejects

Error: Invalid Filing Status
You tried to amend a manifest that is already rejected.
Fix: Click Cancel eManifest, wait for acceptance, fix the original error, then Sync with CBP.

Error: No Person in Charge
No driver is designated as the captain.
Fix: Edit the driver on the manifest and set "Driver's Role" to Person in Charge.

Error: Trip Number Does Not Exist
You tried to cancel/amend a trip CBP doesn't have (often after changing the Trip #).
Fix: If cancelling, no action needed. If updating, use Sync with CBP.

❌ No Reason Specified

CBP rejected the filing but provided no specific error text.

  • Check ETA: Ensure the date isn't too far in the future (over 30 days).
  • Check Empty Trailers: If it's an empty manifest, check the trailer plate format and ACE ID.
  • Advanced: Could be a Port of Arrival mismatch if the trip was previously arrived.
📱

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_ACE_Manifests_(ACE_Manifest)&oldid=3646"