On this page Jump to section
Question and scope
When a customer is made inactive in QuickBooks Online, do that customer's open invoices leave the accounts receivable aging report, or do they remain visible as unpaid balances? The scope is one company file and a defined set of customer status changes, not every QuickBooks edition or every report customization. The test separates the customer's active or inactive status from the invoice's open balance and from the report filter that controls which customers appear. It does not decide whether the customer should be archived, because that is a records and relationship decision. The purpose is to show whether a cleaner customer list changes the receivable picture a reviewer sees.
Why archiving needs its own test
Archiving a customer is often described as hiding the record from daily drop-downs while keeping the history attached. The risk is that a team treats the quieter list as proof that the balance is gone, especially when the aging report is filtered to active customers. A bookkeeper who archives a dormant customer during cleanup may accidentally remove the invoice from the review queue without collecting or writing it off. Testing the report behavior separately keeps a presentation change from being mistaken for a settlement.
The customer status also affects how new work is entered. An inactive customer may not appear in the invoice or sales receipt drop-down, so a later order can be recorded under a duplicate active record. That duplicate can split the history and make the aging report harder to reconcile. The test should record whether the archive was reversed, whether a new customer record was created, and whether any open balance moved between the two records.
Population and unit
Start with a dated export of customers made inactive during the review window. Record the customer reference, the status change date, the person who made the change, the open invoice count, and the total open balance before the change. The unit is one customer status change paired with one open invoice that existed before the change. A customer with several open invoices needs one row per invoice so a partial disappearance is visible. Exclude customers with no open invoices and record the exclusion so the population can be rebuilt.
Freeze the list before opening the aging report. If the customer is reactivated or merged 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 customers that already show the expected report behavior. Use internal customer and invoice references in the working file instead of names and email addresses. Store the export with the test notes so another reviewer can retrace the exact population.
Definitions and measures
A balance remains visible when the open invoice still appears in the aging report for its period after the customer is made inactive. Record the report name, the date range, the aging buckets, and every filter applied before the change and after it. Do not treat the absence of the customer from a drop-down as proof that the invoice left the report, because the two screens use different filters. The measure should let a reviewer compare the customer status, the invoice status, and the report line side by side.
Also record whether the invoice itself was changed. If the invoice was voided, paid, or written off in the same cleanup, the balance may leave the report for a reason unrelated to the customer status. Capture the invoice history and the date of each related action. Keep the measure at the customer-invoice pair so one large balance cannot hide a single invoice that disappeared. A clear definition prevents two reviewers from reaching different conclusions from the same report.
Test design
Use a census when the number of archived customers with open balances is small, and a documented sample when the list is large. Include at least one customer with a single current invoice, one with several past-due invoices, one with a partial payment, and one with an unapplied credit. Include a customer whose invoices span more than one aging bucket if one exists. Freeze the sample before running the reports and compare the customer list, the invoice list, and the aging report in that order.
Document how the sample was selected and which customers were left out. A sample built only from the largest balances will miss the small dormant accounts that are most likely to be archived during cleanup. If the business uses a third-party app to sync customers, include at least one record that came through that app. Record whether the status change was made individually or through a bulk import, because the entry point can change what the reviewer sees. The selection note is what lets a later reader judge whether the result applies beyond the tested rows.
Data collection
Use the customer list, the open invoice list, the accounts receivable aging report, and the general ledger as the source set. Capture the customer reference, the status before and after, the invoice reference, the open balance, and the report run date. Export the aging report before the status change when possible, and keep that file even if the customer 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 customer reference. Include the customer record before and after, the invoice list, the aging report, and any note that explains why the customer was archived. If the change was part of a bulk cleanup, record the batch reference and the time it was applied. A reviewer should not have to search across the customer list and the report 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 archives a customer with one invoice that is ninety days past due. The customer disappears from the active customer list, but the invoice may still appear in the aging report when the report includes inactive customers. The reviewer records the report filter, the invoice status, and the open balance before deciding whether the archive changed the receivable. That sequence shows whether the cleaner list is only a display change or a real change in the review population.
A second case may show the opposite pattern. The aging report is filtered to active customers, so the invoice leaves the report even though the balance remains open in the ledger. The reviewer should report the filter as the cause rather than treating the balance as collected. A third case may show the invoice was voided during the same cleanup, which is a separate event that must be documented. These examples show why the test records the status, the invoice, the report, and the ledger as separate observations.
Evidence standard
Each row needs the customer record before and after, the open invoice, the report view, and the source of each value. Keep the archive approval with the internal record so the reviewer can see who authorized the change. If the customer was reactivated, retain both the original change and the reversal and record the dates. Protect customer details by using internal references in the working file. A test that cannot show the original status and the open invoice is only a recollection of the change.
Interpretation limits
A balance that disappears from one report may still exist in the ledger, especially when the report excludes inactive customers. A balance that remains visible does not prove the customer should stay active, because the status change may still be correct for daily operations. Pair this test with a review of the open balance and a decision to collect, credit, or write it off. Compare the result with the customer payment application workflow when an unapplied credit is involved. Report the report filters, the QuickBooks configuration, and the status date so the finding is not overread.
Review cadence
Run the test after any customer cleanup, merge, or report filter change. A quarterly check fits a business with a stable customer list, 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 report filters change, record a new baseline instead of mixing the old and new views. End the review with a named owner, a specific repair, and a date to retest; for related context, compare the customer duplicate merge checklist.