QuickBooks — A Small Ledger with a Real API

QuickBooks is one of the most widely used accounting systems in the English-speaking market, and it earned that position by solving a problem nobody else took seriously. Intuit built a double-entry ledger a founder could operate without an accounting qualification, wrapped it in bank feeds that reconcile themselves most of the time, and opened an app marketplace deep enough that most small businesses never need a custom integration. What tends to happen next is narrower than “outgrowing QuickBooks”: the bookkeeping stays adequate, and the questions being asked of it stop fitting on a report screen.

At a glance

What QuickBooks is

QuickBooks is Intuit’s accounting software: general ledger, sales invoicing, bills and payments, bank feeds, VAT or sales tax, and — from the Plus tier upward — inventory, budgets and project profitability. Intuit’s own term is accounting software rather than ERP, and that is the honest description. There is no manufacturing module, no warehouse management, no MRP. What QuickBooks does instead is make correct bookkeeping achievable by someone whose job is not bookkeeping, and it has done that for longer and for more companies than anything else in this series.

The bank feed deserves specific credit, because it is the feature that changed the working week for a generation of small companies. Transactions arrive automatically, rules categorise the recurring ones, and the reconciliation that used to consume a Friday becomes a review. Around it Intuit built a deep app marketplace and a developer platform with a documented REST API and webhooks — a more open posture than several systems marketed at larger companies. The result is a ledger that stays current with very little effort, which matters more to a reporting layer than any feature list.

The trade is deliberate. Intuit optimised for a company that can be described on one screen: one entity, one set of books, a chart of accounts small enough to scroll. The 250-account ceiling below Advanced and the two analytical dimensions follow from that.

The two product lines, and what each means for your data

QuickBooks Online and QuickBooks Desktop share a name, a vendor and very little else. For anyone who has to read the data they are separate problems, and which one you have determines the approach.

QuickBooks Online is the product Intuit is building. Two tier boundaries matter most: class and location tracking, project profitability, inventory and budgets all begin at Plus, and usage limits are removed — unlimited accounts, classes and locations, twelve custom fields per form — only at Advanced.

QuickBooks Desktop is a different commitment now. In the United States, Intuit stopped selling new subscriptions to Pro Plus, Premier Plus and Mac Plus on 30 September 2024, while existing subscribers can continue to renew and receive updates, and Desktop Enterprise is still sold. In the UK and Ireland the question is already settled: all Desktop services ended on 30 June 2023, HMRC stopped accepting Making Tax Digital VAT submissions from it in April 2024, and a UK entity holding a perpetual licence can open its file but cannot file with it. Intuit rewrites the policy each cycle rather than publishing a general rule, so the current position lives on its Desktop discontinuation support hub .

Neither column is a deficiency. A multitenant service cannot hand out database logins and keep its performance commitments to every other tenant, which is why the API exists and why it is governed. A desktop file is fast, private and entirely yours, which is why it cannot be queried from elsewhere. Both are coherent; they need different work.

Who QuickBooks fits

The company that wants correct books without an accounting department. One entity, a bookkeeper or an outsourced accountant, bank feeds doing most of the categorisation. This is what QuickBooks was built for and it remains the best answer for a great many businesses.

Service businesses inside the project ceilings. Projects on Plus and Advanced carry income and cost per project, with profitability, unbilled time and — on Advanced — estimates against actuals, which for an agency or a small contractor is often the whole of what job costing needs to be.

Product businesses that fit the stock model. Plus carries stock, and Desktop Enterprise carries considerably more. Where that depth is genuinely needed and the company is American, Enterprise remains a serious product.

The UK, US or Irish entity inside a European group. This is the profile we meet most often. Intuit ships no Slovak, Czech or Polish edition — those markets route to the Global version, which handles multi-currency and user-defined tax rates but carries no local statutory filing and no payroll. So QuickBooks in a CEE-centred group is almost never the group’s ledger. It is the UK subsidiary, the US sales company, the Irish holding entity, sitting beside a POHODA or an Omega in the operating businesses. Each of those choices was locally correct.

