What the data for this category looks like
The data used for general comprehensive financial report analysis is primarily sourced from other comprehensive income-related content in annual, semi-annual, or quarterly financial report notes publicly disclosed by listed companies. This data includes both structured detailed datasets and unstructured note text.
The update schedule strictly aligns with the enterprise financial report disclosure cycle, with no temporary incremental updates. The document structure centers on structured tables, paired with accompanying business description text. It includes fields such as detailed other comprehensive income categories, pre-tax amounts, after-tax net amounts, parent company share, and minority shareholder share. All units use a standard monetary measurement, with no mixed units.
What constraints do these characteristics impose on the citation source and traceability workflow
Because the data includes both structured detailed fields and unstructured note text, accurate association of each data item with its original document location and field identifier is required to avoid vague traceability information. The financial report disclosure cycle is fixed, but updates are concentrated. Regular synchronization of the knowledge base is needed to ensure the timeliness of traceability data. There are numerous highly specialized fields, so irrelevant financial report entries must be avoided during recall, while field metadata must be retained to clarify traceability correspondences. Unstructured note text is lengthy, so segment parsing must not break the binding relationship between fields and their context.
Configuration Settings
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
| Recall Count | Top 8-12 entries | Other comprehensive financial report data includes multiple categories of details and notes, which need to cover core related content to avoid missing key traceability information |
| Similarity Threshold | 0.72-0.85 | Financial report terminology is highly specialized. A threshold that is too low will introduce irrelevant financial report entries, while a threshold that is too high will fail to recall relevant note content |
PARSE_SEGMENT_LENGTH | 1200-1500 characters | Financial report note paragraphs are relatively long. Too long segments will lose the binding relationship between fields and context, while too short segments will damage the integrity of structured data |
REFERENCE_MAX_COUNT | 6-10 entries | There are many traceability entries for other comprehensive financial reports. Setting too many will interfere with the readability of the main answer, while setting too few will fail to cover all relevant data |
REFERENCE_SHOW_SOURCE | Enabled | It is necessary to clearly mark the traceable document name, paragraph location and corresponding fields to meet the compliance traceability requirements of financial report analysis |
EXPORT_REFERENCE_FORMAT | With field mapping format | It is necessary to retain the field identifiers of the original data to facilitate subsequent verification of the correspondence between analysis results and original financial reports |
The parameter values provided on this page are common starting points for configuration. Actual values are affected by material form, data volume and business rules. Specific issues require case-by-case analysis, and testing on independent samples is recommended before finalizing.
Three Common Misconfigurations
- Phenomenon: The knowledge base option is empty when calling in version 4.8.22. Cause: The structured JSON file for the other comprehensive financial report was not correctly imported into the specified knowledge base group, or the corresponding knowledge base ID was not bound in the configuration.
- Phenomenon: The number of returned traceability citations is insufficient, or traceability files cannot be downloaded. Cause:
REFERENCE_MAX_COUNTis set too low, or download permission for traceability files is not enabled, resulting in failure to obtain complete traceability data. - Phenomenon: Traceability results do not link to the corresponding financial report fields. Cause: Field metadata was not retained during parsing, causing recalled content to fail to match the original data's field identifiers and making accurate traceability impossible.
How to Verify Correct Configuration
- Upload a structured JSON file of the other comprehensive financial report, and check whether the corresponding fields and document information are successfully parsed and displayed in the knowledge base management interface.
- Initiate a financial report analysis request, and check whether the returned result includes traceability information marked with the document name, paragraph location and corresponding fields.
- Adjust the
REFERENCE_MAX_COUNTparameter, and verify whether the number of returned traceability entries matches the set value. - Export the analysis result, and confirm whether the format and field mapping of the traceability file meet the configuration requirements.
Question material comes from public community discussions. Configuration values are common starting points and should be measured against your own samples. Verified on 2026-09-14.