On this page Jump to section
BLUF: A payment hold list gives the owner one place to see what is not being paid and why. It prevents accidental payment, preserves the vendor record, and makes the release decision explicit.
Without a list, holds live in email threads and memory. A new assistant runs the payment run, sees an approved bill, and pays it.
What belongs on the list
A hold is appropriate when the bill is disputed, the goods have not arrived, the vendor documentation is incomplete, the amount does not match the purchase order, or the owner has asked to delay payment.
Add the bill number, vendor, amount, due date, reason, owner, date placed, and release condition. The release condition is the part most lists miss. "Awaiting corrected invoice" is a condition; "on hold" is not.
Capture the reason in plain language
Use a short category plus a note:
- Price or quantity mismatch
- Missing or incorrect documentation
- Goods or services not received
- Duplicate suspected
- Owner instruction
- Compliance or vendor onboarding issue
The note should say what has to happen for the hold to end. "Waiting for the vendor to reissue invoice 8841 with the correct PO number" is actionable.
Keep the bill in the ledger
Do not delete or void the bill to keep it out of the payment run. The obligation exists and the ledger should show it.
If the payment run cannot exclude a held bill, mark it clearly in the memo and check the run by hand. A short manual check is cheaper than a wrong payment.
Put the owner in the loop
The hold list goes to the owner before each payment run. The assistant highlights new holds, holds older than the due date, and holds with no recent activity.
Each item needs an owner. A hold owned by nobody quietly becomes a late payment and a vendor complaint.
Release with evidence
Before releasing a hold, confirm that the release condition is met and attach the evidence: corrected invoice, delivery confirmation, credit note, or written owner approval.
Record the release date and who approved it. Then let the bill return to the normal payment run.
Do not release and pay in the same unrecorded step. The separation is what makes the control visible.
Watch the aging
A hold list that keeps growing means the underlying intake is weak. Report the count, total value, and age of holds monthly.
If most holds come from one vendor, fix the vendor process. If they come from one buyer, check the purchase order discipline.
Communicate with vendors
A short, factual note prevents most relationship damage: "We have your invoice and are waiting for the corrected PO reference. We expect to review it on Thursday."
Set the expectation from the hold note, and keep it updated. Silence is what turns a routine hold into a collections call.
Keep the list small
Review the list weekly, close what can be closed, and escalate what cannot. A list of five current items is a control. A list of sixty is a filing cabinet.
QuickBooks VA workflow table
| Workflow area | What the VA prepares |
|---|---|
| Daily queue | Invoices, receipts, bank feeds, and open QuickBooks questions |
| Weekly review | Owner approvals, exception list, and unresolved transaction notes |
| Monthly packet | Reports, missing documents, and accountant-ready source material |
Related resources
Compare the service fit on the QuickBooks VA services page, then use the free consultation form to map the first handoff. For platform context, review QuickBooks Online.


