How to Invoice a Project in Milestones (India, 2026)

If you're running a big project and waiting until the end to send one invoice, you're carrying all the risk yourself. Milestone billing fixes that. It splits a project into stages, and you invoice at the end of each stage instead of once at the finish. For a ₹1,20,000 website build, that might mean three payments of ₹40,000 instead of one nervous wait. This guide covers what milestone billing is, how to split a project, what each milestone invoice must include, how GST and advances fit, and a format you can copy.

The quick answer

Milestone billing is a way to charge for a project in parts, where each part is tied to a clear stage of the work. You agree the stages and amounts with the client before you start, then send a separate invoice as each stage is done and approved. Most freelancers use two to four milestones: an advance to begin, one or two payments at key checkpoints, and a final payment on delivery. Each milestone invoice is a normal invoice with one extra line that names the stage, for example "Milestone 2 of 3: Design sign-off."

Why milestone billing protects you

A single invoice at the end of a long project means you fund the whole thing out of your own pocket until the client pays. If the client goes quiet at week six of an eight-week build, you've done almost all the work and collected nothing.

Milestones move money in step with effort. You have proof the client is committed, because they paid the advance. You have cash landing through the project, not after it. And if a client stops responding, you stop at the current milestone having already been paid for the completed stages. The risk is shared instead of sitting entirely on you.

There's a softer benefit too. A client who has paid for stage one is far more likely to give timely feedback on stage two, because they have money in the project. Milestone billing keeps everyone moving without anyone having to chase.

How to split a project into milestones

Split by outcome, not by calendar. A milestone should map to something the client can look at and approve, not to "two weeks passed." Tie each payment to a deliverable so there's no argument about whether the stage is done.

Here's a common three-milestone split for a ₹90,000 brand identity project:

1. Advance to start (30 percent, ₹27,000). Booked before any work begins. This is your commitment fee.
2. Concept sign-off (40 percent, ₹36,000). Paid when the client approves the main direction.
3. Final delivery (30 percent, ₹27,000). Paid on handover of final files.

For smaller jobs, two milestones are enough: 50 percent advance and 50 percent on delivery. For long builds over ₹2,00,000, four milestones keep the gaps between payments short. The rule of thumb: no single stage should leave more than three to four weeks of your unpaid time exposed.

Write the split into your proposal or contract before the project starts. Milestone billing only works if the client agreed to the stages in advance. Retro-fitting stages onto a project halfway through feels like moving the goalposts.

What each milestone invoice must include

A milestone invoice is a standard freelance invoice plus a clear label for the stage. It should carry:

• Your name or business name, address, and contact
• The client's name and billing details
• A unique, sequential invoice number
• Invoice date and a due date (or payment terms like Net 15)
• A line naming the milestone: "Milestone 2 of 3: Design sign-off"
• The amount for that stage, and the total project value for context
• Your GST number, if you have one
• Payment details: UPI ID or link, bank account, IFSC

The two details freelancers forget are the milestone label and the running total. Naming the stage stops the "which payment is this?" message. Showing the project total, and what remains, keeps the client oriented. If you skip sequential numbering across milestones, read Freelance Invoice Numbering: A System That Doesn't Break before you send the next one.

A milestone invoice you can copy

Notice the invoice bills for one stage but shows the full picture. The client sees what they paid, what they owe now, and what's left. That clarity is worth more than any design flourish.

How GST and advances fit milestone billing

If you aren't registered for GST, which most freelancers under the ₹20,00,000 turnover threshold aren't, milestone billing changes nothing about your tax position. You invoice each stage as a normal amount and add your GST number only if you have one.

If you're registered, there's one thing to know. Under GST, the tax point for services is the earliest of the invoice date, the payment date, or the completion of service. That means when you take an advance for milestone one, GST is generally due on that advance in the period you receive it, even though the work isn't finished. Charge GST on each milestone invoice as you raise it, rather than saving it all for the final bill. If your project is large enough that this matters, confirm the exact treatment with your CA.

Advances and milestones are close cousins. An advance is simply your first milestone. If you want the full picture on booking money before you start, and where it sits against a quote, the Proforma Invoice vs Tax Invoice guide explains when to send a proforma for the advance and a tax invoice once the stage is delivered.

Payment terms across milestones

Keep the terms identical on every milestone invoice so the client is never guessing. If milestone one is Net 15, make all of them Net 15. Consistency here does more for your cash flow than a shorter term you have to fight for each time.

Two rules worth writing into the agreement. First, work on the next stage starts only after the current milestone is paid. This is fair, and it stops you funding stage three while stage two is still unpaid. Second, the final files or handover happen after the final milestone clears, not before. For the full breakdown of Net 15 versus Net 30, advances, and the MSME rule, see Freelance Invoice Payment Terms in India.

Common milestone billing mistakes

• Splitting by time, not deliverables. "Payment every two weeks" invites disputes. Tie money to approvals.
• No advance. Starting a large project on trust alone means you carry all the risk. The advance is the client's commitment.
• Vague stage names. "Part 2" tells the client nothing. "Milestone 2 of 3: Design sign-off" tells them exactly what they're paying for.
• Different terms each time. Changing Net 15 to Net 30 midway confuses the client and slows you down.
• Handing over final files before the final milestone clears. Once the work is delivered, you've nothing left to hold.

FAQ

Milestone billing is one of those habits that decides whether you spend a project chasing or building. Once the stages are agreed, the only work left is sending a clean invoice at each checkpoint. With Riffit, that is a few answers on WhatsApp and the invoice goes out with your branding and a UPI link. Describing the stage in plain language, and sending it on to the client over WhatsApp, are Pro features. Either way the admin never becomes the reason a milestone slips.