The shape of late payment in IT services
UK B2B IT vendors face late payment in three predictable patterns. First, subscription debt: the SaaS customer signs an annual or multi‑year contract, the implementation completes, and quarterly or annual subscription invoices begin to slip. Second, implementation debt: the project completes, the customer signs off, and the final invoice is held up by procurement or by a manufactured "we still have outstanding issues" objection. Third, expansion debt: a customer expands their seat count or module commitment, the contract addendum is signed, and the addendum invoice falls into the same arrears pattern as the parent invoice.
What unites all three patterns: the customer is solvent and the contract is clear. Late payment is a working‑capital decision by the customer, not a dispute about whether the debt is owed.
Why the contract is where the work is
IT contracts are typically more substantial than the average B2B trade contract. A SaaS master services agreement (MSA) of 30 to 80 pages is normal. Statements of work (SOWs) reference the MSA. Order forms reference both. The contractual stack is layered.
This works in the recovery practitioner's favour. A well‑drafted IT contract typically contains express provisions on payment terms, late payment interest (often higher than the statutory rate), suspension of services on non‑payment, the customer's obligation to pay all sums in dispute pending resolution, and the supplier's right to recover collection costs. The Late Payment Act applies on top, never instead.
At intake, we read the contract carefully before drafting Letter I. Most IT customers respond strongly when their own contract is cited back at them, particularly the suspension and termination clauses. The threat of service suspension is a faster motivator than the threat of court proceedings for many SaaS debtors.
Service credits and SLA disputes
The most common dispute lever in IT debt recovery is the service credit claim. The customer alleges that the supplier breached a service‑level agreement, that service credits are due under the SLA, and that the credits should be netted against the invoice. Where the SLA was genuinely breached and the credit calculation is correct, this is a legitimate set‑off and reduces the recoverable balance. Where the SLA breach is alleged but never raised through the contractual process (typically requiring written notice within a defined window), the set‑off claim is procedurally weak.
We assess SLA defences against the contract. Most SaaS contracts require service‑credit claims to be made within 30 days of the alleged breach, in writing, with reference to specific incident tickets. A claim raised for the first time after the invoice falls due is usually outside the contractual window and unenforceable.
The escalation that works for IT customers
IT debtors are typically not natural opponents of court proceedings. The threat that motivates them is reputational: a CCJ on the company's credit register, a winding‑up petition advertised in The Gazette, or a service suspension that affects their own customer base. Letter II often references the suspension clause expressly, alongside the procedural escalation under the Late Payment Act.
For SaaS customers in particular, suspension of service is sometimes commercially impossible (regulated workloads, mission‑critical systems). In those cases the contractual right to suspend remains a credible threat even where the supplier has no intention of exercising it. The negotiation moves to settlement quickly once both sides understand the position.
Implementation and professional services debt
Implementation engagements often produce the largest disputed invoices in IT services. The pattern: a fixed‑fee implementation project completes against agreed acceptance criteria, the customer signs off, the final invoice issues, the customer's procurement team raises a list of "remaining issues" that were not in the acceptance criteria.
The recovery practitioner's first reading: did the customer sign acceptance? If yes, the invoice is due regardless of subsequent commentary. The acceptance signature is a contractual fact. Manufactured post‑acceptance issues are not a defence to the invoice; they are a separate matter to be raised under the warranty or change‑control provisions of the contract.
This is the conversation that resolves most implementation debt within Letter II. The supplier has the signed acceptance form; the customer's procurement has raised a list of items that, on inspection, are not within the acceptance scope. The matter settles.
Renewal pressure as leverage
An overlooked recovery lever in SaaS is the renewal. A customer with an unpaid invoice approaching their renewal date usually wants to renew (the costs of switching SaaS providers are typically high). The supplier's ability to refuse to renew, or to require all arrears to be paid before renewing, is a strong commercial lever even before any procedural recovery is contemplated.
We coordinate the recovery sequence with the customer's renewal calendar where the supplier is willing. Letter I issues, the renewal conversation occurs in parallel, and the matter is typically resolved with the renewal payment carrying the arrears.
Our approach to IT debt recovery
Our intake form for IT matters asks for the contract (MSA, SOW, order form), the unpaid invoices, any acceptance documentation, any service credit or SLA correspondence, and the customer's status (solvent and operating, in administration, dissolved). We assess within twenty‑four working hours.
If we accept the matter, Letter I issues the same day. It cites the Late Payment Act, the contractual payment provisions, and any contractual rights to suspend or terminate that the supplier has chosen to invoke. Recovery costs are payable by the debtor under Regulation 5A.
Most IT debtors settle within Letter II once the contractual posture is fully laid out. Those that do not are referred to our panel solicitor for litigation, with the court fee and judgment costs added to the debtor's bill.
Common questions on IT debt
Can I suspend service to a non‑paying customer?
Almost always yes, if the contract permits it (most SaaS MSAs do). Suspension should be on written notice in accordance with the contract's notice provisions. We do not advise on the suspension itself; that is a contractual decision for the supplier. We do reference the supplier's right to suspend in the demand letter where it is in force.
What about service credit set‑offs?
Genuine set‑offs claimed within the contractual window with documentary evidence reduce the recoverable balance. Manufactured set‑offs raised after the invoice falls due rarely succeed.
Does the Late Payment Act apply to SaaS subscriptions?
Yes. SaaS is a service supplied between businesses; the Act applies in the normal way. Statutory compensation, statutory interest, and reasonable recovery costs are all recoverable from the debtor.
What if the customer is in another jurisdiction?
For UK‑registered companies the procedure is straightforward. Customers domiciled outside the UK fall under different rules; we assess these on a case‑by‑case basis and may decline matters where enforcement realistically requires foreign court proceedings.