Finance / Practical guide
Overdue invoice follow-up: use the existing reminder tools first
Separate routine reminders from disputed or uncertain balances before adding AI to your collections process.
An overdue invoice list rarely needs an agent to improvise a message for every row. It needs accurate balances, clear ownership and a reliable way to exclude cases that require a conversation. Start by separating ordinary reminders from disputes, payment promises and records that have not been reconciled.
Check the built-in route
QuickBooks Online supports automatic reminders before or after an invoice's due date. Intuit says these apply to unpaid invoices already emailed to the customer. You can configure timing and message templates under Settings, Account and settings, Sales, Reminders. Manual reminders are also available. Check the current instructions for your account before changing a live setting. Read Intuit's reminder guide.
That may cover the routine task. AI becomes useful when someone needs help assembling an internal exceptions list, with evidence explaining why each case needs human attention. The following is a proposed process, not an additional built-in QuickBooks feature.
Design the exceptions list
- Choose a cutoff. Record when invoice and payment information was last checked. Do not treat yesterday's export as a current balance.
- Verify the basics. Match customer, invoice number, outstanding amount, due date and intended contact. Investigate credits, partial payments and duplicate records.
- Record the hold reason. Keep disputed work, agreed payment arrangements and uncertain payment status in a separate review queue. Check whether your reminder configuration can exclude the relevant invoice. If it cannot honor an exception, keep automatic reminders off for the affected workflow and review manually.
- Choose one sending route. Avoid having QuickBooks and a separate automation remind the same customer. Record the last action and the person responsible.
- Check again before contact. Review current payment and correspondence history. A prepared message can become inappropriate while waiting.
A fictional example
Cedar Studio has three invoices on Monday's sample list. Atlas is a routine overdue balance. Birch's project manager has recorded a dispute about the deliverable. A third client, Pine Works, says payment was sent that morning. The reviewer considers the ordinary reminder for Atlas, assigns Birch to the account owner and checks the payment claim before contacting Pine Works.
The example does not show recovered revenue or a tested automation. It shows why three apparently similar balances need different next steps.
Keep judgment with the relationship owner
Do not let an assistant invent late fees, concessions, legal language or promises about account treatment. If the records conflict, resolve them first. Measure whether the process prevents missed cases and duplicate contact, as well as the effort required to maintain it.
Bring the exception: Describe the kind of invoice follow-up that keeps falling outside your existing reminders. That is a better starting point than replacing a working feature.
These are practical workflow guides, not claims of a tested client implementation. Examples are fictional. Features, plans and availability can change; check the linked documentation before setup.
Clarify the follow-up process.
Discuss where reminders help, where disputes need a person, and what your current tools already cover.