Source Datav1.0
Fundamentals — Financial Notes
Financial-statement note detail (AR aging, contract assets/liabilities, debt investments, impairments) — the disaggregated balance-sheet notes behind reported fundamentals. Priced per-table (true-name model).
Buy by the field
484 priced fields
Pick the fields you need — priced individually below.
Whole set$6,394.17/mo
Exactly the sum of its fields — no bundle premium, no bundle discount
Pay annually · save 20% — $61,384/yr
ⓘ Take the whole set from the field list below — select everything, add it to your basket, and check out there.
Data due diligence
- Point-in-time: yes
- Carries the disclosure date; restatements preserved.
- Personal data: none
- No personal information.
- Web collection: no
- No web collection; sourced from filings or a licensed feed.
- Generative 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.
Declarations published by ChinaScope. Open the Due diligence tab and sign in to read the full questionnaire.
Fundamentals — Financial Notes
fin_notesSource DataFinancial-statement note detail (AR aging, contract assets/liabilities, debt investments, impairments) — the disaggregated balance-sheet notes behind reported fundamentals. Priced per-table (true-name model).
Daily source stitch · data frontier 2026-10-28
9. Field reference: every column
The full field dictionary: every table and every populated column, with its type and meaning. One real sample row is shown per table.
fin_bs_curr_funds_cat
Table · pick one of 70
Balance-sheet notes: assets
Balance-sheet notes: liabilities & equity
Income-statement (P&L) notes
Other notes
fin_bs_curr_funds_cat
23 columns · 422,465 rows
| Column | Name | Type | Null | Description |
|---|---|---|---|---|
item_orig | Original subject name | string | no | The filer's own as-reported label naming which line-item under monetary funds (货币资金: the cash-and-bank-balances line on the balance sheet) this row breaks out: for example cash on hand (库存现金), bank deposits (银行存款), or other monetary funds (其他货币资金). It tells you, in the company's original wording, exactly which category each figure in this note refers to. |
item_code | Standard subject code | string | no | A standardized code that maps the raw category label to a common monetary-funds sub-category (such as cash on hand, bank deposits, or other monetary funds), so the same category lines up across companies and reporting periods even when firms word it differently. |
end_balance | Ending balance | number | yes | The closing (period-end) balance of this specific monetary-funds category, expressed as an RMB amount for one company and one reporting period. A small share of rows carry negative values; the data does not state why, so treat negatives with caution rather than as normal cash balances. Shows buyers the end-of-period make-up of a company's monetary funds. |
open_balance | Beginning balance | number | yes | The opening (period-beginning) balance of this specific monetary-funds category, expressed as an RMB amount for one company and one reporting period; paired with the ending balance it shows how each category moved over the period. A small share of rows are negative; the data does not state why, so treat negatives with caution. |
operation | Operational Status | string | no | A one-letter record-change flag showing whether this row was added (A), updated (U), or deleted (D), so you can track how the dataset revises over time. |
id | Auto-increment id | number | no | A unique sequential row number that identifies each individual record in this table. |
company_id | Company ID | string | no | The identifier of the listed company that filed this financial statement, so every record can be attributed to a specific issuer (resolvable to that company's full details via ChinaScope's company master). |
publish_date | release date | date | no | The calendar date on which the report was released to the public, which supports point-in-time analysis of when each figure first became available. |
report_start_date | Reporting period start date | date | no | The first day of the accounting period the figures cover (e.g. 2022-01-01). |
report_end_date | Reporting period end date | date | no | The last day of the accounting period covered: the period-end date that the balances and totals are stated as of (e.g. 2022-06-30). |
fy | Financial year end | string | no | The month and day marking the end of the company's fiscal year (e.g. 12-31), identifying its annual reporting calendar. |
p | Reporting period | string | no | The length of the reporting period in months (12 for a full year or 6 for a half-year), which tells you whether the figures are annual or interim. |
q | Financial Quarter | string | no | The fiscal quarter in which the reporting period ends (e.g. Q4 for a full year, Q2 for a half-year), labelling where in the year the figures fall. |
y | Financial Year | number | no | The four-digit fiscal year to which the reported figures belong. |
mkt_code | Securities market code | string | no | A numeric code identifying the securities market or listing board on which the company's shares trade. |
currency | currency | string | no | The three-letter currency code in which this record's monetary amounts are denominated (e.g. CNY for Chinese renminbi). |
create_time | Creation time | timestamp | no | The timestamp when this record was first added to the dataset, useful for tracking data vintage. |
update_time | Update time | timestamp | no | The timestamp when ChinaScope last modified this record. Most modifications do not change a figure (see §7), and a company's restatement arrives as a new row in its next report rather than as a change here. |
entity_id | ID of the invested unit database | string | yes | An identifier for a related or invested entity (for example an investee company) that a line item refers to, which resolves to that entity's full details in ChinaScope's company master; it is often blank where a note carries only a single company-level figure. |
std_company_id | Standard company ID (filer) | string | no | The standard ChinaScope identifier for the filing company: the universal company key shared across SAM, C2C, RFP, Affiliate and SmarTag, so this note schedule joins to the same company's fundamentals, ownership, supply chain and news. It identifies the filer (distinct from entity_id, which resolves a referenced entity such as an investee). |
std_company_code | Standard company code (filer) | string | no | The standard ChinaScope company code for the filing company: the code form of the universal company key, so the filer lines up consistently across ChinaScope's datasets. It identifies the filer, not a referenced entity (see entity_id). |
_known_date | Delivery date | date | no | The date of the ChinaScope delivery this version of the row arrived in; the panel is partitioned by it. It is not the disclosure date (that is publish_date): it is the second date a correction-aware view needs, used to keep each id's latest version delivered on or before your as-of date (§7). Every row of the history carries 2026-04-08, a marker one day before the history's delivery on 2026-04-09. |
_panel_op | Applied change marker | string | no | How this version of the row was applied to the panel: A added, U updated, D deleted. It can differ from the delivered operation flag: a row delivered as an update whose id had never been seen is an insert and is marked A here. To exclude deleted rows, first keep each id's latest version (§7), then drop it if that version is 'D'; dropping 'D' rows alone leaves the earlier versions of a deleted row in place. |
Sample row:
item_orig: 库存现金
item_code: cce_as_1
end_balance: 2471169.62
open_balance: 16112279.52
operation: A
id: 1
company_id: CSF0000000611
publish_date: 2020-08-25
report_start_date: 2020-01-01
report_end_date: 2020-06-30
fy: 12-31
p: 6
q: Q2
y: 2020
mkt_code: 1001
currency: CNY
create_time: 2023-06-03 06:38:10
update_time: 2023-06-03 06:38:10
·
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 before you buy. See the Overview tab for this dataset’s Matrix evaluation lag; “None” means no intentional delay.
- How is it delivered?
- Apache Parquet over a signed-URL REST API, the same pipe as Construct Data. The free Matrix sandbox serves an evaluation snapshot. Its delay, if any, is shown in the Overview tab.
- 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 →
02
Questions This Dataset Comes Up In
Public reference pages answering a question that spans several datasets, this one among them. No account needed.
- Why a join to China A-share company data silently drops rowsEntity resolution in Chinese company data is partial, and the resolved share differs by dataset and by relationship type. An inner join discards exactly the rows that were not resolved, and those rows are not a random sample.
- Which China A-share datasets are point-in-time, and which only look like itA dataset is point-in-time only if it tells you when a figure became public, not just which period it covers. Several widely used China datasets carry the period and not the filing date, which reads as point-in-time and is not.
- Missing, zero, or blank: three different states in China filing dataA real zero, a blank cell the filer left empty, and a line with no row at all are three distinct states in filing data. Collapsing them to one fills a panel with zeros that were never reported.
- Code and unit traps in China A-share dataSentiment where 2 means negative, ownership ratios in two different units inside one dataset, and standardized line items that hide the as-reported label. Each one returns plausible numbers when read wrongly.
- Primary key versus grain: why de-duplicating China filing data deletes real rowsThe column that uniquely identifies a row and the columns that say what the row is about are not the same thing. De-duplicating on the second silently discards real disclosures.
- Daily delivery does not mean daily dataDelivery cadence and data cadence are separate facts. Several China datasets are delivered daily and change semi-annually, and one table inside Affiliate runs a full period behind its siblings.