Jobber and QuickBooks Online Sync Problems: Tax Mismatches, Missing Invoices, and the Chart of Accounts Nobody Set Up

Your Jobber invoices and your QuickBooks books disagree, and you need it fixed today. Here is the direct answer.

A broken Jobber to QuickBooks Online sync falls into 1 of 3 failure classes. Tax settings that were never set up to match in both systems. A chart of accounts with nowhere to put field-service money. Migration damage carried in from a previous system. Each class is diagnosable in under an hour. Each one is fixable.

We build integrations for Jobber shops, which means we usually get called after the sync has been fighting the bookkeeper for months. We are independent builders and not affiliated with Jobber or Intuit. One hedge before the checks: sync behavior changes as Jobber and Intuit ship updates. Everything below describes the setups we see. The current word on any specific setting is Jobber’s help center. The help-center articles document one setting at a time, so this post starts one level up: which class you are in.

Here is the shape this takes in real life. A hiring post we read this week, from an HVAC and refrigeration shop under $1M a year that moved onto Jobber from an invoicing app, describes all three classes in one paragraph: invoices that never arrived in QuickBooks or arrived missing line items, sales tax that disagrees between the two systems because it was never fully set up in either one, and no chart of accounts built to receive field-service money. That shop is shopping for all three fixes at once. Most shops have one class. The checks below sort you.

Start here: compare one invoice on both sides

Before touching any setting, pick one recent invoice in Jobber. A taxed one, with at least two line items. Find the same invoice in QuickBooks Online and put them side by side. Compare five things:

1. Does it exist in QuickBooks at all?
2. Line item count. Same number of lines, same descriptions?
3. Subtotal and total. To the penny.
4. Tax amount. And, if you can see it, the rate and agency it was booked under.
5. Where the money landed. Ask your bookkeeper which income account each line hit.

Now route yourself:

• Missing entirely, or clean after some date and broken before it: migration damage. Class three.
• Present, but the tax disagrees: tax setup. Class one.
• Present, totals match, but revenue sits in one generic account: mapping. Class two.
• Present and matching: your sync works today. The problem is historical, which is still class two or three, just bounded.

Failure class 1: tax was never set up to match

The symptoms: small dollar differences that appear only on taxed invoices. Jobber says you collected one tax number for the month and the QuickBooks liability report says another. Filing time arrives and nobody trusts either figure.

The cause is structural. Jobber calculates tax on the invoice. QuickBooks records tax as a liability owed to a named agency. For the two to agree, the rates and agencies have to correspond. In the setups we see, the history is short. Someone created a tax rate in Jobber on day one, typed a percentage, and moved on. Nobody built the matching agency and rate in QuickBooks, or QuickBooks was left computing its own tax and the two calculations drift.

Three checks, about twenty minutes:

1. List every tax rate Jobber has, then every rate and agency QuickBooks has. Match them by hand, name and percentage. An orphan on either side is a leak.
2. Pull last month’s sales tax liability report in QuickBooks and compare it to Jobber’s number for the same month. A gap means taxed invoices are syncing without their tax, or not syncing at all.
3. Check your sync settings for how tax is handled. We are deliberately not naming toggles here, because they change. What you are verifying: the sync sends tax as tax, and QuickBooks knows which agency owns it. Jobber’s help center documents the current behavior.

The fix direction: pick one system as the authority on rates and make the other match it exactly. Then run the one-invoice test again on a fresh invoice and confirm the tax line agrees to the penny.

Failure class 2: a chart of accounts with nowhere to put the data

The symptoms: the books balance, and they are useless. Run last month’s P&L and all your revenue is one row. Or an account with a name like uncategorized income, or a generic services default, is quietly absorbing transactions.

That default account is the tell. A sync needs a destination account for every line item it sends. When nobody maps products and services to income accounts, everything falls into the catch-all, and every invoice that syncs lands in one undivided pile. The books close, the bank reconciles, and the owner still cannot see service revenue apart from install revenue apart from materials.

Three checks:

1. Run last month’s P&L in QuickBooks. If one income row holds nearly everything, mapping was never done.
2. Look for the suspense or uncategorized account. In the setups we see, that account is where unmapped items land. Its transaction list is a to-do list of the skipped mappings.
3. Open the products and services list in QuickBooks. Read what income account each item points to. If they all point at one, that is the whole story.

