Skip to content
Robnu

Your AJIO settlement, line by line.

Dense, unfamiliar, and easy to accept without reading — which is exactly why discrepancies survive in it. Here is what each section represents, how to reconcile it properly, and which mismatches are worth raising.

Free during early access · Forever free under 25 orders/day
app.robnu.com/protect/deductionsDeduction categoriesWhere money typically leaks · illustrativeSLA missDisputableQuality disputeDisputableMis-pickSunkLate ackDisputableRTO leakSunkSlip mismatchDisputableDISPUTE-READYRobnu surfaces them
TL;DR
  • The settlement reconciles your sales against commission, logistics, returns, adjustments and tax.
  • Reconcile order by order, never by comparing totals — offsetting errors hide inside a plausible total.
  • The most-missed discrepancy is an order absent from the statement entirely.
  • Your dispatch weight record is what turns a suspected logistics overcharge into a documented one.
  • Robnu reconciles each AJIO settlement automatically and flags what does not match. Free while we figure out pricing.

AJIO is live on Robnu today, and settlement reconciliation is where most AJIO sellers quietly lose money. Not through large obvious errors — through small ones that nobody has time to chase across a dense report every cycle.

How to read it

Totals lie, orders do not

The instinct with any settlement is to check whether the final number looks about right. It is the least useful thing you can do. A total within your expected range can contain an overcharge on one order offset by a missing deduction on another — both wrong, neither visible.

Reconciling per order is slower and it is the only method that finds anything. For each order: was the sale value right, was each deduction attached to it justified, and is the order present at all.

The absence problem
A wrong number draws the eye. A missing order does not. Orders that never appear on a settlement are among the most common and least detected discrepancies, because noticing them requires comparing against your own records rather than reading the statement.
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
Section by section

What each part of the statement covers

Exact labels and formats change over time — check against your current statement. The categories below are what you are looking for regardless of naming.

Section 1

Sales and order value

What you sold in the period at recorded values. Check for orders you shipped that do not appear, and for values that differ from the listing price you expected.

Section 2

Commission and fees

The platform’s share. Usually predictable — verify the rate applied matches your category, particularly after any catalogue changes.

Section 3

Logistics and returns

Forward and reverse freight. The most error-prone section: check weights against your dispatch record and look for returns charged that you never received.

Section 4

Adjustments and tax

Corrections, penalties, TCS and TDS. Any adjustment without a clear order reference is worth querying. Tax components are reclaimable, not costs.

app.robnu.com/ajio/settlement-errorsWhere AJIO settlement errors hideRanked by how often they go undetectedOrder missing entirelyhardest to spotReturn charged, never receivedcostlyWeight mismatch on freightcommonUnreferenced adjustmentquery itIllustrative. Bar length reflects how easily each error escapes a totals-level check.
app.robnu.com/protect/deductionsDeduction categoriesWhere money typically leaks · illustrativeSLA missDisputableQuality disputeDisputableMis-pickSunkLate ackDisputableRTO leakSunkSlip mismatchDisputableDISPUTE-READYRobnu surfaces them
The Robnu way

Reconciliation that happens every cycle

Per-order reconciliation is the right method and almost nobody sustains it, because it means re-reading a dense report every cycle while also running the business. The work gets deferred, and deferred reconciliation finds errors that are no longer claimable.

Robnu is an agentic OMS with AJIO live today. It ingests each settlement, matches every line against your order and dispatch records, and flags what does not reconcile — missing orders, returns billed but never received, freight computed on the wrong weight. 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.

FAQ

AJIO settlements, answered

It is the periodic report showing what AJIO has paid you and what was deducted before payment. It reconciles your sales for the period against commission, logistics costs, returns, adjustments and tax components. The credit that reaches your bank is the net of everything on it, which is why reading the statement rather than just the final figure matters.

Because commission, shipping, return costs, any adjustments and statutory deductions are all applied first. A gap between gross order value and net credit is entirely normal. What you are checking for is not whether there is a gap, but whether each component of that gap is correct and explicable.

Work order by order rather than comparing totals. For each order in the period, confirm the sale value recorded matches what you expected, then check each deduction attached to it. Totals can look approximately right while containing several errors that offset one another, which is exactly how discrepancies survive undetected.

Orders missing from the settlement entirely, returns charged that you have no record of receiving, logistics costs computed on weights that do not match your dispatch records, and adjustments applied without a clear reference to the order they relate to. The missing-order case is the easiest to overlook because an absence is harder to notice than a wrong number.

Establish first whether the statement itself is wrong or whether the payment against a correct statement is short. They are different problems with different escalation routes. Check bank details and any hold state before raising a discrepancy, then reference specific order IDs rather than describing a total shortfall.

Reconcile each settlement as it arrives rather than in a periodic catch-up. Dispute windows are limited, so discrepancies found during a quarterly review are frequently past the point where they can be raised. The reconciliation effort is the same either way; only the recoverability differs.

Your own order log with dispatch weights, your inward record for returns received, and the settlement statement itself. The dispatch weight record is the one sellers most often lack, and it is the one that turns a suspected logistics overcharge into a documented one.

Proportionally, yes — small sellers usually have thinner margins, so a given rupee error hurts more. The argument against reconciling is time rather than value, which is precisely the trade-off that changes once the checking is automated rather than manual.

build 784fa3bcf2c49040d2767e4be9bbfa4d11b7f32f · 2026-07-21T20:33:16+05:30