DeadlineScan
QuickBooks Reports API

QuickBooks Online reports look wrong since Sept 1, 2026

Columns landing in the wrong place. Blank cells where you used to read zeros. Account hierarchies at a different depth. A report that returns nothing at all, or is simply gone. The API is answering; the shape of the answer changed.

Find the call sites:
deadlinescan scan ./my-repo --json report.json

A call to a documented survivor is reported as a response-shape change to re-test; a call to a report name that is not among the survivors is reported as a gap with no equivalent call to migrate to. SDK references are flagged too, so you can check the pinned version — for the .NET, Node and Python SDKs a version bump, not a rewrite, is usually the fix for that half.

A finding count of zero means no affected call sites were FOUND — not that you're unaffected. Read that literally here: the QuickBooks rules have never been run against a real QuickBooks codebase. The five repositories in the published validation audit are all EWS, so zero QuickBooks findings across that corpus is evidence that the rules do not fire on unrelated code — not evidence that they fire correctly on yours.

Scan your code

Free, local, one command. Splits Reports API call sites the way the cutover does.

Get the scanner

Get the scanner: email [email protected] and you'll get the source and a Windows binary by reply — the public repository is being prepared.

Named in the documented set

Profit and Loss
Balance Sheet
Cash Flow
General Ledger
Trial Balance

Reported as dropped

Transaction Detail
Unpaid Bills
Invoice List
Customer Contact List

Check your own names against Intuit's current list, not this page →
Get the scanner Fix what it finds →