Jobber Not Syncing to QuickBooks? Start With the Symptom

Somebody notices on the 3rd of the month. The bank balance in QuickBooks looks nothing like the one in the app, a fortnight of invoices are missing, and there's a red number sitting in the corner of Jobber.

Almost everything written about this problem is a list of error strings, which is fine if you already know which error you have. But that isn't the position you're usually in. You're looking at a symptom — things aren't arriving, or they're arriving twice, or they arrived but the totals are off by a few cents — and you want to know what that symptom means before you start clicking things.

So this walkthrough is organised the way the problem actually presents. Find the paragraph that matches what you're seeing, and work from there.

Before Anything: Which Version Are You Running?

Jobber operates two generations of QuickBooks Online integration, and they don't behave alike. Half the guidance floating around the internet was written for the other one, which is a large part of why troubleshooting advice so often doesn't match what's on your screen.

The quickest tell is whether you have to ask for a sync. The older version waits for you to trigger it and puts a QuickBooks icon in the top navigation to do that. The newer one runs continuously in the background, with no sync button at all, managed under Gear Icon → Settings → Connected Apps → QuickBooks Online, and it surfaces problems through an alert in the top navigation that opens a sync activity dashboard.

That dashboard lists every error and warning with suggested steps and keeps a history of previous syncs. If you're on the newer generation, it's where the rest of this article happens.

A word of caution if you're thinking of upgrading as a way out of a mess: Jobber describes the move as permanent, with no route back to the older integration. Clear your existing backlog first and migrate deliberately.

The Triage Table

Match what you're seeing to the section that explains it:

Symptom 1: Nothing At All Is Arriving

When the flow has stopped completely rather than partially, don't start opening invoices. A total halt is nearly always one of four things, and none of them live in your data:

• The authorisation lapsed. You'll see wording along the lines of the Jobber account no longer being connected. Re-authorise through the link on the message, or disconnect and reconnect the app.
• The QuickBooks user who set it up was deactivated or had permissions reduced. The connection inherits that person's rights, so removing them quietly removes the integration's access — and the message you get talks about permissions rather than about the user, which sends people looking in the wrong place.
• The QuickBooks subscription lapsed. A failed card on the QuickBooks side stops the interface entirely. Nothing to fix in Jobber.
• The accounting period is closed. If you closed the books and the sync is trying to post into that period, it can't. Either reopen it briefly or date the entries into the open period.

There's a fifth case that's temporary and self-healing: a message about too many updates, or a straightforward failure to reach either service. That's rate limiting or an interruption at one end. The correct response is to wait half a minute and retry once. Hammering Retry is what causes the rate limiting in the first place, so the instinctive reaction genuinely makes it worse.

Symptom 2: Some Things Sync, Others Never Do

This is the most common presentation and the most misread. A list of thirty errors feels like thirty problems. It usually isn't.

Records travel to QuickBooks in a fixed order of dependency. A customer must exist before an invoice can name them. The services on the invoice must exist before the invoice can list them. The invoice must land before a payment can be attached to it. And a card payout can only be assembled once its constituent payments are all there.

Which means one stuck customer at the top produces a growing tail of unrelated-looking failures underneath, each with its own message. Jobber publishes the sequence to work in, and following it turns a long afternoon into a short one:

1. Customers
2. Products and services
3. Invoices
4. Payments, refunds and tips
5. Payouts

Retrying an invoice whose customer is broken will fail every time, forever. The error you can see is rarely the error you need.

Read the entire list before acting, note how many entries relate to the same handful of customers, fix those, and watch most of the rest clear on their own.

Symptom 3: Duplicate Customers Keep Multiplying

Here's the mechanism, because once you know it the behaviour stops being mysterious.

Customers are paired between the two systems by comparing their display names as plain text. Not by email, not by an ID both sides agreed on — by the name string. QuickBooks separately refuses to keep two customers sharing a display name.

Put those together and consider a landscaping outfit with a client entered as "Brightleaf Grounds Care Ltd." in one system and "Brightleaf Grounds Care" in the other. To you they're obviously the same account. To the matching logic they're strangers, so a second customer is created — and from then on, half the invoices go to one and half to the other.

Usual offenders, all of which look like nothing:

• A trailing period after Inc. or Ltd.
• A comma before LLC in one system and not the other
• & versus the word "and"
• A double space where somebody hit the spacebar twice
• Title Case in one place, ALL CAPS in the other

To fix a split that already happened: pick the record you want to keep and make both sides match it exactly. Where the two really need to become one, Jobber documents a merge manoeuvre — rename the client in Jobber to something obviously different, allow it to sync, then rename it back to the original and accept the merge prompt, which joins the records rather than adding a third.

