Fox & SantiagoTechnology, applied.Call (877) 244-9687

Problem guide

Hours logged to the work don't match the timesheets

Hours logged to the work and hours on the timesheet disagree because they are two different records. The work record holds time spent on a customer's order, ticket or job. Payroll holds every paid minute, including setup, the morning meeting, supply runs and travel between sites, which federal rules count as hours worked. Then edits land in one system and not the other. In ServiceTitan's legacy job costing, for example, an edited past timesheet leaves job cost unchanged until payroll is updated for that period.

Hands typing a handwritten work ticket into a computer late at night

How it actually happens

A work record and a timesheet answer different questions. The ticket, order or client time entry says how long someone worked for this customer. The timesheet says how long the company owes that person for. The two were never meant to be equal, and most businesses have no written rule for the hours that sit between them.

Start with the morning. A service technician reports to the shop at 7:00, loads fittings and a recovery machine, hears the day's board at a short meeting, and taps travel to the first call at 7:40. If the dispatch status starts the clock, those 40 minutes belong to nobody. If the technician clocks in at the shop, they are paid with no job attached. Federal rules side with the clock: travel from a place the employee must report to for instructions or tools is part of the day's work under 29 CFR 785.38. A technician on Reddit's r/HVAC described the other version in 2024: time started at the first travel tap and ended at the last completion, and he was told mistakes could only be fixed once a year.

The same shape shows up away from the field. A warehouse associate punches in at 6:00 and scans the first pick for a client at 6:20. A staff accountant clocks a full day and logs six hours to client engagements. The paid hours are real, and nothing on the work side says where they went.

During the day the split repeats. Travel between sites is hours worked. The supply run is hours worked. Rework on last month's order is hours worked. On the work record, each of those is either missing or coded to whichever job or client was open on the screen.

Then the corrections start, and they are made in different places. A manager fixes a forgotten clock-out in the field system on Tuesday. The payroll administrator fixes a different person's Thursday in Gusto or QuickBooks on Friday. With Jobber, the next sync overwrites the Gusto fix with the field number. With ServiceTitan's legacy job costing, the Tuesday fix does not reach the job until someone refreshes payroll for that period. In QuickBooks, a community responder explained in 2023 that hours added on the paycheck rather than the timesheet show as Not Specified on the project, as designed.

Construction adds a file transfer and a classification. Procore exports hours to Sage 300 CRE as a text file that payroll imports, so any change after export is entered twice. On prevailing wage jobs, an hour in the wrong classification is not a rounding issue: without an accurate split, the whole day is owed at the highest applicable rate.

By month end the cost report and the payroll register are both correct about what they hold, and the difference between them is a pile of small decisions nobody wrote down.

Why it matters past payroll

Every unassigned hour is labor cost that lands in overhead instead of on a job, client or order. Margins by customer look better than they are, and prices get set from them. The hours do not disappear; they just stop showing which work they belong to.

Signs you have this problem

  • Hours charged to jobs, clients or orders for the week come in well under the hours on the payroll register
  • A correction made in the payroll provider is gone after the next sync
  • The first hour of the day, spent setting up, loading or in the morning meeting, appears on no work record
  • Cost reports still show last week's hours after the office fixed a timesheet
  • On prevailing wage work, nobody can say how many hours a worker spent in each classification

What usually causes it

  • Paid time and time on the work are captured by different events, so setup, supply runs and travel between sites land only on the payroll sideThe field-to-office split
  • Hours corrected in the payroll provider or the accounting system never travel back to the system where the work is loggedThe re-entry trap
  • Forgotten clock-outs, overlapping entries and split classifications are fixed one at a time by whoever noticesThe exception swamp
  • Edited timesheets wait for someone to refresh payroll data before the cost of the work catches upThe invisible queue

Find your cause

Ask these in order. The first yes is usually where yours starts.

  1. Do people clock in when they arrive but start logging time only at the first customer, ticket or order?If yes: the gap is the start and end of the day. Write the paid-time rule for that first hour and give it a code.
  2. Does anyone correct hours in the payroll provider or in the accounting system after export?If yes: the correction is not reaching the system where the work is logged, and some syncs will overwrite it. Pick one place to edit.
  3. Do cost reports change only after payroll is processed, or not at all after an edit?If yes: the cost of the work is waiting on a payroll refresh. Make the refresh part of every edit.
  4. Are forgotten clock-outs and overlapping entries fixed by the office every week?If yes: the clock is driven by events people do not always trigger. Count how many and which ones before changing settings.
  5. Does anyone on covered work switch classifications during a day?If yes: the payroll must split those hours, or the highest rate applies to all of them.

How it breaks in each industry

