Home › Guides › Invoice vs. Receipt

Invoice vs. receipt: what's the difference?

Invoices and receipts often look nearly identical — both list what was bought, from whom, and for how much — but they serve different moments in a transaction and shouldn't be used interchangeably.

The short version

An invoice is a request for payment, sent before money changes hands. A receipt is proof of payment, given after money changes hands. If the document is asking to be paid, it's an invoice. If it's confirming payment already happened, it's a receipt.

Invoice: request for payment

You send an invoice when you've delivered goods or services and are asking to be paid — it establishes the amount owed, the due date, and how to pay. Invoices are used in credit-based transactions: the work happens (or the goods ship) first, and payment follows on agreed terms, often 15, 30, or 60 days later. An invoice is also a formal accounts-receivable record for you and an accounts-payable record for your customer — it's what gets matched against a purchase order and what triggers the payment process on their end.

Receipt: proof of payment

You issue a receipt once payment has actually been received — it confirms the amount paid, the date, and the payment method. Receipts matter for the customer's own records (expense tracking, reimbursement, tax deductions) and for you as confirmation that a transaction is closed. Point-of-sale purchases (retail, restaurants, in-person services) typically skip the invoice step entirely and go straight to a receipt, since payment happens at the same moment as the sale.

Side-by-side comparison

	Invoice	Receipt
When it's sent	Before payment	After payment
Purpose	Request payment	Confirm payment received
Includes a due date	Yes	No — payment already happened
Typical use case	B2B billing, freelance work, credit terms	Retail, point-of-sale, confirming a payment

Do you ever need both?

Yes — for a credit-based sale, it's common to send an invoice first and then, once the customer pays, send a payment receipt as confirmation. This is especially useful for larger transactions or when the customer specifically requests proof of payment for their own records.

Where credit notes and debit notes fit in

Neither of these is a receipt, but both are common follow-ups to an invoice that get confused with one. A credit note is issued by the seller to reduce or cancel an already-invoiced amount — for a return, a billing error, or a discount applied after the fact — and reduces what the customer owes without confirming any payment happened. A debit note works the other direction: it increases the amount owed on an existing invoice, typically to correct an undercharge. Both reference the original invoice number rather than standing alone, and neither replaces sending a receipt once payment for the corrected amount actually arrives.

What a receipt needs to include

A receipt is shorter than an invoice but still needs to be complete enough to serve as proof of the transaction:

• A receipt number — unique, same reasoning as an invoice number.
• The date payment was received — not an issue date or due date, since neither applies once payment is done.
• What was paid for — a description matching the original sale or invoice, referencing the invoice number if there was one.
• The amount paid, and the payment method (cash, card, bank transfer, check).
• Seller and buyer details — same as an invoice, so it's identifiable as a standalone record.

Unlike an invoice, a receipt should not include a due date or payment instructions — both would be meaningless once payment has already been made, and including them tends to confuse whoever receives the document about which stage of the transaction it represents.

Digital vs. paper receipts

A digital receipt (PDF, emailed, or generated at point of sale) is now standard for most transaction types and is generally accepted anywhere a paper one would be, provided it contains the same information. Some jurisdictions and industries still have specific paper or point-of-sale-system requirements for certain transaction types (particularly cash sales in retail) — if you're in a regulated retail category, it's worth confirming your local requirement rather than assuming a PDF is always sufficient.

Mistakes that cause real problems

• Sending an invoice after payment has already been made — at that point it should be a receipt, not an invoice with a due date that's already moot.
• Omitting the payment method on a receipt — it's one of the few fields that specifically belongs on a receipt and not an invoice.
• Editing and resending an invoice instead of issuing a credit note — once an invoice has been sent (and especially once partially paid), correct it with a credit note that references the original, not a silently modified duplicate.
• Treating "paid invoice" and "receipt" as identical — a paid invoice still shows the original request-for-payment framing (due date, terms); a proper receipt is framed as confirmation, which some customers specifically need for their own expense or tax records.

Common questions about invoices and receipts

Is a receipt legally required for every sale?

It depends on your jurisdiction and industry — many places require receipts for retail transactions above a certain amount, or specifically for cash transactions, while others leave it to business discretion outside a few regulated categories (fuel, alcohol, and regulated services often have specific rules). Check your local requirements if you're unsure; this varies enough that there's no universal answer.

What's a credit note, and is it the same as a receipt?

No — a credit note is issued by the seller to reduce or cancel an amount already invoiced (for a return, an error, or a discount applied after the fact), not to confirm a payment was received. It reduces what the customer owes or is owed back; a receipt confirms money already changed hands. They're both follow-up documents to an original invoice, but for opposite reasons.

Can a receipt double as an invoice?

Not really, because they document different moments — a receipt confirms payment already happened, so it doesn't need (and normally shouldn't have) a due date or payment instructions. For point-of-sale transactions where payment happens immediately, businesses often skip a separate invoice and issue only a receipt, since there's no gap between the sale and payment to document separately.

Do I need to keep copies of receipts I issue?

Generally yes, for your own bookkeeping and in case a customer disputes a transaction or needs a duplicate later — retention periods for business records vary by jurisdiction, commonly several years. This isn't a substitute for checking your specific local requirement.

What information does a receipt need that an invoice doesn't?

A receipt should show the payment method used (cash, card, bank transfer) and, ideally, a payment confirmation or transaction reference — details that don't apply to an invoice since payment hasn't happened yet. A receipt also generally omits a due date, since one isn't needed once payment is already complete.

Make either one

Our invoice generator supports both document types — including a dedicated receipt generator — so the layout and fields match whichever one you actually need.

Create a Document