How to Read Your Meesho Payment Report XLSX, Column by Column
A line-by-line walkthrough of the Meesho payment report XLSX for sellers. Understand settlement, commission, shipping, RTO, and compensation columns so you can verify every deduction.
Every few weeks, Meesho drops a payment report XLSX into your Seller Panel. For sellers running more than a handful of orders, reading that file is the single most important skill for knowing whether you actually made money. This guide walks through every column you care about, one at a time.
Where the file comes from
Log in to the Meesho Seller Panel, open the Payments section, and look for the payment cycle you want to inspect. Each cycle exposes a downloadable XLSX file. Download it to your computer without opening and re-saving it in Excel first — Excel occasionally re-formats cell types (dates and long numeric IDs in particular), which can confuse any tool that parses the file later.
The file usually arrives with a name similar to
Payment_Dashboard_Order_Level_YYYYMMDD.xlsx. Inside,
the main sheet has one row per sub-order (not per order — more on
this distinction below).
Order vs sub-order: the most important distinction
If a buyer places a single order containing three products, Meesho splits it into three sub-orders, each with its own sub-order ID. The payment report has one row per sub-order, which means:
- Each row has its own settlement amount, commission, and shipping charge.
- The same parent order ID can appear on three different rows.
- If you are reconciling against the Orders view in Seller Panel, match on sub-order ID, not order ID.
Column-by-column tour
1. Sub-order ID
The atomic unit. Always unique. Treat this as the primary key when you cross-reference against any other report (orders, shipping labels, returns).
2. Order date / dispatch date / delivery date
These three timestamps tell you the lifecycle. If a delivery date is blank but the row has a negative settlement, the order likely went into RTO. If dispatch date is blank, the order was probably cancelled before handover and the row may still carry a cancellation deduction.
3. SKU / product name
Your internal SKU identifier and the listed product name. If you see the same SKU appearing with wildly different settlement amounts, that is usually a pricing variant (size or colour) or a discount campaign — worth a look.
4. Listed price / final customer price
The price shown to the buyer at the moment of sale. This is not what you get paid. Discounts, commissions, and fees have not yet been removed.
5. Supplier listed price
What you configured as the catalogue price on your seller account. If this is lower than the final customer price, a Meesho-funded discount or markup was applied for the buyer.
6. Settlement amount (the big one)
This is the rupee amount Meesho actually credited to your account for the sub-order. It is after platform commission, shipping fees, taxes collected, and most other deductions. Think of this as net revenue from a single sub-order as far as Meesho is concerned.
Negative values are legal. A return, cancellation, or RTO-heavy cycle can produce rows with negative settlements, meaning Meesho deducted from your balance instead of paying you.
7. Commission
Meesho's platform fee, usually a percentage of the final customer price, varying by category. Already reflected in the settlement amount — this column exists so you can see the commission separately.
8. Shipping charges
The forward shipping fee Meesho billed you for the delivery. Shipping is weight-tier based. A 400g product pays a lower forward fee than a 1.8 kg product.
9. RTO charges
Return-to-origin shipping fees. Applied when a buyer refuses the package at the door or cancels after dispatch. RTO is the single biggest silent killer of Meesho margins, and this column is where it shows up. On categories with high return rates, RTO charges can cancel out commissions several times over.
10. Compensation / claims
Positive adjustments that Meesho credits back to you — for example, when a courier loses a package or the buyer reports a wrong-product issue. Verify that compensation amounts on this column match the claims you have filed.
11. Penalties / other deductions
Late dispatch penalties, quality-check rejections, packaging non-compliance fines. Small, silent, and they add up. Filter this column for non-zero values periodically to make sure you know what you are being fined for.
12. Tax columns (TCS, TDS)
Tax Collected at Source and Tax Deducted at Source amounts. You will need these at tax filing time. Keep every payment report archived for at least seven years.
Reading a single row end to end
Pick any row. Ask these five questions, in order:
- Was this order delivered? If delivery date is blank, it did not complete. Check the lifecycle columns.
- What was the settlement? If it is positive, Meesho paid you for this sub-order. If it is negative, they recovered money from you.
- What did Meesho charge? Commission + shipping + any RTO + any penalty. These four columns explain the gap between the listed price and the settlement amount.
- What are my costs? Product cost (what you paid your supplier) + packaging + any overhead. Meesho does not know these, so you have to layer them in yourself.
- What is left? Settlement minus your own costs equals real net profit for that sub-order. Do this for every row and you have a true P&L for the cycle.
Two common misreadings
- Treating settlement amount as profit. Settlement is Meesho's net payment, not your net profit. Your product cost and packaging have not been subtracted yet.
- Ignoring RTO rows. An RTO row can quietly show a ₹ -160 settlement. Scroll past a few of those in a thousand-row file and you have miscounted your profits by thousands of rupees. Always sum the RTO column separately.
Where a tool helps
Meesho Profit parses the whole file in one pass, groups sub-orders by SKU, applies cost inputs you configure once, and shows a clean P&L per product. If you are spending more than ten minutes per payment cycle reading rows manually, upload a file and see the numbers in thirty seconds.