GST compliance automation for multi-channel e-commerce sellers

Why GST compliance is exceptionally complex for marketplace sellers

An offline retailer with ₹35 lakh turnover pays no GST and files no returns, while the same person selling the same products on Amazon must register for GST from day one, even at ₹10,000 turnover, pay GST on every sale, reconcile TCS deducted by Amazon with their GSTR-2B, claim ITC on Amazon's commission, and file GSTR-1 and GSTR-3B monthly. This asymmetry creates a compliance structure that traditional back-office staffing cannot handle efficiently.

Marketplace operators deduct 1% of the seller's taxable sales value as TCS and deposit it with the government, but sellers can later claim this as Input Tax Credit. The problem: TCS deduction reduces immediate receivables and creates working capital pressure, and sellers must match platform data with GST returns, reconcile returns and cancellations carefully, since TCS applies only to net taxable supplies. A ₹1 lakh order on Amazon nets ₹99,000 to the seller after TCS; the seller must then claim that TCS in GSTR-2B and adjust for any order cancellations, since the TCS base changes month to month.

Every sale, return, commission, and fee flows through digital records that must match the GST portal's ledgers exactly, making reconciliation essential for avoiding mismatches and notices. Manual reconciliation across three or more platforms—each with different settlement rhythms, fee structures, and reporting formats—creates a recurring data entry and validation job that grows exponentially with sales volume.

The six highest-impact processes automation runs for marketplace sellers

1. TCS calculation and deduction tracking

What staff do today: Download platform settlement reports (Amazon MTR, Flipkart Seller Ledger, Meesho JSON), manually extract TCS amounts, cross-check against GST portal ECL (Electronic Cash Ledger), and flag discrepancies. Errors here block tax credits for 30–60 days.

What automation does: Connects directly to marketplace APIs (or ingests native reports daily), calculates TCS liability in real time by state and product category, maps each TCS entry to the seller's GSTIN and period, cross-validates against GSTR-8 filings from operators, and alerts staff to shortfalls or duplicate entries before the credit window closes.

Data needed: Marketplace settlement reports, tax rate master (18%, 12%, 5%, 0%), seller GSTIN(s), state-wise registration list, monthly GST period calendar.

Owner still decides: Whether to use reverse charge for specific suppliers, which state inventory location to use for FBA orders, whether to claim TCS or carry it forward for later use.

2. GSTR-1 outward supply reconciliation

What staff do today: Export orders from each platform, compile them into a single list, map HSN codes, segregate B2B from B2C sales, check state of supply against shipping address, calculate tax rates, and manually enter into GSTR-1. Settlement reports from Amazon or Flipkart show returns and cancellations, while GST GSTR-1 must show gross sales with returns separately accounted, and a mismatch creates discrepancies that trigger notices.

What automation does: Pulls order data from all connected platforms, applies HSN and tax rate rules automatically, flags orders missing buyer GSTIN (for B2B), calculates state-wise liability, and generates GSTR-1 Table 4 (B2B) and Table 7 (B2C) ready to upload. Automatically separates returns and credit notes, with runrate tracking so cancellations don't inflate gross sales figures in GSTR-3B.

Data needed: Product master with HSN codes, tax rates, and category assignments; buyer GSTIN (for B2B orders); marketplace order feeds; HSN rate change schedule (updated when GST Council announces changes).

Owner still decides: HSN classification for ambiguous products, whether to split an order across two states (for shipping vs. billing), approval of B2B sales to unregistered buyers (edge case compliance).

3. ITC matching and GSTR-2B reconciliation

What staff do today: Download GSTR-2B from the portal, cross-check invoice details against purchase register, flag invoices in purchase records but absent from GSTR-2B, contact suppliers to investigate delays, and manually note which invoices can be claimed. If ITC claimed in GSTR-3B exceeds 105% of GSTR-2B, GST registration can be processed for cancellation, and a proper officer issues a notice requiring explanation.

