Outsource Payroll Company guide
Catch Duplicate Payroll Payments Before the Bank File Leaves
Published

A payroll operations routine for finding duplicate payments before release, with matching keys, stop rules, and a named owner decision.
Payroll handoff readiness check
Use this table before a provider or Filipino payroll support worker receives access.
| Work area | Ready to hand off when | Owner check |
|---|---|---|
| Matching keys | employee ID, bank account, net amount, and effective date agree | payroll manager confirms the key set for the cycle |
| Candidate review | each flagged row carries a reason and a named reviewer | owner decides release, hold, or correction |
| Release evidence | bank file row count and total match the approved register | reviewer signs the release record |
Why duplicates survive an ordinary register review
A duplicate payment rarely looks wrong in the register. Two rows can carry the same employee, the same net amount, and two reasons that each sound plausible. The first review often passes because the reviewer checks whether a payment belongs to the period, not whether an identical payment already exists. That gap is why the duplicate test has to run as its own step before the bank file is released.
Most repeat payments begin upstream. A retro adjustment that was already paid, a rehire record that recreated an active assignment, or an off-cycle request submitted twice under different ticket numbers can all produce a second row. The register inherits each one without a warning. Waiting for the bank to reject a duplicate is detection after the money has moved, and recovery then depends on the employee or the bank cooperating. Prevention belongs in the release path, where the payroll manager still has a choice.
The review also needs a memory longer than one cycle. A payment released last period can be resubmitted this period with a new ticket and a fresh approval, and the current register will look perfectly normal. Comparing against the prior register and the last released bank file closes that gap. Without the backward look, the control only catches duplicates that happen to land in the same run.
Build the test before the bank file
Start from the approved register and build a stable key for each row. Employee ID, bank account, net amount, and effective date form a stronger combination than name plus amount, because names repeat and amounts are rounded. Add the payment type when the payroll system allows it, so a regular wage and a bonus with the same net value are not treated as one another. Write the key into the cycle checklist so the test does not change shape between reviewers.
A useful test flags candidates rather than declaring guilt. Sort the register by the key and show every group with more than one row, along with the source document behind each entry. Run the same comparison against the prior two pay periods to catch a repeat that crosses cycles. Keep the output small enough for a person to read, because a list of hundreds of warnings will be dismissed before anyone investigates the first one.
Separate a true duplicate from a legitimate repeat
Some employees genuinely receive two payments in one cycle. A final paycheck and a separate bonus, a correction paired with a reversed original, or two cost centers paying a shared assignment can all be valid. The reviewer needs to see the business reason, the approving document, and the accounting treatment before calling the row a duplicate. A flag without that context is only a coincidence of numbers.
Ask three questions of every candidate. Does a released payment already exist for the same work period, and can its confirmation be located? Is the second row supported by a document that the first row did not cover? Would releasing both leave the employee with a recoverable overpayment? The payroll manager answers the release question, while the specialist assembles the comparison and records the reasoning. A decision to release both should name the reason in the register note.
Set a stop rule the team will actually follow
A stop rule needs a clear trigger and a named person who can clear it. For example, any flagged group above a set amount holds the bank file until the payroll manager records a decision. Smaller flags can move with a second reviewer's note, but they still need a disposition before close. The threshold should reflect the employer's risk, not a number copied from another company.
Write the rule where the release happens, not in a policy folder nobody opens at cutoff. Put the hold reason in the same tracker as the payment, and give the backup approver authority to act when the primary owner is unavailable. Test the rule once with a harmless sample so the team knows what a hold looks like. A control that only exists during an audit is not a control.
Work one duplicate case end to end
Suppose a specialist finds two rows for the same employee, same net pay, and the same effective date. The first row links to a released off-cycle payment with a bank confirmation. The second links to a ticket that describes the same missed hours but carries a later ticket number. The specialist marks the pair, attaches both documents, and holds the bank file without editing either row.
The payroll manager reviews the evidence and confirms that only one payment was owed. The second row is reversed in the payroll system before release, and the reversal is linked to the original case. The manager records why the duplicate was created and which intake step should have caught it. The correction lands in the next cycle's checklist, and the case closes with both the reversal and the prevention note attached.
Close the loop with a prevention change
Count the duplicate candidates found each cycle, how many were confirmed, and how many were released with a documented reason. A rising candidate count can mean better detection or a worsening intake process, so read it beside the confirmed count. If one source keeps producing repeats, fix that source instead of adding another reviewer. The goal is fewer chances to pay twice, not a longer queue.
Review the test itself at a fixed cadence. Check whether the matching keys still fit the payroll system, whether new payment types create blind spots, and whether reviewers understand the stop rule. Keep a short sample of past cases so a new analyst can see what a good decision record looks like. A duplicate control earns trust when the team can show what it caught, what it released, and why.
Copy-ready brief
Payroll support role brief
Replace the tool names and owner details, then use this list in a provider call or job brief.
- Specialist assembles the candidate list, evidence, and release comparison.
- Payroll manager decides whether a flagged payment is released, held, or reversed.
Questions from payroll buyers
Who decides whether a duplicate candidate can be released?
The authorized payroll manager decides, after reviewing the source documents and the existing payment confirmation.
What closes a duplicate-payment case?
A recorded disposition linked to the payment rows, the evidence reviewed, and any correction or prevention step.
Sources
- IRS Publication 15 (Circular E)Employer payroll reporting and withholding context.
- U.S. Department of Labor Wage and Hour DivisionPayroll recordkeeping and wage-payment guidance.
- U.S. GAO Assessing Data ReliabilityChecks for completeness and provenance in operational data.
- NIST Cybersecurity Framework 2.0Control and monitoring outcomes relevant to payment files.