To stop it recurring: agree one house style for customer names and stick to it. It's a dull rule that removes an entire recurring category of error.

The other reason customers get rejected: field limits

QuickBooks caps how much text various fields hold, and the failures read as cryptic messages about string length. The recurring cause is nearly always a structured field being used to store a note — "gate code 4471, dog in yard" typed into an address line, or "mobile — don't call before 8" in the phone box.

Jobber's documentation lists the ceilings: 25 characters for a client display name, 30 for a phone number, 50 for an address, 100 for an email, 1,000 for the message to the client on an invoice, and 4,000 for a line item description. Payment reference numbers such as cheque numbers are capped at 21.

Move the commentary into job notes or a custom field, where it belongs and where nobody's field limit applies to it.

Symptom 4: Invoices Won't Go Across

Two causes account for the overwhelming majority.

The invoice number is already taken

Each system runs its own numbering, and QuickBooks won't accept a document number it's already holding. If invoices were once entered directly in QuickBooks, or historical records were imported, the two sequences overlap and collide.

Fixing them one at a time is a losing game. Instead, lift the Jobber numbering above the highest number QuickBooks already contains so the ranges separate permanently. Then settle the underlying question: if Jobber raises invoices, it should raise all of them.

A tax rate that doesn't exist on the other side

Tax is the single biggest source of invoice rejections, and it arrives in a few distinct flavours:

• A rate Jobber uses has no counterpart in QuickBooks. Create it in the QuickBooks tax settings, or drop it from the Jobber invoice. Corresponding names matter — a rate of the same percentage under a different label doesn't count as a match.
• There's no zero percent code. This one catches a lot of people. A line that carries no tax still has to be recorded as something, and QuickBooks expresses that as an explicit 0% code. If one has never been created, every single non-taxable invoice fails — which is why the symptom often looks like "all my mowing invoices sync and none of my exempt ones do". Create the 0% rate once and the pattern vanishes.
• The regional setting is wrong. If the integration thinks you're on one region's QuickBooks and you're on the other's, you get tax errors that look like data faults. The tell is a message about GST/HST when you don't file it. Correct the setting rather than the invoices.

Two smaller ones worth knowing: an invoice totalling zero or less is refused outright, because QuickBooks needs at least a cent — usually the result of a discount swallowing the whole subtotal. And backdating an invoice to before an inventory item's start date in QuickBooks will be rejected, which bites when catching up on a backlog.

Symptom 5: It Synced, But the Numbers Are Wrong

This is the quietest failure on the list and the one most worth understanding, because nothing appears in your error queue. Both cases show up as warnings, not errors, and warnings are easy to skim past.

Tax rate substitution. If the rate an invoice needs can't be located in QuickBooks — commonly because somebody made it inactive rather than deleting it — QuickBooks may proceed using a different rate. The invoice syncs successfully. It syncs with the wrong tax on it. Reactivate or recreate the correct rate, then go back and check whatever crossed while the substitution was running.

Rounding differences. Jobber and QuickBooks don't always round tax identically, so the same invoice can land a cent or two apart. The record syncs and a warning is raised. Individually it's noise; over a year of invoices it becomes a difference nobody can trace when the accounts don't tie.

Symptom 6: Payments Arrive But Aren't Applied to Anything

When a payment reaches QuickBooks and floats unattached, or refuses to sync with a message about a transaction that can't be linked, the cause is nearly always the same: the invoice was edited, voided or deleted inside QuickBooks after it had already synced. The payment is reaching for something that has changed shape.

The documented way through: open the payment in Jobber, change what it's applied to from the specific invoice across to the client account balance, and save. It then syncs as an unapplied credit sitting on that customer, and you match it to the right invoice manually inside QuickBooks. The cash ends up correct; only the linking is done by hand.

More useful than the remedy is the rule that prevents it. Once Jobber is raising your invoices, stop editing them in QuickBooks. The sync runs in one direction, so a change made on the QuickBooks side never travels back, and it becomes a payment error later that looks completely unrelated to the edit that caused it.

Two setup gaps that break payments

Payments collected outside Jobber's own card processing — cash, cheques, bank transfers — need an Undeposited Funds account in your QuickBooks chart of accounts to sit in until a deposit groups them. If it doesn't exist, they have nowhere to land, and on the older integration the resulting message is unhelpfully technical rather than saying so.

Similarly, each payment method Jobber sends has to exist on the QuickBooks payment methods list. Missing ones are added under Gear Icon → All Lists → Payment Methods. Both are one-off jobs.

