ACE Manifest Amendments Explained: How eManifest Sync Corrects Accepted Filings

Justin K

Operations & Content Manager

BorderPrint — Cross-border shipping documents & compliance supplies for highway carriers and brokers.

An ACE manifest is supposed to be a shared version of the trip: carrier, broker, driver, equipment, cargo, and arrival plan all telling the same story before a truck reaches the U.S. port. The hard part rarely happens at the first transmission. It happens later, when a trailer is swapped, a shipper adds a piece, a consignee address is corrected, or an arrival estimate moves after the manifest is already on file with CBP.

At that point, the traditional worry is not just what changed. It is whether the person at the keyboard knows the right way to tell CBP about the change. Should this be an amendment? Does it require a cancel and a fresh resubmission? Which button sends the correct message, and in what order? That guesswork is exactly what BorderConnect's eManifest Sync feature is designed to remove. You edit the manifest, click Sync with CBP, and BorderConnect works out and sends the messaging the update requires.

1) The old way: knowing which message to send

Before syncing became the default, correcting an accepted ACE manifest meant translating an operational change into a specific customs message. BorderConnect's legacy-method guide lays out the choices a user faced under Send to CBP: Amend Completed eManifest to transmit changes to an accepted manifest, Cancel Completed eManifest to withdraw one, and Send Complete eManifest to resend after a cancellation.

Some corrections could be handled with a single amendment. Others required a sequence: cancel the completed manifest, wait for the cancellation to be accepted, make the change, then send the complete manifest again and verify acceptance. Getting that sequence wrong, or picking the amend path when the change actually called for a cancel-and-resend, is where dispatch teams lost time and created mismatched records. The knowledge lived in a few experienced heads, and coverage suffered whenever those people were off shift.

CBP's ACE Truck Manifest User Guide describes the ACE Portal as a place to submit truck manifest information, check for errors, send a completed filing, and print a cover sheet. It confirms that a completed filing and a printed cover sheet are the end of a workflow, not proof that a later change has been transmitted. When a fact changes, someone still has to reopen the file and get the correct update to CBP.

2) How eManifest Sync changes the amendment

BorderConnect's eManifest Sync feature, according to its support-wiki guide, lets the software handle more of the complex messaging that some eManifests require. It applies to ACE eManifests, which are synchronized with CBP in the United States, and to ACI eManifests, which are synchronized with CBSA in Canada. It is enabled by default, and the wiki recommends keeping it on for most operations.

The initial send is straightforward: prepare the ACE eManifest and click Sync with CBP at the top of the details page. The status moves to Transmitted while synchronization runs, and the eManifest Sync section shows that a message is in progress along with an estimated time remaining. When CBP accepts the filing, the status changes to a complete-manifest-on-file state and the Sync section shows a check mark reading Synced with CBP.

The amendment flow is where the feature earns its place. Following the updating-an-accepted-ACE-manifest guide, you open the manifest from the ACE Manifest Search page, make the required edits in BorderConnect, and click Sync with CBP again. When you change a manifest that is already on file, the Sync section reappears with a note that synchronization is required and a list of the exact changes it detected. You confirm the changes, sync, and the status returns to a complete-on-file state with an accepted response recorded under ACE eManifest History.

3) Why syncing beats picking a message type

The advantage of eManifest Sync is not only fewer clicks. It is that the risky decision — which customs message a given change requires — moves from the operator to the software. That has several practical effects for a fleet.

Less specialized knowledge required per correction

Under the legacy path, a correct amendment depended on someone knowing whether the change could be amended in place or whether it needed a cancel-and-resubmit sequence. With Sync, the person making the change focuses on getting the operational fact right in the record. The software reads what changed and transmits accordingly, so a newer dispatcher can handle a routine trailer swap without memorizing message types.

The change list becomes a built-in review

Because the Sync section lists the changes it detected before you transmit, you get a confirmation step that doubles as a sanity check. If the list shows a field you did not mean to touch, you catch it before it reaches CBP rather than after. That is a safer review point than remembering to select the right option from a menu.

