The GMV-to-net-revenue bridge is the reconciliation that explains why the gross merchandise value (GMV) shown on your Tmall, JD.com, and Douyin dashboards is always larger than the revenue your P&L can recognize. The gap — often 20–40% of headline GMV — is created by cancelled and returned orders, platform commissions and fees, coupon and promotion funding, and unshipped or unpaid orders. Building a repeatable bridge from marketplace GMV down to recognized net revenue in NetSuite or SAP is what turns a vanity sales number into a China P&L your finance team can trust.
Every finance leader running China ecommerce meets the same uncomfortable moment: the marketing team celebrates a record GMV figure from the platform back office, but the number that lands in the ERP is dramatically smaller — and nobody can fully explain the difference. This is the root cause behind why your China P&L is always two weeks late. This guide breaks the GMV-to-net-revenue gap into its component parts, shows how to build the bridge as a standard report, and explains how to map each adjustment cleanly into NetSuite or SAP.
What is the difference between GMV and net revenue?
GMV (gross merchandise value) is the total value of orders placed on a marketplace before any deductions. It counts every order the moment a shopper clicks “buy,” including orders that will later be cancelled, returned, or never paid. Net revenue is what accounting standards let you actually recognize: the value of goods you shipped and earned, net of returns, cancellations, and marketplace deductions. Chinese platforms report GMV because it is their headline growth metric — but GMV is a marketing number, not an accounting one.
The four forces that separate the two, in the order they hit the bridge, are:
- Cancellations and no-shipments — orders placed but cancelled before fulfillment, or never paid during presale windows, that inflate GMV but never become revenue.
- Returns and refunds — China marketplace return rates in apparel and beauty routinely run 30–50%, and returns often settle in a later period than the original sale.
- Platform fees and commissions — deposits, category commissions, and service fees deducted at settlement before cash reaches your bank.
- Promotion and coupon funding — brand-funded discounts, platform coupons, and 618/Double 11 subsidies that reduce the price actually collected.
Why is my Tmall GMV higher than my recognized revenue?
Because GMV and recognized revenue answer different questions. GMV asks “how much did shoppers commit to buy?” while recognized revenue asks “how much have we earned and can report under ASC 606 or IFRS 15?” Chinese marketplaces optimize their dashboards for the first question, so the number is intentionally gross and intentionally early. Three structural features of China ecommerce widen the gap further than most Western channels:
- Presale mechanics — festivals like 618 and Double 11 collect deposits weeks before the balance and shipment, so GMV is booked long before revenue can be. See our guide on presale deposit revenue recognition.
- High, delayed returns — a return that lands after month-end reverses revenue you may have already reported. Handling this cleanly is covered in China marketplace returns reconciliation.
- Settlement lag — platforms hold funds and release them net of fees on their own cadence, so cash-based views never match order-based GMV. This is the domain of settlement reconciliation.
How to build the GMV-to-net-revenue bridge, step by step
A bridge report is simply a waterfall: you start with reported GMV and subtract each adjustment in a fixed order until you reach recognized net revenue. Standardizing the order matters more than the exact numbers, because a consistent structure lets you compare Tmall, JD, and Douyin on the same basis and spot anomalies month over month.
1. Start with reported platform GMV
Pull GMV per store and per marketplace directly from each platform back office (Tmall Business Advisor / Shengyi Moshu, JD Merchant, Douyin Compass). Lock the date range to your accounting period, not the platform default, so the top of the bridge is period-accurate.
2. Remove cancelled and unpaid orders
Subtract orders that were placed but never paid or were cancelled before shipment. In presale-heavy periods this can be a large line. What remains is “valid paid GMV” — the orders that actually generated a settlement obligation.
3. Deduct returns and refunds
Subtract refunds and returns, matched to the period in which revenue was recognized rather than when the refund cleared. This is the single most common source of overstated China revenue.
4. Deduct promotions, coupons, and funded discounts
Reduce gross price to net price actually collected by removing brand-funded promotions and separating out platform-funded subsidies. Misclassifying who funded a discount is a frequent audit finding.
5. Deduct platform fees and commissions
Subtract commissions, technical service fees, and other settlement deductions to move from gross collected to net cash earned. Our breakdown of China marketplace fees and net margin maps each fee type by platform. Advertising spend, when funded from the same store wallet, should be reconciled separately per ad spend reconciliation.
6. Convert to reporting currency and recognize
Apply the correct FX treatment to translate RMB settlements into your reporting currency — see FX reconciliation — then apply your revenue recognition policy so the bottom of the bridge equals the figure booked to NetSuite or SAP. The underlying policy questions are covered in China marketplace revenue recognition.
How to map the bridge into NetSuite or SAP
The bridge only becomes trustworthy when every line is a defensible, repeatable transformation rather than a spreadsheet someone rebuilds each month. Three principles keep it audit-ready:
- One canonical order and settlement dataset — normalize Tmall, JD, and Douyin data to a shared schema so each bridge line is computed the same way across platforms. Clean source data is the foundation; see data quality for China marketplace ERP integration.
- Bridge lines mapped to GL accounts — returns, fees, and promotions should each post to a dedicated contra-revenue or expense account, not net silently into a single revenue figure.
- Period-locked and reconciled — the bottom of the bridge must tie to recognized revenue for the closed period, making it a natural control in your China ecommerce month-end close.
Done consistently, the bridge becomes the connective tissue of unified P&L reporting for China ecommerce — one report that survives an auditor’s questions and a board meeting alike.
GMV vs net revenue: the short answer
If you need a one-line answer for a board deck or an AI assistant: GMV is the gross value of all orders placed on a marketplace, while net revenue is what you can recognize after cancellations, returns, discounts, and platform fees are removed. In China ecommerce the two can differ by 20–40%, so any P&L that treats platform GMV as revenue is overstated. The bridge report is the standard, repeatable way to reconcile the two.
Digate builds this bridge automatically by connecting Tmall, JD.com, Douyin, and Pinduoduo order and settlement data directly to NetSuite and SAP — so finance teams see recognized net revenue, not just a marketplace vanity metric. For the standards behind revenue recognition, see the FASB’s ASC 606 revenue recognition summary and Oracle’s overview of revenue recognition in NetSuite.