Payment schedules · Contract reading guide
A milestone is not a payment due date
“Pay on completion” leaves several events compressed into one phrase. Separate the work trigger, evidence, invoice and payment clock to see which date your budget actually depends on.
Read the schedule alongside its referenced clauses
Four events, four different questions
Advance, if any
What triggers the initial amount: signature, an invoice or another event? Locate whether it is credited against later amounts. Do not add an advance again if it is already part of the total.
Milestone evidence
What work or deliverable must be recorded, and who confirms it? Separate delivery from acceptance or certification when the document treats them differently.
Invoice trigger
When may an invoice be issued, what must accompany it and where must it go? Completing work does not identify those details by itself.
Payment clock
Which event starts the period: issue, receipt or validation of an invoice? Find the number of days, calendar or working-day definition, and any separate treatment of disputed sums.
Fictional teaching example · Not a payment recommendation
One milestone can produce three dates
Assume invented wording says: invoice after written milestone approval; payment 10 calendar days after invoice issue. For this illustration, count the day after issue as day 1. The dates below are assumptions, not a legal deadline calculation.
- 6 Nov 2026
Milestone approved
The stipulated evidence is recorded. Under these invented terms, the supplier can now issue the invoice.
- 9 Nov 2026
Invoice issued
The invoice is issued three days later. This event starts the assumed clock; approval did not start it.
- 19 Nov 2026
Assumed due date
Ten calendar days after November 9. A receipt-based or working-day clause could produce a different date.
Reading check: writing “due November 16” by counting from the November 6 approval would use the wrong trigger in this example. If the actual contract does not identify the trigger, mark it as unresolved rather than inventing a date.
Primary-source case study · England & Wales model
Evidence and retention can sit between a milestone and cash
The UK Model Services Contract separates the Implementation Plan (Schedule 9), Testing Procedures (10), and Charges and Invoicing (11). In Schedule 11, Part B, milestone invoices require a Milestone Achievement Certificate; specified pricing mechanisms also require a Certificate of Costs with supporting documentation.
- Edition and period
- Version 2.2A · September 2025
- Specific model provision
- 10% milestone retention
- Percentage base
- Target Price for the target-cost mechanism; Charges for the other mechanisms named in Part B
A percentage needs its base and release event
Part B specifies the retention calculation and separately addresses its release. Do not read a retained amount as immediately payable just because a milestone has been reached.
Invented milestone Charges: £1,000
10% retained: £100
Remainder: £900
This isolates retention arithmetic using the model’s Charges-based case. It ignores any other adjustments and does not establish an invoice amount or due date for a real contract.
Make a payment record you can trace back
- Amount and reconciliation: note the currency, stated milestone amount, any advance already credited, retention, tax and other expressly stated adjustments separately. Mark missing amounts as unknown.
- Evidence and responsible recipient: write down the named certificate or approval, who supplies it, and the invoice destination. Keep the clause or schedule reference beside each entry.
- Clock and release: record the exact trigger and day definition. For retained money, find its own release condition; do not assume it shares the ordinary invoice date.
- Unresolved wording: ask “Which recorded event starts this clock?” or “Where is the release condition for this amount?” A date in a spreadsheet cannot fill a gap in the document.
Return to the MSA reading guide to locate the framework and schedules that contain these details. This page helps read existing wording; it does not supply replacement payment terms.
Sources and limits
A named model, not a universal payment rule
- Cabinet Office: Model Services Contract collection. Scope, intended users and value threshold. Consulted November 2, 2026.
- Model Services Contract schedules (England & Wales). Consolidated schedules v2.2A, September 2025: Schedule 9 (Implementation Plan), Schedule 10 (Testing Procedures), Schedule 11 (Charges and Invoicing), Part B, “Milestone Payments” and “Release of Milestone Retentions.” Consulted November 2, 2026.
- Official consolidated schedules, Word document. The percentage and certificate requirements above are model-contract provisions. Descriptions adapted from Cabinet Office / Government Legal Department material under the Open Government Licence v3.0.
TermsHuman explains common contract language and risk patterns for education only. It is not a law firm, does not provide legal advice, and cannot tell you whether to sign. For material obligations, ask qualified counsel in your jurisdiction.