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.

Flipkart Big Billion Days: Planning Inventory and Ads Months Ahead

Every year the same pattern repeats. In late August, brands wake up to the fact that Big Billion Days is weeks away. They scramble to top up stock, throw together a discount sheet, and pile budget into ads the day the event opens. Then they spend the post-mortem complaining about stockouts, thin margins, and ad costs that doubled overnight. None of that was bad luck. It was the predictable result of planning a tentpole event as if it were a surprise. BBD is on the calendar every year. The winners treat it like the fixed deadline it is, and they start a quarter early.

We run marketplace media and operations for brands across India, and the gap between a good BBD and a bad one is almost never execution during the event. It is everything decided before it. The teams that grow lock inventory and ad budgets months ahead. The teams that struggle decide in real time, which is exactly when the platform’s economics work against them.

The decision window closes long before the sale

The instinct is to think of BBD as an event you run. It is more useful to think of it as an event you commit to. By the time the sale opens, every meaningful lever is already set. Your stock is in the warehouse or it is not. Your price is locked into the platform’s deal structure or it is not. Your ad budget and bid ladder are configured or you are improvising against competitors who configured theirs in June.

This is why last-minute prep feels so expensive. You are making decisions in the one window where you have the least leverage and the platform has the most. Inbound logistics are congested, the ad auction is at its cost floor, and discount commitments are non-negotiable. Move those same decisions back a quarter and the leverage flips. You ship inventory before the rush, you model your discount against margin calmly, and you set bids before every competitor floods the auction.

BBD is not a week you survive. It is a quarter you plan, compressed into a few days of execution.

Inventory is the bet you cannot unmake mid-event

Of everything, inventory is the least forgiving. You cannot conjure stock during the sale. If you sell out on day two of a five-day event, you have handed the back half of your demand to a competitor and trained the algorithm that your listing goes dark when traffic peaks. If you overstock, you carry the cost of dead inventory into a slow Q4 and end up fire-selling to clear it.

The hard part is that BBD demand is spiky and non-linear. Your steady-state sell-through tells you almost nothing about a sale-week peak that can run many times your normal volume on the hero SKUs and barely move the long tail. This is where most forecasts break. We treat sale-event forecasting as its own discipline, separate from baseline planning, because the math is different. Our approach to forecasting demand when it is spiky rather than smooth is built precisely for these windows, where a single week distorts the whole quarter.

The planning order we use is simple to state and hard to do well:

Rank SKUs by event-week potential, not annual volume. The products that win BBD are not always your everyday bestsellers. Deal-friendly price points and gifting demand reshuffle the ranking.
Set a depth target per hero SKU with a deliberate buffer. Stocking out at the peak costs more than the carry on a modest overstock. Bias toward not going dark.
Book inbound logistics early. Warehousing and fulfilment slots get scarce as the event nears. Late inventory that misses the cutoff is the same as no inventory.
Reserve a replenishment plan you can actually trigger. A mid-event top-up only helps if the lead time fits inside the sale window, which usually means it must already be in transit.

Discount is a margin decision, made in advance

The platform wants your deepest possible discount, because depth drives the visibility it sells. Your job is to protect margin while still earning placement. That tension cannot be resolved in the panic of event week. You need to know your floor before you commit, and you need to know which SKUs you are willing to run thin as traffic drivers versus which ones carry the margin.

That is a pricing architecture, not a spreadsheet you fill in the night before. We lay out how to defend the bottom line when discounting is mandatory in our piece on protecting margin when everyone around you discounts. The short version is that a discount you modelled in advance is a strategy, and a discount you agreed to under deadline pressure is a leak.

Ad budgets get set in the calm, not the storm

The BBD auction does not behave like a normal week. Every competitor floods in at the same moment, the cost floor jumps, and bids that were comfortable in August get overrun on day one. If you carry your steady-state bidding into the event, you either underbid and vanish from the placements that matter in the only week that matters, or you leave normal caps in place and watch your entire budget evaporate in forty-eight hours.

Neither outcome is a platform problem. It is a planning problem. The bid decision is made weeks before the sale opens, with a separate event bid ladder, separate efficiency targets, and caps that assume the floor jumps. Flipkart’s auction also weighs your listing’s own conversion signal heavily, which means a strong listing earns placement more cheaply than a competitor brute-forcing it with budget. That dynamic is the core of our Flipkart PLA bidding logic, and it matters more during BBD, not less, because the cost of every inefficient impression multiplies when the floor is high.

Set your event ad plan in the calm of the prior quarter. Decide your daily caps, your hero-SKU bid priority, and the point at which you stop chasing unprofitable impressions. Then during the event you are governing a plan, not inventing one while spend runs hot.

The whole thing is one rehearsed motion

