General import declarations: upgrades for operations handover

What the documents look like

For general trade import declaration, the working materials are the import declaration form, commercial invoice, packing list, bill of lading and contract. Data comes from the International Trade Single Window, customs tariff schedules, freight forwarder arrival notices and foreign exchange payment documents, refreshed per shipment. In operations permission and handover management, these materials matter because the parties, goods, amounts and status recorded on them become the objects compared during handover. The materials record declared and accompanying information. They do not by themselves grant operating authority to any person or system.

Handover requests among the customs manager, the declaration broker and the importer can only be characterised by comparing each item against the source wording. The category differs from export declaration in that import declaration centres on dutiable value, freight and insurance, and tax payment.

Constraints at the upgrades step

During deployment and upgrade, the central constraint for operations permission and handover management is that retrieval, form entry and page display only present or collect information. Business verification, approval, database writes and external synchronisation each require their own downstream implementation. From V4.17.0, AI Proxy is a required dependency: App and Admin services that reuse App/Service configuration must both set AIPROXY_API_ENDPOINT and a non-empty AIPROXY_API_TOKEN, and missing either causes startup validation to fail. FILE_TOKEN_KEY, AES256_SECRET_KEY and INVOKE_TOKEN_SECRET are required at runtime. V4.17.2 contains two manually triggered upgrade scripts, the historical chunk training task migration and the knowledge base rebuild status migration. Neither blocks service startup, and both require confirmation that old instances have fully stopped and old task leases have expired before execution.

Hypothetical paper exercise sample: a customs manager at an importer retains a handover note whose source text reads: "The consignee named on the commercial invoice for this shipment is Company A; the notify party on the bill of lading is Company A; the signing party on the contract is Company A; the invoice amount equals the contract amount; this consignment has not yet been declared to customs." A separate draft sentence reads: "Handover complete; the declaration broker has obtained declaration authority for this shipment and may submit directly to customs." The comparison objects are the parties, amount and declaration status on the three materials, and the question is whether the draft sentence's claimed authority is supported by the materials. No authorisation clause appears in the source text.

Configuration and implementation checks

The table below relates to this page's sample and lists documented settings or implementation checks connected to deployment, upgrade and handover comparison. Values are hypothetical starting points for this exercise, used for comparison against the reader's own environment, and are not official defaults.

Three common errors

1. Treating retrieval or form display as authority to act. Input: the three sample materials and the draft sentence. Comparison object: whether an authorisation clause appears in the materials. Observable result: the source text records only parties, amount and declaration status, and contains no authorisation wording, so the claimed authority remains unsupported and is recorded as pending verification.
2. Writing a pending-review status as approved. Input: the handover request and its status field. Comparison object: the status value. Observable result: pending review and approved are different values, and where the materials contain no approval record the fact is unsupported.
3. Associating knowledge bases across different vector models in one retrieval. Input: the vector model identifier of each knowledge base. Comparison object: whether the identifiers match. Observable result: entries with differing identifiers are excluded first; the document does not describe runtime behaviour after joint association.

How to verify the setup

1. Input: the three sample materials and the draft sentence "Handover complete; the declaration broker has obtained declaration authority for this shipment." Comparison object: whether the consignee, notify party and signing party fields match the party named in the draft, and whether the materials contain an authorisation clause. Observable result: the three materials name the same party and none records authorisation, so the claimed authority is unsupported and is logged as pending verification.
2. Input: the sample source text "this consignment has not yet been declared to customs" and the draft sentence "has obtained declaration authority". Comparison object: the value of the same declaration status field. Observable result: the source value is not yet declared, which is a different fact from the claimed authority; the claim is recorded as unsupported rather than as a negation or conflict.
3. Input: the hypothetical AIPROXY_API_ENDPOINT and AIPROXY_API_TOKEN values above. Comparison object: the documented required-item and format statements. Observable result: when both are set and the token is non-empty, startup validation passes; when either is missing, startup validation fails as documented. This judgement rests on the documentation and was not tested in this environment.

Related reading

• self-host/config/env
• self-host/upgrading/4-17/4172
• FastGPT upgrades