MCA compliance calendar for a grant-funded health-tech startup’s milestones

A health-tech startup that wins a government grant inherits two clocks running at the same time. One is the Registrar of Companies (ROC) year, built around incorporation date, AGM date and financial year end. The other is the grant’s own milestone calendar, built around proof-of-concept demos, utilisation certificates and tranche release dates. Most compliance calendars are written for the first clock and ignore the second, which is exactly why grant disbursements stall on a director’s deactivated DIN or a company still sitting on an unfiled INC-20A. Building one calendar that reads both clocks together is not a paperwork exercise, it is what keeps the next tranche moving. This article sets out how a grant-funded health-tech startup builds that calendar around INC-20A, DIR-3 KYC and AOC-4/MGT-7A, and where the grant’s own reporting cycle forces dates to move earlier than the statutory minimum.

Which single MCA filing most often delays a grant tranche?

A deactivated Director Identification Number (DIN) does the most damage, because it blocks the director’s Digital Signature Certificate (DSC) from authenticating any MCA e-form, including the board resolution that authorises signing the utilisation certificate the grant agency is waiting for. Under the Companies (Appointment and Qualification of Directors) Amendment Rules, 2025 (G.S.R. 943(E), effective 31 March 2026), DIR-3 KYC has moved from an annual to a triennial filing, which reduces the frequency of this risk but raises the cost of missing it, since three years of drift can pass before anyone checks.

Why a grant-funded startup runs two compliance clocks

A grant agreement and the Companies Act, 2013 are event driven in different directions. The Registrar of Companies (ROC) calendar is anchored to the company’s financial year (1 April to 31 March) and its Annual General Meeting (AGM) date. A grant agreement is anchored to the project’s technical milestones, whatever calendar month they land in. A BIRAC Biotechnology Ignition Grant (BIG), for instance, releases funds in three to four milestone-based instalments over an 18-month project period that has nothing to do with the company’s financial year end (BIRAC BIG Scheme Guidelines). A Startup India Seed Fund Scheme (SISFS) grant releases in two to three tranches tied to prototype and revenue milestones, each requiring a fresh utilisation certificate before the next tranche moves.

A health-tech AI startup has a third variant of this problem through the IndiaAI Mission. Under the IndiaAI-NCG Cancer AI & Technology Challenge (CATCH), a joint programme with the National Cancer Grid, selected AI health solutions receive up to ₹50 lakh in milestone-linked tranches for development, validation and pilot deployment, with a further ₹1 crore available for scaling based on performance (IndiaAI Mission, Lok Sabha reply, 1 April 2026). CATCH adds a fourth precondition on top of the usual grant checks: every approved project must submit a study protocol to the Institutional Ethics Committee (IEC) of the participating clinical institution, and IEC clearance has to be in hand before the grant award letter is issued and before any fund is released. A calendar for this kind of grant needs an IEC clearance milestone sitting alongside the ROC dates, because a delay there holds up the tranche exactly the way a deactivated DIN does.

The two calendars do not compete for attention on their own. They collide at four specific points:

• The grant agency’s due diligence check before signing, which usually asks for an “active” ROC status, meaning no filings pending beyond their due date
• Every tranche release, which typically requires a board resolution authenticated by a DSC tied to an active DIN
• The utilisation certificate for each tranche, which a chartered accountant will not certify cleanly if the statutory books are not current, because the UC format asks for a reconciliation against the company’s own audited accounts
• For health-tech grants with a clinical validation component, an ethics or regulatory clearance milestone that sits entirely outside the Companies Act but still blocks disbursement if missed

A calendar built only around 30 September (AGM), 30 October (AOC-4) and 29 November (MGT-7A) misses all four of these collision points, because none of them are ROC due dates. They are grant due dates that borrow ROC compliance, and sometimes a clinical or regulatory clearance, as a precondition.

The three MCA filings every grant-funded health-tech startup must track

Three filings under the Companies Act, 2013 form the backbone of the ROC clock for a young private limited company. Each has a different trigger, and each has a different failure mode when a grant tranche is in flight.

Table 1: Core MCA filings for a grant-funded private limited company

