Close each CARM Statement of Account with a reconciled variance packet
Saxum reconciles the monthly SOA against customs declarations and broker records, reconstructs carry-forward balances, and routes only unresolved differences for importer or adviser review.
No CARM portal credentials are required. Saxum does not replace customs advice or authorize account payments.
Current operating snapshot
CBSA’s CARM environment provides importer account and payment information. The recurring control problem is not portal access itself; it is reconciling account statements against declarations, broker records, prior-period debits, credits and payments before the customer acts on the balance.
A monthly account balance is not a reconciliation
An importer can see the closing amount and still lack a defensible explanation of how it was formed. Historical debits, unallocated credits, duplicate broker records and timing differences can carry into later periods.
Best-fit customer
Customs advisers and finance teams managing importer accounts, plus Canadian importers with recurring declarations
Useful source systems
CARM SOA exports, customs declaration records, broker statements and payment-ledger extracts.
Three bounded populations
The control works when each source is preserved separately before mapping.
- CARM Statement of Account export
- Importer declaration or CAD transaction export
- Broker invoice or transaction record
- Opening balance and known payments or credits
- Customer-approved column mapping
A monthly packet that explains the balance
The output separates reconciled entries from facts that still need an importer, broker or customs adviser.
- SOA-to-declaration match register
- Broker-to-importer variance worklist
- Duplicate and missing-transaction register
- Opening-to-closing balance bridge
- Carry-forward debit and credit schedule
- Source-linked executive control report
- Signed evidence manifest and cycle receipt
From source exports to a reviewable account close
Unsupported amounts remain unresolved instead of being converted to zero or inferred from another source.
Map
Identify account, transaction, amount, type and date fields in each source.
Reconcile
Match current-period entries and reconstruct opening-to-closing movement.
Investigate
Group duplicates, missing declarations, broker differences and carry-forward items.
Close
Release the packet only after material variances are resolved, waived or assigned.
Reconcile monthly CARM accounts across importer clients
Keep importer accounts segregated while reusing declaration/broker mappings, carry-forward controls and variance review across the advisory team.
Segregated accounts
Each customer, entity or operating unit keeps separate source evidence, mappings, exceptions and outputs.
Reusable controls
Approved mappings and review policy reduce repeat setup without allowing one client's assumptions to leak into another.
Portfolio oversight
Firm teams can see recurring due work, unresolved exceptions and evidence-backed outcomes without flattening client boundaries.
Show the buyer exactly what Saxum proved
The first controlled cycle produces customer-visible proof before the workflow is expanded. Saxum keeps internal completion separate from external/provider acceptance and never turns estimates into verified outcomes.
Source coverage
See which files, mappings and authority sources were used, what was missing and which assumptions remained unresolved.
Exception register
Every blocker has a reason, owner and current state. Unsupported facts remain open instead of disappearing into a generic pass.
Evidence-graded scorecard
Separate Saxum-completed work from provider-final evidence, verified value, source-backed exposure, observed time savings and estimates.
Use it as a recurring importer account control
The strongest fit is a repeat monthly close, not a one-time historical recovery project.
Onboarding covers source mapping and a controlled baseline. Monthly service covers intake, reconciliation, exception routing and the signed close packet.
Request a CARM control assessment →CARM SOA Control FAQ
No. The workflow uses exported records or a customer-controlled connector.
No. Saxum identifies mechanical differences and preserves evidence; customs judgments remain with the importer and its adviser.
It separates and carries forward historical debits and credits when the source records support them.
The difference becomes a source-linked exception. It is not silently netted away.
Yes. Saxum supports segregated client accounts, mappings and review queues.
Verify the account framework
The official sources remain authoritative and should be rechecked before each engagement.
Primary-source review date: 12 August 2026. Re-check before each engagement.
Continue the control layer
Bring one real monthly account
Describe the sources, account structure and monthly volume. Do not send credentials or regulated data through the public form.
See the workflow before you bring customer data
Every executable Saxum product now has a synthetic first-cycle walkthrough. Where a free checker or guide exists, it is linked here too.