China (CN)

​

Overview

China corporate data is sourced from NECIPS. Search, Lite Profile, and Enhanced Profile are all supported across V1 and V2. registrationAuthority is returned as "NECIPS" regardless of which provincial / municipal SAMR sub-authority is recorded at source.

​

Company identifiers

The USCC is the current primary CN registration number; it encodes registering authority, entity type, region, and a check digit. Pre-USCC registration codes and organisation codes remain available as secondary identifiers for entities registered before the USCC system.

​

Company names

CN companies are registered in Chinese; an English name (when published) is a transliteration / translation. For CN entities you should treat englishName (not companyName) as the Latin-script form for display in English-language contexts.

​

Legal form

CN legal form is populated on both legalForm.original (the registry-source label, in English) and legalForm.normalized (the standard value). If the source label is absent, the legal form is inferred from the Chinese-script company-name suffix (分公司, 股份有限公司, 有限责任公司, 有限合伙, 有限公司).

​

Branch vs Subsidiary — translation gotcha

In Chinese corporate law:

• 分公司 = branch — no independent legal personality, an operating arm of the parent.
• 子公司 = subsidiary — separate legal entity owned by the parent. This would map to Private Limited Company (or Public Limited Company) on its own merit.

Kyckr maps both the source English string "Subsidiary" and the Chinese name-suffix 分公司 to Branch in the normalised response, so integrators see the correct concept. The raw source label is preserved in legalForm.original.

​

Status

CN legalStatus.original carries the registry-source English string (which varies across cohorts — multiple parallel translations of 在营 / 开业 appear in the wild). legalStatus.normalized maps to one of the standard values:

​

Activity / industry codes

CN activities populate activities[] with:

• activities[].description — free-text Chinese / English description (e.g. "Water conservancy, environment and public facility management")
• activities[].code — registry-source industry code where present
• activities[].classificationScheme — null (CN does not carry an explicit classification scheme — NACE / NAICS not used)
• activities[].type — "Primary" when the source flags the activity as primary

​

Address

CN address returns the flat fullAddress only — there is no component parsing (city, region, streetName, etc. are null).

• country: "China"
• isoCode: "CN"
• postcode, rawAddressLines, structured components: null

​

Capital structure

CN entities populate the standard V2 capital / totalCapital shape:

• Currency: RMB (人民币元 at source; surfaced as RMB in normalised output)
• totalCapital.type: typically Registered — the registry reports registered-capital amount (rather than authorized or paid-in). See Normalised values.
• Thousands-comma source values (e.g. "302,973,182") are normalised to numeric totalValue

Per-class shareholding capital is surfaced inside shareholdings[].

​

Shareholders

CN shareholders are returned in V2 shareholdings[].shareholders split by entity type:

• Corporate shareholders → shareholdings[].shareholders.corporations[]
• Natural-person shareholders → shareholdings[].shareholders.individuals[]

Subscribed-capital values that arrive with a currency suffix at source (e.g. "156,000,000 RMB") are normalised to numeric totalNominalValue with the currency on the parent capital entry.

​

Representatives / directors

CN representatives populate V2 representatives.individuals[] with English and Chinese name, role, ID information, address, and appointment / outgoing dates. Common CN-specific roles (mapped to standard role values via the director-role lookup):

• Director, Supervisor, Chairman, Vice Chairman, Manager, General Manager, Executive director, Legal Representative, Board Secretary, Financial Officer of a Listed Company
• Compound roles follow most-significant-first (e.g. "Manager, Director" → MANAGER; "Director, General Manager" → DIRECTOR)
• "person in charge" (the natural-person 负责人 commonly recorded for branch entities) → LEGAL_REPRESENTATIVE

​

Contact details

CN entities consistently surface contact details on V2 contactDetails:

• contactDetails.telNumber
• contactDetails.email (with "N/A" placeholders filtered out)
• contactDetails.website (with "N/A" placeholders filtered out)

This is CN-specific behaviour — HK and JP responses do not include contact details.

​

Data Availability

​

Additional resources

• Normalised values guide
• Company V2 API Reference