What the documents look like
Export tax rebate filing happens after goods leave the country. The work matches tax vouchers against export records. Routine materials include the export exemption and rebate filing form, the export customs declaration, purchase invoices, and foreign exchange receipt vouchers. Sources include the electronic tax bureau, the export rebate filing system, customs electronic information, and the financial ledger. These materials sit in different systems, and their field definitions and issue dates do not line up. During handover, a summary conclusion can travel while the supporting basis does not.
This page addresses one task only: operational permissions and handover management, within knowledge base retrieval and recall. The retrieval node returns reference content, and that reference content can have a length of zero. A retrieval hit means a document entered the reference scope. It does not mean the current operator holds permission to file, modify, or submit.
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. During review, check the vector model identifier first, exclude the non-matching bases, and record the actual observation. Do not run a cross-model search to compare recall differences.
Search modes are semantic retrieval, full-text retrieval, and hybrid retrieval. Semantic retrieval computes similarity by vector distance. Full-text retrieval works by keyword hit. Hybrid retrieval uses both paths and merges them through RRF. RRF is a result fusion process and is not a standalone switch. Minimum relevance takes effect only under semantic retrieval or when result reranking is used. It is a filter threshold and does not perform permission or entity isolation. The reference cap is measured in tokens and controls the maximum amount of content referenced per search.
Hypothetical exercise sample: a finance staff member at a foreign trade enterprise is handing over after departure. The handover list contains three sentences of source material. Sentence one: "Export customs declaration number A-2024-0311, export date 11 March 2024, corresponding purchase invoice number FP-0311, amount consistent with the customs declaration." Sentence two: "Foreign exchange receipt voucher SW-0402 shows arrival on 2 April 2024, at 60% of the customs declaration amount." Sentence three: "The export exemption and rebate filing form has been completed by the previous post holder, status pending review." The handover request to be assessed is: "Confirm that this export batch has completed rebate filing and meets handover conditions."
Configuration and implementation checks
| Configuration or check item | Assumed starting point for this exercise | Reason and comparison method |
|---|---|---|
| Associated knowledge bases | Associate only this enterprise's rebate materials base | Check whether the vector model identifiers of each base match; exclude non-matching bases |
| Search mode | Hybrid retrieval | Run the same question through semantic and full-text separately, compare which materials each path hits |
| Reference cap | Assumed starting point 2000 tokens | Test with filing forms and invoices of different lengths to see whether references are truncated, compared against full material length |
| Minimum relevance | Assumed starting point 0.5 | Label relevant and irrelevant samples first, then compare filtering results under different thresholds |
| Question optimization | Not enabled for now | Compare the original question against the optimized question to see whether the subject was altered |
| Result reranking | Not enabled for now | When candidates are numerous, compare ordering before and after reranking, confirming model and enablement settings |
Three common errors
- Treating a retrieval hit as permission confirmation. The input is the handover request above. The comparison object is the reference content returned by retrieval against the authorization record. The observable result is that the reference content contains only material text and no approval field. The error is concluding that handover conditions are met on this basis.
- Reading a pending-review status as completed filing. The input is sentence three, "status pending review." The comparison object is the field values of pending review and completed. The observable result is that the two values are mutually exclusive. The error is treating pending review as completed filing.
- Reading partial receipt of foreign exchange as full receipt. The input is sentence two, "at 60% of the customs declaration amount." The comparison object is the received amount against the customs declaration amount. The observable result is that the two are unequal. The error is concluding on this basis that the receipt voucher fully covers this batch.
How to verify the setup
- Input the three source sentences and the handover request above. Compare whether the reference content returned by retrieval contains only material text. Observe whether any authorization or approval field appears. The condition is satisfied only when an approval field appears; when none appears, record it as unsupported.
- Input sentence three, "status pending review." Compare whether that field value and the "completed" value are mutually exclusive. Observe whether a pending-review conclusion is obtained. The condition is satisfied only when a pending-review conclusion is obtained and no completion field appears.
- Input the received amount and the customs declaration amount from sentence two. Compare whether the two values are equal. Observe whether a conclusion of insufficient amount is obtained. The condition is satisfied only when the values are unequal and the difference is clear.
For the empty-result scenario, use the paper input [] to check the downstream design. Do not claim that a fictional rule search necessarily returns an empty array. Image retrieval requires a corresponding image input and model capability. Reranking requires an available model and enablement per settings. Optional paths listed in a flow diagram do not mean every path executes on every request. Retrieval and similarity do not handle permission or entity isolation. Business verification, approval, database writes, and external synchronization each require their own downstream implementation.