Purchase order vs invoice: ordered, received, and billed

A purchase order records the buyer’s authorized order to a supplier; an invoice records the supplier’s request for payment. In a purchase order vs invoice review, compare what was ordered with what is being billed, then use receiving records to establish what arrived. A PO number on an invoice connects the documents but does not prove delivery or payment approval.

Keep each document’s owner and status visible. The buyer needs the supplier commitment, receiving needs the delivered quantity, and accounts payable needs the amount awaiting review or payment. One invoice can cover only part of an order, so paying it can leave an open delivery obligation.

Separate the order, sales order, receipt, and invoice

The purchase order comes from the buyer. It identifies the supplier, items or services, quantities, prices, and requested delivery details. Intuit’s purchase-order documentation describes a PO as communicating an intent to buy and distinguishes that from vendor acceptance. Retain acceptance and agreed terms instead of assuming a sent document proves the supplier agreed to every field.

Here, authorized means approved under the buyer’s purchasing policy. It is not a conclusion that every document labeled PO creates the same legal obligations. Keep the governing agreement and accepted revisions available when someone needs to resolve a commitment. The purchase requisition vs purchase order comparison covers the earlier distinction between an internal request and a supplier-facing order.

The sales order is the seller’s order record. A supplier may assign its own sales-order number to your PO, so preserve both references. Microsoft’s Business Central sales-order documentation separates sales orders, shipments, and invoices and provides an external-document field for customer references. A supplier’s sales-order confirmation is not the same document as its request for payment.

The goods receipt records the delivery. Receiving should identify what arrived, when, where, and against which order line. Record accepted, held, or rejected quantities according to your operation’s definitions. Microsoft’s vendor-invoice overview describes product receipts as partial or complete deliveries and allows invoices to refer to partial receipt quantities. It also supports non-PO invoices, so a missing reference requires the applicable approval policy rather than an invented order.

The invoice comes from the supplier. It carries the billed quantities or service amounts, charges, invoice date, and payment terms. Intuit’s document definitions call a supplier invoice a bill from the receiving business’s perspective. The supplier sends an invoice; your accounts payable team may enter that same claim (with its supplier reference retained) as a bill.

Connect document numbers without replacing them

The PO number belongs to the buyer’s ordering record, while the invoice number belongs to the supplier’s billing record. Store both, along with supplier identity, buying entity, currency, and line references. A short number reused by another supplier cannot safely identify the same invoice.

Do not assume a one-to-one relationship. Oracle’s 26D invoice-matching documentation permits multiple invoices against one purchase order and one invoice against multiple purchase orders. Keep the allocation at the line or schedule level so an invoice spanning two orders does not appear to settle both in full.

Preserve source units beside any conversion. If an invoice bills six cartons of ten pieces, its quantity is sixty pieces after conversion, not six pieces. Keep product price, freight, and tax in separate fields so a total difference does not get mislabeled as a price increase on the item.

Reconcile a partial delivery and its invoice

Consider a hypothetical order for component C-12, with all item quantities measured in individual pieces and all amounts in US dollars. PO-1042, line 10, orders 100 pieces at $12 each: $1,200 in goods. The example terms allow $30 freight on the first delivery; the invoice states tax separately. Supplier sales order SO-880 refers back to PO-1042.

The first delivery contains sixty pieces, all accepted under receipt RCV-291. Invoice INV-577 bills those sixty pieces at the agreed $12, plus $30 freight and $57.60 tax. The tax amount is an illustrative input, with no jurisdiction or tax treatment assumed. No quantity is canceled or returned in this example.

Remaining goods quantity = 100 ordered - 60 accepted = 40 pieces. Remaining unbilled goods value = 40 × $12 = $480. That $480 excludes any later freight or tax; it is not a forecast of the final cash payment. The $807.60 settlement closes this invoice under the example’s assumptions, without establishing that the rest of the order arrived.

Keep these statuses descriptive instead of treating them as universal ERP labels. The purchase order tracking process follows outstanding quantities, date changes, and receiving dispositions. A system-specific header status needs interpretation before it becomes evidence that the supplier has fulfilled the order.

Check document meaning before payment review

Use a document check to find missing evidence before deciding whether a charge should be approved. An invoice total that agrees with the PO total can still refer to another location, an earlier revision, or goods not yet received. These checks establish what needs review; they do not grant payment authority.

• A supplier reuses a short invoice number. Can the record distinguish supplier, buying entity, currency, and prior submissions before treating it as new?
• The invoice cites the original PO price after a revision. Can the reviewer locate the accepted version and its effective date?
• A carton conversion changes between order and delivery. Are original units and the applicable conversion retained beside the normalized quantity?
• The invoice is marked paid after a partial receipt. Can the buyer still see the unreceived quantity without reopening the invoice?

When the documents disagree, preserve the original claim and its review history. Do not overwrite the purchase order to make an invoice appear consistent without the required change approval. The three-way matching process covers the separate workflow for comparing order, receipt, and invoice evidence and resolving exceptions.

Where Permute fits across purchasing records

Permute sells connected business data, custom applications, and governed context for AI tools. We can scope a purchasing view around permitted NetSuite or QuickBooks records and supporting documents in Google Drive. Item and supplier references need agreed matching rules, with source identifiers retained when records are connected.

We use declared definitions to keep ordered, accepted, billed, and paid measures distinct. A buyer or accounts payable reviewer can ask which delivery an invoice covers and inspect the linked evidence through a scoped application or an AI tool such as Claude or ChatGPT. Verify source access and refresh behavior before relying on the view for a live decision.

Keep commitment and payment authority explicit

We do not decide whether disputed terms are enforceable or choose your accounting and tax treatment. A connected report does not approve a purchase, release payment, or change a supplier record. Any execution needs a separately verified, supported workflow with explicit authorization and current permissions; linking documents does not provide that authority.

A purchase order records the authorized purchase, and an invoice records the supplier’s claim for payment. Receiving evidence explains which part of the order arrived. Preserve the references and units across those records, with freight and tax separate from goods. A paid invoice can coexist with an open order when a delivery remains outstanding.

Questions about purchase orders and invoices