How to Handle Audit Queries on Reconciliation

Audit queries on reconciliation are a common source of stress for finance teams. Auditors focus on whether internal records reconcile to external statements, and they expect clear evidence, traceability, and consistent methodology.

This guide shows practical steps finance operators can use to prepare reconciliation outputs, compile supporting documentation, and respond to audit questions efficiently. It assumes teams use repeatable reconciliation processes or reconciliation software to standardize files and surface exceptions.

You will find a checklist-style workflow, recommended deliverables for auditors, and tips to minimize back-and-forth during the review.

Why this topic matters

Audits test not only the accuracy of ledger balances but also the integrity of processes that produce those balances. Reconciliations are the frontline control that ties internal records to banks, payment gateways, marketplaces, vendors, and other external sources.

When reconciliation work is unclear or inconsistently documented, auditors raise queries that expand review scope, increase time-to-close, and create risk of findings. A structured response saves time, protects working capital, and builds credibility with auditors.

Core components

A confident response to audit queries rests on four core components: the reconciliation output, supporting documentation, exception handling, and an audit trail that links everything.

Documentation and evidence

• Source files: Keep the original exports you used for reconciliation (books, bank statements, PSP reports, marketplace settlements). Use native CSV/XLS/XLSX where possible.
• Mapping document: Provide a short file that shows which column in each file was used as date, amount, and identifier. This reduces auditor friction when re-running checks.
• Transaction-level evidence: For sampled transactions, include invoices, payment receipts, bank UTRs, or settlement lines that prove the flow of cash.

Reconciliation outputs and classification

• Fully matched items: Transactions where internal and external records match on identifier and amount, and therefore require no further explanation.
• Partially matched items: Identifiers match but amounts differ; these need a clear explanation such as fee deductions, chargebacks, or timing differences.
• Unmatched items: Items present on one side only; auditors will expect either an explanation, evidence of follow-up, or a note that the item is outside the audit period.

Present reconciliation results with counts and totals for each category and include sampled examples for auditor review.

Exception and adjustment tracking

• Adjustment log: For manual corrections or journal entries created to resolve recon differences, keep a dated log that includes reason, approval, and link to source evidence.
• Open exceptions register: Maintain a live list of unresolved items, status (investigating, awaiting vendor response, scheduled for reversal), and owner.

Automation and audit trail

• Reuseable configuration: Store reconciliation mappings and rules so you can reproduce the same run for the audit period without reconfiguration.
• Audit trail: Ensure every manual match, manual override, or adjustment is tagged with user, timestamp, and reason. This creates a defensible record.

Practical implementation steps

1. Prepare source packages

   • Export the exact data used for reconciliation: books, bank statements, PSP or marketplace reports, and any supporting feeds.
   • Save files with descriptive names and a short README that notes the report period and any filters applied.

2. Re-run (or confirm) the reconciliation

   • Use your reconciliation software or spreadsheets to re-run the reconciliation for the audit period with the saved source files.
   • Ensure date normalization and amount formatting match the original run so totals reconcile.

3. Produce an audit-ready reconciliation report

   • Include a summary page with counts and totals for fully matched, partially matched, unmatched, and skipped records.
   • Include a drill-down CSV or export for each category and a small sample of transaction-level evidence.

4. Compile supporting documentation

   • For sampled transactions, attach invoices, receipts, bank advices, or settlement lines that explain the cash flow.
   • For partially matched items, include calculations showing how fees, refunds, or taxes explain the variance.

5. Document manual interventions

   • For every manual match or adjustment, record the rationale, approver, and link to source evidence. Keep these in a single adjustment log.

6. Prepare an exceptions narrative

   • Write a short narrative explaining systemic reasons for exceptions during the period (e.g., timing lag between settlement and bank credit, carrier chargebacks, or duplicate uploads).
   • For items still under investigation, indicate expected closure dates and responsible parties.

7. Respond to auditor queries clearly and promptly

   • When auditors ask for evidence, deliver the reconciliation report, supporting source files, and the adjustment log together so they can trace items end-to-end.
   • Use numbered lists in responses to map auditor questions to specific report rows or evidence files.

8. Preserve records and learn

   • After queries close, store the full audit package in a shared archive with retention metadata.
   • Review recurring query themes and update mapping, automation, or process controls to reduce future queries.

Common mistakes to avoid

• Delivering incomplete source files: Auditors expect the raw exports you used, not a filtered subset.
• Missing mapping documentation: If auditors cannot tell which column you treated as identifier or amount, they will re-create work and raise questions.
• No evidence for manual adjustments: Unexplained journal entries are a major red flag.
• Over-reliance on screenshots: Provide native files and machine-readable exports in addition to visual summaries.
• Allowing forced matches: Never present low-confidence or forced matches without explanation; auditors will flag these as unsupported.

Key Takeaways

• Produce a clear reconciliation report with counts and totals for matched, partially matched, and unmatched items.
• Provide source exports, a mapping document, and transaction-level evidence for sampled items.
• Keep an adjustment log and a live exceptions register that show ownership and closure timelines.
• Use repeatable reconciliation configurations and preserve an audit trail for manual actions.
• Respond to queries with a single audit package so auditors can trace items end-to-end.

Conclusion

Handling audit queries on reconciliation is straightforward when you rely on repeatable reconciliation outputs, complete supporting documentation, and a clear audit trail for manual actions. Preparing an audit-ready reconciliation report, preserving source exports, and maintaining an adjustment log significantly reduce auditor time and help close queries faster.

Start your 14-day free trial with Cointab to create reproducible reconciliation runs and downloadable audit-ready reports: Start your 14-day free trial with Cointab. No credit card required. 14-day free trial.