Correcting Rejected ACE Manifests (ACE Manifest)

This article is part of the BorderConnect ACE Manifest Guide

This guide explains how to correct an ACE eManifest that received a reject response from CBP in BorderConnect ACE Manifest software.

How to make changes and cancel an ACE Manifest in BorderConnect

Video walkthrough: How to make changes and cancel an ACE Manifest in BorderConnect

When an ACE Manifest is rejected, review the History/Status Messages on the ACE eManifest Details page. The CBP response normally identifies whether the reject is for the trip, a shipment, a driver or passenger, a trailer, or a specific data field. Fix the issue before selecting Sync with CBP again.

This guide covers common rejects. If multiple rejects, unassociated shipments, port mismatches, or other advanced events are involved, contact BorderConnect Support.

Quick Workflow

Open the ACE eManifest Details page.
Review the most recent CBP Response in History/Status Messages.
Identify whether the response points to the trip, a shipment, a driver/passenger, a trailer, or a commodity.
Correct the data in BorderConnect.
Use Sync with CBP unless the specific reject requires a cancellation first.

Do not keep resending the same rejected manifest without making the required correction. CBP may keep returning the manifest to preliminary status until the underlying issue is fixed.

Shipment Already On File

Example response:

CBP Response: Shipment Already on File, Shipment [ABCD0092355]

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

This reject means a shipment on the manifest is already active in CBP's system. The response identifies the Shipment Control Number causing the problem.

Common causes and fixes:

Trip number or ETA was changed after the original filing: CBP may treat the new trip number or date as a new manifest while the shipment is still attached to the original manifest. Cancel the current manifest, wait for the accepted cancellation, change the trip number or ETA back to the original value, cancel the original filing, then change the manifest to the desired value and select Sync with CBP.

The shipment was sent as an unassociated shipment: Cancel the rejected manifest. Open the shipment, send a Detach Shipment Message if needed, then send a Cancel Shipment Message for the unassociated shipment. After those messages are accepted, return to the manifest and select Sync with CBP.

The shipment was moved from another manifest: Cancel both the current manifest and the original manifest if the shipment was already filed there. Detach and cancel the shipment message if required, then resubmit from the correct manifest.

The shipment control number was used previously: Cancel the manifest, update the shipment control number, and select Sync with CBP.

Shipment Not On File

Example response:

CBP Response: Shipment Not On File, Shipment [ABCD474439]

CBP Response: Shipments Failed Amend [1], Shipments Successfully Amended [0] for Amendment Request

This reject means CBP does not have the shipment that BorderConnect is trying to amend or cancel.

Common causes include changing the shipment control number on a manifest that was already accepted, or adding a new shipment and attempting to send the change as an amendment through legacy send options. CBP interprets that as an attempt to amend a shipment it does not have.

To resolve it, cancel the manifest from the ACE eManifest Details page, wait for the cancellation to be accepted, then select Sync with CBP so the current version is filed cleanly.

If the reject happened while using advanced Shipment Only options, contact BorderConnect Support before continuing.

Manifest Already On File, Do Not Resend

Example response:

CBP Response: Manifest Already On File, Do Not Resend, Trip [ABCD002001]

CBP Response: Manifest Rejected, Trip [ABCD002001]

This reject means CBP already has the manifest on file.

You made changes and intended to update CBP: Use Sync with CBP from the ACE eManifest Details page. Resending an already accepted manifest as if it were new can cause this reject.

You resent the manifest by mistake: No correction may be needed. CBP still has the original accepted manifest.

This was the first attempted send: The trip number may already exist in CBP, possibly from the ACE Portal, another service provider, or an earlier BorderConnect filing. Use the existing manifest, cancel it in the other system if appropriate, or assign a new trip number.

Incorrect Harmonized Number

Example response:

CBP Response: Incorrect Harmonized #, Commodity [Frog Suits]

This reject occurs when an ACE In-Bond shipment contains an invalid Harmonized Code. The response identifies the shipment and commodity.

