Post: The $27K Spreadsheet Error: What David’s Payroll Mistake Teaches HR Leaders
David, an HR manager at a mid-market manufacturer, watched a manual re-entry error move a $103K figure into the system as $130K, a $27K overpayment that surfaced only when an employee questioned their own paycheck. The employee quit once the error was corrected. The failure wasn’t the typo. It was the missing bridge between two systems that let the typo travel unchecked.
Result: $27K overpayment, undetected until an employee flagged it
Method: Manual data re-entry between ATS and HRIS, no validation step
Entity: David, HR Manager, mid-market manufacturing
This case study accompanies From Spreadsheets to Systems: How HR Leaders Can Escape Broken, Disconnected Tooling and illustrates the cost of the manual bridges that guide is built to eliminate.
Context
David’s team ran compensation data through a familiar pattern: a figure entered in one system, manually re-typed into another, with no automated check between them. A $103K compensation figure, correctly recorded in the source system, was re-typed as $130K during a manual transfer into payroll. Nothing in the process flagged the discrepancy. The number simply moved forward, unchecked, into a live paycheck calculation.
Approach
There wasn’t one, and that’s the point of this case study. The gap wasn’t a broken tool. Both systems worked exactly as designed. The gap was the manual step between them, a re-entry point with no validation layer to catch a number that had drifted outside a reasonable range.
This is the pattern behind the broader argument in What Is a System of Record in HR?: without one authoritative source that other systems read from directly, every manual re-entry point is a place where two systems can disagree without anyone noticing, until the disagreement has real financial consequences.
Implementation
There was no implementation, because there was no system to catch the error before it processed. That absence is the actual subject of this case study. A validation rule as simple as flagging any compensation figure that changes by more than a small percentage during a transfer would have caught this before it reached payroll. No such rule existed, because the transfer itself was never treated as a step worth automating or validating.
| Metric | Value |
|---|---|
| Correct compensation figure | $103,000 |
| Figure entered in error | $130,000 |
| Resulting overpayment | $27,000 |
| How the error was caught | Employee questioned their own paycheck |
| Outcome | Employee resigned after correction |
Results
The $27K overpayment was eventually corrected, but the correction came after the employee had already noticed, questioned, and lost confidence in the accuracy of their own pay. The employee resigned shortly after the correction was made. The financial cost was real. The trust cost, both for that employee and for how the broader team viewed HR’s data accuracy, outlasted the dollar figure.
Lessons Learned
An employee catching a payroll error is the most expensive way an organization can find one. By the time it reaches a paycheck, the mistake has already cost money, and the person who caught it has already started questioning whether HR’s numbers can be trusted. A validation step between systems, or a single system of record removing the re-entry point entirely, would have caught this before it ever reached a human decision to worry about it.
Expert Take
Nobody in David’s story was careless. That’s what makes this case study worth telling. A capable person made a typo, the way anyone eventually does, and the system had no way to catch it. Blaming the person who typed the wrong number misses the actual fix. The fix is removing the point where a typo can travel unchecked into a paycheck, not training someone to type more carefully.
For the framework on building a single system of record that removes this exact re-entry point, see What Is a System of Record in HR? For what a connected alternative looks like in practice, see 207% ROI: How TalentEdge Replaced Spreadsheets with Connected Systems.
RELATED POST
