Skip to content
Robnu

Flipkart settlement reports, decoded line by line.

Every payout is the order value minus a stack of deductions. Learn what each line means, which fees are wrong often enough to check, and how to reconcile a Flipkart settlement to the rupee — before the money is spent.

Free during early access · Forever free under 25 orders/day
app.robnu.com/payment-reconciliation/settlementThe settlement cycleMoney is earned on delivery, but paid on the platform's clockOrder placedday 0Deliveredbuyer receivesSettlement clockcycle runsPayoutcredited to bankNet payout = order value − commission − fees − TCS − TDSMeesho: 7-day cycle from deliverysettledReconcile every payout line against the settlement statement — that is where wrongdeductions hide. Robnu matches payout to order to adjustment, automatically.
TL;DR
  • A settlement report shows, per order, the sale value minus every deduction, ending in the net credited to your bank.
  • The deduction stack: category commission, shipping/collection fee, fixed fee, payment collection fee, plus GST adjustments.
  • The shipping fee is the line most often wrong, because it depends on parcel weight and delivery distance.
  • Reversals are corrections — refunds to you or clawbacks after returns; they need checking, not ignoring.
  • Robnu reconciles AJIO, Meesho, and Amazon to the rupee today; Flipkart is coming soon, waitlist only.

The settlement report is the least glamorous document in your seller panel and the most important. It is the only place that tells you what you were actually paid, and it is where recoverable money hides in plain sight. Most sellers glance at the net figure and move on. Reading it properly is a habit that pays for itself.

A Flipkart settlement is not one number; it is a chain of them. The order sold for one amount, a series of deductions came off it, and what landed in your bank is the remainder. If you only ever look at the remainder, you are trusting that every deduction in the chain was correct — and across thousands of orders, some of them are not. This guide takes the report apart so you can read it with a sceptical eye.

What a settlement report actually is

Each settlement cycle, Flipkart issues a report that lists every order eligible for payout and, against each one, the full breakdown: the sale value, each deduction, any GST adjustment, any reversal, and the net credited. You can download it from the payments section of the Flipkart seller panel. Think of it as a bank statement for your marketplace: the running record of money in, money out, and corrections. If you sell across platforms, you will keep one of these per marketplace — see our Meesho operations overview and Amazon order management guide for how the others compare.

The deduction stack, line by line

Four deductions do most of the work. The commission is a percentage of the selling price set by your product category — the single biggest line, and the reason category choice matters so much. The shipping or collection fee covers the logistics of getting the parcel to the customer, calculated from the parcel’s weight and the delivery distance. The fixed fee is a flat per-order charge. The collection fee relates to how the payment was taken from the customer.

On top of these sit GST adjustments, and for orders that returned or cancelled, one or more reversals. The net you receive is the sale value minus the deduction stack, adjusted for GST and any reversals. When a payout looks surprisingly small, it is almost always one of three causes: a high-commission category, a heavy shipping slab on a low-value item, or a fee that was charged in error. The first two are pricing problems you fix by modelling fees before you list; the third is a recovery problem you fix by reconciling.

The shipping fee is where errors hide
Commission and fixed fee are predictable — you can compute them from the category and the sale value. The shipping fee is not, because it depends on the recorded weight and lane. A parcel logged at a higher weight than it actually is inflates the charge on every order at that weight, quietly, for as long as it goes unnoticed. This is the single most common recoverable error across Indian marketplaces.

Reversals: refunds, clawbacks, and the trap between them

A reversal is a correction, and there are two kinds that mean opposite things. A fee reversal credits a charge back to you — good news, a fee that should not have applied. A payment clawback pulls back the sale value after a return or cancellation — expected, because the sale did not complete. The trap is when a return triggers a clawback of the sale but also leaves a reverse-logistics charge standing that should have been waived, or vice versa. Reading reversals carefully is how you separate the corrections you owe from the ones you can claim. Our Flipkart return charges guide goes deeper on the return side specifically.

