Chinese Customer Stops Paying SaaS Fees: When Can an Overseas Provider Suspend Service?

The direct answer: may the provider suspend the account?

Possibly, but not automatically. This guide concerns an overseas provider supplying remote SaaS, cloud accounts, seat subscriptions or software licences to a mainland Chinese business, assuming the relevant PRC rules apply. Governing law, forum, export controls, cyber and data duties, payment arrangements and any sector-specific continuity rules require separate checking. A customer in China does not make PRC law the answer to every issue.

A defensible sequence is to prove the contract and authorised scope; prove the current term, renewal or metered use, supplied access and maturity of each charge; and only then assess whether the suspension clause or a statutory defence supports a restriction, with any cure, notice and restoration mechanism. Permanent termination requires a separate basis, effective notice and post-termination settlement. Temporary suspension, termination and data deletion should never be collapsed into one undefined step.

1. Use five record groups to test whether fees matured

An invoice or dashboard screenshot does not prove the entire claim. Put each billing period on one schedule and state what every record establishes.

• Contract and authority: master agreement, order form, applicable online-terms version, signature or click-accept record, purchase order, and the authority or ratification of the Chinese customer's user.
• Term and renewal: initial term, auto-renewal mechanism, cancellation window, renewal notice, price-change notice, continuing login or ordering, and when the relevant terms became binding.
• Access and use: provisioning, administrators and seats, login or API activity, enabled functions, support tickets, service status, and native requests for configuration or expansion.
• Billing and maturity: rules for fixed subscription, seats, storage, API or overage, billing period, currency, tax, invoice or tax-document conditions, credits and receipts.
• Default and exit: demands, dispute grounds, grace or cure period, suspension notice, restoration condition, export requests, retention and deletion plan, and post-termination settlement.

2. What continued use proves—and what it does not

Continued logins, API calls, added seats, support tickets or implementation requests can show that the customer retained access and commercial benefit, weakening a claim that nothing was supplied. Preserve the origin, field definitions, time zone, account mapping, generation method and full export. A cropped dashboard total is a weak substitute.

Usage does not prove every amount. Each charge must still connect to incorporated pricing, a valid renewal or change, a reliable metering method and the agreed payment trigger. Where click-acceptance, auto-renewal, unilateral price changes or liability limits are standard terms, PRC Civil Code Articles 496–498 raise incorporation, notice, fairness and interpretation questions. Posting a term on a webpage does not invariably make it binding.

Civil Code Article 512 provides a delivery-time rule for some electronic contracts concluded through information networks. Whether a particular SaaS falls within it and when delivery occurred remain contract- and fact-specific. Remote access records may prove performance; they do not prove acceptance of every additional feature, seat or overage.

View China commercial contract dispute services →

3. Keep three possible suspension grounds separate

First, the contract may expressly permit suspension. Verify the defined overdue amount, grace period, treatment of disputed sums, notice route, scope and restoration condition, and confirm that the clause was incorporated and is not displaced by mandatory rules. Even then, restricting every group account, critical data or an undisputed service may require a proportionality and good-faith assessment.

Second, Civil Code Article 526 can allow a party due to perform later to refuse corresponding performance where the other party was due first but failed to perform as agreed. A next-period prepayment model may create a clear sequence. It does not necessarily justify restricting a current prepaid term or services unrelated to the disputed charge.

Third, the insecurity defence in Articles 527–528 applies where the provider must perform first and has definite evidence of a specified serious threat to the customer's performance ability. Timely notice is required, and performance should resume if adequate security is provided. A single late invoice or a general concern does not automatically meet that test.

4. Suspension, termination and data deletion are different acts

Suspension usually limits future access while preserving a route to restoration. Termination ends unperformed contractual duties and moves the parties into settlement and winding-up. Export, retention, return or deletion of data is governed by the contract and applicable data, privacy, confidentiality and record-retention obligations. The notice should state the basis, timing, scope and reversibility of each act.

Civil Code Articles 562–566 require a contractual or statutory termination basis and an effective notice process; settlement and winding-up clauses may survive. A specific, good-faith billing dispute should prompt separate treatment of undisputed sums, disputed sums, temporary access and evidence. Customer data should not be deleted merely as collection leverage.

Abrupt restriction may magnify foreseeable loss for healthcare, finance, core operations or shared accounts. Consider graduated limits, a read-only period, an administrator export window or emergency access where the contract and risk require it. Create a service-state snapshot before any action so the provider can later show what was restricted, when and why.

5. Is non-payment also software copyright infringement?

Not necessarily. A software licence should identify the software, territory, term, devices, users, purpose and exclusivity. Articles 18–19 of the Regulations on Computers Software Protection distinguish licensed rights and require a written agreement for an exclusive licence. Installation, copying, modification or use outside an actual licence may raise a copyright issue distinct from the fee claim.

Continued remote SaaS access should not be labelled software copying or infringement solely because an invoice is unpaid. SPC Guiding Case 279 concerned actual installation, evidence preservation and source-code comparison, illustrating the technical specificity of an infringement case. Copyright depends on the controlled act, licence scope and proof; an ordinary subscription debt should first be organised as a contract claim.

6. Amounts, the remaining term and likely defences

Civil Code Article 579 can support a claim for matured monetary debt. Damages and liquidated damages remain subject to Articles 584–585 on foreseeability, calculation and adjustment. Ending a fixed-term continuing contract does not automatically make every remaining month a matured debt. Article 61 of the SPC Contract Book interpretation considers a reasonable substitute-transaction period, the remaining term, investment and avoidable costs when measuring lost performance benefit.

Expected defences include lack of authority, ineffective incorporation or renewal, timely cancellation, unagreed price or overage, logs mapped to the wrong account, persistent service-level failures, security or data incidents, set-off, unmet tax-document conditions, and loss caused by the suspension itself. Tie each issue to a billing period, term, log and amount. Neither side should turn one outage into a defence to all historical charges or every future charge into an immediately due debt.

7. Limitation, notice and recovery path

An ordinary PRC-law contract claim commonly has a three-year limitation period running from knowledge or deemed knowledge of the injury and obligor. Instalments, a performance demand, acknowledgment, court proceedings or arbitration may affect accrual or interruption. Civil Code Article 594's four-year period is confined to international sales and technology import/export contracts; it does not apply merely because the provider is overseas or the product is software.

A demand and suspension notice should identify the parties, account, billing period, maturity clause, net debt, particular dispute, current service status, proposed action, cure period and restoration condition, and follow the agreed delivery route. A negotiated solution can combine partial payment, temporary read-only access, security, data export, instalments, restoration and defined default consequences. A promise to pay is not cash received.

Seek prompt advice before acting if the customer is exporting large datasets, removing administrators, shifting use to an affiliate, facing a critical-service interruption, approaching a retention deadline, or nearing a possible limitation date. For an initial assessment, provide the five-record schedule, amount table, suspension clause, latest notices and the intended commercial outcome. These steps do not create a legal grace period.