The CARM Client Portal changed customs accounting by moving key controls into an importer-owned account. A customs broker may still prepare and transmit accounting information as an agent, but the importer generally remains responsible for the accuracy of the declaration, the resulting duties and taxes, the payment process and the records supporting each transaction.
That is a different operating model from treating customs accounting as a document the broker sends and the importer pays. For a company importing into a Brampton warehouse, a Toronto office or a Mississauga distribution centre, the practical question is no longer only whether a broker filed the entry. It is whether the importer has a controlled process from shipment data through CARM statement settlement and later correction.
What changed in the importer’s role
CARM provides a central environment for commercial import activities, including account information, broker delegation, commercial accounting declarations, statements and payments. The portal gives the importer direct visibility into information that was previously handled largely through broker systems, carrier documents, internal accounting software and government correspondence.
The change creates four importer-owned responsibilities:
- Access: the company needs an appropriate CARM account structure and controlled user access.
- Authority: the importer needs to decide which customs brokers and employees may act for it, and what authority should be granted or withdrawn.
- Accounting: the importer needs to validate the commercial data that produces duties and taxes, even when a broker prepares the submission.
- Settlement and evidence: the importer needs to review account activity, arrange payment and retain records that explain the amounts reported.
This does not mean that every importer has to perform every portal action personally. A broker can continue to prepare and transmit declarations where the importer has authorized that service. The control point is that the importer should know what was submitted, why it was submitted and how the resulting amount moved into the company’s accounts payable and inventory records.
The new control cycle, from shipment to statement
A practical CARM process is a sequence of handoffs. Each handoff needs an owner, a record and an exception route.
1. Establish the account and delegation structure
The importer should first identify the legal entity that imports the goods and confirm that the CARM account reflects that entity. Companies with several operating divisions or related corporations should avoid treating a shared finance mailbox as a substitute for account governance. The account should have named users, suitable permissions and a documented process for adding, changing and removing access.
Broker delegation is a separate control. The importer should identify which broker is authorized, what services the broker performs and who can approve a change. When a relationship ends, the importer should review and remove obsolete authority rather than allowing a former arrangement to remain active.
A broker can help with registration, delegation and portal navigation, but the importer should retain the decision record showing who approved the relationship and which legal entity it covers.
2. Build the accounting package before transmission
The broker’s accounting file should be supported by commercial records appropriate to the transaction. Depending on the goods and terms, that package may include the commercial invoice, purchase order, packing information, transport document, origin or tariff-treatment evidence, valuation support and any permit or agency documentation.
The importer’s review should focus on the fields that change the customs result:
- the importer of record and the party that purchased the goods;
- the tariff classification and any applicable tariff treatment;
- the country of origin and, where relevant, the country of export;
- the value for duty and currency conversion;
- assists, royalties, commissions, freight or other valuation adjustments where relevant;
- the quantity, unit of measure and description; and
- the treatment of taxes, exemptions, reliefs or special programs.
The importer does not need to duplicate the broker’s data entry. It does need a review threshold. For example, a company may require review of all new products, unusual values, related-party purchases, preference claims and changes to a supplier’s invoice format, while using sampling for routine repeat shipments.
3. Approve exceptions rather than approving every keystroke
High-volume importers often cannot have a finance manager examine every line before accounting. A more workable approach is to define exception rules. A transaction can be routed for review when the classification is new, the value differs materially from the purchase order, the origin changes, the goods are subject to trade-remedy measures, the invoice contains assists or royalties, or the broker cannot match the shipment to an internal purchase record.
The broker’s role is to identify missing information, apply the importer’s instructions and flag issues that require a decision. The broker should not be expected to invent a valuation basis, resolve an unexplained origin conflict or approve a product classification without appropriate importer input.
4. Review the CARM statement as a control report
The portal changes the statement from an external bill to an internal reconciliation source. Finance should compare the CARM activity for the period with the company’s customs entry data, broker reports, freight records and general-ledger postings.
A useful review can answer these questions:
- Does each accounting transaction belong to the correct importer account?
- Can each amount be matched to a shipment, accounting declaration or approved adjustment?
- Do duties and taxes agree with the amounts posted to the customs payable account?
- Are credits, corrections, reassessments or interest items identified separately?
- Are there transactions in the portal that do not appear in the broker’s report?
- Are any items still unresolved at the point the statement is approved for payment?
This is broader than comparing a broker invoice with a purchase invoice. The CARM statement can expose timing differences between release, accounting, correction and payment. The importer’s procedure should state who investigates each difference and how the resolution is documented.
5. Connect customs payment to treasury controls
CARM also makes payment administration an importer process. Treasury or accounts payable should know which account is being paid, what supporting statement or portal record was approved, and how the payment is matched to the company’s liability. Portal access should not be concentrated in one person who can both change account settings and release payment without independent review.
For an importer operating warehouses along the 401 or 407 corridor, the customs liability may be generated by shipments handled at different facilities while being settled through one legal entity. Internal coding should preserve the shipment, business unit or cost-centre detail needed for management reporting without confusing that detail with the legal importer account.
What the customs broker still does
CARM did not make the broker unnecessary. It made the division of responsibility more visible.
Subject to the agreed mandate, a broker may:
- review commercial documents for missing or inconsistent information;
- classify goods using the facts and technical descriptions supplied by the importer;
- prepare and transmit a commercial accounting declaration;
- identify apparent origin, valuation, tariff-treatment or permit issues;
- monitor transaction status and provide accounting or exception reports;
- prepare correction or adjustment information when the importer supplies the basis; and
- help the importer interpret portal activity and organize supporting records.
The broker generally cannot replace the importer’s product owner, buyer, finance approver or record keeper. Classification depends on the goods’ characteristics. Origin depends on production facts and supporting records. Valuation depends on the commercial relationship and terms of sale. The importer is normally the party best positioned to confirm those facts.
A sound service arrangement therefore describes the handoff. It should identify what the importer provides, what the broker checks, which exceptions pause transmission, who approves corrections and how reports are delivered. Without that definition, portal visibility can create more confusion rather than better control.
Failure modes after CARM adoption
Shared logins and unclear authority
When several employees use one login, the importer loses a reliable audit trail. When a broker’s delegation is not reviewed, an old service relationship may remain active after personnel or corporate structures change. Named users, periodic access review and documented delegation decisions address both problems.
Assuming broker transmission means importer approval
A declaration transmitted by a broker is not necessarily a declaration reviewed by the importer. Companies should define whether the broker works from standing instructions, transaction-level approval or an exception-based model. The chosen model should be recorded and supported by product and valuation master data.
Reconciling only broker invoices
A broker invoice may cover service fees rather than the full customs liability. It may also follow a different timing convention from the CARM statement. Reconciliation should therefore use the portal statement and transaction-level accounting information, not just the broker’s billing document.
Leaving corrections with no owner
Corrections can affect duties, taxes, financial reporting and future controls. An importer should record the reason for a correction, the affected transaction, the supporting evidence, the person approving it and the date it was submitted or completed. The broker can prepare the action, but the importer needs ownership of the underlying explanation.
Failing to update master data
If a product description, supplier, origin, tariff classification or valuation assumption changes, correcting one transaction may not fix the next one. The importer should feed confirmed corrections back into its product and supplier records, then tell the broker which instruction has changed.
A workable operating model for GTA importers
A smaller importer in Mississauga may combine customs and accounts-payable duties in one role. A larger importer distributing through Brampton or serving Toronto customers may separate customs operations, finance, procurement and warehouse receiving. Both can use the same basic control design:
| Control point | Importer action | Broker contribution |
|---|---|---|
| Account and authority | Own the legal-entity account, user access and delegation decisions | Support registration and act within the approved mandate |
| Shipment data | Provide complete commercial, product and origin information | Review for gaps and prepare the accounting data |
| Exceptions | Resolve factual, commercial or policy questions | Flag inconsistencies and explain customs implications |
| Statement review | Match portal activity to shipment and ledger records | Provide transaction reports and investigate broker-side discrepancies |
| Corrections | Approve the factual basis and retain evidence | Prepare or transmit the correction where authorized |
The first implementation step is usually not another portal training session. It is a control map showing who owns each decision and which record proves it. The importer can then configure portal access, broker reporting, finance coding and exception queues around that map.
What to retain for an audit-ready file
Importers should generally retain a file that connects the commercial transaction to the customs result and the settled liability. The exact record set depends on the transaction, but a practical file may include the purchase and shipping documents, product classification rationale, origin support, valuation analysis, broker correspondence, accounting declaration details, correction records, statement review evidence and payment confirmation.
The important feature is traceability. A reviewer should be able to start with a CARM statement item, identify the related shipment and commercial documents, understand how the duty and tax result was reached, and see who approved any exception or correction.
Bottom line
CARM changed the importer’s role from receiving customs accounting as a largely finished broker output to managing an accountable control cycle. The broker remains valuable for classification support, document review, transmission and exception handling. The importer, however, needs to own the account, the facts, the approval rules, the statement review and the evidence.
For GTA businesses moving goods through Pearson or into distribution facilities in Mississauga, Brampton and Toronto, the strongest process is the one that links customs data to the same operational records used by procurement, receiving, finance and treasury. That link is what turns portal access into reliable customs accounting.