What evidence should a finance team retain for reconciliation review?
A reviewable reconciliation record should retain the source files and period in scope, field mappings and transformations, matching rules or tolerances, match and exception results, reviewer notes, supporting evidence for resolved items, changes or reruns, unresolved ownership, and the final reconciliation summary or sign-off context. The objective is that another reviewer can understand what was compared, how decisions were made, and what remained unresolved.
A reconciliation can be numerically correct and still be difficult to review if the evidence trail is fragmented across spreadsheets, chats, email attachments, and undocumented manual decisions. Evidence quality is therefore not only about retaining files; it is about retaining the context that explains how those files became a reconciliation conclusion.
The checklist below focuses on reviewability. It intentionally separates source evidence, process evidence, decision evidence, and completion evidence so teams can see where a workflow is strong and where it still depends on tribal knowledge.
Certanexa evidence framework
This checklist is an educational first-party framework for reviewability. 'Audit-ready' means evidence is organized for review; it does not mean audit certification, guaranteed auditor acceptance, or compliance with a specific standard without additional professional assessment.
Four evidence layers in a reviewable reconciliation
A strong record normally needs more than one evidence layer. Missing process or decision evidence can make raw source files difficult to interpret later.
| Class / layer | Signal or question | First review step | Evidence to retain |
|---|---|---|---|
| Source evidence | What was actually reconciled? | Confirm file/source identity, period, entity, account, and scope. | Source files or immutable references, period, account/entity, ingestion timestamp or checksum where available. |
| Process evidence | How were records prepared and compared? | Review mappings, normalization, rules, tolerances, grouping logic, and relevant configuration. | Mappings, transformations, rule/tolerance version, matching run context. |
| Decision evidence | Why was an exception accepted, rejected, adjusted, or escalated? | Review candidate context, supporting documents, and reviewer rationale. | Exception class, notes, support, owner, decision status, timestamps where appropriate. |
| Completion evidence | What was the final state of the reconciliation? | Confirm matched/unresolved totals, open items, reruns, approvals, and handoff status. | Final summary, unresolved register, rerun history, reviewer/sign-off context. |
How to build the evidence trail during the workflow
Evidence is easier to preserve when it is captured as the work happens rather than assembled at the end of the month.
Bind evidence to the reconciliation scope
Start with the entity, account, period, source files, and owner so later evidence cannot be mistaken for another run.
Version the matching context
Retain the rules, tolerances, mappings, and material transformations that affected the result instead of documenting only the final matched count.
Capture exception reasoning at decision time
Reviewer notes should explain the evidence used and why the item was resolved, left open, or escalated.
Preserve reruns and material changes
If source data or rules change, keep enough history to understand why the new result differs from the earlier run.
Close with an unresolved register and summary
A final evidence package should make remaining open items visible rather than hiding them inside a total.
Reconciliation evidence checklist
- Entity, account, period, and reconciliation owner are identified.
- Source files or source references are retained and distinguishable from later versions.
- Field mappings, material transformations, and normalization rules are documented.
- Matching logic, tolerance, grouping, and relevant configuration are identifiable.
- Matched, unmatched, and partially resolved populations remain traceable to source records.
- Exception classification and reviewer notes explain material decisions.
- Supporting documents or source-system context are linked where they influenced resolution.
- Reruns, changed files, changed rules, and material result differences are visible.
- Unresolved items have status, owner, and follow-up context.
- Final summary or sign-off context reflects the actual reviewed state rather than implying that open items disappeared.
Important boundaries
The evidence needed for a specific audit or control depends on the organization's policies, materiality, applicable standards, and auditor requirements.
Audit-ready means organized and reviewable; it does not mean certified, compliant, or guaranteed to satisfy an auditor.
AI-generated notes or explanations should remain identifiable and user-reviewed before they become part of final evidence.