What audit-ready reconciliation means
Audit-ready reconciliation means more than a clean set of totals. It means that for every period reconciled, a finance team can show:
- Which files were reviewed and for which period
- What matching approach was applied
- Which transactions matched and how
- Which transactions did not match and why
- How each exception was investigated
- What decision was made for each exception and why
- Who reviewed each exception
When all of this is documented and exportable, auditors can review the reconciliation evidence without needing to ask the finance team to reconstruct it from memory or spreadsheet notes.
Why totals are not enough
A reconciliation that shows "matched: 847, unmatched: 12, total difference: $0" tells an auditor very little. They cannot tell from totals:
- Whether the 12 unmatched items were investigated or ignored
- Whether any matched items were force-matched without adequate evidence
- Whether any possible duplicate payment candidates were reviewed
- What the matching logic was — and whether it was applied consistently
- Whether any exceptions carry ongoing risk that needs monitoring
The gap between reconciliation and audit evidence
What evidence should be preserved
A complete reconciliation evidence set should include these ten components:
Files reviewed
Which files were uploaded and reconciled — bank statements, ledger exports, invoices — with period, date, and source recorded.
Mapping approach
How columns were mapped — which fields were used for date, amount, reference, and party — and any normalization applied.
Matching method applied
Which matching methods were used — exact amount, date proximity, tolerance, reference, vendor — and the parameters configured for each.
Match status per transaction
The result for each transaction: matched (with pair identified and match method recorded), partially matched, or unmatched.
Exception type and context
For unmatched entries: the exception category (timing difference, amount mismatch, missing entry, possible duplicate), the nearest candidate reviewed, and the difference.
PowerBot draft note (where used)
Where PowerBot was used to investigate an exception, the AI-generated context is recorded — showing what was asked and what was surfaced.
Reviewer note (edited and approved)
The reviewer's finalized note for each exception — describing what was investigated, what was found, and what the decision rationale was.
Decision status
The final resolution for each exception: resolved, pending, escalated, or written off — with the reviewer identified.
Unresolved items tracking
Items that could not be resolved in the current period — with the outstanding issue described and a follow-up plan noted.
Exportable summary
A structured export of the full reconciliation — match summary, exception log, reviewer notes, and decision status — ready for audit review.
Exception documentation workflow
Each exception should move through a structured documentation workflow:
Identify exception
The transaction is surfaced as unmatched or partially matched — with the exception type (timing difference, amount mismatch, missing entry, etc.) noted.
Classify exception type
Assign the exception to one of the standard categories: timing difference, amount mismatch, possible duplicate, missing entry, reference mismatch, or vendor mismatch.
Review supporting signals
Review the available context — nearest candidate match, difference amount, date gap, reference comparison — to understand the likely explanation.
Draft note
Write or use AI to draft a reviewer note describing what was reviewed, what the likely explanation is, and what the recommended resolution is.
Reviewer verifies note
The assigned reviewer reads the draft note, edits as needed, and confirms that it accurately represents the investigation and decision rationale.
Decision recorded
The final decision is recorded against the exception — resolved (with note), pending (with follow-up action), escalated (with escalation reason), or written off.
Export summary
At close, the exception log with all notes and decision status is included in the reconciliation evidence export.
Reviewer notes best practices
Reviewer notes are the most important element of audit-ready reconciliation evidence. A useful reviewer note explains the why, not just the what:
Weak notes
- "Reviewed"
- "OK"
- "Timing"
- "Checked with vendor"
- "Will follow up"
Strong notes
- "Timing difference — payment posted Dec 31 in bank but Jan 2 in ledger due to bank cut-off. Confirmed correct posting period in GL."
- "Amount difference of $42 — bank shows $4,200, GL shows $4,158. Difference confirmed as card processing fee. Coded to fee account."
A strong reviewer note answers: what type of exception is this, what evidence was reviewed, what is the likely explanation, and what was decided.
PowerBot-assisted audit note drafting
PowerBot — Certanexa's AI finance investigation assistant — can help draft structured reviewer notes for exceptions. It has access to the transaction context in the current session and can:
- Identify the exception type based on the available signals
- Describe what fields match and what differs between the transaction and its nearest candidate
- Suggest the most likely explanation based on the transaction pattern
- Draft a structured reviewer note that the finance team can review, edit, and approve
AI drafts — reviewers approve
Exportable reconciliation summary structure
A structured reconciliation summary export should contain the following sections:
Summary header
Match summary
Exception log
Possible duplicate review
Unresolved items
Audit-ready reconciliation checklist
Use this checklist before closing a reconciliation period to confirm that audit evidence is complete:
- Files reviewed are listed with period and source
- Matching approach is recorded
- Exceptions are grouped by type
- High-risk exceptions are reviewed first
- Possible duplicate candidates are documented
- Reviewer notes are added per exception
- AI-drafted notes are reviewed and approved
- Unresolved items are marked with follow-up
- Decision status recorded for each exception
- Reconciliation summary exported
- Assumptions and limitations documented
- Period closed with reviewer sign-off
Frequently asked questions
Build audit-ready reconciliation evidence as you work
Certanexa supports exception documentation, AI-assisted reviewer notes, and structured evidence export — in early access for modern finance teams.