A foreign SaaS company usually enters China through the sales door. A multinational customer with an operation in Shanghai asks whether it can buy the same platform locally, a distributor offers to resell, and a first contract is signed from the offshore entity with a Chinese affiliate named as the local support provider. The arrangement works for a year. Then a domestic enterprise buyer asks for a renminbi invoice, the security questionnaire asks where the data is stored, and the procurement team asks for the licence number. The company discovers that it has been selling into China without the legal infrastructure to keep selling.

The pattern is common because the first year of cross-border SaaS in China can genuinely work. Latency is tolerable for many workloads, the customer is often an affiliate of an existing global client, and nobody in procurement asks hard questions about a pilot. The difficulty arrives with scale, with domestic customers and with regulated industries, and it arrives all at once.

The conclusion worth planning around is this: the hosting decision, the entity decision and the licensing decision are one decision, taken three ways. A company that chooses hosting first and discovers the entity and licence consequences later will rebuild the architecture, the contract set and often the cap table. The sections below take the three questions in the order they constrain each other, then set out how the reseller route differs from selling direct, because for most foreign SaaS companies the honest answer in year one is a hybrid of the two.

The hosting question decides everything else

Where the service runs determines who can lawfully operate it, which entity contracts with the customer, and which regulator has an interest.

Hosting outside mainland China means the service is not served from within the jurisdiction. That is lawful in itself. What it produces is a chain of consequences: latency that makes interactive products unpleasant, a domain that cannot be filed, a payment flow that runs offshore, and a data flow that crosses the border on every request. Some of those are commercial problems. The data flow is a legal one, and it is discussed below.

Hosting inside mainland China means the service is served from a mainland data centre, on a mainland domain, through a licensed access provider. That brings the site within the filing regime, requires the domain to be held by a Chinese entity, and puts the operator in front of the provincial communications administration. It also, in practice, requires the operator to be a Chinese company, because a foreign entity cannot hold the filing for a mainland-hosted site in its own name and cannot obtain the licence that paid services require.

There is no third option that avoids the choice. A Chinese CDN in front of an overseas origin is still overseas hosting for filing purposes. A Hong Kong region is overseas. A partner’s data centre is the partner’s hosting, which means the partner is the operator.

The hosting decision therefore has to be taken with the revenue model in view. A product sold to multinational affiliates that can procure offshore, used by a handful of users, with no personal information of Chinese residents beyond business contact details, can run offshore for a period. A product sold to domestic enterprises, embedded in their workflows, holding employee or customer records, will migrate to mainland hosting, and the migration is an engineering project with a legal deadline attached.

Four delivery architectures

The market has settled into four architectures. Each is internally coherent, and each fails in a characteristic way.

ArchitectureWho contracts with the customerWhere the service runsLicence positionBest fitCharacteristic failure
Offshore directOffshore parentOutside the mainlandNo Chinese licence; offshore termsGlobal accounts, pilot use, low data sensitivityProcurement blocks the deal on invoicing or data residency
Local support entityOffshore parent, with a WFOE providing supportOutside the mainlandWFOE holds an ICP filing for a marketing site onlyEarly market validation with global customersThe WFOE drifts into selling, which it cannot lawfully do
Domestic operator, licensedChinese entity with an ICP licenceMainland cloud regionFull licence, filing and content regimeDomestic enterprise sales at scaleCapital, staffing and time required before revenue
Reseller or local partnerDomestic partnerPartner’s environment or a mainland region the partner operatesPartner holds the licenceFast market access, regulated customersThe partner owns the customer, the data and the renewal

The offshore direct model is a legitimate way to test demand. It is not a China business. The moment the offshore entity hires sales staff in Shanghai, markets in Chinese, prices in renminbi or signs a contract with a domestic customer that expects local support, the arrangement has become something the structure does not describe.

