An accounts payable team's AI agent competency matrix lists the skills needed to work with an invoice agent, defines four levels for each, and shows who in the team holds which level today. Use it to plan training, set who may release held payments, and check that every payment run has enough certified cover. A filled example follows.
What is the matrix for?
It turns "the team is trained" into something you can check. An AP team working with an agent does different work from one keying invoices: the agent matches invoices to purchase orders and receipts, posts within tolerances at depth 3, and holds variances, duplicates and bank-detail changes for a person. Payment release is depth 4. The skills that matter are reading those holds correctly and knowing which ones must never be waved through.
A matrix shows where those skills sit. If only one clerk can confidently handle supplier bank-detail changes, that is a single point of failure the matrix makes visible. It also feeds two related documents: the approver authority matrix for the accounts payable team, which says who may approve what, and the reviewer rota, which needs enough qualified people on each day.
How do you fill it in?
- List the skills (rows in Table 1). Keep to eight to ten.
- Define four levels for each skill in plain terms, so two managers would rate the same person the same way.
- Rate each person against each skill (Table 2), using evidence: an assessment, a practicum log, observed work. Not self-rating alone.
- Add each person's credential and its expiry, because level 3 for payment release should depend on a current certificate.
- Count coverage: how many people at level 3 or above per skill. Flag any skill with fewer than two.
Levels used here: 0 not yet; 1 aware (can explain it); 2 supervised (does it with a countersignature); 3 independent (does it alone, certified where required); 4 coach (assesses and teaches others).
The competency matrix template
Table 1: skills
| No. | Skill | What level 3 looks like |
|---|---|---|
| 1 | Reading a verdict | States which bound held an invoice and why, from the workspace |
| 2 | Three-way match variances | Decides price and quantity variances against PO and receipt within tolerance rules |
| 3 | Duplicate detection | Identifies true duplicates, including changed dates or references |
| 4 | Provenance of supplier data | Knows an emailed bank-detail change is external and cannot authorise payment; verifies by known channel |
| 5 | Releasing held payments | Releases depth 4 payments within limit, with reasons |
| 6 | Upholding refusals | Explains why a refusal stands and routes the item correctly |
| 7 | Teaching the agent | Submits corrections with sources when the agent repeats an error |
| 8 | Agent certificate events | Knows a run that clears no depth drops the agent to depth 1 the same day, and what that does to the queue |
Table 2: who holds what
| Person | Role | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | Credential | Expires |
|---|---|---|---|---|---|---|---|---|---|---|---|
| People at level 3 or above |
A worked example
Take a sample distributor's AP team of five. Values are illustrative.
| Person | Role | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | Credential | Expires |
|---|---|---|---|---|---|---|---|---|---|---|---|
| M. Hale | AP supervisor | 4 | 4 | 4 | 4 | 4 | 3 | 3 | 3 | Operator certificate | 30 Nov |
| D. Price | Senior clerk | 3 | 3 | 3 | 3 | 3 | 3 | 2 | 2 | Operator certificate | 31 Jul |
| S. Khan | Clerk | 3 | 3 | 2 | 2 | 2 | 2 | 1 | 1 | Foundations badge | No expiry |
| R. Lowe | Clerk | 2 | 2 | 2 | 1 | 0 | 1 | 1 | 1 | None | |
| F. Ito | Clerk (new) | 1 | 1 | 1 | 1 | 0 | 1 | 0 | 1 | None | |
| At level 3+ | 3 | 3 | 2 | 2 | 2 | 2 | 1 | 1 |
Three things stand out. Skill 4, supplier bank-detail provenance, has only two people at level 3, and one of them is the supervisor, so any week the supervisor is away leaves a single person. Skill 7 has one: corrections to the agent depend on one person's time. And S. Khan is close to level 3 on most skills but has no certificate, so cannot be given payment release yet.
The plan that follows is simple: S. Khan takes a practicum to reach level 3 on skills 3 to 5; D. Price is coached on skill 7; R. Lowe gets supervised work on duplicates. In three months, the matrix is redone. For the definition of the work itself, see what accounts payable is; for how the same structure looks in a different function, compare the competency matrix for a risk team.
Where the Academy fits
Pryme Intelligence Academy maps cleanly to the levels: the Foundations badge sits at level 1, and Certified Pryme Operator, with its two-week practicum on real review decisions, is a fair test of level 3 for skills 1 to 6. A business can make payment release depend on a current certificate, as the approver rule for the accounts payable team describes. The admin view shows certificates and expiry dates for the last two columns. More in AI agent skills by role.
Questions people ask
How often should the matrix be updated?
Quarterly, and whenever someone joins, leaves, passes an assessment or lets a credential lapse. A lapsed credential should drop the person's level for payment release the same day.
Should the AP supervisor rate everyone?
The supervisor proposes ratings; a second person, such as the financial controller, checks a sample. Ratings at level 3 or above need evidence attached.
Is level 4 necessary?
At least one person at level 4 on the payment skills is needed to supervise practicums and coach. Without one, the team cannot grow its own approvers.