How to Connect QuickBooks Online to Your ERP
Why accounting integrations break so often
Most accounting integrations fail quietly rather than loudly. A connection made with a pasted access token works for an afternoon, expires overnight, and then stops sending anything. Nobody notices until a bookkeeper asks why last week is missing from the books.
The second failure mode is duplication. An integration that retries after a timeout, or that runs on a schedule as well as on an event, can post the same invoice twice. Duplicate revenue in a customer ledger is far more damaging than a missing entry, because it has to be found and reversed by hand.
The third is unmapped accounts. If the integration does not know which ledger account your sales revenue belongs in, it either guesses or dumps everything into a catch-all. The result reconciles to the right total and tells the accountant nothing useful.
What these three share is that none of them announce themselves. A failed sync leaves no gap in your ERP, because the invoice posted locally exactly as it should have. The absence only shows up in the other system, which is usually the one nobody opens until the end of the month. By then you are reconstructing a fortnight of activity from memory rather than fixing a problem you saw on the day it happened.
That is why the setup steps below spend as much attention on verification as on connection. Authorising takes about a minute. Confirming that one invoice arrived intact, with the right customer, the right lines, the right tax, and exactly one copy, is what turns a connection into something a bookkeeper will actually rely on at close.
Why this happens
- Access tokens are pasted manually and expire without warning.
- No stored link between a local invoice and the record already created externally.
- Ledger accounts and tax rates were never mapped, so postings land in a default account.
- Failures are logged where nobody looks, instead of surfaced to the person who can fix them.
Biznsbook addresses this through OAuth 2.0 connect, account mapping, execution logging when the Integrations module is licensed and a SiteAdmin has assigned the connector to your company.
Finance teams lose days each month reconciling versions that should never have diverged. Naming Biznsbook screens as the system of record — and closing periods when agreed — prevents silent edits that auditors flag immediately.
Step-by-step: Connect QuickBooks Online to Your ERP
Written for owners, bookkeepers, and controllers running Biznsbook alongside QuickBooks Online or Xero. Connecting is supported today; the two-way sync is Beta, so verify each step against a sandbox company before a live month-end depends on it.
- Confirm the module and connector are available. The Integrations module must be licensed for your company, and a SiteAdmin must assign the QuickBooks connector to your tenant before it appears in your Integration Hub.
- Open the connector settings page. Go to the Integration Hub from the Integrations menu and choose QuickBooks Online. The page shows connection status, sync switches, and the credential panel.
- Authorise with OAuth. Click Connect. You are redirected to Intuit to sign in and pick the company file. Biznsbook records the company you authorised and stores the credentials encrypted per tenant.
- Verify the connection. Use Test connection. Biznsbook performs one live read against the connected company and reports the result on screen, so you learn about a problem now rather than at month-end.
- Choose which directions are on. Sending documents out and syncing contacts are on by default. Accepting changes back into Biznsbook and importing items are opt-in, because they write into your data.
- Map ledger accounts and tax rates. Open account mapping and link each Biznsbook ledger account to its QuickBooks counterpart. Run the suggest pass first to match on account number or exact name, then resolve the rest by hand.
- Send one invoice and check it. Post a single sale invoice, confirm it appears once in QuickBooks with the right customer, lines, and tax, then review the Integration Hub execution log for the run.
- Watch the execution log for a week. Filter the log by connector and status. Failures carry the provider message, and connection problems also raise an item in the Attention Center.
Review results after the first full monthly cycle. Adjust roles, mappings, or approvals where the same exception repeats.
Screen-level flows live in the Help Center. This guide focuses on the business process; help articles cover click-by-click navigation.
Common mistakes to avoid
- Mistake 1: Access tokens are pasted manually and expire without warning. Repeating this each month usually shows up first in duplicate invoices or postings landing in the wrong ledger account.
- Mistake 2: No stored link between a local invoice and the record already created externally. Repeating this each month usually shows up first in duplicate invoices or postings landing in the wrong ledger account.
- Mistake 3: Ledger accounts and tax rates were never mapped, so postings land in a default account. Repeating this each month usually shows up first in duplicate invoices or postings landing in the wrong ledger account.
- Mistake 4: Failures are logged where nobody looks, instead of surfaced to the person who can fix them. Repeating this each month usually shows up first in duplicate invoices or postings landing in the wrong ledger account.
Track recurring exceptions in month-end notes; each should map to a control above.
Best practices that hold up as you scale
- Confirm the module and connector are available — The Integrations module must be licensed for your company, and a SiteAdmin must assign the QuickBooks connector to your tenant before it appears in your Integration Hub.
- Open the connector settings page — Go to the Integration Hub from the Integrations menu and choose QuickBooks Online.
- Authorise with OAuth — Click Connect.
- Verify the connection — Use Test connection.
- Choose which directions are on — Sending documents out and syncing contacts are on by default.
Send one invoice before you send a batch. An integration that survives a week of real trading volume with a clean execution log is one you can safely put on a schedule.
How Biznsbook supports this workflow
OAuth 2.0 connect is documented in Biznsbook Integrations / Accounting capabilities. Use it as part of a controlled finance process — posting, review, and period close — not as an isolated export. When Sales, Purchase, Inventory, Taxation, Expense, or Finance Management modules are enabled, related documents can post through the central accounting posting service with double-entry validation.
account mapping is documented in Biznsbook Integrations / Accounting capabilities. Use it as part of a controlled finance process — posting, review, and period close — not as an isolated export. When Sales, Purchase, Inventory, Taxation, Expense, or Finance Management modules are enabled, related documents can post through the central accounting posting service with double-entry validation.
execution logging is documented in Biznsbook Integrations / Accounting capabilities. Use it as part of a controlled finance process — posting, review, and period close — not as an isolated export. When Sales, Purchase, Inventory, Taxation, Expense, or Finance Management modules are enabled, related documents can post through the central accounting posting service with double-entry validation.
Four switches must all be on: the Integrations module licence, the connector assignment from SiteAdmin, the connector toggle on the settings page, and a completed OAuth connection. Sending documents out is on by default; anything that writes back into Biznsbook is opt-in.
Suggested implementation timeline
- Week 1: Document current process gaps and configure OAuth 2.0 connect with finance owner sign-off.
- Weeks 2–3: Pilot on one month or one entity; post all test transactions through Biznsbook; freeze parallel spreadsheet journals.
- Week 4: Run first trial balance or report tie-out; fix mapping and permission issues.
- Month 2–3: Roll out to full team; add approvals and period close cadence from this guide.
- Ongoing: Monthly review using what to check before you trust the connection and leadership dashboard.
Metrics to track monthly
- Invoices synced versus invoices posted in the period
- Duplicate external records created (target: zero)
- Unmapped ledger accounts remaining
- Failed connector runs in the execution log per week
- Open sync conflicts awaiting a decision
Start with three metrics; trend direction matters more than a single point-in-time snapshot.
Spreadsheet / manual books vs integrated ERP
Compare typical manual finance work with Biznsbook OAuth 2.0 connect and related capabilities.
| Capability | Manual / Spreadsheet | Biznsbook |
|---|---|---|
| Authorisation | ❌ Pasted access token | ✅ OAuth 2.0 with automatic renewal |
| Token expiry | ❌ Silent disconnection | ✅ Refreshed in the background before it expires |
| Duplicate protection | ❌ Retry can post twice | ✅ One external record per document |
| Ledger accuracy | ❌ Everything to a default account | ✅ Mapped account per posting |
| Tax treatment | ❌ Assumed or omitted | ✅ Mapped tax rate per line |
| Failure visibility | ❌ Buried in logs | ✅ Execution log plus Attention Center |
What to check before you trust the connection
Send one invoice, not a batch. Confirm the customer, the line detail, the tax, and the document number all match what Biznsbook shows, and confirm it appears exactly once. Then leave the execution log open for a few days of normal trading. A connection that survives a week of real volume without an unexplained failure is one you can schedule.
Document this in your finance SOP and revisit each quarter as transaction volume or entity structure changes.
Frequently asked questions
Do I need to paste a QuickBooks access token into Biznsbook?
No. Connecting uses OAuth 2.0. You authorise once with Intuit and Biznsbook renews access automatically in the background, so there is nothing to copy, store, or replace by hand.
What happens when the access token expires mid-sync?
Access is renewed automatically before it lapses. If the authorisation itself is revoked or expires, syncing stops and Biznsbook raises an Attention Center item telling you to reconnect rather than retrying silently.
Can the same invoice be sent to QuickBooks twice?
No. Biznsbook stores the link between the local invoice and the record QuickBooks created. An invoice already sent is recognised and skipped, so retries and scheduled runs cannot duplicate it.
Is the QuickBooks two-way sync production ready?
Connecting is supported. Two-way sync is Beta: outbound invoices, contacts, payments and inbound accounts, tax rates and payment status all work, but verify them against your own sandbox company before relying on the results.
Will Biznsbook change my QuickBooks chart of accounts?
No. The chart of accounts and tax rates are read inbound only, so you can map them. Biznsbook never creates or edits accounts in QuickBooks, and never deletes anything there automatically.
Who can connect the integration?
A company administrator with permission to manage company settings, on a tenant where the Integrations module is licensed and a SiteAdmin has assigned the QuickBooks connector.
How this differs by industry
Retail
Retailers posting high invoice volume benefit most from the duplicate protection, because a retry storm during a busy trading day is exactly when double-posting would otherwise happen.
Wholesale & distribution
Wholesale finance teams get customer records matched on email or exact name rather than merged on a near match, which keeps credit control against the right account.
Manufacturing
Manufacturers with a separate bookkeeper can keep production and inventory in Biznsbook while the accountant continues working in QuickBooks against the same invoice numbers.