The local support entity is the most common architecture and the most fragile. A wholly foreign-owned enterprise is set up to provide marketing, technical support and after-sales service to the offshore parent’s customers. That is a real function and it can be lawfully performed. The failure comes when the support entity starts negotiating contracts, taking orders or handling customer data, because at that point it is operating the service rather than supporting it. The distinction is not formalistic. It determines whether the entity needs a licence, whether the revenue is Chinese-source, and whether the data sits inside or outside the regime.

A domestic operator with a licence is the only architecture that supports a genuine domestic business at scale. It requires the entity, the capital, the licence and the compliance functions described in the companion guide to ICP licensing, and it takes months before the first renminbi invoice can be issued. Companies that plan for it from the start find the timeline manageable. Companies that arrive at it after two years of informal selling find it expensive, because the migration involves re-papering customer contracts, moving data and explaining a change of counterparty to procurement teams that have already approved a supplier.

The reseller model is treated in its own section below, because the legal differences are larger than the commercial ones.

The entity, and why a foreign entity cannot invoice

The single most concrete reason a foreign SaaS company ends up with a Chinese entity is the invoice.

Chinese enterprises account for value-added tax through a special invoice, and the buyer’s finance department needs that invoice to claim input credit. A foreign entity cannot issue one. It can issue a commercial invoice, and the Chinese customer can pay it, but the payment then requires a cross-border service transaction with withholding tax, foreign exchange documentation and a contract that the customer’s tax team will examine. Some multinational affiliates can do this because their treasury function is set up for it. Most domestic enterprises cannot, or will not, because the finance process is built around domestic invoices and the tax deduction is real money.

The consequence is that a foreign vendor selling direct to a domestic enterprise hits a wall in procurement that has nothing to do with the product. The deal stalls at the point where the purchase order should be raised.

Four entity options exist, and the choice follows from the architecture.

A wholly foreign-owned enterprise is the default vehicle for a foreign technology company. It can employ staff, sign contracts, hold a domain and an ICP filing, invoice in renminbi and remit profits. It cannot hold an ICP licence because of the foreign ownership cap on value-added telecommunications services. That single fact determines whether the WFOE can be the operating company or only the support company.

A joint venture with Chinese majority ownership can hold the licence, and is the cleanest lawful structure for direct domestic operation. The cost is governance. A joint venture in which the foreign party holds a minority stake and the Chinese party holds the licence is a partnership in which the licence holder has structural leverage, and the joint venture contract has to be drafted with that in mind: deadlock resolution, exit mechanics, valuation, and what happens to the licence if the partnership ends.

A representative office is a liaison presence. It cannot sign revenue contracts, cannot invoice and cannot employ staff directly in the way an operating company can. It is a reasonable way to station two people in Shanghai while the structure question is being decided, and a poor way to run a business.

No entity at all is a valid position for a company selling to global accounts that procure offshore. It becomes untenable when the customer base turns domestic.

There is a fifth arrangement that is not an entity but behaves like one: a domestic partner that holds the licence and contracts with customers while the foreign company supplies technology. It is the reseller model, and it is where most foreign SaaS companies actually start.

Data localisation: what has to stay

China’s data regime has three layers that matter for SaaS: the cybersecurity law, the data security law and the personal information protection law, supplemented by the rules on cross-border transfer. The practical question for a vendor is narrower than the statutes suggest. What data must be stored in China, what data may leave, and what has to be done before it leaves.

Personal information is the category that catches most SaaS products. It is defined broadly, and it includes information relating to an identified or identifiable individual. Employee records, customer contact details, support tickets containing names, usage logs tied to an account, and in many products the content that users upload, all fall within it. Foreign product teams routinely assume that B2B data is not personal information because the customer is a company. The customer is a company; the data subjects are its employees.

Important data is the second category. It is defined by reference to harm to national security or public interest if disclosed, and sector regulators publish catalogues identifying what counts in their industries. For most enterprise SaaS products the category does not apply, but for products serving finance, healthcare, automotive, mapping or critical infrastructure customers, the customer’s own classification may pull the vendor’s data into scope.

Critical information infrastructure operators face the strictest regime, including a presumption of local storage and a security assessment before any transfer. A foreign SaaS vendor is rarely a critical information infrastructure operator itself. Its customers sometimes are, and those customers will impose flow-down obligations in the contract that go beyond what the law requires of the vendor directly.

