Export Invoice vs VAT Invoice in China: A Practical Explainer

Two documents that point in opposite directions

Ask an export finance team to describe the difference between an export invoice and a VAT invoice and you will usually get a functional answer — one goes to the customer, one goes to the tax bureau — without the structural reason behind it. The structural reason is that they answer different questions. An export invoice answers a commercial question: what was sold, to whom, on what terms, for how much. A VAT invoice answers a tax question: how much input tax was incurred, on what goods, and is it therefore creditable or refundable.

Because the questions differ, the documents differ in who issues them, what they must contain, whether they are validated by a government system, and what happens when they are wrong. Collapsing the two — issuing a VAT invoice for an export sale, or treating the invoice you emailed the customer as evidence of input tax — is one of the most common and most expensive documentation errors in Chinese export operations.

What an export invoice actually is

An export invoice is a commercial document you produce yourself, in the format your customer and your bank expect. It typically carries your company details, the buyer, the contract or order reference, a description of the goods, quantity, unit price, trade term, total value in the settlement currency, and often the HS code and country of origin. For customs purposes it accompanies the declaration as a supporting document; for the bank it supports the collection or letter of credit; for your own books it evidences revenue.

What it is not is a tax instrument. It is not issued through the tax authority's invoicing system, it carries no tax control code, and it does not by itself create or prove any input tax. This is why the same shipment can legitimately have an export invoice with one set of amounts and a separate VAT invoice from a domestic supplier with entirely different amounts — the first is about your sale, the second is about your purchase.

• Issued by: you, not the tax system.
• Currency: usually the settlement currency (USD, EUR), not necessarily RMB.
• Purpose: commercial evidence for the customer, the bank and customs.
• Tax effect: none directly — it neither charges output VAT nor proves input VAT.
• Common variants: commercial invoice, proforma invoice, packing list companion.

Why export sales normally do not carry a VAT invoice

For exported goods, the sale is generally either exempt or zero-rated, which means no output VAT is charged to the foreign buyer. Since there is no output VAT to document, there is no need for the special VAT invoice that would normally accompany a domestic taxable sale. Issuing one would create an expectation of output tax that does not exist and would need to be reversed or explained.

Where export-facing VAT invoicing does exist — for example in specific regimes, or when goods are sold into a bonded or domestic-within-bond area — the treatment follows the specific rules of that arrangement rather than the general export rule. This is precisely the kind of question where the correct answer depends on your exact transaction structure and should be confirmed with your tax adviser or the local tax authority rather than generalised from an article. The mechanism of the rebate itself, including the filing deadline, is covered in export tax rebate ERP software for China.

The VAT invoices that actually matter for a refund

Here is the asymmetry that catches people: the invoices that matter most to an exporter are the ones it receives, not the ones it issues. A rebate claim rests on input VAT. That input VAT is evidenced by VAT invoices (or equivalent creditable vouchers) issued to you by your domestic suppliers — the factory that sold you the goods, the supplier of the materials, the provider of taxable services consumed in producing the export.

So the document chain for a trading company looks like this: supplier issues a VAT special invoice to you for the goods; you export the goods and issue a commercial export invoice to the buyer; customs issues a declaration; the bank records settlement. The refund is computed on the input VAT evidenced by the supplier's invoice, matched against the customs declaration and the settlement. If the supplier's invoice is missing, late, wrongly titled, or for goods that do not correspond to the declared export, the refund fails — regardless of how immaculate your export invoice looks.

For a producer under the exemption-credit-refund method, the same principle applies to input VAT on materials and services consumed in manufacturing the exported goods. The refundable amount comes out of the credit balance, not out of anything on the sales side. This is why tax teams obsess over the invoice collection rate from suppliers and much less over the formatting of the export invoice.

The four mistakes that recur

These appear in almost every review of an exporter's documentation process, and each has a systems dimension.