Two details matter more for a grant-funded startup than for an ordinary early-stage company. First, MGT-7A applies only if the company qualifies as a “small company” under Section 2(85), meaning paid-up capital up to ₹4 crore and turnover up to ₹40 crore. A health-tech startup that has drawn down its full grant and stacked it with a seed round can cross this threshold mid-year without noticing, and default to the full MGT-7 form, which needs Company Secretary certification once paid-up capital hits ₹10 crore or turnover hits ₹50 crore. Second, the 2025 amendment to DIR-3 KYC changed the failure window, not the failure. A director who has already completed KYC has their next filing due only by 30 June 2028, but a director who has never filed, or whose DIN was allotted just before the transition, still needs to close that gap by 30 June 2026 under the transitional provision, before the triennial cycle starts running for them. Third, treat the AOC-4 and MGT-7A dates in Table 1 as the statutory default, not a guarantee. MCA extended the FY 2024-25 AOC-4 and MGT-7/MGT-7A window twice by circular, first to 31 December 2025 and then to 31 January 2026, so a calendar built on the statutory date alone can miss a live extension that applies that year. Check MCA’s current circulars before locking a UC or board resolution to a specific AOC-4 or MGT-7A date.

Does a pending INC-20A affect DPIIT recognition or grant eligibility?

DPIIT startup recognition itself does not require INC-20A to be filed, since recognition checks incorporation status through the Certificate of Incorporation and CIN, not commencement of business. The practical block appears later: most grant agencies and incubators run an MCA “company master data” check before releasing a tranche, and a company still showing “commencement of business pending” past 180 days signals exactly the kind of compliance drift that a due diligence reviewer is trained to flag before disbursing public money.

Why grant milestones and ROC deadlines collide instead of aligning

Consider a health-tech AI startup incorporated in June, financial year ending 31 March, that signs a BIRAC BIG agreement in October with the first milestone (functional prototype) due the following March. The ROC calendar says INC-20A is due in December (180 days from June), AGM by the following September, AOC-4 in October, MGT-7A in November. The grant calendar says a utilisation certificate is due within 30 days of the March milestone review, well before the company’s own AGM season starts.

If the founder tracks only the ROC dates, the UC gets prepared against unaudited numbers, because the statutory audit will not happen until after the AGM in September, six months later. If the CA preparing the UC has to certify a reconciliation against management accounts instead of audited financials, some grant agencies accept this as an interim measure; others hold the tranche until the audited AOC-4 is on public record. This is not a hypothetical timing gap. It is the default outcome of never mapping the two calendars against each other in the first place.

A second collision point is DIN status. A BIRAC BIG project running 18 months will usually span at least one, sometimes two, DIR-3 KYC cycles for its founder-directors. Under the pre-2025 annual regime this meant an automatic annual check. Under the triennial regime, a director could go the entire 18-month project without a DIR-3 KYC event at all, which sounds like less work but means the one check a founder used to do out of habit every September no longer happens by default. The calendar has to build that check in deliberately, not assume the old rhythm still applies.

What happens if a director’s DIN gets deactivated mid-tranche?

The director cannot authenticate any MCA e-form, including the board resolution the bank or grant agency needs before releasing the tranche into the no-lien account. Reactivation needs the DIR-3 KYC-Web form filed with a ₹5,000 late fee and typically clears within a few working days, but that delay lands directly on the grant’s own disbursement timeline, not just on the company’s ROC record.

Building the master calendar: mapping grant tranches to statutory trigger dates

A working calendar for a grant-funded startup treats the grant agreement as a source of compliance triggers, not just a funding schedule. Build it in four steps.

1. Pull every date from the grant sanction letter first, not the Companies Act. List each milestone review date, each utilisation certificate due date, and each no-lien account audit requirement exactly as the sanction letter states them.
2. Overlay the fixed ROC dates for the financial year in which each grant milestone falls. AGM (by 30 September), AOC-4 (30 days after AGM), MGT-7A (60 days after AGM), and the DIR-3 KYC-Web due date if this is a triennial year for any director.
3. Insert a DIN and DSC status check 45 days before every tranche milestone, regardless of whether a KYC filing is due that year. This single check catches deactivations from address or mobile number changes that trigger a 30-day event-based filing obligation under the amended rules, independent of the triennial cycle.
4. Flag every UC due date that falls before the AGM in the same financial year, since these need a management-certified interim position rather than audited financials, and should be scoped with the auditor in advance rather than discovered a week before the deadline.

