# Invoice vs Receipt vs Quote: What Each Document Does (and When to Send Which)

> The three documents every service business confuses — quotes propose, invoices demand, receipts confirm. What each must contain, the legal weight of each, and the workflow connecting them.

Canonical: https://brightdesk.app/blog/invoice-vs-receipt-vs-quote  
Last updated: 2026-07-13  
Author: Brightdesk Team  
Category: Invoicing

Small businesses lose real money to document confusion: work started on a "quote" the client never accepted, payments claimed against an "invoice" that was actually a receipt, disputes with no paper showing what was agreed. The fix is understanding that quotes, invoices, and receipts are three different speech acts — *propose*, *demand*, *confirm* — and using each at its moment. Here's the complete breakdown.

## The One-Line Definitions

- **Quote (quotation/estimate):** "Here's what this will cost if you say yes." Sent *before* work. Creates no obligation to pay.
- **Invoice:** "Work is done (or due) — please pay this amount by this date." Sent *after* work or at an agreed milestone. Creates a receivable.
- **Receipt:** "I received your payment." Sent *after* money arrives. Creates proof of payment.

One transaction can involve all three: quote → (acceptance) → work → invoice → payment → receipt.

## Quotes: The Proposal

A good quote contains: your business details, a quote number (its own series, e.g. `QUO-2026-0014`), itemized scope with prices, taxes indicated, **validity period** ("valid 14 days" — never leave prices open-ended), and payment terms that will apply. 

Key legal nuance: an *accepted* quote plus commencement of work starts to look like a contract — which is exactly why the quote's wording matters and why serious engagements should still get a [real contract](https://brightdesk.app/blog/how-to-write-a-contract) with terms beyond price. A quote alone doesn't authorize you to invoice; acceptance does. Get acceptance in writing, even one line: "Confirmed, please proceed."

**Estimate vs quote:** an estimate signals approximation ("roughly ₹40–50k"), a quote commits to numbers. Say which one you're giving; clients remember the lower number of any range.

## Invoices: The Demand

The invoice is the only document of the three that creates a legal receivable — the paper you'd stand on in a dispute or recovery. Its essentials: sequential [invoice number](https://brightdesk.app/blog/invoice-number-formats), issue date and **due date**, itemized lines mirroring the accepted quote, taxes ([GST rules](https://brightdesk.app/blog/gst-invoice-format-guide) if registered), amount due, and how to pay.

Timing rules of thumb:

- Deliverable-based work: invoice on delivery, same day
- Milestone/retainer work: invoice each milestone per the agreed schedule
- Event services: [advance invoice at booking, balance before the event](https://brightdesk.app/blog/photography-payment-terms)

An invoice the client disputes isn't void — it gets corrected via credit note, never silently deleted; your invoice trail is your income record for tax.

## Receipts: The Confirmation

Receipts are the most-skipped document — and skipping them creates the worst disputes, because *payment* is the fact most often contested. A receipt needs: receipt number (own series), date, amount received, mode (UPI/cash/bank), what it was for (invoice number reference), and the remaining balance if partial.

That last field is the underrated one. For businesses collecting advances and instalments, every receipt should state: "Received ₹50,000 against invoice INV-2026-0871. Balance due: ₹91,600 by 10 Nov." Each receipt then doubles as a gentle statement of account. (GST-registered businesses receiving advances have a formal version of this — the receipt voucher — covered in the [invoice rules guide](https://brightdesk.app/blog/gst-invoice-rules-2026).)

Cash payments especially demand receipts, in both directions: the client wants proof they paid; you want an unambiguous record of what came in.

## The Confusion Matrix (What Goes Wrong)

| Mistake | Consequence |
|---|---|
| Working off an unaccepted quote | "We never agreed to that price" |
| Sending an invoice as a quote ("just so you know the cost") | Numbering polluted; client thinks they owe money — or ignores real invoices later |
| Calling a receipt an invoice | Books show income demanded twice |
| No receipt for cash/partial payments | "We already paid the full amount" |
| [Proforma invoice](https://brightdesk.app/blog/proforma-invoice-guide) treated as a tax invoice | GST/credit mess for both sides |

## Run Them as One Flow

The three documents share 90% of their data — client, line items, amounts. Retyping that into three separate templates is where errors (and mismatched totals) creep in. In a connected system, the booking holds the agreed services, the invoice is built from it, and every payment recorded against it updates the amount received and balance due — [Brightdesk](https://brightdesk.app/auth/login) does precisely this for service businesses, free, so every job carries its complete paper trail from booking to final payment.

## Related

- [All blog posts](https://brightdesk.app/blog)