Bank CSV Reconciliation Template
Free template structure for reconciling bank CSV/XLSX exports with orders or invoices.
Try with sample files | View sample report
Download the working files
Problem statement
Bank CSV/XLSX files come in inconsistent formats, and manual matching becomes fragile when signed amounts, references, and review states are not normalized into one repeatable layout.
Template example
| Line item | Amount |
|---|
| Bank date | 2026-05-04 |
| Signed amount | $517.82 |
| Expected source amount | $549.82 |
| Open amount difference | $32.00 |
Why the numbers do not match
- Some banks provide one signed amount column while others split debit and credit into separate fields.
- Descriptions may hide or truncate the invoice ID, order ID, or payout reference you need.
- Several rows can share the same amount and date, so a safe template needs an explicit review state.
- A lower bank amount may only prove an amount difference until another export confirms the exact cause.
What files to export
- Bank statement CSV/XLSX with dates, descriptions, signed amounts or debit-credit columns, and references.
- Orders, invoices, or payout export with dates, references, and expected amounts.
Manual workflow
- Export the bank statement.
- Export the source file.
- Normalize dates and amounts.
- Extract references.
- Match with strict evidence first.
- Keep open rows visible.
- Export the final review package.
Common mistakes
- Using debit and credit columns without converting them into a stable signed amount.
- Overwriting the raw description after extracting a reference from it.
- Treating amount-only candidates as final instead of keeping them in review.
- Mixing matched, review, unpaid, and unknown rows in the same spreadsheet block.
How Reconcile Locally helps
- Takes the cleaned bank CSV layout and turns it into a repeatable local review flow.
- Separates matched rows, review rows, unpaid items, and unknown bank payments into clear report sections.
- Keeps grouped payments and amount differences visible in the exported report.
- Preserves the raw file workflow without uploading financial data to a server.
What still needs manual review
- Truncated descriptions can still require a human to confirm the final source row.
- Grouped deposits and amount-only candidates should stay in review until the evidence is stronger.
Content review and sources
Written and reviewed by the Reconcile Locally product team. Last reviewed June 7, 2026.
Guidance is checked against current product behavior and first-party documentation where available. Reconciliation results still require human review.
Frequently asked questions
Should I keep debit and credit columns if the bank already gives me a signed amount?
You can keep them for audit purposes, but matching is usually safer when one final signed amount column is used throughout the review workflow.
When should I say amount difference instead of fee?
Use amount difference whenever the source exports do not prove the exact cause. You can note a possible fee, refund, tax, timing difference, or payout adjustment, but keep the row in review until the data confirms it.