Engineering subcontractors that finish their scope on a cross-border project often meet a main contractor or an end client who delays, disputes, or simply stops paying the final balance. Debt recovery for engineering subcontracting turns on the certificates, variations, and retention terms recorded during the works, not on the size of the invoice. We assess the file before any recovery step, and say plainly when a claim does not justify the cost of pursuing it.
The unpaid balance on an engineering subcontract is rarely one clean invoice. It is split across a final certificate, a retention released only after defects sign-off, and one or more variations that the main contractor never formally instructed in writing. Currency conversion between the subcontract and the head contract adds a further layer that a debtor can use to dispute the exact figure owed. We handle this profile alongside freight forwarding disputes and other cross-border trade claims, because the underlying problem – a solvent counterparty that has decided not to pay – is the same.
The debtor's own cash position often depends on whether the end client has paid the main contractor. A subcontractor pursuing the second tier down the chain is exposed to a payment default that happened one level above, not to any failure of its own work. That distinction matters when a defence is raised, because it points to who actually controls the money.
The subcontract agreement sets the payment mechanism, and it is the first document we read. Payment certificates, signed variation orders, and the correspondence around delay or completion follow closely behind, because a debtor will argue the sum owed differs from the sum claimed if any of these is missing or ambiguous. Site instructions given verbally and never confirmed in writing are the weakest part of most files we see.
Where the subcontract is silent on governing law, or names a law neither party understands well, the file is assessed under our wider cross-border debt recovery practice before any local step is taken. Proof of delivery, completion sign-off, and the retention release mechanism are checked against the actual dates in the contract, not against the dates either side now remembers.
A common belief among subcontractors is that a pay-when-paid clause removes the claim entirely once the main contractor says it has not been paid by the client. That is usually wrong. Most pay-when-paid clauses require proof that the upstream payment was genuinely withheld, not merely delayed, and a main contractor that cannot produce that proof loses the defence. We test the clause wording against the actual payment record before accepting or rejecting the debtor's position.
Set-off for alleged defects, liquidated damages for delay, and a claim that the variation was never formally instructed are the other defences we meet repeatedly. The pay-when-paid defence in particular is treated differently depending on the court that would hear the claim, a point covered in our note on unpaid invoice claims. None of these defences defeats a well-documented claim on their own; they simply set the terms of the argument.
The route starts with a formal demand that references the specific certificate, variation, or milestone in dispute, not a general statement of the balance owed. Before formal proceedings, we can commission a debtor asset report to confirm the counterparty still holds recoverable assets in the jurisdiction where enforcement would eventually run.
Where the demand does not produce payment, the file moves to admitted lawyers and licensed providers in the jurisdiction concerned, who take the claim through the local court or the contractual dispute mechanism named in the subcontract. We stay involved through that stage, coordinating the file and the evidence rather than stepping back once proceedings begin.
A valid claim rests on a certified sum, a signed variation, or a contractual milestone that has fallen due and been invoiced correctly. Informal instructions and unsigned variation requests weaken the claim even where the work was completed. We review the certificate trail and the subcontract wording before treating a sum as recoverable.
Yes in most contract structures, because a pay-when-paid clause typically requires proof that the upstream payment was not received, not merely that it was delayed. If the main contractor was paid and still withholds payment down the chain, the subcontractor has a stronger position, not a weaker one. We check the specific wording of the clause before advising on this point.
The timeline depends on whether the debtor disputes the certificate, where the debtor's assets sit, and which court would hear a contested claim. A file with a clean certificate and an undisputed variation moves faster than one where the debtor raises a defects counterclaim. We set out a route and a realistic sequence once the documents are reviewed, rather than a fixed period in advance.
Retention on most engineering subcontracts falls due on a fixed date, and once that date passes without a formal claim on file, the main contractor tends to treat the sum as settled. Other subcontractors on the same project are pursuing the same shrinking pool of funds, and the claim that reaches a local court or arbitration mechanism first is usually the one that recovers something. A subcontractor waiting for the final account to be agreed before taking advice is often waiting behind a queue it cannot see.