LLP Form 32 — Filing Addendum for Rectification of Defects or Incompleteness
ROC Defect Notice | Addendum Response | Form SRN | MCA V3 | Deadlines

When a Limited Liability Partnership files an MCA form — whether it is Form 3 (LLP Agreement change), Form 4 (partner change), Form 8 (Statement of Accounts), Form 11 (Annual Return), or any other LLP filing — the ROC processes the submission and may find it defective or incomplete. The ROC then issues a formal defect notice by email to the LLP, specifying exactly what information or documents are missing or incorrect. To respond to this notice, the LLP must file LLP Form 32 — the "Form for Filing Addendum for Rectification of Defects or Incompleteness" — as a supplementary addendum to the original filing.

LLP Form 32 is one of the most time-sensitive compliance forms an LLP can receive a notice for. The ROC sets a specific deadline for response — typically 15 days from the date of the defect notice. If Form 32 is not filed within this period, the ROC may reject the original form or treat it as invalid in the electronic record — requiring the LLP to re-file the entire original form with fresh fees and accumulated late fees. This turns a correctable documentation issue into a significant compliance and financial setback. According to the Ministry of Corporate Affairs, the defect notice is sent by email to the last registered email address of the LLP — making it critical that the LLP's contact email on MCA records is always current.

At N D Savla & Associates, we monitor MCA V3 portal status for all LLP clients and respond immediately when a defect notice is issued on any form we have filed. For forms filed by clients independently and subsequently flagged by the ROC, we provide emergency Form 32 response services — analysing the defect notice, preparing the precise addendum response, and filing within the ROC-mandated deadline. Our LLP compliance team has successfully resolved ROC defect notices across Forms 3, 4, 5, 8, 11, and 24 — turning what could have been full re-filings into corrected approvals at no additional filing cost.

LLP Form 32 — Quick Reference Guide

An addendum for rectification is a supplementary submission that corrects or completes a previously filed MCA form that the ROC has found to be defective or incomplete. It is not a fresh filing — it is filed against the same SRN (Service Request Number) as the original form. The defect notice is issued by the ROC when:

• Missing mandatory attachment: A document that is required under the relevant LLP Rule or MCA instruction kit was not uploaded with the original form — for example, a missing consent letter (Form 6) in a Form 4 filing, or a missing LLP Agreement copy in a Form 3 filing
• Incorrect or illegible document: A required document was attached but is unclear, scanned at poor quality, in the wrong format (e.g., not in PDF), or the signature is not legible
• Data mismatch: Information entered in the form fields does not match the attached documents — e.g., the profit sharing ratio in Form 3 does not match the submitted LLP Agreement, or the DPIN in Form 4 does not match MCA records
• Missing certification: A CA or CS certification is required for the form but is absent — for example, the Statement of Accounts in Form 8 or Form 24 lacks the CA's UDIN
• Expired document: A document that must be dated within a specific window (e.g., Statement of Accounts not older than 30 days for Form 24) was submitted but has since expired
• Incomplete details: A required field was left blank or filled with generic/unclear text — e.g., the description of business activities in Form 3 is too vague for the ROC to assess compliance with naming guidelines
• Authentication missing: A foreign document that requires apostilling (for FLLP forms) was submitted without the apostille — the ROC calls for the properly authenticated version

LLP Form 32 can be filed as an addendum to any LLP e-form that is in "Pending for User Clarification" status on the MCA portal. The most common forms that generate defect notices requiring Form 32 responses include:

• Form 3 — LLP Agreement and Changes: The most commonly defected form — agreement not attached, signatures missing, or data mismatch between the form and the attached agreement
• Form 4 — Partner/Designated Partner Information Change: Missing Form 6 (partner consent), incorrect DPIN, unclear KYC documents, or Form 3 SRN not entered when required as linked form
• Form 5 — Name Change: Expired or incorrect RUN-LLP SRN, missing partner resolution, name discrepancy between form and RUN-LLP approval
• Form 8 — Statement of Account and Solvency: Statement of Accounts without UDIN, expired (older than 30 days), or CA/CS credentials incomplete
• Form 11 — Annual Return: Partner contribution details inconsistent with previous year's Form 11 or with Form 8; designated partner count discrepancy
• Form 24 — Strike Off Application: Statement of Accounts older than 30 days, indemnity bond not on stamp paper, bank closure letters from third parties not accepted (formal bank-issued letters required)
• Form 25 — FLLP Name Reservation: Home country incorporation certificate not apostilled, or authorization letter not properly executed
• Form 27 — Registration of Foreign LLP: Missing home country documents, incomplete details of partners or registered office

When an ROC defect notice is received, the LLP has two potential routes — filing Form 32 as an addendum, or abandoning the defective filing and submitting the entire form afresh. Understanding which route is appropriate prevents unnecessary cost:

