02 Automated Compliance · E-commerce and marketplace retail
One sales number from five marketplaces: automating GST returns for a multi-channel seller
Selling across Amazon, Flipkart, Meesho, Myntra and a Shopify store meant five differently formatted sales reports every month, hours of clubbing and reformatting, and a GST return built on a spreadsheet nobody fully trusted. We built the system that produces one consolidated, return-ready sales figure — automatically.
- Five marketplace report formats ingested and normalised into a single sales ledger
- GSTR-1 and GSTR-3B figures — taxable value, tax by rate, returns, state-wise supplies — produced from the ledger, not assembled by hand
- The monthly clubbing-and-formatting exercise eliminated
- Marketplace TCS and commission reconciled against the same record, so the return and the books agree
The situation
Every marketplace reports differently. Amazon’s settlement and MTR reports, Flipkart’s sales and returns files, Meesho’s order and payment statements, Myntra’s reports, and a Shopify export each carry the same underlying facts — what was sold, to which state, at what value, with what tax, and what came back — in a different shape, with different column names, on a different cadence.
For this client, producing a single monthly sales figure meant downloading all of them, reformatting each into a common layout, clubbing them, stripping out returns and cancellations, and reconciling the total against what had actually landed in the bank after marketplace commissions and TCS. It took days, it was done at month-end under GST deadline pressure, and the resulting spreadsheet was the basis of the return. Any error in it was an error in the return.
What we built
- A per-marketplace ingestion layer. Each platform’s export is parsed by a script built for that format — column mapping, date handling, and the platform’s own quirks (Amazon’s multiple fee lines, Meesho’s return adjustments) handled once, in code, not every month by hand.
- A single normalised sales ledger. Every order, return and cancellation from every channel lands as a row in one structure: date, channel, order reference, state of supply, taxable value, GST rate, tax amount, and status.
- Return-ready outputs. From that ledger, the figures GSTR-1 and GSTR-3B actually need — B2C supplies by state and rate, credit-note adjustments for returns, the marketplace TCS to be claimed — are produced as a report, not a project.
- Reconciliation to cash. Marketplace settlements are matched to the ledger, so commissions, TCS deducted, and net receipts tie to sales. The return and the books describe the same month.
What changed
The monthly exercise became a monthly check: run the ingestion, review the exceptions the script flags, file. The days of clubbing disappeared, and so did the class of error that comes from reformatting five spreadsheets under deadline. Because the ledger is the single source, the client’s books, the GST return, and the marketplace settlements now agree with each other — which is also what a GST officer will test first if the return is ever examined.
The broader point
Multi-channel sellers are audited on reconciliation: sales as per books, sales as per GSTR-1, sales as per the marketplaces’ TCS statements. The three rarely agree when each is built separately. Building them from one ledger is the only durable fix, and it is the model behind our automated compliance and GST compliance engagements.
Next step
Have a process like this one?
Book a 30-minute discovery call. We scope the build, confirm what it changes, and give you a fixed-fee proposal within 48 hours.