Home > Commands > Input > Valuation Assumptions > Increase & Crediting Rates

Increase & Crediting Rates

In the OPEB mode of operation this topic is entitled “Increase Rates”. “Crediting Rates” refers to cash balance Accrual Definitions and employee contribution refund, which are not found in OPEB mode. For Long Term Disability assumptions in OPEB mode, only Benefit Formula Components are applicable.

A cash balance accrual definition can use crediting rates from the valuation assumptions instead of from the Accrual Definition itself, which allows more flexibility when defining those rates. For example, rates can vary by calendar year when input as a valuation assumption, but only a constant crediting rate is available in an Accrual Definition. Similarly, a career average accrual definition in the universal pension mode may have indexation rates that are input under this topic (i.e., specified in the Valuation and Projection Assumptions).

ProVal allows you to set increase assumptions for items found in the following categories:

You must define increase rates for all regulatory items referenced directly or indirectly in the Plan Definition, even if the increase rates are zero (ProVal will not read a blank as zero). Furthermore, you must always provide increase rate(s) (even if zero) for the maximum compensation limit of a U.S. public or U.S. qualified pension plan, regardless of whether you are doing a funding or an accounting valuation. For example, an undefined (instead of zero) input value for the increase rate for the maximum compensation limit in a U.S. qualified funding valuation will result in an error message (and aborted run) at execution.

The increase rates entered under this topic apply for determining values only in “future” calendar years, i.e., years after the calendar year of the valuation date (as indicated by the Valuation Date parameter of the Valuation or Core Projection dialog box). For years up to and including the year of the valuation date, ProVal will use its historical regulatory data unless you override that data under the Regulatory Data topic. Note that “historical” refers to any year up to and including the year of the valuation date, even a year for which regulatory data is not yet published (or, if recently published, may not yet be in ProVal). Thus, for some valuation dates, ProVal may be missing historical data for some year(s). You must add the data you wish to assume for those years, either under the Regulatory Data topic or by modifying ProVal’s regulatory data text files (see the discussion, under the Regulatory Data topic, of overriding historical data); such data cannot be entered by means of increase rates.

In the U.S. qualified pension mode, there are special considerations with respect to IRC section 415(b) maximum benefit limits and IRC section 401(a)(17) maximum compensation limits when computing liabilities under the Pension Protection Act of 2006 (PPA). If you wish to project increases in these limits for purposes of determining the target liabilities for the maximum tax deductible contribution limit (see IRC section 404(o)(3)(B)(ii)), then two increase rate specifications may be desired: a 0% increase rate for purposes of determining the target liabilities for the minimum required contribution limit, but an x% (x>0) increase rate for target liabilities for the maximum tax deductible contribution. ProVal allows you to specify only a single increase rate for the maximum benefit limit; the same is true for the maximum compensation limit. If this is material, run a separate Valuation or Core Projection that references a Valuation Assumptions set with positive increase rates for the limits and select this Valuation or Core Projection, under the Overrides parameter when you set up your Valuation Set or forecast, for the PPA maximum tax deductible basis target liabilities for active participants. Thus, if your law selection is “PPA”, you may use a 0% increase rate for PPA target liabilities under minimum funding rules but override with x% for PPA target liabilities for the maximum contribution limit. If your law selection is “Pre-PPA and PPA”, that is, you are coding a forecast that begins before the funding rules of PPA take effect, with transition to PPA over the forecast period, the increase rates you enter as valuation assumptions will be used for all years of the forecast. Again, you may use the Overrides button to “switch”, when PPA takes effect, from 0% for pre-PPA actuarial liabilities to x% for just the PPA liabilities used for the maximum contribution limit.

In the Canadian registered pension mode, to reflect published Income Tax Act (ITA) maximum pension amounts for years after the year of the valuation date, you must enter increase rates under this topic (not overrides under the Regulatory Data topic). See the example of variable increase rates presented in a paragraph below.

If you wish for any of the topics above except Insurance Contracts and Modified Cash Refund Annuities, you may select a Plan Filter (or Promise filter for German pension mode) from the dropdown list, to reduce the list of possible choices to those associated with a particular Plan Definition. Please see Filters for details.

Select a category to select the items or components to which you wish to apply increase rates, crediting rates or, for universal mode insurance contracts, excess interest rates:

Any custom regulatory table you have created will also be listed in this category, under the name by which it is known in the Custom Regulatory Tables library.

To apply increase rates, select the desired items, click the Edit button, and complete the parameter for defining the associated rates.

Increase rates for components, and crediting rates for cash balance components, unlike increase rates for regulatory items, are applied retrospectively as well as prospectively. That is, a constant increase rate (or a varying increase rate that is not zero for years prior to the year of the valuation date) will produce a decreasing, not level, component value for years before the calendar year of the valuation date.

Note that increase rates applied to an Accrual Basis Component alter the value of the Accrual Basis for all years (of service, age or points, as applicable). Alternatively, instead of increase rates, you may use the with new rates as of parameter of the Accrual Rates topic of the (accrual definition) Benefit Formula Component, with the new rates applied for all years of benefit service. If the new benefit levels are stated as a dollar amount or a percentage of pay, it may be preferable to use the latter parameter, rather than increase rates, thereby avoiding the need to compute the equivalent rate of increase, to input here, of a new benefit level over the old level (see the example, shown in a following paragraph, of determining the equivalent increase rate). Be mindful, however, of attribution issues under unit credit and projected unit credit cost methods; see our Frequently Asked Questions article entitled “Flat dollar plan with increasing benefit level ” for more information.

