Producer export tax processes: shared access for staff training

What the documents look like

Producer export tax refunds combine the offset of domestic sales tax with the refund calculation. This differs from the export refund process used by trading enterprises. The working materials for this category are the refund declaration detail schedule, export contracts, the sales subsidiary ledger, and export customs declarations. Data arrives from the electronic tax bureau, ERP sales records, customs electronic information, and the accounting books. In a store-service and internal-training setting, these materials move between store staff and internal personnel in paper or electronic form. The sharing and embedding step therefore has to state which authorization state each material is in before any link is distributed.

The refund declaration detail schedule carries line-level export values and customs declaration numbers. Export contracts and customs declarations carry the counterparty, object, and period that let a reviewer check consistency. The sales subsidiary ledger ties the declared amounts back to the accounting books. None of these documents by itself grants permission to share the material outside its intended audience.

Constraints at the shared access step

The no-login window is created under the publishing channel, and the system generates a complete link that can be copied and used. The link identifier is an access entry only. It does not serve as a business authorization, and it does not show that a material has been approved for external sharing or for training use.

Identity verification is limited to the commercial edition. When the verification root address is configured, the share link sends requests to the corresponding endpoints at initialization, before a conversation starts, and at conversation end. The server returns whether verification succeeded, and the unified response format requires success plus a uid. The uid must be a string of no more than 255 bytes that does not contain the characters "|", "/", or "\\". FastGPT uses success to decide whether the user may continue. When success is not true, the returned message or msg is shown as the error. The optional result-reporting endpoint has no required return value and carries totalPoints and token.

The anonymous local identifier depends on the same device and the same browser. Records are pulled from the cloud for the recent 30 days and 20 entries. Switching devices or clearing browser cache loses those records. Cross-device records need a separately designed identity and session arrangement. The expiration time and QPM are set according to the intended use and checked against the actual edition; QPM is the maximum number of visits per user per minute. The points cap is checked against the usage limit of the sharing entry and the cost belongs to the team that owns the application. Some parameters are configurable only in the commercial edition.

Hypothetical drill sample: a store plans to share a producer export tax refund material with internal training personnel so they can check the consistency between the declaration detail schedule and the export customs declaration. The material text to be checked reads: "Line 3 of the refund declaration detail schedule lists an export goods FOB price of 120000 yuan, corresponding to export customs declaration number XXXX2024001, for the declaration period May 2024." The proposed draft sentence reads: "Please view the above declaration detail schedule through the share link and confirm whether the customs declaration number and the FOB price are consistent." This request is in a pending-share state and has not received any authorization to execute.

Configuration and implementation checks

Three common errors

1. Treating the share link identifier as a business authorization credential. The link provides an access entry only; it does not show that the material has been approved for external sharing or for training use.
2. Treating a pending share request as an approved execution. In this sample the proposed draft sentence is in a pending-share state and cannot be regarded as executed before authorization is granted.
3. Treating conversation records under the anonymous local identifier as training records usable across devices. That identifier depends on the same device and the same browser; switching devices or clearing cache loses the records.

How to verify the setup

1. Input the sample material text and the proposed draft sentence, then compare whether the draft sentence exceeds the subject, object, and period scope stated in the source text. The draft sentence only asks to confirm the consistency of the customs declaration number and the FOB price, and it does not exceed the source scope, so the condition is met.
2. Input the success and uid returned by the identity verification interface, then compare whether the uid format excludes "|", "/", and "\\" and stays within 255 bytes. When the condition is met, the user is allowed to continue.
3. Input the expiration time and QPM setting of the share link, then compare the configurable range of the actual edition against the hypothetical trial starting point. The 7-day expiration time and the QPM value need to match the range supported by the edition; when they do not match, record the item as pending verification.

These checks stay within the named primary task: inspecting specific proposed copy sentences against the supplied source wording and its limitations. They do not certify identity, analyze reports, or claim that any test, deployment, approval, refund, or other business action actually happened. Missing evidence remains missing, and a pending request is not an approval.

Related reading

• guide/build/publish/link
• FastGPT shared access