The month-end pack that explains itself.
We match your ledger export against the source-system export. Every difference gets a reference, a rule and an amount. Material items wait for a person. Nothing is marked reconciled until someone signs it off.
The totals are close. That is not the same as reconciled.
Month-end reconciliation usually ends with a difference nobody can explain and a hunt through two files. The missing row, the duplicate, the twelve-dollar mismatch and the sync that stopped nine days ago are all invisible in a totals check.
- A difference without a list is a mystery. The pack shows that it does not tie, but not why.
- Material items get treated like noise. A 2,450 missing row and a 12 rounding difference arrive with equal weight.
- The sign-off is verbal. Nobody can reconstruct who accepted which difference, or when.
The difference arrives with its reason attached.
Every finding carries the reference, the side it came from, the amount it affects and a plain description. Material findings become a sign-off queue with a decision and a timestamp. The close pack is a Sheet you own, not a hunting exercise.
Four steps, and a person still signs off.
The checks are code. They do not post journals and they do not change your ledger.
It comes in
A short form sets the period, the materiality threshold and which source system is being compared.
Two extracts
The ledger and the source export are normalised to one shape: reference, date, amount, currency, counterparty.
Checks run
Duplicate references, rows present on one side only, amount tolerance, stale sources and sign errors.
You get the ones that matter
Each finding is ranked by impact. Anything above the threshold becomes a pending sign-off, with an audit row.
A close pack with the differences already named.
Period, row counts, matched references, findings and variance, written once per run.
Every difference with reference, rule, side, severity and amount. Sortable, filterable, readable.
Material findings only, each waiting for a named decision and a timestamp.
The period's numbers in the inbox, with a pointer to the evidence rather than the whole sheet.
If a run breaks, the email names the workflow and the step. A partial run cannot pass as a closed month.
The checks are code, documented, so the next person can see why something was flagged.
Built and run, not a slide.
Run RC-778025, period 2026-09: 41 ledger rows, 40 source rows, 39 matched references, 5 findings, 2,682.00 CAD of variance explained, 2 material items waiting for sign-off.
findings, each named
matched references
CAD variance explained
check tests passing
Demo environment · sample data · tested on 23 October 2026. Read the case study.
What it does not do.
- It reads, it does not post. No journals, no ledger changes. The output is findings and sign-offs for the person who owns the close.
- The extracts must exist. If the source system cannot export a row-level file, the comparison needs a different input first.
- Rules catch mechanics, not judgement. A finding can be real and still acceptable. That decision stays with you, and it is recorded.
- One company per install. Multi-entity closes are a bigger build, not a setting.
Start with one period.
Fixed price, agreed in writing before we start. The first audit is deliberately small: two extracts and one period, so you see the findings before you commit to a monthly process.
- Matching rules written down
- Findings list with reference, rule and amount
- Material items queued for sign-off
- Run record and summary email
- Everything in Starter
- Sign-off decisions recorded per item
- Written rules and handover notes
- A walkthrough of the first close
Starter is a fixed price. Standard is quoted after your first audit, against the periods, extracts and sign-off loop you need. Prices in USD. Ongoing monthly close audits are quoted per month. No per-row fee and no subscription.
What we need before we quote an audit.
- One period's ledger export and the source-system export for the same period.
- The reference that should match the two files, and any known exceptions to it.
- The materiality threshold: the amount above which a difference must reach a person.
- Who signs off, and where the decisions should be recorded.
The ones we get asked.
Where does our data go?
Does it change our accounting software?
What if our exports do not line up by reference?
Can it run every month?
Send one month.
Send the period, the two extracts and the threshold you care about. We will tell you what the checks would catch before you commit to a build.
Demo environment · sample data · fixed-price audit quoted after the extracts are seen.