Insights

HubSpot QuickBooks Integration: What Syncs, What Breaks, and How to Choose

By Jayant Chaudhary · November 8, 2026

A HubSpot QuickBooks integration is supposed to settle an argument that most growing companies have every month, usually around the close. Sales says a deal closed and was invoiced, finance says the QuickBooks invoice shows a different amount, customer name or no payment at all, and somebody spends an afternoon reconciling two systems that were each correct by their own lights. The two products were built for different people. HubSpot is organized around contacts, companies and deals, which is how salespeople think, while QuickBooks Online is organized around customers, items, invoices and the ledger, which is how accountants have to think. A connector can move records between them, but it can’t decide which one is right.

This article is for the owner, controller or ops lead who already runs both systems and wants them to agree. I’ll go through what needs to sync, object by object, and which system should own each one, then compare the realistic options (HubSpot’s own app, the QuickBooks-side app and other marketplace connectors, an iPaaS, or a custom build against Intuit’s API), describe the traps specific to this pair, and finish with how to test and reconcile the integration before anyone relies on it.

What actually needs to sync, object by object

The first decision is the least technical one. For every kind of record, somebody has to say which system’s version wins when the two disagree. HubSpot’s app makes you face this directly with a data conflict setting, and if nobody has thought about it before that screen appears, it gets decided by whoever happens to be clicking.

ObjectTypical directionSystem of recordCommon trap
Contacts and companies to customersTwo-wayHubSpot until the customer is billed, QuickBooks for billing details afterQuickBooks needs unique customer display names, so a second contact from the same company can fail to sync
Products to Products & ServicesQuickBooks to HubSpotQuickBooksItems without a SKU are skipped by default, and unmatched invoice lines land on a generic line item
Deals and quotesStay in HubSpotHubSpotTreating a closed-won deal as if it were an invoice, or as revenue
InvoicesOne-way or two-way, by choiceWhichever system issues them, decided onceEdits made on the QuickBooks side that never flow back to HubSpot
PaymentsQuickBooks to HubSpotQuickBooksA payment applied to several invoices doesn’t sync to HubSpot
Credit memosTwo-wayQuickBooksCredits spread across several invoices don’t allocate correctly in HubSpot
Sales taxCalculated in QuickBooksQuickBooksHubSpot switches off invoice tax once the sync app is installed
Processing fees and depositsRecorded in QuickBooksQuickBooksCard fees from HubSpot payments don’t sync, so deposits need manual work

Two things in that table deserve emphasis. Deals don’t belong in QuickBooks at all. A deal is a forecast with a probability attached, while an invoice is a legal claim on a customer, so the useful flow is deal to quote to invoice, with the invoice as the first object both systems genuinely share. And payments and fees are accounting events. It’s very useful for a salesperson to see on the deal that a customer has paid, but the ledger has to live in QuickBooks.

The options, and where each one breaks

The right route depends mostly on where you want invoices to be created and on how far your data departs from the defaults.

HubSpot’s QuickBooks Online app is built by HubSpot and installed from its App Marketplace. According to HubSpot’s documentation it syncs contacts to customers, products to Products & Services, and invoices and credit memos in either or both directions, and shows payment information on associated deals. HubSpot to QuickBooks changes are picked up within a few minutes, and QuickBooks to HubSpot changes about every 30 minutes. Custom field mappings need a paid HubSpot tier (the listing names which, so check it against what you have).

The QuickBooks-side HubSpot app works the other way round. Intuit documents a HubSpot for QuickBooks app, for QuickBooks Online Advanced, that sends HubSpot deals into QuickBooks as draft invoices for someone to review and save. It’s one-way and deal-based, and it suits a finance team that wants a human to approve every invoice.

Third-party marketplace connectors fill the gaps the native apps leave, such as QuickBooks Desktop, unusual mappings or historical backfills. They vary a great deal, so ask the vendor to show you, on your own data, what happens when one payment covers two invoices. An iPaaS (Zapier, Make, Celigo and similar) is very good for narrow, one-directional flows, such as creating a QuickBooks customer when a deal reaches a stage, and gets fragile when a workflow has to carry state, handle partial failures or reconcile. A custom build against HubSpot’s APIs and the QuickBooks Online Accounting API costs the most to start and gives you full control over matching, idempotency, tax handling and audit trails.

