Start with the report and payout period
A payment report can show what the marketplace recorded for an order, but it does not by itself answer whether the order was profitable or confirm that a bank credit arrived. To understand the outcome, match payment events to distinct sub-orders, add your own product and operating costs, and reconcile the payout with your bank statement.
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.
Payment exports can contain identifiers, adjustments and event rows that are easy to misread when opened in a spreadsheet. This guide explains common fields and checks to run against the files available in your Supplier Panel. Column names and export formats can change, so compare the guide with the report you actually downloaded.
When the Supplier Panel offers a CSV for the report you need, it is usually easier to filter, sort and reconcile than a PDF. Keep the original export unchanged, preserve identifiers as text, and confirm the date range and report type before combining it with other files. A CSV still needs review: spreadsheet formulas or imports do not establish that a payout reached your bank.
How to Download the Meesho Payment CSV File
Open the Payments area in your Meesho Supplier Panel and choose the payment or settlement report for the period you need. Download the format offered for that report; it may be CSV or another spreadsheet format. Panel labels and report options can change, so follow the controls currently shown in your account.
The Meesho CSV Column Guide: What Every Field Means
Exports differ by report and can change over time. The examples below are fields to look for when they appear, not a promise that every file contains them. Preserve identifiers as text, including leading zeroes, and check the report period and event date before combining files.
| Field to look for | What to check |
|---|---|
| Sub-order reference | Use the identifier defined by that report to connect related order and payment records. Store it as text to preserve leading zeroes and suffixes. |
| Supplier SKU or product reference | Check that the code belongs to the same seller account and item before grouping. Similar product names do not prove a SKU match. |
| Sale or order value | Read the report's definition and amount sign. Do not treat a listed price as the seller's net proceeds. |
| Shipping, return or other adjustment | Identify the event type, date, amount sign and order reference. Compare with the relevant order record and current policy; do not assume a universal rate or that an event is automatically incorrect. |
| TCS or TDS field | Keep the tax collection or withholding separate from operating costs, and reconcile it with the correct tax statement and period. |
| Compensation or credit | Check the related case or adjustment reference and confirm whether the amount is included in the settlement total. |
| Net or settlement amount | Use the report's definition and match its payout reference to the bank separately. Do not subtract a fee twice if it is already included. |
When a report includes TCS or TDS, keep those entries separate from operating fees and reconcile them to the right tax statement and period. Our Meesho GST, TDS and TCS reconciliation guide explains how these records differ, including the 2026 income-tax transition. Confirm the treatment for your own return with a qualified tax adviser.
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 check an unexpected payment entry
A charge that looks unfamiliar is a reason to trace the record, not proof of an overcharge. Before raising a query, check:
- Match the sub-order or other available reference to the correct order and shipment.
- Read the event type, date, sign and amount together. A later return, correction or compensation can appear as a separate event.
- Compare the entry with the corresponding order, return, invoice or current policy document. Do not infer a universal fee from a single row.
- Keep the source report and supporting reference, then use the current Supplier Panel support route if the records still do not agree.
Match the payment report to the bank
First reconcile report events to distinct sub-orders; then match the payout reference and amount to the bank statement. Keep payment events, seller-entered costs and any tax records separate so a spreadsheet does not count the same deduction twice. For a forecast before selling, use the profit calculator walkthrough; forecast assumptions are not actual payment events.
Common questions
Where do I find a Meesho payment or settlement report?
Open the Payments area in your current Supplier Panel and choose the report and period that match the question you are checking. Menu labels and available formats can change; use the download options shown in your account.
Is TCS the same as TDS or a marketplace fee?
No. TCS and TDS are different tax collection or withholding records, not interchangeable operating fees. Match each reported amount to the relevant tax statement and period, and ask your tax adviser about its treatment.
Does a payment report prove that the money reached my bank?
No. Match the payout reference and amount from the report to the corresponding credit in your bank statement. A marketplace report alone is not proof of a bank deposit.
Reconcile the report against your records
Upload a supported report to your account workspace and review its imported totals against the source file. 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.
