Recovering milestone payment across borders starts with matching the disputed instalment to the exact contract clause that triggered it. A creditor holding a signed milestone schedule and proof that the stage was completed has a workable claim. A creditor relying on an oral understanding of what "complete" meant usually does not. We establish which position applies before any recovery step begins.
What a milestone payment dispute usually looks like
Milestone structures appear across construction, engineering, software delivery and long-form service contracts. The payment schedule ties each instalment to a defined stage – a foundation poured, a module accepted, a phase of work signed off. The creditor completes the stage, invoices against it, and expects payment inside the period the contract sets. The debtor then either pays late, disputes that the milestone was reached, or deducts for an alleged defect.
Cross-border versions of this dispute add a second layer. The debtor may now be a foreign subsidiary, a joint-venture partner, or a buyer who has since restructured. The underlying claim survives the restructuring, but tracing which entity is currently liable, and where that entity's assets sit, becomes the first task before any demand is sent.
The profile that recovers well is narrow: a written schedule, a defined trigger for each stage, and a paper trail showing the trigger was met. Disputes without that paper trail move slowly and cost considerably more to prove than the sum at stake often justifies.
The documents that decide the claim
Before we quantify anything, we ask for the file that proves the milestone happened, not only the invoice that followed it.
- The contract clause setting out the milestone schedule and the trigger for each instalment
- An acceptance certificate, sign-off email, or equivalent written confirmation that the milestone was reached
- Delivery or handover records – shipping documents, commissioning reports, test results, site logs
- The invoice issued against the specific milestone, matched line by line to the contract
- Any written notice the debtor sent disputing completion or asserting a defect
- Correspondence in which the debtor's own conduct treats the milestone as met – onward use of the deliverable, resale, or a partial payment made against it
A claim built on this record is workable before we consider where the debtor's assets are located. A claim built on an oral understanding of completion is not, whatever the invoice itself states.
The defences debtors raise, and what defeats them
Four objections recur across sectors and borders.
- The milestone was not fully met. Defeated by an acceptance certificate, or by the debtor's own subsequent use of the deliverable as though it were complete.
- A defect entitles the debtor to withhold payment. Defeated where the contract sets a defect notice procedure the debtor did not follow, or where the deduction claimed is disproportionate to any defect actually demonstrated.
- Payment is conditional on a later milestone not yet due. Defeated by reading the payment clause against the delivery clause – the two are frequently drafted separately and do not always align in the debtor's favour.
- The claim is now time-barred. A limitation period applies in every jurisdiction, and for commercial claims it is often shorter than the general period; we confirm the applicable period against the statute before advising, rather than assume it from the invoice date.
How the recovery route runs in outline
The sequence follows the strength of the paper trail, not a fixed script.
- We verify the contract, the milestone trigger, and the completion evidence against everything the debtor has said in writing.
- We send a formal demand that identifies the specific milestone, the sum outstanding, and the documents supporting the position.
- We allow a negotiation window, because a debtor disputing a milestone on principle sometimes pays once the file is assembled properly.
- Where negotiation fails, the claim moves to the forum the contract names – litigation or arbitration – or, absent such a clause, to the court with jurisdiction over the debtor.
- Any resulting judgment or award is enforced against assets in the jurisdiction where they actually sit, which is not always the jurisdiction named in the contract.
When we are not the right firm
- The milestone was never formally accepted and no written record shows it was reached – this reads as a scope dispute, not a payment failure, and needs different advice.
- The disagreement is genuinely about quality or scope, not about whether payment is owed for work both sides agree was carried out.
- The sum outstanding does not justify the cost of cross-border litigation once the debtor's jurisdiction and asset position are known.
- The debtor holds no assets in any jurisdiction where a judgment could realistically be enforced.
Common questions
What proof do we need that a milestone was actually reached?
A written acceptance, sign-off, or handover record is the strongest proof. Where none exists, correspondence showing the debtor treated the deliverable as complete – using it, reselling it, or paying part of the invoice – can substitute. An invoice alone rarely settles the question on its own.
Can we still recover if the debtor claims a defect in the work?
Often, yes. A defect claim only defeats payment where the contract's defect procedure was followed and the deduction is proportionate to what was actually shown. Many defect claims raised after a demand letter do not meet either condition.
Is it worth pursuing a milestone payment dispute across borders if the sum is modest?
That depends on the debtor's asset position and the strength of the completion evidence, not on the invoice total alone. We assess both before advising on whether the route below is worth starting.
A milestone dispute left unresolved does not stay still. The debtor's balance sheet moves, other creditors file first, and the contract clause that once made the claim straightforward becomes one more document in a queue nobody is racing to read. The window in which the evidence is fresh and the debtor still holds reachable assets is the same window in which the route above still works.