It’s the overlap of three frameworks at once: updated IFRS rules, evolving AAOIFI standards, and tighter CBUAE supervision. None fully replaces the others, so CFOs must express one financial reality through multiple reporting lenses at the same time.

The law strengthens the regulatory perimeter and expects clearer accountability for Shari’ah-aligned activities. It doesn’t redefine Shari’ah governance, but it elevates expectations around oversight, documentation and financial reporting discipline.

CFOs will need tighter audit trails, clearer segregation of Shari’ah-sensitive transactions, and more coordinated workflows between Finance, Risk and SCF teams. The mandate essentially formalises practices that were already becoming necessary.

IFRS 18 introduces a standardised “operating profit” subtotal and highlights management-defined performance measures, making Islamic banks’ core earnings more visible. Because it also brings finance costs and profit-sharing effects into focus, CFOs need to prepare early.

These contracts don’t always behave like conventional interest-based instruments, so mapping their returns into IFRS 18’s subtotals requires judgement. The challenge is aligning economic reality with the new presentation rules without misrepresenting performance.

FAS 43 keeps participant and shareholder funds strictly separate, while IFRS 17 and consolidation rules often pull them back together. This creates two valid views of the same business that CFOs must reconcile.

Because each framework treats fund boundaries differently, one ledger cannot serve both purposes. Dual-view reporting avoids conflicts between Shari’ah-aligned statements and IFRS group requirements.

Stricter asset-backing may shift risks away from the issuer and toward investors, which can affect balance-sheet recognition, collateral requirements and rating assumptions. The risk isn’t negative by default — but it does require careful structuring.

Tawarruq provides a structure that is easier to align with ownership and transfer requirements while avoiding some asset-transfer hurdles. As standards tighten, issuers may favour structures that are simpler to defend.

Capital ratios will reflect full expected-credit-loss movements with no add-backs. This makes provisioning decisions more visible and increases sensitivity to model changes.

FAS 30 looks at risk-sharing economics, while IFRS 9 focuses on cash-flow characteristics and SPPI rules. This means a contract may be compliant under AAOIFI yet still fall into a different IFRS measurement category.

Their classification depends on both financial rights and Shari’ah character. Without clear documentation, valuation and recognition can become challenging under both IFRS and AAOIFI.

Because the two frameworks allocate income and impairment differently. A bridge statement prevents misunderstandings by showing how each number is derived.

MPMs must now be disclosed consistently and reconciled to IFRS figures. Auditors will review how they are defined, calculated and used — especially when linked to Shari’ah-based distribution models.

Teams need blended IFRS–AAOIFI expertise, stronger Shari’ah coordination, and systems that support dual-ledger reporting and digital-asset classification. The capability gap is now a strategic issue, not an operational one.

Calibration is not a one-time event.

In practice, AI actuarial models require:

• Continuous performance monitoring
  
  
• Scheduled recalibration cycles (often quarterly or semi-annually)
  
  
• Event-driven recalibration after material portfolio or market changes

Model drift is not always visible in headline metrics. Actuaries must design validation frameworks that detect subtle bias accumulation and assumption decay, not just accuracy loss. Regulators increasingly expect documented calibration governance, not ad hoc fixes.

The liability does not shift to the model. In regulated environments, including the UAE:

• The actuary signing the opinion retains responsibility
  
  
• The institution owns the decision
  
  
• Vendors disclaim liability through contract

Using proprietary AI models does not dilute professional accountability. It concentrates on it. This is why governance frameworks must be explicit about reliance, overrides, and limitations.

Ethical risk is not solved by accuracy metrics. Effective governance requires:

• Bias testing across protected and proxy variables
  
  
• Independent review committees
  
  
• Clear escalation protocols when fairness concerns arise

Most importantly, it requires actuarial oversight with authority to override model outputs. Ethics cannot be “monitored.” They must be enforced.

Black-box models are increasingly unacceptable without mitigation. Common XAI techniques include:

• Feature importance analysis
  
  
• Local explanation methods (e.g., sensitivity-based reasoning)
  
  
• Surrogate models for regulatory explanation

However, explainability is not purely technical. Actuaries must translate model logic into regulatory language, not data science terminology. Transparency is about trust, not diagrams.

They don’t assume it is. Actuaries apply data provenance reviews, temporal relevance testing, and exclusion of structurally outdated periods. Historical data reflects historical behaviour, including past discrimination, outdated pricing logic, and legacy market structures. Filtering this requires judgment, not automation.

In crises, actuaries do not “adjust models.” They suspend reliance. They design extreme stress narratives, manual scenario overlays, and even capital buffers disconnected from model outputs This human intervention is not failure. It is professional control.

