As of 13 August 2026, AI can only partly create a purchase order process.

What to actually do

1. Use a tool built for this

   The route this page recommends

2. Do it yourself

   Second choice

   A chat interface, chat-fluent skill, and roughly 1 hour until you can act on the result.

   How to actually do it

   1. Open your purchasing, finance and approval policies, then gather the current spending limits, roles, systems, supplier rules, invoice requirements and record-keeping rules.
   2. Write down one normal purchase and one recent exception, including who requested it, who approved it, what was ordered, how receipt was confirmed and how the invoice was paid.
   3. Paste the gathered information into the prompt, replacing each bracketed slot and marking unknown items as unknown rather than guessing.
   4. Ask the chatbot to produce the SOP, responsibility table, required fields, exception routes, controls, implementation checklist and unresolved questions specified in the prompt.
   5. Compare every approval, role, system action and record requirement in the draft against your current policies and one real purchase file, correcting unsupported details.
   6. Ask the purchasing or finance colleague who owns the process to resolve the open questions and run both test scenarios before approving the SOP.
   7. Publish the approved version in the staff knowledge base and configure the purchase order system or forms to match the final steps and required fields.

   Prompt

   Create a UK business purchase order process from the information below. Do not invent policies, approval limits, system features, legal requirements, supplier terms or accounting treatment. Where information is missing, mark it as an open question and give a safe default only if it is clearly labelled as a proposed option.
   
   Business context:
   - Organisation and department: [describe]
   - What is being purchased: [goods, services or both]
   - People involved and their roles: [list]
   - Current purchasing and finance systems: [describe]
   - Current supplier and invoice process: [describe]
   - Approval limits and spending rules: [provide or write unknown]
   - Budget ownership: [describe]
   - Required records and retention rules: [provide or write unknown]
   - Known risks, exceptions or recurring problems: [describe]
   
   Produce:
   1. A short purpose and scope.
   2. Definitions for requisition, purchase order, goods or service receipt, invoice and payment where needed.
   3. A numbered end-to-end procedure from identifying a need to closing the order.
   4. A responsibility table showing who requests, checks, approves, orders, receives, records and pays.
   5. Required information for a purchase requisition and purchase order.
   6. Approval and segregation-of-duties controls, using only the rules supplied and marking missing limits.
   7. Handling for urgent purchases, changes, cancellations, partial deliveries, unsuitable goods, duplicate invoices and no-PO invoices.
   8. Records, audit trail and system actions required at each stage.
   9. A short implementation checklist and a test scenario for one normal purchase and one exception.
   10. A list of unresolved questions that a purchasing or finance colleague must answer before publication.
   
   Write it as a practical SOP for staff in a UK business. Keep the language plain. Separate confirmed facts from proposed process decisions. Do not claim that the draft is compliant with any law or standard.

   Open it prefilled in ChatGPT or Claude, or copy it into Gemini, which takes no prefill link.

3. Hand it to a person

   The distant third

   A person who owns the outcome does this end to end, worth it when the failure is dear.