BorderConnect Wiki

Correcting Rejected ACE Manifests (ACE Manifest)

🔖 This article is part of the BorderConnect ACE Manifest Guide

Load video
YouTube
How to Make Changes and Cancel an ACE Manifest in BorderConnect.

Fixing ACE eManifest Rejects in BorderConnect (CBP)

This guide explains how to troubleshoot and correct an ACE eManifest that has been rejected by CBP in BorderConnect ACE Manifest software.

When CBP rejects a manifest or shipment, you will see:

  • The manifest status move back (often to a preliminary/returned state), and
  • A CBP Response message in History/Status Messages explaining the reason.
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 Support.

Before you start: the fast troubleshooting workflow

Use this quick sequence before diving into a specific reject:

  1. Open the ACE eManifest Details page
  2. In History/Status Messages, locate the most recent CBP Response that contains the word Rejected
  3. Note the Trip Number and (if applicable) the Shipment Control Number
  4. Make the correction in the appropriate place:
    • Trip-level issue → Trip/Manifest page
    • Shipment issue → Shipment Details page
    • Driver/Trailer issue → Driver/Trailer profile
  5. 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)

What does the reject mention? Most likely fix location Most likely action
Trip / Manifest ACE eManifest Details (trip) Sync with CBP (or Cancel eManifest → Sync)
Shipment / Bill ACE Shipment Details Fix shipment data → Sync with CBP
Driver / Passenger Driver profile Fix/remove invalid ACE ID or FAST info → Sync with CBP
Trailer Trailer profile Fix/remove invalid ACE ID / plate format → Sync with CBP
No reason specified Check ETA / trailer (if empty) / advanced attach cases Fix likely cause → Sync with CBP

Common reject messages and how to fix them

Shipment Already On File

Example
CBP Response: Man Returned to Preliminary, Trip [ABCD028321]
CBP Response: Shipment Already on File, Shipment [ABCD0092355]
CBP Response: XXXX Bill Rejected XXXX, Shipment [ABCD0092355]
CBP Response: Shipments Rejected [1], Shipments Accepted [0] for Complete Manifest

What it means 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.

What to do Start by identifying why CBP already has the shipment:

Scenario A: You changed the trip number or ETA date and resent

This is common. CBP treats it as a different manifest, but the shipment still exists under the original trip/date context.

  1. Click Cancel eManifest on the ACE eManifest Details page
  2. Wait for CBP to accept the cancellation
  3. Change the trip number or ETA date back to the original values
  4. Click Cancel eManifest again to clear the original version in CBP
  5. Once accepted, set the trip number/ETA to the correct (desired) values again
  6. Click Sync with CBP

Scenario B: Shipment was previously sent as an unassociated shipment

CBP already has the shipment, then the complete manifest attempt fails.

  1. From the ACE eManifest Details page, click Cancel eManifest
  2. Open the shipment and use Detach Shipment Message (Shipment Only Send to CBP)
  3. After detach is processed, use Cancel Shipment Message (Send to CBP)
  4. 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

  1. Cancel the current manifest (Cancel eManifest)
  2. Locate and cancel the original manifest containing that shipment
  3. Detach and cancel the shipment message if needed
  4. Re-submit cleanly using Sync with CBP

Scenario D: The shipment control number was used previously (reused number)

If none of the above applies, the shipment control number may have historical reuse.

  1. Click Cancel eManifest
  2. Update the shipment control number to a new unique value
  3. Click Sync with CBP

Shipment Not On File

Example
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

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)

  1. Click Cancel eManifest on the ACE eManifest Details page
  2. Wait for CBP to accept the cancel
  3. Click Sync with CBP to submit the current version as a clean replacement

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

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

What it means An ACE In-Bond shipment contains an invalid Harmonized System (HS) code.

Fix

  1. Open the shipment listed in the reject (example: ABCD0012120)
  2. Edit the commodity identified in the message
  3. Enter a valid HS code in 6-digit format
  4. Return to the ACE eManifest Details page and click Sync with CBP

Invalid Trailer ACE ID

Example
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

What it means The trailer has an ACE ID on file in BorderConnect that CBP does not recognize.

Fix

  1. Open the trailer profile for the trailer listed
  2. Verify the ACE ID is correct, or remove it entirely if not required/unknown
  3. Save the trailer profile
  4. Return to the manifest and click Sync with CBP

Inv Travel Doc Number

Example
CBP Response: Manifest Rejected, Trip [ABCD1933]
CBP Response: Inv Travel Doc Number
CBP Response: Shipments Rejected [1], Shipments Accepted [0] for Complete Manifest

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:
  1. Update the driver profile with the correct FAST ID
  2. Click Sync with CBP
  • If the FAST number is correct but still rejected:

The FAST credential may be inactive or not valid in ACE.

  1. Driver should verify/resolve FAST credential status (TTP/FAST program support)
  2. If time-sensitive, temporarily remove FAST from the driver profile and enter the required non-FAST driver details
  3. Click Sync with CBP
  4. Re-enter FAST once resolved (recommended)

Invalid Driver/Passenger ACE ID

Example
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

What it means A driver or passenger profile includes an ACE ID that CBP does not recognize.

Fix

  1. Open the driver profile listed
  2. Verify the ACE ID or remove it if incorrect
  3. Ensure the driver profile contains the required identity details for ACE filing
  4. Click Sync with CBP

Invalid Filing Status

Example
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

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

  1. Click Cancel eManifest
  2. Wait for accepted cancellation
  3. Fix the original reject cause (if not already fixed)
  4. Click Sync with CBP

No Person in Charge

Example
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

What it means No driver on the manifest is assigned the role Person in Charge.

Fix

  1. On the ACE eManifest Details page, locate the driver list
  2. Use the driver menu (three dots) → Edit Driver
  3. Set Driver’s Role on Trip to Person in Charge for at least one driver
  4. Save, return to the eManifest, and click Sync with CBP

No Reason Specified

Example
CBP Response: Manifest Rejected, Trip [ABCD0025]
CBP Response: Shipments Rejected [1], Shipments Accepted [0] for Complete Manifest

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

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

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

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 changes guide.
Retrieved from "https://wiki.borderconnect.com/index.php?title=Correcting_Rejected_ACE_Manifests_(ACE_Manifest)&oldid=2243"