Invoice vs Receipt: What Is the Difference?

The core difference

An invoice is issued before payment (or before the final payment clears) and asks for money. A receipt is issued after payment and confirms money was received. One creates a receivable on your books; the other marks that receivable as settled.

Mixing the labels causes real operational problems. If you mark a paid document "Invoice", a client may pay twice, or their system may keep showing the balance as open. If you only ever issue receipts and never invoices, you lose a clear audit trail of what was owed and when it was due.

Side-by-side comparison

	Invoice	Receipt
Purpose	Request payment	Confirm payment
Timing	After delivery (or at a milestone), before payment	At or after payment clears
Includes due date	Yes	Usually no
Amount meaning	Amount owed	Amount received
Used by buyer for	Approving and scheduling payment	Expense claims, warranty, returns, tax records
Creates a receivable	Yes	No
Typical label	"Invoice" plus unique number	"Receipt" or "Payment confirmation"

When you need both

For most B2B work you issue an invoice first, then a receipt (or a paid stamp / payment confirmation) when the transfer clears. The receipt should reference the original invoice number so both parties can match documents during reconciliation.

For retail, café, or instant online checkout, a receipt alone is often enough because payment and delivery happen at the same moment. There was never an unpaid balance to track. Even then, some business buyers still ask for a formal tax invoice for reclaim purposes, so ask before you assume a till receipt is enough.

What each document should include

On the invoice

• Unique invoice number, issue date, and due date
• Seller and buyer legal details
• Itemised lines, tax breakdown, and total due
• Payment instructions

On the receipt

• Confirmation that payment was received (amount and date)
• Payment method (card, bank transfer, cash)
• Reference to the invoice number being settled
• Seller details and a receipt or confirmation number

If a payment only partially settles an invoice, say so clearly: "Partial payment of £800 against invoice 2026-0041; balance £1,600 remaining." Ambiguous partial receipts create disputes months later.

Accounting and tax angle

Invoices support revenue recognition and receivables tracking. Receipts support proof of settlement and, for buyers, expense evidence. Tax authorities often want both sides of the story for larger B2B transactions: the tax invoice showing tax charged, and evidence that it was paid.

Never treat a bank statement line alone as a substitute for a proper receipt when a client asks for one. The statement proves money moved; the receipt ties that money to a specific invoice and supply.

Common mistakes

• Labelling a paid document "Invoice" without marking it paid: clients may pay twice or file it as unpaid.
• Issuing a receipt with no reference to the original invoice number.
• Using receipts as your only sales record, which makes year-end reconciliation painful.
• Sending a receipt before funds clear (especially cheques or slow international wires).
• Changing totals on a "receipt" to match what the client paid when the invoice was wrong. Fix the invoice with a credit note instead.

How bookkeeping treats each document

On accrual books, issuing an invoice typically records revenue and a receivable. Receiving payment clears the receivable and increases cash. The receipt is operational proof for the customer and a useful attachment for your records; the accounting event is the payment match against the invoice. Cash-basis businesses may recognise income when paid, but they still benefit from invoices as a way to track what is outstanding.

If you only issue receipts, you lose a clean list of unpaid work. If you only issue invoices and never confirm payment, customers chasing expense reports ask you for documents you never prepared. Budget a few minutes to close the loop every time money clears.

Retail, marketplaces, and card payments

Card terminals and online checkouts often produce a payment receipt automatically. That receipt proves the card charge. For a business buyer who needs a tax invoice, you may still need to issue a separate document with registration numbers and a proper breakdown. Ask early whether they need a tax invoice for reclaim or whether the card receipt is enough.

Marketplaces sometimes remit net of fees. Your invoice to the end customer, if any, and your payout report from the platform are different artefacts. Do not assume one PDF satisfies both sales documentation and creator payout reconciliation.

Disputes, refunds, and chargebacks

When a refund happens, document it with a credit note or refund receipt that references the original invoice and payment. Chargebacks are easier to contest when you can produce the invoice, the delivery evidence, and the receipt together. Keep them filed under the same client and year so retrieval takes seconds, not hours.

Partial refunds should state the remaining balance explicitly. Ambiguous refund emails that never become documents are how both sides end up with different memories of what was settled.

Labelling paid invoices clearly

Some businesses stamp the original invoice PDF "PAID" instead of issuing a separate receipt. That can work if the stamp includes payment date and method, and if your client accepts it for their records. When in doubt, send a short separate receipt that references the invoice number. It takes a minute and prevents double-payment risk.

Never change the invoice total after payment to match a wrong transfer. Issue a credit or request the balance; altered history undermines audits.

Practical workflow

1. Deliver the work or ship the goods.
2. Create and send a numbered invoice (PDF).
3. Record the receivable in your books or tracker.
4. When payment clears, mark the invoice paid and send a receipt referencing that number.
5. Store both PDFs together by year and client.

For related distinctions, see invoice vs estimate and invoice vs quotation. To create the unpaid document correctly the first time, use the free invoice generator.