E-commerce GST reconciliation gets genuinely harder the moment you sell on more than one marketplace, because each one hands you sales data, return data, TCS credit, and settlement payouts in a different report format and on a different schedule. Reconciling Amazon in isolation and Flipkart in isolation, then hoping the totals add up to your books, is how sellers end up chasing small unexplained gaps every single month.
This article lays out a four-layer framework you can apply consistently across marketplaces, walks through what each layer is actually checking, and covers the added complexity of consolidating across multiple GSTINs and states.
Why Reconciling One Marketplace Isn't Enough
Your GSTR-1 is filed per GSTIN, consolidating every channel that sells under that registration, not per marketplace. If you reconcile Amazon cleanly and Flipkart cleanly but never check the combined numbers against your filed return, channel-level errors that individually look small can add up to a return-level discrepancy that's much harder to trace back once the filing window has closed.
The Four-Layer Reconciliation Framework
| Layer | What you're checking | Primary source documents |
|---|---|---|
| 1. Sales | Every completed order across every marketplace is captured as a taxable supply, correctly classified | Marketplace tax invoice reports, direct invoices |
| 2. Returns | Cancelled, RTO, and refunded orders are excluded or credited correctly, not double-counted as sales | Marketplace return/RTO reports |
| 3. TCS | Tax collected at source by each marketplace matches what you can claim as credit | Marketplace TCS/TDS certificates, GSTR-2B related credit |
| 4. Settlement | Net bank credits tie back to gross sales minus commission, fees, and adjustments | Marketplace settlement reports, bank statement |
Each layer feeds the next: sales minus returns gives you real taxable turnover; TCS is calculated on that turnover by each marketplace; and settlement is the final cash outcome after commission and TCS deductions. Reconciling settlement without first getting sales and returns right just means you're chasing a downstream symptom.
Layer by Layer: What to Actually Do
Sales layer
Consolidate tax invoice reports from every channel, whether that's Amazon, Flipkart, Meesho, Myntra, AJIO, JioMart, or direct GST invoicing, into one view before classification. Uploading these under Admin > Upload Files and letting GSTR-1 automation handle B2B/B2C classification across channels keeps the logic consistent instead of applying slightly different rules per marketplace by hand.
Returns layer
Each marketplace has its own return-reporting cadence; a Meesho return might settle in the same cycle as the sale, while a Flipkart RTO can lag by a cycle or more. Reconcile returns against the specific sale they relate to, not just as a lump total for the period, so a return that arrives late doesn't get missed entirely.
TCS layer
Each marketplace deducts TCS on your behalf and is required to report it, which should ultimately support a corresponding credit for you. Mismatches here are usually traceable to a marketplace's own filing timeline rather than your records, similar to a GSTR-2B mismatch on the purchase side; if you're unfamiliar with that pattern, our guide on how to fix a GST mismatch covers the timing-versus-error distinction in more depth.
Settlement layer
Match net settlement credits against your bank statement using the bank statement parser, and treat any unexplained shortfall as a prompt to check the sales and returns layers first before assuming it's a settlement-specific issue.
Consolidating Across Multiple GSTINs and States
If you dispatch inventory from fulfilment centres in more than one state, the same marketplace account can generate supplies under more than one GSTIN. Reconciliation has to be split by GSTIN before it's consolidated, not the other way around; pooling multi-state data first and splitting it later is a common source of place-of-supply errors. OneBooks GST's multi-organization, multi-GSTIN structure with role-based access is built to keep this separation clean when more than one person is handling different registrations.
A Monthly Cadence That Scales With Marketplace Count
- Download sales, return, TCS, and settlement reports from every active marketplace for the same filing period.
- Run the sales and returns layers per marketplace, then consolidate per GSTIN.
- Check TCS credit against the consolidated taxable turnover per GSTIN.
- Reconcile total settlement across all channels against bank credit for the period.
- Compare the consolidated total against your filed or draft GSTR-1 before submission, not after.
- Log any unresolved variance with its likely layer (sales, returns, TCS, or settlement) so next month's review starts from where this one left off.
Where OneBooks GST Fits In
Marketplace sales imports across Amazon, Flipkart, Meesho, Myntra, AJIO, JioMart, and Excel/CSV feed into one GSTR-1 preparation workflow with B2B/B2C classification, credit/debit notes, HSN summary, and validation warnings, so the sales and returns layers are handled consistently regardless of channel count. For a deeper look at any single marketplace, see the Amazon GST reconciliation guide or the Meesho GST reconciliation guide. Current plans and limits are listed on OneBooks GST plans.
Common Pitfalls When You Scale Past Two Marketplaces
The four-layer framework holds up well at small scale, but a few pitfalls tend to appear only once a seller is active on three or more channels at once. The first is inconsistent invoice numbering across channels feeding into one GSTIN, which creates duplicate or colliding invoice numbers in your consolidated GSTR-1; prefixing each channel's series distinctly avoids this. The second is treating every marketplace's settlement cycle as if it runs on the same calendar, when in practice one platform might settle weekly and another fortnightly, making a same-period settlement comparison misleading unless you align by order date rather than payout date. The third, and most disruptive, is adding a new marketplace mid-year without updating your GSTIN-level consolidation process, which can leave an entire channel's sales sitting outside your regular reconciliation cadence until someone notices the gap at year-end.
A simple guardrail
Whenever you onboard a new marketplace, add it to your monthly cadence checklist on day one rather than after the first filing cycle, and confirm its report formats and settlement timing against the four layers before your first reconciliation run, not during it.
Frequently Asked Questions
Why is reconciling each marketplace separately not enough?
GSTR-1 is filed per GSTIN, combining every sales channel under that registration. Small channel-level errors that look fine individually can add up to a real discrepancy at the consolidated return level.
What are the four layers in this reconciliation framework?
Sales, returns, TCS, and settlement. Sales minus returns gives real taxable turnover, TCS is calculated on that turnover, and settlement is the resulting net cash credited to your bank.
Why doesn't my TCS credit match across marketplaces?
TCS mismatches are usually caused by a marketplace's own filing timeline rather than an error in your books, similar to a purchase-side GSTR-2B mismatch. Check again after the marketplace's next filing cycle.
How should I handle multiple GSTINs when reconciling e-commerce sales?
Split reconciliation by GSTIN first, based on the state that actually dispatched each order, then consolidate. Pooling data across states before splitting is a common source of place-of-supply errors.
How often should e-commerce GST reconciliation be done?
Monthly, aligned with your filing cycle, is the practical minimum. Sellers with high order volumes often benefit from a lighter weekly check to catch returns and RTOs before they pile up.
Can OneBooks GST reconcile sales across multiple marketplaces at once?
Yes, marketplace sales imports from Amazon, Flipkart, Meesho, Myntra, AJIO, JioMart, and Excel/CSV feed into a single GSTR-1 preparation workflow, and Admin > Detailed Reports gives a consolidated view across channels.