Table 2: Sample master calendar for an 18-month BIRAC BIG grant (October sanction, March financial year end)

The same structure applies to an IndiaAI Mission grant such as the CATCH programme, with one addition: insert an IEC clearance checkpoint before the first tranche row, since the grant award letter and the first disbursement will not issue until that clearance is on file.

How the audit trail for grant funds interacts with your AOC-4 filing

Most grant schemes, including BIRAC BIG and SISFS, require the grant to be held in a separate, auditable, no-lien bank account, distinct from the company’s operating account (BIRAC BIG Scheme Guidelines, Version 8). This account gets its own periodic utilisation certificate, but it is not a parallel universe to the statutory audit. The company’s auditor, when signing off on AOC-4, is certifying the full set of books, and a grant received during the year sits on the balance sheet or as deferred income depending on how the scheme treats it. A mismatch between the UC figures submitted to the grant agency and the audited AOC-4 figures is one of the fastest ways to trigger a query from either side.

Startups that keep the grant ledger and the statutory books reconciled monthly, rather than only at UC time, avoid the scramble that shows up as “restated” utilisation figures in the next reporting cycle. This is also where a founder should decide early whether grant income is treated as a capital receipt, a reimbursement, or income under the specific scheme’s terms, since the accounting treatment shapes what the AOC-4 disclosure and the UC both need to say, and the two documents get compared side by side by anyone doing diligence later, including a future investor.

What grant agencies and DPIIT check before releasing the next tranche

DPIIT startup recognition itself is checked once, through Certificate of Incorporation, CIN and founder DINs at the time of application (the Startup India portal). What repeats at every tranche is a narrower, MCA-specific check: is the company’s ROC status “active”, are the required annual filings on record, and are the signing directors’ DINs valid. A BIG Partner conducting technical and financial due diligence before releasing a tranche, or an incubator reviewing an SISFS milestone, is not auditing the company’s full compliance history, but a company flagged “Active, Non-compliant” or a director shown “DIN Deactivated” on the MCA public master data search is an easy reason to hold a tranche pending clarification, and grant agencies operating on public money have limited appetite to waive that.

Table 3: What each stakeholder checks before releasing a tranche

Does the 2026 ROC reorganisation change where a grant-funded startup files?

It changes which Registrar of Companies (ROC) office holds a company’s records, not the filing obligations themselves. Under notification S.O. 6112(E), effective 16 February 2026, MCA split ROC Delhi into ROC Delhi-I and ROC Delhi-II, carved Haryana out into its own ROC, and split ROC Mumbai into ROC Mumbai-I, ROC Mumbai-II and ROC Nagpur, reallocating companies by CIN range and district. The move is automatic and needs no filing, but a grant-funded startup verifying its registered office proof for a BIRAC or IndiaAI due diligence check should confirm which ROC its CIN now falls under on the MCA master data search, since a mismatch between an old ROC name on a data room document and the current jurisdiction is exactly the kind of small inconsistency a grant agency’s finance team flags during a tranche review.

Health-tech specific triggers that layer onto the standard ROC calendar

A health-tech AI startup carries a few triggers that a generic SaaS grantee does not. If the product processes patient health data, obligations under the Digital Personal Data Protection Act, 2023 and its 2025 Rules sit alongside, not instead of, the ROC calendar, and a data breach notification timeline does not pause because an AOC-4 deadline is also due that month. If the product moves from a decision-support tool toward a Software as a Medical Device (SaMD) classification, CDSCO registration timelines run on their own clock entirely separate from the Companies Act, and a founder should confirm classification status early rather than assume an AI wellness tool stays outside CDSCO’s scope indefinitely, since that determination is fact-specific and changes as the product’s claims change. None of these substitute for MCA compliance, they stack on top of it, and a calendar that tracks only ROC dates will miss all of them.

What the CCFS-2026 window and the pending 2026 reform bill mean for this calendar

Two further 2026 developments sit outside the routine calendar but change what a founder should do if a gap is found while building one.

