Developers, designers, and consultants
Invoice milestones for developers: payment schedule template
Plan invoice milestones for developers with a free payment schedule template, a $6,000 worked example, acceptance criteria and client feedback deadlines.
What are invoice milestones for developers?
Invoice milestones split a development project's fee into payments tied to defined events, such as signing the agreement, approving a staging build and completing handover. Each milestone names the deliverable or approval, acceptance criteria, invoice amount and payment deadline. The installments should add up to the agreed project fee.
When to use it
Use this schedule inside a project agreement when delivery can be divided into objective stages the client can review or approve.
Example: invoice milestones for a $6,000 website build
Illustrative fixed-price project in USD, with no tax or discount in this example. Each $2,000 installment is part of the original $6,000 fee, not an additional charge. Agree the triggers and due dates before starting.
| Milestone | When to invoice | Amount · USD | Payment deadline |
|---|---|---|---|
| 1. Project kickoff | Both parties sign the agreement; issue the deposit invoice. | 2,000 | Before development starts. |
| 2. Staging approval | The client approves the staging build against the agreed pages, responsive layouts and form behavior. | 2,000 | Within 7 calendar days of the invoice issued after written approval. |
| 3. Final handover | Deliver the agreed production release, source repository access and handover notes. | 2,000 | Within 7 calendar days of the invoice issued on handover. |
| Total project fee · USD | 6,000 | Three installments, one agreed fee. | |
For this example, give the client 5 business days to review staging. That feedback deadline is separate from the invoice payment deadline. If feedback is late, follow up and agree revised dependent delivery dates; do not silently treat the work as approved. Price an added feature in a separate change order rather than changing the original three installments.
Replace every bracketed field before sending.
01
Engagement summary
Client: [Client legal name] Professional: [Your legal or business name] Engagement: [Project or service name] Currency: [USD / EUR / GBP / NGN / other] Project fee before tax: [Amount] Tax, if applicable: [Amount or rate] Total engagement value: [Amount]
02
Milestone 1 — Start condition
Trigger: The agreement is signed by both parties. Deliverable or decision: [Deposit / discovery start / reserved delivery capacity] Invoice amount: [Amount] Invoice timing: [Issued on signature] Payment due: [Date or number of days] Work unlocked by payment: [Specific work that may begin after cleared payment]
03
Milestone 2 — Reviewable delivery
Trigger: [Prototype / staging build / audit / workshop output] is delivered for review. Acceptance criteria: [Observable criteria] Client review window: [Number] business days Invoice amount: [Amount] Invoice timing: [On delivery / on written approval] Payment due: [Date or number of days]
04
Milestone 3 — Final delivery
Trigger: [Production launch / final files / roadmap / executive readout] is delivered. Final handover includes: [Files, access, documentation, or presentation] Invoice amount: [Amount] Invoice timing: [On delivery / before transfer of final access] Payment due: [Date or number of days]
05
Review delays and changes
If the Client does not provide the required review, access, or consolidated feedback within [number] business days, later delivery dates will move by the resulting delay. Any request that changes deliverables, cost, or delivery time will be documented and approved in a separate change order before the additional work begins.
Before you send it
Customize the commercial details.
- 01Make every trigger observable to both parties.
- 02Confirm all milestone amounts plus tax reconcile to the stated total.
- 03Name what cleared payment unlocks at each stage.
- 04Replace silence-based approval with an explicit rule appropriate to the engagement.
Developer milestone invoicing questions
When should a developer invoice a milestone?
Invoice when the trigger written in the agreement occurs. A deposit can be invoiced on signature, while a staging milestone might require written client approval. State whether invoicing happens on delivery or approval; a label such as ‘50% complete’ does not explain what the client is paying for.
What if the client misses the feedback deadline?
Keep the feedback deadline separate from the payment deadline. Record the requested review, follow up with the named decision-maker and agree how the delay affects later delivery dates. A late reply is not itself client approval or confirmation that an invoice has been paid.
How does Censiq connect a signed milestone to an invoice?
When a client signs a milestone-backed agreement, Censiq creates connected invoice drafts for its milestones. You review the amount, due date, payment instructions and billing trigger, then send each invoice when that stage becomes billable. The draft is not an automatic charge to the client.
Put the approved terms into the workflow
Keep the agreement, invoices, follow-up, and payment record connected.
This template is a general commercial starting point, not legal, tax, or financial advice. Adapt it to the engagement and obtain professional advice where required.