MAS Circular ID 01/26: Avoiding Lapses in ORSA Report Submissions

An ORSA report submission to MAS under Notice 126 lapses when the report is late, incomplete or not demonstrably owned by the board, and MAS Circular ID 01/26 reminds insurers that these are supervisory concerns rather than administrative slips. The practical answer is to treat the ORSA report submission as a managed project with a fixed calendar, named owners, board sign-off built into the timetable and a final completeness check against what MAS expects. This article sets out the requirements, the usual causes of lapses and a checklist you can adopt before your next submission.

What Notice 126 Requires of the ORSA

MAS Notice 126 on Enterprise Risk Management for Insurers requires a licensed insurer to maintain an ERM framework and to conduct an Own Risk and Solvency Assessment. The ORSA is the insurer's own forward-looking evaluation of the risks it faces and the capital it needs to support its business plan, assessed against both its internal view and the regulatory requirements under the risk-based capital framework.

Three features of the ORSA requirements for a Singapore insurer matter most for submission discipline:

• The ORSA is performed at least annually, and also when a material change in the risk profile, strategy or capital position makes the last assessment stale.
• The ORSA report must be approved by the board of directors (or, for a branch, the equivalent senior governance body) before it goes to MAS.
• The assessment must be integrated into strategic planning, capital management and risk appetite, not produced as a standalone document.

Because the report is a regulatory deliverable, the date it reaches MAS is as important as its content. A strong ORSA delivered after the deadline in the Notice is still a lapse, and repeated lapses invite closer supervisory attention to the whole ERM framework.

Why MAS Is Focused on Submission Lapses

Circular ID 01/26 should be read alongside MAS supervisory commentary on weaknesses in ORSA reports, in particular incomplete coverage of non-financial risks and of group risk. Taken together, the message is that MAS reads the ORSA as evidence of how the insurer actually governs risk and capital, and that a late or thin submission suggests the process behind it is not operating as designed.

Insurers should obtain the circular from the MAS website and confirm its precise wording with their compliance function. The points below reflect the practical issues that experience of ORSA processes suggests are most likely to cause a lapse, and they should be tested against the circular itself.

Common Causes of Late or Deficient ORSA Submissions

Lapses rarely come from a single failure. They usually come from a chain of small slippages that compound as the deadline approaches.

Timetable built backwards from the wrong date

Many insurers plan to the MAS deadline rather than to the board meeting that must approve the report. If the last board or board risk committee meeting before the deadline is missed or deferred, there is no recovery path. The timetable should be built backwards from the board approval date, with the MAS deadline treated as the outer limit.

Dependence on year-end financial and capital numbers

The ORSA projections start from the latest solvency position. When valuation, reserving or capital calculations finalise late, the stress testing and projections slip with them. Agree early which balance sheet date anchors the ORSA, and run the projection machinery on a preliminary basis before final numbers arrive.

Gaps in non-financial and group risk coverage

Reports that concentrate on insurance, market and credit risk, and treat operational, conduct, technology, cyber and group or intra-group exposures lightly, attract questions from MAS. Missing coverage often surfaces in review only days before submission, forcing late rewrites.

Unclear ownership between risk, actuarial and finance

When the Chief Risk Officer, the Appointed Actuary and the finance function each assume another is coordinating, no one owns the timetable. A single accountable owner for the ORSA process, usually the CRO, with documented contributors, removes this ambiguity.

Board approval treated as a formality

A board that receives the draft a few days before the meeting cannot challenge it meaningfully, and a challenge that arrives late leads to rework. Minutes should show that directors engaged with the stress scenarios, the risk appetite linkage and the capital conclusions.

Branches and group-reliant insurers

Branch operations and subsidiaries that rely on group ORSA material need to show that the content is relevant to the Singapore licensed entity. Importing a group document without tailoring it to the local risk profile and local capital position is a frequent cause of deficiency.

What a Complete ORSA Report Should Demonstrate

A complete ORSA report gives MAS a coherent picture of how the insurer sees its own risk and capital. At a minimum, reviewers should be able to find:

• A description of the ERM framework and the governance arrangements around the ORSA, including the role of the board and senior management.
• The risk profile and risk appetite, with limits and tolerances that connect to the stress scenarios used.
• Forward-looking capital projections over the business planning horizon under base and adverse conditions, including the effect of management actions.
• An assessment of overall solvency needs that compares the insurer's own view with the regulatory capital requirements, and explains any difference.
• Coverage of non-financial risks and, where relevant, group and contagion risks.
• The conclusions the board reached and the actions it approved as a result.

The final element is where many reports are weakest. An ORSA that does not record decisions or actions suggests the exercise did not influence the business.

Pre-Submission Checklist for Compliance and Risk Teams

Use the following sequence as a working discipline for each annual cycle:

1. Fix the ORSA calendar at the start of the financial year, including the board approval date, the date the draft goes to directors, and the MAS submission deadline set by Notice 126.
2. Confirm the balance sheet date and capital figures that the projections will use, and a fallback if final numbers are delayed.
3. Assign a single accountable owner and named contributors from risk, actuarial, finance, compliance and technology.
4. Map the report against the MAS expectations, including non-financial and group risks, and record any area where coverage is deliberately limited and why.
5. Deliver the draft to the board or board risk committee with enough lead time for genuine challenge, and keep the minutes of that discussion.
6. Run a final completeness and consistency review: figures reconcile to regulatory returns, scenarios match the stated risk appetite, and conclusions are supported by the analysis.
7. Submit to MAS with margin before the deadline, and retain evidence of the submission date.
8. After submission, record lessons learned and update the next year's calendar.

When an Independent Review Helps

An independent review before submission is useful where the ORSA process is new, where the business has changed materially, where the last cycle produced supervisory feedback, or where the board wants assurance that the report would withstand scrutiny. A reviewer who has not been involved in drafting can test coverage, challenge the scenarios and check that the governance trail is complete while there is still time to correct gaps.

If your next ORSA cycle is approaching and you want to confirm that the process, the report and the board governance are ready, our team supports insurers with framework design, independent review and submission readiness. Speak to us about ORSA advisory, or see how it fits within a broader enterprise risk management programme.