A software vendor or SaaS provider watches a licence fee go unpaid while the customer keeps using the product. This page sets out how debt recovery for software and SaaS invoices actually proceeds: what evidence decides the claim, which defences a debtor raises, and when the balance is not worth pursuing.
Arrears in this sector rarely start as a single missed payment. A subscription renews automatically, the customer disputes a feature, and the invoice sits open for two billing cycles before anyone escalates it internally. Custom development work follows a different pattern: a milestone is delivered, the client raises a defect, and payment for that milestone stops entirely while later milestones remain unbilled.
Both patterns move from an internal collections note into a legal file once the counterparty sits in another country and stops answering email. At that point the claim becomes a matter of cross-border debt recovery, and the questions change from "when will they pay" to "what proves the debt and where can it be enforced".
A software or SaaS claim is decided on paper before it reaches any court. The order form or master services agreement fixes the price and the payment terms. The statement of work fixes what "delivered" means for a milestone. Acceptance emails, sign-off in a project tool, or the absence of a rejection within the agreed window all carry weight once a debtor disputes quality.
Usage logs are the item creditors most often forget to keep, and the one that most often decides the claim. A debtor who kept using the platform after the invoice date has a weak position on non-payment.
Four defences recur across this sector. The first is non-conformity: the product did not meet the acceptance criteria, so payment is withheld pending a fix. The second is deployment scope: the customer claims fewer users or a smaller environment than billed. The third is early termination: the customer says the contract ended before the disputed renewal. The fourth is set-off: the debtor holds a separate claim, often a security or data incident, against the same vendor.
A debtor rarely owes one vendor alone. The same finance team that stopped paying a SaaS invoice often runs the same delay against other technology suppliers, which changes how quickly assets move and how a claim ranks against other unsecured creditors.
The route starts with a formal demand that states the contract basis, the amount and a deadline, sent in a form the debtor cannot later claim not to have received. Where the debtor is silent or disputes without substance, the next step depends on what the contract says about jurisdiction and dispute resolution, and on where the debtor holds assets rather than where it is registered.
Before committing to litigation or arbitration, the practical question is whether the debtor can pay at all. A short check on the debtor's standing and known assets, delivered as an asset and solvency check, is usually the cheapest way to answer that before spending on proceedings.
Once assets are confirmed, the file either proceeds under the contract's own dispute clause or, absent one, follows the general route for IT services disputes in the debtor's jurisdiction. A limitation period always applies to the underlying claim, and it can be shorter for commercial contracts than the general civil period; we confirm the applicable period against the statute before advising, a point set out in more depth in our note on limitation periods in cross-border claims.
Yes, provided the contract and the usage records support the claim and the customer holds assets that can be reached. The assessment starts with those two questions before any proceedings are proposed.
A non-conformity defence is weighed against the acceptance record and continued use after the disputed date. Where the customer kept using the product without a documented rejection, the defence carries little weight.
Timing depends on the debtor's jurisdiction, whether the contract fixes a dispute forum, and whether the debtor contests the claim at all. We give a realistic estimate once the contract and the jurisdiction are known.
A licence fee left unpaid past one renewal cycle rarely gets easier to collect on the next one, and a contract with no clear dispute clause leaves the creditor guessing at the forum while the debtor keeps trading. The file gets harder, not easier, the longer the invoice sits open.