Anchor the credit control rota to the dunning calendar and month-end. Those are the days the agent's holds peak: disputed invoices, proposed account stops, requests for more credit and payment plans. Keep key accounts with their own controller and put a credit manager on the rota for stops.
Set response targets so every dispute is resolved before the next reminder goes out, and limit changes are decided before the customer's next order needs them.
What does a credit control rota cover?
A credit control agent sends statements and reminders on schedule, allocates incoming cash, chases overdue invoices and proposes the next step when a customer stays overdue. It holds what affects the customer relationship or the organisation's exposure: disputes raised against invoices, proposed account stops, credit limit changes, payment plans outside policy and referrals to an external collector. Those decisions belong with people who know the customer.
The credit manager owns the rota; the finance director agrees who may stop an account or raise a limit. The guide to AI agent skills by role covers what credit controllers need to know, and what a reviewer rota is explains the basic idea.
What are the steps?
- Agent, depth 1: reports holds by type, customer and date. Pull a few months to see the dunning-day and month-end peaks.
- Person (credit manager): sets response targets. Disputes resolved before the next scheduled reminder, so the customer is not chased for an invoice they have challenged; proposed account stops decided within one working day; limit requests within two; payment plans within one.
- Person (credit manager): assigns portfolios. Each controller owns a set of customers. Key accounts stay with their controller even on peak days.
- Person (credit manager): names cover for each portfolio. A backup controller who knows the accounts well enough to decide a dispute.
- Agent, depth 3: sends reminders and statements on schedule. Paused automatically on any invoice under dispute.
- Agent, depth 2: drafts the case for each proposed stop or limit change. Payment history, current exposure, any dispute, and the source of each figure.
- Person (controller): decides disputes and payment plans. With a reason, and a note to sales where the dispute concerns a sale.
- Person (credit manager): decides account stops and limit changes. On the rota as a named approver every working day, with a deputy.
| Step | The agent does | Depth | Stays with a person |
|---|---|---|---|
| Statements and reminders | Sends on schedule | 3 | Sampling tone and accuracy |
| Cash allocation | Allocates clear matches | 3 | Unmatched receipts |
| Disputes | Pauses reminders, holds | 2 | Resolving with customer and sales |
| Payment plans | Drafts within policy, holds outside | 2 | Approval outside policy |
| Account stops | Drafts the case and holds | 4 | Decision by the credit manager |
| Credit limit changes | Drafts the case and holds | 2 | Decision within authority |
Why should account stops sit with a named approver?
An account stop is the credit control action most likely to damage a customer relationship and hardest to take back quietly. Orders stop, the customer's operations may be affected, and sales will hear about it within the hour. Treat it as a depth 4 action: the agent drafts the case, a named person decides.
That person must be on the rota every working day, because a stop delayed is exposure growing. It is also why the reviewer is the control, not the agent: the agent can see the numbers, but only a person can weigh a long relationship, a promised payment and a disputed invoice together.
Which controls matter, and what evidence do they leave?
- Reminders pause on dispute. Evidence: the pause timestamp and no reminders sent for that invoice while the dispute is open.
- Stops and limit changes have a named approver. Evidence: the approver and the limit that applied, on the verdict.
- Portfolio ownership is visible. Evidence: each decision names the controller, and cover decisions note the handover.
- Figures are sourced. Cash received is sealed by the bank feed; a customer's statement that payment "was sent yesterday" is declared. Evidence: provenance on the case for each stop.
- Sales is told. Evidence: the notification recorded with each stop or dispute.
What should be measured?
- Disputes resolved before the next reminder date.
- Stops decided within target, and stops later reversed.
- Days sales outstanding by portfolio, read alongside dispute volume.
- Payment plans kept versus broken, by approver.
- Reminders sent on disputed invoices: the target is none.
Where does it usually go wrong?
The rota ignores the dunning calendar. If reminders go out on the first working day of the month, disputes arrive on the second and third. Staff those days.
Key accounts go to whoever is free. A cover controller who does not know the account approves a stop the owner would have avoided with a phone call.
Sales pressure on stops. Sales teams lobby to lift stops. The rota should make clear who decides, and the record should show their reason.
Credit and payroll teams staff their queues with the same method; compare the rotas for the credit team and the payroll team. The AI agent competency matrix for the credit control team shows who is ready to cover a portfolio.
Questions people ask
Can the agent put an account on stop automatically?
It can be given that capability, but most organisations keep stops held for a person because of the relationship cost. If you allow it, certify the capability on your own cases first and set a low bound.
How many portfolios should one controller cover on a peak day?
Their own, plus at most one they back up. Beyond that, cover becomes unfamiliar and decisions become mechanical.
Who resolves a dispute that turns on what sales promised?
The controller gathers the evidence, and sales confirms what was agreed. The controller decides, and the record holds both.