Purchase Order Process: Steps, Workflow, and Controls

The purchase order process is the workflow that turns an internal buying request into an approved purchase order, supplier delivery, receipt confirmation, invoice matching, exception handling, and final closure. In a typical procure to pay process, it begins when someone requests goods or services and ends only after the organization has confirmed what was received, matched the supplier invoice, resolved any discrepancies, and closed the transaction with a clear audit trail.

Most organizations move through the same core stages:

1. Requisition: A department identifies a need and submits an internal request.
2. Review: The request is checked for budget, policy, and specification accuracy.
3. Approval: An authorized approver signs off based on the company's control rules.
4. PO creation: Purchasing or procurement issues the formal purchase order.
5. Supplier acknowledgment: The supplier confirms acceptance, availability, pricing, or delivery timing.
6. Receiving: Goods or services are delivered and the business records what arrived.
7. Invoice validation: Accounts payable compares the invoice with the PO and, where relevant, receipt evidence.
8. Exception handling: Teams resolve price differences, quantity mismatches, missing references, or partial deliveries.
9. Close-out: The PO is closed once obligations are complete and the records support future review.

That sequence is why a purchase order workflow matters beyond procurement. A well-run process creates the document trail that finance teams rely on later, especially when they need to confirm that an invoice matches an approved commitment and an actual receipt. It also reduces three recurring control problems: non-PO spend, duplicate ordering, and invoices that cannot be validated because the underlying PO was incomplete, outdated, or never approved properly.

---

From Requisition to an Approved Purchase Order

The first half of the purchase order approval workflow determines whether the rest of the process will run cleanly or become a series of manual fixes. It starts with the difference between a purchase requisition and a purchase order. A requisition is an internal request to buy something. A purchase order is the approved external document sent to the supplier. If teams blur those two steps, they often end up treating informal requests, emails, or spreadsheets as if they were authorized commitments.

In practice, the sequence usually looks like this:

1. A requester submits the need, quantity, specification, delivery location, and expected timing.
2. Procurement, finance, or the requester's manager reviews whether the purchase is valid, budgeted, and aligned with policy.
3. The request moves through an approval matrix, which may depend on spend thresholds, departments, project codes, or vendor category.
4. Once approved, the buyer creates the PO with the final commercial details and releases it to the supplier.

The accuracy of the PO at this stage matters more than many teams expect. The document should clearly identify the supplier, PO number, item descriptions, line-item quantities, agreed unit prices, delivery expectations, and any relevant tax, freight, or charge treatment. If any of that is vague, AP inherits the problem later. A missing unit of measure can cause a quantity dispute. An outdated price can trigger a false mismatch. A weak description can make it hard to tell whether the invoice line really belongs to the approved order. That same clarity matters later when manufacturers need to allocate freight, duty, and brokerage costs across received inventory instead of leaving those charges stranded in AP.

Speed also matters, but only when it does not undermine control. According to APQC's benchmark on cycle time to issue a purchase order, the median cycle time to issue a purchase order for services, from requisition to PO release, is 1 day based on data from 1,146 companies. That benchmark is useful because it shows PO issuance is measurable. It should not be read as a reason to skip review steps. A fast but inaccurate PO only moves the exception downstream.

What Happens After the PO Is Sent

Once the PO leaves the buyer's system, the process shifts from authorization to fulfillment and receipt control. The supplier should acknowledge the order, confirm what can be delivered, and flag any changes in price, quantity, or timing. That acknowledgment step sounds administrative, but it is often where teams discover that the supplier is working from different assumptions than the buyer.

The purchase order receiving process typically includes several checkpoints:

1. The supplier ships goods or confirms service delivery.
2. The receiving team or operating department checks what arrived against the PO.
3. The business records a receipt, acceptance, or service confirmation.
4. Open quantities stay visible until the order is fully fulfilled or formally closed.

This stage depends on supporting documents, not memory. A delivery note may show what was shipped. A goods received note (GRN) records what the business actually received and accepted. For service-based POs, that acceptance evidence often takes the form of a service entry sheet before invoice approval. Supplier acknowledgment records whether the supplier agreed to the order as issued or introduced changes that now need to be tracked. If you want a deeper view of what a goods received note adds at the receiving stage, the key point is that the GRN turns physical receipt into evidence AP can rely on later.

Partial receipts are one of the most common weak points in the purchase order lifecycle. If the first shipment is received but the remaining quantity stays open, the records must show that clearly. Otherwise AP may approve an invoice for the full order before the full order exists in reality. The same problem appears when suppliers ship against an outdated PO version or when buyers accept verbal changes without updating the document trail. Receiving records are valuable precisely because they replace assumptions with documented status.

How the PO Connects to Invoice Matching and Close-Out

