What the documents look like
Export tax rebate filing happens after goods leave the country, and the work is matching tax vouchers to export records. The main data comes from the electronic tax bureau, the export rebate filing system, customs electronic messages, and the financial ledger. The daily documents are the export tax exemption and rebate filing form, the export customs declaration, purchase invoices, and foreign exchange receipt vouchers. These materials sit at different authorization states during an operations handover. A filing form may have been submitted and be awaiting review. A customs declaration may exist only as an electronic message receipt. An invoice may have completed verification only. A receipt voucher may be a bank statement summary. A deployment and upgrade step has to preserve these state differences. The presence of a document does not mean the underlying business step was approved.
Constraints at the upgrades step
Before upgrading, compare the current version with the target version and its upgrade notes. Do not infer current behavior from an old configuration name. AI Proxy is a required dependency. Both the App and the Admin service must set AIPROXY_API_ENDPOINT and a non-empty AIPROXY_API_TOKEN; missing either one causes startup validation to fail. FILE_TOKEN_KEY, AES256_SECRET_KEY, and INVOKE_TOKEN_SECRET are required at runtime. Use random strong keys rather than example values. The upgrade scripts are manually triggered tasks that do not block service startup. Confirm that all old-version App and Pro instances have fully stopped and that old task leases have expired before running them. After upgrading, re-check import, retrieval, and application calls with the same sample. A completed step sequence does not support a claim of zero interruption.
Hypothetical drill sample: a finance staff member at a foreign trade enterprise plans to hand over one export tax rebate filing after an upgrade. The source text provided for checking reads: "Export customs declaration number E2026XXXX, export date 2026-03-12, export amount USD 120,000. Corresponding purchase invoice number INV-2026-0312, invoice date 2026-03-15, amount CNY 780,000. Foreign exchange receipt voucher is a bank statement summary, value date 2026-04-02, amount USD 120,000." One handover request to be judged reads: "Please submit the filing data corresponding to the above materials to the electronic tax bureau, and authorize the successor to continue handling follow-up discrepancy feedback." The request states no authorization boundary for either "submit" or "authorize."
Configuration and implementation checks
The table below centers on this page's sample and lists documented settings or implementation check items. The values are starting points for this hypothetical drill only, used to compare against the corresponding value in the target version upgrade notes. They are not official defaults.
| Configuration item | Hypothetical drill starting point | Check and comparison method |
|---|---|---|
AIPROXY_API_ENDPOINT | http://aiproxy:3000 | Check whether /v1 is appended; compare against the AI Proxy service root address |
AIPROXY_API_TOKEN | Non-empty string | Check whether it matches the server-side configuration; compare against an empty value |
FILE_TOKEN_KEY | Random strong key | Check length of at least 6 characters; compare against example values |
AES256_SECRET_KEY | Random strong key | Check length of at least 6 characters; compare against example values |
INVOKE_TOKEN_SECRET | Random strong key | Check length of at least 32 characters; compare against example values |
DEFAULT_TEAM_BASIC_PERMISSIONS_ENABLED | false | Check whether FastGPT and Pro Admin configurations agree |
Three common errors
- Treating a filing form awaiting review as an approved rebate. Input is the source text's "export date 2026-03-12" and "value date 2026-04-02." Compare whether the filing form status field explicitly states "review passed." The condition is met only when that field explicitly states it passed; when the field is not stated, record it as pending verification.
- Treating retrieval or form completion as authorized execution. Input is the handover request's "authorize the successor to continue handling follow-up discrepancy feedback." Compare whether an explicit authorization boundary exists (authorized party, scope of operations, validity period). When it is missing, record the item as unsupported.
- Treating a completed upgrade script run as zero business interruption. Input is the upgrade note's "manually triggered task (does not block service startup)." Compare whether an interruption observation record exists for the local environment. When no record exists, record the item as unverified.
How to verify the setup
- Input the export date and the receipt value date from the hypothetical sample's source text. Compare whether both fall within the same filing period field, and observe whether the filing form status field explicitly states "review passed." When it is not stated, output pending verification.
- Input the "submit to the electronic tax bureau" action from the handover request. Compare whether the request states a submitting party, a submission target, and a submission period, and observe whether an authorization boundary statement exists. When it is missing, output unsupported.
- Input the import, retrieval, and application call records for the same sample after the upgrade. Compare the values of the same field before and after the upgrade, and observe whether a reviewable difference record exists. When no record exists, output unverified, and do not infer zero interruption.