Consider an order for 60,000 payable in three instalments of 20, 50 and 30 percent. The amounts are 12,000, 30,000 and 18,000. The useful part of the schedule is knowing exactly what makes each instalment due and whether the supporting event has already happened.
Identify the trigger for each amount
Read the agreement for precise wording. An order signature, dispatch notice and customer acceptance are three different events. Assign someone to capture each document and someone to release the corresponding invoice. Show billed-to-date and remaining value alongside the milestone so a resubmitted acceptance cannot trigger a second invoice.
Rework the schedule when the order changes
If a variation increases the contract value, document whether it changes an existing milestone or creates a new one. Keep payments received separate from amounts invoiced. A customer may still owe the first instalment when the second milestone becomes billable.
Use the milestone acceptance stage in Project360 to identify the delivery evidence behind a billing request.
More to discover in Numerish.
Explore related insights and practical enterprise workflows.