The Companies Compliance Facilitation Scheme, 2026 (CCFS-2026) was a one-time relief window introduced by MCA’s General Circular No. 01/2026 dated 24 February 2026, letting companies clear pending annual filings by paying the normal statutory fee plus only 10 percent of the otherwise uncapped ₹100-per-day additional fee, or exit through dormant status (Form MSC-1, half fee) or strike-off (Form STK-2, quarter fee). The window originally closed 15 July 2026 and was extended to 31 August 2026 by General Circular No. 03/2026 following a fire incident at the MCA data centre. As of this article, that window has closed. A grant-funded startup that discovers a filing gap now faces the full uncapped additional fee with no concession, which is precisely why the calendar built in this article treats prevention as the only reliable strategy rather than counting on the next relief scheme arriving in time. MCA has run comparable one-time schemes before, so a future window is plausible, but nothing should be deferred on that assumption.

Separately, the Corporate Laws (Amendment) Bill, 2026 (Bill No. 85 of 2026), introduced in the Lok Sabha on 23 March 2026, proposes amendments across 107 clauses to the Companies Act, 2013 and the LLP Act, 2008, including statutory backing for virtual AGMs (at least one physical AGM every three years), formal recognition of Restricted Stock Units and Stock Appreciation Rights, and decriminalisation of several procedural defaults. The Joint Parliamentary Committee examining the Bill tabled its report in both Houses of Parliament on 3 August 2026, recommending adoption with clause-wise modifications, and its recommendations explicitly include easing compliance requirements for One Person Companies, small companies, startups and producer companies. As of this article, the Bill has not been passed by Parliament or received presidential assent, so none of its provisions are in force. A grant-funded startup should treat the JPC’s endorsement as a signal that compliance relief for startups is likely coming, not as a relief already available, and should keep filing on the existing statutory calendar until a commencement notification is issued.

Common mistakes that cost grant-funded startups time and money

Treating the grant sanction letter as a finance document only. Founders route the sanction letter to the finance team and never share the milestone dates with whoever tracks ROC compliance. The fix is simple: the moment a sanction letter is signed, extract every date into the same calendar that tracks INC-20A, AGM and AOC-4, not a separate spreadsheet nobody else opens.

Assuming DIR-3 KYC is now “once every three years, don’t worry about it.” The 2025 amendment reduced filing frequency, not monitoring frequency. A DIN can still be deactivated mid-cycle from an unfiled event-based update (change of mobile number, email or address), and the company only finds out when a DSC fails at exactly the moment a tranche needs signing.

Filing INC-20A late because “the company hasn’t really started operating yet.” Grant-funded pre-revenue startups are the most common victims of this mistake, since the founders reasonably feel the company is still in R&D mode. The Companies Act does not care whether revenue has started; it cares whether subscription money has been received, and the 180-day clock runs regardless.

Preparing the utilisation certificate before checking whether the AOC-4 for that year is even filed. A UC that references unaudited numbers because the statutory audit is still pending invites exactly the kind of query that delays the next tranche by weeks.

Letting small company status lapse unnoticed. A grant plus a parallel seed round can push paid-up capital or turnover past the Section 2(85) thresholds mid-year, which switches the company from MGT-7A to full MGT-7 with Company Secretary certification, and founders who file MGT-7A anyway because “that’s what we filed last year” create a defective filing that needs correction.

Assuming a discovered compliance gap can always be cleared cheaply later. The CCFS-2026 window, which let companies regularise pending filings for 10 percent of the additional fee, closed on 31 August 2026. A founder who spots a gap while building this calendar and defers fixing it on the hope that a similar scheme reopens soon is choosing to pay the full uncapped ₹100-per-day fee in the meantime, with no guarantee of when, or whether, the next relief window arrives.

Treelife’s practitioner note

