The Consent Template CT047, finalised by the use case sub-council for Credit Rating Agency, provides a set of upper bounds for SEBI-registered Credit Rating Agencies to access financial information for periodic credit risk assessment. This template supports ongoing monitoring and review of an issuer’s financial position throughout a rating’s lifecycle, aligning with regulatory obligations under the SEBI Master Circular for Credit Rating Agencies (SEBI/HO/DDHS/DDHS-POD2/P/CIR/2025/101).
Please find below the parameters for Fair Use Template ID CT047 as finalized by the Credit Rating Use Case Council:
Consent Template Information – CT047
| Consent Template Information | Description | Further Explanation |
|---|---|---|
| Consent Template ID | CT047 | For Sahamati's internal records and explanation to the community |
| Status | Active | For Sahamati's internal records and explanation to the community |
| Use Case Category | Monitoring by Credit Rating Agency | For Sahamati's internal records and explanation to the community |
| Use case | To analyse the financials to assign and review the credit rating periodically by credit rating agencies | This use case enables a SEBI-registered Credit Rating Agency (CRA) to periodically monitor the financial position of an issuer throughout the lifecycle of a rating, based on regulatory obligations under the SEBI Master Circular for Credit Rating Agencies (SEBI/HO/DDHS/DDHS-POD2/P/CIR/2025/101, dated 11 July 2025), specifically Clause 9: Monitoring and Review of Ratings and Clause 11: Non-Cooperation by Issuer |
Consent Template Attributes and Values – CT047
| Consent Details (Attributes) | Values (as agreed in the Council | Rationale |
|---|---|---|
| Purpose Text | As agreed by FIUs to show to the customer: To analyse the financials to assign and review the credit rating periodically | To access and analyse GSTN data for periodic rating surveillance as per regulations |
| As per ReBIT: Explicit consent for monitoring of the accounts | In line with the purpose code | |
| Purpose Code | 104 | Explicit consent for monitoring of the accounts as per ReBIT |
| Purpose Code Category Name | Account Query and Monitoring | In line with per ReBIT Purpose Codes |
| FI Types | GSTR1_3B | To be able to do a continuous assessment of risk profile of the borrower based on a holistic financial assessment |
| Consent Types | Profile, Summary, Transactions | To be able to do a continuous assessment of risk profile of the customer based on a holistic financial assessment on GSTN Data |
| Fetch-type | Periodic | This requires a recurring data fetch to be able to continuously monitor a customer's financial health |
| Maximum Frequency | 1 time per month | FIUs require quarterly monitoring of the borrower’s financial health; however, since the ReBIT specification does not support quarterly frequency, this is represented as one fetch per month while operationally being used to meet quarterly surveillance needs. |
| Maximum FI Data Range | 12 months | While the Maximum FI Data Range is 12 months, the FIUs agree that they will do only incremental pulls over and above their last date of fetching data |
| Maximum Consent expiry | 5 Years or rating is withdrawn whichever is earlier | While consent should ideally match the full instrument tenure (10–30 years or perpetual), it is initially set to 5 years, with renewals thereafter. |
| Maximum Data Life | 1 Month | Based on the average time required to complete the financial analysis |
| Last Published on: 31st December 2025 |
Please note that the parameters of the individual consent templates in the Consent Template Library represent upper bounds for the respective use cases, as decided in the relevant User Councils. The parameters in the consent templates should be treated by participant(s) as outer limit(s) and not be construed as legal advice in any manner. Participants are encouraged to review their use case(s) and ensure compliance with applicable laws, including the RBI Master Directions on NBFC-AA and the DPDP Act.
Sahamati will publish additional consent templates as the AA ecosystem evolves based on discussions in the relevant Use Case Councils and the Fair Use Committee. Existing consent templates may also be revised based on statutory and regulatory guidance, including the DPDP Act and the Rules issued thereunder.