What the data for this category looks like
The data used for other comprehensive financial report analysis comes from the other comprehensive income-related modules in annual and semi-annual financial reports publicly disclosed by enterprises. Annual reports are released within 4 months after the end of the fiscal year. Semi-annual reports are released within 2 months after the end of the half-year. Some enterprises also include relevant details in quarterly reports. Most documents are in PDF format. They contain other comprehensive income items and accompanying notes in the consolidated income statement and statement of changes in owner's equity. Fields include the amount of each detailed other comprehensive income item, after-tax net amount, prior period adjustment amount, and more. The disclosure unit is usually Renminbi yuan or ten thousand yuan.
What constraints do these characteristics impose on HTTP interfaces and external systems
The single document volume of data in this category is large. Data must be pulled from public financial report websites or uploaded as local files. HTTP interfaces must support large file upload or remote URL pulling capabilities. Data update frequency is fixed and the cycle is long. Interfaces must support scheduled trigger call configurations. There are many field dimensions and detailed levels. Interface parameters must support specifying the extraction field range. Different enterprises use different disclosure units. Interface returns must carry unit information or support unit conversion configurations. Minor differences exist in financial report document formats. Interfaces must integrate structured parsing rules to adapt to the disclosure formats of different enterprises.
How to Configure
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
PARSE_FILE_TIMEOUT_SECONDS | 600 seconds | Other comprehensive financial report files usually contain multi-page structured content, which takes a long time to parse. 600 seconds covers most scenarios |
EXTRACT_FIELD_WHITELIST | ["total other comprehensive income","after-tax net amount details","prior period adjustment amount"] | This category focuses on core other comprehensive income-related fields. Limiting fields reduces invalid data returned |
SOURCE_DATA_UNIT | Auto-detect | Different enterprises use different financial report disclosure units such as yuan and ten thousand yuan. Auto-detection adapts to multi-source data |
UPLOAD_FILE_MAX_SIZE | 50 MB | A single annual financial report PDF usually does not exceed 50 MB. Exceeding this size causes interface timeouts |
API_RETRY_TIMES | 3 times | Pulling financial report data may fail due to temporary fluctuations on external financial report websites. Retrying improves success rates |
WEBHOOK_TRIGGER_MODE | Triggered by disclosure cycle | The data update frequency for this category is fixed. Scheduled triggering is more efficient than real-time calls |
The parameter values provided on this page are common starting points for configuration. Actual values are affected by material format, data volume and business rules. Specific issues require individual analysis. It is recommended to test on your own samples before finalizing settings.
Three Common Misconfigurations
- Interface calls return
403 Forbiddenorconnection timeouterrors. This occurs because no data source access proxy is configured, preventing public financial report data from being pulled in some regions. - Interface returns missing financial report data fields or incorrect formatting. This happens because
EXTRACT_FIELD_WHITELISTis not configured, or the field mapping rules do not match the actual financial report structure. - After configuring
ONE_API_LINK, the interface fails to forward requests normally. This is because the proxy address was not correctly filled in the FastGPT source code, or key verification was not completed.
How to Confirm Proper Configuration
- A test financial report PDF is uploaded. The fields returned by the interface are checked to confirm they match those configured in
EXTRACT_FIELD_WHITELIST. - The interface is called to pull public financial report data. The returned results are checked for correct unit information, to verify that the
SOURCE_DATA_UNITconfiguration takes effect. - A scheduled trigger call is simulated. The interface is checked to confirm it executes according to the preset cycle, verifying that the
WEBHOOK_TRIGGER_MODEconfiguration is correct. - Interface call logs are checked. Error codes such as
413 Request Entity Too Largeor403 Forbiddenare confirmed to be absent, to verify that theUPLOAD_FILE_MAX_SIZEand proxy configurations take 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.