What the documents look like
Export tax rebate filing takes place after goods have left the country. The work centres on matching tax vouchers against export information, and the material set is split across several sources: the electronic tax bureau, the export rebate filing system, customs electronic information, and the accounting books. The documents handled day to day are the export tax exemption and rebate filing form, the export customs declaration, purchase invoices, and foreign exchange receipt vouchers. These materials come from different origins and refresh on a monthly and per-batch rhythm, so store service and internal training need a workflow built around documents that do not arrive together and do not share one format.
Two facts shape this page most directly. First, the filing form is a distinct document from the customs declaration, the purchase invoice and the receipt voucher; a set that lists three of the four is not the full set. Second, the matching between vouchers and export records is a business step, and no workflow node performs it. Training material that treats a submitted form as a completed match will mislead staff about where the filing actually stands.
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 it to later nodes. The User Selection node is also a user interaction node with the same interaction behaviour. When the user makes a choice, the node evaluates that choice and executes the "yes" branch. Neither node writes orders, backfills documents, or synchronises external status; those actions need a separate business interface or a later process.
Hypothetical drill sample. A trainer prepares a handover request for a store service session. The source material reads: "Export customs declaration number 2024XXXX, export date 15 March 2024, purchase invoice number INV-0301, amount RMB 80,000, foreign exchange receipt voucher number RC-0310, receipt date 2 April 2024." The draft sentence under review reads: "The rebate filing materials for this shipment are complete and the filing process can begin." In this sample the customs declaration, purchase invoice and receipt voucher are all listed. The export tax exemption and rebate filing form does not appear, and the material does not state whether voucher matching has been completed. The draft sentence claims the materials are complete, and the filing form is the missing item of evidence.
Configuration and implementation checks
| Configuration item | Type | Description |
|---|---|---|
| Form Input node | User interaction | Enters the interaction state when triggered, collects required information, passes it to later nodes |
| User Selection node | User interaction | Executes the "yes" branch after the user makes a choice; verify each branch connection individually |
| Interaction state check | Implementation check | State recording is behaviour of the interaction nodes; no separate global state-recording switch is set |
| Output handover check | Implementation check | Pass collected information explicitly to later retrieval, judgement or interface nodes; compare each output against its input |
| External action split | Implementation check | Order writing, document backfill and external status synchronisation require a separate business interface or later process |
| Hypothetical trial starting point | This drill only | Use the three materials in the sample as input and check whether downstream nodes receive every field, compared against the sample text |
Three common errors
- Accepting the draft sentence "The rebate filing materials for this shipment are complete" at face value. The sample text lists the customs declaration, purchase invoice and receipt voucher. It does not list the export tax exemption and rebate filing form, and it does not state the voucher matching status. Compare the field coverage of the draft sentence against the source text. A missing filing form field means the claim is unsupported.
- Treating the Form Input node's submit action as business authorisation. The node collects required information and passes it to later nodes. It does not complete a filing submission or a tax review. Compare the node output against whether a later interface node carries a separate business authorisation statement. With no such statement, record the gap.
- Treating execution of the User Selection node's "yes" branch as approval. The node executes a branch connection; approval needs its own business implementation. Compare the branch execution record against the approval status field. If the two are not linked, mark the item as pending verification.
How to verify the setup
- Input the sample source text "Export customs declaration number 2024XXXX, export date 15 March 2024, purchase invoice number INV-0301, amount RMB 80,000, foreign exchange receipt voucher number RC-0310, receipt date 2 April 2024" together with the draft sentence "The rebate filing materials for this shipment are complete and the filing process can begin." Compare the completeness claimed by the draft sentence against the material items actually listed in the source text. The export tax exemption and rebate filing form does not appear. The expected result is that the draft sentence is unsupported, and the filing form field must be added before any judgement is made.
- Input the three material fields from the sample and check whether downstream nodes receive every field after the Form Input node is submitted. Compare the node output against the field list in the sample source text. The expected result is a one-to-one field match. If a downstream node lacks receipt voucher number RC-0310, record an output handover gap.
- Input purchase invoice number INV-0301 and receipt voucher number RC-0310 from the sample, and check whether execution of the User Selection node's "yes" branch triggers a filing submission action. Compare the branch execution record against the filing submission record. The expected result is that branch execution does not automatically produce a filing submission, and the two must be checked separately.
Across all three checks, the sample text and the draft sentence are the only evidence in scope. Whether the filing form exists elsewhere, whether voucher matching has been performed, and whether any approval has been granted remain unknown until a document stating each of those facts is supplied. A pending request is not an approval, and an offered option is not an executed action.