The operational point is that localisation is an architecture decision, not a compliance checkbox. A product built with a single global tenant database, a global analytics pipeline and a global support console cannot be made compliant by adding a data processing agreement. It needs a mainland region, a separate tenant boundary, a support model that does not require an overseas engineer to open a customer record, and a logging design that keeps Chinese user data in the Chinese environment. Those are engineering choices with cost and lead time, and they are best taken before the first domestic customer signs.

The three cross-border pathways

Where data does leave China, the transfer must follow one of three routes: a security assessment organised by the provincial cyberspace administration, a standard contract filed with the same authority, or certification by an accredited body.

The choice is driven by volume, sensitivity and the nature of the data. The framework, in outline, is that transfers below a stated cumulative volume of individuals fall outside the three routes entirely; transfers between that figure and a higher one may use the standard contract or certification; transfers above the higher figure require the security assessment; and sensitive personal information triggers the assessment at a much lower volume. The figures are set by the implementing provisions and have been adjusted since the regime began, so the current thresholds must be confirmed before a transfer programme is designed. What does not change is the structure: small volumes are exempt, medium volumes need a filing or a certificate, large volumes need an assessment.

Two features of the regime are routinely underestimated.

Remote access counts. An overseas engineer opening a customer record in a support console, a global analytics dashboard that queries the Chinese tenant, or a parent company’s finance system that pulls Chinese customer data for reporting are all transfers, whether or not a file is exported. Companies that map their data flows by looking at integrations miss the human access paths, which are usually the largest.

The standard contract is a filing with ongoing obligations, not a signature. The contract must adopt the prescribed clauses, the filing must be made before the transfer begins, and the parties must be able to demonstrate that they assessed the necessity and the impact. A signed contract that was never filed is not a lawful pathway. A filed contract that no longer matches the data flows is a filing that has drifted.

For a SaaS business, the practical sequence is to map the flows, classify the data, decide the architecture, and only then choose the pathway. Companies that choose the standard contract first and map afterwards usually discover that their largest flow is one they had not considered.

The licence that matches the delivery model

The licence question is answered by what the customer is paying for and where the operator sits.

A paid SaaS service delivered over the internet to Chinese users is a commercial information service, and the operator needs an ICP licence. That is the general position, and the companion guide to ICP licensing sets out the ownership cap, the capital and staffing requirements and the application sequence in detail.

Two points matter for SaaS specifically.

One concerns classification. Some SaaS products are classified as online data processing and transaction processing rather than information services, particularly where the product processes transactions or handles data on behalf of the customer rather than delivering content. The classification is decided with the provincial administration on the facts of the service, and a product that both delivers information and processes transactions may need both categories. The application should describe the service as it actually functions, including any marketplace, payment or settlement element, because a mismatch between the description and the product is discovered at inspection or at the customer’s procurement review.

The other concerns where the licence sits. It attaches to the operator, not to the software. If a reseller operates the service in China, the reseller holds the licence and the foreign company is a technology supplier. If the domestic entity operates the service, the domestic entity holds the licence. There is no arrangement in which the foreign company holds the licence through a contractual workaround, and an arrangement that describes itself that way is either a reseller model with the labels changed or an unlicensed operation.

Several other requirements sit alongside the telecom licence, and enterprise buyers check them.

MLPS, the multi-level protection scheme for information systems, requires the operator to grade its system, file the grading with the public security bureau, and complete an assessment at the applicable level. Enterprise SaaS platforms commonly sit at level two, and systems with large user bases, sensitive data or sector significance sit at level three with annual assessment and more demanding controls. The grading is a self-assessment confirmed by an assessment body, and the practical work is a control framework covering access management, logging, backup, incident response and physical security.

Algorithm filing applies where the product uses a recommendation algorithm to serve content or products to users. Generative AI capability offered to the public triggers the separate generative AI filing and security assessment, and generated content must be labelled. A SaaS product that adds an AI assistant has added a regulatory process, and the product team usually learns this from the customer’s security questionnaire rather than from its own compliance function.

