What the documents look like
Producer export tax processes combine the offset of domestic sales tax with the calculation of export refunds. This combined treatment means product data and selection questions must carry both a domestic-sales basis and an export basis at the same time. The documents handled each month include the exemption, offset and refund declaration detail schedule, export contracts, the sales detail ledger, and export customs declarations. Data originates from the electronic tax bureau, ERP sales records, customs electronic information, and financial accounts. The monthly update cycle matters here because a product question about a specific period depends on which month's declaration detail schedule, ledger entries, and customs records are in scope.
Product data questions ask which refund rate and which price term apply to a given product in a given period. Selection questions ask which declaration path a specific export shipment should follow. Both question types rest on field consistency across the same set of documents. A refund rate stated in one document and a price term stated in a contract must be read against the declaration detail schedule and the customs declaration for the same shipment and the same period.
Constraints at the workflow routing step
The form input node is a user interaction node. When it is triggered, the conversation enters an interaction state, the workflow state is recorded, and the workflow continues only after the user completes the interaction. The node collects the required information the user fills in and passes that information to subsequent nodes after submission. The user selection node is also a user interaction node. When triggered, the conversation enters the interaction state and the workflow state is recorded. When the user makes a selection, the node evaluates that selection and executes the corresponding "yes" branch.
The interaction state is recorded by the interaction nodes themselves. No separate global state-recording switch is documented. Information collected at either node must be explicitly passed to a later retrieval, judgment, or interface node, and the output must be compared item by item against the input. Order writing, document backfill, and external status synchronization require a separate business interface or a later process. The nodes themselves do not perform those actions.
The following hypothetical paper exercise illustrates the routing boundary. It is a constructed example, not a real customer, company, or filing.
Paper exercise sample: For a producer enterprise, in the October 2024 declaration period, the export customs declaration for product code A shows an FOB price of RMB 1,200,000 and an export date of September 2024. The sales detail ledger for the same month records domestic sales revenue of RMB 800,000. The export contract states the price term as FOB. The proposed judgment sentence is: "Product A was declared under the exemption, offset and refund method in September 2024, and the FOB price matches the customs declaration." The pending request is: "Backfill this product data into the declaration detail schedule and synchronize it to the ERP."
Configuration and implementation checks
| Configuration item | Type | Description |
|---|---|---|
| Form input node | Interaction node | Enters the interaction state when triggered, collects required information, passes it to later nodes after submission |
| User selection node | Interaction node | Executes the corresponding "yes" branch after the user makes a selection; verify each branch connection individually |
| Interaction state check | Implementation check | State recording is behavior of the interaction nodes; no separate global state-recording switch is documented |
| Output handoff check | Implementation check | Collected information is explicitly passed to a later retrieval, judgment, or interface node, with output compared item by item against input |
| External action separation | Implementation check | Order writing, document backfill, and external status synchronization require a separate business interface or later process |
| Retrieval scope check | Implementation check | The materials needed for verification must sit in a target retrieval scope the requester can access, or in an explicit manual input |
Three common errors
- Treating information collected by the form input node as completed business verification. The form collects values only. Business verification, approval, database writes, and external synchronization need downstream implementation. In the paper exercise, whether the FOB price in the proposed judgment sentence matches the customs declaration requires comparing the customs declaration text against the proposed sentence. The node's submission action does not itself provide evidence of consistency.
- Treating the "yes" branch of the user selection node as authorized execution. The user selection node evaluates a selection and executes a branch. It does not indicate that approval passed or that authorization is complete. The backfill and synchronization in the pending request are external actions requiring a separate interface. The selection action does not produce a backfill result.
- Extending the same-vector-model requirement for retrieval libraries to external systems. Libraries built on different vector models cannot be associated together. The identifier must be checked first and non-matching libraries excluded. If the verification materials in the paper exercise do not fall within an accessible retrieval scope, the gap must be recorded as a gap. No inference about retrieval results follows from that gap.
How to verify the setup
- Input the proposed judgment sentence and the customs declaration text from the paper exercise. Compare the two fields: the FOB price value and the export date. A contradiction exists only when the same field holds clearly mutually exclusive values. If the dates match but the price term is not stated in one source, the price term portion is unsupported and the evidence gap must be retained.
- Input the pending request. Compare whether the backfill and synchronization actions named in the request have a configured business interface or later process. The condition is met only when an interface node is observed and the output handoff is explicit. A form submission or a selection action alone does not meet the condition.
- Input a paper empty result []. Check whether the downstream design accepts an empty result. Acceptance of an empty result can be checked with an explicit paper input. No claim can be made that a constructed rule's retrieval will necessarily return []. The retrieval check records actual observations and the failure branch. It does not guarantee a first-hit match or full recall.
This page addresses one task only: producer export tax processes, product data and selection questions, workflow routing. During operational handover, the authorization status of materials, actions, and requests must be kept distinct. Retrieval and form submission are not authorization to execute.