Hourly cost rates in QuickBooks Online only apply to future time
QuickBooks Online applies employee cost rates only to future time entries, so existing project timesheets can show missing labour costs until they are re-entered.
QuickBooks Online users who track profitability by project keep meeting the same quiet gap. An employee hourly cost rate applies only to time recorded after that rate is saved. Hours already sitting on a project timesheet keep the cost basis they had when they were entered, which is often nothing at all. The project then reports revenue with no matching labour cost.
The symptom is a missing number
The first sign is usually a profitability view that looks too good. Hours appear on the timesheet, the project is assigned, and the time is marked billable. The labour cost column stays at zero, or lands well below what the job consumed.
Nothing in the project itself explains it. The employee exists. The time entry exists. The project exists. What is missing is the link between hours and cost, and that link is created when the time is saved, not when the report runs.
Most teams notice this after a month of tracked hours. By then the timesheet has become the record of what happened on the job, and the cost figure has to be rebuilt around it.
Two ways QuickBooks Online costs labour
Payroll expenses are the actual cost of paying someone. They cover wages plus the employer-side items that ride along with a paycheque, such as payroll taxes and workers compensation. Where payroll runs inside QuickBooks Online, those amounts already exist and can be tied to projects.
Estimated hourly costs take a different route. They multiply hours worked by a fixed rate you set for each employee. That rate can bundle wages with overhead the pay run never touches, such as office electricity or supplies, so the estimate reflects a fuller cost of the work.
Either approach works. Running both against the same project at the same time does not.
Setting a cost rate, in order
The sequence matters more than the clicks. Set rates before anyone tracks time against a project, because the rate is read at the moment a time entry is saved.
Go to All apps, choose Projects, then Projects. Open the Manage settings dropdown and select Set cost rate. On a first project you may need to select Start a project before that option appears. Find the employee and select Add, or use the pencil icon to change an existing rate. Enter the cost rate, save, and repeat for each person. Then close the window.
Intuit flags the ordering as important in its own instructions, and the placement is a fair hint at how easily it is missed.
Re-entering hours so the cost attaches
When rates are set late, the existing hours have to be re-created. The work is simple but tedious.
Note the employee, the date, the project and the hours from the current timesheet. Remove that time entry from the project. Add the same hours back against the same project and employee now that a rate exists. Open the project profitability view and confirm the cost appears.
Do one entry first and check the result before touching a full month. Where the volume is large, work backwards from the most recent week, since that is the period someone is usually asking about. Payroll-based costs are not affected the same way. They come from the pay run rather than the timesheet, so a late rate change does not strip them out.
Which cost basis should a project use?
Estimated rates are fast and apply straight away. They are also an approximation, and they drift as soon as wages change without the rate being updated. Payroll expenses are accurate to the cent, but they depend on the pay run being recorded and mapped to the right accounts.
Pick one basis per project and stay with it. A job costed with estimates in one month and payroll in the next produces a trend line that cannot be compared to itself.
Checks before you trust the figure
Four things break labour cost reporting more often than anything else. The report date range does not match the period the hours were worked. A time entry was never assigned to the project. The billable setting was never applied to the entry. A cost rate was added after the hours were saved.
Each of those leaves the same fingerprint: hours present, cost absent. Working through them in that order saves a lot of rebuilding before anyone starts over on a timesheet.
The gap is not a defect in reporting. It is a sequencing rule, and an easy one to trip over. Set the rate first, track time second, review profitability third. When that order is reversed, the remedy is a re-entry rather than a recalculation.