The 30-minute monthly audit that finds every wrong shipping charge.
Freight, reverse charges, weight re-bills and penalties leave your payout in dozens of small lines, and nobody at the marketplace double-checks them for you. This guide is the monthly routine that does: pull the lines, bucket them, compare each against the slab it should have been, flag the deltas, dispute the flags, and log what comes back.
- Once a month, pull every settlement and deduction report, isolate the shipping-related lines, and bucket them: forward freight, reverse/RTO, weight discrepancy, penalty. Thirty minutes is realistic once the sheet exists.
- Compare each line against the expected charge from your per-SKU mapping sheet (packed weight, dimensions, expected slab). Four deltas matter: wrong slab, reverse charge with no return event, duplicate lines, and penalties on orders that shipped on time.
- File disputes for the flags the same week — windows are short, check the current policy on your panel — and log every outcome. The log is what turns one-off recoveries into corrected SKUs and a falling error rate.
Shipping charges are computed by machines. Machines drift.
Every shipping line on your settlement is the output of an automated pipeline: a hub scanner weighs the parcel, a rate engine picks the slab, a returns system decides whether a reverse charge applies, a penalty engine checks dispatch timestamps. Each step is mostly right — and at hundreds of orders a month, “mostly” leaves a residue of wrong lines that nobody upstream is paid to catch. Sellers who never audit are effectively agreeing to every one of those errors, forever.
The audit is not paranoia and it is not a fight with the marketplace. Most lines will check out, and that is a result too: a confirmed cost base you can price against. What you are hunting is the delta — the billed number that the paperwork cannot reproduce. If you do not yet know what each charge type means, keep our deductions glossary open in the next tab while you work through your first month.
Illustrative arithmetic: at 600 orders a month, a 2% error rate with an average ₹45 wrong charge is roughly ₹540 leaking monthly — call it ₹6,000–₹7,000 a year — before counting the occasional phantom RTO charge that runs far larger. Thirty minutes a month is a good trade for that.
The 30-minute audit, step by step
Block the first working morning after your settlement cycle closes. The first run takes longer because you are building the sheet; from month two, this is genuinely a half-hour job.
- 01
Pull the settlement and deduction reports
Download the full settlement or payment report for the cycle from each panel — AJIO and Meesho export these per cycle — plus any separate weight-reconciliation or penalty report. Work from exports, not the on-screen summary: the summary hides exactly the line-level detail the audit needs.
- 02
Bucket every shipping-related line
Tag each charge line with a type: forward freight, reverse/return shipping, RTO charge, weight-discrepancy re-bill, penalty, other. Sorting by type first makes the patterns visible — a cluster of reverse charges in a week you had few returns jumps out immediately.
- 03
Maintain the expected-slab mapping sheet
One row per SKU: packed weight, box dimensions, volumetric weight (commonly length x width x height / 5000), and the expected forward slab. This sheet is the audit's engine and it barely changes month to month — update it when packaging changes, and reuse it for weight disputes too.
- 04
Compare billed against expected, line by line
For each forward-freight and discrepancy line, put the expected charge next to the billed one and compute the delta. Zero or near-zero deltas get status ok. Anything else gets flagged. For reverse, RTO and penalty lines, the comparison is against events: does a matching return, RTO or late dispatch actually exist on the order timeline?
- 05
Flag the four delta types
Wrong slab: billed weight class the SKU cannot reach. Reverse charge with no return event: a return fee on a delivered order with no return initiated. Duplicate lines: the same AWB billed twice across cycles. Penalty on a compliant order: a breach fee where your dispatch log shows on-time handover. Each flag gets its own row status and evidence note.
- 06
File or queue the disputes
Dispute each flag through the panel with the charge line quoted — order ID, AWB, billed versus expected — and the evidence attached. Windows are short, so file the same week; check the current policy on your panel for each charge type. Wrong-slab flags follow the weight-dispute playbook, linked below.
- 07
Log recoveries and close the loop
Record every outcome against its row: recovered, rejected, re-appealed. Then read the log for patterns — one SKU repeatedly re-billed is a weight-correction escalation, not a monthly ritual. The log is also your proof of history if a dispute pattern ever needs escalating past first-line support.
Eleven columns and a monthly rhythm
The whole system fits in one spreadsheet, one row per charge line: settlement cycle, order ID, AWB, SKU, charge type, billed amount, expected amount, delta, status (ok / flagged / disputed / recovered / rejected), dispute reference, notes. The expected amount comes from your SKU mapping sheet — if you sell on more than one marketplace, our SKU-mapping guide shows how to keep one master sheet feeding both panels.
The rhythm: a full pass monthly, on a fixed day right after the cycle closes, plus a five-minute weekly skim for large lines so nothing big ages toward a dispute window. Month one is slow because you are building the mapping sheet and learning the report formats. Month three is when it gets fast — and when the log starts showing which SKUs, couriers or charge types produce your deltas, which is the information that lets you fix causes instead of chasing refunds.
This audit is a job a machine should do — every day
Everything in the routine above is deterministic: match a charge line to an order, compute the expected amount, compare, flag. Robnu runs exactly that reconciliation continuously across your AJIO and Meesho settlements — every freight, reverse, RTO, discrepancy and penalty line matched to its order and checked against your SKU weight profiles the day the settlement lands, not on audit day.
Deltas arrive as flags with the paperwork pre-assembled: charge line quoted, evidence attached, dispute drafted and filed. Fully-autonomous filing is rolling out, and the rare claim still asks you for one approval click before it goes. The recovery log builds itself, and your monthly half-hour becomes what it should be — reading the pattern report and deciding which SKU gets a weight-correction push, not hunting duplicates in a spreadsheet.
Shipping-deduction audits, answered
A monthly pass over your settlement reports where you isolate every shipping-related charge — forward freight, reverse and RTO charges, weight-discrepancy re-bills, penalties — and check each against what it should have been for that SKU and that order. The goal is a short list of deltas: lines where the billed amount does not match the expected slab or where the charge has no matching event behind it. Those deltas become disputes; everything else is confirmed cost you can price into your margins with confidence.
It depends entirely on volume and error rate, so treat any figure as illustrative: a seller doing 500–600 orders a month who finds wrong slabs on even 2–3% of shipments and a few phantom reverse charges is often looking at four figures in rupees monthly. The bigger value is the trend — audited sellers report that error rates on their SKUs fall over time because repeat offenders get corrected, while unaudited accounts leak quietly at whatever rate the errors happen to occur.
Four patterns cover most finds. Wrong slab: the billed weight class exceeds what the SKU can physically be. Reverse charge with no return event: an RTO or return-shipping fee on an order your panel shows as delivered, with no return initiated. Duplicate lines: the same AWB charged twice across settlement cycles. And penalties on compliant orders: an SLA or breach fee on an order your dispatch logs show went out on time. Each has a different dispute framing, but all four start as a delta in the same audit sheet.
One row per charge line, with: settlement cycle, order ID, AWB, SKU, charge type (forward, reverse, RTO, discrepancy, penalty), billed amount, expected amount from your slab mapping, delta, status (ok, flagged, disputed, recovered, rejected), dispute reference, and a notes column. The expected-amount column is the engine — it only works if you maintain a per-SKU mapping of packed weight, dimensions and expected slab, which is the same sheet that powers your weight disputes.
Windows are short and vary by marketplace and charge type — typically days from the charge surfacing, not weeks, so check the current policy on your panel rather than assuming. This is why the audit is monthly at minimum and why many sellers add a five-minute weekly scan for big-ticket lines: a monthly-only rhythm means a charge from early in the cycle can be near or past its window by the time you find it. Flag first, polish evidence second — filing on time with a partial pack beats missing the window with a complete one.
Robnu does continuously what this guide does monthly. It ingests every AJIO and Meesho settlement, matches each charge line to its order, computes the expected charge from your SKU weight profiles, and flags the deltas — wrong slab, reverse charge without a return event, duplicates, penalties on compliant orders — the day they land instead of at month-end. Disputes are assembled with references and evidence attached and filed; fully-autonomous filing is rolling out, and the rare claim still asks for one approval click. Recoveries are logged against each line, so you always know what came back.
Where this comes from
- Marketplace settlement and payment report formats: Meesho supplier panel and AJIO seller-panel export documentation (check the current report set on your panel — formats change).
- Courier volumetric-weight conventions from published Indian courier rate cards (volumetric divisor commonly /5000).
- Recurring seller reports of duplicate freight lines, phantom reverse charges and wrongful penalties: public seller community threads (Reddit r/IndiaBusiness, seller Facebook and Telegram groups), 2024–2026.
Related guides & pages
Weight-discrepancy deductions
The biggest audit bucket, explained: how re-billed slabs happen.
Deductions glossary
Every charge type on your settlement, decoded line by line.
SKU mapping
One master sheet per SKU — the engine behind the expected column.
Payment reconciliation
How Robnu matches every settlement line to its order for you.