• The ROC has already rejected the original form (not merely raised a defect notice) — a rejected form cannot be corrected via Form 32
• The original form was filed with fundamentally incorrect data that cannot be corrected by adding documents — for example, wrong LLPIN or an incorrect financial year entered in Form 8
• The Form 32 response itself was not filed within the deadline — after which the ROC treats the original form as invalid
• The LLP's annual filings are overdue for multiple years and the CCFS 2026 scheme is being used to regularise them — in which case fresh filings are required anyway

Based on N D Savla & Associates' experience across hundreds of LLP filings, the following are the most frequently encountered defect categories, organised by form type:

Cross-Cutting Defects That Apply to Multiple LLP Forms

• DSC mismatch: The Digital Signature Certificate affixed to the form does not match the DPIN, DIN, or PAN registered on the MCA V3 portal for that designated partner. The ROC flags this as a signing authority defect. Resolution: Use the DSC that is correctly linked to the MCA V3 account, or update the DSC registration before filing a Form 32 response
• UDIN not present or invalid: For any form requiring CA or CS certification (Form 8, Form 24 Statement of Accounts, certain Form 3 certifications), the certificate must carry a valid UDIN from the ICAI or ICSI portal. An invalid or expired UDIN is one of the most common reasons for Form 8 defect notices. N D Savla & Associates generates fresh UDIN on all CA certificates as part of its Form 32 response process
• Wrong form version or legacy form: Occasionally, a form filed using an older version of the MCA form (before a regulatory update changed the form structure) is flagged as defective. The ROC may ask for the correct current version fields to be addressed via Form 32
• Email address not registered on MCA: If the LLP's MCA account has an outdated email address, the defect notice is sent there — but the LLP never receives it. By the time the defect is discovered through MCA portal status checks, the response deadline may have passed. Always keep the registered email address on MCA V3 current

The Form 32 response timeline is one of the most critical aspects of handling a defect notice correctly:

• Defect notice deadline: The ROC sets a specific response period in the defect notice — typically 15 days from the date of the notice. This deadline is non-negotiable from the MCA system's perspective
• Extension possible in limited cases: In exceptional circumstances, the ROC may grant an extension on a written request — but this is at the ROC's discretion and is not guaranteed. Do not assume an extension will be granted
• Clock starts from notice date: The 15-day clock starts from the date the defect notice is issued — not from the date it is received, opened, or acted upon. Even if the email was missed, the clock runs
• Portal status tracking: The form's status on MCA V3 changes to "Pending for User Clarification" when a defect notice is issued. Monitoring form status through the MCA portal is a critical early warning mechanism — the email notice may be the first alert, but portal monitoring provides a backup
• N D Savla response protocol: We acknowledge a defect notice within 24 hours of it being issued, analyse the defect within 48 hours, and aim to file the Form 32 response at least 3 days before the ROC deadline — allowing buffer time for document procurement, UDIN generation, and DSC signing

The documents required for Form 32 depend entirely on the specific defect or incompleteness identified by the ROC in the defect notice. Every Form 32 filing must include:

• SRN of the Original Form: The Service Request Number of the LLP form to which this addendum is being filed — this is the unique linking reference. On entering the SRN, the MCA V3 system auto-fills the form number, LLPIN, date of filing, and the specific defect text raised by the ROC
• Response to Each Specific Defect: The defect notice identifies one or more specific defects (numbered items). The Form 32 response must address each defect point explicitly. A generic response covering all defects together may not be accepted by the ROC
• Corrected or Additional Documents: Upload the specific documents requested by the ROC — a fresh CA-certified Statement of Accounts with UDIN, a corrected consent letter, an apostilled home country certificate, a revised LLP Agreement extract, or whatever the notice specifically asks for. Up to 5 attachments can be uploaded in a single Form 32 submission. If more than 5 documents are needed, additional Form 32 filings linked to the same SRN may be required
• DSC of a Designated Partner: Form 32 must be digitally signed by a designated partner of the LLP using their active DSC. This can be any designated partner — not restricted to the one who signed the original form. For Foreign LLPs, the Authorized Representative signs
• Any other information specifically requested: If the ROC has asked for a written explanation, clarification, or reconciliation statement (not just documents), this should be prepared as a signed letter and attached as one of the 5 allowed attachments

Failing to file Form 32 within the ROC-mandated response period has serious consequences for the underlying LLP form:

