Home → Insights → Administrative penalty data

China Administrative Penalty Data: Official Sources vs Court Judgments

A Chinese administrative penalty record and a Chinese court document are different evidence objects. If your legal AI product needs market-regulation enforcement history, begin with official penalty disclosure. If it needs judicial reasoning about an administrative act, define a separate court-data track. Combining the two under one label creates coverage claims that neither source can support.

This guide maps the official market-regulation sources, explains why a public search is not a permanent register, and provides measured court-query pools for planning a pilot. It is written for data buyers, legal engineers and China-practice research teams. The sources and query responses were checked on October 12, 2026. It provides data-source analysis and procurement questions, not legal advice about a particular penalty.

1. Choose the evidence object before choosing the database

Start with the question your user will ask. “What did the regulator decide?” requires an administrative decision or an authoritative disclosure of it. “What happened when the decision was challenged?” requires the corresponding judicial material. “What is publicly displayed today?” requires a current source observation. Those questions can concern the same business and still demand different records.

Keep the issuing institution visible. A market-supervision authority issues a penalty decision; a court issues judicial documents. An official publicity system is a publication channel. A commercial court corpus is a captured research collection. None of these roles becomes another merely because a search result includes the words administrative penalty.

For the wider official court-source map, see our PRC court-data endpoints inventory. This page covers the penalty-disclosure boundary; it does not repeat the food-and-drug case-law guide or claim to inventory every Chinese regulator.

2. Two official market-regulation routes

SAMR's official website links both the National Enterprise Credit Information Publicity System and the China Market Regulation Administrative Penalty Documents website. The latter was announced on January 9, 2020. Its published homepage presents subject and geographic categories. These are official starting points, not a tested bulk export service. Sources: SAMR homepage, official launch announcement, penalty-documents portal.

The current market-regulation penalty-publicity rules specify publication through the enterprise publicity system for ordinary-procedure decisions, with exceptions. The disclosure includes a decision and summary identifying the decision number, party, violation category, penalty, authority and date. Confidentiality and personal-information processing remain relevant. Read the official consolidated rules, amended in 2025.

For procurement, distinguish an enterprise-centered lookup from a document-centered search. Write down which route supplied each field. A company name, decision number and source document identifier are different identifiers; a search interface that displays all three does not establish that each can be exported, queried without limits or used as a permanent join key.

We have not enumerated these official services, tested their pagination ceilings, obtained an export agreement or verified a supported public API. A working homepage cannot answer those questions. If a supplier promises nationwide historical coverage, ask for the source inventory and a reproducible coverage test rather than inferring completeness from an official logo.

3. Public disclosure has a lifecycle

The consolidated publicity rules provide correction and withdrawal procedures and different disclosure periods for different penalty categories. They also allow early cessation of some disclosures subject to conditions. This means the displayed population can change for reasons other than new enforcement. A missing result is not proof that no decision ever existed. Official publicity rules.

The credit-repair measures, effective December 25, 2025, additionally address coordination with other systems. Article 26 requires third-party business-information query providers to update the information they supply in accordance with the enterprise publicity system. The exact obligations for a proposed product need legal review. Official credit-repair measures.

Our engineering inference is to model an observation history separately from current display status. “Observed at source on this date” is a narrower statement than “currently published.” A later failed request also differs from a verified withdrawal. Keep transport failures, empty results and an express source status in separate states.

Agree how updates reach downstream search indexes, generated summaries and evaluation sets. A pipeline that can append records but cannot locate derived copies has an operational gap. Do not hide that gap under the phrase daily updates. Your acceptance note should identify the supported update actions and the evidence required to confirm each one.

4. Read the portal notice before treating it as a feed

The penalty portal's published notice says the issuing authorities are responsible for their published documents, the material is for reference with the formal text controlling, and commercial websites may not create full or partial mirrors without permission. It also addresses withdrawal of corresponding documents elsewhere. These are important reuse boundaries, not an enterprise data licence. Official document-page notice.

The document page retrieved during this check stated that a penalty document had not been uploaded. That observation concerns one page. It does not establish the proportion of missing documents across the portal. A buyer should test whether a selected record contains a usable decision, a structured summary, both or neither before counting it toward a full-text requirement.

