Order AJ-52301: a ₹1,299 cotton kurta, dispatched on time, delivered without drama. The settlement statement pays ₹886. That ₹413 gap is not a scandal — most of it is the contractual cost of selling on a managed fashion marketplace. But buried inside the same statement, one cycle out of three, sits a line that should not be there: a penalty without an event, a return charged twice, a reversal that never reversed. You only catch those if you can read the statement line by line.
This is the decode. We will walk an illustrative AJIO settlement statement entry by entry, split the lines into the three kinds that behave differently, and end with the six-point error sweep worth running every cycle. Rupee figures and fee bands here are illustrative — your category rate card and seller agreement are the source of truth. (Robnu is independent software built for AJIO sellers; we are not affiliated with or endorsed by AJIO.)
The shape of an AJIO settlement statement
However the export is formatted in a given quarter, an AJIO settlement statement reduces to the same skeleton: an order identifier, a gross sale value, a stack of deductions, and a net payable. The deductions are where the reading skill lives, because they are not one kind of thing. They are three:
- Contractual lines. Commission (a percentage of sale value, set per category in your rate card) and logistics/processing fees. Predictable, negotiated, boring — exactly as they should be. The only check: is the rate applied the rate you signed?
- Reclaimable tax lines. 18% GST charged on commission and fees (input credit), GST TCS deposited against your GSTIN, and income-tax TDS under section 194-O deposited against your PAN. These come back to you through filings — they are timing costs, not real costs, provided you claim them.
- Event-driven lines. SLA penalties, return reversals, quality-dispute deductions, claim adjustments. Each one asserts that something happened in the real world. This is the only category where statements are regularly wrong — and the only one where reading carefully pays cash.
Walking the statement, line by line
Gross sale value (₹1,299). What the buyer paid for the item. Confirm it matches your listing price for that order date — price revisions occasionally desync.
Commission (−₹234). Charged per your category rate card. The number itself is not disputable; the rate is, if it differs from your agreement. Recompute the percentage on a few orders each cycle — rate-card drift after a category re-mapping is one of the quieter ways margins erode.
Logistics and processing fees (−₹89). The cost of moving and handling the parcel within AJIO's managed flow. Watch for weight-band or zone reclassifications you did not expect — a product that shipped in the 500-gram band for six months and suddenly bills in the next band up is worth a measurement and a query, because the reclassification applies to every order from that day forward, not just one.
GST on commission and fees (−₹58). 18% on the two lines above. Claimable as input tax credit against your GST output liability — make sure the marketplace invoices land in your GSTR-2B.
GST TCS (−₹6) and income-tax TDS (−₹1). Statutory deductions deposited on your behalf. Verify monthly: TCS as credits on the GST portal, TDS in Form 26AS. The check is not whether they were deducted — it is whether the deducted amounts were deposited.
SLA penalty (−₹25). Event-driven. The statement says you dispatched or confirmed late. Your manifest timestamps say what actually happened. When the two disagree, that is a dispute — and it is winnable, because timestamps are evidence.
Return reversal (₹0 here). When a delivered order is returned, an earlier settlement gets clawed back in a later cycle. The error pattern to watch: the same return charged in two different cycles, or a forward payment reversed for a return that was actually an exchange.
Build your expected-deductions baseline
Reading a statement well requires knowing what it should say before you open it — otherwise every line is plausible and nothing stands out. The baseline takes one sitting to build. Take ten recent orders across your main categories and compute, for each: gross price, commission at your rate-card percentage, the logistics fee for that weight band and zone, and 18% GST on the two. Add the statutory lines — TCS and TDS at current rates — and you have an expected net payable per order. Now every future statement gets compared against an expectation instead of being read cold. The payoff is speed: when AJ-52301 should settle at ₹911 and the statement says ₹886, the ₹25 difference jumps out in seconds, and it has to be one of two things — an event-driven charge (check whether the event happened) or drift in a contractual rate (check the rate card). Sellers who skip the baseline end up doing the same arithmetic from scratch on every suspicious line, which is exactly the friction that kills the habit by the third cycle. Build the expectation once; update it when your rate card or category mapping changes; reuse it forever.
One practical note on hygiene: download every settlement export the week it is issued and archive it with a consistent name — period, marketplace, file type. Statement formats change, portals re-organise, and a dispute filed in June may need a statement from March. Your archive is your evidence locker; treat it like one.
The six errors worth checking for, every cycle
From sellers we've sat with at 5–25 orders/day, the same handful of error patterns accounts for nearly everything recoverable. Ordered by how often each check finds money: commission charged at a rate other than your rate card (especially after a category change); return charges double-applied across two cycles; SLA penalties with no matching late event in your dispatch records; reversal credits missing after a won claim or accepted dispute; TDS/TCS totals that do not match what reached Form 26AS and the GST portal; and the quietest one — delivered orders that never appear in any settlement at all. The last one is invisible unless you reconcile from your order list toward the statement, not from the statement toward your orders.
A worked example of the double-charge check, because it is the highest-frequency find. Suppose order AJ-50117 was returned in March, and the March statement shows a return charge of ₹118 against it. In April's statement, an adjustments block lists AJ-50117 again — another ₹118, labelled slightly differently. Nothing about the April line looks wrong in isolation; it only becomes an error when you group return-related deductions by order ID across cycles and see the same order twice. That grouping takes one spreadsheet filter and zero judgment, which makes it the perfect first check for a seller new to auditing. The dispute is equally mechanical: two statement lines, one return record, a one-paragraph ticket. From sellers we've sat with, these small documentary disputes resolve faster than any other category — there is nothing to argue about.
From reading to reconciling
Reading one statement is a skill; reconciling every statement is a system. The working method is a three-way match — what your records say you shipped, what the marketplace says happened, what the bank says you were paid — run at the order level so a ₹25 phantom penalty cannot hide inside a ₹40,000 payout. We cover that full method in our payment reconciliation guide; the settlement statement is one of its three legs.
The cadence question answers itself once you know the windows. Settlement cycles arrive frequently enough that a monthly-only review means some disputable lines are already past their window by the time you see them. The workable rhythm at 5–25 orders/day is a ten-minute scan per statement as it lands — expected vs net for anything that looks off, plus a glance at every event-driven line — and a fuller monthly sweep using the six checks above. The scan catches the time-sensitive errors; the sweep catches the patterns. Neither requires software, though both get dramatically cheaper with it.
Where Robnu fits
Robnu is an agentic OMS with AJIO operations live today. It keeps every order tied to its slip, invoice, manifest, and settlement line — so when a statement pays short, you get a flagged order with evidence attached, not homework. Per-order margin comes from settled rupees, not sticker prices, and recoverable errors flow into claims; autonomous claim filing is rolling out now, with the rare one-click human approval where a marketplace flow requires it.
Robnu is free for everyone right now — every feature, every order, no card, no trial timer — while we work out paid pricing. When paid pricing launches, sellers under 25 orders/day stay free forever, and today's users keep grandfathered locked rates. If your AJIO statements currently get a glance and a sigh, start here: pull last cycle's statement and run the six checks. Thirty minutes, and you will know whether the leak is real.