What the data for this category looks like
Financial report data in professional service scenarios comes primarily from exchange public disclosure platforms, professional financial databases, and official listed company announcements. Data updates follow fixed regulatory disclosure schedules. Annual and quarterly reports are released at required fixed timestamps, while temporary announcements are updated alongside major operating events. Documents contain structured financial indicator tables, business operation notes, and management discussion content. Core fields include attributable net profit, return on net assets, earnings per share, and others. Common units are RMB yuan, percentage, and operating multiples.
Constraints imposed by these characteristics on citation source and traceability
The mixed structured and unstructured nature of financial report data means citation traceability must mark both the cell position of structured tables and the chunk range of unstructured paragraphs. Fixed disclosure schedules create version differences, so traceability must link data disclosure timestamps to the knowledge base’s synchronized version to avoid cross-version citation confusion. Precision requirements for large financial fields mean traceability must retain complete original units and decimal places, without arbitrary truncation. Professional needs for cross-source cross-verification require traceability to record whether data comes from exchange public disclosures or third-party professional databases, to support compliance checks.
Configuration Settings
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
recall count | top 8-12 | Financial reports have relatively large chunked content. Excessive recall will exceed context limits, while insufficient recall cannot cover complete financial analysis logic |
maxContext | 8000-12000 characters | Financial report analysis requires integrating multiple chunked contents, so this value must match the average total chunk length of a single financial report |
citation display toggle | enabled | Professional service scenarios require clear traceability information to support report credibility and compliance |
citation format | [Source: {knowledge base name}, Chunk ID: {chunkId}, Disclosure Date: {date}] | Meets compliance traceability format requirements for professional service reports |
similarity threshold | 0.75-0.85 | Financial report terms are highly specialized, so high matching accuracy is needed to avoid irrelevant content recall |
re-ranked return count | top 4-6 | Perform secondary screening on recall results to retain chunked content most relevant to the financial report analysis theme |
The parameter values provided on this page are conventional recommendations used as a starting point for configuration. Actual values are affected by material form, data volume, and business rules. Specific issues require case-by-case analysis, and it is recommended to test on your own samples before finalizing.
Three Common Configuration Errors
- A
quote type errorerror occurs, prompting abnormal variable format. Cause: The variable placeholder format specified in thecitation formatconfiguration item was not followed during filling, or a custom variable not defined in the knowledge base was referenced. - In FastGPT v4.6.7, setting the
citation limitto 1500 still retrieves citation content exceeding this length. Cause: ThemaxContextparameter was not adjusted synchronously, or the knowledge base chunk size was set to 5000 tokens. Single chunk content exceeds the citation limit without truncation, and this version does not automatically verify the matching relationship between chunks and the citation limit. - The reply does not include the address information of the cited file. Cause: The
citation display togglewas not enabled, or the file address placeholder was not added in the citation format configuration, resulting in missing traceability information.
How to Confirm Configuration Is Complete
- Upload a single financial report sample, trigger knowledge base retrieval, and check if the reply includes traceability information matching the configured format.
- Adjust the
similarity thresholdto verify if retrieval result relevance meets expectations, with no irrelevant financial report content included. - Modify the
citation formatconfiguration to confirm that traceability content in the reply is synchronously updated to the new format. - View the knowledge base parsing log to confirm that chunk numbers and disclosure date fields have been correctly extracted and associated.
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.