Fixed-date instalments vs milestone payments for B2B invoices

Use fixed-date instalments when the buyer and seller want to spread an agreed balance across known dates. Use milestone payments when the buyer pays in stages as agreed work is completed or accepted. In both cases, record what triggers each invoice or payment, the amount and the due date.
Create your free account

Key facts

Check what starts the clock. A fixed-date instalment follows the agreed calendar. An acceptance-based milestone follows the sign-off and then the agreed payment period. A calendar date in the project plan may be a forecast for sign-off.

Use fixed dates for a known balance

Fictional example. A supplier invoices USD 24,000 for equipment already delivered. Both parties agree to three USD 8,000 payments and accounts payable records these due dates against the invoice.

  • 15 April: USD 8,000 due. If received in full, USD 16,000 remains unpaid.
  • 15 May: USD 8,000 due. If received in full, USD 8,000 remains unpaid.
  • 15 June: USD 8,000 due. If received in full, the balance is zero.

If the buyer pays in April and misses the May instalment, USD 16,000 remains unpaid on 16 May. Under this example schedule, USD 8,000 is overdue and USD 8,000 is still due in June. Apply receipts to the correct instalment so the next statement shows both amounts.

Use milestones when sign-off triggers invoicing

In a separate fictional USD 24,000 implementation project, three stages are worth USD 8,000 each. The parties agree that the supplier invoices when the buyer signs off each stage. Payment is due 14 calendar days from the invoice date. The supplier issues each invoice on the day of acceptance.

  • Configuration: accepted and invoiced 1 April, due 15 April.
  • User testing: acceptance expected 1 May, accepted and invoiced 11 May, due 25 May.
  • Go-live handoff: accepted and invoiced 1 June, due 15 June.

The late user-testing sign-off moves the invoice and its due date by ten days. With April paid, on 16 May USD 8,000 has been invoiced and is due 25 May, and USD 8,000 is still tied to the June handoff. If a milestone slips, update the forecast, record who needs to sign off and confirm the date you can invoice. See the milestone payment terms guide for the details to agree before work starts.

Record the trigger, due date and balance for each payment

  1. Give every payment an amount and a trigger. For a fixed-date schedule, write out the dates. For a milestone schedule, name the deliverable, the evidence of completion and the person who can approve it.
  2. Show when each invoice goes out and how its due date is set. Share the same schedule with the buyer’s finance team and the people who approve the work.
  3. If you combine models, split the amounts explicitly. For example, a USD 6,000 mobilisation payment on an agreed date and three USD 6,000 milestone invoices add up to USD 24,000.
  4. Reconcile scheduled, invoiced, received and overdue amounts separately. A late approval goes to the project owner. An unpaid instalment past its due date goes to accounts payable.

For more on putting timing into writing, read contract payment terms examples or the payment terms guide. If an undisputed cross-border business invoice stays overdue, you can start a collection case with Debitura.

See business.gov.au’s guide to payment terms and CanadaBuys’ procurement examples of milestone and fixed-interval payments.