How to onboard a new credit controller to an AI agent workspace

For a new credit controller, the first fortnight in a team where agents chase overdue invoices and match receipts runs in two halves. First, learn exactly what the agent sends, matches and holds, and why. Then take over the held work, disputes, credit holds and unmatched cash, with a senior controller checking each decision.

What does the agent do on the sales ledger?

In a finance team with agents, the credit control agent typically sends reminder emails on a set schedule within approved templates (depth 3), matches incoming payments to open invoices (depth 2, with exact matches allocated at depth 3 where certified), drafts statements and chase letters for escalated accounts (depth 2), and flags accounts approaching or over their credit limit. It must stop chasing invoices marked as disputed, and hand over any reply that raises a complaint or a dispute.

The new controller works the held items: unmatched or part-matched receipts, disputes, customers asking for more time, accounts on stop, and requests to raise limits. How the day shifts is set out in what changes in a credit controller's day when AI agents arrive. The credit manager owns onboarding; a certified senior controller coaches.

How do the two weeks run?

1. Day 1. Person (credit manager): explains the agent's bounds: the dunning schedule, template wording, matching rules, and the triggers that stop chasing.
2. Day 1 to 2. Person (new controller): learns sources and provenance. The bank feed is sealed. Remittance advice from a customer is signed if it comes through a verified channel, external if it arrives as an unverified email. A customer saying "we paid last week" is declared.
3. Day 2 to 3. Agent, depth 2: proposes matches and chase letters, decided by the coach while the new controller follows each one.
4. Day 4. Person (new controller): works a past month in a sandbox, matching unallocated cash and deciding which accounts to escalate, then comparing with what was done.
5. Day 5. Person (new controller): reads the dispute log with the coach, learning how disputes are recorded so the agent stops chasing.
6. Week 2. Person (new controller): works live held items, each checked by the coach.
7. End of week 2. Person (credit manager): signs off solo work on matching and standard chasing. Stop and limit decisions stay with the senior controller or manager until later.

What does a new controller need to master?

Disputes stop the clock. If a customer disputes an invoice, it must be logged so the agent stops chasing it at once. A new controller who reads the dispute in an email and forgets to log it leaves the agent sending reminders on an invoice the customer has already challenged. That damages the relationship and can breach the company's own terms.

Unmatched cash is a question, not a guess. Allocating a receipt to the oldest invoice because it is the closest amount creates errors that surface months later. Ask the customer for remittance.

Credit holds affect sales. Putting an account on stop halts orders. The controller should know who in sales to tell and what the policy requires before a stop.

Context the agent cannot see. A customer may be in a long negotiation with the sales team, or an account manager may have agreed revised terms by phone. The agent chases what the ledger says. New controllers should learn which accounts carry such context and make sure it is recorded where the agent can read it, so reminders do not undercut a commercial conversation.

How do corrections feed back to the agent?

Every changed match or chase letter gets a reason: wrong invoice, remittance ignored, dispute not logged, template inappropriate, or controller judgement. "Controller judgement" covers decisions such as giving a long-standing customer more time; it should not be banked as a rule. Genuine errors go to the agent owner to change the agent's brief, sources or bounds.

Which controls and evidence should onboarding leave?

• Sandbox month. Evidence: the controller's allocations compared with actual.
• Checked decisions in week two. Evidence: both controllers named on each.
• Dispute logging tested. Evidence: a test dispute raised and the agent's chasing stopped.
• Staged authority. Evidence: dated access for matching, later for stops and limits.

What should the credit manager measure?

Misallocated receipts found after sign-off. Disputes logged within the same day. Reminders sent on disputed invoices, which should be none. Debtor days on the new controller's accounts over the first quarter. And reason quality on corrections.

Where does it usually go wrong?

Disputes left in inboxes. The agent cannot stop chasing what it does not know is disputed.

Matching by amount. Quick but wrong, and the unwinding takes longer than asking.

Treating the agent's chase as the last word. Some customers need a phone call, not a third email. Controllers keep the relationship.

The month-end close puts pressure on cash allocation, which links this role to the financial controller's; see the plan for a new financial controller and what changes in a financial controller's day when AI agents arrive. Lending teams onboard credit analysts with a different focus, covered in onboarding a new credit analyst. The wider approach is in training teams for AI agents.