Corporate Laws (Amendment) Bill, 2026

What the Corporate Laws (Amendment) Bill, 2026 Means for Your Company

Once in a while, a piece of legislation moves through Parliament that’s worth tracking even before it becomes law, because the direction it signals matters as much as the final text will. The Corporate Laws (Amendment) Bill, 2026 is one of those. Introduced in the Lok Sabha on 23 March 2026 by Finance and Corporate Affairs Minister Nirmala Sitharaman, it proposes changes across 107 clauses of the Companies Act, 2013 and the Limited Liability Partnership Act, 2008 — the most sweeping revision to India’s corporate law framework since 2020.

Where the Bill Currently Stands

It’s important to be precise about this: as things stand, the Corporate Laws (Amendment) Bill is a Bill, not an Act. Individual provisions can still change before it’s enacted, and businesses shouldn’t restructure compliance programmes around specific numbers in the current draft as though they were already law. It was referred to a Joint Parliamentary Committee for detailed, clause-by-clause examination, and that committee has already reported back — on 3 August 2026, the Joint Committee backed the Bill while recommending further decriminalisation of procedural lapses, additional compliance relief, and easier CSR norms for small businesses, alongside dropping imprisonment provisions for certain NFRA-related defaults. That’s a strong signal the Bill will move toward passage in something close to its current shape, but the final enacted version and its effective dates are still to be confirmed.

What that means practically is that this is the moment to understand the direction of travel and start preparing, not the moment to assume any particular provision is binding yet. Companies that get ahead of the Bill’s intent tend to find the eventual transition far smoother than companies that wait for the notification and then scramble.

The Decriminalisation Shift

The Bill’s central theme is converting a long list of procedural corporate law defaults from criminal offences into civil penalties. Under the current law, things like wilfully failing to furnish information about a company’s affairs, contravening prescribed rules, failing to provide information the Registrar has asked for, violating requirements around maintaining books of account, or failing to comply with a Registrar’s requisition can all carry criminal exposure — imprisonment or fine, on top of whatever commercial consequence follows. The Bill proposes replacing that criminal exposure with civil penalties for this category of procedural, non-fraudulent default, recovered through a proposed new statutory framework.

The logic behind this shift, as the Joint Committee’s report frames it, is that criminal liability was historically disproportionate to genuinely procedural lapses — a late filing or an administrative oversight shouldn’t sit on the same legal footing as deliberate fraud. Serious violations retain criminal sanctions under the Bill; what changes is the treatment of the technical, non-fraudulent defaults that make up the bulk of routine corporate law non-compliance. For directors and company secretaries who have spent years operating under the shadow of criminal exposure for essentially administrative lapses, this is a meaningful reduction in personal risk, even though the underlying obligation to comply on time doesn’t go away.

What’s Changing for Small and Mid-Sized Companies

Several provisions in the Bill are aimed squarely at reducing the compliance load on smaller businesses. The small company thresholds — already raised once by the MCA in December 2025 to ₹10 crore paid-up capital and ₹100 crore turnover — are proposed to roughly double again under the Bill, to ₹20 crore paid-up capital and ₹200 crore turnover. If that provision survives in its current form, a considerably larger share of India’s private companies would qualify for the lighter small-company compliance regime: the simplified MGT-7A annual return, fewer mandatory board meetings, and relief from certain audit requirements.

CSR obligations get similar treatment. The net profit threshold that triggers mandatory CSR spending is proposed to rise from ₹5 crore to ₹10 crore, and the Joint Committee’s recommendations go further, suggesting the government be given power to exempt eligible small companies from CSR obligations entirely. For a company sitting just above the current CSR threshold, this could mean a meaningful change in whether CSR spending is mandatory at all — worth watching closely if your company’s net profit sits in that band.

The Bill also proposes shifting certain filings, such as Form MBP-1 relating to director interests, from a routine annual filing to an event-based one — meaning it only needs to be filed when something actually changes, rather than repeated every year regardless. Alongside that, companies would gain formal permission to hold AGMs and EGMs through video conferencing or hybrid formats, though at least one physical AGM would still be required once every three years, and a fully virtual EGM could be convened on a shorter seven-day notice period rather than the standard longer window.

Tighter Rules for Larger Companies and Auditors

