PARS (CBSA Shipment Type)
| This article is part of the Shipment Release Types Guide |
Training video: Creating an ACI eManifest with a PARS shipment in BorderConnect.

PARS stands for Pre-arrival Review System. It is the standard Canadian Shipment Type for most commercial goods entering Canada by highway carrier through Canada Border Services Agency (CBSA) and ACI eManifest.
PARS allows the customs broker to submit release information to CBSA before the goods arrive. The carrier files an ACI eManifest using the same shipment identifier so CBSA can connect the broker's release request to the carrier's cargo report.
How PARS works
PARS links two filings:
- the carrier's ACI eManifest cargo report; and
- the broker's CBSA release request.
The PARS number is the common value that allows CBSA to match the carrier's cargo control number to the broker's release request. If the number entered on the ACI eManifest does not exactly match the number used by the broker, the shipment can be delayed at the border.
PARS number
A PARS number is a type of Cargo Control Number (CCN) assigned by the carrier for pre-arrival release. CBSA guidance states that a cargo control number begins with the carrier code followed by a unique shipment number, and the CCN must not be reused for at least three years.<ref name="ccn">CBSA: Cargo Control Number</ref>
A PARS number must begin with the carrier's CBSA carrier code and then include the carrier's unique sequence. The word PARS is not required, but many carriers include it in the barcode. If the word PARS appears in the barcode or paperwork, it must be entered the same way on the ACI eManifest and broker release request.
Carrier and broker workflow
The usual PARS workflow is:
- The carrier picks up the shipment and assigns a unique PARS number.
- The carrier puts the PARS number or barcode on the commercial paperwork, such as the invoice or bill of lading.
- The paperwork is sent to the customs broker.
- The broker files the release request with CBSA using that same PARS number.
- The carrier creates an ACI eManifest shipment using that same PARS number.
- CBSA matches the broker release request and carrier cargo report before the truck arrives, allowing the officer to release the goods or refer them for examination.
Declaring a PARS shipment in ACI eManifest
PARS shipments are reported on an ACI eManifest. To report a PARS shipment in BorderConnect:
- Create an ACI shipment.
- Select PARS as the shipment type. In some systems this may also appear as Non-CSA.
- Enter the PARS number exactly as it appears on the paperwork supplied to the broker.
- Enter the shipper, consignee, and commodity information normally required for an ACI shipment.
- Save the shipment and transmit it as part of the ACI eManifest.

Before the driver goes to the border, confirm that both the ACI eManifest and broker release request are on file. This can be verified with BorderConnect PARS/RNS status checking or directly with the customs broker.
Timing
For highway shipments, CBSA requires advance electronic cargo and conveyance data to be transmitted and accepted before arrival. The standard highway timing requirement is at least one hour before arrival at the first Canadian port of arrival.<ref name="eccrd">CBSA: ACI/eManifest Highway Electronic Commerce Client Requirements</ref>
The broker's release request should also be filed and matched before the driver reaches the border. BorderConnect status messages such as release, transaction number, or RNS/PARS updates can help confirm that the PARS is ready.
Troubleshooting
If the PARS is not showing as ready:
- confirm that the broker has filed the release request;
- confirm that the broker used the exact same PARS number or CCN;
- check whether the word PARS is included or omitted consistently;
- check for typos, spaces, dashes, or missing carrier-code characters;
- confirm that the ACI eManifest was transmitted and accepted by CBSA; and
- allow time for CBSA status messages to update after transmission.
Do not send the driver to the border until the carrier and broker have confirmed that the ACI eManifest and broker release request are ready.
References
<references />