On this page Jump to section
Question and scope
When a credit memo, refund, or unapplied payment is applied to a customer account after the statement date, does the QuickBooks Online customer statement include that credit in the balance it presents? The scope is one company file and a defined set of statements produced during a review window. The test compares the statement date, the transaction dates, the credit application date, and the accounts receivable balance at each point. It does not decide whether the credit itself was warranted, because that depends on the customer agreement and the billing history. The test shows whether the customer document and the internal receivable tell the same story.
Why the statement date matters
A customer statement is a point-in-time document, not a live view of the account. It presents activity and a balance as of the statement date, so a credit applied the next day may fall outside the statement period. That behavior can be correct and still create a collection problem if the customer reads the statement as the current amount owed. A bookkeeping VA who understands the cutoff can explain the difference before the customer calls about a balance that was already reduced.
The risk is higher when a credit is applied after a statement has been generated but before it is sent. The internal accounts receivable aging report shows the reduced balance, while the file attached to the email shows the older one. The customer pays the older amount, creates an overpayment, and the next statement has to explain a credit balance. Testing the timing keeps the statement, the aging report, and the customer message from disagreeing at the moment of collection.
Population and unit
Start with a dated list of customer statements generated during the review window. Record the customer reference, statement date, statement balance, delivery method, and the person who generated it. Pair each statement with every credit memo, refund, and payment applied to the same customer within a defined window after the statement date. The unit is one statement paired with one credit event, so a statement with two later credits produces two observations. That structure makes a partial reflection visible instead of hiding it inside a customer total.
Exclude statements with no activity and record the exclusion so the population can be rebuilt. If a statement was regenerated after the credit, keep both versions and note which one was sent. Freeze the list before opening the customer register, because a moving list makes it too easy to select only the statements that already match the aging report. Use internal customer references in the working file and store the export beside the test notes.
Definitions and measures
A reflected credit means the statement balance already accounts for the credit, either because the credit was applied on or before the statement date or because the statement was regenerated afterward. Record the statement balance, the accounts receivable balance as of the statement date, the credit amount, the credit application date, and the balance after application. Do not treat a zero customer balance as proof that the statement reflected the credit, because a later payment or write-off can produce the same result. The measure must let a reviewer compare the document, the ledger, and the aging report side by side.
Also record whether the credit appears as a line on the statement, as an unapplied credit, or not at all. A credit that appears without reducing the balance is a different problem from a credit that is absent. Capture the statement template and the delivery method, because a summary statement and an open-item statement may present the same account differently. Keep the measure at the statement-credit pair, because a customer-level total can hide one credit that was reflected and another that was missed.
Test design
Use a census when the number of statements is small, and a documented sample when the list is large. Include at least one statement with a credit applied before the statement date, one with a credit applied the same day, one with a credit applied the next day, and one with a credit applied after the statement was sent. Add a statement with a partial credit, a statement with a credit larger than the open balance, and a statement for a customer with several open invoices. Include a statement generated in the current open period and one from a closed period if both exist.
Document how the sample was selected and which statements were left out. A sample built only from large balances will miss the routine credits that create most of the questions. If the business uses consolidated statements for parent customers, include one where the credit belongs to a child account. Record whether the statement was generated manually, on a schedule, or through an app, because the entry point can change which transactions are included.
Data collection
Use the statement list, the customer register, the credit memo list, the payment list, and the accounts receivable aging report as the source set. Capture the statement date, statement balance, credit amount, credit date, application date, and the balance before and after application. Export the statement and the aging report before regenerating anything, and keep those files even if the statement is later corrected. Mark any reconstructed value and name the person who reconstructed it. Do not overwrite the original export columns when adding analysis fields.
Save the supporting files in one folder keyed by the statement reference. Include the statement as sent, the customer register view, the credit memo, the aging report, and any customer message that references the balance. If the statement was part of a monthly batch, record the batch reference and the time it was generated. A reviewer should not have to search across the customer list and the email archive to reconstruct one statement. 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 customer receives a statement dated the last day of the month showing an open balance of four thousand dollars. A credit memo for six hundred dollars is applied on the second day of the following month. The internal aging report now shows thirty-four hundred dollars, but the statement attached to the email still shows four thousand. The reviewer records the statement date, the credit application date, and both balances, then checks whether a corrected statement was sent.
A second case may show the opposite pattern. The credit was applied on the statement date but after the statement was generated, so the document and the ledger disagree by one day. The reviewer should report the timing rather than treating the credit as missing. A third case may show a credit that appears on the statement as an unapplied amount without reducing the balance. These examples show why the test records the document, the ledger, and the delivery record as separate observations.
Evidence standard
Each row needs the statement as sent, the customer register before and after the credit, the aging report at the statement date, and the source of each value. Keep the generation log or batch record with the internal file so the reviewer can see when the statement was produced. If the statement was regenerated, retain both the original and the replacement and record the dates. Protect customer details by using internal references in the working file. A test that cannot show the statement that the customer actually received is only a reconstruction of what might have been sent.
Interpretation limits
A statement that omits a later credit may be correct because the credit falls outside the statement period. A statement that includes a credit may still be wrong if the credit was applied to the wrong invoice or customer. A customer balance that matches the aging report does not prove the statement was understandable, because the presentation may still confuse an open-item versus summary format. Report the statement date, the credit date, the template, and the delivery method so the finding is not overread. Pair this test with a review of the statement delivery log and a comparison of the customer's payment remittance.
Review cadence
Run the test after any change to the statement template, the credit memo workflow, or the accounts receivable process. A quarterly check fits a business with stable billing, while a monthly check may be needed during a collections push or a system migration. Keep the sample rule and the definitions stable so two periods can be compared. If the statement process changes, record a new baseline instead of mixing the old and new methods. End the review with a named owner, a specific repair, and a date to retest.
For related evidence, compare the customer statement delivery check and the accounts receivable aging review. For platform context, use Intuit's QuickBooks Online help center. Record the repair in the same evidence folder as the test rows. Retest the changed statement path before the review is closed.