As companies move beyond IFRS 17 implementation and shift focus to streamlining their actuarial processes, one area that often requires attention is the Analysis of Change (“AOC”) calculations. These calculations are critical in IFRS 17 reporting, as they provide insights into the drivers of movements in key balances like Best Estimate Liabilities (“BEL”), Risk Adjustment […]
In reality, many of the underlying cash flow structures—such as premiums, benefits, and expenses—are largely consistent across product types and reporting regimes. This means that the base model used to generate projected product cash flows can and should be designed as a unified model, capable of supporting multiple views through flexible logic, control structures, or reporting configurations.
In many of our conversations with Prophet users, the topic of sub-product codes, or SPCODE, often surfaces—particularly when discussing model structure and output interpretation. While SPCODE is a standard part of Prophet’s model point setup, how it is used can significantly impact both model flexibility and the range of analyses it can support. In this
In our previous post on using enumerations in Prophet, we briefly referenced the concept of calculation looping. That mention sparked a thought—many Prophet users, especially those who work primarily with standard valuation models, may not be entirely familiar with this technique. Yet, calculation looping is a powerful and often underutilized feature that can enhance both
In our engagements with valuation teams using Prophet, we’ve observed that most users are confident with in-force projections—such as those required for monthly valuation or embedded value reporting. However, when it comes to new business (“NB”) processing, many find the setup and logic less intuitive.
