Problem guide
Cost reports arrive after the work is over
Costs arrive late because time, vendor bills and payroll each have to be matched, imported, approved or posted somewhere else before the cost report can see them. In QuickBooks Online, for example, payroll costs reach a project only after payroll is run. By the time every cost has landed, the job, order or engagement is done. Shorten each hop, and review cost weekly while the work can still be steered.

How it actually happens
Every cost travels from the place it happens to the report that shows it, and every stop on the way is a day or a week. Picture a commercial electrical contractor running a six-week tenant improvement, as an example. The project manager works in Procore. The controller works in Sage 300 CRE. The foreman enters crew time each day.
Labor takes the longest road. The foreman's hours sit in Procore Timesheets until they are approved. Then someone exports them as a text file and imports it into Sage Payroll. If an employee's class or a cost code does not match exactly, that line drops into an error file and waits for someone to fix it. Payroll runs every two weeks. Only after payroll posts in Sage does the labor cost exist in the books, and only after the next sync does it show up in Procore's ERP Direct Costs column, by default as a summary.
Material takes a different road. The purchase order goes out from one system. The supplier's invoice arrives by email a few weeks later. Accounts payable enters it and posts the batch. That is when the cost lands on the job. Subcontract cost waits on the sub's pay application, which waits on its own billing cycle.
None of these hops is slow by itself. Procore says that for most automatic syncs, the software hops take minutes. The days are lost in the human steps around it: approving time, fixing a mismatched code, running payroll, entering a bill, posting a batch. Add them up and the project manager is looking at week two's cost in week five, on a six-week job.
Service companies see the same thing at a smaller scale. The ticket closes and the invoice goes out the same day, so revenue is current. Cost is not. In ServiceTitan, whether material counts when a purchase order is created, received or billed is a setting, and an unposted batch keeps it off the job. In the legacy job costing model, fixing a timesheet does not fix job cost until payroll is updated for that period. In smaller apps, labor cost depends on time tracking and on a rate that does not reach backward when it changes.
Other businesses run the same roads. A firm knows an engagement's hours the day they are entered, but not its cost or realization until payroll, overhead and collections settle. A restaurant knows its sales every night and its food cost after the month-end count. In each case revenue is current and cost is a month behind.
In construction, FMI's 2023 study found that six in ten contractors believe 11% or more of field labor cost is wasted. Cost that arrives after the job cannot help recover any of it.
Estimated now beats exact later
The fix is not to make the final number arrive faster. It is to give the manager a labeled estimate the same week, from time already entered and from rates the office already knows, and then to replace it with actuals as they post. A trend seen in week two can still change week three.
Signs you have this problem
- The manager learns a job, order or engagement lost money at the closeout meeting
- Labor on the cost report trails the work by a payroll cycle or more
- Material shows on the job only when the vendor bill is entered, weeks after it was used
- Hours fixed on a timesheet still show the old numbers in the cost report
- The project tool and the accounting system show different costs for the same work
What usually causes it
- Time, purchase orders and vendor bills are entered in one system and have to be matched and moved to another before cost showsThe re-entry trap
- The people doing the work know what was used today, but the cost lands only when the office posts the bill or runs payrollThe field-to-office split
- Exports wait for an accounting approver or a batch to be posted before anything movesApproval drag
Find your cause
Ask these in order. The first yes is usually where yours starts.
- Does labor reach the job only after payroll is processed?If yes: the lag is at least a pay cycle. Show an estimated labor cost from timesheets in the meantime.
- Do timesheet imports into accounting throw errors or land on the wrong cost code?If yes: the codes do not match between systems. Fix the setup before fixing the reports.
- Does material cost appear only when the vendor bill is entered?If yes: the bill is the trigger. Post bills weekly, or cost on receipt if your system allows it.
- Does the manager see a different cost than accounting for the same work?If yes: one of them is reading a summary that has not synced. Find which hop is behind before arguing about the number.
- Is cost reviewed only at month end?If yes: short jobs finish between reviews. Move open work to a weekly review.
How it breaks in each industry
- Commercial electrical and mechanical
- The project manager works in a project tool such as Procore while the books live in an ERP such as Sage 300 CRE. Field time goes to payroll by file export, vendor bills post in accounting, and the job cost the project manager sees comes back from accounting at summary level. By the time that number moves, the area is installed.
- HVAC and plumbing service
- Revenue is on the invoice the day the job closes, but cost waits on vendor bills and payroll. In ServiceTitan the setting chosen for costing decides whether material shows when a purchase order is created, received or billed, and a batch that has not been posted keeps it off the job entirely.
- Accounting, law and other professional services firms
- Hours are recorded against the engagement, but cost per hour comes from payroll and overhead allocations that land at month end. The partner sees realization after the work is billed and collected, which is after the next year's fee has been quoted.
- Restaurants and hospitality
- Food cost is known only after the month-end inventory count and the last vendor invoices are entered, and labor cost after payroll posts. A menu item that started losing money when a supplier raised prices in week one shows up in the numbers in week six.
Where it breaks between systems
- Procore and Sage 300 CRE (job costs)
- Job costs flow from Sage 300 CRE into Procore, not the other way. By default they sync at summary level into a custom ERP Direct Costs column in the budget view. Procore does not sync production quantities, and new cost codes must be created in the ERP, not in Procore.[1]
- Procore and Sage 300 CRE (sync timing)
- For most automatic syncs, data moves from the Sage 300 CRE server to the hh2 cloud service about every five minutes, and Procore polls hh2 every 30 minutes. A cost appears in Procore only after Sage has recorded it and both steps have run.[2]
- Procore Timesheets to Sage 300 CRE Payroll
- Field time goes to Sage Payroll as a downloaded text file that is imported, not through a live sync. Six pairs of fields must match exactly: employee and employee ID, classification, pay ID and time type, job and project, sub job, and cost code. Records that cannot be converted go to an error file, and the cost type follows from the pay ID.[3]
- Procore ERP Integrations (on-demand sync)
- An on-demand sync is a separate button on each of six tabs: standard cost codes and cost types, vendors, jobs, sub jobs, prime contracts and job costs. Budgets, commitments and change orders cannot be synced on demand and go to the ERP Integrations tool, where by default an accounting approver accepts or rejects them.[5]
- Procore Direct Costs and Sage 300 CRE
- If the Direct Costs tool is turned on for an integrated project, direct costs created in Procore cannot sync back to Sage 300 CRE. Costs entered in the field tool stay in the field tool.[7]
- ServiceTitan (costing settings and posted bills)
- Actual cost on a job is calculated from purchase orders, receipts or vendor bills, depending on a setting, with receipts as the default. ServiceTitan's troubleshooting for projects that show no expenses is to enter the bills in the batch and post the batch.[8]
- ServiceTitan (edited timesheets, legacy job costing)
- In the legacy job costing model, editing a past timesheet does not re-sync payroll data, so job costing keeps the pre-edit hours until someone updates payroll for that technician and period.[10]
- QuickBooks Online Projects
- Intuit's help describes two ways to see labor on a project: estimated hourly costs that appear immediately, and payroll expenses that post only after payroll is run. Hourly costs come only from timesheets assigned to the project.[11]
- Housecall Pro job costing
- Labor cost is each employee's loaded rate times time on the job, travel included, so a tech who does not track time leaves labor out. Housecall Pro's help says a later rate change does not update labor already recorded, and material unit costs are entered by hand.[12]
- Jobber and QuickBooks
- Jobber's help says labor cost comes from timesheets times each employee's hourly cost, and a changed cost applies only to future hours. Item costs first sync in from QuickBooks, after which Jobber treats its own costs as the source of truth.[13]
By the numbers
| Figure | What it measures |
|---|---|
| 60%[14] | Contractors in FMI's 2023 Labor Productivity Study who said 11% or more of their field labor cost is wasted. 259 contractors responded, 42% of them mechanical, electrical and plumbing. |
| 78%[14] | Share of contractors with extremely reliable cost-to-complete information who get productivity feedback weekly or daily, in the same FMI study. It shows the two go together, not that one causes the other. |
| 5 and 30 minutes[2] | Procore's stated intervals for most automatic syncs with Sage 300 CRE: Sage to hh2 about every five minutes, then Procore checking hh2 every 30 (vendor documentation). The software hop is fast. The days are lost before it, in entry, approval and posting. |
| Roughly 30 days[15] | How far reporting ran behind the work at Paragon Sports Constructors, a Fort Worth specialty contractor, while it assembled job cost reports by hand, per a CMiC customer story. One vendor's named customer, not an industry figure. |
Rules that apply
- 29 CFR 5.5(a)(3)(ii)(A), weekly certified payroll[16]
- On Davis-Bacon and Related Acts covered work, the contractor submits certified payroll weekly for every week covered work is performed. There is no rule on how fast job cost must post, but on these jobs labor by job is already reported every week, so a weekly labor cost view uses data you must produce anyway.
Measure it in your own shop
From: Twenty recently finished jobs, orders or engagements from the last 60 days, with the dates work was done, the dates timesheets were approved and payroll posted, and the dates vendor bills were entered and posted.
- For each one, note the date the last work happened.
- Find the date the last labor cost and the last material cost appeared on the cost report.
- Subtract the first date from the second for each, and find the median and the slowest.
- For Procore with Sage 300 CRE, compare the timesheet export date, the Sage payroll import date and the date the cost appears in Procore's ERP Direct Costs column.
Reading it: This is our own method, not a published benchmark. The median is how long after the work your cost picture is complete. If it is longer than your typical job, every cost report you read is about finished work.
What does not fix it
- A new ERP or operating system
- The new system still needs codes that match, time that gets entered, bills that get posted and an approval step. CMiC's own customer story describes the lag before the change, not a guarantee after it.
- Telling people to enter time daily
- Daily time helps only if it reaches the job. If payroll posts every two weeks and the report uses payroll cost, daily entry still shows up late.
- Turning on every sync option
- Some options conflict. Procore warns that if the Direct Costs tool is enabled on an integrated project, costs created in Procore cannot sync back to Sage, so a setting chosen for speed can split the record.
What to try this week
- Write down every hopFor labor, material and subcontract or outside cost, list each place the number passes through from the work to the cost report, who moves it and how often. Most businesses find four or five hops and at least one that happens monthly.
- Make the codes match before the first entryTime that does not match the accounting system on employee, class, pay type, job and cost code fails the import or lands in the wrong place. Set up the job and its codes once, in the system your connector expects, before the work starts.
- Show estimated cost now, actual cost laterUse an estimated labor rate for a same-week view, and label it estimated. Replace it with payroll actuals when payroll posts, so the manager is never waiting on a pay cycle to see a trend.
- Post vendor bills on a fixed rhythmIf cost lands only when a bill is entered and a batch is posted, post the batch at least weekly. Under a received-goods setting, material cost can show when the purchase order is received, so receive it in the system when it arrives.
- Review cost to complete weeklyPut open work on a weekly review: budget, cost to date, estimated cost to complete. A monthly look at a three-week job is a postmortem.
Where do-it-yourself stops
These steps narrow the lag, but costs still pass through several systems before anyone sees them, and someone keeps reconciling the hops by hand. The lasting fix is a cost view built on your operating and accounting systems, so each cost shows on the work the day it is known. That is what a Workflow Spec designs.
Questions people ask
Why does Procore show different job costs than Sage 300 CRE?
Procore receives job costs from Sage 300 CRE, by default at summary level, through the hh2 service. Until Sage has posted the cost and the sync has run, Procore's ERP Direct Costs column is behind. Costs entered directly in Procore with the Direct Costs tool do not go back to Sage.
Why don't payroll costs show on my QuickBooks Online project?
Intuit's help says payroll expenses post to a project only after payroll is run, and only from timesheets assigned to that project. Estimated hourly costs show right away but are a rate you set, not actual payroll cost.
Why is job costing still wrong after I fixed a timesheet in ServiceTitan?
Under the legacy job costing model, a changed timesheet leaves payroll data as it was. The job cost report holds onto the original hours until payroll is updated for that tech and pay period.
Does changing an employee's labor rate fix old job costs?
Not in Housecall Pro or Jobber, according to their help pages. A new rate applies to time going forward, and labor already recorded keeps the old rate.
How often should we look at cost?
Weekly for open work is a practical floor. In construction, FMI found that contractors with very reliable cost-to-complete numbers mostly get productivity feedback weekly or daily.
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.
