Book a Demo
Book a Demo
Login

JD.com 1P vs 3P Accounting: Reconciling Self-Operated and POP Marketplace P&L

For global brands selling on JD.com (Jingdong, 京东), the single most confusing line in the China P&L is often the JD channel itself. That is because JD is not one business model — it is two. The self-operated model (自营, commonly called 1P) and the open marketplace (POP, commonly called 3P) settle cash differently, recognize revenue differently, and hit your general ledger in ways that rarely reconcile without manual intervention. Finance teams that treat “JD” as a single revenue stream almost always end up with a distorted view of channel profitability.

This guide breaks down how JD 1P and 3P actually work from an accounting perspective, why the two models must be reconciled separately, and how to build a JD channel P&L that ties cleanly back to unified P&L reporting in your ERP.


The short answer: what is the difference between JD 1P and 3P accounting?

JD 1P (self-operated / 自营) is a wholesale relationship: you sell inventory to JD, and JD resells it to the consumer. JD 3P (POP marketplace) is an agency relationship: you sell directly to the consumer and JD takes a commission. The two require different revenue recognition, different settlement reconciliation, and different inventory treatment — and they must never be netted together.

  • 1P (自营): Revenue is recognized on sell-in to JD (wholesale). JD owns the inventory, sets the retail price, and pays you on purchase-order terms (often 30–60+ days).
  • 3P (POP): Revenue is recognized on sell-through to the end consumer (gross or net, depending on your control assessment). You own the inventory until delivery; JD deducts commission, fulfillment, and marketing fees from settlement.
  • Cash timing: 1P follows AP-style invoice terms; 3P follows marketplace settlement cycles with a T+ escrow hold and periodic payouts.
  • Deductions: 1P carries chargebacks, returns provisions, and trade-marketing (JD RMA and 京准通/JingZhunTong ad) deductions; 3P carries platform commission, tech service fees, and logistics (JD Logistics) fees.

Why JD is uniquely hard to reconcile

Most Western brands run JD alongside Tmall, Douyin, Pinduoduo, and Xiaohongshu. But JD is the one channel where a single brand often operates both a 1P and a 3P relationship simultaneously — sometimes for the same SKU. That dual model creates reconciliation problems that do not exist on a pure marketplace like Tmall.

1. The same SKU can appear in two revenue models

A hero product might be stocked by JD as 1P for guaranteed availability during Singles’ Day, while the long-tail catalog sits in your POP flagship store. If your data pipeline keys on SKU alone, 1P sell-in and 3P sell-through get double-counted or collapsed into one number. You need a model dimension (1P vs 3P) on every transaction before it reaches the ledger.

2. Revenue recognition points are weeks apart

Under IFRS 15 / ASC 606, the 1P sale to JD is recognized when control transfers to JD at the warehouse — potentially weeks before the consumer ever buys. The 3P sale is recognized at consumer delivery. Booking both on the same “order date” misstates the period. This is the same revenue recognition discipline you apply across channels, but JD forces you to apply two rules inside one platform.

3. Settlement files do not map to your chart of accounts

JD’s merchant settlement exports (结算单) itemize gross sales, platform commission (扣点), 京准通 advertising, JD Logistics (京东物流) fees, and consumer subsidies in Chinese-language line items that have no native mapping to a NetSuite or SAP GL account. Left unmapped, these collapse into a single “JD deposit” entry and your net margin by channel becomes a guess. Proper settlement reconciliation requires a line-item mapping table.


The JD 1P (self-operated) reconciliation chain

For the 1P relationship, treat JD as a wholesale customer — but a wholesale customer that deducts aggressively. The reconciliation chain looks like this:

  1. Purchase order → sell-in revenue: Recognize revenue when JD takes control at inbound. Match each JD PO to your shipment and invoice.
  2. Returns & RMA provisions: JD returns unsold or defective stock. Accrue a returns reserve against 1P revenue rather than waiting for the debit note.
  3. Trade deductions: Rebates, listing fees, and 京准通 co-op marketing are deducted from JD’s payment. Book these as contra-revenue or marketing expense per your policy — consistently.
  4. Payment matching: Reconcile JD’s remittance against open invoices net of approved deductions. Flag unexplained short-pays as disputed AR.

