FMF compliance
FMF compliance, without the paperwork.
The IRDAI Fraud Monitoring Framework has been mandatory since 1 April 2026. NRD keeps your incident registry current, your RFI workflow structured and your FMR-1 reports ready when your compliance team needs them.
Regulatory context: IRDAI's Fraud Monitoring Framework (FMF) is in force for all general insurers from 1 April 2026. Inadequate fraud monitoring or non-submission of FMR-1 reports can attract a default penalty of up to ₹1 crore under IRDAI Act Section 102. NRD is a compliance workflow tool — it does not make fraud determinations. Your compliance team reviews and approves every incident and every report.
RFI engine — structured across all five categories
IRDAI's framework covers five fraud categories: claimant fraud, intermediary fraud, internal fraud, vendor fraud and policy fraud. NRD structures your Requests for Information against this taxonomy from the start — so every incident is tagged to the right category, has the right evidence attached and is traceable from receipt to resolution.
The RFI engine does not flag suspicious claims automatically and call them fraud. It gives your investigators a structured workflow: what information is needed, from whom, by when, and what has been received.
Central incident registry — the single record the regulator expects
FMF requires a central fraud incident registry. NRD maintains it: every incident, its category, the evidence gathered, the outcome and the disposition — all in one place, per insurer, with an immutable audit trail.
The registry is the source of truth for FMR-1 generation. When your compliance officer opens it, every incident is in the right state, tagged correctly and ready to report. There is no manual aggregation from spreadsheets.
One-click FMR-1 — JSON and PDF, ready to submit
FMR-1 is the IRDAI standardised incident report format. NRD generates it in both JSON (for digital submission) and PDF (for board packs and records) from the incident registry data. Your compliance team reviews the draft, approves it and submits — the report is not sent automatically.
The generated report maps to the IRDAI FMR-1 schema. If the schema changes with a regulatory update, NRD updates the template — you don't rebuild a spreadsheet.
Quarterly RMC packs and annual Board packs
FMF requires fraud monitoring data to go to your Risk Management Committee every quarter and to your Board annually. NRD compiles the pack automatically from the incident registry: incident count by category, resolution rate, trend vs prior period, open RFIs pending closure.
The pack is a structured document your RMC and Board receive. Nothing needs to be assembled manually the week before the meeting.
Built for a regulated buyer
India-resident · audit-logged · isolatedData stays in India
All claimant data processed and stored in ap-south-1 (Mumbai). Consent manager, retention TTLs, 72-hour breach workflow.
DPDPA 2023CERT-In aligned
180-day log retention, 6-hour incident reporting, NTP-synced clocks, continuous monitoring.
CERT-In 2022Encrypted per-tenant
AES-256 at rest via customer-managed KMS keys. Immutable audit archive on Object-Lock (WORM).
KMS · WORMHard tenant isolation
Your claim file never touches another insurer's tenant. Lanes stay separate — enforced, not promised.
per-insurerChain of custody
Every retrieved document carries a tamper-evident, timestamped, court-ready certificate.
BSA S.63FMF questions
The IRDAI Fraud Monitoring Framework (FMF) is a mandatory regulatory requirement for all Indian general insurers, in force since 1 April 2026. It requires insurers to maintain a central fraud incident registry, report incidents in a standard format (FMR-1), and present fraud monitoring data to the Risk Management Committee quarterly and to the Board annually.
Get your FMF workflow in order.
We'll walk through your current incident reporting process and show you how NRD fits in.