On this page Jump to section
Question and scope
When a chart of accounts entry is made inactive in QuickBooks Online, does its historical balance and transaction activity disappear from reports for periods that were already closed? The scope is one company file and a defined set of accounts inactivated during a review window. The test compares the same report period before and after the status change, at the account level and at the transaction level. It does not decide whether the account should have been inactivated, because that depends on the reporting design and the owner's intent. The test shows whether the historical record stays visible after the status change.
Why an inactive account needs its own test
Inactivating an account is usually described as hiding it from future use. That description is easy to misread as removing it from the books. In practice, an inactive account can still hold a balance, still appear in a balance sheet, and still be required to explain a prior-period total. A team that expects the account to vanish may conclude a report is broken when the balance remains, or may miss that a balance disappeared from a detail view. Testing the report separately from the picker keeps the two behaviors distinct.
The status change also affects how the team works. An inactive account cannot be selected for most new transactions, so a recurring entry or import that references it may fail or post to a default account. The failure may appear as a missing transaction rather than an account problem. Testing the report and the transaction path together shows whether the change is only cosmetic or whether it changes the accounting record the team relies on.
Population and unit
Start with a dated export of accounts made inactive during the review window. Record the account number, the account name, the account type, the date of the status change, and the person who made it. The unit is one inactivated account paired with the report period that contains its activity. An account with activity in several periods needs one row per period so a partial disappearance is visible. Exclude accounts with no activity and record the exclusion so the population can be rebuilt.
Freeze the list before opening the reports. If an account is reactivated during the test, keep the first observation and add a dated note rather than replacing the earlier state. A moving list makes it too easy to select only the accounts that already show the expected behavior. Use internal account references in the working file where the report names are sensitive. Store the export with the test notes so another reviewer can retrace the exact population.
Definitions and measures
A historical removal occurs when an account that had activity in a closed period no longer appears in the same report, or appears with a zero balance, after the status change. Record the report name, the period, the account line, and the amount before and after as separate observations. Do not treat the absence of the account from a dropdown as proof of removal, because the picker and the report are different views. The measure should let a reviewer compare the report line, the underlying transactions, and the trial balance side by side.
Also record whether the account still appears in the chart of accounts list and whether it can be selected for a new transaction. Capture the report run date and the accounting period so a period cutoff does not look like a status effect. Keep the measure at the account-period level, because a company-level total can hide one account whose balance moved into another line. The unit is the account-period pair, not the account alone.
Test design
Use a census when the number of inactivated accounts is small, and a documented sample when the list is large. Include at least one asset account, one liability account, one income account, and one expense account. Include an account with a zero balance, one with a balance carried from a prior year, and one used by a recurring transaction. Include a period that was closed before the status change and a period still open if both exist. Freeze the sample before running the reports and compare the chart of accounts, the report, and the transaction list in that order.
Document how the sample was selected and which accounts were left out. A sample built only from accounts with large balances will miss the routine cleanup that creates most status changes. If the business uses classes or locations, include an account whose activity is split across them. Record whether the status change was made through the account screen, an import, or a third-party app, because the entry point can change which related records are affected. The selection note is what lets a later reader judge whether the result applies beyond the tested rows.
Data collection
Use the chart of accounts, the trial balance, the balance sheet, the profit and loss report, and the audit log as the source set. Capture the account number, the report period, the account line, the amount, and the status-change date. Export the reports before the change when possible, and keep that file even if the account is later reactivated. Mark any reconstructed value and name the person who reconstructed it. Do not overwrite the original export columns when adding analysis fields, because the original values are the evidence.
Save the supporting files in one folder keyed by the account reference. Include the account before and after, the reports, the transaction list, and any note that explains why the account was retired. If the change was part of a chart of accounts cleanup, record the batch reference and the time it was completed. A reviewer should not have to search across the account list and the audit log to reconstruct one status change. The folder can be small, but it must let another person follow the same path without asking the preparer what happened.
A worked example
Suppose a business inactivates an old equipment account after moving its remaining balance to a newer fixed asset account. The balance sheet for the prior year may still show the old account line, because the historical period uses the transactions as posted. The reviewer records the report line, the amount, and the account status before and after the change. That sequence shows whether the account disappeared from the historical report or only from the picker for new entries.
A second case may show the opposite pattern. The account is inactivated with a zero balance, but a recurring journal entry still references it, so the next run posts to a default account or fails outright. The reviewer should report the recurring-entry failure as a separate event rather than treating it as proof that the account was removed correctly. These examples show why the test records the account, the report, the transaction path, and the audit log as separate observations.
Evidence standard
Each row needs the account record before and after, the report before and after, the transaction list, and the source of each value. Keep the inactivation approval with the internal record so the reviewer can see who authorized the change. If the account was reactivated, retain both the original and the reversal and record the dates. Protect sensitive report details by using internal references in the working file. A test that cannot show the original account line and the original balance is only a recollection of the status change.
Interpretation limits
An account that remains in a historical report may reflect correct behavior rather than a failure to inactivate, because the report is showing posted activity. An account that disappears may reflect a report filter, a period selection, or a reclassification, not only the status change. A clean chart of accounts does not prove the reports are correct, because the remaining accounts may be mapped to the wrong financial statement line. Pair this test with a review of the inactivation approval and a comparison of the trial balance. Report the account type, the report used, and the period so the finding is not overread.
Review cadence
Run the test after any change to the chart of accounts, the reporting template, or the import process. A quarterly check fits a business with stable reporting, while a monthly check may be needed during a cleanup or a system migration. Keep the sample rule and the definitions stable so two periods can be compared. If the reporting design changes, record a new baseline instead of mixing the old and new settings. End the review with a named owner, a specific repair, and a date to retest; for related evidence, compare the item account change test and the chart of accounts optimization guide.