CARM changed the importer’s role in duties-and-taxes accounting by making the importer’s own account, records and payment controls central to the customs process. A customs broker may prepare and transmit information, but the importer generally remains responsible for maintaining reliable records, reviewing accounting results and settling amounts shown on the importer’s account.
For finance teams, the important change is not just a new portal login. It is the need to connect four records that have often lived in separate systems: the commercial transaction, the customs declaration, the CBSA account activity and the company’s general ledger. An importer with warehouses in Mississauga or Brampton and finance operations in Toronto may need one control process that follows goods from entry through period-end close.
The accounting responsibility CARM puts in sharper focus
Customs accounting has always involved more than forwarding an invoice to a broker. The importer’s records need to support the declared tariff classification, origin, value for duty, applicable duties, taxes, relief claims and adjustments. CARM makes the account-level consequences of that work more visible to the importer.
Importers who use a broker generally remain responsible for giving accurate and complete instructions, reviewing information submitted on their behalf and acting on account activity. The broker can apply customs expertise, transmit data and help investigate discrepancies, but the broker’s file is not a substitute for the importer’s books.
That distinction matters because a customs transaction can affect several accounting periods and systems:
- The purchase or inventory system records the commercial transaction.
- The customs entry records the classification, origin, value and border charges.
- The CARM account records assessed amounts, payments, credits and other account activity.
- The general ledger records the company’s expense, inventory, payable, recoverable tax or accrual treatment.
A control failure often occurs between these records. The entry may be correct, but the payment is posted to the wrong period. A revised value may be sent to the broker, but the resulting adjustment is not linked to the original accrual. A statement may be paid, but individual transactions remain unassigned to purchase orders or landed-cost records.
What changed for month-end and year-end close
Under a portal-based account structure, customs activity should be treated as a recurring close process rather than an occasional invoice check. The accounting team generally needs to identify what was accounted for, what was paid, what remains outstanding and what may require an adjustment.
1. Establish the customs population
Start with a defined population of import transactions for the period. Depending on the business, this may come from the enterprise resource planning system, broker transaction files, warehouse-receipt data or customs reports. The population should identify the importer, shipment or transaction reference, entry date, supplier, purchase order and the relevant legal entity.
Do not assume that a carrier invoice or broker invoice is the complete customs population. Brokerage fees, duties, GST or other tax amounts can be represented differently in operational and accounting systems. A control owner should know which report is the starting point and what it excludes.
2. Match customs data to the commercial record
The next control is a transaction-level match. Useful fields can include the customs transaction number, invoice number, purchase order, broker reference, currency, declared value, duty, tax, tariff item and accounting date.
Exact matches are not always possible. Consolidated shipments, split invoices, foreign-exchange conversion and post-entry corrections can create legitimate differences. The objective is not to reject every exception; it is to classify each exception and document who resolved it.
3. Tie activity to the CARM account
The importer’s account activity should be compared with the company’s customs subledger or equivalent schedule. The comparison should identify assessed amounts, payments, credits, corrections and unresolved balances. A balance-level comparison alone can conceal two offsetting errors, so transaction-level support is preferable where the system and volume allow it.
Statements and portal records should be retained according to the importer’s record-retention policy and any applicable customs, tax or corporate requirements. A downloaded report with no explanation of the reporting period or extraction date is weaker evidence than a dated report retained with the reconciliation and sign-off.
4. Post the accounting result
Once the customs amount is matched and reviewed, the finance team can apply the company’s accounting policy. Depending on the goods and the importer’s tax position, duties and taxes may have different treatment from freight, brokerage fees, inventory cost or recoverable tax. The correct treatment depends on the importer’s facts and tax advice; the customs portal does not determine the company’s general-ledger policy.
Where an entry has not yet been finalized in the accounting system but the goods have been received, an importer may need an accrual process. That accrual should be reversed or cleared against the final customs information rather than left as a permanent estimate.
The evidence chain finance teams should be able to produce
A defensible file links the business event to the customs result and then to the accounting entry. It does not require every participant to keep the same document, but it should make the handoff understandable to someone who was not involved in the shipment.
| Control point | Evidence to retain | Question the reviewer should answer |
|---|---|---|
| Commercial transaction | Supplier invoice, purchase order, receiving record and terms | What goods were purchased, by which legal entity and in what currency? |
| Customs declaration | Broker transmission record, accounting data and supporting classification or origin documents | How were value, tariff treatment and tax bases determined? |
| Account activity | CARM account report or statement, payment record and credit or adjustment support | What amount was assessed, settled or changed? |
| General ledger | Journal entry, accrual schedule, clearing record and approval | How did the customs result enter the company’s books? |
| Exception resolution | Written explanation, corrected documents and broker or internal review notes | Why did the records differ, and who authorized the resolution? |
The evidence chain is particularly important when an importer changes broker, legal entity, warehouse, accounting system or payment process. A new broker may be able to access current instructions but not historical explanations. The importer’s own records should therefore preserve the reasoning behind a classification, origin position, valuation method or correction.
Where the broker’s role fits
A broker’s role can be divided into preparation, transmission, interpretation and exception support. For example, a broker may review the commercial documents supplied by the importer, prepare the customs data, transmit an accounting transaction and explain a notice or discrepancy. The broker may also help identify whether a correction appears to involve classification, origin, value, tax, relief or another data element.
The importer’s accounting team still has control responsibilities that a broker cannot perform on the importer’s behalf without the importer’s governance:
- Maintaining the authoritative supplier, purchase-order and receiving records.
- Deciding which legal entity owns the goods and the related accounting entry.
- Approving the company’s accrual, landed-cost and tax treatment.
- Comparing CARM activity with the general ledger and bank or payment records.
- Approving corrections, credits, write-offs and period-end adjustments.
- Retaining evidence that supports the importer’s position.
A practical broker handoff should therefore contain more than a request to “check the entry.” It should identify the transaction, the suspected field or amount, the desired accounting period, the supporting commercial document and the decision required. That gives the broker a defined investigation and gives finance a clear basis for clearing the exception.
Common accounting-control failures after CARM
Using the broker invoice as the customs ledger
A broker invoice may show service fees and amounts advanced or collected, but it may not provide the complete transaction-level evidence needed for customs accounting. Importers generally should reconcile the customs account and underlying entries rather than treating the service invoice as the sole source of truth.
Posting payment without assigning the underlying entries
A payment can reduce an account balance while leaving the company unable to explain which imports it settled. This becomes difficult when one payment covers multiple transactions, legal entities or periods. The payment process should preserve the remittance detail and the allocation method.
Leaving corrections outside the books
A corrected customs transaction can change duties, taxes, inventory cost or an accrual. If the customs correction is handled only in the broker’s system, the company’s ledger may remain inconsistent with the account activity. Corrections should be routed to both customs and accounting owners, with a defined posting or clearing action.
Confusing a portal message with a completed accounting action
A notification, report or statement may identify an issue, but it does not by itself prove that the importer reviewed the issue, approved a response or posted the result. The close file should show the action taken and its status.
Relying on one person’s portal access
Access should reflect job responsibilities and segregation of duties. The person who prepares or reviews customs data may not be the person who releases payments or approves a journal entry. Importers should also maintain an internal process for access changes when staff leave or responsibilities move.
A workable ownership model for GTA importers
A company with a distribution operation in Brampton or Mississauga may have receiving staff, customs staff, accounts payable and corporate finance using different systems. Toronto-based finance personnel may see the account balance while warehouse teams hold the documents needed to explain a discrepancy. A simple responsibility matrix can prevent the portal from becoming another isolated data source.
- Procurement or receiving: confirms the goods, supplier documents, purchase order and receipt.
- Customs: reviews classification, origin, valuation instructions and broker exceptions.
- Broker: prepares or transmits agreed customs data and investigates defined customs questions.
- Accounts payable: controls invoice matching, payment support and allocation.
- Finance: owns the close, ledger treatment, accruals, approvals and management reporting.
The names may differ by organization. What matters is that every customs amount has an owner, every exception has a due date and every correction has a path into the ledger.
How to implement the control without rebuilding every system
- Document the data flow. List where commercial, broker, CARM and ledger data originate, who changes it and where it is retained.
- Choose a transaction key. Use a consistent combination of references that can connect the customs record to the purchase order, shipment and legal entity.
- Define the close population and cut-off. Record how goods in transit, recently released goods and late corrections are treated for the period.
- Create an exception queue. Categorize differences by missing document, timing, amount, classification, origin, valuation, payment or system mapping.
- Set escalation rules. Send questions involving a possible customs correction to the customs owner and questions involving ledger treatment to finance.
- Test the process. Select transactions from different suppliers, ports, currencies and warehouses. Confirm that a reviewer can reconstruct the result without relying on informal knowledge.
- Review the control periodically. Changes to suppliers, tariff treatment, broker instructions, ERP mapping or CARM users can alter the reliability of the process.
The result should be a repeatable audit trail, not a second manual version of every customs system. Automation can help with matching and exception reporting, but the importer still needs documented rules for unresolved differences and corrections.
What importers should ask before the next close
- Can we identify every customs transaction included in this period’s duties-and-taxes balance?
- Can we trace each significant amount from the commercial document to the customs record and ledger entry?
- Do payment records show which account activity was settled?
- Are open corrections visible to both the customs and finance owners?
- Can the broker explain the customs data, while our team explains the accounting treatment?
- Would a new reviewer understand the file without relying on a former employee’s mailbox?
CARM does not remove the need for broker expertise. It changes where control must sit. The importer’s finance, customs and operations teams need a shared view of the customs account, while the broker needs complete instructions and a defined route for exceptions. When those roles are connected to the company’s own books, duties and taxes become an auditable part of the close instead of a balance that is explained only after a problem appears.
Sources