What the documents look like
Producer export tax refunds combine the offset of domestic-sales tax with the refund calculation. That structure means product data and selection questions must work across four document types at once: the refund declaration detail schedule, the export contract, the sales subsidiary ledger, and the customs export declaration form. Their field definitions do not match. The declaration detail schedule records export sales value and the non-exempt, non-deductible tax amount under the refund offset calculation basis. The sales subsidiary ledger records revenue and cost under the accounting basis. The customs declaration form supplies the free-on-board value and the commodity code. The export contract supplies the trade term and the quantity agreement.
Model connection and configuration must keep these bases traceable when a question cites the materials. A figure from the accounting ledger is not the refund offset tax basis. The materials update monthly; this page does not derive any batch or real-time synchronization mechanism from that frequency.
Constraints at the model connections step
Model connection depends on AI Proxy. Both the App and any Admin service that reuses App/Service configuration must set AIPROXY_API_ENDPOINT and a non-empty AIPROXY_API_TOKEN. Missing either item causes startup validation to fail. AIPROXY_API_ENDPOINT takes the service root address and does not append /v1. Model capabilities are checked separately against the inputs the application needs; multimodal input, tool choice, and thinking configuration are each verified on their own.
A relevance score from retrieval does not carry permission or entity-isolation duties, and the retrieval action itself is not authorization. Libraries that use different vector models cannot be jointly associated; the vector model identifier is checked first and non-matching libraries are excluded.
Hypothetical paper exercise: a producer export enterprise's March 2026 refund declaration detail schedule states "export sales value 1,200,000 yuan, non-exempt and non-deductible tax amount 24,000 yuan." The sales subsidiary ledger for the same period states "main business revenue 1,180,000 yuan." The export contract specifies "FOB Shanghai, quantity 5,000 units, shipment period March 2026." The proposed sentence is "the enterprise's March export sales value is 1,180,000 yuan." Checking requires comparing the value for the same field in the same period. The schedule and the ledger use different bases, so the two figures cannot be declared contradictory on that ground alone.
Configuration and implementation checks
The table lists only settings or implementation checks that the official documents state, tied to this page's main task. The values are hypothetical starting points for this paper exercise, chosen for comparison against documented ranges or adjacent settings. They are not official defaults.
| Configuration item | Hypothetical starting point | Reason and comparison object |
|---|---|---|
AIPROXY_API_ENDPOINT | Enter the AI Proxy service root address | Documented requirement: do not append /v1; compare with a path-appended form |
AIPROXY_API_TOKEN | Enter a non-empty token matching the server | Documented requirement: must not be empty; compare with an application API key |
| Model capability check | Verify each input the question needs | Multimodal and tool choice verified separately; compare with the built-in model description |
| Retrieval library vector model identifier | Record the vector model each library uses | Libraries on different vector models cannot be jointly associated; compare with a same-model library |
| Probe interval | Hypothetical start of 30 minutes | Documented range 5 to 60 minutes as an integer; compare with boundary values |
| Retry determination | Hypothetical start of at most 4 attempts per round | Documented: up to 3 retries after the first failure; compare with attempt count |
Three common errors
- Treating the accounting-basis figure in the sales subsidiary ledger as the refund offset export sales value. Input is the ledger figure; the comparison object is the same field for the same period in the declaration detail schedule. The two bases differ, and equating them directly hides the basis difference.
- Using a relevance score to exclude unrelated business or unauthorized records. Input is the returned score; the comparison object is the permission determination basis. A score does not carry permission or entity-isolation duties.
- Jointly associating libraries that use different vector models. Input is the vector model identifier of each library; the comparison object is whether the identifiers match. When they differ, the only step is to exclude the non-matching library and record the observation.
How to verify the setup
- For the hypothetical sample's proposed sentence, input the declaration detail schedule text and the ledger text, and compare the value and basis statement for the same field in the same period. A contradiction exists only when both sources give explicitly mutually exclusive values for the same field. A different basis, or evidence covering only a related stage, is recorded as unsupported or pending verification.
- For the retrieval library configuration, input each library's vector model identifier and compare whether the identifiers match. Joint association is possible only when they match. When they differ, exclude the non-matching library; do not run a cross-model retrieval to compare missed recall. For an empty result, check the downstream design against an explicit paper input of
[]. - For model connection, input the configured values of
AIPROXY_API_ENDPOINTandAIPROXY_API_TOKEN, and compare whether the endpoint is the root address and whether the token is non-empty and matches the server. Both conditions must hold for startup validation to pass. When either is missing, startup validation fails, which is a failure branch requiring the configuration to be completed.
A pending review does not demonstrate a lack of operating permission. Signing, reaching cooperation, and contract effectiveness are three distinct facts. A quotation validity period does not indicate a supply period. The materials needed for the check must sit within an accessible target retrieval scope or an explicit manual input; when absent, record the gap.