How Do Payment Milestone Clauses Work?

A payment milestone clause lets you invoice your client when an agreed stage of a project is reached, instead of waiting until the whole job is finished.

That sounds simple, but the wording matters. A milestone can protect your cash flow, reduce awkward payment conversations and make project delivery smoother. But if the clause is vague, you can end up arguing about whether the milestone was actually completed, whether the client has accepted the work, or whether changes to the project have shifted the payment date.

If you run a consulting business, creative agency, software company, building related business or any project based service, getting your business terms and conditions and milestone payment settings right can make a big difference. The aim is to make payment feel predictable, not like something you have to renegotiate every few weeks.

What Is A Payment Milestone Clause?

A payment milestone clause is a contract term that says when you can invoice for each stage of the project, how much you can invoice, and what has to happen before payment is due.

Instead of saying the client pays 100% at the end, your agreement might break the project into stages such as:

• 30% deposit on signing the contract
• 30% when the first draft, strategy or prototype is delivered
• 30% when implementation, build or production is completed
• 10% on final delivery or handover

Milestones can be based on events, deliverables, dates or a mix of all three. For example, a brand agency might invoice when the brand strategy is approved. A software developer might invoice when the staging version is delivered for testing. A consultant might invoice monthly based on progress against an implementation plan.

The practical benefit is that you're not carrying the whole cost of the project until the end. If you have staff, subcontractors, software costs or suppliers to pay, milestone payments can help your business stay healthy while the work is still underway.

How Should You Structure Project Milestone Payments?

You should structure project milestone payments around the real flow of work, risk and costs in your project.

There isn't one correct formula. A good milestone structure depends on your industry, the project length, how much upfront work you do, whether you use contractors, and how much control the client has over approvals.

Common Milestone Structures

Here are a few common ways to structure milestone payments:

• Deposit plus completion payment: useful for smaller projects where the scope is simple and the timeline is short.
• Stage based payments: helpful for projects with clear phases, such as discovery, design, build, testing and launch.
• Date based payments: useful for ongoing consulting, retainers or long projects where progress may depend on client input.
• Deliverable based payments: useful where each output can be identified clearly, such as a report, campaign, website module or training program.
• Hybrid payments: often the most practical option, combining a deposit, stage payments and monthly progress payments.

For example, Maya runs a digital agency in Melbourne. She agrees to build a new website for a retail client. Instead of invoicing only at launch, her contract says:

• 40% is payable when the contract is signed
• 25% is payable when wireframes are delivered
• 25% is payable when the development site is ready for client testing
• 10% is payable on launch, or 10 business days after the site is ready to launch if the client delays approval

That last part is important. If the client takes three weeks to provide feedback or delays launch for reasons outside Maya's control, her final payment isn't stuck indefinitely.

Match The Payment To The Risk

Try to avoid doing a large amount of unpaid work before the first real payment. A small deposit might be fine for low risk work, but it may not be enough if you're booking staff, paying subcontractors or buying project materials early.

You can also use higher upfront payments where the project is custom, you need to reserve team capacity, the client is new, the timeline is tight, or there are third party costs you need to pay in advance.

For bigger or longer projects, smaller and more frequent milestones can be better. They keep invoices easier for the client to approve and help you spot payment issues early.

Can You Invoice On Milestone Completion?

Yes, you can invoice on milestone completion if your contract clearly says you can.

Your clause should explain what counts as completion, when the invoice can be issued, and when the client must pay. If you leave this loose, you may end up with a client saying, We don't think that stage is finished yet, even though you've done the work you agreed to do.

A clear clause might cover:

• the milestone name or stage
• the deliverable or task attached to that milestone
• the invoice amount or percentage of the project fee
• whether GST is included or added on top
• when you can issue the invoice
• the payment due date, such as 7, 14 or 30 days from invoice
• what happens if the client doesn't respond to a milestone submission

If your business is registered for GST, your pricing and invoicing should make clear whether amounts are GST inclusive or GST exclusive. Your invoice terms should also line up with your contract. If the agreement says payment is due within 7 days, but your invoice says 30 days, the inconsistency can create confusion and slow down payment.

Be Careful With Completion Versus Acceptance

Completion and acceptance aren't always the same thing.

