Article

ICP Filing for Foreign Companies: Step-by-Step Timeline

September 23, 2026

You have decided to host your site or application on mainland servers. That decision triggers a regulatory requirement: an ICP filing (Bei'an, 备案) before your domain can stay online. For foreign companies, the process has more moving parts than it does for a domestic operator — entity structure, hosting choice, and document preparation all interlock.

This article walks the five phases in order. Each phase section covers what happens, who handles it, and what typically goes wrong. This is practical guidance based on our coordination work, not legal advice.

Pre-filing readiness check

Before you start the five phases, confirm three prerequisites:

1. A qualifying entity. You need a mainland-registered company or qualifying partner to hold the filing. For most foreign brands, this means a WFOE. A Hong Kong entity alone does not qualify — see Who can file for ICP? below.
2. A registered domain. The domain you plan to operate must be registered and under your control.
3. A mainland hosting provider selected. Filing and hosting are interdependent — your provider must accept your entity type and business category.

If you are still evaluating whether your stack is ready for China, the 10-point China readiness check covers ICP gaps alongside performance and dependency issues. Rows 9 and 10 map directly to the entity and filing questions this article expands.

Phase 1: Entity readiness

What happens

Confirm that you have a mainland company or qualifying partner that can hold the ICP filing. For foreign brands, this is typically a WFOE. The entity must be registered and hold a valid business license before any filing work begins.

Who handles it

Your legal counsel or corporate services provider coordinates the WFOE setup. We work with your counsel on the technical prerequisites — hosting, domain, and HTTPS configuration — aligned with filing rules.

What goes wrong

Companies discover too late that their entity structure does not qualify. The classic version: assuming a Hong Kong entity is sufficient — it is not (see Who can file for ICP? below). Discovering this late stalls launches, because entity setup cannot be rushed.

Phase 2: Hosting selection

What happens

Choose a mainland hosting provider — Alibaba Cloud, Tencent Cloud, or another local provider — that accepts your entity type and business category. The provider matters because you file through their portal, and not every provider works with every entity structure. For the cost side of that choice — entry bundles vs pay-as-you-go — see the China hosting cost comparison. For the CDN side of that choice, see China CDN for foreign companies. For the head-to-head provider decision, see Alibaba Cloud vs Tencent Cloud.

Who handles it

Your engineering or infrastructure lead, coordinated with your compliance advisor. Our mainland infrastructure service covers hosting selection, CDN configuration, and the dependency audit that often surfaces blocked APIs alongside the hosting decision.

What goes wrong

Two problems recur. First, committing to a hosting provider before confirming they accept your entity type and business category — then discovering the filing cannot proceed through that portal. Second, treating hosting and filing as sequential rather than interdependent. Mainland hosting triggers the ICP filing obligation, so the two decisions must happen together. For a detailed explanation of why mainland hosting matters for performance and compliance, see why your website is slow in China.

Phase 3: Document preparation

What happens

Assemble the four required documents — a fixed set, enumerated in the document checklist below.

Who handles it

Your compliance coordinator or legal counsel gathers the documents. The responsible person (the individual named on the filing) must provide identification and may need to complete verification steps through the hosting provider's portal. We supply the document checklist and timeline plan as part of the coordination work.

What goes wrong

Incomplete or incorrectly formatted documents stall this phase. A business license that does not match the filing entity name, a domain certificate that lists a different registrant, an incomplete authorization letter — each comes back for correction. Prepare the checklist early and verify every document against the provider's requirements before you submit.

Document checklist for ICP filing

The filing requires four documents: a business license, domain certificates, responsible person identification, and authorization letters. All four share one failure mode: the entity name. Every document is keyed to the filing entity name — the license must name the entity that will hold the filing, the domain certificates must list the same registrant, and the authorization letters must reference the same company.

Phase 4: Submission & review

What happens

File through your hosting provider's portal. As the review proceeds, you may receive queries from the provider or from the reviewing authority — respond promptly with corrections or additional documentation.

Who handles it

Your compliance coordinator submits and monitors. We handle the portal workflow and query responses as part of our ICP compliance service.

What goes wrong

Slow responses to queries. The 2–4 week window — varying by province and business category — assumes complete documents and a qualified entity; open queries stretch it, and incomplete documents or a non-qualifying entity push the timeline past it. That is why phases 1 through 3 matter.

Where filings stall

Most timeline slippage traces to four causes. None is a regulatory mystery — each is a preparation failure. When a preparation failure surfaces as a formal rejection instead of a stall, the fix loop is documented too — see the provider-documented rejection catalogue and fixes.

Non-qualifying entity discovered late. The team assumes their Hong Kong entity is sufficient, or they have not yet decided on an entity structure, and they discover the gap after hosting is provisioned and documents are drafted.

Provider rejects the entity type or business category. The filing runs through the hosting provider's portal, and not every provider works with every entity structure or accepts every business category. The same gate blocks CDN acceleration domains — see why an unfiled domain never reaches a mainland CDN.

Document mismatches. A business license that names a different entity. A domain certificate with the wrong registrant. An incomplete authorization letter. Each defect comes back for correction. The fix is mechanical — reissue and resubmit — but each round stretches the timeline.

Slow query responses. During review, the provider or the reviewing authority may raise questions. The 2–4 week submission window assumes prompt responses — open queries stretch it. Teams that treat submission as a fire-and-forget step, rather than monitoring the portal, let queries sit unanswered.

These four causes are preventable. The phases exist in order for a reason: entity first, hosting second, documents third, submission fourth. Skipping ahead does not save time. Mini Program filings carry their own failure modes, above all the 24-hour SMS window — see the Mini Program flow's own stall points. When the outcome is a rejection rather than a stall, a separate fix-and-resubmit loop takes over — see If your filing is rejected below. More filing questions? See the FAQ hub.

If your filing is rejected

A rejection can come back at two layers. The provider's filing specialists review every order first — within 1–2 working days at both Tencent Cloud and Alibaba Cloud — and can reject it before the provincial Communications Administration (CA) ever sees it. Tencent Cloud publishes the mechanics: if the reviewer's verification call goes unanswered, they retry about an hour later, and an order that still cannot be verified is rejected. Rejection comments arrive through the contact email on the order or the filing console — fix exactly the flagged items and resubmit. After a rejection at the CA stage, Alibaba Cloud notes that the rejected status takes about 1 working day to sync back to its console before the resubmit entry reappears. Each fix round re-runs inside the same 2–4 week submission-and-review framing.

Both providers publish the reason catalogue. The recurring categories:

• Certificate problems. Unclear or incomplete certificate images; per Tencent Cloud, ID documents must carry more than 3 months of validity at submission; per Alibaba Cloud, the document set must be complete and the subject responsible person must be the company's legal representative.
• Domain real-name mismatch. Per Alibaba Cloud, the domain's real-name data — holder name, certificate type, and certificate number — must match the filing subject exactly, or the CA rejects the order. The fix is transferring the domain to the filing subject.
• Website naming. Per Alibaba Cloud's published rules: at least 3 Chinese characters, no pure digits or English, no 中国/中华/中央/人民/人大/国家 prefixes for non-state entities, and the name must not be the domain itself.
• Phone reachability. The responsible person's number must answer and must come from the filing province's number range; per Alibaba Cloud, some provincial CAs do not accept virtual-operator ranges.
• Process collisions. Per Alibaba Cloud: a duplicate order for the same subject at another provider; a phone or ID number already used under another subject; an existing MIIT record — including records created through WeChat or Alipay Mini Program platform filings, which route the order to access/new-website filing instead of a first filing; and one rejected APP in a multi-APP order returns the whole batch. The alternative platforms feed the same MIIT system — Douyin and Alipay mini program filing windows.

Platform-filed records are one of the ways the Mini Program and website pipelines interact — see the Mini Program filing flow for that pipeline, and the China CDN article's rejection FAQ for the domain-match rules. If a rejection lands on your launch calendar, our ICP compliance service decodes the rejection comments and drives the resubmission.

Phase 5: Display & maintenance

What happens

Once approved, you receive an ICP number. Publish it on your site and keep it displayed for the life of the site. When you add domains, change entities, or expand to new regions, update the filing. When "update the filing" means a provider switch, a subject change, or a shutdown, the documented sequence is in how to transfer or cancel a filing when providers change.

Who handles it

Your engineering team adds the ICP number to the site. Your compliance coordinator handles updates when the filing details change.

What goes wrong

Two problems. First, failing to display the ICP number after approval — display is part of the requirement, not an optional extra. Second, forgetting to update the filing when something changes. Adding a domain, restructuring the entity, or expanding services all require filing updates.

Display and updates are one half of the post-approval picture; the license question is the other half. The trigger is what your product does, not where it is hosted. The ICP filing covers baseline site operations; if your product adds paid services, transaction features, or regulated content categories, the ICP license — a separate, longer permit process layered on top of the filing — may apply. Most marketing and content sites need only the filing; transaction platforms need to assess the license. If your product may handle paid transactions or regulated content in mainland China, start the license evaluation early.

After approval: display and the license question

Both post-approval tasks — displaying the ICP number and the license question — are covered in Phase 5 above. Plan the display step into your launch checklist on day one. Once displayed, the number is publicly verifiable through MIIT's ICP filing lookup.

Who can file for ICP?

The ICP filing holder must be a mainland-registered company or qualifying partner. For foreign brands, this is typically a WFOE.

A Hong Kong entity alone does not satisfy the filing-holder requirement. Teams often discover this late, when the rest of the launch is otherwise ready. If you operate in China through a WFOE, the WFOE is the entity that holds the filing — the Hong Kong entity cannot substitute for it. Plan entity structure before you plan your launch date. For the full entity comparison, see WFOE vs Hong Kong Company: ICP Filing Entity Rules Explained. And while the filing is in progress, your visitors do not have to wait — see how to serve China visitors while the filing is in progress.

The same filed entity underpins other China digital operations. If you later build WeChat Mini Programs, the Mini Program operates under the same ICP-filed entity. That program needs its own filing before WeChat will publish it — see how Mini Program filing works. The vehicle choice — Mini Program, H5, or native app — is a product decision layered on the same compliance foundation. See our comparison of WeChat Mini Program vs H5 vs app for the product-side analysis. The same filed entity also typically holds the WeChat Pay merchant account — see WeChat Pay for foreign companies: acceptance paths and requirements. Term definition: Mini Program glossary entry.

Entity status → filing path

Your entity structure determines which filing path applies. Three scenarios cover most foreign-brand situations.

The choice of mainland structure is a legal and tax decision. The filing question is narrower: does the entity qualify as a mainland-registered company or qualifying partner? If the answer is yes, proceed. If the answer is no, fix the entity structure first.

Frequently asked questions

Next steps

The five phases are straightforward in structure but easy to missequence. Entity setup must come before hosting selection. Document preparation must be complete before submission. And the filing holder must qualify before anything else starts.

Bring your entity structure, product description, and hosting requirements. We will map the phases to your timeline, flag the entity and filing questions early, and coordinate the technical prerequisites alongside the compliance work. Start with the ICP compliance service or email hello@chinagateway.pro.