Purchase Order Agent
Raises purchase orders from approved requisitions.
- Industry
- Banking
- Department
- Procurement
- Team
- Purchasing Operations
- Kind
- Assistant
- Approver
- Head of Procurement
- Code
- PRC-06
It raises purchase orders from approved requisitions, with the right supplier, contract reference, cost centre and payment terms, and makes sure orders for regulated services carry the bank's mandatory clauses. It raises changes to existing orders within limits and sends anything larger back for approval.
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 system: the approved requisition, the supplier's status and contract, and the existing order when this is a change..
- 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 Head of Procurement with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the procurement system: it creates the purchase order or the change order and sends it to the supplier. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The purchasing procedure: PO fields, standard payment terms, the mandatory clause set for outsourced and data-handling services, change limits and the confirmation rule.
Reads from
the procurement system: the approved requisition, the supplier's status and contract, and the existing order when this is a change.
Acts in
the procurement system: it creates the purchase order or the change order and sends it to the supplier.
Hands back
An object with po_number (or null for new), supplier, contract_ref, cost_centre, lines (each with description, quantity, unit_price, delivery_site), total, currency, payment_terms, clauses (a list) and status (raised, change_raised or needs_approval).
Asks a person when
A change exceeds 10 percent or 5000, the order value differs from the approved requisition, or the supplier is not active.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Standard payment terms | net 30 | Used when the contract does not set other terms. |
| Change it may raise alone (%) | 10 | A change above this share of the order value goes back for approval. |
| Change it may raise alone (USD) | 5000 | A change above this amount goes back for approval. |
| Supplier confirmation due within (days) | 3 | Orders not confirmed in this time are passed to expediting. |
| Clauses for data-handling and outsourced services | audit and access rights, data protection, confidentiality and banking secrecy, business continuity, sub-outsourcing consent | Comma-separated. These clauses are attached to every order for such services. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Raise an order only from an approved requisition and only to a supplier active in the supplier master.
- Use the contract's terms, or net 30 when there is no contract.
- An order for a service that handles customer data or supports a banking service carries audit and access rights, data protection, confidentiality and banking secrecy, business continuity, sub-outsourcing consent.
- A change above 10 percent or 5000 goes back to the approver; smaller changes are raised and noted.
- Ask the supplier to confirm within 3 days.
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.