A global brand can reconcile every Tmall, JD, and Douyin settlement to the yuan and still report a China P&L that is wrong — because the numbers were captured in RMB and translated to USD or EUR at the wrong rate, on the wrong date, in the wrong place. Currency is the last mile of China marketplace finance, and it is where a surprising amount of “phantom” margin appears and disappears each month.
China marketplace FX reconciliation is the process of translating RMB-denominated marketplace revenue, fees, refunds, and payouts from Tmall, JD, and Douyin into your reporting currency using the correct exchange rate for each transaction type and date, then reconciling the resulting USD or EUR amounts against what actually lands in your bank — so the China numbers in your consolidated ERP match reality. This guide explains why RMB translation breaks, which exchange rate applies where, and how global brands automate it in 2026.
The short answer
If you only read one section, read this:
- Chinese marketplaces settle in RMB, but your consolidated books report in USD, EUR, or GBP — so every order, fee, and refund has to cross a currency boundary before it can be trusted.
- The RMB is not freely convertible. Funds move through the platform, a cross-border payment provider, and China’s foreign-exchange system (SAFE) — and each hop can apply a different rate on a different day.
- Booking revenue at the order-date rate but receiving cash at the payout-date rate creates FX gains and losses that most brands never isolate — they get buried in “other” and silently distort net margin.
- Correct reconciliation means applying the right rate (transaction, settlement, or period-average) to the right layer, and posting a clean, auditable FX variance line into your ERP instead of a plug.
Why RMB marketplace revenue is so hard to translate
Translating a single foreign-currency invoice is routine accounting. Translating hundreds of thousands of micro-transactions that flow through Chinese marketplaces, cross-border payment rails, and a controlled currency regime is not. Four structural issues make China different:
1. Multiple rates for the same money
An order placed on Tmall on the 1st, settled by the platform on the 15th, and repatriated to your Western bank on the 25th can touch three different exchange rates. The marketplace reports gross revenue in RMB, your payment provider converts at its own rate and spread, and your ERP may revalue the receivable at month-end using yet another. If you pick one rate for everything, you are wrong for the other two layers.
2. RMB is a managed, non-freely-convertible currency
Cross-border RMB flows are governed by China’s State Administration of Foreign Exchange (SAFE) and cleared through the onshore (CNY) and offshore (CNH) markets, which trade at slightly different rates. The rate your payment service provider actually applies when converting a Douyin or JD payout is rarely the mid-market rate you would pull from a public feed — it embeds a spread you need to capture as a cost, not lose to rounding.
3. Timing mismatches between booking and cash
Revenue is earned when the order ships, but cash arrives weeks later after the platform’s settlement cycle and cross-border remittance. Under US GAAP (ASC 830) and IFRS (IAS 21), that gap is a monetary receivable that must be revalued at the closing rate — generating a realized or unrealized FX gain or loss that is entirely separate from operating performance. Brands that skip this step report FX noise as if it were margin.
4. Fees and refunds are netted in RMB before you see them
Platform commissions, ad deductions, and refunds are taken out in RMB inside the settlement, so a single payout already blends gross revenue and multiple cost types at the source currency. Translating only the net payout hides the true RMB cost base — you need each component translated, not just the bottom line. This is the same layering problem that breaks settlement reconciliation and fee-to-net-margin reconciliation, compounded by currency.
The four FX gaps that distort your China P&L
- Rate-selection gap — using one convenient rate (often month-end) for revenue that was actually earned across 30 different daily rates.
- Spread gap — the difference between the mid-market rate in your ERP and the real rate your payment provider applied, quietly eroding cash versus book.
- Revaluation gap — open RMB receivables between order date and cash date that are never restated at the closing rate, so FX movement hides inside revenue.
- Component gap — translating net payouts instead of gross revenue, fees, and refunds separately, which understates both the top line and the cost base.
What correct FX reconciliation looks like
A defensible China marketplace FX reconciliation follows the same discipline every month:
- Capture every amount in source RMB first. Store gross revenue, each fee type, refunds, and payouts in yuan before any conversion, so the audit trail starts at the currency of record.
- Assign the correct rate to each layer. Revenue at the transaction- or shipment-date rate, receivables revalued at the period-close rate, and cash at the provider’s actual conversion rate — not one blended average for all three.
- Book the FX variance explicitly. The difference between revenue translated at booking and cash received after conversion is a realized FX gain or loss. Post it to its own account, not into net sales.
- Reconcile translated cash to the bank. The USD or EUR that hits your account should tie back, within the provider spread, to the sum of translated payouts. Any residual is a real exception to investigate, not a rounding plug.
- Feed clean, multi-currency lines into the ERP. NetSuite, SAP, and similar systems handle multi-currency well — but only if they receive correctly translated, correctly dated, component-level entries instead of a single lump payout.
Which exchange rate applies where?
The most common question finance teams ask is simply which rate do I use. Under both ASC 830 and IAS 21 the answer depends on what you are translating:
- Revenue and expenses — the spot rate on the transaction date, or a period-average rate when transaction volume makes daily rates impractical.
- Monetary items (RMB receivables, cash in transit) — the closing (period-end) spot rate, with the change since last period booked as an FX gain or loss.
- Actual cash conversion — the real rate your payment provider used, which defines realized FX and the spread cost.
Getting this three-way split right is what separates a China P&L that survives audit from one that relies on a month-end plug to balance.
How to automate China marketplace FX reconciliation
Doing this by hand across Tmall, JD, and Douyin — each with its own RMB reports, settlement cadence, and payment rails — is where finance teams lose days every close and still distrust the result. It is also why China P&L is always two weeks late. Automation changes the economics:
- Ingest gross revenue, fees, refunds, and payouts from each marketplace in source RMB, preserving the original currency of record.
- Apply rate tables automatically — transaction-date, period-close, and actual provider rates — to the correct layer of every transaction.
- Isolate the FX variance as its own posting so operating margin is never contaminated by currency movement.
- Push correctly translated, component-level entries into NetSuite or SAP, ready for consolidation.
This is exactly the problem Digate’s China-to-ERP data integration is built to solve: it connects Tmall, JD, and Douyin to your Western ERP and carries every amount through in its source currency with the right rate applied at the right layer — so month-end close starts from numbers you can trust rather than a currency-translation guess.
Frequently asked questions
What is China marketplace FX reconciliation?
It is the process of translating RMB-denominated revenue, fees, refunds, and payouts from Chinese marketplaces into your reporting currency using the correct exchange rate for each transaction type and date, then reconciling the translated amounts against actual bank receipts so your consolidated China P&L is accurate.
Why can’t I just use one month-end exchange rate?
Because revenue is earned across many daily rates, receivables must be revalued at the closing rate, and cash is converted at your provider’s actual rate. Using a single rate for all three collapses genuine FX gains and losses into revenue and misstates net margin.
Does the RMB being non-convertible affect my accounting?
Yes. Cross-border RMB flows are managed by SAFE and cleared through onshore (CNY) and offshore (CNH) markets that trade at different rates, and your payment provider applies a spread on conversion. That spread is a real cost that should be captured, not lost to rounding.
Which standard governs this — ASC 830 or IAS 21?
US GAAP filers apply ASC 830 and IFRS filers apply IAS 21; both require transaction-date rates for revenue and expenses and closing rates for monetary items such as RMB receivables, with the movement recorded as an FX gain or loss.
See your true China numbers, in your own currency. Digate connects Tmall, JD, and Douyin to NetSuite and SAP and reconciles RMB revenue, fees, refunds, and FX into one unified P&L. Learn how Digate works or explore our integrations.