Three clauses that look alike
Consider three payment clauses. First: "Supplier shall submit its invoice within 5 days of delivery; Client shall pay within 30 days of a valid invoice." Second: "Client's obligation to pay is conditional upon Supplier submitting a compliant invoice within 5 days of delivery." Third: "Payment becomes due 30 days after Client receives the invoice, provided the invoice is submitted within 5 days of delivery."
They read similarly, but they allocate risk very differently. The first makes late invoicing a breach while the payment obligation survives - the supplier can still sue for the price. The second arguably stops the payment obligation arising at all if the invoice is late, leaving the supplier to a quantum meruit claim for the value supplied. The third sits in between, turning on how a court reads "provided".
Condition, procedure, or sequencing
The distinction is between three things: a true condition precedent, where no event means no obligation; a procedural requirement, a step you must take but whose breach does not extinguish the underlying entitlement; and a promise about sequencing, which simply orders performance. Contracts routinely blur them, and the blur is where the dispute lives.
Getting this right is the difference between a clean debt claim and a contested damages claim. Decide which you intend for each payment trigger, and draft it so the category is unmistakable.
How courts identify a true condition precedent
You do not need the words "condition precedent" for one to arise. In Disclosure and Barring Service v Tata Consultancy Services Ltd [2025] EWCA Civ 380, Coulson LJ framed the test as whether the words, in context, make it plain that there is a conditional effect: that unless one step is taken, you are not entitled to the relief at the next step.
The contract's if...then structure was decisive there: if the work failed and caused delay, then the customer could claim delay damages - but only if it had first issued a compliant report. It never did, and a proven claim of over GBP 1.6 million fell away. The structure of the clause, not its label, made the report a condition precedent. (For notice and report gateways to a remedy, see the companion guide on conditions precedent to a claim.)
Debt or damages: why the category bites
If a payment is subject to a true condition precedent and the condition is not met, the payment never becomes a debt. You are left claiming damages, which must be proved and are subject to mitigation and any liability cap. A procedural breach, by contrast, usually leaves the debt intact and sounds only in whatever loss the breach caused.
So the same late invoice can be trivial or fatal depending on which clause you wrote. That is why payment triggers deserve as much attention as the price itself.
Drafting payment triggers that mean what you intend
Say explicitly whether a step is a condition to payment or merely procedural. Where you want certainty of payment, avoid conditional wording around the invoice or milestone and keep the obligation to pay freestanding, with late steps handled as breach. Where you genuinely want payment gated, make the condition and its consequence clear.
In review, watch for small words that change the category - a "conditional upon", a "provided that", an "only if" attached to a payment - because they can quietly move you from a debt you can demand to a loss you must prove.
Use at the desk
Practical checklist
- Decide for each payment trigger whether it is a true condition precedent or a procedural step, and draft it so the category is clear.
- Remember: a true condition unmet means no debt; a procedural breach usually leaves the debt intact.
- Watch the words that create conditions - "conditional upon", "provided that", "only if" - around invoices, milestones, and payment.
- Where you want certainty of payment, keep the pay obligation freestanding and treat late steps as breach.
- Use the if...then test from DBS v TCS [2025] EWCA Civ 380 to spot conditions precedent without magic words.
- If a milestone can be blocked by the payer, address prevention expressly (see the deemed-fulfilment guide).
This guide is informational only and is not legal advice. It does not replace advice from licensed counsel on the facts of a specific transaction.
Product demo
Use the guide for context. Use Veqtor for the Word documents.
Watch Claude compare negotiation drafts and create a separate Word document with proposed tracked changes.
See Veqtor work with Word redlines