The relief side of the Bill isn’t the whole story — it’s paired with meaningfully tighter accountability in other areas, particularly around financial reporting and audit quality. The National Financial Reporting Authority is proposed to be restructured into a full body corporate with independent rule-making power and fee-levying authority, giving it a more powerful, quasi-judicial standing than it currently holds. Auditors of prescribed classes of companies would be required to register their ICAI credentials directly with NFRA and file periodic returns, with penalties for non-compliance or false information proposed in the range of ₹25,000 to ₹50 lakh.

Independent directors would carry a continuing obligation throughout their tenure rather than a one-time eligibility check at appointment, which raises the bar for ongoing governance diligence at the board level. Listed companies and larger corporates, in other words, should read this Bill less as a relief measure and more as a rebalancing — procedural burden goes down, but genuine governance and audit accountability goes up, particularly for the businesses regulators consider systemically significant.

What to Do While You Wait

Since the Bill isn’t law yet, the practical response for most companies is preparation rather than immediate action. It’s worth checking where your company’s current paid-up capital and turnover sit relative to both the existing and the proposed small-company thresholds, since a company that’s currently just outside the small-company bracket could find itself comfortably inside it if the doubled thresholds pass, with real implications for how much board and filing overhead is actually required going forward.

If your company’s CSR obligations sit close to the current ₹5 crore net profit threshold, it’s worth modelling what changes if that threshold moves to ₹10 crore, since CSR budgeting decisions made months in advance are harder to unwind than ones made with the pending change already factored in. And if your company works with auditors who fall under NFRA’s expanding jurisdiction, a conversation about their registration readiness now avoids a scramble once the requirement actually takes effect.

None of this requires overhauling a compliance programme today. It requires knowing which of your current obligations are likely to loosen, which are likely to tighten, and making sure whoever manages your company’s compliance calendar is tracking this Bill’s progress through Parliament rather than being caught off guard by an enactment date that, by the time it arrives, will have been visible from a long way off.

DPDP Act Compliance

DPDP Act . India, compliance guidelines.

What Every Business Handling Customer Data, Must Do Now

Most businesses that collect a customer’s phone number, email address, or payment detail assume data privacy law is something that applies to tech giants and hospitals, not to them. India’s Digital Personal Data Protection Act changes that assumption completely. If your business processes the digital personal data of anyone in India — a customer database, an employee HR system, a marketing list, a delivery app’s location logs — you are a data fiduciary under this law, regardless of your size, sector, or turnover.

Where the Rollout Actually Stands

The DPDP Act itself was passed back in 2023, but a law without implementing rules is largely aspirational, and it’s the rules that turn broad principles into obligations a business can actually be held to. The Digital Personal Data Protection Rules, 2025 were notified on 13 November 2025, and they set out a phased rollout rather than a single switch-on date — which matters, because it means different obligations become enforceable at different times, and treating the whole thing as one distant deadline is a common and costly mistake.

The first phase took effect immediately on notification: the Data Protection Board of India, the body that will handle complaints and enforcement, began being constituted, and digital filing of proceedings started. If your business hasn’t started thinking about DPDP compliance at all, this is the phase you’re already behind on, though the practical consequences of that lag haven’t landed yet.

The second phase lands on 13 or 14 November 2026 (sources differ by a day depending on how the twelve-month period from notification is counted), when the Consent Manager framework under Rule 4 becomes operational. Consent Managers are registered intermediaries — companies incorporated in India with a minimum net worth of ₹2 crore — that give individuals a single interoperable dashboard to grant, review, and withdraw consent across different businesses that hold their data, without the Consent Manager itself being able to read the underlying information. Businesses that rely on third-party consent infrastructure, or whose customer base will expect to manage consent through these platforms, need their systems ready to integrate by this date, not starting the integration after it.

The third and largest phase arrives on 13 May 2027, when the remaining substantive obligations become enforceable all at once, with no indication of a further grace period. This is the phase that actually governs day-to-day operations for most businesses: notice and consent standards, reasonable security safeguards, breach notification timelines, data retention and erasure limits, data principal rights fulfilment, and — for businesses designated as Significant Data Fiduciaries based on the volume, sensitivity, or systemic risk of the data they handle — a heavier set of additional obligations again.

What “Full Compliance” Actually Requires

