Accounts payable

Set a duplicate invoice check before payment

A duplicate invoice check that compares vendor, invoice number, amount, and date before the payment run is released.

Set a duplicate invoice check before payment workflow illustration

Set a duplicate invoice check before payment

How to approach: Set a duplicate invoice check before payment

A duplicate invoice check is a control at the payment gate, not a cleanup after the money leaves. Compare the vendor, the invoice number, the amount, and the invoice date. A match on vendor and amount alone is not enough. Write the deadline as a date and a local time.

Run the check on the full payment run, not a sample. The duplicate may be in the batch that is about to be paid. The check should be quick enough to finish before the release window. Record the date and the source so the next reviewer can repeat the check.

Compare the invoice identity

Match the vendor identifier and the invoice number exactly. A different suffix or a reissued number should be treated as a question. Record the match and the source record. Keep the original note beside the corrected version.

Check whether the invoice was already paid in a prior run. A vendor may resend an old invoice with a new date. The payment history is part of the check. Use the same format for every handover so the next reader can scan it.

Compare the amount and the date

Compare the amount and the invoice date with the prior record. A duplicate may have a slightly different amount because of a credit or a tax adjustment. The difference should be explained, not ignored. Keep the evidence with the record rather than in a separate log.

Check the purchase order and the receipt. A duplicate may arrive with a different purchase order number. The underlying transaction is the same, and the payment should not happen twice. Use the same format for every handover so the next reader can scan it.

Set the stop and the review

A suspected duplicate should stop the payment and go to a named reviewer. Record the reason and the evidence. The reviewer should decide whether the invoice is valid or a duplicate. A short note with four fields is easier to use than a long narrative.

Do not delete the invoice from the system. Mark it as held and link it to the original. A deletion hides the pattern and makes the audit harder. Name the owner in the same line as the action.

Record the outcome

Record whether the invoice was paid, rejected, or combined with another. If it was a duplicate, record the vendor and the amount. The record should support a later review. A control that depends on memory is not yet a control.

Share the pattern with the AP team monthly. A vendor that repeatedly sends duplicates may need a conversation. The check should reduce the recurrence, not just catch the next one. Write the deadline as a date and a local time.

Keep the check current

Review the check after a system change or a new payment channel. A new portal may create a new duplicate path. The rule should cover the channels the team actually uses. Write the deadline as a date and a local time.

Test the check with a known duplicate in a safe environment. A control that has never been tested is only an intention. Record the test and the result. Name the owner in the same line as the action.

This note is operational guidance, not accounting, tax, legal, or security advice. Use the back office support service and read the GAO Green Book before turning the routine into policy.