That quiet payroll error cost me $1,700 before I caught it

I run a small shop in Omaha with 8 people on staff. Around January I kept seeing our biweekly total creep up by a few hundred dollars, and I figured it was just overtime from a rush project. Then last Tuesday I actually checked the export file line by line instead of skimming the summary. One of my senior folks had been accidentally clocking out at 5:30 PM instead of 5:03 PM, and the system rounded that to a half hour each day. Over 3 months that added up to about $1,700 in overpayments. I wrote a little script to flag any clock out that lands within 7 minutes of a boundary, and now we catch it before payroll runs. Has anyone else had a silent payroll error that took way too long to spot because the numbers looked normal every time?

0 comments

0 Comments

No comments yet

Be the first to share your thoughts on this discussion.