On Chinese marketplaces, the price a shopper pays is rarely the price you booked. Every Tmall, JD.com, and Douyin order carries a stack of discounts — and the single most important accounting question is who funded each one. Merchant-funded discounts (your brand’s own coupons and price cuts) reduce your net revenue and must be booked as contra-revenue. Platform-funded subsidies (coupons the marketplace pays for) do not reduce the revenue you earned — you are still owed the full price, with the platform making up the difference. Getting this split wrong is one of the most common reasons a China P&L understates net revenue and margin.
Promotion funding is the fourth force in the GMV-to-net-revenue bridge, and it is the one finance teams most often get wrong. During 618 and Double 11, a single order can layer a store coupon, a cross-store discount, a platform voucher, and a livestream flash price — some funded by you, some funded by the marketplace. If your ERP treats every discount as a revenue reduction, you silently erase subsidy income you actually earned. This guide explains how to separate merchant-funded from platform-funded promotions on Tmall, JD, and Douyin, how each is treated under ASC 606 and IFRS 15, and how to map the promotion line cleanly into NetSuite or SAP.
What is the difference between merchant-funded and platform-funded discounts?
A merchant-funded discount is a price reduction your brand pays for: a store coupon, a member discount, or a flash-sale markdown you set in the seller back office. It reduces the amount the customer pays and the amount you collect, so under both IFRS 15 and ASC 606, it reduces the transaction price and is booked as contra-revenue. A platform-funded subsidy is a discount the marketplace pays for to drive traffic — a platform-issued voucher, a government consumption coupon, or a festival subsidy. The customer pays less, but the platform reimburses the difference at settlement, so your earned revenue is unchanged. The subsidy is consideration received from the platform on the customer’s behalf, not a reduction of what you earned.
- Merchant-funded — you pay, revenue goes down. Treated as a reduction of the transaction price (contra-revenue).
- Platform-funded — the marketplace pays, your revenue is unchanged. The subsidy appears as a receivable settled by the platform, not a discount to net revenue.
- Co-funded — split by an agreed ratio (common in 618/Double 11 campaigns). Only your share is contra-revenue; the platform’s share is a receivable.
The accounting principle is the same one behind gross vs. net revenue recognition: you recognize what you earn. A merchant-funded coupon lowers what you earn; a platform-funded coupon does not.
Why does it matter who funds a China marketplace coupon?
Because the funding source changes both your net revenue and your true margin — and Chinese marketplaces do not label the split cleanly in their standard exports. Treating a platform-funded subsidy as your own discount understates revenue and makes your promotions look far less profitable than they are. Treating a merchant-funded discount as a platform cost overstates revenue and inflates margin, which eventually reverses when settlement cash comes in short. Three consequences follow directly:
- Net revenue accuracy — the promotion line is often 10–30% of headline GMV during festivals, so misclassifying it distorts the entire net-margin calculation.
- Campaign ROI — you cannot judge whether a 618 push was profitable if platform subsidies are buried inside your own discount total.
- Settlement reconciliation — platform-funded amounts reappear as a positive line in the payout. If you booked them as your discount, your settlement reconciliation will never tie out.
What types of promotions run on Tmall, JD, and Douyin?
Chinese marketplaces run a denser promotion stack than most Western channels, and each type has a default funding source you need to confirm per campaign:
- Store coupons (店铺优惠券) — issued by your store; almost always merchant-funded and contra-revenue.
- Cross-store discounts (跨店满减) — the “spend 300 save 50” festival mechanic; typically merchant-funded but allocated across multiple items, so the discount must be spread proportionally.
- Platform vouchers & red packets (平台券/红包) — issued by Tmall, JD, or Douyin to drive traffic; usually platform-funded and reimbursed at settlement.
- Government consumption coupons (消费券) — subsidised by local authorities via the platform; platform/third-party-funded, not your revenue reduction.
- Livestream & flash prices — Douyin and Taobao Live discounts that may be merchant-funded, KOL-subsidised, or co-funded, depending on the deal.
- Presale deposit incentives — deposit-multiplier discounts tied to 618 and Double 11; see presale deposit revenue recognition for the timing rules.
How should merchant-funded discounts be recorded?
Merchant-funded discounts reduce the transaction price and are recorded as contra-revenue at the order line, not as a marketing expense. Booking your own coupons as an expense is a common error: it overstates gross revenue and misclassifies a price concession as promotional spend. Under IFRS 15 and ASC 606, a discount you grant to the customer is variable consideration that reduces revenue at the point of sale. The practical rules:
- Record the discount against the specific order and SKU so gross-to-net is auditable per line.
- Allocate multi-item discounts (cross-store 满减) proportionally across the qualifying items, matching how returns will later reverse them.
- Keep merchant-funded discounts separate from advertising spend — a store coupon is contra-revenue; an Alimama or Qianchuan ad is an expense.
How should platform-funded subsidies be recorded?
Platform-funded subsidies are recorded as consideration you are still owed — you recognize the full pre-subsidy price and carry the subsidy as a receivable from the marketplace until it settles. The customer pays a reduced amount, but the platform reimburses the balance, so your earned revenue is the full ticket price. Two acceptable treatments exist depending on your policy and materiality:
- Full-price revenue + platform receivable — recognize the gross price; the shortfall between customer cash and gross price becomes a receivable cleared at settlement. This keeps net revenue accurate and is the preferred method.
- Net-with-add-back — some teams book net-of-all-discounts, then add platform-funded amounts back as other income. This works only if the add-back is disciplined; otherwise the subsidy is silently lost.
Whichever you choose, the subsidy must survive from order data through to the ERP. This is fundamentally a data quality problem: if the platform export collapses customer-paid and platform-funded amounts into one “discount” column, you cannot split them downstream. The split has to be captured at ingestion.
How do you reconcile promotion funding to net revenue?
The promotion reconciliation is a three-way tie-out: order-level discounts must equal the sum of merchant-funded plus platform-funded amounts, and the platform-funded total must match the subsidy credits in the settlement statement. Run it as a standing monthly control alongside your settlement reconciliation:
- Step 1 — Total discount per order: sum every promotion applied to the line from the order/transaction export.
- Step 2 — Classify each discount by funding source using the promotion type and campaign rules, tagging merchant vs platform vs co-funded.
- Step 3 — Tie platform-funded to settlement: the platform-funded total should equal the subsidy reimbursement lines in the payout file. Gaps mean a misclassified promotion or an unpaid subsidy.
- Step 4 — Bridge to net revenue: only merchant-funded discounts (plus returns and fees) reduce recognized net revenue.
How do you map China promotion accounting into NetSuite or SAP?
The mapping requires distinct accounts for merchant-funded contra-revenue and platform-funded receivables, fed by an integration that classifies each discount before it reaches the ledger. A typical structure:
- A contra-revenue account (e.g. “Marketplace Promotions – Merchant Funded”) posted against the revenue line per marketplace.
- A platform subsidy receivable account that accrues platform-funded amounts and clears when settlement cash lands.
- Per-marketplace dimensions (Tmall / JD / Douyin) and per-campaign tags so 618 and Double 11 performance can be isolated.
- Automated FX handling so RMB discounts convert on the same basis as the underlying sale — see FX reconciliation.
Doing this by hand in spreadsheets is why China P&Ls run two weeks late. A platform like Digate ingests order, promotion, and settlement data from each marketplace, classifies every discount by funding source at the source, and posts merchant-funded contra-revenue and platform-funded receivables into NetSuite or SAP automatically — so your net revenue reflects exactly what you earned, festival or not.
Key takeaways
- Ask “who funded it?” for every discount. Merchant-funded reduces net revenue; platform-funded does not.
- Merchant-funded = contra-revenue, booked against the order line — never as marketing expense.
- Platform-funded = full-price revenue plus a receivable cleared at settlement.
- Capture the split at ingestion. If order data collapses discounts into one column, the classification is lost for good.
- Reconcile platform-funded amounts to settlement monthly so subsidies you earned are never silently erased.
For the full picture of how promotions fit alongside returns, fees, and FX, start with the GMV-to-net-revenue bridge and the complete guide to China marketplace-ERP integration.