What the documents look like
Work in this category centres on four document families: foreign-exchange receipt advices, trade contracts, invoices and foreign-exchange business registration materials. Together they point at the authenticity of foreign-exchange funds and the underlying trade background. This differs from letter-of-credit document examination, which reviews a full document set. In order fulfilment and after-sales answering, finance staff, bank relationship managers and foreign-exchange specialists check the counterparty, the amount and the trade-background statement for a given receipt, then respond to customer follow-up questions about settlement progress and directory status. Materials update per transaction and per month. The retrieval step needs the contract, invoice and receipt advice for the same transaction to be recalled together.
The knowledge-base search node can associate one or more knowledge bases that use the same vector model. Knowledge bases built on different vector models cannot be associated together. Before retrieval, check the vector model identifier, exclude anything that does not match and record the observation; do not run cross-model retrieval to compare missed recalls. Quoted content is output as an array and its length may be 0, so the output path still runs when nothing is found. An empty result can be checked against downstream design using the paper input []; do not claim that a fabricated rule makes retrieval return [] in every case. Minimum relevance takes effect only in semantic retrieval or when result reranking is used, and it is a filter threshold rather than a final ordering rule. Retrieval and similarity scores do not perform permission or entity isolation, and the same-vector-model requirement for associated knowledge bases does not extend to business-registration websites or other external systems. RRF is a result-fusion step inside hybrid retrieval and is not described as a switch. Image retrieval requires a corresponding image input and model capability, and reranking requires a model enabled according to settings. Optional paths shown in the overall document flow diagram do not mean every request executes all of them.
Constraints at the retrieval step
A hypothetical drill sample is used below. The material text reads: "Company A submitted export contract HT-0310 on 10 March 2026; the contract amount is USD 80,000; the signing parties are Company A and Company B. On the same day, receipt advice SW-0310 shows the payer as Company B for USD 80,000. In the foreign-exchange business registration materials, the status of this transaction is registered." The draft sentence to be assessed is: "This receipt of Company A has completed settlement and the customer can be told that the settled funds have arrived." The materials do not state a settlement-completed field, so this draft sentence is not supported.
Two further constraints follow from the same documents. First, a pending-review status in registration materials is a status field only; it does not show that Company A lacks operating authority. Signing, reaching cooperation and contract effectiveness are three distinct facts. Second, when the contract amount and the receipt amount are both USD 80,000, that is consistency within the same field. When a draft sentence claims settlement completion and the materials carry no such field, record it as unsupported and keep the evidence gap open rather than calling it a contradiction.
Configuration and implementation checks
| Configuration item | Value or check action for this sample | Basis and comparison method |
|---|---|---|
| Associated knowledge bases | Associate only knowledge bases using the same vector model | Check the vector model identifier, exclude non-matching ones and record the observation |
| Search mode | Run semantic, full-text and hybrid retrieval on the sample question | Compare per test question; do not presume one mode suits all materials |
| Reference upper limit | Measure the contract and receipt fragments to be quoted under the chosen model, then set a trial limit | Compare completeness against a shorter setting; only excerpts are available and full text length is not provided |
| Minimum relevance | Label relevant and irrelevant fragments in the sample first, then adjust the threshold | Takes effect only in semantic retrieval or result reranking |
| Question optimisation | Compare the original question with the optimised question | Check whether the subject was altered and confirm the coreference resolution result |
| Output references | Record the length of the reference array | Length may be 0 and the path still runs |
Three common errors
- Treating a retrieval hit as authorisation. After entering the sample question, if the quoted content contains the contract and the receipt advice, this only shows that recall succeeded. Whether settlement is complete and whether the customer may be answered require downstream business verification; the retrieval result does not constitute authorisation or approval.
- Treating pending review as missing permission. If the registration materials show the transaction status as pending review, this is only a status field and does not show that Company A lacks operating authority. Signing, reaching cooperation and contract effectiveness are three separate facts.
- Merging different fields into a contradiction. In the sample, the contract amount and the receipt amount are both USD 80,000, which is consistency within one field. If a draft sentence claims settlement completion while the materials carry no such field, record it as unsupported rather than as a negation or conflict.
How to verify the setup
- Enter the sample material text and the draft sentence, then compare "settlement completed" in the draft against whether a settlement-completed field exists in the materials. Expected observation: when the materials do not state that field, the output is marked unsupported, the evidence gap is preserved, and no authorisation or effectiveness clause is invented.
- Enter the sample question, then compare the contents of the reference array against the contract and receipt advice text. Expected observation: quoted content matches the original and allows the counterparty and amount to be checked. If the reference array is empty, downstream handles it as an empty result; do not claim retrieval necessarily hits.
- Enter the proposed reply "Company B is the seller under this contract", then compare the signing parties in the contract against the payer in the receipt advice. The original names both Company A and Company B and identifies Company B as payer, without stating buyer or seller roles. The seller claim remains to be verified; the payer does not yield the seller role, and the retrieval score is not used to judge that role.
These checks describe expected observations only. No test, deployment, approval, refund or other business action is claimed to have occurred.