What does data for this category look like?
This category of data comes from the unified budget management system, centralized treasury payment system, accounting system, and asset management system, and is updated annually. Daily output documents include department final account statements, balance sheets, income and expenditure final account statements, final account explanations, and government financial reports. Data fields cover income and expenditure details, asset and liability balances, budget execution difference explanations, and more. The core measurement standard is the Chinese Yuan. The size of a single document varies based on the hierarchy of the affiliated unit.
What constraints do these characteristics impose on the "citation sources and traceability" link?
The annual update feature means the knowledge base does not need frequent incremental synchronization. Only a full update during the annual final account cycle is required. The mixed output of data from multiple systems requires clear marking of the source system for each piece of data during traceability, to avoid confusion between different systems’ statistical standards. The fixed document structure requires traceability to accurately locate specific reports, table page numbers, or explanatory paragraphs, rather than broadly associating with the entire document. Additionally, errors in final account data may lead to returned statements or audit issues. The traceability link must ensure cited content is fully consistent with original data, with no deviations in statistical standards.
How to set the configurations
| Configuration Item | Recommended Value | Basis for This Setting |
|---|---|---|
quoteMaxToken | 800–1200 token | Adapts to the average length of single-page data in department final account documents, avoiding truncation of key policy clauses or data details |
| Similarity Threshold | 0.5–0.7 | Matches the relevance between policies and regulations and final account data, filtering low-relevance non-financial content |
responseData | Includes document path, system source, page number | Meets the requirement to mark the data source system and specific location during traceability |
detail | Enabled | Displays field details of original data, facilitating verification of consistency between final account data and policy requirements |
| Single Recall Limit | Top 3 entries | Controls context length to avoid exceeding the model’s processing limit, while covering core policy basis |
Three common mistakes
- Setting
quoteMaxTokento too small a value causes cited policy basis in responses to be truncated, making full display of source content impossible. This occurs because the setting does not adapt to the single-page data length of department final account documents, truncating key policy clauses or data details. - Knowledge base recall results fail to cover required policy basis, and responses cannot match correct regulatory content. This is caused by setting the similarity threshold too high, filtering out content that meets required relevance levels, or setting the single recall limit too low.
- Traceability information only displays the document name without marking the system source and page number, making data standard verification impossible. This occurs because return parameters for
responseDataare not correctly configured, and the switch for displaying system source and specific location is not enabled.
How to confirm the configuration is complete
- Initiate a query containing specific department final account policy requirements, and check whether complete citation source information is displayed at the end of the response, including document name, system source, and page number.
- Adjust the value of
quoteMaxTokenand verify that cited policy basis in responses is fully displayed without truncation. - Test configurations with different similarity thresholds to confirm all recalled results are policy and regulatory content related to department final accounts, with no irrelevant entries.
- Check the FastGPT v4.17.0 system logs to confirm that traceability information return fields include preset document paths, system sources, and other required content.
Note: The values listed above are common starting points. They should be evaluated against the reader’s own specific samples.
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-28.