Purchase Requisition Agent
Checks purchase requests against budget and policy and routes them.
- Industry
- IT Company
- Department
- Procurement
- Team
- Sourcing and Contracts
- Kind
- Decision-maker
- Approver
- Procurement Manager
- Code
- PRC-01
It checks purchase requests for what an IT company buys (cloud capacity, software licences and SaaS tools, laptops and test devices, subcontracted developers and training) against the project or department budget and the buying policy, and routes each to the right approver. It approves small in-policy requests, sends anything that will touch client data to security review, and holds requests that bypass a preferred supplier.
How it works
7 steps, and a person signs off before step 7.
- 01Looks it up
Finds the record the request is about in the procurement and purchasing system: the open requisitions, preferred suppliers by category and remaining budgets, with project budgets and SOW recharge terms from the PSA system..
- 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.
- 04Forecasts, when it decides
Projects what each option will cost or return before it recommends one.
- 05Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 06Asks a person
Hands the work to Procurement Manager with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the procurement and purchasing system: it updates each requisition with its decision and routes it to its approvers. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The buying policy: approval limits by amount, preferred suppliers by category, the security review rules for new software and SaaS, the open-source and licence rules, and which project costs can be recharged to clients.
Reads from
the procurement and purchasing system: the open requisitions, preferred suppliers by category and remaining budgets, with project budgets and SOW recharge terms from the PSA system.
Acts in
the procurement and purchasing system: it updates each requisition with its decision and routes it to its approvers.
Hands back
A list with one entry per request, each with requester, item, amount_usd, budget_after_usd, decision (approve, route, hold or reject), route_to (a list of roles), security_review (true or false) and reason.
Asks a person when
A request is at or above 1000 USD, bypasses a preferred supplier, needs security review, exceeds budget, or is recharged to a client without SOW cover.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Approve without a person below (USD) | 1000 | In-policy requests below this from a preferred supplier are approved. |
| Requests that also need the CFO (USD) | 50000 | Requests at or above this, or recurring ones at or above this a year, also need the CFO. |
| Security review needed for | client data | Software or SaaS with this level of data access, or higher, goes to security review first. |
| Must use a preferred supplier | On | When on, a request for a category with a preferred supplier that names another one is held. |
| Recharged costs need SOW cover | On | When on, a cost marked billable to a client must be allowed by the project's SOW. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Check each request against the remaining project or department budget; a request that would exceed it is held.
- Approve in-policy requests below 1000 USD from a preferred supplier; at or above 50000 USD (annualised when recurring) it also needs the CFO.
- Software or SaaS with client data access or higher goes to the Chief Information Security Officer for review, with a data-processing agreement, before approval.
- When on is true, a request that bypasses the preferred supplier is held with the reason.
- When on is true, a cost recharged to a client needs the project's SOW to allow it.
- Open-source or licensed components for client delivery are checked against the licence rules; copyleft licences in client code need the Procurement Manager.
- Never split a request to stay under a limit; requests from the same requester for the same item within 30 days are added together.
See the Purchase Requisition Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.