How to Connect QuickBooks to Power BI

There is no native QuickBooks entry in Microsoft's current Power Query connector catalogue. To connect QuickBooks to Power BI reliably, choose one of three production routes:

1. Use a third-party QuickBooks connector for the quickest supported path.
2. Extract QuickBooks Online through its OAuth 2.0 API into a database or warehouse you control.
3. For QuickBooks Desktop, use an SDK, Web Connector or vendor bridge, with controlled exports reserved for one-off or low-frequency reporting.

The route is only half the job. Finance reporting is successful when the refresh is supportable, access is understood and every important total reconciles to QuickBooks.

Choose the route before writing Power Query

Do not start with a generic Web.Contents snippet copied into a PBIX file. QuickBooks Online uses Intuit OAuth 2.0. Microsoft says arbitrary services commonly need a custom connector for OAuth, and custom connectors must handle login, token refresh and Power BI Service refresh correctly. Microsoft also warns connector developers not to embed confidential client secrets that users can inspect. A server-side extractor or a reviewed connector creates a clearer security and support boundary.

If another company in the group uses Sage, review how to connect Sage to Power BI alongside this plan. Reconcile each source separately before mapping both companies to a shared chart of accounts.

A seven-step QuickBooks-to-Power-BI build

1. Inventory the source

Record whether each company uses QuickBooks Online or Desktop, its country edition, company identifier, home currency, reporting basis and available tracking fields. Treat each QuickBooks Online company as a separate connection identified by its realmId; do not assume one sign-in means one combined ledger.

2. Define the reports and controls first

Write down the decisions the model must support and the QuickBooks reports it must match. At minimum, agree:

• Cash or accrual basis.
• Reporting calendar and period-close rules.
• Home and reporting currencies.
• Treatment of classes, locations, customers and projects.
• Which Profit and Loss, Balance Sheet and A/R or A/P reports form the control totals.

This prevents a technically successful extraction from producing a finance model nobody trusts.

3. Choose and approve the connection

For a third-party connector, verify its Intuit authentication method, Power BI Service refresh support, history limits, multi-company model, data location, deletion process, schema-change handling, support response and full recurring price. Confirm whether it uses the official API or another mechanism.

For an owned extractor, register and test an Intuit app, keep tokens and client credentials outside the PBIX file, separate sandbox from production, and document revocation and reconnection. A Power Query custom connector must implement the OAuth and gateway or service-refresh behaviours it needs; a desktop-only proof does not establish production refresh.

4. Land source-shaped data

Preserve raw identifiers, timestamps, status fields, references and line-level amounts before applying reporting logic. Typical accounting entities include accounts, customers, vendors, invoices, bills, payments, credit memos, journal entries and purchases. Report endpoints can also return Profit and Loss, Balance Sheet and ageing output with parameters such as date range and accounting method.

Keep raw entity extracts separate from saved report-control extracts. They serve different purposes: entity data supports the analytical model, while the report output proves what QuickBooks calculated for the same period and basis.

5. Make extraction restartable

Intuit's query language uses pagination, and its API applies per-company request limits. A production extractor needs deterministic page traversal, retry with backoff, per-company watermarks, duplicate-safe loads and alerts for partial runs. Rotate refreshed OAuth tokens correctly and store the replacement atomically so two overlapping jobs cannot invalidate each other.

Use incremental extraction where it is supported, but schedule a periodic wider comparison. An incremental job can run successfully while missing a deletion, a late adjustment or a mapping change.

6. Build a finance model, not an API mirror

Turn source-shaped tables into a model with explicit dimensions for date, account, customer, vendor, company, class or location where available, and currency. Keep transaction facts at a documented grain. Separate operational dates, such as invoice and payment date, from the accounting period used in a report.

For multiple companies, preserve company as a first-class dimension and map each chart of accounts to a governed group structure. Do not combine similarly named accounts merely because their labels look alike.

7. Reconcile before publishing

Run a control pack for a closed period and retain it with the model:

Store the source report date, company, cash-or-accrual setting, currency, model result, difference, tolerance and reviewer decision. A green refresh icon is not a reconciliation.

The OAuth permission is not read-only

This is easy to get wrong. Intuit's current scope for QuickBooks Online accounting data is com.intuit.quickbooks.accounting. Its scopes documentation describes access by data category and does not list a separate read-only Accounting API scope. The Accounting API itself supports create and update operations as well as queries.

For a reporting-only integration:

• Restrict the implementation to query and report calls.
• Do not expose write operations in the extraction service.
• Store tokens in a managed secret store, not source code, a spreadsheet or PBIX parameters.
• Log company connections, token refresh failures and revocations without logging token values.
• Review the connector vendor's data retention and deletion controls.
• Revoke the connection promptly when the service is retired.

These controls make the application read-only by design. They do not turn the broad OAuth grant into a read-only permission, so describe the distinction honestly during approval.

QuickBooks Desktop is a separate architecture

QuickBooks Desktop does not use the QuickBooks Online REST API. Intuit provides a Desktop SDK and the QuickBooks Web Connector, which lets a local QuickBooks environment exchange requests with a web service. Third-party ODBC and sync products can provide another supported bridge.

That introduces operating dependencies which a cloud-only diagram can hide:

• The Windows host, company file and connector schedule must be available.
• Unattended access and service credentials need deliberate approval.
• A local database or file source normally needs a Power BI gateway for scheduled refresh.
• Desktop and connector upgrades need regression testing.
• Failed local syncs must stop the downstream model from presenting stale data as current.

If the requirement is quarterly or one-off analysis, a controlled export with a fixed naming convention, archive and reconciliation may be safer than pretending a fragile bridge is live integration. For repeated reporting, stage the bridge output in a database and let Power BI read the supported store.

Failure modes to test

• Cash versus accrual mismatch. The same period can produce different results; store the selected basis with the control.
• Voids, deletions, credits and late changes. Test how the extraction detects and represents each one.
• Entity data versus report output. A hand-built transaction calculation can differ from a QuickBooks report because parameters and accounting treatment differ.
• Pagination or throttling. A successful first page is not a complete extraction; fail the run if any page or company is missing.
• Token lifecycle. Test expiry, refresh, replacement-token storage, revocation and reconnection.
• Multiple companies. Keep realmId, currency and chart-of-accounts mapping explicit throughout.
• Desktop availability. Alert when the local bridge or gateway misses its expected run.
• Schema and API changes. Pin and test supported API behaviour, then monitor Intuit release notes.

Official implementation references

Checked on 22 August 2026:

• Microsoft's Power Query connector catalogue
• Microsoft's Web connector limitations
• Microsoft's Power Query authentication guidance
• Intuit's current OAuth scopes
• Intuit's API query and pagination guidance
• Intuit's QuickBooks Online Reports API guidance
• Intuit's batch and request-limit guidance
• Intuit's QuickBooks Web Connector guide

Decide the route with the control pack attached

A useful first conversation needs five facts: Online or Desktop, number of companies, cash or accrual basis, required history and refresh frequency, and the three reports that must reconcile. Bring those to a Trusted Numbers Review and we will document the lowest-maintenance route, security boundary, target model and test pack before a build. You can also review our UK Power BI consultancy, Power BI service, data integration service and published BI build pricing, or use the free two-minute reporting checklist to identify which parts of your reporting process need a closer look.