What the documents look like
Producer export tax treatment combines the offset of tax on domestic sales with the refund calculation. This differs from export refund handling at trading companies, and it shapes what an operating review can and cannot conclude from a monthly document set.
Four document families carry the review. The export tax offset and refund declaration detail table records the declared offset and refund amounts by line. The export contract records settlement terms. The sales subsidiary ledger records revenue recognition. The customs export declaration records the free-on-board value. For a monthly review, these four must correspond: the free-on-board value on the customs declaration, the revenue entry in the sales subsidiary ledger, the settlement terms in the export contract, and the offset and refund amount in the declaration detail table. A difference in any one of these carries into the monthly aggregate. The stated update frequency is monthly, so this page does not describe daily or per-shipment synchronization.
For tool calls and plug-ins, this means a tool description must state which document supplies the input, which field is used, and which monthly scope applies. Tool parameters split into fixed parameters for system modules and configurable parameters for plug-ins. A parameter description is not an execution guarantee. When a required parameter has no suitable value in context, the model may not call the tool, and the interaction must guide the user to supply the value before the actual request content is checked.
Constraints at the tool calls step
Tool calls depend on three pieces of information: the tool description, the parameter description, and whether each parameter is required. A tool with no parameters is judged for execution from its description alone. For a tool with parameters, when no parameter is required the model may call the tool even without a suitable value in context, and it may fabricate a parameter value. When a parameter is required and no suitable value exists in context, the model may decline to call the tool; prompt wording can guide the user to provide the value.
In advanced orchestration, available tools are connected to the tool call module, and a connected tool automatically separates tool input from ordinary input. The description can be edited so that the call timing becomes more precise. The documentation advises starting with a small number of tools and tuning before expanding.
The tool call termination node attaches after a tool. When workflow execution reaches it, the current tool call ends by force: no further tools are called and the AI does not summarize the tool results. The custom variable node extends tool variable input, so a node that is not treated as a tool parameter can still be given a parameter description and be called, along with the workflow that follows it. These are existing node behaviors. They do not substitute for business authorization, approval, or database writes.
Hypothetical paper exercise sample. An export producer files its July 2025 offset and refund declaration. The sales subsidiary ledger records one export revenue entry. The export contract states telegraphic transfer as the settlement method. The customs export declaration shows a free-on-board value equal to the contract amount. The corresponding line in the offset and refund declaration detail table has been filled in. The draft sentence under review reads: "This export transaction already meets the conditions for the offset and refund declaration and can be submitted directly." The request under review is to submit this draft sentence together with the four documents for review.
Configuration and implementation checks
| Configuration item | Setting or check for this page | Correspondence with the sample |
|---|---|---|
| Tool description | State the input document name, field, and monthly scope | The four document names and the July 2025 scope |
| Tool parameters | Separate system module fixed parameters from plug-in configurable parameters | Declaration detail table line, customs declaration free-on-board field |
| Required parameters | Check whether the actual request carries the needed value | Whether contract amount and customs declaration amount agree in the sample |
| Tool connection | Connect tools to the tool call module in advanced orchestration, tune a small set first | Connect only the tools this task needs |
| Tool call termination | Attach after a tool to end the call without an AI summary | Whether the actual workflow ends after review is a process decision |
| Custom variable | Add a description for a node not treated as a tool parameter | Add one if the sales subsidiary ledger node must be called |
Hypothetical trial starting point: set the monthly scope in the tool description to "2025-07". The reason for this choice is the declaration period of the sample. The comparison object is the date range recorded in the sales subsidiary ledger and the customs declaration. This starting point is a setting for this paper exercise, not an official default value.
Three common errors
- Writing a tool description as a general statement without the input document and field. Check: read the tool description text and compare it against the four document names and fields in the sample. If no document name or field name appears in the description, the description does not support the call decision.
- Treating a parameter description as an execution guarantee. Check: read the parameter description text and the actual request content. If the description states a value is required while the actual request lacks that value, the interaction must supply it and the request must be rechecked. The call cannot be treated as complete.
- Treating the tool call termination node as completed business approval. Check: compare the process record after the termination node with the authorization state of the request under review in the sample. If the termination node has executed while the review request remains pending, the termination ended the tool call only and the approval state is unchanged.
How to verify the setup
- For the sample draft sentence, "This export transaction already meets the conditions for the offset and refund declaration and can be submitted directly," the input is the four source documents and the draft sentence. Compare "already meets" in the draft with the declaration status field actually recorded in the documents. If that field is pending review or is not recorded, the draft sentence is unsupported and the evidence gap must be recorded.
- For the correspondence between the contract amount and the customs declaration free-on-board value in the sample, the input is the settlement terms in the export contract and the free-on-board field on the customs declaration. Compare the two amounts and their currencies. If they agree, the sample has no internal amount discrepancy. If they disagree, mark the item as pending verification rather than as a negative finding.
- For the authorization state of the request under review, the input is the review process record and the request submission time. Compare the request status field with the value "approved." If the status is pending review, the request is not approved, and an executed tool call cannot be used to infer that business authorization is complete.
Empty-result handling: if a paper input is [], the downstream design must state the branch that handles that empty input. It cannot be claimed that a fabricated rule retrieval necessarily returns an empty array. Libraries built on different vector models cannot be associated together; identifiers must be checked first and non-matching libraries excluded, and no cross-model retrieval is performed to compare missed recall. Retrieval and relevance scores do not carry permission or entity isolation functions, and retrieval is not authorization.
This page addresses one scope only: producer export tax offset and refund, operating reports and exception review, tool calls and plug-ins. At handover, the authorization state of documents, operations, and requests must be stated directly; retrieval and forms are not authorization execution.