Blog
Part of the Invoice fundamentals guides
Invoice vs receipt vs quote: which document when
Three documents, three different jobs, and mixing them up is one of the fastest ways to confuse a client. An invoice asks for money. A receipt confirms money arrived. A quote promises a price before any work starts. Here is what each one does, when to send it, and the mistakes that come from using the wrong one.
The quote: a price before the work
A quote (or estimate) tells the client what the work will cost before they commit. It is your opening position: scope, line items, total, and how long the price is good for. Send it when a client asks "how much would this cost?" or before you start any project where the price could surprise someone. A good quote has a valid-until date, because prices and availability change, and an undated quote can come back to haunt you months later.
The quote becomes the reference point for everything after it. When the client accepts, the invoice should match the quote unless the scope changed, and if the scope did change, say so on the invoice instead of hoping nobody notices. You can build a private quote the same way you build an invoice: no signup, nothing uploaded.
The invoice: a request for payment after the work
An invoice is a formal request for payment, sent after the work is done or at an agreed billing point. It says: this is what was delivered, this is what it costs, this is when it is due, and here is how to pay. The invoice is the document that starts the payment clock. Nothing is officially owed until it goes out, which is why sending invoices late is one of the costliest freelancer habits.
Invoices carry the formal fields: unique invoice number, issue date, due date, line items, totals. They are also the document your records and the client's records both point to, so keep them sequential and never reuse a number. Our guide to what makes an invoice valid covers the full field list.
The receipt: proof the money arrived
A receipt confirms that payment was received. It goes out after the money lands, not before. It references the invoice it settles, states the amount paid, the date paid, and the payment method. Clients need receipts for their own bookkeeping, and some will ask for one every time, so treat it as part of the job, not a favor.
You can generate a private payment receipt referencing the original invoice number, with the payment method and date recorded. Same deal: no signup, nothing leaves your browser.
Side by side
- Quote: sent before the work. Job: agree on price and scope. Key fields: quote number, valid-until date, line items, total.
- Invoice: sent after the work (or at a billing milestone). Job: request payment. Key fields: unique invoice number, issue date, due date, line items, totals, payment instructions.
- Receipt: sent after payment. Job: confirm money received. Key fields: receipt number, invoice reference, date paid, amount, payment method.
The order in a normal project is quote, then invoice, then receipt. Milestone billing repeats the invoice step: one invoice per milestone, one receipt per payment.
The mix-ups that cause real problems
- Invoicing before the work is agreed. An invoice implies the amount is settled. If the client never approved the price, lead with a quote, not an invoice.
- Sending a receipt before you are paid. A receipt says the money arrived. Sending one early creates a paper trail claiming payment that never happened. Wait for the money.
- Quoting after starting work. A quote written after the work is done is just an invoice with the wrong name. Price first, then work.
- Using one document for everything. Some freelancers send a single "bill" that is part quote, part invoice. It confuses clients and gives you nothing clean to point at when there is a dispute. Use the right document for the moment.
- No reference between documents. The invoice should reference the quote number, and the receipt should reference the invoice number. Linked documents are auditable documents.
Quote first, invoice after, receipt last. The right document at the right moment is half of looking professional.
Need the documents themselves? Make a private invoice, build a private quote, or generate a private receipt. No signup, nothing uploaded.
Related in this cluster: what makes an invoice valid, common invoicing mistakes, and the Invoice fundamentals hub.
Get new posts by email.
One post a week: honest build logs and leverage-through-technology pieces for freelancers and bootstrapped founders. No spam, unsubscribe anytime. Subscribe on Substack.