QuickBooks service items by paycheck: Reconcile Labor Job Cost Before You Trust It
Tracking service items by paycheck in QuickBooks Workforce gives contractors labor cost by job without manual journal entries, but the number is only as good as the tie-out behind it. Before anyone reads a job cost report, reconcile each payroll run to the labor posted across service items and projects, then accrue what the pay date missed.
What changed in the labor cost chain
Labor is the cost a contractor can still manage weekly when material prices move. Until now, QuickBooks Online Payroll allocated payroll expense to classes and projects during the Run Payroll step: percentages for salaried staff, hours for hourly staff, and dollar amounts for commission and other pay types. The allocation landed on reports only after paychecks were processed, and the service item on a timesheet did not necessarily follow the dollars onto the paycheck.
The October update narrows that gap. Intuit says that in QuickBooks Workforce Premium and Elite, and in QuickBooks Online, firms can now track service items by paycheck. Service items entered on timesheets flow into payroll, a single paycheck can be split across several service items, and the item can be edited or reassigned while running payroll or correcting a paycheck. The service item detail then carries through to job costing reports.
In accounting terms, the paycheck is the point where a labor cost is recognized: debit direct labor on the job, credit payroll liabilities and cash. If the service item is attached at that point, the debit lands on the right job, cost code, and dimension the first time. If it is attached later by journal entry, the job cost report and the payroll journal start to drift apart, and nobody notices until a WIP review.
That is why the useful question is not whether the feature exists. It is whether your file now produces a labor number that ties, every pay run, to what payroll actually posted. The rest of this article is that tie-out.
Why this matters now
Intuit published the QuickBooks Online October 2026 product update on 2026-10-06. It lists service item tracking by paycheck alongside spreadsheet payroll drafting and migration tools for firms moving clients from ADP or Gusto to QuickBooks Workforce. Contractors who adopt the feature in the fourth quarter will have two or three pay cycles of history before year-end WIP, bonding renewals, and tax planning all ask for labor by job.
Cost pressure makes the timing sharper. The Associated General Contractors of America reported on 2026-09-10 that construction input costs rose 8.9 percent between August 2025 and August 2026, and that 63 percent of surveyed firms had a project postponed, scaled back, or canceled in the prior six months. When material costs are set by tariffs and markets, the labor line is the one a project manager can still correct mid-job. That only works if the weekly labor number is complete and trusted.
Most published guidance on QuickBooks job costing explains setup: create projects, pick a time tracking app, assign hours to jobs. Far less explains how to prove, after the fact, that the labor on the job cost report equals the labor on the payroll journal. That proof is the control a controller, a surety, or a CPA will ask for, and it is what this article adds.
Build the payroll-to-job-cost tie-out
Run the tie-out once per pay run, not once per month. A pay run is the natural unit because the payroll journal, the paychecks, and the service item splits all share the same pay date. Monthly tie-outs hide which run went wrong.
Start with the payroll side. From the payroll summary for the pay date, capture gross wages, employer payroll taxes, and any employer-paid benefits or workers' compensation that QuickBooks posts with the run. These are flow amounts for the period, debits to expense accounts. Then pull the job cost or project profitability report for the same pay date, filtered to labor accounts, grouped by project and service item.
The difference between the two totals is your unallocated labor. Some of it is legitimate: shop time, training, paid time off, and office staff do not belong on a job. Some of it is a problem: hours that reached payroll without a service item, a split that was never completed, or a reassignment made during a paycheck correction that nobody re-reported. The table below is the working layout.
| Line | Payroll source | Job cost report | Difference means |
|---|---|---|---|
| Gross wages | Payroll summary, pay date | Labor by project and service item | Hours without a service item or project |
| Employer payroll taxes | Payroll summary, employer taxes | Burden by project, if allocated | Taxes posted to overhead instead of jobs |
| Workers' comp and benefits | Payroll summary or insurance accrual | Burden by project, if allocated | Burden policy not applied or rate stale |
| PTO, holiday, training | Payroll summary, non-productive pay | Should be zero on jobs | Non-productive time charged to a job |
| Total | Total payroll expense | Allocated plus expected overhead | Anything unexplained is a finding |
A small example makes the layout concrete. Suppose a pay run posts 48,000 of gross wages and 4,100 of employer taxes. The job cost report shows 41,500 of wages across six projects. The 6,500 gap splits into 4,200 of shop and PTO hours that belong in overhead and 2,300 of field hours that reached payroll with no service item. The 2,300 is the finding, the 4,200 is expected, and the 4,100 of taxes is a burden policy question rather than a reconciling item.
Fix findings at the source where you can. The October update allows a service item to be edited or reassigned while correcting a paycheck, so a misallocated split can be corrected inside payroll rather than by a journal entry that the job cost report may not pick up. Reserve manual journal entries for burden allocation and cutoff accruals, and label them so a reviewer can distinguish them from payroll postings.
Handle cutoff deliberately. Payroll recognizes labor on the pay date, but the work happened during the pay period, which usually straddles month-end. For jobs where labor drives the cost-to-cost percent complete, book an accrual at month-end for earned but unpaid hours by project (debit direct labor on the job, credit accrued wages), and reverse it on the first day of the next month. The accrued wages balance is a point-in-time liability; the labor expense is a flow for the period. Keep both in view when you read the WIP schedule built from QuickBooks, because an unaccrued week of labor understates percent complete and shifts revenue into the wrong month.
Decide on burden before the first tie-out. QuickBooks posts the employer costs it processes, but a loaded labor rate for job costing also needs workers' compensation, which often arrives as a premium and an audit true-up rather than a payroll line. The common approach is a burden rate per hour or per wage dollar, applied to each job as an allocation entry, with a quarterly comparison of applied burden to actual employer costs. Over- or under-applied burden is a known amount, not a mystery variance. If your entity is also changing tax accounting methods under the recent guidance, the construction tax transition register explains how to keep those elections separate from job cost policy.
Accounting controls for labor job cost
Source data: approved timesheets with a customer or project and a service item on every productive hour, the payroll summary and payroll journal for each pay date, the pay period start and end dates, the current burden rate with its derivation, and the service-item-to-cost-code map. Record who approved timesheets and when, and keep the Intuit documentation for the plan features you rely on, such as the help article on tracking payroll expenses by classes and projects.
Calculation: a versioned tie-out worksheet that pulls payroll totals and job cost labor totals for the same pay date, computes unallocated labor, classifies it as expected overhead or as a finding, and derives the burden allocation and the month-end accrual from stated inputs. Formula cells only. Nobody types a reconciling number into the difference column.
Review: someone other than the person who ran payroll confirms that the pay date, pay period, and project list match the source data, samples a handful of paychecks split across service items and traces each split to the timesheet, checks that paycheck corrections made during the period were re-reported, and tests that unallocated labor stays below the threshold the firm set. The reviewer also confirms that burden was applied with the current rate and that the cutoff accrual was reversed.
Decision: the controller or owner decides the burden policy, the acceptable unallocated-labor threshold, whether salaried project staff are allocated by hours or by percentage, and whether to accrue labor at month-end on every job or only on jobs above a materiality floor. Document the decision, the date, and the next review date. A decision that lives only in someone's head is not a control.
Limits and common mistakes
The first mistake is double counting. If a time tracking app already posts a loaded hourly cost to the project and payroll now posts wages to the same project, the job carries labor twice. Choose one path for cost and use the other only for hours.
The second is treating the pay date as the work date. A pay run on the third of the month contains labor from the prior month. Without the cutoff accrual, the first week of every job looks cheap and the last week looks expensive, and the WIP schedule inherits the error.
The third is assuming the service item is a cost code. Service items were designed for billing. A contractor who maps service items to cost codes deliberately, one to one where possible, will get usable job cost detail. One who reuses billing items as labor categories will get a report that reconciles to payroll but means nothing to a project manager.
The fourth is allocating salaried staff by a percentage set once and never revisited. Percentages drift as projects start and finish. Review them each month against actual hours or a project schedule.
Finally, verify feature availability in your own file before you build a process on it. Intuit's update names QuickBooks Workforce Premium and Elite and QuickBooks Online, and the payroll allocation help article names Payroll Premium and Elite, but plan details and rollout timing can differ by account. Build the tie-out so it works whether labor arrives by service item, by project, or by class. Spreadsheet layouts for job cost analysis and project budgets are in the FinBoard templates library.
Frequently Asked Questions
What does tracking service items by paycheck change for job costing?
It attaches the service item to labor at the paycheck, so wages post to the job, service item, and dimension when payroll runs rather than through a later journal entry. Intuit says timesheet service items flow into payroll, one paycheck can be split across items, and the detail carries to job costing reports.
How often should a contractor reconcile payroll to the job cost report?
Once per pay run. The payroll journal, paychecks, and service item splits share a pay date, so a per-run tie-out shows which run produced unallocated or misallocated labor. A monthly tie-out blends runs together and hides the cause.
Does QuickBooks allocate labor burden to jobs automatically?
QuickBooks posts the employer payroll costs it processes with each run. Items such as workers' compensation premiums and audit true-ups usually arrive outside payroll, so most contractors apply a burden rate per hour or per wage dollar by allocation entry and compare applied burden to actual costs each quarter.
Why does month-end cutoff matter for labor job cost?
Payroll recognizes labor on the pay date, but the work happened during the pay period, which usually crosses month-end. An accrual for earned but unpaid hours by project, reversed the next month, keeps the labor flow in the right period and keeps cost-to-cost percent complete and the WIP schedule accurate.
FinBoard connects payroll, job cost, and WIP reporting to the source records that support them, so the tie-out is a report rather than a spreadsheet chore. See how FinBoard supports construction finance teams.
