Invoice Generator ยท 7 min read
Invoice vs Receipt: What's the Difference and When Do You Need Each?
Many small business owners use invoices and receipts interchangeably. They are not. Here is how to tell them apart and when to use each one.
The Confusion Is Common โ and Costly
A freelancer sends a client a PDF called "Receipt" when they should send an "Invoice." A retail business hands a customer a document that looks like a receipt but is missing the fields required of an invoice. A taxi driver issues a receipt for a one-time ride but a corporate passenger needs an invoice for expense reporting.
The difference is not semantic. It is legal and financial. An invoice and a receipt serve different purposes, are issued at different times, and have different required fields. Using one when you should use the other can trigger tax disputes, payment delays, and accounting errors.
What Is an Invoice?
An invoice is a request for payment issued before or at the time of delivery. It says: "Here is what you ordered, here is what it costs, and here is when I expect payment."
Key characteristics:
- Timing: Issued before payment is received (or at the time of delivery).
- Purpose: To request payment and provide a record of the transaction for the buyer's accounting system.
- Required fields: Invoice number (unique and sequential), buyer and seller details, description of goods/services, quantity, rate, due date, tax breakdown, and payment instructions.
- Who issues it: The seller (the person requesting payment).
- Who keeps it: Both buyer and seller keep it for accounting and tax records.
Example: A consultant sends an invoice on 1 May for work completed. The due date is 30 May. The client receives the invoice, enters it into their accounting system, processes approval, and pays by 30 May.
What Is a Receipt?
A receipt is acknowledgment that payment has been received. It says: "You paid me this amount on this date for this product/service."
Key characteristics:
- Timing: Issued after payment is received.
- Purpose: To prove to the customer that payment was made (for their records) and to provide the seller with a record of the transaction for tax and accounting purposes.
- Required fields: Receipt number (unique and sequential), date, amount received, payment method, description of goods/services, and seller details. Tax details depend on jurisdiction.
- Who issues it: The seller (the person who received the payment).
- Who keeps it: Both buyer and seller.
Example: A customer buys a shirt at a shop for โน500, pays cash, and receives a receipt. The receipt proves they paid. If they return the shirt later, the receipt proves when and where they bought it.
Key Differences: A Side-by-Side Comparison
| Aspect | Invoice | Receipt |
|---|---|---|
| Issued when | Before payment / at delivery | After payment received |
| Purpose | Request for payment | Proof of payment |
| Payment status | Payment pending | Payment completed |
| Due date | Always included | Not applicable |
| Unique number | Invoice #001, #002, etc. | Receipt #001, #002, etc. |
| Tax handling | Tax shown separately (CGST/SGST in India) | Tax shown separately |
| Typical use | B2B, large purchases, credit terms | Retail, cash sales, proof of purchase |
| Payment method shown | No (not yet paid) | Yes (cash, card, UPI, etc.) |
Real-World Scenarios
Scenario 1: Freelance Consultant
A designer completes a branding project on 10 May. Payment terms are Net 30 (due by 10 June). The designer sends an INVOICE on 10 May. The client pays on 5 June. The designer sends a RECEIPT on 5 June acknowledging payment. Both documents are kept for accounting records.
Scenario 2: Retail Shop
A customer buys items totaling โน5,000 and pays by card immediately. The shop issues a RECEIPT. No invoice is needed (the sale is complete and payment is immediate). If the customer later wants to return the goods, they produce the receipt as proof of purchase.
Scenario 3: Corporate Buying
A small software company provides services to a large corporation. A PO (purchase order) is issued first. The software company delivers the service and sends an INVOICE referencing the PO number. The corporation receives and processes the invoice (often 30 days to pay by their standard terms). Once paid, the corporation may request a RECEIPT for their accounting records. Both documents are kept.
Why the Difference Matters for Taxes
Tax authorities care about two things: what was sold and when payment was received. An invoice proves what was sold and when. A receipt proves when payment was received. For B2B transactions in India, both are legally required: an invoice for the sale and a receipt (or payment confirmation) for the payment.
If you issue a receipt instead of an invoice, the buyer cannot enter it into their accounting system (it lacks required fields). If you issue an invoice without a receipt, there is no proof of payment. GST compliance specifically requires invoices for B2B sales and proper record-keeping of payments received.
The Bottom Line
- Use an invoice: When you are requesting payment from a client (B2B, freelance work, services, large purchases with payment terms).
- Use a receipt: When you have received payment from a customer (proof of purchase, cash sales, immediate payment).
- Use both: For large B2B transactions, issue an invoice first and a receipt when payment clears.
References
- GST Council. (2017). Central Goods and Services Tax Act, Section 31 & 35. Government of India.
- HMRC. (2023). Invoice and VAT records: what you must keep. UK Government.
- ISO/IEC 7498-1:1994. ISO basic reference model for open systems interconnection. International Organization for Standardization.
- Federation of Small Businesses. (2023). Invoices and receipts guide. FSB UK.