Purchase Order vs Invoice
A purchase order is a buyer-issued authorization and supplier-facing commitment for specified goods or services, quantities, prices, delivery, and terms. An invoice is a seller-issued request for payment for goods or services supplied. An invoice should reference but does not create the buyer's original purchase authority.
Seller and buyer, invoice number, issue and due dates, supplied lines, quantities, rates, tax, currency, purchase reference, credits, amount due, and payment details.
Receipt or service acceptance, two-way or three-way match, tolerances, exceptions, approval, payable, payment, project cost, client treatment, and close.
Make the definition traceable to authoritative purchase records.
A trustworthy procurement, matching, purchase-order, invoice, supplier, or vendor concept names its object, perspective, lifecycle boundary, source, owner, evidence, authority, and consequence.
Define the object and boundary
Name the entity, buyer or seller, supplier, client and project, contract or policy, request, order, receipt, invoice, payment, currency, period, rule, and what is included or excluded.
Align authoritative inputs
Use consistent identities, references, versions, dates, quantities, rates, amounts, currencies, tax, statuses, delivery or acceptance evidence, approvals, adjustments, and source systems.
Record the decision or transition
Preserve the rule, tolerance, authority, actor, time, source objects, variance, evidence, communication, and downstream supplier, payable, payment, project, client, access, or accounting action.
Keep uncertainty and exceptions visible
Show missing sources, mismatches, disputed terms, duplicates, partial delivery, credits, refunds, changed details, corrections, and the recovery owner.
Questions that prevent a misleading procurement conclusion.
Use these prompts when designing source-to-pay processes, matching invoices, managing suppliers, releasing payments, communicating with stakeholders, or choosing software.
purchase order vs invoice, answered.
Why does this definition matter?
Without stable boundaries, teams can confuse sourcing with purchasing, treat an invoice as purchase authority, pay without delivery evidence, or split one supplier across duplicate records.
Can software determine the legal or accounting treatment?
Software can apply selected rules, but accountable owners and qualified professionals must choose policy, evidence, authority, tolerance, tax, legal, and reporting treatment.
How should a team apply this page?
Map one real purchase or supplier relationship, identify authoritative records and owners, then test the normal path, a correction or reversal, and a meaningful exception.
Make the definition operational.
Connect it to authoritative records, ownership, evidence, limitations, and recovery.