If you sell on Amazon, Flipkart, Meesho, Myntra, JioMart or AJIO, the deposit that lands in your bank account rarely matches the sales figure in your books. Marketplace settlement reconciliation is the process of matching what a marketplace actually pays you against what you recorded as sales, so that your GST returns, your bank ledger and your profit numbers are all built on the same, verified numbers.
Skipping this step is one of the most common reasons sellers end up filing GSTR-1 with figures that do not tie back to their bank statement, or discover months later that a marketplace has short-paid them on a batch of orders. This guide walks through what a settlement report contains, why it never matches your sales register on its own, and a practical process you can repeat every settlement cycle.
What a Settlement Report Actually Contains
A settlement report (sometimes called a payment report, disbursement report or transaction summary depending on the marketplace) is not a sales report. It is a cash movement report. Every marketplace bundles several types of line items into one payout:
- Order-level sale proceeds for a group of orders delivered in that cycle
- Marketplace commission, referral fees, closing fees and fixed fees
- Shipping and fulfilment charges (if the marketplace handles logistics)
- Refunds and return deductions for orders cancelled or returned
- TCS (Tax Collected at Source) deducted under GST
- Adjustments: storage fees, penalty deductions, previous cycle corrections, promotional cost recovery
Because all of this is netted into a single deposit, the number in your bank statement is a residual figure, not a sales figure. Reconciliation means unpacking that residual back into its components.
Why the Settlement Amount Never Equals Your Sales Register
Timing differences
An order placed and invoiced on the 28th of one month may only be paid out in the settlement cycle that closes in the following month. Your sales register is normally organised by invoice date; the settlement report is organised by payment cycle date. The two calendars rarely line up cleanly at month-end, which matters a great deal when you are closing GSTR-1 for a period.
Fees, commissions and TCS
Commission and fee structures differ by category and marketplace, and TCS at the applicable rate is deducted before payout. None of this appears in your sales register unless you post it separately as an expense and a TCS receivable.
Returns and refunds processed later
A sale recorded in one period can be reversed by a return that is settled two or three cycles later. If you do not track this, your sales register keeps showing revenue for an order that was actually returned.
A Step-by-Step Reconciliation Process
- Pull three reports for the same date range: your sales/order register, the marketplace's settlement report, and your bank statement showing the actual credit.
- Group settlement lines by order ID so each line item (sale, fee, refund, TCS) can be traced back to a specific invoice.
- Match total gross sales in the settlement report against the corresponding invoices in your sales register, flagging orders that appear in one but not the other.
- Post fees, commissions and TCS as separate ledger entries rather than netting them against sales, so your revenue figure stays accurate for GSTR-1.
- Reconcile the net settlement figure to the bank credit to confirm the amount actually received matches the marketplace's own report.
- Investigate and log every unmatched line - short payments, unexplained deductions, or orders missing from either side - before closing the period.
Doing this manually across hundreds or thousands of order lines in a spreadsheet is workable at low volumes, but it becomes error-prone once you cross a few hundred orders a month. OneBooks GST's GSTR-1 automation is built to import marketplace sales and settlement data together so that fees, TCS and refunds are separated automatically instead of being buried in a single netted number.
Mapping Settlement Report Fields to Your Books
| Settlement report field | Where it belongs in your books |
|---|---|
| Gross order value | Sales register / GSTR-1 outward supply |
| Marketplace commission and fees | Expense ledger (commission and selling expenses) |
| TCS deducted | TCS receivable ledger, claimed as credit while filing returns |
| Return/refund deduction | Credit note against the original invoice |
| Shipping/fulfilment charge | Logistics expense ledger |
| Net payout | Bank ledger, matched to the actual credit entry |
Common Mismatches and How to Fix Them
A few patterns show up repeatedly once sellers start reconciling settlements properly:
- Orders missing from the settlement report: usually still in transit or pending delivery confirmation - hold them for the next cycle rather than writing them off.
- Settlement amount lower than expected with no listed deduction: raise it directly with marketplace seller support; keep a log of these so you can track how often it happens.
- TCS in the settlement report not matching the TCS credit shown on the GST portal: this is common enough that it deserves its own check every quarter - compare the marketplace's TCS statement against your GSTR-2A/2B data rather than assuming they match automatically.
- Duplicate refund deductions for a single returned order appearing across two settlement cycles - trace both back to the original order ID before adjusting your books twice.
Keep a running log of every mismatch you investigate, even the small ones. Over a few cycles, this log tends to reveal patterns - a particular fee category that is consistently mislabelled, or a specific return reason code that always settles a cycle later than expected - that are far easier to build a permanent fix for than to keep re-investigating from scratch every month.
How Often Should You Reconcile
Settlement cycles are typically weekly or bi-weekly depending on the marketplace, but you do not need to reconcile at that frequency. Most sellers get good results reconciling monthly, aligned to the GST filing cycle, with a lighter spot-check whenever a settlement amount looks unusually low. If you sell across several marketplaces, doing this consistently for each one before you prepare GSTR-1 avoids a scramble at filing time - see our guide on managing GST across multiple marketplaces for how to structure that workflow. For platform-specific detail, the Amazon GST reconciliation guide and our note on TCS on e-commerce under GST cover the mechanics that apply within a single settlement report.
Frequently asked questions
What is the difference between a sales report and a settlement report?
A sales report lists what you sold and invoiced. A settlement report lists what the marketplace actually paid you after deducting commission, fees, TCS and refunds. The two will rarely show the same total for a given period, which is exactly why reconciliation is needed.
How do I handle TCS shown in a settlement report?
Post it to a TCS receivable ledger rather than treating it as an expense. It is available as a credit against your GST liability when you file returns, so it needs to be tracked separately, not netted off against sales.
Why does my bank credit not match the settlement report total?
Banking charges, currency conversion (for international marketplaces) or a payout split across two bank entries can cause small differences. Always match the marketplace's own settlement report to the bank credit first, before trying to match settlement to sales.
Should I reconcile every settlement cycle or wait till month-end?
Reconciling monthly, ahead of your GSTR-1 filing, works well for most sellers. High-volume sellers or those managing multiple marketplaces often benefit from a lighter weekly check so mismatches do not pile up.
Can reconciliation be automated?
Yes. Tools that import both marketplace sales data and settlement reports together can automatically separate fees, TCS and refunds from gross sales, which removes most of the manual line-by-line matching. Always verify a sample of transactions after any automated import.
Where OneBooks GST helps
This is where tooling earns its place: OneBooks GST imports marketplace sales, returns and settlement reports so marketplace totals can be compared against book totals before anything is filed.
Reviewing the output in OneBooks GST before it leaves the system is the step that catches period, GSTIN and tax-rate errors while they are still easy to fix.
