Invoice vs receipt vs quote: which document when

Three documents track every transaction from “how much would it cost?” to “thanks, paid in full” — and using the wrong one at the wrong moment causes real confusion: clients who treat quotes as bills, tax records built on receipts that don’t exist, deposits paid against documents that commit nobody to anything. Here’s the clean version.

The quote: a priced promise, before the work

A quote (or quotation) answers what would this cost? — in writing, before anything is agreed. It lists the proposed work and prices, and it binds in one direction only: if the client accepts, you’ve committed to those prices for the stated scope; the client has committed to nothing until they say yes.

Two practical rules make quotes safer. Date-limit them (“valid 30 days”) so an accepted quote from last spring can’t resurrect old pricing. Match their structure to your future invoice — same line items, same language — so when the invoice arrives it looks like the quote coming true, which is exactly the feeling that gets invoices approved fast.

An estimate is the quote’s vaguer cousin: a good-faith approximation for work whose scope isn’t knowable up front (repairs behind a wall, debugging of unknown depth). Label it honestly — the word “estimate”, prominently — and state the assumption that changes it (“assumes standard shutoff valves; corroded fittings billed at hourly rate”). In some places consumer-protection rules limit how far a final bill may exceed an estimate, so the safe practice everywhere is simple: when reality diverges, tell the client before the extra work, not on the invoice.

The invoice: the formal request for payment

The invoice is the document with legal and accounting weight: it says the work is done (or the milestone hit), and payment of this amount is now due under these terms. It creates the receivable in your books and, in VAT/GST systems, it’s the document tax authorities regulate — UK invoices have a required field list, Indian GST invoices even more so. Every field is covered in the field-by-field guide, and the generator builds one in a minute.

The invoice’s identity comes from its unique number — the handle both sides use in every conversation about it afterward. Send it when the thing you agreed to bill on has happened: delivery, a milestone, month-end for retainers. Invoicing early looks pushy; invoicing late costs you interest-free days and signals that your due dates are soft, a topic the payment-terms guide takes further.

A proforma invoice sits in the gray zone: it looks like an invoice but isn’t one — it’s a formal preview of what the invoice will say, issued before delivery. Two legitimate uses: international shipments (customs wants a value declaration) and clients whose process requires a document before they can release a deposit. It creates no receivable and no tax event; the real invoice still follows. If you use one, title it “PROFORMA INVOICE” (the generator has it as a document-type option) so nobody books it as the real thing.

The receipt: proof that money moved

The receipt answers the last question: did you get paid? It confirms an amount received, when, and by what method. Where an invoice says “you owe”, a receipt says “you no longer owe”. Consumers get receipts at the register; in invoice-based business the receipt’s role is often played by a paid invoice — the same document reissued showing amount paid and a zero balance. The generator does this naturally: enter the payment in “amount already paid”, and the invoice shows the payment and a balance of zero; switch the document title to “Receipt” if the client wants it named that way.

Clients ask for receipts for three reasons, all legitimate: expense reports, tax records, and reconciliation of partial payments. That last one matters — when a client pays a deposit, acknowledge it in writing and show it deducted on the next invoice. Money that isn’t reflected on paper gets asked about twice.

The sequence, and the two common mistakes

The full lifecycle, then, for a typical project: quote (client says yes) → possibly a deposit invoice → the work → invoice on delivery → payment → receipt or paid invoice if asked. Retainers skip the quote after the first cycle; consumer work often compresses the whole chain into invoice-then-receipt in one visit.

The two mistakes worth engineering out of your habits:

1. Sending a quote formatted like an invoice. If it has an invoice number and a due date, someone in accounts may pay it — or worse, book it — before anyone agreed. Keep quotes visually and verbally distinct: “QUOTE”, validity date, no due date.
2. Never issuing the invoice at all. Handshake projects that end with “just PayPal me” leave no record for either side’s taxes and no document to point to if memories differ. The invoice takes a minute and is the version of events that counts — make one even when the client didn’t ask.

One habit ties all three documents together: keep them numbered, dated and stored. They are the paper trail of your income — and if you build them with this site, that trail lives entirely on your own device, which is where a record of everything you earn belongs.