Insurer Complaint Management System vs Bima Bharosa: How Integrated Grievance Tracking Works
By Ravi Sisodia · Reviewed by CA Divyanshu Sengar · Updated 5 October 2026
2-minute summary
- Bima Bharosa is designed as an integrated grievance repository: a complaint lodged there flows into the insurer’s system as well as the IRDAI repository.
- The practical objective is one reconciled grievance record, not parallel insurer and regulator spreadsheets with different issue descriptions.
- Insurer status updates are intended to mirror into Bima Bharosa, so discrepancies should be captured and raised rather than papered over.
Current position
Control and evidence map
| # | Control / evidence requirement | |
|---|---|---|
| 1 | Use a single complaint taxonomy and amount/fact statement across insurer CMS and Bima Bharosa. | |
| 2 | Map insurer complaint ID to the IRDAI token in the internal tracker. | |
| 3 | Reconcile status, last action date and next owner between the two systems. | |
| 4 | Attach the same core evidence set and record any additional document supplied later. | |
| 5 | At closure, retain the final insurer resolution and the Bima closure/escalation record together. | |
Worked example
The insurer CMS marks a grievance “resolved” on Friday while Bima Bharosa remains Pending. The policyholder should preserve both status captures and ask for reconciliation, especially if the supposed resolution was not actually communicated or does not answer the complaint.
Common mistakes
- Treating the two systems as unrelated complaints with different narratives.
- Changing the claimed amount or issue description midstream without explanation.
- Assuming a back-end status automatically proves the customer received the decision.
- Closing the internal tracker before archiving the final response.
Frequently asked questions
Does Bima Bharosa send the complaint to the insurer?
IRDAI says the complaint flows to the insurer system and IRDAI repository.
Can the customer track it?
Yes, after registration the portal provides status tracking using the registered credentials/token.
Why reconcile two IDs?
Because the insurer reference and IRDAI token may both be needed to prove the same grievance lifecycle.
What if statuses conflict?
Capture the discrepancy and ask the insurer/IRDAI channel to reconcile the record.
Official sources
- Insurance Regulatory and Development Authority of India - Bima Bharosa (IGMS) complaint portal (Current portal; current)
- Insurance Regulatory and Development Authority of India - Bima Bharosa Frequently Asked Questions (Current portal FAQ; current)
- Insurance Regulatory and Development Authority of India - Bima Bharosa grievance call-centre and process guidance (Current portal guidance; current)
- Insurance Regulatory and Development Authority of India - Master Circular on Protection of Policyholders Interests, 2024 (IRDAI/PP&GR/CIR/MISC/117/9/2024; 2024-09-05)
Disclaimer
Educational and professional reference only; confirm the current law, rates and the facts of your case before relying on this page.