Ask any multi-truck service business owner what they dread about the end of the month, and a lot of them will say the same thing: figuring out commissions. The jobs are done, the money came in, and now someone has to sit down and reconstruct which technician did what, add up each person's sales, apply the commission rule, and produce a number that every tech will scrutinize. It's tedious, it's error-prone, and it reliably produces the same argument — a tech who's sure they sold more than the sheet says, and an owner who can't fully prove otherwise because the underlying data was rebuilt from memory and paper tickets.
That argument is a symptom, not the disease. The disease is that commission is being calculated from a source that was never designed to be accurate: a monthly manual reconciliation. The problem is solvable: technician commission tracking software credits each sale to the tech who did the work as the job happens, so the commission report is a byproduct of running the business rather than a month-end project. IntelliDrive OS does this for percentage commission. This guide covers flat-rate versus percentage pay, exactly why the spreadsheet approach falls apart the moment you add a second truck, and how per-sale attribution turns commission math, performance reporting, and "who did that job" disputes into non-events.
Flat-rate vs percentage: pick the behavior you want to reward
Before you track commission, you have to decide what you're paying for. The two dominant structures reward fundamentally different behavior.
Flat-rate commission pays a fixed dollar amount per completed job or task, regardless of the ticket size. Do the lockout, earn the flat amount; do the install, earn the install rate. Flat-rate rewards speed and volume — a tech who closes more jobs earns more — and it's simple to explain. Its weakness is that it doesn't reward the tech for landing a bigger sale, so a flat-rate tech has no built-in incentive to upsell the customer to the better solution.
Percentage commission pays a share of the sale. The bigger the ticket, the bigger the tech's cut, which pushes technicians toward larger jobs, add-ons, and premium options. Percentage rewards selling, not just working. Its weakness is the opposite of flat-rate's: it can nudge techs toward overselling, and it makes every commission number depend on accurate per-sale totals, so sloppy tracking hurts more.
Most established shops land on one or a blend — flat-rate for routine service tasks, percentage on parts and premium installs, sometimes a tiered rate that climbs as a tech hits monthly targets. IntelliDrive OS calculates percentage commission (of gross profit or of revenue); a flat per-job amount or a tiered rate is figured outside it, so decide which model you are paying before you rely on the report. The choice is yours; what the software has to guarantee is that whatever rule you pick is applied to correct numbers. This is the same discipline that governs flat-rate versus hourly customer pricing — the model only works if the underlying totals are trustworthy.
The distinction that trips people up is that your commission structure and your customer-pricing structure are independent decisions. You can charge customers flat-rate for a job while paying the tech a percentage of that flat rate, or bill hourly while paying flat per completed task. What matters for commission is not how you priced the customer — it's that the sale total and the responsible technician are both captured accurately on the invoice, because those two numbers are the entire input to any commission rule you'd ever write. Get either one wrong and every downstream calculation inherits the error.
Why spreadsheet commission math breaks with more than one tech
A single-truck shop can get away with spreadsheet commissions, because there's only one person to attribute jobs to and the owner usually did half of them. Add a second truck and the whole approach starts failing silently. Here's the mechanism.
Spreadsheet commission depends on a human copying every job to the right technician's column, every month, with no missed tickets, no double entries, and no transposed numbers. That's not a workflow — it's a hope. In a busy month with three or four techs running fifteen jobs a day, the reconciliation involves hundreds of line items being manually sorted by memory, calendar, and paper. Three failure modes show up every time:
- A missed job — a ticket that never made it into the sheet — silently shorts a technician, who then feels cheated even though nobody intended it.
- A double-counted job overpays, quietly eroding margin the owner can't see.
- A wrong attribution — the job credited to the tech who didn't do it — starts the argument directly, because now two people have a stake in a number that was reconstructed wrong.
None of these announce themselves. The sheet always produces a number; it just isn't the right number, and nobody can prove which line is off without re-doing the whole reconciliation. Commission math is manual reconciliation in its most argument-prone form, because the person on the other side of the error is standing in your shop asking about their paycheck.
The deeper issue is that the spreadsheet is downstream of the work by weeks. By the time you're reconciling June's commissions in July, the jobs are cold, the details are fuzzy, and every correction is an archaeology project. The fix isn't a better spreadsheet. It's moving attribution upstream, into the moment the job is invoiced.
Per-invoice attribution: capture it in the field, not at month-end
The entire problem dissolves when each invoice records the technician who did the job at the moment the invoice is created. Instead of reconstructing attribution from calendars and memory at month-end, the tech is tagged on the job in the field, when the facts are fresh and nobody has a reason to misremember.
That single tagged field is load-bearing. It feeds three things that used to be separate manual efforts:
- Commission math — each tech's sales total accumulates as their sales complete, so the commission is calculated from the same records that ran the business.
- Per-technician reports — the same attribution powers reports showing each tech's sales, profit, and margin, so you can see who's carrying the volume and who's landing the big tickets.
- Dispute resolution — "who did that job" is answered by the invoice, not by two people's competing recollections.
Because the attribution is stamped when the mobile sale is rung up — often on the tech's own phone, in the field — it's accurate before anyone has a motive to dispute it. Compare that to the spreadsheet, where every number is entered after the fact by someone who wasn't necessarily on the job. The commission report stops being a rebuild and becomes a read-out.
There's a subtler benefit that only shows up once attribution is clean: you can finally trust your per-tech numbers enough to make decisions with them. When commissions are reconstructed monthly, the totals are approximately right at best, which means any conclusion you draw — this tech sells bigger tickets, that one runs more jobs but smaller ones, this hire is paying off — rests on shaky data. Once every invoice carries its technician from the field, the per-tech numbers are exact, and they become a management tool instead of just a payroll input. A number you have to hedge is a number you can't manage by.
Comparing the two ways to run commissions
The difference between reconstructing commission monthly and capturing it per invoice shows up across every dimension that matters to an owner.
| Dimension | Spreadsheet reconciliation | Per-sale attribution (IntelliDrive OS) |
|---|---|---|
| When attribution is captured | Weeks later, from memory | In the field, when the sale is rung up |
| Effort at month-end | Hours of manual sorting | Open the report — it's already done |
| Missed or double-counted jobs | Common, invisible | Largely eliminated — one sale, one credited tech |
| Multiple techs / trucks | Breaks down fast | Rolls up cleanly across all trucks |
| Multiple locations | Merge separate sheets | Reports filterable by shop |
| Dispute over a job | Two memories, no proof | The sale records who was credited |
| Visibility | None until month-end | Commission report updates through the week; weekly email |
| Cost as you add techs | More time per tech | Flat $79/month, unlimited users |
Per-tech reports: coach the week, not the month
Per-sale attribution unlocks something the spreadsheet never could — visibility while the week is still in play. The commission report for the current week updates as sales complete, so you can see before dinner how each truck is doing, and you're not waiting for a month-end report to discover that a tech has been quietly slipping for three weeks.
The weekly commission report makes that visibility actionable: revenue, cost, profit, margin, and commission per tech, with the sales behind each number listed. A tech whose tickets are running small gets a conversation on Wednesday, not a disappointing commission check three weeks later, and the weekly commission email puts the same report in the admin's inbox without anyone opening the app.
For the techs themselves, transparency is a retention tool. A technician who can see their own numbers, and trusts that the commission is calculated from those same numbers, doesn't spend energy suspecting they're being shorted — and in IntelliDrive a tech with report access sees only their own commission, not everyone's. The distrust that spreadsheet commissions breed — the sense that the sheet is a black box the owner controls — evaporates when both sides are looking at the same attributed sales.
Multi-truck and multi-location: the same clean rollup at any scale
The reason attribution scales where spreadsheets don't is that it lives on the sale, not in a separate document that has to be merged. A ten-truck operation across three locations doesn't have three spreadsheets to reconcile into one — every sale already carries its credited technician and its shop, so the per-tech and per-shop totals roll up from a single source. Because inventory and reporting are multi-location by design, the commission side inherits the same clean structure.
This is also where per-user pricing quietly punishes growth. Commission tracking is a feature you need more of as you add technicians — and the field-service platforms that charge per user or per tech get more expensive with every technician whose commission you're trying to compute. IntelliDrive OS is $79/month flat with unlimited users, billed monthly, so tracking commissions for a crew of ten costs the same as tracking two. The tool that solves the multi-tech problem shouldn't get pricier the more techs you have — that's exactly backwards.
The end-of-month commission argument isn't inevitable. It's a direct product of calculating pay from a monthly manual rebuild instead of from the invoices that already recorded who did the work. Move attribution into the field, and commission math, performance reporting, and disputes all resolve to the same trustworthy record — one that was accurate before anyone had a reason to argue about it.
Related reading: The Real Cost of Per-User Field Service Pricing, Crew Scheduling Software for Service Businesses, and When to Switch Field Service Software.
For a complete machine-readable feature and pricing reference, see our LLM reference page.