• Treating the export invoice as proof of input tax. It never is. The proof is the inbound VAT invoice from the supplier, and the two must be linked at the shipment level or the link is reconstructed from memory at filing time.
• Mismatched goods descriptions. The description on the supplier invoice, the customs declaration and the export invoice should describe the same goods consistently. Divergence is a standard audit trigger, and it usually originates in product master data with three different naming conventions.
• Missing or late supplier invoices. A shipment cannot be declared until the input invoice exists. If the ERP does not track invoice receipt against purchase orders, the gap is discovered at filing time when there is no time to chase it.
• Currency and amount confusion. The export invoice is in the settlement currency; the supplier invoice and the refund computation are in RMB. Without a stored exchange rate and a clear conversion basis, the numbers cannot be reconciled across the chain.

The packing list carries the physical facts

Exporters tend to treat the packing list as the invoice's less important sibling, which is a mistake in both directions. The invoice describes commercial value; the packing list describes physical reality — packages, dimensions, gross and net weight, shipping marks, container distribution. Customs compares the two, the carrier uses the packing list to book space and issue the bill of lading, and the warehouse uses it to load. When the two disagree, the shipment is the thing that stops.

The recurring failure is that they are produced from different data. The invoice is generated from order lines in the sales system; the packing list is typed in the warehouse from what was actually packed. Small differences in carton count or net weight are normal and harmless, but once the documents are independent, nobody can tell a normal difference from an error. Generating both from the same shipment record — with packing data captured once at loading — removes the ambiguity. It also makes the bill of lading instruction consistent, since the carrier's document copies the same physical facts.

When a document has to be corrected

Corrections are not exceptional; they are a normal part of export operations, and the system's behaviour during a correction reveals whether it was designed for trade or for general accounting. In an accounting system, a posted document is typically reversed and reissued, leaving a credit note trail. In trade, a correction may mean amending a customs declaration, reissuing a bill of lading, voiding a certificate of origin with the issuing authority and applying for a replacement — each with its own procedure at its own organisation.

The data requirement is version control with an explicit supersession link. The issued document is preserved exactly as it went out, because that is what the customs authority, the bank and the insurer hold; the replacement is linked to it as its successor, with the reason recorded. Systems that overwrite the document in place destroy the evidence of what was declared, which is exactly the evidence needed if a discrepancy is queried months later. Ask the vendor to show an amended export invoice and an amended declaration side by side with the originals. If the originals are gone, the system is not suitable for trade documentation, whatever else it does well.

How the ERP should carry both

The correct model is two separate document streams joined by the shipment, not one document type with a flag. On the sales side, the ERP should generate the export invoice and packing list from order data in the required language and layout, in settlement currency, and store the issued version as an immutable snapshot. On the purchase side, it should record inbound VAT invoices against purchase orders and receiving, capture the invoice number, date, amount and tax, and — critically — link those invoices to the export shipments they support.

That link is the piece most systems miss. Without it, three-document matching (customs declaration, input invoice, settlement) is a manual exercise performed under deadline pressure. With it, the system can present, per shipment, which input invoices support the declared value and which are still outstanding — and that outstanding list is the operational work queue for the finance team, not a surprise at the April 30 boundary.

The e-invoice transition adds a wrinkle rather than removing one. Fully digitalised e-invoices are still VAT invoices with the same legal function; what changes is the channel and the validation mechanism, not the accounting logic. For how that interacts with your ERP's document handling, see fully digitalized e-fapiao and ERP readiness. And if you are still assembling these documents by hand per shipment, the automation pattern in automating export documentation is the logical next step.

A one-line test for your current process

Take your most recent export shipment and ask the system to show you three things: the export invoice you issued, the customs declaration for that shipment, and the supplier VAT invoices that evidence the input tax. If all three come up on one screen, linked, your model is sound. If answering requires opening two systems and finding a colleague who remembers, you do not have a documentation process — you have a reconstruction process that works until the person who remembers leaves, or until an auditor asks the same question with a deadline attached.