Check for duplicate vendor payments before release

Review candidate duplicates before release

A repeated invoice can arrive through several channels or under slightly different references. Build a review queue that links the incoming document to existing invoices and payment status. The assistant gathers and compares evidence; the authorized accounts-payable owner decides whether to hold, correct or release an item.

Compare the underlying transaction

An exact invoice-number match is useful, but formatting changes can hide a repeat. Conversely, the same amount can appear legitimately on recurring invoices. Use your approved matching rules and inspect the transaction context.

Comparison	Evidence to collect	Reason to pause
Supplier identity	Approved supplier reference	Similar names or conflicting entities
Invoice reference	Original and normalized reference	Reissue or changed formatting
Amount and currency	Both documents and ledger values	Partial billing or inconsistent totals
Service or delivery period	Relevant supporting record	Same amount for different periods
Payment status	Approved ledger or payment record	Pending, reversed or unclear status
Credit or replacement	Linked adjustment documentation	Original treatment is unresolved

Example: a reissued invoice

A supplier sends invoice INV-107 and later sends INV-107-R with a corrected address. The assistant finds the earlier record in the payment queue and links both documents. They ask the accounts-payable owner whether the new version replaces the original, and what should happen to the existing entry. They do not create a second payable simply because the reference differs.

Distinguish duplicate risk from supplier changes

A new bank detail or unexpected payment instruction requires the business's separate approved verification process. Do not use an invoice email alone to authorize a supplier-master change. Keep that unresolved issue visible even if the invoice itself is not a duplicate.

Return a decision-ready packet

Include the candidate documents, supplier identifier, ledger references, payment status, supporting transaction evidence and the specific unresolved question. Mark the item according to the approved hold process and record its owner. Preparation access does not grant payment-release authority.

Check the outcome after review

Record the owner's dated decision, the affected references and the resulting status. If a duplicate entry is corrected, verify that the intended record remains available and that the change did not also remove a legitimate invoice. If a payment may already have occurred, route the discrepancy to the authorized finance owner rather than contacting the supplier with an unapproved promise.

Test the review rules

Use examples of an exact repeat, a legitimate recurring amount, a corrected reissue and a partially settled invoice. Review both missed duplicates and false positives. Adjust only approved rules, then inspect a new sample. A higher flag count may simply create more unnecessary review.

Define a repeatable handoff

Agree the review timing, required evidence, hold status and escalation owner before the first queue is assigned. Accounts payable support can prepare the comparison and follow up on missing documents while payment decisions stay with your team.

Practical questions

Should every invoice with the same amount be held?

Use your approved process. Equal amounts can indicate a repeat, but they also occur on legitimate recurring transactions. Compare identifiers, periods and status before asking the owner for a decision.

Can an assistant cancel a suspected duplicate?

Suspicion alone is insufficient. The assistant should follow a defined authorization boundary and retain evidence of the decision and resulting change.

What should remain open?

Anything with unclear payment status, conflicting supplier identity, an unresolved replacement document or missing authorization. A named owner and next action make the exception manageable.