Purchase Order Agent
Raises purchase orders from approved requisitions.
- Industry
- IT Company
- Department
- Procurement
- Team
- Purchasing Operations
- Kind
- Assistant
- Approver
- Procurement Manager
- Code
- PRC-06
It raises purchase orders from approved requisitions for cloud commitments, licences, hardware and subcontracted work, with the right supplier, terms, project code and recharge flag. It creates the POs in the purchasing system and holds any order whose amount or supplier differs from the approved requisition.
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: the approved requisitions, supplier contracts and payment terms, and project codes..
- 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
Prepares the draft, match, recommendation or reply, with its sources.
- 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 creates the purchase orders and sends them to the suppliers. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The purchase order rules: PO templates by category, payment terms, project and cost-centre coding, recharge flags, delegation-of-authority limits and the rules for blanket and call-off orders.
Reads from
the procurement and purchasing system: the approved requisitions, supplier contracts and payment terms, and project codes.
Acts in
the procurement and purchasing system: it creates the purchase orders and sends them to the suppliers.
Hands back
A list with one entry per PO, each with requisition_id, supplier, lines (item, quantity, unit_price_usd), total_usd, payment_days, project, billable (true or false), status (raise or hold) and reason.
Asks a person when
A PO differs from its requisition by more than 5 percent or changes supplier, or lacks a project code while on is true.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Tolerance against the requisition (%) | 5 | A PO more than this above its requisition is held. |
| Default payment terms (days) | 45 | Used when the supplier contract gives none. |
| Longest blanket order (months) | 12 | Blanket orders for subcontractors or cloud run at most this long. |
| Every PO needs a project or cost centre | On | When on, a PO without a project or cost-centre code is held. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Raise a PO only from an approved requisition and within 5 percent of its amount.
- Use the supplier contract's payment terms, or 45 days when none.
- When on is true, every PO carries a project or cost-centre code; billable costs carry the recharge flag.
- Blanket orders run at most 12 months.
- Never change the supplier from the requisition; hold and ask the Procurement Manager.
- Subcontractor POs reference the framework agreement and the SOW they support.
See the Purchase Order Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.