The reason early planning works is that BBD is not really three separate problems. Inventory, pricing, and ads are one system. Your discount depth determines your sell-through, which determines the inventory depth you need, which determines how hard you can afford to bid before margin disappears. Decide any one of these in isolation, at the last minute, and the other two go wrong. Decide them together, a quarter ahead, and they reinforce each other.

This is also why BBD prep rhymes with the rest of the festive calendar. The same operators who plan Flipkart’s tentpole well tend to run a clean Great Indian Festival prep plan too, because the muscle is identical. Forecast the spike, model the margin, set the auction plan, ship the stock early. The platform changes. The discipline does not.

What changed recently

The 2025 festive run reset what a hero quarter looks like, and it reset it in ways you have to plan for, not react to. The GST 2.0 reform landed right before the season, cutting rates on several appliance and mid-priced categories from 28 percent to 18 percent and making many products noticeably cheaper at checkout. That is not a footnote. According to Business Standard, total festive e-commerce sales were projected to grow about 27 percent year on year past ₹1.2 trillion, with the first week alone generating roughly ₹60,700 crore in GMV. When a tax cut pulls demand forward and concentrates it, the brands that pre-modelled their depth against the new price points captured it. The ones still treating discount as a deadline decision left margin on the table or went dark on the hero SKUs.

The demand also moved deeper into the country and faster down the delivery clock. Independent forecaster Redseer called it the strongest festive period in five years, with GMV set to cross ₹1.15 trillion and tier-II and tier-III cities leading the growth. On the speed side, Flipkart Minutes pushed quick commerce into the festive event itself, with premium electronics, not just groceries, emerging as a quick-commerce driver during the sale, as Business Standard reported. The planning consequence is concrete. If your category is now winnable in minutes, your inventory has to sit in the right dark stores and city pools before the sale, not just in a central warehouse. If you sell where tier-II demand is quadrupling, your depth targets and your ad geo-priorities should reflect that, not last year’s metro-weighted mix. None of this changes the discipline. It just raises the cost of skipping it.

What an operator actually does about it

The brands that grow on BBD are not the ones bidding hardest or discounting deepest during the event. They are the ones who made the hard calls in June and spent September simply executing a plan they already trusted. That is the heart of how we run Performance Marketing & Ads for Indian marketplaces. We build the event ad ladders, the per-SKU inventory targets, and the margin-aware discount architecture months before the sale, so that when the auction spikes and the traffic floods, our brands are governing a rehearsed motion instead of feeding the platform’s fees in a panic. Last-minute prep is not cheaper or faster. It is just more expensive, paid out in stockouts, eroded margin, and ad spend that buys less than it should.

The Monthly Account Health Audit Every Serious Seller Should Run

Almost every suspension we have helped a brand recover from was visible weeks before it happened. The signals were there. A creeping defect rate. A policy notification that got skimmed and filed. A listing edit that quietly broke a compliance rule. Nobody was watching on a schedule, so the drift accumulated until Amazon or Flipkart did the watching for them. The brands that stay live are not luckier. They run a fixed audit on a cadence, and cadence beats heroics every single time.

This is the core argument. Account health is not an event you respond to. It is a trend you manage. The seller who opens the dashboard only when something breaks is permanently reacting to problems that were preventable a month earlier. The seller who blocks two hours on the first of every month and walks the same checklist catches the slide while it is still a number on a screen and not a notice in their inbox.

Why monthly, and why fixed

People ask why monthly and not weekly or quarterly. Weekly is the right rhythm for the live operational metrics, the ones that move daily and can spike fast. Quarterly is too slow for anything that matters, because a policy problem left for ninety days is a recovery project, not a fix. Monthly is the cadence for the deeper audit, the structural review that you cannot do every week without it becoming noise you ignore.

The word that matters is fixed. Not when you remember. Not when you feel nervous. The same date, every month, treated like payroll. The discipline is the point. An audit you run only when you are already worried is just panic with a checklist. An audit you run when everything looks fine is the one that catches the thing you did not know was wrong. We have seen calm months hide the worst surprises, because a relaxed seller is a seller who stopped looking.

An audit you run only when you are worried is not an audit. It is a reaction. The whole value is in running it when nothing feels wrong.

What the monthly audit actually covers

A real audit is not refreshing the health page and nodding. It is a walk through every surface where drift hides. Here is the spine of what we review for the brands we manage:

