Off-Contract and Shadow IT Spend Agent
Finds SaaS, cloud and contractor spend outside contracts and POs and explains why.
- Industry
- IT Company
- Department
- Procurement
- Team
- Purchasing Operations
- Kind
- Investigator
- Approver
- Procurement Manager
- Code
- PRC-09
It finds spend outside contracts and purchase orders, above all shadow IT: SaaS tools bought on company cards, cloud accounts outside the master agreement and contractors engaged without a PO. It explains why each pattern happens and logs the finding, with the security risk where client data may sit in an unreviewed tool. **The problem it solves:** Why money is being spent outside contracts and POs: which suppliers, departments and amounts, and whether a missing alternative, slow process, unawareness, client need or bypass explains 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 procurement and purchasing system: card, expense and invoice transactions with supplier and department, matched against contracts and POs..
- 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 Procurement Manager with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the procurement and purchasing system: it logs each off-contract pattern for review and opens the follow-up with the department. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The spend policy: what must go through a PO, the approved SaaS catalogue, the master cloud agreements, card-spend rules and the shadow-IT review process.
Reads from
the procurement and purchasing system: card, expense and invoice transactions with supplier and department, matched against contracts and POs.
Acts in
the procurement and purchasing system: it logs each off-contract pattern for review and opens the follow-up with the department.
Hands back
A list with one entry per pattern, each with supplier, category, department, total_usd, transactions, cause (with evidence and confidence), data_risk (true or false) and fix (bring onto contract, move to approved tool, stop or allow).
Asks a person when
An unreviewed tool may hold client data, or a contractor was engaged without a PO.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Smallest amount to review (USD) | 200 | Transactions below this are counted but not reviewed one by one. |
| Look back (days) | 90 | The window reviewed when the request gives none. |
| Repeats that make a pattern | 3 | A supplier paid off contract this many times is a pattern. |
| Flag tools that may hold client data | On | When on, an unreviewed tool that may hold client data goes to security. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Review off-contract transactions of 200 USD or more over the last 90 days.
- A supplier paid off contract 3 or more times is a pattern to explain.
- Weigh the competing causes: no approved alternative, a slow buying process, a team unaware of the catalogue, a client-specific need or deliberate bypass; say what would confirm each.
- When on is true, an unreviewed tool that may hold client data goes to the Chief Information Security Officer.
- Name the department and the pattern, never blame an individual.
See the Off-Contract and Shadow IT 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.