This research is general operational information, not legal, tax, accounting, employment, benefits, privacy, cybersecurity, insurance, or financial advice.

Question and scope
This is a proposed research protocol, not a report of completed findings. It asks how often a duplicate invoice reaches the payment run and which control catches it. The result would describe the payment gate, not the vendor's intent. Keep the boundary visible in the place where the work is assigned.
The protocol does not measure whether the invoice was valid. It measures whether the same obligation was paid twice or stopped before release. Write the deadline as a date and a local time. Test the rule on one real transaction before applying it to the run.
Population and unit of analysis
Define the population as invoices submitted for payment during a stated window. The unit is one invoice, with the vendor, the invoice number, the amount, and the payment status recorded. Reissued invoices should be linked to the original. Use the same format for every handover so the next reader can scan it.
Link the invoice to the payment run so the same invoice is not counted twice. A short note with four fields is easier to use than a long narrative. Separate what was observed from what was assumed. Keep the original note beside the corrected version.
Definitions and measures
Define a duplicate as an invoice that matches an earlier invoice on vendor and obligation, even if the number or date differs. Define a catch as a duplicate stopped before payment. Review the first few notes together before the process expands. Ask whether a new reviewer could act on the record without a conversation.
Report the duplicate rate, the catch rate, and the amount at risk. A high catch rate with a large amount at risk may still be a serious control gap. If the source is unclear, route the question instead of guessing. Review the first few notes together before the process expands.
Evidence standard
Link each duplicate to the original invoice, the payment record, and the review note. A note that says duplicate without the original is weak evidence. Record the date and the source so the next reviewer can repeat the check. Review the first few notes together before the process expands.
Record the control that caught the duplicate. The study should distinguish a system match from a manual review. Review the first few notes together before the process expands. Record the exception and the person who approved it.
Sampling and collection
Use a census of the payment runs if the volume is manageable. If sampling is necessary, stratify by vendor and amount. Select the sample before reviewing duplicates. Keep the evidence with the record rather than in a separate log.
Pilot the classification on a few invoices and compare the reviewers. Clarify how a credit and a reissue are treated. Keep the evidence with the record rather than in a separate log. If the source is unclear, route the question instead of guessing.
Analysis and reporting
Report the duplicate and catch rates by vendor and amount band. Show the duplicates that were paid and the recovery status. A paid duplicate is a different finding from a caught one. Keep the evidence with the record rather than in a separate log.
Present the results as a description of the payment gate, not a judgment about the vendor. Name the control that should be strengthened first. Record the date and the source so the next reviewer can repeat the check. Name the owner in the same line as the action.
Limits and sources of error
The study may miss duplicates paid through a different system or entity. State the systems included. Record the exception and the person who approved it. Write the deadline as a date and a local time.
The invoice record may be incomplete, which can make a duplicate look unique. State the evidence used. A control that depends on memory is not yet a control. If the source is unclear, route the question instead of guessing.
Review cadence
Repeat the review after a control change or at the same interval each quarter. Compare the same vendor groups and the same definitions. If the source is unclear, route the question instead of guessing. Keep the original note beside the corrected version.
Assign the follow-up to the AP lead and set a date. The protocol should produce a specific decision about the duplicate check. If the source is unclear, route the question instead of guessing. Record the date and the source so the next reviewer can repeat the check.