How to Invoice for Milestone-Based Projects

Milestone billing means you invoice when defined pieces of work are complete—not just at the end. Done well, it improves cash flow and aligns client attention with your delivery rhythm. Done poorly, you argue over whether a “milestone” was met.

Industry guidance from groups like the Project Management Institute emphasizes clear scope and deliverables; your invoices should mirror that clarity.

Define milestones in the contract

Each milestone should list:

• Deliverable — what the client receives (document, build, phase sign-off)
• Acceptance criteria — how they confirm it is done
• Invoice amount — fixed fee or percentage of total contract value
• Due date for payment — tied to acceptance or a fixed calendar offset

Without this, “50% on design approval” becomes subjective.

Typical milestone structures

Percentage of total fee

Common in agencies and software: 30% kickoff, 40% mid-project, 30% launch. Each invoice references the contract value and cumulative billed.

Fixed fees per phase

Good when phases have very different effort. Shows transparency for clients who compare phase value to price.

Deposit + milestones

Combine deposit invoicing with later milestones so you cover early risk without front-loading everything.

What to put on the milestone invoice

• Milestone name and completion date
• Reference to SOW or statement of work clause
• Prior payments and balance — especially on long jobs; see progress billing for related patterns
• Next milestone preview — sets expectations for the upcoming bill

Follow structural basics from how to write an invoice and keep an audit trail of approvals and versions.

When the client delays acceptance

If a milestone is done but approval stalls:

1. Document delivery (email, link, read receipt).
2. Invoke the contract’s deemed acceptance or review window clause if you have one.
3. Send a polite invoice per contract, noting the review period elapsed.

For tension-heavy situations, handling disputed invoices offers de-escalation language you can adapt.

Milestones vs hourly

Not sure which model fits? Read hourly vs fixed-price invoicing—milestones usually pair with fixed fees, but you can blend T&M for out-of-scope work as separate line items.

Putting it into practice

Before kickoff, create a milestone table in the contract with invoice amounts, deliverables, and review windows. During delivery, log evidence of completion in the same folder as the PDF you will attach to the invoice email—design files, staging links, or signed UAT forms. If a client wants to combine milestones for cash-flow reasons, use a single invoice with subsections rather than skipping documentation for earlier gates. For long programs, reconcile cumulative billings monthly against your progress billing plan so you never exceed contract caps accidentally. When a milestone slips, update the forecasted invoice date in your calendar and notify AP early; surprises erode trust more than revised dates. Tie milestone templates to templates so numbering, tax, and footers stay consistent across projects.

Client communication around milestones

Give sponsors a 48-hour heads-up before each milestone invoice sends so AP is not blindsided. Include a plain-language status line in the email body: what shipped, what is next, and the invoice number you are about to book. If legal requires a formal sign-off, attach the approval email as a PDF appendix once, then reference it on subsequent bills. When you combine milestones for administrative ease, still itemize each gate inside the invoice so internal sponsors see their budget impact. Cross-link future work to deposit invoicing if the next phase needs fresh funding before you start.

---

Ship milestone invoices with templates and reminders built in. Get started with InvoiceQuickly.

2026 milestone-billing benchmarks by industry

Source: AIA standard contract terms 2024, AIGA pricing standards, AGC Construction Outlook 2026, and project management software billing benchmarks (Harvest, Bonsai, Float).

Step-by-step: structure a milestone-billed engagement

1. Define each milestone as a deliverable, not a date — "Design phase complete" should mean specific artifacts delivered (wireframes, design system, signed-off mockups), not "by March 15."
2. Tie payment % to value delivered, not effort spent — final 20% should be meaningful enough that you stay engaged through closeout. Front-loading too heavily creates abandonment risk for the client.
3. Write acceptance criteria into the SOW — what exactly does the client need to do/sign to trigger the next invoice? Vague language = stuck invoices.
4. Invoice the day a milestone is hit — not at month-end. Speed matters; AP teams process invoices faster when tied to a specific deliverable.
5. Build a "stalled milestone" clause — if the client delays acceptance past 14 days without written cause, the milestone is deemed accepted and the invoice issues automatically.

Real milestone setups that work

• Kenji (mobile dev shop) structures 5 milestones at 20% each on $80K builds. Project rarely stalls because the client has skin in the game throughout, and Kenji never fronts more than two weeks of unbilled work.
• Anika (wedding photographer) uses 25% booking deposit, 50% at 30 days out, 25% on gallery delivery. She switched from "balance on event day" because day-of payments were stressful and frequently late.
• Owen (construction GC) ties draws to completed inspections — the bank inspector signs off, the invoice issues. Removed all "is it done?" arguments because a third party validates each step.

Frequently Asked Questions

How many milestones should a project have? Three to five for projects under $50K. More creates invoice fatigue and admin overhead. Six or more makes sense only for $200K+ engagements lasting 6+ months.

What if a milestone is "almost" done? It isn't done. Half-complete milestones invite half-paid invoices and disputes. Either ship a smaller scope as the milestone, or note partial progress without invoicing.

Should I require deposits in addition to milestones? Yes for new clients or any project over $5,000. The deposit covers your discovery investment and signals client commitment. Apply it against milestone 1 or final.

How do I handle scope changes mid-project? Issue a change order with new dollar amount and (if needed) a new milestone schedule. Don't fold extra scope into existing milestones — it dilutes everything.

What happens if the client pauses the project? Your contract should include a pause clause: if the client suspends work for more than X days, the most recently completed milestone invoices regardless of acceptance, and resumption requires a new schedule. Otherwise pauses become permanent receivables.