Unknown Bank Deposit Reconciliation - Review Unmatched Bank Rows Safely
Review unmatched bank deposits when there is no safe order, invoice, or payout explanation yet.
Try with sample files | View sample report
Problem statement
An unknown bank deposit is one of the highest-risk reconciliation states because the cash movement exists, but the supporting source row is still unclear. The right next step is usually to preserve it as reviewable evidence, not to force a classification too early.
Numeric example
| Line item | Amount |
|---|
| Unknown bank deposit | $240.00 |
| Candidate invoice | $240.00 |
| Reference evidence | Missing |
| Review status | Keep open |
Why the numbers do not match
- The bank description may be too weak to identify the source row safely.
- The deposit may belong to a payout batch, grouped payment, or prior-period source row not yet in the file set.
- Customer payments can arrive without the expected order or invoice reference.
- Repeated-value transfers make amount-only matching risky.
- A truly unknown deposit should stay visible instead of being blended into a matched total.
What files to export
- Bank statement export with raw bank description, amount, date, and any reference fields.
- Order, invoice, or payout export with the likely source rows that could explain the bank movement.
- Optional prior-period or adjacent-period export when the deposit belongs to delayed or grouped activity.
Manual workflow
- Start from the bank row and keep its raw description intact.
- Check exact references first, then broader source files for grouped or delayed explanations.
- Use customer, date, and amount signals only as support for review, not as final proof on their own.
- Leave the row in review until the supporting source file is strong enough to defend.
- Export the final report with the unknown bank row still visible if the source remains unclear.
Common mistakes
- Treating an unknown deposit as fraud or error without supporting evidence.
- Using amount-only matching as final proof when several rows share the same value.
- Hiding the row inside a spreadsheet total so it disappears from follow-up.
- Ignoring the possibility that the source lives in another export or period.
How Reconcile Locally helps
- Keeps unknown bank rows separate from matched rows and unpaid source rows.
- Shows likely candidates without forcing a final classification.
- Exports a report where unresolved bank cash stays visible for follow-up.
What still needs manual review
- An unknown bank deposit may stay unresolved until another export is available.
- Weak-reference matches should remain in review even when the amount looks correct.
- Keep the row open when the only evidence is amount proximity or guesswork about the source.
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
Does unknown bank deposit mean fraud?
No. It means the bank row does not yet have a supported source explanation in the available files. Keep it open until the evidence is strong enough.
What if I only have the bank CSV right now?
You can preserve the bank row and review nearby evidence, but safer reconciliation usually needs at least one supporting order, invoice, or payout export before the row can be accepted.