What This Category of Data Looks Like
Financial report data for joint-stock banks comes from internal financial report accounting systems and publicly disclosed PDF documents required by banking and insurance regulatory authorities. Official versions are released quarterly, semi-annually, and annually. Documents use a multi-chapter nested PDF format, including consolidated balance sheets, income statements, cash flow statements, supplementary operating indicator tables, risk management descriptions, and other content. Fields include core operating data, asset and liability details, and capital adequacy ratio related values. Units are mostly hundreds of millions of yuan or ten thousands of yuan.
What Constraints These Characteristics Impose on Deployment and Upgrade
Financial report documents have long length and multiple nested chapters, leading to extended single-file parsing time. Adjust the parsing timeout threshold during deployment to avoid task interruptions. Financial reports are updated on a fixed cycle. Adapt the periodic configuration of scheduled synchronization tasks during upgrades to ensure data timeliness. Fields use specific financial indicator naming conventions. The vector database field mapping must match the bank’s internal data standards, otherwise recall accuracy will be compromised. Some data comes from internal systems. Configure intranet access permissions during deployment to secure data transmission.
Configuration Settings
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
PARSE_FILE_TIMEOUT_SECONDS | 600-900 seconds | Full annual financial report PDFs for joint-stock banks have large file sizes, and standard timeout settings cannot complete parsing |
UPLOAD_FILE_MAX_SIZE | 1000-2000 MB | Complete annual financial report PDF files typically exceed 500 MB in size, so large file upload support is required |
RECALL_TOP_N | Top 8-12 entries | Financial reports have many associated fields, so a sufficient number of relevant segments must be recalled to ensure analysis accuracy |
CUSTOM_MODEL_API_BASE | Intranet vLLM service address | Adapt to docker compose deployed vLLM inference services, avoiding public network access restrictions |
MARKER_PDF_API_BASE | In-container Marker service address | Resolve cross-container connection failures for 127.0.0.1 in docker deployments |
DOCKER_BUILD_BASE_URL | Private image repository address | Adapt to bank intranet deployment environments, avoiding delays and security risks from public network image pulls |
The parameter values provided on this page are common recommended starting points for configuration. Actual values are affected by material format, data volume, and business rules. Specific issues require case-by-case analysis. It is recommended to test on your own samples before finalizing values.
Three Common Misconfigurations
- The symptom is a connection failure error returned by marker-pdf calls, with logs showing that 127.0.0.1 is unreachable. The cause is that when deploying with docker, the container intranet address was not used, and the local loopback address was still used to initiate requests.
- The symptom is incorrect configuration of the custom request address when adding a vLLM inference model, leading to inference timeouts or no returned results. The cause is failing to fill in the intranet service address, and mistakenly using a public network address or unmapped local port as the request address.
- The symptom is missing fields or truncated content after parsing large financial report files. The cause is failing to adjust the
PARSE_FILE_TIMEOUT_SECONDSparameter, so file parsing is terminated by the system before completion.
How to Verify Proper Configuration
- Upload a single quarterly financial report PDF, check the parsing logs to confirm the parsing duration does not exceed the configured timeout threshold.
- Initiate a vLLM-based financial report analysis request, check if returned results include structured indicator interpretation content.
- Check the vector database index list to confirm synchronized financial report fields match the preset bank internal data standards.
- Test connectivity to the Marker service in the intranet environment, confirm no connection timeout or access denial prompts appear.
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.