An NBFC with ₹500 crore or more in assets is required to submit at least 14 distinct returns and disclosures to the RBI across various frequencies — monthly, quarterly, half-yearly, and annually. Each has a format, a deadline, and a data specification. The Risk Reporting Agent AI maintains a complete regulatory filing calendar, generates each return from the live operational data at the appropriate frequency, validates the data against the prescribed format before submission, and records the filing confirmation. Compliance is a byproduct of real-time data management, not a separate compliance exercise.
Why regulatory filing is a reporting team's largest single burden — and how automation eliminates it
In most NBFCs with a manual or semi-automated reporting infrastructure, regulatory filing is the reporting team's highest-anxiety task. The anxiety is not about the calculations — the calculations are known and documented. The anxiety is about the data: is the extract current? Does it tie to the financial statements? Are there any discrepancies between what is being filed and what was submitted last quarter? Does the filing team have the authorised signatory available before the deadline?
Each of these concerns is a symptom of the same underlying problem: the data used for the regulatory filing is a copy of the source data, not the source data itself. A copy can be stale. A copy can have formatting errors introduced in the transfer. A copy can diverge from the simultaneously updated source when an account is reclassified or a provision is updated between the extraction and the submission.
The Risk Reporting Agent AI files directly from the source. There is no extraction, no copy, no transfer. The filing data is the operational data, formatted for submission. The question "does the filing tie to the financial statements?" cannot arise because they are the same data.
The RBI regulatory calendar: what gets filed, when
Monthly
Balance sheet summary, income/expenditure, NPA position, and capital adequacy — monthly
NBS-6 is the primary monthly NBFC return — a high-level financial summary submitted to the RBI within 15 days of the month-end. The Risk Reporting AI assembles the NBS-6 from the CBS balance data and the Provisioning AI's classification database at month-end, validates the format against the RBI's prescribed XBRL taxonomy, and submits via the RBI's XBRL reporting portal. The submission is complete 7–10 days before the 15-day deadline — not on the last day.
→ Source: CBS + Provisioning AI · Format: XBRL · Auto-submitted · Confirmation recordedafter month-end
Filed day 8
Quarterly
Detailed NPA schedule by category, provisioning coverage, and sector-wise credit distribution
NBS-7 requires the institution to report the full IRACP-classified NPA position — account counts, outstanding balances, and provisions by category — plus the sector-wise breakdown of the credit portfolio. The Provisioning AI provides the classification data; the Origination AI provides the sector-wise portfolio composition. The two data sets are merged, validated, and submitted within 21 days of quarter-end.
→ Source: Provisioning AI + CBS · Format: XBRL · Sector data from Origination AI · Filed day 14after quarter-end
Filed day 14
Monthly
Asset and liability maturities bucketed by time band — 1–14 days through 5+ years
The ALM return requires the institution to report the maturity bucket structure of its entire balance sheet — assets and liabilities bucketed by days to maturity. The Risk Reporting AI pulls the maturity schedule from the CBS for every asset and liability and applies the RBI's prescribed bucketing rules. The Statement of Structural Liquidity and the Interest Rate Sensitivity Statement are generated simultaneously and submitted as a package.
→ Source: CBS maturity schedules · RBI bucket structure applied · Simultaneous SLS + IRSSafter month-end
Filed day 7
Code Report
Quarterly
Complaints received, resolved, and pending; collection conduct incidents; disclosures made
The FPC quarterly return requires the institution to report on customer complaints (received, resolved, and pending), any collection conduct incidents flagged, and confirmation of the disclosures made during the quarter. The Risk Reporting AI assembles this from the collections system (conduct data), the grievance management system (complaints), and the Disbursement AI (disclosure confirmations). It is the one return that requires data from the most operational systems.
→ Source: Collections, Grievance, Disbursement AI · Conduct incidents cross-checkedafter quarter-end
Filed day 18
Disclosure
Quarterly
Gross NPA ratio, Net NPA ratio, and Provision Coverage Ratio — public disclosure
The three NPA ratios required for public disclosure are computed directly from the Provisioning AI's classification database and the CBS balance data. They are posted to the institution's website simultaneously with the NBS-7 filing — ensuring consistency between the regulatory return and the public disclosure. The Risk Reporting AI generates a disclosure document in the prescribed format and an automated CMS update for the website.
→ Consistent with NBS-7 · Website and XBRL filing simultaneous · CMS update automatedwith NBS-7
Filed day 14
The complete regulatory filing calendar: all 14 returns tracked
| Return | Frequency | Deadline | Primary Data Source | Status — Q3 FY2025–26 |
|---|---|---|---|---|
| NBS-6 (Financial parameters) | Monthly | 15 days post month-end | CBS + Provisioning AI | Filed — all months |
| NBS-7 (Asset quality) | Quarterly | 21 days post quarter-end | Provisioning AI + CBS | Filed Q1 and Q2 |
| ALM — Structural Liquidity | Monthly | 15 days post month-end | CBS maturity schedules | Filed — all months |
| ALM — Interest Rate Sensitivity | Monthly | 15 days post month-end | CBS + Pricing AI | Filed — all months |
| Fair Practice Code Report | Quarterly | 30 days post quarter-end | Collections + Grievance + Disbursement AI | Filed Q1 and Q2 |
| GNPA / NNPA Public Disclosure | Quarterly | With NBS-7 | Provisioning AI | Filed Q1 and Q2 |
| Credit Information Returns (CIBIL) | Monthly | 15 days post month-end | CBS payment register | Filed — all months |
| KYC / AML Suspicious Transaction | As applicable | Within 7 days of identification | KYC AI + Document AI | 3 filed this quarter |
| Significant Counterparty Exposure | As applicable | When threshold crossed | CBS + Origination AI | No threshold crossings |
| Stress Test Report (Q3) | Quarterly | 30 days post quarter-end | Stress Testing AI | Data-ready · Jan 14 filing |
| NBS-7 Q3 | Quarterly | Jan 21, 2026 | Provisioning AI + CBS | Data-ready · Jan 14 filing |
| Annual Director / Auditor Report | Annual | Within 30 days of AGM | All data sources consolidated | Annual · FY2025–26 build |
| Related Party Transactions | Quarterly | With quarterly financials | CBS + Treasury | Filed Q1 and Q2 |
| Capital Adequacy Return (CAR) | Quarterly | 21 days post quarter-end | Stress Testing AI + CBS | Filed Q1 and Q2 |
Regulatory compliance is not a periodic exercise — it is a continuous data quality discipline
An NBFC that treats regulatory filing as a quarterly or monthly event — rather than a continuous data quality practice — will always file in a rush, because the data quality issues that were tolerable between reporting cycles are suddenly urgent at the filing deadline. The Risk Reporting Agent AI treats regulatory filing as the natural output of continuous data management: the CBS is current, the provisioning is current, the ALM maturity schedule is current — and all that the regulatory return requires is to format that current data into the prescribed submission format and send it. When the data is always right, the filing is never the problem. The filing is just the printing of what you already know to be true.