Bank Statement Reconciliation Checklist: 7 Checks Before You Import
Use a bank statement reconciliation checklist to catch balance, duplicate, and sign errors before CSV or XLSX imports hit your books.
Bank Statement Reconciliation Checklist: 7 Checks Before You Import
A bank statement export can look fine and still fail the only test that matters: does it reconcile cleanly after import?
When CSV or XLSX output is headed into bookkeeping, the checklist has to come before the ledger. It is faster to catch a broken balance, duplicate row, or sign error in the export than to unwind a bad close later.
Why a reconciliation checklist matters
Every import assumes a few things are true:
- the opening balance rolls forward correctly
- the closing balance matches the final row
- transaction signs are consistent
- no rows were lost, duplicated, or merged
- the statement period did not drift during cleanup
If any of those assumptions fail, the import may still run, but the books are now harder to trust.
The 7 checks
1. Opening balance continuity
Confirm the opening balance ties to the prior period or source statement. If the first number is wrong, every later number is suspect.
2. Closing balance tie-out
The closing balance should match the final running balance after normalization. If it does not, something changed during extraction or cleanup.
3. Running balance sequence
Check that each row still makes mathematical sense after OCR or export. This is where missing lines and merged transactions usually show up first.
4. Duplicate and reversed transactions
Look for accidental duplicates, repeated refunds, and reversal pairs that should not both remain in the final export.
5. Date range and period boundaries
Make sure the export stays inside the statement period you intended. One wrong boundary can make the whole file look off by a month.
6. Debit and credit sign rules
A clean export is not just rows in columns. The sign convention has to stay stable so downstream bookkeeping does not misread inflows and outflows.
7. Row count versus source file
The row count should be explainable. Big gaps usually point to OCR problems, parsing issues, or manual edits that skipped validation.
Where ParseMyStatement fits
Use ParseMyStatement when you need statement data that survives the move from PDF into CSV, XLSX, or JSON.
If you are choosing the fastest route into the product, start with the tools page. If you want the workflow and terminology first, the guides are the better entry point. For developer-heavy flows, the developers page and API docs make the handoff explicit.
Related reading:
- Bank Statement Balance Validation: Catch Opening and Closing Mismatches Before Import
- Bank Statement JSON Export for API Workflows
- What a Bank Statement Normalization API Should Return
What to avoid
Do not trust a file just because it opens cleanly in Excel.
Avoid:
- skipping the balance check because the columns look right
- mixing manual fixes with OCR output and not revalidating totals
- exporting before the period boundaries are confirmed
- treating a passable CSV as if it were already bookkeeping-safe
FAQ
What is the most important reconciliation check?
The closing balance tie-out is usually the fastest way to spot whether the export still matches the source statement.
Should I validate before CSV or XLSX export?
Yes. Validate before import and before you hand the file to accounting.
Why does a checklist matter if the tool already converts the file?
Because conversion and reconciliation are different jobs. A file can convert correctly and still be wrong for bookkeeping.
FAQ
What is the most important reconciliation check?
The closing balance tie-out is usually the fastest way to spot whether the export still matches the source statement.
Should I validate before CSV or XLSX export?
Yes. Validate before import and before you hand the file to accounting.
Why does a checklist matter if the tool already converts the file?
Because conversion and reconciliation are different jobs. A file can convert correctly and still be wrong for bookkeeping.