Summary of Advisory regarding Online Payment of Court Fees on GSTAT Portal
The advisory deals with a practical difficulty being faced by taxpayers while filing appeals before the Goods and Services Tax Appellate Tribunal on the GSTAT portal. It clarifies that where the taxpayer has made online payment of court fees, but the payment status is not reflected as “Success”, the taxpayer should first wait for a period of up to 72 hours from the time of payment, since the status may take time to update due to payment processing delays.
The advisory further provides that if the payment status does not change to “Success” even after 72 hours, the system shall not restrict or prevent filing of the appeal. In such cases, the taxpayer shall be permitted to continue the appeal filing process on the GSTAT portal without interruption. The payment status will be reconciled at the backend, and the appeal filing process shall not be adversely affected merely because the portal has not immediately reflected the successful payment.
Commentary considering GST Statute
The advisory is significant in the context of appeals before the GST Appellate Tribunal under Section 112 of the CGST Act, 2017. Filing of an appeal before GSTAT is a statutory remedy, and procedural or technical issues on the portal should not defeat the substantive right of appeal, particularly when the taxpayer has already attempted or completed payment of the prescribed court fee.
The clarification proceeds on a sound administrative principle that a taxpayer should not suffer merely because there is a delay in payment-status reconciliation between the payment gateway and the GSTAT portal. Once payment has been made, and the delay is only in reflection of status as “Success”, the appeal-filing process cannot reasonably be kept hostage to a backend technical confirmation. The advisory therefore protects the taxpayer from avoidable limitation disputes, filing delays, and procedural uncertainty.
This is especially relevant because appeal filing under GST is governed by statutory timelines. Any inability to file due to portal restrictions may otherwise expose the appellant to limitation-related objections, even though the delay may not be attributable to the taxpayer. By stating that the system will not restrict filing even where the status is not updated after 72 hours, the advisory ensures that the electronic filing system remains facilitative and does not become an impediment to the exercise of appellate remedy.
From a practical compliance perspective, taxpayers should preserve the payment acknowledgement, transaction reference number, bank debit proof, challan details, screenshots of the portal status, and any other contemporaneous evidence of payment. These records may be relevant if any defect memo, registry query, or reconciliation issue subsequently arises. For instance, if M/s A Metals Pvt. Ltd. pays the court fee on 1 July 2026 while filing an appeal before GSTAT and the amount is debited from its bank account, but the GSTAT portal does not show “Success”, the taxpayer should wait until 4 July 2026. If the status remains unchanged even after 72 hours, the taxpayer may proceed with the appeal filing and keep the payment proof on record, since the advisory assures backend reconciliation.
The advisory also reflects the broader shift in GST appellate administration towards portal-based compliance. However, electronic administration must remain consistent with statutory justice. A technical payment-status lag cannot be equated with non-payment where the taxpayer has in fact initiated and completed payment through the prescribed online mechanism. The clarification therefore provides necessary procedural certainty to taxpayers and professionals filing GSTAT appeals.
Practical Takeaway
Where court fee has been paid online but is not reflected as “Success” on the GSTAT portal, the taxpayer should wait up to 72 hours. If the status is still not updated, the appeal may still be filed, and the portal should not block the filing. The taxpayer should maintain complete payment evidence until backend reconciliation is completed.
