Invoice vs Receipt: What's the Difference and When Do You Need Each?
An invoice asks for money. A receipt confirms money already changed hands. That's the entire distinction, and almost every follow-up confusion about the two (invoice vs bill, proforma vs invoice, which one to file where) comes back to that one line.
Where it actually gets confusing is in the details: who's supposed to create each one, what information belongs on them, and why a bookkeeper cares about keeping both when they seem to describe the same transaction.
The difference, directly
An invoice is issued before payment. It's a request: here's what you owe, here's what it's for, and here's the date by which we expect to be paid. Its whole purpose is to create a documented payment obligation.
A receipt is issued after payment. It's proof: this amount was received, on this date, by this method. Its purpose is to document that the obligation the invoice created has now been settled.
One creates a debt; the other closes it. If you only remember one thing from this article, that's the one worth keeping.
Invoice vs receipt, side by side
| Invoice | Receipt | |
|---|---|---|
| Purpose | Request payment for goods or services | Confirm payment has been received |
| When issued | Before or at the point of delivery | After payment is received |
| Payment status | Unpaid (becomes 'paid' once settled) | Already paid, a completed transaction |
| Who creates it | The seller, billing the customer | The seller, acknowledging the customer's payment |
| Typical information | Invoice number, line items, tax, total due, payment terms | Amount paid, date paid, payment method, reference to the original invoice |
| Accounting role | Recorded as accounts receivable until paid | Closes out the receivable, matched against the invoice it settles |
A concrete way to see this: a design agency invoices a client $5,000 for a completed project on 1 June, with payment due by 30 June. The client pays by bank transfer on 18 June. The agency then issues a receipt referencing that invoice number, confirming $5,000 received on 18 June via bank transfer. Two documents, two different jobs, twelve days apart.
Invoice vs bill
There isn't a meaningful functional difference: "bill" and "invoice" describe the same document from opposite ends of the relationship. A restaurant hands you a "bill"; a freelance consultant sends a client an "invoice." Some industries lean toward one word out of habit (retail and hospitality say bill; professional services say invoice), but nothing about the content or legal status changes based on which word you use.
Invoice vs purchase order
These sit on opposite sides of the same purchase, and in the opposite order to invoice vs receipt. A purchase order (PO) is issued by the buyer, before the work starts, authorizing the purchase and often specifying a budget or approval reference. The seller then delivers the work and issues an invoice referencing that PO number, so the buyer's accounts team can match the invoice to a purchase they already approved.
This is why so many invoices have an optional "PO / reference number" field: it's not decoration. For larger clients, especially, an invoice without the PO number they issued often gets rejected outright rather than delayed, because their system has no way to reconcile it.
Proforma invoice vs invoice
A proforma invoice looks almost identical to a real invoice (same layout, same line items, same total), but it isn't a demand for payment and it's issued before a sale is fully confirmed. It's most commonly used for:
- International shipments, where customs authorities require a declared value before goods cross a border, ahead of the final commercial invoice.
- Giving a prospective buyer a formal, itemized price to secure internal budget approval, before the seller commits time or inventory to the order.
- Situations where the final quantity or price might still shift slightly before the order is locked in.
Because a proforma invoice doesn't create a binding payment obligation, it shouldn't be recorded in your books as revenue or as an accounts receivable entry. The real invoice, issued once the order is confirmed, is the one that actually gets booked and chased for payment.
Why you need to keep both
It's tempting to think that once a receipt exists, the invoice it relates to has done its job and can be discarded. That's backwards. The invoice is your primary evidence of what was sold, to whom, at what price, and under what terms: details a receipt usually doesn't repeat in full. The receipt is your evidence that the resulting obligation was actually settled.
Tax authorities, auditors, and your own future self reconciling a messy quarter all need both halves of that story, not just proof that money moved. Most jurisdictions require businesses to retain both invoices and receipts for a set number of years: the exact period depends on where you're registered, so check your local requirement rather than assuming a fixed number.
Bookkeeping mistakes to avoid
- Treating "sent" as "paid." An invoice being issued doesn't mean money arrived. Track invoice status (draft, sent, paid, overdue) separately from whether it's been raised at all. See how to create a professional invoice for how that status tracking should work in practice.
- Not linking the receipt to its invoice. A receipt with no reference back to the invoice number it settles is far harder to reconcile months later, especially if a client makes several payments in the same week.
- Discarding invoices once paid. As covered above, the invoice remains the record of what was agreed. Keep it alongside the receipt, not instead of it.
- Recording a proforma invoice as revenue. It isn't a completed sale yet. Booking it as one overstates receivables that don't actually exist.
- Inconsistent numbering between the two. If your invoices and receipts use entirely disconnected numbering systems with no cross-reference, reconciling a busy month becomes a manual search exercise instead of a lookup.