The CARM Client Portal changes the accounting handoff between a Canadian importer and its customs broker. A broker may continue to prepare and transmit customs information on the importer’s behalf, but the importer’s organization generally remains responsible for understanding the resulting Customs Accounting Declaration (CAD), monitoring the account, arranging payment and retaining the records that support the duties and taxes reported.
That distinction matters because a broker’s transmission of an entry is not the same as the importer’s approval of the accounting result. Under the CARM model, the importer has a direct account relationship with the Canada Border Services Agency (CBSA) through the portal. The broker is an authorized service provider within that relationship, not the owner of the importer’s customs liability.
The accounting handoff CARM creates
Before CARM, many importers experienced customs accounting primarily through broker entry packages, daily transaction reports and periodic invoices. Those documents still have operational value, but the portal introduces a separate importer-facing account structure. The importer can generally see customs declarations, amounts assessed, payments, account statements and available account functions in the Client Portal.
The core change is not simply that customs documents became electronic. It is that several decisions that were often handled informally around the broker invoice now need an identified owner inside the importing business.
- Access: someone in the importer’s organization needs to manage the portal account, user permissions and delegation relationships.
- Accounting review: finance or trade-compliance staff need to connect the CAD and related account activity to the purchase, shipment and general-ledger records.
- Payment: the importer generally needs a controlled process for reviewing amounts due and ensuring that the selected payment arrangement is funded.
- Corrections: discrepancies in classification, origin, value, tariff treatment or tax treatment need to be identified and routed for correction.
- Evidence: the importer needs to retain the commercial and customs records that support the accounting declaration.
These functions can be performed with broker assistance, but they cannot safely be treated as a single outsourced “entry filing” task. A broker can identify an error, prepare a correction or explain a statement. The importer generally still needs to decide whether the underlying commercial facts are correct and whether the proposed accounting treatment matches its records.
How a transaction moves through the portal
1. The broker prepares the declaration
The process usually begins with shipment information supplied by the importer, seller, carrier or another party in the supply chain. The broker may use that information to prepare a CAD containing the data required to account for the goods. Depending on the transaction, that can include tariff classification, country of origin, value for duty, tariff treatment, duties, GST and other applicable amounts.
The importer’s first control point is before transmission: the information supplied to the broker should be complete, current and tied to an identifiable purchase or shipment. Product descriptions copied from a packing list may not be sufficient for classification. Commercial invoices may not show every fact needed to establish origin or value. A repeat-product database can also preserve an old assumption after the product, supplier or transaction terms have changed.
2. The declaration is submitted under the importer’s account relationship
When a broker submits a declaration under a delegation arrangement, the importer generally should treat the transaction as its customs accounting record, not merely as a broker document. The importer may not prepare the technical declaration itself, but it should have a method for matching the declaration to internal records.
A practical match may use the importer’s purchase order, commercial invoice, shipment reference, receiving record and broker transaction reference. The objective is to establish which goods were imported, which customs declaration accounted for them and which amount eventually appeared in the importer’s account activity.
3. The portal account records the financial result
After accounting activity is posted, the importer’s review should extend beyond the broker’s invoice. The Client Portal account and account statement provide the basis for checking what was assessed, what was paid or credited and what remains outstanding. The broker invoice may include service charges, disbursements or other commercial amounts that are not identical to the customs account activity.
This is an important reconciliation point. An importer may have a correctly calculated broker invoice but an incorrect customs declaration. Conversely, a CAD may be correct while an internal payment allocation or broker disbursement record is wrong. The importer’s process should distinguish customs amounts from brokerage charges and from the company’s own payable entries.
4. The importer reviews and corrects exceptions
Errors do not all have the same source or remedy. A missing invoice may require a document update. An incorrect tariff classification may require technical review across a product family. A value-for-duty error may involve assists, royalties, packing, freight or other elements of the transaction. An origin or tariff-treatment issue may require supplier evidence rather than a simple data edit.
Importers generally should give the broker a documented exception rather than an informal request to “fix the entry.” The request should identify the declaration, the disputed data element, the proposed correction, the reason for it and the supporting evidence. The broker can then determine the appropriate correction process and whether related transactions should be reviewed.
What the importer should own inside its accounting process
Portal access and delegation
The portal account should be treated like a controlled financial system. Importers generally benefit from assigning separate responsibilities for administration, customs review, accounts payable and management oversight. A user who can manage business account permissions does not necessarily need authority to approve every customs accounting decision.
Delegation records also deserve periodic review. When a broker relationship ends, when staff change roles or when an outside service provider no longer needs access, the importer should have a process for removing or changing access. The question is not only whether the broker can submit declarations; it is whether the current delegation reflects the importer’s actual operating model.
Statement-to-ledger reconciliation
A useful reconciliation does more than compare a total monthly customs statement to a total broker invoice. It separates at least three layers:
| Layer | What to compare | Typical exception |
|---|---|---|
| Shipment record | Purchase, receiving and commercial documents against the CAD | Wrong quantity, product, supplier or invoice value |
| Customs account | Assessed duties and taxes, credits, adjustments and payments against portal activity | Unmatched amount or payment allocation |
| General ledger | Customs amounts, recoverable tax treatment, payable entries and disbursements | Broker charge combined with customs liability |
The exact frequency depends on shipment volume, payment terms and the importer’s risk tolerance. High-volume importers may use automated matching and investigate exceptions continuously. A smaller importer may perform a periodic review, provided it can still identify the underlying declaration and supporting documents when an issue appears.
Cash and payment controls
The portal makes payment status an importer-facing operational concern. Importers generally should know which account is used for customs payments, who monitors amounts due, how payment confirmation is recorded and what escalation occurs when an amount does not reconcile.
Using a broker’s disbursement service can simplify individual shipments, but it does not remove the need to understand the customs account. Where the importer uses the Release Prior to Payment program, financial security, release privileges and payment timing should be reviewed as part of the importer’s own cash-control process. The broker may assist with release activity, but the importer remains exposed to the consequences of an underfunded or poorly monitored account.
Where GTA importers commonly encounter friction
For an importer receiving goods into a Mississauga or Brampton warehouse, customs accounting may involve several separate operational records: an air or highway arrival, a receiving transaction, a broker entry package, an accounts-payable invoice and a portal statement. Toronto-based finance or procurement teams may be reviewing the customs result even though the goods are physically received elsewhere in the GTA.
The physical location does not determine who owns the accounting review. A centralized finance team should still be able to obtain product-level classification support, supplier origin evidence and the declaration reference from the warehouse or customs team. If records remain divided between a Pearson-area broker file, a Peel Region warehouse system and a Toronto head office, unmatched transactions are more likely to remain unresolved.
A workable control does not require every warehouse employee to use the portal. It does require a defined handoff: receiving identifies the shipment, the broker provides the declaration reference and accounting result, finance matches the amount, and trade compliance investigates exceptions. The portal is the common account record, while the company’s systems provide the commercial and financial context.
Common failure modes and the broker’s role
“The broker paid it, so the importer is finished”
A broker may advance or arrange funds as part of its service, but that does not establish that the importer’s classification, value, origin or tax treatment was correct. A broker can provide transaction details and explain how an amount was calculated. The importer generally needs to perform the business-side review and retain evidence.
“The portal total should equal the broker invoice”
Customs duties and taxes, broker service fees, disbursements and other charges can be different accounting categories. The broker can help map its invoice to customs transactions, but the importer’s ledger should preserve those distinctions rather than forcing them into one amount.
“A correction is only a broker data-entry issue”
Some corrections are clerical. Others change the legal or financial basis of the declaration. A broker can assess the available correction route and prepare supporting material, but it generally needs accurate facts from the importer. Repeated errors in one product family should trigger a broader review instead of isolated transaction edits.
“Portal access is an administrative task”
Unreviewed users, outdated delegations and unclear approval rights can interfere with payment monitoring and correction decisions. Importers generally should include portal administration in their customs-control review, with documented ownership and a process for staff turnover.
A practical operating model
An importer that wants the portal to support, rather than disrupt, its accounting process can establish a short transaction workflow:
- Assign an owner for portal administration and an owner for customs-account reconciliation.
- Maintain a current product and supplier data set for classification, origin and valuation review.
- Require broker transaction references to flow into receiving and accounts-payable records.
- Match CAD information and portal account activity to the commercial shipment before closing the payable item.
- Separate customs duties and taxes from brokerage fees and other service charges in the ledger.
- Route disputed entries through a documented exception process that records evidence and the correction decision.
- Review delegation, payment arrangements and unresolved exceptions on a defined schedule.
The broker remains important in this model. A broker can classify goods based on supplied facts, prepare and transmit declarations, explain customs account activity, identify patterns in errors and support correction work. The importer’s role is to provide reliable commercial information, approve the business facts, control its account relationship and connect customs activity to its own books.
CARM therefore changes the importer’s role from receiving a completed broker transaction to operating a visible customs-accounting process. The strongest result comes when the Client Portal, broker records, warehouse data and general ledger are treated as connected records with different purposes—not as interchangeable versions of the same invoice.
Frequently asked questions
Does CARM eliminate the need for a customs broker?
No. Importers may continue to authorize a broker to prepare and submit customs declarations. CARM changes the importer’s direct account relationship and control responsibilities; it does not prevent the importer from using broker expertise.
Is the broker responsible for every error on a CAD?
Responsibility depends on the facts, the service arrangement and the source of the information. A broker may be responsible for its own work, but the importer generally remains responsible for the accuracy of the commercial facts and for addressing customs-account obligations associated with its imports.
Should accounting reconcile to the broker invoice or the Client Portal?
Both may be needed, but they serve different purposes. The portal and customs records support the customs-account side of the reconciliation. The broker invoice supports the commercial service and disbursement side. The importer’s ledger should show how the amounts relate.
What should an importer do when the portal amount does not match internal records?
Identify the declaration and isolate the mismatch before requesting a correction. Compare the commercial invoice, shipment and receiving records with the CAD and account activity, then ask the broker to review the specific data element and correction path. A general total mismatch is harder to investigate than a documented transaction exception.
Sources and further reading
For current program details, importers should consult the applicable CBSA material and confirm how their broker and accounting systems implement the requirements.