Credit controllers stay the real control because chasing money is a relationship decision as much as a process. An AI agent can send routine reminders and draft payment plans, but the credit controller decides when to hold an account, which terms to agree and when a disputed invoice must stop being chased altogether.
What can an agent do in credit control, and at what depth?
Most of the volume. At depth 1 the agent reads the aged debt report, the sales ledger and correspondence. At depth 2 it drafts dunning letters, statement covers and payment-plan proposals for a person to send. Once certified, routine first and second reminders on undisputed invoices can run at depth 3, executed within the bounds the business sets.
Anything that commits the business sits higher or stays with a person. Agreeing extended terms, writing off a balance, placing a key account on stop, or passing a debt to collections all change a commercial relationship and are hard to walk back. Those are held for the credit controller, who is named on the decision.
Why is the disputed invoice the first test of control?
Credit control has one rule every experienced controller knows: you do not chase a disputed invoice as if it were simply late. The customer has raised a query about price, delivery or quality, and chasing them while it is open damages the relationship and can be wrong in law.
An agent will only respect that rule if it can see the dispute. If the query sits in a salesperson's inbox and never reaches the ledger, the agent will send a reminder in good faith. The controller's job is to make sure disputes are logged where the agent's sources can read them, and to spot the chase that should have been paused. That is control through knowing the process, not through clicking approve.
The same applies to partial payments, credit notes waiting to be raised and invoices sent to the wrong contact. Each looks like an overdue balance on the aged debt report. Only someone who knows how the ledger gets out of step with reality will see that the agent is about to chase the wrong thing, and fix the source rather than just the letter.
What should a credit controller check on a held item?
Held items in credit control cluster around a few decisions. The controller's checks are what make each one safe:
- Payment plans. Is the plan realistic for this customer, and does it match their history? The agent can model instalments; it cannot judge whether a director's promise on a call was sincere.
- Account holds. Will stopping supply to this customer cost more than the debt? That depends on margin, strategic value and what sales has promised.
- "Already paid" replies. A customer's emailed remittance advice is external under the Pryme Context Protocol. It is a claim, not a receipt. The controller checks the bank side before the agent's chase is cancelled.
- Tone with key accounts. A firm third reminder suits a small trade customer; it may be wrong for a large account in the middle of a contract renewal.
- Write-offs and referrals. These are always the controller's call or their manager's, under the business's own limits.
What does good training for a credit controller cover?
It starts with depth: knowing that reminder sending may be certified at depth 3 while plan agreement is held, and that depth is earned through evidence, not switched on because the controller trusts the agent. Certificates lapse after 90 days, and a run that clears no depth drops the agent to depth 1 the same day, so a controller who returns from leave to find every reminder held as a draft should know why before raising a fault.
Next comes reading verdicts. A held plan names the bound that held it, perhaps the customer's own limit on instalment length. A refused action means it was outside the agent's bounds. A withheld action is a platform decision for every agent at every depth, so no amount of asking will change it. Controllers who understand that difference waste less time and escalate the right things.
Finally, the record. Every chase, hold and approval is filed in an append-only record. If a customer complains that they were chased during a dispute, the record shows who saw the dispute, when, and what they decided. The review method in detail is set out in how credit controllers review an AI agent's decisions.
How does this sit alongside finance and credit analysis?
Credit control is downstream of credit analysis: the analyst decided the customer could have terms, and the controller now collects under them. Upstream of both sits the financial controller, who closes the books on the debt the controller reports. The same pattern runs through all three: the agent prepares, the person decides, the record shows who. Compare credit analysts as the real control and financial controllers as the real control, and see the full role map in AI agent skills by role.
Will the credit controller's job shrink?
The routine part will. Fewer hours go on sending reminders and updating chase notes; more go on the conversations and decisions that move cash. Pryme Intelligence Academy's Operator track is built for exactly this kind of daily reviewer. The question is explored further in will AI agents replace credit controllers, and the logistics market brief on training credit controllers in Australia shows how the role plays out in a sector with thin margins and many small customers.
Questions people ask
Should an agent ever place an account on stop?
Most businesses keep that decision with a person because it affects supply, sales and the relationship at once. An agent can recommend a hold and draft the notice; the controller decides and is named on it.
What if a customer argues with the agent by email?
The agent should hold the reply and route it to the controller once a conversation turns into negotiation or dispute. Arguing terms is not routine work, and a person needs to own it.
How quickly should held payment plans be decided?
Fast enough that the customer's offer is still live. A plan proposed on a call and left in a queue for a week is often worth less than one agreed that day, so plan reviewer time around chase cycles.