Skip to content
← Build with Zaptiva
Intuit logoQuickBooks Online integration

Build cloud accounting flows
that stay in sync.

Zaptiva connects QuickBooks Online to commerce, CRM, operations, payroll-adjacent workflows, reporting, and approvals through Intuit's REST platform.

Best fitFor cloud-first businesses that want event-aware accounting automation without turning QuickBooks into an uncontrolled data endpoint.
INTEGRATION BLUEPRINT
Production pattern
Business appsCRM · commerce · fieldOperational datarecords · files · eventsPeople + approvalsowners · decisions · exceptions
ZAZaptiva control planemap · validate · govern · observe
INTUIT ECOSYSTEMQuickBooks OnlineOAuth 2.0 + realm-scoped REST
Interface verifiedTraceable transactionsRecoverable exceptions
THE INTEGRATION REALITY

Cloud APIs still need state, identity, and reconciliation.

QuickBooks Online integrations use OAuth 2.0 and operate within an authorized company realm. REST resources, references, query behavior, webhook notifications, change-data capture, minor versions, and rate limits must be handled deliberately.

PRODUCT OVERVIEW

What QuickBooks Online
is built to manage.

QuickBooks Online is cloud accounting software for invoicing, expenses, banking, payments, purchasing, reporting, projects, and—in applicable plans—inventory, classes, locations, custom fields, and workflow automation. Capability and user limits vary by subscription and country edition.

Its REST Accounting API uses OAuth 2.0 and a company realm identifier. Zaptiva designs around supported entities, sparse updates, reference fields, change data, webhooks, and the fact that accounting records often depend on customers, items, accounts, tax settings, and other records already existing in the company.

Cloud accounting

Coordinate customers, vendors, invoices, bills, payments, purchases, bank activity, accounts, and financial reporting.

Projects + dimensions

Depending on plan, track project profitability, classes, locations, custom fields, budgets, and role-based workflows.

REST API ecosystem

OAuth-authorized applications can query and update supported accounting entities for a connected company.

Event-driven synchronization

Webhooks and change-data queries can reduce polling while reconciliation catches missed, reordered, or failed events.

CONNECTION MODEL

OAuth 2.0 + realm-scoped REST

Zaptiva maintains encrypted tokens, scopes every request to the correct realm, consumes change notifications, and reconciles source and QuickBooks identifiers.

Financial and master data

Accounting REST API

JSON resources support supported customers, vendors, items, transactions, accounts, and queries in an authorized realm.

Change notification

Webhooks

Signed notifications indicate changed entities; the integration then retrieves current state rather than treating the notification as the full record.

Gap recovery

Change Data Capture

CDC queries help recover changes after downtime and complement webhooks in a resilient synchronization design.

HOW THE EXCHANGE RUNS

Every movement has a source, a rule, and a result.

The workflow is designed for auditability and recovery—not just a successful demo.

DISCOVER

Authorize

An administrator grants the Intuit app access and Zaptiva stores renewable tokens securely.

Connected
MODEL

Normalize

External records are mapped to QuickBooks references, tax, currency, item, and account rules.

Connected
ASSURE

Exchange

REST requests use the target realm and supported API/minor version.

Connected
OPERATE

Reconcile

Webhooks, CDC, IDs, sync tokens, and source totals keep both sides aligned.

Operational
BUSINESS OBJECTS

The records teams
actually work with.

Scope is confirmed against the installed edition, modules, permissions, and current vendor interface before build.

Customers + vendorsProducts + servicesInvoices + paymentsBills + purchasesAccounts + journalsClasses + locations
ENGINEERING GUARDRAILS

Built to survive real operations.

Technical decisions stay visible to finance, operations, and IT.

CONTROL

Token lifecycle

Refresh, revocation, disconnect, and least-privilege handling are part of the operating design.

RELIABILITY

Reference integrity

Transactions are not submitted until required accounts, items, customers, and tax references resolve.

OWNERSHIP

Webhook recovery

Notifications are verified, deduplicated, and backed by scheduled reconciliation or CDC.

COMMON STARTING POINTS

Put the connection
to useful work.

Choose a focused operating problem, prove the flow, and build from a reusable foundation.

Commerce-to-accounting automation↗CRM quote-to-cash↗AP document processing↗Payment reconciliation↗Operational KPI warehouse↗Customer and item master sync↗
TECHNICAL QUESTIONS

What teams ask
before the build.

Practical answers for architecture, compatibility, deployment, and ownership.

Do webhooks contain the complete changed transaction?+

They are best treated as change notifications. The integration retrieves the current entity and applies idempotent synchronization logic.

Can one connection access multiple companies?+

Authorization and requests are realm-specific. Multi-company designs maintain distinct connection and reconciliation state for each authorized company.

FIRST-PARTY REFERENCES

Grounded in current product documentation.

Capabilities vary by edition, version, modules, licensing, and configuration. Zaptiva verifies the target environment during discovery.

Intuit developer platformIntuit App Partner Program tools
Start with the friction

Ready to connect QuickBooks Online?

Bring us the product version, hosting model, connected systems, and desired outcome. We’ll shape the supported technical path.

Book a conversation
Talk to salesBook a call ↗