Invoicing basics

Quote vs. Estimate vs. Invoice: Differences Explained

Quotes fix a price, estimates approximate it, invoices request payment. When to use each, what they commit you to and how to turn a quote into an invoice.

5 min read

Quotes, estimates and invoices often look almost identical — same header, same line items, same totals. The difference is in what they mean: how firm the price is, whether the client has agreed to anything, and whether money is owed. Using the wrong one can leave you stuck with a price you can’t honour or a client who feels misled.

At a glance

Estimate Quote Invoice
Sent Before the work, early Before the work, once scope is clear After the work or at milestones
Price Approximate, may change Fixed for the stated scope Final amount owed
Binding? Generally not a firm price Usually binding once accepted A demand for payment
Validity Indicative Valid until a stated date Has a due date
Purpose Help the client budget Win the job at an agreed price Get paid
Tax document? No No Yes (when tax applies)

The terms are used loosely in everyday speech, and the legal effect depends on your contract and local law. What matters most is what your document actually says — so say it clearly.

Estimates: a ballpark, not a promise

An estimate is your best guess at the cost when you can’t yet know the full scope. A plumber who hasn’t opened the wall, a developer asked “roughly how much for an app?”, or a translator who hasn’t seen the final word count will give an estimate.

Write estimates so they can’t be mistaken for fixed quotes:

  • Label the document “Estimate”
  • State the assumptions: “Based on approx. 40 hours”, “Assumes existing pipework is in good condition”
  • Give a range if helpful: “€2,800–€3,400”
  • Say how you’ll handle overruns: “We’ll contact you for approval before exceeding the estimate by more than 10%”

That last line is good practice anywhere. In some places, consumer protection rules limit how far a final bill may exceed an estimate without the customer’s consent, so agreeing a process up front protects both sides.

Quotes: a fixed price for a defined scope

A quote (or quotation) is a firm offer: “We will do X for Y.” Once the client accepts, you’re generally expected to deliver at that price. Because it’s binding, a good quote is precise:

  • Scope: exactly what’s included — and what isn’t
  • Price: line items, tax and total
  • Validity: “This quote is valid until 30 November 2026”
  • Assumptions and exclusions: “Excludes stock photography licences”
  • Payment terms: deposit, milestones, final payment
  • Acceptance: how the client accepts (signature, email reply, PO)

Example: quote line items

Description Qty Unit price Total
Discovery workshop (half day) 1 $900 $900
Website design — up to 6 page templates 1 $4,200 $4,200
Development and CMS setup 1 $5,500 $5,500
Content migration (per page, up to 40) 40 $35 $1,400
Total (excl. tax) $12,000

Valid until 30 Nov 2026. 40% deposit on acceptance, 30% on design approval, 30% on launch. Additional pages $35 each. Hosting not included.

You can build a quote like this in a few minutes with the free quote generator.

Invoices: the request for payment

An invoice says the client owes money now (or by the due date). It’s an accounting and usually a tax document: it records your income, and for VAT/GST-registered businesses it’s what lets the buyer reclaim tax. It should carry a unique invoice number, dates, tax details and payment instructions. See what to include on an invoice.

How they fit together

A typical project flows like this:

  1. Estimate (optional) — “Somewhere around $10–14k depending on scope.”
  2. Quote — after a scoping call: “$12,000 for this exact scope, valid 30 days.”
  3. Acceptance — the client signs or sends a purchase order.
  4. Deposit invoice — “40% deposit: $4,800.” (Some clients first want a proforma invoice to arrange payment.)
  5. Milestone / final invoices — referencing the quote number so the client can match them.
  6. Receipt — if the client needs proof of payment (see invoice vs. receipt).

Converting a quote to an invoice

When you turn an accepted quote into an invoice:

  • Give the invoice its own number from your invoice series. Quotes should use a separate series (e.g. Q-2026-018), and their numbers don’t count as invoice numbers.
  • Reference the quote (“As per quote Q-2026-018”) and the client’s PO number if they issued one.
  • Change the dates: a quote’s “valid until” becomes an invoice’s due date.
  • Bill only what was delivered. If the scope changed, add or remove lines and explain them — don’t silently change prices.
  • Deduct deposits already invoiced, showing them as a line (“Less deposit invoiced INV-2026-0040: −$4,800”).

Which should you send? Quick guide

  • The client asks “How much would it cost?” and you can’t define the scope yet → Estimate
  • You can define the scope and want to lock in the job → Quote
  • The work (or a milestone) is done, or a deposit is due → Invoice
  • You’ve been paid and the client wants confirmation → Receipt

Common pitfalls

  • Calling a guess a “quote”. If you might need to charge more, call it an estimate and explain why.
  • No validity date on quotes. Prices, exchange rates and your availability change. Thirty days is common.
  • Vague scope. “Website redesign” invites endless revisions. List deliverables and revision rounds.
  • Starting work without written acceptance. An email reply saying “Approved, go ahead” is far better than nothing.
  • Invoicing an amount different from the quote without explanation. List variations on separate lines and refer to the approval you got.

Variations: change orders

If the client asks for extra work after accepting a quote, send a short change order or revised quote for the additional scope and get approval before you do it. Then add those lines to the next invoice with a reference (“Change request #2, approved 14 Oct 2026”). This keeps invoices dispute-free and is one of the simplest ways to get paid faster.

Whether a quote or estimate is legally binding depends on its wording, your contract and local law. This article explains common practice and is not legal advice.