The $13,000 Paycheck Number That Turned Out to Be $4,062

Payroll in a trades business looks simple until it isn't. Techs close tickets, earn tips, hit commission thresholds, and someone pulls a report and cuts checks. That works fine at five employees with one pay structure. It gets shakier at twelve, and it turns genuinely risky once a company is layering tips, warranty adjustments, diagnostic fees, parts commission, and a standard deduction rule on top of everything else, every single pay period.

The danger rarely announces itself. It's quiet. A pay period boundary shifts by a day. A payroll provider changes its cycle dates without much fanfare. A commission rule gets applied against the wrong week of job data. None of it looks like an emergency in the moment. Then a technician's check comes out thousands of dollars off from what anyone expected, and the whole office is suddenly reverse engineering spreadsheets to figure out which number is actually correct.

That's close to what happened at a growing, multi-technician appliance repair company running a busy field service operation. Nobody was careless. The business had simply scaled past the point where hand calculated payroll could keep up with the number of moving pieces involved in paying a technician correctly.

Every Pay Period, Starting From Scratch

For years, this appliance repair company had run payroll the way a lot of trades businesses do when they're smaller and the math still fits in someone's head: manually, every single cycle. Someone pulled job data out of the field service system, tallied tips, applied warranty adjustments, worked out diagnostic fees, calculated parts commission, and layered a standard 3% deduction rule on top of all of it. Then they did it again two weeks later. And again after that.

We don't need to be doing this manually, manually, manually, every single period. Sitting down and hand calculating tips, warranty adjustments, diagnostic fees, and commission from scratch every two weeks is crazy. There has to be a better way to run this.

That frustration is the natural result of a business that grew faster than its payroll process. An owner running eight technicians in the field, each with a different mix of tips, warranty work, and commission eligible jobs, is effectively rebuilding a small accounting model by hand every fourteen days. It works right up until it doesn't.

For this company, the breaking point was a date mismatch. The business actually ran its pay periods from the 1st through the 14th of each month. The payroll system, meanwhile, was set up to calculate on a 2nd through the 15th cycle, a one day offset that sounds trivial and is anything but. Add in a cycle date change from the company's payroll provider, and the two calendars stopped lining up in ways that were easy to miss and expensive to get wrong. Jobs completed on the boundary days were landing in the wrong pay period entirely, which meant tips, commission, and fees tied to those jobs were being counted, miscounted, or dropped depending on which system's calendar you were looking at.

One Technician, One Massive Number Gap

The mismatch stayed theoretical until it hit a real paycheck. For one technician's pay period, the owner sat down and did the math by hand, the same way it had always been done: tips, warranty adjustments, diagnostic fees, parts commission, the 3% deduction rule, all totaled manually against the jobs that technician had closed. That manual calculation landed at roughly $13,000 owed.

The payroll system, running on its own misaligned dates and without the manual review layered on top, showed something wildly different for the same technician and the same stretch of work: about $3,305. That's not a rounding error or a minor discrepancy. That's a gap of roughly $9,700 between two numbers that were both supposed to describe the exact same technician's pay for the exact same two weeks. One of those numbers was going to determine whether that technician got paid fairly, and neither one, as it turned out, was actually right.

Reconciling Line by Line, Not Guessing

Closing a $9,700 gap between a panicked manual estimate and a broken system output isn't something you fix by splitting the difference. It gets fixed by going back to the source data and rebuilding the number from scratch, one pay component at a time.

That's what happened next. Every line item that fed into this technician's pay got pulled and checked directly against the job records: tips reported on each closed ticket, warranty adjustments applied per job, diagnostic fees charged, parts commission earned on qualifying work, and the standard 3% deduction rule applied consistently across the board. Each of those categories was verified independently rather than trusted as a single lump sum, because a single wrong assumption in any one category is enough to throw off the whole total.

Alongside the line item review, the actual root cause got fixed: the pay period dates in the system were realigned to match the company's real cycle, the 1st through the 14th, instead of the offset 2nd through the 15th window the system had been running on. That single correction mattered as much as the line item audit itself, because as long as the dates were wrong, jobs would keep landing in the wrong period no matter how carefully anyone reconciled the numbers by hand afterward.