HVAC, plumbing and electrical service
Many companies let dispatch statuses run the clock: the day starts when the technician taps travel to the first call and ends at the last completion. Anything outside that window, such as loading at the shop or a stop for parts after the final call, is paid time no ticket carries. Callbacks and warranty visits add hours that the flat-rate invoice never reflects.
Commercial mechanical and construction
Crews log time in Procore, Foundation or a paper sheet by cost code, and payroll runs from a separate file. Procore hours reach Sage 300 CRE as an exported text file that payroll imports, so a timesheet changed after export has to be changed twice.
Logistics and third-party warehousing
Hourly associates clock in at a terminal, while labor is charged to each client account by task in the warehouse system so it can be billed. Time between tasks, waiting on a dock door or moving between client areas, is paid and belongs to no account, and a punch fixed in payroll never reaches the client labor report.
Accounting and professional services firms
Nonexempt staff record time to client engagements in the practice system and punch or report paid hours to payroll separately. Admin time, training and work on an engagement that was not set up yet sit on the payroll side only, and a missed entry corrected for payroll stays missing from the client's time record.

Where it breaks between systems

ServiceTitan timesheets and ServiceTitan job costing
In the legacy job costing model, payroll data is not re-synced when someone edits a past timesheet. Job costing keeps the pre-edit hours until a user updates payroll for that technician and period from Payroll Approval.[1]
ServiceTitan and an outside payroll provider
ServiceTitan says every timesheet edit must be made in ServiceTitan before export. Hours changed only in the payroll system leave job costing wrong. It also states that burdened labor cost in job costing and actual payroll cost will almost never match to the penny, because one is an estimate from the labor burden rate and the other is the check.[2]
ServiceTitan idle time and paid hours
If Simple Clock I/O is not enabled, idle time between a technician's clock-in and the first paid event is not paid, whatever the idle settings say. A forgotten clock-out is set to the end of the last activity. Both rules decide paid hours without anyone looking at a ticket.[3]
Jobber and Gusto
Approved Jobber timesheet hours, including edits, sync to Gusto and overwrite any hours already in Gusto. A fix typed into Gusto is replaced by the Jobber figure at the next sync.[7]
Housecall Pro time tracking
Housecall Pro tracks clocked-in time and time on jobs under two separate settings, employees clock in and out only in the mobile app, and the office edits times afterward. With travel and job tracking off, paid hours and job hours are different records by setup.[8]
Procore Timesheets and Sage 300 CRE
Timesheet data leaves Procore as a .txt file that payroll imports through Tools, Import Time. Records that cannot be converted go to an error file, Procore's Time Type becomes the Sage Pay ID, and the ERP integration only fills in project, sub job and cost code automatically.[9]
Simpro and QuickBooks Time (SyncEzy)
SyncEzy documents three common rejections: a schedule entry shorter than 15 minutes is not inserted, rounding set to 15-minute blocks on one side and 30 on the other does not match, and a timesheet logged to a job without a section and cost centre fails.[10]
Simpro and Xero
Simpro does not post labor cost to Xero. Only hours against each schedule rate are sent, so labor dollars in the books come from payroll, not from the job.[11]

By the numbers

FigureWhat it measures
97.1% median, 66.9% at the 10th percentile[12]Billing capture, hours invoiced divided by hours logged on jobs, across 963 contractor companies with at least 100 job-logged hours (Level, a contractor accounting firm, vendor benchmark, May 2025). One company in ten bills about two of every three logged hours.
8.8 paid hours, 5.7 billable[13]Average HVAC technician day across more than 10,000 data points from 300 HVAC companies, with 1.13 hours a day of driving not recovered through trip charges or flat rates (Field Promax customer data, vendor study reported by ACHR News, June 2026). It measures paid against billable time, not timesheet errors.
39.2 hours[14]Average weekly hours for construction employees, September 2026, seasonally adjusted. BLS counts the hours for which pay was received, which is the payroll record, not the ticket (FRED series AWHAECON, updated October 2, 2026).

Rules that apply

29 CFR 785.38, travel that is part of the day's work[15]
Travel from a place the employee is required to report to for instructions, other work or to pick up tools is hours worked regardless of contract, custom or practice, and so is travel from job site to job site during the day. This is the drive most tickets leave out.
29 CFR 785.35, home to work travel[16]
The ordinary drive from home to the first site and back home at night is not worktime, whether the employee works at one location or many. The line between this and 785.38 is where most drive-time arguments sit.
DOL Wage and Hour opinion letter FLSA2020-16 (November 3, 2020)[17]
Foremen who must pick up the company truck at the shop, drive it to the site and return it are on paid time for that travel, because the truck is integral to their work. The letter also says a required report location alone does not make the drive paid, and helpers who choose to meet at the shop and ride along are commuting.
29 CFR 516.2(a)(7), 516.5(a) and 516.6(a)(1), FLSA records[19]
Payroll records must show hours worked each workday and each workweek and be kept 3 years from the last entry; the time cards with daily start and stop times behind them are kept at least 2 years.
29 CFR 785.48(b), rounding[22]
Rounding to 5 minutes, a tenth or a quarter hour is accepted only if, over time, it does not shortchange employees for time actually worked. A system that rounds one way and a payroll that rounds another produces a standing difference.
29 CFR 5.5(a)(1)(i) and WH-347 Column 3, work in more than one classification[23]
A worker may be paid each classification's rate for the time in it only if payroll records accurately show the time spent in each. Per the WH-347 instructions, without that breakdown the worker is paid the highest applicable prevailing rate for all hours. Certified payroll is due weekly under 5.5(a)(3)(ii)(A).

