Separate the request, approval and purchase order
A requisition records a need. Approval authorises expenditure under stated conditions. A purchase order is a separate commercial record sent to the supplier. An approved request may still require quotation selection or another business check before an order is issued.
| Stage | Owner | Condition for moving forward |
|---|---|---|
| Request | Requester | Item, quantity, reason and required date are complete |
| Budget check | Budget owner | Relevant allocation and scope are confirmed |
| Approval | Authorised manager | Amount and exceptions have been reviewed |
| Purchase order | Procurement | Supplier and commercial terms are agreed |
| Receipt | Receiving team | Delivered quantities and shortages are recorded |
Write the exceptions alongside the rule
Suppose an illustrative policy allows a department manager to approve purchases up to €1,000 and requires an additional budget-owner approval above that amount. This is a design example, not a recommended spending threshold. If the same person holds both roles, decide whether an independent second approval is required.
The process should also handle absence. Define the start and end of delegated authority, its spending limits and the identity recorded against each decision. Whether a requester may approve their own purchase is a business-policy decision that should not emerge accidentally from account permissions.
Deal with changes after approval
Changing an approved quantity or total can require a fresh decision. Restarting the entire process for every spelling correction creates friction, while allowing every commercial change without review defeats the control. The process owner should identify critical fields and any permitted tolerances.
For example, increasing an approved purchase from 10 items to 14 is not equivalent to correcting a description. Display the old and new values, the reason and the resulting approval requirement. Preserve the earlier decision so that the history explains what was approved at that time.
Keep ERP acceptance separate
“Approved” and “purchase order created in the ERP” are different states. Users need to see when an integration is pending or has failed. Retrying a transmission must not create another purchase order. Likewise, a partial delivery should not silently close the entire requirement.
Use the pilot to exercise rejection, withdrawal, delegation, changed amounts, duplicate submissions and partial receipt. Measure more than average approval time: track requests returned for missing information, manual interventions and cases without a clear owner. A faster approval is not a benefit if it bypasses the intended checks.
Can a spreadsheet be enough? Yes, for a small number of users and a simple process. Reassess when concurrent work, permission boundaries and decision history become difficult to manage.
Explore our custom software development service. A useful starting point is to map one successful request and one troublesome exception from your current process.
Discuss your purchasing workflow
Related guides
- Custom Software Cost: Development and Operating Budget
- What is a B2B portal? Dealer, supplier and customer portals
- Excel purchase request and approval template
Technical references
- Microsoft Learn — Purchase requisition workflows
- Microsoft Learn — Approval and confirmation of purchase orders
- Microsoft Learn — Record purchases
- Stripe — Idempotent requests
Sources checked: 13 November 2026. Microsoft documentation provides product examples for requisitions, approval, purchase orders and partial receipts. Stripe documents the principle of safe retries; this does not mean every ERP API provides the same support. Verify approval policies, retry behaviour and record checks in the selected system.