What Auditors look for in Reconciliation Reports

Auditors rely on reconciliation records to verify that internal accounting matches external statements, bank records, or partner reports. A clear, well-documented reconciliation report reduces review time and minimizes follow-up queries.

This article explains the elements auditors typically examine, why each matters, and how finance teams can structure reconciliation workpapers and outputs to be audit-ready. The guidance is practical and tool-agnostic, but it highlights ways reconciliation software can speed review and preserve provenance.

Use this as a checklist when preparing monthly reconciliations, period-end close packs, or any internal vs external comparison where an independent reviewer will need confidence in totals and supporting evidence.

Why this topic matters

Auditors are looking for reliable evidence that balances the company's books with external records. Reconciliations are often the first place discrepancies surface — timing differences, missing transactions, duplicate entries, or fee and charge variances.

Well-prepared reconciliation reports demonstrate control, reduce auditor time, and lower the risk of late adjustments or qualified opinions. For finance teams, the value is both operational and strategic: faster close cycles, fewer inquiries, and clearer narratives around exceptions.

Core components of reconciliation reports

Auditors focus on a handful of repeatable components that prove accuracy, traceability, and reasoned judgement. Organize reports to make these elements obvious.

1. Supporting documentation and evidence

• Source files: Include the original exports used for Side A and Side B (ledgers, ERP exports, bank statements, PSP settlement files).
• Identifiers: Ensure order IDs, transaction references, invoice numbers, or UTRs are visible and linked to the source line items.
• Attachments: Where available, attach invoices, payment advices, or settlement breakdowns that explain key variances.

Why it matters: Auditors want to trace an amount to its originating file and see documentary support for unusual items.

2. Matching logic and rules

• Deterministic rules: Document how exact identifier matches are handled and which fields were used (for example, Order ID + Amount + Date).
• Date windows and tolerances: Specify how timing differences are treated (same day, next-day, or open window logic) and any allowed drift.
• Grouping logic: Describe one-to-many or many-to-one matching rules, contra or net-to-net handling, and when totals are compared instead of line-by-line.

Why it matters: Clear rules explain why a particular transaction was matched, partially matched, or left unmatched, and prevent assertions that matching was arbitrary.

3. Exception handling and investigation

• Exception list: Provide a concise list of unmatched or partially matched items and their status (investigating, vendor contacted, awaiting credit).
• Investigation notes: Record actions taken, who investigated, and outcomes or next steps for each exception.
• Timeliness: Note the dates when exceptions were first raised and when they were resolved.

Why it matters: Auditors need to see evidence of follow-up and reasoned outcomes for exceptions, not just a static list of differences.

4. Audit trail and approvals

• Manual adjustments: Log any manual matches or adjustments, who made them, and the justification.
• Versioning: Keep versions or snapshots of reconciliations for each run period so auditors can see how items changed.
• Approvals: Include sign-offs, reviewer names, and dates for reconciliations submitted for audit.

Why it matters: The audit trail shows controls over the reconciliation process and prevents silent or undocumented changes to results.

5. Outputs auditors want to see

• Summary totals: Clear fully matched, partially matched, unmatched, and skipped totals with drilldown links.
• Reconciliation schedule: Period covered, cutoff times, and file versions used.
• Skip logic: Explain why any records were excluded from reconciliation (invalid amounts, missing columns, duplicates).

Why it matters: Auditors prefer a concise top-level summary with the ability to drill into exceptions and supporting evidence.

Practical implementation steps

1. Assemble source files and supporting data.

   • Export ledger lines, bank statements, PSP settlements, or partner reports for the same period.
   • Collect supporting files such as fee breakdowns, return reports, and mapping tables.

2. Standardize and map columns.

   • Confirm date, amount, and identifier columns are correctly specified.
   • Normalize date formats and apply currency conversions where needed.

3. Define deterministic matching rules.

   • Start with exact identifier matches, then date+amount, then permitted grouping or net-to-net matches.

4. Run automated matching and capture results.

   • Export a summary with matched, partially matched, unmatched, and skipped categories.

5. Investigate exceptions and document conclusions.

   • For each exception, add notes, link attachments, and record action items and owners.

6. Record manual matches and adjustments.

   • Ensure any manual intervention includes justification and is visible in the audit trail.

7. Produce an audit-ready pack.

   • Include summary totals, exception register, source files, and approvals. Use consistent file naming and versioning.

8. Retain snapshots and support recurring automation.

   • Archive reconciliation snapshots and consider automated imports or scheduled runs to reduce manual handling.

Common mistakes to avoid

• Missing identifiers or inconsistent reference formats that prevent deterministic matches.
• No documented matching rules, leaving auditors to guess why items were matched.
• Over-reliance on manual matching without logging who did what and why.
• Failing to attach supporting evidence for large or unusual variances.
• Ignoring skipped records; auditors expect to see why items were excluded.

Key Takeaways

• A reconciliation is audit-ready when it contains source files, clear matching rules, and a documented exception process.
• Auditors look for traceability: identifiers, evidence, approvals, and versioned outputs.
• Automating standard rules and recording manual actions reduces review time and strengthens controls.

Conclusion

Preparing robust reconciliation reports protects the close process and speeds auditor review by providing clear evidence, documented rules, and an audit trail. Use consistent identifiers, attach supporting documentation, and record investigation notes for exceptions to meet auditor expectations for transparency.

Start your 14-day free trial with Cointab. No credit card required. 14-day free trial.