How to Pay Flat-Rate Automotive Technicians Accurately

Last updated: September 2026

Why Flat-Rate Pay Is So Difficult to Get Right

Flat-rate pay, sometimes called flag hour or book time pay, is standard across automotive dealerships and independent repair shops. A technician is paid a fixed number of hours for each job completed, regardless of how long the work actually takes. A brake job might pay 1.8 hours whether it takes 45 minutes or 3 hours.

In theory, this creates strong productivity incentives. In practice, it creates some of the most complicated payroll calculations in any industry, and some of the most common wage violations. Mishandling flat-rate pay leads to underpaid technicians, FLSA overtime violations, and, increasingly, class action lawsuits.

How Flat-Rate Pay Works

Each repair job is assigned a standard time value, typically pulled from a labor time guide (Mitchell, Alldata, or the OEM’s own guide). When a technician completes that job, they earn the flat-rate hours, regardless of actual clock time. A tech who earns 40 flat-rate hours in a week with 45 hours on the clock still gets paid for 40 hours. One who earns 50 flag hours in 40 clock hours gets paid for 50.

This creates two distinct calculations your payroll team must track separately:

• Flag hours earned: the billable time assigned to completed jobs
• Clock hours worked: the actual time the technician was at the shop and available for work

Both matter. Clock hours determine overtime liability. Flag hours determine straight-time earnings. Getting either wrong produces a payroll error, and potentially a wage claim.

The FLSA and Flat-Rate Technicians

Flat-rate technicians are non-exempt employees under the FLSA, which means they’re entitled to overtime pay for all hours worked beyond 40 in a workweek. This is where most automotive payroll errors occur.

The Fluctuating Workweek Trap

Some dealerships attempt to pay flat-rate technicians using the FLSA’s fluctuating workweek method, which allows overtime to be calculated as a half-time premium on top of a fixed weekly salary. The DOL has issued guidance clarifying that this method is generally not appropriate for flat-rate technicians, because their pay varies week to week based on production rather than being a fixed salary.

Calculating Overtime on Flat-Rate Earnings

When a flat-rate technician works more than 40 clock hours in a week, overtime must be paid. The calculation uses the technician’s regular rate of pay for that workweek, which is their total flat-rate earnings divided by total hours worked (not flag hours earned).

Example:

• A tech earns 42 flag hours at $22/flag hour = $924 straight-time earnings
• The tech worked 48 clock hours that week
• Regular rate = $924 divided by 48 hours = $19.25/hour
• Overtime premium = $19.25 x 0.5 x 8 overtime hours = $77
• Total pay = $924 + $77 = $1,001

Note that the technician already received straight-time pay for the overtime hours through their flag earnings. The FLSA only requires the additional half-time premium, but it does require it, and dealerships that skip this calculation are underpaying their technicians and violating federal law.

Minimum Wage in Slow Weeks

If a technician has a slow week and their flat-rate earnings fall below what they would have earned at minimum wage for their clock hours, the employer must make up the difference. You can’t legally pay a technician less than minimum wage simply because the shop was slow or the work took longer than book time.

Most dealerships address this with a “guarantee,” a minimum weekly pay floor. But the guarantee must be calculated correctly, and it must cover all clock hours at the applicable minimum wage rate, not just scheduled hours.

Common Flat-Rate Payroll Errors at Dealerships

Using Flag Hours to Calculate Overtime Instead of Clock Hours

Overtime is triggered by clock hours over 40, not flag hours over 40. A tech who earns 35 flag hours but clocked 42 hours has still worked 2 hours of overtime. Many dealerships incorrectly use flag hours as the overtime threshold and underpay as a result.

Excluding Bonuses and Incentives from the Regular Rate

If a technician receives productivity bonuses, come-back bonuses, or other non-discretionary incentive pay, those amounts must be included in the regular rate calculation before computing overtime. Excluding them understates the overtime premium owed.

Not Tracking Clock-In and Clock-Out Times

Some dealerships track flag hours carefully but have no reliable system for tracking clock time. Without accurate clock-hour data, you can’t calculate overtime liability or minimum wage compliance. This is a significant audit exposure.

Failing to Pay for Non-Productive Time

When technicians are required to be at the shop but have no work assigned, waiting for parts, attending mandatory training, participating in required meetings, that time is compensable under the FLSA. It counts toward clock hours and therefore toward overtime calculations, even if no flag time is earned.

Trusting a Clock-Out Your DMS Generated for You

Worse than having no clock data is having clock data that is quietly wrong. An office manager at a Chrysler Dodge Jeep Ram store found her system stamping a six o’clock clock-out on employees whether they left at five or not. The record looks complete. It was generated, not recorded.

Her response is the only one available when you cannot trust the source. Every hourly employee’s punches get verified by hand, every pay period, before anything else happens. Flagged hours then get chased separately against a nine in the morning cutoff on payroll day, and anything that misses it waits a week.

If your DMS closes the day automatically, find out what time it uses and who can override it. An automatic clock-out that runs late inflates your overtime liability. One that runs early understates it, and that is the expensive direction to be wrong in.

Getting Flag Hours Out of Your DMS and Into Payroll

The compliance math above assumes the numbers arrive in payroll cleanly. For most dealerships, they don’t. This is the part nobody puts in a demo, and it’s where the hours actually go.

Here’s a real pattern. A warranty administrator at a 230-employee dealer group pulls the flat-rate report out of the DMS every pay period, prints it on paper, and hand-keys the numbers into a CSV upload file. Not because she likes retyping. Because the export fields don’t map to the payroll system’s earning codes, and manipulating the file takes longer than re-entering it.

