Skip to content
Robnu
Payments · Fix-it guide

Meesho payment not received? Trace where the money actually went.

A payout that never lands is rarely stolen and rarely a bug — it is almost always sitting in one of four places: not settled yet, held for a return window, consumed by deductions, or stuck between Meesho and your bank. This guide is the diagnosis ladder: check them in order, find the money, and escalate properly when it genuinely is missing.

Free during early access · Forever free under 25 orders/day
app.robnu.com/meesho/paymentsWhere a “missing” payout usually wentIllustrative split of missing-payment cases a seller investigatesNot settled yetcycle runs from delivery, not dispatchmost casesHeld for return windowreleased after the window closescommonConsumed by deductionspenalties, reversals, adjustmentsread the statementNegative balance carriedold shortfall repaid firstcheck carry-forwardGenuine payout failurebank re-verification, detail mismatchrareIllustrative — based on recurring patterns in seller community reports, not Meesho data.
TL;DR
  • Before anything else, check the expected payment date on the panel. Meesho settles on cycles counted from delivery — roughly 15 days for many accounts — so an order dispatched last week is not late, it is simply not due.
  • If the date has passed, read the payment statement line by line. Most 'missing' money is there in plain sight: return reversals, penalties, claim adjustments, and negative balance carried forward from an earlier bad cycle.
  • Only after those checks is it an escalation: one ticket with sub-order IDs and the statement extract attached, weekly follow-ups on that same thread, and a written escalation email if the thread goes quiet.
How Meesho settlement works

The clock starts at delivery, not at dispatch

The single biggest source of “payment not received” panic is a misunderstanding about when the clock starts. Meesho settles a sub-order on a cycle counted from the day the buyer received it — not the day you shipped it, and not the day the order was placed. An order you packed on the 1st might deliver on the 6th and settle in the second half of the month. Nothing is wrong; the money is on schedule. The panel prints an expected payment date against every sub-order, and that date is the only one that matters.

On top of the cycle sits the return window. For categories where buyers can return or exchange, the amount may be held until that window closes, because a return would reverse the payment anyway. And cycles themselves are policy, not law — Meesho has revised schedules before and will again, so check the current policy on the panel rather than trusting a number from a seller group. If today's date is before the printed expected date, stop here: the payment is pending, not missing.

app.robnu.com/payment-reconciliation/settlementThe settlement cycleMoney is earned on delivery, but paid on the platform's clockOrder placedday 0Deliveredbuyer receivesSettlement clockcycle runsPayoutcredited to bankNet payout = order value − commission − fees − TCS − TDSMeesho: 7-day cycle from deliverysettledReconcile every payout line against the settlement statement — that is where wrongdeductions hide. Robnu matches payout to order to adjustment, automatically.
The diagnosis ladder

Seven checks, in this order

Each step either finds the money or rules out a cause. Most sellers find the answer by step three — and the sellers who skip to step six get templated replies because they cannot yet say what is actually missing.

  1. 01

    Check the expected payment date

    Open the payments section and find the sub-order. If the expected date is in the future, the payout is not late — the cycle runs from delivery. Set a reminder for that date and stop investigating. Chasing support before the printed date wastes a week and gets a copy-paste answer.

  2. 02

    Check for a return-window hold

    If the product category carries a return or exchange window, the amount can sit in a held state until the window closes. A held payment looks missing but is really queued. The order's payment row on the panel shows its state — held is not gone.

  3. 03

    Download and read the payment statement

    This is where most missing money lives. The statement lists every deduction per sub-order: fees, GST on fees, shipping charges, return reversals, penalties, claim adjustments. A ₹450 sale can legitimately settle at a fraction of that after a return-heavy week. Read it line by line before deciding anything was skipped.

  4. 04

    Check for a negative balance carried forward

    If an earlier cycle's deductions exceeded its earnings, the shortfall rolls into this cycle and is repaid first. The statement shows the carried-forward figure. A payout that arrives at ₹0 with healthy current orders almost always has an old negative balance behind it.

  5. 05

    Rule out a banking-side failure

    If the statement says paid but the bank shows nothing after a couple of working days, the problem is between Meesho and the account: a re-verification pending, a changed account number, an IFSC mismatch, or a name mismatch flagged by the bank. Re-verify bank details on the panel and check with the bank before blaming the marketplace.

  6. 06

    Raise one precise ticket

    Now you can escalate properly: one ticket listing the sub-order IDs, the expected payment date from the panel, the statement rows for those orders, and the bank statement showing no credit. Precise tickets get routed to the payments team; vague ones get the template.

  7. 07

    Follow up weekly — on the same thread

    Reply to the same ticket every week with a dated, factual nudge. Fresh tickets reset the queue and fragment your evidence. If several follow-ups produce nothing, send a written escalation email referencing the ticket number, the amounts, and the dates — a paper trail beats a phone call.

The real cost

Unread statements are where margins go to die

Here is the uncomfortable version: a payment that never arrives at all is rare, gets noticed, and gets chased. A payment that arrives ₹180 short does not. Multiply a quietly short payout across two cycles a month and a seller doing 15 orders a day can lose a few thousand rupees a month to deductions nobody verified — reversals for returns that were never actually received back, penalties that qualified for a waiver, weight adjustments on parcels that were packed correctly. Illustrative numbers, but every experienced Meesho seller recognises the shape.

