INC-22 Is Not a Magic Wand: The Hidden Compliance Trap in ROC-to-ROC Registered Office Shifts

“The form was approved.

The address changed.

The company moved on.

Until due diligence knocked on the door.”

Changing the registered office of a company is often perceived as a routine administrative formality—a task reduced to filing a form, attaching an address proof, securing system approval, and moving on. In compliance calendars and boardroom discussions alike, it is frequently treated as a clerical exercise rather than a statutory decision carrying legal consequences.

This calm, however, is deceptive.

The moment a company shifts its registered office from the jurisdiction of one Registrar of Companies (ROC) to another within the same State, the exercise ceases to be procedural and enters the realm of strict statutory scrutiny. What appears to be a minor geographical relocation can, if handled casually, evolve into a serious compliance lapse with penal exposure.

The real danger lies in the illusion of completion.

Forms are approved.

Master data is updated.

The MCA portal reflects the new address.

And yet, beneath this apparent compliance, a critical legal requirement may remain unfulfilled.

Many companies—and sometimes even professionals—fall into the trap of equating portal acceptance with statutory compliance. The MCA system, efficient as it may be, does not and cannot substitute the mandatory approvals expressly required under the Companies Act, 2013. Where the law demands prior sanction of the Regional Director, reliance on a standalone filing of e-Form INC-22 becomes not only insufficient, but misleading.

Such lapses rarely surface immediately. They remain dormant and unquestioned until the moment they matter most—during due diligence exercises, secretarial audits, fund-raising negotiations, or listing and restructuring processes. At that stage, what was once brushed aside as a minor filing detail abruptly emerges as a governance red flag, necessitating urgent explanation and corrective action.

This article uncovers one such frequently overlooked statutory trap, explains the legal position governing changes of registered office involving ROC jurisdiction under the Companies Act, 2013, and outlines the correct and practical approach to regularisation, grounded in real-world compliance experience rather than theoretical interpretation.

What follows is not merely a technical discussion, but a compliance cautionary tale—one that underscores the importance of understanding what the law requires, not merely what the portal permits

The Compliance That Looked Correct — But Wasn’t

Consider this scenario:

A private limited company originally had its registered office in Kolhapur, falling under the jurisdiction of ROC Pune. Due to business reasons, the company shifted its registered office to Navi Mumbai, which falls under ROC Mumbai.

What did the company do?

It filed e-Form INC-22.

The form was approved.
The registered office address stood updated on the MCA portal.
The ROC jurisdiction changed.

On paper — everything looked perfect.

Legally — it wasn’t.

The Law That Was Ignored

Section 12(5) of the Companies Act, 2013

The law draws a very clear line:

Where a company changes its registered office from the jurisdiction of one Registrar to another Registrar within the same State, such change shall be made only with the prior approval of the Regional Director.

This provision is supplemented by Rule 28 of the Companies (Incorporation) Rules, 2014, which mandates:

• Special Resolution of shareholders
• Application to the Regional Director in Form INC-23
• Approval order of the RD
• Filing of INC-28
• Only thereafter, filing of INC-22

INC-22 is the last step — not the only step.

Why This Mistake Happens So Often

The MCA portal allows companies to file INC-22 even when:

• RD approval is not obtained
• No Special Resolution is passed
• No INC-23 is filed

This technical acceptance creates a dangerous illusion of compliance.

Approval on the portal does not override statutory non-compliance.

Is the Change Invalid or Merely Irregular?

This is the most common question professionals ask.

The answer, based on legal and practical interpretation, is:

• The change is not void
• It is an irregular procedural non-compliance
• The defect is curable

However, the problem surfaces when:

• Due diligence is conducted
• Secretarial audit begins
• Listing or funding is contemplated

At that stage, the innocent INC-22 approval becomes a red flag.

Penal Exposure Under the Act

Non-compliance with Section 12 attracts penalty under Section 12(8):

• Company and officers in default are liable to penalty
• Penalty is calculated on a per-day basis, subject to prescribed caps

While the default is technical in nature, ignorance of procedure is not a defence.

The Right Way to Fix the Wrong

The Companies Act does provide a clean exit route — provided the company acts voluntarily and promptly.

Practical Regularisation Process

1. Board Meeting

• Take note of inadvertent non-compliance
• Approve calling of general meeting
• Authorise application to the Regional Director

2. Special Resolution

• Ratify the change of registered office from one ROC to another within the State

3. Application to Regional Director

• File Form INC-23 with detailed justification
• Attach affidavit explaining the lapse as unintentional

4. Filing of RD Order

• File Form INC-28 with both concerned ROCs

5. Rectification Filings

• Re-file or validate INC-22, if required

In many cases, where the company approaches the authorities voluntarily, lenient view is taken.

Why This Matters More Than It Appears

This issue rarely comes up during routine compliance.
It almost always emerges during high-stakes events:

• Investment due diligence
• Mergers & acquisitions
• Listing exercises
• Secretarial audits

And at that stage, fixing it becomes urgent, visible, and expensive.

Final Takeaway

INC-22 is not a shortcut.
It is not a substitute.
And it is certainly not a magic wand.

When a registered office shift involves a change in ROC jurisdiction, Regional Director approval is not optional — it is mandatory.

Timely understanding and proactive regularisation of such lapses is what separates tick-box compliance from true corporate governance.