• What an Estimate Actually Is
  • What an Invoice Actually Is

The estimate and the invoice look like the same document with two different headers. They are not. They serve different jobs at different points in the buyer's mind, and treating them as interchangeable is the most common reason small businesses lose money on otherwise good projects.

Quick Answer An estimate is a non-binding price offer sent before work begins; an invoice is a legally enforceable demand for payment sent after work or a milestone is complete. Best practice is to lock the estimate the moment the client signs, take a deposit invoice immediately, convert the remaining scope to a final invoice on delivery, and route any scope changes through a separate change order rather than rewriting the estimate or the invoice.

Key Takeaways

This guide covers the practical, field tested rules for working with both documents without losing money in the gap between them.

What an Estimate Actually Is

An estimate is a non-binding offer to do work at an approximate price. The keyword is non-binding. Until the client signs, both sides can walk away.

What an estimate does:

  • Sets expectations on scope, timeline, and price
  • Gives the buyer enough specificity to compare against other vendors
  • Locks the price as of a date, usually for 14 to 30 days
  • Creates the document that becomes the foundation for the invoice and any change orders

What an estimate does not do:

  • Create a legal obligation to pay (until accepted)
  • Trigger revenue recognition in accounting
  • Move money

The Intuit Quicken comparison guide puts it cleanly: "an estimate provides a customer with an expected price before any work begins."

For the deeper teardown of estimate, quote, and proposal differences, see our estimate vs quote vs proposal guide. For now, treat estimate and quote as interchangeable. The distinction between them is mostly geographic.

What an Invoice Actually Is

An invoice is a legally binding demand for payment for work already delivered (or a milestone hit). Once issued, it creates an accounts receivable on your side and an accounts payable on the client's side.

What an invoice does:

  • Triggers the client's obligation to pay within the stated terms
  • Creates a record for both parties' accounting books
  • Starts the clock on late fees if your terms allow
  • Functions as a tax document in most jurisdictions

What an invoice does not do:

  • Negotiate scope (that work is already done by the time the invoice goes out)
  • Move with the work (the invoice freezes a moment in time)

If you want the full mechanics of professional invoicing, our guide to creating a professional invoice covers structure, required fields, and tax handling.

Estimate vs Invoice: Side by Side

The table below is the single most useful reference you can keep when explaining the difference to a client (or to a new bookkeeper).

Field Estimate Invoice
Purpose Pre-work price offer Post-work demand for payment
Legal weight Non-binding until accepted Binding on issue
Triggers payment No Yes
Triggers revenue recognition No Yes (typically)
Has an expiry date Yes (14 to 30 days typical) No (has a due date instead)
Can be revised freely Yes, before acceptance No, revisions are credit notes or new invoices
Includes taxes Usually shown as a line for awareness Required to be shown by jurisdiction
Required fields Less standardized Required by tax law (date, parties, line items, totals)
Lives in Sales pipeline Accounts receivable
Document numbering Often a separate sequence Strict, gap free sequence required in many jurisdictions

The most important row is "document numbering." Tax authorities in most jurisdictions require invoices to be issued in a strict gap free sequence. Estimates have no such rule. Mixing the two numbering systems is a flag at audit time.

The Seven Step Estimate to Invoice Workflow

The cleanest workflow we have seen in real businesses follows seven steps. Skip any of them and disputes appear.

1. Scope and Send the Estimate

Send within 24 hours of the conversation. The Loopio RFP benchmark for 2025 shows that response speed correlates with win rate across industries. Include scope, exclusions, three pricing options, a deposit term, and an expiry date.

2. Get a Written Acceptance

A reply with "approved" is enough for small projects. For anything above a few thousand dollars, use an e-signature. The U.S. SBA's contract guidance explains the conditions for an enforceable written agreement. Save the acceptance email or signed PDF in the same place as the estimate.

3. Issue the Deposit Invoice

This is the single biggest accounting hygiene step. The deposit is not part of the estimate. It is its own invoice, issued separately. It carries its own invoice number, its own date, and goes into accounts receivable until paid.

Common deposit percentages:

Project type Typical deposit
Small creative or trade ($1k to $10k) 50 percent
Medium project ($10k to $50k) 33 percent at signing, 33 percent at milestone, 34 percent on delivery
Large project ($50k+) 25 percent at signing, with milestone billing thereafter
Rush job (under 7 day turnaround) 100 percent

Our guide to deposit invoicing covers the mechanics of recording the deposit as a liability until earned.

4. Do the Work

This is where the document set goes quiet. If nothing changes, you flow straight to step 6. If anything changes, you go through step 5 first.

5. Run Any Scope Changes Through a Change Order

Do not edit the estimate. Do not adjust the invoice. Issue a separate, signed change order that:

  • Describes the change in scope
  • States the cost or credit
  • States the impact on schedule
  • Is signed by both sides before the change is executed

The construction industry has this discipline because the cost of skipping it is enormous. Rhumbix's change order data shows change orders average 10 percent of contract value across projects. Without a written process, that number lands on your margin, not the client's bill.

