What we do
Tools
Industries
Department
How we workLet's talk →
Home/QODBC
QuickBooks ODBC Integration

QODBC: Getting QuickBooks Desktop Data into Excel, Access and Power BI

QODBC is an ODBC driver from FLEXquarters that lets Excel, Access, Power BI, Crystal Reports or SQL Server query a QuickBooks Desktop company file with SQL. If you're on Enterprise, you may already have a read-only version of it. Here's how to connect, and where it gets slow or stops working.

Which QODBC you need

QuickBooks Desktop Enterprise: a read-only ODBC driver, developed with FLEXquarters, is included. Read/write access costs extra.

Pro or Premier: neither includes one. You buy the QODBC driver from FLEXquarters, who also support it.

QuickBooks Online: that's a separate QODBC product sold as a monthly subscription. The steps below are for Desktop.

Either way, the driver runs on a Windows PC with QuickBooks Desktop installed. Reaching it from another machine or a server takes QRemote.

Connecting Excel to QuickBooks Desktop through QODBC

  1. 1

    Install the driver on the QuickBooks machine

    Install QODBC, or the ODBC driver that came with Enterprise, on a Windows PC where QuickBooks Desktop is installed. Recent QODBC versions install both 32-bit and 64-bit drivers, so you can match the program that will query it.

    Watch for: an older 32-bit-only install. A 64-bit Excel or Power BI won't see that data source at all.

  2. 2

    On Enterprise, create an ODBC user

    Intuit's ODBC setup needs its own login, separate from your QuickBooks user, even if you're the admin. It doesn't carry the same permissions, so only give it to people who already have QuickBooks access.

  3. 3

    Open Microsoft Query from Excel

    On Excel's Data tab, choose Microsoft Query (in recent versions it sits under Get Data, then From Other Sources) and pick the QuickBooks data source the driver created.

  4. 4

    Allow access in QuickBooks the first time

    The first connection from each program makes QuickBooks show an application certificate prompt. Switch to QuickBooks and allow it. Excel, Access and Crystal Reports each need their own approval.

    Watch for: the prompt hiding behind other windows. The query just looks frozen until someone answers it.

  5. 5

    Pick the tables and bring the data back

    Choose the tables you need (Customer, Invoice, InvoiceLine and so on), add a date filter, and return the result to a sheet. Refresh pulls it again from the company file.

Why QODBC is slow, stale or refusing to connect

The first query takes ages

How you'll know: A query on a big table, transaction lines especially, runs for minutes.

Fix: That's the QODBC Optimizer building its local cache. The first pass reads every record, and later ones fetch only what changed. Let it finish once, and filter by date rather than pulling every year.

Balances that lag behind QuickBooks

How you'll know: An account balance or on-hand quantity doesn't match what QuickBooks shows right now.

Fix: The Optimizer cache lives on one computer, so other users' latest changes may not be in it yet. Its setting for balances and quantities has a real-time mode: slower, but current.

Power BI or 64-bit Excel can't find the data source

How you'll know: The QuickBooks DSN doesn't appear in the list, or the connection fails straight away.

Fix: A 32-bit versus 64-bit mismatch. Use the 64-bit driver that ships with recent QODBC versions, or QRemote to bridge a 64-bit program to an older 32-bit install.

Works at your desk, fails on a schedule

How you'll know: A refresh runs fine by hand but fails from SQL Server, a web server or a scheduled service.

Fix: QuickBooks can't run as a Windows service, so FLEXquarters says service-based programs need QRemote to reach it. Plan any unattended refresh around that from the start.

Writes that fail or half-apply

How you'll know: An insert into an invoice or item table errors out, or lands with fields missing.

Fix: Writing needs the read/write edition, and even then some data is off-limits. For regular write-back, the SDK or Web Connector is the steadier route.

QODBC, or a proper integration?

QODBC fits

Reading Desktop data into reports

  • Excel and Access reports on customers, invoices, items and sales.
  • Power BI or Crystal Reports dashboards built on the company file.
  • One-off extracts for your accountant or an audit.
SDK or Web Connector fits

Writing to QuickBooks, or syncing another system

  • Orders from a web store or CRM created in QuickBooks every day.
  • Two-way sync where both systems must agree on every record.
  • Jobs that have to run unattended on a server overnight.

Read-only reporting is where ODBC earns its place. Once data has to flow into QuickBooks on its own, look at the QuickBooks Desktop API options and the Web Connector instead.

What this looks like in practice

Shopify retailer

Shopify to QuickBooks sync

A retailer's Shopify sales synced into QuickBooks as one number a day, and every month someone spent half a day working out why a payout didn't match. We rebuilt the sync to itemize by product category, use real product costs, and match each payout to the orders, fees and refunds behind it. The half-day reconciliation became a five-minute check.

Questions people ask

Is QODBC the same as an official QuickBooks API?

No. It's a third-party ODBC driver made by FLEXquarters that presents your company file as tables you can query with SQL. Intuit does ship a read-only version with Enterprise, developed with FLEXquarters, but QuickBooks Desktop's own integration route is the SDK (qbXML) and the Web Connector.

Can ODBC write data back into QuickBooks, or only read it?

The read/write edition can insert and update many tables, but writes are where it's least predictable. Intuit names payroll, multiple ship-to addresses and units of measure among the read/write driver's data limits. If you need the same writes every day, n-frames usually builds them on the SDK or Web Connector instead.

Why does our Power BI connection to QuickBooks keep failing?

Two usual causes. A bitness mismatch: 64-bit Power BI needs the 64-bit QODBC driver, or QRemote in front of an older 32-bit one. Or the refresh runs through a gateway service, and since QuickBooks can't run as a service, that path needs QRemote too. Copying the data into a database first avoids both problems.

Does QODBC work with QuickBooks Online?

There's a separate QODBC driver for QuickBooks Online, sold as a monthly subscription with read/write access. It talks to Intuit's online service rather than a company file, so the Desktop steps on this page don't apply.

Can I link QuickBooks tables in Microsoft Access or SQL Server?

Access can link or import QODBC tables like any other ODBC source. SQL Server can query it as a linked server, but it runs as a service, so it needs QRemote, and every query waits on QuickBooks. For regular reporting, copying the data into SQL Server on a schedule is far quicker.

Is the quote for QODBC work really free, with no obligation?

Yes. n-frames quotes what the report or sync involves and what it costs, and nothing commits you after that.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.