What the documents look like
Producer export tax refunds combine the offset of domestic-sale tax against export refunds in one calculation. That combined calculation means inventory procurement and supplier records cannot sit as a static ledger; they serve as a reconcilable source for the aggregation and calculation steps. The documents handled day to day include the exemption, offset and refund declaration detail table, export contracts, the sales detail ledger, and export customs declarations. The three most time-consuming steps are aggregating self-produced exports, calculating the exemption, offset and refund, and handling free-on-board price differences. In this workflow, inventory procurement and supplier records supply the traceable basis that those steps draw on.
Constraints at the workflow routing step
The Form Input node is a user-interaction node. When it triggers, the conversation enters an interaction state and the workflow state is recorded. After the user completes the required information and submits, the node collects the submitted form information and passes it to subsequent 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 "yes" branch. Both nodes can be added repeatedly and both trigger execution.
Where inventory procurement and supplier records involve order writes, document backfill, or external status synchronization, those actions require a separate business interface or a later process. The interaction nodes themselves do not perform them.
Hypothetical paper exercise sample: a declaration detail table excerpt reads "Period March 2024, export goods A, total free-on-board value 120,000 yuan, corresponding customs declaration number X001." A supplier record excerpt reads "Supplier B, supply batch L202403, procurement warehousing date 18 March 2024." The draft handover request to be assessed reads "Please confirm the above batch can be included in this period's exemption, offset and refund aggregation." This request concerns document reconciliation only and carries no authorization or approval record.
Configuration and implementation checks
| Configuration item | Value or check on this page | Basis and explanation |
|---|---|---|
| Form Input node | Collect declaration detail table number, supplier name, batch number, period | The document states the node collects required information and passes it to later nodes |
| User Selection node | Set a "documents complete / pending supplement" branch | The document states the "yes" branch executes according to the user's choice |
| Interaction state check | Workflow state is recorded after triggering | The document states interaction nodes record state |
| Output handoff | Pass form information to a retrieval or judgment node | The document states submitted information passes to later nodes |
| External action split | Order writes, document backfill and status synchronization connect to separate interfaces | The document does not state interaction nodes perform these actions |
| Hypothetical starting value | Period field filled as "March 2024" | Starting point for this paper exercise, compared against the declaration detail table excerpt |
Three common errors
- Treating form submission as business authorization. The submission action only passes information to later nodes. In the sample, "please confirm inclusion in aggregation" is a request awaiting a decision, with no approval record, so it cannot be treated as approved.
- Treating the "documents complete" branch of User Selection as a conclusion that the documents are genuinely complete. That branch only shows the user made a choice. Whether the documents are complete still requires item-by-item comparison with the declaration detail table and supplier record.
- Treating the interaction state record as proof that an external system has synchronized. The document states only that the node records workflow state. Order writes and status synchronization require separate interfaces.
How to verify the setup
- Input the declaration detail table excerpt and the supplier record excerpt from the sample, and compare the three fields of subject, period and batch number. When all three share the same subject, the same period and the same field values, the documents meet the reconcilable condition. When any field is missing, record it as pending verification.
- Input the draft handover request and compare its content against the attached materials. The request mentions "confirm inclusion in aggregation," while the materials contain no authorization or approval record. The request is unsupported and cannot be judged as approved.
- Input an empty-result handoff scenario and check the downstream design against an explicit paper input of []. How the downstream node handles an empty input must be observed according to the actual configuration. No invented rule can be claimed to make a retrieval return an empty result.
This page addresses only producer export tax refunds, inventory procurement and supplier records, and workflow routing. During operational handover, the authorization state of materials, actions and requests must be kept distinct. Retrieval and forms do not constitute authorization to execute.