E-Manifest Sync Feature (ACE and ACI eManifest): Difference between revisions
No edit summary |
No edit summary Β |
||
| (4 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
{{#seo: | |||
|title=eManifest Sync (ACE & ACI) {{!}} BorderConnect Support Wiki | |||
|title_mode=replace | |||
|keywords=eManifest Sync, sync with CBP, sync with CBSA, automated manifest updates, BorderConnect automation, ACE manifest sync, ACI manifest sync | |||
|description=Learn how to use the eManifest Sync feature in BorderConnect to automatically handle all manifest submissions, updates, and amendments with a single click. | |||
}} | |||
{{note|This article is part of the [[BorderConnect_Software_User_Guide|BorderConnect Software User Guide]]|info}} | {{note|This article is part of the [[BorderConnect_Software_User_Guide|BorderConnect Software User Guide]]|info}} | ||
<div class="bc-wrap"> | |||
<div class="bc-article-hero"> | |||
<h1>eManifest Sync (ACE & ACI)</h1> | |||
<p>The intelligent transmission tool that handles all manifest submissions, updates, and amendments with a single click.</p> | |||
<div class="bc-article-meta"> | |||
<span class="bc-article-pill"><i class="fas fa-sync-alt"></i> Feature: Automation</span> | |||
<span class="bc-article-pill"><i class="far fa-clock"></i> Time: 5 Minutes</span> | |||
</div> | |||
</div> | |||
= | <div class="bc-card"> | ||
<div class="bc-float-video"> | |||
Β <div class="bc-video-trigger" data-video-id="MQr_lDYSf6U"> | |||
Β Β <div class="bc-play-icon"><i class="fas fa-play-circle"></i></div> | |||
Β </div> | |||
</div> | |||
<h2 style="margin-top: 0;">Overview</h2> | |||
<p>The <strong>eManifest Sync Feature</strong> allows users to submit and update both <strong>ACE (CBP)</strong> and <strong>ACI (CBSA)</strong> eManifests using a single action.</p> | |||
<p>Instead of manually selecting specific transmission message types (like "Amend", "Change", or "Add"), users simply click <strong>Sync with CBP</strong> or <strong>Sync with CBSA</strong>. BorderConnect intelligently calculates the difference between your last submission and your current data, then automatically sends the correct message(s) to customs.</p> | |||
Sync | <div class="bc-did-you-know" style="margin-top: 20px;"> | ||
<strong>Why Use Sync?</strong> It removes the guesswork. Whether it's a new manifest, a driver change, or a shipment amendment, Sync handles the required logic for you. | |||
</div> | |||
<div style="clear: both;"></div> | |||
</div> | |||
== What | <div class="bc-card" style="margin-top: 30px;"> | ||
<h3>π€ What Sync Automatically Handles</h3> | |||
<table class="wikitable" style="width:100%; margin-bottom:0;"> | |||
<tr> | |||
<th style="width: 40%;">Scenario</th> | |||
<th>What BorderConnect Sends</th> | |||
</tr> | |||
<tr> | |||
<td><strong>Brand New eManifest</strong></td> | |||
<td>Initial manifest submission (Create Trip + Create Shipments).</td> | |||
</tr> | |||
<tr> | |||
<td><strong>Trip Details Edited</strong></td> | |||
<td>Correction/Update message for the trip data.</td> | |||
</tr> | |||
<tr> | |||
<td><strong>Shipments Added/Removed</strong></td> | |||
<td>Amendment transmission to add or delete shipment data.</td> | |||
</tr> | |||
<tr> | |||
<td><strong>Multiple Changes</strong></td> | |||
<td>All required updates bundled into one efficient transmission.</td> | |||
</tr> | |||
</table> | |||
</div> | |||
<h2 style="margin-top: 40px; border-bottom: 2px solid #eee; padding-bottom: 10px;">How to Use Sync</h2> | |||
<div class="bc-2col"> | |||
<div class="bc-card"> | |||
<h3>Syncing a New Manifest</h3> | |||
<p>When you first create a manifest, it is in "Draft" status. Syncing submits it to customs.</p> | |||
<div class="bc-cleanlist"> | |||
1. Complete your Trip and Shipment details. | |||
2. Click <strong>Sync with CBP/CBSA</strong> at the top of the page. | |||
3. Monitor the status panel. | |||
4. Wait for the <strong>On File / Accepted</strong> status. | |||
</div> | |||
[[File:Emanifest-sync-required.png|thumb|center|Sync Button (Yellow Indicator)]] | |||
</div> | |||
== | <div class="bc-card"> | ||
<h3>Syncing Corrections</h3> | |||
<p>If you edit an accepted manifest, BorderConnect flags it as "Changed".</p> | |||
<div class="bc-cleanlist"> | |||
1. Make your edits (e.g., change driver, fix weight). | |||
2. Review the <strong>Changes made since last sync</strong> summary. | |||
3. Click <strong>Sync with CBP/CBSA</strong> again. | |||
4. Only the specific changes are sent to customs. | |||
</div> | |||
[[File:Emanifest-sync-corrections.png|thumb|center|Change Summary Panel]] | |||
</div> | |||
</div> | |||
<h2 style="margin-top: 40px; border-bottom: 2px solid #eee; padding-bottom: 10px;">Visual Indicators</h2> | |||
<div class="bc-card"> | |||
<div style="display: flex; flex-wrap: wrap; gap: 30px; align-items: center;"> | |||
* | <div style="flex: 1; min-width: 300px;"> | ||
* | <h3>Status Panels</h3> | ||
* | <p>The sync bar changes color to keep you informed:</p> | ||
<div class="bc-cleanlist"> | |||
* <strong>Yellow:</strong> Sync Required (Changes are pending). | |||
* <strong>Blue (Processing):</strong> Transmission in progress. | |||
* <strong>Green:</strong> Synced (Data matches what is on file). | |||
</div> | |||
</div> | |||
= | <div style="flex: 1; min-width: 300px; text-align: center;"> | ||
Β | [[File:Synced-with-cbp.png|thumb|center|Successful Sync (Green)]] | ||
</div> | |||
Β | |||
</div> | </div> | ||
</div> | </div> | ||
<div style=" | <div class="bc-card" style="margin-top: 20px;"> | ||
[[File: | <h3>Manifest Listing Page</h3> | ||
<p>You don't need to open every trip to check its status. The main listing page flags any manifest that has pending changes.</p> | |||
[[File:Emanifest-sync-is-required-listing.png|thumb|center|Listing Page Indicators]] | |||
</div> | </div> | ||
= | <h2 style="margin-top: 40px; border-bottom: 2px solid #eee; padding-bottom: 10px;">Audit & History</h2> | ||
<div class="bc-card"> | |||
Β | <h3>Trip Action Plan / Changelog</h3> | ||
<p>Every Sync action is permanently recorded for compliance auditing. Scroll to the bottom of any manifest to see the <strong>Trip Action Plan</strong>.</p> | |||
Β | <div class="bc-cleanlist"> | ||
* <strong>Submission Times:</strong> Exact timestamp of the sync. | |||
* <strong>Messages Sent:</strong> What specific data was transmitted. | |||
* <strong>Customs Responses:</strong> The raw acceptance or reject message from CBP/CBSA. | |||
</div> | |||
Β | [[File:Ace-trip-action-plan.png|thumb|center|Trip History Log]] | ||
<div | |||
[[File: | |||
</div> | </div> | ||
<h2 style="margin-top: 40px; border-bottom: 2px solid #eee; padding-bottom: 10px;">Advanced: Manual Legacy Methods</h2> | |||
== | <div class="bc-card" style="border-top: 4px solid #f0ad4e;"> | ||
<p style="margin-bottom: 20px;">While <strong>eManifest Sync</strong> is the primary method for all transmissions, legacy manual functions remain available for specific troubleshooting or advanced scenarios. Use these only if Sync is disabled or under support guidance.</p> | |||
<div style="display: grid; grid-template-columns: repeat(auto-fit, minmax(300px, 1fr)); gap: 20px;"> | |||
<div style="background: #fdfdfd; border: 1px solid #e1e1e1; border-radius: 8px; padding: 20px; display: flex; align-items: flex-start; gap: 15px;"> | |||
<div style="font-size: 24px; color: #003366;"><i class="fas fa-flag-usa"></i></div> | |||
<div> | |||
<h4 style="margin: 0 0 5px 0; color: #003366;">ACE Legacy Corrections</h4> | |||
<p style="font-size: 13px; color: #666; margin-bottom: 15px;">Detailed guide for manual Amendments and Cancel/Resubmit actions for U.S. Customs.</p> | |||
[[Updating_or_Correcting_an_Accepted_ACE_Manifest_(Legacy_Method)_(ACE_Manifest)|<span class="bc-article-pill" style="background: #003366; color: white; border: none; cursor: pointer;">Open ACE Guide <i class="fas fa-external-link-alt" style="margin-left:5px;"></i></span>]] | |||
</div> | |||
</div> | |||
<div style="background: #fdfdfd; border: 1px solid #e1e1e1; border-radius: 8px; padding: 20px; display: flex; align-items: flex-start; gap: 15px;"> | |||
<div style="font-size: 24px; color: #d9534f;"><i class="fas fa-leaf"></i></div> | |||
<div> | |||
<h4 style="margin: 0 0 5px 0; color: #d9534f;">ACI Legacy Corrections</h4> | |||
<p style="font-size: 13px; color: #666; margin-bottom: 15px;">Detailed guide for manual Changes and Cancellations for Canada Border Services Agency.</p> | |||
[[Updating_or_Correcting_an_Accepted_ACI_eManifest_(Legacy_Method)_(ACI_eManifest)|<span class="bc-article-pill" style="background: #d9534f; color: white; border: none; cursor: pointer;">Open ACI Guide <i class="fas fa-external-link-alt" style="margin-left:5px;"></i></span>]] | |||
</div> | |||
</div> | |||
</div> | </div> | ||
</div> | </div> | ||
{{AppPromo}} | |||
Β | |||
[[Category:BorderConnect Software User Guide]] | </div> [[Category:BorderConnect Software User Guide]] | ||
Latest revision as of 13:01, 5 May 2026
|
π This article is part of the BorderConnect Software User Guide |
eManifest Sync (ACE & ACI)
The intelligent transmission tool that handles all manifest submissions, updates, and amendments with a single click.
Overview
The eManifest Sync Feature allows users to submit and update both ACE (CBP) and ACI (CBSA) eManifests using a single action.
Instead of manually selecting specific transmission message types (like "Amend", "Change", or "Add"), users simply click Sync with CBP or Sync with CBSA. BorderConnect intelligently calculates the difference between your last submission and your current data, then automatically sends the correct message(s) to customs.
Why Use Sync? It removes the guesswork. Whether it's a new manifest, a driver change, or a shipment amendment, Sync handles the required logic for you.
π€ What Sync Automatically Handles
| Scenario | What BorderConnect Sends |
|---|---|
| Brand New eManifest | Initial manifest submission (Create Trip + Create Shipments). |
| Trip Details Edited | Correction/Update message for the trip data. |
| Shipments Added/Removed | Amendment transmission to add or delete shipment data. |
| Multiple Changes | All required updates bundled into one efficient transmission. |
How to Use Sync
Syncing a New Manifest
When you first create a manifest, it is in "Draft" status. Syncing submits it to customs.
1. Complete your Trip and Shipment details. 2. Click Sync with CBP/CBSA at the top of the page. 3. Monitor the status panel. 4. Wait for the On File / Accepted status.

Syncing Corrections
If you edit an accepted manifest, BorderConnect flags it as "Changed".
1. Make your edits (e.g., change driver, fix weight). 2. Review the Changes made since last sync summary. 3. Click Sync with CBP/CBSA again. 4. Only the specific changes are sent to customs.

Visual Indicators
Manifest Listing Page
You don't need to open every trip to check its status. The main listing page flags any manifest that has pending changes.

Audit & History
Trip Action Plan / Changelog
Every Sync action is permanently recorded for compliance auditing. Scroll to the bottom of any manifest to see the Trip Action Plan.
- Submission Times: Exact timestamp of the sync.
- Messages Sent: What specific data was transmitted.
- Customs Responses: The raw acceptance or reject message from CBP/CBSA.

Advanced: Manual Legacy Methods
While eManifest Sync is the primary method for all transmissions, legacy manual functions remain available for specific troubleshooting or advanced scenarios. Use these only if Sync is disabled or under support guidance.
ACE Legacy Corrections
Detailed guide for manual Amendments and Cancel/Resubmit actions for U.S. Customs.
ACI Legacy Corrections
Detailed guide for manual Changes and Cancellations for Canada Border Services Agency.
