Milestone Invoice Template
A milestone invoice is issued when a defined project milestone is completed — a design approved, a phase delivered, a system live. Payment is tied to deliverables rather than time, which gives both sides a clear, objective trigger for each bill.
When to use this
- When the contract splits payment across defined deliverables
- When you want payment triggered by results, not hours
- When the client wants cost certainty tied to visible progress
- When phases of work can be accepted or signed off independently
- When working with fixed-scope projects and staged payments
Key fields to include
- Milestone name and its acceptance criteria
- Date the milestone was completed or approved
- Amount due for this milestone
- Milestone number in the project sequence
- Client sign-off reference or approval date
- Remaining milestones and their scheduled amounts
Frequently asked questions
What makes a good milestone definition?
A milestone should be specific, verifiable, and accepted by the client — 'homepage design approved in writing', not 'design work progressed'. Vague milestones cause payment arguments; crisp ones prevent them.
Can I invoice a milestone the client has not approved yet?
You can invoice per the contract schedule, but payment usually follows acceptance. If approval is delayed, refer to the contract's acceptance clause — many set a deadline after which the milestone is deemed accepted.
Milestone vs progress billing — which should I use?
Use milestones when deliverables are distinct and sign-off is practical. Use progress billing when work is continuous and best measured as percent-complete. Many projects combine both.
More use cases
Create your document in seconds
Free forever. No signup, no watermarks — your data never leaves your browser.