Procurement process

Purchase orders: the formal commitment to buy

A purchase order is the point where an internal decision becomes an external commitment — the document you send a supplier that says exactly what you are buying, at what price and on what terms. It is also the anchor for everything that follows: goods receipt, invoice matching and payment all reference the PO. This guide explains what a purchase order is, what it should contain, how the PO process works, and how POs underpin financial control.

9 min read · Last updated 11 July 2026 · By Lapasar Procurement Technology

In short

A purchase order (PO) is a document a buyer issues to a supplier that formally commits to buying specified goods or services at agreed quantities, prices and terms. Once the supplier accepts it, it becomes a binding agreement. The PO carries a unique number used to match the later goods receipt and invoice — the basis of three-way matching.

What is a purchase order?

A purchase order is the formal document a buyer sends to a supplier to commit to a purchase. It specifies the items or services, quantities, agreed prices, delivery details and payment terms, and carries a unique PO number. Once the supplier accepts it, the purchase order forms a binding commitment between the two parties.

The PO is the external counterpart to the internal purchase requisition. The requisition is the request for permission to buy; the purchase order is the instruction to the supplier once that permission is granted. And unlike an invoice — which the supplier issues to request payment — the PO is issued by the buyer to place the order in the first place.

Beyond placing the order, the purchase order is a reference point. Its number ties the order to the goods receipt recorded on delivery and to the supplier's invoice, so all three can be checked against each other before payment.

How the purchase order process works

The purchase order process picks up where an approved requisition leaves off and runs through to a matched, paid invoice.

  • Create the PO: convert the approved requisition into a purchase order with items, quantities, prices, terms and a unique number.
  • Issue to the supplier: send the PO to the supplier, who reviews and accepts it, forming the commitment.
  • Fulfilment: the supplier delivers the goods or performs the service against the PO.
  • Goods receipt: the buyer records receipt and checks it against the PO for quantity and condition.
  • Invoice matching: the supplier's invoice is matched against the PO and the receipt — the three-way match.
  • Close and pay: once matched, the invoice is approved for payment and the PO is closed.

Why purchase orders matter

Purchase orders are the backbone of spend control and financial accuracy. Because a PO records exactly what was agreed before delivery, it gives finance a clear view of committed spend and a fixed reference to check deliveries and invoices against. Without POs, organisations pay against invoices alone — with little assurance the price, quantity or even the order itself is correct.

They also protect both sides commercially. A clear purchase order reduces disputes: the agreed price and quantity are documented, so there is less room for a supplier to bill differently from what was ordered. And by anchoring three-way matching, POs are the single most effective defence against duplicate payments, price creep and paying for goods never received. For high-volume buyers, generating and matching POs automatically — rather than by hand — is what makes that control affordable at scale.

Benefits

Visibility of committed spend

Every issued PO is a recorded commitment, so finance sees what is owed before invoices arrive.

Accurate invoice matching

The PO is the fixed reference that goods receipts and invoices are checked against before payment.

Fewer disputes

Documented prices, quantities and terms reduce disagreements about what was ordered.

Protection from overbilling

Matching invoices to POs catches prices or quantities that differ from what was agreed.

A clean audit trail

Numbered POs linked to requisitions, receipts and invoices give a complete, traceable record.

Common challenges

Manual PO creation

Raising POs by hand is slow and error-prone, and rekeying introduces mismatches.

Off-PO spend

Buying without a PO removes the reference that matching and control depend on.

Matching exceptions

Differences between PO, receipt and invoice create rework and delay payment if not resolved cleanly.

Disconnected systems

When POs, receipts and invoices live in separate tools, matching is manual and reconciliation drifts.

Purchase orders in practice

After a requisition for maintenance parts is approved, a purchase order is generated with the exact items, agreed contract prices, delivery address and a unique PO number, and sent to the supplier. When the parts arrive, the storeman records the goods receipt against that PO number. When the supplier's invoice comes in, it is matched against the PO and the receipt — same items, same quantities, same prices — and only then approved for payment.

The value is control without friction. When POs are generated automatically from catalogue requisitions and matched against receipts and invoices electronically, the whole loop runs with minimal manual effort while every purchase stays documented and checkable. Malaysian enterprises that issue and match POs through a managed marketplace — with contract pricing and consolidated invoicing across Peninsular Malaysia — get that control at scale. If you still raise POs manually, the purchase order template linked below is a clean starting point.

Best practices

Require a PO for spend

Set a policy that purchases above a threshold need an approved PO, so control is the default.

Generate POs from requisitions

Convert approved requisitions straight into POs to avoid rekeying and keep prices consistent.

Use contract pricing

Populate POs from a contracted catalogue so prices are correct and invoice matching is clean.

Match before you pay

Enforce three-way matching against the goods receipt and invoice before releasing any payment.

Integrate POs with your ERP

Connect PO issuance and matching to your finance system so records reconcile automatically.

