For a global brand running on Tmall, JD, and Douyin, the value-added tax (VAT) line is where the China P&L quietly falls apart. The platform shows you a gross merchandise value number. Your bank receives a net RMB settlement. And somewhere in between sits a 13% output VAT, a stack of fapiao (发票) tax invoices, and input VAT credits that your Western ERP has no native way to capture. The result: revenue that is overstated, tax that is misclassified, and a finance team that cannot defend the numbers during audit.
This article breaks down how VAT and fapiao actually work on Chinese marketplaces, why they break standard ERP reconciliation, and the framework enterprise finance teams use to fold Chinese indirect tax into a trustworthy, consolidated P&L.
Quick answer: how VAT and fapiao affect your China marketplace P&L
- Prices on Tmall, JD, and Douyin are VAT-inclusive. The standard 13% output VAT is already baked into the consumer price, so booking the gross price as revenue overstates the top line.
- A fapiao is not the same as a marketplace order. The official tax invoice is issued on a different timeline and often at a different granularity than the platform settlement, creating a three-way reconciliation gap.
- Input VAT is recoverable — but only if captured. VAT on platform commissions, advertising (Alimama, Qianchuan), and logistics can offset output VAT, yet it rarely reaches the Western ERP.
- Cross-border models change the rules. Bonded cross-border ecommerce (CBEC) and general trade carry different VAT treatments, so the same product can have two tax profiles.
- The fix is a tax-aware data layer that reconciles platform settlement, fapiao records, and ERP journals into one auditable source of truth.
What VAT and fapiao mean on Chinese marketplaces
The 13% output VAT baseline
China levies VAT on the sale of goods, with the standard rate for most retail goods at 13%. Critically, consumer prices displayed on Tmall, JD, and Douyin are VAT-inclusive. When a customer pays RMB 113 for an item, roughly RMB 100 is net revenue and RMB 13 is output VAT collected on behalf of the tax authority. Booking the full RMB 113 as revenue inflates your top line by more than 11% and distorts every downstream margin metric. This is the same trap that makes gross vs. net revenue recognition so error-prone — VAT compounds the gross-versus-net problem. (Rates and thresholds are set by the State Taxation Administration of China; confirm current rates for your product category before configuring your ledger.)
The fapiao (发票) tax-invoice system
A fapiao is the official, government-regulated tax invoice that legitimizes a transaction for tax purposes in China. There are two forms that matter to brands: the general VAT fapiao (普通发票), issued to consumers, and the special VAT fapiao (专用发票), which supports input-VAT deduction between businesses. Your Chinese entity issues output fapiao for sales and collects input fapiao for the services it buys — platform fees, advertising, warehousing, and logistics. Without the special fapiao on the input side, that VAT is simply lost.
A marketplace order tells you what a customer bought. A fapiao tells the tax authority what happened. Reconciling the two is the heart of a defensible China P&L.
Why marketplace VAT breaks Western ERP reconciliation
NetSuite, SAP, and similar ERPs were built for tax regimes where the invoice is the transaction. China’s marketplace reality is different, and four structural mismatches cause most of the pain:
- Timing mismatch. The sale, the platform settlement, and the fapiao issuance can occur in three different periods — a recurring headache during month-end close.
- Granularity mismatch. Platforms settle in netted batches, while fapiao are often issued per order or per consumer request, so line-level tie-out is non-trivial.
- Currency mismatch. VAT is assessed in RMB, but your consolidated P&L is in USD or EUR, layering tax reconciliation on top of RMB-to-USD/EUR FX reconciliation.
- Capture mismatch. Input VAT on marketplace commissions and fees and advertising sits in platform back-ends and vendor fapiao that never flow into the ERP automatically.
The three-way reconciliation gap
Every accurate China marketplace VAT number depends on tying together three independent records that rarely agree out of the box:
- Platform settlement data — the netted payout from Tmall, JD, or Douyin, already reduced by commissions and (in some cases) VAT withholding.
- Fapiao records — the official output and input tax invoices registered with the tax authority.
- ERP journal entries — the revenue, tax-payable, and expense postings your finance team ultimately reports.
When these three do not reconcile, you get phantom revenue, unrecoverable input VAT, and audit exposure. A disciplined settlement reconciliation process is the foundation, but it must be extended with a tax dimension to be complete.
Output VAT vs. input VAT: what actually hits your P&L
VAT is a pass-through tax, so — done correctly — it should be broadly P&L-neutral. What flows to the income statement is net revenue (price minus output VAT) and the non-recoverable portion of costs. The mechanics:
- Output VAT — collected on sales, sits as a liability until remitted. It is not revenue.
- Input VAT — paid on commissions, ads, and logistics; recoverable against output VAT when supported by a special fapiao. Recoverable input VAT is a balance-sheet item, not an expense.
- Net VAT payable — output VAT minus recoverable input VAT — is what your Chinese entity actually remits.
Get the input-VAT capture wrong and you overstate operating expenses, understate cash, and distort channel profitability by channel. This is exactly the kind of leakage that erodes true net margin without ever showing up as an obvious error.
Cross-border models: general trade vs. bonded CBEC
The same SKU can carry two different tax profiles depending on how it enters China:
- General trade — goods are imported, clear customs, and are sold domestically. Standard 13% VAT plus any consumption tax and import duties apply, and full fapiao obligations are in force.
- Bonded cross-border ecommerce (CBEC) — goods sold through channels such as Tmall Global or JD Worldwide under the CBEC pilot regime benefit from preferential cross-border ecommerce retail import tax treatment rather than standard general-trade VAT, subject to transaction and annual limits.
If your finance team treats CBEC and general-trade revenue identically, both your tax provision and your margin analysis will be wrong. Global authorities such as the OECD International VAT/GST Guidelines and advisory guidance like PwC China indirect tax guidance are useful references, but the operational challenge is data: you need to tag every order with its trade model before it reaches the ERP — a classic China-to-ERP data integration problem.
A reconciliation framework for China marketplace VAT
Enterprise teams that get this right follow a repeatable, tax-aware sequence:
- Ingest at line level. Pull order, settlement, fee, and refund records from each platform with tax fields preserved, not pre-aggregated.
- Split VAT from revenue. Decompose every VAT-inclusive price into net revenue and output VAT at the point of ingestion.
- Match fapiao to transactions. Tie output fapiao to orders and input fapiao (special VAT invoices) to platform and vendor costs.
- Tag the trade model. Classify each order as general trade or bonded CBEC so the correct tax rule applies.
- Convert consistently. Translate RMB tax amounts to reporting currency using a documented FX policy aligned to your close.
- Post a clean journal. Push net revenue, output-VAT liability, and recoverable input VAT to the ERP as structured, auditable entries.
How Digate automates China marketplace VAT reconciliation
Digate connects directly to Tmall, JD, Douyin, and Pinduoduo, then normalizes settlement, fee, refund, and tax data into a single model that maps cleanly to NetSuite, SAP, and other Western ERPs. Instead of manually chasing fapiao and rebuilding VAT logic in spreadsheets, finance teams get VAT-decomposed, trade-model-tagged, currency-converted journals ready to post. It is the tax-aware layer that turns the complete guide to China marketplace-ERP integration from a quarterly fire drill into an automated close.
- Automatic split of VAT-inclusive prices into net revenue and output VAT
- Fapiao-aware matching of output and input tax records to transactions
- General-trade vs. bonded CBEC classification at the order level
- RMB-to-USD/EUR conversion consistent with your reporting policy
- Audit-ready journals delivered to your ERP with full lineage
Frequently asked questions
Is the VAT included in Tmall, JD, and Douyin prices?
Yes. Consumer prices on Chinese marketplaces are VAT-inclusive. The standard 13% output VAT is embedded in the displayed price, so you must strip it out to arrive at net revenue for your P&L.
What is a fapiao and why does it matter for accounting?
A fapiao (发票) is China’s official tax invoice. Output fapiao substantiate your sales for tax, while special VAT fapiao on your purchases allow you to recover input VAT. Without proper fapiao capture, you overstate costs and lose recoverable tax.
Can Western brands recover input VAT on marketplace fees and ads?
Yes, when the expense is supported by a special VAT fapiao, input VAT on platform commissions, advertising, and logistics can offset output VAT. The challenge is capturing those fapiao and mapping them to the right transactions in your ERP.
How is bonded CBEC taxed differently from general trade?
Bonded cross-border ecommerce enjoys preferential cross-border retail import tax treatment rather than standard general-trade VAT and duties, within set limits. Every order must be tagged with its trade model so the correct tax rule and margin are applied.
Ready to close your China P&L with tax you can defend? See how Digate reconciles VAT, fapiao, and settlement data into one auditable source of truth for NetSuite and SAP. Explore Digate or read the complete guide to China marketplace-ERP integration.