Bank reconciliation software should do more than match lines. On every statement it should prove the statement foots, flag duplicates and numbering gaps, show how sure it is about each line it read, and export the evidence. If it forces a balance to agree, it hides the problem you are paying it to find.
What should bank reconciliation software check on every statement?
Bank reconciliation software should run a fixed set of tests on every statement before it reports anything as reconciled. The minimum is a footing test, a continuity test against the prior statement, a duplicate test and a gap test. Each test answers a question a reviewer would otherwise ask by hand.
The feature checklist
The table maps each feature to the audit question it answers. Use it as a buying checklist: if a feature has no row here, ask what question it answers. PreciseBankFlow's checks appear in the last column as one example, not as a ranking. PreciseBankFlow is in early access, so the column describes what it is built to do, not a record of results.
| Feature | The audit question it answers | What good looks like | PreciseBankFlow example |
|---|---|---|---|
| Footing test | Does opening plus deposits less withdrawals equal the printed closing balance? | Pass or fail, with the difference shown | Marks a statement out of balance and shows the difference |
| Continuity test | Does this statement open where the last one closed? | Compares closing to the next opening | Not listed on the homepage, so ask |
| Duplicate detection | Was anything charged or posted twice? | Rules shown, candidates listed for a person to confirm | Flags same payee, same amount, close dates |
| Gap detection | Is a line missing? | Check number sequences and unexplained differences checked | Points to the line that should be there |
| Confidence scores | Which extracted lines might be misread? | A score on each field, sortable | A score on every extracted field |
| Exception list | What needs a human decision? | Each item with its evidence | Differences, duplicates and gaps with supporting lines |
| Export | What goes in the workpaper? | Reconciliation, exceptions and source lines | Excel and PDF workpapers |
Why the order matters
The footing test comes first because every later test depends on it. If the lines do not add up to the closing balance, a line is missing, misread or invented, and matching the rest only produces a confident answer on a wrong base. The arithmetic of that test is worked through in footing each bank statement, opening plus activity equals closing.
What a tool should not need from you
A good tool should run these checks without configuration. If a vendor says each test is available once you "set it up", ask which ones run by default. A test that only runs when someone remembers to enable it will not run on the statement that matters.
Bank reconciliation software that flags differences instead of adjusting
Bank reconciliation software should never force a reconciliation to balance. When the numbers differ, the tool should report the difference and the lines that might explain it. Adjusting, plugging or auto-writing off a difference makes a report look finished while the underlying error is still there.
What forcing a balance looks like
Some tools offer a one-click "adjust" that posts a correcting line equal to the difference. In a ledger, an adjustment is a normal action when you know the cause, such as an unrecorded bank fee. The problem is a tool that creates the entry without a cause, because the difference now looks resolved. Three shapes are common:
- A plug line. An added line named "difference" or "adjustment" that brings the totals together.
- A rounding sweep. A small tolerance that absorbs differences under a set amount, with no list of what was absorbed.
- An automatic write-off. The difference is posted to an expense or suspense account on its own.
What flagging looks like
A tool that flags a difference marks the statement out of balance and keeps it that way until the lines are fixed. It then does the useful work: it looks for a statement line whose amount equals the difference, because one missed or doubled line produces exactly that difference. For example, a statement that is out by 1,250.00 may contain a withdrawal of exactly 1,250.00 that was read twice. The amounts here are an example only. Showing that candidate saves the hour you would have spent scanning.
A question for the demonstration
Ask the vendor to open a statement with a deliberate error and show what the tool does. Watch whether the status stays red, whether the difference is displayed and whether any entry was created. The answer to "did it change anything?" should be a plain no.
Confidence scores and vouching in bank reconciliation software
A confidence score is the tool's own estimate of how reliably it read a field. Low scores mark the lines to vouch, which means to compare against the source document, before you rely on them. Scores do not prove a line is right, but they tell you where to look first.
How to use the scores
Sort the extracted lines by score and start at the bottom. A line with a low score on its amount deserves a look at the PDF. A line with a low score on its description may not matter at all if the amount and date are sound. Scores work best as a way to order your checking, not as a pass mark.
What scores cannot do
A high score can still be wrong. A tool can read a clear digit confidently and still misplace it. This is why the footing test and the scores belong together. The score picks out the lines likely to be wrong, and the footing test confirms whether the total is wrong. If a statement foots and the low-score lines check against the PDF, you have two independent reasons to trust it.
A sensible vouching routine
- Run the footing test. If it fails, find the cause before anything else.
- Sort by confidence and vouch the lowest-scoring lines to the PDF.
- Vouch any line that is large, round or unusual for the account, whatever its score.
- Record which lines you vouched, so the reviewer can see the work.
Without the fourth step your reviewer cannot tell a line you checked from one you did not.
Exports a bank reconciliation program should give your workpapers
A bank reconciliation program should export the reconciliation, the exceptions and the source lines that support them, in files your workpapers can hold. A report that lives only on a vendor's screen is not evidence. Look for Excel and PDF output that opens without the vendor.
What the export should contain
- The reconciled lines, with date, description, amount and balance, so the reader can re-add them.
- The footing result, showing opening balance, deposits, withdrawals, computed closing balance and printed closing balance.
- The exception list, with each difference, duplicate or gap and the evidence for it.
- Source references, so each line can be found on the original page.
- Preparer and reviewer details, with dates, where the tool records them.
Excel and PDF do different jobs
Excel suits a reviewer who wants to re-sort, re-total or select a sample. PDF suits the permanent file, because its content does not change when someone opens it. A tool that offers only one forces you to convert the other yourself, which is where mistakes enter. Check both with a real statement before you buy.
A test for the export
Take one exported reconciliation and hand it to a colleague who has not seen the tool. Ask them to re-add the totals and find one source line on the original statement. If they can do both in a few minutes, the export is good enough for a workpaper.
Can bank reconciliation software read scanned statements?
Many bank reconciliation tools can read scanned statements, but accuracy is lower than on digital PDFs and varies with scan quality. A scan can lose a decimal point, merge two lines or misread a digit. Expect to check more lines by hand on scanned input, and let the confidence scores and the footing test tell you where.
What affects accuracy
- Resolution and skew. A tilted or low-resolution page is harder to read than a flat, sharp one.
- Handwriting. Notes written on a statement are read poorly, if at all.
- Faded or shaded columns. Light print on a tinted background loses digits.
- Multi-page layouts. A running balance that breaks across pages is easy to mis-order.
No honest vendor can give you one accuracy figure for scans, because it depends on your documents. Do not accept a percentage without a test on your own files. PreciseBankFlow reads both digital and scanned PDFs and attaches a score to each field, but it is in early access, so test it on your own scans like any other tool.
How to handle a bad scan
Ask for a better copy first. A digital statement from the bank's own site is almost always cleaner than a scan of a printout. If a scan is all you have, treat every low-score line as unvouched, and keep the footing test as the final gate. A scan that does not foot is not ready to rely on.
When bank reconciliation software is the wrong fix
Bank reconciliation software is the wrong fix when the problem is the process, not the speed of matching. If entries are posted late, nobody owns the reconciliation or the books are missing whole months, a tool will report the mess faster without clearing it. Fix the process first, then automate it.
Problems a tool will not solve
- No owner. If nobody is assigned to the reconciliation, the report will sit unread.
- Late posting. Transactions entered weeks after the fact create timing differences that no matching rule explains.
- No separation of duties. The person who handles cash should not be the only person who reconciles it. Software can record a reviewer but cannot make one exist.
- Missing statements. If a month is absent, the continuity test will say so, but someone still has to get the statement.
- A weak chart of accounts. If cash is spread across several accounts with unclear purposes, reconciling any one of them stays confusing.
The right order
Settle who prepares and who reviews, agree a deadline, and get every statement in the folder. Then pick a tool for the volume that is left. For a firm working across clients, reconciliation software for accountants running engagements explains what to look for beyond the checks above. And if matching rules are your main question, how one-to-one, one-to-many and many-to-many transaction matching works comes next.
If you want to see these checks on a statement of your own, you can request a place in early access.