One consistent status vocabulary

Sync gives the whole team the same status language — transmitted, then synced and on file — instead of separate mental models for "amended," "cancelled," and "resent." When dispatch, a supervisor, and the office all read the same status, a change is less likely to be treated as done before CBP has actually accepted it.

The same habit works for ACI into Canada

Crews that run both directions do not have to learn two philosophies. The wiki notes the same feature synchronizes ACI eManifests with CBSA through a Sync with CBSA button. Edit, confirm the change list, sync — the muscle memory carries across the border.

4) What changes most often after dispatch

Sync removes the message-selection problem, but you still owe CBP an accurate record. Classifying the change before you edit keeps a casual note like "updated truck" from hiding several separate changes.

Equipment and conveyance changes

Trailer swaps happen when a unit has a mechanical issue, a yard assignment changes, or a load is consolidated. In BorderConnect these are edits you make directly — remove the current trailer and use Quick Assign to add the new one, then sync. Capture the time of the swap and who approved it, and record the exact old and new identifiers rather than just "equipment changed," because a driver can still be asked about a mismatch at the booth.

Cargo and package changes

Piece counts, weights, packaging, marks and numbers, commodity descriptions, and bill-of-lading references can change during loading. Tie each update to a specific source document and timestamp. Commodity descriptions deserve a second look: a change that introduces regulated or otherwise sensitive goods may need broker guidance before you sync, not after.

Party, destination, and routing changes

Consignee names, delivery addresses, notify parties, port codes, and intended destinations can shift after booking. In BorderConnect the port of arrival and ETA are simple Edit-and-Save fields; the value is confirming the real destination first so the synced record matches the freight. Call a destination change out as its own line item rather than burying it in a general "manifest update."

Timing and reference changes

Estimated arrival time, trip numbers, purchase-order references, and internal identifiers may change without changing the cargo. They still help the broker's search and the driver's ability to connect the paper packet to the electronic record, so keep the original reference in your log and show the replacement clearly.

5) A clean sync-based amendment workflow

This sequence keeps the discipline that Sync does not do for you — verifying the fact and refreshing the driver — while letting the software carry the customs messaging.

Step 1 — Freeze the current version

Before editing, save the current manifest reference, cover sheet, and relevant documents in the trip record and label them as the pre-change version with a timestamp. This gives you a stable "before" picture if a question comes up later.

Step 2 — Verify the physical fact

Ask the person closest to the change to confirm it: the trailer number and plate from the yard, the revised packing list from the warehouse, the corrected address in writing. Do not copy a value from an old chat when the load has already moved.

Step 3 — Edit the record in BorderConnect

Open the manifest from the ACE Manifest Search page, make the edits, and save. For trucks, trailers, and drivers, remove the old entry and Quick Assign the new one; for port and ETA use Edit and Save; for seals, open the truck or trailer and adjust the seal list.

Step 4 — Review the Sync change list, then sync

Read the list of detected changes in the eManifest Sync section. Confirm it matches what you intended, then click Sync with CBP. The status moves to Transmitted while the update sends.

Step 5 — Confirm acceptance

Wait for the status to return to a complete-manifest-on-file state and check that an accepted response appears under ACE eManifest History. "Transmitted" is in progress; on-file with an accepted response is closure. If a rejection or error appears, correct the record and sync again.

Step 6 — Reconcile the trip packet

Retire superseded driver-facing pages or mark them void, print the updated lead sheet or cover page when your process calls for one, and check it against the tractor, trailer, seal, references, destination, and driver instructions. Update any digital copy at the same time.

Step 7 — Close the loop with the driver

Tell the driver what changed and where the current page is. If the load is near the port, say whether to continue, hold, or call a designated office number. Keep it operational; do not ask the driver to interpret customs policy from the cab.

6) The dispatch, broker, and driver handoff

Sync simplifies the transmission, but the roles around it still matter.

Dispatch owns the change signal and the edit

Dispatch usually learns first that the trip changed. With Sync enabled, dispatch can often capture the fact, edit the record, and sync directly — while still recording the manifest reference, identifiers, changed field, old and new values, reason, effective time, and truck status for the log.

