Job Costing Add-On for QuickBooks Online: 4 Types

Most articles about job costing add-ons for QuickBooks Online compare features. That is the wrong comparison. The decision that actually matters is where your job cost numbers live after you install the thing, and the answer is set by a piece of QuickBooks history that no vendor page mentions.

The short answer

A job costing add-on for QuickBooks Online is any tool that supplies the job cost detail QuickBooks Projects does not: cost codes, committed costs, burdened labour, WIP, retainage, or estimate versus actual by phase. They divide into four types by what they write back into QuickBooks, and that single property determines whether you end up with one set of job numbers or two.

QuickBooks Online does have native job costing through Projects, on the Plus plan or higher. For a one-truck operation running two jobs, it is genuinely enough. The trouble starts at the point where you need to know not just what a job cost, but where the money went inside it.

Why nearly every add-on keeps its own job ledger

Here is the fact that reframes the whole category, and you will not find it on a single page currently ranking for this search.

For most of the life of QuickBooks Online Projects, third-party applications could not read or write Projects at all. On Intuit's own developer help forum, in a thread titled "Once Again: Requesting Access to QBO Projects via API," the answer was blunt: "If you are looking for API for projects, then unfortunately, we do not support project APIs yet. It is on the roadmap. But there is no definite ETA for it."

A developer building field service integrations described the practical effect on r/QuickBooks in May 2025: "our automations could only sync job-costing at the customer level and that project details were locked away because the QBO API wouldn't expose them. Explaining that limitation was always painful."

So every integration built before mid-2025 had to fake it. Apps mapped your jobs onto customers, sub-customers or classes, kept the real job structure inside their own database, and pushed summary invoices and bills into QuickBooks. That was not laziness. It was the only thing the platform allowed.

Intuit finally announced a Projects API on 15 May 2025 as part of the Intuit App Partner Program, which went live on 28 July 2025. But read the availability terms carefully, because they are still restrictive:

• The Projects API shipped as a Premium API, available only to Silver, Gold and Platinum tier partners. The Builder tier, which is where small vendors sit, is excluded.
• Silver costs the vendor $300 per month. Gold is $1,700 and additionally requires 500 active QuickBooks connections. Platinum is $4,500 and requires 3,000.
• It is GraphQL-first. In September 2025 the founder of the integration platform Apideck reported testing Projects "via GraphQL (since it's not yet exposed through REST)" and hitting persistent DataFetchingException errors on the list query even with correct syntax.

The incentive that makes your numbers drift

The App Partner Program did something else that quietly shapes how every QuickBooks integration behaves. Intuit split API calls into two classes:

• Core calls cover data going in: creating and updating invoices, bills, customers, vendors. These are free and unlimited on every tier.
• CorePlus calls cover data coming out: reading accounts, querying records, fetching reports. These are metered and charged.

On the free Builder tier a vendor gets 500,000 CorePlus reads per month, and calls beyond that are blocked outright rather than throttled or queued. Silver buys 1 million reads for $300 per month, with overages at $3.50 per thousand calls. Variable fees were discounted 100% through 31 October 2025 and began applying in full on 1 November 2025.

Sit with what that means. Pushing data into your books is free. Reading your books back to check that the push was right costs the vendor money, every month, forever. Webhooks do not rescue them either, because a QuickBooks webhook carries only the entity ID and the operation type, not the changed data, so the vendor still has to make a metered read to find out what actually happened.

The direction that keeps your two systems honest is the expensive direction. That is the structural reason job costing add-ons drift out of agreement with QuickBooks, and why reconciliation quietly becomes somebody's monthly job.

The four types of job costing add-on

Type 1, field data capture. Tools like QuickBooks Time and SmartBarrel exist because labour is the only major job cost that depends on a human reporting it. Materials arrive with an invoice, equipment with a rental receipt, subs with a bill. Hours arrive from memory. SmartBarrel's write-up of the problem is honest about the mechanics: time gets rounded, check-outs get reconstructed after the fact, cost codes get assigned days later in a batch review. Nothing dishonest is happening, and no QuickBooks setting corrects a number that was already wrong on arrival.

The stakes are set by how thin the margins are. Research cited by the CFMA puts average construction net profit margins in the 3 to 7 percent range. At that margin, hours drifting on one job moves it from profitable to loss while the report still looks fine.

Type 2, the parallel job ledger. Knowify, JobTread, Buildertrend, Houzz Pro and Contractor Foreman sit on top of QuickBooks and own the job. They hold the cost code structure, the budget, the change orders and the committed costs, then push accounting-grade summaries down into QuickBooks, which stays the general ledger for tax, payroll and bank reconciliation. Level Accounting, a construction-only firm, describes the split cleanly: QuickBooks knows what you have spent, the job ledger knows what you have spent, what you have committed, what is still scheduled and what changed yesterday.

This is the type most contractors actually need, and it is also the type that guarantees two sets of numbers. Accept that trade deliberately rather than discovering it in month three.

Type 3, the reporting layer. LiveFlow pushes QuickBooks data into Sheets or Excel for live job and WIP views. On r/QuickBooks, a vendor for FinJinni described a similar approach, pulling QuickBooks data into a SQL database for custom WIP and job costing reports on a one-time price rather than a subscription. These change nothing about your data quality. If your hours are wrong or your transactions are uncoded, a reporting layer renders that faithfully.

Type 4, the replacement. Intuit Enterprise Suite, Acumatica and the construction ERPs are not add-ons. They are exits. Worth naming only because the QuickBooks gravity well is real, and the reason is not the software. As one r/QuickBooks commenter put it: "You could make a killer app and I won't buy it because my accountant uses QB." Another was shorter: "Biggest problem I see is that most accountants will only use QB!"

The labour burden trap