Data export obligations, described above, apply to the operator and to the vendor according to the role each plays. The contract must allocate those roles explicitly, because the customer will want to know who is the personal information processor and who is the entrusted party, and the answer determines who answers to the regulator.

Reseller versus direct: what changes legally

The reseller route is often presented as a commercial choice. It is a legal structure with its own consequences, and the differences from selling direct are worth stating plainly.

In a direct model, the vendor’s Chinese entity contracts with the customer, invoices in renminbi, holds the licence, operates the service and is the personal information processor for the customer data it handles. The vendor owns the customer relationship, sets the price, controls the roadmap and bears the compliance cost. Margin is retained in full and the compliance burden is retained in full.

In a reseller model, the domestic partner contracts with the customer, invoices, holds the licence and operates the service in China. The foreign company licences technology and grants a trademark licence, provides second-line support, and receives a licence fee, a margin on the resale price or a revenue share. The partner owns the customer relationship, the contract and, in most structures, the data.

The legal differences that follow are specific.

Regulatory risk sits with the partner, which is the principal attraction of the model. The partner is the licensed operator and answers for content, for the filing, for the annual report and for the security assessment. It is also the reason a partner will demand control over what the product does in its market, because a feature added by the foreign vendor can change the partner’s regulatory position overnight.

Customer ownership follows the contract. In a well-drafted distribution agreement, the customer contract is between the partner and the customer, and the vendor’s visibility is limited to what the agreement requires the partner to disclose. When the agreement ends, the customers stay with the partner unless the contract provides for assignment or transition. Companies that treat the reseller as a sales channel rather than as the counterparty of record discover at renewal that they have built a book of business for somebody else.

Data follows the operator. If the partner operates the service, the partner is likely to be the personal information processor and the vendor the entrusted party or a sub-processor. That reverses the data relationship the vendor is used to, and it limits the vendor’s ability to use Chinese customer data for product improvement, model training or global analytics. The contract must say what the vendor may see, what it may retain and what it must delete, and the answer is usually narrower than the product team expects.

Characterisation is the risk nobody drafts for. An arrangement labelled as distribution in which the vendor sets the price, approves every customer, controls the brand, receives the customer data and pays the partner a fixed commission may be treated as something other than a genuine resale. Chinese law looks at substance, and the substance may be an agency or, worse, an unlicensed direct operation with a domestic front. The agreement should allocate real functions to the partner: contracting, invoicing, first-line support, customer relationship and regulatory responsibility, with the commercial terms reflecting that allocation.

Exit is where the model is tested. A reseller agreement that runs for years with no performance commitments, no transition obligation and no restriction on the partner developing a competing product is a structure that transfers the business by instalment. The agreement should set minimum commitments, a transition plan on termination, a non-compete limited to the term and the territory, and a clear rule on who keeps the customer list.

A hybrid is often the right answer. Multinational customers that can procure offshore buy from the foreign entity or its support company. Domestic enterprises, and customers in regulated sectors that require a licensed local supplier, buy through the partner. The two channels are kept separate by customer definition rather than by hope, and the agreement says which is which.

The sequence, and who owns each step

The table below is the order in which the decisions constrain each other. Companies that start at the bottom, with a customer contract, usually come back to the top.

