Invoice vs. Receipt vs. Estimate vs. Quote vs. Purchase Order

Last reviewed on April 24, 2026.

Five documents show up again and again in small-business billing, and they're routinely used as if they meant the same thing. They don't. Each one has a specific job — proposing work, authorising work, billing for it, or confirming payment. Mixing them up causes slow payments, disputed scopes, and tax-time confusion. This guide defines each document, shows where it fits in the transaction, and gives a worked example that uses all five.

A map of the transaction

Before the definitions, it helps to see the sequence. For a typical service or product sale between two businesses, documents flow like this:

1. The buyer asks for pricing.
2. The seller replies with an estimate or quote.
3. The buyer confirms by issuing a purchase order (or by simply accepting the quote).
4. The seller delivers the work or product.
5. The seller sends an invoice.
6. The buyer pays.
7. The seller sends a receipt.

Not every transaction has all five documents — a retail sale goes straight from order to receipt — but for business-to-business work where the scope or price isn't fixed in advance, most of them appear.

Quick comparison

Estimate

An estimate is an approximate price, offered before you commit to the work. It's most common in fields where final cost depends on what gets uncovered during the job — building renovations, car repair, rolling consulting work. A good estimate names the scope it assumes, lists the major cost drivers, gives a range rather than a single number, and states clearly that the figure is not a firm offer.

Typical wording: "This is an estimate, not a fixed quote. Actual cost may vary depending on the condition of the existing floor." The buyer understands it's an opening ballpark, not a commitment.

Quote

A quote is a firm price, good for a specified time. When a buyer accepts a quote within its validity window, a contract is usually formed on those terms. Quotes belong to work where the scope is knowable up front: a logo design, a website build, a fixed-scope consultation, a set of deliverables.

A solid quote contains a unique quote number, the client's details, a clear scope, the total price broken down by line item, applicable taxes, the payment terms, and an expiry date. The expiry date matters — without one, you can be held to a price for longer than you intended.

Purchase order

A purchase order, or PO, is the buyer's formal commitment to buy. Mid-size and larger companies use POs to get spending through their own approval system before a supplier starts work. A PO carries a unique number that the supplier is expected to reference on the later invoice — this is how the buyer's accounts-payable team matches the invoice back to an approved spend.

If you work with corporate clients, always ask whether a PO is needed before delivering. Invoices without a referenced PO are commonly rejected in corporate AP systems and held up for weeks. When a PO arrives, save the PO number immediately into your records, and put it on every document that follows — the delivery note, the invoice, and any reminders.

Invoice

An invoice is a seller's formal request for payment for goods or services already delivered (or, in the case of deposits and milestones, for a step that has been agreed). It is not just a total — it has structural requirements, because in most tax systems an invoice is a piece of commercial evidence.

At minimum, an invoice should show: the word "Invoice," a unique invoice number, the date, the seller's business details, the buyer's details, a clear description of what's being billed, the amount due, any tax, payment terms, and how to pay. The how-to-write-an-invoice guide covers each field in detail, and the invoice-numbering guide covers how to design the number sequence so it supports your records.

Receipt

A receipt confirms that payment has been received. Where an invoice says "you owe me," a receipt says "you've paid me." Receipts matter because they close the loop: the buyer needs one for expense claims, tax deductions, and warranty proof; the seller needs a copy to reconcile the invoice against the bank transaction.

A receipt typically references the original invoice number, shows the amount paid, the payment method, and the date received. For card payments it may also show the last four digits of the card and an authorisation code. If you accept payments through a service like Stripe, PayPal, or Square, the service usually generates receipts automatically on your behalf.

Worked example — a website project

To see how the five documents fit together, follow a single project from start to finish.

1. Initial conversation. A small shop asks a web designer to quote for a four-page website.
2. Estimate (optional). The designer sends a rough estimate: "Around $2,000–$2,800 depending on final page count and whether online ordering is included." This is not binding.
3. Quote. After a scoping call, the designer sends a firm quote: "Quote Q-2026-041: four-page marketing site with contact form and basic SEO, $2,400, valid for 14 days." The shop accepts the quote in email.
4. Purchase order. Because the shop uses a bookkeeping tool, they raise PO PO-0087 and email it to the designer, committing to the $2,400.
5. Delivery. The designer does the work and launches the site.
6. Invoice. The designer sends invoice 2026-0147 for $2,400, referencing PO PO-0087 on the header so the shop's accounts team can match it.
7. Payment. The shop pays by bank transfer on day 27.
8. Receipt. The designer sends a short receipt referencing invoice 2026-0147: "Payment of $2,400 received on 19 June 2026. Thank you."

The sequence is clean because every document points to the one before it. The quote has a number, the PO references the quote, the invoice references the PO, and the receipt references the invoice. A dispute at any step is easy to resolve because the paper trail is linear.

Common mistakes

• Sending a quote and calling it an estimate. If you gave a firm price and the buyer accepted it, you've offered a quote. Calling it an estimate afterwards doesn't remove your commitment.
• Invoicing without a PO at a corporate client. The invoice gets bounced by accounts payable and you find out three weeks later.
• Using the same number for an invoice and a receipt. They need different identifiers; sharing numbers makes reconciliation painful.
• Sending no receipt at all. Clients should not have to chase you for proof of payment. Send it automatically when the money clears.
• Treating an emailed "sounds good" as a purchase order. Fine for small clients, risky for larger ones where AP follows a strict process.

Related guides

• How to Write an Invoice: Complete Guide
• How to Send an Invoice: Email, PDF, and Follow-Up
• Invoice Numbering Systems Explained
• Invoice Payment Terms: Net 15, Net 30, and Beyond