Trust & accuracy
Deterministic matching first. AI only comments, with citations.
Every reconciliation decision in InNumber comes from rules you can read and reproduce. This page sets out exactly what the engine does, what our accuracy numbers mean, and where we are in SOC 2 preparation.
Match determinism
100%
Same inputs, same output — no model decides a match.
Auto-match rate
98.7%
Measured on our 500,000-row synthetic ledger with seeded breaks.
Throughput
~12,000 rows/sec
In-browser, single laptop, measured on the same dataset.
AI-created matches
0
AI never matches, posts or clears. It only comments with citations.
These figures are measured on our own synthetic demo ledger, not on customer data, and will vary with your data quality, tolerance settings and reference hygiene. They are performance measurements, not an assurance opinion.
How the matcher works
Pass 1 — exact reference match
Ledger and subledger rows are bucketed by normalised reference and matched when the amount agrees within your tolerance. Fully deterministic: the same inputs always produce the same pairs.
Pass 2 — amount band + date window
Unmatched rows are bucketed by amount and paired with the nearest counterpart inside your date window. Ties break on the smallest date distance, then the smallest amount difference.
Pass 3 — many-to-one aggregation
Split payments and batched deposits are grouped by counterparty and matched as a set against a single ledger entry. Available on Team and Scale.
US GAAP reconciliation pack
The free pack installs these checks as editable heuristic rules. Thresholds are yours to change — nothing is hidden inside a model.
| Reference | Check | What it flags |
|---|---|---|
| ASC 305 | Cash tie-out | Bank balance vs general ledger cash; unreconciled differences above your tolerance are raised as breaks. |
| ASC 310 | Receivables subledger agreement | AR subledger total vs GL control account, with ageing movement flagged for review. |
| ASC 405 | Payables subledger agreement | AP subledger total vs GL control account, including unposted invoice batches. |
| Suspense | Clearing and suspense accounts | Any residual balance in suspense, clearing or intercompany accounts is flagged for clearing before sign-off. |
| Flux | Material movement review | Period-over-period movement beyond your percentage and absolute thresholds is queued for explanation. |
US GAAP reconciliation pack
Balance-sheet reconciliation heuristics aligned to the ASC topics most often challenged in a US GAAP close: cash, receivables, payables, accruals, suspense clearing and revenue cut-off.
IFRS reconciliation pack
Reconciliation heuristics aligned to IFRS presentation and measurement requirements: cash, financial instruments, ECL-bearing receivables, provisions, FX retranslation and revenue cut-off.
The packs are aligned to common US GAAP and IFRS reconciliation practice. They are advisory tooling, not an audit, and InNumber does not issue accounting opinions.
SOC 2 preparation
InNumber is not SOC 2 certified today and has not completed an audit. This is an honest status board of what is already in place and what is still ahead.
Data scoped to a single workspace, no cross-tenant reads in the reconciliation engine
In place
Reconciliation runs execute in your browser; ledger files are not required to leave the device for matching
In place
Every engine run is written to an append-only run log with actor, timestamp and parameters
In place
AI review is restricted by policy scope, requires citations and is rejected server-side without them
In place
Formal access-control, onboarding and offboarding policies documented
Planned
Vendor risk register and subprocessor list published
Planned
Continuous control monitoring and evidence collection tooling in place
Planned
Type I readiness assessment with an independent auditor
Planned
Type II observation window completed
Planned
See the rules run on your own numbers
The free reconciliation check runs the US GAAP pack on one entity and one period. No card required.