Updated Annexure B for GST Refund of Unutilised ITC: Transition to JSON Filing
The GST Council's recent mandate for JSON-based Annexure B filings marks a significant shift in the procedure for claiming refunds of unutilised Input Tax Credit (ITC). This change, coupled with system-based reconciliation, demands heightened diligence from all assessees.
What Changed: A Shift to JSON
The core of the change lies in the adoption of a JSON (JavaScript Object Notation)-based format for Annexure B. This format necessitates detailed, invoice-wise reporting of all inward supplies for which unutilised ITC is being claimed. The transition is designed to bolster data accuracy and streamline the refund process.
Detailed Explanation: Navigating the New Requirements
The new mechanism has several key components:
- Invoice-Level Data: Each invoice related to the refund claim requires specific details, including the supplier's GSTIN, invoice number, date, and value.
- ITC Component Breakdown: The amount of ITC claimed per invoice must be itemised by tax type (IGST, CGST, SGST/UTGST).
- GSTR-2B Reconciliation: The system automatically cross-references the ITC claimed in Annexure B with the ITC reflected in the assessee's GSTR-2B. Discrepancies will trigger scrutiny.
- GSTR-3B Alignment: The ITC claimed in Annexure B must align with the ITC declared in the GSTR-3B returns. Mismatches will be flagged.
- Documentation: Though the focus is on data, maintaining supporting documents like invoices and debit notes is still essential to substantiate claims.
Practical Implications for Assessees
The transition presents practical challenges for assessees:
- Heightened Compliance: The move to invoice-wise reporting increases the compliance burden. Meticulous record-keeping is now paramount.
- Increased Scrutiny: The automated reconciliation process leaves little room for error. Even minor discrepancies can lead to delays or rejections.
- Technology Upgrades: Businesses may need to update accounting software or implement new processes to accommodate JSON filing.
- Potential for Delays: The enhanced verification process will likely extend the time it takes to process refund claims.
Illustrative Example
Consider a scenario where an assessee, Alpha Ltd., claims a refund of ₹8,00,000 in unutilised ITC through Annexure B. During scrutiny, the GST authorities find a discrepancy. The ITC claimed on a specific invoice in Annexure B does not match the ITC reflected in Alpha Ltd.'s GSTR-2B. This could be due to a reporting error or a mismatch in the supplier's GSTR-1. As a result, the authorities could issue a notice, requesting supporting documentation. If Alpha Ltd. cannot adequately justify the discrepancy, the refund for that portion of the ITC may be rejected. (This is illustrative only. Actual liability depends on applicable slab rates, surcharge, cess, and the specific facts of each case.)
Conclusion
The shift to JSON-based Annexure B filing for GST refunds necessitates a proactive approach from all assessees. A strong emphasis on data accuracy, robust reconciliation, and maintaining complete supporting documentation is critical to navigate these changes successfully.
Disclaimer: This article is for educational and informational purposes only and does not constitute professional advice. Please consult a qualified Chartered Accountant for advice specific to your situation.