Manual Bank Reconciliation in Excel: Match Bank Statements with Invoices and Orders
Manual bank reconciliation in Excel for matching bank statements with invoices, orders, payout exports, and clear spreadsheet review steps.
Try with sample files | View sample report
Problem statement
Manual reconciliation becomes fragile when bank rows, order rows, and invoice rows are copied into separate sheets without a clear status model or review process.
Numeric example
| Line item | Amount |
|---|
| Invoice INV-1042 | $1,240.00 |
| Bank deposit | $1,240.00 |
| Invoice INV-1047 | $890.00 |
| Bank deposit with amount difference | $864.20 |
Why the numbers do not match
- Dates and amounts use inconsistent formats.
- References are buried inside bank descriptions.
- Matched and unmatched rows are mixed together.
- Formula results are overwritten during manual review.
- There is no audit trail for why a row was accepted.
What files to export
- Bank CSV/XLSX with date, amount, description, debit or credit, and reference fields.
- Orders or invoices export with reference, date, customer, and expected amount.
- Optional payout export with payout IDs, fees, refunds, and net amounts.
Manual workflow
- Create separate tabs for bank rows, source rows, and review output.
- Normalize dates and signed amounts.
- Extract references from bank descriptions into a helper column.
- Run exact reference matching first.
- Use amount and date matching only as a fallback.
- Assign every row a status: matched, review, unmatched, or ignored.
- Export a final report with matched rows first and review rows next.
Common mistakes
- Mixing matched, review, and unmatched rows in the same manual filter view.
- Using amount-only matching as if it were final proof.
- Overwriting formulas during review without keeping a separate audit column.
- Posting spreadsheet output to accounting before unresolved rows are clearly separated.
How Reconcile Locally helps
- Takes the spreadsheet column logic and turns it into a repeatable local review flow.
- Keeps matched rows, review rows, and unmatched rows separate instead of manually sorting them.
- Preserves source row context so the report is easier to audit later.
What still needs manual review
- Excel-only workflows get fragile once references are messy or one deposit maps to several source rows.
- Amount-only matching should stay in review until a human confirms it.
- Grouped settlements and partial payments still need an explicit reviewer decision.
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
Can Excel be enough for reconciliation?
Yes, if the file volume is small and the matching rules are simple. The process becomes harder when references are messy or payouts include fees and refunds.
What is the most important spreadsheet column?
Status. Every row needs a clear status so matched, review, and unmatched items do not get mixed together.