Philippines duplicate invoice exception queue: stop a second payment without stopping valid bills

Why exact matching misses the dangerous pair

A vendor submits invoice 004817 for $12,400, then sends INV-4817 for the same amount two weeks later. One references a purchase order and the other a project name. Exact-number logic misses the pair; a loose amount rule may hold unrelated recurring bills.

The exception engine should combine normalized supplier identity, invoice number, amount and currency, date proximity, purchase order, contract milestone, line descriptions, tax, and payment destination. It produces candidates, not verdicts. GAO has reported on federal improper payments, and its Green Book describes internal-control principles that are useful context; each business still designs controls for its systems and obligations.

The offshore reviewer opens a pair with stable document IDs and payment status. It must include credits and reversals so a legitimate correction is not mistaken for another charge. If either item is scheduled, apply the client’s documented temporary hold while review proceeds.

Reconstruct the commercial event

Compare the underlying goods or service, not merely the page image. Confirm supplier legal entity, remit-to account, purchase order and receipt, service period, milestone, quantities, unit prices, tax, freight, credit references, and prior payment. Look for scanning duplicates, portal resubmission, a changed invoice format, split billing, consolidated billing, deposits, progress claims, and one charge spanning multiple departments.

Preserve original documents and extraction values. If a supplier reused an invoice number for a different entity, that is a control problem but not automatic proof of duplicate liability. The reviewer labels facts, source, and retrieval time.

In the scenario, both documents claim the same milestone and one was emailed after the first already entered through the portal. That strongly supports duplicate submission, but the client accounts-payable owner confirms treatment. The specialist must not delete one record to make the ledger look clean; link it and retain the disposition.

Use a disposition taxonomy that explains the pair

Useful outcomes include confirmed duplicate, legitimate recurring charge, corrected replacement, credit and rebill, split invoice, consolidated invoice, same amount for separate delivery, test document, suspected fraud, and unresolved. Each has a next action and approval rule. A corrected replacement should identify which document is payable and whether the earlier one must be voided.

A credit and rebill needs all three records linked. A suspected fraud case leaves ordinary supplier outreach to the incident owner, because contacting a compromised channel can worsen the event. Record confidence separately from disposition; high similarity is not approval.

The exception note answers one question: why can these two obligations coexist, or why should only one survive? Attach receipt and contract evidence through approved links rather than copying financial data into chat. If the explanation depends on an oral statement, log who provided it through what independently governed contact.

Control holds and releases explicitly

A hold protects cash but can also breach terms or disrupt a critical supplier. Store the hold scope, reason, start, owner, review time, affected payment run, and allowed expiration. Do not place a broad vendor hold when only one invoice is in question unless policy directs it.

The preparer recommends a disposition; a client AP or finance owner authorizes void, release, recovery, offset, or supplier communication. Named accounts record execution. Before release, recheck payment status because another user or automated run may have acted during review.

If both documents were paid, route recovery without editing history. If neither was paid and one is approved, confirm the correct bank record and scheduled date.

The queue should surface holds approaching cutoff so silence never becomes accidental release or indefinite nonpayment. Emergency decisions retain the same evidence and receive retrospective review.

Reconcile the system after the decision

Verify invoice status, payment proposal, general-ledger impact, purchase-order balance, receipt matching, vendor statement, and any credit. A void in the AP tool may not restore committed PO value; a recovery promise is not recovered cash. Link system transaction IDs and capture the approved explanation.

Notify procurement or the business owner when recurring process defects cause duplicates. Close only when the ledger represents the intended obligation and every hold has a disposition. For invoice 004817, the retained case should show the portal submission first, the later email copy, milestone evidence, authority to void the second record, and confirmation that exactly one payment remains.

If the duplicate was caught after transmission, keep the bank and supplier follow-up open as linked actions. This downstream check turns detection into loss prevention rather than a dashboard of flags.

Tune rules from reviewed evidence

Track candidates by rule, confirmed-duplicate rate, false-positive explanation, value protected, late detection, time awaiting owner, paid duplicates, recovered amounts, and reconciliation defects. High precision is not the only goal; an overly narrow rule misses altered invoice numbers. Sample unflagged payments using supplier, amount, and time patterns to estimate gaps.

Analyze causes: vendor resubmission, multiple intake channels, OCR variation, interface retry, weak PO matching, or staff override. Fix intake design when possible instead of endlessly reviewing noise. The pilot should cover recurring and nonrecurring suppliers, several currencies, credits, and staged billing, but exclude unsupported high-risk payment rights.

Readers gain a queue that distinguishes similarity from liability, keeps valid invoices moving, and leaves a clear audit trail from candidate through authorized financial outcome. A final worksheet asks whether supplier and currency match, whether both documents claim the same delivery or period, what changed, and whether either entered a payment proposal or settled. It links the contract, purchase order, receipt, and governed supplier contact; names the hold and decision owner; and lists downstream records to reconcile.

A second reviewer should reach the same next step. If not, the case is incomplete, not ready for release. Review access to the queue quarterly.

Preparers need invoice and receipt evidence but usually do not need unrestricted bank-master editing or payment release. Remove stale rights and test the backup approver path.

During an application outage, record holds in the approved continuity process and reconcile them immediately after recovery. Invisible email flags or personal spreadsheets are not durable payment controls.