Cross-Border Complications: Recovering Enterprise Tech Debt Across International Jurisdictions

A London-based SaaS company has a customer in Singapore that has not paid in six months. The contract is governed by English law. The debtor is a Singapore-incorporated entity. The guarantee was signed by a director based in Hong Kong. The amount is GBP 127,000. The finance team does not know whether to demand in pounds or Singapore dollars, whether to send a statutory demand or a letter before action, or whether a UK judgment can be enforced in Singapore without starting over in local court.

Cross-border software collections are one of the fastest-growing areas of tech debt, and they are also the area where a wrong first step can cost the entire recovery. Every jurisdiction has its own pre-action protocol, limitation period, and document-service requirement. A demand letter that is perfectly valid in England may be inadmissible in Australia or enforceable only after a local court order in Canada. The software company that expanded internationally faster than its back-office operations can manage is now sitting on trapped cash that no domestic collection process can reach.

The three friction points in international tech collections

• Governing law and jurisdiction clauses. Most international SaaS contracts specify a governing law and an exclusive jurisdiction. A contract governed by English law with exclusive jurisdiction in London is enforceable there, but the debtor is in Singapore. Collecting requires either the debtor's voluntary compliance or a local enforcement action in Singapore under the Reciprocal Enforcement of Commonwealth Judgments Act. Both paths are viable, but they take different time and cost structures.
• Multi-currency reconciliation. A debtor who paid in EUR but owes under a USD contract has not paid the right amount. Currency fluctuation between invoice and payment date creates a second dispute layer that a domestic collector never sees. The contract's currency clause determines what is owed, but the debtor's AP team will use whichever number benefits their side of the balance sheet.
• Statutory demand and insolvency thresholds. In the UK, a statutory demand can be served for debts over GBP 750. In Australia, the threshold is AUD 5,000. In Hong Kong, it is HKD 5,000. Each has a different waiting period and a different court route. Filing the wrong demand type wastes months.

Localized negotiation, not escalation

The best cross-border collection is the one that never reaches a courtroom. A multilingual collector who understands the debtor's local business culture and payment customs can resolve most international disputes at the demand stage. In the UK, a letter from a London-based collector with a clear demand and a 14-day deadline resolves roughly half the accounts we see. In Australia, the same demand with language referencing the Corporations Act has a similar effect. The difference is knowing which lever to pull and how to phrase it so the debtor understands the legal consequence, not just the commercial ask.

When collection does require local enforcement, the right structure is a network of vetted local counsel who work on a contingency basis. Filing fees are the only out-of-pocket cost. The same no-recovery-no-fee model that makes domestic collection risk-free applies internationally — as long as the collector has the jurisdictional coverage to manage it.

The takeaway

International software receivables are not a special case. They are the standard case for any software company that sells to enterprise customers outside its home market. The question is whether your collection partner has the jurisdictional reach, the contract literacy, and the local legal network to handle the recovery without losing the relationship or the leverage.