Settlement Reconciliation: Are Marketplaces Actually Paying You Right?

Most brands treat the marketplace settlement report the way they treat a salary slip. The money lands, the number looks roughly right, and nobody reads the line items. This is exactly the assumption the platforms are built on. A settlement is not a payment. It is a calculation, run by software you do not control, against a fee schedule that changes without notice, applied to thousands of transactions you never audit. Some of those calculations are wrong. Some sales never get paid out at all. And because the errors are small per order and buried in a spreadsheet with forty columns, they leak margin quietly for months before anyone notices. The question is not whether your marketplaces make settlement errors. They do. The question is whether you are catching them or eating them.

A settlement is a claim, not a fact

When Amazon or Flipkart pays you, what arrives in your account is the net of a long subtraction. Gross sale value, minus commission, minus fulfilment fees, minus closing fees, minus shipping, minus payment gateway charges, minus returns, minus reserves held against future returns, minus tax deductions. Each of those is a separate computation with its own rate, its own rounding, and its own room for error. You are handed the final number and asked to trust the working.

The trouble is that the working is opaque and the rates are not static. Commission percentages vary by category and sometimes by price band. Fee structures get revised. Promotional fee waivers are supposed to apply and sometimes silently do not. Weight-based shipping charges depend on a dimensional weight the platform measured, not the one you declared. Every one of these is a place where the number you were paid can drift from the number you were owed. Treating the settlement as a fact rather than a claim you should verify is the original mistake.

Where the money actually leaks

After enough reconciliations you start to see the same failure modes repeat across platforms. The leaks are rarely dramatic. They are small, systematic, and they compound across volume.

• Commission charged at the wrong rate. Your SKU is categorised one way for the listing and another way for the fee engine, so you are billed a higher commission slab than your contract specifies. On a few hundred orders a month this is real money.
• Fees on cancelled or returned orders that were never reversed. The order came back, the customer was refunded, but the commission or shipping fee on the original sale was never credited back to you.
• Settlements that simply never arrive. A batch of orders marked delivered, eligible for payout, and then absent from every settlement cycle that follows. Not delayed. Missing.
• Shipping charged on the wrong weight. The platform’s measured dimensional weight bumps you into a higher slab than your actual product, and you pay the difference on every unit until someone disputes it.
• Reserves held longer than policy. Money parked against potential returns that should have released weeks ago and quietly did not.
• Promotion and ad-fee double counting. A deal-day fee deducted at settlement that was supposed to be covered by the campaign you already funded.

None of these will bankrupt you in a month. That is precisely why they survive. A single order shorted by twelve rupees is beneath notice. The same error on every order in a category, every month, for a year, is a number that would change how you feel about that category.

Marketplace fee errors are not loud enough to notice and not large enough to chase, which is exactly why they are worth chasing.

Why nobody catches it

Reconciliation is unglamorous, manual, and easy to defer. The settlement file is enormous, the order export lives in a different report with different identifiers, and matching one to the other by hand is the kind of task that gets pushed to next week forever. So most brands never do it. They look at the headline payout, compare it loosely to last month, and move on.

This is understandable and expensive. The platforms are not run by villains running a scam. They are running imperfect software at enormous scale, and imperfect software at scale produces a steady drip of errors that always, by the structure of the situation, favour the party doing the calculating. There is no malice required. There is only the fact that an unaudited counterparty computing your revenue will, on average, compute it in its own favour more often than yours. The only correction is to check.

What real reconciliation looks like

Doing this properly means rebuilding the settlement from your own data and comparing it to theirs, line by line. You take your order export, you apply the fee rates your contract actually specifies, you compute what each order should have netted, and you match that against what the settlement report says it did net. The gaps are your evidence.

The matching key matters. Reconcile at the order or transaction level, not the summary level, because a summary that nets out to roughly the right total can hide an overcharge in one place cancelling an undercharge in another. You want to know that every single delivered order produced a settlement line, that every fee on that line is at the contracted rate, and that every return reversed the fees it should have. Orders that appear in your sales data but never appear in any settlement are the highest-value find, because a missing payout is one hundred percent leakage, not a few percent.

This is fundamentally a data exercise, which is why it belongs in the same system as the rest of your marketplace numbers. If you are already running a real reporting dashboard leadership actually reads, settlement variance is one more panel on it, computed automatically instead of chased manually every quarter.