Edit the commodity on the shipment, enter a valid six-digit HS code, return to the manifest, and select Sync with CBP.

Invalid Trailer ACE ID

Example response:

CBP Response: Invalid Trailer ACE ID, Trailer [0108]

This reject means the trailer profile contains an ACE ID that CBP does not recognize.

Edit the trailer profile. Correct the ACE ID if you know the valid value, or remove the ACE ID from the profile. Return to the manifest and select Sync with CBP.

Invalid Travel Document Number

Example response:

CBP Response: Inv Travel Doc Number

This reject usually refers to a FAST card number that is invalid or inactive in ACE.

First verify the driver's FAST ID in the driver profile. If the number was entered incorrectly, update the profile and select Sync with CBP.

If the FAST number is correct, the card may not be active or may not be valid in ACE. The driver may need to review the card in the Trusted Traveler Programs account system or contact CBP support. If the trip must be filed before the FAST issue is resolved, it may be necessary to remove the FAST card from the driver profile temporarily and enter the full non-FAST driver information, including travel document and commercial driver's license information.

When the FAST issue is resolved, add the FAST card back to the driver profile.

Invalid Driver/Passenger ACE ID

Example response:

CBP Response: Invalid Driver/Passenger ACE ID, Driver [JOHN DOGGETT]

This reject means the driver or passenger profile contains an ACE ID that CBP does not recognize.

Edit the driver or passenger profile. Correct the ACE ID if you know the valid value, or remove the ACE ID and ensure the profile has the required non-ACE-ID information for ACE eManifest use. Return to the manifest and select Sync with CBP.

Invalid Filing Status

Example response:

CBP Response: Invalid Filing Status, Trip [ABCD46121]

CBP Response: Inv Amend Code for Trip, Truck [AR1234 ON]

This reject usually occurs when attempting to amend a manifest that is in preliminary status because it was previously rejected.

Cancel the manifest from the ACE eManifest Details page, wait for the cancellation to be accepted, fix the original reject reason, then select Sync with CBP.

No Person in Charge

Example response:

CBP Response: No Person in Charge, Trip [ABCD15920]

This reject means none of the drivers on the manifest are designated as the person in charge.

On the ACE Manifest, edit the driver and update Driver's Role on Trip to Person in Charge. Save the change, return to the manifest, and select Sync with CBP.

No Reason Specified

Example response:

CBP Response: Manifest Rejected, Trip [ABCD0025]

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

This section applies only when the response does not include any other reject reason.

Known causes include:

ETA is too far in the future: If the ETA date is more than 30 days in the future, update the ETA to the correct date and select Sync with CBP.

Trailer issue on an empty or IIT manifest: If there are no shipments on the manifest, CBP may reject the trailer without returning the detailed trailer reason. Check the trailer profile for an invalid ACE ID, spaces or dashes in the license plate, or other invalid values. Correct the trailer and select Sync with CBP.

Port mismatch on advanced attach or in-bond actions: If a manifest was arrived at a different port than the port listed on the manifest, an advanced attach shipment message or in-bond linking action may fail. Amend the manifest port or the in-bond port, depending on which value is incorrect, before trying the advanced action again. These are advanced cases, so contact BorderConnect Support if you are unsure.

Trip Number Does Not Exist

Example response:

CBP Response: Trip Number does not Exist, Trip [ABCD00122012]

CBP Response: Shipments Failed Delete [1], Shipments Deleted [0] for Delete Request

This reject means BorderConnect sent a cancel or amend request for a trip that CBP does not have on file.

You were cancelling the manifest: No further correction may be needed. The response confirms that the trip is not on file with CBP.

You were changing something other than the trip number or ETA: Use Sync with CBP to send the current manifest state instead of relying on the rejected amend/delete request.

You were changing the trip number or ETA: Set the trip number or ETA back to the original value and follow the procedure in Updating or Correcting an Accepted ACE Manifest.