Saas Customer Refusing to Pay After a Platform Outage, Romania: What to Do

When a SaaS customer refuses to pay after a platform outage, Romanian vendors face a problem that is equal parts commercial, technical, and legal. At Olawru, I regularly advise technology companies through exactly this scenario, and the outcome almost always depends on what the vendor does in the first 48 hours, not the first 48 days. Romania’s Civil Code (Law No. 287/2009) provides a robust framework for contractual liability, force majeure defences, and debt recovery, but those statutory tools only work if evidence is preserved, the contract has been read properly, and the escalation path is proportionate.

This guide sets out the step-by-step playbook I walk clients through, from immediate incident response to court enforcement, so you can protect revenue without damaging the customer relationship beyond repair.

Immediate Steps to Take if a Customer Withholds Payment After a SaaS Outage

The first objective is simple: do not make the legal position worse. Whether you are the provider or the customer, the actions taken immediately after a SaaS outage in Romania will shape every conversation and proceeding that follows. Here is the checklist I give to clients on day one.

Who to Involve Internally

Assemble a cross-functional response team before you contact the customer or respond to a payment dispute. In my experience, the following roles are essential:

• Site Reliability Engineering (SRE) / DevOps. They own the technical timeline, root cause, duration, and scope of the outage. Their logs are your primary evidence.
• Billing / Finance. Confirm the outstanding invoices, payment terms, any automatic dunning that has already triggered, and whether credits have been applied.
• Legal / In-House Counsel. Review the contract before any external communication goes out. One poorly worded email can constitute an admission or waive a contractual right.
• CISO / DPO. If personal data was affected, even potentially, the clock starts on GDPR notification obligations to ANSPDCP (the Romanian Data Protection Authority).

Communication Template, What to Say (and What Not to Say)

Once the team is assembled, send a single, controlled communication to the customer. I recommend the following structure:

1. Acknowledge the incident. Confirm you are aware of the outage and provide the known duration and affected services.
2. State facts only. Do not speculate on root cause, admit liability, or promise specific remedies until your legal and technical review is complete.
3. Reference the contract. Direct the customer to the SLA and dispute-resolution clause: “We are reviewing the incident under the terms of our Service Level Agreement (Schedule [X]) and will revert within [contractual timeframe].”
4. Reserve rights. Include a brief reservation of rights: “Nothing in this communication constitutes a waiver of any rights or remedies available to [Provider] under the Agreement or applicable law.”
5. Propose a timeline. Commit to a date for the formal incident report and any applicable credit calculation.

Avoid two traps in particular. First, do not offer ad-hoc discounts or “goodwill” credits outside the contractual framework, these can be treated as precedent. Second, do not suspend the customer’s access in retaliation for withholding payment unless the contract explicitly grants a right to suspend for non-payment, and you have followed the notice procedure to the letter.

Contract Analysis, What Clauses Decide This Dispute?

Every SaaS payment dispute after an outage is ultimately a contract dispute. Before you draft a demand letter or accept a settlement, pull out the agreement and work through the following clauses systematically. In my practice, I have seen vendors lose recoverable amounts simply because they never checked what the contract actually said about service credits vs damages.

The Clause Checklist

• Outage definition. How does the contract define “downtime” or “unavailability”? Scheduled maintenance windows, force majeure events, and third-party failures are often excluded.
• SLA uptime commitment. Is there a percentage (e.g., 99.9%) and a measurement period (monthly, quarterly)? The measurement period matters, a 2-hour outage in a month may not breach a 99.9% monthly SLA.
• Service credits. What is the credit formula? Is it calculated as a percentage of monthly fees, or a flat amount? Critically, does the clause state that credits are the customer’s sole and exclusive remedy for downtime?
• Liability cap. Most B2B SaaS agreements cap total liability at 12 months’ fees or a fixed sum. Check whether the cap applies to the specific claim the customer is raising.
• Payment obligations during disputes. Many well-drafted contracts require the customer to continue paying undisputed amounts while the disputed portion is resolved. If yours does, the customer’s full non-payment may itself be a breach.
• Suspension and termination. Does the provider have a right to suspend for non-payment? What notice period applies? Does the customer have a right to terminate for material breach, and is a single outage sufficient?
• Dispute resolution. Arbitration, mediation, or Romanian courts? Mandatory pre-action steps (e.g., senior management escalation, mediation attempts) must be followed before proceedings can be filed.