Stripped of the regulatory language, the DPDP framework asks a business to be able to answer a handful of concrete questions about the personal data it holds, and to have systems in place that make those answers true rather than aspirational.

Can you show, for every piece of personal data you hold, that you collected it with a clear, purpose-specific notice the individual actually understood — in English or any of the 22 Indian scheduled languages, not just the language your business defaults to? Can an individual withdraw consent as easily as they gave it, and does that withdrawal actually stop the downstream uses of their data rather than just switching off a flag somewhere in a database nobody checks? If a breach happens, does your business have a tested process for notifying the Data Protection Board and every affected individual promptly, followed by a detailed report within the required timeline — or would that process be improvised for the first time during an actual crisis? Is personal data deleted once its stated purpose is fulfilled, or does it sit indefinitely in a system that was never built with a retention limit in mind?

These aren’t abstract governance ideals. They’re the specific, auditable requirements the Rules translate the Act into, and a business that can’t answer them concretely today has real work to do before 2027, not a compliance box that can be ticked in a weekend once the deadline gets closer.

Why the Penalty Structure Changes the Calculation

Non-compliance penalties under the DPDP Act can reach ₹250 crore per violation. That figure alone should reframe how this gets prioritised internally — this isn’t a fine on the scale of a delayed regulatory filing that a business can reasonably absorb and move on from. It’s structured to be proportionate to genuinely large organisations and genuinely serious lapses, but the ceiling itself signals how seriously the framework is meant to be taken, and smaller businesses shouldn’t assume the number doesn’t apply to them simply because it sounds disproportionate to their size — the Act doesn’t carve out a separate, gentler penalty scale for smaller data fiduciaries.

Beyond the direct financial exposure, there’s a commercial dimension that’s easy to underweight. Enterprise buyers, particularly in regulated sectors like banking, healthcare, and financial services, are increasingly building DPDP readiness into their vendor due diligence — asking suppliers and partners to demonstrate their own compliance posture before signing a contract. A business that can show a genuine data governance programme closes those deals faster than one that can only offer assurances. Treated well, DPDP compliance becomes a competitive differentiator rather than purely a defensive cost.

Building Toward Compliance Without Panicking

The businesses that will struggle most with the 2027 deadline are the ones that wait until late 2026 to start, because the underlying work isn’t something that compresses well into a short window. It starts with a data inventory — a genuine mapping of what personal data the business actually collects, where it’s stored, who has access to it, and which third parties it gets shared with, since most businesses discover during this exercise that they’re holding more personal data, in more scattered places, than anyone realised.

From there, the priority is building consent architecture that’s granular and purpose-specific rather than a single blanket checkbox, and making sure vendor contracts with any data processor acting on the business’s behalf include the security and accountability clauses the Rules require — a legal workstream that typically takes longer than the technical one, because renegotiating existing vendor agreements takes time businesses often underestimate. Security safeguards — encryption, access controls, logging, monitoring, and backups — need to extend not just to the business’s own systems but to every processor handling data on its behalf.

Where the volume or sensitivity of data justifies it, appointing a Data Protection Officer, whether hired in-house or engaged through outsourced privacy counsel, gives the compliance programme an actual owner rather than leaving it distributed across departments that each assume someone else is responsible. And because this is a live regulatory area rather than a settled one — the Consent Manager ecosystem is still being built out, and enforcement posture will likely sharpen as the Data Protection Board matures — DPDP compliance isn’t a project with a defined end date so much as an ongoing governance function that needs periodic review as the framework itself continues to develop.

The businesses treating 2026 as the year to build this properly, rather than the year to start worrying about it, are the ones that will find May 2027 uneventful. Everyone else will find it expensive.

Why is Legal Compliance important?

Why Is Legal Compliance Important?

Ask most business owners why they haven’t got around to sorting out their statutory filings, labour registrations, or sector-specific licenses, and you’ll hear some version of the same answer: there was no time, no one person whose job it was, and nothing bad had happened yet.

That last part is the trap.

Compliance Risk Doesn’t Behave Like Other Business Risks

Compliance is one of the few areas of running a business where the absence of a visible problem isn’t evidence that things are fine. It’s often evidence that the problem hasn’t been noticed yet — by the company, or by the regulator who will eventually notice it for them.