The finance value of the purchase order process becomes visible when the invoice arrives. At that point, accounts payable is no longer asking only whether the purchase was approved. It is checking whether the supplier invoice matches the approved commitment and, where required, what was actually received.

That review usually starts with a few core checks:

• Does the invoice reference the correct PO number?
• Is the supplier the same party named on the PO?
• Do the descriptions, quantities, and unit prices align with the approved order?
• Has the business recorded receipt or acceptance where the control model requires it?
• Is the PO still open, or has it already been fulfilled or closed?

This is where the difference between two-way matching and three-way matching matters. In a three-way matching purchase order workflow, AP compares the invoice, the purchase order, and receipt evidence such as a GRN or service confirmation. In a two-way match, the comparison stops at the invoice and PO. If you need a broader primer on how invoice matching works after the PO is issued, the important point here is that a purchase order only helps AP if the document is complete enough to support the comparison.

Common exceptions usually fall into a few categories: a price variance from the approved rate, invoiced quantities that exceed received quantities, invoices arriving before receipt is confirmed, invoices submitted against closed POs, or invoices with no usable PO reference at all. When spend arrives without a usable PO, AP usually needs a separate non-PO invoice workflow to document coding, approvals, and control evidence before payment. The resolution should be explicit. Someone needs to confirm whether the variance is acceptable, whether the PO should be amended, whether the receipt record is incomplete, or whether the invoice should be rejected and reissued.

Close-out matters because open POs can distort reporting and hide unresolved obligations. A PO should be closed when the business has received what it expected, resolved any approved differences, processed the related invoice correctly, and documented any residual balance or cancellation. That is why a purchase order process is not complete at approval. The control payoff appears in matching, exception handling, and closure.

---

Who Owns Each Stage and Which Documents Must Stay Aligned

One reason purchase order workflows break down is that the steps exist, but ownership is fuzzy. The names vary by company, yet the responsibilities are usually consistent.

• Requester or department owner: identifies the need and provides the business justification.
• Manager or budget owner: confirms the purchase is appropriate and funded.
• Procurement or purchasing: validates supplier and commercial details, then issues the PO.
• Supplier: confirms acceptance and fulfills the order.
• Receiving, operations, or service owner: records what was actually delivered or completed.
• Accounts payable: validates the invoice against the PO and receipt evidence before payment.

Those roles do not need to sit in separate departments to work well. In a small business, one person may cover several of them. What matters is that each handoff is visible and supported by records. The purchase order process becomes fragile when the same team that requests a purchase also approves it informally, confirms receipt verbally, and pushes the invoice through without independent checks.

The documents also need to stay distinct. A requisition initiates the request. The purchase order communicates the approved commitment to the supplier. The receipt document confirms what arrived. The supplier invoice requests payment. If your team needs a sharper explanation of how purchase orders differ from invoices and work together, that distinction is central to auditability: one document authorizes spend, another confirms receipt, and another asks to be paid.

For downstream validation, a few PO fields carry outsized value: the PO number, supplier identity, item description, quantity, unit price, delivery location, approval evidence, and receipt status. When those elements are inconsistent across documents, the organization spends more time reconstructing what happened than processing the transaction itself.

Common Purchase Order Process Breakdowns and Stronger Controls

Most organizations do not struggle because they lack a diagram of PO process steps. They struggle because the live workflow drifts away from the documented one. A few breakdowns appear repeatedly.

Delayed approvals. Requests sit with approvers, teams chase urgent purchases outside the formal path, and buyers create workarounds. The result is often last-minute ordering and weak evidence of authorization.

Outdated PO versions. A buyer revises quantity, price, or delivery timing, but the supplier or receiving team keeps using an earlier version. That disconnect shows up later as a mismatch that AP has to interpret.

Poor handling of partial deliveries. The business receives part of the order but records it as complete, or records nothing at all. Then the invoice arrives and no one can tell whether the billed quantity is reasonable.

Unauthorized changes and duplicate ordering. Informal amendments, duplicate requests, or rushed reorders create conflicting document trails and increase the risk of paying for something twice.

Non-PO spend. Purchases bypass the process entirely, which removes the approval and matching structure that the rest of the workflow depends on.

Stronger controls do not require a more complicated policy document. They usually require better discipline around a few points:

• clear approval thresholds and escalation rules
• a controlled process for revising POs so everyone works from the same version
• mandatory PO references on supplier invoices where the process requires them
• timely receipt logging for goods and services
• visible tracking of open quantities, approved variances, and exceptions
• separate monitoring of non-PO spend so it is managed as an exception, not treated as normal

A well-run purchase order processing model is really a document-control system. When the PO, receipt record, and invoice stay aligned, receiving decisions are clearer, matching success improves, and finance teams get better visibility into what the business has actually committed to buy.