QuickBooks Integration: Connecting QuickBooks to Your CRM and Other Systems

A QuickBooks integration connects QuickBooks to another system so that customers, invoices and payments move between them without anyone retyping them. You have three routes: an app from Intuit’s app marketplace, a no-code tool such as Zapier or Make, or a custom build on the QuickBooks Online Accounting API. The right one depends on your volume, how many records must be matched between systems, and whether you need two-way sync.

Check the marketplace first. Intuit says QuickBooks connects with over 800 popular business apps, and a listed app that moves the right records in the right direction is usually the cheapest and quickest route. A custom build earns its cost when the logic spans several systems, the volume is high or nothing listed fits the way you work. With us, connecting two systems starts from £5,000 (about $6,500), at a fixed price agreed before work starts.

This guide covers what to connect QuickBooks to, how to choose a route, what an API build involves and costs, the limits and fees Intuit sets, and the problems that catch teams out. It is a neutral buy-or-build guide, so it will tell you when a ready-made connector is the better answer.

What can you connect QuickBooks to?

QuickBooks is the finance end of the stack, so the useful question is which system creates the money events. Many CRMs and ecommerce platforms offer a connector of some kind, so look for a listing before you plan a build. The table shows the usual candidates.

System type	Examples	Typical data flow
CRM	HubSpot, Salesforce	Customers and won deals into QuickBooks as invoices; payment status back
Ecommerce	Shopify	Orders and payouts into QuickBooks
Payments	Card processors, payment links	Payments matched against open invoices
Field service and job management	Job, scheduling and timesheet tools	Completed jobs or approved hours become invoices
Your own platform	Customer portal, internal system	Whatever your data model creates, built against the API

For ecommerce, Intuit lists the Shopify Connector by QuickBooks among its integrations, so that is the first thing to test if you sell on Shopify. For a CRM, the usual first flow is a won deal raising an invoice, with the payment status flowing back so sales can see who has paid.

A bespoke platform is different. Nothing in a marketplace knows your data model, so the QuickBooks side is built against the API. For an international events group, we connected Pipedrive, SmartDocs and Xero without replacing any of them. When a contract is signed, the CRM updates and the sales invoice is raised automatically. That project used Xero, not QuickBooks, and the same signed-contract-to-invoice pattern carries over.

If your problem is supplier bills arriving in QuickBooks, that is a capture problem before it is an integration problem, and our accounts payable automation guide compares the tools. Our API integration guide covers the general mechanics of connecting any two systems, and our ERP integration guide covers larger estates.

App marketplace, Zapier/Make or a custom API build?

The cheapest route that does the job is usually the right one. Work down the table in order and stop at the first row that fits.

Route	Wins when	Watch for
Marketplace app	Your CRM or ecommerce platform has a listing that moves the records you need	It syncs what its maker chose, in the direction they chose
Zapier or Make	Both sides have connectors and the logic is a simple trigger and action	Usage-based billing, and a flow that quietly becomes critical
Custom API build	The logic spans systems, volumes are high or nothing listed fits	It needs a proper build and someone to look after it

Search the Intuit integrations directory for the name of your CRM or ecommerce platform. For each listing, check which records it syncs, in which direction, and what it does when a record already exists or a call fails. Test it on a copy of your data before you commit.

No-code tools are the middle step. Zapier’s QuickBooks Online integration lists dozens of triggers and actions. Make has a QuickBooks app that includes a module for making your own API calls. That is useful when a standard module does not cover the record you need.

These tools break down in four places:

• Custom matching rules. Deciding that two customer records are the same person takes more than a trigger and an action.
• High volume. Usage-based pricing climbs, and a flow that retries blindly can hit Intuit’s limits.
• Two-way conflicts. When both systems can edit a record, simple flows overwrite each other.
• Your own platform. There is no connector for software only you run, so the API is the only way in.

Our systems integration page takes the same position: if two of your systems already sync natively, we’ll tell you to switch that on.