How to reconcile a settlement to the rupee

Reconciliation is a simple loop done consistently. For each order on the report, take the sale value, subtract the commission you expect for that category, subtract the fixed fee, and check the shipping fee against the parcel’s actual weight and lane. If the net matches what you computed, the order is clean. If it does not, you have found either a pricing surprise to learn from or an error to claim. Keep a running list of the mismatches; the ones inside their claim window go into a ticket. The RTO cost calculator helps you model the freight side, and the payment reconciliation approach scales the same logic across every order.

The catch is volume. At a handful of orders a day this is a fifteen-minute weekly habit. Past a dozen orders a day it becomes impossible to check every weight by hand, and that is precisely when errors start slipping through — not because they got more common, but because nobody is watching. That is the problem an OMS is built to solve, and the reason reconciliation is a core Robnu pillar for the marketplaces it already runs.

Sources & further reading

Fee structures and report formats change over time. Always confirm the current deduction definitions against the official Flipkart documentation, and check GST treatment against the government portal:

app.robnu.com/protect/deductionsDeduction categoriesWhere money typically leaks · illustrativeSLA missDisputableQuality disputeDisputableMis-pickSunkLate ackDisputableRTO leakSunkSlip mismatchDisputableDISPUTE-READYRobnu surfaces them
The stack

Four deductions decide your payout

Learn to read them in order and no settlement will ever surprise you again.

  • Commission. A category-set percentage of the sale — the biggest line, and the reason category choice matters.
  • Shipping fee. Based on weight and distance — the line most worth checking against your actual parcel weight.
  • Fixed fee. A flat per-order charge, predictable and easy to verify.
  • Collection fee. Tied to how the payment was taken, with GST layered on top of the whole stack.

For the full recovery workflow, see payment reconciliation.

The loop

The reconciliation loop, per order

Done consistently, this is how you catch every error before the money is gone.

Step 1

Compute the expected

Take the sale value, subtract the commission you expect for the category, subtract the fixed fee. That is your baseline before shipping.

Step 2

Check the shipping

Match the shipping fee against the parcel’s actual weight and lane. A weight logged higher than reality is the most common inflated charge.

Step 3

Read the reversals

Separate fee refunds from payment clawbacks. Make sure a return credited the sale back and did not leave a charge standing that should have been waived.

Step 4

Flag and claim

Any order where the net does not match goes on a list. The ones inside their claim window become a ticket with the order ID, weight, and a screenshot.

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
The Robnu way

Reconciliation without the spreadsheet

The manual loop above works — until volume beats it. Robnu is an agentic OMS: for the marketplaces it runs today (AJIO, Meesho, Amazon) it reads every settlement automatically, matches each fee against the weight and lane it should have been, and flags what does not line up — wrong weights, duplicates, and returns billed on parcels that never came back. It then prepares the claim and files it, with a rare approval click while fully-autonomous filing rolls out.

Flipkart reconciliation is coming soon — waitlist only. When it lands, the same engine reads your Flipkart report the way this guide teaches you to, at a scale no spreadsheet can match. Until then, reconcile by hand, and join the waitlist so you are first in.

Free while we figure out pricing — no card, no caps, forever free under 25 orders a day when paid pricing launches.

app.robnu.com/payment-reconciliation/settlementThe settlement cycleMoney is earned on delivery, but paid on the platform's clockOrder placedday 0Deliveredbuyer receivesSettlement clockcycle runsPayoutcredited to bankNet payout = order value − commission − fees − TCS − TDSMeesho: 7-day cycle from deliverysettledReconcile every payout line against the settlement statement — that is where wrongdeductions hide. Robnu matches payout to order to adjustment, automatically.
FAQ

Flipkart settlements, answered

