Index Fund Overview

OIPA contains the architecture required to administer Equity Indexed Life (IUL) and Annuity products (EIA). These types of polices give companies the option of allowing policyholders to use a Stock Market Index rather than individual funds as a basis for account value growth. Many customers prefer this strategy as it reduces exposure to market risk while at the same time provides limited stock market participation. The performance is based on an underlying index such as the S&P 500 or Russell 2000. Other factors that impact the calculation of the credit to the policy, called the Index Credit, are variables such as the Cap, Floor and Participation rate.

The Index Prototype Company in the Prototype Company of the Rules Palette demonstrates some common design features that are characteristic of index funds.

Common Index Fund Characteristics

Sweep Date

Many index funds use a Sweep Date. Sweep dates, in this context, restrict the addition of money into the Indexed tracking funds to certain times, such as a particular day of the month. In order to accommodate that restriction the concept of an Interim or Holding Fund is introduced. Money received prior to a given date will be held in the interim fund and credited with a fixed rate of interest. When the Sweep date arrives that deposit plus the interest earned is added to the Indexed Fund. In OIPA, a combination of plan data can be configured to set a standard Sweep Date and then math configuration for calculating any needed logic to figure out the actual business day the sweep date can occur is reused to support this portion of Index fund design.

Index Segment Period

Indexed funds also use an Index Segment Period, which is the length of time money allocated to an indexed fund must remain in the fund in order to receive the full value of the Index Credit. This is also known as the Index Period. Through transaction configuration, premiums are swept into indexed funds according to allocations. A configurable feature called buckets provide a means of tracking multiple premiums to ensure index segment period requirements are met.

There are several common methods that can be used to credit the policy account. The three common types are listed and summarized below:

For each of these methods, OIPA rate tables are used to store index daily rate values, which can be easily called from configuration. Configuration logic can figure out if an ending index value is higher, compare averages or figure out a difference, which is all supported by the OIPA math syntax.

Valuation for index funds is not done in unit values, but rather an Index or Index Value is stored in AsRate and updated. A range of these values is then used to determine the percentage that will be used as the main component for the Index Credit or credit.

Some other product design items use the Rate table for information that isn't technically a rate, but because it is easy to call the Rate table from configuration, it is stored there. These values are applied to the Index Credit to arrive at the final Index Credit that is used to update the policy’s value. The product’s specification will determine which of these should be used.

Buckets

Buckets are used to uniquely identify, value and track one or more deposits into an indexed fund that must be valued separately from the fund as a whole. In OIPA, a bucket is represented by an integer value in the AsBucket database table. The bucket links a bucket and its Effective Date with a policy and the actual values of premium and the associated bucket in the AsValuation table, using the BUCKET column.

The maximum number of buckets for an indexed fund is dependent on how often a new Index Segment can begin and the duration of the Index Segment, which can then be configured in the Plan Data page of the Rules Palette. For example, if a new Index Segment can begin once a month and the duration is one year, there could be a maximum of 12 buckets. If the duration is 5 years, then there could be up to 60 buckets.

The bucket value is updated when deposits are transferred (“swept”) into an indexed fund. It is common to use the calendar month as the integer value for twelve month tracking periods. For example, a deposit may be received on February 15. If the Sweep day is the 28th of each month, then on February 28 the net deposit is transferred to the user allocation. The bucket is updated to 2 if any money is allocated to an indexed fund in that transfer.

In assignment processing, there are two attributes in the Assignment tag that relate to buckets.

When working with arrays, the following math operations relate to buckets.

When pulling values into buckets, keep the following information in mind.

High Level Steps to Configure Indexed Funds

  1. Create a plan.

  2. Create and configure a FundScreen override.

  3. Create interim funds to hold premiums until the Sweep date.

  4. Create index funds.

  5. Configure allocations to allow policy owners the option to select index funds via the OIPA interface.

  6. Configure the InterestRateCalculation business rule to calculate the interest that should be credited to the premium in interim funds.

  7. Create Rate Groups and enter initial rates for the index funds.

  8. Create Rate Groups and load initial rates for the Growth Cap, Growth Floor, Participation Rate and Spread.

  9. Configure static values.

  10. Configure reusable configuration.

  11. Configure transactions to take in money, move money into the interim account, move money from interim account into index funds, apply index credits and other design features according to the product design.

  12. Configure the ValueScreen business rule.

For detailed configuration steps involved in setting up index funds, refer to the Configure Index Fund section.

Related Topics

Configure Funds, Fund Database Tables, Child Funds, Currency Codes for Funds, Fund Screens in OIPA, Allocation Models

     
Copyright © 2017, Oracle and/or its affiliates. All rights reserved. About Oracle Insurance | Contact Us