IRDAI Risk-Based Capital Framework: What Partners Should Track

The IRDAI risk based capital framework development does not create new capital or distribution requirements for insurance partners today. As of November 11, 2026, IRDAI has formed working groups to develop proposals for aligning a future risk-based capital, or RBC, regime with Indian Accounting Standards, or Ind AS. The immediate task for lenders, brokers, fintechs and embedded-insurance platforms is not to rewrite live programmes. It is to understand where product economics, insurer capacity, data and governance depend on assumptions that may later change. Business Standard reported on November 10, 2026 that the groups have one month to prepare an exposure draft and an approach paper.

What the IRDAI risk based capital framework panels are examining

Risk-based capital links an insurer’s required capital more closely to the types and levels of risk on its balance sheet. This differs from a mainly factor-based approach, where prescribed factors are applied to measures such as reserves, sums at risk, premiums or claims. The current Indian solvency framework remains factor-based, while the proposed model is intended to examine risks through an economic or market-consistent balance-sheet approach, according to the November 10 report on the working groups.

IRDAI has constituted separate groups for life and non-life insurance. Their reported mandate covers:

• valuation of assets and insurance liabilities;
• the calculation of available and required capital;
• risk modules, calibration and stress factors;
• aggregation of risks and recognition of diversification benefits;
• treatment of reinsurance contracts;
• debt securities and expected credit losses;
• insurance acquisition cash flows;
• property valuation;
• discount rates, yield curves and illiquidity premiums;
• the relationship between the RBC risk margin and the Ind AS risk adjustment; and
• templates for reconciling Ind AS financial statements with RBC calculations.

These are technical design questions. The groups are also expected to assess where common methods should apply across the insurance industry and where insurers might have choices within defined limits. The reported mandate requires recommendations to be supported by data, impact assessment and sensitivity testing, rather than relying only on conceptual alignment between the two frameworks. Business Standard’s account of the panel scope also says the prudential purpose of RBC and the financial-reporting purpose of Ind AS are not to be diluted through convergence.

The direct answer: what changes for insurance partners today

For insurers: Ind AS is already a live regulatory development, but the new RBC working-group exercise is still preparatory. It does not itself replace the existing solvency calculation or establish a new capital threshold.

For brokers and corporate distribution businesses: The panel announcement does not amend distribution permissions, remuneration arrangements, customer disclosures or servicing duties. Existing regulations, insurer agreements and product-specific controls continue to apply unless they are separately amended.

For lenders and fintechs: The announcement does not impose an insurer-style RBC calculation on a lender or platform. Its relevance is indirect. A lending-linked programme may depend on an insurer’s willingness to support a product, risk segment, tenure, benefit structure or volume commitment.

For embedded and affinity platforms: No immediate API, consent, enrolment or claims-process change follows from the announcement. Partners should continue operating live embedded and affinity insurance programmes against current product documents, commercial agreements and applicable regulatory requirements.

The distinction matters because an exposure draft, an approach paper and a final regulation are different stages. The November 10 announcement starts a technical drafting exercise. It does not tell partners what the final capital formula, calibration, transition period or implementation date will be. Partners should therefore avoid presenting any modelled RBC effect as a confirmed regulatory outcome.

Why risk-based capital could affect product design and insurer capacity

Although the proposed framework applies directly to insurers and reinsurers, its eventual commercial effects could travel through the distribution chain. Capital is one input into an insurer’s decision to launch, price, retain or expand a product. Reinsurance availability, claims experience, operating expenses, investment risk and concentration can also shape that decision.

A final RBC framework could cause insurers to examine product portfolios at a more granular level. The direction and size of any effect would depend on the final risk modules, correlations, diversification treatment, transition measures and insurer-specific balance sheet. Partners should not assume that every higher-risk product will become more expensive or that every short-tenure product will require less capital.

Instead, product and partnership teams should test where their economics are sensitive:

• Benefit structure: Compare fixed benefits, indemnity covers, deductibles, waiting periods, sub-limits and policy tenure.
• Risk concentration: Identify programmes concentrated in one geography, employer, lender portfolio, platform cohort or asset type.
• Claims volatility: Separate stable-frequency portfolios from products exposed to infrequent but severe losses.
• Reinsurance dependence: Record which programme terms or capacity commitments rely on a specific reinsurance arrangement.
• Guarantees and long duration: Flag features that may create long-dated or difficult-to-hedge obligations for an insurer.
• Operational cost: Capture issuance, endorsement, servicing, reconciliation and claims expenses rather than reviewing only premium and commission.
• Growth commitments: Test whether minimum volumes, exclusivity or rapid scale-up assumptions remain workable if insurer capacity changes.

This does not mean partners should redesign products now. It means they should be able to explain the economic and risk logic of each programme. A lender offering protection at loan disbursal, for example, should be able to analyse performance by loan tenure, borrower cohort, benefit design and claims experience. A mobility platform should distinguish driver accident cover from vehicle or charging-infrastructure risk rather than treating the programme as one blended portfolio.

Partners using a white-label retail insurance shelf should also separate insurer selection from interface design. A consistent customer journey can sit above multiple insurers, but commercial terms, underwriting rules, service levels and capacity remain insurer-specific.

What Ind AS convergence could mean for insurer reporting and partner governance

Ind AS convergence is not only a future proposal. The IRDAI amendment regulations notified on March 30, 2026 took effect on April 1, 2026 and apply to life, general, health and reinsurance companies. They require applicable insurer financial statements to conform to Ind AS and introduce specific provisions for insurance reporting.

