Case library

Cross-border contract engineering.

Aligning a contract with payment, delivery, acceptance, liability, and performance across countries — before counterparties rely on conflicting language.

Each outline follows the same engineering sequence: Situation → Conflicting terms → Risk → Proposed amendment → Execution control. Scenarios below are illustrative teaching composites unless noted; no client names, savings, or closed outcomes are stated.

Illustrative · trade & carriage

01

FCA 2020 — goods with carrier, payment on arrival

  • Situation Seller ships under FCA; buyer’s bank pays only after goods reach the buyer’s site.
  • Conflicting terms Incoterms handover at carrier vs payment trigger tied to inland arrival.
  • Risk Title, loss, and cash timing diverge — disputes on when performance and payment obligations crystallise.
  • Proposed amendment Tie payment to documented handover (FCA point) or shift term/delivery model with explicit transfer-of-risk language.
  • Execution control Carrier receipts, inspection checkpoints, and invoice triggers mapped in a single delivery-and-payment matrix.

Illustrative · acceptance

02

Acceptance without a deadline delays payment

  • Situation Deliverables are live; the contract requires “acceptance” before the final instalment but sets no period or process.
  • Conflicting terms Open-ended acceptance vs fixed payment schedule and statutory reasonable-time expectations.
  • Risk Buyer silence stalls cash; seller continues warranty and support without a defined acceptance record.
  • Proposed amendment Deemed-acceptance after inspection window, objective acceptance criteria, and cure mechanics for defects.
  • Execution control Acceptance notices, test scripts, and payment release tied to dated sign-off or deemed-acceptance clock.

Illustrative · language versions

03

Diverging language versions on delivery and transfer

  • Situation Bilingual agreement; English and local-language clauses describe delivery place and transfer of risk differently.
  • Conflicting terms “Delivery to warehouse” in one language vs “arrival at port” in the other; governing-law clause silent on precedence.
  • Risk Enforcement and insurance follow the version each party prefers; payment milestones no longer match physical flow.
  • Proposed amendment Single controlling language, aligned Incoterms or DAP/DDP definitions, and explicit precedence rule.
  • Execution control Version register, aligned exhibits, and milestone checklist referencing one defined delivery point.

Illustrative · term & renewal

04

Auto-renewal and a missed notice deadline

  • Situation Multi-year services contract auto-renews unless either party gives 90 days’ notice; internal calendar misses the window.
  • Conflicting terms Strict notice formalities (registered mail only) vs operational e-mail practice; renewal fee uplift buried in a schedule.
  • Risk Unintended renewal term, higher fees, and exit negotiation under time pressure.
  • Proposed amendment Notice by acknowledged e-mail, rolling renewal caps, and uplift tied to documented index or fixed bands.
  • Execution control Renewal diary, delegated notice owner, and pre-renewal review gate in the legal workflow.

Illustrative · SaaS & DPA

05

SaaS/DPA — data duties and liability gaps

  • Situation EU customer procures US-hosted SaaS; main agreement caps liability while the DPA imposes processor duties and subprocessors in multiple regions.
  • Conflicting terms Broad limitation of liability vs uncapped data-protection indemnities; unclear breach-notification timelines.
  • Risk Operational teams cannot see which regime governs security incidents; payment and suspension rights fight the service-level story.
  • Proposed amendment Carve-outs for data breaches, aligned notice periods, subprocessors list with object-and-replace, and liability basket for privacy claims.
  • Execution control DPA register, incident runbook with contractual clocks, and periodic alignment between SLA credits and DPA remedies.