A payroll audit checklist usually asks someone to sample transactions and confirm that classifications, hours and tax withholdings look right, the same list whether or not anything actually changed. It catches an error a reviewer happens to look at directly. It does not catch a change: a rate, a deduction, a direct-deposit account, different this period than last for a reason nobody approved. Payroll schemes run a median 18 months before detection and account for 10 percent of occupational fraud cases studied by the Association of Certified Fraud Examiners (ACFE, 2024 Report to the Nations).
At Marloe Logistics, 240 employees, this period's register differs from last period's in 34 rows. Cross-checking each against the approved change log explains 31: merit increases, a benefit tier change, a new dependent. Three do not match anything on file. Owen McAllister's raise, sized against his compensation band, was approved at $33.00 an hour; the register shows $34.50, a $120 keying error. Farrukh Islam's rate rose to $31.50 with no raise on file anywhere, $280 this period. Bianca Souza's direct-deposit account changed with no request logged, putting $2,150 at risk.
The pack opens with the Audit Procedure and Correction Guidance, then the Change Register listing every row that differs between two periods. Exception Flags carries the three unexplained rows forward, priced and prioritized. The Correction Log records what each turned out to be: Owen's was corrected, Bianca's was legitimate, Farrukh's is still open, feeding a total rewards statement only as trustworthy as the register beneath it. A state auditor's fraud alert advises reviewing the system's own change log for unauthorized changes, not just the amounts (Arizona Auditor General).