Skip to content
ERP Builders

Integration · Accounting

QuickBooks and ERP: integrate during transition, migrate when ready

Many businesses come to ERP from QuickBooks. Sometimes accounting stays in QuickBooks for a while — for a subsidiary, or until year end — while operations move to the ERP. Sometimes everything migrates at once.
Integration flow from QuickBooks through an integration layer with queueing, mapping and retries into ERPSOURCEQuickBookswebhook · RESTINTEGRATION LAYERValidate + mapQueue (idempotent)Retry w/ backoffDead-letter + alertSYSTEM OF RECORDERPorders · stock · ledgerINBOUND (ORDERS, CUSTOMERS)OUTBOUND (STOCK, STATUS, INVOICES)

Overview

What this integration is for

We support both: temporary integration that keeps QuickBooks accurate, and clean migration of master data, open items and balances.

01Data

What data syncs, and in which direction

Data synchronised between QuickBooks and the ERP
EntityDirectionNotes
Customers & vendorsERP → AppCreated or updated in QuickBooks from ERP partners.
Invoices & credit notesERP → AppPosted with mapped items, taxes and accounts.
BillsERP → AppSupplier bills synchronised for payables.
Payments⇄ BothDepending on which system records payments.
Journal summariesERP → AppInventory and COGS as summarised journals.

02Use cases

Common use cases

01

Phased ERP adoption

Operations on ERP, accounting in QuickBooks until cutover.

02

Subsidiary accounting

Small entities remain on QuickBooks with consolidated data.

03

Migration

Master data and opening balances moved to ERP.

03 — Architecture

API architecture

The QuickBooks Online Accounting API is used with change data capture queries to detect updates. ERP documents are posted as they are confirmed, or as daily summaries to reduce volume.

Account and tax mapping tables translate ERP structures into QuickBooks equivalents.

Integration flow from QuickBooks through an integration layer with queueing, mapping and retries into ERPSOURCEQuickBookswebhook · RESTINTEGRATION LAYERValidate + mapQueue (idempotent)Retry w/ backoffDead-letter + alertSYSTEM OF RECORDERPorders · stock · ledgerINBOUND (ORDERS, CUSTOMERS)OUTBOUND (STOCK, STATUS, INVOICES)

04Reliability

Authentication, errors and retries

01

Authentication

OAuth 2.0 authorisation by a QuickBooks admin; access tokens refreshed using refresh tokens, which must be renewed before they expire. Token health is monitored.

02

Error handling

Validation errors (closed periods, missing tax codes, duplicate document numbers) logged per document with an exception queue.

03

Retry strategy

Retries respect API throttling; documents are posted idempotently using stored QuickBooks IDs.

05 — Data mapping

Field mapping essentials

Field mapping between QuickBooks and the ERP
QuickBooksERP
ERP partnerCustomer / Vendor
ERP productItemOr summarised by category
ERP accountQuickBooks account
ERP taxTax code
ERP invoiceInvoice

06 — Automation

Automation opportunities

  • Post invoices and bills on confirmation
  • Daily inventory and COGS journals
  • Alert when OAuth connection needs reauthorisation
  • Reconciliation report of ERP vs QuickBooks totals

07 — Security

Security considerations

Tokens stored encrypted; access limited to required scopes; connection authorised by a named administrator.

Insights

Related reading

ERP Integrations2 min read

RFID Integration with Odoo: A Practical Architecture

How to integrate RFID readers with Odoo inventory: middleware design, mapping EPCs to products and serials, receiving and counting flows, performance and what to build vs buy.

FAQ

Frequently asked questions

Should we keep QuickBooks with an ERP?

Short-term during transition it can work. Long-term, running two accounting systems adds reconciliation work.

Can you migrate QuickBooks history?

We usually migrate master data, open items and balances, with history archived.

Does this work with QuickBooks Desktop?

Desktop requires different methods; we assess case by case.

Next step

Connecting QuickBooks to your ERP?

Describe the data that needs to move and who owns it. We will propose a design with error handling and monitoring included.