The fix is not heroic effort; it is a habit. Every cycle, put the statement next to your own order list and answer one question per sub-order: does the credited amount match what this order should have paid? The gap between sellers who do this and sellers who do not is usually a full margin point or more — on the same products, the same marketplace, the same month.

The one-thread rule
When you do escalate, keep everything on one ticket. Support queues treat every new ticket as a new case with no history. A single thread with weekly dated follow-ups, sub-order IDs, and the statement extract is the difference between a payments-team review and an endless loop of first-line replies.
app.robnu.com/reconciliation/2026-04Payment reconciliationPayouts ↔ Orders ↔ Adjustments — line by linePayoutsAJIO settlement fileOrdersshipped + deliveredAdjustmentsdeductions + claimsMatch enginededup_key + amount + AWBOR-7782 · ₹1,249 · ✓OR-7783 · −₹47 · ΔOR-7784 · ₹890 · ✓ReconciliationBatch · BATCH-2026-04-26218 matched · 7 deltas · ₹1,348 recoverable₹+1,348
The Robnu way

Reconciliation is a job. Robnu does the job.

Everything on this page is checkable by hand — and almost nobody checks it by hand every cycle, because a two-person team has orders to pack. Robnu does the checking as a matter of course: it tracks what every AJIO and Meesho sub-order should pay, reads settlement lines as they land, and raises a flag the day a payout comes up short, late, or missing — with the expected date, the actual credit, and the deduction rows already lined up side by side.

When a deduction deserves a fight, Robnu assembles the evidence and files the claim. Fully-autonomous filing is rolling out now — the rare claim that needs judgement still asks you for one approval click, and everything else just proceeds. You find out about missing money the day it goes missing, not the month after.

app.robnu.com/reconciliation/2026-04Payment reconciliationPayouts ↔ Orders ↔ Adjustments — line by linePayoutsAJIO settlement fileOrdersshipped + deliveredAdjustmentsdeductions + claimsMatch enginededup_key + amount + AWBOR-7782 · ₹1,249 · ✓OR-7783 · −₹47 · ΔOR-7784 · ₹890 · ✓ReconciliationBatch · BATCH-2026-04-26218 matched · 7 deltas · ₹1,348 recoverable₹+1,348
FAQ

Missing Meesho payments, answered

Four explanations cover almost every case: the order has not reached its settlement date yet (Meesho pays on roughly 15-day cycles counted from delivery, not from dispatch), the amount is being held while the return or exchange window runs, the payout was issued but penalties and return reversals consumed most of it, or the money left Meesho and is stuck on the banking side — usually a re-verification or account-detail mismatch. Work through them in that order before assuming Meesho simply did not pay. The panel's payment section answers the first three; your bank answers the fourth.

Settlement is counted from the delivery date, and the panel shows an expected payment date against every sub-order. Cycles run in the region of 15 days for many sellers, but the exact schedule depends on your account and can change — always trust the date printed on the panel over anything you read in a seller group. If today is before that date, the payment is not late; it has not happened yet. Chasing support before the printed date rarely produces anything except a templated reply.

Download the payment statement from the payments section of the supplier panel for the cycle in question. It lists, per sub-order, the sale amount and then every line that reduced it: commission-style fees, GST on those fees, shipping charges, return reversals, penalties, claim adjustments, and any negative balance brought forward from an earlier cycle. Most 'missing' payments are sitting in that file as a stack of deductions. Read it line by line before raising a ticket — you will either find the money or have the exact rows to dispute.

If a cycle's deductions — returns reversed, penalties, adjustments — exceed what Meesho owed you for that cycle, the shortfall becomes a negative balance that carries forward. Your next payout first repays that hole, and only the remainder reaches your bank. A seller who had a heavy-return fortnight can see two or three later payouts arrive smaller than expected or not at all, without anything being wrong with the current orders. The statement shows the carried-forward figure explicitly; check it whenever a payout looks short.

Raise one ticket from the supplier panel with the sub-order IDs, the expected payment date from the panel, and the relevant rows of the payment statement attached — specific beats angry. Then follow up on that same ticket weekly; opening fresh tickets resets you to the back of the queue every time. If the thread produces nothing after a few cycles of follow-up, move up a level in writing: a firm, factual escalation email that references the ticket number, the dates, and the exact amount, and states what resolution you expect.

Robnu reconciles every payout against every order automatically for AJIO and Meesho. It knows what each sub-order should have paid, reads the settlement lines as they land, and flags the gap the day it appears — settled short, held, consumed by a penalty, or simply absent. Instead of discovering a hole weeks later while reading a spreadsheet at midnight, you get the discrepancy with the evidence already assembled: order value, expected date, actual credit, and the deduction rows that explain the difference. When a claim is worth filing, Robnu files it — a rare one still asks you for a single approval click.

Sources

Where this comes from

  • Meesho supplier panel documentation on payment cycles, payment statements and bank verification: supplier.meesho.com learning hub.
  • Recurring seller reports of held, short and delayed payouts and support-escalation outcomes: public seller community threads (Reddit r/IndiaBusiness, seller Facebook and Telegram groups), 2024–2026.
  • Statutory marketplace deductions referenced: TCS at 0.5% under GST s.52 and TDS at 0.1% under s.194-O (post-2024 revisions).
build c3ffebc77e7004ab28f3be8d8e290923969592fe · 2026-07-08T12:37:42+05:30