Ask any bookkeeper what they trust least in their accounting software and you’ll hear the same answers: the bank feed that breaks at month-end, the duplicates that appear when it reconnects, the “reconciled” checkmark that turns out to mean nothing, and the undo button that either doesn’t exist or punishes you for using it. Bank reconciliation is the oldest workflow in accounting software — and somehow still the most complained about.
We just finished rebuilding ours, end to end. Here’s what we built, and the standard we held it to.
A reconciliation is only worth what its green checkmark means. Ours means one thing: every line was verified, the balance foots, and nothing is quietly wrong underneath.
Item-level truth, not balance-level hope
Most tools call a month reconciled when the balance ties. But two offsetting errors tie to the penny — a missed $500 deposit and a missed $500 payment net to zero, and a totals-only check waves them both through. In Caytava, a month is green only when every statement line is matched to a book record, every book record is cleared or explained, and the balance foots. If any of that isn’t true, the month says so — with the exact rows that need a decision, each carrying the control that resolves it.
And where the system can’t verify item-by-item — a hand-keyed balance with no statement behind it — it doesn’t pretend. It asks the human to sign off, records who and when, and the sign-off is the green. Verified by the system, or attested by a person: never silently assumed.
Reconciliation that runs all month
The matching engine doesn’t wait for month-end. Every bank line that arrives is matched against your ledger the moment it lands — exact matches, date-window matches, group matches (three vendors paid the same amount on the same day is a Tuesday, not an edge case), transfers between your own accounts, net-of-fee deposits. By the time you open the month, the work left is the work that genuinely needs judgment. Payments settle the oldest open invoice by default, the way remittance processing is supposed to work — unless the bank memo names a specific invoice, which always wins.
Months with no activity verify themselves — but only on positive evidence: a live feed that demonstrably ran past month-end and returned nothing, chained to a verified prior month. “No data” is never read as “no activity.” That distinction is the difference between automation and wishful thinking.
An undo that forgives
In most tools, unmatching is where good intentions go to die: one platform permanently excludes unmatched lines from ever auto-matching again; another can only undo by deleting the entire statement — along with the period’s reports. We think changing your mind is part of accounting. In Caytava, Unmatch releases the pair, both sides return to open work, and the system remembers the rejection so it never silently re-makes the match you just said was wrong. Change your mind again? Your manual match overrides the memory. Every step audited, nothing destroyed, nothing punished.
Feeds that repair themselves
The industry’s dirtiest secret is that nobody has solved bank feeds — reconnecting an account duplicates history, identical same-day charges get silently merged, and pending-charge cleanup is your job. We built for the mess: when a feed reconnects, we count what’s already there instead of guessing, so three real $608.44 payments stay three; you can re-read a statement as many times as you like without making a mess or paying twice; pending charges that settle are cleaned up automatically; and when a bank connection breaks, the account tells you — it doesn’t just quietly stop syncing.
Ask the ledger why
Because reconciliation state lives in the ledger — not in a bolt-on workspace — Kate can read it. Ask why a month doesn’t foot and the answer isn’t a shrug; it’s the specific rows, with drafts ready for the ones that need an entry. And like everything Kate does, she suggests — a person approves before anything touches the books. AI that never posts without you is the only AI an accountant should trust with cash.
Sign-off, the way a real firm runs it
When every line is settled and the balance ties, someone marks the month reconciled — and if your team is big enough to care who, you can require two signatures: the preparer marks it done, and a reviewer signs off before it’s final. Different person, enforced by the system, with both names on the record. Running solo? Flip that off and one click closes the month. Big-firm controls when you want them, zero ceremony when you don’t.
The lock at the end
When the month is done, lock it. The lock is a real integrity guarantee — every edit path refuses, the audit trail records the close, and next month opens on the locked balance. And if something new lands in a locked month, the lock doesn’t hide it: the month reopens, visibly, and tells you what changed. A green that can quietly become wrong is worse than no green at all.
The whole module is live today, for every Caytava company, included — not a separate reconciliation subscription bolted on top of your ledger. It is the ledger.