Do not design around an assumption that search visibility authorizes commercial mirroring. Ask the appropriate owner or supplier for the permission needed for the proposed use. Keep that analysis separate from a court-data licence: permission for one collection does not silently cover a different official portal or its notices.

5. What measured court-query pools actually show

We ran three read-only queries against our captured judgments index. Each phrase query takes the logical union of ik_smart and ik_max_word analyzer results. The bench testing batch was excluded, and all count responses had zero failed shards. The pools overlap and have different fields and meanings; they must not be added into a total.

Download the query definitions, timestamps and exact count responses. Measurement date: October 12, 2026. These are record counts, not distinct proceedings, administrative decisions or verified market-regulation disputes. No semantic audit, party-role extraction or case-level linkage was performed for these pools.

A body match can refer to an administrative penalty in a civil dispute, an enforcement proceeding, a statutory quotation or a party's argument. An authority mention need not concern a penalty at all. Title matching narrows the evidence differently; it does not fix source publication selection or missing terminology. The smaller pool is not automatically the more accurate dataset.

Use these counts to assess query behavior and the possible size of a review task. Do not put them into an enforcement-risk chart. For that, first define the decision or dispute unit, classify context, validate the classifier, resolve duplicate records and document the denominator. A court collection cannot supply the universe of all administrative penalties merely by matching a phrase.

6. Keep decision numbers and case numbers separate

An administrative decision number identifies a regulator's document. A court case number identifies a judicial proceeding. Store them in different fields with the issuing body attached. If a court text quotes an administrative number, retain the quotation and location as evidence for a proposed link; do not replace the court identifier with it.

Name-only joining is especially fragile. Similar business names, former names, abbreviated institutions and anonymized court parties can create false matches. A proposed connection should carry its evidence and confidence state. Where a verified enterprise identifier is unavailable, say that the entity linkage remains unresolved.

One penalty may appear in multiple judicial documents. One judicial document may discuss several administrative acts. Your data model must allow those relationships rather than enforcing one row per company or one row per penalty. Otherwise a duplicate-removal step can accidentally delete a legally meaningful procedural document.

Also separate the date of the administrative decision, the judicial date, the publication date and the capture timestamp. Our court-corpus audit explains why a stored date field needs verification. A timeline built from inconsistent date semantics can suggest a lag or policy change that the underlying evidence does not establish.

7. A procurement checklist that produces testable answers

Use an evidence packet whose contents can be reviewed independently of the sales demonstration. It should include the exact queries, retrieval dates, response definitions and excluded populations. If precision is estimated from a sample, require the sample size, selection method and random seed, and examine source-batch and repeated-party concentration. A convenient first page of results is not a representative sample.

Agree how an unresolved item affects acceptance. For example, a record with metadata but unavailable text may satisfy a lookup requirement and fail a judicial-reasoning requirement. Make that distinction before delivery. It is much cheaper to scope two products honestly than to discover during acceptance that the same coverage claim was being used for both.

8. Scope a court-data pilot around the actual question

For a legal AI team, a useful pilot might ask whether captured court documents support a particular judicial-review research task. Define the subject, jurisdiction, dates, procedural stages and usable text criteria. Keep the official penalty track separate and obtain whatever permissions that track requires.

SinoVerdict offers a 160M+ record court collection with bulk, REST API and MCP delivery options. That record-scale statement is not a promise that every record has complete text, that every administrative decision is captured, or that the collection is more complete than another supplier's. Ask for a scoped coverage report and a trial API key through the access form; see delivery options.

For related subject research, compare the administrative-litigation guide and food-and-drug enforcement guide. For delivery verification, use our acceptance checklist. The endpoint inventory, subject guide and acceptance procedure serve different procurement decisions.

Keep a clear stopping rule: if the intended answer depends on current official display status, unresolved entity identity or a missing administrative decision, a court-text mention cannot close that gap. Record the missing evidence and narrow the answer. A dependable legal data product exposes those boundaries to its user.

Frequently asked questions