Demystifying the Meesho Settlement Report: Stop Losing Track of Your Money
Every Meesho seller knows the feeling of looking at their bank account and wondering, "Did I actually make money on those 500 dispatches this week?" While Meesho offers a zero-commission model, they deduct shipping, returns, GST, and tax compliance fees at source. The only way to know your true net earnings is to read the payment reconciliation sheets.
This guide explains payment-report fields and row-level checks. For matching a payout to a bank receipt, continue to the Meesho payment reconciliation workflow. A report row alone is not proof that the bank received the money.
For most suppliers, opening the Meesho Settlement CSV is a confusing experience. With over 25 columns filled with technical terms, tax rates, and transaction IDs, it is easy to ignore the details. However, ignoring this report means you might be losing thousands of Rupees to double shipping fees, unclaimed returns, and tax mismatches. In this guide, we break down every single column of the Meesho payment CSV so you can audit your payouts like a pro.
Always download your payment reports in CSV format instead of PDF. CSVs allow you to use formulas, sort transactions by SKU, and upload files into automation tools for instant auditing.
How to Download the Meesho Payment CSV File
To get your hands on the raw settlement file, follow these simple steps:
- Log in to your Meesho Supplier Panel.
- On the left sidebar, click on Payments.
- Select the Payments Page tab.
- Find the specific payout date or click on Download Payout Report.
- Select your date range and export as CSV (Comma Separated Values).
The Meesho CSV Column Guide: What Every Field Means
These are common field labels, not a guaranteed schema for every export. Report names, columns and menu labels can change. Preserve identifiers as text, including leading zeroes, and check the report period and event date before combining files.
| Column Name | Data Type | Description & How to Audit It |
|---|---|---|
| Sub Order No | Text identifier | Order reference for matching reports. Store as text, not a rounded spreadsheet number. Multiple payment events can share it. |
| SKU | Text Label | Your Stock Keeping Unit identifier. Essential for calculating SKU-level profit. |
| Product Price | Currency (INR) | The base price at which you listed the product on Meesho (before shipping fees). |
| Quantity | Integer | Number of units ordered. Verify this if you pack multi-unit orders. |
| Shipping Charge | Deduction (-) | The forward shipping charge deducted. Ensure it matches your weight slab! |
| Return Shipping Charge | Deduction (-) | Deducted only if a customer returns the item. Check if this is charged on RTOs (it shouldn't be). |
| TCS Amount | Tax collection | Reconcile the recorded collection with the relevant tax records for that period. Do not treat an assumed refund as received cash. |
| TDS Amount | Tax withholding | Reconcile recorded withholding with your tax records and adviser. Tax credits and marketplace operating fees are different categories. |
| Compensation Amount | Credit (+) | Reimbursement from Meesho for damaged returns, lost shipments, or approved claims. |
| Net / Final Settlement Amount | Signed payment amount | Read the export definition. Fees already netted into this amount must not be subtracted again. Match the payout reference to the bank separately. |
Three checks before summing payment rows
- Distinguish duplicates from adjustments. An identical repeated event may be a duplicate export; a later return, compensation or correction on the same order is not automatically a duplicate. Compare event type, date, amount and reference.
- Keep the sign. A debit and a credit should not both become positive. Reconcile signed event totals before producing an order-level summary.
- Avoid double deductions. If net settlement already includes return shipping, show that fee as a diagnostic breakdown rather than subtracting it again. Use the export definition, not a guessed universal formula.
For a forecast before selling, use the profit calculator walkthrough. Do not mix forecast losses with actual payment events.
How to Investigate Unexpected Deductions
Now that you know what the columns represent, it is time to audit your file for common payment discrepancies. Look out for the following issues:
1. Double Forward Shipping Deductions
Sometimes, courier partners miscalculate the weight of your packages, pushing them into a higher slab. Compare the Shipping Charge column against your product weight. If a 200-gram item was charged ₹120 instead of ₹45, you can raise a ticket with the manifest proof.
2. Return Charges on RTO (Return to Origin)
Meesho’s public shipping guidance distinguishes customer-return shipping from RTO treatment. If a charge looks inconsistent, check the event classification, current policy and full order history before asking support to review it; do not assume every mismatch guarantees a refund.
3. Missing Compensations
If you filed a Safe-T claim for a damaged customer return and it was approved, check the Compensation Amount column in the subsequent payout files. Many sellers forget to verify if the approved refund was actually credited.
Automating Your Payment Audit: Move Beyond Spreadsheets
Manually auditing thousands of rows in Excel is exhausting and prone to errors. To scale your business, you need automated reconciliation.
📊 Audit Your Meesho Payouts in One Click
Upload a supported report to your account workspace and review the imported totals against your source. Dashboard imports use server-side processing and account storage; read the data-handling policy first. Bank matching still requires the relevant bank evidence.
Reconcile Payouts NowTry the workflow with your own data.
Open the matching Seller Analytics Hub tool and review the result before using it for dispatch or reporting.
