SaaS Subscription Debt Collection from US Companies

A European, Israeli, or APAC SaaS vendor chasing an unpaid USD 180,000 Master Service Agreement from a Delaware-incorporated buyer does not need a US office. It needs the right clause stack, a correct reading of Bankruptcy Code § 365, and a licensed collection partner inside the debtor's state. The MSA governs the claim. The Federal Arbitration Act and the New York Convention carry the award home.

How do you collect unpaid SaaS subscription fees from US companies?

A foreign SaaS vendor collects from a US buyer by issuing a demand letter through a US-licensed collection agency or counsel, invoking the arbitration clause in the MSA under AAA Commercial Rules, or filing suit in state or federal court if no arbitration clause exists. Where the debtor is in bankruptcy, the vendor files a proof of claim under 11 U.S.C. § 501.

The first move is rarely litigation. It is a dated written demand on the creditor's letterhead or a US agency's letterhead, citing the specific invoice numbers, the MSA section on late fees, and the governing-law clause. Most B2B SaaS disputes settle at this stage because the buyer's counsel reads the clause stack and realises the path forward is expensive.

If the buyer refuses, the MSA's dispute resolution clause dictates the next step. An arbitration clause is the cleanest outcome for a foreign vendor. An AAA commercial arbitration seated in Delaware or New York can be administered remotely, produces an award enforceable in the debtor's home state under the Federal Arbitration Act, and carries globally under the New York Convention if the vendor ever needs to pursue US assets held abroad.

The subscription-versus-license distinction

A SaaS subscription is a contract for continuing access to software delivered as a service. US courts have, on balance, declined to treat pure SaaS as a sale of goods under UCC Article 2, because nothing tangible changes hands and the vendor retains the code. That matters for collection. It means the vendor cannot rely on Article 2's gap-filling rules on delivery, acceptance, or revocation. The MSA is the entire contract universe.

A perpetual on-premises licence with a maintenance tail is different. Courts have sometimes applied Article 2 by analogy where the software is delivered to the customer's own hardware. For pure cloud SaaS, the dominant view treats it as a service, and the governing law clause in the MSA decides the rest.

Collection routes for a foreign SaaS vendor: decision matrix

Does UCC Article 2 apply to SaaS contracts?

The leading authority treats pure cloud SaaS as a service contract, so UCC Article 2 does not automatically apply. The MSA governs. Courts have split on hybrid licences delivered to customer hardware, but for subscription-only cloud delivery the service classification dominates, meaning the written agreement's terms on payment, cure, and termination control the enforcement analysis.

This is not academic. It affects what the vendor can argue about rejection of non-conforming goods, about revocation of acceptance, and about Article 2's four-year limitation period at § 2-725. Because Article 2 likely does not apply, the governing-law clause in the MSA dictates which state limitation period runs. Delaware is three years for most written contracts under 10 Del. C. § 8106. New York is six years under CPLR § 213. The difference is enforcement life, and vendors who sat on a claim for four years under a Delaware choice of law have lost perfectly good receivables at the door.

What happens to a SaaS contract when the customer files Chapter 11?

The MSA is almost always an executory contract under 11 U.S.C. § 365. The debtor-in-possession may assume, assume and assign, or reject it. Pre-petition unpaid invoices become general unsecured claims filed under 11 U.S.C. § 501. If the debtor continues using the SaaS after filing, the vendor has an administrative priority claim under 11 U.S.C. § 503(b)(1)(A) for the post-petition period, which ranks ahead of pre-petition unsecured claims.

The strategic lever is clause § 365(b): if the debtor wants to assume the contract and keep using the service, it must cure the pre-petition default. Cure means paying the vendor what it is owed before assumption is approved. For a SaaS vendor whose product is mission-critical to the debtor's operations, this is often the fastest path to full payment. The vendor should not suspend service reflexively on the petition date. Keeping the lights on while demanding assumption with cure is frequently the better tactic.

Bankruptcy treatment comparison

Does the FDCPA apply to B2B SaaS collection?

No. The Fair Debt Collection Practices Act, 15 U.S.C. § 1692 et seq., applies only to debts incurred for personal, family, or household purposes. B2B SaaS subscription debt is commercial debt and falls outside the FDCPA entirely. Vendors frequently over-engineer their collection scripts under the belief FDCPA rules apply. They do not.

What does apply is state-level commercial collection licensing. A collection agency pursuing commercial debt in New York, Massachusetts, Washington, or several other states must typically hold a commercial collections licence or register under the relevant statute. A foreign SaaS vendor instructing a US-licensed agency inherits the compliance perimeter without needing any direct US registration. This is the operational reason vendors route through a domestic partner even when the claim is simple.

State limitation periods for written contract claims

