Clients sometimes ask for "an invoice" when they mean a quote, or vice versa. The confusion is understandable — both documents deal with prices and services. But they serve fundamentally different purposes, and using the wrong one at the wrong time creates accounting errors, legal ambiguity, and payment disputes.
The core difference
| | Quote | Invoice | |---|---|---| | Timing | Before work begins | After work is delivered (or during, for milestones) | | Legal status | Offer — no obligation until accepted | A claim for payment | | Accounting | Not recorded | Recorded as revenue (when due) | | Triggers VAT | No | Yes (at issue or payment, depending on your country) | | Creates a debt | No (unless accepted) | Yes |
In short: a quote is a promise of price; an invoice is a demand for payment.
What is a quote (also called an estimate or proposal)?
A quote is a document you send before starting work, which outlines:
- What you'll deliver (scope)
- How much it will cost (price, broken down by item if needed)
- Under what conditions (timelines, payment terms, validity period)
Legal implications of a quote
When a client accepts your quote (by signature, email confirmation, or purchase order), it becomes a binding contract. Both parties are committed: you to deliver, them to pay at the stated price. Changing the scope or price after acceptance requires a formal amendment.
An unaccepted quote has no legal weight — it's simply an offer that can expire. Always set a validity date (e.g. "valid for 30 days") to avoid being held to a price you quoted months ago.
When should you always send a quote first?
- Any project over a few hours of work
- New clients (establishes expectations and creates a paper trail)
- Projects with variable scope (day rates, research-heavy work)
- Trades and construction (legally required above certain thresholds in many countries)
- Any project where the client might dispute the price later
What is an invoice?
An invoice is a formal request for payment that you issue after delivering the agreed work (or at a defined milestone). It's a legal document that:
- Records a sale or service in both parties' accounting
- Triggers VAT obligations (if applicable)
- Creates a legally enforceable debt
- Starts the payment clock (the due date countdown begins on the invoice date)
Required content on an invoice
Invoices have mandatory legal requirements that quotes don't. You typically need to include:
- A sequential invoice number
- Issue date and due date
- Full identity of both parties (including VAT/tax numbers if applicable)
- Detailed description of goods or services
- Net amount, VAT breakdown, gross total
- Payment terms and late payment clause
- Bank details
A quote has far fewer formal requirements — it just needs to be clear about what's being offered and at what price.
The typical workflow
The standard B2B workflow goes like this:
- Discovery call or brief — you understand what the client needs
- Quote sent — you set out scope, price, timeline
- Quote accepted — client signs or confirms by email
- Work starts
- Deposit invoice (optional but recommended) — client pays upfront, you start working with financial security
- Work delivered
- Final invoice — deducting any deposit already paid; client settles the balance
Some projects add intermediate invoices at milestones (particularly useful for long projects spanning several months).
What about proforma invoices?
A proforma invoice is a third document that sits between quote and invoice. It looks like an invoice but explicitly states "PROFORMA" and carries no accounting or legal weight. It's mainly used for:
- Customs declarations (to declare the value of goods being exported)
- Pre-sales documentation for financing or import licences
- Showing a client what the invoice will look like before finalising
A proforma is not a payment demand and should never be entered into your accounting system as a receivable.
Common mistakes
Sending an invoice when you should send a quote
If a client asks "can you send over an invoice for the project?" before you've agreed on scope and price, they probably mean a quote or proposal. Sending a real invoice creates a legal debt before any agreement exists — awkward, and potentially damaging to the relationship.
Treating a quote as a guaranteed commitment
A quote you've sent is not binding until the client accepts it. Don't start work based on a sent-but-unsigned quote — you have no legal protection if the client then disputes the scope or price.
Using the same numbering for quotes and invoices
Quotes and invoices should have separate, sequential numbering systems (e.g. Q-2026-001 for quotes, INV-2026-001 for invoices). Mixing them makes accounting complicated and can create confusion in audits.
Forgetting to convert the accepted quote into a formal invoice
For accounting purposes, the invoice is what counts — not the quote. Even if the client has accepted your quote and even paid a deposit, you still need to issue a formal invoice recording the sale.
Quote and invoice in one tool
Invoice Creator handles both quotes and invoices from a single interface. Toggle between the two modes with one click: the quote converts to an invoice when you're ready to bill, with all line items and prices carried over automatically.
The deposit workflow is fully supported: create a deposit invoice at project start, then generate the final invoice at delivery — the previously invoiced deposit is deducted automatically, with a cross-reference to the original deposit invoice number.
For freelancers managing multiple projects, having quotes and invoices in one place means a consistent audit trail from proposal to payment, without copying data between different tools.