Completion usually means you've done the work required for that milestone. Acceptance means the client has reviewed and approved it.

If you say payment is due only on acceptance, the client may be able to slow payment simply by delaying approval. In many project contracts, it's better to say payment is due when you submit the milestone deliverable, unless the client identifies specific defects or non compliance within a set review period.

That doesn't mean the client has no protection. It just means they need to be specific and timely if they believe the work doesn't meet the agreed requirements.

What Acceptance Criteria Should You Include?

You should include objective acceptance criteria that make it clear whether the milestone has been met.

This is one of the most useful parts of a payment milestone clause, because it turns a subjective argument into a practical checklist. Instead of asking whether the client is happy, you ask whether the agreed criteria have been satisfied.

Good acceptance criteria might include:

• the deliverable format, such as PDF report, editable design file, training session or software release
• the functions or features that must be included
• the number of concepts, revisions, pages, modules, workshops or deliverables
• technical requirements, such as browser compatibility or file specifications
• client responsibilities, such as providing content, access, approvals or test data
• what isn't included, such as copywriting, extra integrations or out of hours support

The more custom or technical the project is, the more helpful this becomes. For software, creative work and consulting projects, acceptance criteria can stop scope creep from being disguised as a quality issue.

Use Review Periods

Your contract should give the client a reasonable review period for each milestone. For many service projects, this might be 5 or 10 business days, but the right period depends on the project size and complexity.

The clause can say that the client must either approve the milestone, give written reasons why it doesn't meet the agreed acceptance criteria, or identify the specific changes needed to meet those criteria.

If the client doesn't respond within the review period, you can include a deemed acceptance mechanism. This means the milestone is treated as accepted if the client stays silent after a set time.

Allow Reasonable Revisions, But Set Limits

Many project disputes come from unclear revision rights. The client thinks unlimited changes are included. You thought two rounds of revisions were included.

Your milestone clause or statement of work should spell out how many revision rounds are included, what counts as a revision rather than a new request, how quickly the client must provide consolidated feedback, and whether extra revisions are charged at an hourly rate or agreed fixed fee.

This is particularly important for marketing, design, website, software development, architecture, consulting and training projects where the client may want to refine the work over time.

What Happens If The Client Delays Or Withholds Approval?

If the client delays or withholds approval, your contract should say whether payment still becomes due, whether deadlines move, and what process applies if there's a genuine issue with the work.

This is where many milestone payment clauses fall short. They describe the happy path, but not what happens when the client goes quiet, changes their mind, or delays giving feedback.

Client Delays

Your contract should identify the things the client must do for you to complete the project. This might include providing briefs, documents, images, access or logins, attending meetings, reviewing drafts, making decisions and arranging internal approvals.

If the client misses these steps, your contract can say the project timeline is extended and any affected milestone payment dates still apply, or are adjusted in a fair and specific way.

For example, you might say that if the client delays providing required materials for more than 10 business days, you can invoice for work completed to date and move the project to your next available production slot.

Withheld Approval

A client shouldn't be able to withhold approval for vague reasons if the milestone meets the agreed criteria.

Your contract can say that approval can only be withheld if the deliverable materially fails to meet the scope, specifications or acceptance criteria. The client should need to explain the issue in writing and give enough detail for you to fix it.

You can also include a process such as:

1. You submit the milestone deliverable.
2. The client has a set review period to approve it or raise specific issues.
3. If the client raises valid issues, you correct them within a reasonable timeframe.
4. If the client doesn't respond, the milestone is deemed accepted.
5. If the client uses the deliverable commercially, the milestone is treated as accepted.

The last point can be very useful. If a client starts using your strategy, designs, software, campaign assets or report, it's hard for them to say the milestone hasn't been accepted at all.

Non Payment

If an invoice isn't paid, your contract can give you practical options. These might include pausing work, withholding final deliverables, charging interest on overdue amounts, recovering reasonable debt collection costs, or terminating after notice.

Be careful with how these rights are drafted. If your terms are standard form contracts used with small business clients, Australia's unfair contract terms regime under the Australian Consumer Law may apply. Since November 2023, unfair contract terms can attract penalties, not just be declared void.

