How to Create Milestones in an ERP: Stages That Are Gated, Signed Off and Billed Once
For project managers, contractors and agencies paid by stage: set up milestones that know their order, wait for the client's approval and turn into an invoice on completion.
Anyone asking how to create milestones is usually holding a contract with a payment schedule: advance, design approval, delivery, handover. Each line is a stage of work and a sum of money, and each one has to be tracked from the day the project starts.
In many Indian SMEs those stages live in the proposal PDF. The team finishes a stage, nobody tells accounts, the client's approval is a WhatsApp thumbs up, and the invoice goes out at month end, if it goes out at all.
This guide sets out what a well-formed milestone holds, the steps to create one in any ERP, an illustrative example from a Kochi software agency, and how Apragya's Project Management app handles gating, sign-off and billing.
How to create milestones, step by step
A milestone is a checkpoint in a project that marks the end of a meaningful stage: a design approved, a structure completed, a module accepted. Unlike a task, it has no effort of its own. It records that a set of work is finished and, often, that money is now due.
A usable milestone needs a clear name, a due date, the tasks that lead to it, any earlier milestones it depends on, who must approve it and, for payment stages, the amount to bill. Leave out the dependencies and stages get closed out of order; leave out the approver and completion becomes an argument.
Keep milestones few. Four to eight per project is typical for Indian contract work, and each should match a line in the client's payment schedule or a real decision point.
- Open the project and list the stages from the contract or plan.
- Create a milestone for each stage with a name, description and due date.
- Mark the earlier milestones each one depends on.
- Enter the billing amount for stages that release a payment.
- Switch on sign-off where the client or a manager must approve.
- Link the tasks that lead to each milestone and review status weekly.
An example: a Kochi software agency's four-stage build
Take an illustrative 30-person agency building an ordering portal for a seafood exporter. The contract pays in four parts: discovery, design, build and go-live. The client's operations head must approve each stage before the next begins.
The design milestone, from set-up to invoice
Created with amount
Due date, description and the sum to bill.
Gated on discovery
Cannot complete while discovery is open.
Work finished
Linked tasks closed by the team.
Client approves
Approve or reject, with notes and date.
Invoice raised
One sales invoice, recorded on the milestone.
The client rejected the first design round with two notes, so the milestone stayed open. The revised screens were approved on a Thursday, and the design invoice was raised that afternoon. When the build stage was later marked done early by mistake, the gate held it, because design sign-off had to come first.
What loosely tracked milestones cost
Late invoices
Finished stages are billed weeks later, and cash waits.
Disputed stages
The client says a stage was never accepted.
Work out of order
Build starts before the design stage is approved.
Billed twice
Two sheets, two invoices for the same stage.
How the project milestone tracker works in Apragya
Step 1 of 5
Define
Name, description and due date on the project.
- Define: Name, description and due date on the project.
- Gate: List the earlier milestones that must be complete first.
- Track: Status runs pending, in progress, completed or missed.
- Sign off: Where switched on, completion waits for an approver.
- Bill: A milestone with an amount raises a sales invoice on completion, once.
Milestone billing: proposal PDF or ERP record
A calendar reminder tells you a date has arrived. It does not know whether the earlier stage was approved, whether the client signed, or whether the stage was already invoiced. A milestone record holds all of that, so billing follows the work instead of someone's memory.
Milestones in a proposal, compared with Apragya
| Feature | Proposal and email | Apragya milestones |
|---|---|---|
| Stage order | Trusted to the team | Earlier milestones must be complete |
| Client approval | An email or chat reply | Approve or reject, with notes and date |
| Invoice | Raised when someone notices | Raised when the stage completes |
| Billing twice | Possible | Blocked once an invoice is recorded |
| Late stages | Found at review | Status shows missed |
Checked against public information on 16 September 2026.
What sets Apragya apart for payment milestones in projects
Straight to sales
Milestone invoices land in the same books as other sales.
Linked risks
Risks tied to a milestone show against it.
Stage budgets
A budget head can be allocated to one milestone.
Client portal
Clients can follow progress when the portal is on.
Delay warnings
An agent can flag stages close to their date with open work.
One record
Tasks, milestones and invoices share the project.
Read more on the milestones feature and how stages roll into project financials. Milestones sit inside projects, and repeatable stages belong in project templates.
Getting started
- Take the payment schedule from one live contract.
- Create each stage as a milestone with its due date and amount.
- Set which stages depend on earlier ones.
- Switch on sign-off for the stages the client must approve.
- Link the project to the customer you bill.
The first month usually brings at least one invoice forward by a couple of weeks.
What it costs to start
Creating milestones, answered
What if the client rejects a stage?
Can a milestone be completed before the one it depends on?
Do all milestones need an amount?
Can a stage be invoiced twice?
What does it cost to start?
Bill each stage the day it is approved
Turn one contract's payment schedule into milestones and follow them through.