For the deeper protocol, see our guide to handling estimate revisions.

6. Issue the Final Invoice

The final invoice should reference:

  • The original estimate number
  • The deposit invoice number (and credit the deposit against the total)
  • Any change order numbers (and add their cost to the total)
  • The final balance due, with payment terms

A well structured final invoice tells the client's bookkeeper exactly how the number was built. Disputes drop because the math is reproducible.

Example reference block:

Original estimate #EST-2026-118: $11,400
Change order #CO-001 (added drainage tile): +$1,400
Deposit invoice #INV-2026-301 (paid): -$3,420
Final balance due: $9,380

7. Reconcile and Archive

After payment, mark the estimate, deposit invoice, change orders, and final invoice as a single project bundle. Most accounting tools support this. If yours does not, use a consistent folder structure.

When to Use an Estimate vs Going Straight to an Invoice

Most People Also Ask sources phrase the question as "when would you use an estimate instead of going straight to an invoice." The answer comes down to three factors.

Situation Use an estimate first Go straight to invoice
Project size Above one or two days of work Small, well defined tasks
Price certainty Variable or scope dependent Fixed, standard service
Client relationship New client or new project Established client with recurring rate
Customer expectation Buyer wants to compare options Buyer already agreed verbally
Risk of dispute Material risk of "that's not what we agreed" Low risk, repeat work
Cash flow impact Want a deposit Net 30 acceptable

The simplest rule: if either side could reasonably misremember the price or scope a week later, write an estimate first. Trust your memory only on small, well defined tasks.

What Stays Static, What Stays Flexible

A common source of disputes is uncertainty about which fields can move once the estimate is signed.

Stays Static After Signature

  • The scope as written, minus exclusions
  • The price for in-scope work
  • The deposit term
  • The payment terms (net 14, net 30, etc.)

Stays Flexible (Without a Change Order)

  • The schedule, if the client causes the delay
  • The order of deliverables, as long as the total scope is preserved
  • The platform or tool used, if it does not change the outcome

Requires a Change Order

  • Adding deliverables
  • Removing deliverables (credit needed)
  • Changing the deliverable definition (a 5 page site becoming a 12 page site)
  • Changing the timeline because of new scope
  • Changing the payment terms

The line is simple: if either side wants a different outcome than the estimate described, change order. If they want a different path to the same outcome, no change order needed.

Deposit Timing Best Practices

The deposit is the single biggest predictor of project profitability. The data on this is consistent.

Pattern Typical use Risk of non-payment
100 percent up front Rush jobs, new clients with red flags, small one-off tasks Lowest
50 percent up front, 50 percent on delivery Standard project work under $20k Low
33/33/33 (signing, milestone, delivery) Medium projects ($20k to $100k) Medium
25 percent up front, milestone billing Large projects ($100k+) Medium
Net 30 with no deposit Established clients only Highest

FreshBooks' guidance on deposits lists three signals that you should require an up-front payment: a new client, a rush job, or a project under $5,000 where the cost of chasing payment exceeds the project margin.

For the mechanics of recording and tracking deposits, see our deposit invoicing guide. For milestone payment structures, see our progress invoicing guide.

Why Late Payments Are an Estimate Problem

Most "late payment" problems trace back to bad estimate hygiene, not bad client behavior. The 2025 Intuit QuickBooks Small Business Late Payments Report found that:

  • 56 percent of U.S. small businesses are owed money from unpaid invoices
  • Those businesses are owed $17,500 on average
  • 47 percent report some invoices overdue by more than 30 days
  • Businesses using 90 day payment terms are 50 percent more likely to report cash flow problems than businesses asking for immediate payment

The link to estimates is direct. When the estimate is vague, the invoice is vague. A vague invoice is easier to dispute, slower to approve, and slower to pay. A specific estimate produces a specific invoice that flows through the client's accounts payable without friction.

For practical tactics on chasing slow payments, see our guide on how to follow up on unpaid invoices.

Two Real Templates

Template A: Service Project Estimate

Estimate #EST-2026-203
Issued: 20 May 2026
Expires: 3 June 2026

Client: Acme Co.
Project: Q3 launch microsite

Scope
- 1 page launch microsite (responsive)
- 3 hero variants for A/B testing
- Analytics setup (GA4 + one custom event)
- 14 day post-launch tweak window

Not included
- Paid ad creative
- Custom illustration or photography
- Translation

Pricing
- Standard: 1 hero, single variant            $3,800
- Recommended: 3 hero variants                $5,600
- Premium: 3 variants + 60 day support        $7,400

Terms
- 50 percent deposit on signature, balance on delivery
- Deposit invoice issued separately on approval
- Scope changes require signed change order
- Estimate valid until 3 June 2026

Approved by: ___________________   Date: ________

Template B: Matching Final Invoice

Invoice #INV-2026-345
Issued: 30 June 2026
Due: 14 July 2026 (Net 14)

Bill To: Acme Co.
Bill From: [Your Business]

