Freelance Payment Terms: A Worked Milestone Example

Turn a ₹30,000 project into named milestones

Imagine a freelancer and client agree to a ₹30,000 landing-page design project. For this arithmetic example, ₹30,000 is the complete agreed invoice amount; no tax rate or added fee is being assumed. They choose a 40% deposit followed by two 30% payments.

The calculation is ₹30,000 × 0.40 = ₹12,000 and ₹30,000 × 0.30 = ₹9,000 for each remaining milestone. After the deposit, the unpaid balance is ₹18,000; after the design payment, it is ₹9,000. The percentages are an illustration, not a rule for all freelance projects.

For a smaller job, one payment may be easier to administer. For a longer engagement, more milestones may better match delivery. Choose a schedule that both sides can understand and track, rather than copying a percentage without considering the work.

Editable payment-schedule wording

Project: [project name]
Agreed total: [currency and amount]

The payment schedule is:
1. [amount or percentage] due by [date/event] before the scheduled start.
2. [amount or percentage] due [payment window] after [defined milestone and approval method].
3. [amount or percentage] due [payment window] after [defined final milestone].

Invoices will be sent to [billing contact and email]. Payment can be made using [agreed method]. Please include the invoice number as the payment reference.

If either party expects a delay, they will contact [named person/channel] so the next steps and any revised dates can be agreed in writing.

Fill in every bracket. Replace “design approved” with a defined deliverable, such as a desktop and mobile design for one landing page, and say who can approve it. Set an actual payment window: “within [number] days of the milestone invoice” is clearer than “as soon as possible.” Make the final handoff event explicit too; do not assume both parties mean the same thing by “completion.”

The Australian Government's payment-terms guidance describes the value of specifying how and when payment is expected. These examples use that planning principle without importing jurisdiction-specific contract rules.

Keep scope changes separate from overdue payments

A payment reminder asks about an amount already agreed. A scope-change note asks the client to approve extra or different work. Combining them can make it unclear whether the client owes an existing balance or is being offered a new service.

Subject: Scope change for [project]

Hi [name],

The agreed scope covers [current deliverables]. The request for [new deliverable] adds [specific work].

I propose [additional amount] for that addition, with [effect on milestones or dates]. The existing project balance is [amount] and the proposed additional work is listed separately.

Please confirm whether you want to proceed with this change. I will schedule the additional work after we agree the updated scope, price and timing.

Thanks,
[your name]

Worked change: the ₹30,000 project gains a second design variation quoted at ₹3,000. If the client accepts, the revised total is ₹33,000. If ₹12,000 has already been paid, the remaining agreed amount becomes ₹21,000. Record how that extra ₹3,000 changes the remaining invoices; do not silently change the earlier 40/30/30 schedule or treat the proposal as accepted.

Use a short checklist before the next invoice

• Confirm which deliverable or event this invoice covers.
• Check the amount against the agreed schedule and accepted changes.
• Record payments and credits already applied.
• Name the billing contact, payment method and reference to use.
• Include the due date or agreed payment window.
• Check whether the client needs a purchase-order number or other billing detail.
• Record where the deliverables will be handed over and what the client must supply.

For example, “final files” might mean editable design files plus exported images, while the client expects implementation on a live website. Resolve that difference in the scope before attaching a payment milestone to it. Keep approvals in a place both parties can refer to.

A checklist helps you notice missing information; it does not replace the agreement. Do not assume you can withhold work, cancel a project or charge a late fee unless the applicable terms and rules support that step.

If an agreed payment becomes overdue

Check the invoice and payment record first. Then send a short reminder with the invoice number, remaining balance and a request for the expected payment date. Our overdue invoice letter templates include first reminders, follow-ups, partial-payment calculations and a letter format.

If the client disputes the work, address the specific issue and record the next step. If a payment date changes, confirm the revised date in writing rather than silently resetting your records. See business.gov.au's guidance on checking terms and contacting the customer for a general process; formal recovery options depend on the transaction.