It is connected to numbers you already care about

Reconciliation is not a side quest. It feeds directly into the decisions you make with the rest of your data. The fees you actually paid, as opposed to the fees you assumed, are an input to profitability per SKU. If your true commission is higher than the slab you modelled, the SKU you believe is your margin hero may be quietly underwater, and you would never know because you costed it on the wrong fee.

It connects to liquidity too. A settlement that arrives late, or a reserve held past policy, is cash trapped exactly where you cannot afford it. We have argued at length that working capital is the real constraint on marketplace growth, and unreconciled settlements make that constraint worse in two directions at once. You are short the money that was miscalculated, and you are blind to the timing of the money that was merely delayed.

And it overlaps with tax. The deductions on your settlement include TCS and TDS, and those have to reconcile not just against your expectation but against what gets reported to the authorities in your name. The mechanics are their own discipline, which we cover in the TCS, TDS and reconciliation nightmare, but the principle is the same. If you are not checking what was deducted, you are trusting a number that has compliance consequences attached to it.

What changed recently

The last year handed marketplace operators two reasons to rebuild their reconciliation baseline rather than coast on last year’s assumptions, and both are the kind of thing that quietly breaks a model nobody updated.

The first is fees. From March 16, Amazon India overhauled its seller fee schedule, expanding zero referral fees to over 12.5 crore products priced under 1,000 rupees across more than 1,800 categories, cutting referral fees on several high-volume categories above that band, and reducing Easy Ship and closing fees for low-price items, with the closing fee on sub-300-rupee products dropping from 45 rupees to 20 according to Amazon India. This is good news for margin, but it is a reconciliation trap. A fee cut only reaches your bank account if the fee engine actually applies the new rate to your category, and the single most common settlement error we find is a SKU that keeps getting billed at the old slab after a schedule change. The brands that benefit are the ones reconciling every payout against the current fee table, not the table they memorised eighteen months ago. A lower headline fee you are still being charged the old rate on is not a saving, it is a dispute waiting to be filed.

The second is tax. The GST 2.0 reform that took effect on 22 September 2025 collapsed the old four-slab structure into mainly 5 and 18 percent bands, which forced a wave of repricing and changed the tax math sitting inside every settlement line, as Unicommerce details. When the GST on a product moves, the gross-to-net working on your settlement moves with it, and any reconciliation rebuilt on pre-reform rates will throw false variances or, worse, hide real ones. The deadline pressure is real too. From December 2025, GST returns more than three years past their due date can no longer be filed, per Cashfree, which means a settlement mismatch you ignore today can become a permanently unrecoverable tax position. Reconciliation used to be about clawing back fees. It is now also about not letting a tax window close on money the platform already deducted in your name.

Make it a process, not a panic

The brands that recover this money do not do a heroic one-time audit and then stop. They turn reconciliation into a monthly cadence that runs against every payout, flags variances above a threshold, and produces a clean list of disputes to file with the platform. The recovery is real. Filing a well-evidenced fee dispute, with order IDs and the contracted rate attached, is usually paid out, because the platform’s own data confirms the error once you point at it. What you cannot do is dispute what you never measured.

This is the kind of work our Analytics & Reporting practice is built for, because it is pure data plumbing with a direct rupee return. Pulling settlement and order exports across platforms, normalising them to a common ledger, computing expected versus actual at the transaction level, and surfacing the gaps. From there our Marketplace Account Management team turns the variances into filed disputes and chases the recoveries, and our D2C & Marketplace Strategy Consulting folds the true fee picture back into pricing and catalogue decisions so you are not just clawing back the past but costing the future correctly.

The short version

Your marketplace settlements are calculated by the counterparty, against a fee schedule that moves, on data you do not audit. Under those conditions the errors will not be random. They will, on balance, favour the platform, not because anyone intends it but because that is what unchecked computation does. The leak is small per order and invisible per month, which is exactly why it runs for years.

Reconcile every payout against your own expected numbers, at the transaction level, on a fixed cadence. Treat a missing settlement as a fire and a mis-rated fee as recoverable cash, because both are. Assume you are being shorted until your own ledger proves otherwise. On a marketplace, that assumption is not cynicism. It is just arithmetic.