A client asks to split the fee. It sounds simple, even reasonable. Projects take time to deliver, budgets get allocated in phases, and nobody wants to wire a large sum before work has begun. But the moment you agree to spread payment across milestones, you have quietly accepted a new set of risks — risks that have nothing to do with the quality of your work. You are now a creditor. The work will be done before the money arrives, and the gap between those two events is where most freelance disputes are born.
This guide is written for the professional who already knows how to do the work. What it covers is the mechanics of protecting the payment: how to structure an instalment schedule that serves both parties, how to write clauses that actually hold, what to do when a milestone hits and a client delays, and how the settlement layer itself — the infrastructure that moves money from their account to yours — can give you certainty instead of anxiety.
Figures quoted in the data section of this guide; the 85% is from the 2025 Contractor Management Report.
Why clients ask to pay in instalments — and what it really means
Payment plans can be particularly effective when clients are committed to paying but are experiencing cash flow problems. That is often the honest reason. A small business running a website redesign, a product launch, or a brand refresh may genuinely be managing a budget quarter by quarter. Splitting a $12,000 (AUD 18,500) engagement into three tranches lines up with how their finance team releases spend.
But there is a second, less comfortable version of the same request: the client who wants to defer commitment. Paying in full upfront forces a decision. Paying across milestones lets them stay loosely engaged — approving work incrementally, reserving the right to slow down, pivot, or quietly wind down the scope if something internal changes. Freelancing or contracting by nature has less predictability and stability around frequent, regular, ongoing payments — because projects are defined by singular engagements and shorter-term stints, working for different companies.
You cannot always tell, at the proposal stage, which type of client you are dealing with. What you can do is build a payment structure that works whether the client is in good faith or not.
There is a third scenario that comes up on larger deals: the client is not one person but an organisation with approval hierarchies, procurement timelines, and accounts payable teams who operate on Net 30 or Net 45 cycles regardless of what the project manager agreed. International clients, or clients inside large organisations, may operate on different payment norms — some use Net 15 terms, others use Net 30 or longer cycles. When you are working directly with a procurement-controlled budget, milestone billing does not just protect your cash flow — it is often the only realistic way to receive payment at a pace that matches your output.
The instalment structures that actually work
Freelance payment terms are the written conditions that say when you get paid, how much, by what method, and what happens if the client pays late — and they live in your contract and get repeated on every invoice. The specific split you choose matters less than the logic behind it.
The 50/50 structure
The most widely adopted split is 50% on signing, 50% on delivery. Some freelancers prefer getting paid in three instalments, separated into 40/40/20 or 30/30/40, while others agree on two instalments: 25/75 or 50% upfront and the rest on completion of the project. For short engagements — under four weeks — 50/50 is clean and defensible. Half the fee at signature commits the client. The remainder on final delivery gives you leverage for the last handover.
The weakness: if the project runs long, you may be financing the second half of the work with your own runway for weeks.
The three-milestone structure
For projects between four and twelve weeks, three tranches work better. A common structure is:
- 30% on contract signing — confirms intent, covers your immediate costs
- 40% at a defined midpoint deliverable — draft approval, prototype sign-off, mid-project review
- 30% on final delivery — releases the remaining assets, closes the engagement
Most freelance projects work well with three to five milestones. A simple structure is: deposit on signing, payment at midpoint, and final payment on delivery.
The midpoint payment is the most important of the three. It breaks the long gap between start and finish. Beyond risk management, there is a pure cash flow reality: if you are working on a project for eight to twelve weeks and only invoicing at the end, you are funding the client's project with your own money.
The 40/40/20 structure
This variant loads more weight into the first two payments, leaving a smaller final tranche. The logic: the bulk of your value — time, expertise, iteration — is delivered before the final handover. A 20% completion payment is still meaningful to the client as leverage, but limits your exposure if the final approval drags. For creative work where final sign-off involves subjective judgement and can become a negotiating point, a lighter completion payment is often the wiser call.
Retainer-based instalments
For ongoing relationships, monthly retainers are a form of instalment that work differently. Even with retainer clients, the standard discipline is to collect payment before the work period begins — a retainer paid on the first of the month covers work done during that month. This inverts the risk entirely: the client pays ahead of delivery, not after. If a new relationship is unwilling to accept this structure, that itself is diagnostic information worth noting.
What goes in the contract
A payment schedule is not a payment plan until it is in writing, signed by both parties, and referenced on every invoice. Defining deliverables — specifying what work will be delivered and when — reduces the grounds for dispute, and payment terms must always be documented in a signed contract.
Every instalment agreement should contain, at minimum:
1. Milestone definitions. Each tranche must be tied to a deliverable or a date — never to a subjective outcome like "client satisfaction." Write: "Milestone 2 payment of $4,800 / AUD 7,400 is due within 5 business days of the freelancer delivering the revised wireframe set." Not: "upon client approval." Approval without a deadline is an indefinite deferral in disguise.
2. Payment window. Net 30 is the corporate default, Net 15 is a reasonable ask, and due on receipt suits small one-off jobs. Smaller, milestone-triggered invoices warrant a tighter window. For creative and professional services, 7 to 14 days per milestone invoice is standard. A 14-day term is both common and practical — it shows whether your client is serious about paying promptly.
3. Late payment provisions. A late fee of 1.5% to 2% of the unpaid balance per month, stated in both the contract and on the invoice, is the widely recognised standard. State the exact rate, the trigger date, and how it compounds. Whatever you decide for your late fee, make sure the terms are clearly communicated from the beginning so clients are aware and more motivated to pay on time.
4. Work stoppage clause. Some freelancers include work stoppage provisions — if payment is 15 days late, work pauses until accounts are current. This is not punitive; it is operational. You cannot logically continue work on a project while the previous milestone remains unpaid. Writing this into the contract removes the awkward conversation — it becomes policy, not a personal grievance.
5. Intellectual property conditionality. Copyright and deliverables should transfer only when payment has been received in full. This means that at each milestone, the client receives a licence to use what has been delivered — but ownership of the full work transfers only at final payment. This is one of the most powerful and underused clauses in freelance contracting.
6. Governing law. Name the law and the courts in the contract. Nothing protects you by default across borders. This is especially important for cross-border projects where the client and freelancer are in different jurisdictions.
Negotiating the structure — how to frame it
Many freelancers accept whatever payment terms the client proposes because they feel uncomfortable negotiating. The reframe that changes this dynamic: milestone billing is not unusual or demanding. It is industry standard, and it benefits the client as much as the freelancer.
Milestone billing protects both parties: for the freelancer, it delivers steady cash flow and reduced non-payment risk, with a built-in pause mechanism; for the client, it provides visibility into progress, approval checkpoints, and lower risk of paying for unfinished work.
When a client pushes back against a deposit, the conversation usually needs two things: a rationale and a concrete number. Rationale: "Standard practice across the industry is to confirm projects with an upfront payment — it secures a place in my schedule and covers initial research and setup." Concrete number: $3,000 (AUD 4,600) on a $10,000 (AUD 15,400) project is 30%, which most clients find reasonable.
Requesting a deposit is especially important when working with new clients with no payment history. An upfront deposit of 25% to 50% of the project fee before work starts is standard. For a new client with no history, closer to 50% is appropriate.
If a client objects to milestones altogether and proposes payment only at the end, consider this a yellow flag for established clients and a red flag for new ones. Waiting until the end of a project to invoice is the single riskiest thing a freelancer can do. Your willingness to work to the end without interim payment signals that you absorb the risk entirely. A client who genuinely values the engagement should be willing to share it.
The real exposure: what the data says
In 2025, 58% of freelancers globally encountered non-payment or delayed payments, threatening their financial stability. This is not a fringe problem. According to the 2025 Contractor Management Report, 85% of freelancers have their invoices paid late at least some of the time, and more than one in five freelancers are paid late more than half the time — meaning late payment is their normal experience, not the exception.
Approximately 40% of freelancers report payment delays ranging from 30 to 60 days, while 18% encounter total non-payment, losing between $500 and $2,000 per project.
The mechanism of instalment billing changes this exposure. When you are owed a single large invoice at project end, non-payment is a catastrophic event. When you are owed a series of smaller invoices across milestones, non-payment on any single one triggers a pause before the debt grows larger. There is a subtler benefit most freelancers miss: clients who pay as they go are better clients. Each payment is a moment of active commitment — they are reviewing the work, approving a milestone, and making a conscious decision to continue.
One in three freelancers frequently chase late payments, while 23% include a billing schedule in their contractual agreement or bill their clients in instalments — a figure that suggests the majority of freelancers are still absorbing avoidable risk.
When a milestone payment is late
The instalment structure only holds if you enforce it. This is where many freelancers lose what the contract promised them.
- Day 1 past dueSend a short, professional note referencing the invoice number, the milestone description, and the due date. No apologies, no hedging. "Invoice [reference] for Milestone 2 was due on [date]. Please confirm payment status."
- Day 7 past dueSend the work stoppage notification if you have one in your contract. Phrase it as policy: "In line with our contract, work on Milestone 3 is paused pending receipt of the Milestone 2 payment. Once payment clears, we will resume immediately."
- Day 14 past dueIssue a formal overdue notice with the late fee calculation and a final payment deadline. Attach the contract clause. Keep the tone professional but unambiguous.
- Day 21 past dueEscalate. For corporate clients, contact the accounts payable team directly and copy the project manager. For smaller clients, a formal letter outlining the debt and consequences of continued non-payment — including your intent to pursue the matter — is the appropriate step. A formal demand letter outlining the debt and the consequences of non-payment serves as a final warning before sending the problem to a collection agency or considering legal action.
The most common reason freelancers fail to collect is that they delay these steps. Each day of delay without a concrete action normalises the late payment. Clients who are disorganised but willing to pay will be spurred to act by a firm communication on day one. Clients who are avoiding payment will not improve their behaviour if you wait.
How the settlement layer changes everything
Up to this point, this guide has been about structure and contract mechanics — the things that are true regardless of how payment is moved. Now consider the payment infrastructure itself.
For most freelancers, the settlement layer is an afterthought. You send an invoice, the client does a bank transfer or a card payment, and you wait. The problem is that traditional payment rails introduce their own delays and ambiguities on top of whatever the contract says. A wire transfer can sit in clearing for one to three business days. An international transfer may route through correspondent banks and add further lag. Some digital payment platforms apply holding periods before funds can be withdrawn, with additional processing time once withdrawals are initiated — understanding these timing factors helps you plan more effectively.
The result: even a client who pays on time may trigger an anxious wait. Did the transfer go through? Is it still in clearing? Has it actually landed? The confirmation comes through an email notification, or a bank statement, or a manual check of your balance. None of that is final. A payment that has "arrived" via a traditional bank transfer can, in certain circumstances, be reversed.
Onchain payment routing resolves this. When a milestone payment is sent onchain, settlement finality is the point at which a blockchain transaction becomes irreversible — after finality, the payment cannot be reorganised out of history, double-spent, or unwound. The money is there, permanently, with a transaction hash as the record. There is no clearinghouse that might claw it back. There is no three-day float. There is no ambiguity about whether it has settled.
This matters even more when a deal involves multiple parties — a freelancer, a co-contractor, a platform, a revenue-share arrangement. Under traditional rails, one incoming payment requires a human intermediary (or a slow, manual accounting process) to split and redistribute the funds. Each leg of that redistribution is its own transfer, its own delay, its own potential for error.
This is exactly what shaka.deal is built to solve. It is a B2B onchain payment router on Ethereum. A payer sends one transaction; shaka.deal routes it instantly to every party at preset shares in a single transaction, with finality. The routing is non-custodial — the protocol distributes, it never holds. Every party receives their share in the same block. No one waits for a manual redistribution. No one trusts an intermediary to execute the split correctly. The shares are set in advance, on-chain, and the settlement is simultaneous and final.
Consider a concrete scenario. A three-person creative team — a strategist, a designer, and a developer — works together on a $30,000 (AUD 46,200) brand and build project. The client has agreed to three milestone payments of $10,000 (AUD 15,400) each. Under a traditional arrangement, each milestone payment arrives in one account. That account holder manually splits and redistributes to the other two parties — creating lag, creating trust dependencies, and creating accounting complexity. If the account holder is slow, sick, or travelling, the other parties wait.
Under a shaka.deal routing setup, each $10,000 (AUD 15,400) milestone payment is a single inbound transaction. The preset split — say, 40/35/25 across the three parties — executes simultaneously, in the same transaction. For treasury teams and project teams alike, finality is the moment risk leaves the books and cash is truly cash. Each of the three parties receives their share in the same settlement event, with the same transaction hash as proof. No one owes anyone anything after the transaction confirms.
For a freelancer working alone on a milestone deal, the same principle applies in a simpler form: the milestone payment arrives, confirms onchain, and is final. There is nothing more to track. The invoice is settled.
Building the full workflow
The structure, contract, enforcement process, and payment layer all need to connect into a single workflow that you can operate efficiently across multiple clients. Here is how the complete picture looks in practice.
- Proposal stageDefine milestones as part of the scope document, not as an afterthought in the invoice. Each milestone should have a named deliverable, a trigger condition, a dollar value, and a payment window. Clients who receive a professional proposal with explicit milestones understand the structure before they sign.
- Contract stageTranslate the proposal milestones into binding contract language. Include the late fee, the work stoppage clause, the IP conditionality, and the payment method. Almost every number you will read on payment terms is convention, not law — the 50% deposit, the Net 30, the 1.5% monthly late fee are widely used because they work and because clients recognise them. The convention exists because it has been tested at scale.
- Milestone deliveryInvoice on the day you hit the milestone, not days or weeks later. Digital delivery ensures faster receipt, and the delivery date starts the countdown for your payment terms. Send the invoice with the deliverable attached, so both items arrive in the client's inbox simultaneously. This removes any ambiguity about when the milestone was triggered.
- SettlementUse a payment channel that gives you confirmation you can trust. For high-value milestones in particular, onchain settlement through a routing protocol like shaka.deal gives you finality — not an email notification, not a bank statement, but an immutable on-chain record that the payment has cleared and been distributed. The case for on-chain transactions in business payments comes down to verifiable settlement evidence, automated compliance signals from immutable records, and operational certainty.
- Post-paymentAcknowledge the receipt, confirm that the next milestone is scheduled, and move to the next phase. A clean acknowledgement keeps the relationship professional and sets the expectation for how subsequent milestones will be handled.
When instalments become renegotiation
There is a specific scenario worth naming: the client who agreed to milestones, misses a payment, and then tries to renegotiate the total fee as a condition of resuming. This is not a payment dispute. It is a scope and pricing renegotiation, and it should be handled as such.
Your contract already covers the milestone payment. Ignoring or overlooking payment terms has serious consequences — delayed payments can impact your ability to meet financial obligations, and ambiguous terms make it harder to enforce payment through legal channels.
The cleaner the original milestone structure — with deliverables tied to specific outputs, payment tied to specific triggers, and IP conditionality written in — the harder it is for a client to use a late payment as leverage.
A note on client relationships
None of this is adversarial. The contract, the milestones, the late fees, the work stoppage clause — all of it exists to make the engagement clearer, not more contentious. Structuring payment terms for a project can ensure you receive payment and help your client keep a vested interest in the project's success. It can also help keep your cash flow strong and benefit your client by breaking down the fee into smaller, manageable payments.
Most clients who ask to pay in instalments are not trying to defraud you. They are managing a budget, a cash flow, or an approval process. A well-structured instalment agreement gives them what they need — phased commitment, progress visibility, manageable payment sizes — while giving you what you need: certainty at each stage, leverage if things slow down, and a settlement layer that makes each payment genuinely final the moment it lands.
Milestone payments keep money moving in while the project is active — and that is the point. Not a favour to the client. Not a concession on your part. A professional structure that reflects the reality of how complex work gets done and paid for.
The instalment checklist
Before you sign a contract that includes instalment payments, confirm each of the following is in place:
- Deposit secured before any work begins. No exceptions for new clients.
- Each milestone tied to a defined deliverable, not a subjective approval. The trigger should be something you control — delivery of the draft, launch of the build, submission of the report.
- Payment window specified per milestone. 7 to 14 days is standard for professional services.
- Late fee rate and trigger date written into the contract and repeated on every invoice.
- Work stoppage clause referencing the specific number of days after which work pauses.
- IP conditionality clause reserving full ownership until final payment.
- Governing law and jurisdiction named explicitly.
- Payment method specified. If using onchain routing, include the routing address and confirm the settlement method in the contract. This removes any ambiguity at payment time.
- Communication protocol agreed. Who handles invoices on the client side? What is the escalation path if the primary contact is unavailable?
Each item on this list is a door that closes off a common failure mode. A client who has signed a contract with all of these elements in place has fewer legitimate reasons to delay, dispute, or renegotiate. And if they try, you have a document that says exactly what was agreed.
Instalment payments are not a risk to avoid — they are a structure to manage. The freelancers who handle them well are not those who negotiate harder or chase more aggressively. They are the ones who built the architecture before the project started: clear milestones, unambiguous triggers, enforceable terms, and a settlement layer that makes each payment conclusive the moment it arrives. That combination does not eliminate every dispute, but it does mean that when a milestone hits, the money moves, the record is permanent, and the next phase of the work can begin without doubt.
