What Should a Reconciliation Report Include
A practical standard for what a reconciliation report or package should contain before client handoff or accounting review.
Try with sample files | View sample report
Problem statement
A reconciliation report is weak when it shows only a summary total, hides open items, or omits the source-file evidence needed to reproduce the review. A useful package has to separate what is final from what is still open.
Minimum report sections
| Line item | Amount |
|---|
| Matched rows | Accepted evidence first |
| Needs review | Open but plausible rows |
| Unknown bank payments | No safe source explanation yet |
| Carry-forward or in-transit items | Explicit next-period schedule |
What a useful reconciliation report needs
- Matched rows should come first so the accepted evidence is clear.
- Needs-review rows should stay visible instead of being collapsed into an adjustment line.
- Unknown bank deposits, unpaid source rows, duplicate candidates, and grouped-payment cases need their own sections or labels.
- The report should preserve the review notes and source-file context behind open items.
What the package should include
- Reviewed report output with matched, review, unknown, unpaid, duplicate, and amount-difference sections.
- Supporting exports such as bank, payout, invoice, order, or activity files.
- Reviewer notes for unresolved rows, carry-forward balances, and next actions.
Report standard
- Start with the review scope: account, period, and files used.
- List matched rows first, then review rows, then unresolved or carry-forward sections.
- Preserve row-level references, amounts, dates, and notes needed to reproduce the review.
- State clearly what remains open instead of assigning unsupported causes.
- Include next actions for unresolved items before the package is handed off.
Recommended report sections
- Scope and date range
- Matched rows
- Needs-review rows
- Unknown bank payments
- Unpaid invoices or orders
- Amount differences, duplicate candidates, and grouped-payment candidates
- Carry-forward or in-transit schedule
- Reviewer notes and next actions
How Reconcile Locally helps
- Exports matched rows first, review rows next, and unresolved cases separately.
- Keeps report wording aligned with the methodology and editorial policy.
- Supports a cleaner handoff than a workbook where notes and formulas are mixed together.
What still needs manual review
- The report standard improves evidence quality but does not approve accounting entries or replace final reviewer sign-off.
- Different teams may need extra tax, entity, or ledger attachments outside the core reconciliation package.
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 a reconciliation report include unresolved rows?
Yes. A strong report separates open items clearly instead of hiding them. Review visibility is part of the evidence package.
Do I need the source exports with the report?
Usually yes. The report should be reproducible from the supporting files and notes, especially when it is handed to another reviewer.