CARM SOA
A synthetic CARM Statement of Account representing the monthly account balance and transaction population.
Synthetic product walkthrough
CARM SOA reconciliation
A synthetic importer statement is reconciled against declaration, broker, payment and prior-period records to explain the account balance before customer action.
Synthetic inputs
See exactly what enters the control
No customer, provider or production data is used in this demonstration.
Declaration/CAD records
Synthetic declaration/CAD records used to match assessed activity to the account statement.
Broker/payment ledger
A synthetic broker and payment ledger used to reconcile payments, credits and operational postings.
Scope42 entries
Findings5 variances
OutputReconciled SOA
Controls exercised
- Opening-balance roll-forward
- Declaration matching
- Payment/credit matching
- Broker variance detection
- Customer-action worklist
Synthetic findings
- One synthetic declaration appears on the SOA without a matching customer-side ledger record.
- Two broker payment entries do not match the supplied account posting population and remain open variances.
- The opening-balance roll-forward exposes a residual difference rather than forcing the account to balance.
Proof boundary
What this demonstration proves
The demo proves account reconciliation and variance evidence on synthetic records.
What it does not prove
It does not change CBSA records, make customs judgments or prove a provider-side correction.
Bring a real cycle →Evaluate the workflow before onboarding
The synthetic walkthrough shows the shape of the control. A real assessment tests your sources and exceptions without silently granting provider authority.