Credit control teams should drill a failure that damages customer relationships fast: the agent sends final demands and stop-supply warnings on invoices that customers have already disputed. In a tabletop of about an hour, credit controllers practise pausing the agent to draft-only, escalating to the finance lead and sales, recording decisions, and repairing relationships account by account.
Why does credit control need a drill?
Credit controllers chase business customers for unpaid invoices. Agents typically send routine statements and first reminders at depth 3 within bounds, draft escalating letters at depth 2, and hold any account with a disputed invoice or a key account flag for a person. A credit controller's decisions protect cash flow, but a wrong final demand to a large customer can cost more than the invoice.
The financial controller or credit manager owns the drill. A senior credit controller facilitates. Credit controllers, a sales account manager and someone from finance systems take part. For the general idea, see what an incident drill is.
The scenario
Monday, 08:45. A key customer's finance director emails the sales director, furious. Over the weekend the credit control agent sent his company a final demand and a stop-supply warning for three invoices his team disputed a month ago. A credit controller checks the ledger: dispute flags were cleared by a month-end clean-up script, so the agent saw the invoices as simply overdue. About 40 customers with disputes received escalated letters; some letters warned of supply being stopped.
The drill step by step
- Person (facilitator): reads the scenario and starts the clock.
- Person (sales director, played by a participant): forwards the complaint to the credit manager. The test: how fast does it reach someone who can act?
- Person (credit manager): pauses the agent to draft-only. The business's own limits are tightened so every statement and reminder is held. The agent drops to depth 2.
- Person (credit manager): escalates to the financial controller and finance systems. Finance systems confirms what the clean-up script did.
- Person (credit controller): lists affected accounts from the record, cross-checked against the dispute log kept outside the ledger.
- Person (financial controller): confirms no supply was actually stopped. If an order hold was placed by another system based on the agent's letter, it is released.
- Person (credit manager and sales): decide on contact. Account managers call key customers; credit controllers write to the rest with an apology and confirmation that disputes stand.
- Person (credit manager): records each decision with owner and time, and decides on internal reporting to the finance director.
- Person (facilitator): runs the debrief.
| Step | The agent does | Depth | Stays with a person |
|---|---|---|---|
| Complaint | Has sent escalated letters | 3 | Routing the complaint |
| Pause | Holds every letter | Dropped to 2 | Tightening limits |
| Escalate | Nothing new | 2 | Finance systems check |
| Scope | Nothing new | 2 | Listing accounts from the record |
| Supply check | Nothing | 2 | Releasing any order holds |
| Contact | Drafts apology letters | 2 | Calls to key customers |
| Record | Files verdicts | 2 | Decisions and reporting |
What is specific about credit control incidents?
Two things. First, the source of truth was split. Disputes lived partly in the ledger and partly in a separate log. The agent read the ledger, which is sealed, and could not see the log. The debrief should decide where disputes are recorded and make sure the agent reads that source.
Second, the relationship cost falls on sales. Credit control and sales must rehearse together, because the calls that repair the relationship are made by account managers, not credit controllers.
The drill should also test tone. Credit controllers are used to firm language, and the apology letters they draft under pressure often read like reminders with an apology added. Have the sales account manager read each draft aloud in the exercise. If it would annoy a customer who has just been threatened with a supply stop, it needs rewriting before it goes out, whoever drafted it.
Which controls does the drill test, and what evidence do they leave?
The pause. Evidence: the limit change in the record.
Change control on data clean-ups. A script that clears flags the agent depends on is a change to the agent's sources. Evidence: an agreed rule that finance systems tells the credit manager before running such scripts.
Contact decisions. Evidence: a contact list showing who called or wrote to each customer.
Order holds. Evidence: any hold released, with the name of the person who released it.
What should the credit manager measure?
- Minutes from the complaint reaching the business to the pause.
- Completeness of the affected list.
- Time until every key customer had a call.
- Whether any supply was stopped, and how fast it was restored.
Where do credit control drills go wrong?
Credit control works alone. Without sales and finance systems, the team can pause the agent but cannot fix the source or the relationships.
Fixing the flags and resuming. Restoring the dispute flags is necessary. Checking the next batch of letters before restoring depth 3 is what prevents a repeat.
Treating it as a technical glitch. Customers experienced it as a threat. The response should match that.
Credit control has close neighbours: the credit team drill covers lending decisions, and the claims team drill covers payments to customers. New reviewers can learn the incident steps through the reviewer onboarding checklist for a credit control team. For the training behind the drill, see how to train a team to handle an AI agent incident and training teams for AI agents.
Questions people ask
Should the agent ever send a stop-supply warning on its own?
Most businesses keep stop-supply warnings at depth 2 for a credit controller to approve. They carry commercial weight and are hard to take back.
Who owns the dispute log?
Decide that in the debrief. Whoever owns it must also own making sure the agent reads it.
How often should credit control drill?
Twice a year, and after any change to month-end processes or ledger clean-up scripts.