What the documents look like
Producer export tax refunds combine the offset of domestic sales tax with the refund calculation. That difference shapes the material set for order fulfilment and after-sales questions: the workflow must cover both the domestic sales line and the export line at the same time. The primary documents for this page are the exemption, offset and refund declaration detail table, the export contract, the sales subsidiary ledger, and the export customs declaration. These come from the electronic tax bureau, ERP sales, the finance ledger, and customs electronic information respectively, and they update monthly. Workflow routing for order fulfilment and after-sales questions has to align export contract terms, customs declaration details and the sales subsidiary ledger month by month, then carry the field definitions of the declaration detail table forward.
A concrete difference from foreign-trade export refund work is that the producer category merges the domestic offset and the refund into one calculation rather than treating them as separate streams. The practical consequence is that a question about one order can require evidence from four sources before any answer is drafted. The monthly update cycle means the month field matters in every comparison.
Constraints at the workflow routing step
The form input node is a user interaction node. When it triggers, the conversation enters an interaction state, the workflow state is recorded, and after the user completes the required fields and submits, the collected information is passed to later nodes. The user selection node is also a user interaction node. When the user makes a choice, the node evaluates that choice and executes the corresponding branch. Both nodes can be added repeatedly and both trigger execution.
Routing for order fulfilment and after-sales questions therefore has two landing points. When the task requires collecting fields such as customs declaration number, contract number or month, the form input node is the collection point. When the task requires choosing among several handling paths, the user selection node is the branch point. The interaction state record is behaviour of the node itself; no separate global state switch is described in the supplied documents.
Retrieval results and submitted forms do not constitute authorization. Order writes, document backfill and external status synchronisation require a separate business interface or a downstream process. A pending request is not approval, and an offered option is not execution.
Hypothetical paper exercise sample: export contract HT-2024-08 specifies a free-on-board price of 1,000,000 for a given model. Customs declaration BG-2024-08 corresponds to the same contract number. The sales subsidiary ledger for that month records export sales of 1,000,000 for that contract. The exemption, offset and refund declaration detail table for that month shows 1,000,000 in that contract's column. One draft sentence awaiting review reads: "The customer asked whether this order has completed the refund; reply that it is completed." That sentence does not state the refund approval status, so it is unsupported by the material.
Configuration and implementation checks
| Configuration or check item | Purpose on this page | Basis and boundary |
|---|---|---|
| Form input node | Collect contract number, customs declaration number, and month | Official description: triggers interaction state; submitted information passes to later nodes |
| User selection node | Choose between the fulfilment query path and the after-sales answer path | Official description: executes the corresponding branch after the user makes a choice |
| Interaction state check | Confirm the conversation enters interaction state and the workflow state is recorded | Interaction state recording is node behaviour; no separate global switch is described |
| Output handover check | Pass collected form information explicitly to a later retrieval or judgement node | Compare node output with node input item by item; record missing fields as gaps |
| External operation separation | Order writes, document backfill, status synchronisation | Requires a separate business interface or downstream process; forms and retrieval do not constitute authorization |
| Empty result handover check | Use a paper input of [] to check the downstream design | Do not claim that a fictional rule retrieval necessarily returns an empty result |
Hypothetical starting point for this exercise: set the month field as required. The reason is that the materials on this page update monthly and must align with the declaration detail table month. The comparison method is to check whether the same contract number shows a consistent month across the contract, the customs declaration, the sales subsidiary ledger and the declaration detail table. This starting point is not an official default value.
Libraries built on different vector models cannot be associated together. Check the identifier first and exclude those that do not match; do not run cross-model retrieval to compare missed recall. A relevance score does not perform permission or entity isolation.
Three common errors
- Treating a retrieval hit as evidence that the refund is complete. Input: a retrieval request for contract HT-2024-08. Comparison: the retrieved content against the refund approval status field. Observable result: when the retrieved content does not contain the approval status, the draft sentence is unsupported.
- Treating form submission as authorized execution. Input: the contract number and month a user fills in and submits at the form input node. Comparison: the submission action against the order write and document backfill actions. Observable result: after submission, a downstream interface or process is still required to carry the action out.
- Treating a user selection branch as automatic judgement. Input: the choice a user makes at the user selection node. Comparison: the selected branch against the expected handling path. Observable result: branch connections must be verified one by one; automatic judgement is not assumed.
How to verify the setup
- For the draft sentence "The customer asked whether this order has completed the refund; reply that it is completed", the input is contract HT-2024-08, customs declaration BG-2024-08 and the declaration detail table record for that month. The comparison is whether the material states the refund approval status. When the material does not state it, the sentence is judged unsupported and the evidence gap is retained.
- For the form input node, the input is the three required items — contract number, customs declaration number and month — filled in and submitted. The comparison is the fields received by later nodes against the fields that were filled in. The condition is satisfied when they match item by item with nothing missing; missing fields are recorded as gaps.
- For empty result handover, the input is a paper retrieval result of []. The comparison is the downstream node's design for handling an empty result. The condition is satisfied when the downstream node can explicitly accept the empty value and does not perform an external write. Do not claim that this retrieval necessarily returns an empty result.
A relevance score is not a category, entity or permission filter, and it does not by itself exclude unrelated businesses or unauthorized records. Retrieval is not authorization.