Getting paid

Milestone Invoicing and Partial Payments

Anything longer than a few weeks should not be invoiced in one lump at the end. Doing so means you fund the entire project from your own working capital, and it concentrates all of your credit risk into a single moment months away. Milestone invoicing spreads both. The difficulty is not the concept — it is choosing milestones that cannot be argued about, which is where most schedules quietly fail.

By Arshad Hossain · Published 16 August 2026

The short version

Tie milestones to observable events, never to dates. Dates drift and become arguments.
Front-load the schedule slightly — you carry the risk earliest in a project.
A partial payment does not settle the invoice unless you agree it does, in writing.
A payment plan is better than a bad debt, but put it in writing with a default clause.

Choose milestones that are observable, not scheduled

The most common mistake is tying payments to dates: 30% on 1 September, 30% on 1 October. It looks tidy and it produces arguments, because projects slip and the moment they do, the payment schedule is disconnected from reality. The client refuses to pay for a stage not reached; you point at the contract; nobody is clearly right.

Tie payments to observable states instead. Not "1 October" but "on approval of the design concept". Not "month two" but "on completion of first fix". Either the thing has happened or it has not, and both parties can see which.

Where a milestone requires client approval, add a deemed-approval clause with a specific window: approval is deemed given if no feedback is received within five working days. Without it, a client who simply does not respond can stall your payment indefinitely without ever refusing anything.

Keep the number of milestones proportionate. Three to five suits most projects. A dozen creates more invoicing admin than the cashflow benefit justifies.

Weak milestone	Strong milestone	Why
1 October	On concept approval	Survives project slippage
50% complete	On delivery of the beta build	Percentage complete is arguable
Month two	On first fix completion	Observable by both parties
When client is happy	On sign-off, or 5 days after delivery	Satisfaction is not a testable state
On launch	On handover of final files	Launch may depend on third parties

Front-load the schedule

A schedule of 25/25/25/25 looks fair and is not, because your risk is not evenly distributed. You are most exposed early: you have committed time, turned down other work, and possibly bought materials, all before the client has demonstrated they will pay at all.

Something closer to 40/30/30, or 50/25/25 on shorter projects, matches the risk better. The first payment establishes the client is real and covers your setup exposure.

Resist a schedule that back-loads heavily — 10/20/70 — however much a client pushes for it. That structure leaves you funding almost the whole project and concentrates your risk at the exact point where a client who wants to avoid paying has already received most of the value.

Never let the final payment be so large that walking away is attractive to the client. If the last stage is 60% of the fee, a client in difficulty may simply take what they have and disappear.

When a client pays part of an invoice

A partial payment against an invoice is not the same as a settled invoice, and how you handle it matters more than the amounts involved.

First, work out why. A part payment is usually one of three things: a genuine dispute about a portion of the work, a cashflow problem, or a deduction such as withholding tax. Each needs a different response, and treating a tax deduction as a dispute damages the relationship for nothing.

Second, be careful about accepting a part payment described as being "in full and final settlement". In some jurisdictions, banking a payment on those stated terms can be treated as accepting them. If you do not agree it settles the debt, say so in writing before or immediately on receipt, and keep the record.

Third, allocate it explicitly. Tell the client which invoice and which lines the payment has been applied to, and issue a statement showing the remaining balance. Ambiguous allocation across several invoices is how balances become genuinely uncertain months later.

Payment plans for clients in difficulty

A client who cannot pay in full but will pay over time is a better outcome than a bad debt, and refusing to engage often converts the first into the second.

Put the arrangement in writing: the total owed, the instalment amounts, the dates, and what happens on default. A default clause matters — typically, missing an instalment makes the whole remaining balance immediately due. Without it, you have quietly converted a due debt into a long-dated one with no consequence for missing payments.

Keep the original invoice standing rather than cancelling and reissuing. The debt is the debt; the plan is how it is being paid. Reissuing muddies the audit trail and can reset limitation periods in ways that do not favour you.

Stop further work while a plan is running unless it is genuinely necessary to enable payment. Continuing to deliver into an unpaid balance is how a manageable problem doubles. There is more on the wider situation in how to chase an unpaid invoice.

Milestone and part payment questions, answered

What is milestone invoicing?

Splitting a project fee into several invoices, each issued when a defined stage is reached. It reduces how much work you fund from your own capital and spreads your credit risk instead of concentrating it in one payment at the end.

How do I choose payment milestones?

Pick observable events rather than dates — concept approval, first fix complete, beta delivered. Either the thing happened or it did not, which both parties can see. Dates disconnect from reality the moment a project slips, and then they generate arguments.

How many milestones should a project have?

Three to five for most projects. Fewer leaves you carrying too much unpaid work between payments; more creates invoicing admin that outweighs the cashflow benefit. Scale with project length rather than value.

What percentage should each milestone be?

Front-load slightly, because your risk is highest early. Something like 40/30/30, or 50/25/25 on shorter work, matches exposure better than an even split. Avoid a large final payment that makes walking away attractive to a client in difficulty.

What is a deemed approval clause?

A term stating that a deliverable is treated as approved if the client does not respond within a set window, commonly five working days. Without it, a client who simply goes quiet can stall your milestone payment indefinitely without ever refusing anything.

What do I do if a client pays only part of an invoice?

Establish why first — a dispute, a cashflow problem, or a deduction such as withholding tax each need different handling. Then allocate the payment explicitly, tell the client what it was applied to, and issue a statement showing the remaining balance.

Can I refuse a partial payment?

You generally do not have to refuse it — banking it and continuing to pursue the balance is usually the practical route. The exception is a payment expressly offered in full and final settlement, where accepting may be treated as agreeing to those terms.

What does "full and final settlement" mean?

An offer to close the whole debt for less than the amount owed. In some jurisdictions banking a payment stated to be on those terms can amount to accepting them, so if you do not agree, say so in writing before or immediately on receipt.

Should I offer a payment plan?

Usually yes, where the client is engaging and the alternative is a bad debt. Put it in writing with instalment amounts, dates and a default clause making the whole balance due on a missed payment. Keep the original invoice standing rather than reissuing.

Should I keep working during a payment plan?

Generally no, unless the work is what enables the client to pay you. Continuing to deliver into an unpaid balance is how a manageable exposure doubles, and it removes any incentive for the plan to be honoured.

How do I invoice a stage that the client has not approved?

If you have a deemed approval clause and the window has passed, invoice it and reference the clause. If not, ask specifically what is outstanding and set a response deadline. Silence is not rejection, but it also is not something you should absorb indefinitely.

What is a progress invoice?

Another term for a milestone invoice, common in construction, where it usually reflects the value of work completed to date less amounts previously certified and any retention held. The principle is identical: bill as you progress rather than at the end.

Frequently Asked Questions

Should milestone invoices reference the original quotation?

Yes. Quote the quotation or contract number and state which milestone this invoice covers and what remains. It lets the client reconcile the sequence of invoices against the total they agreed, which is the most common cause of milestone invoices being queried.

What is retention in a milestone schedule?

A percentage held back from each payment, common in construction, released after a defects period. Show it as an explicit deduction on each invoice and diarise the release dates, because retention nobody chases is frequently never paid.

Can I change the milestone schedule mid-project?

Only by agreement, in writing. Scope changes often justify it, and a client asking to defer a payment is worth discussing rather than refusing outright. What you should not do is unilaterally reschedule, which undermines the agreed basis of the whole arrangement.

Create a milestone invoice

Free, no sign-up, no watermarks. Your data stays in your browser.

Create an Invoice Free