Compliance Calendar for NBFCs: Never Miss a Filing
Last reviewed: November 2026
A compliance calendar for NBFCs is a single schedule of every recurring RBI, Registrar of Companies (ROC) and tax obligation, with a due date, data owner, reviewer and proof of filing for each. Without one, deadlines live in personal inboxes and spreadsheets, and a single late return becomes a supervisory finding.
This guide is for chief compliance officers and company secretaries at non-banking financial companies (NBFCs) of every layer. It covers the obligation categories to track, why deadlines get missed, a six-step calendar workflow, an illustrative cost case and the metrics that show the calendar is working.
Key Takeaways
- An NBFC compliance calendar must cover three families of obligations: RBI returns and reporting, corporate law filings, and tax payments and returns.
- RBI's Supervisory Returns Directions, 2026 set uniform timelines: 15 days for monthly returns and 21 days for quarterly and yearly returns.
- Most missed deadlines come from late source data, not late filing, so every entry needs a named data owner and an internal due date.
- A calendar is only useful if it escalates, enforces maker-checker review and stores evidence, which spreadsheets do poorly.
What Is a Compliance Calendar for NBFCs?
A compliance calendar for NBFCs is a register of recurring obligations, each linked to a regulation, frequency, due date, owner and evidence.
Three families of obligations sit inside it. RBI obligations include supervisory returns, credit information reporting and fraud reporting, and they vary by layer under scale-based regulation for NBFCs.
Corporate law obligations include board meetings, the annual general meeting (AGM) and ROC filings. Tax obligations include tax deducted at source (TDS), goods and services tax (GST) and advance tax.
Which RBI Returns Belong on the Calendar?
The RBI returns that belong on the calendar depend on your layer, and RBI's own returns list is the starting point. It shows these returns for NBFCs other than housing finance companies (HFCs):
| Return | What It Covers | Frequency | Applies To |
|---|---|---|---|
| DNBS01 | Important financial parameters | Quarterly | Middle and upper layer (not CICs) |
| DNBS02 | Important financial parameters | Quarterly | Base layer (not P2Ps) |
| DNBS03 | Important prudential parameters | Quarterly | Middle and upper layer |
| DNBS04A / DNBS04B | Short-term and structural liquidity | Quarterly / Monthly | Middle and upper layer, some base layer |
| DNBS10 | Statutory auditor certificate | Yearly | All NBFCs |
| DNBS13 | Overseas investment details (nil if none) | Quarterly | All NBFCs |
| FMR | Fraud monitoring return | As and when | All applicable NBFCs |
Core investment companies (CICs) and peer-to-peer (P2P) platforms file their own variants. HFCs follow separate return directions, so a group with an HFC needs a separate set of entries.
Why Do NBFCs Miss Compliance Deadlines?
NBFCs miss compliance deadlines for five reasons: late source data, unclear ownership, rule changes not reflected in the tracker, single-person dependency and no escalation. Each one has a simple prevention check.
| Cause | Effect | Prevention Check |
|---|---|---|
| Source data arrives late | Return prepared in a rush, errors slip in | Internal data due date 5 to 7 days before filing |
| No named owner | Everyone assumes someone else filed | One preparer and one reviewer per entry |
| Rule changes not updated | Old timelines or forms used | Monthly circular review with calendar sign-off |
| One person holds the logins | Leave or exit stops filing | Maker and checker users for every portal |
| Reminders without escalation | Overdue items sit quietly | Auto-escalation to CCO and CFO on breach |
The first cause dominates: a 21-day return is hard to file well if the finance close takes 18 days.
What Changed in RBI Return Timelines in 2026?
RBI consolidated return timelines in 2026. According to RBI's Non-Banking Financial Companies – Supervisory Returns Directions, 2026 (31 July 2026), weekly returns are due by the Wednesday of the following week, monthly returns within 15 days, and quarterly and yearly returns within 21 days.
Some returns have special timelines. The DNBS10 auditor certificate is due within five working days of signing the auditor's report, and the fraud monitoring return within 14 days of a fraud being classified.
What Is the Right Compliance Calendar Workflow for NBFCs?
The right compliance calendar workflow for NBFCs has six steps: build the obligation register, map data and owners, set internal due dates, automate reminders and escalation, file with maker-checker review and evidence, and review rule changes monthly.
- Build the obligation register from RBI, Companies Act and tax sources.
- Map each entry to its data source, preparer and reviewer.
- Set internal due dates well before the regulatory due date.
- Automate reminders and escalation by days remaining.
- File with maker-checker review and attach proof of submission.
- Review rule changes monthly and update the register.
Step 1: What Goes Into the Obligation Register?
The obligation register holds every recurring duty with its legal basis, frequency, applicability and due-date rule. Write the rule, not just the date, such as "within 21 days of quarter end", so the system can generate future dates.
Include non-return deadlines too. Under RBI's NBFC Credit Information Reporting Directions, 2025, as amended from 1 July 2026, credit data is reported as on the 9th, 16th, 23rd and last day of each month, with the month-end full file due by the 5th of the next month.
Step 2: Why Map Data Owners, Not Just Filers?
Mapping data owners matters because most returns draw on finance, risk, treasury and operations data. A liquidity return needs treasury cash flows, while a prudential return needs asset classification from the loan system.
Name the data owner for each field group. The same discipline improves your NBFC MIS reporting, because the board and RBI then see numbers from one source.
Step 3: How Early Should Internal Due Dates Be?
Internal due dates should give the reviewer at least three working days before the regulatory deadline. A practical rule is data lock seven days before, draft four days before and filing two days before.
The table shows how this works across families:
| Obligation Family | Example | Regulatory Rule | Internal Data Lock |
|---|---|---|---|
| RBI quarterly return | DNBS02 | Within 21 days of quarter end | Day 12 after quarter end |
| RBI monthly return | DNBS04B | Within 15 days of month end | Day 8 after month end |
| ROC filing | AOC-4 | Within 30 days of AGM | Signed accounts ready before AGM |
| ROC filing | MGT-7 | Within 60 days of AGM | Shareholding data frozen at AGM |
| Tax deposit | TDS | By the 7th of next month (March differs) | Day 3 of next month |
The ROC timelines come from the Companies Act, 2013.
Step 4: How Should Reminders Escalate?
Reminders should escalate by stage, not repeat the same email. Send the preparer a reminder at data lock, the reviewer at draft, and the chief compliance officer (CCO) and CFO when any item crosses its internal date.
Digiqt's regulatory return automation AI agent shows how return preparation and validation can be automated around such a calendar.
Step 5: Why Is Maker-Checker Filing Essential?
Maker-checker filing is essential because it protects accuracy and continuity together. RBI's 2026 Directions provide a super user credential on the Centralised Information Management System (CIMS) to create maker and checker users, and say hard copy or email submissions are not treated as filed unless prescribed.
Attach the acknowledgement, final file and reviewer sign-off to each entry. That evidence trail is what an inspector asks for, as our guide to RBI inspection readiness for NBFCs explains.
Step 6: How Do You Keep the Calendar Current?
Keep the calendar current with a monthly rule-change review signed off by the CCO. Since November 2025, RBI has replaced many master directions with entity-wise directions, and the Income-tax Act, 2025 replaced the 1961 law from 1 April 2026, changing TDS form numbers.
Digiqt's regulatory change tracking AI agent shows how new circulars can be flagged and mapped to affected obligations.
How many of last quarter's filings were submitted on the final day?
Talk to Our Compliance Software Specialists
Visit Digiqt to see how a custom compliance calendar can escalate every deadline before it is missed.
How Much Does a Manual Compliance Calendar Cost an NBFC?
A manual compliance calendar costs an NBFC in staff hours, last-minute rework and supervisory risk. In this illustrative scenario, a middle layer NBFC tracks 160 recurring filings a year across RBI, ROC and tax.
With a spreadsheet tracker, each filing takes about six hours of chasing data, collating and reviewing. A rules-based calendar with data owners and escalation cuts that to about 3.5 hours.
| Measure | Spreadsheet Tracker | Rules-Based Calendar |
|---|---|---|
| Filings a year | 160 | 160 |
| Hours per filing | 6 | 3.5 |
| Total hours a year | 960 | 560 |
| Cost at ₹1,500 per hour | ₹14,40,000 | ₹8,40,000 |
| Filings made on the last day | 24 | 6 |
That is a saving of 400 hours, or ₹6 lakh a year. The larger gain is fewer last-day filings, where most errors and resubmissions happen.
The lesson for leadership: the cost of a missed or wrong return is not the staff time, but the supervisory attention that follows. A calendar that escalates early is cheap insurance against that.
Where Does Custom Software Development Fit in a Compliance Calendar for NBFCs?
Digiqt's custom software development services cover UI/UX design, web development, app development and quality assurance. A compliance calendar for NBFCs would be built as a custom application, scoped through Problem Statement Analysis or delivered by a Dedicated Development Team.
A typical build would include modules you specify:
- Obligation register that stores due-date rules and generates future dates.
- Owner and data mapping with preparer, reviewer and data owner per entry.
- Escalation engine that alerts by stage and breach.
- Evidence store for acknowledgements, final files and sign-offs.
- Integrations with the loan management system and general ledger, so data readiness is visible.
Access control and audit logs should follow the RBI IT governance expectations described in our guide to RBI IT governance directions for NBFCs.
Which Compliance Calendar Approach Fits Your NBFC?
The right compliance calendar approach depends on your layer, entity count and filing volume.
| NBFC Situation | Recommended Approach |
|---|---|
| Small base layer NBFC, one entity | Shared calendar with named owners and two-stage reminders |
| Middle layer NBFC with monthly liquidity returns | Rules-based calendar linked to finance close and loan system |
| Group with an NBFC and an HFC | Separate obligation sets per entity in one calendar |
| NBFC with listed debt securities | Add stock exchange disclosure deadlines to the register |
| NBFC with frequent rule changes and audits | Custom calendar with evidence store and change review |
Which Metrics Show the Compliance Calendar for NBFCs Is Working?
Five metrics show whether the compliance calendar for NBFCs is working: on-time filing rate, average buffer days, last-day filing share, data lock adherence and resubmission rate. Review them at every compliance committee meeting.
| Metric | Formula | What a Weak Number Signals |
|---|---|---|
| On-time filing rate | Filings made by due date ÷ filings due | Gaps in ownership or escalation |
| Average buffer days | Due date minus filing date, averaged | Work is compressed into the deadline |
| Last-day filing share | Filings on due date ÷ total filings | Data arriving late |
| Data lock adherence | Entries with data by internal date ÷ total entries | Weak data owner discipline |
| Resubmission rate | Returns revised after filing ÷ returns filed | Review step is too short |
Which Mistakes Undermine an NBFC Compliance Calendar?
Four mistakes undermine an NBFC compliance calendar.
- Tracking only RBI returns. ROC and tax deadlines carry their own fees and interest.
- Making compliance the only owner. Finance, treasury and operations own the data that drives most delays.
- Not updating after rule changes. The 2025 and 2026 RBI consolidations changed references and some timelines.
- Keeping no evidence. A filed return without an acknowledgement on record is hard to prove.
Want every RBI, ROC and tax deadline owned, tracked and escalated?
Talk to Our Compliance Software Specialists
Visit Digiqt to see how custom software can turn your obligation list into a working calendar.



