GST Audit Preparation for E-commerce Sellers
A GST audit or scrutiny of an e-commerce seller is, at its heart, a data-matching exercise. The officer holds several independent versions of your sales story — your GSTR-1 and 3B, the marketplaces' GSTR-8 filings, your suppliers' GSTR-1s feeding your 2B, e-way bill trails, and your income-tax filings — and checks whether they agree. Sellers who reconcile monthly walk through this easily; sellers who file from marketplace downloads and hope for the best discover years of small drifts all at once. Here is what to prepare, and how far ahead to prepare it.
The cross-checks an officer will run
| Comparison | What it tests | Common e-commerce failure |
|---|---|---|
| GSTR-1 vs GSTR-3B | Declared supplies vs summarised liability | Credit notes reflected in one but not the other |
| GSTR-1 vs operators' GSTR-8 | Your sales vs marketplace-reported sales | Netting returns silently; timing of order vs invoice dates |
| GSTR-3B ITC vs GSTR-2B | Credit claimed vs credit available | Claiming from booked invoices missing in 2B; unreversed platform credit notes |
| GST turnover vs income-tax turnover | Consistency across tax regimes | Payout-based booking in one, gross-based in the other |
| Cash/credit ledger usage | Payment discipline | Unaccepted TCS while cash was short-paid |
Every one of these is a reconciliation you can run yourself, today, before anyone asks. That is the entire strategy: pre-run the officer's checks and document the explanations for known gaps (timing differences, RTO policies, rate corrections) while memory is fresh.
It also helps to understand the department's information position. Officers examining e-commerce sellers can draw on the operators' filings and can seek data about supplies made through platforms, which means your marketplace activity is visible independently of anything you produce. The strongest position is books that generate the marketplace numbers rather than books reverse-engineered from them: voucher-level drill-down from any return figure to the underlying orders, fees, and settlements. When an officer's question can be answered by exporting a ledger instead of building a spreadsheet over a weekend, the audit changes character. Books built that way also shorten the audit itself, since most questions die at the first documented answer instead of spawning follow-up requisitions.
The document set to keep audit-ready
- Marketplace reports, archived monthly: sales, returns, settlement, tax, and TCS reports for every platform — downloaded and stored, because portal retention windows are not guaranteed to match audit look-back periods.
- Fee invoices from every platform entity (commission, ads, logistics), the backbone of your ITC claim.
- Books that tie to settlements: vouchers reconciling gross sales, returns, fees, TDS, TCS, and net payout for each settlement cycle.
- Return workings: the month-wise computation trail from books to each GSTR-1 and 3B figure, including credit-note registers and HSN summaries.
- TCS acceptance trail: period-wise records of GSTR-8 amounts accepted, matched to your TCS receivable ledger — see our GSTR-8 reconciliation guide.
- Policies in writing: your documented treatment of RTOs, cancellations, freebies, and rate corrections, ideally with CA sign-off.
A 90-day readiness plan
- Month 1 — rebuild the spine. Import and reconcile marketplace data for the open periods; get books to tie to settlements. TallySutra accelerates precisely this step, converting Amazon, Flipkart, and Meesho reports into balanced TallyPrime vouchers with settlement reconciliation and duplicate-safe re-imports for historical backfills.
- Month 2 — run the officer's checks. Execute each comparison in the table above; log every difference with its explanation, and quantify anything unexplained.
- Month 3 — remediate with your CA. Where genuine short-payment or excess ITC surfaces, voluntary correction before a notice is almost always the cheaper path; the mechanics and timing are professional-judgment territory.
During the audit itself
Respond through your CA, in writing, within timelines; provide exactly what is asked with a covering reconciliation rather than raw dumps; and never guess at explanations — an unexplained difference honestly flagged is better than an invented story that unravels. Most e-commerce audit findings are process findings, and demonstrating a monthly reconciliation discipline materially changes the tone of proceedings. If your CA manages several sellers, our CA workflow keeps voucher-level review and approval organised across clients.
Audit powers, thresholds, and procedures come in several statutory flavours and change over time; nothing here quotes limits or timelines for that reason. This article is educational preparation guidance — engage a qualified CA or tax professional the moment any audit intimation or scrutiny notice arrives, and before making voluntary payments. For the notice-handling side specifically, read our guide to common GST notices.
Frequently asked questions
What is the single best audit preparation for a marketplace seller?
Monthly reconciliation of books to marketplace settlements, and of returns to books — effectively pre-running the officer's own cross-checks (GSTR-1 vs 3B, vs GSTR-8, ITC vs 2B) and documenting explanations while the facts are fresh.
How long should I keep marketplace reports and fee invoices?
Archive them permanently as a practical matter — statutory record-retention periods apply and audit look-backs can reach several years, while marketplace portal retention windows may be shorter. Local copies cost nothing; missing evidence costs arguments.
What if my own pre-audit checks reveal short-paid tax?
Discuss voluntary correction with your CA promptly — self-identified corrections made before a notice are generally treated more favourably than the same amounts discovered by the department. The mechanics and interest computation need professional handling.
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