References
- Original estimate: EST-2026-203
- Deposit invoice: INV-2026-322 (paid 22 May 2026)
- Change order: CO-2026-009 (signed 12 June 2026)

Line items
- Q3 launch microsite (per EST-2026-203)        $5,600.00
- Change order: add 5 day support extension       $850.00
- Deposit credit                                -$2,800.00
- Subtotal                                       $3,650.00
- Sales tax (per jurisdiction)                     $292.00
- Total due                                      $3,942.00

Payment
- ACH, card, or wire (instructions attached)
- 1.5 percent late fee per month after due date

The matching pair shows the audit trail end to end. Anyone (your bookkeeper, the client's AP team, your accountant) can reproduce the math.

Estimate-to-Invoice in Software

Doing this manually works at small volume. Once you are running more than a handful of projects at a time, three things tend to break:

  1. Estimate numbering and invoice numbering get mixed up. Keep them in separate sequences.
  2. The deposit credit gets lost. The final invoice forgets the deposit was already paid.
  3. Change orders sit in email and never make it into the document trail.

Tools that handle the end to end workflow (Billed does this, and so do FreshBooks, QuickBooks, Wave, and Xero) automatically:

  • Generate the deposit invoice from the approved estimate
  • Carry the estimate number into the final invoice
  • Apply the deposit as a credit
  • Attach change orders to the project bundle

If you are starting from scratch and want a software comparison, see our piece on excel or invoicing tool for when to graduate from spreadsheets.

Common Pitfalls

The four most common estimate-to-invoice mistakes we see:

  • Editing the estimate after signature. Once signed, the estimate is the contract. Edit it and you reset the agreement. Issue a change order instead.
  • Issuing the final invoice without referencing the estimate. The client's bookkeeper has no way to tie the invoice back to the agreement, which means it sits in their "to review" pile longer.
  • Forgetting to credit the deposit. The client pays the deposit, then receives a final invoice for the full project total. Even when corrected fast, this damages trust.
  • Letting change orders live in email. A signed change order document is a 60 second job. Skipping it can cost a percent of the project margin.

FAQ

Is there a difference between an invoice and an estimate? Yes. An estimate is a non-binding price offer sent before work. An invoice is a binding demand for payment after work or a milestone is delivered. Estimates set expectations; invoices move money.

Can an estimate become an invoice automatically? In most invoicing software, yes. The estimate's line items become the invoice's line items, the client and project info carries over, and you confirm and send. The mechanics still produce two separate documents with their own numbers.

What are the four types of estimates? The most common framework comes from AACE International, which defines five classes from Class 5 (rough order of magnitude, accuracy -50% to +100%) to Class 1 (definitive, accuracy -5% to +15%). Outside the construction and engineering industries, the practical four types are preliminary, detailed, fixed price, and time and materials. Each has its place. See our project estimate guide for which to use when.

What is a red flag in an invoice? From the client's side: a different bank account on a follow up email (likely fraud), an invoice number out of sequence, a vendor name that does not match the contract, or a sudden change to wire payment instead of ACH. From the vendor's side: a client asking for an invoice without a signed estimate or PO is a common red flag for slow or non-payment.

When would you use an estimate instead of going straight to an invoice? Any time the price or scope might be disputed later, any time the client wants to compare options, and any time you want a deposit before starting work. For repeat work with a known rate, skip the estimate.

Do I have to issue a deposit invoice separately, or can I just deduct it on the final invoice? You can do either, but separate is much cleaner. A separate deposit invoice creates an accounts receivable when issued and converts to deferred revenue when paid. Deducting on the final invoice works for cash basis bookkeeping, but it complicates accrual reporting and tax handling.

What happens if the client signs the estimate but then disputes the invoice? The signed estimate is your defense. If the invoice matches the estimate plus any signed change orders, the dispute usually resolves in your favor. If there are no signed change orders and the invoice exceeds the estimate, you are exposed. This is why change orders matter.

How long should an estimate stay valid? 14 to 30 days is the most common range. Trade work with volatile material prices (asphalt, copper, lumber) often uses 7 to 14 days. Long sales cycle projects can go to 60 or 90 days, but the math should be re-checked at signature.

When This Guide Isn't for You

The estimate-to-invoice flow described here is built for service businesses, contractors, and project-based work. Skip it if any of these apply.

  • Product sales with public pricing. A SaaS subscription does not need an estimate. It needs a contract or order form.
  • E-commerce. The flow is order -> payment -> shipment, not estimate -> deposit -> work -> final invoice.
  • Pure hourly work. Open ended hourly billing belongs in a retainer agreement. See our retainer invoicing guide.
  • Public sector procurement. Government and federal contracts use formal RFPs, scoring matrices, and required forms. The estimate-to-invoice flow described here does not apply.
  • Construction with AIA contracts. Construction projects on AIA contracts have their own forms (G701 for change orders, G702 for pay applications). See our construction estimating basics guide for that workflow.

How We Verified This

Where two sources disagreed (most commonly on win rates and average late payment days), we used the most recent and noted the discrepancy.

Related Articles

Share

Was this article helpful?