Answering an Audit Sample After the Asset Record Has Changed
Preserve the sampled register version and explain later corrections through a dated bridge, so evidence still answers the original asset request.
How should you answer an audit sample when the live register has changed since selection?
Retain the register version from which the sample was selected, then explain subsequent changes with dated evidence and an old-to-current record bridge. Respond to the original sample identifier. Do not substitute the latest record silently or imply that a later correction was already present in the sampled population.
Auditors select a vehicle from an exported register. Before the evidence request reaches operations, finance corrects its class and the asset team updates its location. The live screen is now more accurate, but it no longer reproduces the selected row. A controlled response needs to show both the original record and the legitimate work completed afterwards.
Anchor the response to the sampled population
Save the sample request, original asset identifier and the export version used for selection. Record the relevant reporting date and the date the request was received. If the original export is unavailable, disclose that gap and seek the selected row details rather than reconstructing a supposedly original file from current records.
Create a response reference that stays attached to the original sample item even if its identifier later changes. This reference can connect the source row, current record and evidence pack. Avoid matching only by a broad description such as utility vehicle, particularly where several records could plausibly satisfy the request.
Explain each intervening change
List changes between the sampled version and the current record with effective date, processing date, reason and approval reference. Separate a physical movement from a data correction and from a financial adjustment. Those events answer different questions and may have occurred on different days.
Attach the underlying evidence for the change, such as a transfer receipt or approved correction schedule. Preserve before-and-after values. If an update corrected an old error, say so plainly instead of presenting it as a new event. A clear explanation is more useful than a clean current screenshot that leaves the reviewer unable to understand the earlier discrepancy.
Submit a response that preserves the timeline
Package the original row, change bridge, current state and requested evidence in a logical order. State which documents describe the sampled date and which describe later events. Where a later observation is supplied, give its actual date and explain any movement information used to connect it to the earlier period.
Let the auditor decide whether the evidence answers the request or requires further work. Internally, keep the sample response open until questions about the bridge are addressed, rather than closing it when files are uploaded. This is an evidence-handling method, not a promise that a corrected record removes an audit finding or establishes an audit conclusion.
Practical Example
Illustrative example: a sample refers to vehicle V-28 at Central Depot in a 30 June export. A supported transfer moves it to North Depot on 8 July, and a class correction is processed on 12 July. The response retains the June row, attaches both change references and supplies the later observation from North Depot with its true date. It does not rewrite the June export to make the current location appear historical.
Action Checklist
- 1.Retain the selected population version and the original sample identifier.
- 2.Link the original row and current record through a stable response reference.
- 3.List intervening movements, corrections and financial changes separately.
- 4.Label evidence by the date and event it actually supports.
- 5.Track follow-up questions until the reviewer can understand the full change trail.
For sample responses that preserve the original record and later changes, explore Audit-Ready Asset Management.
