How to Build a Purchase Order Process for a Small Business

• Use a purchase request for internal approval and a purchase order for the supplier.
• Give every order an owner, limit, number and clear description.
• Before payment, compare the order with what arrived and the supplier invoice.

A small purchase often begins in chat. Someone asks for a tool, a manager says yes, and a supplier sends an invoice weeks later. By then, nobody is sure which price was approved or who checked the delivery.

A purchase order process creates a short trail before money leaves the business. It can run in a spreadsheet, accounting tool or shared form. Decisions matter more than software.

Separate the request from the order

The Chartered Institute of Procurement and Supply defines a purchase requisition as an internal request for authority to buy. After approval, the buyer creates a purchase order for the supplier. Keep those jobs separate on the page.

Your request should explain the need, budget, expected cost and wanted date. The purchase order should state what the supplier agreed to provide. Add quantity, unit price, tax treatment where known, delivery point, payment terms and the buyer's contact.

Do not send a draft order that still needs approval. That can look like a promise to buy. Mark drafts clearly and let only authorised people release the final order.

Choose approval limits that fit the risk

Write a small approval table. Base it on value, cash impact and risk, not job title alone. A low-cost item can still create a long contract, expose customer data or lock the team into a tool.

These routes are examples, not standard limits. Set your own amounts and exceptions. Link the table to the small-business budget so an approval means both “needed” and “affordable.”

Give every order a useful number

Use a unique sequence such as PO-2026-0041. Never reuse a cancelled number. Record who requested, approved and sent the order, plus the dates for each step.

A supplier should place the PO number on its invoice when your process requires it. The UK Small Business Commissioner advises suppliers to request a needed PO number early because waiting for it can delay invoice submission and payment.

Describe the item well enough for another person to check it. “Office items” is weak. “Twelve stackable visitor chairs, navy fabric, delivered to York site” gives the receiver a usable test.

Check the delivery before the invoice

Record the arrival date and condition. For services, record the agreed milestone, the evidence of completion and the person who accepted the work. The requester should not tick “received” just because the invoice appeared.

HM Revenue and Customs describes two-way matching between the order and invoice. A three-way match also includes a goods-received record. Small firms can use the same idea without copying a large-company system.

1. Match the supplier and PO number.
2. Compare quantity, description and price.
3. Check delivery or service evidence against the agreed date and scope.
4. Confirm tax and totals with the invoice.
5. Record any difference and its owner.

Utilities, rent and card purchases may sit outside the PO route. Put those exceptions in writing. Match them to the contract, receipt or other approved record instead.

Keep proof with the transaction

The IRS says purchase and expense records may need the payee, amount, payment proof, date and a description. It also lists invoices, receipts and payment records as supporting documents. HMRC likewise requires accurate business-expense records, including receipts or invoices that correctly support the figures recorded for the transaction.

Keep the request, approval, order, receipt evidence, invoice and payment reference together. Rules vary by record and location. Use the business-records guide as a starting map, then confirm the rule that applies.

Use one exception queue

A mismatch should not vanish into email. Keep one queue with the PO number, difference, owner, next action and due date. Common cases include partial delivery, price changes, duplicate invoices and an invoice sent to the wrong address.

Call the supplier before the payment date when a difference may hold payment. Keep the message factual. If late-payment problems continue, the seven-day payment-chase plan shows the supplier side of the same handoff.

Labelled example: A ten-person design studio wants six monitors. The requester records the model, quantity, quote and budget code. The operations lead approves the spend.

After delivery, another team member records five good units and one damaged box. Accounts pays for the five accepted units after the supplier issues a corrected invoice. This is an illustration, not an accounting or tax rule.

Start with a seven-field process

1. Need and business reason
2. Requester and budget
3. Approval route
4. Unique PO number
5. Supplier, price and delivery terms
6. Receipt or service evidence
7. Invoice match and payment reference

Test the process on three real purchases. Note where people wait, repeat data or bypass the route. Then write the stable version with the one-page SOP method.

Frequently asked questions

Does every small purchase need a purchase order?

No. Define an exception list for items such as rent, utilities or low-value card purchases, then keep the supporting record.

What is the difference between a purchase request and a purchase order?

A purchase request asks for internal approval. A purchase order is the buyer's document sent to the supplier after approval.

Who should approve a purchase order?

Choose the role from the value, risk and budget involved. The requester should not approve a purchase outside their stated authority.

What should happen when the invoice does not match?

Pause payment, record the difference and ask the buyer, receiver or supplier to resolve it before the due date.

Sources and scope

CIPS: purchase requisitions and purchase orders · IRS: supporting business records · HMRC: procure-to-pay controls · UK Small Business Commissioner: getting invoices right · HMRC: records for self-employed businesses. This is general operational information, not legal, tax or accounting advice.