How to Connect QuickBooks?
For a large share of small and mid-sized businesses in the United States, QuickBooks Online is where the financial story is written. Sales happen in an online store, deals are tracked in a CRM, payments arrive through a payment platform, and eventually all of it has to land in QuickBooks. When those systems don't talk to each other, someone on the team spends hours retyping invoices and matching payments by hand. A QuickBooks integration closes that gap by moving data between systems automatically, accurately, and as soon as it changes. In this guide, we'll look at which QuickBooks product you're integrating with, what an integration can automate, the options available, how the API connection works, and the recent platform changes every integration project should account for.
QuickBooks Online or QuickBooks Desktop?
The first question in any QuickBooks project is which product the business actually uses, because the two are integrated in completely different ways. QuickBooks Online is a cloud platform with a modern REST API, OAuth 2.0 authorization, and webhooks, which makes it the natural target for integrations with web applications and cloud services.
QuickBooks Desktop runs on a local computer or server and relies on older integration technology that requires software to run alongside it. It can still be integrated, but the architecture, effort, and maintenance are quite different. This guide focuses on QuickBooks Online, which is where Intuit concentrates its development and where most new integrations are built.
What a QuickBooks Integration Can Automate
The most common use case is invoicing: when an order is placed or a project milestone is completed in another system, a matching invoice is created in QuickBooks with the right customer, products, and tax settings. Payments received through a payment platform can then be recorded against those invoices automatically, so accounts receivable is always current and bank reconciliation takes minutes instead of hours.
Integrations also work in the other direction. Customer and product records can be kept consistent across systems, and financial data can be pulled from QuickBooks into dashboards, client portals, or internal tools, giving management a live view of revenue and outstanding balances without exporting spreadsheets. The best integrations start with a clear map of which system owns which data, so records never conflict or get duplicated.
Ready-Made Apps or a Custom Integration
The QuickBooks App Store lists a large number of ready-made apps that connect QuickBooks Online with popular e-commerce, payment, payroll, and CRM platforms. When a business's workflow matches what an app offers, this is the fastest route: connect the accounts, adjust a few settings, and the sync begins.
Custom integrations make sense when data needs to flow in a specific way, when business rules are unusual, or when QuickBooks must connect to proprietary software that no marketplace app supports. A custom integration built on the QuickBooks Online API can map fields exactly, handle edge cases such as partial payments and credit notes correctly, and grow with the business. The decision usually comes down to how standard the workflow is and how much the business depends on it running flawlessly.
How the API Connection Works
A custom integration starts in the Intuit Developer portal, where you create an app and receive credentials for development and production. Intuit provides sandbox companies filled with sample data, so the entire integration can be built and tested without touching real books. Authorization uses OAuth 2.0: the business owner signs in to QuickBooks, approves the requested access, and the app receives tokens along with a realm ID that identifies the specific QuickBooks company.
Access tokens are short-lived and expire after about an hour, so the integration must refresh them reliably in the background and always store the newest refresh token it receives. Every API request targets a specific realm ID, which means an application serving many businesses must keep each company's connection and tokens separate and secure. Moving from sandbox to production also requires completing Intuit's security self-assessment and approval process.
Recent Platform Changes to Plan For
In 2025, Intuit introduced the App Partner Program, which changed the economics of the QuickBooks API. Writing data, such as creating or updating invoices, customers, and payments, remains free and unlimited. Reading data, such as queries and reports, is now metered: the free Builder tier includes 500,000 read calls per month, and any read calls beyond that allowance are blocked rather than billed. Paid tiers raise the allowance and add usage-based overage fees.
This makes efficient design a financial concern, not just a technical one. Integrations should fetch only records that have changed, rely on webhooks instead of constant polling, and avoid reading the same data repeatedly. Intuit has also rebuilt its webhooks platform, and all apps had to move to the new CloudEvents format by 15 May 2026, so older integrations may need updating. Rate limits apply per company as well, so large syncs should be spread out and retried gracefully when a limit is reached.
Conclusion
Connecting QuickBooks Online to the rest of your systems removes one of the most repetitive jobs in any finance team and gives you accurate, up-to-date books without manual effort. The key decisions are clear: confirm whether you're working with QuickBooks Online or Desktop, choose between a ready-made app and a custom integration, implement OAuth 2.0 and token refresh carefully, and design around metered API reads and the new webhook format from day one. If your workflow needs more than an off-the-shelf app can offer, our team builds custom QuickBooks integrations tailored to the way your business actually works, designed to stay efficient, secure, and reliable as you grow.