Milestone Payment Schedules: Turn "Every 30 Days From Kickoff" Into Actual Dates Before You Sign

Most milestone payment clauses are written as arithmetic, not as dates: "four equal instalments at thirty-day intervals from project kickoff." Everyone signs, everyone nods, and nobody actually knows when the money moves. Then milestone two lands on a Saturday, the client's accounts-payable run doesn't happen on weekends, the payment slips to the following Tuesday, and the contractor is chasing a "late" payment that the client's system considers perfectly on time. The clause was never wrong — it was just never turned into a calendar.

Intervals are calendar days; payments happen on business days

The interval in a milestone clause is almost always counted in calendar days — thirty days means thirty days, weekends included, exactly like Net 30 invoice terms. That part is easy. The friction appears at the endpoint: banks don't settle on weekends, accounts-payable teams don't cut payments on public holidays, and approval workflows sit idle from Friday evening to Monday morning. So while the interval is calendar math, each resulting payment date only works if it lands on a working day. A schedule that ignores this is guaranteed to drift — and drift compounds, because a payment that slips past a weekend often misses that week's payment run entirely and waits for the next one.

When a date lands on a weekend, move it earlier — not later

This is the decision most people get backwards. The instinct is to roll a Saturday payment forward to Monday, the way delivery deadlines roll forward. But payment obligations point the other way: if the contract says the client pays by day 60 and day 60 is a Saturday, paying on Monday is paying late. The defensible convention is to roll backward to the last working day before the scheduled date — the payment arrives on or before the contractual day, never after. The Milestone Payment Schedule calculator applies exactly this rule: each milestone date that collides with a weekend or holiday moves to the previous working day, so the projected schedule is one the paying side can actually honor without breaching the interval.

For the contractor, backward rolling is also the conservative planning assumption: your cash-flow forecast should use the earliest defensible date the client could pay, not an optimistic Monday that quietly becomes Thursday. If the schedule works when payments arrive a day or two early, it also works when they arrive on the nominal date.

Equal splits, and what the percentages are telling you

A four-milestone schedule at equal weights means each payment releases 25% of the contract value, and the schedule's real story is the cumulative line: 25% after milestone one, 50% at the halfway point, 100% at the end. Projecting that cumulative percentage against the calendar is how you spot structural problems before signing. If 50% of your revenue arrives more than two months after kickoff but your subcontractors bill you monthly, the contract is quietly asking you to finance the project. That's sometimes acceptable — but it should be a decision, not a surprise discovered in week seven. Many negotiations that look like fights about price are really fights about this curve: pulling one payment earlier can matter more than a few points on the total.

Cross-border projects need the right holiday calendar

Weekend collisions are predictable; holiday collisions are where schedules break silently. A US contractor invoicing a German client will hit holidays that exist in neither party's head at signing time — and it's the payer's holiday calendar that governs when money can actually move. When you project a schedule, use the holiday calendar of the country where the paying entity (and its bank) operates, and if the project spans a year-end, look hard at the late-December dates: a milestone scheduled between Christmas and New Year is a milestone that will be paid in January, whatever the contract says.

Write the dates into the contract, not just the formula

The cleanest fix costs nothing: once both sides agree the interval and the kickoff date, generate the concrete schedule and attach it to the contract as a payment table — dates, amounts, cumulative percentages. Formulas invite interpretation; a table of dates doesn't. It also surfaces the weekend and holiday collisions while everyone is still friendly, instead of at the moment money is late.

The Milestone Payment Schedule calculator does the projection in one pass: give it the kickoff date, the number of milestones, and the interval, pick the workweek and holiday country that govern the paying side, and it returns every payment date — each already rolled back off weekends and holidays — with the cumulative percentage released at each step. Run it before you sign, attach the output, and the "when do we actually get paid" conversation is over before it starts.