Edit ACI eManifest Page (ACI eManifest): Difference between revisions
No edit summary |
No edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
{{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>Edit ACI eManifest Page</h1> | |||
<p>Update the core trip details, ports, and arrival times for an existing ACI eManifest.</p> | |||
<div class="bc-article-meta"> | |||
<span class="bc-article-pill"><i class="fas fa-edit"></i> Type: Data Entry</span> | |||
<span class="bc-article-pill"><i class="fas fa-flag"></i> Country: Canada (CBSA)</span> | |||
</div> | |||
</div> | |||
<div class="bc-card"> | |||
<h2 style="margin-top: 0;">Overview</h2> | |||
<p>The <strong>Edit ACI eManifest Page</strong> in BorderConnect’s [https://www.borderconnect.com/aci-e-manifest/index.htm ACI eManifest software] allows users to update the main trip-level details of an existing ACI manifest.</p> | |||
<p>This page is typically used when:</p> | |||
<div class="bc-cleanlist"> | |||
* Trip numbers need correction. | |||
* Arrival ports or bonded warehouses change. | |||
* ETA updates are required due to delays. | |||
* Trip information must be adjusted before or after transmission. | |||
</div> | |||
[[File:Editaciemanifest1.png|800px|thumb|center|Viewing the '''Edit ACI eManifest''' page]] | |||
| | |||
| | |||
== | <div class="bc-did-you-know" style="margin-top: 15px;"> | ||
<strong>How to Access:</strong><br> | |||
Click the <strong>Edit</strong> button on the [[ACI_eManifest_Details_Page_(ACI_eManifest)|ACI eManifest Details Page]]. | |||
</div> | |||
<div style="clear: both;"></div> | |||
</div> | |||
= | <h2 style="margin-top: 40px; border-bottom: 2px solid #eee; padding-bottom: 10px;">Page Actions</h2> | ||
<div class="bc-card"> | |||
<table class="wikitable" style="width: 100%;"> | |||
<tr> | |||
<th style="width: 25%;">Button</th> | |||
<th>Action</th> | |||
</tr> | |||
<tr> | |||
<td><strong>Save</strong></td> | |||
<td>Applies all updates and returns you to the ACI eManifest Details Page.</td> | |||
</tr> | |||
<tr> | |||
<td><strong>Cancel</strong></td> | |||
<td>Discards changes and returns to the details page without saving.</td> | |||
</tr> | |||
<tr> | |||
<td><strong>Clear</strong></td> | |||
<td>Removes all entered values from the form fields.</td> | |||
</tr> | |||
</table> | |||
</div> | |||
= | <h2 style="margin-top: 40px; border-bottom: 2px solid #eee; padding-bottom: 10px;">Manifest Trip Information Fields</h2> | ||
The | <div class="bc-card"> | ||
<p>The following fields control how the manifest is identified and transmitted to CBSA.</p> | |||
* | <h3>Trip Number (Conveyance Reference Number)</h3> | ||
<p>The Trip Number uniquely identifies the manifest with CBSA.</p> | |||
* Must be unique for each trip | <div class="bc-cleanlist"> | ||
* <strong>Structure:</strong> Begins with your Canadian Carrier Code followed by 4 to 21 alphanumeric characters. | |||
* <strong>Rules:</strong> Must be unique for each trip. Cannot be the same as a PARS or Cargo Control Number. | |||
* <strong>Best Practices:</strong> Use internal load numbers or sequential numbering (e.g., CARRIER1001). | |||
</div> | |||
<h3>Route & Destination</h3> | |||
<table class="wikitable" style="width: 100%;"> | |||
<tr> | |||
<th style="width: 30%;">Field</th> | |||
<th>Description & Usage</th> | |||
</tr> | |||
<tr> | |||
<td><strong>First Canadian Port of Entry</strong></td> | |||
<td>Indicates where the driver will physically enter Canada. Search by Port Code or City Name.</td> | |||
</tr> | |||
<tr> | |||
<td><strong>Sub Location / Bonded Warehouse</strong></td> | |||
<td>Required for in-bond shipments. Defines where goods are destined if not released at the border. <br><em>(Note: Typically left blank by non-bonded carriers).</em></td> | |||
</tr> | |||
</table> | |||
<h3>Arrival Timing</h3> | |||
* | <div class="bc-cleanlist"> | ||
* | * <strong>Estimated Arrival Date:</strong> Specifies when the driver is expected at the border. (Remember: Manifests cannot be transmitted more than 30 days before arrival). | ||
* <strong>Estimated Arrival Time:</strong> Defines the expected time of arrival (Hour/Minute/AM-PM). | |||
</div> | |||
</div> | |||
= | <h2 style="margin-top: 40px; border-bottom: 2px solid #eee; padding-bottom: 10px;">Common Update Scenarios</h2> | ||
<div class="bc-card"> | |||
<p>Use the Edit page to address these common situations:</p> | |||
<table class="wikitable" style="width: 100%;"> | |||
<tr> | |||
<th style="width: 40%;">Situation</th> | |||
<th>Field to Update</th> | |||
</tr> | |||
<tr> | |||
<td><strong>Driver delayed</strong></td> | |||
<td>Estimated Arrival Date and Time.</td> | |||
</tr> | |||
<tr> | |||
<td><strong>Border crossing changed</strong></td> | |||
<td>First Canadian Port of Entry.</td> | |||
</tr> | |||
<tr> | |||
<td><strong>In-bond routing updated</strong></td> | |||
<td>Sub Location / Warehouse.</td> | |||
</tr> | |||
<tr> | |||
<td><strong>Trip reference correction</strong></td> | |||
<td>Trip Number.</td> | |||
</tr> | |||
</table> | |||
<div class="bc-did-you-know" style="margin-top: 15px;"> | |||
<strong>Note on Post-Save Actions:</strong> Once saved, if the manifest is already on file, BorderConnect may prompt you to <strong>Sync</strong> updates with CBSA to ensure they receive the changes. | |||
</div> | |||
</div> | |||
{{AppPromo}} | |||
</div> | |||
[[Category:BorderConnect Software User Guide]] | [[Category:BorderConnect Software User Guide]] | ||
Latest revision as of 17:42, 18 February 2026
|
🔖 This article is part of the BorderConnect Software User Guide |
Edit ACI eManifest Page
Update the core trip details, ports, and arrival times for an existing ACI eManifest.
Overview
The Edit ACI eManifest Page in BorderConnect’s ACI eManifest software allows users to update the main trip-level details of an existing ACI manifest.
This page is typically used when:
- Trip numbers need correction.
- Arrival ports or bonded warehouses change.
- ETA updates are required due to delays.
- Trip information must be adjusted before or after transmission.

How to Access:
Click the Edit button on the ACI eManifest Details Page.
Page Actions
| Button | Action |
|---|---|
| Save | Applies all updates and returns you to the ACI eManifest Details Page. |
| Cancel | Discards changes and returns to the details page without saving. |
| Clear | Removes all entered values from the form fields. |
Manifest Trip Information Fields
The following fields control how the manifest is identified and transmitted to CBSA.
Trip Number (Conveyance Reference Number)
The Trip Number uniquely identifies the manifest with CBSA.
- Structure: Begins with your Canadian Carrier Code followed by 4 to 21 alphanumeric characters.
- Rules: Must be unique for each trip. Cannot be the same as a PARS or Cargo Control Number.
- Best Practices: Use internal load numbers or sequential numbering (e.g., CARRIER1001).
Route & Destination
| Field | Description & Usage |
|---|---|
| First Canadian Port of Entry | Indicates where the driver will physically enter Canada. Search by Port Code or City Name. |
| Sub Location / Bonded Warehouse | Required for in-bond shipments. Defines where goods are destined if not released at the border. (Note: Typically left blank by non-bonded carriers). |
Arrival Timing
- Estimated Arrival Date: Specifies when the driver is expected at the border. (Remember: Manifests cannot be transmitted more than 30 days before arrival).
- Estimated Arrival Time: Defines the expected time of arrival (Hour/Minute/AM-PM).
Common Update Scenarios
Use the Edit page to address these common situations:
| Situation | Field to Update |
|---|---|
| Driver delayed | Estimated Arrival Date and Time. |
| Border crossing changed | First Canadian Port of Entry. |
| In-bond routing updated | Sub Location / Warehouse. |
| Trip reference correction | Trip Number. |
Note on Post-Save Actions: Once saved, if the manifest is already on file, BorderConnect may prompt you to Sync updates with CBSA to ensure they receive the changes.