Source Datav1.0
C2C — Disclosed (Point-in-Time)
Point-in-time customer–supplier disclosures. The same disclosed relationships as C2C — Disclosed, but every vendor revision is retained with the date it became known, so an as-of read reconstructs what was on file on any past date rather than only what is true today. 9 tables covering customer and supplier equity links, related-party sales and purchases, related receivables and payables, and individually-material receivables. Priced per-table (true-name model).
Buy by the field
62 priced fields
Pick the fields you need — priced individually below.
Whole set$5,218.33/mo
Exactly the sum of its fields — no bundle premium, no bundle discount
Pay annually · save 20% — $50,096/yr
ⓘ Take the whole set from the field list below — select everything, add it to your basket, and check out there.
C2C — Disclosed (Point-in-Time)
c2c_pitSource DataPoint-in-time customer–supplier disclosures. The same disclosed relationships as C2C — Disclosed, but every vendor revision is retained with the date it became known, so an as-of read reconstructs what was on file on any past date rather than only what is true today. 9 tables covering customer and supplier equity links, related-party sales and purchases, related receivables and payables, and individually-material receivables. Priced per-table (true-name model).
Updated Daily · sample in the Matrix
7. Field reference — every column
Every column of every table, with the served type, whether it contains nulls in the current vintage, and what it means. Column names are exactly as delivered.
equity_customer_pit
Table · pick one of 9
equity_customer_pit
47 columns · 994,569 rows · grain (primary key): id
One row per id within each delivery. When the vendor corrects a record it comes back in a later delivery under the same id, marked as an update — so match on id and keep the newest delivery.
Business key (what a row is ABOUT, distinct from the row identifier): company_id, report_end_date, publish_date, entity_orig, typ — one Disclosed Major Customers line per filer x reporting period x disclosure date x as-reported counterparty x disclosure type — measured 1.039 rows per key on the served panel — a filer files several lines per key, so this is NOT unique and the surrogate id is the only unique key. The disclosure date is part of the grain: the same period is re-disclosed on later dates and every version is retained.
| Column | Name | Type | Null | Description |
|---|---|---|---|---|
operation | Operational Status | string | no | ChinaScope's record-operation flag. Every row of the delivered history carries 'A' — the history load is a full snapshot, not a change stream. The vendor's specification defines 'U' (update) and 'D' (delete) for the daily change files; neither value occurs anywhere in the history as delivered. |
id ·PK | Record ID | string | no | Unique record identifier and the primary key of this table — one row per id within each delivery, measured unique in every delivery received as of 2026-08-25, as declared by the vendor. NOT unique across the pooled history: a corrected record returns under the same key in a later delivery, so match on id and keep the newest _known_date for the current state. |
company_id | Company ID | string | no | The resolved ChinaScope entity id of the listed company the disclosed-customer record belongs to. Populated on every row; it is the stable key for joining this issuer to every other Numinor dataset. |
publish_date | Disclosure Date | timestamp | no | The as-of date. The date the announcement carrying this row was published — what the market could actually know, and the column every point-in-time query anchors on. Populated on 100% of rows, spanning 2017-07-13 to 2026-08-19. |
ann_collection_time | Announcement Collected | timestamp | no | The moment ChinaScope first ingested the underlying announcement from CNINFO (巨潮). An operational ingest stamp, not a market event: it is later than the disclosure date for filings collected during ChinaScope's own backfill, so never use it as an as-of. Use Disclosure Date. |
report_start_date | Period Start Date | timestamp | no | First day of the reporting period the disclosed-customer figures cover. |
report_end_date | Period End Date | timestamp | no | Last day of the reporting period the disclosed-customer figures cover — the accounting period, not the disclosure date. Spans 2017-06-30 to 2026-06-30. |
fy | Fiscal Year-End | string | no | The company's fiscal year-end convention (e.g. 12-31). Every row carries the same value (12-31). |
p | Period Length | int | no | Length of the reporting period in months (6 = interim, 12 = full year). |
q | Fiscal Quarter | string | no | Fiscal quarter the period ends in (Q2 for interims, Q4 for annuals). |
y | Fiscal Year | int | no | Fiscal year the reporting period belongs to. |
mkt_code | Market Code | string | no | Exchange code for the listed company's shares — joins to the market dictionary. |
currency | Currency | string | no | Currency the monetary columns on this row are denominated in — joins to the currency dictionary. Every row carries the same value (CNY). |
item_sequence | Line Number | int | yes | Line number of this item within its announcement table, preserving the order the company disclosed it in. |
secu | Securities Code | string | no | The listed company's ChinaScope standard security code, exchange-suffixed (_SH_EQ Shanghai, _SZ_EQ Shenzhen, _BJ_EQ Beijing). |
ticker | Ticker | string | yes | The listed company's plain exchange code — the six-digit stock number without a market suffix. |
entity_orig | Counterparty Name (as reported) | string | yes | The name of the customer, exactly as it appeared in the filing — raw, unstandardised text. Companies often disclose an abbreviation rather than a full registered name, which is why the resolved id is the more reliable join. 114,475 distinct strings. |
entity_id | Counterparty Entity ID | string | yes | The resolved ChinaScope entity id for the customer named on this row — the join key that turns a disclosed name into a trackable entity. 114,475 distinct names as disclosed resolve to 77,231 entities. Organisations resolve against ChinaScope's institution master, individuals against its person master, so the same counterparty is recognisable across companies and over time. Populated on 42% of rows. Blank where the disclosed name could not be matched to a registered entity — commonly private or unregistered counterparties; see the as-reported name column for those rows. |
entity_cat | Customer Entity Type | int | yes | Customer Entity Type — a type marker accompanying the name and id on this row. Coded 1 = natural person, 2 = organisation, 0 = unresolved. |
amount | Amount | number | yes | Amount for this disclosed-customer record. In the currency given by the Currency column. Measured range -5.33m to 16.22trn. What this number measures depends on the Business Type column on the same row: 主要客户 (major customer — the figure is sales to that customer), 应收账款 (receivable aged over one year — the figure is the period-end balance), 预收款项 (advance received — the figure is the period-end balance). Populated on 99.98% of rows. |
ratio | Share of Total | number | yes | Share of Total for this disclosed-customer record. Stated as a PERCENTAGE, not a 0-1 fraction: measured range -34.60 to 139,029.75 across the served history, so a value of 12.5 means 12.5%. A small number of filer outliers sit far above 100 — screen them out rather than assuming a scale change. Negative values occur and are genuine (reversals and credit balances). What this number measures depends on the Business Type column on the same row: 主要客户 (major customer — the figure is sales to that customer), 应收账款 (receivable aged over one year — the figure is the period-end balance), 预收款项 (advance received — the figure is the period-end balance). Populated on 96% of rows. |
typ | Business Type | string | no | Which of the company's disclosed business categories this row belongs to — it governs what the Amount and Share columns on the same row mean: 主要客户 (major customer — the figure is sales to that customer), 应收账款 (receivable aged over one year — the figure is the period-end balance), 预收款项 (advance received — the figure is the period-end balance). |
duration | Ageing | string | yes | Ageing, as disclosed by the company — free text, not a controlled vocabulary. Populated on 7% of rows. |
amount_type | Nature of the Balance | string | yes | Nature of the Balance, as disclosed by the company — free text, not a controlled vocabulary. Populated on 4% of rows. |
prev_amount | Amount, Prior Period | number | yes | Amount, Prior Period for this disclosed-customer record, as ChinaScope defines it. Carried on only 122 rows of 989,766 (0.01%) — present, but too thin to build on, so it is delivered, but not charged for. |
prev_ratio | Share of Total, Prior Period | number | yes | Share of Total, Prior Period for this disclosed-customer record, as ChinaScope defines it. Carried on only 27 rows of 989,766 (0.00%) — present, but too thin to build on, so it is delivered, but not charged for. |
is_related_std | Related Party | int | yes | A yes/no marker ChinaScope sets while reading the announcement, recording whether this disclosed-customer row is flagged “related party”. Coded 1 = yes, 0 = no. Populated on 1% of rows. |
item_part | Business Segment | string | yes | Business Segment, as disclosed by the company — free text, not a controlled vocabulary. Populated on 2% of rows. |
accrual_reason | Reason for Provision | string | yes | Reason for Provision for this disclosed-customer record, as ChinaScope defines it. Carried on only 42 rows of 989,766 (0.00%) — present, but too thin to build on, so it is delivered, but not charged for. |
accrual_ratio | Provision Ratio | number | yes | Provision Ratio for this disclosed-customer record, as ChinaScope defines it. Carried on only 116 rows of 989,766 (0.01%) — present, but too thin to build on, so it is delivered, but not charged for. |
bad_debt_reserves | Bad-Debt Provision | number | yes | Bad-Debt Provision for this disclosed-customer record. In the currency given by the Currency column. Measured range -1.94bn to 106.82bn. Populated on 32% of rows. |
accounting_company | Accounting Entity Name | string | yes | Accounting Entity Name for this disclosed-customer record, as ChinaScope defines it. Carried on only 5 rows of 989,766 (0.00%) — present, but too thin to build on, so it is delivered, but not charged for. |
arrears_reason | Reason for Arrears | string | yes | Reason for Arrears for this disclosed-customer record, as ChinaScope defines it. Carried on only 463 rows of 989,766 (0.05%) — present, but too thin to build on, so it is delivered, but not charged for. |
book_value | Carrying Value | number | yes | Carrying Value for this disclosed-customer record, as ChinaScope defines it. Carried on only 87 rows of 989,766 (0.01%) — present, but too thin to build on, so it is delivered, but not charged for. |
is_accrual_bad_debts_std | Bad-Debt Provision Made | int | yes | Bad-Debt Provision Made for this disclosed-customer record, as ChinaScope defines it. This column is empty on every row of the nine-year history — it is delivered, but not charged for. |
arrears_nature | Nature of Arrears | string | yes | Nature of Arrears, as disclosed by the company — free text, not a controlled vocabulary. Populated on 7% of rows. |
arrears_time_reason | Age of Arrears and Reason Unsettled | null | no | Age of Arrears and Reason Unsettled for this disclosed-customer record, as ChinaScope defines it. This column is empty on every row of the nine-year history — it is delivered, but not charged for. |
relation | Related-Party Relationship | string | yes | Related-Party Relationship, as disclosed by the company — free text, not a controlled vocabulary. Populated on 3% of rows. |
is_list_related_std | Related to the Issuer | int | yes | Related to the Issuer for this disclosed-customer record, as ChinaScope defines it. This column is empty on every row of the nine-year history — it is delivered, but not charged for. |
accounting_company_id | Accounting Entity ID | string | yes | Accounting Entity ID for this disclosed-customer record, as ChinaScope defines it. Carried on only 5 rows of 989,766 (0.00%) — present, but too thin to build on, so it is delivered, but not charged for. |
accounting_company_cat | Accounting Entity Type | int | yes | Accounting Entity Type for this disclosed-customer record, as ChinaScope defines it. Carried on only 6 rows of 989,766 (0.00%) — present, but too thin to build on, so it is delivered, but not charged for. |
file_id | File ID | string | no | Pointer to the original announcement file this row was extracted from. Together with Element ID it lets any number be traced back to the exact place in the exact filing it came from. Included free with the dataset. |
element_id | Element ID | string | no | Pointer to the specific element inside the announcement file this row was extracted from — the finest grain of the audit trail. Included free with the dataset. |
create_time | Created | timestamp | no | Timestamp when the record first entered ChinaScope's store — a vintage/audit marker, not a corporate or filing event date. |
update_time | Updated | timestamp | no | Timestamp when the record was last revised in ChinaScope's store — a vintage/audit marker, not a corporate or filing event date. |
_panel_op | Panel row operation | string | no | Row operation for panel replay — an add, an update, or a delete of the row's key as of this _known_date. A delete marker is how a retracted disclosure is represented; dropping these rows silently keeps retracted records alive. Delivery-structural: never priced, always included. The Matrix evaluation copy is already resolved to a single current view, so it carries _known_date but not this column; the purchased export carries both. |
_known_date | Delivered-on date (transaction time) | timestamp | no | Transaction time — the date this version of the row was DELIVERED to us, as opposed to publish_date, which is when the disclosure became public. Partitions the panel so it can be replayed to any past delivery date. Delivery-structural: never priced, always included. |
·
Sourced as-delivered from ChinaScope, with resolved codes and structural links computed by Numinor. Licensing passes through to you; fields are served exactly as the vendor issues them.
01
Access & FAQ
- How do I buy just a few fields?
- Check the fields you want and you'll see your running subtotal. Select every field and the whole-set price applies automatically. Add them to your basket and check out — this dataset, or fields combined across several.
- Can I evaluate these fields in the Matrix before I buy?
- Yes — load the actual source tables in the Matrix and analyze them with an AI agent (served on the Matrix evaluation lag) to decide what is worth buying before you buy it.
- How is it delivered?
- Apache Parquet over a signed-URL REST API, the same pipe as Construct Data. The free Matrix sandbox serves a time-delayed view for evaluation.
- When is each update available, and how reliable is it?
- Source data refreshes on the ChinaScope cadence and is delivered through the same signed-URL pipeline as Construct Data, with the same manifest/status behaviour. Evaluate freshness yourself in the Matrix before you commit.
- Why are some fields free and others cost thousands?
- Price tracks non-replicability. Resolved codes and structural links are the moat; machine scores and raw text are cheap; identifier keys are free. Figures are priced per table; codes are charged once per dataset.
Still have questions? Contact Sales →