This one deserves its own section because it is counterintuitive and it silently overstates your margin on every job.

QuickBooks Online can assign a fully burdened cost rate to each employee, including wages, employer taxes, workers' comp and overhead, and apply it to projects through timesheets. The team at QBKAccounting, who train accountants on exactly this, attach a condition to that capability in capital letters: the feature only works if you do not run payroll within QuickBooks.

Run QuickBooks Online Payroll instead, and projects receive gross wages and payroll taxes only, provided the timesheet exists before you run payroll. Workers' comp, health insurance and overhead cannot be added to the project at all. Apps4Rent's comparison reaches the same conclusion independently: QuickBooks Online can include gross payroll and payroll tax data, and cannot include other costs such as workers' compensation.

If workers' comp, benefits and overhead add 25% on top of wages and taxes, and labour is 35% of a job, your reported job margin is overstated by roughly nine points of job cost. On a trade running a 7% net margin, that is the difference between a job you would bid again and one you would not. Fixing it is the clearest single reason to buy either a field capture tool that carries a burdened rate or a parallel job ledger that computes burden itself.

Committed costs, the gap that actually costs money

QuickBooks Online has no concept of a cost you have committed but not yet incurred. Cut a $8,000 purchase order to a sub who has not billed you, and QuickBooks shows a job that is $8,000 healthier than it is. The bill lands three weeks later and the margin moves.

This limitation is confirmed by three independent sources: Fourlane, QBKAccounting and Level Accounting all list committed cost reporting as something QuickBooks Online cannot do, with QuickBooks Desktop Enterprise being the only Intuit product that offers it.

The full list of what QuickBooks Online Projects cannot produce, per QBKAccounting and Fourlane:

• An estimate carrying estimated item cost, so you cannot calculate projected margin
• Estimates versus actuals, or job progress percent reports
• A WIP report or a committed costs report
• Project start dates, estimated completion dates or actual completion dates
• Organising or tracking projects by job type
• Proactive alerts when a job approaches or exceeds budget
• Assigning costs to a specific invoice or estimate rather than to the project as a whole

Every item on that list is available in some version of QuickBooks Desktop. The move to QuickBooks Online cost contractors job costing depth, and the add-on market exists to sell it back.

When you actually need one

The honest threshold, from Level Accounting's work setting this up for hundreds of contractors, is around $1.5M in revenue and five or more simultaneous active jobs. Their diagnostic is worth stealing. You have outgrown QuickBooks Projects alone when three or more of these are true:

1. You run five or more active jobs at once and transactions stop getting tagged correctly
2. Your field crew is larger than three people
3. Jobs run longer than 30 days, so you need WIP, percent complete and over/under billing
4. The same sub works across multiple jobs and you cannot see total committed spend with them
5. Your estimating bottleneck is hurting your hit rate
6. You cannot name which of your last five jobs was least profitable, with real numbers

Point six is the real test. If you cannot answer it, you have already outgrown QuickBooks alone, because that answer requires cost codes and QuickBooks Online does not have them.

Below that line, stay. Under $1M, one to four jobs at a time, you plus a helper or two, jobs closing inside 30 days: QuickBooks Online Plus with Projects is plenty, and our walkthrough of QuickBooks job costing setup covers getting the most out of it before you spend anything.

What it really costs

The subscription is the small number. Level Accounting publishes the full arithmetic for a JobTread implementation, and the shape holds across this category:

Two costs never appear on a vendor page. The first is the parallel run: two to three weeks of entering everything twice while you confirm the new system agrees with the old one. Skip it and you will not find out the mapping was wrong until quarter end. The second is per-seat pressure inside QuickBooks itself. As one operator put it on r/QuickBooks, "Paying a full seat for someone who only enters time is dumb." Check whether the add-on's field users need QuickBooks seats or only add-on seats, because that difference compounds monthly.

Seven questions to ask before you buy

1. Do you have Projects API access, and will my costs land in the QuickBooks Projects tab? If no, ask where job cost truth lives instead.
2. Does the integration write, read, or both? A write-only integration will drift, and you need to know who reconciles it.
3. How is labour burden calculated? Ask specifically about workers' comp, benefits and overhead, not just wages and taxes.
4. Do you track committed costs? If not, you are buying a nicer report on the same blind spot.
5. What happens when a customer is renamed in QuickBooks? Name-matched integrations break here and duplicate records.
6. Which of my people need QuickBooks seats versus add-on seats?
7. Can my accountant read the outputs? Estimate versus actual, cost code variance and WIP are not standard accounting reports, and a generalist CPA usually does not read them.

For a fuller treatment of the sync mechanics behind questions two and five, our guide to what two-way QuickBooks sync actually means has the eight tests that separate a real integration from a demo.

A 30-day evaluation

Week 1. Diagnose the failure before you shop. Pick your three most recent completed jobs and try to explain the margin on each by cost category. If you cannot, note whether the blocker is missing hours (buy type 1), missing structure (type 2), or data that exists but will not report (type 3).

Week 2. Check your burden. Open one project's labour cost in QuickBooks and compare it to that crew's true burdened cost for the same period. If the gap is workers' comp and benefits, you have confirmed the trap above, and burden handling becomes your primary buying criterion.

Week 3. Trial one tool of one type. Run a single live job through it in parallel with QuickBooks. Do not migrate anything. At the end of the week, compare the job cost in both systems and ask the vendor to explain any difference.

Week 4. Price the whole thing. Subscription plus setup hours plus seats plus the parallel run. Compare that against the margin you are currently unable to see, which for most contractors past $1.5M is the larger number.

The contractors who get burned are not the ones who bought the wrong software. They are the ones who kept stretching QuickBooks past its limits because switching felt expensive, then paid more in cleanup later. Decide deliberately, and know which of your two systems is telling the truth.