If an item requires an increase or crediting rate and none has been entered, then execution of a Valuation or a Core Projection will be aborted. To apply increase rates, select the desired items, click the Edit button, and complete the parameter for defining the associated rates.

Increase rates for lifetime maximums and annual limits, unlike those for regulatory items, are applied retrospectively as well as prospectively. That is, a constant increase rate (or a varying increase rate that is not zero for years prior to the year of the valuation date) will produce a decreasing, not level, lifetime maximum or annual limit value for years before the calendar year of the valuation date.

If an item requires an increase rate and none has been entered, then execution of a Valuation or a Core Projection will be aborted.  To apply increase rates, select the desired items, click the Edit button, and complete the parameter for defining the associated rates.

There are two otherwise identical spreadsheets on the dialog box: one each for the employee and employer insurance contracts. In each case, the excess return crediting rates for participation are entered first for the current contract, and then for each prior contract. By default, the spreadsheets accommodate assumptions for up to three (3) prior contracts, but if the referenced Plan Definition includes more than three, a row will be provided for each defined prior contract.

You are required to enter the Excess Rate 1 and Excess Rate 2, in decimal form (e.g., 0.03), for each participating contract. Typically these rates will be the same, but the excess rate 1 is applied to the end of year reserve and the excess rate 2 is applied to the half of the difference between the end of year and the beginning of year reserve when the participation is based on the average reserve. (When the participation is based on the total reserve, the excess rate 2 is applied to the full difference between the end of year and the beginning of year reserve.)  

Currently ProVal uses the valuation assumptions for excess return crediting as the projection assumptions. Thus, there is currently no opportunity to value insurance contract participation experience during a forecast as anything other than expected (i.e., as anything other than anticipated in the valuation).

Note that crediting rates for modified cash refund annuities are not applied prior to the valuation date, a consequence of the fact that if the deferral period begins prior to the valuation date, the annuity is treated as in payment status on the valuation date, and thus there is no deferral period subject to crediting rates.

If a deferred modified cash refund annuity is referenced by the Valuation or Core Projection, then an interest crediting rate is required; if none has been entered, then execution of the run will be aborted.

The choices for the parameter defining the associated rates are:

Instead of a single table, you can specify "<rates by coded database field>" if different tables should be used for different groups of records, identified by values of a coded database field (e.g., Division). After selecting this choice from the dropdown list, to select the tables for the various field codes, click the Parameters button that becomes accessible (on the right), which provides access to additional parameters to specify how the rates vary according to the contents of a coded database field. Select from the list (of all coded fields unhidden in the current Project) that appears when you click the arrow for the parameter Coded database field. In the spreadsheet displayed, each code of the selected field appears in the Database Code Column. For each code, click its row in the Rate Table column and then click the arrow that appears. Choose the applicable rate table from the list.

Note that there is a “<no rates>” option for Benefit Formula Components, Accrual Basis Components and modified cash refund annuities. Although this option produces the same Valuation results as a Constant increase rate of zero, results in a Core Projection will differ. This is because valuation assumption sensitivities are applied to a zero constant increase rate, whereas a table selection with “<no rates>” specified is treated as if no increase rates are applied to the component or modified cash refund annuity and thus no sensitivities are applied.

From To Rate
-- 2001 0.05
2002 -- 0.06

ProVal fills in the To column automatically, and the last rate will be used for the last year entered and all years thereafter. Note that the From box in the first row cannot be completed. Our example involved only two rates: if you have several rates in your assumptions, you may need to press the ENTER key, to create a new row, when you get to the bottom of the spreadsheet.

A rate of increase must be entered for a regulatory item or component, not its value for a particular calendar year. If a value for a particular year is stated, rather than a rate of increase, compute the equivalent rate of increase over the preceding year’s value and enter that rate in the row for the preceding year. For example, if the valuation date is 1/1/2000 and you have a benefit formula component with a value of $50, increasing to $60 at 1/1/2001, then the increase is 20% and you should enter

From To Rate
-- 1999 0
2000 2000 0.2
2001 -- 0

Note that if instead you enter

From To Rate
-- 2000 0.2
2001 -- 0

ProVal will decrease the component value by 20% from 1/1/2000 back to 1/1/1999, another 20% from 1/1/1999 back to 1/1/1998, and so forth.

Note also that if the valuation date is, for example, 10/1, ProVal uses the increase rate in the row for 2000 for the one year period beginning on 10/1/2000, not for the calendar year 2000.

(See Increase Rate Tables for another example of this technique, applied to a schedule of benefit increases in future years under a pension plan.)

Another use for varying increase rates is application of Canadian ITA maximum pension amounts, which are published for some years into the future. As a specific example, ITA maximums through 2009 were known in 2006. To perform a valuation as of 1/1/2006 reflecting these published limits, and, e.g., a 4% per year increase thereafter, you would calculate the rate of increase for each year as follows:

Year Limit Increase over prior year Calculated as
2006 2111.11 -- --
2007 2222.22 0.05263108 (2222.22/2111.11) -1
2008 2333.33 0.05 (2333.33/2222.22) -1
2009 2444.44 0.04761864 (2444.44/2333.33) -1

and enter variable interest rates as follows:

From To Rate
-- 2005 0
2006 2006 0.05263108
2007 2007 0.05
2008 2008 0.04761864
2009 2009 0.04

For each component specified under all categories of the Increase & Crediting Rates topic you can specify whether or not +/- valuation assumption sensitivities are applicable.  Check the +/- valuation assumption sensitivities applicable box to apply the valuation assumption sensitivity specified (if any) in the Valuation.