Maverick Spend Agent
Finds spend outside contracts and purchase orders and explains why.
- Industry
- Procure AI
- Department
- Procurement
- Team
- Purchasing Operations
- Kind
- Investigator
- Approver
- Client Engagement Lead
- Code
- PRC-09
It finds maverick spend for a client: invoices with no purchase order or contract, card spend in managed categories, and preferred categories bought from other suppliers, and works out why each happened, whether urgency, card use, unaware requisitioners, a lapsed contract or a missing catalogue. It reports contract leakage by cause and creates follow-up tasks for the cost centre owners. **The problem it solves:** Why spend went outside contracts and purchase orders: where it went, how much, through which channel, and what caused it.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the spend analytics warehouse: the spend cube for the client: invoices, POs, card transactions, contracts and catalogues by category and cost centre..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Weighs competing explanations against the evidence and shows which one holds up.
- 05Asks a person
Hands the work to Client Engagement Lead with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the source-to-pay suite: it creates follow-up tasks for cost centre owners with the leakage and the compliant buying channel. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The client's spend policy, the category taxonomy, contract and catalogue coverage by category, the maverick-spend definition and the client's target maverick-spend share.
Reads from
the spend analytics warehouse: the spend cube for the client: invoices, POs, card transactions, contracts and catalogues by category and cost centre.
Acts in
the source-to-pay suite: it creates follow-up tasks for cost centre owners with the leakage and the compliant buying channel.
Hands back
An object with client, period, addressable_spend, maverick_spend, maverick_percent, by_cause (a list with cause, amount and count), by_category (a list with category, amount and contracted_supplier) and by_cost_centre (a list with cost_centre, amount and main_cause).
Asks a person when
The analysis would name individual employees, or a lapsed contract shows the client paying above contract price.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Target maverick-spend share (%) | 5 | The client's target share of addressable spend that is off contract or without a PO. |
| Smallest transaction to classify (USD) | 1000 | Transactions below this are counted but not given a cause. |
| Include purchasing card spend | On | When off, card transactions are left out and the report says so. |
| Cost centre leakage that gets a follow-up (USD) | 25000 | A cost centre with more off-contract spend than this gets a follow-up task. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Spend is maverick when the supplier has no contract or PO, the PO was raised after the invoice, or a contracted category is bought elsewhere.
- Each transaction above 1000 is given one cause: urgent purchase, card spend, unaware of preferred supplier, lapsed contract, no catalogue or other.
- When on is false, card transactions are left out and the report says so.
- A cost centre above 25000 gets a follow-up task; the total share is compared with 5 percent.
- Causes are reported by cost centre and team, never by named employee.
See the Maverick Spend Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.