How to build a collections process that actually works.

A durable collections process gives every invoice a current state, every account a next action, and every exception a named owner. It should be simple enough to run during a busy week and flexible enough to respect customer context. If the workflow depends on one person remembering whom to chase, it is not a process yet.

Define the outcome before the cadence

The goal is not to send a sequence of messages. The goal is to understand what will happen next and move the invoice toward resolution. Useful outcomes include payment received, payment committed for a date, document requested, dispute identified, contact corrected, payment arrangement proposed, or human review required.

Design the workflow backward from those outcomes. Each touch should either close the invoice or produce information that changes the next action.

Begin with billing readiness

Collections performance is constrained by invoice quality. Before launch, confirm the correct legal entity, contact, amount, due date, tax treatment, purchase order, and supporting documents. Record customer-specific requirements so they do not have to be rediscovered after the invoice is late.

• The work or delivery has been accepted.
• The billing contact and escalation contact are current.
• Required references and documents are attached.
• The customer knows how and where to pay.
• Any account-specific communication restriction is visible.

Create states, not just aging buckets

Age matters, but it does not describe the work. Two invoices at 35 days overdue may need different actions. One is awaiting a payment run; the other has never received a response. Add operating states such as:

• Ready for routine reminder.
• Silent after reminder.
• Call required.
• Promise to pay active.
• Document requested.
• Disputed or commercially sensitive.
• Human handoff pending.

Use a channel policy that can change

Email is efficient for confirming receipt, sharing documents, and preserving a written record. Voice is better when the customer is silent, the reason for delay is unclear, or a commitment needs to be established. A practical cadence uses both without treating every account identically.

If there is no response to a courteous reminder, the next action can be a call rather than a third rewritten email. If the customer requests a statement during that call, send it and schedule a specific check-back date. The policy follows the signal.

Define agent boundaries before automation

An AI voice agent should know the approved calling hours, tone, account exclusions, maximum attempts, information it may share, and situations that require a person. Disputes, threats, legal questions, sensitive customers, and commercial negotiations should route to a named owner.

Make ownership explicit

Every handoff needs a person, a reason, and a due date. “Sales to review” is not sufficient. “Account owner to confirm disputed service line by Thursday” is actionable. The workflow should notify the owner and pause inappropriate outreach until the issue is resolved.

Run a short weekly operating review

1. Review large balances with no recent meaningful contact.
2. Confirm promises due or missed this week.
3. Assign disputes and document requests without an owner.
4. Investigate accounts repeatedly moving between states.
5. Approve any change to cadence or agent policy.

Measure whether the process creates movement

• Invoices with a valid next action.
• Time to first meaningful customer response.
• Commitments captured and commitments kept.
• Exceptions resolved within the expected time.
• Cash collected by aging band and account segment.
• Manual hours required per resolved invoice.

Start with a controlled queue and review outcomes closely. Once the team trusts the states, conversations, and handoffs, expand coverage. A collections process works when routine follow-up continues without prompting and unusual cases reach a person early enough to matter.