The safer approach is to make payment rights clear, balanced and connected to the actual problem. For example, pausing future work after giving written notice of an overdue invoice is usually easier to justify than immediately cancelling everything without warning.

How Do Variations, Delays And Scope Changes Affect Milestones?

Variations, delays and scope changes should affect milestones only in the way your contract says they do.

Projects rarely run exactly as planned. The client may ask for extra features, new pages, more workshops, a different timeline or a change in direction. If your contract doesn't deal with this, you can end up doing extra work without being paid for it.

Variations

A variation clause should explain how changes are requested, priced and approved, with clear clause drafting.

A practical variation process might say:

• either party can request a change in writing
• you'll confirm the impact on fees, milestones and timing
• the change only starts once both parties approve it in writing
• urgent changes may be charged at agreed hourly or day rates
• work outside the agreed scope isn't included in the original milestone price

This protects both sides. The client knows what extra work will cost before it happens, and you avoid unpaid scope creep.

For smaller jobs, an email approval may be enough if your contract allows it. For larger projects, a signed variation or updated statement of work review is usually cleaner.

Delays

Your contract should separate delays caused by you from delays caused by the client or third parties.

If you cause the delay, the client may reasonably expect revised delivery dates. If the client causes the delay, you may need the right to extend deadlines, invoice for completed work, and charge for extra time if the delay creates additional cost.

Construction And Building-Related Projects

If your project involves construction work or related goods and services, security of payment laws may also be relevant. These laws are state and territory based and can set strict rules around payment claims, payment schedules and adjudication.

Because the rules differ across Australia, construction businesses should be careful to align milestone clauses with the relevant security of payment legislation in the state or territory where the work is performed.

Intellectual Property And Final Handover

Milestone payments often connect closely with intellectual property. For example, you might not want ownership of final designs, source code, documents or campaign assets to transfer until all invoices are paid.

Your contract can say whether the client receives:

• ownership of the final deliverables after full payment
• a licence to use the work while fees are being paid
• no right to use drafts, rejected concepts or unpaid work
• a limited right to use certain materials for a specific purpose

This is especially important for creative, software, consulting and training businesses. Copyright will often be owned by the person or business that created the work, subject to important exceptions such as employee created IP. If the client is meant to own the final deliverables, your contract should include a clear written IP assignment or licence clause, and state whether ownership transfers only after full payment.

What Other Payment Terms Should Sit Around Your Milestones?

Your milestone clause should work together with the rest of your payment terms, not sit on its own.

Think of milestones as the trigger for invoicing, while the surrounding payment terms explain the mechanics and consequences.

Your agreement should usually cover:

• Fees: fixed fee, hourly rates, day rates or a mix.
• GST: whether prices include GST or are plus GST.
• Expenses: what costs are reimbursable and whether pre approval is needed.
• Invoice timing: when invoices can be issued for each milestone.
• Payment period: how many days the client has to pay.
• Late payment: whether interest, suspension rights or recovery costs apply.
• Deposits: whether they're refundable, partly refundable or applied to the final invoice.
• Termination: what is payable if the project ends early.
• Disputed invoices: the process for raising and resolving payment concerns.

Also think about your Australian Consumer Law obligations. If you're dealing with consumers or small businesses, avoid terms that are one sided, unclear or likely to mislead. Your pricing, deliverables and payment triggers should match what you actually sell.

Templates can be a helpful starting point, but milestone clauses often need tailoring. A clause that works for a graphic design package may not work for a software build, business consulting project or engineering engagement.

Key Takeaways

• A payment milestone clause lets you invoice at agreed project stages instead of waiting until the end.
• Clear acceptance criteria help prevent disputes about whether a milestone has been completed.
• Your contract should deal with client delays, silence and withheld approval so your cash flow isn't held up indefinitely.
• Variations should be approved in writing, with the impact on fees, timing and milestones clearly recorded.
• Milestone payment terms should sit alongside GST, late payment, IP ownership, termination and disputed invoice clauses.
• If your project involves construction, software, creative work or large upfront costs, tailored drafting can make a real difference.

If you'd like help with your project contracts, milestone payment terms, acceptance criteria or variation clauses, you can reach us at 1800 730 617 or team@sprintlaw.com.au for a free, no-obligations chat.