AJIO payout doesn't match your orders? Here's how to prove it.
A payout that feels short is not evidence; an order-by-order reconciliation is. This guide shows you how to build the expected line for every order, tag each difference by its real cause — reversals, freight slabs, adjustments, tax lines — and turn what is left into one mismatch ticket AJIO's support can actually act on.
- Reconcile by order, never by week. The expected line per order is: order value minus commission minus freight minus known adjustments. Compare that against the actual credit for the same order ID — weekly totals hide everything.
- Most scary payouts are cycle lag, not theft: this week's payout carries reversals from last month's returns and RTOs. Match every reversal to its original order before calling it a mismatch — and keep TCS/TDS tax lines out of your fee maths.
- What survives the tagging is your real mismatch list. Raise it as one ticket: statement extract, order IDs, expected-vs-actual per line. And if a whole cycle simply never arrives, that is a stall, not a mismatch — a different problem with a different playbook.
A payout is hundreds of order-level lines wearing a trench coat
What lands in your bank as one AJIO credit is really the sum of many per-order calculations: each delivered order's value, minus its commission, minus its freight, plus or minus corrections — and then, layered on top, reversals for earlier orders that came back as returns or RTO after you had already been paid for them. Two payouts of the same total can have completely different stories underneath.
This is why the weekly-total instinct — “last week ₹18,000, this week ₹11,000, something is wrong” — proves nothing. Maybe this week absorbed a wave of return reversals from a heavy sale month. Maybe a freight slab changed. Maybe a real mismatch is hiding in there. The only method that separates these is building the expected line per order and letting the statement confirm or contradict it, one order ID at a time. Everything else in this guide is that method, step by step.
Seven steps from suspicion to a ticket that sticks
Run the steps in order. Most of the fear dissolves at step five; what survives step six is real money worth chasing.
- 01
Pull the statement and the order list
Download the settlement statement for the cycle from the panel, and export your orders for the matching period plus the previous few weeks — reversals reference old orders, so a too-narrow window is the first way reconciliation goes wrong.
- 02
Build the expected line per order
For every delivered order: order value − commission (your category's current rate) − freight (your slab) − any known adjustment = expected payout. Use your actual rate card from the panel, not remembered percentages — half of all imagined mismatches are stale assumptions.
- 03
Match actual credits to order IDs
Walk the statement and attach every credited line to its order. Whatever matches your expected line within a rupee or two is done. Park the rest — unmatched credits, missing orders, deltas — on a working list with the raw statement text kept alongside.
- 04
Tag every delta by cause
Five usual suspects: a return/RTO reversal referencing an earlier order; an adjustment with no obvious reference; freight billed at a different slab than assumed; a penalty; or a TCS/TDS tax line misread as a fee. Give every parked line one tag — the tag decides what happens next.
- 05
Check for cycle lag before crying foul
This week's payout contains last month's reversals. A heavy return period shows up weeks later as a light payout that looks wrong but is arithmetically correct. Trace each reversal to its original order and date; if the story checks out, close the line — that is lag, not loss.
- 06
Build the mismatch list
What is left is your real dispute: adjustments nobody can explain, freight slabs that do not match your agreement, penalties without a cause, credits that never arrived. For each line, record order ID, expected, actual, delta, and tag. This list is both your ticket and your evidence.
- 07
Raise it as one consolidated ticket
One ticket, statement extract attached, order IDs listed, expected-vs-actual per line. Precise beats loud. Keep the ticket number, add follow-ups in the same thread, and re-check the next cycle to confirm corrections actually land — a promised fix is not a credited fix.
Small deltas, never checked, compound into a salary
An illustrative picture: a seller doing 15 AJIO orders a day, with an unnoticed average leak of ₹20 per order — a slab difference here, an unexplained adjustment there — is losing roughly ₹9,000 a month, over a lakh a year, without a single dramatic incident. Documented seller reports across marketplaces consistently describe this shape: not one big theft, but a drizzle of small deductions that no one reconciles because each individual line feels too small to chase.
The counterweight is boring consistency: reconcile every cycle, tag every delta, dispute the real ones while they are fresh. Statements and panel data have practical retrieval limits, and support conversations about last quarter's lines are far harder than conversations about last week's. Fresh disputes with clean evidence get corrected; stale suspicions get sympathy.
Reconciliation is a job for software that never gets bored
Everything in the seven steps above is mechanical: build expected lines, match credits, trace reversals, tag deltas. Robnu does it continuously for every AJIO and Meesho order — each settlement is checked against what each order should have paid, reversals are linked back to their original orders so cycle lag explains itself, and tax lines stay separated from fees so the picture stays honest.
What reaches you is the part that needs a human: a mismatch list with the evidence already assembled, and claims raised for the recoverable lines. Fully autonomous claim filing is rolling out — the rare claim still asks you for one approval click — and every recovered rupee shows up where you can see it, against the order it came from.
AJIO payout mismatches, answered
Usually one of five reasons: return or RTO reversals from earlier orders landing in this cycle, an adjustment line without an obvious reference, freight charged at a different slab than you assumed, a penalty you did not notice, or TCS and TDS tax lines being read as fees. The only way to know which is to reconcile order by order — build what each order should have paid, compare it to what actually credited, and tag every difference by cause instead of judging the payout by its weekly total.
Build an expected line per order: order value minus commission minus freight minus any known adjustment equals expected payout. Then pull the settlement statement, match every credited line back to its order ID, and compare. Anything that matches is done; anything that does not goes on a mismatch list with its delta and your best guess at the cause. It is tedious in a spreadsheet at 20 orders a day — which is exactly why most sellers never do it and never learn how much they quietly lose.
Reversals are earlier payouts being taken back — most often because an order you were already paid for was returned or came back as RTO, and the marketplace recovers the amount from a later cycle. Adjustments are corrections of any kind: a recalculated fee, a penalty, a claim credit. The trap is that these lines reference old orders, sometimes weeks old, so they look like mystery deductions against this week. Always match a reversal to its original order before treating it as an error.
No — they are tax lines, not marketplace charges, and misreading them inflates your sense of being overcharged. Marketplaces collect TCS under GST section 52 (0.5% after the 2024 revisions) and deduct TDS under income-tax section 194-O (0.1%). Both are deposited against your registrations, and the TCS credit can be claimed in your GST filings. Keep tax lines in their own column when reconciling, so your fee analysis stays clean and your mismatch list only contains genuine mismatches.
One consolidated ticket beats ten vague ones. Include the settlement statement extract covering the disputed lines, the order IDs affected, your expected-vs-actual figure per order with the delta, and one sentence per line naming the suspected cause — unexplained adjustment, freight slab difference, missing credit. Precise tickets get routed to someone who can act; a ticket that says the payout looks short gets a template reply. Keep the ticket number and screenshots, because follow-ups work best when the whole history sits in one thread.
Robnu builds the expected-vs-actual line for every AJIO order automatically: what the order should have paid after commission and freight, matched against what the settlement actually credited, with reversals traced back to their original orders so cycle lag stops looking like theft. Genuine mismatches surface as a ready-made list with the evidence attached, and Robnu raises claims for recoverable amounts — fully autonomous filing is rolling out, and the rare claim still asks you for one approval click. You see one honest number: what you earned, what you got, and the gap.
Where this comes from
- AJIO seller panel settlement statements and seller-facing documentation on payment cycles and deduction lines.
- GST section 52 (TCS at 0.5% post-2024 revisions) and Income-tax section 194-O (TDS at 0.1%) as they apply to marketplace settlements.
- Documented seller reports of payout discrepancies, reversal confusion, and reconciliation practices in public seller communities, 2024–2026.
Related guides & pages
AJIO payment not received
When the cycle never credits at all — the stall playbook.
Settlement cycles
How marketplace payment cycles actually work, and why timing confuses everyone.
Meesho charges
The same deduction anatomy on Meesho, decoded line by line.
Payment reconciliation
How Robnu checks every settlement against every order for you.