What should a QuickBooks CRM integration sync first? Customers, invoices and payment status, with one system named as the owner of each field. The CRM should own the sales process, and QuickBooks should own the books. Most sync problems come from skipping that decision, not from the API.
Here is how we would scope the work if you run on QuickBooks Online and your sales team keeps asking finance whether an invoice has been paid.
What should a QuickBooks CRM integration sync first?
Start with three flows: customers, invoices and payment status. Those give sales and account teams the answer they ask finance for most often, which is whether a customer has been billed and has paid.
We would build them in this order:
- Customer records. Create the QuickBooks customer when a deal is won, not when a lead appears. That keeps prospects out of your accounting file.
- Invoices. Decide whether the CRM creates a draft invoice or only shows invoices that finance created in QuickBooks.
- Payment status. Send invoice balance and paid status back to the CRM as read-only fields, so account managers can see them without a QuickBooks login.
Leave these for later: the chart of accounts, journal entries, full product catalogs and tax setup. They belong to finance, and most sales teams do not need them to do their job.
Which system should own each record?
Give every field one owner before anyone writes code. Two-way sync on everything sounds helpful, but it is how a typo in the CRM ends up on a customer's invoice.
A simple ownership split works for most companies:
- CRM owns: leads, deals, contacts, activity history and sales stage.
- QuickBooks owns: invoices, payments, balances, credits, tax and anything that affects your books.
- Shared with a rule: company name and billing address. Pick one system as the source. If the other system differs, flag it for a person to review.
You also need one match key. Store the QuickBooks customer ID on the CRM account and the CRM account ID in a reference field on the QuickBooks side, if your setup allows it. Matching on company name alone creates duplicates the first time someone types "Inc." differently.
Check your own QuickBooks data before go-live. Merge duplicate customers first, because a sync will copy that mess into your CRM. Our guide to CRM data cleanup covers the CRM side of that work.
What QuickBooks API limits should you plan for?
This guide covers QuickBooks Online, and these numbers come from Intuit's developer documentation. Check them again before you build, because Intuit has changed them before.
Intuit's published limits for the REST API include:
- 500 requests per minute per company (Intuit calls this a realm ID).
- 10 requests per second per company and app.
- 120 batch requests per minute per company, with a recommended maximum of 30 payloads per batch.
- An HTTP 429 response when you are throttled, with advice to wait 60 seconds before retrying.
These limits rarely hurt day-to-day sync for a small team. They do hurt the first historical load and any job that reads every invoice on a timer. Plan the first load as a slow batch job outside business hours, and make it safe to restart.
Does reading QuickBooks data cost money?
It can, and this catches teams that built their integration before 2025. Under the Intuit App Partner Program, data-in calls such as creating or updating invoices and customers are not metered. Data-out calls such as reading accounts and fetching reports are metered as CorePlus calls.
The free Builder tier includes 500,000 CorePlus credits a month, and calls above that are blocked. The paid Silver tier includes 1 million credits and charges variable fees beyond that. Prices and tiers can change, so confirm them with Intuit.
The design lesson is simple. A sync that polls every invoice every few minutes uses read calls you may not need. Event-driven updates usually use far fewer. If you buy a connector instead of building one, ask the vendor how it handles these limits and who pays for the usage.
How do you keep the sync from drifting?
Use webhooks for speed and a scheduled check for accuracy. Webhooks tell you a record changed. They are not a guarantee that you received every change.
Intuit's webhook guidance says to respond to a notification within 3 seconds with an HTTP 200, and to queue the real work instead of processing it in the endpoint. It also recommends Change Data Capture calls to recover events you may have missed, with an optional daily run for the entities you need.
We would add three controls of our own:
- A daily reconciliation. Compare open invoice counts and totals between the two systems, and alert someone when they differ.
- An error queue with an owner. Failed records need a named person, not just a log file.
- Safe retries. A retry must never create a second invoice. Test this on purpose in a sandbox.
Also read Intuit's change notices. Its 2025 API changes removed the Customer and Vendor Source field from responses and added usage limits on classes, departments and accounts tied to subscription tier. An integration that relied on one of those could break with no change on your side.
Should you buy a connector or build a custom integration?
Buy a connector when your process is standard: one QuickBooks company, one CRM, and simple customers and invoices. It will likely cost less and go live faster.
Build custom when the rules are the hard part. Common signs include multiple QuickBooks companies, approvals before invoicing, milestone or usage billing, or a third system such as a project or inventory tool in the same flow. In those cases, a connector can leave your team doing the difficult exceptions by hand.
Either way, ask the same questions:
- What happens when a record fails, and who is told?
- Can we see every sync event and replay a failed one?
- How does it handle a voided invoice or a merged customer?
- What does it cost when volume doubles?
If you are weighing this for other finance systems too, our posts on NetSuite integration and payroll integration use the same ownership approach.
Frequently asked questions
Yes, but limit it. Use two-way sync only for a few shared fields, with one system named as the source. Invoices and payments should be owned by QuickBooks and shown read-only in the CRM.
Usually not. Create the QuickBooks customer when a deal is won or when you are ready to invoice. This keeps your accounting file limited to real customers.
Not directly. The limits and program details here are for QuickBooks Online. Desktop connects differently, so confirm the integration method for your version with Intuit or your connector vendor.
It depends on your rules and data quality more than on the API. A standard connector is often the fastest route. Custom billing rules, duplicate cleanup and testing are what add time, so scope those first.
Sources
- Intuit Developer: API call limits and throttles
- Intuit Developer Blog: Introducing the Intuit App Partner Program
- Intuit Developer Blog: Best practices for using webhooks with QuickBooks Online
- Intuit Developer Blog: Upcoming changes to the Accounting API
Connecting QuickBooks to your CRM
We can map your fields, ownership rules and exceptions with you, then tell you whether a connector is enough or a custom integration makes sense.
Talk to Our Integration Team
