Estimate vs. invoice: what’s the difference?
An estimate proposes a price before the work; an invoice requests payment after it. Here is how they differ, when to send each, and how to convert one.
Updated · Published · By the Invoice Mint team
The short answer
An estimate is a proposal sent before the work: it proposes a price and asks the client for a decision. An invoice is a request for payment sent after the work (or at an agreed milestone): it states an amount due and a due date. Only the invoice creates a receivable in your books. The best practice is to convert the accepted estimate into the invoice rather than retyping it.
An estimate is a proposal. An invoice is a request for payment. Everything else follows from that one distinction.
They are easy to confuse because they contain nearly the same information — your details, the client’s details, a list of work, a total. But they do different jobs at different moments, and sending the wrong one is a real problem: an invoice sent before the work is agreed reads as presumptuous, and an estimate sent after the work is done does not obligate anyone to pay you.
The short answer
- An estimate comes before the work. It proposes a price, is not a bill, and the client is expected to accept, decline or ask for changes.
- An invoice comes after the work (or at an agreed milestone). It requests payment, carries a due date and a balance, and the client is expected to pay it.
Side by side
| Estimate | Invoice | |
|---|---|---|
| Sent | Before the work | After the work or a milestone |
| Purpose | Propose a price | Request payment |
| Client action | Accept, decline or ask for changes | Pay by the due date |
| Numbering | EST-001, EST-002… | INV-001, INV-002… |
| Can the amount change? | Yes, if the scope changes | No — it states what is due |
| Accounting effect | None until accepted | Creates a receivable |
Timing
The estimate is written while you are standing in the client’s driveway looking at the job. The invoice is written when that job — or an agreed stage of it — is finished.
What it asks the client to do
An estimate asks for a decision. An invoice asks for money. That is why an estimate should make accepting easy, and an invoice should make paying easy.
Numbering
Keep two separate sequences — EST-001 and INV-001. Mixing them makes your records harder to follow and makes it unclear which document a client is referring to.
Legal and accounting weight
An accepted estimate is evidence of what was agreed. An invoice is the accounting record of money owed, and it is what goes into your books and your tax return. Only the invoice creates a receivable.
Whether the number can change
An estimate is a good-faith projection and can move if the scope moves — that is the point of the word. An invoice states an amount that is now due. If the scope changed mid-job, the honest move is a revised estimate approved before the work, not a surprise on the invoice.
What about a quote?
In everyday use, “quote” and “estimate” are used interchangeably, and most clients will not distinguish them. Where people do draw a line, a quote is a fixed price you are committing to and an estimate is an approximation that may change. If you mean a firm price, say so on the document — “Fixed price, valid 30 days” — rather than relying on which word you used.
What about a proposal?
A proposal is an estimate with the sales case attached: scope, approach, timeline, sometimes photos of comparable work. On larger residential or commercial jobs it is worth the extra effort. For a one-day repair it is overkill.
The handoff is where money gets lost
The expensive mistake is not confusing the two documents. It is rebuilding the second one from scratch. You quote a job from the driveway, win it three weeks later, then sit down and retype every line item into an invoice — and that is where a line gets dropped, a price gets stale, or the deposit gets forgotten.
An estimate that converts directly into an invoice removes that risk entirely. The client, the line items, the taxes and the totals carry across exactly as approved, and the only thing you change is the due date.
A practical sequence
- Walk the job and send the estimate before you leave. Speed is a competitive advantage here; most trades take days.
- Let the client accept, decline or request changes on the document itself, so the approval is recorded rather than buried in a text thread.
- Do the work. If the scope changes, send a revised estimate and get it approved before you continue.
- Convert the accepted estimate into an invoice, set the due date, and send it before you leave the site.
- Record payments against the invoice as they come in, so the balance is always current.
Two documents, one workflow. Get the order right and the paperwork stops being a source of argument.
Common questions
Is an estimate legally binding?
An estimate is generally a good-faith approximation, not a bill, and it does not by itself oblige anyone to pay. An accepted estimate is evidence of what was agreed, and local consumer rules may limit how far a final price can exceed it. If you mean a firm price, write “fixed price” on the document.
What is the difference between a quote and an estimate?
In everyday use they are interchangeable. Where a distinction is drawn, a quote is a fixed price you commit to, and an estimate is an approximation that may change if the scope changes.
Can I turn an estimate into an invoice?
Yes. Most invoicing apps, including Invoice Mint, convert an accepted estimate into an invoice draft with the same client, line items, taxes and totals, so nothing is retyped.
