Information date: 5 November 2026 — Customs Notice 2020 No.75 added 9710 for cross-border B2B direct export and 9810 for export to overseas warehouses, alongside ordinary trade code 0110. All three are declarable export modes, but only 0110 and the B2B codes with matching input invoices support a VAT refund; retail cross-border exports more commonly rely on tax-exempt treatment. If the supply chain can produce full special invoices and buyers are identifiable businesses, declare 0110 or 9710 and claim the refund. If goods go to an overseas warehouse with uncertain final buyers, use 9810 and plan for pilot-zone exempt treatment rather than a refund, unless the warehouse sales and receipts can be documented end to end.
Verified facts and scope
Customs Notice 2020 No.75 added 9710 for cross-border B2B direct export and 9810 for export to overseas warehouses, alongside ordinary trade code 0110. All three are declarable export modes, but only 0110 and the B2B codes with matching input invoices support a VAT refund; retail cross-border exports more commonly rely on tax-exempt treatment.
Scope has to be fixed before the numbers mean anything: Applies to exporters choosing a declaration code for goods leaving China. Confirm first: whether the seller is a general VAT taxpayer holding special invoices, whether goods move to a bonded overseas warehouse or straight to a business buyer, whether the entity sits inside a cross-border e-commerce pilot zone, and how foreign-exchange receipts will be matched to the declaration. Anything outside that set is a separate question with its own evidence requirement, and mixing the two is the most common way a workable plan turns into an unusable one.
For a decision on “Comparison: Cross-Border E-Commerce Export Codes 9710 and 9810 vs Ordinary Trade 0110 — the Customs Filing, the VAT-Refund Voucher Trail and Who Can Actually Claim the Rebate”, keep three layers apart: the published rule or statistic, the company’s own orders and process records, and the assumptions nobody has tested yet. The first layer defines the external conditions, the second proves what is true for this business, and the third is where the risk actually sits. Public material cannot substitute for a contract, a system log, a sample or a live test.
A practical way to test the scope is to ask which parts of “Comparison: Cross-Border E-Commerce Export Codes 9710 and 9810 vs Ordinary Trade 0110 — the Customs Filing, the VAT-Refund Voucher Trail and Who Can Actually Claim the Rebate” would still be true if the company changed supplier, entity or product line tomorrow. Items that survive that change belong to the rule layer and can be taken from official publications; items that do not survive belong to the operating layer and have to be rebuilt from invoices, warehouse records, customs entries or platform statements. Where Applies to exporters choosing a declaration code for goods leaving China. Confirm first: whether the seller is a general VAT taxpayer holding special invoices, whether goods move to a bonded overseas warehouse or straight to a business buyer, whether the entity sits inside a cross-border e-commerce pilot zone, and how foreign-exchange receipts will be matched to the declaration, the two layers are frequently mistaken for each other, and an action plan built on the wrong one either over-complies or misses a deadline it never saw coming.
How the effect reaches operations
The refund is voucher-driven: the customs declaration, the VAT special invoice, the foreign-exchange receipt and the logistics record must align in quantity, amount and counterparty. 9810 defers the sale until the goods leave the overseas warehouse, so the refund clock and the receipt trail are harder to close than under 0110, where the export sale occurs at the border.
The classic misjudgement is assuming a 9710 or 9810 declaration automatically unlocks a refund; without compliant input invoices there is nothing to refund and pilot-zone exemption applies instead. Second, mismatched buyer names between the platform order, the declaration and the invoice trigger refund suspension, and warehouse-mode receipts can be challenged on timing.
Translated into an operating sequence, The refund is voucher-driven: the customs declaration, the VAT special invoice, the foreign-exchange receipt and the logistics record must align in quantity, amount and counterparty. 9810 defers the sale until the goods leave the overseas warehouse, so the refund clock and the receipt trail are harder to close than under 0110, where the export sale occurs at the border. That ordering matters: check applicability first, then the transmission step, and only then the size of the gap in cost or timing. When an intermediate step cannot be confirmed, the honest response is to narrow the scope of the conclusion rather than to substitute an industry average for the company’s own figures.
The cost of getting the order wrong is asymmetric. A team that checks applicability too late usually discovers it at the point where the shipment, the filing or the invoice can no longer be changed without penalty, and by then the only remaining lever is price. A team that checks early spends a few hours on questions that turn out to be irrelevant, which is cheap by comparison. On “Comparison: Cross-Border E-Commerce Export Codes 9710 and 9810 vs Ordinary Trade 0110 — the Customs Filing, the VAT-Refund Voucher Trail and Who Can Actually Claim the Rebate” the practical rule is therefore to spend the first hour on scope and the second on the numbers, never the other way round.
Decision
If the supply chain can produce full special invoices and buyers are identifiable businesses, declare 0110 or 9710 and claim the refund. If goods go to an overseas warehouse with uncertain final buyers, use 9810 and plan for pilot-zone exempt treatment rather than a refund, unless the warehouse sales and receipts can be documented end to end.
The conditions should be written down so the decision can be re-run by someone else: Applies to exporters choosing a declaration code for goods leaving China. Confirm first: whether the seller is a general VAT taxpayer holding special invoices, whether goods move to a bonded overseas warehouse or straight to a business buyer, whether the entity sits inside a cross-border e-commerce pilot zone, and how foreign-exchange receipts will be matched to the declaration. When those hold, proceed as described; when one is missing, close the gap first and decide afterwards. Trade-compliance comparison only; not customs, tax or accounting advice, and eligibility depends on the specific entity, invoices and pilot-zone rules in force.
Two workstreams usually have to move in parallel. The compliance workstream closes the document side of “Comparison: Cross-Border E-Commerce Export Codes 9710 and 9810 vs Ordinary Trade 0110 — the Customs Filing, the VAT-Refund Voucher Trail and Who Can Actually Claim the Rebate” — registrations, confirmations, filings — while the commercial workstream protects the delivery date, the pricing already quoted and the customer commitments that were made on the earlier reading of the rules. Running them as one queue is how small documentation gaps become missed shipment dates: the commercial side waits for a certificate that could have been requested a week earlier. If the supply chain can produce full special invoices and buyers are identifiable businesses, declare 0110 or 9710 and claim the refund. If goods go to an overseas warehouse with uncertain final buyers, use 9810 and plan for pilot-zone exempt treatment rather than a refund, unless the warehouse sales and receipts can be documented end to end. Set one owner per workstream and one shared status sheet, and treat a red item on either side as a reason to freeze only the affected order.
Implementation checklist
- Map invoices against every declaration before choosing the code.
- Match buyer names across platform, customs and invoice files.
- Model cash flow on exemption if input invoices are missing.
- Name one decision owner, one execution owner and one review date.
- Keep the source page, access date, entity and internal evidence.
- On any change, reopen only the affected judgement.
Evidence and review
Start with the smallest test that can change the answer: Map invoices against every declaration before choosing the code. Pick one real entity or one representative case, write down the continue, watch and stop conditions in advance, and record the input version, the owner, the start time and the actual result. The first pass should only look at facts that move the decision; formatting preferences are not risk.
The second pass is completed by “Match buyer names across platform, customs and invoice files”, and someone who did not prepare the file should spot-check one piece of critical evidence. The classic misjudgement is assuming a 9710 or 9810 declaration automatically unlocks a refund; without compliant input invoices there is nothing to refund and pilot-zone exemption applies instead. Second, mismatched buyer names between the platform order, the declaration and the invoice trigger refund suspension, and warehouse-mode receipts can be challenged on timing. A single small deviation can be corrected in place; a repeated deviation, or one that touches a statutory duty or changes the economics, is what justifies pausing the affected part.
After “Model cash flow on exemption if input invoices are missing”, compare the actual result with the baseline rather than with the impression of the team. If the supply chain can produce full special invoices and buyers are identifiable businesses, declare 0110 or 9710 and claim the refund. If goods go to an overseas warehouse with uncertain final buyers, use 9810 and plan for pilot-zone exempt treatment rather than a refund, unless the warehouse sales and receipts can be documented end to end. When the arrangement is extended to more products, customers or processes, keep the same success test and one complete record per batch. If later information changes, update only the affected fields.
One last discipline keeps the file usable next quarter: write the closing note as if a colleague who has never spoken to the supplier has to act on it. That note states what was verified, on which date, against which source, and what remains open — on “Comparison: Cross-Border E-Commerce Export Codes 9710 and 9810 vs Ordinary Trade 0110 — the Customs Filing, the VAT-Refund Voucher Trail and Who Can Actually Claim the Rebate” it also states which of the three actions was actually finished and which was only scheduled. Teams that skip the closing note re-litigate the same question every month, and each round costs more than the documentation would have. Trade-compliance comparison only; not customs, tax or accounting advice, and eligibility depends on the specific entity, invoices and pilot-zone rules in force.
Limits of the conclusion
Trade-compliance comparison only; not customs, tax or accounting advice, and eligibility depends on the specific entity, invoices and pilot-zone rules in force.
The limits are structural rather than cautious wording. Public sources describe rules and market conditions; they do not observe “Comparison: Cross-Border E-Commerce Export Codes 9710 and 9810 vs Ordinary Trade 0110 — the Customs Filing, the VAT-Refund Voucher Trail and Who Can Actually Claim the Rebate” inside a specific company. Where the analysis quotes a second-hand interpretation, the original release has to remain reachable, and a figure that cannot be traced back does not enter the decision table. Where the point depends on Applies to exporters choosing a declaration code for goods leaving China. Confirm first: whether the seller is a general VAT taxpayer holding special invoices, whether goods move to a bonded overseas warehouse or straight to a business buyer, whether the entity sits inside a cross-border e-commerce pilot zone, and how foreign-exchange receipts will be matched to the declaration, the conclusion is only as current as the last check of those conditions.
