Estimate vs. Invoice: What's the Difference and Why It Matters
It sounds like a basic question, but a surprising number of disputes in small service businesses trace back to this exact confusion: was that document an estimate, or was it an invoice? The two look similar — a list of items, a total, maybe your logo at the top — but they mean different things legally and practically, and mixing them up costs money.
An estimate is a proposal, not a bill
An estimate says "here's what I propose to do, and here's roughly or exactly what it will cost." It isn't a demand for payment, and depending on how it's worded, it may not even be a firm commitment to the final price — a "quote" is often treated as fixed, while an "estimate" can carry more wiggle room if the scope changes once work starts. Nobody owes you money because you sent an estimate. It exists to get a yes.
An invoice is a request for payment for work that's owed
An invoice says "this work happened (or is scheduled and agreed), and payment is now due." It typically includes payment terms — due on receipt, net 15, a deposit already applied — and it becomes part of your financial records in a way an estimate doesn't. Sending an invoice before a client has actually agreed to the scope and price is a fast way to create a dispute, because you're asking to be paid for something that was never formally approved.
Why the conversion moment matters
The cleanest businesses treat the moment an estimate is approved as a real event, not a vague understanding. That's the point where a proposal becomes a commitment on both sides — you're committing to the price you quoted, and the client is committing to pay it. Everything downstream (the invoice, the payment, any later dispute about scope) traces back to whether that approval actually happened and what exactly was approved.
Keep a record of the approval itself
"They said yes on the phone" is a lot weaker than a dated, written approval of the exact document that was quoted. It doesn't need to be complicated — an email reply, a signed PDF, or a client clicking "approve" on a document that's timestamped and can't be silently edited afterward all work. What matters is that if a disagreement ever comes up about what was agreed to, you have something better than memory to point to.
The practical takeaway
Treat every estimate as a real proposal worth approving formally, and only invoice once that approval exists. It's a small discipline that prevents an outsized amount of the "but I never agreed to that" conversations that eat into both your time and your client relationships.