In the MCA compliance engagements we have run at Treelife for grant-funded health-tech startups, the pattern that recurs is not a missed statutory deadline in isolation, it is a missed statutory deadline that surfaces at the worst possible moment because nobody connected it to the grant calendar in advance. We have seen a BIRAC BIG tranche held for eleven days over a director’s DIN deactivation that traced back to an unreported mobile number change eight months earlier, filed correctly but never linked to the fact that a tranche milestone was three weeks away. Under Rule 12A of the Companies (Appointment and Qualification of Directors) Rules, 2014 as amended, that kind of event-based update carries its own 30-day filing window independent of the triennial cycle, and it is the clause most compliance calendars built before 2026 simply do not carry, because it did not need to exist under the old annual regime. Our working rule for these engagements is to run a DIN and DSC status check as a standing agenda item at every board meeting that precedes a grant milestone review, not as a reaction to a filing deadline. It costs fifteen minutes of a board meeting and it has, in more than one engagement, been the difference between a tranche releasing on schedule and a founder explaining a delay to a grant agency that has no obligation to be patient about it.

Case Study

Situation: Seed-stage health-tech AI startup based in Hyderabad, building an AI-assisted diagnostic triage tool, incorporated eight months prior and holding a BIRAC BIG grant sanctioned at ₹48 lakhs across three milestones.

Challenge: INC-20A had been filed on time, but the founder-director’s DIN had been deactivated after a residential address change went unreported. The second grant tranche, worth ₹18 lakhs, required a board resolution the director could not sign. The founder had not filed AOC-4 for the prior short financial year either, and the incubator’s finance team was asking for it before certifying the utilisation certificate.

What Treelife did: Filed the reactivation KYC form with the late fee, prepared and filed the pending AOC-4 with the abridged small company disclosures, and rebuilt the company’s calendar to map all three remaining grant milestones against ROC trigger dates for the current and following financial year.

Outcome: Tranche released nineteen days after the original due date instead of the open-ended hold the incubator had initially flagged; all subsequent milestones since have released within the grant’s own SLA window with no compliance-related delay.

FAQ’s on MCA compliance calendar for a grant-funded health-tech startup’s milestones

Q: Is grant money received from BIRAC or SISFS taxable income for the startup?
A: Government grants to DPIIT-recognised startups against specific milestones are generally not treated as taxable income when used for the granted purpose, but the treatment depends on the scheme’s structure. Confirm the specific tax position with your CA against the scheme’s sanction letter before signing, since equity-linked and reimbursement-style grants are treated differently.

Q: What does it typically cost to keep an MCA compliance calendar running for a grant-funded startup?
A: Recurring secretarial compliance for an early-stage private limited company, including AOC-4, MGT-7A and DIR-3 KYC monitoring, is usually quoted as an annual retainer rather than per-filing, since the value is in the calendar discipline, not any single form.

Q: What is the end-to-end timeline from grant sanction to first tranche release?
A: Indicative ranges run from 30 to 90 working days for central schemes and 90 to 180 days for BIRAC BIG, from application to first disbursement, with each subsequent tranche depending on milestone review and utilisation certificate turnaround rather than a fixed calendar date.

Q: What documents does a grant-funded startup need on file for an MCA compliance audit?
A: Certificate of Incorporation, MoA and AoA, board resolutions for the no-lien account and each tranche, statutory registers, audited financial statements, INC-20A and AOC-4/MGT-7A acknowledgements, and DIN/DSC status confirmations for every signing director.

Q: Does a foreign co-founder’s DIN follow the same triennial DIR-3 KYC rule?
A: Yes, Rule 12A applies to every individual holding a DIN as on 31 March of a financial year regardless of residency, though a foreign director should plan the KYC-Web filing around DSC and video verification logistics well ahead of the due date.

Q: What happens to the grant if the company’s founders restructure and DPIIT recognition lapses?
A: Most grant agreements require continued DPIIT recognition and continued incorporation status as conditions of the agreement, so a lapse triggered by a restructuring, a change in shareholding pattern, or crossing the turnover threshold should be flagged to the grant agency proactively rather than discovered at the next milestone review.

Q: Can a health-tech startup self-certify labour law compliance while running a grant?
A: DPIIT-recognised startups can self-certify compliance under specified labour and environmental laws for a defined window from recognition, independent of the grant itself, but this self-certification does not extend to MCA filings, which remain due on the statutory calendar regardless of DPIIT status.