Another group of five stores collects a weekly spreadsheet from each service manager covering flag time, production bonuses, and spiffs, then cuts and pastes all five into payroll. A third dealership rebuilds its payroll spreadsheet from scratch every single cycle because the column layout doesn’t persist between runs.

Why the Mapping Breaks

Technicians in the same shop are rarely paid the same way. A typical service department has some techs on pure flat rate, some on clock hours plus a dollar amount per flagged hour, and quick-lube techs who fall back to a separate hourly rate in weeks they don’t flag enough. Union shops add another layer, with rate tiers that shift based on flag hours turned and separate rates for warranty and light-duty work.

A payroll system that only accepts one earning type per employee can’t represent that. So somebody rebuilds it by hand each cycle.

And Then the Journal Entry

The trip back to the DMS causes as much trouble as the trip out. One office manager described exporting payroll to Excel, then reformatting it before her DMS would accept the journal entry: find and replace, strip the spaces, no blank cells anywhere, everything exact. She also found amounts posting to account numbers nobody recognized, left over from a setup she inherited and couldn’t correct without a support ticket.

Add it up and you get what several controllers reported independently: two to three days per cycle on a payroll of 45 to 100 people. That’s not a compliance problem. It’s just time, every two weeks, forever.

The cost isn’t spread evenly across your runs, either. The same office manager above processes two payrolls: the semi-monthly salaried one takes about ninety minutes, and the hourly and technician one takes four hours. Almost all of that gap is reconciliation.

The extreme version of this shows up in adjacent trades, and it’s worth knowing about because it’s where dealerships end up if clock tracking quietly lapses. At a heavy equipment sales, service and rental company, mechanics clock into work orders and out of work orders all day and never clock in for the day at all. There’s no attendance record sitting opposite the billed time, so there’s nothing to reconcile against and no way to tell whether what the work order says matches what happened. What their operations lead asked for wasn’t a better report. It was a punch at the start and end of the day.

When you evaluate a platform, test this specifically. Ask to see your own DMS export loaded, with more than one technician pay type in the file, and then ask to see the journal entry it produces going back the other way.

How PTO Accrual Works When There Are No Clock Hours

Most accrual rules are written against hours worked. Flat-rate technicians break that assumption, because the system may have no hourly record to accrue against.

The consequence is predictable. One office manager at a 45-person store couldn’t set her techs up as hourly employees at all, so their hours landed in a separate column and PTO stopped accruing entirely. She now maintains a second spreadsheet that divides earnings by hours to derive an hourly equivalent, updates it monthly for every technician, and manually enters the result whenever someone takes a day.

Pick an Accrual Basis the System Can See

You have a few workable options, and any of them beats a spreadsheet:

• Flat per-pay-period grant. Simplest to administer and easiest for technicians to understand.
• Accrual against clock hours. Works if you’re already capturing clock time for overtime compliance, which you should be.
• Front-loaded annual bank with a carryover cap.

Then Decide What Rate You Pay It At

Accruing the time is half the problem. Paying it is the other half, because a technician has no standing hourly rate to pay a vacation day at.

Most dealerships settle on a rolling average, commonly the last 90 days of earnings divided by hours in that window. That’s a reasonable approach and it’s fair to the technician. It only works, though, if the system recalculates it. Doing it by hand every month for every tech is how it quietly stops happening.

One more detail worth checking, because it produces employee complaints out of proportion to its size: confirm whether your system debits a balance on the date the time was taken or on the check date. Debiting on the check date charges a day off against the wrong accrual year whenever a request falls near an anniversary. Technicians notice that before payroll does.

What Good Flat-Rate Payroll Requires

Paying flat-rate technicians correctly requires your payroll system to handle several things simultaneously:

• Separate tracking of flag hours earned and clock hours worked
• Weekly regular rate recalculation based on total earnings divided by total hours
• Overtime half-time premium calculated on the correct regular rate
• Minimum wage floor comparison and automatic adjustment when earnings fall short
• Inclusion of all non-discretionary pay in regular rate calculations
• Accurate tracking of non-productive compensable time
• More than one pay type on a single technician, without a workaround
• A defined PTO accrual basis and payout rate for employees with no standing hourly rate
• A DMS import and a general ledger export that don’t need reformatting by hand

Spreadsheets and manual calculations make this process error-prone and time-consuming. A payroll platform built to handle automotive pay structures eliminates most of the manual work and the risk that comes with it.

How Netchex Supports Automotive Payroll

Netchex payroll supports the complex pay structures common in automotive dealerships, including flat-rate pay configurations, overtime calculations based on clock hours, and multi-rate pay for technicians who work at different labor rates. The platform integrates with dealership DMS systems, reducing double-entry and the errors that come with it.

Because time and attendance and payroll share one record, clock hours and flag hours sit together rather than being reconciled between systems, and accrual rules can run against a basis the system actually holds. A technician can carry more than one pay type without a monthly spreadsheet standing in for the configuration.

When your payroll calculates correctly every time, automatically, your service managers spend less time fixing pay errors and your technicians spend less time questioning their paychecks.

Frequently Asked Questions

This guide reflects publicly available product information and independent reviewer data (G2, Capterra, Trustpilot, Yelp, Better Business Bureau, Reddit, Software Advice, GetApp) as of 2026. Feature availability and pricing may vary by plan. Contact each provider for current details.

Disclaimer: Any product roadmap or future plans provided herein are for informational purposes only. They do not represent a commitment to deliver any material, code, feature, or functionality. Plans may change without notification. The development, release and timing of any features or functionality described remain at the sole discretion of Netchex, its affiliates, and partners. Netchex does not give legal, tax, or accounting advice. You are responsible for ensuring your use of Netchex product meets your individual business and compliance requirements.

Print this page