The same notification permits IRDAI to grant one year of forbearance to an insurer that was not ready to prepare compliant Ind AS financial statements, subject to conditions including a board-approved transition plan. Requests had to be made by April 30, 2026. An insurer receiving forbearance must submit Ind AS financial information quarterly, provide progress reports and achieve full compliance within one year. The regulations also require parallel submission of Ind AS statements and information under the earlier schedule for the first two years of implementation, unless IRDAI specifies another period. The notification also provides for independent validation during the first implementation year.

For partners, this can create reporting differences that require explanation rather than immediate action. An insurer’s accounting presentation, timing of profit recognition or reported liability movement may not map directly to the partner’s programme-level premium, claims or commission view.

Governance should therefore focus on reconciliation and ownership:

• Which insurer report is the source for premium, policy and claims figures?
• Which figures are accounting measures, regulatory capital measures or operational programme measures?
• How are acquisition costs, cancellations, refunds and endorsements represented?
• Who explains material differences between partner dashboards, insurer bordereaux and financial reports?
• What data history is retained when a methodology or reporting field changes?

The proposed IRDAI Ind AS convergence with RBC is intended to reduce avoidable duplication while preserving the different purposes of financial reporting and prudential capital. A partner should not expect one number to serve every operational, accounting and capital-management need.

A partner checklist for embedded, affinity and lender-linked insurance programmes

1. Build product-level economics

Maintain a product and cohort view covering premium, taxes, insurer and distributor economics, claims, cancellations, refunds, servicing cost and technology cost. Document whether figures are booked, collected, issued, earned or reconciled. Do not combine these stages into a single sales number.

2. Map insurer dependencies

Record the insurer responsible for each product, along with underwriting appetite, capacity, approval dependencies, reinsurance dependencies, service levels and renewal dates. Identify where one insurer supports a large share of a programme or a critical customer journey.

3. Prepare alternatives without assuming migration

Maintain an orderly process for evaluating another insurer or product configuration if capacity changes. This should cover data mapping, policy wording comparison, customer communication, consent, servicing, claims continuity and treatment of existing policyholders. It should not assume that live policies can simply be moved.

4. Improve data lineage

Track where every critical field originates, who can change it and which system holds the final record. Relevant fields can include eligibility, age, asset value, loan balance, tenure, sum insured, premium, tax, nominee details, issuance status and claims status.

Partners can use insurance API infrastructure to structure member templates, validation, policy status and endorsement records. Technology should preserve an auditable trail rather than only passing data between screens.

5. Reconcile failed and partial events

An embedded journey can produce mismatches when payment succeeds but issuance fails, a member record is rejected, an endorsement remains pending or a cancellation is not reflected across systems. Maintain queues, owners and escalation timelines for each exception type.

6. Review contracts and change control

Check which party owns product configuration, customer wording, premium collection, issuance, servicing, complaint handling, claims assistance, reporting and regulatory change implementation. Define how notice periods and technology changes work if an insurer revises its requirements.

7. Keep governance evidence

Retain product approvals, meeting decisions, model assumptions, version histories, reconciliation records, incident logs and insurer communications. Evidence should show why a decision was made and who approved it, not merely the final configuration.

Questions to ask insurer and technology partners before the framework evolves

Questions for insurers

1. Which product lines or programme features are most sensitive to your internal capital and risk-appetite reviews?
2. How do you assess geographic, channel, lender, employer or platform concentration?
3. Which products depend materially on reinsurance capacity or renewal?
4. What programme-level data would you need for an RBC impact assessment?
5. How would you communicate a change in capacity, underwriting appetite or product terms?
6. What reporting differences should partners expect during the Ind AS transition?
7. Who owns reconciliation between accounting, actuarial, solvency and operational data?
8. What transition support would be available if a product configuration needed to change?

Questions for technology and servicing partners

1. Can data be exported by product, insurer, cohort, geography, tenure and risk type?
2. Does the system retain field-level history and approval records?
3. Can a product configuration be versioned without changing existing policy records?
4. Are insurer-specific rules separated from the customer-facing journey?
5. How are failed issuance, endorsement and cancellation events reconciled?
6. Can claims and servicing performance be analysed by insurer and product version?
7. What controls apply when a new insurer, field or validation rule is introduced?
8. Can the platform distinguish operational reporting from insurer financial or regulatory reporting?

FAQ: Does IRDAI’s risk-based capital work change current insurance distribution rules?

Does the working-group announcement change distribution rules?

No. The announcement concerns the preparation of proposed insurer capital regulations and an approach paper. It does not itself amend distribution rules, commercial agreements or customer journeys. The Department of Financial Services’ insurance regulation collection continues to list the notified regulations governing areas such as actuarial and finance functions, expenses including commission, products and policyholder protection.

Does it create a new capital requirement for brokers, lenders or platforms?

Not through this announcement. The reported panel mandate concerns capital calculations for insurers and reinsurers. Other partners should monitor indirect dependencies, but should not describe the proposed insurer framework as a capital requirement that already applies to their own balance sheets.

Has Ind AS already taken effect for insurers?

Yes. The March 30, 2026 amendment regulations took effect on April 1, 2026, subject to their transition and forbearance provisions. The new RBC groups are examining how a proposed prudential-capital framework can use or reconcile with that accounting base.

Should a partner pause a product launch?

The working-group announcement alone is not a reason to pause a launch. A partner should assess the product against current approvals, agreements, distribution requirements, data controls and insurer capacity. Where a programme has unusual risk concentration or a long implementation cycle, the contract and system design can include proportionate change-control provisions.

The practical response is readiness, not prediction. Partners that can explain programme economics, trace data, compare insurer dependencies and govern configuration changes will be better placed to respond when IRDAI publishes a draft or final framework.

Book a demo to discuss how BharatSure can help structure a flexible, white-label insurance programme with the product, servicing and claims workflows needed as insurer requirements evolve.