Service Credits vs Damages, A Critical Distinction

The distinction between service credits vs damages is commercially decisive. If the contract makes credits the sole remedy, the customer’s refusal to pay the full invoice, rather than claiming credits, is likely itself a breach. If credits are non-exclusive, the customer may have a stronger position, but they still need to follow the contractual claims process.

Legal Doctrines: Breach, Force Majeure, Mitigation, and Good Faith

Romanian law offers both parties several legal tools. Understanding them allows you to assess, realistically, whether the customer’s refusal to pay is defensible or whether you are holding the stronger hand.

Force Majeure Under Romanian Law

The Romanian Civil Code defines force majeure as an external event that is unforeseeable, irresistible, and beyond the control of the party invoking it. To succeed with a force majeure defence in Romania, the party must demonstrate all three elements cumulatively. In my view, most SaaS outages fail this test, a server failure, a misconfigured deployment, or even a cloud provider’s regional outage is rarely “irresistible” in the legal sense if alternative infrastructure or disaster recovery was reasonably available.

However, there are genuine edge cases: a catastrophic cyberattack by a state actor, a complete loss of a cloud region due to a natural disaster, or a government-ordered internet shutdown could meet the threshold. The key evidence required includes:

• Externality. Proof that the cause originated outside the provider’s organisation and infrastructure decisions.
• Unforeseeability. Evidence that the event could not reasonably have been anticipated at the time the contract was signed.
• Irresistibility. Demonstration that no reasonable measure could have prevented or mitigated the impact.

If a customer invokes force majeure in Romania to justify withholding payment, scrutinise these elements rigorously. Equally, if you are the provider considering a force majeure defence, be aware that Romanian courts interpret the doctrine narrowly, and a failure to maintain adequate backups or redundancy will undermine your position.

Good Faith and Mitigation

The Romanian Civil Code imposes a general duty of good faith in the performance of contracts. Both parties are expected to mitigate their losses. A customer who experiences a short outage but refuses to pay three months of invoices may be acting disproportionately, and a provider who fails to restore service promptly or communicate transparently may equally be in breach of the good faith obligation. This principle of proportionality is something I regularly use in negotiations to bring unreasonable positions back to the centre.

How to Preserve Evidence After a SaaS Outage, Technical and Commercial Checklist

Evidence wins disputes. Whether you end up in negotiation, arbitration, or before a Romanian court, the quality of your evidentiary bundle will determine the outcome. The challenge with SaaS outages is that critical evidence is often ephemeral, log files rotate, dashboards refresh, and incident channels get archived. Here is the preservation checklist I recommend to technology clients.

A few practical points from what I have seen go wrong. First, instruct your engineering team to preserve evidence before they start fixing the problem, or at least in parallel. Log rotation policies can destroy critical data within hours. Second, mark any internal post-mortem report as “prepared at the direction of legal counsel” if your jurisdiction recognises legal privilege for such documents. Third, maintain a clear chain-of-custody record: who exported each file, when, and using what tool. Romanian courts expect documentary evidence to be authentic and unaltered, and a simple metadata record goes a long way toward establishing that.

Commercial Remedies and Negotiation Playbook

Not every SaaS customer refusing to pay after a platform outage needs to end up in court. In fact, in my experience, the vast majority of these disputes settle commercially, provided the vendor approaches the negotiation with a clear timeline and proportionate offers.

Escalation Timeline

• Days 0–7: Preserve evidence, complete the incident report, calculate any applicable service credits, and send the initial communication (see template above).
• Days 7–30: Engage in formal dunning. Propose a settlement: apply contractual credits, offer a modest goodwill gesture (extended support, waived fees for a future period), and request payment of undisputed amounts within 14 days.
• Days 30–90: Escalate to senior management on both sides. If the contract requires mediation as a pre-condition to litigation or arbitration, initiate it now. Document every step.
• Day 90+: If the customer has not paid and has not engaged constructively, prepare for formal dispute resolution, summary recovery for undisputed invoices, arbitration, or court proceedings.

