What Is a Purchase Order (PO)? A Practical Explainer

A purchase order is a document issued by a buyer to a seller authorizing a specific purchase. It lists what is being bought, how much of it, at what price, with what terms, shipped to what address, and on what schedule. Once accepted by the seller, the PO becomes a legally binding contract for that specific transaction.

The purchase order is often described as the 'first document in the procure-to-pay cycle,' and that framing captures most of what matters about it. A PO is the record that says: this purchase was authorized, by this person, at this price, for this delivery. Every subsequent document in the cycle — the receipt, the invoice, the payment — traces back to the PO to be validated. Without a PO, the validation loop breaks, and invoices get paid on trust rather than on control.

What a Standard Purchase Order Contains

POs vary in layout across systems, but the content is consistent. Every functional PO captures the same set of facts — what was bought, from whom, under what terms.

Purchase Order vs. Purchase Requisition

The purchase requisition (PR) is an internal request — someone in the company asking to buy something. The purchase order is external — an issued commitment to a specific vendor. The requisition comes first, gets reviewed and approved internally, and then becomes the basis for the PO. In small organizations the two documents collapse into one step; in larger ones they are distinct and serve distinct control purposes.

The control reason for separating them: the person who requests a purchase (the requisitioner) should generally not also be the person who authorizes it (the approver) or who receives the goods (the receiver). The PR-to-PO sequence creates natural segregation of duties, with approval and vendor commitment as separate acts.

Why POs Matter for AP

From an accounts payable perspective, the PO is the control document that validates every incoming invoice. Three questions need to be answered before any invoice is paid: was this purchase authorized, was it actually delivered, and does the invoice match both of those? The PO answers question one definitively. Without a PO, question one has no clean answer, which forces AP to either trust the submitting department or issue exceptions on every invoice.

PO-Based vs. Non-PO Invoicing

Not every invoice has a PO. Utility bills, recurring subscriptions, professional service retainers, and small administrative expenses often flow through AP without a PO — either through direct allocation against an approved budget or through a simplified non-PO workflow. The right split between PO and non-PO invoicing depends on organizational structure, spend category, and internal controls policy.

A common control pattern: all spend above a threshold (e.g. $2,500) requires a PO, all spend below can flow through non-PO approval routing. Some spend categories (utilities, rent, insurance) are exempt from PO requirements even above the threshold because their recurring nature makes a PO redundant. The policy is the record of which invoice types require what form of authorization.

The PO and 3-Way Matching

The PO is one of the three documents in the classic 3-way match: PO, receipt, invoice. The invoice gets compared against the PO to confirm the purchase was authorized (vendor matches, items match, price matches, total is within tolerance). The receipt gets compared to confirm the goods or services were actually delivered. Only when all three documents align does the invoice clear for payment.

For the 3-way match to work, the PO has to be in the system before the invoice arrives. An invoice that shows up referencing a PO that doesn't exist is an exception. An invoice that references a PO but includes items not on the PO is an exception. An invoice whose total exceeds the PO total beyond tolerance is an exception. All three exceptions point back to the PO as the source of truth for what was authorized.

Blanket POs and Release POs

Not every PO is for a single one-time purchase. Two common variants handle recurring purchases more efficiently. A blanket PO authorizes a total dollar amount with a specific vendor over a defined period (e.g. 'up to $50,000 from Acme Electrical Supply, Jan-Dec 2026'). Release POs are issued against the blanket PO for each specific delivery, and the blanket PO's remaining authorization decreases as releases are issued.

Blanket POs work well for predictable recurring purchases from preferred vendors. They reduce the administrative overhead of issuing dozens of small POs while preserving the control benefit (the vendor relationship, the total authorization, and the price terms are all captured upfront). Release POs create per-delivery traceability without requiring a new approval workflow for each one.

POs in Construction Specifically

Construction POs have some distinct patterns. Material POs are issued to suppliers for specific job-site deliveries and include job and cost code allocations so the accounting matches the project. Subcontractor agreements — which function similarly to POs for subs — are usually handled as separate subcontract documents rather than as POs, but the control principle is the same: the subcontract authorizes the scope and dollar amount before any pay app is approved.

The operational challenge in construction is that field supervisors frequently need to make real-time purchases — an unexpected material need, an equipment rental, a specialty tool. A purely rigid PO policy breaks down when the supervisor can't wait for a formal PO process. The practical answer is a two-track policy: formal POs for planned purchases, and a well-controlled field purchasing mechanism (with per-project and per-supervisor dollar caps) for real-time needs, with a reconciliation step that rolls field purchases back into proper job costing.

POs and the Vendor Master

The PO is the moment where the vendor master database earns its keep. A PO issued to a vendor that isn't in the master at all, or that's flagged for compliance reasons (expired W-9, lapsed insurance, suspended license), should not be able to clear the issuance gate. The tighter the connection between PO issuance and vendor master integrity, the less likely it is that non-compliant vendors start accruing payables behind the scenes.

Automation's Role

PO generation, approval routing, and matching against incoming invoices are all highly structured workflows — ideal candidates for automation. Modern AP platforms generate POs from approved requisitions, route them through configurable approval hierarchies, issue them electronically to vendors, receive acknowledgment, and maintain the full audit trail. When invoices arrive, automated 3-way matching validates them against the PO and the receipt within seconds, and only exceptions land in a human queue.

The end state of a mature automated PO operation: 70-85% of PO-backed invoices clear automatically within hours of receipt, exceptions are resolved with full context in minutes rather than days, and the AP analyst spends their time on genuine judgment questions rather than manual comparison.

Bottom Line

The purchase order is one of the oldest and least exciting documents in business — and also one of the most operationally important. It turns informal purchasing into controlled purchasing, creates the audit trail that AP needs to validate every invoice, and makes 3-way matching possible. Every organization that skips POs 'to move faster' eventually reintroduces them after a duplicate payment, a phantom vendor, or a scope dispute teaches the lesson the hard way. Starting with POs costs less than recovering from their absence.