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

E-Manifest Sync Feature (ACE and ACI eManifest): Difference between revisions

From BorderConnect Wiki
← Older editNewer edit →
No edit summary
No edit summary
Line 5: Line 5:
= eManifest Sync Feature (ACE & ACI) =
= eManifest Sync Feature (ACE & ACI) =


The '''eManifest Sync Feature''' lets you update an '''ACE''' or '''ACI''' eManifest using a single action — '''Sync with CBP''' or '''Sync with CBSA'''. Instead of choosing specific “Send to CBP/CBSA” message types manually, you can make changes directly on the manifest and then sync to have BorderConnect transmit the appropriate update message(s) to customs automatically.
The '''eManifest Sync Feature''' lets you submit and update '''ACE''' and '''ACI''' eManifests using a single action — '''Sync with CBP''' or '''Sync with CBSA'''.
 
Instead of manually selecting specific “Send to CBP/CBSA” message types when changes are needed, you can:
# Edit the manifest normally
# Click Sync
# BorderConnect transmits the appropriate update message(s) to customs automatically


This guide assumes you have an active BorderConnect subscription. If you are not currently set up, please [https://borderconnect.com/contact-us.htm contact BorderConnect].
This guide assumes you have an active BorderConnect subscription. If you are not currently set up, please [https://borderconnect.com/contact-us.htm contact BorderConnect].


== What eManifest Sync does ==
== What Sync does ==
When you click '''Sync with CBP''' or '''Sync with CBSA''':
When you click '''Sync with CBP''' (ACE) or '''Sync with CBSA''' (ACI), BorderConnect:
* BorderConnect transmits the manifest to customs (or transmits the required update if the manifest is already on file).
* Transmits a new manifest to customs, '''or'''
* If changes were made, the Sync panel summarizes what changed.
* Sends the correct update/correction messages if the manifest is already on file
* You can track what was sent using the '''Trip Action Plan / Changelog History''' on the eManifest Details page.
* Shows a summary of detected changes (when applicable)
* Records all messaging activity in the '''Trip Action Plan / Changelog History'''


== When to use Sync ==
== When you should Sync ==
Use eManifest Sync when:
Sync is used when:
* You are submitting a new ACE/ACI eManifest to customs.
* You are sending a brand-new ACE/ACI eManifest to customs
* Your manifest is already on file and you need to update:
* Your manifest is already on file and you changed something, such as:
** Driver, truck, or trailer details
** Driver, truck, or trailer details
** Trip number / CRN
** Trip number / CRN
** Port details
** Port selection
** Shipments added/removed or shipment edits
** Shipments added/removed, or shipment detail edits
* You see a “Sync required” message on the eManifest Details page or on the eManifest listing page.
* You see a “Sync required” prompt on the eManifest Details page or on the listing page


== Syncing a new eManifest ==
== Syncing a new eManifest ==
Follow these steps to transmit a new ACE or ACI eManifest:
# Create the ACE or ACI eManifest and complete the required details.
 
# Create your ACE or ACI eManifest and complete the required details.
# On the eManifest Details page, click:
# On the eManifest Details page, click:
#* '''Sync with CBP''' (ACE), or
#* '''Sync with CBP''' (ACE), or
#* '''Sync with CBSA''' (ACI)
#* '''Sync with CBSA''' (ACI)
# Once transmitted, the manifest status typically changes to '''Transmitted''' (two yellow bars).
# While syncing, the page will display a status panel showing progress.
# Wait for the sync to finish. When accepted, the manifest will typically move to '''On File''' (three blue bars).
# Once accepted, the manifest typically transitions to an “On File” status.


<center>
<div style="text-align:center; margin:16px 0;">
[[File:Emanifest-sync-required.png|800px]]
  <img src="{{filepath:Emanifest-sync-required.png}}" alt="Sync with CBP/CBSA is required panel" style="max-width:900px; width:100%; height:auto;">
</center>
</div>


<center>
<div style="text-align:center; margin:16px 0;">
[[File:Emanifest-sync-in-progress.png|900px]]
  <img src="{{filepath:Emanifest-sync-in-progress.png}}" alt="Sync in progress panel" style="max-width:900px; width:100%; height:auto;">
</center>
</div>


<center>
<div style="text-align:center; margin:16px 0;">
[[File:Synced-with-cbp.png|900px]]
  <img src="{{filepath:Synced-with-cbp.png}}" alt="Synced confirmation panel" style="max-width:900px; width:100%; height:auto;">
</center>
</div>


== Using Sync to make changes to a manifest already on file ==
== Syncing after you make changes ==
If an eManifest is already on file and you make changes, BorderConnect will prompt you to sync again.
If an eManifest is already on file and you edit it, BorderConnect will prompt you to sync again.


# Open the eManifest Details page.
# Open the eManifest Details page.
# Make the required updates (truck/driver/trailer, trip number, shipment changes, etc.).
# Make the required updates.
# At the top of the page, review the '''Changes made since last sync''' summary.
# Review the “Changes made since last sync” summary near the top.
# Click '''Sync with CBP''' or '''Sync with CBSA''' to transmit the update.
# Click '''Sync with CBP''' or '''Sync with CBSA''' to transmit the updates.
# Watch the Sync panel for progress and confirmation.


<center>
<div style="text-align:center; margin:16px 0;">
[[File:Emanifest-sync-corrections.png|900px]]
  <img src="{{filepath:Emanifest-sync-corrections.png}}" alt="Sync required after edits summary" style="max-width:900px; width:100%; height:auto;">
</center>
</div>


== Identifying manifests that require sync ==
== Identifying manifests that require Sync ==
You don’t need to open each manifest individually to find out whether action is required.
You don’t need to open each manifest individually.


On the '''eManifest Listing''' page:
On the '''eManifest Listing''' page:
* Manifests requiring sync are clearly flagged.
* Manifests requiring sync are clearly flagged
* This helps dispatchers quickly identify which trips still need to be updated before arrival.
* Dispatchers can quickly identify which trips still need to be updated


<center>
<div style="text-align:center; margin:16px 0;">
[[File:Emanifest-sync-is-required-listing.png|900px]]
  <img src="{{filepath:Emanifest-sync-is-required-listing.png}}" alt="Manifest listing showing sync required indicator" style="max-width:900px; width:100%; height:auto;">
</center>
</div>


== Viewing transmitted messages (Trip Action Plan / Changelog History) ==
== Viewing what was transmitted (Trip Action Plan / Changelog History) ==
For full transparency, BorderConnect records all messaging activity related to each manifest.
BorderConnect records the messaging activity for each manifest.


To view message details:
To view the details:
# Open the '''eManifest Details''' page.
# Open the '''eManifest Details''' page
# Scroll to the bottom.
# Scroll to the bottom
# Review the '''Trip Action Plan / Changelog History''' to see:
# Review the '''Trip Action Plan / Changelog History'''
#* What messages were transmitted
#* When they were sent
#* Any responses or validation results


<center>
<div style="text-align:center; margin:16px 0;">
[[File:Ace-trip-action-plan.png|900px]]
  <img src="{{filepath:Ace-trip-action-plan.png}}" alt="Trip Action Plan / Changelog History section" style="max-width:900px; width:100%; height:auto;">
</center>
</div>


== Troubleshooting: “Error creating thumbnail” ==
== Why we avoid thumbnails on this page ==
If you see '''Error creating thumbnail''' on this page, it means MediaWiki is trying to generate a thumb for at least one image.
If your wiki is showing '''Error creating thumbnail''', it usually means the thumbnail generator is failing (server/image processing/permissions/job queue).


This page is written to avoid thumbnails entirely. If the error still appears:
To keep this page readable even when thumbnails are broken, this article:
* Confirm there are '''no''' image tags using: <code>thumb</code>, <code>frame</code>, <code>right</code>, <code>left</code>, or <code>upright</code>.
* Does '''not''' use <code>thumb</code>
* Ensure the file exists and the filename is spelled exactly (including capitalization).
* Does '''not''' use <code>|800px</code> on <code>[[File:...]]</code> tags
* If your wiki’s thumb generator is disabled/broken, keep images inserted exactly like this page does:
* Displays images using the original file URL via <code>{{filepath:...}}</code> to avoid thumbnail rendering entirely
: <code>[[File:Example.png|900px]]</code>


[[Category:BorderConnect Software User Guide]]
[[Category:BorderConnect Software User Guide]]

Revision as of 16:43, 23 January 2026

🔖 This article is part of the BorderConnect Software User Guide
Load video
YouTube
Introduction video to how eManifest Sync works in BorderConnect.

eManifest Sync Feature (ACE & ACI)

The eManifest Sync Feature lets you submit and update ACE and ACI eManifests using a single action — Sync with CBP or Sync with CBSA.

Instead of manually selecting specific “Send to CBP/CBSA” message types when changes are needed, you can:

  1. Edit the manifest normally
  2. Click Sync
  3. BorderConnect transmits the appropriate update message(s) to customs automatically

This guide assumes you have an active BorderConnect subscription. If you are not currently set up, please contact BorderConnect.

What Sync does

When you click Sync with CBP (ACE) or Sync with CBSA (ACI), BorderConnect:

  • Transmits a new manifest to customs, or
  • Sends the correct update/correction messages if the manifest is already on file
  • Shows a summary of detected changes (when applicable)
  • Records all messaging activity in the Trip Action Plan / Changelog History

When you should Sync

Sync is used when:

  • You are sending a brand-new ACE/ACI eManifest to customs
  • Your manifest is already on file and you changed something, such as:
    • Driver, truck, or trailer details
    • Trip number / CRN
    • Port selection
    • Shipments added/removed, or shipment detail edits
  • You see a “Sync required” prompt on the eManifest Details page or on the listing page

Syncing a new eManifest

  1. Create the ACE or ACI eManifest and complete the required details.
  2. On the eManifest Details page, click:
    • Sync with CBP (ACE), or
    • Sync with CBSA (ACI)
  3. While syncing, the page will display a status panel showing progress.
  4. Once accepted, the manifest typically transitions to an “On File” status.
 <img src="https://wiki.borderconnect.com/images/e/ee/Emanifest-sync-required.png" alt="Sync with CBP/CBSA is required panel" style="max-width:900px; width:100%; height:auto;">

 <img src="https://wiki.borderconnect.com/images/9/9e/Emanifest-sync-in-progress.png" alt="Sync in progress panel" style="max-width:900px; width:100%; height:auto;">

 <img src="https://wiki.borderconnect.com/images/5/5c/Synced-with-cbp.png" alt="Synced confirmation panel" style="max-width:900px; width:100%; height:auto;">

Syncing after you make changes

If an eManifest is already on file and you edit it, BorderConnect will prompt you to sync again.

  1. Open the eManifest Details page.
  2. Make the required updates.
  3. Review the “Changes made since last sync” summary near the top.
  4. Click Sync with CBP or Sync with CBSA to transmit the updates.
 <img src="https://wiki.borderconnect.com/images/d/d0/Emanifest-sync-corrections.png" alt="Sync required after edits summary" style="max-width:900px; width:100%; height:auto;">

Identifying manifests that require Sync

You don’t need to open each manifest individually.

On the eManifest Listing page:

  • Manifests requiring sync are clearly flagged
  • Dispatchers can quickly identify which trips still need to be updated
 <img src="https://wiki.borderconnect.com/images/c/cb/Emanifest-sync-is-required-listing.png" alt="Manifest listing showing sync required indicator" style="max-width:900px; width:100%; height:auto;">

Viewing what was transmitted (Trip Action Plan / Changelog History)

BorderConnect records the messaging activity for each manifest.

To view the details:

  1. Open the eManifest Details page
  2. Scroll to the bottom
  3. Review the Trip Action Plan / Changelog History
 <img src="https://wiki.borderconnect.com/images/d/d5/Ace-trip-action-plan.png" alt="Trip Action Plan / Changelog History section" style="max-width:900px; width:100%; height:auto;">

Why we avoid thumbnails on this page

If your wiki is showing Error creating thumbnail, it usually means the thumbnail generator is failing (server/image processing/permissions/job queue).

To keep this page readable even when thumbnails are broken, this article:

  • Does not use thumb
  • Does not use |800px on File:... tags
  • Displays images using the original file URL via to avoid thumbnail rendering entirely
Retrieved from "https://wiki.borderconnect.com/index.php?title=E-Manifest_Sync_Feature_(ACE_and_ACI_eManifest)&oldid=2387"