Meesho payments: when the money actually lands.
The settlement cycle decides your cash flow, and the deductions decide how much survives it. Here is the timeline, everything taken out before you are paid, and how to tell a normal gap from a wrong one.
- Meesho settles on a cycle, not per order — today's delivery lands in a future payout.
- Your bank credit is net of commission, shipping, RTO, penalties and tax. A gap is normal; the size of it is what to check.
- Sale revenue and its associated costs do not always fall in the same cycle, which makes settlements look wrong when they are not.
- TCS is not a cost — it is your money, claimable as credit. Most small sellers never claim it.
- Robnu reconciles each settlement order by order and flags what does not add up. Free while we figure out pricing.
“When do I get paid, and why is it less than I expected?” are the two questions behind almost every payment search a Meesho seller makes. The answers are connected: the cycle explains the timing, and the deduction stack explains the amount.
Why the money arrives later than the sale
Marketplaces settle in batches. An order is only eligible for payment once delivery is confirmed and the return window has moved on sufficiently — because a delivered order can still become a return, and the platform is not going to pay you for a sale that may reverse.
For a growing seller this creates a real working-capital problem: you have paid for stock and shipping now, and you are paid for it later. Understanding the cycle is what lets you plan around that gap rather than being surprised by it every month.
What comes out before you are paid
Each of these is applied before the credit reaches your bank. Knowing the list is how you spot the one that should not be there.
Commission
The platform’s share of the sale. Predictable and rarely wrong — check it against the rate for your category if a payout looks materially off.
Shipping and RTO
Forward freight, plus reverse freight on any return to origin. The most error-prone line — weights and duplicates are worth checking.
Penalties
SLA misses, cancellations and policy breaches. Unlike the others, this is the category you can drive to near zero through dispatch discipline.
TCS and TDS
Statutory deductions held against your GSTIN and PAN. Not a cost — money you can claim back at filing time, and frequently forgotten.
Knowing what you should have been paid
Checking a settlement properly means matching every order to its deductions and asking whether each one is correct. Done honestly for a month of orders, that is hours of work — which is why almost nobody does it, and why errors persist quietly.
Robnu is an agentic OMS. It reads each settlement, reconciles it order by order against what the charges should have been, and flags the lines that do not hold up — wrong weights, duplicate reverse charges, penalties applied to orders you dispatched on time. Where a claim is warranted it is prepared and filed, with a rare approval click while fully-autonomous filing rolls out.
You sell. Robnu runs the rest — and makes sure every rupee is paid correctly.
Meesho payments, answered
Meesho settles on a defined cycle rather than per order, so payment follows delivery by a set period rather than arriving immediately. The practical implication is that money from an order delivered today lands in a future cycle, not this week. Your Supplier Panel shows the payment date attached to each settlement, and that date is the one to plan cash flow around.
Because the payout is net of everything deducted first: commission, shipping, any RTO or return costs, penalties for SLA misses, and tax components such as TCS and TDS. The gap between order value and bank credit is normal — but the size of that gap is what deserves checking, because errors hide inside it.
Typically commission on the sale, forward and reverse shipping where applicable, return and RTO charges, any penalties applied for policy or SLA breaches, and statutory deductions. Each is individually small and collectively significant, which is why reconciling per order rather than per total is the only way to see what actually happened.
Work through it in order: confirm the settlement was actually generated for that cycle, check your registered bank details are current and verified, look for a hold or pending state against specific orders, and confirm no compliance flag is blocking release. Most delayed payments resolve into one of those four rather than a genuine platform failure.
It can. An order that goes to return to origin does not generate the sale revenue, and the associated freight deduction may land in a later cycle than you expect. That timing mismatch is a common reason a settlement looks wrong — the sale and its costs are not always in the same period.
Take the settlement report and reconcile it order by order rather than comparing totals. For each order confirm the sale value, then each deduction against it. This is tedious by hand and it is the only reliable way to catch a wrong charge — a total that looks roughly right can hide several offsetting errors.
TCS is tax collected at source, deducted by the marketplace and deposited against your GSTIN. It is not a cost — it is your money held with the tax authority and claimable as credit when you file. A striking number of small sellers never claim it, which turns a temporary deduction into a permanent loss.
Claim windows are defined and short, varying by the type of issue. This is the practical argument for reconciling every cycle rather than quarterly: an error found three months later is usually an error you can no longer recover, however clearly wrong it was.