Bank statement reconciliation software should prove that a client's run of statements is complete, tie each month's opening balance to the prior month's close, read scanned and multi-account PDFs without silent errors, and hand clean data to the next tool. Judge it on those points with your own clients' statements, not on a vendor's demo file.
Does the reconciliation software prove the statement run is complete?
Reconciliation software proves a statement run is complete when it checks, for every account, that each statement's opening balance equals the previous statement's closing balance and that the periods meet without a gap. If it cannot say "March is missing for account XXXX-4821," it is matching lines, not proving completeness.
Completeness is the first requirement because every later step depends on it. A perfect match of eleven months still leaves a twelfth month unexamined. The software should know how many statements to expect for each account and period, and report the shortfall in plain terms.
Ask to see three things on your own files:
- A deliberate gap. Remove one month from a client's set and upload the rest. The software should name the missing period and the account.
- A balance break. Use a set where one month's opening balance does not equal the prior close, such as a statement from a different account mixed in. The software should flag the break, not average over it.
- An overlap. Upload a statement twice, or two statements with overlapping dates. The software should treat the repeat as a duplicate, not as extra activity.
How firms find and chase a gap by hand, and what the client is asked for, is covered in missing bank statements: find gaps in a run.
Completeness also covers accounts nobody mentioned. Software that lists every account number it found across a client's uploads makes it easier to notice a savings account that appears in a transfer description but never sent a statement.
Statement reading accuracy in reconciliation software
Statement reading accuracy in reconciliation software means pulling the right date, description, amount and running balance from every line, including on scanned pages and PDFs that hold several accounts. Test it yourself on hard files. A tool that reads clean bank PDFs well can still misread a skewed phone photo or merge two accounts into one run.
No vendor's general claim tells you how a tool handles your clients' statements, so build a small test set. Include:
- A clean digital PDF downloaded from a bank's website, as the baseline.
- A scanned paper statement, slightly skewed, with a fold line across the page.
- A phone photo of a statement page taken on a kitchen table.
- A combined statement that holds a checking and a savings account in one PDF.
- A long statement of twenty or more pages with transactions continuing across page breaks.
- A statement with a credit balance or overdraft, where the running balance goes negative.
For each file, check the extracted totals against the statement's own summary box. Total deposits, total withdrawals and the closing balance are printed on most statements. If the extracted lines do not add up to the printed totals, the tool should say so before you do.
What matters most is how the software behaves when it is unsure. A good tool marks a line it could not read with confidence and asks for review. A weak one fills in a plausible amount and moves on. The first costs a minute; the second costs a reconciliation that will not tie, found weeks later.
Multi-account PDFs need their own check. The software should split the checking and savings sections into separate accounts with separate runs. If it treats them as one account, every balance tie-out after that point is wrong.
Export and handoff from bank reconciliation software
Export and handoff from bank reconciliation software is where the checked data leaves the tool and enters the ledger, a spreadsheet or a tax workpaper. The output should keep the account, period and source statement on every row, open cleanly in Excel or import as CSV, and not create duplicates in the system that receives it.
Questions to settle about the export:
- Format. Excel and CSV are the common minimum. Check that dates come out as dates, amounts as numbers and negative amounts in one consistent form.
- Columns. Each row should carry the account identifier, statement period, transaction date, description, amount and running balance, so rows from different accounts can sit in one sheet.
- Traceability. A row should point back to the statement and page it came from, so a reviewer can check it.
- Repeat exports. Exporting the same month twice should not produce a file that, once imported, doubles the month.
That last point matters most when the destination is accounting software with a bank feed. Intuit's help article Fix duplicate transactions in QuickBooks Online bank feeds lists importing "a file that overlaps with your bank feed" as one cause of duplicates. An export that states its exact date range makes overlap easier to avoid.
Converting statements into spreadsheet rows is a subject of its own; the guides in bank statements to Excel cover formats, columns and conversion methods in depth.
What questions should you ask a reconciliation software vendor?
The questions to ask a reconciliation software vendor are the ones a polished demo avoids: what happens with your worst files, how it reports what it could not do, where the data goes, and what it costs at your page volume. Bring your own statements and ask for answers you can test, not descriptions.
Questions that expose weak spots:
- "Show me what happens when I upload eleven months for an account. What does the screen say?"
- "How does the tool tell me a line was read with low confidence?"
- "What happens when one PDF holds two accounts?"
- "If a client uploads the same statement twice, what do I see?"
- "Which export formats exist today, and which connections are planned but not available?"
- "What does the export look like if I run the same month twice?"
- "Is pricing per client, per firm, per page or per account, and what happens in a heavy month?"
- "Does the tool give accounting or tax advice, or does it prepare data for the firm to judge?"
The fifth question deserves a careful listen. A product roadmap is not a feature. Write down what exists today and buy on that.
A 10-point buyer's checklist
Use this checklist during a trial. Fill in the result column with Pass or Fail from your own test files. The results below are blank on purpose; they are for your evaluation.
| # | Requirement | How to test | Pass or Fail |
|---|---|---|---|
| 1 | Flags a missing month by account and period | Upload a set with one month removed | |
| 2 | Ties each opening balance to the prior close | Mix in one statement from another account | |
| 3 | Treats a repeated upload as a duplicate | Upload the same statement twice | |
| 4 | Splits multi-account PDFs into separate runs | Upload a combined checking and savings PDF | |
| 5 | Reads scanned pages and phone photos | Upload a skewed scan and a photo | |
| 6 | Checks extracted lines against printed totals | Compare against the statement summary box | |
| 7 | Marks uncertain lines for review | Look for flags on the hardest file | |
| 8 | Exports Excel and CSV with account and period columns | Open the export and sort by account | |
| 9 | Leaves a review trail back to the source page | Click from a row to its statement | |
| 10 | States clearly what it does not do | Ask about connections, advice and roadmap items |
How this kind of software fits next to the ledger's own reconcile screen is covered in which two reconciliation tools a firm should pair.
Reconciliation software red flags for accounting firms
Reconciliation software red flags are claims or gaps that should end an evaluation: a headline accuracy number with no test behind it, no way to flag a missing month, exports that need retyping, or features described as available that turn out to be planned. Any one of these means the tool will create work a firm has to catch later.
Red flags to watch for:
- Accuracy numbers without a method. A percentage on a sales page says nothing about your clients' scans. Ask how it was measured, on what files, and test anyway.
- Silence about gaps. If the demo never shows a missing statement, ask why. Completeness is the first thing a firm needs.
- "It just matches everything." Matching every line is easy when lines are missing. Ask what the software does with a month that has no statement.
- Roadmap features in present tense. A connection or report "coming soon" is not part of what you are buying.
- No export you can open. Data that only lives inside the tool cannot go into a workpaper or another system.
- Advice it should not give. Software that suggests how a client's items should be treated for tax purposes is stepping beyond reading statements.
Analysis features are a different purchase. Software that summarizes cash flow or spots recurring payments answers other questions; see bank statement analysis software for what that category does.
Where Schema CPA fits in bank statement reconciliation
Schema CPA fits at the start of bank statement reconciliation: it reads the checking, savings and loan statements clients upload, ties each month's balance to the month before, and calls out any gap in the run. It exports Excel or CSV. It does not connect to QuickBooks or Xero, so matching in a ledger happens after import.
In checklist terms, Schema CPA speaks to items 1 to 3 and to the file format in item 8: it flags a missing month, checks balances month to month, flags a second copy of a document as a duplicate instead of counting it twice, and produces Excel or CSV output. Run the rest of the checklist on it with your own files, as you would for any tool. It reads statements alongside every other document type a client sends, so bank statements, W-2s and receipts arrive through one upload link per client.
Statement reconciliation is part of the Practice plan, listed at $499 a month for up to 20 staff and 10,000 pages, with plans priced per firm rather than per client; the full list is on the Schema CPA pricing section. It gives no accounting or tax advice. The firm still decides what every flagged item means for its client. To run the checklist on your own statements, Get started.