BorderConnect Wiki

Edit ACI eManifest Page (ACI eManifest): Difference between revisions

← Older edit
No edit summary
No edit summary
 
(3 intermediate revisions 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}}


[[File:Editaciemanifest1.png|400px|thumb|right|Viewing the '''Edit ACI eManifest''' page]]
<div class="bc-wrap">


The '''Edit ACI eManifest Page''' 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.
<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>


This page is typically used when:
<div class="bc-card">


* Trip numbers need correction 
<h2 style="margin-top: 0;">Overview</h2>
* Arrival ports or bonded warehouses change 
<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>
* ETA updates are required 
* Trip information must be adjusted before or after transmission 


You can access this page by clicking '''Edit''' on the [[ACI_eManifest_Details_Page_(ACI_eManifest)|ACI eManifest Details Page]].
<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>


== Saving or Cancelling Changes ==
[[File:Editaciemanifest1.png|800px|thumb|center|Viewing the '''Edit ACI eManifest''' page]]


{| class="wikitable"
<div class="bc-did-you-know" style="margin-top: 15px;">
! Button !! Action
<strong>How to Access:</strong><br>
|-
Click the <strong>Edit</strong> button on the [[ACI_eManifest_Details_Page_(ACI_eManifest)|ACI eManifest Details Page]].
| Save || Applies all updates and returns you to the ACI eManifest Details Page
</div>
|-
| Cancel || Discards changes and returns to the ACI eManifest Details Page
|-
| Clear || Removes all entered values from the form fields
|}


== Manifest Trip Information Fields ==
<div style="clear: both;"></div>
</div>


The following fields control how the manifest is identified and transmitted to CBSA.
<h2 style="margin-top: 40px; border-bottom: 2px solid #eee; padding-bottom: 10px;">Page Actions</h2>


=== Trip Number (Conveyance Reference Number) ===
<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>


The Trip Number uniquely identifies the manifest with CBSA.
<h2 style="margin-top: 40px; border-bottom: 2px solid #eee; padding-bottom: 10px;">Manifest Trip Information Fields</h2>


* Always begins with your Canadian Carrier Code 
<div class="bc-card">
* Followed by 4 to 21 letters or numbers 
<p>The following fields control how the manifest is identified and transmitted to CBSA.</p>
* Must be unique for each trip 
* Cannot be a PARS number or Cargo Control Number 


'''Common best practices include:'''
<h3>Trip Number (Conveyance Reference Number)</h3>
<p>The Trip Number uniquely identifies the manifest with CBSA.</p>
<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>


* Using internal load numbers 
<h3>Route & Destination</h3>
* Including the date in the reference 
<table class="wikitable" style="width: 100%;">
* Using a sequential numbering system 
<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>


=== First Canadian Port of Entry ===
<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>


Indicates where the driver will physically enter Canada.
<h2 style="margin-top: 40px; border-bottom: 2px solid #eee; padding-bottom: 10px;">Common Update Scenarios</h2>


You may search by:
<div class="bc-card">
<p>Use the Edit page to address these common situations:</p>


* Port code 
<table class="wikitable" style="width: 100%;">
* Canadian city name 
<tr>
* Often the U.S. city name will also locate the matching Canadian port 
<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>


=== Sub Location / Bonded Warehouse ===
<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>


Used to define where in-bond shipments are destined.
{{AppPromo}}


This field:
</div>
 
* Is required for in-bond shipments 
* Allows failed PARS to move in-bond 
* Should be completed by bonded carriers 
* Is typically left blank by non-bonded carriers 
 
You can search by:
 
* Warehouse name 
* Sublocation code 
 
=== Estimated Arrival Date ===
 
Specifies when the driver is expected to reach the Canadian border.
 
Features include:
 
* Manual entry (MM/DD/YYYY) 
* Calendar selector 
* Eraser icon to clear the date 
 
'''Important rule:''' 
Manifests cannot be transmitted more than 30 days before arrival.
 
=== Estimated Arrival Time ===
 
Defines the expected time of arrival using dropdown selectors for:
 
* Hour 
* Minute 
* AM / PM 
 
== Common Update Scenarios ==
 
{| class="wikitable"
! 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
|}
 
== After Making Edits ==
 
Once saved:
 
* You will return to the ACI eManifest Details Page 
* If the manifest is already on file, BorderConnect may prompt you to Sync updates with CBSA 
* All changes are recorded in the Trip Action Plan / Changelog History 


[[Category:BorderConnect Software User Guide]]
[[Category:BorderConnect Software User Guide]]
Retrieved from "https://wiki.borderconnect.com/index.php?title=Edit_ACI_eManifest_Page_(ACI_eManifest)"