A finance team's AI agent competency matrix lists the skills people need once agents match invoices, draft journals and prepare payment runs, sets a level for each skill, and names which role must hold it. Clerks must read verdicts and provenance; controllers must approve depth 4 payments and reconstruct any posting from the record.
What is the matrix for, and when should a finance team use it?
Finance is where an agent's mistake becomes money. An agent that matches invoices at depth 3 or prepares a payment run at depth 4 is acting on the ledger, and the people around it need specific skills before that happens, not after the first misposted accrual. The matrix makes those skills visible, assignable and testable.
Use it at three points: before an agent first shadows the purchase-to-pay or close process, before any capability rises to depth 3, and whenever roles change. It sits under the wider view in AI agent skills by role. It also pairs with your authority matrix, which records who may approve what. The competency matrix answers the question before that one: who is able to.
How do you fill it in?
List the skills down the side and the finance roles across the top, then enter the level each role must reach. Four levels suit most finance teams:
- Aware: knows the vocabulary (depth, the four verdicts, provenance) and can explain a held or refused item to a colleague or a supplier.
- Practising: decides held items correctly in a live queue and writes a reason a colleague could follow.
- Accountable: approves at depth 4, signs off a period, and can reconstruct any agent action from the record.
- Designing: writes the agent's brief, chooses sources and bounds, and reads a certification result.
Add an evidence column for each skill: what proves a person has reached the level. A level with no evidence is a hope. Then review the matrix at each quarter-end close, because that is when held volumes peak and gaps show.
The template
Copy this table, replace the role names with your own, and enter a level from 1 to 4 in each cell.
| Skill | AP clerk | Finance analyst | Financial controller | Finance systems lead | Evidence of the level |
|---|---|---|---|---|---|
| Explains depth and the four verdicts | |||||
| Reads which bound decided a verdict | |||||
| Weighs provenance: sealed ledger entry against an emailed invoice | |||||
| Decides held invoices and journals with written reasons | |||||
| Routes bank-detail changes that arrive from outside | |||||
| Approves payment runs at depth 4 | |||||
| Runs the queue when an agent's certificate lapses | |||||
| Reconstructs a posting from the record | |||||
| Writes the agent's brief, sources and bounds | |||||
| Reads a certification result gate by gate |
A worked example
Take a hypothetical group finance team of twelve: six AP clerks, three analysts, two controllers and one systems lead. The values below are illustrative.
| Skill | AP clerk | Analyst | Controller | Systems lead | Evidence |
|---|---|---|---|---|---|
| Explains depth and verdicts | 1 | 1 | 1 | 1 | Foundations test |
| Reads which bound decided | 2 | 2 | 3 | 3 | Review sample marked by controller |
| Weighs provenance | 2 | 2 | 3 | 4 | Review sample |
| Decides held items with reasons | 2 | 2 | 3 | 1 | Two weeks of live decisions |
| Routes external bank-detail changes | 2 | 2 | 3 | 1 | Scenario test |
| Approves depth 4 payment runs | none | none | 3 | none | Named on the approver rule |
| Runs the queue after a lapse | 1 | 2 | 3 | 2 | Drill at quarter-end |
| Reconstructs a posting | 1 | 2 | 3 | 3 | Audit walkthrough |
| Writes brief and bounds | none | 1 | 2 | 4 | Certified agent |
| Reads certification result | 1 | 1 | 3 | 4 | Walkthrough of a failed gate |
Three choices in the example are deliberate. First, clerks hold level 2 on bank-detail changes. A new account number in an emailed letter is an external claim, and an external claim cannot authorise a payment, so the clerk's skill is to recognise it and route it to a call-back, not to judge it alone.
Second, the systems lead is kept at level 1 for deciding held items and has no payment approval. The person who designed the matching agent should not be marking its work. The approver rule for the finance team should say so in writing.
Third, analysts must reach level 2 on running the queue after a lapse. If the invoice-matching agent's certificate lapses after 90 days during close, or a run that clears no depth drops it to depth 1 the same day, every match becomes a held item. The analysts absorb that, and the reviewer rota for the finance team should already show who covers.
Where the Academy fits
Pryme Intelligence Academy maps cleanly to these levels. Foundations, about four hours and free, covers level 1 for everyone. The Operator track, with its exam and two-week practicum of real review decisions, evidences levels 2 and 3 for clerks, analysts and controllers. The Builder track evidences level 4 for the systems lead. The admin view shows who holds which certificate and when it expires.
Questions people ask
Should the financial controller also be able to build agents?
It helps if the controller can read a certification result and challenge the bounds, which is level 3. Designing the agent is better left to someone else, so that the person signing off the period is not also the author of the agent's rules.
How often should levels be re-tested?
Tie re-testing to two clocks: the person's certificate, which for reviewers runs 12 months, and the agent's changes. If the agent gains a new capability or source, the people reviewing it should see a sample of the new work before it goes live.
Does a small finance team need all four levels?
It needs the skills, not the headcount. In a team of three, one person may hold levels 2 and 3 while an outside adviser holds level 4. Keep payment approval and agent design in different hands even then.