• Form treated as invalid: The ROC is empowered under the LLP Rules to reject the original form or treat it as invalid in the electronic record if the defect is not rectified within the allowed period
• Fresh filing required: Once a form is rejected or invalidated, it must be re-filed as a completely fresh submission — with the same government fee as the original, plus accumulated late fees from the original due date to the re-filing date. What was a documentation error that could have been corrected for free via Form 32 now becomes a significant financial penalty
• Compliance status impact: If the original form was a mandatory annual filing (Form 8 or Form 11), a rejected form counts as a non-filing — further adding to the daily late fee accumulation
• Cascading compliance issues: Some forms are prerequisites for other filings. If a defective Form 3 (LLP Agreement) is not corrected via Form 32 and is rejected, subsequent Form 4 filings or Form 8/11 filings may also be affected due to data inconsistencies in the MCA system
• Director disqualification risk: Persistent non-compliance with MCA filings — including failure to correct rejected forms — can contribute to DPIN deactivation and director disqualification for designated partners

• 2008 — LLP Act + e-filing framework: When the LLP Act 2008 was enacted and the MCA e-filing system was built for LLPs, a mechanism for correcting defective filings was needed. The initial framework relied on manual ROC communication and paper corrections — slow, inefficient, and inconsistently applied
• 2009 — LLP Rules and prescribed forms: The LLP Rules 2009 formalized the filing framework. As e-forms became mandatory, the need for a standardized digital addendum mechanism became apparent — LLPs needed a structured way to respond to ROC defect notices without having to re-file entire forms
• 2014 — Companies (Registration Offices and Fees) Rules: Rule 10 of the Companies (Registration Offices and Fees) Rules 2014 codified the defect notice and rectification procedure for company filings, establishing GNL-4 for companies. The equivalent LLP Form 32 followed the same framework for LLP-specific filings
• 2017-2021 — E-form standardisation: As the MCA e-filing portal matured, Form 32 was standardised with specific dropdown options for document types, a 5-attachment limit, and the non-STP processing designation — ensuring that all addendum responses received manual ROC review rather than auto-approval
• 2022-2023 — MCA V3 migration: Form 32 migrated to the MCA V3 portal with enhanced pre-fill functionality — the form automatically populates the LLPIN, original form details, and the exact defect text from the ROC notice when the SRN is entered. This reduced data entry errors and made the addendum more precisely targeted at the specific defect
• Present: The Form 32 addendum is a well-established and critical compliance tool for LLPs. Given the high standard of MCA form review and the strict UDIN and DSC requirements in the current regulatory environment, defect notices are increasingly common — making professional Form 32 response management a standard part of LLP compliance

Defect Notice on Form 3 — LLP Agreement Not Properly Executed

This is the most common Form 32 scenario. The ROC raises a defect on a filed Form 3 because the LLP Agreement attached is:

• Not on stamp paper of the correct value — the form is attached but the stamp paper value is insufficient for the state
• Not notarized — the agreement is executed but the notary seal is missing or unclear in the uploaded PDF
• Profit sharing ratio in the form fields does not match the ratio in the attached agreement — a data entry error in the form
• Form 32 response: Re-execute the LLP Agreement on correct stamp paper, have it notarized with a clear seal, and ensure the data in Form 32 addendum matches the agreement precisely. Upload the corrected agreement as the attachment

Defect Notice on Form 4 — Partner Consent Missing

A defect notice on a Form 4 partner change filing typically arises because:

• The incoming partner's consent letter (Form 6) was not attached — or the version attached is unsigned or undated
• The DPIN or PAN entered for the partner does not match the MCA records (a common error when the DP's DPIN was recently updated)
• Form 32 response: Re-execute Form 6 with correct date and signature. Verify the DPIN through the MCA portal and submit corrected partner details. If the DPIN is deactivated, reactivate via DIR-3 KYC before filing the Form 32 response

Defect Notice on Form 8 — UDIN Missing from CA Certificate

A defect notice on Form 8 most commonly arises because the Statement of Accounts attached does not carry a valid UDIN:

• The CA forgot to generate a UDIN before certifying the Statement of Accounts
• The UDIN was generated but has since expired (UDINs have a validity period and must be current at the time of form review)
• The Statement of Accounts itself is now older than 30 days by the time the Form 32 response is being filed — requiring a completely fresh set of accounts
• Form 32 response: Prepare a fresh Statement of Accounts (Form 8) certified by a CA with a freshly generated UDIN. Ensure the Statement is dated within 30 days of the Form 32 filing date. N D Savla & Associates prepares and certifies fresh Statements of Accounts as part of Form 32 defect responses

Defect Notice on Form 11 — Annual Return Data Inconsistency

Form 11 defect notices often arise from data inconsistencies across different filings:

• The total partner contribution disclosed in Form 11 does not match the figure in the corresponding Form 8
• The number of designated partners in Form 11 differs from MCA records (perhaps a Form 4 partner change was not processed before Form 11 was filed)
• Form 32 response: Prepare a reconciliation statement explaining the discrepancy — with supporting evidence (latest Form 4 SRN confirming partner update, cross-reference with Form 8 figures). File Form 11 addendum addressing each inconsistency with documentary support