Measure it in your own shop

From: Two weeks of payroll register hours by technician from your payroll provider, and job-costed labor hours by technician for the same weeks from your field system (ServiceTitan, Jobber, Housecall Pro, Procore Timesheets) or from tickets.

  1. For each technician and day, put paid hours beside the sum of hours on that day's jobs.
  2. Label each difference: shop time before the first call, drive between calls, supply runs, callbacks, a missing job, a forgotten clock-out, or an edit made in only one system.
  3. Count the hours in each label and the number of separate corrections the office made.
  4. Separately, divide hours invoiced by hours logged on jobs for the same weeks.

Reading it: The first ratio shows how much paid time has no job, and the labels tell you which rule or setting creates it. The second ratio is your billing capture, the number Level's benchmark compares. No association or agency publishes a rate of timesheet to payroll mismatch, so your two weeks are the baseline.

What does not fix it

GPS timekeeping
It shows where the truck was. In ServiceTitan's GPS integration a manager can still dismiss a flagged discrepancy, which removes the warning, and an edit that leaves a gap turns it into idle time. Location does not decide which job or which classification an hour belongs to.
Fixing hours in the payroll provider
It makes this week's checks right and leaves the field system wrong. Where the field system pushes hours on a schedule, as Jobber does to Gusto, the next sync puts the old number back.
Paying book hours to make the two agree
Paying the flat-rate book time does not change what federal rules count as hours worked. Travel between job sites and required shop time are still hours, and the records still have to show them.

What to try this week

  1. Write the paid-time rule for the first and last hourDecide in writing what happens before the first piece of work and after the last one: loading a vehicle, picking up tools or supplies, the morning meeting, closing down a station. Federal rules make that time paid in common cases, so give each one its own paid code instead of leaving it off the work record.
  2. Give time that belongs to no customer a homeCreate named codes for supply runs, rework, warranty callbacks, training and internal work. Time that has no code ends up on whatever job or client the person was near, or on nothing.
  3. Pick the system where hours get correctedChoose one place to fix hours, normally the system where the work is logged, and stop editing in the payroll provider. Jobber's Gusto sync and ServiceTitan's payroll export both assume the field system is the record.
  4. Refresh payroll data after every past-period editIf your system costs labor from a payroll snapshot, as ServiceTitan's legacy job costing does, add a standing step: after any edit to an earlier timesheet, run the payroll update for that person and period, then recheck the work.
  5. Split hours by classification on covered workOn Davis-Bacon work, record time per classification every day a worker changes tasks. Without that split, every hour is owed at the highest rate that applies.

Where do-it-yourself stops

These steps narrow the gap and settle the arguments about setup and travel time. They leave two records that are filled in by different people at different moments and corrected in different places. The lasting fix is a tool built around the system where your work is logged and your payroll provider, so each hour is captured once with its work and its pay code, and a correction made anywhere lands everywhere. That is what a Workflow Spec designs.

How a Workflow Spec fixes it for good

Questions people ask

Is drive time between service calls paid?

Yes, under federal rules. 29 CFR 785.38 counts travel from job site to job site during the workday as hours worked, and the Labor Department's Hours Worked Advisor gives a plumber driving from customer to customer as its example. The ordinary drive from home to the first job is not (29 CFR 785.35). State law can add more.

Is the time spent loading the truck at the shop paid?

When the tech is required to report there for instructions, other work or to pick up tools, the travel from the shop to the site is hours worked under 785.38. The Labor Department's 2020 letter applied this to foremen who must collect the company truck. A helper who chooses to ride along from the shop is commuting.

Why doesn't job costing show the hours we fixed?

In ServiceTitan's legacy job costing, editing a past timesheet does not re-sync payroll data. Job costing keeps the old numbers until someone updates payroll for that technician and period.

How long do we keep time cards?

Under the FLSA, time cards with daily start and stop times are kept at least 2 years (29 CFR 516.6(a)(1)) and payroll records 3 years from the last entry (516.5(a)). On Davis-Bacon work, payroll records are kept 3 years after all work on the prime contract is complete.

Is rounding to the quarter hour legal?

Federal rules accept rounding to 5 minutes, a tenth or a quarter hour if, over time, employees are still paid for all the time they worked (29 CFR 785.48(b)). Rounding that always favors the company fails that test.

Next step

How we fix this

This guide is how to find it and work around it. If it keeps coming back, it is rarely the only thing costing you. We come on site, find the issues costing you the most, and fix them, starting with the most pressing.

Fox & Santiago, Genesee, Idaho. We work nationwide, for clients across the United States, from our headquarters in Genesee, Idaho.