On this page Jump to section
Question and scope
After a bill payment is voided in QuickBooks Online, does the linked bill return to the open payable list, and does the transaction history make the void clear enough for a reviewer? The scope is one business's bill payments during a defined window, not every QuickBooks configuration or payment method. The test separates the bill's payable status from the cash movement so a reopened bill is not inferred from a bank credit alone. It does not decide whether the vendor should be paid again, because that is a cash-management decision. The purpose is to show whether the accounting record supports a deliberate next step.
Why a void needs its own test
A bill payment reduces the accounts payable balance and creates a cash or bank movement in the same transaction. When that payment is voided, the business needs the payable restored, the bank movement reversed, and the audit trail retained. A team that tests only deleted payments may never see how a void behaves when the original bill remains linked. The distinction matters because a deletion can remove evidence while a void may preserve the transaction and its history. Testing the void path separately prevents the team from assuming that every reversal restores the bill in the same way.
The test also separates a bill payment from a vendor credit or a check. A vendor credit reduces what the business owes without moving cash, while a bill payment settles an existing payable. A check written outside the bill payment workflow may link differently or not at all. Recording the payment type, the bank account, and the link to the bill lets a reviewer see which path was tested. Without that detail, a result from one payment method can be misapplied to another.
Population and unit
Start with a dated export of bill payments voided during the review window. Record the payment date, the vendor reference, the bank account, the payment method, the linked bill number, the bill amount, and the payment amount. The unit is one voided bill payment linked to one bill, not the vendor or the whole batch. A payment that covers several bills needs one row per bill so a partial reopen is visible. Exclude payments that were never linked to a bill and record the exclusion so the population can be rebuilt.
Freeze the list before opening the bill records. If a bill is edited or paid again after the void, keep the first observation and add a dated note rather than replacing it. A moving list makes it too easy to select only the cases that already show the expected status. Use internal vendor and bill references in the working file instead of names and bank numbers. Store the export with the test notes so another reviewer can retrace the exact population.
Definitions and measures
A bill is reopened when its open balance returns to the amount that was unpaid before the void, in the same period and for the same vendor. Record the balance before the payment, after the payment, and after the void as three separate observations. Do not treat a bank credit as proof that the bill reopened, because the cash reversal and the payable status are different events. Also record whether the bill remained linked to the voided payment or became a standalone open bill. The measure should let a reviewer see both the cash side and the payable side.
Capture the void date, the person who voided the payment, and the reason recorded in the transaction. If QuickBooks keeps the voided payment in the bill's payment history, note what that history shows and whether the link is still usable. If the payment disappears from the bill, record that as a separate finding rather than calling the bill reopened. Keep the measure at the payment-bill pair so one payment covering several bills cannot hide a partial result. A clear definition prevents two reviewers from reaching different conclusions from the same screen.
Test design
Use a census when the number of voided payments in the window is small, and a documented sample when the list is large. Include at least one payment by check, one electronic payment, one partial payment, and one payment that covered more than one bill. Include voids processed by different people if the business has more than one approver. Freeze the sample before opening the bill records and compare the original bill, the payment, the void, and the current balance in that order. A second reviewer should recheck a subsample and record disagreements before the team resolves them.
Document how the sample was selected and which payments were left out. A sample built only from the largest payments will miss the routine voids that create most of the daily noise. If the business uses a separate bill approval system, include at least one payment that passed through that system. Record whether the void was done from the bill payment screen or from the bank register, 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 bill, the bill payment, the void confirmation, and the bank register as the source set. Capture the transaction dates, the amounts, the vendor reference, and the bank account for each row. If the bill history no longer shows the voided payment, export or screenshot the payment record before the void is completed. 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 payment reference. Include the bill before the payment, the payment confirmation, the void confirmation, and the bank reversal when one exists. If the payment was part of a batch, record the batch reference and the time the batch was posted. A reviewer should not have to search three systems to reconstruct one void. 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 pays a fifty-dollar utility bill by check and later voids the payment because the check was cancelled. The bank register shows the original withdrawal and a reversal, while the bill record may show either an open balance or no payable at all. The reviewer records the bill balance before the payment, after the payment, and after the void, then checks whether the voided payment remains linked. That sequence shows whether the payable returned and whether the evidence survived the reversal.
A second case may show the opposite pattern. The bill reopens, but the bank reversal posts to a different account or date than the original payment. The payable looks correct while the cash reconciliation carries an unexplained timing difference. The reviewer should report the account and date mismatch as a separate finding rather than treating the reopened bill as a complete pass. These examples show why the test records the payable, the cash movement, and the link as separate observations.
Evidence standard
Each row needs the original bill, the payment, the void confirmation, the bill balance before and after, and the source of each value. Keep the vendor-facing confirmation with the internal record so the reviewer can see what the vendor was told. If the payment was stopped at the bank, retain the stop-payment confirmation and record the date. Protect bank account numbers and vendor contact details by using internal references in the working file. A test that cannot show the original bill and the void record is only a recollection of the reversal.
Interpretation limits
A bill that does not reopen may be correct when the payment was applied to a different bill, when the void failed, or when the business uses another accounts payable system. A bill that does reopen does not prove the cash reconciliation is right, because the bank reversal could be missing or posted to the wrong period. Pair this test with a bank reconciliation review and a check of the vendor balance after the void. Compare the result with the bill payment approval evidence review and report the payment method, entry point, and configuration. The finding describes the tested voids, not the permanent reliability of the accounts payable process.
Review cadence
Run the test after any change to the bill payment workflow, the bank feed, or the approval roles. A monthly check fits a business with frequent voids, while a quarterly review may be enough for a small accounts payable queue. Keep the sample rule and the definitions stable so two periods can be compared. If the void process changes, record a new baseline instead of mixing the old and new method. End the review with a named owner, a specific repair, and a date to retest; for a related control, compare the journal entry attachment reversal test.