The broker or authorized filer owns the filing decision

Where a broker or other authorized party files, dispatch should send a concise change package and confirm who transmits. Even when your team syncs its own eManifests, escalate anything that touches release, in-bond status, or a special program to the responsible customs professional.

The driver owns the physical truth at the gate

The driver confirms what is physically present — tractor, trailer, seal, documents, routing — and should carry one current packet that matches the accepted record, not diagnose a filing question in a primary lane.

One person owns closure

Assign a named closer per amendment: the record was edited, the sync accepted, the driver packet refreshed, and any open question handed off. Without a closer, a change can sit half-finished while the truck moves on.

7) Keeping an audit trail alongside Sync

Sync records its own history in BorderConnect, but a short operational log still helps your team answer five questions: what changed, who noticed it, who edited and synced it, what CBP returned, and which version went with the truck.

• Trip identity: ACE reference, internal load number, tractor, trailer, and driver.
• Change detail: field, old value, new value, reason, source, and timestamp.
• Sync record: who edited, time synced, the change list confirmed, and the accepted-or-rejected response.
• Packet control: version number, printed time, driver acknowledgment, and closure time.

Use version names that sort naturally, such as "ACE-48271-v01-before-swap," "ACE-48271-v02-trailer-update," and "ACE-48271-v03-final," and never overwrite the only copy of the original. For recurring errors, review the log weekly and look for patterns — trailer swaps after cutoff, descriptions corrected repeatedly, packets printed before the accepted response.

8) What the current corridor means for data discipline

The Windsor–Detroit corridor is a reminder that physical infrastructure and electronic filing are connected. The Government of Canada's Gordie Howe International Bridge page says the crossing opened on July 27, 2026 and is intended to transform trade movement through the corridor. More routing options do not remove the need for accurate trip data; they make it more important that the synced record shows the selected port and current conveyance.

There is also a U.S.-side process signal. In its August 26, 2026 bulletin, CBP announced the termination of the “Flying Trucks” process, with a transition period ending November 24, 2026, and reiterated that electronic manifest transmissions must reflect the actual transportation mode. The operational takeaway is the same discipline Sync supports: when the route or mode changes, edit the record to match reality and sync, and let the responsible filer confirm the correct treatment.

9) A driver-facing lead sheet at the border

ACE Manifest Lead Sheets

Once a change is synced and the manifest is back on file, a consistent driver-facing page makes the final reconciliation easier so the truck carries one current reference at the border.

• Physical lead sheets for fleets that keep a printed trip packet in each unit
• Digital option for teams that print after the sync is accepted

See the ACE manifest lead-sheet collection, or compare the digital download when on-demand printing fits the workflow.

10) A copy-and-use amendment checklist

Save this in the dispatch SOP. It keeps the discipline Sync does not automate — verifying the fact and refreshing the driver — while letting the software carry the customs messaging.

1. Identify: ACE reference, internal load number, truck, trailer, driver, and intended port.
2. Verify: Confirm the changed fact with the yard, shipper, consignee, driver, or source document.
3. Edit: Make the change in BorderConnect (Edit/Save for port and ETA; Remove and Quick Assign for truck, trailer, driver).
4. Review: Read the eManifest Sync change list and confirm it matches your intent.
5. Sync: Click Sync with CBP and let BorderConnect transmit the required update.
6. Confirm: Wait for the complete-manifest-on-file status and the accepted response in ACE eManifest History.
7. Reconcile: Check the accepted record against the manifest, documents, equipment, and route.
8. Refresh: Reprint the driver packet, retire superseded pages, and notify the driver.
9. Close: Record the final owner and closure time; flag recurring causes for review.

Read the final packet as if you were a driver seeing it for the first time. Can you tell which page is current? Do the tractor and trailer match what is outside the window? If not, the amendment is not operationally closed yet — even after a clean sync.

Related reading:

• ACE eManifest timing and filing errors
• ACI eManifest rejected-message troubleshooting

11) FAQ