Purchase Requisition Agent
Checks purchase requests against budget and policy and routes them.
- Industry
- Procure AI
- Department
- Procurement
- Team
- Sourcing and Contracts
- Kind
- Decision-maker
- Approver
- Category Manager
- Code
- PRC-01
It checks every requisition raised in a client's buying channel or our own against the cost centre's remaining budget, the client's delegation-of-authority matrix, the preferred supplier list and the competitive-quote thresholds, and adds related requisitions together so a split purchase cannot slip under a limit. It then routes the requisition to the right approvers in the source-to-pay suite, sends it back with what is missing, or steers it to a catalogue or contract that already covers the need.
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 source-to-pay suite: open and recent requisitions for the same cost centres and suppliers, the cost centres' budgets and committed spend, the client's approval matrix, live catalogues and the preferred supplier list..
- 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 Category Manager with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the source-to-pay suite: it routes each requisition to its approvers, returns it to the requester with what is missing, or redirects it to the catalogue. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
Each client's procurement policy and delegation-of-authority matrix, quote thresholds by value band, the no-splitting rule, the preferred supplier list and catalogues by category, and the segregation-of-duties rules between requester and approver.
Reads from
the source-to-pay suite: open and recent requisitions for the same cost centres and suppliers, the cost centres' budgets and committed spend, the client's approval matrix, live catalogues and the preferred supplier list.
Acts in
the source-to-pay suite: it routes each requisition to its approvers, returns it to the requester with what is missing, or redirects it to the catalogue.
Hands back
A list with one entry per requisition, each with requisition_id, client, total_checked (amount after related requisitions are added), decision (route, send_back, redirect_to_catalogue or escalate), approvers (a list of roles), missing (a list of what is missing) and reason.
Asks a person when
The routing skips an approver the delegation-of-authority matrix requires, a split purchase is suspected, a sole-source reason is offered above 10000, or the requisition takes the cost centre past 100 percent of its budget.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Value that needs three competitive quotes (USD) | 10000 | A requisition above this value needs three written quotes or an approved sole-source justification. |
| Value that needs the Category Manager (USD) | 25000 | Above this value the Category Manager for the category approves as well as the budget owner. |
| Value that needs the Procurement Director (USD) | 250000 | Above this value the Procurement Director approves, under the delegation-of-authority matrix. |
| Window for adding related requisitions (days) | 30 | Requisitions from the same cost centre for the same supplier or category within this window are added together before any limit is checked. |
| Budget use that escalates (%) | 100 | A requisition that takes the cost centre past this share of its period budget goes to the Procurement Director. |
| Send catalogue items back to the catalogue | On | When on, a free-text requisition for an item on a live catalogue or contract is returned with the catalogue link instead of routed. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- A requisition above 10000 without three quotes or an approved sole-source reason is sent back, not routed.
- Requisitions from the same cost centre for the same supplier or category within 30 days are added together before any limit is checked.
- Above 25000 the Category Manager approves; above 250000 the Procurement Director does too, as the client's delegation-of-authority matrix sets.
- The requester never appears as an approver on their own requisition; segregation of duties overrides the matrix.
- A requisition that takes its cost centre past 100 percent of its period budget goes to the Procurement Director whatever its value.
- When on is true, a free-text request for an item on a live catalogue or contract is returned with the catalogue link, counted as avoided maverick spend.
- A non-preferred supplier in a category with a preferred one needs a written reason and the Category Manager; urgency never removes an approver, it only moves the requisition up their queue.
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.