Invoice vs Receipt: the Difference and When to Use Each
The two documents get conflated constantly — clients ask for "an invoice" when they need proof of payment, sellers hand over "receipts" for money they have not received yet. The distinction is worth thirty seconds, because it decides what the document must contain, what it proves, and whose records it protects: an invoice is a request for payment; a receipt is evidence of it.
The one-sentence difference, expanded
An invoice travels from seller to buyer *before* money moves. It itemises what is owed, names a deadline, and explains how to pay — it is the opening move of a payment, and until it is paid it represents money you are owed (what accountants call accounts receivable). A receipt travels the same direction *after* money moves. It confirms the amount received, records how it was paid, and closes the transaction.
The timeline is the tell. Work finished, awaiting payment → invoice. Cash handed over the counter, transfer landed, deposit cleared → receipt. Many transactions properly involve both: the invoice opens the file, the receipt closes it, and both carry the same reference number so they reconcile.
What each document must contain
They share a skeleton — both parties, a date, a unique number, itemised amounts, any tax broken out. From there they diverge exactly where their jobs diverge. The invoice carries the machinery of getting paid: a due date, payment terms, and complete payment instructions (bank details, UPI, accepted methods). The full field-by-field checklist is in What to Include on a Professional Invoice.
The receipt instead carries the machinery of proof: the payment date, the method actually used (cash, card, transfer), an explicit PAID marking, and — for partial payments — the amount received against the amount due. It needs no due date and no bank details; asking for money is no longer its business.
Why the paying side cares so much
For the buyer, the receipt is the valuable one. Expense claims, warranty service, returns and audits all ask the same question — "prove you paid" — and an invoice cannot answer it; it only proves someone *asked* you to pay. Employers routinely reject expense reports backed by invoices for exactly this reason. If a customer asks you for "something for my expenses", what they need is a receipt with the payment method and date on it.
For the seller, the invoice is the valuable one: it is the documented basis of the debt. If payment never arrives, the invoice — with its number, date, itemisation and agreed terms — is what you chase with, escalate with, and if it comes to it, take to a collections process or small-claims court. Issuing receipts casually for unpaid amounts hands away that leverage.
Making either one, without new software
Both documents are structured PDFs, and both can be produced in a browser in a couple of minutes. The receipt generator handles the proof-of-payment side — PAID mark, payment method, no due-date clutter — while the invoice generator is the same engine in request-for-payment mode. The two share a data format: save an invoice as JSON, load it into the receipt tool when the payment lands, and the receipt inherits every line item without retyping.
Everything runs client-side — the documents are generated on your device and nothing you type is uploaded — and the totals are computed in integer cents with the discount-before-tax ordering accountants expect. Formatting only, as both tools note: neither document generator is legal or tax advice.
Frequently asked questions
Can one document be both an invoice and a receipt?
In casual point-of-sale trade, effectively yes — a shop till slip requests and confirms payment in the same moment. For anything with a gap between billing and payment, keep them separate: mark nothing PAID until it is, and issue the receipt against the invoice number once the money arrives.
Is a paid invoice the same as a receipt?
Close, but not identical. An invoice stamped or reissued as "PAID", with the payment date and method added, functions as proof of payment and many businesses use exactly that. A dedicated receipt is cleaner because it states the method and date as first-class fields rather than annotations — which is what expense systems look for.
Do receipts need to be numbered like invoices?
Yes, and for the same reasons: unique numbers are how both sides file, find and verify the document later. Keep a separate sequence from your invoices (RCP-001 alongside INV-001) so neither sequence develops gaps when only one kind of document is issued.
Which document do I give for a deposit or advance payment?
Both, in order. Invoice the deposit (or note it as a line on the main invoice), then issue a receipt when it is paid, stating what it covers — "50% deposit against INV-042". The final invoice then shows the deposit as already received, so the balance due is unambiguous.