What automation does: Auto-downloads GSTR-2B through API, matches every invoice in your purchase register against GSTR-2B line by line using supplier GSTIN, invoice number, and tax amount as keys, classifies mismatches (missing invoices, value discrepancies, GSTIN errors), calculates maximum claimable ITC (capped at 105% of GSTR-2B), and generates a reconciliation report with corrective actions. Alerts if a supplier's GSTIN is incorrect or if an invoice amount doesn't match.

Data needed: Purchase register with supplier GSTIN, invoice number, date, and tax amounts; GSTR-2B (auto-populated from portal); debit/credit note register.

Owner still decides: Whether to pursue a supplier for a missing or delayed invoice, whether to claim partial ITC if the supplier's invoice has an error, approval to write off an unclaimed ITC amount after 120 days.

4. Multi-state GST liability aggregation

What staff do today: Sales through Amazon, Flipkart, Meesho create state-wise liabilities based on shipping address. Staff manually split orders by state, calculate intra-state and inter-state tax separately, and file multiple GSTR-1 forms if the seller has multiple state registrations. A seller with inventory in Delhi, Mumbai, and Bangalore must file and reconcile three separate GSTR-1 forms—a 3x multiplication of reconciliation work.

What automation does: Traces every order to its shipping state automatically (using platform address data), calculates CGST/SGST for intra-state and IGST for inter-state supplies, aggregates liability by state, generates state-wise GSTR-1 versions, and produces a master reconciliation showing tax liability by state and period. If a seller has FBA inventory spread across states, automation tracks which fulfillment center shipped each order and applies the correct state tax.

Data needed: Order shipping addresses, seller's state registration list (GSTIN per state), intra-state vs. inter-state business model, FBA warehouse location data.

Owner still decides: Which states to register in (and deregister from) based on sales volumes, whether to consolidate inventory in one state to reduce compliance.

5. Return and cancellation adjustment

What staff do today: Track returns and cancellations from each marketplace (rates vary: Amazon 5–15%, Meesho 20–40%), manually adjust the TCS base, verify refunds against settlement reports, and ensure GSTR-1 shows gross sales with returns in a separate line. TCS is calculated on net value after returns, not gross sales, and returns in e-commerce can be 20–40% of gross sales, so the TCS base is much lower than gross for high-return-rate sellers, and sellers must ensure TCS reconciliation uses the platform's net sales figure.

What automation does: Ingests daily return and cancellation feeds from each marketplace, adjusts the TCS calculation for each period, reverses the original sale in GSTR-1 (Table 4B for returns), and recalculates output GST liability with the correct net base. Flags unusual return patterns (e.g., 50% returns on a single SKU in one week) so staff can investigate fraud or product quality issues.

Data needed: Daily/weekly return and cancellation reports from each marketplace, original order GST data, refund settlement data.

Owner still decides: Whether to apply exceptions (e.g., damaged goods threshold before refund), escalation path if returns spike above a threshold.

6. GSTR-3B filing and payment reconciliation

What staff do today: Compile GSTR-1 data into GSTR-3B (Table 5 outward taxable supplies, Table 6 outward exempt supplies), pull ITC from GSTR-2B, enter opening ITC balance, fill in tax liabilities by rate (5%, 12%, 18%), reconcile TCS credit, calculate net tax payable, and manually file on the GST portal. If previous GSTR-1 periods remain pending, the GST portal blocks further uploads under Section 37(4), creating a chain effect because delayed GSTR-1 disrupts GSTR-3B filing, TCS credit reflection, and ITC matching for buyers.

What automation does: Pulls completed GSTR-1 data, fetches auto-calculated ITC from GSTR-2B reconciliation, auto-populates GSTR-3B tables, calculates net tax due, applies TCS and manual tax paid amounts, and either generates a ready-to-file JSON or auto-files on the portal (if connected). Flags if GSTR-1 dependencies are missing and halts filing to prevent rejection.

