

GSTR-8 is the monthly GST statement filed by e-commerce operators that collect tax at source under Section 52 of the CGST Act. It brings together the value of supplies made through the platform, returned supplies, the resulting net amount, and the TCS collected against individual sellers. The requirement applies when an e-commerce operator collects consideration for supplies made by sellers using its platform.
A seller’s TCS credit depends on what the marketplace reports against its GSTIN. GSTR-8 carries that transaction-level information into the GST system, so errors in seller details or taxable values can directly affect the credit visible to the supplier.
Marketplace sales rarely remain unchanged after purchase. Cancellations, returns, and refunds can reduce the value originally recorded, which means TCS should follow the revised transaction value rather than the initial sale alone. GSTR-8 allows those changes to be reflected before the monthly position is finalized.
The return brings sales, returned supplies, TCS, seller details, and earlier corrections into the same monthly record. Place-of-supply reporting, applicable from the April 2025 tax period, gives operators another figure to match against internal records and helps surface inconsistencies before they spill into later filings.
The normal GSTR-8 due date is the 10th day of the month following the relevant tax period. A return covering transactions for March would ordinarily be due by April 10, although a government extension can move the deadline for a particular period.
A completely inactive month does not necessarily require a GSTR-8 filing. When no TCS has been collected and there are no amendments, rejected entries, or other reportable transactions waiting from an earlier period, the operator is not required to file the statement for that month. Where filing is required, however, a delay beyond the applicable due date can bring late-fee consequences.
The GSTR-8 format keeps current transactions, corrections, interest, and payments in separate parts of the return. This arrangement prevents fresh monthly activity from becoming mixed with adjustments relating to an earlier filing.
| Table/Section | Information Covered | What Needs Attention |
|---|---|---|
| 1 and 2 | GSTIN, legal name, and trade name | Confirm that GSTR-8 is being prepared under the correct TCS registration |
| Table 3 | Supplies on which TCS is collected | Review supplier GSTIN, place of supply, gross supplies, returns, and TCS collected |
| Table 3.1 | Supplies involving unregistered suppliers | Check enrollment details, gross value, returned supplies, and resulting net value |
| Table 4 | Amendments to previously reported TCS transactions | Connect every correction with the original period and affected transaction |
| Table 4.1 | Amendments involving unregistered suppliers | Correct information previously reported through enrollment-based supplier records |
| Table 5 | Interest payable under the return | Review interest created by delayed liability or upward amendments |
| Tables 6 and 7 | Payment of TCS and related amounts | Match the liability with the available electronic cash ledger balance |
| Cash-ledger debit details | Payment entries created after liability settlement | Check the debit references for TCS, interest, and related payments |
Current-period transactions are primarily dealt with through Table 3, whereas corrections belonging to earlier returns move through the amendment tables. Keeping these two sets of information separate preserves the original filing history and makes later changes easier to track.
The same principle applies when the operator deals with unregistered suppliers. Separate reporting fields allow enrollment-based transactions and their later corrections to remain identifiable instead of being absorbed into the current month’s figures.
A required GSTR-8 filed after the applicable due date can attract a late fee for the period of delay. The amount becomes part of the filing liability and needs to be cleared before the delayed return can be completed.
Interest follows a different trigger because it relates to delayed payment of TCS rather than the filing delay by itself. An upward amendment relating to an earlier period can also create additional interest when the correction increases the TCS that should have been paid earlier.
Some errors can create consequences beyond late fees and interest. Failure to collect TCS where required, short collection, incorrect supplier reporting, or repeated discrepancies between marketplace records and the return may need separate correction or compliance action depending on the circumstances.
For that reason, GSTR-8 works best when it is treated as the final stage of the marketplace reconciliation process. Sales, cancellations, returns, supplier details, place of supply, and TCS should already agree before those figures are carried into the GST return.