# Purchase order approval workflows: from request to goods receipt

> Design a purchase order workflow from requisition to goods receipt, with an authority matrix, versioned orders and no release before approval.

Source: https://www.fyadvisers.com/blog/purchase-order-approval-workflow-singapore/  
Author: Fiona Wang, FYAdvisers  
Published: 2026-11-08  
Last updated: 2026-11-08

A purchase order workflow begins before a supplier receives an order. It records what the team wants to buy, checks who can approve the commitment and issues a controlled version of the order. The design question is whether an unapproved purchase can still leave the building.

The supplier’s bill is a later process. Match it in the [invoice approval](/blog/invoice-approval-workflow-automation-singapore/) guide. The supplier record itself, especially bank details, belongs to [supplier onboarding](/blog/supplier-onboarding-bank-detail-change-workflow/). A stock alert that creates a request, and only a request, is the [reorder](/blog/inventory-reorder-approval-workflow/) guide.

## Five records, five owners

| Record | What it is allowed to decide | System that should be authoritative |
|---|---|---|
| Requisition | Someone wants something, in a quantity, for a reason | The request store |
| Approval | A named role accepts that commitment, on a stated version | The approval record, not the email |
| Purchase order | The version released to the supplier | The purchasing record |
| Goods receipt | What arrived, was damaged, or was cancelled | The receipt record |
| Invoice | What the supplier asked to be paid | The bill, matched later |

If the same spreadsheet cell is updated to mean all five, you cannot explain a dispute. Name the authoritative store for each before you choose a tool.

## What the request must contain

Collect requester, employing entity, cost centre or project, supplier id, description, quantity, unit, currency, requested date and the attachments that justify the buy. Missing supplier, missing budget owner or a free-text supplier with no master record is an exception. Do not default it to “approved” because the form was submitted.

A reorder suggestion can pre-fill a request. It should not select the supplier and the price as if a buyer had decided. That commercial choice stays with the buyer.

## Authority, absence and self-approval

Build a matrix the flow reads: entity, project or cost centre, amount, sequence. Microsoft’s [sequential approval](https://learn.microsoft.com/en-us/power-automate/set-up-sequential-approvals) pattern can express “first this role, then the next”. Parallel approval fits when two functions must both agree, such as a project lead and finance, and neither is a substitute for the other. Any amount in a vendor tutorial is an example, not your policy.

Write the awkward rules down:

- **Delegation and leave.** The delegate is named in advance. An out-of-office reply is not a delegation.
- **Self-approval.** State whether it is forbidden, or allowed only below a ceiling with a second role above it. The test is a requester who is also the configured approver.
- **Amendment.** A change to quantity, price or supplier after approval creates a new version and returns to the path that the change requires. Editing the PDF that was already sent, without a version, is the failure.
- **Cancellation.** Cancel the open quantity. Do not delete the approved version.

[Error handling](https://learn.microsoft.com/en-us/power-automate/guidance/coding-guidelines/error-handling) matters when the approval action times out or the supplier message fails. A retry must not send two different versions, and it must not send the order twice. Use a business key: entity, supplier, and a purchase-order number that the system allocates once. The acceptance test is two simultaneous requests that must not reuse one reference.

## Release, then receipt

Generate the supplier-facing order only from an approved version. Record who released it and when. Approving the order must not post an invoice and must not create a bank payment.

Receipt is a new event:

- partial quantity received;
- damaged or rejected quantity, with a note;
- cancelled remainder;
- a receipt that arrives before the paperwork, held until the order version exists.

Feed receipt status to invoice matching without overwriting the order. When a revised quantity is approved after a partial delivery, the new version should show what was already received against the previous version. Otherwise the site and finance will argue from two documents that look current.

GST-registered businesses keep source records. IRAS states that records, including the documents behind GST entries, are kept for at least five years from the end of the accounting period. A purchase order and its receipt are part of that evidence when they support a GST entry. Platform run history is not the archive. See [retention](/blog/workflow-automation-data-retention-audit-logs/).

## When the existing tools are enough

Ask for an audit export of request, version, approver and receipt; a change history on the matrix; a clear licence boundary; and a defined behaviour when the approval connector fails. A short matrix inside accounting or a purchasing module is enough for many SMEs. A separate procurement system earns its place when releases, catalogues and receipts are already escaping the accounting tool. [System integration](/services/system-integration/) is the piece that stops the order number in purchasing from differing from the number on the bill.

Illustrative scenario, not a client engagement: a site manager on a contractor’s job requests materials. The project lead approves the need, then finance approves the commitment. The supplier is already on the master file. A revised quantity does not edit the issued order in place. It produces a new version, the open quantity changes, and the earlier receipt stays on the old lines.

Witness three tests before you accept the build: the requester is also the approver; the order changes after a partial delivery; two requests cannot take the same number. Ask the supplier what, in the built system, physically prevents release before approval.

This is an operational design guide, not legal or tax advice, and FYAdvisers is not a law firm. To map a purchase that currently bypasses the form, use the contact form or WhatsApp +65 9071 3976 ([chat](https://wa.me/6590713976)).

## Frequently asked questions

### Where should the authority matrix live?

In a record the workflow reads at decision time, not in a slide that was true last quarter. Each row needs entity, cost centre or project, amount band, approver and delegate. Changing the matrix should be its own approved change.

### What stops an order reaching the supplier before approval?

The release action should be unavailable until the current version is approved. Emailing a PDF from a requester’s laptop is the bypass. If people can still do that, the workflow is a parallel process, not a control.

### How should a partial receipt be stored?

As receipt lines against the order lines: quantity received, quantity damaged or rejected, and quantity still open. The original order version stays intact. Invoice matching should read the receipt, which is covered in the invoice approval guide.

### Does approving a purchase order approve the invoice and the payment?

No. The order approves a commitment. The invoice and the payment run need their own decisions, even when the supplier and the amount look the same.
