Match Bank Statements to Bookkeeping
Bank records and books view one account through separate systems. A defensible match uses the same cutoff, linked evidence, and a schedule for genuine timing differences.
Create a portable CSV with one record for each posted transaction and stable columns covering descriptions, dates, balances, credits, debits, review notes, categories, and confidence.
Choose CSV for portable row data when formulas, workbook styling, and multiple sheets are unnecessary.
posted_on,bank_text,outflow,inflow,running_balance,review_status 2026-10-02,"Sample payroll",,2620.00,4112.40,check 2026-10-04,"Sample rent",1450.00,,2662.40,checkIllustrative structure, not uploaded data.

Your statement is being secured before analysis begins.
Leave this window open; your private results will load here when ready.
CSV suits database loading, scripts, bookkeeping staging, and tools that need rows rather than workbook formatting. It carries plain tabular values without formulas, multiple sheets, styling, or a built-in summary page.
The format does not dictate how receiving software handles dates, decimals, delimiters, encoding, or blanks. Verify mapping settings; an upload success message does not prove that fields landed correctly.
Quote and encode source descriptions consistently so punctuation and non-English characters neither split records nor become corrupted. Keep debit separate from credit and retain blank balances when the statement prints none.
Specify the date format and identify source currency wherever multiple currencies could be mistaken. An ambiguous day and month cannot acquire a year without period evidence.
Load a small sample before the full dataset and compare its opening, middle, and final records with both CSV and statement. Verify row count, field mapping, directions, decimals, leading zeros, long references, and embedded line breaks.
After complete loading, recalculate controls within the destination. Retain the source CSV and a mapping record so the import can be reproduced without hidden settings.
Imagine a quoted CSV description reading "MARKET, CENTRAL". Software that ignores quotes divides it into two fields and shifts every following value; testing five rows exposes this mapping failure before full loading.
Once delimiter and quoting rules are corrected, compare row count, debit and credit controls, and the opening and closing records across systems. File size and upload status are not reconciliation evidence.
Bank records and books view one account through separate systems. A defensible match uses the same cutoff, linked evidence, and a schedule for genuine timing differences.
The purpose of reconciliation is to account for every difference at one cutoff. Removing difficult entries merely creates agreement without evidence.
A workbook becomes reliable when every row can be traced to the statement. Its controls must demonstrate complete capture and make corrections visible.
Learn how the transaction entries and their uncertainty are retained before the receiving system applies its field rules.