Evidence control · 3 minute read
Why version control becomes an audit issue before anyone notices
How changing reports, schedules and evidence packs create hidden review work, and the controls that keep everyone working from the same approved position.
Version control becomes an audit problem before it becomes an obvious file-management problem. Finance may be updating a fourth draft while the auditor is testing the second, a reviewer may approve a schedule that has already been superseded, and a corrected financial-statement number may no longer agree to the supporting evidence originally submitted.
The risk is not solved by adding ‘final’ to a filename. A controlled version needs an identifiable owner, preparation and review status, a retained baseline and a clear explanation of material changes. Without those features, neither side can easily tell whether a later file corrects an error, reflects a new judgement or simply reformats information already reviewed.
Version changes can also spread across connected documents. A revised impairment assumption may affect the model, accounting paper, financial statements, disclosure and governance materials. Updating one output without identifying the consequential changes leaves the evidence pack internally inconsistent even where each individual file looks complete.
A practical change log should stay proportionate. Record the version, date, owner, reason for change, affected outputs and review status. Minor presentational edits can be grouped, while changes to amounts, assumptions, scope or conclusions should be visible enough for the next reviewer to understand what needs to be reconsidered.
The objective is not to prevent legitimate revision. Audit evidence and financial reporting develop as questions are resolved. The control is knowing which version is authoritative, what changed and whether the connected review work has been completed before the new file is treated as ready.
What to do next
- Nominate one owner and one authoritative location for each material deliverable.
- Separate approved baselines from current working drafts.
- Record the reason and consequence of material changes, not only the filename.
- Identify connected schedules, papers and disclosures that require reconsideration.
- Confirm review status before a revised file is presented as ready.