Nine questions to ask before buying any QuickBooks integration

“Does it integrate with QuickBooks?” is not a question. Every vendor says yes, and the answers behind that yes differ enormously — from a full two-way sync posting proper accounting objects, to a nightly job that dumps journal entries and hopes for the best.

The difference doesn’t show up in a demo. It shows up at month-end, three months later, when the reports don’t work and nobody can say why.

These are the nine questions that separate them. Each one comes with why it matters and what a good answer sounds like, because the follow-up matters more than the question.

1. Does it post native QuickBooks objects, or journal entries?

Why it matters more than anything else on this list.

QuickBooks has real object types — invoices, bills, purchase orders, payments, deposits. Its reporting is built on them. Accounts receivable aging works because invoices are invoices. Sales by customer works because sales are sales.

A journal entry moves the right money to the right account and carries none of that structure. An integration that posts journal entries instead of native objects produces a general ledger that balances and reports that don’t work. Your AR aging is empty. Sales by product shows nothing. The numbers are right and the reporting is gone.

Journal-entry integrations exist because they’re dramatically easier to build. One object type, no relationship handling, no edge cases.

2. Is the sync one-way or two-way — and in which direction?

One-way is simpler and often correct. It’s also silently incomplete the moment anyone changes something on the other side.

The specific failure: an integration pushes invoices into QuickBooks. Someone edits an invoice in QuickBooks. The source system never knows. Now two systems disagree and neither is flagged as wrong.

Two-way sync solves that and introduces conflict resolution as a new problem — if a record changes in both places, which wins?

Ask which direction, for which objects, and what happens on conflict. “Two-way” without specifics usually means invoices go one way and payment status comes back, which is not the same thing.

3. Order-level or summary-level?

Mostly relevant to e-commerce and POS, and it’s a genuine trade-off rather than a right answer.

Summary-level posts a daily or per-settlement total. Clean books, small file, easy reconciliation. You lose per-transaction detail inside QuickBooks.

Order-level posts every transaction. Full detail, and for a high-volume seller it loads QuickBooks with records the business will never query there — because the order detail already lives in the sales platform.

The right answer depends on whether QuickBooks is being used as an order management system. Usually it isn’t, and summary-level is correct. Ask which the connector does, and whether it’s configurable.

Related: Why your Shopify and Amazon payouts don’t reconcile

4. What happens when a sync fails halfway through?

The question vendors are least prepared for, and the one that tells you most about engineering quality.

A batch of two hundred transactions. Number 147 fails validation. What now?

• Does the whole batch roll back, or are 1–146 already in the books?
• Does it retry, and does the retry re-post the ones that succeeded?
• Does anyone find out, or does it fail into a log nobody reads?
• Can you see which records didn’t make it, or do you reconcile to discover it?

It happens. Rate limits alone guarantee it — see the technical section below.

5. Who else is already posting these transactions?

Not a question for the vendor. A question about the client file, and the single most common cause of duplicates.

Before connecting anything, establish what’s already writing to QuickBooks: the bank feed, a payment processor, another app, someone manually. A new connector posting transactions the bank feed also imports produces duplicated income or expenses that look entirely legitimate.

Ask this before every connection, not once. The answer changes as clients add tools.

Related: Sync is not accuracy

6. Will it modify the chart of accounts?

Frequently overlooked, occasionally serious.

Connecting apps can cause QuickBooks to add, rename or remove accounts to accommodate how the external system maps its data — sometimes without a clear notification. The connector follows its own mapping rules and the chart of accounts adjusts to fit.

That’s a reporting-level change made by software with no view of what the client needs to report.

Ask whether it creates accounts, whether mapping is configurable to an existing chart, and whether it will modify accounts that already exist. Then screenshot the chart of accounts before connecting, so you can tell.

7. What’s the release state, and whose revenue depends on it?

Two questions that answer the same thing: how likely is this to still work in two years?

Release state. Beta after several years isn’t a stage, it’s a signal. Microsoft’s Power BI connector for QuickBooks spent its entire life in Beta and was deprecated from it in August 2025, with no replacement.

Whose revenue. A connector that’s central to the vendor’s product gets maintained. One that’s a checkbox on a feature list competes with everything else for engineering time. A payments platform will fix its QuickBooks sync because reconciliation is what it sells. A BI tool may not.

Ask about the deprecation policy and the notice period. A paid vendor should be able to answer. If nobody can, you’ve learned something.

Related: When the native connector isn’t enough

8. What are the volume limits, and will this client approach them?

Where the technical constraints become a business question.

QuickBooks Online’s API enforces throttle limits per company file. Widely cited figures:

Exceeding them returns HTTP 429, Too Many Requests, with error code 003001. Sandbox and production share the same limits.

Verify these against Intuit’s own developer documentation rather than any secondary source, including this one. Published figures disagree — concurrent requests appear as both 10 and 40 depending on where you look, and the batch limit as both 40 and 120 per minute. Limits also change.

Why a buyer should care about numbers that look like a developer’s problem: 500 requests per minute per company sounds generous until a large client’s initial sync paginates through tens of thousands of invoices. A well-built connector queues, batches and backs off. A poorly built one hits 429s and fails partway — which is question 4 arriving in practice.

9. What’s the exit, and what happens to the history?

Ask before you sign, because the answer is different then.

• If you disconnect, does anything already posted stay in QuickBooks?
• Can historical data be exported, in what format, and how quickly?
• Does the connector hold data of its own that doesn’t exist elsewhere?
• Is there a re-sync on reconnection, and will it duplicate what’s already there? (Reconnection re-import is a documented cause of duplicates.)

The cost question nobody asks

Worth separating out, because it’s genuinely under-known and it’s a pricing question rather than a technical one.

Intuit meters its API asymmetrically. Writing data in is treated differently from reading data out. Operations that create records — invoices, bills, customers — fall into one category. Operations that read: querying data, fetching reports, pulling account lists, fall into another that is metered against a monthly allotment, with a substantial free tier before charges begin.

The practical implication: a reporting or analytics integration consumes metered capacity in a way a transaction-posting integration doesn’t. A dashboard refreshing hourly across a book of clients is doing a lot of reading.

That cost sits with whoever built the app, not with you directly — but it shapes their pricing, their refresh frequency, and how enthusiastic they are about your five-minute sync interval. It’s worth asking a vendor how their pricing responds to read volume, because the answer explains constraints that otherwise look arbitrary.

Verify the current thresholds with Intuit’s developer documentation; the tiers change.

The short version

Frequently asked questions