The failure mode here is silent margin erosion: JD deductions land in the bank feed weeks after the sale, and if nobody ties them back to the originating PO, they simply disappear into a catch-all account.

The JD 3P (POP marketplace) reconciliation chain

For the 3P relationship, JD behaves like Tmall or Douyin. The chain mirrors your other marketplace flows:

  1. Order → gross GMV: Capture consumer orders at list price, including presale deposits during 618 and Singles’ Day.
  2. Gross-to-net bridge: Deduct platform commission, tech service fee, JingZhunTong ad spend, coupons, and platform subsidies to reach net revenue.
  3. Escrow & payout timing: Funds sit in escrow until confirmed receipt, then release on JD’s settlement cycle — a classic driver of settlement DSO.
  4. Fulfillment costs: If you use JD Logistics, warehousing and last-mile fees are netted from settlement and must be allocated to landed cost.

How to build one JD channel P&L that actually ties out

The goal is a JD channel view that shows 1P and 3P side by side, each reconciled to source, then rolled into a single platform contribution margin. Practically, that means:

  • Tag every transaction with a model dimension (1P / 3P) and a marketplace dimension (JD) at ingestion, before any aggregation.
  • Map JD settlement line items to GL accounts with a maintained Chinese-to-English translation table for commission, ads, logistics, and subsidies.
  • Reconcile to two sources of truth: JD PO/invoice data for 1P and JD merchant settlement exports for 3P — the same discipline that keeps a broken China marketplace ERP integration from silently dropping fees.
  • Roll up into consolidated reporting so JD sits alongside Tmall and Douyin in group P&L consolidation without double-counting or FX distortion.

A quick JD reconciliation checklist

  • Does every JD transaction carry a 1P/3P flag before it hits the ledger?
  • Are 1P sell-in and 3P sell-through recognized on separate revenue rules?
  • Is there a maintained mapping from JD settlement line items (扣点, 京准通, 物流费) to GL accounts?
  • Are trade deductions and platform commissions tied back to their originating PO or order?
  • Do 1P returns reserves and 3P coupon/subsidy accruals exist, or are you booking on cash?
  • Can you show JD contribution margin split by 1P and 3P in the same report?

How Digate fits

Digate connects JD.com — both the 1P self-operated feed and the 3P POP merchant settlement exports — directly into NetSuite, SAP, and other Western ERPs. Every JD transaction arrives tagged with its model dimension, every Chinese-language settlement line item is mapped to your chart of accounts, and 1P and 3P reconcile to their own sources before rolling into one JD channel P&L. The result is the same cross-marketplace comparability you need across Tmall, JD, and Douyin — without the month-end spreadsheet gymnastics. It is part of the broader China data integration layer that gives global brands unified P&L visibility.


Frequently asked questions

Is JD 1P revenue recognized gross or net?

JD 1P is a wholesale (sell-in) relationship, so revenue is typically recognized gross at your wholesale price when control transfers to JD, with returns and trade deductions treated as contra-revenue or expense per policy. It is not a commission model.

Is JD 3P (POP) revenue gross or net?

It depends on your control assessment under IFRS 15 / ASC 606. Most brands acting as principal on POP recognize gross GMV and then bridge to net revenue via platform commission, ad, and logistics deductions. See our guide to China marketplace revenue recognition for the principal-versus-agent test.

Can one SKU be sold as both JD 1P and 3P?

Yes — and this is the core reason JD reconciliation breaks. Brands frequently stock hero SKUs as 1P for availability while running the full catalog on POP. Without a model dimension on each transaction, the same SKU gets double-counted or collapsed.

Why do JD deductions show up weeks after the sale?

JD deducts commission, advertising, logistics, and rebates from periodic settlement or invoice payments, not at order time. That lag is a major source of settlement DSO and unexplained margin leakage unless deductions are tied back to their originating order or PO during settlement reconciliation.

How does JD compare to Tmall and Douyin for finance teams?

Tmall and Douyin are primarily marketplace (3P-style) models, so their reconciliation is single-rule. JD is the outlier because of the dual 1P/3P structure. Our Tmall vs JD vs Douyin data comparison details the differences across all three.

For further reading on the underlying standards and market context, see the IFRS 15 revenue standard, JD.com investor relations disclosures on the 1P/3P mix, Marketplace Pulse for platform economics, and China Briefing for VAT and settlement guidance in China.