Start from the payment record

A duplicate-payment check begins with the record that will actually be paid. Capture the vendor name, the invoice number, the invoice date, the amount, the currency, and the bank account that will receive the money. Add the purchase order or approval reference when the business uses one. The check should describe the payment, not only the document that arrived.

Read the invoice before comparing it with the payment history. A revised invoice may carry the same number with a different amount, and a credit note may cancel an older charge. Record the version and the reason for any change. A check that ignores the revision can approve the wrong amount twice.

Keep the bank record in the same view as the invoice. A payment to a different account under the same vendor name is a separate risk that a simple amount match will miss. Compare the account reference with the vendor master and flag any change. The reviewer should see the payee before the payment is released.

Give every payment record a stable identifier so it can be found later. The invoice number is useful, but it is not enough when vendors reuse numbers or send a credit note. Add the vendor identifier and the payment period. A stable key makes the duplicate check repeatable.

Match before the payment is scheduled

Run the check before the payment enters the scheduled batch. A check performed after the bank file is created is a recovery step, not a control. Compare the candidate invoice against paid and scheduled records for the same vendor. Include payments that are still waiting for approval.

Search a window that covers the vendor's normal billing cycle. A duplicate may arrive one day later or one month later with a new date. Use the vendor's history to choose the window, and record it beside the check. A window that is too short will miss the common case.

Use two levels of matching. Start with an exact match on the vendor identifier and invoice number, then review near matches on amount, date, and description. A near match is not proof of a duplicate, but it deserves a second look. Record which level produced the hold.

Place a possible duplicate in a hold state that cannot be paid by accident. The hold should name the original payment, the candidate record, and the person who must decide. Do not release the hold by editing the amount or the invoice date. The decision needs its own note.

Separate a true duplicate from a recurring bill

A recurring bill can look identical every month without being a duplicate. The invoice number may repeat, the amount may be fixed, and the description may not change. Check the service period and the expected billing schedule before raising a hold. A utility bill or a retainer is not a duplicate just because the amount matches.

A true duplicate usually shares the same obligation, not only the same number. Compare the invoice period, the purchase order, and the delivery or service record. If two records point to one obligation, the second payment should wait. If they point to different periods, the check should say so.

Write the distinction into the check so a new specialist can apply it. Give one example of a recurring bill and one example of a duplicate. Explain which field settled the question. A short example is more useful than a long definition.

Ask the vendor when the evidence is unclear. A short message that names the invoice and the period is better than an accusation. Keep the reply with the payment record. The vendor may confirm a credit, a reissue, or a genuine second charge.

Give the check one owner and one status

One person should own the duplicate check for a payment batch. That person may prepare the comparison and route the holds, while a manager keeps the release decision. A shared inbox without an owner can leave a hold unread. Name the owner and the backup in the payment calendar.

Use a small set of statuses such as clear, held for evidence, released, and cancelled. Each status should have a definition and a next action. A record that is merely marked reviewed does not show whether the payment can proceed. The status should answer that question directly.

Set a response target for holds that matches the payment schedule. A hold that is reviewed after the bank cutoff has no effect on this run. Publish the cutoff and the person who can approve an exception. The target should be visible to the accounts team and the approver.

Do not let the check become a second approval layer for every invoice. The routine match should clear most payments without a meeting. Reserve the owner's attention for near matches, bank changes, and repeated vendors. A control that stops the whole queue will be bypassed.

Review holds and false positives

At the end of each week, review the holds that were cleared without a change. A false positive may mean the matching rule is too broad or the vendor master is incomplete. Record the reason and adjust one rule at a time. The check should improve without becoming invisible.

Review the payments that were released after a hold and confirm that only one payment left the account. A release without a second check is the moment a duplicate can still slip through. Keep the bank confirmation with the record. The evidence should be easy to find during a later review.

Measure the number of holds, the share that were true duplicates, and the time to resolve a hold. A high false-positive rate makes the team skip the check. A low hold rate with a known duplicate is worse. Use both numbers to judge the rule.

Share one corrected case with the accounts team each month. Explain what the original record looked like and which field exposed the duplicate. A real case teaches the judgment that a checklist cannot fully capture. Keep the case anonymous and short.

If the duplicate rules and release owners are already defined but need a steady reviewer, accounts support can turn approved examples, decision lines, and review rules into a draft your manager can check. The manager still owns exceptions and final approval.

For the next step, compare this workflow with Build an exception log for a delegated accounts inbox and the operations guide. For access and oversight, use the authoritative planning reference alongside your own policy.