StepResponsible partyTypical timingWhat foreign companies miss
Map data flows, including support accessProduct, security and counselTwo to four weeksOverseas engineer access is a transfer
Choose the delivery architectureManagement, with counselOne to two weeksHosting chosen before the revenue model is understood
Decide the entity and ownership structureManagement, counsel, investorsTwo to four weeksThe licence cap determines the cap table
Incorporate the entity and fix the business scopeMarket regulation bureau, with a local agentFour to eight weeksScope omits the service description the licence needs
Contribute capital and hire the compliance and technical staffFinance and HROne to three monthsStaff seconded from the parent do not satisfy the requirement
Obtain the ICP filing for the marketing siteProvincial administration, via the hosting providerTen to twenty working daysDomain held offshore or by a founder
Complete the licence applicationProvincial administration, then the ministrySixty to ninety working days if cleanLaunch date promised before the certificate
Grade and file the system under MLPSPublic security bureau, with an assessment bodySix to twelve weeksLeft until a customer questionnaire arrives
Build the mainland region and tenant separationEngineeringThree to six monthsTreated as a hosting migration rather than a product change
File the cross-border pathway, if any transfer remainsProvincial cyberspace administrationFour to eight weeksRemote access not included in the mapping
Complete algorithm or generative AI filing, if applicableCyberspace administrationEight to sixteen weeksTreated as a product team matter
Re-paper the customer contractsLegal and salesBefore the first domestic invoiceGlobal terms of service used unchanged
Set up invoicing, tax and transfer pricingFinanceBefore the first renminbi invoiceIntercompany pricing undocumented

Two observations on the sequence. The capital and staffing steps sit before the licence application and are the reason the licence takes months rather than weeks, because the application cannot be filed until the entity can demonstrate the resources. The engineering step sits in parallel with the licence and usually takes longer, which is why companies that start the licence early still launch late.

Where foreign companies get this wrong

Six failure modes account for most of the wasted spend, and each has a recognisable consequence.

Running a support entity as a sales operation. The wholly foreign-owned enterprise is described as providing marketing and support, and in practice it negotiates, quotes and closes. The revenue is booked offshore to avoid the licensing question. The consequence arrives when a domestic customer asks for an invoice, when the tax authority examines the permanent establishment question, or when the arrangement is reviewed in diligence and the buyer discounts the China revenue because it is not lawfully earned.

Assuming employee data is not personal information. A workforce analytics product, an HR platform or a collaboration tool holds records of identified individuals. The data mapping exercise excludes them because the customer is a company. The consequence is an unregistered transfer of personal information at a volume that may require a filing or an assessment, discovered when the customer’s own compliance team asks for the vendor’s pathway documentation.

Treating the standard contract as a signature. The clauses are signed, the transfer proceeds, and nobody files. The consequence is that the transfer has no lawful basis, and the exposure is not hypothetical once a customer in a regulated sector audits its supply chain.

Letting the reseller own everything. The partner holds the licence, the contract, the data and the customer relationship, and the vendor’s agreement has no performance commitment, no transition right and no restriction on competing products. The consequence is that after three years the vendor has a licence fee and no business, and the partner has both.

Signing enterprise contracts before the invoicing capability exists. Sales closes a domestic logo, procurement raises a purchase order, and finance discovers that the vendor cannot issue a special invoice. The consequence is a delayed payment, a strained first relationship and, often, a discount given to apologise.

Ignoring MLPS until the questionnaire arrives. A large customer sends a two-hundred-question security assessment, including a request for the MLPS grading certificate. The vendor has none, and the assessment takes weeks. The consequence is a stalled deal at the final stage, after the commercial terms have been agreed.

A seventh failure belongs to the finance function rather than the legal one: intercompany pricing that is set to move profit to the parent without documentation. The China entity is profitable on paper only if the service fee is set correctly, and the tax authority is entitled to challenge a price that does not reflect the functions performed. The consequence is an assessment, interest and penalties, and it usually surfaces during an audit or at exit.

Cost and commercial impact

The cost of entering China with a SaaS product is dominated by four items, and only one of them is a legal fee.

The compliance build comes first: the mainland region, the tenant separation, the logging and access controls, the moderation tooling and the security assessment. This is engineering cost and it scales with how much the global architecture assumed a single environment. Companies that designed for regional isolation spend far less than companies that did not.

Entity and licence costs follow: incorporation, capital contribution, the licence application, the compliance staff and the ongoing accounting and audit. The capital is committed rather than spent, but it is capital that cannot be used elsewhere.

Time to revenue is the third item and the one most often left out of the budget. The sequence above runs to roughly six to nine months before a domestic invoice can be issued, depending on the architecture and the licence category. A sales team hired in month one is a cost with no revenue for two or three quarters.