The fix direction: this is a bookkeeping design job. Build the accounts a field-service shop needs first: the short list is two sections down. Map each item to its account, and the sync has somewhere to put things. Until the accounts exist, no setting will save you.

Failure class 3: migration damage from the system you left

The symptoms cluster around one date: your cutover. Invoices from before it are missing in QuickBooks or arrived thin, with line items gone. Customers exist twice. The month you switched is the month the numbers stopped tying out.

The cause: migrations import records without the full structure a sync needs. An invoice imported from an invoice-first app can arrive without the item and tax detail that Jobber-native invoices carry. In the setups we see, records like that sync incompletely, or fail without an error anyone notices. Shops in this class tend to blame the sync for weeks while the damage actually came in with the import.

Three checks:

1. Pick three invoices from before the cutover and three from after. Run the one-invoice comparison on all six. If the after set is clean, your sync works and the damage is bounded to the import window.
2. Count invoices per month in each system for the past year. The months where the counts disagree are the months to reconcile. This goes faster with the data out of both systems. Our guide to exporting data from Jobber covers every route.
3. Search QuickBooks customers for near-duplicate names. Imports create twins. A payment applied to the wrong twin is why a customer shows a balance they already paid.

The good news about this class: it is bounded. The cause was a one-time event, so once the import window is reconciled, it stays fixed.

What fixing it costs: the three-rung ladder

Three tiers exist, and we sell the top one, so read our placement of it knowing that. Most sync problems never need it.

The middle rung is where most shops land, and it is money well spent when the damage spans months. Hand the bookkeeper this post, the one-invoice test results, and the export CSVs, and the engagement gets shorter.

The chart of accounts a field-service shop actually needs

Prevention is a design question, and the design principles are short. Your accountant picks the names. The structure is what matters:

• Revenue split by service line. Service calls, installs, and maintenance agreements as separate income accounts. This is what makes the P&L answer questions.
• Materials COGS as its own account, separate from labor. Parts margin and labor margin move for different reasons, and one blended number hides both.
• Subcontractor COGS as its own account. The month you sub out overflow work should show in the books. It is the month your margin structure changed.
• Few enough accounts that people use them. A forty-account revenue tree gets ignored by week three. Ignored accounts recreate the catch-all you just cleaned.

With that structure mapped, gross margin by service line becomes a P&L read instead of a spreadsheet project. Margin by individual job is a harder problem, because it needs operational data the sync does not carry. Which brings us to the last question.

When the native sync is the wrong tool

For a shop with simple tax, invoicing whole jobs, the native sync set up correctly is the answer. If that is you, stop at the second rung of the ladder and keep your money. We mean that.

The structural misfit signals are different from broken settings. No amount of remapping fixes them:

• Deposits and progress billing that your accountant needs recorded differently than the sync records them in your setup.
• Multiple divisions or entities that need revenue routed by rules a flat item-to-account mapping cannot express.
• Job costing that needs data the sync does not move. Visits, timesheets, and crew assignments stay behind, so per-job margin cannot be assembled on the QuickBooks side. We wrote up the full job-costing problem separately.
• You have rebuilt the mapping twice and it broke again. That is the sync telling you the business shape and the sync shape disagree.

“We had a bunch of different tools that technically worked, but nothing really talked to each other. Danilo and his team came in, figured out how everything worked, and built the missing pieces.”

Owner, HVAC and plumbing company. Client name shared on a call.

A custom bridge reads from Jobber’s API and writes to your books under your rules. It is real work with real constraints. The API is gated to Jobber’s top plan, and our Jobber pricing guide covers the tiers. The API also meters everything you pull, and we measured the meter in production in our Jobber API rate limits post. For the full menu of what connects to what, start with the honest guide to Jobber integrations.

Where to start

Run the one-invoice test today. It costs nothing and takes twenty minutes with your bookkeeper on the phone. It converts “the sync is broken” into a named problem: tax setup, mapping, or migration damage. Most shops fix it at the first or second rung of the ladder.

If your test points at the third rung, the shape problem, that is our lane. Our integrations page covers the bridges we build between Jobber, QuickBooks, and the rest of a shop’s stack. Or book a discovery call and bring your six-invoice comparison. If a bookkeeper can fix it for a few hundred dollars, we will say exactly that.