For a credit control team working with an AI agent that chases debts, this competency matrix lists the eight skills that decide whether its held proposals are handled well: disputes, account stops, cash allocation, write-offs and credit notes among them. It sets four levels, asks for the evidence behind each rating, and shows who holds what. Template and example follow.
Why does credit control need a matrix now?
Because the agent takes the volume and leaves the judgement. In a typical deployment, it sends routine reminders within rules at depth 3, drafts escalation letters at depth 2, and holds the actions that can damage a customer relationship or the ledger: putting an account on stop, releasing a stop, agreeing a plan, raising a credit note, writing off a balance. Those are exactly the decisions where a weak controller costs money or a customer.
The argument that credit controllers are the real control in this kind of deployment is made in why credit controllers are the real control in an AI agent deployment. The matrix is how you check the control is staffed.
How do you fill it in?
- Rate each controller as Learner, Practitioner, Approver or Lead on each skill.
- For Approver or Lead, name the evidence in the "evidence" column: a practicum log reference, a quality sample, an assessment result.
- Add credentials and expiry dates.
- Total the Approvers per skill and check the reviewer rota for the credit control team has at least one on every working day.
Levels: Learner (knows the skill exists and why); Practitioner (does it with a countersignature); Approver (decides held items alone, within limits); Lead (sets limits, assesses others, handles escalations from sales or directors).
The competency matrix template
Skills
| Code | Skill | What an Approver does |
|---|---|---|
| CC1 | Disputes | Pauses chasing on disputed items only, keeps chasing the rest, and gets the dispute resolved |
| CC2 | Account stops | Decides stops on customer value and history, not only on days overdue |
| CC3 | Cash allocation | Releases stops on cash shown in the bank feed (sealed), never on a remittance (external) alone |
| CC4 | Write-offs and credit notes | Approves within limits with documented reasons |
| CC5 | Trade payment plans | Agrees plans within policy and records the customer's commitment |
| CC6 | Reading verdicts | Explains why the agent held or refused an item, from the workspace |
| CC7 | Sales escalations | Handles requests from sales to lift stops, with the reason recorded |
| CC8 | Teaching the agent | Submits corrections with sources, such as an updated credit limit or customer contact |
Who holds what
| Controller | Role | CC1 | CC2 | CC3 | CC4 | CC5 | CC6 | CC7 | CC8 | Evidence | Credential | Expires |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
A worked example
Take a sample electrical wholesaler's credit control team of four. Values are illustrative. L, P, A and Ld for the four levels.
| Controller | Role | CC1 | CC2 | CC3 | CC4 | CC5 | CC6 | CC7 | CC8 | Evidence | Credential | Expires |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| G. Moran | Credit manager | Ld | Ld | A | Ld | Ld | A | Ld | A | Practicum log PL-11; annual review | Operator certificate | 31 Jan |
| E. Tran | Senior controller | A | A | A | A | A | A | P | P | Practicum log PL-14 | Operator certificate | 30 Jun |
| B. Owusu | Controller | A | P | P | P | A | A | P | L | Quality sample QS-3 | None | |
| J. Lake | Controller | P | P | L | P | P | P | L | L | None yet | None | |
| Approvers or above | 3 | 2 | 2 | 2 | 3 | 3 | 1 | 1 |
Three findings. CC3, cash allocation, has two Approvers: on a day when both are out, stops can only be released by someone who may trust a remittance. CC7, sales escalations, rests on the credit manager alone, which is why sales requests stall when G. Moran is on leave. And B. Owusu is an Approver on disputes and plans, with evidence, but holds no certificate.
The plan: E. Tran shadows G. Moran on sales escalations for a month; B. Owusu completes a certified practicum, after which the approver rule for the credit control team can grant release rights on stops; J. Lake starts supervised work on CC3. Credit teams that lend rather than collect use a related matrix with different skills; compare the competency matrix for a credit team and the matrix for a lending team.
Where the Academy fits
Pryme Intelligence Academy's Certified Pryme Operator requires a written exam and a two-week practicum of real review decisions, signed off by a Pryme assessor, which is solid evidence for Approver on CC1 to CC6. A business can make a controller's right to release stops or approve write-offs depend on a current certificate. See AI agent skills by role.
Questions people ask
Should salespeople be on the matrix?
No, but the matrix should show who in credit control can handle their requests. Sales pressure to lift stops is a skill in its own right for controllers.
Does a certificate automatically make someone an Approver?
No. It is strong evidence for some skills, but local ones such as CC7 still need evidence from your own operation.
What happens to ratings when a controller's certificate lapses?
Ratings that depend on it, such as releasing stops, drop to Practitioner the same day and return when the renewal shows as current at source.