It is the statement Flipkart issues each settlement cycle showing, for every order, the sale value and each deduction applied, ending in the net amount credited to your bank. It is your single source of truth for what you were actually paid versus what the order was worth.

Because Flipkart earns through per-order deductions: a category commission, a shipping or collection fee, a fixed fee, and a payment collection fee, with GST adjustments layered on top. Your net is the order value minus all of these. A payout that looks surprisingly low usually means either a high-commission category, a heavy shipping slab, or a fee charged in error.

The shipping fee is the usual suspect, because it depends on parcel weight and delivery distance — a weight recorded higher than reality inflates the charge. Duplicate fees and return charges billed on parcels that never came back are the other common errors. The commission and fixed fee are more predictable.

Raise a ticket through the seller panel with evidence: the order ID, the actual parcel weight, and a screenshot of the settlement line. The clearer your evidence and the faster you raise it, the better your odds. Errors caught within the claim window are far more likely to be reversed than ones spotted months later.

A reversal is a correction — either a fee refunded back to you, or a payment clawed back after a return or cancellation. Reversals are normal, but they need checking, because a return reversal should credit back the sale while any legitimately-owed reverse-logistics charge stands. Confusing the two is a common way sellers lose track of what they are owed.

Flipkart pays out on a settlement cycle after delivery, with the exact timing depending on your account terms and the return window behaviour of each order. The report is issued per cycle. Treat each new report as a checkpoint to reconcile before the money is spent.

Not to start — at a few orders a day you can reconcile by hand with a spreadsheet and the order weights. The problem is scale: once you are past a dozen orders a day, checking every shipping fee against every weight by hand becomes impossible, and that is exactly where errors slip through unnoticed.

Not yet — Flipkart is coming soon for Robnu, waitlist only. Robnu reconciles AJIO, Meesho, and Amazon settlements to the rupee today. This guide teaches the manual method so you can reconcile Flipkart yourself now, and you can join the waitlist for when Robnu adds Flipkart.

Keep reading

Related seller guides

More on the operations, money and claims that decide whether a marketplace catalogue actually makes money.

Marketplace settlement cycles: AJIO & Meesho payment timelines

When AJIO and Meesho actually pay you, why the payout never matches the order value, and how to reconcile every settlement line so wrong deductions don't keep your money.

Amazon India settlement reports explained

Referral fees, closing fees, shipping, refund reversals — reconcile order by order, spot the wrong-rate and duplicate errors, and find the refund reversals worth a SAFE-T claim.

Payout Reconciliation: How to Match Every Rupee a Marketplace Owes You

Marketplace payouts arrive net of a dozen deductions, and some of those deductions are wrong. Here is the discipline of matching every payout to the orders and charges behind it — so no rupee slips through.

Flipkart Return Charges for Sellers: What You Pay and the SPF Basics

Every Flipkart return has a cost stack — reverse logistics, lost margin, and the seller protection fund basics. Here is what you actually pay, which charges are wrong often enough to check, and how to claim.

Myntra Partner Payment Cycles Explained: Settlement Timing, Deductions & Reconciliation

How Myntra settlement works — the lead time from delivery to payout, every deduction that lands on a remittance, why payments get held, and how to reconcile a settlement against your orders.

Meesho seller charges & deductions: every line on your payout

Commission, shipping, SLA penalties, cancellation charges, return and RTO reversals, TCS and TDS — every charge on a Meesho payout, what each means, and which ones you can claim back.

Meesho Pay Later: The Charges and Settlement Effects Sellers Miss

Pay Later changes when and how the money reaches you, and a few costs ride along quietly. What it means for your settlement timeline, the fees sellers overlook, and how to reconcile it correctly.

Meesho payment cycle: when you actually get paid

The settlement timeline, every deduction applied before payout, and why your bank credit never matches your order value — plus how to tell a normal gap from a wrong one.

build 381ae572f18c631ad98c0bb20dbe902acf608cc6 · 2026-07-23T01:12:01+05:30