Q: What happens if the grant tranche is delayed because of an MCA compliance gap, does the milestone deadline also move?
A: Not automatically. Most grant agreements treat the technical milestone and the disbursement as separate clocks, so a compliance-related disbursement delay does not by itself extend the project timeline, which is why founders should flag compliance gaps to the grant agency as early as possible rather than let the delay compound silently.

Q: Does a promoter director need a fresh DIN if they were previously disqualified under Section 164(2)?
A: A director disqualified for three consecutive years of AOC-4 or MGT-7 default cannot be reappointed or continue as director of any company for five years under Section 164(2)(a), and this history surfaces in DPIIT and grant agency due diligence checks, so a disqualification should be resolved before signing a new grant agreement in that director’s name.

Q: What is the DIN/DSC risk for an NRI or overseas investor sitting on the board of a grant-funded startup?
A: The same DIR-3 KYC-Web triennial obligation applies, but overseas directors face longer lead times for DSC renewal and video-based verification, so their KYC and DSC status should be checked earlier in the calendar than for resident directors, ideally 60 rather than 45 days before a tranche milestone.

Q: If the grant fails and the project is discontinued, what MCA filings are still due?
A: The company’s ROC obligations, AOC-4, MGT-7A, DIR-3 KYC and INC-20A if not already filed, continue regardless of whether the grant project succeeds, since these are filed against the company’s existence, not the grant’s outcome. A discontinued grant does not exempt the company from its statutory calendar.

Q: How does a small company crossing the Section 2(85) threshold affect an in-progress grant?
A: It does not affect the grant agreement directly, but it changes the ROC filing from MGT-7A to full MGT-7 with Company Secretary certification, so the calendar should flag paid-up capital and turnover against the ₹4 crore and ₹40 crore thresholds every quarter, not just at year end.

Q: What is the practical first step for a founder who has just signed a grant agreement and has no compliance calendar yet?
A: Extract every date in the sanction letter into a single calendar alongside the standing ROC dates for the current financial year, and run an immediate DIN and DSC status check for every signing director before the first board resolution is needed, rather than waiting for the first tranche request to surface any gaps.

Regulatory references

• Section 10A, Companies Act, 2013 and Rule 23A, Companies (Incorporation) Rules, 2014 (INC-20A)
• Rule 12A, Companies (Appointment and Qualification of Directors) Rules, 2014, as amended by the Companies (Appointment and Qualification of Directors) Amendment Rules, 2025 (G.S.R. 943(E), dated 31 December 2025, effective 31 March 2026), governing the DIR-3 KYC-Web triennial cycle
• Section 137, Companies Act, 2013 (AOC-4)
• Section 92, Companies Act, 2013 and Companies (Management and Administration) Amendment Rules, 2021 (MGT-7A)
• Section 2(85), Companies Act, 2013, on small company thresholds
• Section 164(2)(a), Companies Act, 2013, on director disqualification for three-year default
• BIRAC Biotechnology Ignition Grant (BIG) Scheme Guidelines, on milestone-based disbursement and the no-lien account requirement
• Digital Personal Data Protection Act, 2023 and Digital Personal Data Protection Rules, 2025
• MCA notification S.O. 6112(E), dated 30 December 2025, on the ROC and Regional Directorate jurisdiction reorganisation effective 16 February 2026
• MCA General Circular No. 01/2026, dated 24 February 2026, and General Circular No. 03/2026, dated 8 July 2026, on the Companies Compliance Facilitation Scheme, 2026 (window closed 31 August 2026)
• Corporate Laws (Amendment) Bill, 2026 (Bill No. 85 of 2026), Joint Parliamentary Committee report tabled 3 August 2026, not yet passed by Parliament or in force

External sources

• Ministry of Corporate Affairs
• Startup India (DPIIT)
• BIRAC
• IndiaAI Mission

About the Author

Share

• Link copied to clipboard!
  https://treelife.in/compliance/mca-compliance-calendar-for-a-grant-funded-health-tech-startups-milestones/
  
• 
• 
• 
• 

Treelife

Treelife Team | support@treelife.in

We are a legal and finance firm with a deep focus on the startup ecosystem. We offer a wide range of services, including Virtual CFO, Legal Support, Tax & Regulatory, and Global Expansion assistance.

Our goal at Treelife is to provide you with peace of mind and ease in business.