源数据v1.0

客户-供应商（披露 · 时点）

Name: 客户-供应商（披露 · 时点）
Creator: ChinaScope

时点客户-供应商披露数据。与「客户-供应商（披露）」同源，但保留供应商的每一次修订及其获知日期，因此按 as-of 读取可还原任一历史日期的在案记录，而不仅是当前状态。9 张表，涵盖客户与供应商权益关联、关联方销售与采购、关联方应收与应付，以及单项重大应收款。按表计价（true-name 模型）。

按字段购买

62 个计价字段

挑选你需要的字段——下方按字段单独计价。

整套$5,218.33/月

恰好等于各字段之和——既不加价，也不打折

按年预付 · 省 20% —— $50,096/年

ⓘ 可在下方字段列表中一次全选，加入清单后直接结算，即可获得整套。

联系销售 →在 Matrix 中探索 →

数据尽调声明

时点数据: yes: Carries the disclosure date; restatements preserved.
个人信息: public-names: Individuals are named, as they appear in public filings or published news.
网页采集: no: No web collection; sourced from filings or a licensed feed.
生成式 AI: no: No third-party generative AI is used; processing is proprietary ML/NLP.

The personal-data values are descriptive, not risk grades: no personal information in any dataset is collected from individuals; all of it is drawn from mandatory public company disclosure or already-published news.

以上为 ChinaScope 发布的声明。完整问卷见“尽职调查”标签页，需登录查看。

客户-供应商（披露 · 时点）

c2c_pit源数据

每日源拼接 · 数据前沿 2026-11-07

字段说明

选择一张数据表，查看各字段的含义、数据类型和示例值。

数据表 · 共 9 张，选择其一

`equity_customer_pit`

47 个字段 · 994,569 行 · 记录粒度（主键）：id

字段	名称	类型	可空	说明
`operation`	操作状态	字符串	否	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` ·主键	记录id	字符串	否	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`	企业id	字符串	否	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`	发布日期	时间戳	否	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`	原始公告发布时间	时间戳	否	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`	报告期起始日期	时间戳	否	First day of the reporting period the disclosed-customer figures cover.
`report_end_date`	报告期截止日期	时间戳	否	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`	财务年结日	字符串	否	The company's fiscal year-end convention (e.g. 12-31). Every row carries the same value (12-31).
`p`	报告期间	整数	否	Length of the reporting period in months (6 = interim, 12 = full year).
`q`	财务季度	字符串	否	Fiscal quarter the period ends in (Q2 for interims, Q4 for annuals).
`y`	财务年份	整数	否	Fiscal year the reporting period belongs to.
`mkt_code`	证券市场code	字符串	否	Exchange code for the listed company's shares: joins to the market dictionary.
`currency`	货币	字符串	否	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 of this item within its announcement table, preserving the order the company disclosed it in.
`secu`	证券代码	字符串	否	The listed company's ChinaScope standard security code, exchange-suffixed (_SH_EQ Shanghai, _SZ_EQ Shenzhen, _BJ_EQ Beijing).
`ticker`	交易代码	字符串	是	The listed company's plain exchange code: the six-digit stock number without a market suffix.
`entity_orig`	原始披露名称	字符串	是	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`	ChinaScope 代码	字符串	是	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: a type marker accompanying the name and id on this row. Coded 1 = natural person, 2 = organisation, 0 = unresolved.
`amount`	金额	数值	是	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 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`	业务类型中文	字符串	否	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, as disclosed by the company: free text, not a controlled vocabulary. Populated on 7% of rows.
`amount_type`	款项性质	字符串	是	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 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 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`	是否存在关联关系	整数	是	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, as disclosed by the company: free text, not a controlled vocabulary. Populated on 2% of rows.
`accrual_reason`	计提理由	字符串	是	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 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 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 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 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 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 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, as disclosed by the company: free text, not a controlled vocabulary. Populated on 7% of rows.
`arrears_time_reason`	欠款时间和未偿还或结转的原因	null	否	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, as disclosed by the company: free text, not a controlled vocabulary. Populated on 3% of rows.
`is_list_related_std`	是否与上市公司存在关联关系	整数	是	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 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 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`	文件id	字符串	否	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`	元素id	字符串	否	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`	创建时间	时间戳	否	Timestamp when the record first entered ChinaScope's store: a vintage/audit marker, not a corporate or filing event date.
`update_time`	更新时间	时间戳	否	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_op	字符串	否	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`	_known_date	时间戳	否	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.

按 ChinaScope 原样交付，已解析代码与结构化关系由 Numinor 计算。许可直接转授予你；字段完全按供应商发布的形式提供。

获取方式与常见问题

我可以只购买其中几个字段吗？: 勾选你想要的字段，即可看到实时小计。选择全部字段时将自动套用整套价格。加入清单后直接结算——无论是本数据集，还是跨多个数据集组合的字段。
购买前，我可以在 Matrix 中评估这些字段吗？: 可以——在 Matrix 中加载真实的源数据表，用 AI 智能体分析，在购买前判断哪些字段值得买。“概览”标签页列出了该数据集的 Matrix 评估延迟；“无”表示不额外延迟。
如何交付？: 以 Apache Parquet 格式通过签名 URL 的 REST API 交付，与构建数据同一通道。免费的 Matrix 沙盒提供评估快照，是否有延迟及延迟天数请查看“概览”标签页。
每次更新何时可用，可靠性如何？: 源数据按 ChinaScope 的频率更新，并通过与构建数据相同的签名 URL 管道交付，具有相同的清单/状态机制。购买前可在 Matrix 中自行评估数据新鲜度。
为什么有些字段免费，有些却要数千美元？: 价格取决于不可复制性。已解析的代码与结构化关系是护城河；机器评分与原始文本较便宜；标识主键免费。数值型字段按表计价；代码在整个数据集内只计一次。

还有疑问？联系销售 →

涉及本数据集的问题

公开参考页面，回答跨多个数据集的问题，其中包括本数据集。无需账户。