Groups that grew sideways. QuickBooks Online in the entity founded last year, something else in the one acquired before that, a spreadsheet holding the group view together. Nobody chose this shape; it accumulated, one reasonable decision at a time. It is the context in which QuickBooks most often reaches us.

What QuickBooks holds — and why it is good material

A well-kept QuickBooks file is better raw material than its reputation suggests. Because the bank feed drives categorisation, the ledger tends to be current rather than reconstructed at quarter end, and currency is worth more to a reporting layer than sophistication. Transactions carry their customer, vendor, item, class, location and project. The customer list is hierarchical — sub-customers nest four levels below the parent, which is how jobs and sites were modelled long before Projects existed.

The dimension model is the part to understand properly, because it is where profitability analysis either happens or does not. QuickBooks Online gives two analytical axes, both from Plus upward. Class can be applied per transaction or per line — a genuine choice, set once in company settings — and nests five levels deep. Location applies to the transaction only, never the line, and can be relabelled to whichever word your business uses, from a short list of labels including department, division, property, store and territory. Companies typically spend one axis on cost centre and the other on region. Two documented facts shape everything built on them: on Plus the two share one cap of forty combined, which Advanced removes; and custom fields, which look like a third axis, are not one — “Can I create a P&L report by custom field? No. This capability doesn’t exist.”

And the data quality is usually workable. Against what we more often meet — half-migrated spreadsheets, a decade of manual journals, an ERP where nobody has filled a dimension in years — a QuickBooks file that reconciles weekly is a strong start.

What sits outside QuickBooks’ scope

QuickBooks is scoped to keeping one company’s books correctly. Three things sit outside that scope, and each boundary was drawn deliberately.

The group view. One QuickBooks Online company is one legal entity, and Intuit is unambiguous on both halves of that: “Each company you create requires its own separate paid subscription”, and “The ability to merge two company data files into one company is currently not available in QuickBooks Online.” Companies can share a sign-in; their data does not mix. The partial routes Intuit does offer are in the FAQ below. For a simple statutory consolidation of entities whose charts already match, they often hold. For a group view people interrogate, they are the wrong shape.

The view across systems. Whether Shopify revenue matches the ledger, whether the payroll run matches headcount in the HR system, whether the pipeline squares with invoiced work. This is worth saying plainly: no ERP does this. Not QuickBooks, not Business Central, not SAP. Cross-system truth is a layer above every transaction system, which is the point we make at more length here .

The management view, held somewhere durable. Intuit’s reporting is more capable than it is given credit for, particularly on Advanced. It runs out in the same place every time: reports are scoped to one company, the dimensionality available to them is two axes, definitions live inside the product rather than somewhere versioned, and Intuit publishes no warehouse, no ODBC route and no first-party connector for QuickBooks Online. None of that is a data model a dashboard or an AI assistant can query across a group.

None of this is a reason to change system. It is a reason to add a layer.

How we elevate it

We connect QuickBooks in both lines, in single entities and in multi-system groups.

Getting the data out depends on which line you have, and being precise about it is most of the job. For QuickBooks Online the route is the Accounting API and there is no second option: an OAuth 2.0 connection scoped to a realm — one realm, one company, always — then paged query calls inside Intuit’s budget of 500 requests per minute and ten concurrent. One design decision saves trouble later. Querying JournalEntry returns manually entered journals only; the postings produced by every invoice, bill and payment are not JournalEntry objects, so a general ledger rebuilt that way is quietly incomplete. We take the ledger from the GeneralLedger and TrialBalance report endpoints, tie it back to the transaction objects for detail, and run incrementally against Change Data Capture thereafter. For QuickBooks Desktop, the file is proprietary and reading it directly is neither supported nor advisable, so we work as Intuit documents: the Desktop SDK over qbXML through the Web Connector, or the read-only ODBC driver. Read-only throughout, and nobody in finance notices a difference.

What happens next is the QuickBooks-specific work.

