Progress Invoice vs Final Invoice

Short answer

A progress invoice requests payment for an approved portion of a project before the entire scope is complete. A final invoice bills the last approved amount and reconciles the full contract value, change orders, earlier invoices, deposits, payments, credits, retainage where applicable, and the remaining balance.

Create a project invoice with the free invoice generator, then connect every billing stage to the contract and documented approval.

What is a progress invoice?

A progress invoice, also called an interim or stage invoice in some contexts, is issued during a project. Its calculation may be based on:

• A completed milestone.
• Percentage of work completed.
• Measured quantities.
• Time and materials during a billing period.
• A scheduled payment stage.

The invoice should identify the covered period or milestone, current charge, previous billings, and remaining contract value where relevant.

What is a final invoice?

A final invoice is issued after the final billable event under the agreement. It should close the project billing record by showing:

• Completed final scope or milestone.
• Original contract value.
• Approved additions and deductions.
• Total amount previously invoiced.
• Deposits, payments, and credits received.
• Any valid retainage or final release amount.
• Final total and remaining amount due.

"Final" should mean the normal billing cycle is complete. If a legitimate later correction is required, use a traceable correction or adjustment process rather than changing the issued document silently.

Key differences

• Project status: Progress invoices cover ongoing work; final invoices follow completion or the agreed final trigger.
• Amount: A progress invoice bills one stage; the final invoice reconciles the full project.
• Balance: Progress documents show remaining contract value; the final invoice establishes the final payable balance.
• Evidence: Progress billing may need milestone or quantity approval; final billing often needs completion or acceptance evidence.
• Adjustments: The final invoice should account for all approved change orders, credits, deposits, and previous payments.

Practical milestone example

Assume a $12,000 software project uses four stages:

1. Deposit before work: $3,000.
2. Progress invoice after design approval: $3,000.
3. Progress invoice after beta acceptance: $3,000.
4. Final invoice after production release: $3,000.

Each invoice identifies its milestone and the earlier verified payments. The final invoice also confirms the complete contract value and whether any approved changes altered the total.

For a broader schedule design, see the invoice installment payment plan guide.

Percentage-complete billing

When billing by percentage complete, show the basis used to measure progress. A clear calculation can state:

• Adjusted contract value.
• Approved percentage complete to date.
• Earned amount to date.
• Amount billed previously.
• Current progress charge.
• Retainage or other agreed holdback, if applicable.
• Current amount due.

Do not use an unsupported percentage. Keep site records, quantity measurements, approvals, or milestone evidence that explains the value.

Previous billings vs previous payments

Previous billings are amounts already invoiced. Previous payments are amounts actually received. They are not interchangeable.

A customer may have been invoiced $6,000 but paid only $3,000. Show both values separately so the current charge and overdue balance do not become confused. Read amount due vs balance due for clear labels.

Change orders

Add only changes that follow the project's approval process. Identify each change-order number, description, amount, and effect on the contract value. Unapproved extra work should not be hidden inside a progress percentage.

Keep the original scope, approvals, progress invoices, payments, and final invoice connected through the invoice audit trail.

Retainage or holdback

Some project agreements withhold part of each progress payment until completion or another condition. Show the agreed rate, amount withheld, cumulative balance, and release condition clearly.

Rules and terminology vary by contract and jurisdiction. Confirm the required treatment and do not present retained funds as paid.

Supporting documents

Depending on the project, attach or retain:

• Milestone approval.
• Progress report.
• Quantity or completion certificate.
• Timesheet and expense evidence.
• Approved change order.
• Delivery or deployment record.
• Final acceptance or completion confirmation.

The invoice supporting documents guide explains how to keep evidence relevant and traceable.

Final checklist

• Invoice identifies progress or final status.
• Covered milestone, period, or quantity is clear.
• Contract value includes approved changes only.
• Prior billings and prior payments are separate.
• Deposit and credits are applied once.
• Retainage or holdback is calculated correctly where applicable.
• Current charge and total balance reconcile.
• Final invoice includes completion or acceptance evidence.

Browse the blog archive for more project billing and payment guidance.

FAQs

Is a progress invoice the same as a deposit invoice?

No. A deposit is usually requested before the related work is completed. A progress invoice generally bills work or a milestone completed during the project.

Does every progress invoice need a new invoice number?

Each formal invoice should use its own unique identifier while also referencing the same project, contract, or schedule.

Should the final invoice show previous invoices?

Yes, when needed to reconcile the full project. Show prior billings, payments, deposits, credits, and the remaining balance without rebilling earlier work.

Can a final invoice be corrected?

Yes, when a genuine error or later adjustment requires it, but preserve the original and use the appropriate correction, credit, debit, or replacement process.