What does a QuickBooks API integration involve?

A custom integration is code that talks to QuickBooks for you, with rules for what to send, when, and what happens when something fails. The technical side is conventional. The QuickBooks Online Accounting API is a REST API that uses JSON. Webhooks notify your system whenever data changes, so you do not have to poll QuickBooks all day to find out.

Get authentication right first. Intuit’s OAuth FAQ sets out the token rules:

• Access tokens are valid for 3,600 seconds, which is one hour.
• Refresh tokens expire on a rolling basis, 100 days after they were last used.
• Refresh token rotation. Intuit updates the refresh token value every 24 hours, so your integration must always store the newest one.
• Maximum validity. All refresh tokens have a maximum validity of five years.

The rotation rule has a practical consequence. If your code refreshes the access token but throws away the new refresh token, a later refresh fails, and the sync stops. Store the latest token every time, in a secure place, and alert someone if a refresh fails.

Whichever route you take, the build work has the same shape:

• Map one flow first. Name the trigger, the fields that move and the direction, such as a won deal creating an invoice. Add the next flow only when the first is live.
• Build the matching rules. Decide how a record in one system is recognised in the other. Store each system’s ID in the other and match on those.
• Make every call safe to repeat. A retry must never create a second invoice.
• Add an error queue. A failed record goes to a queue a named person reviews, so one bad customer does not block the rest.
• Test with messy data. Use real customers with missing ZIP codes or postcodes, odd characters in names and part-paid invoices.
• Produce a reconciliation report. A simple report showing what moved, what failed and what is waiting lets finance trust the sync.
• Go live in stages. Start with one flow and a short run alongside the manual process.

QuickBooks API limits and what they mean for your build

Intuit sets limits and throttles on the QuickBooks Online API. Each company, identified by its realm ID, allows 500 requests per minute. A second limit allows 10 requests per second for each company and app. Intuit recommends no more than 30 operations in a single batch request.

When you go over a limit, QuickBooks returns an HTTP 429 response. A well-built integration queues its calls, waits and retries with back-off, and carries on instead of failing. Batching helps too, because one batch request can carry up to 30 operations.

Two illustrations show the scale. Both use simple arithmetic on the published limits.

• Day-to-day. Raising 500 invoices a month, one call each, is a trickle. Even at 22 working days that is roughly 23 calls a day, far below 500 a minute.
• Month-end and back-fill. Pushing 10,000 records in one burst is a different job. At 500 requests a minute with one operation per request, that is at least 20 minutes of calling. Batches of 30 operations cut the number of requests to around 334. Either way, run it as a paced, scheduled job that watches for 429 responses.

The lesson is to pace bulk work. Month-end is when finance wants everything synced at once, and it is also when a naive integration hits the limits. Queue the work and spread it out.

Intuit’s developer fees (the App Partner Program)

Intuit charges developers through its App Partner Program. The fee depends on how many API calls the app makes. At the time of writing (November 2026), the US rates are:

Tier	Monthly fee	CorePlus API calls included
Builder	No charge	500,000
Silver	$300	1 million
Gold	$1,700	10 million
Platinum	$4,500	75 million

Intuit splits API calls into two groups. Core calls are uncapped. CorePlus calls are metered against the credits in the table, so check Intuit’s page for which calls fall in each group. The limits page lists 500,000 CorePlus calls per workspace per month on the Builder tier.

For a single-company integration, 500,000 CorePlus calls a month is a large allowance, so the free Builder tier is usually enough. The fees fall on whoever owns the app, which for a custom build may be you. Ask any integrator which tier their app sits on, and who pays if it moves up. Prices change, so check Intuit’s page before you budget.

How much does a QuickBooks integration cost?

There are two costs: the QuickBooks plan you already pay for, and the integration on top. For context, Intuit’s pricing page lists QuickBooks Online at $38 a month for Simple Start, $85 for Essentials, $140 for Plus and $340 for Advanced, at the time of writing (November 2026). Intuit is also running 50% off for the first three months, so the price you pay may differ.

