What the documents look like
Dealer rebate calculation happens after sales close. The core work concerns policy definitions and financial treatment. The data comes from ERP sales records, dealer remittances, contract ledgers, and the finance system. Day-to-day documents cluster into four types: rebate policies, sales achievement tables, reconciliation statements, and red-letter invoices. These facts shape retrieval directly. Rebate policies and contract ledgers define the authorization boundary for a given rebate request. Sales achievement tables and reconciliation statements define the calculation basis. Red-letter invoices define the material state at the offsetting stage. The retrieval step only recalls relevant document fragments as quoted content. It does not perform authorization judgment, approval execution, or database writes.
Constraints at the retrieval step
The knowledge base search node can associate one or more knowledge bases that use the same vector model. Knowledge bases with different vector models cannot be associated together. Verify the vector model identifier, exclude those that do not match, and record what is observed. Do not run a cross-model retrieval to compare missed recalls. Quoted content is output as an array and its length can be 0. The output link still completes when nothing is found. Downstream design can be checked against an explicit paper input of []. The minimum relevance value is a filter threshold. It takes effect only in semantic retrieval or when result reranking is used. It is not a permission or entity isolation mechanism. The same-vector-model requirement for associated knowledge bases does not extend to business registration sites or other external systems.
Hypothetical paper exercise sample: A brand finance user, during a handover period, checks one rebate policy original. The original contains two sentences: "This policy applies to 2025 dealer rebate calculation. Rebate recipients are dealers that have signed an annual dealer agreement. Rebate applications must be submitted within thirty days after the quarter ends, and may enter calculation only after confirmation by both channel sales and brand finance." The draft sentence to be assessed is: "After a dealer submits a rebate application, it may enter calculation without confirmation by both parties." This draft sentence conflicts with the original wording "may enter calculation only after confirmation by both channel sales and brand finance." It is a statement not supported by the original.
Configuration and implementation checks
| Configuration item | Assumed trial starting point | Reason and comparison method |
|---|---|---|
| Associated knowledge bases | One rebate policy base and one contract ledger base | Both bases use the same vector model before they can be associated together; check the identifier first and exclude mismatches |
| Search mode | Hybrid retrieval | Rebate policies contain codes and natural-language clauses; compare semantic, full-text, and hybrid retrieval against test questions |
| Quote limit | Assumed trial starting point of 800 tokens | Test content completeness with policy clauses of different lengths, then compare against larger or smaller values |
| Minimum relevance | Assumed trial starting point of 0.3 | Label relevant and irrelevant samples first, then adjust the threshold; it takes effect only in semantic retrieval or result reranking |
| Question optimization | Enabled | Used for coreference resolution and question expansion; compare the original question with the optimized question and check whether the subject was changed incorrectly |
| Result reranking | Enabled according to settings | Reranking requires a model and is enabled according to settings; it performs a second ordering of candidate texts |
Three common errors
- Treating retrieval recall as authorization execution. The policy original states "may enter calculation only after confirmation by both channel sales and brand finance." A retrieval hit on this clause only means the quoted content was recalled. It does not mean confirmation is complete or calculation is authorized. A pending-review state does not demonstrate that operating permission is absent.
- Treating minimum relevance as a permission or entity filter. This value is a filter threshold. It does not exclude unrelated businesses or unauthorized records. Retrieval is not authorization. Setting 0.3 does not make unauthorized dealer records disappear automatically.
- Treating an empty result or cross-model association as a definite conclusion. Quoted content length can be 0. Do not claim that a fictional rule retrieval necessarily returns []. Knowledge bases with different vector models cannot be associated together. Check the identifier, exclude mismatches, and record what is observed. Do not invent missed recalls or redundant results.
How to verify the setup
- Input the hypothetical original "This policy applies to 2025 dealer rebate calculation. Rebate recipients are dealers that have signed an annual dealer agreement" and the draft sentence "After a dealer submits a rebate application, it may enter calculation without confirmation by both parties." Compare the draft sentence against the original wording "may enter calculation only after confirmation by both channel sales and brand finance." The draft sentence and the original share the same subject, the same period, and the same field, and their values are mutually exclusive. When these conditions are met, judge it as not supported by the original.
- Input the hypothetical original "Rebate applications must be submitted within thirty days after the quarter ends" and a handover request "Please let the rebate application enter calculation directly." Compare whether the request contains evidence of confirmation by both parties. The request carries no confirmation record. When this condition is met, record it as pending verification and preserve the evidence gap.
- Input the paper input [] to check the downstream design. Compare how the downstream handles an empty quoted-content array. Quoted content length can be 0. When this condition is met, confirm that the empty-result link still completes. Do not claim that a fictional rule retrieval necessarily returns [].