What the data for this category looks like
Post-loan ledger data comes from three types of data sources in the core credit system: repayment transaction records, overdue collection records, and post-loan inspection ledgers. The update schedule is daily batch synchronization. Single-record updates trigger when repayment is completed, overdue status changes, or post-loan operations are completed.
The structure of each individual document is fixed, and includes the following fields: customer unique identifier, credit contract number, current due amount, actual repayment amount, overdue days, operation type, and operation time. The unit for amounts is CNY yuan. Time fields use ISO 8601 format. The unit for overdue days is calendar days.
What constraints these characteristics impose on the citation sources and traceability link
The multi-data-source nature of post-loan ledgers requires the traceability system to mark each record with its original data source identifier. This prevents confusion between identical field values from different systems.
The daily batch update schedule generates large volumes of incremental records in a short period. The traceability link must support fast filtering of ledger data for corresponding batches by time range.
The fixed field structure simplifies field mapping. However, customer ID and contract number must be strictly matched as cross-source association primary keys. Otherwise, traceability results will be mismatched.
Additionally, the fixed units for repayment amounts and overdue days require unit consistency checks during traceability. This prevents distortion of traceability data from unit conversion errors.
How to configure the settings
| Configuration Item | Recommended Approach | Rationale |
|---|---|---|
rag_source_filter | Group recalls by data source tags | Post-loan ledgers come from three fixed data sources. Grouped recalls prevent cross-source field confusion |
rag_batch_size | 200 records per batch | Adapts to the incremental data scale of daily batch updates, avoids overload from single-batch recalls |
rag_match_key | ["customerid", "contractno"] | Based on the fixed field structure, use customer ID and contract number as cross-source association primary keys |
rag_time_range_auto_update | Enabled | Adapts to the daily batch update schedule, automatically associates ledger data for corresponding batches |
rag_unit_validate | Enabled | Checks unit consistency for amounts and days, prevents distortion of traceability data |
rag_source_log_enable | true | Enables data source logging to facilitate troubleshooting of citation traceability issues |
rag_citation_hide | Enabled | Hides explicit citation marks, prevents residual mark text in output content |
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 individual analysis. Testing against local samples is recommended before finalizing settings.
Three common mistakes
- Phenomenon: Logs cannot distinguish post-loan ledger records from different data sources, and field values are cross-mixed. Cause:
rag_source_filteris not configured to group recalls by data source tags, leading to unfiltered matching of identical field data from different sources. - Phenomenon: Traceability results output by the large model include forged citation IDs with no corresponding real records from the data source. Cause: The
rag_source_log_enablelogging function is not enabled, making it unable to verify the validity of citation IDs, leading to matching of invalid historical data entries. - Phenomenon: The large model output contains the phrase "Citation Mark: [1]". Cause: The
rag_citation_hideparameter is not configured to disable explicit citation mark output, causing original recall marks to be directly appended to the result.
How to confirm the configuration is correct
- Access the data source management page. Confirm if
rag_source_filterhas the corresponding three post-loan ledger data source tags selected, to verify the grouped recall configuration is active. - Perform a traceability test for a single post-loan ledger record. Check if traceability logs containing data source identifiers and matching primary keys are generated in the logs, to verify the
rag_source_log_enableconfiguration is correct. - Trigger a batch update task. Check if the system automatically associates ledger data for the corresponding time range, to verify the
rag_time_range_auto_updateconfiguration is active. - Generate a test response. Check that the output contains no explicit citation mark phrases, to verify the
rag_citation_hideconfiguration is correct.
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.