OptionFits whenBreaks when
HubSpot’s QuickBooks Online appYou invoice from HubSpot, run US sales tax through QuickBooks, and your data is close to the defaultsMany contacts per company, heavy QuickBooks-side invoice editing, non-US tax requirements, revenue recognition
HubSpot for QuickBooks (QuickBooks Online Advanced)Finance wants deals to arrive as drafts for reviewYou need anything to flow back to HubSpot, or you’re not on Advanced
Third-party marketplace connectorYou need QuickBooks Desktop, deeper mappings or backfillIts handling of edge cases is a black box you can’t test
iPaaSA few simple, one-directional triggersMulti-step flows with retries, partial failures and reconciliation
Custom buildUnusual data models, volume, several entities, or strict audit needsNobody owns it after go-live

In my experience the native app is the right first answer for more companies than consultants admit, and the wrong one for most B2B companies with several buyers per account.

The traps specific to HubSpot and QuickBooks

Customers are companies, and HubSpot thinks in contacts

HubSpot’s app syncs contacts to QuickBooks customers, and by default it sets the customer’s display name from the contact’s associated company. QuickBooks requires display names to be unique, so, as HubSpot’s own documentation puts it, any further contacts from that company that try to sync after the first one will fail. HubSpot recommends a single billing contact per company, which is really a process decision: someone has to name the billing contact at each account and keep the rest of the buying committee out of the sync. Teams that skip this end up with failed syncs and, after a few manual workarounds, duplicate customers.

Who owns the invoice

You can create invoices in HubSpot (from a deal, a quote, a record or a workflow) and have them sync to QuickBooks, or create them in QuickBooks and sync them back. Either is reasonable on its own; doing both at once causes trouble. HubSpot’s documentation lists QuickBooks-side edits that won’t sync back, including adding or removing line items, changing prices, removing payments and adding tax. So if HubSpot issues the invoice, corrections belong in HubSpot, or the two copies quietly diverge. Write the rule down, and tell whoever in finance has been fixing invoices in QuickBooks for years.

Products, SKUs and the catch-all line

HubSpot recommends syncing products from QuickBooks and matching on SKU, and by default only products with SKUs sync at all. An invoice line in HubSpot that doesn’t match a QuickBooks item goes to a generic custom line item product in QuickBooks. That keeps the invoice moving, but the revenue lands in whatever income account that item uses, which is rarely what the controller intended. Clean up SKUs in QuickBooks first, and treat any invoice hitting the catch-all as an exception.

Sales tax, revenue recognition and non-US companies

Tax is where the native app is most constrained. HubSpot’s documentation says that once the QuickBooks Online sync app is installed you can’t add taxes to HubSpot invoices, and that HubSpot invoices can’t be created with tax, which rules the invoice sync out for non-US QuickBooks accounts that require tax. HubSpot invoices also don’t carry service dates, so QuickBooks’ revenue recognition isn’t supported through the sync. For a US company selling simple services this hardly matters, but for a subscription business recognizing revenue over a term, or a company billing VAT or GST, it often decides the case for invoicing from QuickBooks or building something custom.

I couldn’t find anything in HubSpot’s documentation about how the app treats multi-currency invoices, so if you bill in more than one currency, test it explicitly before you rely on it.

Payments, fees and the deposit that doesn’t match

When a customer pays a HubSpot invoice online, the payment syncs to QuickBooks, but HubSpot says card fees won’t sync to the invoice and processing fees don’t create expenses there, so the bank deposit is smaller than the payments recorded against it and someone has to book the difference. ACH payments are marked paid in QuickBooks only once they complete, even if HubSpot already shows the invoice as paid. A payment applied to more than one invoice in QuickBooks won’t sync to HubSpot at all, and payments made before the connection don’t sync either, so the payment history in HubSpot begins on the day you switched it on.

