Meesho Payout Reconciliation: A Practical Guide
Meesho suppliers run on volume: thousands of low-value sub orders, settled in rolling cycles, with returns and RTO recoveries constantly flowing against new payments. In that environment, an unreconciled book is not slightly wrong, it is unknowably wrong. Payout reconciliation is the routine that keeps you certain Meesho paid what it owed, and it is entirely mechanical once you know the joins. Here is the process.
The three documents and their join keys
- GST sales report: what you supplied; joined to settlements by Sub Order No.
- Payment statement: what Meesho paid per sub order, with Payment Date, UTR, Final Settlement Amount, commission (incl. GST), GST on Commission, TCS and TDS; joined to the bank by UTR.
- Bank statement: what actually arrived.
Reconciliation is walking these joins in both directions: every bank credit decomposes into sub orders, and every shipped sub order eventually resolves into a payment, a return, or an RTO.
The five-step cycle
- Export the payment statement for the period and group rows by UTR, totalling Final Settlement Amount per group.
- Match each UTR total against a bank credit; the UTR itself usually appears in the bank narration, making this exact rather than approximate.
- Explain the composition of each UTR: positive rows are settlements, negative rows are recoveries for returned or RTO'd sub orders settled earlier. Both must be included or totals will not tie.
- Sweep for orphans: shipped sub orders absent from all statements beyond the normal payout cycle go on a follow-up list; aged ones become support tickets.
- Post in TallyPrime only what reconciled: receipt per UTR, commission and GST-on-commission journals, TCS and TDS to receivables, recoveries netted against their credit notes.
Reading the failures
| Symptom | Likely cause | Resolution |
|---|---|---|
| UTR total ≠ bank credit | Negative recovery rows excluded from the group | Re-total including negatives |
| Bank credit with no statement UTR | Statement export window missed a cycle | Re-export with wider dates |
| Sub order never settled | Return/RTO in progress, or settlement hold | Check sub order status; escalate if aged |
| Recovery with no matching credit note | Return or RTO event not yet booked | Book the credit note; see the RTO guide |
| TCS/TDS totals look off | Returns reduce the base; timing straddles months | Reconcile at sub order level against the statement columns |
The party ledger as your truth meter
Post sales at Total Invoice Value, credit notes for Return and RTO events, commission and tax entries, and UTR receipts, all against the Meesho party ledger, and the ledger balance acquires a precise meaning: the value of sub orders shipped but not yet settled. Check that number against a filtered view of your recent unsettled orders and you have a single-figure health test for the entire month's bookkeeping. When it drifts, the drift amount itself usually identifies what was missed.
Automating the mechanical layer
Every step above except the judgement calls is deterministic, and Meesho's lack of a public seller API does not prevent automation, it just means automation starts from files. TallySutra ingests the payment statement and GST sales report you export from the supplier panel, performs the UTR grouping, sub-order matching and recovery pairing automatically, and produces balanced TallyPrime vouchers for everything that ties out, with duplicate-safe re-imports keyed on Sub Order No. Whatever does not reconcile, orphaned recoveries, arithmetic that fails, unmatched sub orders, is held in an exception queue for you or your CA to resolve, and the CA review step gates the final export. The judgement layer, disputing short settlements, deciding an aged orphan is a write-off, stays with you, which is where it belongs.
Suppliers who reconcile monthly catch short payments while Meesho support can still act on them and walk into GST filings with books that match the marketplace record. Suppliers who do not are, at best, trusting a counterparty's automation with their entire cash flow. The process above takes a morning with spreadsheets or minutes with tooling; either way, it is the least optional part of Meesho accounting.
A final word on cadence: reconciliation debt compounds. One skipped month means the next reconciliation carries two months of recoveries crossing periods, and by a quarter the orphan list becomes archaeology. Suppliers who hold the monthly line spend an hour; suppliers who lapse spend days and still end up with write-offs nobody can explain. Put the reconciliation on a fixed calendar day, keep the working file from each month, and the process stays an hour forever.
Frequently asked questions
How do I match Meesho payments to my bank statement?
Group payment statement rows by UTR and total the Final Settlement Amount per group, including negative recovery rows. Each UTR total should equal one bank credit, and the UTR reference typically appears in the bank narration, so matching is exact. Discrepancies almost always trace to excluded negative rows or an export window that missed part of a settlement cycle.
What are the negative amounts in my payment statement?
Recoveries. A sub order paid in an earlier cycle was subsequently returned by the customer or RTO'd, and Meesho claws the earlier payment back in the current cycle. Each recovery should pair with a credit note for the underlying event in your books. Excluding them from UTR totals is the most common reason reconciliations fail to tie to the bank.
How long should I wait before chasing an unsettled sub order?
Know your normal payout cycle first, settlements follow delivery plus the return window, then flag sub orders unsettled meaningfully beyond it. Delivered sub orders with no settlement, return, or RTO event after the customary cycle deserve a supplier support ticket citing the Sub Order Nos. A standing orphan list, refreshed at each reconciliation, is what keeps these from silently expiring.
TallySutra turns Amazon, Flipkart and Meesho reports into reconciled, reviewed TallyPrime vouchers — duplicate-safe, with every rupee traceable to its source row.
Book a 30-minute demo