Symptom 7: The Card Payout Won't Reconcile

If you take card payments through Jobber, the money doesn't arrive invoice by invoice. It arrives as a settled batch — many customer payments, bundled, with processing fees deducted. That figure is not supposed to match any single invoice, and expecting it to is itself a common source of confusion.

What it does need is for every payment inside the batch to already be in QuickBooks and still unbanked. When that isn't true, you get one of two complaints.

"These payments are already associated with a bank deposit." Something beat the payout to it. Usually a bank feed matched the incoming deposit before the payout sync arrived, or somebody keyed the deposit in manually. Those payments are now committed elsewhere and can't join a second deposit. Three ways out, depending on how far things have gone:

• If the existing deposit is right and already reconciled, tidy the payments in QuickBooks by hand and tell Jobber to ignore that payout. Acceptable once; grim as a monthly habit.
• If it isn't reconciled yet, send the payments back to Undeposited Funds and retry the payout so it can group them properly. Usually the cleanest option.
• Delete the deposit outright and retry — only when you're sure nothing else depends on it.

The durable fix is a decision rather than a repair: choose which system creates the deposit. If the payout sync is doing it, don't let the bank feed match those deposits first.

"Payments from the following invoices haven't been pushed." The dependency chain from Symptom 2, biting at the last link. Go back up the queue. If the payout predates the day you switched payout syncing on, it needs backdating from Jobber's end — that's a support conversation rather than a setting.

Things That Are Working As Designed (Even Though They Look Broken)

A fair share of reported "sync problems" are documented boundaries. Recognising them saves hours of hunting for a fault that isn't there:

• Marking an invoice paid in QuickBooks doesn't inform Jobber. The status only travels outward. Record payments in Jobber if you want both to agree.
• Deleting a record in Jobber doesn't delete its QuickBooks twin. This is how QuickBooks lists gradually fill with things you thought you'd removed.
• One-off invoice lines lose their identity. Anything that isn't a saved product or service arrives as a generic "Custom Service" carrying your text. The money is right; the reporting isn't. If you'll want to analyse it later, make it a real saved item.
• Timesheets are fussy — they need QuickBooks Payroll switched on and employee names matching exactly, and a shift running past midnight must be split across the two days.
• Products and services land as specific types. Services become Services and products become Non-inventory Products, so an existing QuickBooks item of Inventory type with the same name is a conflict that can't be resolved by changing its type in place — it has to be recreated correctly.

Four Habits That Keep the Queue Empty

Nearly every recurring failure above traces to one of these being absent:

1. Give every record one owner. If invoices originate in Jobber, they're never created or edited in QuickBooks. This single rule removes most payment errors.
2. Do the reference data properly, once. Every tax rate you use plus an explicit 0%, all your payment methods, an Undeposited Funds account, a bank account for payouts, and a products list with no duplicate names. Half an hour, once, versus a recurring afternoon.
3. Don't store notes in name and address fields. That's the whole character-limit category, gone.
4. Clear the queue weekly, earliest first. Because of the dependency chain, one ignored customer in week one is forty failures by week four. A ten-minute Friday habit is worth more than any amount of month-end heroics.

If the accounts still won't tie once the sync is clean, the trouble may lie elsewhere — our walkthroughs on reconciling a bank statement and closing the month in order cover the bookkeeping side of the same symptoms.

The Part No Amount of Troubleshooting Solves

Everything above is worth doing, and for many businesses it's the end of the story — a clean setup plus a weekly glance keeps the queue at zero.

Still, it's worth naming why this whole category of problem exists. Two products each keep their own set of books, and the integration's task is to reproduce one product's records inside the other's — pairing on names, submitting to the second product's numbering, tax codes and field limits. Look back over the symptoms: a name that didn't match, a number already claimed, a code that was never created, a record altered on the far side. They're all the same shape of problem.

And there's the thing a perfectly healthy sync still won't give you. Your crews think in jobs. The work is quoted as a job, scheduled as a job, argued about as a job. But that identity is exactly what thins out when invoices become ledger entries, which is why "what did the Halvorsen property actually earn us once materials and the subcontractor were paid?" tends to get answered in a spreadsheet rather than from the accounts. If that's your real question, our guide to job costing for small business covers how to structure it regardless of the tools you run.

Where Kantivo stands on this

Stated flatly, so nobody reads more into it than is there: Kantivo has no Jobber connector at present. One is in active development.