The governing-law clause in the MSA decides which row applies. A Delaware-chosen law combined with a California venue can produce a three-year limitation that surprises vendors who assumed New York's six-year window. Check the clause first, then calendar backwards from the earliest unpaid invoice date.

Information gain: the four points competitors miss

First, SaaS contracts are executory contracts under 11 U.S.C. § 365. The assume-reject-cure triangle is the single most valuable piece of leverage in a Chapter 11 where the debtor still uses the product. Most vendor-facing content ignores this entirely.

Second, the FDCPA does not apply to B2B collection. The compliance exposure is state-level commercial collection licensing, not federal consumer rules.

Third, UCC Article 2 most likely does not apply to pure SaaS. The MSA is the universe. Vendors who rely on implied Article 2 protections will be disappointed.

Fourth, arbitration plus the New York Convention is the cleanest global enforcement path for a foreign vendor with a US debtor and any possibility of the debtor holding non-US assets. An AAA award recognised under 9 U.S.C. § 1 converts into enforceable judgments in 168 New York Convention states.

Operational data points

Evergreen and auto-renewal clauses: a US state-law trap

Most SaaS MSAs contain automatic renewal language. California Business and Professions Code § 17600 requires clear and conspicuous disclosure of auto-renewal terms for certain contract categories, and New York and several other states have parallel rules. For pure B2B contracts with negotiated MSAs, these statutes often do not apply, but a poorly drafted auto-renewal clause can still be attacked by a defaulting buyer's counsel as a consent failure. Vendors should audit the clause before suing on a renewed term that was never affirmatively accepted.

Minimum contacts and personal jurisdiction

When litigation is the path, the threshold question is whether a US court has personal jurisdiction over the buyer. For a Delaware-incorporated debtor, this is trivial: Delaware always has general jurisdiction over its own corporations. For out-of-state subsidiaries or contracting parties, the International Shoe v. Washington minimum-contacts standard applies, and a forum-selection clause in the MSA typically resolves it on its face. Vendors that omit a forum clause end up litigating jurisdiction before they ever reach the merits.

How InterStation Handles a US SaaS Subscription Collection

1. File audit. We read the MSA, the invoicing history, every suspension notice, and the buyer's corporate status in Delaware or the state of incorporation. We extract the governing-law clause, arbitration clause, and limitation period.
2. Debtor intelligence. We pull the buyer's litigation docket, UCC filings, recent financing activity, and any Chapter 11 signals from PACER. A bankrupt debtor changes the entire playbook under § 365.
3. Demand and engagement. A dated demand letter goes out via a US-licensed partner in the debtor's state. We invite engagement on a defined payment window, with the dispute clause referenced directly.
4. Escalation path. If no engagement, we activate arbitration under the MSA or file suit in state or federal court, depending on the clause stack and the diversity math under 28 U.S.C. § 1332.
5. Bankruptcy posture. Where the debtor is in or entering bankruptcy, we file the proof of claim under § 501, assert administrative priority for any post-petition use under § 503(b)(1)(A), and press for full cure on assumption under § 365(b).

For broader sector context, vendors can read our briefing on SaaS debt collection as a complement to this US-specific page. For cross-border skip tracing prior to a US filing, see our cross-border skip tracing operation. The operating spine for outbound US claims sits in our international collections operation, and escalation into state or federal court runs through legal escalation.

Frequently Asked Questions

Ready to Collect Your US SaaS Receivable?

InterStation operates as an intelligence-led collection embassy. We read the MSA, map the debtor, choose the right forum, and move. If you are a SaaS vendor anywhere in the world with a delinquent US corporate subscriber, we can open the file today. Contact Us, Free Review.

Sources and Legal References

1. US Bankruptcy Code, 11 U.S.C. §§ 365, 501, 502, 503 — https://www.law.cornell.edu/uscode/text/11
2. Federal Arbitration Act, 9 U.S.C. § 1 et seq. — https://www.law.cornell.edu/uscode/text/9
3. Diversity jurisdiction, 28 U.S.C. § 1332 — https://www.law.cornell.edu/uscode/text/28/1332
4. Fair Debt Collection Practices Act, 15 U.S.C. § 1692 — https://www.law.cornell.edu/uscode/text/15/chapter-41/subchapter-V
5. UNCITRAL, New York Convention 1958 — https://uncitral.un.org/en/texts/arbitration/conventions/foreign_arbitral_awards
6. International Shoe Co. v. Washington, 326 U.S. 310 (1945) — https://www.law.cornell.edu/supremecourt/text/326/310
7. California Business and Professions Code § 17600 — https://leginfo.legislature.ca.gov
8. Delaware Code, 10 Del. C. § 8106 — https://delcode.delaware.gov/title10/c081/index.html
9. New York CPLR § 213 — https://www.nysenate.gov/legislation/laws/CVP/213
10. American Arbitration Association Commercial Arbitration Rules — https://www.adr.org