Summary

A purchase order is the formal, numbered commitment a buyer issues to a supplier — the external counterpart to the internal requisition and the anchor for goods receipt, invoice matching and payment. It gives finance visibility of committed spend and a fixed reference to check deliveries and invoices against.

POs are the backbone of spend control: they reduce disputes, prevent overbilling and enable three-way matching. Generating them automatically from catalogue requisitions and matching them electronically is what makes that control affordable at scale — which is exactly what a managed marketplace with contract pricing delivers.

Key takeaways

  • A PO is the buyer's formal, binding commitment to a supplier.
  • It is issued after a requisition is approved; the invoice comes later, from the supplier.
  • The PO number anchors three-way matching of receipt and invoice.
  • POs give finance visibility of committed spend before invoices arrive.
  • Automating PO creation and matching makes control affordable at scale.

Frequently asked questions

What is a purchase order?
A purchase order (PO) is a document a buyer issues to a supplier to formally commit to buying specified goods or services at agreed quantities, prices and terms. It carries a unique PO number and, once the supplier accepts it, becomes a binding commitment. It also anchors the later goods receipt and invoice for matching.
What is the difference between a purchase order and an invoice?
A purchase order is issued by the buyer to place an order — it states what will be bought and at what price. An invoice is issued by the supplier to request payment after delivery — it states what is being billed. In a controlled process the invoice is matched against the PO (and the goods receipt) before it is paid.
What is the difference between a purchase requisition and a purchase order?
A purchase requisition is the internal request for approval to buy; a purchase order is the external commitment sent to the supplier once that request is approved. The requisition controls spend before commitment; the PO makes the commitment and becomes the reference for receipt and invoice matching.
What should a purchase order include?
A purchase order should include a unique PO number, the supplier's details, a clear description of each item or service, quantities, agreed unit prices and totals, applicable tax, delivery address and date, payment terms, and the authorising details. Enough for the supplier to fulfil correctly and for the invoice to be matched later.
How can Lapasar help with purchase orders?
Lapasar generates purchase orders automatically from catalogue requisitions at contract prices, issues them to suppliers, and matches them against goods receipts and consolidated invoices, with ERP punchout to remove rekeying. That gives finance clean visibility of committed spend and reliable three-way matching across Peninsular Malaysia. A free purchase order template is linked below if you are still working manually.

Take it further with Lapasar

Explore related across the knowledge graph

GuideERP integrationConnecting the procurement channel to the ERP so requisitions, orders and invoices flow between systems without manual re-keying.GuideOracle integrationConnecting a supplier catalogue to Oracle procurement and NetSuite through PunchOut so buyers requisition without leaving their system.GuidePunchOut catalogThe catalogue mechanism that lets a buyer shop a supplier's live catalogue from inside their ERP and return a populated requisition.SolutionMicrosoft Dynamics 365 PunchOut in MalaysiaConnect Microsoft Dynamics 365 to the Lapasar marketplace as an external punchout catalog — requisition live items at contract pricing inside D365.SolutionNetSuite PunchOut Integration in MalaysiaConnect NetSuite procurement to the Lapasar B2B marketplace via punchout — requisition live catalogue items at contract pricing inside NetSuite.SolutionPunchout & ERP Integration in MalaysiaConnect Lapasar's B2B marketplace to your ERP via punchout — SAP, Oracle and Coupa. Requisition in your existing workflow with no rekeying.ToolFree Procurement Tools & TemplatesEvery Lapasar procurement calculator plus editable RFQ, purchase order, policy and evaluation templates.TemplateBudget Request FormAn editable Excel and PDF form to itemise, justify and route a budget request for approval.TemplateProcurement SOP TemplateAn editable Word and PDF standard operating procedure covering the buying process from requisition to payment.TemplatePurchase Order Tracker TemplateAn Excel tracker to follow every purchase order from raised to delivered and paid, with automatic status.GlossaryAccounts Payable (AP)Accounts payable (AP) is the money an organisation owes its suppliers for goods and services received but not yet paid for, and the team that manages those payments.GlossaryAccrualsAccruals are accounting entries that recognise expenses which have been incurred but not yet invoiced, so costs appear in the correct period.GlossaryApproval WorkflowAn approval workflow is the defined sequence of authorisations a purchase must pass through before it can proceed, based on rules such as value or category.GuideSAP integrationConnecting a supplier catalogue to SAP and SAP Ariba through cXML PunchOut so buyers requisition without leaving SAP.GlossaryBack OrderA back order is an order for goods that cannot be fulfilled immediately because they are out of stock, to be delivered when stock is replenished.

Put these ideas to work

Talk to our team about consolidating spend, wholesale pricing, credit terms and delivery across Peninsular Malaysia — or request a walkthrough of the marketplace.

Prefer to talk to a real person?

Our team replies fast on WhatsApp and email — no forms, no waiting.