What is Purchase Order vs Invoice?

**A purchase order (PO) and an invoice are both formal business documents used in commercial transactions, but they serve opposite purposes and are issued by different parties.** A purchase order is issued by the buyer before the work or goods are delivered -- it is an authorization document that commits the buyer to purchasing specific goods or services at an agreed price. An invoice is issued by the seller after the work or goods are delivered -- it is a payment request document that demands payment for what has been provided. In a typical B2B transaction, the buyer sends a PO to the vendor to authorize a purchase. The vendor fulfills the order and then sends an invoice referencing the PO number to request payment. The buyer's accounts payable team matches the invoice against the original PO (and often a receiving document) before approving payment -- a process called three-way matching. This workflow creates a clear audit trail and reduces the risk of unauthorized purchases or duplicate payments. For freelancers and small business owners who work with corporate clients, understanding the difference between purchase orders and invoices is essential. Many large companies require a PO before any work begins and will not process an invoice without a valid PO number. Knowing how to handle POs -- and how to request them proactively -- keeps your billing process aligned with corporate procurement requirements.

The purchase order and invoice workflow represents a complete transaction cycle. It begins with the buyer identifying a need and issuing a purchase order that specifies the vendor, items or services requested, quantities, agreed pricing, delivery date, and payment terms. The PO is an internal authorization document that also serves as a contractual commitment to the vendor. The vendor receives the PO, performs the work or delivers the goods, and then issues an invoice that references the PO number. The invoice should mirror the PO in terms of items, quantities, and pricing -- any discrepancies will trigger a hold in the buyer's accounts payable system. When the buyer's team receives both the invoice and confirmation that the goods or services were delivered, they approve payment according to the payment terms in the original PO. For freelancers dealing with corporate clients, the practical implication is that you may need to wait for a PO before starting work. Some procurement departments strictly enforce this policy -- no PO, no payment -- regardless of verbal agreements with your project contact. Building the habit of requesting PO numbers before starting engagements with large clients protects you from invoices that get stuck in procurement approval indefinitely.

Most small freelancers working with individual clients or small businesses will never encounter a formal purchase order process. But freelancers who work with medium to large corporations, government agencies, or academic institutions will frequently be required to have a PO in place before work begins. When a corporate client issues you a PO, treat it as a contractual commitment. Review the terms carefully before accepting -- POs often include payment terms, scope limitations, and liability clauses. If the PO terms differ from what you agreed verbally, address the discrepancy before signing or beginning work. When the work is complete, your invoice must reference the PO number provided. Invoices without PO numbers are frequently rejected or delayed by corporate accounts payable systems that require the PO reference for matching. Including the PO number on your invoice is one of the easiest ways to prevent payment delays with large clients.

Three documents -- purchase order, invoice, and receipt -- represent sequential stages of a transaction. A purchase order is issued before any transaction occurs. An invoice is issued after the transaction is complete but before payment is made. A receipt is issued after payment is collected as confirmation of payment. For a freelancer: you might receive a PO from a corporate client authorizing your services (before work begins), send an invoice after completing the project, and then issue a receipt when the client's payment is received and cleared. Each document has a distinct role in the transaction record. For tax and accounting purposes, all three documents should be retained. The PO establishes the original terms of the engagement. The invoice establishes the payment obligation and is the basis for accounts receivable entries. The receipt or payment confirmation closes the transaction and is used to reconcile accounts.

Best practices for managing purchase orders in your freelance business: 1. Ask about PO requirements at the start of every corporate engagement -- before beginning any billable work, confirm whether a PO is required and request the PO number. 2. Keep PO copies on file -- Store every PO you receive with the associated project files so you can reference them when creating invoices. 3. Reference the PO number on all invoices -- Include the PO number prominently on your invoice to prevent payment holds in the client's AP system. 4. Verify PO amounts before invoicing -- Ensure your invoice amount does not exceed the PO amount without an authorized PO amendment. Invoices that exceed the approved PO amount are typically rejected. 5. Flag scope changes immediately -- If project scope expands beyond the original PO, request an amended PO before doing the additional work.

Eonebill.ai makes it easy to create professional invoices that include all the fields corporate clients need for PO-based payment processing, including PO number fields, itemized line items, and payment terms that mirror the original PO. Use the [free invoice generator](/free-tools/invoice-generator) to build invoices that reference purchase orders correctly and meet the formatting expectations of corporate accounts payable teams. Eonebill Pro and Business plans at [Eonebill pricing](/pricing) let you track which invoices are tied to which purchase orders, monitor payment status across all outstanding invoices, and send automated reminders to clients whose invoices are approaching their due dates.

1. Starting work without a PO when the client requires one: Beginning a project without a PO in a PO-required environment risks having your invoice rejected or delayed indefinitely while procurement processes the approval. 2. Not referencing the PO number on your invoice: This is the single most common reason invoices are held in corporate AP systems. Always include the PO number on every invoice sent to a PO-issuing client. 3. Invoicing for amounts that exceed the PO value: Invoices that exceed the approved PO amount are almost always rejected. Request an amended PO before billing for work beyond the original scope. 4. Confusing a PO with a signed contract: A PO is a procurement document, not a comprehensive service agreement. For large engagements, use both a service contract and require a PO for billing purposes. 5. Losing track of partial PO usage: If a PO covers $10,000 in services and you have invoiced $7,500, you have $2,500 remaining on the PO. Track PO balances to avoid over-invoicing or under-utilizing approved budget.

[Invoice](/glossary/invoice) is the payment request document issued after services are delivered, which should reference the purchase order. [Payment terms](/glossary/payment-terms) are often defined in the purchase order and govern when payment is due. [Accounts payable](/glossary/accounts-payable) is the department at the buying company that processes purchase orders and pays invoices. [Purchase requisition vs PO](/glossary/purchase-requisition-vs-po) describes the internal approval step that precedes the issuance of a purchase order.