Section 158A of CGST explained: this guide covers what it means, who it applies to, the step-by-step process, documents required, fees, due dates and penalties in India — so you can stay compliant with confidence and avoid costly mistakes.
Section 158A of the CGST Act, 2017 enables the sharing of information furnished by a registered person on the common portal — such as registration details, returns, invoices under e-invoicing and e-way bill data — with other systems and persons, subject to obtaining the taxpayer's consent in the prescribed manner.
What Section 158A Says — In Plain English
Section 158A was inserted to create a lawful, consent-based mechanism for sharing GST data with external systems and recipients — a modern data-governance provision built around the account aggregator ecosystem. It provides that specified information furnished by a registered person may, subject to conditions, be shared: the particulars in the registration application under Section 25; the return under Section 39 and details of outward supplies under Section 37; the e-invoice details prepared under Section 31; and the e-way bill information, along with such other details as may be prescribed. Critically, the section is anchored in consent — the consent of the supplier for sharing details furnished in registration, returns and e-invoices, and the consent of the recipient where the details being shared identify or affect them. The information may be shared only with such other systems as may be notified by the Government. This provision underpins schemes that let taxpayers share verified GST data with account aggregators and financial information users to access credit and other services more easily.
Clause / Sub-section Breakdown
- 158A(1): Prescribed information — registration (S.25), returns (S.39) and outward supplies (S.37), e-invoice (S.31), e-way bill, and other prescribed details — may be shared with notified systems, in the prescribed manner.
- Supplier consent: Required for sharing details furnished in registration, returns and e-invoices.
- Recipient consent: Required where the details being shared relate to and identify the recipient.
- 158A(2): No action shall lie against the Government or the portal for sharing done in accordance with the section.
Applicability & Scope
- When a registered person consents to share their GST data with banks, lenders or account aggregators.
- When notified systems seek verified GST information to offer services such as loans or analytics.
- Whenever consent-based data flows are enabled through the common portal to a notified recipient.
- Only to systems notified by the Government — not to any recipient at large.
Worked Examples
Example 1 — Working-capital loan. A small business wants a working-capital loan from a bank that is a notified financial information user. Instead of manually compiling turnover proofs, the business, through an account aggregator, gives consent under Section 158A to share its GST return and turnover data from the common portal with the bank. The bank receives verified GST data directly and can assess the loan faster. Because the sharing happens only with the taxpayer's explicit consent and to a notified system, it is lawful and does not breach Section 158.
Example 2 — Recipient-identifying data. A platform seeks e-invoice details that identify the recipient of certain supplies. Here Section 158A requires not just the supplier's consent but also the recipient's consent before those recipient-identifying particulars are shared, ensuring both parties control their data.
Step-by-Step in Practice
1. A notified system (e.g., an account aggregator serving a lender) requests GST data. 2. The taxpayer grants consent in the prescribed manner on the common portal. 3. Where the data identifies a recipient, the recipient's consent is also obtained. 4. The portal shares only the specified data with the notified system. 5. The data is used by the recipient (e.g., to underwrite credit); the Government and portal are protected from action for sharing done per the section.
Common Mistakes & Practical Notes
- Assuming sharing can happen without explicit consent — consent in the prescribed manner is mandatory.
- Forgetting that recipient-identifying details need the recipient's consent too, not just the supplier's.
- Believing data can be shared with any third party — only notified systems qualify.
- Confusing Section 158A (consent-based, taxpayer-driven) with Section 158's official-exception disclosures.
Related Sections
Section 158A is a carefully bounded exception to the confidentiality regime in Section 158 and complements the bar on statistical disclosure in Section 152. The data it covers is furnished under Section 25 (registration), Section 37 (outward supplies), Section 39 (returns) and Section 31 (invoices, including e-invoicing), and is generated through the common portal governed by Section 146. By operating on consent, it aligns GST data sharing with the account aggregator framework and modern data-privacy expectations.
Recent Amendments & Context
Section 158A is itself the recent amendment at the centre of this cluster: it was inserted by the Finance Act, 2023 and notified into force from 1 October 2023, with the manner of consent and the systems to be notified prescribed through rules and notifications. It operationalises the account aggregator model for GST — letting a taxpayer push verified GST turnover and return data to a lender or financial information user with a click of consent, rather than assembling paper proofs. This directly supports flow-based lending to MSMEs. As India's broader data-protection framework matures, Section 158A's consent-first design positions GST data sharing to align with contemporary privacy norms, while Sections 152 and 158 continue to guard against non-consensual or identifiable disclosure.