Bank reconciliation is monthly for exactly 1 reason: a person had to do it, and a person cannot do it every day.
Nothing about the underlying task requires a monthly cadence. Money moves continuously. Statements arrive continuously. The ledger records continuously. The only element that ever needed batching was the human sitting between the statement and the books, matching lines by eye, and the monthly rhythm was built around that person's capacity rather than around the work.
Remove that constraint and the natural cadence of reconciliation is the same as the cadence of the transactions. Which is to say: constant.
agent dedicated to clearing the bank, holding its own identity and audit trail
days to close at Tillo, with reconciliation among the tasks that stopped accumulating
of the journal population available to an auditor through the API, reconciliation entries included
What a month of unmatched transactions costs
The expense of a monthly reconciliation is not the matching. It is the age of the evidence.
A payment that lands today matches its bill in seconds, because the bill is recent, the reference is intact and the amount is unambiguous. The same payment matched on day 26 requires somebody to work out what a round number from a vendor with 4 open invoices was actually settling. Multiply by a few hundred transactions and the exercise stops being reconciliation and becomes archaeology.
Everything that makes reconciliation hard is a function of delay. Partial payments, batched settlements, FX differences on the receiving side, fees netted off the transfer, refunds that arrive without reference. All of them are tractable on the day and expensive a month later.
Continuous, and attributable
The Bank Rec Agent clears the bank against live feeds as transactions arrive. It carries its own principal, so every match it makes is tracked against that identity rather than disappearing into a shared service account, and each run shows what it matched and on what basis.
It sits alongside the rest of the workforce doing the same thing to adjacent work. The Bill Agent codes bills as they arrive and routes them by policy. The Accrual Agent books month-end entries. Astra, the always-on analyst, watches what agents and humans post and raises what needs attention. None of them save work up, which is the mechanism behind a close that shortens rather than a close that gets better project managed.
Tillo's close fell from 12 days to 5. Reconciliation was among the tasks that stopped accumulating.
The exceptions still reach a person. That is the correct division. A genuinely ambiguous payment needs judgment, and there are far fewer of them when the ambiguity is 4 hours old rather than 4 weeks.
Old model
Match in a batch
Statements import, a person works the unmatched list at month-end, and the hardest items are the oldest ones.
Light's model
Match on arrival
The Bank Rec Agent clears against live feeds continuously under its own identity. Exceptions surface the same day, while the context still exists.
What changes
Cash position is current
The bank is reconciled today rather than as of last month-end, so the cash number the business acts on is the real one.
The reporting consequence
A month-end reconciliation means the cash position is trustworthy once a month and an estimate the rest of the time. Most finance teams have quietly accepted this and built around it, running a separate cash view in a spreadsheet for the questions that arrive between closes.
Continuous reconciliation removes the second system. The ledger is the cash position, today, which is the precondition for the sort of question a CFO actually gets asked: what is our runway, can we cover this commitment, what did we actually spend with that vendor this quarter. Those are trivial questions against reconciled books and guesswork against a ledger that is 3 weeks stale.
The audit position
Reconciliation is a standard control and auditors test it as one. The traditional evidence is a reconciliation document: a point-in-time artefact showing the balance agreed as at a date, prepared by a person, reviewed by another.
On an immutable ledger with an agent doing the matching, the evidence is the record itself. Every match is attributable and timestamped, every correction is a new entry referencing the original rather than an edit in place, and audit agents verify the work continuously against policy, producing a monthly control report of what was checked, what passed and what was flagged. Auditors at customers with $500M ARR have completed engagements against exactly this.
Reconciliation stopped being a monthly event because the reason for the month disappeared. What is left is a control that runs every day and proves it ran.
See the agents that run the close, or book a demo.