On this page Jump to section
QuickBooks Online can send automatic payment reminders on a schedule the business chooses, but the schedule is only useful if someone reviews it before the messages leave the account. A reminder that reaches a customer who already paid, or who is waiting on a disputed line, creates a support problem rather than a collection result. The bookkeeping VA should treat reminders as customer-facing output, not as a background setting. This review routine checks the audience, the timing, the template, and the stop conditions before each reminder cycle runs.
Map which invoices are eligible for reminders
Start with the open invoice list and identify which balances will receive a reminder under the current schedule. Separate current invoices from past-due invoices and from those with a partial payment or an unapplied credit. A reminder aimed at the full invoice amount when only a small balance remains looks careless to the customer. Export the list before the cycle and mark the accounts that should be excluded, so the review has a record.
Check the reminder schedule against payment terms
Compare the reminder days with the payment terms on each invoice, because a net-30 customer should not receive the same sequence as a due-on-receipt customer. Look for a reminder that fires before the invoice due date or immediately after a holiday weekend. Confirm the schedule uses business days where the customer expects them, and record any invoice whose terms were overridden. The schedule should follow the terms in the transaction, not a single company-wide default.
Review the email template and sender identity
Read the reminder template as a customer would, including the subject line, greeting, amount, due date, and payment link. Confirm the sender name and reply-to address belong to the business and that the signature names a real contact. Remove language that threatens action the owner has not approved, such as suspension of service or referral to collections. The template should state the balance, the original due date, and a simple way to ask a question.
Confirm the customer contact and billing address
Check the primary contact, billing email, and billing address on the customer record before the cycle runs. A reminder sent to a former employee or a shared inbox may never reach the person who approves payment. Compare the record with the latest purchase order or vendor onboarding form and note the source of any change. If two contacts are valid, use the billing contact and keep the second as a copy only when the customer asked for it.
Test the reminder on invoices with partial payments
An invoice with a partial payment needs a reminder that shows the remaining balance, not the original total. Open a test invoice, apply a small payment, and confirm the reminder preview uses the updated amount. Check whether an unapplied credit reduces the balance or sits unused while the reminder asks for the full amount. Record the result, because a misleading balance is the fastest way to trigger a customer dispute.
Exclude disputed and promised-payment accounts
Hold reminders for invoices with an open dispute, a pending credit, or a documented promise to pay. The collection log should show the promise date and the person who made it, so the reviewer can decide whether the promise has passed. Sending a reminder during an active dispute tells the customer that no one is reading the account history. Release the hold only when the dispute closes or the promise date passes without payment.
Decide who owns the pause and escalation
Give one named person the authority to pause a reminder and another person the authority to approve a manual follow-up. The VA can prepare the exclusion list and draft the message, but the owner should approve changes to the schedule or the template. Record the approver and the date beside each exception, especially when a large balance is involved. Separation keeps a routine reminder from becoming an unauthorized collection action.
Leave an audit note for every reminder change
Write a short note whenever the schedule, template, sender, or audience changes. Include the old value, the new value, the reason, and the person who approved it. Attach the note to the reminder settings record or keep it in the close file, not in a private inbox. A later reviewer should be able to explain why a customer received a reminder on a particular day.
Measure whether reminders create support noise
Track replies that ask what the reminder is about, complaints about tone, and payments that arrive after a reminder. Compare the volume with the number of reminders sent, and review a sample of replies each month. A high question rate may mean the template is unclear, while a high complaint rate may mean the schedule is too aggressive. Use the pattern to adjust the sequence rather than blaming the customer.
Keep the review inside the collection workflow
The reminder cycle should connect to the same records the team uses for payment application and dispute handling. If a customer replies with a remittance, route it to the person who applies cash rather than answering from the reminder inbox. If a customer disputes a line, pause the sequence and open a case with the invoice, the source document, and the expected resolution. A reminder is only one step in the collection process, not a substitute for reading the account.
Review the reminder cycle before it runs, not after a customer complains. Confirm the audience, the terms, the template, the contact, and the hold list, then record who approved the change. Link the review to the customer payment application workflow and the accounts receivable collections board so the reminder fits the rest of the collection process. For platform guidance, use Intuit's QuickBooks Online help center.
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.