For the integration itself, no-code routes cost a tool subscription plus the time to set them up and test them. Marketplace apps are subscriptions priced by their makers.

With us, connecting two systems you already use, such as your CRM and QuickBooks, starts from £5,000 (about $6,500) and includes syncing both ways with checks. A business-wide integration across your core tools starts from £12,000 (about $15,600). Each price is fixed and agreed before work starts. After go-live, support starts from £400 (about $520) a month.

For a larger estate with an ERP and several other systems, enterprise software integration starts with an integration audit and plan from £4,000.

What moves the price of a custom build:

• How many systems and flows. A CRM-to-QuickBooks invoice flow is one job. A second system adds its own mappings, tests and failure cases.
• Direction. Sending invoices into QuickBooks is simpler than also writing payments and contact changes back, which needs a rule for when both sides edit a record.
• Data quality. Duplicates already sitting in your CRM or QuickBooks need cleaning before they can be matched.
• History. Copying years of past transactions is a separate job from syncing new ones.
• Volume. Bulk and month-end loads need batching, a queue and back-off.

QuickBooks Desktop or QuickBooks Online?

Build new integrations against QuickBooks Online. From 30 September 2024, Intuit stopped selling new US subscriptions to QuickBooks Desktop Pro Plus, Premier Plus, Mac Plus and Enhanced Payroll. Existing subscribers are unaffected, and Desktop Enterprise is still sold.

Desktop integrations work differently, because there is no cloud API like the one Online provides. If you run Desktop today, the integration route depends on your version and setup, so ask your integrator to confirm what is possible before you scope anything. If you are thinking about moving to Online, treat that as a separate decision and do it before you build, so you do not integrate twice.

What goes wrong with QuickBooks integrations?

These problems appear after go-live, so settle them at the start. For polling, webhooks and alerting in general, see our API integration guide.

Duplicate customers from loose matching. Matching on a name or an email address creates duplicates, because people type “Acme Inc.” and “ACME Incorporated” and use more than one email. Store each system’s ID in the other and match on those.

A refresh token that is not stored after rotation. Intuit rotates the refresh token, so code that keeps using the old one works for a while and then stops. The sync fails silently, and nobody notices until finance asks why invoices are missing. Store the newest token every time and alert on any failed refresh.

Throttling at month-end. Bulk syncs near month-end collide with the per-minute and per-second limits. Pace the work through a queue and retry 429 responses with back-off.

Two-way sync conflicts. When both systems can edit a record, they overwrite each other. Decide which system wins for each field and write it down. This is the default we start from:

Record	Usually owned by	Why
Deal, stage, contract	The CRM	Sales works there
Invoice, tax, payment status	QuickBooks	Finance reports from it
Customer name and address	One system, chosen up front	Two editors overwrite each other

Change these where your business differs.

Syncing summary reports instead of transactions. A report shows totals, and totals cannot be matched back to the deal or order that produced them. Sync the individual transactions and build reports from those.

Tax and currency settings that differ between systems. If your CRM stores prices including tax, or quotes in a different currency, an invoice in QuickBooks can differ from the quote unless the mapping is deliberate. Have your accountant confirm the tax and currency treatment of each product line before go-live. This is general information, not tax advice.

Using Xero instead?

Many of the same patterns apply to Xero. Our Xero integration guide covers the Xero App Store, its API limits and the pitfalls specific to Xero.

If the job is wider than a connection, such as invoicing, payment chasing or reconciliation, start with our business process automation service.

A sensible next step

Name the two systems you want connected and the one flow that costs you the most time, such as a won deal becoming an invoice in QuickBooks. From that we can tell you whether a marketplace app, a no-code tool or a custom build fits, and if an app will do the job, we will say so.

For two systems, start with our systems integration service, from £5,000 (about $6,500). For an ERP and several other systems, our enterprise software integration work begins with an audit and plan from £4,000.