Settlement Reconciliation Explained for Beginners
If you sell on Amazon, Flipkart or Meesho, you have noticed that the money arriving in your bank account never equals your sales for the same period. Settlement reconciliation is the process of explaining that difference, order by order, until every rupee is accounted for: paid, deducted as a fee, refunded, or still on its way. It sounds like accounting housekeeping. In practice it is how sellers discover short payments, missed refunds and fee errors, and it is the difference between knowing your margins and guessing them. This guide explains the concept from zero.
What a settlement actually is
Marketplaces do not pay you per order as it ships. They accumulate your transactions, sales, commissions, shipping fees, collection charges, refunds, adjustments, and pay the net amount on a cycle, typically linked to delivery dates and your payment terms. Each payout comes with a settlement report: a file listing every transaction included in that payment. That report is the key document. Your bank statement tells you what you received; the settlement report tells you why.
The three-way match
Reconciliation is a three-way comparison:
- What you sold: the order or sales report from the marketplace.
- What they say they paid: the settlement report, with every deduction itemised.
- What actually arrived: the credit in your bank statement.
For every order, you are asking one question: did this order end up fully explained? A healthy order flows from sale to settlement to bank, with fees within expected rates. An unhealthy one is missing from settlements weeks after delivery, or settled short, or refunded without the fee reversal you were entitled to. Reconciliation finds the unhealthy ones.
A worked example
| Line | Amount |
|---|---|
| Order value (customer paid) | 1,000 |
| Marketplace commission | -150 |
| Shipping fee | -80 |
| Collection or payment fee | -20 |
| Taxes deducted at source (as reported) | -15 |
| Net settled to bank | 735 |
The figures are illustrative, real rates vary by category, marketplace and your contract, but the shape is universal: roughly a quarter of this order's value went to deductions. Reconciliation checks each line against what the marketplace's own rate card says it should be, and confirms the 735 actually landed. Multiply by a few thousand orders a month and you see both why the work matters and why nobody wants to do it by hand. For a deeper look at each deduction type, see why payouts never match sales.
How to start, practically
Begin with one month and one marketplace. Download the order report and every settlement report touching that month, then match at order level: each order ID in the sales report should appear in a settlement, with the net amount explained by itemised deductions. Sort the leftovers into three buckets: pending (recent orders not yet due for payout), returned (refunds that should net off), and exceptions, anything else. The exceptions bucket is where the money is: short payments, double-charged fees, refunds without fee reversals. Keep the marketplace's own help pages for its settlement report open beside you the first time through; column names differ across Amazon, Flipkart and Meesho, and half the early confusion is vocabulary rather than accounting. Spreadsheets can do this at small volume; the method matters more than the tool at first. As volume grows, the matching becomes mechanical and error-prone by hand, which is what reconciliation software automates. TallySutra does this order-level matching from your uploaded report files and turns the results into balanced TallyPrime vouchers, with unmatched items landing in an exception queue instead of disappearing.
What good looks like
A seller with working reconciliation can say, at any time: this month's orders are 96 percent matched, these specific orders are pending, and these five need action. The books built on top of this are equally clean, sales at gross value, every fee visible on its own ledger, and the bank tying to settlements. That standard is achievable for any seller, and if a CA manages your books, it is reasonable to ask for it; the CA workflow version of this process shows what your accountant sees. When the buckets are defined and the exceptions have owners, reconciliation stops being a project and becomes a habit. Expect the first month to be the hardest: history is messy and opening positions take judgement. From the second month the buckets mostly roll forward, and the work shrinks to matching the new cycle and chasing the exceptions that age.
Frequently asked questions
How often should I reconcile marketplace settlements?
Match settlements as they arrive, weekly for most sellers, and do a full month-end pass. Waiting a quarter multiplies pending items and lets short payments age past the point where marketplaces respond easily to claims.
Is reconciling monthly totals enough instead of order level?
Totals catch large breaks but hide offsetting errors, a short payment on one order offset by a pending payment on another looks fine in total. Order-level matching is what surfaces recoverable money.
Do I need software to reconcile settlements?
Not at low volume; a careful spreadsheet works for a few hundred orders a month. Past that, manual matching becomes slow and error-prone, and automation that matches at order level and flags exceptions earns its keep quickly.
TallySutra turns Amazon, Flipkart and Meesho reports into reconciled, reviewed TallyPrime vouchers — duplicate-safe, with every rupee traceable to its source row.
Book a 30-minute demo