What this category’s data looks like
Financing daily report data draws from four sources: consolidated group financing statements, independent financing announcements from subsidiary companies, internal credit approval documents, and publicly disclosed financing information. The platform generates full or incremental update files daily, covering all financing activity from the previous workday. Documents have two structural parts: a group summary page and subsidiary detail pages. Fields include subsidiary name, financing type, financing amount, financing time, fund provider, and disclosure channel. Some files include consolidated scope explanations. Most files use structured CSV format or PDF with tables. Each daily report includes multiple financing detail entries.
What constraints these characteristics impose on citation sources and traceability workflows
Since data uses a two-level structure—group summary and subsidiary details—traceability requires clarifying the subject level for each citation to avoid mixing consolidated group data and independent subsidiary data. Daily updates mean traceability workflows must filter redundant historical files, only linking to the latest data from the current day. Multi-source data requires labeling each citation with source type to distinguish internal documents and publicly disclosed information. Financing amount fields do not use uniform units, so unit matching must be verified during traceability to prevent errors where amount values do not align with their units.
How to configure settings
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
recall count | 15-20 entries | The financing daily report includes group summaries and details from multiple subsidiaries, requiring coverage of all critical items |
similarity threshold | 0.72-0.85 | Financing-related terminology is highly specialized, requiring filtering of low-match irrelevant recall results |
segment length | 800-1200 characters | Each financing detail entry contains multiple fields, avoiding truncation that would cause loss of traceability information |
SOURCE_TAG_ENABLE | Enabled | Each citation must be labeled with source file name and corresponding subsidiary entity |
RECALL_FILTER_BY_UPDATE_TIME | Only retain files updated in the last 24 hours | Financing daily reports are updated daily, requiring exclusion of redundant historical data |
PARSE_FILE_AUTO_TAG | Tag subsidiaries by filename prefix | Bulk-uploaded daily report files use the naming format subsidiary name_financing daily_report_date, enabling automatic association of traceability subjects |
The parameter values provided on this page are common starting points for configuration setup. Actual values are affected by material format, data volume, and business rules. Specific issues require case-by-case analysis, and it is recommended to test against your own samples before finalizing settings.
Three common configuration mistakes
- Symptom: Citation results returned via API do not include source file name or subsidiary identifier. Cause:
SOURCE_TAG_ENABLEis not enabled, or the automatic subject tagging rule by filename is not configured. - Symptom:
quote type errorerror is triggered. Cause: The referenced field format does not meet requirements, such as mixing text and numeric fields, or failing to specify the correct source file identifier. - Symptom: The large language model output cites financing data from a non-target date. Cause:
RECALL_FILTER_BY_UPDATE_TIMEis not set to only retain files from the last 24 hours, or the configured time range exceeds reasonable limits.
How to confirm configuration is correct
- Upload a test financing daily report file, and check in the knowledge base preview interface whether parsed entries are automatically labeled with subsidiary name and source file name.
- Submit a test query, such as "What was the financing situation of XX subsidiary last month", and check whether the citation list below the answer includes the corresponding source file and specific field information.
- Call the API to retrieve the answer result, and check whether the returned
source_infofield contains complete traceability information such as file name, subsidiary name, and update time. - Adjust the similarity threshold to below 0.7, submit the same test query, and confirm that low-match irrelevant entries are not recalled, verifying that the threshold configuration takes effect.
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.