QuickBooks Online project labour costs arrive late unless rates are set first

QuickBooks Online projects promise a tidy profit figure for every job, and for most costs the software delivers exactly that. Labour is where the promise bends. Payroll costs do not reach a project until a payroll run has finished, and estimated hourly rates ignore every hour logged before the rate was saved. Both quirks push reported profit upward, sometimes for weeks at a time.

A recent QuickBooks Online question about tracking labour costs by project runs straight into both rules. We have pulled apart how the feature behaves, and the setup order that keeps the numbers honest.

Two ways to cost labour on a project

Intuit gives projects two routes to a labour figure, and both work with QuickBooks Online Payroll or a third-party payroll service. The route you choose decides how fast the numbers appear and how accurate they are.

The first route is actual payroll expense. This captures what payroll genuinely costs: wages, employer taxes, workers’ compensation and similar direct costs. The catch is timing. With QuickBooks Online Payroll, expenses reach the project only after the run finishes, so a fortnight of work shows nothing until payday closes it out.

Estimated hourly costs work differently. Hours worked are multiplied by a fixed rate for each employee, so a figure appears the moment time is recorded. That makes estimates handy between payroll runs, or for businesses that run no payroll product at all. The trade-off is accuracy, because a flat rate is only as good as the number you chose and goes stale when wages move.

The estimate can also carry more than wages. Employer taxes and overhead that never passes through payroll, such as office electricity or site supplies, can be folded into the per-hour figure. Done carefully, the estimate starts to resemble a fully burdened labour cost rather than a bare wage.

A setup sequence that avoids the surprises

Order of operations matters more than most people expect. Work through these steps before anyone records a minute of project time.

1. Open Projects from the left navigation. If the entry is missing, edit the navigation menu and add it.
2. Open the chart of accounts from the settings menu and confirm you have expense accounts ready to receive wages, payroll tax and workers’ compensation.
3. Set an hourly cost rate for every employee who will log time, entered against the employee’s pay details. Fold employer taxes and chosen overhead into that rate, not just the base wage.
4. Record time against the project through a single time activity or the weekly timesheet.
5. After payroll has run, or as estimates accumulate, read the labour and profitability figures on the project itself.

Intuit’s warning on step 3 is blunt, and it is the detail people miss. An hourly cost rate applies only to time tracked after the rate is saved. Rates are never applied backwards.

Why does project profit look wrong between payroll runs?

Because the two methods answer different questions at different speeds. Payroll expense is the settled truth, but it arrives in lumps after each run. Between runs, a project’s cost total understates what the work is really costing, and the margin looks healthier than it is. Estimated hourly costs are the opposite: immediate and smoother, but approximate.

The rate timing rule compounds the confusion. A team that switches hourly costs on halfway through a job will see its earlier hours carried at zero cost. The project looks more profitable than it is until someone works out why.

Neither behaviour is a fault. The software is following its own rules. The trouble starts when users assume costs appear the moment work is performed, because in QuickBooks Online projects, labour lands on its own schedule.

Running both methods side by side

Nothing stops you using both at once. A common pattern is to keep hourly rates switched on for a live estimate during the pay period, then let actual payroll expense land on the project once the run finishes. Intuit allows switching between the methods as needed, and both rest on the timesheet hours logged against the project.

Two habits keep the estimates usable. Revise a rate whenever wages change, and give every new starter a rate on day one. An estimate that skips employer taxes will always understate the true cost, so review the burden whenever pay moves.

The bottom line is short. Set cost rates before the first timesheet, expect payroll figures only after each run, and use hourly estimates to fill the gap between the two. Do that, and the profitability report holds up between paydays.