Data needed: Finalized GSTR-1 (outward), ITC from GSTR-2B (inward), manual tax payments made, opening balances, tax rate schedule.

Owner still decides: Whether to claim full available ITC or defer some for future use (strategic decision for cash flow), approval to pay the net tax on the due date or request extension.

Impact ranking: effort vs. value

A seller managing three platforms (Amazon, Flipkart, Meesho) with ₹50–₹100 lakh monthly turnover typically spends 30+ hours on GST reconciliation monthly—equivalent to 0.75–1 FTE accountant or compliance staff. Automation reduces this to under 4 hours, freeing staff to focus on dispute resolution, supplier management, and strategic compliance planning.

GST rules specific to marketplace sellers and India (2026)

Even if annual turnover is below ₹40 lakh, marketplace sellers must register for GST if they want to sell through any digital marketplace. This mandatory registration applies to every seller from day one of sales.

Every e-commerce operator must collect TCS at 0.5% on the net value of taxable supplies made through its platform under Section 52 of the CGST Act, with the rate halved from 1% to 0.5% effective July 10, 2024 (0.25% CGST + 0.25% SGST for intra-state, or 0.5% IGST for inter-state supplies). The rate change mid-2024 requires automation to apply the correct rate by transaction date.

E-commerce sellers must file GSTR-1 (sales details), GSTR-3B (summary return), and GSTR-9 (annual return). Composition scheme is not available to e-commerce sellers, so all must file regular returns, month after month.

The reconciliation between marketplace settlement statement and GST returns is where most e-commerce sellers lose money or attract notices; outward supplies vs. the platform's sales report (total GMV, HSN-wise breakup, state-wise split) must align, and differences arise from returns, cancellations, replacements, and price adjustments.

If an e-commerce business operates in multiple states, separate GSTINs are needed for each state. A seller with FBA inventory in Delhi, Mumbai, and Bangalore must maintain three separate GST registrations and file three separate GSTR-1 forms each month.

The ₹1,000 threshold for claiming GST refunds has been removed, and small e-commerce exporters can now claim every rupee of GST paid on packaging, raw materials, and shipping costs, regardless of amount. This 2026 change benefits export-focused sellers selling through e-commerce platforms.

Common compliance mistakes and automation guards

Mistake 1: Claiming TCS credit before the operator files GSTR-8. When the e-commerce operator has not filed GSTR-8 for that period, the seller cannot claim TCS credit until the operator files. Staff often forget to wait for GSTR-8 and claim TCS in GSTR-3B early, then face a notice demanding reversal. Automation tracks operator filing status and halts TCS claims if GSTR-8 is pending.

Mistake 2: Over-claiming ITC against GSTR-2B. If ITC claimed in GSTR-3B exceeds 105% of GSTR-2B, the taxpayer's GST registration can be processed for cancellation, and a proper officer issues a notice requiring explanation. Automation caps ITC claims at 105% of available GSTR-2B and flags over-claims before filing.

Mistake 3: Mismatching GSTR-1 with marketplace settlement reports due to returns not being accounted. Settlement reports show net payouts after returns and cancellations, but GSTR-1 must show gross sales with returns separately accounted, and a mismatch creates discrepancies that trigger notices. Automation segregates returns and credit notes automatically, preventing this discrepancy.

Mistake 4: Filing state-wise GSTR-1 incorrectly for FBA inventory. A seller with inventory in Delhi warehouse but orders shipped to Mumbai customers may file GSTR-1 in Delhi only, creating a state-wise liability mismatch. Automation maps every order to its shipping state and generates state-wise GSTR-1 versions automatically.

Mistake 5: Ignoring ITC mismatches until the GST notice arrives. Failure to reconcile and correct mismatches can lead to denial of ITC claims and imposition of interest and penalties, with interest levied at 18% per annum for the period of delay in correcting the mismatch. Automation flags mismatches in real time, not in hindsight.

