The short version: an invoice says "you owe me." A receipt says "you paid me." Same transaction, opposite ends of it — and mixing them up confuses clients and accountants alike.
It's one of those distinctions that feels obvious once you hear it but trips people up in practice, especially freelancers sending their first few bills. Let's make it permanent.
The core difference
An invoice is a request for payment. It's issued before payment. It lists what was delivered or agreed, how much is owed, when it's due, and how to pay. Its job is to get money moving toward you.
A receipt is proof of payment. It's issued after payment. It confirms that money was received, when, how, and for what. Its job is to close the loop and give the payer evidence.
A bill is the casual sibling of the invoice. In everyday language, "bill" and "invoice" mean the same thing; in business contexts, invoices are the formal document and bills are the informal one.
Here's the sequence for a typical freelance job:
- Work delivered → you send the invoice ("$1,470 due within 14 days")
- Client pays → you send the receipt ("$1,470 received on 7 Oct 2026, thank you")
- Both of you file your copies → everyone's books balance
What's on each document
Invoice: your details, client details, invoice number, invoice date, due date, line items, subtotal, discount, tax, total due, payment instructions. (Full breakdown in our freelance invoice template guide.)
Receipt: your details, payment date, invoice number reference, amount received, payment method (bank transfer, card, cash), and ideally the word "RECEIPT" or a "PAID" stamp so nobody mistakes it for a new bill.
The payment method and date are what make a receipt a receipt — they're the evidence. An invoice without those is just a request.
The "paid invoice" shortcut
Here's a legitimate simplification: take your original invoice PDF, mark it clearly as PAID with the payment date and method, and send that back to the client. A paid invoice functions as a receipt — it ties the original bill to the payment in one document.
This is extremely common among freelancers and small businesses. It's simpler than maintaining two document types, and the audit trail is arguably cleaner since the invoice number, line items, and payment confirmation all live together.
When each one is required
Invoices: required in most B2B relationships and whenever tax/VAT applies — tax authorities generally want a paper trail of what was billed. Even where not legally required, invoice for everything; memory is not an accounting system.
Receipts: legally required in some jurisdictions for certain transactions (retail, cash payments). For services, they're usually good practice rather than law — but good practice matters: a client who needs to claim your fee as a business expense needs that receipt.
Records: both matter at tax time. Your invoices show revenue; your receipts (and the client's) prove what was actually paid. Keep them filed by year, numbered consistently.
Related documents: quotes, proformas, and statements
Invoices and receipts have cousins worth knowing:
Quote / estimate. Sent before the work: "here's what it will cost." Not a request for payment — a proposal. If the client accepts, the later invoice should match the quote (or explain why it doesn't).
Proforma invoice. Looks like an invoice but isn't a payment demand — it's typically used for customs, or to request payment before delivery. Common in international trade. Don't confuse it with a real invoice in your books.
Statement. A summary of multiple invoices and payments over a period: "here's everything outstanding." Useful for ongoing client relationships — one statement replaces five "just checking on invoice #..." emails.
Credit note. The undo button: issued when you need to reduce or cancel a previous invoice (overbilling, returned goods, agreed discount after the fact). It references the original invoice number.
Each has its moment. The discipline is the same throughout: the right document, clearly labeled, at the right point in the money's journey.
Mistakes people make
Sending an invoice after payment. If the client already paid, what you're sending is a receipt. Sending something labeled "INVOICE" with a due date for money already received causes genuine panic in finance departments.
No invoice number reference on the receipt. If a client pays three invoices from you in a year, an unreferenced receipt is a mystery. Always tie the receipt back to the invoice number.
Assuming the bank transfer is the receipt. A bank statement shows money moved; it doesn't show what for. The receipt connects the payment to the work — that's its whole job.
Verbal "we're square." Fine between friends, useless for business. If a payment is ever disputed, the document wins.
Not matching the receipt to the books. File receipts alongside their invoices — physically or digitally — so each transaction's full trail (bill → payment → confirmation) sits together. Scattered documents are how duplicate-payment disputes start.
The one-minute rule
If you're about to send a document about money, ask: has the money moved yet? Not yet → invoice. Already moved → receipt. Get that one distinction right and you'll handle every billing situation correctly — and you can generate the invoice itself in about five minutes.
Note: this article covers general business documentation practices, not professional accounting or tax advice. Rules on invoicing, receipts, and record-keeping vary by country — when in doubt, check with a local accountant.
