Form MGT-14 is used to place specified company resolutions and agreements on the Registrar of Companies record. The common mistake is to treat it as a filing required after every Board or shareholder meeting. The safer approach is event-based: identify what was approved, then test whether that resolution or agreement falls within Section 117 of the Companies Act, 2013 and any applicable rule or exemption.
The legal starting point is Section 117 in the current consolidated Companies Act, 2013 on India Code. Section 117 requires specified resolutions or agreements, with the Section 102 explanatory statement if any, to be filed with the Registrar within 30 days. Rule 24 of the Companies (Management and Administration) Rules prescribes Form MGT-14 for this filing.
Step 1: test the resolution, not merely the meeting
A Board meeting does not automatically create an MGT-14 filing, and neither does a general meeting. Section 117(3) identifies the classes of resolutions and agreements that are registrable. Review the agenda item that was actually approved. The same meeting can contain one item that requires MGT-14 and another that does not.
Step 2: recognise the main Section 117 triggers
- Special resolutions. Section 117(3)(a) is a direct filing trigger.
- Unanimous resolutions that would otherwise require a special resolution. Unanimity does not remove the filing requirement where the resolution would otherwise need to be special.
- Managing-director appointment terms. A Board resolution or company agreement concerning appointment, re-appointment, renewal or variation of the terms of appointment of a managing director is specifically covered.
- Class resolutions and agreements. Certain resolutions or agreements binding a class of members are covered where a specified majority or particular approval method is required.
- Voluntary liquidation resolution. Section 117 includes the relevant voluntary winding-up resolution under Section 59 of the Insolvency and Bankruptcy Code, 2016.
- Section 179(3) Board resolutions. Resolutions passed under the Board powers listed in Section 179(3) are included, subject to the statutory provisos and any valid class-specific exemption applicable to the company.
Section 179(3) covers important powers such as issuing securities, borrowing money, investing company funds, granting loans or guarantees or providing security, approving financial statements and the Board's report, diversifying the business, approving amalgamation, merger or reconstruction, and taking over another company or acquiring a controlling or substantial stake.
Step 3: check exemptions before filing a Section 179(3) Board resolution
The bare Section 117 list is not always the end of the analysis. Section 462 permits the Central Government to exempt classes of companies from provisions of the Act, while Section 117 itself contains a specific ordinary-course exception for certain lending resolutions of specified regulated financial entities. Your internal checklist should therefore contain an applicability and exemption column. Do not copy another company's filing conclusion merely because its Board resolution looks similar.
Step 4: calculate the 30-day period from the correct event date
Section 117(1) requires a covered resolution or agreement to be filed within 30 days of passing or making it. For a resolution passed at an adjourned meeting, Section 116 says the resolution is treated as passed on the date it was actually passed. Create the filing task on the event date instead of waiting for the signed minutes.
Step 5: build the filing pack
The statutory core is the relevant resolution or agreement and the explanatory statement under Section 102, if any, that accompanied the meeting notice. The live MCA form may require event-specific information or attachments, so the final upload pack should be checked against the current webform before submission.
A practical internal pack should capture the final resolution text, meeting or postal-ballot date, governing section, explanatory statement where applicable, relevant agreement where the filing concerns an agreement, and a short legal note showing why MGT-14 is required or why an exemption has been relied on.
Worked example: one meeting, two different outcomes
Assume a company holds a general meeting with two items. Item 1 is an ordinary resolution on routine business. Item 2 is a special resolution to alter the articles of association. The meeting itself does not determine the filing obligation. Item 2 falls directly within Section 117(3)(a), while Item 1 must be tested under its own governing provision rather than being filed merely because it was passed at the same meeting.
For Item 2, the company should create the MGT-14 task immediately and complete the filing within 30 days. Section 117 also says that a resolution having the effect of altering the articles must thereafter be embodied in or annexed to every copy of the articles issued after the resolution.
What happens if the filing is late?
Under the current Section 117(2), the company is liable to a penalty of ₹10,000 and, for continuing failure, a further ₹100 for each day after the first, subject to a maximum of ₹2 lakh. Every officer in default, including the liquidator if any, is liable to ₹10,000 plus ₹100 for each continuing day, subject to a maximum of ₹50,000.
That is why the 30-day clock should be controlled independently of the final minutes process. A later portal filing or additional fee should not be treated as a substitute for analysing the statutory default and any resulting penalty exposure.
Practical MGT-14 checklist
- Identify the exact event. Record what the Board, members or class of members approved.
- Map the governing provision. Test Section 117(3) and any other provision that expressly requires filing.
- Check the company class. Review any Section 462 or other applicable exemption before concluding that a Board resolution must be filed.
- Fix the event date. Calculate 30 days from the actual date the resolution was passed or agreement made.
- Prepare the documents. Keep the resolution or agreement and explanatory statement if any aligned with the filing.
- Use the correct form and purpose. File MGT-14 under Rule 24 for the legal event actually approved.
- Retain the trail. Preserve the filed form, acknowledgement or challan, supporting documents and applicability note with the statutory records.
Common mistakes
- Filing every Board resolution automatically without testing Section 117 and exemptions.
- Assuming every ordinary resolution is outside filing without checking the underlying provision.
- Missing a managing-director appointment or variation resolution specifically listed in Section 117(3).
- Using an earlier meeting date when the resolution was actually passed at an adjourned meeting.
- Starting the filing exercise only after final minutes are signed and losing most of the 30-day window.
- Copying another company's MGT-14 position without checking company-specific applicability.
Practical takeaway
MGT-14 compliance works best as an event-classification control. For every material resolution, identify the governing section, test Section 117, check exemptions, calculate the 30-day deadline, assemble the resolution and explanatory statement, and preserve the filing trail. Recheck the current Companies Act text on India Code before a live filing because statutory provisions and exemption notifications can change.
