Estimate vs Invoice

Use estimates for approval

Estimates help clients understand scope, pricing, and validity before committing. Include line items, validity period, and a note that pricing may change if scope changes.

• Add validity date
• Describe scope clearly
• Note that pricing may change if scope changes

Use invoices for payment

After the client approves the estimate, issue an invoice for the agreed amount. Set payment terms, due date, and payment instructions. Do not assume an approved estimate replaces a formal invoice.

• Set payment terms and due date
• Use a new document number
• Include remittance details

Convert approved estimates into invoices

Reuse line items and client details from the estimate to save time and avoid mismatches. Update the document number, switch to payment terms, and set a due date before sending.

• Copy client and line items from estimate
• Update document type and dates
• Send only after client approval

Handle scope changes before billing

An approved estimate is a useful baseline, but it should not hide later decisions. If the client adds two pages, changes the delivery date, or requests another revision round, document the change before invoicing it.

Send a revised estimate or short change order that names the added work and price, then use those same descriptions on the invoice.

This creates a simple approval trail and prevents an accounts-payable reviewer from seeing a total that does not match the document their team originally approved.

Example document trail

A photographer might send estimate EST-2026-014 for a half-day shoot at $900, valid for 14 days. After approval, the client adds $150 of retouching and confirms that change by email.

The final invoice can reference EST-2026-014, list the $900 shoot and $150 retouching separately, and set a specific due date.

The estimate explains how the project started; the approval records the added scope; the invoice requests the final $1,050. Saving all three records gives each document one clear job.