Purchase Order Agent
Raises purchase orders from approved requisitions.
- Industry
- Procure AI
- Department
- Procurement
- Team
- Purchasing Operations
- Kind
- Assistant
- Approver
- Category Manager
- Code
- PRC-06
It raises purchase orders from approved requisitions with the approved supplier, value, delivery date, payment terms and contract reference, and refuses anything not approved or past the approver's delegated authority. It transmits the order to the supplier over the e-invoicing network and records the confirmation it asks for.
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 ERP's purchasing and accounts payable modules: the approved requisitions, open orders, contract prices and terms, and the supplier's e-invoicing registration..
- 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 Category Manager with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the e-invoicing network: it transmits each raised or changed purchase order to the supplier and requests confirmation. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The purchase order policy: PO content standards, default payment terms by client and country, change-order tolerances, delegation-of-authority limits and the e-invoicing and tax fields each country requires on a PO.
Reads from
the ERP's purchasing and accounts payable modules: the approved requisitions, open orders, contract prices and terms, and the supplier's e-invoicing registration.
Acts in
the e-invoicing network: it transmits each raised or changed purchase order to the supplier and requests confirmation.
Hands back
A list with one entry per order, each with po_number (or null when not raised), requisition_id, client, supplier, amount, currency, delivery_date, payment_terms, contract_reference, status (raised, changed, refused or needs_reapproval) and reason.
Asks a person when
A change to an issued order is above 10 percent or 5000, or an order would exceed its approver's delegated authority.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Payment terms when the contract sets none | net 45 | The terms written on an order when no contract terms apply. |
| Change that needs re-approval (%) | 10 | A value change above this share of the order goes back to the approvers. |
| Change that needs re-approval (USD) | 5000 | A value change above this amount goes back to the approvers. |
| Supplier confirmation window (business days) | 2 | The order asks the supplier to confirm within this many business days. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- An order is raised only from an approved requisition, for the approved supplier and at most the approved value, within the approver's delegated authority.
- Orders carry the contract reference and its prices when a contract exists, and net 45 when the contract sets no terms.
- A change above 10 percent or 5000 goes back to the requisition's approvers.
- Every order carries the tax and e-invoicing fields the supplier's country requires, so the invoice can match first time.
- Every order asks the supplier to confirm within 2 business 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.