A factory that has skipped its pollution control renewal isn’t safer than one that hasn’t, simply because no inspector has turned up this quarter. A company that’s been late filing its annual returns isn’t in good standing merely because nobody has flagged it. The moment someone does — a lender doing due diligence, an acquirer’s legal team, a former employee’s lawyer — the lapse becomes retroactively expensive, sometimes sharply so.

Most business risks announce themselves gradually, through declining sales or rising costs. Compliance risk sits dormant, accumulates quietly, and surfaces all at once — usually during a fundraise, a merger, a leadership change, or a dispute with someone who has every incentive to go looking for exactly this kind of vulnerability.

Growth is what widens the gap. Crossing a certain headcount triggers labour law obligations that didn’t apply before. Opening in a new state adds an entirely separate set of registrations. Taking on institutional funding brings new governance and disclosure requirements. Each milestone gets celebrated; almost none get flagged as a compliance event. By the time anyone looks properly, the list has grown long enough that fixing it feels less like a task and more like an excavation — which is exactly why it keeps getting pushed to next quarter.

The Financial and Legal Risks

The consequences of letting that gap persist are rarely limited to a single fine that gets paid and forgotten.

Regulatory penalties across company law, tax, labour, and environmental statutes are generally structured to compound. A delay in filing typically attracts a per-day penalty that keeps accruing until the filing is made — so a lapse that would have cost a modest amount in month one can cost many multiples of that by month twelve, purely through accumulation.

Some defaults carry consequences that reach past the company’s bank account. Directors can face personal liability for certain categories of default under the Companies Act — meaning the very protection incorporation is meant to offer can be pierced in exactly the situation a business is least prepared for.

Licenses the business depends on to operate — a factory license, a trade license, a sector-specific approval — can be suspended or cancelled for non-compliance. That’s not a fine to absorb; it’s a halt to revenue while the matter is resolved, while a competitor who kept its house in order keeps trading.

Tax authorities carry powers beyond a standard penalty notice: interest that runs from the original due date rather than the date of discovery, and in cases involving deliberate evasion rather than delay, criminal proceedings become a live possibility.

There’s litigation exposure from the counterparty side too. A contract signed by someone without proper authority, because governance records weren’t maintained, can be challenged. An employee dismissed without following correct statutory process can bring a claim that costs far more than compliance ever would have. A lender who discovers a lapsed registration during due diligence can use it as leverage — or walk away — because it signals that other things might be similarly loose.

None of this requires the business to have done anything deliberate. It’s usually the ordinary, unglamorous failure to keep up with obligations that were never hidden, just never tracked.

One lapse also tends to invite scrutiny of everything else. A GST mismatch rarely stays confined to the return in question — it typically opens a wider review of prior filings, because a discrepancy in one period raises the question of whether others exist. An inspection triggered by one missed renewal frequently expands into a full site review, once the inspector is already on the premises. Regulatory systems are built on the reasonable assumption that a business careless about one obligation is statistically more likely to be careless about adjacent ones — and that assumption tends to be borne out often enough that regulators keep acting on it.

The Reputational and Operational Damage

Financial penalties are at least quantifiable, and a business with reserves can absorb them. Reputational and operational damage is harder to price, because it doesn’t show up as a line item — it shows up as a slow erosion of the relationships the business depends on.

To a bank, an inconsistent compliance record is a standard red flag in credit screening. A company that fails that screen doesn’t just lose one loan — it can face higher rates or added collateral demands on every facility after, because the lapse becomes part of its credit history.

To an institutional investor during due diligence, a pattern of missed filings signals something about governance quality more broadly. If a team can’t manage a filing deadline, the reasonable inference is that they may be similarly loose about disciplines that are harder to verify from outside — and that inference can affect valuation, or kill a deal, often over a lapse whose original cost would have been a fraction of the deal’s value.

To a large client or a government tender board, many procurement processes now require proof of statutory compliance as a threshold condition. A business can be disqualified from bidding entirely, not because of anything to do with its product, but because a box on a checklist couldn’t be ticked.

To employees, a business visibly careless about its statutory obligations toward them — delayed provident fund contributions, inconsistent labour law adherence — sends a message about how it regards its obligations generally, and that affects retention in ways that are hard to trace back to the original cause but real all the same.

