AR collections follow-up that sounds like your team, not a dunning robot

Collections often happens in the gaps of an AR specialist's week, using the same reminder template for a reliable customer who forgot and a struggling one who is avoiding you. An agent can read each account's context, draft the right message, and keep the follow-up cadence that people let slip.

01the problem and who owns it

Generic dunning emails go out on a schedule, customers ignore them, and the real follow-up depends on someone remembering to call. Meanwhile the reason an invoice is unpaid is often sitting in an email thread: a missing PO number, a disputed line, a new AP contact. Until someone reads that thread, the invoice just ages.

Finance owns days sales outstanding and cash, but the customer relationship belongs to sales or account management, who worry that aggressive collections will damage renewals. Both sides need to see the same picture.

02what the AI does, step by step

1. Build the worklist dailyThe agent pulls open invoices from the accounting system and ranks them by amount, days overdue, customer payment history, and any upcoming renewal or order, so the largest and riskiest balances surface first.
2. Read the account contextFor each customer it reviews the recent email threads, prior promises to pay, open disputes, and notes in the CRM, then summarizes why the invoice is likely unpaid, such as missing PO, wrong billing contact, or disputed line.
3. Draft the right follow-upMessages are drafted in your team's voice, tailored to the situation: a resend with the PO number attached, a question to a new AP contact, or a firmer note for repeat late payers. Each references the specific invoices, amounts, and due dates.
4. Capture replies as structured dataWhen a customer answers, the agent extracts promised payment dates, disputes, and requests for documents, and records them on the account so the next action is scheduled automatically.
5. Route disputes and escalationsBilling disputes go to whoever can fix the invoice; relationship-sensitive accounts go to the account manager with a summary; balances past your escalation threshold go to the controller with a recommended next step.
6. Report the state of receivablesA weekly summary shows aging movement, promises kept and broken, disputes by cause, and accounts needing a call from a person.

03systems it connects to

• Accounting or billing system. QuickBooks, Xero, NetSuite, or a billing platform holding invoices and payments.
• Email. The AR mailbox, where most of the useful context about unpaid invoices lives.
• CRM. Salesforce or HubSpot, for account owners, renewals, and relationship notes.
• Payments. Payment links or a customer portal so paying is easy once the customer is ready.

04human checkpoints

• Message approval. AR approves drafts before they go out, and may later allow first-stage reminders to send automatically for low-risk accounts.
• Account manager review. Strategic accounts and anything above a set balance get the account manager's eyes before escalation language is used.
• Credits and write-offs. Any credit memo, payment plan, or write-off requires approval from someone with that authority, never the agent.

05what to measure

• Days sales outstanding. Trended monthly, alongside the aging buckets.
• Promise-to-pay reliability. Share of promised payments received by the promised date.
• Dispute cycle time. Days from dispute raised to resolved, by cause.
• Customer complaints. Any pushback about collections tone, tracked to protect relationships.

06risks and guardrails

• Consumer debt rules. If any receivables are owed by consumers rather than businesses, debt collection laws such as the FDCPA and state rules may apply to how and when you contact them. Review the approach with counsel before automating consumer outreach.
• Wrong amounts. A follow-up quoting a balance that was already paid erodes credibility. Pull invoice status live at send time, not from a morning snapshot.
• Separation of duties. The person who applies cash and issues credits should not be the only reviewer of collection outcomes. Keep credit authority separate from the collections workflow.

07build vs buy

AR automation tools such as Chaser, Upflow, Versapay, and the collections modules in larger ERPs handle reminder cadences, portals, and aging dashboards. For straightforward B2B receivables, those cover most needs.

A custom agent is worth building when the reason invoices go unpaid lives in email threads and CRM notes those tools do not read, or when collections must be coordinated closely with account management because receivables and renewals are tied together.

08related playbooks

Browse every finance and accounting playbook or the full library.