QuickBooks Online Collection Workflow Evidence Pack

August 23, 2026

Bottom line: give every delinquent invoice a single packet that shows its aging, contact history, promise date, message sent, and next owner decision, so follow up stays consistent instead of reactive.

Sidebar: Collections touch client relationships. Evidence and templates keep outreach consistent while decisions stay with the owner.

Why a collection packet matters for AR control

Collections often feel urgent but fragmented. One teammate remembers a promise the customer made on the phone, another sends a reminder from memory, and the aging detail in QuickBooks Online remains the only record the next reviewer can see. When follow up lives only in inboxes, the owner cannot answer whether the customer was contacted, whether the last message matched the approved language, or whether a concession was authorized.

For QBOAssistant clients, the virtual assistant typically prepares the AR hygiene layer: refreshing aging, flagging past due invoices, drafting templated reminders, logging contacts, and escalating accounts that need owner judgment. The assistant does not decide payment terms, change balances, or commit to a client about collection status. A workflow evidence pack preserves that boundary while giving the owner a predictable way to make the decisions only they can make.

The packet also protects the customer relationship. A consistent cadence with approved language prevents duplicate or contradictory asks. A documented promise date gives the customer a clear next checkpoint. And a visible escalation path ensures that accounts that truly need a call or modified terms receive it promptly rather than lingering in a generic aging bucket.

Define the scope before collecting

Start with the aging report that defines the population. Use the Accounts Receivable Aging Detail as of the review date, filtered by customer, sub-customer, and whether class or location splits apply. Save the report before starting collection actions. Record the report date, filters, preparer, and reviewer. If the business excludes certain customers from automated reminders, such as intercompany or payment plan accounts, state that scope in the cover sheet and point to the separate handling note.

Group invoices by customer and then by follow up stage rather than by invoice date alone. The useful grouping shows one customer with all open invoices sorted from oldest to newest, then tags each invoice with its current stage: on terms, first reminder queued, promise outstanding, disputed, payment plan approved, or escalated. That stage map tells the reviewer how aggressive the next message should be and who should send it.

State what is excluded. For example, credits, unapplied payments, or invoices less than the business's grace threshold may be handled in the cash application review rather than the collection packet. A clear scope note prevents a later assumption that every receivable received the same intensity of follow up.

Keep the evidence together for each invoice

For each invoice that is past due or approaching due, assemble the evidence row that the packet will carry forward. The row begins in QuickBooks: invoice number, type, issue date, due date, original amount, open amount, days past due, customer and job, terms, and current status such as sent, viewed, or overdue. Add last contact date and the user who last touched the record when history supports it.

Add the promise history: promise date, promise amount if partial, who made the promise, how the promise was recorded, and whether the promise was met. Many promises are captured in a phone note or an email thread that is not visible in QuickBooks. The packet links that external note to the invoice row so the next follow up builds on it.

Add correspondence: the template version used, the date it was sent, the channel used, and whether the message was delivered or bounced. If the business uses multiple templates, such as a friendly reminder, a firm reminder, and a formal escalation notice, record the template name and the approval for its use. If the owner asked to pause automated reminders for an account, record that instruction with the effective period.

Add the decision notes: what the VA is recommending as the next action, and what decision remains with the owner. Keep recommendation and decision in separate fields so an approved action is never mistaken for an autonomous one.

Handle the common collection scenarios consistently

No promise yet is the starting state for many invoices. The invoice is past grace and no customer commitment has been captured. Record invoice age, amount, last contact attempt, and whether contact information on file is still current. Draft the next templated message but hold it for the owner to approve for accounts that require a personal touch. A generic broadcast to every overdue balance can do more harm than good when a client has a known delay or a dispute in progress.

Promise outstanding is the state that needs close monitoring. The customer said payment would arrive by August 20, but no payment has been linked by the review date. Compare the promise amount to the open amount, check for a payment in unapplied credit that may already cover the promise, and flag the account for a targeted follow up on the promised date plus one business day. If the promise remains unmet after two cycles, escalate to the owner with a summary of prior contacts.

