An estimate helps a customer decide whether to authorize work. An invoice requests payment for an amount that has become billable. Mixing those roles creates avoidable disputes: a customer may treat an invoice as an unapproved proposal, or a business may mistake an accepted estimate for a payment record.
The safest workflow is a documented handoff from proposed scope to approved scope, then from completed milestone to invoice, and finally from payment to receipt. Each document should point backward to the event that justifies it.
Use the estimate to frame a decision
Describe the scope, assumptions, exclusions, pricing basis, expected schedule, and how long the offer remains valid. If quantities may change, identify what will be measured and how the final amount will be calculated.
An estimate should say how approval occurs. A signature, accepted portal action, purchase order, or written email can be the trigger, depending on the arrangement.
Capture the approved baseline
Freeze the accepted version instead of editing it in place. Save the approval beside that version so later changes can be distinguished from the original decision.
When scope changes, document the price and timing effect before performing the additional work. A revised estimate or change order is more useful than a surprise line on the final invoice.
Issue the invoice when the trigger occurs
The trigger may be a deposit, a completed milestone, delivery, a recurring service period, or final acceptance. Reference the estimate or purchase order and bill only the amount supported by that trigger.
Keep proposal language out of the invoice. The invoice should concentrate on the payable amount, due date, payment instructions, credits, and the delivered item or period.
Close the chain after payment
Record the payment against the invoice number and issue a receipt or paid status when appropriate. If the customer pays only part, preserve the original invoice total and show the allocation and remaining balance.
Retain the estimate, approval, changes, invoice, and payment evidence as one sequence. That chain is more informative than any single document.
Pre-send control checklist
- Estimate identifies scope, assumptions, exclusions, and validity period.
- Approval method and authorized approver are known.
- Accepted version is preserved without later silent edits.
- Changes are approved before they are billed.
- Invoice references the estimate, order, or project.
- Billable trigger is supported by delivery or milestone evidence.
- Invoice contains one clear due date and payment route.
- Payment is allocated to the invoice number.
- Receipt or paid status is created only after funds are confirmed.
- The full document chain is stored together.
Decision table
| Stage | Control question | Required action or evidence |
|---|---|---|
| Estimate | Customer is deciding whether to authorize work | Scope, assumptions, price basis, validity |
| Approval | Customer accepts the proposed baseline | Version, approver, date, conditions |
| Invoice | A contractually billable event occurs | Charge, reference, due date, payment route |
| Receipt | Funds are confirmed and allocated | Amount received, date, method, invoice reference |
Primary sources
BillingFixPro reviewed the following government guidance for the recordkeeping and financial-control principles used on this page: