A supplier asks for your PO number before shipping. Your colleague says the invoice is already approved. The boxes arrive, but two are missing. These are not three unrelated admin problems. They are signs that the business needs a clear record of what it ordered, what it received and what it owes.
A purchase order (PO) is a document the buyer sends to a supplier to specify an intended purchase. It records the goods or services, quantities, agreed prices, delivery requirements and relevant terms. A PO helps authorize and track the order. An invoice comes from the seller and requests payment. Neither document, by itself, proves that everything was delivered.
This guide follows a small-business purchase from request to payment, with a worked example and a checklist you can adapt. It draws on public procurement guidance, SAP, Microsoft and Oracle documentation, and the US Uniform Commercial Code. Sources were checked on October 12, 2026. Examples are illustrative, not tax or legal advice. Illustrations were AI-generated for this guide and do not show a real purchasing system.
1. What is a purchase order, and what problem does it solve?
Think of a purchase order as the buyer’s agreed purchasing instructions, not a receipt or a payment. It gives the supplier a specific reference for the work and gives your team a record to check later. A useful PO answers four practical questions: who is buying, what is being bought, on what terms, and where or when it should arrive.
A short email can work for a simple purchase, but it becomes harder to follow when someone changes the quantity, a delivery is split or the person who placed the order is away. The PO gathers the order details under one identifier. That identifier can connect the supplier’s confirmation, receiving record and invoice without asking everyone to remember the conversation.
The New York State Comptroller’s purchasing guidance describes a PO as an ordering document that communicates goods or services, price and delivery information. Its agency-specific thresholds are not rules for every private business. The transferable point is simpler: an order needs enough detail to support receiving and invoice checks.
Ordering is different from tracking stock
A PO records a purchasing decision. An inventory record describes stock you actually hold. If 20 items were ordered but only 16 arrived, the PO may still show 20 while the receiving record shows 16. Our inventory management software guide covers the separate stock-control job. Do not increase available inventory just because an order was approved.
Likewise, a PO is one step within procurement, not the whole supply chain. Supplier selection, forecasting, transportation and returns need their own decisions. The wider role of technology in supply chain management helps explain where the purchasing record fits without making it responsible for everything.
2. Purchase order vs invoice vs purchase requisition
The easiest way to distinguish the documents is to ask who creates them and what the next person should do. A requisition asks your own organization for approval. A purchase order tells a supplier what the buyer is ordering. An invoice tells the buyer what the seller is charging. A receiving record says what was delivered or accepted.
| Document | Created by | Main purpose | Typical stage |
|---|---|---|---|
| Purchase requisition | Employee or requesting team | Ask for internal approval | Before the order is issued |
| Purchase order | Buyer | Specify the approved purchase to the supplier | Before fulfillment, subject to the agreed process |
| Supplier invoice | Seller | Request payment for stated charges | According to the agreed billing schedule |
| Receiving record | Receiving employee or service owner | Document actual delivery or acceptance | As goods arrive or services are accepted |
On a small screen, swipe the table sideways to read every column.
In SAP Ariba’s documented workflow, an approved requisition can generate one or more POs, with orders sent to the relevant suppliers. That is a product-specific example of the distinction, not a requirement to buy SAP. Even a spreadsheet process can keep the request separate from the approved order.
Why an invoice cannot replace an approval process
An invoice can arrive after someone has already committed the business to a purchase. Approving it at that point does not give the company the same control as approving the order beforehand. If nobody had authority to place the order, an accounts-payable check may find the problem too late.
Conversely, an approved PO does not tell the bookkeeper to pay any bill with that number. The invoice still needs checking against the agreed price and the relevant delivery or service evidence. Our accounting software comparison addresses the finance system, while the purchasing workflow establishes what that system should be allowed to pay.
Different records may live in different systems. Before connecting them, map which record is authoritative for orders, receipts and payments. The distinction between an enterprise application and an ERP matters here: adding another application does not automatically give every team one consistent source of truth.
3. What information belongs on a purchase order?
A PO should be specific enough that a supplier can fulfill it and another employee can check it without reopening the original chat. Avoid descriptions such as “equipment as discussed.” Identify the product, service scope or specification that both sides actually reviewed.
- Buyer and supplier: correct legal or trading details, contacts and billing address.
- Order reference: a unique PO number, issue date and any contract or quotation reference.
- Line items: description, item code where useful, quantity and unit of measure.
- Charges: currency, unit prices, discounts and agreed shipping or other charges.
- Delivery: destination, requested date, permitted partial shipments and receiving contact.
- Payment and other terms: agreed timing, acceptance criteria and relevant contract references.
- Approval trail: who approved the purchase and which version was sent.
Units and scope prevent avoidable disputes
Ten boxes is not the same as ten individual units. A service priced per hour is not a fixed project fee. Record the unit consistently in the quote, order and receiving check. For a service, name the deliverable or milestone and who can accept it. A vague service line makes a later disagreement harder to settle.
Separate billing and delivery addresses. The finance office may receive invoices while a warehouse receives goods. An address that worked for a previous order is not proof it is correct for this one. If the item changes, record the change rather than expecting the supplier to infer it.
Our guide to supply chain software features provides context for shared records and order visibility. For businesses with multiple stock locations, the warehouse management feature checklist helps connect delivery details to the people who will receive the goods.
Keep sensitive information out of documents that do not need it. A PO does not ordinarily need a card number, password or unrelated employee data. Send the document through the agreed business channel and limit access to the people handling the order. More fields are not automatically better fields.
4. Is a purchase order legally binding?
A purchase order can form part of a binding agreement, but “every PO is automatically binding when created” is too broad. The answer depends on the applicable law, the existing agreement, the document’s terms and how the parties accept or perform the order.
A buyer may send a PO as an offer. A supplier may confirm it, ship goods or respond with different terms. If a master agreement already governs the relationship, the PO may be an order under that agreement rather than the entire contract. A document labeled “purchase order” does not remove the need to understand those conditions.
For US sales of goods, UCC Section 2-206 describes circumstances in which an order for prompt shipment invites acceptance by a promise to ship or by shipment. The provision includes qualifications. It is not a universal rule for service contracts, other countries or every dispute involving an order.
Confirm the terms before the supplier acts
Ask the supplier to confirm the product, price, delivery date and important conditions. If its response changes those terms, resolve the difference before fulfillment where possible. Do not assume that silence means agreement or that an internal manager’s approval means the supplier accepted.
Cancellation deserves the same care. A company may have approved a PO internally, but cancelling an accepted order can involve supplier costs or contractual obligations. Check the agreed route and terms before telling someone the purchase can be reversed without cost.
For large orders, custom goods, cross-border transactions or conflicting terms, get qualified legal advice. Operational records help show what happened, but this guide cannot determine whether a particular agreement is enforceable. The supply chain risk management guide offers broader planning context, not a substitute for reviewing the actual contract.
5. A purchase-order workflow from request to payment
A practical workflow keeps responsibilities clear without making every small purchase a committee meeting. Use the steps below as a starting point, then adapt approval thresholds and exceptions to your business. There is no single dollar threshold that applies to every company.
- Define the need. Record what is required, why, quantity and desired delivery date. Check existing stock or commitments first.
- Confirm budget and authority. Route the request to the person allowed to approve it. Approval should happen before ordering unless a documented exception applies.
- Confirm the supplier and quote. Check specifications, terms, charges and the correct business contact.
- Create and approve the PO. Give it a unique reference, complete the lines and keep the approved version.
- Send and confirm. Dispatch it to the supplier and resolve differences in the acknowledgment.
- Receive and inspect. Record actual quantities, damage, missing items or accepted service milestones.
- Check the invoice. Compare the order, invoice and required receiving evidence; resolve exceptions.
- Pay and close. Follow agreed payment terms, record payment and close only the completed commitment.
Name the owner of each handoff
The buyer does not have to be the receiving employee, and the receiving employee does not have to approve payment. In a small business one person may hold several roles, but another person should review higher-risk purchases where practical. The objective is accountability, not an impressive-looking workflow chart.
A short purchasing meeting agenda can clarify who approves requests and how exceptions are escalated. After those rules are settled, the ERP selection guide helps evaluate whether software supports them. Do not let a default setting become your purchasing policy by accident.
Keep status labels meaningful. “Approved” means permission to order, not delivered. “Received” should reflect actual evidence, not an expected date. “Closed” should not hide an unresolved invoice or return. An employee should be able to identify the next action from the status without guessing.
6. A worked purchase-order example with a partial delivery
Consider an illustrative office purchase: 20 desk organizers at $25 each, with $40 agreed shipping. The merchandise total is $500, and the total before any applicable tax is $540. Those numbers describe this example only; they are not vendor prices or a tax calculation.
The buyer creates PO-1042 with the product description, quantity, USD currency, delivery address and supplier-confirmed terms. The supplier acknowledges the order. When the delivery arrives, the receiving employee counts 16 organizers, checks their condition and records four still outstanding.
What each document says
The PO still records the agreed order of 20. The receiving record says 16 arrived. An invoice for 20 does not make the other four delivered. The accounts-payable employee should investigate the difference under the company’s matching rules instead of approving the full quantity simply because the PO exists.
If the supplier bills only the 16 delivered units, the merchandise amount is $400. How shipping is allocated needs agreement; do not invent a prorated shipping charge. If the remaining four are backordered, keep that commitment visible. If they are cancelled, document the agreed change and any credit or revised invoice.
Now suppose the invoice lists $27 per organizer rather than $25. That is a separate price discrepancy. Receiving the correct quantity does not make the new unit price correct. Check whether there was an approved amendment or a supplier error before payment.
This example explains why order visibility and stock accuracy need separate records. Our warehouse software comparison covers receiving and stock workflows, while the supply chain software selection guide helps assess broader coordination. A tool is useful only if the people counting boxes can update the relevant record.
For a service purchase, replace the count with acceptance evidence. A signed milestone review, agreed time record or delivery approval may be more relevant than a warehouse receipt. Define that evidence in advance so the invoice checker does not have to decide what “completed” means after the work is billed.
7. Standard, blanket, planned and contract purchasing documents
You may encounter several purchasing document names. They describe different ways to manage a commitment, but terminology and supported features vary between organizations and software. Do not select a document type solely because a blog calls it more advanced.
Standard purchase orders
A standard PO usually suits a defined purchase when the items or service scope, quantity, price and delivery requirements are known. The office organizer example is a straightforward use. It gives both parties a specific order to fulfill and reconcile.
Blanket purchase agreements
A blanket arrangement can support recurring purchases from a supplier over a period, with agreed items or pricing but individual delivery schedules still to be determined. Releases or separate orders can authorize actual deliveries. Track the spending limit and remaining commitment; the arrangement should not become permission for unlimited buying.
Planned orders and contract agreements
Oracle’s purchasing documentation distinguishes planned POs, with a longer-term commitment and tentative schedules, from contract purchase agreements that set terms without specifying every later item purchase. Its terminology belongs to that documented system; your application may use different names.
The practical choice depends on what you know now and what will be decided later. If quantities are unknown, do not fill in invented quantities merely to complete a form. If the business has committed to a minimum spend, make that commitment visible even before all releases are scheduled.
The benefits of ERP include coordinating related records, but more structure also means setup and training. Review the ERP challenges and drawbacks before choosing a large implementation for a process a small team can manage clearly today.
8. Invoice matching, controls and when to use software
Two-way matching compares the invoice with the PO. Three-way matching adds the receiving record. Microsoft Dynamics 365 Finance documentation describes matching prices to PO lines and quantities to product receipts, with configured tolerances. That supports a control principle, not a promise that every system uses identical rules.
A match is not a guarantee that the supplier is legitimate or that a purchase was wise. It asks whether particular records agree. Keep supplier verification, authority to buy and payment-detail checks separate. A false document can still match another false document.
Handle exceptions instead of hiding them
Set a route for shortages, substitutions, price changes and duplicate invoices. Give each exception an owner. Record what changed and why it was approved rather than repeatedly editing the original order until the records appear to match. Emergency purchases need a documented exception process, not backdated approval presented as if it occurred beforehand.
A spreadsheet can be sufficient when orders are few, responsibilities are clear and the team keeps versions reliably. Consider software when duplicate entry, lost approvals, partial receipts or multiple locations make that process hard to control. Evaluate change history, permissions, receipt handling, invoice links and export options before comparing attractive dashboards.
Our cloud supply chain software guide gives a broader shortlist context. The enterprise application integration guide helps frame connections between purchasing, warehouse and finance systems. Integration should preserve identifiers and responsibilities, not copy inconsistent data faster.
Automation can extract document fields or flag a mismatch, but someone still needs authority to approve a changed commitment. Read our workflow automation explanation alongside the cybersecurity and digital transformation guide when deciding who can view, edit and approve purchasing records.
9. Purchase-order questions businesses ask
Does every purchase need a purchase order?
No universal rule requires a PO for every private-business purchase. Requirements can come from company policy, supplier terms, a contract or applicable public-procurement rules. A company might use POs for stock and higher-value services while handling approved routine expenses another way. Define the exceptions and approval route explicitly rather than letting employees guess.
Who creates the PO, and who creates the invoice?
The buyer creates or issues the PO; the supplier creates the invoice. A system may generate either document, but that does not change its role. The buyer’s finance team can help check the order without becoming the supplier. Keep the PO number and invoice number separate, since one order may be linked to several invoices.
What is a PO number?
It is the buyer’s reference for an order. It helps connect confirmations, deliveries, invoices and related communications. Use a consistent numbering scheme and avoid duplicate numbers. The number is an identifier, not proof of approval or delivery. Ask the supplier to include it on relevant paperwork, then check the actual order details rather than relying on the number alone.
Can I change or cancel a purchase order?
Possibly, subject to the accepted terms and applicable law. Confirm the supplier’s position, record the amendment and obtain the required internal approval. Do not overwrite the original without a change history. If production has started or goods are custom-made, cancellation may have costs. A software “cancel” button does not settle those contractual questions.
Is a purchase order the same as proof of payment?
No. A PO records the order, an invoice requests payment and a payment record shows the transfer or settlement. A receiving record addresses delivery. Keep them connected but distinct. When a supplier asks whether an invoice was paid, check the finance record and reference rather than sending the PO as if it proves money changed hands.
How do we start without buying another system?
Choose one simple purchase and document the request, approved PO, supplier confirmation, receipt and invoice check. Assign the owner of each step, then test a partial delivery and a price mismatch. Keep a register of open orders and a clear change history. Fix the process first; buy software when you can describe the recurring work it should remove.
The practical test: someone who did not place the order should be able to tell what was authorized, what arrived, what is owed and what remains open. If your records answer those questions, the PO is doing useful work rather than adding another form.
