The Pre-Payroll Review That Catches Errors Before the Money Leaves

Ninety percent of your employees are salaried. Their pay shouldn’t change from one run to the next. So if it does, that’s either a raise you know about or a mistake you don’t.

That’s the whole logic behind a pre-payroll review, and it’s the single cheapest control most employers aren’t running. Not a deeper approval chain. Just a comparison against last time, read by a human, before the file goes.

Last updated: September 2026

Compare this run to the last one

An oil and gas consultancy with about 100 employees does exactly this, and their HR director was clear it’s the thing she’d refuse to give up in a system change.

She runs a comparison report against the previous payroll before she submits. Anyone whose pay moved appears with the variance. She marks anything unexpected, exports it, and sends it to the CFO. He looks at the exceptions only, not 100 rows. Then she processes.

Her description of it was simple: that’s her checks and balances. Two people, ten minutes, and every unexplained change gets looked at by someone who didn’t enter it.

When the reviewer wasn’t there

A hotel group processes payroll centrally for 12 properties. General managers approve time at each property. By the time it reaches corporate, nobody in the building knows who actually worked.

Their operations director framed the question precisely. Once it gets to their office they can’t verify who worked and who didn’t, so what they look for is anomalies and notable variances against prior weeks. That’s the only review available to them, and it’s a good one, but they were doing it by eye.

This is the normal shape of multi-location payroll. The person with the knowledge and the person with the button are in different buildings. Variance analysis is what bridges that.

The parallel spreadsheet nobody wants to keep

A manufacturer’s HR manager runs her own spreadsheet alongside every payroll. Her reason was defensive and entirely fair. She’s relatively new, the system has repeatedly miscalculated holiday and differential pay, and she isn’t willing to be blamed for it.

Her line was that it’s never right. So she checks.

A refugee nonprofit does something similar at a smaller scale and more formally. Their payroll manager builds a spreadsheet, finance reviews it, HR reviews it again, then it’s keyed into the system. Three reviews, 38 employees. Their head of HR noted she used to run payroll for hundreds of people in less time. She also credited that spreadsheet with being the only reason errors hadn’t reached employees.

The digit that would have cost eighty thousand dollars

A hospice owner still handwrites every check, and he’s aware that sounds absurd. His reasoning is worth hearing anyway.

He said he likes the pain of writing them, because he knows every penny and where it’s going, and if it gets too easy he’ll stop paying attention. Then he gave the example that proves his point. He once entered a chaplain’s mileage as 115,000 miles instead of 1,150. The resulting payment would have been roughly eighty thousand dollars. He caught it because he was looking.

He’s not wrong about the risk. He’s wrong about the only available control being friction. A variance check would have flagged that line instantly, without requiring him to hand-write anything.

What to look at before you submit

• Gross pay variance against the prior run, by employee, with a threshold so only real movement surfaces
• Anyone active with no hours and no pay. One restaurant group runs this every cycle and had 25 names on it recently, a mix of people who hadn’t started yet and people who never showed up
• Anyone terminated who still appears, and anyone paid who shouldn’t have been
• New or changed deductions, particularly anything that appeared without a corresponding request
• Banking changes since the last run, which is where both fraud and simple error concentrate
• Outliers on the extremes. The largest and smallest checks, which is where a decimal point error announces itself

The Department of Labor’s recordkeeping requirements assume you can evidence what was paid and why, and PayrollOrg publishes practical guidance on pre-processing controls. Both point the same direction: catching it before release is dramatically cheaper than a correction afterward, as our post on what a payroll error really costs sets out.

Approval and detection are two different controls

A community bank’s HR lead does all the preparation, then has to chase an approval by email before she can process, with no record of it kept in the system. She has the sign-off. What she doesn’t have is anything telling the approver what changed.

That’s the gap worth closing. An approval without a variance report is a signature on a total. Running payroll and tax on the same platform as time and attendance means the comparison is generated from live data rather than rebuilt in Excel, and HR changes that drove a variance are visible next to the number they moved.

Frequently Asked Questions

This guide reflects publicly available product information and independent reviewer data (G2, Capterra, Trustpilot, Yelp, Better Business Bureau, Reddit, Software Advice, GetApp) as of 2026. Feature availability and pricing may vary by plan. Contact each provider for current details.

Disclaimer: Any product roadmap or future plans provided herein are for informational purposes only. They do not represent a commitment to deliver any material, code, feature, or functionality. Plans may change without notification. The development, release and timing of any features or functionality described remain at the sole discretion of Netchex, its affiliates, and partners. Netchex does not give legal, tax, or accounting advice. You are responsible for ensuring your use of Netchex product meets your individual business and compliance requirements.

Print this page