Invoice to Bank Reconciliation Example
A bank-first walkthrough showing partial, grouped, and unresolved invoice matching against one transfer.
Try with sample files | View sample report
Problem statement
An invoice export and a bank statement may not line up one to one. The example shows how a reviewer handles partial payments, two invoices in one transfer, and unknown remainder rows without hiding the uncertainty.
Numeric example
| Line item | Amount |
|---|
| Invoice INV-401 | $500.00 |
| Invoice INV-402 | $300.00 |
| Customer transfer | $650.00 |
| Matched amount | $650.00 |
| Carry-forward balance | $150.00 needs review |
Why the numbers do not match
- One customer transfer can pay several invoices at once.
- A partial payment can settle only part of an invoice and leave a carry-forward balance.
- The bank description may be too weak to prove a final match by reference alone.
- A remaining gap may only be an amount difference until another file confirms the cause.
What files to export
- Invoice export with invoice ID, date, customer, balance, and paid status.
- Bank statement export with transfer amount, date, and any customer or reference text.
- Optional payment register or notes when the bank description is weak and the invoice support needs another reference source.
Manual workflow
- Normalize the bank export and extract any invoice or customer references from the description.
- Match exact references first, then review grouped-payment and partial-payment candidates.
- Apply the customer transfer across the supported invoices without hiding the unpaid remainder.
- Keep carry-forward balances and unknown remainder rows visible in review.
- Export a final report with matched rows first and unresolved balances separate.
Review checks
- Forcing one bank transfer into a one-invoice match when it likely covers several invoices.
- Marking an invoice fully paid when only a partial transfer is supported by the bank row.
- Hiding the unpaid remainder instead of carrying it forward explicitly.
How Reconcile Locally helps
- Keeps invoice rows, bank rows, grouped-payment candidates, and carry-forward balances in one report layout.
- Separates clear matches from duplicates, unknown deposits, and open amount differences.
- Makes the handoff cleaner than a spreadsheet where notes and formulas are mixed together.
What still needs manual review
- Very weak bank references can still require manual confirmation or another support export.
- The walkthrough does not replace downstream approval of write-offs, credits, or accounting entries.
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
What should happen to the unpaid remainder in the example?
It should stay visible as a carry-forward or open balance until another payment or approved adjustment explains it.
Should grouped invoice payments be forced into one-to-one matches?
No. The safer approach is to keep grouped-payment reasoning explicit and preserve any unresolved remainder separately.