The CARM Client Portal changes customs accounting less by replacing the broker’s entry work than by making the importer the accountable owner of the commercial account. A broker may prepare and submit a Commercial Accounting Declaration (CAD) under delegated authority, but the importer’s finance and trade teams still need to decide whether the transaction is correct, whether the amount is payable, how it should be recorded and what evidence supports any correction.
That distinction matters for companies receiving goods through Pearson (YYZ), trucking freight along the 401/407 corridor or distributing inventory from warehouses in Mississauga and Brampton. Customs data now needs to move through the same control environment as purchase orders, receiving records, tax recovery and accounts payable. The CARM portal provides visibility; it does not replace the importer’s internal accounting process.
The role that changed
Before an importer had direct access to its customs account, many businesses treated the broker’s accounting package as the practical end of the process. The broker transmitted entry data, arranged payment or communicated amounts owing, and the importer posted a summarized figure to its books. That model could hide gaps between the customs declaration, the commercial invoice, the goods received and the amount ultimately paid.
Under CARM, the importer’s account is a direct control point. CBSA describes the CAD as the document used to account for imported commercial goods and the CARM Client Portal as the place where account information, transactions, statements and payments can be managed. A broker can continue to perform delegated work, but delegation does not transfer the importer’s responsibility for the underlying transaction.
In practice, the importer now owns four decisions:
- Whether the declared transaction matches the goods, supplier documents and terms of sale.
- Whether duties and taxes have been posted to the correct shipment, business unit, inventory item or expense account.
- Whether the amount shown in the portal has been paid, remains payable or has been affected by an adjustment.
- Whether a correction, adjustment request or accounting treatment is supported by records that can be retrieved later.
This is an ownership change, not an instruction for finance staff to prepare every customs declaration themselves. The broker remains useful for classification analysis, origin review, valuation questions, CAD preparation and filing execution. The importer must provide accurate commercial facts and operate the approval and reconciliation controls around that work.
What the portal shows—and what it does not prove
A portal record is evidence of what was submitted or posted to the customs account. It is not, by itself, proof that the entry is commercially correct. A CAD can contain an accurate total while still being assigned to the wrong purchase order, product, cost centre or tax treatment in the importer’s systems.
Importers should separate three related records:
| Record | What it answers | Control question |
|---|---|---|
| Commercial documents | What was bought, from whom, under which sale terms and at what price? | Do the invoice, packing list, transport record and purchase order describe the same shipment? |
| CAD and transaction details | What was declared for classification, origin, value for duty, duties and taxes? | Does the customs declaration reflect the commercial facts and approved trade data? |
| Portal statement and payment records | What amount is posted to the account, what has been paid and what remains outstanding? | Can the balance be tied to approved entries and the corresponding bank or payment record? |
The accounting team should not treat the broker’s invoice, the CAD and the CARM statement as interchangeable. A broker invoice may include service charges or disbursements. The CAD records the customs accounting event. The statement reflects the account-level balance and payment activity. Each may be needed to explain a different part of the general-ledger posting.
A practical importer control sequence
1. Capture the commercial facts before filing
The importer’s purchasing, receiving or trade-compliance process should establish a shipment record before the broker files where operationally possible. Useful fields include the supplier invoice, purchase order, importer of record, destination, currency, Incoterm, product identifier, country of origin and expected receiving date.
This is particularly important where Toronto head-office records, Mississauga receiving operations and Brampton distribution facilities use different internal references. The customs transaction should be capable of being linked back to the business event that created it, even if the broker’s shipment reference is different from the importer’s purchase-order number.
2. Approve the data used for the CAD
The importer should define which party supplies and approves classification, origin and valuation information. A broker can identify inconsistencies, request supporting documents and apply the instructions provided, but it may not know that a product was modified, bundled, returned, sold under a different term or subject to an assist or other valuation fact.
A workable handoff identifies exceptions instead of asking finance to review every line in the same way. For example, a new product, a changed supplier, a revised country of origin, a preferential tariff claim or a material price adjustment can trigger trade-compliance review before accounting accepts the transaction.
3. Match the filed transaction to receiving and purchasing records
After the CAD is available, the importer should match it to the commercial file. The aim is not simply to compare the total amount. The review should identify whether the quantity, invoice value, currency, origin, tariff treatment and importer reference are consistent with the shipment.
Exceptions commonly arise when one commercial invoice covers multiple conveyances, when a consolidated shipment contains several purchase orders or when the customs transaction is filed before final receiving information is available. Those exceptions should be recorded as open items with an owner and resolution date rather than silently passed into the ledger.
4. Reconcile the portal account to the ledger
The CARM statement and transaction views should be used for account-level reconciliation, while the CAD and commercial file support transaction-level reconciliation. A monthly close procedure can compare:
- CADs posted during the period with broker reports and receiving records.
- Duties and taxes recorded in the ledger with the amounts attributed to the related transactions.
- Payments released through the importer’s payment process with activity shown in the CARM account.
- Open balances, credits, adjustments and disputed items with the reconciliation schedule.
The reconciliation should explain timing differences. A declaration may be posted in one accounting period while the related payment, invoice approval or goods receipt occurs in another. Without that explanation, an apparently small balance can become a recurring unexplained difference between the customs account and the general ledger.
5. Retain the evidence behind exceptions
Where an importer identifies a possible error, the file should preserve the original transaction, the reason for concern, the supporting commercial records and the action taken. Depending on the issue, the next step may involve the broker, a correction or adjustment process, a request for additional information or an internal accounting reclassification.
A portal screenshot alone is rarely a sufficient case file. The useful record shows what was declared, what the importer believes is different, why the difference matters and which documents support the proposed resolution.
Failure modes that become more visible under CARM
Assuming broker delegation means broker ownership
Delegated access allows a broker to work in the importer’s account according to the authority granted. It does not make the broker the owner of the importer’s product data, accounting policy or payment approval. Importers should document who can submit, review, approve and request changes, and should remove or revise access when responsibilities change.
Posting a broker invoice as the customs liability
A broker invoice may be the payment request that starts an internal workflow, but it may not provide the same detail as the CAD or the account statement. Posting it without separating customs amounts from brokerage charges, recoverable taxes and other components can make later reconciliation difficult.
Reconciling only the bank payment
A payment match proves that funds left the importer’s account. It does not establish that the correct CADs were included, that the statement balance was understood or that an adjustment was applied to the intended transaction. Account reconciliation should begin with the customs account activity and then connect to payment evidence.
Leaving corrections with no accounting trail
When a customs amount changes, the importer’s ledger, tax recovery records and internal shipment file may need corresponding updates. A correction that is handled only in a portal or only in an email exchange can leave the original posting unexplained. The control should retain both the original and revised positions, with the reason for the change.
Using one owner for every decision
Trade compliance, purchasing, receiving, accounts payable and treasury often hold different parts of the evidence. A single person may coordinate the process, but separating preparation, approval and payment reduces the risk that a classification or valuation assumption passes into the books without review.
What a customs broker can do about the change
A broker can help design the handoff between customs filing and importer accounting. That can include defining the data required before release, mapping broker references to purchase orders, identifying transactions that need review, explaining CAD fields, supporting account reconciliation and escalating discrepancies found in commercial documents.
The broker can also distinguish a customs-data problem from an accounting problem. If the declared origin or value is wrong, the issue may require customs analysis and a formal correction path. If the CAD is accurate but was posted to the wrong internal entity, the importer may need a ledger correction instead. Treating both issues as a generic “broker invoice difference” slows resolution and weakens the audit trail.
For GTA importers, a useful operating model is to give the broker one controlled intake for shipment facts, give finance a regular transaction and statement report, and route exceptions to a named trade or accounting owner. That approach works whether goods arrive by air through YYZ for a Toronto operation or by truck to a Mississauga or Brampton warehouse. The location changes the movement and receiving process; it does not remove the need to connect the customs account to the importer’s books.
Questions management should ask before the next close
- Can every CAD in the reporting period be linked to a commercial file and an internal business reference?
- Can the team distinguish customs duties and taxes from broker service charges and other payment components?
- Who approves classification, origin and value information when a product or supplier changes?
- Can the importer explain every open balance, credit, adjustment and timing difference in the CARM account?
- Does the correction file preserve the original declaration, the supporting evidence and the resulting accounting entry?
- Are CARM permissions aligned with current staff, brokers and internal approval roles?
The central control is straightforward: the importer should be able to trace a balance from the CARM account to a transaction, from the transaction to commercial evidence, and from that evidence to the general ledger and payment record. The broker supports the customs portion of that chain. CARM makes it harder to treat the chain as someone else’s accounting responsibility.