Actuaries are not becoming data scientists. But they must become model governors.

Increasingly expected skills include:

• Understanding machine learning logic
  
  
• Data governance literacy
  
  
• Familiarity with validation frameworks
  
  
• Regulatory technology awareness

The goal is oversight, not coding supremacy.

Validation costs are higher. AI models require:

• More extensive testing
  
  
• Greater documentation
  
  
• Stronger governance controls

However, this cost reflects risk exposure, not inefficiency. Complex models demand stronger safeguards and regulators increasingly expect institutions to bear that cost.

Sandboxes are not shortcuts. They are controlled learning environments.

Actuaries use them to:

• Test model behaviour under supervision
  
  
• Refine governance frameworks
  
  
• Demonstrate regulator engagement

Successful sandbox use depends on transparency, not ambition.

Responsibility is layered but not diluted. Typically:

• Model owners manage technical risk
  
  
• Data scientists manage implementation risk
  
  
• Actuaries manage decision and opinion risk
  
  
• Institutions bear ultimate commercial responsibility

Courts and regulators do not accept “the model decided” as a defence. Human accountability remains the final control.

No. Existing End-of-Service Benefit (EOSB) liabilities do not vanish simply because a company adopts a voluntary savings scheme. The liability reflects service already rendered. Under accounting and legal principles, past obligations remain unless they are formally settled, funded, or legally transferred under an approved framework. Voluntary schemes change how future benefits accrue. They do not erase history. This distinction matters because many businesses assume a clean reset. Auditors do not. Any attempt to derecognise EOSB without proper settlement will attract challenge.

Not in all cases. But “not mandatory” does not mean “not required.” For SMEs reporting under IFRS, auditors increasingly expect actuarial valuations where EOSB is material. Size does not eliminate complexity. A smaller workforce with long tenure can still create significant liabilities. In practice, the decision is driven by materiality and audit risk, not revenue thresholds. Where estimates materially affect the financial statements, professional actuarial input becomes difficult to avoid.

Excel is a calculation tool. It is not a valuation framework. Spreadsheets can replicate formulas, but they cannot replace actuarial judgment, assumption governance, or stochastic analysis. More importantly, they lack audit defensibility. When regulators or auditors ask why a discount rate was selected or how turnover assumptions were validated, Excel has no answer. Actuarial methodology does.

Costs vary. Workforce size, benefit structure, data quality, and reporting requirements all matter. But focusing on cost misses the point. The financial impact of under-reserving EOSB, mis-pricing inter-company transactions, or failing an audit review is consistently higher than the cost of proper valuation. In 2026, actuarial work is not an expense line. It is a risk control.

Penalties depend on the nature and scale of exposure, but they can include tax reassessments, penalties, and reputational damage. More importantly, missing documentation weakens the company’s position during audits. Once credibility is lost, every assumption becomes suspect. Actuarial modeling strengthens transfer pricing defence by grounding pricing decisions in risk-based analysis rather than narrative justification.

Yes. Zero interest is still a price. Tax authorities assess whether an independent third party would have offered similar terms under comparable risk conditions. If not, the transaction must be justified, or adjusted. Actuarial credit risk models help quantify default risk, liquidity risk, and opportunity cost. Without this analysis, “interest-free” is often indefensible.

Because fixed premiums do not eliminate risk. They shift it. Under capitation or bundled payment models, healthcare providers carry utilisation risk. Higher-than-expected patient volumes or treatment intensity directly erode margins. Actuarial healthcare models forecast utilisation patterns and cost volatility. Without them, profitability becomes a matter of luck, not planning.

The difference is not hierarchy. It is perspective. Accountants record what has happened. Actuaries model what could happen. Both roles are essential. But when future obligations dominate financial risk as they do in 2026 actuarial insight becomes indispensable.

Only with careful adjustment. Economic conditions, labour mobility, healthcare usage, and regulatory frameworks in the UAE differ from global averages. Using unadjusted global assumptions weakens credibility and invites audit challenge. Local context matters. Regulators expect it to be reflected in the numbers.

Interest rates drive discount rates. Discount rates drive present values. When rates fall, long-term liabilities increase. When rates rise, they decrease. The effect can be material. Actuarial models quantify this sensitivity. That visibility allows CFOs to explain balance sheet movements instead of defending them after the fact.

Yes, where IFRS and IAS 19 apply. Free Zone status does not exempt companies from accounting standards. The Projected Unit Credit method ensures that benefits are attributed fairly over service periods – a requirement auditors enforce consistently.