Mistake 6: Not reconciling TCS amounts in GSTR-2B with actual TCS deducted by the marketplace. It is critical to regularly reconcile the TCS amounts shown in GSTR-2B with the actual TCS deducted by Amazon/Flipkart as per their seller reports, as discrepancies can lead to compliance issues. Automation reconciles TCS daily against settlement reports and alerts to variance.

90-day rollout sequence

Days 1–10: Assessment & setup. Audit current GST filings for the past 3 months, identify data sources (marketplace APIs, manual reports, bank feeds), list all seller GSTINs and state registrations, download historical GSTR-1, GSTR-2B, and GSTR-3B files. Identify backlogs: any ITC mismatches, pending TCS credits, or reconciliation gaps.

Days 11–25: Data integration. Connect to marketplace APIs (Amazon MWS, Flipkart API, Meesho API) or set up daily/weekly report pulls (native CSV/JSON downloads). Ingest historical order data (last 12 months where possible), categorize by platform and state, validate against existing GSTR records. Map product HSN codes, apply tax rates, flag any unclassified SKUs.

Days 26–40: TCS & ITC reconciliation setup. Build TCS calculation engine: code tax rate rules (0.5% current rate, 1% for orders before July 2024), apply to each order, calculate state-wise liability. Pull GSTR-2B and build invoice matching logic: match supplier GSTIN + invoice number + amount against purchase register. Test on 1 month's historical data, resolve 3–5 discrepancies manually, verify result against actual filed GSTR-3B.

Days 41–55: GSTR-1 generation & testing. Build GSTR-1 generation from clean order data: segregate B2B (with buyer GSTIN) from B2C, apply correct state-of-supply (shipping address), assign HSN codes and tax rates, generate Table 4 and Table 7 outputs. Test against a historical month's filed GSTR-1 (should match exactly or flag variance reason). Resolve any state-wise discrepancies or missing GSTIN entries.

Days 56–70: Multi-state handling. For sellers with multiple state registrations, generate state-wise GSTR-1 versions. Test: seller with Mumbai and Delhi GSTIN should produce two separate GSTR-1 files (one for each state, showing only orders shipped to that state). Verify state-wise output tax matches aggregated total.

Days 71–85: GSTR-3B integration & reporting. Build GSTR-3B generator: pull GSTR-1 (outward), pull ITC from GSTR-2B reconciliation, auto-calculate net tax by rate, apply TCS credit, flag missing payments or late-filed GSTR-1 dependencies. Test on 1 month's finalized data, file test JSON on GST portal (or export for manual review). Build dashboard: TCS tracking, ITC status, filing deadlines, mismatch alerts.

Days 86–90: Dry-run & handoff. Run automation on current month (in progress), generate outputs, compare against manual work, document any variance, train staff on new process. Go live with next month's filing using automation (dry-run mode: staff reviews before filing, but automation handles 95% of data work). Monitor for errors, refine rules, move to auto-file mode by month 2.

What an owner still controls and monitors

Automation handles data aggregation, tax calculation, and compliance format generation—but the owner must still decide: which TCS credits to claim vs. defer (cash flow optimization), approval of HSN codes for new product categories (risk of misclassification), inter-state transfer pricing for FBA inventory, dispute escalation when a marketplace TCS claim is rejected, and strategic choices like whether to consolidate state registrations to reduce filing complexity.

AiStaffo connects your marketplace settlement feeds, bank transaction feeds, and purchase invoices directly into a reconciliation engine. The system calculates TCS liability by state and date, auto-flags ITC mismatches against GSTR-2B, generates GSTR-1 and GSTR-3B ready to file, and emails alerts when TCS credit is delayed or when outward supply totals don't match platform reports. Your team reviews the alerts, approves exceptions, and hits upload—removing the 20+ hours of manual reconciliation that now sits in your back office. Book a free automation audit to map your e-commerce workflow and see where hours are lost.