GoWin Tools
Tools
โ† Purchase Order Generator

Purchase Order Generator ยท 5 min read

PO numbers explained: what they are and why they matter for accounting

A PO number is more than a reference code. It enables three-way matching, connects invoices to approved budgets, and provides the audit trail that finance teams and external auditors depend on.

A purchase order number is a unique identifier assigned to a purchase order at the time of creation. It appears on the PO itself, on any related goods receipt documentation, and must be quoted on the supplier's invoice. This single reference number is the thread that connects three separate documents โ€” the order, the receipt, and the invoice โ€” and enables the matching process that sits at the heart of accounts payable control.

What a PO number is and what it is not

A PO number is an internal identifier created by the buying organisation. It is not assigned by the supplier, not issued by a bank, and not regulated by any external body. The buying organisation controls the numbering format, the sequence, and the logic behind it. A supplier who receives a PO is expected to reference that number on their invoice โ€” they do not create or modify it.

Suppliers sometimes confuse a PO number with an order number from their own system. These are distinct. The buyer's PO number and the supplier's sales order number both refer to the same transaction but exist in different systems. When both appear on a supplier invoice, it is the buyer's PO number that matters for the buyer's accounts payable process.

How PO numbers enable three-way matching

Three-way matching is the core accounts payable control that prevents duplicate payments, overpayments, and fraudulent invoices. It works by comparing three documents before releasing payment:

  • The purchase order: what was ordered, at what price, in what quantity.
  • The goods receipt note (GRN) or service confirmation: what was actually received or delivered.
  • The supplier invoice: what the supplier is claiming payment for.

The PO number is the key that links all three. The AP system retrieves the PO using the number on the invoice, then retrieves the GRN associated with that PO, and compares the three documents. If the invoice quantity matches the GRN quantity and the invoice price matches the PO price (within defined tolerance levels), payment is released automatically. If anything diverges, the invoice is flagged for human review.

Without a PO number on the invoice, this process cannot run automatically. The invoice must be routed to a human to identify the correct PO โ€” if one exists โ€” adding days or weeks to the payment cycle. Ardent Partners' AP research consistently identifies "missing PO number on invoice" as one of the top five causes of invoice processing delays in corporate finance functions.

Common PO number formats

There is no universal standard for PO number format. Organisations design their numbering schemes based on internal reporting needs, system constraints, and the volume of purchases they process. Common approaches include:

  • Sequential integers: PO-0001, PO-0002, PO-0003. Simple, unambiguous, works for any volume. The limitation is that the number alone carries no information about department, year, or category.
  • Year-prefixed sequential: 2026-0001, 2026-0002. Allows easy identification of which financial year an order belongs to without looking up the document. Useful for audit and reconciliation.
  • Department-prefixed: IT-2026-0042, MKT-2026-0017. Adds a department or cost centre code to the prefix. Useful in larger organisations where multiple departments issue POs and reports need to be filtered by department.
  • ERP-assigned: Enterprise systems like SAP, Oracle, and Microsoft Dynamics generate PO numbers automatically using configurable number ranges. SAP S/4HANA allows organisations to define number range intervals per purchasing organisation, ensuring that different business units do not generate conflicting numbers.

Whatever format is chosen, the key requirements are uniqueness (no two POs should ever share the same number) and persistence (a PO number, once assigned, should never be reassigned to a different purchase).

What happens when PO numbers mismatch

PO number mismatches โ€” where the number on the invoice does not match any open PO in the buyer's system โ€” are among the most disruptive problems in accounts payable. When a mismatch occurs, the typical resolution path involves: routing the invoice to the requestor or procurement team, identifying whether a PO was issued and if so what the correct number is, correcting the invoice or creating a PO retrospectively, and manually approving payment. This process takes time and creates reconciliation work.

Common causes include suppliers quoting a PO number from a previous order, typographical errors in the PO number on the invoice, suppliers issuing invoices before a PO has been raised (particularly for urgent purchases), and internal teams placing orders without going through the PO process.

Organisations that strictly enforce the policy "no PO, no payment" โ€” where invoices without a valid, open PO reference are returned to the supplier unpaid โ€” see the highest rates of PO compliance from their supplier base, because the commercial consequences of non-compliance are immediate and consistent.

PO numbers in ERP systems

In enterprise resource planning systems, the PO number is the primary key that connects purchasing, inventory management, and accounts payable. When a PO is created, the system reserves budget against the relevant cost centre or project code. When goods are received, the GRN is matched to the PO. When the invoice arrives, it is matched to the PO and GRN and the corresponding accounting entries are made automatically.

This integration means that a single PO number, followed through the system, generates a complete audit trail: who approved the purchase, what was ordered, when it was received, whether there were any quantity or price discrepancies, and when and how payment was made. External auditors and internal audit functions rely on this trail to verify that purchases were properly authorised and that the organisation did not pay for goods it did not receive.

Best practices for small businesses

Small businesses without ERP systems benefit from the same discipline applied through simpler tools. A spreadsheet or a dedicated PO tool that assigns sequential numbers and records each PO creates the same audit trail at a fraction of the cost. The key practices are: always issue a PO before committing to a purchase, always include the PO number on the order sent to the supplier, always ask the supplier to quote the PO number on their invoice, and always file invoices against the corresponding PO for easy retrieval. These habits significantly reduce payment disputes and simplify year-end accounting.

References

  1. Burt, D. N., Petcavage, S., & Pinkerton, R. (2019). Supply Management (9th ed.). McGraw-Hill Education.
  2. Ardent Partners. (2023). Accounts Payable Metrics That Matter. Ardent Partners Research.
  3. CIPS. (2021). Best Practice Guide: Purchase to Pay. Chartered Institute of Procurement and Supply.
  4. SAP SE. (2023). SAP S/4HANA Procurement documentation: Purchase order number ranges. SAP Help Portal.
  5. Institute of Internal Auditors. (2022). Global Technology Audit Guide: Auditing Smart Devices and the Internet of Things. IIA.