A client may send a replacement invoice, statement or other source record after an earlier version has already entered the bookkeeping workflow. The replacement may correct a reference, amount, date or other detail, but simply saving the new file does not ensure that the old version stops influencing the books.
A replacement-record review establishes which document is current, what changed and which bookkeeping activity is affected. It preserves useful history without leaving two competing versions in active use.
Identify the record being replaced
Start with the supplier, customer or other relevant party, the document reference, period and the earlier version already held. Make sure the replacement genuinely relates to the same underlying record.
Similar filenames or amounts are not enough to establish that one document supersedes another.
Confirm what changed between versions
Compare the material fields needed for the bookkeeping work and record the relevant difference. A replacement may correct only one detail while the rest of the document remains unchanged.
This helps the team assess impact without treating every replacement as a completely new transaction.
Preserve the source trail
Keep the superseded record according to the firm's established document controls where history needs to be retained, but mark or locate it so that it is not mistaken for the current working source.
Do not silently overwrite evidence if doing so would remove the reason for a later bookkeeping correction.
Check whether the earlier version was already processed
Review the bookkeeping record to establish whether the original document affected an entry, allocation, reconciliation or query. If it did, determine which connected records need review.
A replacement file should not automatically create a second transaction.
Process supported corrections through the normal workflow
Where the changed evidence requires a bookkeeping correction, use the firm's established control and approval process. Connect the revised entry to the replacement evidence where appropriate.
If specialist accounting judgement is required, escalate it to the responsible person rather than inferring the treatment from the document change alone.
Close dependent queries and exceptions carefully
A replacement may resolve an open question, but only close that issue if the new record actually supplies the missing evidence. Update linked working notes so colleagues do not continue chasing information that has already arrived.
Keep any remaining uncertainty visible as a separate issue.
Confirm one current working version
At the end of the review, the team should be able to identify the current source record, the status of the superseded version and any bookkeeping action taken because of the change.
A controlled replacement-record review prevents document updates from creating duplicate or conflicting evidence. It gives bookkeepers a clear route from the old source to the current one and keeps the resulting bookkeeping changes traceable.