A client once paid an estimate. Not the invoice that followed, not the deposit request, but the estimate itself: transferred the quoted total to the account on the page, then asked when work would start. It took three emails. The document said "ESTIMATE" in large type, but nobody had explained what that meant.
Estimates and invoices share a format: client, line items, quantities, rates, total. They do different jobs, and confusing them creates unmatched payments, revenue recorded too early, and quotes that turn into unpaid work.
Here is the practical difference, when to send each, and how to move from one to the other without losing the details.
The one-sentence version
An estimate (often called a quote) is an offer: this is what the work will cost if you approve it. An invoice is a request for payment for work that has been delivered or agreed. A quotation is not a bill, and an invoice is not a proposal. Keep that distinction straight and most of the confusion disappears.
| Estimate / quote | Invoice | |
|---|---|---|
| Purpose | Propose scope and price | Request payment |
| Timing | Before work begins | After delivery or milestone |
| Client action | Approve, negotiate, or decline | Pay by the due date |
| Accounting treatment | Not revenue; a pipeline document | Records the amount owed |
| Numbering | Separate sequence, e.g. EST-0031 | Separate sequence, e.g. INV-0142 |
| Expiry | Usually has a validity window | Has a due date, not an expiry date |
| Revision | Can be revised freely before approval | Should only be corrected by credit note or a replacement invoice |
Two related documents exist: a pro forma invoice requests payment before supply, often for a deposit, and is not a tax invoice in most jurisdictions; a receipt confirms payment happened. Check local rules.
What goes on each document
What belongs on an estimate
An estimate should give enough certainty to say yes and protect you if scope changes. Include:
- A clear heading: "Estimate" or "Quote", with the estimate number and date
- A validity period, e.g. "valid for 30 days", client details and a short job description
- Line items with quantities, rates, and what is included
- Exclusions and assumptions: what is not covered, and what would change the price
- Any tax you expect to charge, marked as estimated where relevant, plus payment terms and deposit requirements
- An approval line, or instructions to reply confirming
What belongs on an invoice
An invoice is a demand with a deadline. Include:
- A clear heading: "Invoice", with a sequential invoice number
- Issue date and a specific due date, plus your business details and any required registration numbers
- The client's legal name, billing details and any PO or reference number
- The deliverables actually supplied, with quantities and rates
- Discounts, tax and the total, in a stated currency
- Payment instructions and the reference to quote
- Terms already agreed, not new conditions
The difference is tense: estimates describe what might happen; invoices describe what did, and ask to be paid.
When to send an estimate first
Estimates are not mandatory, but they earn their keep when work is uncertain or the stakes exceed a single invoice:
- New clients. It sets expectations, gets scope agreed before money is spent, and is your reference if the job grows.
- Variable scope. Renovations, bespoke design, consulting, anything where "it depends" is honest.
- Larger projects. Clients usually need internal approval, and the estimate is what they take to whoever signs off.
- Multiple options. Two or three service levels let the client choose without a fresh quote.
- Materials-heavy jobs. Listing materials separately protects you if a price moves.
When you can invoice directly
You do not need a formal estimate for every small job, especially with clients you know:
- Repeat clients on a standing arrangement with the rate and process agreed
- Fixed-price jobs quoted verbally and confirmed by email
- Retainer work invoiced on an agreed schedule
- Milestone billing where the contract sets the milestones
- Deposit invoices, if the deposit was agreed beforehand
The common thread is prior agreement: if the price is approved, you do not need a fresh proposal, you need a clear bill.
Converting an estimate into an invoice: the checks that prevent rework
Many tools turn an approved estimate into an invoice in a tap. That is convenient, but errors hide in the conversion, because the estimate was written before the work happened. Before sending, check:
- The approved version. If you sent three iterations, convert the one the client accepted, not the latest file.
- Client details. Billing entity, address and PO number: confirm they are current.
- Actual quantities. Replace assumed quantities with what you delivered; a smaller job should invoice lower unless it was a fixed fee.
- Scope changes. Add approved change orders as separate lines rather than adjusting the original silently.
- Deposits already paid. Credit the deposit and show the balance due: two documents, one clear total.
- Document identity. Remove estimate language, validity dates and approval instructions; rename the PDF and keep the estimate on file.
If a revision changed the price, treat it as a new estimate revision, not an invoice with a surprise total.
The patterns that cause disputes
Options totalled together. If you present three packages, list each as a choice or send separate estimates; a total that sums all options invites someone to approve the wrong number.
Estimates with no expiry. One from eight months ago is not a price commitment; include a validity window and re-price if it lapsed.
Missing exclusions. "$4,800 for the bathroom" may exclude tiling or assume daytime access. When extras appear the client feels ambushed, so write exclusions down while they are boring.
Deposits with no written agreement. Agree the deposit before work starts and show it as a credit later; an unexpected request after signing is a negotiation, not a billing step.
Treating an approved estimate as revenue. Estimates belong in your pipeline, not your income; only invoices record amounts owed.
A numbering and file system that keeps them apart
Use two sequences, EST-0001 and INV-0001 upward, and never reuse a number. Save the approved estimate beside the invoice that results from it, named like INV-0142-Northwind-Nov2026.pdf.
Record each estimate's status (sent, approved, declined, expired) and each invoice's dates and payment status, linking the two so your records tell the story.
How the tooling helps
Cleanup is mostly remembering the checks above. Tools reduce retyping, and therefore the places a detail can go wrong: client details and line items carry across, an accepted estimate becomes a populated invoice, and payment status sits with the document.
Invoice Maker is a free-to-download iPhone and Android app built around that workflow: estimates convert to invoices with details carried over, clients and price-book items are saved for reuse, and it supports PDF sharing, 34 currencies and paid/unpaid/partial payment tracking. Manual invoicing works offline; the optional AI drafting, which turns a typed description or voice note into an editable draft you confirm before creating, needs a connection.
The habit to build
Before you send anything, ask: am I asking for approval, or for payment? For approval, send an estimate with a validity date and clear exclusions. For payment, send an invoice with a due date and payment instructions. When converting, use the approved version and show the deposit as a credit.
Disclosure: I work with the team behind Invoice Maker, which is why it is used as an example above. This article is general business information, not legal, tax or accounting advice. Document requirements and local rules vary by jurisdiction; confirm yours with a qualified professional.
Top comments (0)