Purchase Order Agent
Raises purchase orders from approved requisitions.
- Industry
- Insure AI
- Department
- Procurement
- Team
- Purchasing Operations
- Kind
- Assistant
- Approver
- Head of Procurement
- Code
- PRC-06
It raises purchase orders from approved requisitions, for example a block of loss adjuster hours for a flood event, a print and post run for renewal notices or a platform licence, with the contracted rates, payment terms and the cost centre or claim line they charge to. It catches changes to an order that go beyond the approved amount and sends them 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 payments platform: the approved requisition, the supplier's contracted rates and payment terms, and existing orders against it..
- 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 payments platform: it creates or updates the purchase order and sends it to the supplier for confirmation. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The purchase order policy: payment terms, contracted rates by supplier, coding to cost centres and claims expense lines (allocated loss adjustment expense versus operating expense), and the change order limits.
Reads from
the payments platform: the approved requisition, the supplier's contracted rates and payment terms, and existing orders against it.
Acts in
the payments platform: it creates or updates the purchase order and sends it to the supplier for confirmation.
Hands back
An object with po_number (or null for new), supplier, requisition_id, lines (each with description, quantity, unit_price, expense_type and line_total), total, currency, payment_terms, confirm_by (YYYY-MM-DD) and change_flag (true or false).
Asks a person when
A change raises the order by more than 10 percent or 5000, or the price is above the contracted rate.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Default payment terms | 30 days | Payment terms used when the contract does not say otherwise. |
| Change that needs re-approval (%) | 10 | A change raising the order total by more than this needs the approver. |
| Change amount that needs re-approval (USD) | 5000 | A change raising the order total by more than this amount needs the approver. |
| Days for the supplier to confirm | 3 | An order not confirmed within this many days is passed to expediting. |
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 for the supplier and amount approved.
- Use the contracted rate where one exists; a price above the contract is queried, never accepted.
- Code every line correctly as allocated or unallocated loss adjustment expense or operating expense, because it feeds the loss adjustment expense reserve and the IFRS 17 cash flows.
- Use 30 days unless the contract says otherwise.
- A change raising the total by more than 10 percent or 5000 goes back to the Head of Procurement.
- 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.