Milestone Invoicing: How to Bill Partial Payments on Big Projects

A $30,000 project billed as one invoice at the end is a $30,000 bet that the client pays on time. If they don't, you've financed months of work, materials, and payroll out of your own pocket. That's the problem milestone invoicing (also called progress billing) solves: you break the project total into partial payments, each triggered by a finished piece of work, so money arrives while the project is still moving.

This guide covers picking milestones, common payment splits, what each milestone invoice shows, numbering the series, and the final reconciliation.

The quick version

• Milestone invoicing means billing a large project in partial payments, each tied to a completed deliverable (design approved, framing inspected, phase 1 launched), not to calendar dates.
• Common splits: 50/50 for short fixed-scope work, 40/30/30 or thirds for medium projects, and deposit + monthly progress + final for long engagements.
• Each milestone invoice should show three numbers: the full project total, the amount due for this milestone, and the remaining balance after payment.
• Number the series consistently (INV-2041-1, INV-2041-2, INV-2041-3) so every partial payment traces back to the same project.
• The final invoice reconciles the whole project: total contract value, every prior payment listed as a credit, and the exact balance due.

Milestones tied to deliverables, not dates

The biggest mistake in progress billing is scheduling payments by date. "Second payment due June 1" sounds tidy, but if the project slips, June 1 arrives with nothing visibly finished and the client pushes back on paying.

A deliverable-based milestone removes the argument: "second payment due when the approved design files are delivered" is either done or it isn't. Good milestone triggers share three traits:

• Observable. The client can verify it without trusting your word: a staging link, a passed inspection, a signed-off proof.
• Binary. It's complete or it isn't. "Design mostly done" is not a milestone; "design approved in writing" is.
• In your control (mostly). Avoid triggers that depend entirely on third parties. If a permit office might sit on paperwork for weeks, tie the milestone to your submission, not their approval.

Examples that work: "wireframes approved," "rough plumbing passes inspection," "phase 1 deployed to production." Examples that invite disputes: "50% of the work complete" (who measures?) or "mid-February" (what if scope moved?).

For client-dependent triggers like "design approved," add a backstop so a silent client can't freeze your cash flow: "milestone is deemed complete 10 business days after delivery unless written revisions are requested."

Common milestone splits (with the math)

There's no single right structure. Match the split to project length and risk.

Two rules of thumb apply to every structure:

• Front-load when your costs are front-loaded. A general contractor buying $5,000 of materials in week one should not be on a 25% first milestone.
• Keep the final payment the smallest chunk you can accept. The last invoice is the one clients slow-walk once the leverage of undelivered work is gone. On a 40/30/30 split you never chase more than 30% of the project.

In the deposit + monthly progress + final model, the deposit works like any upfront payment (see our deposit invoices guide), monthly progress invoices bill work completed that month, and the final invoice trues everything up. It is not the same as a retainer, which reserves ongoing availability rather than paying down one project; see how to bill a retainer for that model.

There's a reason this rhythm is standard: the Federal Reserve's 2025 Report on Employer Firms found that 51% of small employer firms cite uneven cash flow as a financial challenge. Milestone billing turns one lumpy payday into a steady sequence.

What each milestone invoice should show

A partial-payment invoice that just says "Payment 2, $3,600" creates confusion at exactly the moment you want clarity. Every milestone invoice should orient the client with three numbers: the whole, this piece, and what's left.

Here's milestone 2 of 3 on a $12,000 website project, 40/30/30:

Invoice INV-2041-2 for the Riverside Web Project

