Purchase Order vs Purchase Request: What's the Difference and When to Use Each
If you've spent five minutes researching purchasing workflows, you've run into both terms and probably wondered: aren't these the same thing? They're not. They sit at different points in the buying process, they're sent to different people, and they have different legal weight.
Here's the plain-English explanation, with real examples.
The short answer
- A purchase request (PR) is an internal document. Someone on your team asks the company for permission to buy something.
- A purchase order (PO) is an external document. Once approved, your company sends a formal order to the vendor.
The PR happens first. The PO happens after approval, and only if you choose to issue one.
Side-by-side comparison
| Purchase Request (PR) | Purchase Order (PO) | |
|---|---|---|
| Audience | Internal (manager, owner) | External (vendor) |
| Purpose | Get approval to spend | Place a binding order |
| Sent to | Approver inside your company | Supplier/vendor |
| Legal status | None — internal record | Contract once accepted by vendor |
| Created by | Requester (any employee) | Buyer / fulfiller (after approval) |
| Includes | What, why, estimate, justification | Exact items, prices, terms, PO number |
| When in process | Step 1 (before approval) | Step 3 (after approval, before payment) |
A real example
Sarah works in marketing at a 20-person agency. She wants to buy a $1,200 stock photo subscription.
Step 1 — Purchase Request: Sarah opens her company's approval app and submits a request: "Annual Shutterstock Pro subscription for the design team, $1,200, vendor: Shutterstock, category: Software, justification: replaces three individual seats and saves $400/year."
This is her PR. It goes to her manager.
Step 2 — Approval: Her manager reviews. She approves.
Step 3 — Purchase Order: The agency's office manager (the fulfiller) generates a PO: a numbered document sent to Shutterstock with the exact items, billing details, and PO number "AGY-2026-0142." Shutterstock invoices back referencing that PO number. Their AP team can match the invoice to the PO before paying.
Step 4 — Receiving + Payment: The subscription is activated. The receipt is uploaded back to the original request. The invoice gets matched (PO + invoice + receipt = three-way match). Payment goes out.
When small businesses skip the PO
Here's the honest reality: most small businesses don't formally issue POs for every purchase. They go straight from PR → approval → buy → receipt.
That's fine for:
- Small purchases under a few hundred dollars
- Card transactions (the card swipe IS the order)
- Subscriptions and recurring services
- Trusted vendors with established invoice flows
You should issue a PO when:
- The purchase is over a few thousand dollars
- The vendor specifically requires one (many large vendors do)
- You're working with a new vendor
- The order is custom, made-to-order, or has long lead time
- You need to lock in pricing and terms before fulfillment
- You're in an industry where POs are standard (construction, manufacturing, healthcare)
Why POs matter even for small businesses
Three reasons:
1. Legal protection. A PO is a written offer. When the vendor accepts it (by acknowledging, shipping, or invoicing against it), you have a binding contract with agreed-upon terms. Without a PO, you're relying on email threads and verbal agreements — which fall apart when something goes wrong.
2. Three-way match. When the invoice arrives, your finance team can verify: the PO authorized the purchase, the receipt confirms delivery, the invoice matches both. This catches errors and fraud. Without a PO, you're just trusting the invoice.
3. Budget tracking. A PO commits budget at the moment of order, not at the moment of payment. This gives you accurate "encumbered" spend numbers, which matters when you're tight on cash flow.
The full lifecycle: PR → Approval → PO → Receipt → Invoice → Payment
For a complete picture, here's the standard purchasing lifecycle:
- Purchase Request (PR) — internal ask
- Approval — manager/owner says yes
- Purchase Order (PO) — formal order to vendor (skipped for small purchases)
- Receiving — confirm what was delivered matches the PO
- Invoice — vendor bills you
- Three-way match — PO + receipt + invoice agree
- Payment — AP pays the invoice
For more on three-way match, see our guide on three-way match for small businesses.
What a small business actually needs
If you're a 5–50 person team, here's the realistic stack:
- Always: A purchase request system (so you have approval records)
- Sometimes: Formal POs for purchases over a threshold (often $1,000–$2,500)
- Always: Receipts captured and attached to requests
- Sometimes: Three-way match for vendors over a threshold
You don't need a full procurement suite. You need a clean approval workflow that captures the request, the approval, and the receipt — and lets you optionally issue a PO when it matters.
That's exactly what Becision does. Submit requests in 60 seconds, route approvals automatically, capture receipts, and generate POs when needed. Free for small teams. Try it →
Common questions
Q: Is a purchase request the same as a requisition? Yes — "purchase requisition" is the older, more formal term. "Purchase request" is more common today, especially in software tools.
Q: Do I need a PO if I have an approved request? Not always. For small purchases on a card, the approval is enough. For larger purchases, a PO protects you legally and operationally.
Q: Who creates the PO? Usually a designated buyer (office manager, ops lead, or AP person). In smaller companies, it's whoever is fulfilling the request.
Q: Do POs need to be signed? Most small business POs are sent electronically without a signature — your authorized issuance is the contractual offer. Larger or contract-heavy POs may require signatures from both sides.