Cashbook and Bank Reconciliation Evidence
Explain two account balances with explicit matched groups, timing items, bank-only entries and corrections.
Loading tool…
How to use Cashbook and Bank Reconciliation Evidence
Enter openings and the complete dated movements in each record set. Declare equal-sum matches and unmatched classifications, apply signed corrections to their named side, and keep unresolved items visible even when they cancel numerically.
- Use the example as the schema; replace its labels and entered model assumptions.
- Enter openings and the complete dated movements in each record set. Declare equal-sum matches and unmatched classifications, apply signed corrections to their named side, and keep unresolved items visible even when they cancel numerically.
- Calculate, inspect the complete witnesses and limitations, then copy or download the JSON report.
Good to know
- At most 200 book and statement movements together, 100 explicit match groups and 50 corrections. Each kind has distinct IDs. All movement dates fall in the inclusive openingDate/asOf range, Gregorian 1900–9999. Openings, movements and corrections are signed exact cents within ±1,000,000,000.
- Each matched-classified movement must be in exactly one same-sum group. Book-only timing movements adjust bank; statement-only unrecorded movements adjust book. Explicit corrections add their signed value only to the selected side and require a reason.
- Ready requires equal adjusted balances and no unresolved rows, including net-zero unresolved pairs. User-supplied classifications/corrections can make numbers balance without proving identity or accuracy. No import, automatic/fuzzy match, posting, banking access, cash transfer, audit/fraud assurance or accounting-standard certification.
- Local calculation with no upload, input persistence or outside lookup. Model JSON is limited to 30,000 characters and 10,000 values. Decimal quantities are strings with up to six places; count fields use plain JSON integers. Exact fractions are capped at 8,192 bits. The complete JSON output is limited to 1,000,000 characters; approximate numbers preserve their stored values. Unsupported states fail explicitly.
Common questions
Does a zero difference prove that the account records are correct?
No. Explicit classifications, matches and corrections can produce equal totals while source records are wrong. Ready only means this entered evidence is fully classified and arithmetically balanced. It does not authenticate a statement, prove transaction identity or replace an accounting review.
Are my model inputs saved or sent to a server?
No. This model runs in the current browser tab and creates a local JSON download. It does not save your input or call an external data service.
Keep going with related tools
All calculators →Invoice Line Rounding and Reconciliation
Inspect exact invoice bases, per-line or per-rate tax rounding, and a discrepancy against your entered total.
CalculatorsCustomer Receipt Allocation Ledger
Apply customer receipts to invoices with exact partial balances and visible unapplied credit.
CalculatorsDated Cash-flow Balance Planner
Build a calendar-day closing-balance schedule from supplied signed cash movements and an opening balance.
DataIBAN Format and Checksum Checker
Check one IBAN or a local list against pinned national formats and exact MOD97 arithmetic. Preserve original lines and download complete JSON or spreadsheet-protected CSV evidence.
FilesOFX XML Statement Exporter
Export posted bank or credit-card transaction source rows from a selected local OFX 2.x XML file without changing amount, date or ID text.
CalculatorsCash Drawer Shift Reconciliation
Reconcile opening and closing denomination counts with actual cash tender, change, refunds and drawer transfers, keeping ticket discrepancies visible.