Disputed invoice is a third pattern that must not be treated as an ordinary collection. The customer claims the charge is wrong, a credit is pending, or delivery is incomplete. Move the invoice to a dispute hold rather than continuing with standard reminders. Record the dispute reason, the person who raised it, the supporting evidence location, and the reviewer who must decide. Standard collection language should not continue while the dispute is under ownership.

Partial payment and short pay need clarity. A customer paid 8,000 of a 10,000 invoice and shows no remittance for the remainder. Compare the payment to the invoice, check for a pending credit, a price question, or a fee deduction, and draft a polite confirmation request that references the specific amount and invoice number. Do not apply a discount or write off the residual without approval.

Payment plan approved is a controlled state. The owner has approved installments. Record the plan terms, the installment that is due now, and the next installment date. Follow up should reference the plan rather than the original due date, and any missed plan payment should trigger escalation rather than a fresh round of generic reminders.

Unreachable customer is a practical exception. Emails bounce, phone numbers are outdated, or the portal requires a credential no one can locate. Record the failed contact attempts, the addresses tried, and the recommended update to the customer master. Update access only after verification.

Build a packet the owner can act on

A useful packet is one document with links and clear ownership. Start with a cover sheet that names the business, period, aging report date and filters, preparer, reviewer, and the number of invoices in each stage. The header should tell the reviewer where effort belongs before the detail does.

Follow with the exception table, one row per invoice that requires follow up, hold, or escalation. Each row carries invoice identification, aging detail, promise history, last contact, next template proposed, evidence links, stage, and owner. A stage field such as first reminder approved, promise pending, disputed hold, plan follow up, or escalated keeps the list actionable. An owner field clarifies who must send the next message or make the next account decision.

Add a follow up calendar that shows promise dates for the next two weeks and the proposed message date for each. That calendar turns an aging list into a schedule the VA can drive day by day.

Include a holdings note that lists invoices intentionally excluded from the next reminder batch, with a reason for each hold: dispute under review, recent promise within tolerance, plan on schedule, or customer contact pause approved by the owner.

Add an escalation section that highlights accounts that have exceeded tolerance: no contact after three attempts, promise missed twice, dispute without an owner decision, or a balance that crosses the threshold the policy defines for direct owner outreach. The VA prepares the section. The owner decides whether to call, modify terms, engage finance leadership, or place the account on hold.

Cadence and quality checks

For high-volume AR clients, refresh the packet weekly. The VA pulls fresh aging, updates promise outcomes, links new correspondence, and reclassifies invoice stages before the owner's review session. For clients with few overdue balances, a biweekly cadence can be enough, supplemented by a same-day entry whenever a promise or dispute is recorded.

Archive the packet with the aging export and the correspondence log so an accountant can later verify that receivables were pursued consistently and that no balance was written off without approval.

A reviewer should be able to answer five questions after reading the packet: which invoices need outreach now, which promises are outstanding and when they expire, which accounts are on dispute hold, what language is being used, and who owns each next action. If those answers are quick, the packet is working.

Routine quality checks help. Ask whether each past due invoice was either messaged with the approved template or placed on a documented hold, whether each promise has a date and amount, whether disputed invoices were paused rather than reminded again, and whether any plan change bypassed approval. Sampling should include older invoices, recent promises, and accounts marked unreachable.

The QuickBooks bookkeeping VA service frames preparation and review boundaries for AR support. For aging presentation context, use the QuickBooks AR aging review.

What good looks like

Good looks like outreach that is timely, polite, and consistent because the evidence is together and the next step is obvious. Reminders do not duplicate. Disputes are routed rather than ignored. Promise dates provide a clear checkpoint for both the business and the customer. And the VA never has to improvise how to handle a sensitive balance.

Next step

Pilot the pack on five to seven customers who represent the range of AR situations: one current but at risk, two with one reminder behind them, one overdue with a promise, one disputed, and one not yet reachable. Build the table, link evidence locations, draft templated messages, and name one owner per row. Review the packet for readability. Keep fields that made the next action obvious, remove fields that added noise, and reuse the approved packet for the normal weekly cycle. That focused start delivers a repeatable collection workflow without changing approval authority in QuickBooks Online.