Workflows
Automate Purchase Orders
A purchase request is not yet an order. Someone still needs to check the supplier, budget, quantity and approval before anything is sent. Automating purchase orders connects those decisions to a traceable document and keeps the team informed when goods arrive or something changes.
Key takeaways
Keep requests, approved orders and received goods as distinct records.
Generate an order only after the correct approval.
Track revisions and partial deliveries without losing the original decision.
Collect a structured purchase request, validate supplier and item details, obtain the required approvals and generate a uniquely numbered purchase order. Send the approved version, record the supplier response and track receipts against individual order lines.
- Capture the request and needed-by date.
- Check the supplier, quantity, budget code and duplicate request.
- Obtain approval for the exact request version.
- Generate and send the purchase order.
- Record supplier acknowledgement, receipts and remaining quantities.
Turn informal requests into a complete starting record
Use a form or existing purchasing screen to collect what the buyer needs: requester, supplier, item or service, quantity, unit, price source, delivery location and date. Give the request a unique ID before it enters approval.
A low-stock notification can suggest a purchase request, but it should not automatically become a supplier order unless the business has explicitly approved that rule. Check open orders and expected deliveries before buying more of the same item.
For services, define the milestone or acceptance evidence that counts as received. A service order cannot always use the same receipt logic as a box of goods.
| Record | What it proves | Keep with it |
|---|---|---|
| Purchase request | Someone asks to buy specified items | Requester, purpose and required date |
| Approval | The authorised person accepted a version | Approver, limits, timestamp and decision |
| Purchase order | The approved order was issued | Order number, version and supplier destination |
| Receipt | Goods or services were accepted | Line quantities, date and receiver |
| Invoice match | Supplier billing was compared with evidence | Invoice, order and receipt references |
Make approval limits explicit
Write a small approval matrix before building the flow. It can depend on department, amount, supplier status or purchase type. A new supplier may need purchasing review even when the amount is low. Keep those decisions visible rather than hiding them in a long email chain.
Power Automate supports sequential approval patterns where one decision precedes the next. That is one implementation option, not a reason to add unnecessary approvers. Choose the smallest review route that matches the business's actual purchasing authority.
If quantity, price or delivery terms change, compare the revised request with the approved version. Route material changes back for approval. Record rejected and withdrawn requests so a later retry cannot accidentally issue them.
Worked example: 30 items ordered, 20 received
Imagine a team requests 30 replacement parts at an illustrative unit price of 8. The request total is 240 before any other applicable charges. The department owner approves that version, and the automation creates one purchase order linked to the request ID.
The supplier confirms delivery in two batches. When 20 parts arrive, the receiver records 20 against the order line. The order remains Partially received with ten outstanding. A reminder goes to the buyer only if the remaining delivery passes the agreed follow-up date.
An invoice for all 30 can then be flagged against the recorded receipt rather than treated as fully matched. If the final ten arrive later, that receipt completes the quantity. If they are cancelled, the buyer records the change and its approval instead of editing history to make the numbers fit.
Control the order document and supplier handover
Generate the document from approved data and retain its version. Validate the supplier destination from the approved supplier record. Avoid silently accepting a new email address pasted into a request when that address changes who receives commercial information.
Store the sent document, delivery result and acknowledgement separately. Sent means the system accepted the handover; it does not mean the supplier agreed to every term or delivery date.
Use the request ID to prevent duplicate order creation. After a timeout, inspect the existing order and send record before repeating an action. If the supplier requires a portal, assess its supported integration or permitted browser workflow rather than assuming every portal can be automated.
Test changes, cancellations and partial receipts
A useful pilot covers more than a straightforward approved request. Try a rejected request, an absent approver, a changed price, two identical submissions and a partially received order. Give each case an expected state and owner.
Reconcile requested, ordered, received and cancelled quantities. These should explain what is still outstanding. Do not mark an order complete merely because a document was generated.
Keep a manual fallback for urgent purchases during the trial, with a way to enter the resulting order into the same register. Otherwise the automation's view of outstanding orders will be incomplete.
Build the purchasing workflow you actually need
Automations For Business can customise purchase order automation around your forms, spreadsheets, supplier list, document template and supported purchasing or accounting tools. We can add department-specific approvals, separate delivery locations and a receiving view that fits your team.
Send an example request, purchase order and approval matrix with private details removed. We can scope the workflow from request to receipt, identify the connections available and agree the cases that must pass before it is used for real orders.
Your ready-to-use checklist
0 of 6 checked
Make the next step clear.
Purchase order workflow brief
Free templateConnect this with the rest of your workflow
Sources and notes
Sources checked on October 28, 2026.
- Microsoft: sequential approvals
A documented implementation pattern for ordered approval steps.
- Microsoft: approvals overview
Approval types and prerequisites to assess when using Power Automate.
