The CARM Client Portal changed the importer’s accounting task from receiving a broker’s customs package to controlling a customs account. Importers generally need a repeatable way to connect the commercial import, the accounting declaration, the broker’s work, the statement of account and the eventual payment. The practical issue is not simply where to find a duty or tax amount. It is deciding which record is authoritative for each accounting step, identifying what changed, and preventing a correction or payment allocation from being recorded twice.
This is especially relevant for companies whose customs work is distributed between a broker, an accounts-payable team and a warehouse or purchasing group. A business receiving goods through Pearson or distributing inventory from Mississauga, Brampton or Toronto may have several internal references for one import. The CARM portal does not eliminate those handoffs. It makes ownership of the importer’s account, permissions, balances and payment controls more visible.
The accounting change is a control change
The CARM Client Portal is the importer’s online environment for managing its commercial accounting information with the Canada Border Services Agency. The portal is separate from a broker’s own operating system. A broker may prepare and transmit customs information under delegated authority, but the importer remains the party that should understand its account structure, review customs records and control access to its financial information.
CBSA describes CARM as the system of record for commercial accounting declarations and related account activity. The accounting record for a shipment is commonly referred to as the Commercial Accounting Declaration, or CAD. The relevant record for reconciliation is therefore not necessarily the PDF, spreadsheet or email attachment that arrives first. It is the declaration and account activity that the importer can review in the portal, together with the supporting commercial and transportation documents.
This distinction creates four separate questions:
- What goods and values were imported?
- What did the importer or its broker declare on the CAD?
- What amount did CBSA assess, and when did it appear in the account?
- What amount was paid, credited, corrected or left outstanding?
A sound month-end process answers all four without assuming that they will always produce the same amount. Differences can arise from classification, origin, tariff treatment, valuation, tax treatment, corrections, reassessments or payment allocation. The difference is a review signal, not automatically a new payable.
Build the reconciliation around the CAD, not the invoice email
The first useful control is a shipment-level customs register. The register should connect the importer’s purchase or shipment reference to the customs accounting record and to the financial posting. It can be maintained in an enterprise resource planning system, a customs application or a controlled spreadsheet, provided the owner and change history are clear.
For each import selected for reconciliation, the file will generally need:
| Record | Why it matters |
|---|---|
| Commercial invoice and packing information | Supports the goods description, quantity, price, currency, seller and purchaser information used in the declaration. |
| Transport and release references | Connects the shipment to the carrier, entry event, release activity and warehouse receipt. |
| CAD and related portal information | Shows the accounting declaration and the duties and taxes assessed in the customs account. |
| Broker accounting or transaction report | Provides an operational cross-check and identifies what the broker transmitted or adjusted. |
| Statement of account and payment evidence | Shows the account-level amount due, credits, payments and remaining balance. |
| Correction or reassessment documentation | Explains why a previously recorded amount changed and whether the change affects inventory, cost, recoverable tax or another account. |
The register does not require finance to recreate the broker’s customs work. It gives finance a controlled way to determine whether the broker’s transaction report, the portal record and the accounting entry refer to the same import. A shipment reference alone may not be sufficient where one purchase order is split across entries or where one declaration covers multiple commercial documents.
Separate three dates
Importers often lose clarity by using a single “customs date.” The file should distinguish at least the date the goods were imported or accounted for, the date the amount was posted to the CARM account, and the date the importer paid or received a credit. Those dates can fall in different reporting periods.
The distinction matters at month-end. A shipment received in a Peel Region warehouse near the end of a month may be physically available while its accounting declaration or account posting appears in a later period. Finance should follow its accounting policy and tax rules for recognition, but the customs reconciliation should preserve the sequence instead of forcing all events into one date field.
Use the portal to test the broker handoff
The portal is not a replacement for broker instructions or shipment documents. It is a second control point. After the importer’s account is registered and the appropriate users are assigned, a designated employee can compare portal information with the broker’s transaction output.
The review should focus on exceptions rather than manually rechecking every field on every shipment. Useful exception rules include:
- A CAD exists in the portal but has no matching internal shipment or purchase reference.
- An internal shipment has broker documentation but no expected accounting record has been located.
- The declared importer, consignee, currency, value or tariff treatment differs from the commercial file.
- The amount assessed does not agree with the amount posted by the importer’s system.
- A correction, adjustment or reassessment appears after the original entry was closed.
- A payment or credit is visible at the account level but cannot be allocated to the expected customs records.
Where a discrepancy appears, the broker should generally be asked to explain the transmission or provide the supporting transaction history. The importer, however, should not outsource the final accounting decision. The business that owns the inventory, payable and tax records is best placed to determine whether a difference is a timing item, a correction to the original entry, a recoverable tax issue, an inventory-cost change or an unresolved exception.
Do not confuse account activity with a new import
A common failure is to treat every portal line, broker adjustment or statement movement as a separate import liability. That can overstate expense and create duplicate entries. A later activity may relate to an existing CAD, a payment allocation, a credit, a correction or a reassessment.
Before posting a new amount, the reviewer should identify the underlying customs record and classify the movement. A simple control status can be enough:
- Original declaration: the first accounting record for the import.
- Payment or allocation: settlement activity against the account or declaration.
- Correction: a change to information or amounts associated with an earlier record.
- Reassessment or review result: an authority-driven change that requires supporting documentation and an accounting conclusion.
- Unmatched: activity that cannot yet be connected to an existing file.
This classification keeps the customs ledger and the general ledger aligned. It also creates an escalation queue for the broker instead of allowing unexplained differences to disappear into a generic duty or tax account.
Control payments at the account level
CARM places greater importance on the importer’s own payment and security administration. Importers using the Release Prior to Payment program generally need to manage the requirements associated with their own account and financial security. The details depend on the importer’s situation and the applicable CBSA program rules; the broker’s ability to transmit release information does not mean the broker controls the importer’s account balance or payment obligation.
Finance teams should establish a payment workflow that identifies:
- who can view account balances and statements;
- who can prepare or authorize a payment;
- who reviews the payment against the statement of account;
- how credits and unapplied amounts are investigated;
- how portal access is removed when an employee changes role or leaves the business.
Segregation of duties is important. The person who maintains the customs register should not automatically be the only person who approves payment or changes portal permissions. A broker can help explain a transaction, but the importer should retain an internal approval trail for payments, account changes and material corrections.
Payment evidence should be stored with the statement and the reconciliation period, not only in a bank folder. If a payment is applied at the account level rather than matched immediately to individual shipments, the reconciliation should show the allocation method and any residual amount awaiting investigation.
Give customs corrections a defined accounting path
Corrections are where a portal-based process most often breaks down. A correction may change duty, tax, value, classification, origin or another declaration field. The accounting treatment depends on what changed and on the importer’s own financial and tax policies. The customs file should therefore contain both the original record and the reason for the subsequent change.
A practical correction workflow is:
- Identify the original CAD and the affected shipment, goods or invoice lines.
- Obtain the broker’s explanation and supporting documents, including the corrected declaration or other portal evidence where available.
- Compare the original and revised values, tariff treatment and duty or tax amounts.
- Determine whether the difference changes inventory cost, cost of goods sold, recoverable tax, payable, accrual or another account.
- Post one controlled adjustment that references the original entry rather than creating an unrelated import record.
- Retain the approval and close the exception only when the portal, broker file and general ledger agree.
If the change concerns classification, origin, valuation or a trade program, the customs review may require more than a finance-only decision. Finance can identify the monetary difference, while customs or the broker should evaluate the underlying declaration and supporting evidence. Where the issue could affect other imports, the importer should consider whether a broader file review is appropriate.
Design a workable GTA handoff
For an importer operating between a Toronto office, a Mississauga customs or logistics function and a Brampton distribution facility, the most useful control is usually a single owner for the customs reconciliation, not a requirement that every location work directly in the portal. Local receiving teams can confirm quantities and warehouse references. Purchasing can validate the commercial invoice. The customs or brokerage contact can explain the declaration. Finance can own the statement, payment and general-ledger reconciliation.
That division works only if the handoff contains defined fields. At minimum, the receiving or purchasing team should pass the internal shipment reference, supplier invoice, received date, warehouse location and any discrepancy. The broker or customs team should return the CAD reference, assessed amounts, release information and correction status. Finance should record the posting, payment allocation and open exception.
The result is a chain of evidence from goods receipt through customs accounting. It is more reliable than forwarding a broker email to accounts payable and assuming that the attachment represents the final account position.
A monthly review that remains manageable
Importers do not necessarily need a separate manual investigation for every shipment. A monthly control can combine a complete account-level review with risk-based shipment testing. The review may include:
- reconciling the CARM statement opening balance, activity, payments, credits and closing balance;
- matching new CAD records to the customs register;
- testing a sample of shipments against the commercial file and broker report;
- reviewing all corrections, reassessments and unmatched items;
- confirming that portal users and delegated authorities remain appropriate;
- documenting the reviewer, period, exceptions and resolution date.
High-risk shipments may warrant full review. Examples include new suppliers, unusual valuation terms, preferential tariff claims, regulated goods, material changes in duty or tax, and shipments where the importer or broker has changed. The objective is not to duplicate the broker’s work. It is to prove that the importer can explain its customs balance and its accounting entries.
The CARM Client Portal makes that responsibility more visible, but the underlying discipline is familiar: identify the source record, reconcile movements to the account, investigate exceptions and preserve an audit trail. Importers that build the process around the CAD and the statement of account can use the broker for customs expertise without losing control of their own duties, taxes and payment records.