The core health metrics, read as a trend. Order defect rate, late dispatch rate, pre-fulfilment cancel rate, valid tracking rate. Not today’s number, the direction over the last thirty days. A metric inside the threshold but climbing is a future problem you can still solve.
Every policy notification, opened and resolved. Not skimmed. Each IP complaint, authenticity flag, restricted-product warning, or listing-policy hit, with a documented action and a status. An unaddressed notification is the single most common root of a no-warning suspension.
Listing integrity. Did anyone edit a title, image, or bullet in a way that breaks a category rule? Did a variation get hijacked? Did a tax code drift out of sync after a rate change? Catalog drift is silent and it compounds.
Invoice and sourcing readiness. Can you produce a clean invoice from an authorised distributor for every active SKU today? If not, you have a recovery file with holes in it.
Inventory accuracy versus listed stock. Oversell is the operational root that propagates into cancellations, late dispatch, defects, and eventually policy strikes. Audit it monthly before it cascades.
Account-level settings and access. Who has admin access, are deposit details current, are tax and compliance documents about to expire. Boring, and exactly the kind of thing that locks an account at the worst moment.

The point of walking the same list every month is that you stop relying on memory and start relying on a system. We go deeper on which of the live numbers actually carry suspension risk in our piece on the five metrics that actually get you suspended, and the monthly audit is simply the structured habit that keeps those five honest.

How to read drift before it reads you

Drift is the word we keep coming back to because it describes the failure mode precisely. Nothing breaks at once. A defect rate slides from comfortable to borderline over six weeks. A packer leaves and dispatch times creep. One restricted SKU gets listed without approval and sits unnoticed. None of these is a crisis on the day it starts. All of them become a crisis if nobody is auditing on a schedule.

Reading drift means looking at direction, not just position. A number that is fine but moving the wrong way is the most valuable thing the audit surfaces, because it is the only problem you can still fix cheaply. By the time a metric breaches a threshold, your options have collapsed to appeal and apology. We have watched the same spike be either a Monday morning fix or a deactivation notice, and the only variable was whether someone looked in time. If you do end up writing an appeal, the audit trail you have been keeping becomes the backbone of a credible plan of action, because you can show exactly what changed and when.

Turning the audit into something leadership can see

An audit that lives in one operator’s head is fragile. The brand that survives an account manager leaving is the one where the audit produces an artefact, a short written record of what was checked, what moved, and what action was taken. This is not bureaucracy. It is continuity. It is also the thing that lets a founder sleep, because they can see the account is being watched without having to learn the dashboard themselves.

We package the monthly audit output into the same view leadership already reads, which is why we put so much weight on a reporting dashboard leadership will actually read. The audit feeds the dashboard, the dashboard makes the audit visible, and the loop means nobody is surprised. A founder who sees a flat green trend line every month is a founder who is not getting a 2am suspension email.

What changed recently

Two shifts in the last year have made the monthly audit less optional, not more. The first is regulatory. The GST 2.0 reform that took effect on 22 September 2025 collapsed the old four-slab system into a simpler structure and re-bucketed more than two hundred product lines, which means a large share of catalogues now sit on a different rate than they did before. Amazon and Flipkart both moved fast to surface the new rates and festive savings to shoppers, as Business Standard reported, but the responsibility for applying the correct product tax code to every active listing still sits with the seller. A wrong tax code is exactly the kind of quiet listing drift the audit exists to catch, and it now carries a reconciliation tail as well as a margin one. Add a tax-code sanity check to your listing-integrity pass.

The second is scale. The volume flowing through these accounts keeps climbing, which means the cost of an unmanaged account climbing with it. Marketplace and D2C order volumes were already up around a fifth during the 2025 mid-year sales, with Tier II and Tier III towns doing much of the lifting, per YourStory, and quick commerce has become the structural growth story of the year in Inc42‘s read of the first half. More orders across more pincodes means more surfaces where a defect, an oversell, or a policy hit can originate. A bigger account is not a safer account. It is one with more places for drift to start, which is precisely the argument for auditing on a fixed cadence rather than hoping nothing slips during the next big sale.

Who should actually run it

Here is the uncomfortable part for a lot of brands. The monthly audit is real work, and it is the unglamorous kind. It does not grow revenue this week. It prevents a catastrophe that may never visibly arrive, which makes it exactly the task that gets dropped first when the team is busy. That is why it tends to get skipped right up until the month it would have saved the account.

This is the case for treating account health as a managed discipline rather than a someday task. Whether you run it in-house or hand it to a partner, someone has to own the cadence and refuse to skip it. That ownership is the spine of Marketplace Account Management as we practise it, and it is a large part of why a good operator pays for themselves long before the first suspension they prevent. We make that math explicit in our piece on how a marketplace account manager earns their fee. Pair the monthly audit with steady Marketplace Growth work and you have a brand that scales without quietly building up the risk that takes everyone else offline during the big sale events.

None of this is exotic. It is a fixed date, a written checklist, and the discipline to run it when everything looks fine. Suspensions feel sudden to the sellers who were not looking. To the ones who audit on a cadence, they almost never come at all.