Illustrative scenario: a composite of common situations, not a specific client. A professional services firm turns on the native app and starts invoicing from HubSpot. Its larger clients pay quarterly with a single transfer covering several invoices, which the bookkeeper applies in QuickBooks. Within a month, account managers are chasing clients for invoices that were paid weeks earlier, because those payments never reached HubSpot. The fix is unglamorous: change how those payments are recorded, or add a small piece of custom logic that reads them from QuickBooks and updates HubSpot.

When you build it against the QuickBooks Online API

A custom build, or a custom component next to the native app, works against Intuit’s QuickBooks Online Accounting API, and a few of its characteristics shape the design. Intuit documents a limit of 500 requests per minute per company (what Intuit calls a realm), separate limits for batch requests, and an HTTP 429 response when you’re throttled, with advice to wait 60 seconds before retrying. Under Intuit’s App Partner Program, certain API calls, mostly reads, are metered against a monthly allowance, so a chatty integration now has a running cost as well as a performance cost. Check Intuit’s current tier details before designing the polling schedule.

For changes, Intuit offers webhooks, which tell you that an entity changed (its name, ID, operation and timestamp) and leave you to fetch the current record, and a change data capture endpoint that returns records changed since a point no more than 30 days back. Use both: webhooks for speed, and change data capture to catch anything the webhooks missed. Updates to QuickBooks objects carry a sync token, which acts as an optimistic lock, so a writer working from a stale copy is rejected. The integration should handle that by re-reading and retrying. On the HubSpot side, every write should be idempotent, keyed on the QuickBooks ID, for the reasons set out in our article on idempotent webhooks.

How to test and reconcile before trusting it

Testing this pair has one awkward wrinkle: HubSpot’s app can’t connect to a QuickBooks sandbox company. A custom build can use Intuit’s sandbox, but the native app needs a real QuickBooks company that isn’t your books, set up with your chart of accounts, tax settings and item list. Don’t run the first sync against production and hope.

Then work through the cases that break things, deliberately:

  • two contacts at the same company, both marked for sync;
  • a HubSpot invoice with a line item that has no SKU in QuickBooks;
  • an invoice edited in QuickBooks after it synced, both adding a line and changing a price;
  • an online card payment, an ACH payment, and a manual payment;
  • one payment applied across two invoices, and a credit memo applied across two;
  • a voided invoice and a refunded payment;
  • a deliberate conflict, with the same field changed in both systems inside the sync window.

For each, record what you expected and what happened, and decide whether the answer is configuration, a process rule or custom logic.

Once it’s live, reconcile on a schedule. A weekly report should compare open invoice balances in both systems and list unmatched QuickBooks payments, failed customer syncs and catch-all invoices. At month-end, compare payments received through HubSpot with the deposits in QuickBooks and confirm that fees explain the difference. Our article on the integration reconciliation report covers how to build one that people actually read, and once it exists, finance can stop double-checking everything by hand.

Related reading

How we approach it at eProxim

eProxim has been building the technical layer between business systems since 1997, and HubSpot integration services and QuickBooks integration services are a regular part of that work, alongside ecommerce, accounting, CRM, marketing and inventory platforms. We start by deciding, object by object, which system owns what, then configure the native app where it fits and build only what it can’t handle, such as multi-invoice payments, tax-aware invoicing or a reconciliation report. Sometimes the native app plus a couple of process rules is enough, and we’ll say so.

We can usually start within a week, and small, fixed-scope jobs are welcome. We work by fixed price, by the hour, or as a monthly block of hours. Agencies with a client in this position can read how we work behind them on our page for small agencies and dev shops. You’ll find more about our CRM work on our HubSpot page, and if your HubSpot and QuickBooks numbers don’t agree, tell us about it.

About the author

Jayant Chaudhary

Jayant Chaudhary is a technology executive, entrepreneur, and recovering optimist about how businesses make decisions. After more than 30 years in the industry, he's learned that technology is rarely the hardest part. People, politics, and PowerPoint usually are. He writes about business, technology, leadership, and lessons learned the expensive way. He has strong opinions, but reserves the right to change them when confronted with facts. This, as we all know, is an increasingly unfashionable habit.

Working with eProxim

Have integration work your team can’t - or doesn’t want to - take on? We deliver it under your brand.