A management chart of accounts, held above the account ceiling

The statutory chart keeps doing its job. We map it to a second structure built to answer management questions — revenue by what you actually sell, cost by what you actually control, margin at the level you actually decide. In QuickBooks this earns its keep immediately, because every tier below Advanced caps the chart at 250 accounts, and the usual response to that cap is a chart compressed until it no longer describes the business. Holding the management structure above means the QuickBooks chart stays small and clean, while the reporting hierarchy gets as many levels as the business needs. Mapped once, versioned, owned by a named person, reviewed at each close. The design problem underneath: chart of accounts architecture .

Two dimensions, extended into as many as the business has

Two axes are enough right up to the moment someone asks for product by channel by region — at which point the third question has nowhere to go, and on Plus the forty-item cap has usually been reached long before that. We flatten class and location onto every ledger row, resolving the class hierarchy so a five-level nest reports at any level. We rebuild line-level attribution for location, which QuickBooks holds only on the transaction header, correcting it against customer, item and project where a transaction genuinely spans two. And we add the dimensions QuickBooks was never asked to hold — channel, brand, product family, market — derived from the item, the customer hierarchy and the systems either side of the ledger.

One view across companies, currencies and systems

Each QuickBooks company becomes one entity in a common model — beside another QuickBooks company, a POHODA database, a Business Central environment, a Xero file, an e-commerce platform or a payroll export, all producing the same standardised output. Group reporting in any currency with currency translation applied consistently, reconciliation across systems, and drill-down from a consolidated total back to the QuickBooks transaction behind it. Two QuickBooks specifics matter here. Charts of accounts do not have to match, which is the condition Intuit’s own multi-company routes impose. And home currency cannot be changed once multi-currency is on, so an entity reporting in the wrong currency is a mapping decision above the ledger.

This is routine rather than aspirational: we work with 70+ companies across 11 countries, on 12+ different ERP and accounting systems. See Group Reporting & Consolidation .

On the governed layer, the rest is the platform doing its standing job: daily reconciliation against the ledger so the close confirms rather than rebuilds, a semantic model that Power BI and AI can both query reliably , and your business context accumulating so answers get sharper the longer it runs.

What becomes answerable

• Which customers are actually profitable, after delivery and service cost — not just gross margin on the invoice?
• What is group EBITDA in one currency, when the UK company is on QuickBooks and two others are not?
• What did that project cost against what we quoted, while it is still running?
• Why did overhead move this month, ranked by the lines that moved most — against budget and against last year?
• What does margin look like by product and channel and region at once, rather than by whichever two we gave class and location to?

Every one is answered from data QuickBooks is already holding. What was missing was the structure to ask.

What it takes, and what does not change

Connection in days. First reports in the first week. For a single-entity QuickBooks client, the connection is a read-only login and the first governed reports follow inside a week. A full build — management chart of accounts, dimension repair, consolidation across several entities, the reporting suite — runs in phases over the following months. The distinction matters, and we would rather be precise about it than promise a finished model in a fortnight.

What we need from you: an NDA, read-only access, and a conversation about what the numbers should mean.

What does not change: QuickBooks stays your system of record. Your accountant keeps working the way they work. No migration, no data cleanse project, no retraining, nothing written back.

Read-only access throughout. Your data stays in an EU-hosted Azure environment, aligned with ISO 27001 and GDPR, governed by you.

When QuickBooks is eventually replaced

Some companies stay on QuickBooks indefinitely and are right to. Others move — to Xero for a like-for-like change, to Business Central or NetSuite when operations outgrow the ledger, or to Intuit Enterprise Suite where every entity is American.

In each of those directions the same thing holds: because the governed layer sits above the ERP, only the connection changes. The data model, the reports and the consolidation logic stay as they are. Clients who built the layer first find the migration measurably easier, because they can prove the new system’s numbers against the old from day one.

This is not a theoretical claim. When JING Tea replaced its operational stack, the reporting layer carried through the change unaltered — the systems underneath moved, the numbers and the reports did not.

