The sales ledger becomes something an agent works through every morning before the credit controller logs in. Controllers should learn how far the agent may act on chasing, cash allocation and disputes, why a customer’s remittance note is only a claim, which account decisions are always held for them, and how to review the agent’s drafts without redoing them.
What will the agent do on the ledger?
The repetitive work that fills a controller’s day.
| Credit control task | Depth | The controller’s part |
|---|---|---|
| Reading the aged debt, payment history, remittances and correspondence | 1, read | None |
| Drafting reminders, statements and replies to queries | 2, draft | Checks and sends, at first |
| Sending routine reminders in approved wording; allocating cash that matches exactly | 3, within bounds | Samples |
| Placing an account on stop, raising a limit, writing off | Held | Controller or manager decides |
Most firms begin with reminders at depth 2 and move them to depth 3 once certification on their own past ledger supports it. Depth is earned, not configured. Certificates lapse after 90 days, and a run that clears no depth drops the agent to depth 1 the same day, so the morning chase can come back to people without much warning.
Why is a remittance note only a claim?
Because provenance decides how much weight a fact carries. Every fact reaching a governed agent is stamped:
- Sealed: from the firm’s own systems, such as the sales ledger or bank feed.
- Signed: a named party answers for it, such as a credit insurer’s confirmation.
- Declared: what the customer says, such as “payment sent Tuesday” or “invoice disputed”.
- External: from outside, such as an emailed remittance advice.
A customer’s remittance claiming they paid three invoices is external until the bank feed shows the cash. An agent will not allocate cash on the remittance alone; it waits for the sealed bank line. Controllers should apply the same discipline when they review, especially at month-end when pressure to clear the ledger is high.
How does the decision chain help a controller?
Every action meets five bounds: the agent’s role scope, its certificate, its sources, the firm’s own limits (such as chase cadence, tone rules and account thresholds) and the platform guardrails. The lowest wins, and the verdict names the bound that decided. A reminder held because the customer has an open dispute is held by the firm’s limits. One held because the bank feed is late is held by sources. The controller deals with each differently.
Which account decisions stay with the controller?
Stopping supply to a customer, changing a credit limit, agreeing extended terms, accepting a part-payment in settlement, referring a debt to an agency or lawyers, issuing credit notes beyond a small threshold, and writing off. These carry commercial weight. A stop on a key logistics customer can halt their operations and the relationship with it. The agent can prepare the case with the facts; the controller decides with the sales team.
How should a controller review the agent’s drafts?
Quickly for the routine, carefully for the rest. For reminders, check the tone and the facts on a sample. For dispute replies, read the customer’s point and the evidence the agent cited, and check it is not dismissing a fair complaint. For proposed allocations that do not match exactly, check the bank line and the invoices before approving.
When you change something, say why in a short note. Those notes are how the agent’s brief and sources improve before its next certification.
What does a morning look like in a logistics firm?
Take a credit controller at a freight forwarder with several hundred trade customers. Overnight, the agent sent routine reminders, allocated most of yesterday’s receipts, and held a short list. One customer’s remittance claims payment of an invoice the bank feed does not show. Another has emailed disputing a demurrage charge; the agent drafted a reply citing the contract clause but held it because disputes are outside its limits. A third has gone over their credit limit with a large booking waiting. The controller chases the missing payment, checks the demurrage evidence with operations, and calls the sales lead about the limit before deciding.
How do other roles and markets compare?
Credit controllers sit between finance and credit; see what financial controllers should learn first and what credit analysts should learn first. Practice differs by country: compare credit controller training in Australian logistics and German logistics. Why controllers are the safeguard is argued in why credit controllers are the real control. The overview is in AI agent skills by role.
Questions people ask
Will the agent call customers?
Usually not at first. Written reminders and statements suit agents; calls about difficult debts suit people.
Can the agent allocate part-payments?
Where the remittance and bank line agree, within rules. Where they do not, it holds the item for the controller.
What happens to the relationship with customers?
Routine chasing becomes more consistent, which customers often prefer. Controllers have more time for the conversations that need a person.