The June 30 QuickBooks Deadline Just Hit — Here's What Broke, and What to Do Now

The June 30, 2026 deadline Intuit gave everyone to prepare for QuickBooks Online's report format migration has passed. If you're reading this on the other side of it and your Fintech uploads, Excel macros, or any QBO-connected workflow just started failing — here's exactly what changed and what to fix right now.

We didn't wait to find out the hard way on July 1. We found out three months early, when our Fintech upload broke in March with no warning from Intuit. That early break gave us time to reverse-engineer every change. This article is the playbook we wish we'd had.

What Just Changed (Permanently)

On March 30, 2026, Intuit published "Upcoming Changes to Reports APIs" on their developer blog. As of July 1, the old format is gone across all 29 supported report types. Here is what changed:

Column headers renamed — "ALL CAPS" to "Title Case." Any parser, macro, or VLOOKUP that matches on an exact header string will fail. "DATE" is gone. "AMOUNT" is gone. If your Excel formula references a column called "TOTAL," it's now looking for a column that doesn't exist.

Row ordering is no longer stable. Row indices are generated dynamically now. If your workflow assumes "row 3 is always the first account line" — that assumption is broken.

Null values changed. Fields that previously returned 0 now return an empty string "". Any SUM formula, any numeric parser, any system expecting a zero gets a blank instead.

Account nesting behavior changed. Child accounts now always nest under their parent, even when the parent has transactions. This restructures the output of every Balance Sheet, P&L, and Trial Balance export.

Split account fields changed. Used to show "-Split-" when no split account existed. Now returns blank.

Date summarization capped. Yearly reports summarized by day used to return 365 columns. Now capped at 100, with everything beyond that bucketed into "Others."

Undocumented report endpoints removed. Only the 29 officially supported report types survive. If you built anything on an unlisted endpoint, it's gone.

The 29 surviving report types include: Profit and Loss, Balance Sheet, Cash Flow, A/R Aging Detail, A/P Aging Detail, General Ledger, Trial Balance, Inventory Valuation, Sales by Customer, Sales by Product, Vendor Balance, Journal Report, and more. See the full list at the Intuit Developer Blog.

If You Upload to Fintech, This Is Your Most Urgent Problem

Fintech processes $53 billion in annual alcohol purchases across over 1 million B2B relationships. Their PaymentSource platform expects invoice data in a very specific tab-delimited format — exact column names, CRLF line endings (not LF), and a specific sign convention on quantities.

When we first hit this break in March, it came down to three simultaneous changes in the Journal export:

1. The header column "Date" was renamed to "Transaction date" — our parser searched for an exact match and never found it.
2. Detail rows now repeat metadata on every line — date, type, invoice number, customer name now appear on every row instead of only the first. Our row classifier treated every line as a new invoice header.
3. Quantity signs were flipped — sale quantities that exported as negative (inventory-out, as QBO had always done it) now come through as positive. Fintech ingested every quantity with the wrong sign.

Any one of those changes breaks a Fintech upload. All three arrived simultaneously, with no advance notice.

Fintech works with 9,200+ distributor partners. If you're one of them and you export from QBO — whether through an Excel macro, middleware, or an in-house tool — test your upload process today. Pull a fresh Journal export, run it through your existing workflow, and confirm Fintech accepts it. If it returns "0 records found," you're looking at one of the three breaks above.

What to Fix Right Now

1. Check your headers first. Pull your most critical QBO reports (Journal, P&L, A/R Aging, A/P Aging) and compare the column headers to a version from before June 30. "Date" → "Transaction date" is the most common break. Fix every exact-match header reference in your macros or parsers.

2. Stop depending on row positions. If your workflow identifies fields by column letter or row number, rewrite it to identify by column header. Column A won't always be what you expect.

3. Add null handling where you had zeros. Every numeric field that could return blank instead of zero needs a null check. IF(ISBLANK(A1),0,A1) in Excel. Explicit None/NaN handling in any code.

4. Verify quantity signs on your Fintech output. If your upload is being rejected and the data looks structurally correct, check whether debit/credit signs are inverted. The Journal export flip from negative to positive quantities is subtle and will pass a structure check while still causing Fintech to reject the file.

5. Talk to every vendor that reads your QBO exports. If you upload to Fintech, a payroll processor, a tax prep tool, or any SaaS integration — ask them directly whether their import parser has been updated for the new format. Some will have already fixed it quietly. Others won't know until you ask.

6. If you have an API integration, the testing_migration query parameter Intuit offered to preview the new format before June 30 is no longer relevant — you're now always on the new format. Treat your current live API responses as the source of truth and audit your parsing logic against them.

What We Built to Handle This

After we hit the March break, we rewrote our Fintech upload builder to handle both the old and new QBO export formats automatically. The parser now detects which format it's reading based on the header row, adjusts its row classification logic, corrects the quantity sign convention, and rebuilds the output file to Fintech's exact spec — CRLF line endings, the two-blank-row separator structure, all of it.

We've built format-drift detection into ThirstMetrics, our operations platform for beverage distributors. When a QBO export comes in, the system fingerprints the file structure, compares it to what it expects, and flags changes before they can silently corrupt your data downstream.

If you're a beverage distributor dealing with broken QBO exports right now — or trying to get ahead of any remaining breakage in your stack — reach out.

Source: [Upcoming changes to Reports APIs — Intuit Developer Blog, March 30, 2026](https://medium.com/intuitdev/upcoming-changes-to-reports-apis-5083ec9aadce)

Additional reference: [QuickBooks Online Reports API: Best practices and troubleshooting — Intuit Developer Blog, February 2026](https://medium.com/intuitdev/quickbooks-online-reports-api-best-practices-and-troubleshooting-31edc9934b4c)

[Fintech Celebrates 1 Million Distributor-to-Client Connections — BusinessWire, January 2024](https://www.businesswire.com/news/home/20240123129581/en/Fintech-Celebrates-Remarkable-Milestone-1-Million-Alcohol-Distributor-to-Client-Connections-with-PaymentSource)