QuickBooks in the regional context

QuickBooks is one of several capable systems in the estates we work in, and in a Central European group it is usually one entity rather than the standard. Each has its own article in the series .

From a data-layer perspective the choice matters less than it appears. Each becomes an entity in the same governed model, which means the ledger decision can be made on operational fit rather than on reporting fear.

Frequently asked questions

Do we need to replace QuickBooks to get proper management reporting? No, and we would usually advise against it. Keep QuickBooks for what it does well — clean transaction capture, bank feeds that keep the ledger current, an interface your team already knows — and build the reporting layer above it. Replacing a working ledger to solve a reporting problem is an expensive way to solve the wrong problem.

Is Onetribe a replacement for QuickBooks? No. QuickBooks remains your system of record and your team keeps using it exactly as they do now. We read from it, never write to it. If you change ERP later, the reporting layer stays.

Is QuickBooks an ERP or accounting software? Accounting software, and Intuit says so itself. It carries the ledger, receivables, payables, banking, tax, and from Plus upward inventory, budgets and projects — but no manufacturing, no warehouse management, no MRP. That is why a QuickBooks company with real operational complexity runs an operational system beside it.

What database does QuickBooks use, and can we read it directly? This depends entirely on the line. QuickBooks Online publishes no database and offers no customer database connection — the Accounting API is the documented read path, over OAuth 2.0, scoped to one realm, which is one company. QuickBooks Desktop keeps a proprietary company file (.QBW) on your own machine, read through the Desktop SDK over qbXML or the read-only ODBC driver, both of which need QuickBooks running.

Can QuickBooks connect to Power BI? Yes, through the API. Intuit publishes no first-party Power BI connector, no ODBC route and no warehouse for QuickBooks Online, so anything built reads live against the Accounting API — 500 requests per minute per company, ten concurrent, a thousand rows per page. That is generous for an application and thin for a report refreshing for several users at once. The durable pattern is to extract once on a schedule into a governed model and point BI reporting at the model rather than the ledger.

Can QuickBooks consolidate several companies? Not within QuickBooks itself. One company is one legal entity with its own subscription, and Intuit documents that two companies cannot be merged. Partial routes exist: Spreadsheet Sync on Advanced and Desktop Enterprise both combine reports into Excel across companies whose charts of accounts match by name, type and level, and Intuit Enterprise Suite consolidates properly, with intercompany eliminations, for US entities only. None gives you a group figure you can drill from.

Does QuickBooks have an API? Yes, and it is one of the better ones in this segment — the Accounting API v3, REST and JSON over OAuth 2.0, with a SQL-like query endpoint, a batch endpoint, report endpoints including GeneralLedger and TrialBalance, Change Data Capture, and webhooks. Throughput is governed at 500 requests per minute per realm, ten concurrent and a thousand rows per page. Every connection is scoped to one company, so a five-company group is five authorisations, five token pairs and five extraction schedules.

Is Intuit’s own reporting enough? For a single company, often yes — and worth exhausting before adding anything. Advanced adds a Custom Report Builder, two-way Spreadsheet Sync into Excel, nine dashboards and a KPI scorecard of 80-plus measures. It runs out in the same place: one company at a time, two analytical axes, and no route for another tool to query the result. If QuickBooks is your only system and one company is your whole business, start there and stay as long as it holds.

Official QuickBooks resources

• QuickBooks — Intuit
• QuickBooks Online plans and pricing
• Intuit Developer — QuickBooks Online Accounting API
• QuickBooks Desktop SDK and the Web Connector
• Usage limits in QuickBooks Online
• ODBC driver for QuickBooks Desktop

Onetribe is not an Intuit partner or reseller. We build the governed data layer above your ERP, whichever ERP that is.

Next steps

• Every source system we connect — the series hub, with the full matrix
• How we consolidate any combination of ERPs — group reporting
• Why your ERP doesn’t govern your data — the cross-system layer
• Discuss your QuickBooks estate — free assessment