Philippines staffing guide · Published
Build a duplicate-payment check before an outsourced invoice queue releases funds
A duplicate invoice can pass every normal check because each field looks valid on its own. Compare the invoice number, amount, and date against earlier payments before approval, and record what the match found.

The short answer
A duplicate-payment check works when it compares invoice number, amount, and date against earlier payments before approval. Normalize the reference, show the prior payment beside the match, and record a clear outcome for every exception.
Why a normal invoice review misses duplicates
An invoice reviewer usually checks the vendor, the amount, and the approval against the purchase order. That routine catches a wrong price or a missing signature, but it does not compare the invoice with earlier payments.
A duplicate often carries a valid vendor name and a valid approval, so every field looks correct in isolation. The second copy is only visible when it is placed beside the first.
Duplicates arrive through several ordinary routes. A supplier resends an invoice after a portal outage, a scanned copy is keyed twice, or a credit note is never matched to the original charge. None of these events looks suspicious at the moment it happens.
The queue simply receives another document that passes the same checks. A duplicate rule adds the one comparison the normal review leaves out.
Match on invoice number and amount, not vendor name
Vendor name alone is a weak match because the same supplier may issue several invoices on one day. Match the invoice number first, then the amount and the invoice date as a secondary check.
Some suppliers reuse numbers across business units, so the amount helps separate a true repeat from a coincidence. Record which fields the rule compares so a reviewer can explain the result.
Normalize the text before comparing. Remove spaces, punctuation, and leading zeros from the invoice number so that two formats of the same reference still match. Store the normalized value next to the original, because the original is what the supplier will recognize in a dispute.
If the queue uses a portal, capture the portal reference as well. The goal is a comparison that survives formatting differences without hiding real distinctions.
Place the check before approval
A duplicate check after payment is a recovery process, not a control. The money has already left, and the team now has to ask the supplier for a refund.
Move the comparison to the point where the invoice enters the queue, before anyone approves it. Then the reviewer can hold the item while the earlier payment is confirmed.
The check should run automatically and produce a short result that a person can read. A match score without the earlier invoice reference is not useful under time pressure. Show the prior invoice, its payment date, and the field that matched.
If the system cannot show that evidence, the reviewer will approve the invoice to clear the queue. Design the output for the decision, not for the report.
Write the exception note for a suspected duplicate
When the rule flags an invoice, the reviewer needs a place to record what happened. Write the supplier contact, the earlier payment, the matched field, and the action taken.
If the invoice is genuinely new, say why the match was a false positive. That explanation is what lets the next reviewer trust the rule instead of bypassing it.
Do not close a suspected duplicate with a one-word status. A note that says checked tells nobody what was checked or who confirmed it. Use a small set of outcomes: confirmed duplicate, new invoice with a reused number, or unresolved awaiting supplier reply.
Each outcome should have an owner and a date. The note then becomes evidence for the next month review.
Test the rule with a known repeated invoice
Test the rule before it goes live by feeding it two copies of an invoice that was already paid. Confirm that it flags the second copy and names the first.
Then test a near match with a different amount and confirm that it does not block a legitimate invoice. A rule that catches everything is as costly as a rule that catches nothing.
Run the test again after any change to the accounting system or the invoice format. A new portal field can break the match without any visible error. Keep the test cases in the same folder as the rule so the next owner can repeat them.
Record the date and the result. A control that is not tested after a change is a control you cannot describe.
Review the rule after a false positive
A false positive is useful evidence. Ask why the invoice number matched when the charge was new. The answer may be a supplier habit, a portal setting, or a normalization rule that is too broad.
Fix the narrow cause and keep the test case that exposed it. Do not weaken the rule for every supplier because one supplier reuses numbers.
Review the flagged items once a month and count how many were confirmed, cleared, or left open. A rising open count means the queue is not resolving the exceptions. A falling confirmed count may mean the rule is catching fewer real duplicates, or that the supplier has changed its process.
Either way, the trend is worth a short conversation. The rule stays useful when someone reads its results.
Keep the rule visible after a system change
An accounting upgrade can remove the field the rule depends on without telling the payment team. Ask the system owner to confirm that the invoice reference, amount, and date still arrive in the same form.
Then run the known duplicate test again before the next payment run. A rule that silently stops matching is worse than no rule because the team believes it is protected.
Write the rule owner and the last test date beside the rule description. When the owner leaves, the description is the only way the next person knows what the check does.
Add a short note about the exceptions the rule cannot catch, such as a credit note applied to the wrong invoice. The note keeps the team from expecting more from the check than it can deliver.
Questions to copy for the sales call
- "Which invoice fields does the queue compare today?"
- "Where would a duplicate appear before anyone notices it?"
- "Who confirms the earlier payment when the rule flags a match?"
- "What evidence does the exception note need to be useful?"
Sources
- IRS: Publication 583, Starting a Business and Keeping Records: Recordkeeping expectations for business transactions and supporting documents.
- GAO: Standards for Internal Control in the Federal Government: Internal control principles covering review, documentation, and segregation of duties.
- SBA: Manage your business: Operational guidance for managing payments and business records.
Common questions
Should every invoice be checked for duplicates?
Yes, but the check can be automatic. A rule compares the reference, amount, and date, then sends only the matches to a person for a decision.
What if the supplier reuses invoice numbers?
Use the amount and date as secondary fields, and record the reuse pattern. A known reuse should not disable the rule for every other supplier.
Who should clear a flagged invoice?
Someone other than the person who entered it. A second reviewer can confirm the earlier payment and record the reason for release.
How long should the exception note be kept?
Keep it with the payment record for the period your recordkeeping policy requires. It should remain readable to a reviewer who was not involved.