Supplier invoice references are often used to identify documents, spot duplicates and connect statement activity to the books. When the reference on a received invoice differs from the one already recorded, or when two documents appear to share the same reference, routine processing can become unreliable.
A reference-conflict review establishes the document identity before the team edits, merges or creates records. It helps prevent a simple labelling inconsistency from becoming either a duplicate invoice or the accidental loss of a genuine transaction.
Capture each conflicting reference exactly
Record the reference shown on each relevant source document, statement entry and existing bookkeeping record. Do not normalise the values too early, because punctuation, prefixes or other differences may help explain the issue.
Keep the sources distinguishable so later reviewers can see where each version came from.
Compare more than the reference field
Review supplier identity, document date, amount and other available invoice details. A shared reference does not prove two documents are duplicates, and a different reference does not prove they represent different transactions.
The document should be identified from the combined evidence.
Check whether the supplier issued a corrected document
Where two invoices are otherwise closely related, establish whether one supersedes the other or whether both remain valid. Look for supporting communication or corrected-document evidence rather than assuming the later file replaces the earlier one.
If the relationship is unclear, raise a focused query.
Review the existing bookkeeping record
Check whether either reference has already been used for an entry, payment match, statement review or another process. Understand the downstream effect before changing the identifier.
This prevents a local reference correction from breaking a connection elsewhere in the records.
Keep suspected duplicates unconfirmed until supported
If the conflict suggests duplicate entry, investigate it through the firm's duplicate-review process. Do not delete one record solely because the references look similar.
Conversely, do not create another invoice merely because a reference differs if the evidence suggests an existing record may represent the same source event.
Correct the current identity through controlled review
Once the evidence establishes the appropriate reference and document relationship, update the bookkeeping records using the firm's normal controls. Preserve the reason for the change where the working history requires it.
Make sure colleagues can identify the current source document after the correction.
Check statement and payment links before closure
Confirm that connected supplier statement items, payment records and open queries still point to the correct transaction. Keep any remaining conflict visible with an owner.
A structured reference-conflict review helps bookkeeping teams avoid treating identifiers as infallible. By checking the wider evidence before creating, deleting or changing records, the team can resolve inconsistencies without introducing a duplicate or obscuring a genuine transaction.