This is the part that's easy to underestimate from the outside: a one day calendar offset sounds like a rounding issue. In a job based pay structure with tips, fees, and commission tied to specific completed jobs, it's the difference between a technician getting fully credited for two weeks of work and quietly losing several jobs' worth of pay to the wrong pay period, cycle after cycle, without anyone noticing until the numbers get checked line by line.

Why Manual Payroll Becomes a Silent Risk as You Grow

Every trades business starts somewhere close to manual. When you have three or four technicians, hand calculating payroll is annoying but manageable. The problem is that the risk doesn't scale linearly with headcount. It scales with the number of pay components layered on top of each technician's base pay: tips, warranty work, diagnostic fees, parts commission, deduction rules, and whatever custom incentive structure a company has built to keep good technicians around.

Add a growing team, a busy season, and a payroll provider that changes its cycle dates, and you have all the ingredients for exactly the kind of gap this company hit. The scary part isn't that the error happened. It's how close the company came to acting on either of the two wrong numbers. Paying out the $13,000 manual estimate would have meant a significant overpayment based on a calculation nobody had cross checked against the actual pay period dates. Paying out the $3,305 system number would have meant shortchanging a technician who had earned considerably more than that for two full weeks of real work.

This is the case for moving off manual, cycle by cycle math and toward automated payroll reconciliation that ties directly into the job data a company already has. When tips, fees, commission, and deduction rules are calculated automatically against the correct pay period every time, there's no gap for a date mismatch to hide in, and no technician's paycheck depends on someone getting a manual calculation right under deadline pressure.

The Real Number, and What It Means

After the full line item reconciliation and the pay period correction, the verified number for that technician's pay came out to $4,062. That figure sits nowhere near either of the two numbers that had been on the table. It's roughly a third of the panicked $13,000 manual estimate, and it's meaningfully higher than the broken system's $3,305. Neither the owner's hand calculation nor the misconfigured system had it right, and the only way to find the actual, defensible number was to check every component against the source data and the correct dates.

That's the uncomfortable truth about payroll errors in a trades business: your gut check and your software can both be wrong at the same time, in opposite directions, and there's no way to know which one to trust without doing the reconciliation. A $9,700 spread between two numbers isn't a footnote. It's real money that either goes to the wrong place or gets held back from someone who earned it.

The company didn't stop at fixing this one paycheck. With the pay period dates corrected and every component mapped out clearly, the business moved toward a fully automated payroll process going forward, so tips, warranty adjustments, diagnostic fees, parts commission, and the deduction rule get calculated correctly against the right dates every cycle, without anyone sitting down to rebuild the math from scratch every two weeks.

A Warning Worth Heeding for Any Growing Service Business

This isn't a one-off story specific to appliance repair. Any owner still running payroll by hand, any facility manager coordinating pay for technicians across multiple sites, and any dispatcher trying to reconcile tips and commission against job data is exposed to the same risk. Pay period date mismatches can happen with any payroll provider, not just the one involved here, especially when a provider changes its cycle dates and nobody re-checks that it still lines up with the actual business calendar.

The businesses most exposed are the ones that have grown just enough to make manual calculation genuinely hard, but haven't yet put a system in place to catch the kind of date and line item errors that come with that growth. That describes a lot of field service teams running tips, commission, and incentive pay on top of hourly wages, whether the trade is appliance repair, HVAC, plumbing, or electrical work.

Takeaways Any Trades Owner Can Apply Today

• Confirm your pay period dates match your payroll provider's actual cycle. A one day offset is enough to shift jobs into the wrong pay period without anyone noticing until a check looks wrong.
• Never trust a single number, manual or automated, without a line item check. Tips, warranty adjustments, diagnostic fees, and commission should each be verifiable against the underlying job data, not just totaled and trusted.
• Treat a big gap between your gut check and your system as a signal, not a nuisance. A nine or ten thousand dollar spread on one technician's pay means something upstream is broken, and it's worth finding before you pay out either number.
• Re-verify your setup any time your payroll provider changes cycle dates. A change on their end can silently break the alignment between your real pay periods and what the system calculates.
• Automate the reconciliation, not just the paycheck. Moving tips, fees, commission, and deduction rules into an automated process removes the recurring, error-prone manual step entirely, instead of just making it faster.

Payroll errors in the trades rarely come from someone being careless. They come from growth outpacing the process, one pay period at a time, until a single technician's check exposes how much was riding on math nobody had fully checked. Fixing it once is good. Building a system so it never has to be fixed again is better.