Clean data. Complete data. Consistent data. Dates of birth. Joining dates. Salary history. Benefit structures. Exit patterns. Financial loss data where relevant. There are no shortcuts. Poor data undermines even the best models.

Yes – often more so. Family groups face long time horizons, succession complexity, and concentrated risk. Actuarial modeling supports liquidity planning, generational transitions, and sustainable dividend policies. Ignoring future obligations does not protect family wealth. Measuring them does.

Yes. Many organisations outsource to specialist actuarial consulting firms. What matters is not where the work is done, but how well management understands and governs the assumptions. Outsourcing analysis does not outsource responsibility.

Sensitivity analysis shows how liabilities respond when assumptions change. It answers questions like: What happens if inflation rises? If turnover falls? If discount rates move? Auditors insist on it because it reveals risk exposure. Management should insist on it because it supports informed decision-making.

The shift toward branch-level auditing reflects MOIAT’s intention to capture financial performance and localisation impact at a more granular level. Consolidated accounts tend to blur the economic footprint of each branch, especially when procurement, payroll, and assets are pooled. By isolating each branch’s activity, the ICV score becomes a more accurate reflection of where value is created, allowing the government to evaluate localisation outcomes Emirate by Emirate.

Branches within the same Emirate often fall under one licence, but they may still carry separate activities, cost centres, or operational setups. MOIAT’s intent is not only legal structure but also operational transparency. If the branches function distinctly — with their own revenues, procurement patterns, or staffing — auditors are generally expected to treat them individually. However, where activities and books are genuinely unified, auditors may still consider a combined review, provided disclosures support that structure.

Shared-services setups can continue, but reliable branch-level allocation mechanisms must support them. The new rule doesn’t prohibit centralised accounting; it simply requires that each transaction can be traced to the originating branch. Companies relying on shared ledgers may need to enhance cost allocation, tagging, and internal reporting controls so the auditor can extract branch-specific performance without relying on assumptions alone.

The absence of revenue does not prevent branch evaluation. MOIAT views localisation through multiple dimensions — payroll, Emiratisation, operating expenses, assets, and supplier spend. A branch with zero revenue can still demonstrate localisation contribution. The key requirement is that audited financials present a true picture of that branch’s activity, even if minimal.

In such cases, certification teams generally look for evidence that the company made reasonable attempts to comply. Where historical data isn’t split by branch, auditors may request internal allocations backed by logic, documentation, or ERP extracts. MOIAT tends to be cautious about accepting reconstructed data, so companies may face delays or partial scoring. Preparing proper branch-level books early significantly reduces these risks.

There is no specific mandate to upgrade to a new ERP, but whatever system is used must allow auditors to extract branch-level transactions without relying on guesswork. This can be done through tagging, cost centres, or structured spreadsheets. The emphasis is on traceability rather than technology, so even smaller systems can comply if properly configured.

Auditors generally expect staff costs to be allocated based on the economic reality of their work patterns. Time sheets, project logs, or HR deployment plans can support fair allocation. The goal is to avoid double-counting and to ensure that each branch shows only the payroll cost genuinely associated with its operations. Consistency across months is more important than mathematical perfection.

Branches treated purely as cost centers often show higher expenses and little to no revenue, which can distort certain ratios. Under the 2025 framework, auditors may focus more on localisation inputs—payroll, assets, supplier spend—rather than revenue-driven metrics. While some score categories may shift, branches can still achieve competitive ICV results if localisation efforts are well-documented.

Merging branches across Emirates tends to conflict with MOIAT’s objective of Emirate-level economic visibility. Even if activities match, the geographical footprint is considered significant. Auditors may hesitate to combine branches unless MOIAT provides explicit justification. In practice, companies are advised to maintain separate reviews when branches operate in different jurisdictions.

Shared suppliers continue to be acceptable, but the company must show how the spend was consumed by each branch. Allocation can be based on usage, volume, project size, or other logical drivers. The auditor’s role is to ensure the methodology is reasonable and consistently applied. Clear documentation from procurement teams helps avoid disputes during certification.

During transition periods, some flexibility may exist, especially for companies that historically used consolidated books. However, MOIAT generally prefers branch-specific audit trails. A hybrid model may be acceptable if the supporting schedules are detailed, well-substantiated, and reviewed by the auditor. Transition allowances, if any, will likely reduce over time as the 2025 requirement becomes standard practice.

Auditors are expected to outline the methodology used to isolate each branch’s financials. This may include allocation principles, inter-branch eliminations, shared cost distribution, and verification procedures applied to branch sub-ledgers. Enhanced disclosures ensure that MOIAT can trace how the auditor arrived at branch-level results, especially when centralised systems or shared services are involved.