What the documents look like
Producer export tax processes combine the offset of domestic sales tax with the refund of export tax in a single calculation. That combined calculation shapes which documents matter at the order-fulfilment and after-sales question stage. A shared knowledge base for this category normally holds the export contract, the customs declaration form, the sales ledger, and the detail schedule for the exemption, offset and refund declaration. The detail schedule aggregates self-produced export goods by accounting period. The export contract and the customs declaration form establish the free-on-board price and the trade term. The sales ledger provides the booked sales amount. Customs electronic information serves as an external comparison source. These materials update monthly, and the comparison at the sharing step concerns whether the same accounting period, the same customs declaration number and the same export invoice number carry consistent field values. The supplied material does not describe an automatic synchronization mechanism among these sources, so difference handling remains a manual comparison action.
Constraints at the shared access step
A share link is an access entry point. The link identifier does not represent a business authorization. A no-login window is created from the publishing channel, and the system-generated full link is copied for use. Any internet user who obtains that address can use it, and the resulting cost is charged to the team that owns the application. Conversation records depend on a localId that the system generates for each user. That mechanism only supports use on the same device and the same browser. Switching devices or clearing browser cache loses those records, and the system only allows retrieval of the most recent 20 records within 30 days. Identity verification is a commercial-edition feature. After a root address is configured, initialization, conversation start and conversation end each send a POST request to a specific interface under that address, and the server response with success and uid determines whether the user may continue. Retrieval results and relevance scores do not perform identity, entity or permission filtering, and a retrieval action does not itself constitute authorization.
Hypothetical paper test case: a tax accountant at an export producer places an export contract summary and a detail schedule summary into the knowledge base for order-fulfilment and after-sales questions during preparation for an exemption, offset and refund declaration. The contract summary reads: "Contract number HT-2025-018, seller is a domestic producer, goods are self-produced A-type motors, trade term FOB, export date 12 March 2025, contract amount USD 120,000." The detail schedule summary reads: "Accounting period March 2025, customs declaration number Guan-20250312001, export invoice number FP20250301, export goods A-type motors, free-on-board price RMB 840,000, exemption-offset-refund amount column pending declaration." The proposed draft sentence reads: "This export completed the exemption, offset and refund declaration in March 2025 and the refund was received." The request to be judged reads: "Please confirm whether the contract and the detail schedule above support the draft sentence."
Configuration and implementation checks
The table below lists settings or implementation checks documented for the no-login window, tied to the sample on this page. Values that do not appear in the supplied material are left out.
| Configuration item | Sample value on this page | Basis and comparison method |
|---|---|---|
| No-login window link | Created from the publishing channel and copied as the full address | The link identifier is an access entry only and cannot serve as a declaration or refund authorization credential |
| Expiry time | Set according to the intended sharing scope | After that time the link cannot be used; compare against the actual question-handling period |
| QPM | Checked as the maximum access count per user per minute | The value represents an access frequency ceiling; compare against the supported range of the actual edition |
| Points cap | Checked as the usage limit for the sharing entry | Cost is charged to the team that owns the application; compare against the team budget basis |
| Identity verification root address | A third-party verification root address is entered | Commercial-edition feature; the interface response with success and uid determines whether the user may continue |
| Conversation record boundary | Relies on localId on the same device and browser | Cross-device records require separate identity and session management design |
Three common errors
- Treating the no-login window link identifier as a declaration authorization or a refund eligibility credential. The link only indicates an accessible entry point. In the sample, the detail schedule states that the exemption-offset-refund amount column is pending declaration, which shows the declaration status is not yet complete. Link availability and declaration completion are two separate facts.
- Treating a success response from the identity verification interface as business approval. That interface returns only a verification result and a uid. The draft sentence in the sample concerns completing a declaration and receiving a refund. That business status requires tax authority acceptance and treasury refund records, and the interface return value does not carry that meaning.
- Joining the retrieved contract summary and detail schedule summary directly into an affirmative conclusion. The contract states the export date and trade term. The detail schedule states the accounting period and the pending declaration status. Neither states declaration completion or refund receipt. When that field is absent, the conclusion is recorded as unsupported.
How to verify the setup
- Input the sample contract summary and detail schedule summary, and compare the draft sentence "This export completed the exemption, offset and refund declaration in March 2025 and the refund was received" against the source text. The source text contains only "pending declaration" and does not contain a declaration-completion field or a refund-received field. The observed result is that the draft sentence is unsupported, and declaration acceptance and treasury refund evidence must be added before any judgment.
- Input the sample request to be judged, and compare the subject, accounting period and customs declaration number in the request against the source text. The contract subject is a domestic producer, the detail schedule accounting period is March 2025, and the customs declaration number is Guan-20250312001. When all three match, proceed to field comparison. When the subject or the customs declaration number does not match, record an evidence gap and do not issue an affirmative or negative conclusion.
- Input the success value and uid returned by the identity verification interface, and compare that return value against the business approval status. A success value of true only indicates that the conversation may continue. The observed result is that the conversation may continue, while declaration completion and refund receipt remain unknown and require acceptance and treasury refund records from a downstream system.