Invoice vs. Estimate: What's the Difference, and Why It Matters
Module 1: Accounts Receivable Fundamentals, Chapter 4
The short answer
An estimate is a proposed price for work not yet approved or completed; it's not a bill, and it shouldn't be tracked in your accounts receivable. An invoice is a formal request for payment for work that's been approved and delivered. Confusing the two, or treating an estimate as if it were already billed, is a quiet but common source of AR chaos.
What's actually different between them?
Estimate
- A proposed price, before work is approved
- Not a demand for payment
- Needs the client's sign-off to become real
- Not part of your AR balance
Invoice
- A formal bill for work already approved and delivered
- A demand for payment, with a due date
- Legally and financially binding once sent
- Counted in your AR balance the moment it's issued
Why does the distinction actually matter for AR?
Because tracking an estimate as if it were an invoice inflates your AR with money that was never actually owed yet, and tracking an approved job without ever converting the estimate into a real invoice means work you've delivered never gets billed at all. Both mistakes distort your numbers, just in opposite directions.
What's the right sequence?
- Estimate goes out for the client's approval, before work begins, or before a new phase starts.
- Client approves it, in writing or through a formal sign-off process.
- Work is delivered against the approved scope.
- Estimate converts into an invoice, at the agreed price, with a due date attached.
- Invoice is what actually enters your AR and starts being tracked toward payment.
The moment of conversion, estimate becoming invoice, is where a lot of small businesses lose time. If that step depends on someone remembering to do it manually, delays creep in between "client said yes" and "invoice actually went out," and every day of that gap adds directly to your DSO before the clock even properly starts.
Does every business actually need estimates?
Not every transaction. A straightforward monthly retainer rarely needs a fresh estimate each month. But any variable-scope work, a new project, an added phase, work outside a standard retainer, benefits from an estimate first. It sets expectations in writing and gives both sides a clear reference point if a dispute comes up later.
Quick check
Three questions. No email required, this one's just for you.
1. A client verbally agrees to a project scope but hasn't signed anything yet. What should you send?
2. Should an outstanding estimate be counted in your accounts receivable balance?
3. What's the risk of a slow, manual estimate-to-invoice conversion process?
Frequently asked questions
Can an estimate legally double as an invoice?
No. An estimate is a proposal, not a bill. Treating it as one can create real confusion with clients about what's actually owed and when payment is due.
What if the client wants changes after approving the estimate?
That's a scope change, and it should generate a new or revised estimate for the additional work, approved before it's billed, not silently added to the final invoice.
Do estimates expire?
Many businesses build in an expiration window (30-60 days is common) so pricing doesn't stay open-ended indefinitely if a client goes quiet after receiving one.
Sources
- AiranSuite product documentation, invoice and estimate workflow
Prefer to have this run for you?
A Receivables Review shows exactly where your own AR process could improve.
Book a Receivables Review