The CARM Client Portal changed the importer’s accounting task from receiving a broker’s duty-and-tax figure to maintaining a controlled record of the importer’s own customs account. Brokers can continue preparing and transmitting declarations under their authority, but the importer’s organization generally remains responsible for the account structure, payment arrangements, financial security where applicable, corrections and the accounting records that support them.
That distinction matters at month-end. A customs entry can be released, a broker invoice can be paid and a shipment can reach a warehouse in Mississauga, Brampton or Toronto while the importer’s books still contain the wrong tax treatment, an unmatched adjustment or an unexplained balance in the CARM account. The effective control is a reconciliation between four records: the commercial transaction, the customs declaration, the broker’s billing and the CARM financial record.
What changed for the accounting function
The CARM Client Portal gives importers direct access to customs-account functions that were previously handled largely through broker communications or older payment and accounting arrangements. The exact tasks available to an employee depend on the roles and permissions assigned to that business account, but the broader operating model is clear: the importer owns the account relationship and has to decide how the account will be controlled.
This does not mean that an importer has to prepare every customs declaration internally. An importer may authorize a customs service provider to transact on its behalf. It does mean that the importer should be able to answer questions such as:
- Which legal entity owns the import transaction and the associated account?
- Which broker transmitted the declaration, and which internal purchase or shipment record supports it?
- What amount was assessed for customs duties, GST or other applicable charges?
- Was the amount paid directly through the importer’s account, settled through an authorized arrangement, or later changed?
- Who reviewed an adjustment, correction, reassessment or account statement?
The accounting consequence is a shift from broker-file storage to importer-controlled evidence. The portal becomes one source in the close process, not a replacement for the purchase ledger, inventory system, broker statement or general ledger.
The four records that need to agree
1. The commercial record
The commercial record normally begins with the purchase order, commercial invoice, freight documentation and receiving record. It establishes what was bought, from whom, in what quantity and under what terms. It may also support the value used for customs purposes, although the customs value and the accounting cost can require separate analysis.
For example, freight, assists, royalties, commissions, currency conversion and other cost elements may not flow into the accounting system in the same way as the invoice total. An accounting team should not assume that the amount posted to inventory or expense is automatically the amount used as value for duty.
2. The customs declaration
The declaration contains the data that drives the assessment: the importer account, transaction identifiers, tariff classification, origin, tariff treatment, value for duty and applicable taxes or trade remedies. A broker may prepare this data from information supplied by the importer, but the importer generally remains the party best positioned to confirm whether the product, supplier and transaction information is accurate.
Classification and origin errors can therefore appear as accounting variances before they appear as obvious customs problems. A product bought under the same internal stock code may change supplier, composition, packaging or origin. A recurring SKU does not automatically justify copying the previous customs treatment.
3. The broker record
The broker’s invoice or transaction report is useful operational evidence, but it is not necessarily the complete customs accounting record. Depending on the arrangement, it may combine disbursements, service fees, duties, taxes and other charges. It may also arrive on a different date from the customs statement or the importer’s payment.
Accounting teams should identify whether each broker line represents a government assessment, a broker charge, a recoverable tax amount, a landed-cost component or an amount that still requires investigation. A single “customs” expense account can conceal all four.
4. The CARM financial record
The importer’s CARM account provides the account-level view of assessments, payments, balances and related transactions. The CARM help and guidance material should be used for the current portal screens and account procedures, because access and workflow details can change.
The portal record is especially important when the amount paid does not match the amount shown on a broker invoice. Differences can result from timing, multiple declarations in one payment, a correction, a reassessment, interest, a refund or the separation of broker fees from government charges. The reconciliation should explain the difference rather than force it into a suspense account indefinitely.
A practical month-end close process
Step 1: Define the population
Start with a shipment or declaration population for the accounting period. Depending on the importer’s systems, this may be built from receiving records, purchase receipts, broker transaction files, release information or CARM account activity. The population should include goods that were released during the period as well as open items that were declared, adjusted or paid at a different time.
Do not rely only on the date a broker invoice was received. Customs release, broker billing, payment and inventory receipt can occur in different periods. The accounting policy should state which event drives recognition and which records support accruals or cut-off entries.
Step 2: Match at transaction level
Match each declaration or broker transaction to an internal shipment, purchase order, invoice or receiving record. Useful matching keys can include the transaction number, purchase order number, invoice number, entry date, importer account and broker reference. Where the systems do not share a common identifier, the importer should establish a controlled cross-reference rather than relying on free-text descriptions.
At a minimum, the review should identify:
- unmatched customs transactions;
- commercial receipts with no corresponding customs record;
- duplicate broker charges or duplicate postings;
- tax amounts posted to the wrong entity, period or account;
- entries with unexpected duty, origin, classification or trade-remedy treatment; and
- payments or credits that remain unallocated in the CARM account.
Step 3: Reconcile amounts by type
Separate the comparison into duties, GST or other applicable taxes, trade-remedy amounts, broker fees, disbursements, interest, refunds and corrections. This is more useful than comparing one grand total because each category has a different accounting treatment and a different owner.
Where an importer is registered for GST/HST, the tax treatment of an import amount should be reviewed against the organization’s tax process and supporting customs records. The accounting team should not assume that a customs tax amount is recoverable simply because it appears on a broker invoice. The appropriate treatment can depend on the importer, the transaction and the organization’s tax position.
Step 4: Investigate exceptions before posting
Exceptions should be assigned to a person who can resolve the underlying issue. A broker may be able to confirm what was transmitted or explain a billing line. A classification or origin owner may need to review the product. Treasury may need to investigate a payment allocation. Tax or controllership may need to determine the treatment of GST/HST, a credit or a reassessment.
The file should record the question, evidence reviewed, decision, responsible approver and date closed. This is more defensible than changing a ledger amount without preserving why the change was made.
Step 5: Tie the result to the ledger
After transaction-level exceptions are resolved or accrued, reconcile the totals to the general ledger, accounts payable, inventory or landed-cost module and the CARM account. The reconciliation should show opening balance, current assessments, payments, credits, adjustments and closing balance, with explanations for timing differences.
Where the importer uses multiple brokers or legal entities, the reconciliation should be segmented accordingly. A consolidated total may hide an account that belongs to the wrong importer, an inactive business number or a payment applied to another account.
Where importers commonly lose control
Treating the broker invoice as the customs source of truth
A broker invoice is an important source document, but it may not show every portal-level transaction or later correction. Importers generally benefit from obtaining a consistent transaction report from each broker and comparing it with the CARM account and internal shipment data.
Giving portal access without ownership
Registration alone does not create a control framework. Importers should generally define who can view account activity, who can manage permissions, who can make or authorize payments and who reviews corrections. Segregation of duties is particularly useful where the same organization prepares payment files, approves customs changes and posts the resulting entries.
Ignoring financial-security and payment design
Importers using the Release Prior to Payment program should understand how their financial-security arrangement affects release, account monitoring and cash planning. The accounting team may not own the security instrument, but it needs visibility into the obligations and the data used to monitor them. An importer that treats release as the end of the transaction can miss the later payment and statement requirements.
Failing to preserve the correction trail
A changed amount is not self-explanatory. When a declaration is corrected or reassessed, retain the original reference, the new information, the reason for the change, the related broker or portal record and the accounting entry. The CBSA accounting and release guidance provides the regulatory context for customs accounting processes; internal procedures should translate that context into document retention and approval steps.
How a customs broker fits into the control
A broker can help validate declaration data, identify information gaps, transmit corrections when authorized, explain assessment lines and provide reports that make matching possible. The broker can also help distinguish a customs assessment from a service charge or identify when a discrepancy appears to arise from classification, origin, value or tariff treatment.
The broker does not replace the importer’s accounting owner. The importer generally supplies the commercial facts, confirms the legal entity and transaction context, approves material changes and determines the organization’s financial reporting and tax treatment. A workable operating agreement should specify:
- which data the importer supplies before declaration;
- which reports the broker provides and at what frequency;
- how unmatched transactions and corrections are escalated;
- who approves changes to classification, origin, value or tariff treatment; and
- how portal activity is reconciled to the importer’s ledger and payment records.
For GTA importers with inventory moving from Pearson or through the 401/407 corridor into Peel Region distribution facilities, the control is most effective when the customs record is linked to the same shipment and receiving identifiers used by procurement, warehouse and finance teams. That linkage reduces the chance that a release record, warehouse receipt and payment remain in separate systems with no accountable owner.
A minimum evidence package for each close
| Control area | Evidence to retain | Review question |
|---|---|---|
| Commercial transaction | Invoice, purchase order, freight record and receipt | Does the customs transaction relate to the goods actually received? |
| Declaration | Transaction reference and declared data or broker report | Are classification, origin, value and treatment supported? |
| Assessment | CARM transaction or statement detail | Do duties and taxes agree with the accounting entry? |
| Payment | Payment confirmation and allocation record | Was the payment applied to the correct account and period? |
| Exception | Investigation notes, approval and correction record | Can a reviewer understand what changed and why? |
The purpose is not to create a separate file for every minor variance. It is to make the material transactions and unresolved exceptions visible, reproducible and assigned to an owner. The level of review can be risk-based, with more scrutiny for new products, new suppliers, unusual values, trade remedies, related-party transactions and repeated broker or portal mismatches.
The operating principle
CARM changed the accounting question from “What did the broker charge?” to “Can the importer explain the complete customs financial record?” The answer should connect the purchase, declaration, assessment, payment, correction and ledger treatment.
Importers that build this reconciliation into the regular close are better positioned to identify errors before they accumulate. They can also give a broker a precise exception to investigate instead of asking for a general statement review. The portal is therefore not simply another payment screen: it is a control point in the importer’s evidence chain.

