| Problem | What to compare | Correction |
|---|---|---|
| Flat/plot number differs | Form vs proof vs NOC/lease | Use the authoritative property/address record consistently. |
| Owner name differs | Ownership proof vs consent | Clarify relationship/authority with appropriate evidence. |
| Utility proof too old | Document date vs filing requirement | Obtain a current acceptable proof. |
| PIN/locality mismatch | All attachments | Correct the filing or proof discrepancy before resubmission. |
| Unreadable upload | Full PDF/image | Rescan legibly without hiding seals or reference data. |
← Full guide: Registered Office Proof Rejected: Document Checklist
Common mismatch map
For “Common mismatch map”, problem. What to compare. Correction. Flat/plot number differs. Form vs proof vs NOC/lease.
Start here
For “Common mismatch map”, problem. What to compare. Correction. Flat/plot number differs. Form vs proof vs NOC/lease. Use the authoritative property/address record consistently. Owner name differs. Ownership proof vs consent. Clarify relationship/authority with appropriate evidence. Utility proof too old. Document date vs filing requirement. Obtain a current acceptable proof. PIN/locality mismatch. All.
What applies to this exact problem
Check these first
- Flat/plot number differs: Form vs proof vs NOC/lease.
- Owner name differs: Ownership proof vs consent.
- Utility proof too old: Document date vs filing requirement.
Fix it in this order
- Flat/plot number differs: Form vs proof vs NOC/lease.
- Owner name differs: Ownership proof vs consent.
- Utility proof too old: Document date vs filing requirement.
- PIN/locality mismatch: All attachments.
- Unreadable upload: Full PDF/image.
- Use the authoritative property/address record consistently.
Evidence to keep
- MCA SRN/acknowledgement — keep it with the evidence for “Common mismatch map”.
- Identity and registered-office evidence — keep it with the evidence for “Common mismatch map”.
- Final signed forms/attachments — keep it with the evidence for “Common mismatch map”.
- Resubmission remark and correction note — keep it with the evidence for “Common mismatch map”.
Do not make it harder
- Sharing DSC credentials casually For “Common mismatch map”, that can hide whether the underlying issue is actually resolved.
- Using inconsistent spellings across forms For “Common mismatch map”, that can hide whether the underlying issue is actually resolved.
- Assuming name approval equals trademark clearance For “Common mismatch map”, that can hide whether the underlying issue is actually resolved.
How you know it is fixed
- The source record is corrected and the downstream record matches it for “Common mismatch map”.
- You have a fresh dated copy showing the corrected value for “Common mismatch map”.
If this still isn't resolved
- MCA helpdesk/ticket route State the unresolved issue explicitly: “Common mismatch map”.
- Professional correction where a filing/legal interpretation is involved State the unresolved issue explicitly: “Common mismatch map”.
- Cybercrime/police route for impersonation or payment scams State the unresolved issue explicitly: “Common mismatch map”.
Parent-guide references
These references support the parent guide and escalation context. Verify provider-, model-, policy-, or jurisdiction-specific details before an irreversible step.
Need the complete context?
This page solves one branch. The parent guide covers the full decision, edge cases, alternatives, and related checks.