Spark Inventory

Ideas for inventory operators

Purchase Order vs Invoice: What Each Does

Practical guidance on demand planning, purchasing, multichannel operations, and building a healthier inventory business.

A supplier says an order is ready to ship, finance has received a bill, and your warehouse is waiting for stock. If the documents do not line up, the purchase order vs invoice question becomes more than bookkeeping. It determines whether you receive the right inventory, pay the right amount, and keep an accurate view of incoming supply and working capital.

For an operations leader at a growing product business, the short answer is simple: a purchase order authorizes what you intend to buy before the supplier fulfills it. An invoice requests payment for what the supplier says it has provided. They refer to the same commercial transaction, but they serve different decisions and happen at different points in the workflow.

Purchase Order vs Invoice: The Core Difference

A purchase order, or PO, is created by the buyer and sent to the supplier. It records the items, quantities, agreed prices, delivery location, expected delivery date, payment terms, and any other conditions of the purchase. Once accepted, it gives both sides a reference for what should arrive.

An invoice is created by the supplier and sent to the buyer. It states what the supplier is charging, when payment is due, and usually references the PO, shipment, or delivery. Depending on the supplier relationship, the invoice may arrive before shipment, with the shipment, or after goods are received.

The timing matters because each document answers a different operating question. The PO asks, “What are we authorizing and expecting?” The invoice asks, “What are we being asked to pay?” Neither document, by itself, proves that inventory has physically arrived in the warehouse.

That third event is receiving. A receiving record confirms the quantity your team actually counted and accepted. In a controlled purchasing process, the PO, receipt, and invoice are compared before payment. This is commonly called three-way matching.

What a Purchase Order Controls

A PO is an operational commitment. It converts a reorder recommendation into a clear instruction to a supplier and gives your team a record of incoming inventory.

For example, a planner may see that a SKU has 18 days of supply left, while its supplier lead time is 35 days. The reorder recommendation might call for 600 units based on the per-SKU forecast, open demand, on-hand stock, incoming inventory, and the inventory policy for that item. When the operator approves the draft purchase order, the PO documents that 600-unit commitment at the agreed cost and expected arrival date.

That expected arrival date is not a minor detail. If it slips, your available inventory position changes. A system that tracks incoming POs can distinguish between stock you own today and stock that is expected but not yet received. That distinction prevents a common spreadsheet error: treating an open order as if it were already available to sell.

A good PO also provides a control point before cash is committed. The buyer can review supplier minimums, case-pack constraints, freight assumptions, and unit cost before sending the order. If demand has softened, the operator may reduce quantities. If a promotion or wholesale commitment has changed the forecast, they may increase them. The purpose is not to make purchasing slow. It is to make the approval explicit.

What an Invoice Controls

An invoice starts the payment side of the transaction. It should identify the supplier, invoice number, invoice date, payment due date, items billed, quantities, unit prices, taxes or freight where applicable, and the total amount owed.

For operations, the invoice matters because a mismatch can reveal an issue that affects both inventory and margin. Perhaps the supplier billed 500 units but only 460 were received. Perhaps the unit cost differs from the PO because a price increase was not reflected in the order. Perhaps freight was added unexpectedly. These are not merely accounts payable exceptions. They can change landed-cost assumptions, inventory valuation workflows, and future reorder decisions.

There are legitimate reasons for differences. A supplier may partially ship an order, substitute an item after approval, bill freight separately, or invoice a deposit before production. The right response depends on the agreement and the supplier's terms. What matters is that your process distinguishes an expected difference from an unexplained one.

An invoice should not be used as the source of truth for what is inbound. It may confirm that a supplier has billed you, but it does not replace the PO's expected delivery date or the warehouse's receiving record.

The Workflow That Keeps Inventory and Cash Aligned

For most product businesses, the cleanest sequence is forecast, reorder decision, purchase order, supplier confirmation, receipt, invoice matching, and payment. The steps can overlap, but the records should remain distinct.

Start with the demand signal. Historical sales alone are not enough when you sell across marketplaces, wholesale, and direct channels. A useful forecast accounts for sales across channels, seasonality, current on-hand inventory, open orders, supplier lead times, and the policies that define acceptable stock coverage.

Next, decide what to purchase. This is where a buying plan should show the recommended quantity, timing, supplier, expected cost, and the stock risk the order is meant to prevent. The operator should be able to adjust the recommendation before approving a draft purchase order.

Then receive against the PO, not against memory or a supplier email. If the shipment is short, damaged, or split across deliveries, record what actually arrived. Your inventory count and available-to-promise position should reflect receipts, while the remaining PO balance stays visible as incoming inventory.

Finally, match the invoice. A practical three-way match compares the approved PO, the receipt, and the supplier invoice. If all three align, payment can move forward under your normal approval policy. If they do not, route the exception to the person who can resolve it, whether that is purchasing, receiving, or accounts payable.

This process can feel formal for a small team, but it becomes more valuable as purchase volume and SKU count grow. Without it, excess payments, duplicate invoices, unexpected cost changes, and phantom inbound inventory become harder to spot.

Common Purchase Order and Invoice Mistakes

The first mistake is creating POs after the supplier has already shipped. That may satisfy a system requirement, but it removes the approval control and leaves no reliable record of the original quantity, cost, or expected date.

The second is closing a PO when the invoice arrives rather than when goods are fully received or formally canceled. An invoice can be valid for a partial shipment. Closing the PO too early makes the remaining inbound quantity disappear from planning.

The third is treating supplier lead time as fixed. A PO date is a plan, not a guarantee. When a supplier confirms a new ship date or your warehouse records a delay, update the expected receipt date. Your reorder recommendations should recalculate against the new incoming timing, especially for SKUs approaching a stockout.

The fourth is approving invoices without checking unit price and quantity against the PO and receipt. Teams sometimes skip this on trusted supplier relationships. That may be reasonable for a low-value recurring expense, but inventory purchases directly affect cash and stock records. The higher the value or variability, the more useful the match becomes.

Where Modern Inventory Operations Help

The practical challenge is not understanding the definitions. It is maintaining a single source of truth when demand, supplier dates, and warehouse receipts keep changing.

Spark uses Demand ESP to create a per-SKU forecast from sales across channels, including seasonality, then combines that with on-hand and incoming inventory, supplier lead times, and inventory policies. It identifies stock risk and prepares reorder recommendations and draft purchase orders. The operator reviews, adjusts, and approves before anything is sent or committed.

Text with Sparki makes the approval step more usable when you are away from your desk. Sparki can text a low-stock or stock-risk alert, answer what needs reordering, and let the operator reply YES to create a draft purchase order from their phone. The order remains a draft for review and approval, rather than becoming an automatic supplier commitment.

Spark MCP also gives teams a more current option than legacy inventory software built around static screens and manual exports. With OAuth, operators can use supported AI assistants to map and validate connected data, ask operational questions, and approve what enters the system before it is imported. The goal is governed execution, not handing purchasing decisions to an unattended agent.

A PO should tell your supplier what you intend to buy. An invoice should tell your finance team what the supplier expects to be paid. Keep both tied to actual receiving, and your inventory plan stays grounded in what is ordered, what has arrived, and what still needs attention. Spark and Text with Sparki handle that flow by turning stock risk into reviewable draft purchase orders, while keeping operator approval at the center.

All Spark Inventory Blog articles