QuickBooks Online Balance Sheet keeps prior-month totals in a one-month report
QuickBooks Online users report Balance Sheet totals that ignore the chosen date range; the accepted answer explains cumulative balances and the aging fix.
A familiar puzzle has resurfaced in QuickBooks Online discussions: users run a Balance Sheet for a single month, and balances from earlier months still appear in the totals. The report is not broken. The accepted answer explains that the Balance Sheet accumulates by design, and it gives readers a way to find the day a balance genuinely goes wrong. The symptoms are consistent across the threads: cumulative totals, mismatched receivables, and reports that seem to contradict each other.
April’s report still carries March
Running the report is simple: open Reports, choose Standard reports, and select Balance Sheet. The confusion begins with the Report period dropdown. Narrow it to one month, and the figures refuse to shrink to that month alone.
The reason is structural rather than a glitch. A Balance Sheet is a snapshot of the company as of the end date, and every account carries a beginning balance forward. Money that landed in March does not leave the April report just because the filter now says April.
Picture a sales tax liability account with $50 accrued in March and another $60 in April. Set the report to April only, and the account still shows $110. Select that figure to drill down, and the transaction detail opens with a $50 beginning balance followed by the April entry of $60. The filter changed the window, not the running total.
Which reports actually respect the date range?
Not every report behaves this way. Sales by Product/Service is a true period report: set it to April, and it shows only that $60. This split is the trap. Users compare a cumulative Balance Sheet against a period report, see different figures for the same account, and conclude that one of the two must be wrong.
Nothing is wrong. The two reports are doing different jobs, and the accepted answer spells out which job each one performs. The Balance Sheet answers what the account holds as of a date. The sales report answers what moved inside the window you set.
Receivables that refuse to match
There is a second mismatch, and it appears when the Balance Sheet is compared against the Accounts receivable aging report. For any date in the past, the two totals agree only when the aging report uses a particular setting.
The fix is one dropdown. On the aging report, set the Aging method to Report period. Do that, and Total Accounts Receivable matches on both reports. Leave the method on its default, and a historical Balance Sheet will disagree with the aging summary sitting right beside it.
Finding the day the balance went off
When a Balance Sheet is truly off, the accepted answer recommends a narrowing search rather than a hunt through every transaction. The tool for that search is the Balance Sheet Comparison report.
Open it from the report search bar, set Report period to Custom dates, choose a start and an end, and refresh. From there, select any account in the report to see the transactions behind its balance.
Start wide, with the full year to date. Narrow the window one month at a time and watch where the totals stop agreeing. Keep shrinking the range until it covers the single day the balance sheet goes off. That day now holds the transaction causing the problem, and the correction usually follows from there.
One setting worth verifying first
The accepted answer closes with a configuration check that quietly affects every comparison. Under Settings, open Account and settings, then Advanced, and edit the Accounting section. If First month of income tax year is set to anything other than January, change it to January and save.
A fiscal year that starts off the calendar shifts how periods line up across reports. Comparisons built on mismatched year starts will show gaps that no amount of transaction hunting explains.
The takeaway for readers is plain. The balances are usually real; they simply belong to a wider window than expected. Knowing which reports accumulate and which ones reset settles most of the confusion, and the narrowing search handles the rest. We will follow the discussion in case the behavior changes.