What is Meesho payment reconciliation?
Payment reconciliation means checking each distinct sub-order against its payment events, return outcome and bank payout. A missing row in one export is a question to investigate, not proof that Meesho has withheld money. Returns, adjustments and a report's date range can change where a payment appears.
Meesho's supplier guidance describes a seven-day payment cycle from delivery and says suppliers can see deposited and future payments in the Supplier Panel. Use the current Panel and your own bank statement for an individual payout. This public statement does not establish a universal dispute deadline or guarantee that every order settles on the same calendar day.
Collect the records for the same account
- Orders: Sub-order ID, account, order date, delivery or return state and seller SKU.
- Payments: All rows for those sub-orders, including later negative and positive adjustments.
- Returns: RTO or customer-return status and whether the parcel physically came back.
- Bank: Credits and payout references for the period you are checking.
Keep the original downloads. Reports may name columns differently, so identify the sub-order key and signed amount before calculating totals. The payment CSV guide gives a field-by-field starting point.
Match by sub-order before summarising
- Choose one seller account and a date range that includes the order period plus later payment and return events.
- Count each sub-order once in the order list. Do not treat repeated lifecycle or status rows as extra sales.
- Join payment events by sub-order. Keep every legitimate adjustment and its sign; do not keep only the first row.
- Classify delivered, customer-return and RTO outcomes separately. Check returned inventory where relevant.
- Compare the resulting payout reference or batch with the bank credit. A bank transfer can cover more than one sub-order.
Also list payment rows that have no matching order in the selected export. They may belong to an earlier order or a missing Orders file. Do not silently remove them or label them as profit. For SKU margin, add product and operating costs only after the payment join is sound.
What is Meesho payment proof?
There are three different records: a Supplier Panel status or future-payment line, a payment report entry, and an actual bank credit. A scheduled payout is not yet bank proof. For a support query, save the sub-order ID, relevant payment rows, payout reference if present, bank statement extract for the date range, and the return or delivery status. Share only the documents the current support flow requests.
Payment date, transaction date and bank credit date can differ. If a value looks wrong, check those dates and the report filter before assuming the amount is missing. Avoid inventing a fixed “7 to 15 days” rule or a universal 30 to 45-day dispute window from an unsourced article.
Investigate the exception, then raise the right query
| Exception | First check | Evidence to keep |
|---|---|---|
| Delivered, no payment row | Delivery date, future payment view and later report windows | Sub-order, delivery proof and report filters |
| Payment row, no order row | Other account or earlier order export | Raw row and source file name |
| Return marked complete, parcel absent | Tracking and warehouse receipt log | Return status, tracking and handover records |
| Bank amount differs | Payout grouping and signed adjustments | Payment rows, reference and bank entry |
When the records still disagree, use the current Supplier Panel support route for the relevant payment or return issue. State the sub-order, expected event, observed event and attached proof. Save the ticket ID and check the actual payment report and bank record again after resolution. A support response by itself does not prove cash was received.
Review orders and payments together
Use your imported reports to inspect order and payment differences, then verify each exception in the Supplier Panel and bank records.
Open Seller DashboardTry the workflow with your own data.
Open the matching Seller Analytics Hub tool and review the result before using it for dispatch or reporting.
