Cross-Border E-Commerce Export Tax Refund and Customs Codes: Using 9610, 9710, and 9810
Export tax refund in cross-border e-commerce is often treated as an accounting problem, when it is first of all a data problem: whether you can claim depends on whether you can prove how the goods left, how the money came back and how the invoices were issued. Collection accounts and entity structure are covered in the cross-border seller entity structure and collection account guide, and the boundary here is the choice of supervision code and the construction of the refund document chain, not how to pick an entity or open an account.
1. Why Start with the Supervision Code
A supervision code is a customs classification for statistics and control, not an arbitrary number. Choose the wrong one and the goods still leave, but everything downstream drifts: statistics fall into the wrong bucket, declaration elements are incomplete and the refund basis is missing. By the time the problem surfaces the goods are in an overseas warehouse and the cost of tracing back is enormous.
A Code Is Not a Number but a Switch for the Declaration Path
Behind every supervision code sits a set of declaration requirements: which documents to submit, at what frequency, who consolidates the data, and whether it can serve as refund evidence. The moment the code is chosen, that set switches on. Many companies pick a code that looks close enough at registration, then have to live with the full requirement set for the whole transaction, and changing it midway means rebuilding the data chain.
The code should follow the substance of the transaction, not habit. Retail direct mail to overseas consumers, business-to-business bulk export, export to an overseas warehouse before sale, and entry into a bonded area before leaving it are four different situations with four different codes. Once business models mix, declarations must be split rather than covering everything with one code.
Three-Flow Inconsistency Is the Real Difficulty
In theory an export refund rests on goods, funds and documents corroborating each other. In practice cross-border e-commerce is exactly where three-flow inconsistency appears: goods may leave several factories for several ports, funds may arrive as a platform settlement covering many orders, and documents may sit with different service providers. Each line is real, but they do not line up.
The consequence is not simply that the refund is refused, but that nothing can be explained, which is worse because it spreads into receipt verification, platform compliance reviews and bank due diligence, all pointing at the same question. The task is therefore not to assemble a set of documents but to make the three lines carry linkable fields from the moment they are generated.
| Supervision code | Use case | Declaration points | Refundable |
|---|---|---|---|
| 9610 | Cross-border retail export, shipped directly to overseas consumers | List release and consolidated declaration, with list data collected by order | Possible when documents are complete and matched, but retail parcels often fail for lack of a special VAT invoice |
| 9710 | Cross-border business-to-business direct export | Must show the overseas corporate buyer and transaction evidence | Possible when documents are complete, with the key being matched purchase invoices and declaration data |
| 9810 | Cross-border export to an overseas warehouse | Must show warehouse information and the subsequent sales arrangement | Depends on actual sale and documentation; uncertainty exists before the goods are sold |
| 1210 | Bonded cross-border e-commerce, goods entering a bonded area first | Follows bonded area ledger and exit declaration requirements | Exit declarations differ between domestic sale and export, so judgement depends on the actual flow |
2. 9610: List Release and Consolidated Declaration
9610 is the main code for cross-border retail export, used when goods are shipped directly to overseas consumers. It was designed to solve the conflict between enormous parcel volumes and the impracticality of declaring each parcel separately, so it uses declaration logic entirely different from general trade.
How List Release and Consolidated Declaration Work
List release means goods clear on a list basis at exit rather than through a full declaration for every parcel. Consolidated declaration means that within a declaration cycle the list data is gathered and filed as a formal declaration record. The mechanism gives mass parcel traffic statistical visibility and lets the authorities see the real export scale.
The requirement it places on the business is data completeness. Who collects the list data, whether fields are complete, whether order numbers map to waybill numbers, and whether amounts and currencies are correct all determine whether the consolidated declaration completes. If list data is collected by a logistics provider, confirm the returned fields serve your later purposes instead of discovering the gap at filing time.
Why the 9610 Refund Route Often Fails
The reason is direct: an export refund generally requires a special VAT invoice, while upstream purchasing for retail parcels often produces none. Small factories, wholesale markets and sole traders charge more when issuing invoices, so many sellers choose the cheaper no-invoice purchase at the sourcing stage and then lack the key document at the refund stage.
This is not an operational problem but a problem at the start of the chain. Without an invoice at sourcing, any later remedy is a formal patch, and patched documents rarely survive scrutiny. The implication matters: if your sourcing structure is inherently invoice-free, the 9610 refund process is not worth studying, and the alternative route described below is the relevant one.
3. 9710 and 9810: B2B Export and Overseas Warehouses
9710 and 9810 were designed for two different business shapes. The first serves bulk transactions between companies, the second serves the stock-first, sell-later overseas warehouse model. Both share a longer transaction chain and therefore a higher demand for complete documentation.
When 9710 Applies and What to Declare
9710 applies to cross-border business-to-business direct export, typically bulk purchases by overseas corporate customers. The key is proving both that the buyer is a company and that the transaction happened: the overseas buyer's entity information, the order or contract, and the payment evidence must correspond.
Its advantage is that the transaction structure resembles general trade, so the document chain is easier to complete. If upstream purchasing yields a special VAT invoice, the match between declaration, receipts and invoices has a foundation. The difficulty is receipt timing: B2B deals often carry payment terms, so money arrives after the declaration date, and that interval must be explained in the supporting documents rather than ignored.
When 9810 Applies and What to Declare
9810 applies to cross-border export through overseas warehouses: goods are shipped in bulk to a warehouse abroad and dispatched from there to consumers or small customers. The peculiarity is that no final sale exists at export, so the refund question cannot be answered from the declaration alone; it also depends on whether the goods were eventually sold, to whom, and at what price.
The data difficulty is joining two chain segments: the export declaration and the overseas sale. When the segments sit in different systems without a shared key, the refund filing cannot prove that the goods declared are the goods sold. The fix is to assign a batch identifier at the dispatch step and let overseas sales data post back to the same batch.
4. Three Preconditions for Export Tax Refund
Before discussing process, settle the preconditions. If they fail, familiarity with the process achieves nothing. The three below are generally applicable, and specific execution is subject to the latest rules of the competent authorities and official channel documentation.
Complete Documents with Matching Information
Complete means the customs declaration, the special VAT invoice and the foreign exchange receipt all exist. Matched means the key fields across them correspond, including product name, quantity, amount, currency, counterparty and date range. Complete but unmatched equals incomplete.
The hardest field is the product name. If the commodity code used at declaration does not match the invoice description, or a shipment split into several items is invoiced as one broad name, an unexplainable variance appears. Fix the naming convention at the sourcing stage so invoice, declaration and order all use one set of names and codes.
Consistency of Entity, Goods and Receipts
The exporting entity, the owner of the goods and the receiving party should correspond. If entity A declares the export while entity B receives the payment, those receipts are hard to accept as consideration for that export. Businesses running multiple entities need particular care here, and the design logic and common misalignments are set out in the adjacent entity structure article.
Consistency does not require one entity everywhere; it requires every relationship to be backed by a contract and to be explainable. Entrusted export, agency collection and intra-group division of labour are all acceptable arrangements, provided written evidence and a reasonable commercial rationale exist.
5. Tax-Exempt Without Invoices: the Pilot Zone Route
Comprehensive pilot zones for cross-border e-commerce carry an important policy arrangement: qualifying enterprises inside the zone that engage in retail export may apply VAT and consumption tax exemption. The industry calls this the invoice-free exemption, because its value is dropping the requirement for an upstream special VAT invoice.
How the Exemption Works
Exemption and refund are different concepts. A refund returns input tax already paid, which presupposes that input tax exists and is documented. Exemption imposes no output tax, so no liability arises at the output stage. For retail export with invoice-free sourcing, exemption is the realistic route because it removes the must-have-invoice precondition.
Its practical significance is that sellers sourcing without invoices gain a compliant export path instead of being forced to choose between cheap no-invoice supply and no refund at all. It is not a licence to ignore everything, since entity eligibility, business authenticity and data filing requirements still apply.
Conditions and Boundaries
Conditions usually include registration inside a comprehensive pilot zone, engagement in retail export, declaration through compliant channels, and data the authorities can access. Specific conditions and procedures are subject to the latest rules of the competent authorities and official channels, and local execution detail can differ.
The boundaries are equally clear: the exemption addresses output-stage tax, not input deduction; it applies to retail export and not automatically to every trade shape; and it requires genuine business, not packaging a transaction that never exported anything. Treat it as a compliant route that better fits invoice-free sourcing, not as a label to apply at will.
6. Building a Document Chain You Can Trace Back
The value of a document chain is not whether it can be submitted at filing time but whether it can be traced back later. Reviews often happen long after the business completed, when staff have moved and systems have migrated, and the only reliable basis is the structured data left behind.
Five Nodes of the Document Chain
The first node is sourcing: purchase contracts, special VAT invoices, or explanatory material for invoice-free purchasing. The second is the order: a platform order number or overseas customer order, which is the primary key for the whole chain. The third is logistics: waybill number, port of exit, actual dispatch date. The fourth is the declaration: declaration number, supervision code, declared amount. The fifth is the receipt: settlement records, conversion records, payer information.
At least one cross-verifiable key must connect the five nodes. The most common are order number with waybill number, then declaration number with invoice number. The key need not be unique but must be stable and written identically across all systems.
Four Retrieval Capabilities the System Must Have
First, look up the entire chain by order number, from sourcing through receipts in one query. Second, look up by declaration number and work back to orders and receipts. Third, query by date range plus amount band for batch reviews. Fourth, query by exception flag to find records missing a node.
These four capabilities determine the efficiency of reconciliation and review, and the structure of collection data decides whether they are achievable. The reconciliation approach and bill download steps are in the reconciliation and bill download handbook, and automated multi-source aggregation is described in the reconciliation automation script guide.
7. Relating Refunds to Receipt Flows
The refund is cash flow on the revenue side, receipts are cash flow on the goods side, and the two never align naturally in timing or amount. What must be built is an explainable relationship, not an exact equality.
Why Payment Data Must Keep Order-Level Detail
If the collection account only reports a periodic aggregate credit, every filing reduces to total-level matching, and any request to drill into a single transaction stalls. Order-level detail means each credit maps to one or a group of orders, and each order maps to a declaration record.
Multi-currency operations amplify this. A platform may settle in one currency while sourcing is paid in another and the refund is computed in a third, so a clear conversion basis and conversion date are required. Account operation and conversion handling are covered in the multi-currency collection account operations guide.
Matching Strategy Across Platforms and Entities
With several platforms, the same goods may sell through different marketplaces and entities. The strategy starts by fixing the aggregation dimension: by entity, by marketplace, or by batch. Once the dimension is fixed, the table structure follows.
Batch as the main dimension and order as the detail dimension works best. The batch maps to the declaration, the order maps to the receipt, and the two lines meet at the batch. Even when platform settlement merges many orders into one payment, the order list restores the batch.
8. Launch Checklist and Six Common Blockers
With the mechanics covered, execution decides the outcome. Most blockers are not policy problems but unprepared data, or a business model that simply does not match the chosen code.
Six Common Blockers and Responses
| Common blocker | Symptom | Response |
|---|---|---|
| Supervision code does not match the business | Declaration basis drifts from transaction substance and elements are missing | Re-map codes to transaction substance and split declarations for mixed models |
| Invoice-free upstream sourcing | No special VAT invoice, so no refund basis | Evaluate the pilot zone exemption route or restructure sourcing |
| Inconsistent product names and codes | Invoice, declaration and order use different names | Fix naming and coding rules at sourcing and reuse them end to end |
| Receipts never match declared amounts | Variance cannot be explained and is questioned repeatedly | Build batch-to-order mapping and explain each variance line by line |
| Multi-entity collection without contracts | Receiving entity differs from exporter with no written basis | Complete entrustment or agency agreements with clear rationale |
| Overseas warehouse goods never sold | Export declared but sales data missing | Assign batch identifiers and post overseas sales back to the batch |
Launch Checklist
The checklist should cover: confirming the supervision code for each business model; building a document aggregation table keyed by batch; fixing product names and codes at sourcing; ensuring the collection account exports order-level detail; completing contracts and agreements for multi-entity arrangements; defining multi-currency conversion basis and date; auditing document chain completeness each quarter; confirming the applicable route for invoice-free purchasing in advance; and creating a posting mechanism for overseas warehouse sales data.
On tools and institutions, providers that expose order-level receipt detail and multi-currency settlement make the document chain far easier to build, including the multi-currency accounts of Airwallex, the seller-oriented offerings of Payoneer, PingPong and WorldFirst, and the acquiring and settlement data interfaces of Adyen. Ask one question at selection: can it export receipts by order number, rather than only a periodic total?
Domestic invoice and corporate payment matching is described in the domestic B2B collection loop guide, and the full framework of tax definitions and filing duties in the VAT and sales tax compliance guide. One closing reminder: the value of a refund is not the amount recovered but the way it forces sourcing, logistics and receipts onto one connected line, and once that line exists the business itself becomes markedly more controllable.
More payment and finance crossover scenarios are collected under the Payment category.
Source: 16IDC original. Relevant rules are subject to the latest regulations of customs, tax, foreign exchange and cyberspace authorities and to official channel documentation.
Original source: 16IDC ↗