Project total (per signed estimate #EST-2041): $12,000.00

This invoice: Milestone 2 — Design approved and development started ... $3,600.00

Previously invoiced and paid (INV-2041-1, 03/10/2026): $4,800.00 Remaining after this payment (Milestone 3, due at launch): $3,600.00

Amount due: $3,600.00 (Net 15)

The description line matters: "Milestone 2 — Design approved" documents that the trigger was met, useful evidence if the relationship ever sours.

Progress-style invoices in construction often add a percent-complete column and a retainage line. Retainage is a small percentage of each payment (commonly 5-10%) that the customer holds back until final completion, released after punch-list items are closed. Retainage rules and caps vary by state and contract type, so verify yours before agreeing to a holdback.

Numbering a milestone series

Each milestone payment gets its own invoice with its own number. Never issue one invoice and "collect against it" three times; that breaks your records and confuses everyone's bookkeeping.

The cleanest convention is a shared project root with a sequence suffix:

• INV-2041-1 (milestone 1, deposit)
• INV-2041-2 (milestone 2)
• INV-2041-3 (final)

Anyone scanning your records can see these are partial payments on one project, and each invoice still has a unique identifier for payment matching. A plain global sequence (INV-0147, INV-0148...) works too, as long as each invoice references the project name and estimate number so the series is traceable. Our guide on how to number invoices covers the schemes and pitfalls.

Invoity's Multiple-invoices option can generate the whole numbered series across your milestone dates in one pass, so invoices 2 and 3 are drafted before the project even starts.

Handling scope changes between milestones

Long projects change. The client adds a room, a feature, a second shoot day. The rule: never silently absorb changes into existing milestones, and never inflate a milestone invoice for extras the client hasn't approved in writing.

Document each change as a change order stating the new work, its price, and its effect on the project total and payment schedule. Bill it as its own invoice or as a clearly labeled line on the next milestone ("Change order CO-2: add contact form integration ... $850"). The final invoice then reconciles against the revised total, not the original one. Mechanics and wording are in our companion post on how to bill change orders.

The discipline pays off at the end. According to the Intuit QuickBooks 2025 US Small Business Late Payments Report, 56% of US small businesses are owed money from unpaid invoices, averaging about $17,500. Disputed scope is a classic reason final payments stall, and a paper trail of approved change orders removes the dispute.

The final invoice: reconciling the whole project

The last invoice in a milestone series does double duty: it bills the final payment and summarizes the entire project's money flow, so the client's accountant can close the file without emailing you.

Continuing the $12,000 example with one $850 change order:

Invoice INV-2041-3 (Final) for the Riverside Web Project

Original project total (estimate #EST-2041): $12,000.00 Change order CO-2 (approved 04/22/2026): +$850.00 Revised project total: $12,850.00

Less: INV-2041-1, paid 03/10/2026: −$4,800.00 Less: INV-2041-2, paid 04/15/2026: −$3,600.00

Balance due (Milestone 3 — site launched, plus CO-2): $4,450.00

Every prior payment appears with its invoice number and payment date, and the balance is arithmetic the client can check in seconds. If an amount needs adjusting downward, issue a credit note rather than editing a paid invoice.

Set the final due date deliberately (Net 15 rather than Net 30 is reasonable when the work is already delivered) and make paying easy: invoices with online payment options get paid up to twice as fast (Xero, 2024).

One disclaimer: this is general information, not legal or tax advice. Contract and retainage rules vary by state and jurisdiction, so verify yours or ask a professional for anything contract-critical.

Ready to set up your series? Create each milestone invoice with our free invoice generator, showing the project total, current milestone, and remaining balance, then download the PDF instantly with no signup. Put the payment schedule in writing first with the estimate generator.

Frequently asked questions

What is milestone invoicing?

Milestone invoicing (or progress billing) is splitting a large project's price into partial payments, each invoiced when a defined deliverable is complete. Instead of one invoice at the end, the client pays as visible progress lands: for example 40% at kickoff, 30% at design approval, 30% at launch. Each milestone gets its own uniquely numbered invoice.

How do I invoice a partial payment on a project?

Issue a separate invoice for each partial payment, not one invoice paid in pieces. Show the full project total, the milestone being billed with a description of the completed deliverable, amounts previously invoiced, and the remaining balance. Number it as part of a series (INV-2041-2) so payments trace back to one project.

What is a good milestone payment schedule?

For short fixed-scope work, 50/50 (half upfront, half on delivery) is standard. Medium projects suit thirds or 40/30/30 tied to a start, a midpoint deliverable, and completion. Long engagements usually run deposit + monthly progress invoices + final reconciliation. Whatever the split, tie each payment to a verifiable deliverable and keep the final payment the smallest.

What is retainage in progress billing?

Retainage is a portion of each progress payment (commonly 5-10%) that the customer withholds until the project is fully complete and accepted, mainly in construction. It's released after final walkthrough and punch-list completion. Rules, caps, and release timelines vary by state and contract, so check what applies before agreeing to a holdback.