The approach differs in a way worth explaining. Instead of pushing your records outward into a second ledger, it draws invoices, payments and card payouts inward and writes them as genuine double-entry bookkeeping — the payout recorded as a bank deposit alongside its processing fee, clearing its holding account back to zero, and every entry carrying the Jobber job it belongs to, so a profit and loss report for a single job is something you open rather than something you assemble. Jobber remains the authority on the invoice itself; nothing is written back into it.

Being honest about the limits of that: reading in one direction removes the class of trouble where two systems both believe they own an invoice, but it doesn't make every entry postable. Where something can't be recorded cleanly, we decline it and show the reason, rather than forcing a balance and leaving you to discover it at year end.

If that sounds useful, tell us what you'd want from it — there's a request form on our integrations page and we'll let you know when it's ready. And if you came here, fixed your QuickBooks sync, and never think about us again, this page did the job it was written for.

In Summary

Begin with the symptom, not the error text. A complete stoppage points at the connection, the subscription or a closed period. A partial one points at a single jammed record with a queue behind it — so work customers, then items, then invoices, then payments, then payouts, retrying only what sits beneath something you've genuinely repaired. Read the warnings as well as the errors, because a substituted tax rate goes through looking like a success.

Then spend half an hour on the reference data and settle who owns each record, and most of this page stops applying to you.

Frequently Asked Questions

My Jobber invoices stopped appearing in QuickBooks — where do I look first?

Establish whether the connection itself is alive before investigating any individual invoice. A lapsed authorisation, a deactivated QuickBooks user or an unpaid QuickBooks subscription halts everything simultaneously and shows a connection-level message rather than a per-record one. If the connection is healthy, a blocked record is holding up the queue, and the sync activity list will identify it.

Why do the same customers keep appearing twice?

The two systems pair customers by comparing display names as text. A trailing "Inc.", a stray double space, an ampersand instead of "and", or a comma before "LLC" all read as a different customer, so a second record gets created instead of the existing one being reused. Standardising how names are written on both sides is the lasting fix; Jobber documents a rename, sync, rename-back sequence for merging records already split.

A payment reached QuickBooks but isn't applied to the invoice — why?

The invoice it pointed at was changed, voided or removed inside QuickBooks after syncing, so the link no longer resolves. Open the payment in Jobber, switch it from the specific invoice to the client account balance, and save. It syncs as an unapplied credit on that customer, and you match it to the correct invoice inside QuickBooks yourself.

Why won't my Jobber Payments payout reconcile?

A payout is one settled amount covering many card payments with fees deducted, so it deliberately doesn't equal any individual invoice. It can only be assembled if all the payments inside it reached QuickBooks and none have been banked by something else. Where a bank feed already matched the deposit, those payments are spoken for and the payout has nothing left to group.

Every non-taxable invoice fails — what's missing?

An explicit zero percent tax code in QuickBooks. Zero tax isn't the same as no tax rate, so if a 0% rate has never been created, every non-taxable line has nowhere to be recorded and the invoice is refused. Creating it once clears the whole pattern.

Can changes made in QuickBooks flow back into Jobber?

No. The current integration sends data one way, Jobber to QuickBooks, treating Jobber as the master copy. Changes made in QuickBooks stay put, and they're a leading cause of later errors because the record the sync expects has quietly changed. Correct things in Jobber instead.

Is it worth moving to Jobber's newer QuickBooks integration?

For most people yes — it runs continuously rather than on demand, and it handles a single payment spread across several invoices, which the older one doesn't. But Jobber describes the migration as one-way with no route back, so clear your outstanding errors first and do it on a quiet week rather than as an emergency measure.

Where This Information Comes From

The behaviours, messages and remedies described here come from Jobber's own published help documentation, which is the definitive reference and worth keeping to hand:

• Common QuickBooks Sync Errors and How to Fix Them — Jobber Help Center
• QuickBooks Online Sync Error Messages — Jobber Help Center
• How Items Sync Between Jobber and QuickBooks Online — Jobber Help Center
• Migrate to the NEW QuickBooks Integration — Jobber Help Center

Where a fix isn't available through the interface — several of the broken-reference cases fall into this bracket — Jobber's support team can re-sync affected records from their side.

Related Reading

• Job Costing for Small Business: How to Find the Projects Carrying You
• How to Reconcile a Bank Statement (Without Losing an Evening)
• The Month-End Close Checklist for Small Business
• Accounts Receivable Aging Report: How to Read It and Get Paid Faster
• 7 Best QuickBooks Alternatives (Honest Comparison)
• What Is Double-Entry Bookkeeping? A Plain-English Guide
• The Hidden Costs of Cloud Accounting Software