Then there’s the pure operational cost of a compliance crisis once it’s allowed to develop. Senior leadership time that should go toward strategy gets redirected to emergency meetings with lawyers. Staff get pulled into reconstructing years of documentation. Decisions that should take a day get delayed for weeks. A business with its compliance house in order treats these matters as routine. One that doesn’t treats every one of them as a fire.

How a Manageable Gap Becomes a Genuine Crisis

This pattern rarely happens through one dramatic failure. It happens through a slow accumulation of small, individually forgivable lapses that nobody connects — until an outside party connects them first.

In the first year or two, compliance is genuinely manageable, because the obligation list is short enough for a founder or a single hire to track. Then the business grows, and growth is where the gap opens, because growth changes the obligation list faster than most internal teams notice.

A new headcount threshold triggers labour law applicability that didn’t exist before. A second state adds a separate set of registrations, on top of the existing ones, not instead of them. Institutional funding adds governance obligations a founder-run company never had to think about. Each trigger arrives quietly, embedded in a milestone that gets celebrated rather than flagged.

A year or two later, a second trigger gets missed, then a third — and the business now has a genuine backlog rather than a single oversight. Backlogs are different in kind from single lapses, because fixing them means reconstructing a compliance history, not just making one overdue filing.

This is usually the point at which the gap surfaces — almost never discovered internally. It comes up during due diligence for a funding round, a bank’s credit review, a tax assessment that looks back several years, or a dispute where a lawyer starts asking pointed questions about governance. What could have been a routine filing at modest cost is now a matter requiring specialist support to untangle, under time pressure, because an external deadline forced the discovery.

The businesses that end up in real difficulty are rarely ones that set out to ignore the law. Almost without exception, they’re businesses that grew faster than their internal administrative capacity — where nobody was specifically responsible for noticing that obligations had grown alongside the business.

Building a Compliance Function That Actually Works

None of this is an argument for treating compliance as a cost to be minimised or endured. It’s an argument for treating it as an ongoing operational function — the way a business treats accounting or payroll — rather than an occasional emergency project.

The starting point is a proper compliance mapping exercise: not a generic checklist, but a specific, current inventory of every central, state, and sector-level obligation that applies to the business as it actually operates today. That map has to stay a living document, revisited whenever the business crosses a meaningful threshold — a new state, a new headcount band, a new funding round, a new product line under different sector regulation.

Once obligations are mapped, the next piece is a tracked calendar with clear ownership — every filing and renewal assigned a deadline, a responsible person, and a review process that catches a miss within days rather than letting it compound silently for months. This is where outside support tends to earn its keep, not because internal teams are incapable, but because compliance tracking needs a kind of specialised, unglamorous consistency that teams focused on running the business don’t naturally prioritise.

A periodic compliance audit, run by someone outside day-to-day operations, does for compliance what a financial audit does for accounts — it catches the gaps that people close to their own processes are structurally likely to miss.

Training matters more than businesses tend to credit. Most compliance risk in practice comes down to whoever is doing the filing actually understanding what they’re filing and why, rather than repeating a process learned once and never updated as the law changes.

And when a statutory notice does arrive — even well-run businesses occasionally get one — how it’s handled matters enormously. A notice addressed quickly, with proper documentation and a considered response, tends to close with minimal consequence. The same notice ignored, or handled reactively, tends to escalate into something far more serious than the original observation warranted.

The Business Case, Beyond Risk Avoidance

There’s a version of this argument that treats compliance purely as insurance — a cost paid to avoid a downside. That framing understates the case for it.

A business with its compliance function properly built out moves faster through every situation where compliance status actually matters. A funding round closes without a due diligence delay caused by scrambling for missing filings. A tender gets entered without a last-minute panic over an expired license. A bank facility gets approved at a better rate because the credit review found nothing to flag. Leadership spends its time on the next stage of growth, not on reconstructing paperwork under pressure.

Speed and cost of capital are competitive advantages in their own right, and a well-maintained compliance record is one of the more reliable, if unglamorous, ways of earning both.

Set against that, the ongoing cost of a properly run compliance function — built internally or maintained through an outsourced arrangement with clear ownership and a tracked calendar — looks less like an expense and more like one of the more straightforwardly justifiable line items a business carries. Its absence is what tends to produce the largest, least predictable costs a business will ever face.