84 QuickBooks Desktop Reports Over One REST API: A Field Guide
- quickbooks desktop reports api
- quickbooks profit and loss api
- quickbooks balance sheet api desktop
- quickbooks report filters api

Quick answers
How many reports can I pull from QuickBooks Desktop over the API? 84, split into QBO-named reports translated from Desktop's report engine, Desktop extension reports under their Desktop names, and one derived CashFlow.
What do I get if I send no dates? Fiscal year-to-date, the same default behavior as the QuickBooks Online reports API.
Which filters are supported? start_date/end_date, date_macro, accounting_method, summarize_column_by, columns, and customer/vendor/item/class/account filters — though not every report accepts every one.
Which reports have hard edges? MissingChecks requires an account, 1099Detail rejects every filter, and Advanced Inventory reports return REPORT_FEATURE_UNAVAILABLE on files without that feature enabled.
ExampleCo's app has a dashboard. Three tiles: this month's P&L, a receivables aging, and an inventory value number that Pat Owner checks every Monday. Against QuickBooks Online it's three GET /v3/company/{realmId}/reports/... calls and some chart code. Then a prospect shows up on Desktop Enterprise, and somebody asks whether the dashboard still works.
The answer depends on which reports you call and how picky you are about the shape of the response. This post is a walk through the report surface TenkeyBridge exposes from a Desktop company file — what's there, how it's grouped, which parameters do what, and the specific places where a request that works against QBO comes back differently or not at all. It's a tour, not a tutorial. The reports guide has the full list; this is the map you read first.
Three groups, one endpoint shape
All 84 live under the same path pattern you already use:
GET /v3/company/{realmId}/reports/{ReportName}
What differs is where the report comes from.
Group one: QBO-named reports, translated. ProfitAndLoss, BalanceSheet, TrialBalance, GeneralLedger, AgedReceivables, AgedPayables, CustomerIncome, VendorExpenses, InventoryValuationSummary, and the rest of the familiar set. These keep their QuickBooks Online names and return the QBO report JSON envelope — Header, Columns, Rows, Rows.Row[].ColData[]. Under the hood they're Desktop report requests; the translation happens on the way out. If your chart code already walks the QBO row tree, it walks these.
Group two: Desktop extension reports, under Desktop names. Desktop's report engine has reports QBO never had, and inventing QBO-style names for them would be a lie about where they came from. So they keep the Desktop name: OpenInvoices, BalanceSheetDetail, MissingChecks, TransactionListWithSplits, UnpaidBillsDetail, and friends. Same endpoint shape, same JSON envelope, non-QBO name. Code that only knows QBO report names will never call these by accident — which is the point.
Group three: one derived report. CashFlow is computed, not fetched. Desktop's statement of cash flows doesn't come back in a form that maps cleanly to the QBO CashFlow response, so it's derived from underlying data. Treat it as a convenience, not as a byte-for-byte match for what Desktop prints on paper. If your use case is "a CFO reconciles this against the printed statement," pull the components and do your own math.
The parameter surface
The query parameters are the QBO ones, and they behave the way you'd expect — with the caveat that support is per-report, not global.
start_date/end_date— ISO dates,YYYY-MM-DD.date_macro— named ranges likeThis Fiscal Year-to-date,Last Month. Mutually exclusive with explicit dates in practice; send one or the other.accounting_method—CashorAccrual. Applies to the reports where Desktop itself offers the toggle.summarize_column_by—Month,Quarter,Year,Customers,Classes, and so on. This is the one that turns a single-column P&L into a trend grid, and it's where most dashboards get their value.columns— which columns come back on detail reports.- Entity filters —
customer,vendor,item,class,account. Values are IDs, the same IDs you get back from the corresponding entity queries.
Omit the dates and you get fiscal year-to-date
This matches QBO. A bare GET /v3/company/{realmId}/reports/ProfitAndLoss returns the current fiscal year to date, using the fiscal year start configured in the company file — not the calendar year, unless those happen to agree. ExampleCo closes its books in September; a dateless P&L in October returns about a month of data, which looks like a bug to anyone who assumed January.
Send dates. Dashboards that render a number without a visible period are a support ticket waiting to be filed.
Five reports a typical app pulls
Pick five and the dashboard is usually done. Here's one GET each — abbreviated, headers omitted, assume Authorization: Bearer ... on all of them.
1. Profit and loss, by month
The QuickBooks profit and loss API call most apps start with. summarize_column_by=Month gives you a column per month across the range, which is what a trend chart wants.
GET /v3/company/{realmId}/reports/ProfitAndLoss
?start_date=2026-01-01
&end_date=2026-09-30
&accounting_method=Accrual
&summarize_column_by=Month
2. Balance sheet, as of a date
For a QuickBooks balance sheet on Desktop, only end_date carries meaning — it's a point-in-time report. Sending a start_date is harmless but doesn't narrow anything.
GET /v3/company/{realmId}/reports/BalanceSheet
?end_date=2026-09-30
&accounting_method=Accrual
3. Aged receivables
Collections screens live on this one. Filter by customer when you're drilling into a single account.
GET /v3/company/{realmId}/reports/AgedReceivables
?end_date=2026-09-30
&customer=112
4. Open invoices (Desktop extension)
OpenInvoices is a Desktop-native report with no QBO twin. It's a per-invoice list of what's outstanding, which is often closer to what a collections UI needs than the bucketed aging summary.
GET /v3/company/{realmId}/reports/OpenInvoices
?end_date=2026-09-30
5. Transaction list with splits (Desktop extension)
When somebody needs to see both sides of every entry — reconciliation tooling, audit views, anything that cares about the distribution lines — TransactionListWithSplits is the one. It's verbose. Date-bound it tightly.
GET /v3/company/{realmId}/reports/TransactionListWithSplits
?start_date=2026-09-01
&end_date=2026-09-30
The edges
Three of these come up often enough to be worth memorizing. The rest are in the compatibility matrix.
MissingChecks requires an account
MissingChecks finds gaps in check number sequences. Desktop's report engine runs it against one bank account at a time, and there's no sensible "all accounts" semantic — a gap in account A is not a gap in account B. So account is required. Omit it and you get a fault, not an empty report.
GET /v3/company/{realmId}/reports/MissingChecks?account=84
Fetch your bank accounts first, then loop. If your UI offers a "run for all accounts" button, that's N requests on your side, not one.
1099Detail refuses every filter
1099Detail takes no filters at all. Not customer, not vendor, not account, not summarize_column_by. The report is what the report is; it comes back whole, and you filter client-side if you need a subset. This is a deliberate refusal rather than silent ignoring — sending a filter gets you an error, so a request that looks like it worked did work the way you asked.
Silently-ignored parameters are the worse failure mode. A 400 you can see in the logs beats a number that's quietly wrong, which is the same reasoning behind how Desktop faults get mapped to QBO-shaped errors generally.
Advanced Inventory reports need Advanced Inventory
Enterprise with Advanced Inventory enabled has reports that other files don't: lot and serial tracking, bin-level quantities, site-specific valuation. Those endpoints exist in the API surface regardless, because you don't know what a given file supports until you ask. On a file without the feature, they return:
{
"Fault": {
"Error": [{
"code": "REPORT_FEATURE_UNAVAILABLE",
"Message": "Report requires a feature not enabled in this company file",
"Detail": "Advanced Inventory is not enabled"
}],
"type": "ValidationFault"
}
}
Handle it as a capability check, not an outage. The right UI response is hiding the tile, not retrying — unlike the transient cases where a 503 or 504 means the request is worth another attempt.
What reports are not good at
Two things worth saying plainly.
Reports are not a sync mechanism. It's tempting to pull TransactionListWithSplits nightly and diff it. Don't. Reports are formatted output — row trees with summary rows, group headers, and totals mixed in with data rows — and the formatting changes with parameters. For incremental sync, use change data capture, with its 30-day window and 1,000-object cap accounted for. Reports are for showing humans numbers.
Reports are slower than entity queries. Desktop computes them against the company file, and a wide GeneralLedger across a full fiscal year on a large file takes real time. Cache aggressively on your side, give the user a visible "as of" timestamp, and don't put an uncached multi-year report behind a page load that a browser will time out on.
Where the row tree gets you
One structural note, since it's the thing that most often breaks ported chart code. The QBO report envelope nests: a Rows object contains Row[], each Row may have ColData[] (a data row), or a Header/Rows/Summary triple (a group), and groups nest arbitrarily deep. Desktop reports translated into this envelope nest too, and the depth depends on the report and the summarize_column_by you sent.
If your QBO code already handles that recursion, it handles these. If your QBO code was written against one report and hardcodes two levels, it'll break on Desktop for the same reason it would break on QBO the first time someone enabled subaccounts. Write the recursive walk once.
The short version
84 reports, one endpoint shape, QBO parameter names. Familiar reports keep their QBO names and envelope. Desktop-only reports keep their Desktop names so you know what you're getting. CashFlow is derived and should be treated as such. Dates default to fiscal year-to-date. Three reports have specific requirements worth coding around up front.
If you're evaluating whether an existing QBO integration can serve Desktop customers, reports are usually one of the easier surfaces — the parameter vocabulary ports almost unchanged. The checklist for pointing a QBO integration at Desktop covers the surfaces where the port takes more work.
FAQ
Which reports can I read from QuickBooks Desktop?
84 total: the QBO-named set (ProfitAndLoss, BalanceSheet, TrialBalance, GeneralLedger, agings, and more), a set of Desktop extension reports under their Desktop names (OpenInvoices, BalanceSheetDetail, MissingChecks, TransactionListWithSplits, and others), and a derived CashFlow. The reports guide lists all of them by name.
What period do I get if I send no dates?
Fiscal year-to-date, based on the fiscal year start in the company file — matching QBO's default. If the company's fiscal year doesn't start in January, a dateless report in March returns a different range than a calendar-year assumption would suggest. Send explicit dates whenever the period matters to the user.
Which reports need extra parameters?
MissingChecks requires an account parameter and errors without one. Point-in-time reports like BalanceSheet only use end_date. And 1099Detail goes the other way — it rejects every filter you send, so pass none and filter client-side.
Can I request a report that doesn't exist in QuickBooks Online?
Yes — that's what the Desktop extension group is for. Those reports use their Desktop names rather than invented QBO-style ones, so there's no ambiguity about whether a given endpoint has a QBO counterpart.
Do report parameters behave identically to the QuickBooks Online reports API?
The names and value vocabularies match, but support is per-report rather than universal — a parameter valid on one report may be rejected on another. Check the per-report notes in the docs before assuming a filter applies, and treat a 400 as information rather than a bug.
How do I test report calls without a real company file?
The sandbox serves a seeded Desktop company file over the same API, so you can exercise report shapes, parameter combinations, and error paths before you touch a customer's data. If you want to see the row tree for yourself, the quickstart gets you a token and a ProfitAndLoss response in about five minutes.