A milestone payment tracker for a website project has one row for each of three payments: advance, middle and final. Each row shows the deliverable it is tied to, the amount, the invoice date, the due date, the date received and the balance. Tie every payment to something the client can see, so that "is this due yet?" has a clear answer.
How should the payments be split?
The split is a business choice you agree with the client in writing before work starts. A common pattern is a start payment, a payment at a midpoint and a payment on handover. Say a project costs ₹90,000 and you agree on 40 percent, 30 percent and 30 percent. The advance is ₹36,000, the middle payment is ₹27,000 and the final payment is ₹27,000, and 36,000 plus 27,000 plus 27,000 is ₹90,000.
What does the tracker look like?
This example is made up, with dates in the same month.
| Milestone | Tied to | Amount | Invoiced | Due | Received |
|---|---|---|---|---|---|
| Advance | Signed scope and start | ₹36,000 | 3 March | 3 March | 3 March |
| Middle | Design approved | ₹27,000 | 20 March | 27 March | 2 April |
| Final | Site live and handed over | ₹27,000 | Not yet | Not yet | Pending |
The middle payment came 6 days after the due date, from 27 March to 2 April. Received so far is ₹36,000 plus ₹27,000, which is ₹63,000. Balance is ₹90,000 minus ₹63,000, which is ₹27,000, and that is the final payment still to come.
What if the client wants to change the scope midway?
Treat it as a new line on the tracker. Add a row called Change request, with its own amount, deliverable and due date, and get it agreed in writing before you start. That keeps the original three payments clean and makes it obvious later what was extra, which is often where disputes begin.
What formulas do the work?
With the amount in C, the status in G and the received amount in H, try these:
- Total received: =SUM($H$2:$H$4)
- Balance: =SUM($C$2:$C$4)-SUM($H$2:$H$4)
- Days late for a payment: =IF(F2="","",F2-E2), where E is the due date and F is the received date. Blank means not received yet.
If you like, add a column called Overdue that shows Yes when today's date is past the due date and nothing has been received: =IF(AND(F2="",TODAY()>E2),"Yes","No").
What should each milestone be tied to?
Choose something that can be said yes or no to: signed scope, approved designs, a working staging site, content added, final handover. Avoid vague triggers such as "when 50 percent done", since two people will measure that differently. Write the triggers in the agreement, along with how many rounds of changes are included and what an extra round costs.
What if the client deducts something or adds taxes?
Record three amounts if they apply: the invoice amount, any amount the client deducted at payment, and the net amount you actually received. If you charge GST, keep that part in its own column. The rules and rates change and depend on your situation, so confirm how to handle them with your CA. The tracker's job is to show that the invoice amount, the deductions and the receipt all reconcile.
Matching the tracker to your bank
When a milestone is paid, find the credit in your statement and write the date and amount in the tracker. SpendixAI can import the statement, with rows reviewed before saving, so you can confirm the credit and label it as project income, and you can add receipts to transactions for expenses on the same job. The milestone tracker stays your record of what is due.
Before you start the next project
- Put the split, triggers and due dates in writing.
- Create the tracker rows on day one, with expected dates.
- Send each invoice on the day the milestone is met.
- Chase politely on the day after the due date, not three weeks later.
- Mark the project closed only when the balance is zero.
Useful ideas start with a clearer picture of your own spending.
Explore your reports