Channel cost is the fourth. A reseller takes a margin that a direct model would retain, and the margin is the price of market access, licensing and customer ownership. The question is not whether the margin is worth it in the abstract, but whether the alternative, which is waiting a year to build a direct operation, costs more.

Two commercial realities deserve a line each. Enterprise buyers in China expect long payment cycles and detailed acceptance processes, and a vendor whose global standard terms assume annual prepayment will find the first negotiation harder than expected. Security review is also substantive: buyers in finance, healthcare, automotive and government-adjacent sectors will ask for data residency warranties, penetration test reports, MLPS evidence and a right to audit, and the answers have to be true rather than aspirational.

Practical checklist

China is a market where a foreign SaaS product can be sold, but not casually. The companies that succeed treat the entry as an architecture and governance project with a commercial objective, rather than as a sales campaign with a legal appendix. The order of the decisions matters more than the speed of any single step.

Our business licensing service covers the entity and licence sequence, and data compliance covers the mapping, the pathways and the contract set. The licensing framework itself is set out in ICP Filing, ICP Licence and EDI Licence, the cross-border transfer rules in China Cross-Border Data Transfer, and the entity question in Do I Need a Chinese Entity?.

Frequently Asked Questions↑ Back to article

Do enterprise saas companies need a Chinese entity to enter China?

It depends on your business model. If you are only selling hardware components or software licenses cross-border, you may not need a local entity. But if you are providing services to users in China, handling Chinese user data, or having a physical presence — you typically need a domestic entity. We assess your specific situation and advise on the right structure.

How long does it take to launch an enterprise saas product in China?

Timeline varies significantly by product type. Entity setup takes 6–8 weeks. Licensing and compliance add 2 weeks to 6+ months depending on your product category and regulatory requirements. Budget 3–9 months for a full compliant launch, depending on what certifications and filings you need.

What are the biggest compliance risks for foreign enterprise saas companies in China?

The biggest risks vary by sub-sector but generally include: data compliance (data localisation and cross-border transfer), product safety and standard compliance (especially for physical products), algorithm and AI regulation, and licensing requirements. The specific risks depend on your product architecture and business model.

Do foreign SaaS companies need to host data in China?

It depends. If you serve Chinese customers from overseas servers, you may not need local hosting — but performance will be poor, and certain industries require local data storage. If you set up a Chinese entity and provide services locally, you need to comply with Chinese data security regulations, which may require storing certain types of data in China. For regulated industries (finance, healthcare, government), local data storage is usually mandatory.

What is the difference between WFOE and joint venture for SaaS in China?

A WFOE (Wholly Foreign-Owned Enterprise) gives you full control but requires you to navigate all regulations independently. A joint venture (JV) with a Chinese partner can help with market access, licences, and local relationships — but you give up some control and share profits. For SaaS companies, WFOE is more common because IP control is critical. JVs are more common in regulated industries where foreign ownership restrictions apply.

Why is an ICP licence required for enterprise SaaS in China?

An ICP licence is required for enterprise SaaS in China because if you charge customers for your service, you are providing paid information services over the internet, which falls under value-added telecommunications services regulated by MIIT. The ICP licence has foreign ownership restrictions capped at 50% foreign equity subject to approval, which is a key consideration for foreign SaaS companies entering the Chinese market. Without an ICP licence, you cannot legally charge Chinese users for SaaS services provided from within China.

What are the cross-border data transfer options for SaaS companies in China?

Enterprise SaaS companies transferring data out of China must use one of three lawful cross-border data transfer pathways. The most commonly used pathway for SaaS companies is the Standard Contract pathway, where you sign standard contractual clauses with the receiving party and file with the Cyberspace Administration. The other two pathways are the Security Assessment pathway (for large volumes or sensitive data) and the Certification pathway (through accredited certification bodies). The right pathway depends on data volume, data type, and your specific architecture.

Geason Law Offices AI Industry Research Group | Reviewed by He Qianggao (Lawyer License No. 14403201310092337, 10+ years of practice)