When to Accept Partial Recovery vs Litigate

The decision to litigate should be commercial, not emotional. I advise clients to weigh three factors: (1) the amount in dispute relative to litigation costs, (2) the strength of the contractual position (sole remedy clause, liability cap, and payment-during-dispute obligations), and (3) the ongoing commercial value of the customer relationship. If the disputed amount is less than the cost of arbitration and the customer is otherwise valuable, a negotiated credit is often the rational outcome. If the customer is using the outage as a pretext to exit a contract they no longer want, enforcement may be the only option.

Dispute Resolution and Enforcement in Romania

When negotiation fails, Romanian law provides several practical enforcement paths. The right choice depends on the contract’s dispute-resolution clause, whether the debt is disputed, and whether the customer is domiciled in Romania or abroad.

For cross-border enforcement, common in SaaS disputes where the customer is in another EU member state, Romanian court judgments benefit from the Brussels I Regulation (Recast), which provides for recognition and enforcement across the EU without a separate exequatur procedure. If the customer is outside the EU and the contract provides for arbitration, enforcement of the award proceeds under the New York Convention. In either case, the quality of your evidentiary bundle and strict compliance with procedural requirements are critical. I recommend filing through the Romanian courts portal, which provides jurisdictional guidance and electronic filing options.

Drafting Checklist and Sample Clauses for SaaS Outage Disputes

Prevention is better than recovery. If you are drafting or renegotiating a SaaS agreement governed by Romanian law, consider the following clause structures to reduce the risk of a SaaS customer refusing to pay after a platform outage:

• Uptime definition. “Availability” means the percentage of time the Service is operational during a calendar month, excluding Scheduled Maintenance, force majeure events, and failures attributable to Customer’s systems or third-party services not under Provider’s reasonable control.
• Credit calculation and sole remedy. If Availability falls below [99.9%] in any calendar month, Customer shall be entitled to a service credit equal to [X%] of monthly fees for each [0.1%] shortfall. Such credits shall be Customer’s sole and exclusive remedy for any failure to meet the SLA., Note: Use “sole and exclusive remedy” language deliberately. If you intend credits to be non-exclusive, replace with “without prejudice to any other rights or remedies.”
• Undisputed payment during disputes. During any dispute under this Agreement, Customer shall continue to pay all undisputed amounts when due. Failure to pay undisputed amounts shall constitute a material breach entitling Provider to suspend the Service upon [14] days’ written notice.
• Liability cap with carveouts. Provider’s total aggregate liability shall not exceed [12 months’ fees]. This cap shall not apply to: (a) liability for wilful misconduct or gross negligence; (b) breach of confidentiality obligations; or (c) liability that cannot be limited under applicable law.

In my experience, the undisputed-payment clause is the single most valuable drafting tool for SaaS providers. It separates the payment obligation from the service-quality dispute and prevents a customer from using an outage as leverage to withhold payment across the board.

Conclusion

A SaaS customer refusing to pay after a platform outage in Romania is a high-stakes situation, but it is manageable if you act methodically. Preserve your evidence within the first 48 hours, read the contract before you communicate, calculate credits accurately, and escalate proportionately. Romanian law, particularly the Civil Code’s framework for contractual liability, force majeure, and good faith, provides effective tools for both vendors and customers, but those tools require clean evidence and disciplined execution. If you are facing a payment dispute after an outage and need Romania-specific legal guidance, I would encourage you to consult with a technology lawyer in Romania who understands both the contractual and technical dimensions of the problem.

Sources

1. Portal Legislativ, Law No. 287/2009 (Romanian Civil Code)
2. Portalul instanțelor de judecată (Romanian Courts Portal)
3. ANSPDCP, Romanian Data Protection Authority
4. EUR-Lex, Council Directive 93/13/EEC (Unfair Contract Terms)
5. EUR-Lex, Directive 2011/83/EU (Consumer Rights Directive)
6. Uniunea Națională a Barourilor din România (UNBR)