The New Sales Tax Liability Report in QuickBooks Online
Filing sales tax out of QuickBooks Online has involved a familiar detour. Run the liability report, find that it does not match how your state wants the numbers presented, export it, rebuild it in a spreadsheet with your own formulas, and cross-reference a second report to fill in what the first one left out.
QuickBooks rebuilt the report to remove that detour. It started rolling out at the end of July 2026 and carries a beta label. The old version is still available, labeled legacy, and the two are linked to each other so you can compare them on the same data.
This is a report change, not a tax engine change. Your calculated tax amounts are the same. What changed is how the numbers are grouped, totaled, and taken apart.
Who can see it
Two conditions.
- You have to be on automated sales tax rather than classic sales tax. If your sales tax area looks like a dashboard with its own pages underneath, you are on automated and the report applies to you. If it looks like the older single-screen version, it does not, and the file needs upgrading first. Automated sales tax covers both automatic rate calculation and custom rates.
- You also have to be in the United States. This report is US only.
Rollout is staged, so a file that meets both conditions may still not show it yet.
How to open it
Three routes reach the same report.
- Go to Reports, then standard reports, and scroll to the sales tax section, or type "sales tax" into the report search box. The new one carries a beta label and the old one carries a legacy label.
- Open the sales tax app from the all apps menu, which now lands on the new report.
- Come at it from the returns page, through view summary or the e-filing flow.
From inside either report there is a link to the other, so switching back to the legacy version to sanity check a number takes one click.
What is actually different
Jurisdictions are nested instead of listed flat
The legacy report sorted rows by type: the state first, then every county, then every district at the bottom. Nothing told you which district belonged to which county. On a return with any real geographic spread, you were reconstructing the hierarchy in your head.
The new report indents rows to show the relationship. A county district sits underneath its county. A city district sits underneath the jurisdiction it belongs to. You can read the structure instead of inferring it.
The totals you were missing are there
The legacy report gave you a total tax figure and left the rest to you. The new one totals gross sales, non-taxable sales, and taxable sales as well, which is what most state forms ask for on the first few lines.
Drill-downs go to the right transactions
This one was a straightforward bug in behavior. Clicking a non-taxable amount in the legacy report opened a transaction list built around tax and taxable amounts, so the detail did not tie to the figure you clicked.
In the new report, clicking a non-taxable figure gets you the transactions that make up that non-taxable figure. You can view the detail grouped by customer or by transaction, and switch between those two without leaving the report.
There is also an inline option. Each row has a chevron that expands the transactions underneath it in place, so you can open two jurisdictions side by side and compare them without opening and closing separate detail pages.
Pivot the whole report by tax rate
States do not agree on how tax should be reported. Some want it by jurisdiction. Others want it grouped by rate, so every one percent line reports together regardless of which county it came from.
The new report handles both. In the customize bar you choose whether the report is organized by tax jurisdiction or by tax rate. Switch to tax rate and the whole report regroups, with all 1 percent rows together, all 0.5 percent rows together, and so on. If you file in Florida, this is the setting that removes the spreadsheet step entirely.
Combine components for states that report them merged
Some states want the county district and city district portions reported as a single combined figure. California is the standard example: the district amounts have to be added together before they go on the form.
In customize, switching the component setting to combined folds the county district portion into the city district line and reports the sum. The report does the addition, so you are reading a number rather than calculating one. Tooltips flag amounts that are already included in a subtotal above them, which is the specific place where hand-built spreadsheets have historically double counted.
A worked example of why the flexibility matters
Two states, two different requirements, one report.
Arizona wants city and county separated so you can file them individually. That is what the nesting gives you: each level visible on its own row, with its own amount.
Ohio wants state, county, and district reported as one aggregated figure at the current level. That is what combining components gives you.
Neither of those is a preference. They are what the forms require, and the reason a single fixed layout could never work for everyone.
What Intuit says is coming
From the August 2026 session, the roadmap includes:
- More subgroup options beyond customer and transaction
- A column showing the reason a sale was tax exempt
- Non-taxable and exempt split into two separate columns
- Jurisdiction and location codes available both as an extra column and as the primary grouping, with Washington and Colorado being the states that need this most
- Local and state agencies merged into one report structure rather than reported separately, which is relevant in Colorado and Louisiana
Treat all of that as announced rather than shipped.
The part that still lands in a spreadsheet
The report is better. What happens after the report is unchanged.
Most firms filing sales tax keep a workbook alongside it: a tab per state, prior periods for comparison, a reconciliation against what was actually remitted, and the notes explaining the quarter when something went sideways. The rebuilt report makes the QuickBooks half easier to read. It does not fill in the workbook.
Exporting does not fix that either. An export is correct for exactly as long as nobody edits a transaction in the period, which on a filing deadline is not a safe assumption.
To be straightforward about scope: Retriever does not sync the Sales Tax Liability report itself. Run that one in QuickBooks. What Retriever does sync is most of what sits around a filing workbook, including Sales by Customer, Sales by Product, the Transaction List, and the Profit and Loss, pulled into Google Sheets and refreshed on a schedule so the supporting tabs stay current instead of being re-exported every quarter. It is read-only, so it never writes to your books, and it works on any QuickBooks Online plan.
If your sales tax work is one report and no workbook, you do not need any of this. If you keep supporting schedules that go stale between filings, that is the part worth automating.
Keep the schedules around your filing current
Retriever pulls Sales by Customer, Sales by Product, the Transaction List, and your P&L into Google Sheets and refreshes them on a schedule, so the supporting tabs are never a re-export away. Any QuickBooks Online plan, read-only, from $60 a month.
See how Retriever worksFrequently asked questions
Where is the sales tax liability report in QuickBooks Online?
Reports, then standard reports, then the sales tax section, or search "sales tax" in the report search box. You can also reach it from the sales tax app in the all apps menu or from the returns page through view summary.
Why can't I see the new sales tax liability report?
Most likely you are on classic sales tax rather than automated sales tax, or the rollout has not reached your file yet. The report is also US only. Check your sales tax area first: the automated version shows a dashboard with additional pages beneath it.
Can I still use the old sales tax liability report?
Yes. The previous version is still available with a legacy label, and the two reports link to each other so you can move between them.
How do I group the sales tax liability report by tax rate instead of jurisdiction?
Open the customize bar and change the grouping from tax jurisdiction to tax rate. Every row at the same rate is then reported together, which matches how states like Florida want the return filed.
Can QuickBooks combine county and city district taxes into one line?
Yes. In customize, set the component option to combined. The county district portion is folded into the city district line and the report shows the sum, which is what states like California require.
Can I sync the sales tax liability report into Google Sheets?
Not with Retriever, which does not cover that report. Run it in QuickBooks. Retriever syncs the reports that usually sit around a filing workbook, including Sales by Customer, Sales by Product, the Transaction List, and the Profit and Loss, and keeps them refreshed on a schedule.
Did my sales tax calculations change with the new report?
No. This is a reporting change. The underlying calculations, rates, and transactions are the same.
See also
Source: Intuit, "In the Know" live webinar, August 20, 2026, with the report walkthrough presented by David Gudai, product manager for sales tax at QuickBooks.