How to Set Up a Purchase Order Process for a Small Business

A purchase order is a document the buyer issues to a supplier before delivery. It records the supplier, the items or services, quantities, prices, tax treatment, and delivery terms the business has authorised.

Most small businesses in Singapore run without one. Someone WhatsApps a supplier, the goods arrive, the invoice lands in an inbox, and finance finds out about the commitment when payment is due.

That works at low volume. It stops working when:

• Nobody can say whether an invoice price was actually agreed
• Two people order the same thing
• A supplier bills for more than was ordered and nobody notices
• Finance cannot see committed spend until invoices arrive
• The person who made the deal has left, gone on leave, or forgotten

A purchase order process answers one question before money is committed:

Who authorised this purchase, from whom, at what price?

This guide sets out a right-sized version for a business with five to fifty staff.

What a purchase order is not

A purchase order is not:

• A quotation. The supplier's quote is an offer. The PO is the buyer's commitment, usually referencing the quote.
• An invoice. The supplier issues the invoice after delivery. The PO comes first and belongs to the buyer. If the distinction is blurry in your business, that is usually a sign nothing is being agreed in writing before delivery.
• A legal formality with no operational use. A PO that nobody checks invoices against is paperwork. The value comes at invoice time, when the match against the order and receipt catches quantity and price differences.

Decide what needs a PO

Do not require a purchase order for everything. A blanket rule produces fake POs raised after the invoice arrives, which protect nothing.

A workable small-business policy:

Purchase	PO required?
Inventory, materials, equipment	Yes
Project subcontractors and milestone work	Yes
One-off services above a threshold (e.g. SGD 500–1,000)	Yes
Recurring approved contracts (rent, subscriptions, retainers)	No — approve the contract once
Petty and card purchases below the threshold	No — control through expense claims or card limits

Set the threshold where the risk starts, not at zero. A business that argues about a SGD 40 stationery order while a SGD 15,000 subcontract goes uncontrolled has the policy backwards.

The minimum viable purchase order

Each PO needs:

• A sequential PO number
• Date
• Supplier legal name (and UEN where you have it)
• Item or service description
• Quantity and unit price
• Currency
• GST treatment
• Delivery date and location, or completion milestone
• Project, department, or cost centre
• Requester and approver

That is one form or one screen. It does not require procurement software on day one — accounting platforms such as Xero can raise POs, and even a controlled template with a shared PO register works at low volume.

What matters is that the PO exists before the commitment, and that finance can find it when the invoice arrives.

Set approval authority

Write down who can commit the business to spend, and up to how much.

Example for a small company:

Up to SGD 1,000    — department lead
Up to SGD 10,000   — general manager
Above SGD 10,000   — owner or director
New supplier       — owner approval regardless of amount

Two rules keep this honest:

1. The requester and the approver should not be the same person above a low threshold. In a very small team where that is unavoidable, compensate with owner review of the monthly PO register.
2. Watch for split orders. Three POs of SGD 900 to the same supplier in one week is one SGD 2,700 purchase avoiding the SGD 1,000 threshold. This is the same pattern to watch in supplier payment approvals.

Record receipt

The PO says what was ordered. Someone still has to record what arrived.

For goods: quantity, date, condition, and who received them. For services: an approved timesheet, milestone sign-off, or a named confirmation that the work was done.

This is the step small businesses skip most often, and it is the step that makes the PO useful. Without a receiving record, an invoice can only be checked against the order — not against reality. Delivery shortfalls, damaged goods, and billed-but-never-delivered services all pass through unnoticed.

The receiving record does not need to be elaborate. A photo of the delivery order plus a quantity confirmation from the person who took delivery is enough, as long as it is captured somewhere finance can see it.

Close the loop at invoice time

When the supplier invoice arrives, check it against the PO and the receipt:

• Supplier matches
• PO reference quoted
• Quantity billed ≤ quantity received
• Price matches the order
• GST treatment as expected

Differences become questions for the buyer or receiver — before approval, not after payment. The full method, including tolerances and partial deliveries, is covered in the three-way matching guide.

Tell suppliers to quote the PO number on their invoices, and reject invoices for PO-required purchases that arrive without one. Suppliers adapt quickly, and the matching step becomes mostly mechanical.

Keep the register visible

A live list of open purchase orders gives finance something the accounting ledger cannot: committed spend that has not yet become an invoice.

Review it monthly:

• Orders delivered but not yet invoiced (an accrual, and a call to the supplier)
• Orders open past their delivery date (chase or cancel)
• Orders that should have been closed (stop matching new invoices against them)

This is also what makes a cash-flow forecast honest — commitments appear weeks before the invoice does.

Where automation helps

A purchase order process is people and policy first. Automation earns its place once the basics exist:

• Raising POs from an approved request, with the approval routed by amount and category instead of by email chase
• Capturing receiving records from a phone at the point of delivery
• Extracting the PO reference from incoming invoices and matching order, receipt, and invoice automatically, so finance only sees the exceptions
• Flagging split orders, orders past delivery date, and invoices without a PO
• Keeping the register current without a spreadsheet that someone forgets to update

Software cannot fix a business where nobody knows who may approve what. Write the policy first; automate the routing, matching, and chasing second. For where this sits in the wider finance stack, see the finance automation guide for Singapore SMEs.

What to measure

• Purchases above the threshold made without a PO
• Invoices received without a PO reference
• Orders open past delivery date
• Price and quantity variances caught at invoice time
• Time from purchase request to approved PO

If request-to-approval time is slow, fix the approval routing — do not let people bypass the process, because they will, permanently.

The bottom line

A small-business purchase order process is four habits:

1. Above a sensible threshold, commit in writing before you buy
2. A named person approves within written limits
3. Someone records what actually arrived
4. Invoices are checked against both before approval

Start with your five largest or most frequent suppliers rather than every purchase. The control exists to catch material surprises, not to slow down buying coffee.

The same logic applies on the customer side: commit terms in writing before you extend credit. Our credit control and customer onboarding guide is the receivables mirror of this process.

Use the Calcudesk automation ROI calculator to estimate the time spent chasing order confirmations and checking invoices. If purchasing lives in WhatsApp threads and finance finds out at invoice time, book a 30-minute discovery call and we will map the workflow before recommending automation.