What the documents look like
Producer export tax processes combine the offset of domestic sales tax with the export refund calculation. This combined method shapes which materials a copy-drafting task can draw on. The working documents for this category are the exemption, offset and refund declaration detail schedule, the export contract, the sales detail ledger, and the export customs declaration. These materials update monthly.
Statements that appear in product or marketing copy, such as export value, goods name, trade method, and transaction price, need to stay consistent with the corresponding fields in those materials. Any statement the materials do not carry remains unverified content and cannot be supplied from the drafting need alone.
Two industry facts matter most for this page. First, because domestic offset and export refund are calculated together, a copy sentence about whether goods were sold only for export can conflict with a ledger that records domestic sales in the same period. Second, the declaration detail schedule, contract, ledger, and customs declaration are separate documents, and a field present in one is not automatically present in another.
Constraints at the interactive forms 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 execution continues after the user completes the interaction. The node collects the information the user fills in and passes it to later nodes. It does not itself act as a business database.
The user selection node is also a user interaction node. When it triggers, the conversation enters an interaction state and the workflow state is recorded. When the user makes a selection, the node evaluates that selection and executes the corresponding branch. It does not act as a personnel directory or a business data selector.
Hypothetical paper exercise sample. A producer enterprise intends to draft a product copy sentence. The available material text consists of three sentences. Sentence one: "The export goods under this contract are self-produced plastic tableware, the export date is March 2025, and the transaction method is FOB." Sentence two: "The exemption, offset and refund declaration detail schedule for the March 2025 period lists export sales value of RMB 120,000 for this batch of goods." Sentence three: "The sales detail ledger for the same month records domestic sales value of RMB 45,000 for this batch of goods." The draft sentence to be assessed is: "This product is entirely for export and does not involve domestic sales."
To check this, compare the draft sentence with the three source sentences. The source text states only that this batch of goods was exported, and it also records domestic sales value for the same month. The universal wording of the draft sentence is not supported by the material. This sample only illustrates the checking method. It does not indicate that any real business activity occurred.
Configuration and implementation checks
| Configuration or check item | Document basis or hypothetical starting point | How to check |
|---|---|---|
| Form input node | Official documentation states it collects filled-in information and passes it to later nodes | Confirm the fields needed for drafting are listed in the form, and that submitted information can be read by later nodes |
| User selection node | Official documentation states it executes a branch according to the user's selection | Confirm both branches exist: continue drafting, and return to supplement materials |
| Interaction state | Official documentation states the node records workflow state and waits for interaction after triggering | Observe the conversation entering the interaction state, and continuing after interaction completes |
| Required-field check | Hypothetical starting point for this exercise: subject name, export period, goods name, and transaction method are set as required | Observe whether the form prompts when one is missing; after completing it, observe whether submission is allowed |
| Downstream division of work | Official documentation states the node does not carry business database functions | Field validation, approval, and write-back are implemented in external systems or later nodes, and are not assumed complete inside the form node |
Three common errors
- Treating a universal statement in the draft sentence as already verified fact. In the sample, the draft sentence says "entirely for export and does not involve domestic sales," while the sales detail ledger records domestic sales value for the same month. The two take mutually exclusive values on the same field, which constitutes a contradiction. The correct approach is to compare the draft sentence against the corresponding fields in the source text and return the unsupported part for supplementation.
- Treating the interaction state as completed approval. The form input node records workflow state and waits for interaction; after the user submits, the information is passed to later nodes. The act of submission does not itself indicate that business approval has passed. Approval needs to be implemented by an external system or a later node.
- Treating a user selection node branch as business data filtering. This node executes a branch according to the user's selection and does not carry entity isolation or permission filtering functions. The selection result only determines the process direction and does not change the range of accessible data.
How to verify the setup
- Enter the three source sentences and the draft sentence from the hypothetical sample above, and compare the draft sentence "entirely for export and does not involve domestic sales" with the sales detail ledger entry "domestic sales value of RMB 45,000." If the system marks the draft sentence as pending verification or returns it for supplementation, this meets the expectation. If it directly outputs the sentence as verified, this does not meet the expectation.
- Enter a form submission request that lacks the transaction method, and compare the required-field setting with the submission result. If the form prompts that this item is missing and blocks submission, and after completing it allows submission and passes it to later nodes, this meets the expectation. This starting point is a hypothetical test setting for this exercise, used to contrast with the missing-item case.
- Enter a user selection request choosing "return to supplement materials," and compare the branch direction with the execution of later nodes. If the process enters the return branch and does not execute the drafting output, this meets the expectation. This result needs actual observation. The documentation does not state a specific error message, so the missing part is recorded as unknown.