Universdaxu · Reconciliation Toolkit
Reconciliation and exception handling, in practice
Bank reconciliation is where errors surface, and it is the work most often rushed at month-end. This toolkit covers how to run reconciliation cleanly, what to do with the transactions that do not match, and the controls that catch problems before your accountant does.
Matching work, one page at a time
The one number that matters
A short exception list is the goal. Not a zero-exception one — every unmatched line is a question waiting for a judgment call.
What reconciliation is actually proving
Reconciliation proves that your ledger balance and your bank statement balance agree, and it explains any difference. That is the whole job. The work lives in the differences: a missing transaction, a duplicate, a payment that cleared in a different month, a bank fee nobody recorded.
When you reconcile, you are not only matching numbers. You are confirming that every transaction in the ledger is real and every transaction on the statement is accounted for. Skip the explanation step and you have matched a balance without proving anything — which is exactly the month-end position nobody wants to defend to an owner or a lender.
What the explanation has to cover
- Every ledger line traced to a real statement line.
- Every statement line either matched or written down as a difference.
- A reason attached to each remaining difference, not just a note that it exists.
- A decision recorded for anything that needed a second opinion.
Bank reconciliation automation shortens the matching step. It does not remove the explanation step, and no tool should be asked to.
Setting up a bank feed that stays clean
The quality of reconciliation depends on the quality of the feed. Connect every account, including the ones you rarely use, because dormant accounts hide transactions nobody is watching. Re-authenticate when your bank prompts you — a broken feed does not announce itself, it just stops delivering lines.
Reconcile on a fixed schedule, ideally weekly, so the list stays short. A weekly reconciliation takes minutes; a quarterly one takes a day. The frequency matters more than which tool you use.
Feed habits that hold
Connect once, then check the feed before you start matching. If a connection dropped, the missing lines arrive late and land in the exception list instead of the clean run.
Transaction matching rules worth setting
Matching rules pair bank lines with ledger entries based on amount, date, and vendor. Rules work well when the vendor name is consistent, and they struggle when the bank description is generic — an undifferentiated debit line — or when one vendor bills under several names.
The practical fix is a vendor alias list: map every bank description to the correct vendor once, and matching improves from there. This is unglamorous work, and it is the difference between a short exception list and a long one. Set your rules on amount plus a narrow date window first, then layer vendor aliases on top; a rule that matches on description text alone will misfire the first time the bank changes its wording.
Rule settings, by reliability
Building an exception queue
An exception queue is a list of transactions that did not match, with the context needed to resolve them. It should be a specific place — not a mental note, not a cell in a spreadsheet that only one person opens.
Each item should show the bank line, the closest ledger entry, and the reason it did not match. The person resolving it should be able to mark it done with a note. Keeper is an example of a tool built around this pattern, cited by Xenett as part of the automated reconciliation software category. The queue is the workflow; the tool just holds it.
Each queue item carries
- The bank line, exactly as it arrived.
- The closest ledger entry, so nobody re-searches it.
- The reason it did not match, in plain words.
- Who resolved it, when, and with what note.
The five exception types you will see most
Most exceptions fall into a few categories. Each type has a standard resolution, and documenting them turns exception handling from a scramble into a routine.
Timing differences
The transaction is real but sits in the wrong period. Confirm the date on both sides, then post it to the period it belongs to instead of the one that looks tidier.
Duplicates
The same payment recorded twice. Check whether the bank also posted it twice before you delete anything — reversing the wrong copy creates a new exception.
Missing entries
A bank fee, an interest charge, a service charge nobody recorded. These are quick to fix and easy to forget, so record them the same day you see them.
Amount mismatches
A payment that came in short, usually after fees or a partial credit. Decide whether the difference is a cost of doing business or something to chase, and write the decision down.
Unmatched deposits
Money in the bank with no corresponding invoice. Hold it until you know what it is; guessing at the customer is how a clean ledger gets a wrong name on it.
A worked example, start to finish
A monthly software charge arrives three days after the period closed. It matches an existing ledger entry on amount and vendor, but the date lands in the next month. Mark it a timing difference, leave the ledger entry where it is, and note the period on the queue item. When the next statement arrives, the line matches without a second look — and the explanation is already written for anyone who reviews the account later.
Controls that catch problems early
Three controls make the biggest difference, and none of them require expensive software. They require the discipline to run them every month, in the same order, whether or not anything looks wrong.
Reconcile on a schedule, not at month-end
A weekly pass keeps the exception list to a handful of lines. Waiting until the close turns reconciliation into a project with a deadline attached to it.
Second review on manual journal entries above a set amount
Pick a threshold you can defend, write it down, and apply it without exceptions. The review is cheap; the correction after a closed period is not.
Lock prior periods once they are reconciled
A locked period stops someone from posting into a month that has already been reviewed and signed off. If you need a correction, you make it visible instead of silent.
Choosing between reconciliation tools
The market splits into two kinds of tools, and the split matters more than the feature lists. If your problem is the matching work, a reconciliation tool is the fit. If your problem is coordinating a multi-person close, a close platform is.
Reconciliation-focused
Matching and exception queues
Tools in this group handle matching, exception queues, and the reconciliation workflow itself for bookkeeping teams, often across multiple clients. Keeper is the example cited by Xenett in the automated reconciliation software category. Choose this when the recurring pain is the volume of unmatched lines and the time spent pairing them.
Close management platforms
Task tracking around the close
Platforms in this group include reconciliation as part of a broader close workflow with task tracking and controls. FloQast is cited by Xenett as a reconciliation automation example, and it sits in the close-automation category rather than basic bookkeeping. Choose this when several people have to hand work to each other before the period can close.
The question to ask first
Write down where the time actually goes. If most of it disappears into matching bank lines to ledger entries, a reconciliation-focused tool addresses the cause. If it disappears into chasing people for status, the close platform does. Buying the second when you have the first problem adds a tool without removing the bottleneck.
Where this leads
Once you know which problem you have, the next pages cover the close itself and the rollout that keeps the process honest.
A weekly reconciliation routine
A routine that works: Monday morning, review the bank feeds for the past week. Match what you can and move the rest to the exception queue. Resolve anything straightforward, and flag anything that needs a decision from the owner or the accountant. Friday, check the queue again to make sure nothing is aging.
At month-end, the reconciliation becomes a review of work already done rather than a fresh project. Teams that run this routine close faster and with fewer surprises. The routine is the automation, in a sense; the software just makes it easier to follow.
The week, in two passes
Monday
Review feeds, match what matches, queue the rest, resolve the easy ones.
Friday
Walk the queue, chase what is aging, confirm nothing is waiting on a silent decision.
Month-end
Review finished work and lock the period. No new matching project.
Questions bookkeepers ask
Short answers to the three questions that come up most often when a team sets up a reconciliation routine.
How often should I reconcile my bank account? Open Close
Weekly is the practical sweet spot for most small businesses. It keeps the exception list short and catches feed problems early. Monthly works if your volume is low, but the work is less pleasant and the queue is longer by the time you open it.
What is an exception queue? Open Close
A specific list of transactions that did not match during reconciliation, with enough context to resolve each one. It is a workflow pattern before it is a feature, and some tools such as Keeper are built around it.
Can I automate reconciliation completely? Open Close
No. Matching can be automated for clean transactions, but exceptions require judgment — someone has to decide what a short payment or an unexplained deposit means. The goal is a short exception list, not a zero-exception one.
Start with the routine
Pick one account and reconcile it this week
The toolkit is only worth anything once it is running on a real account. Choose the busiest one, connect the feed, set the matching rules you can defend, and open a queue for whatever does not match. Then do it again next Monday. If you would rather see the wider workflow first, start with the basics or ask us a question directly.
Reach us
452 Maple Avenue, Suite 200, Chicago, IL 60607, USA
+1-312-558-5102 · [email protected]
Monday–Friday: 9:00 AM – 6:00 PM