QuickBooks receivables automation

QuickBooks Online already has automatic invoice reminders. Start there if your service business needs a polite email before or after an invoice is due. Add a separate accounts receivable workflow when someone still has to check payment status, pause a disputed invoice, coordinate follow-up in the CRM or assign a difficult account to a person.

A useful first question is: what does your team do after the reminder goes out? If the answer is nothing until the customer pays, the built-in settings may be enough. If staff compare QuickBooks with email replies and a spreadsheet every morning, that handoff is the part to automate.

We checked Intuit's US help page, Send invoice reminders automatically or manually in QuickBooks Online, on November 2, 2026. The QuickBooks settings below come from that page. The queue and approval rules are the workflow we would design around it, not extra features we claim QuickBooks provides by default.

In QuickBooks Online, go to Settings, Account and settings, then Sales. Edit the Reminders section and turn on Automatic invoice reminders. Choose the number of days before or after the due date for each reminder. Intuit documents up to three reminders, scheduled up to 90 days before or after the invoice due date.

Edit the subject, greeting and message for each reminder. Use the available invoice and company variables instead of copying an amount into a fixed template. Check the recipient and payment instructions before enabling the sequence. Intuit also documents a manual Send reminder action on individual invoices and a separate workflow option for QuickBooks Online Advanced.

Two limits matter when you review the setup:

• QuickBooks sends these reminders only for invoices you have already emailed.
• The invoice must match the reminder timing and remain unpaid.

An invoice entered into the books but never emailed is a different problem from a customer ignoring a reminder. Check the original send step before buying another collections tool. This guide covers QuickBooks Online; do not apply its menu paths to QuickBooks Desktop.

Our QuickBooks integration page covers the connection's data and authorization boundaries. For the wider practice workflow, see accounting firm workflow automation.

For a service business using QuickBooks and a CRM, we would keep the invoice and its recorded balance in QuickBooks. The CRM would show who needs to follow up, when and why. It would not become a second place to edit what the customer owes.

Each queue item would carry the connected QuickBooks company, invoice ID, customer match, current balance, due date, last reminder, next permitted contact time and responsible person. It would also carry an explicit hold reason when follow-up must stop. Using the invoice ID avoids matching two invoices merely because they have the same amount or customer name.

An illustrative sequence looks like this:

1. 1Read invoices eligible under the business's agreed reminder policy through an authorized connection.
2. 2Confirm that the original invoice was sent and the customer mapping is unambiguous.
3. 3Check the current recorded balance, any hold, the last contact and the next allowed contact time.
4. 4Create a CRM task or prepare an approved reminder. Give one system responsibility for sending that stage.
5. 5Immediately before sending, read the invoice state again. Stop if it was paid, voided, changed or put on hold.
6. 6Record the send result and move unresolved exceptions to the named staff member.

That last check matters because a queue can become stale between the morning sync and an afternoon email. If the accounting connection is unavailable, pause the send and alert the owner. A saved balance from yesterday is not enough evidence for a new payment demand.

A customer's "I paid" reply should pause the automatic chase while staff check it. It should not mark the invoice paid in the books. A partial payment needs a current balance check and the business's own rule for the remaining amount; it should not restart the full original demand.

A single overdue label hides several kinds of work. Give staff a queue that distinguishes them:

• The invoice was never sent, or the email bounced. Check delivery and the billing address.
• The customer disputes an amount or the service. Assign the account owner and pause reminders.
• The customer reports a payment that is not reflected on the invoice. Ask the bookkeeper to reconcile it.
• A credit, void or changed invoice makes the saved reminder wrong. Refresh the balance and review the message.
• A promised payment date or agreed plan changes the next contact. Record who approved it and when to review it.
• The connection or sender fails. Keep the item open with the error and the next person responsible.

Keep notes relevant to collections and restrict access to the people who need them. An error alert can name the invoice and link to the secured record without copying a customer's full financial history into a chat channel.

Enabling a CRM sequence alongside QuickBooks reminders can produce duplicate contact even when both tools work correctly. Before launch, list every sender: QuickBooks, the CRM, an accounts receivable app and staff email. Assign one owner to each stage and check how to exclude invoices already handled elsewhere.

The custom workflow also needs a durable record of each attempted reminder. If the email service times out after accepting a message, check its delivery record before retrying. A timeout does not prove that nothing was sent. Our guide to webhook idempotency explains how duplicate triggers and uncertain outcomes should be handled.

If an invoice changes after a reminder was prepared, discard the draft and prepare it again from the current record. Do not let a retry use an old balance or carry over approval for a different amount.

A reminder workflow can move a record, send agreed wording and assign a task. Write-offs, credits, refunds, new fees, collection escalation and payment-plan changes need the business's authorized reviewer. Receiving a customer email is not approval to alter the books or terms.

AI may help summarize a reply or draft a response when the business has approved that use. It should not decide whether a disputed fee is valid or invent a promise about a payment. Fixed rules are easier to inspect for routine reminder timing. Our finance approval guide describes the separate approval path for changes that affect money or accounting records.

Before allowing unattended sends, run the proposed queue without sending messages and have staff compare its decisions with their own. Include an unpaid invoice already emailed, an unsent invoice, a paid invoice, a partial payment, a dispute, a void, an incorrect customer match and an unavailable connection.

Then test the awkward timing: record a payment after the queue is built but before the send; deliver the same trigger twice; interrupt the sender after it accepts an email. Confirm that the right message is held or sent once, and that unresolved cases remain visible to their owner. A green run log alone cannot prove the customer received the right reminder. See automation error alerts for checks on failed runs and workflows that quietly stop producing anything.

Measure from your own starting point: staff time spent preparing follow-up, duplicate reminders, disputed accounts chased by mistake and exceptions waiting for review. Track invoice aging too, but do not attribute every payment change to automation; customer behavior and billing terms affect it.

If the built-in sequence covers your timing and one person can handle the few exceptions, keep that setup. A separate integration adds connection maintenance, sender coordination and another queue to manage. It earns its place when repeated cross-system checks or missed handoffs cost more than that upkeep.

For a scoped review, send us the tools involved, approximate invoice volume, current reminder schedule and one anonymized example of an exception. Leave bank details, passwords and customer documents out of the initial message. Through our free automation audit, we can help identify whether QuickBooks settings are enough or whether a small systems integration would remove the repeated checks.