Release documentation - Life - Enhancements and requests

Problem:

Run General Transfer Ledger does not transfer data to GL_T_ALL table of Service contract business

Solution:

The type of business Service Contract should be supported for General Ledger transfer

Declination Reason:

Workaround:

Root Cause:

Problem:
Original Accounting Year/Period fields are not present in retrocession created through the RPO

Solution:
When the system parameter 'Original Accounting Year/Period Based on Policy Anniversary Year'

The fields Original Accounting Year and Period should be available on the standalone retrocession that is created when running the RPO

The values from the inward cession should be copied to the retrocessions

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Abend when listing businesses in a Projection Calculation Order. Occurs when a Projection Basis is selected

Solution:

Remove abend. Make sure businesses matching the selection criteria are listed

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

ACs are not created, when given MCOB on the ACs only,then the ACs are being created with no name

Solution:

All the classifications marked as 'in AC= Yes' in the base company settings- classification 1 for the base company should be listed when you generate the accounting classifications

The AC name should be listed as per the settings defined on the system paramters - Accounting classifications eg reference data name/ and or ref data code, separator = _ or whatever

When the system parameter 'Use Additional Classification as Main Class of Business' is selected AND the additional classification mapped as MCOB is not selected with 'In AC= Yes', then the value should not be listed while generating the ACs (similar to any other additional classification)

Declination Reason:

Workaround:

Root Cause:

Problem:

Commission got calculated when we did not define any commission on D condition of Assumed business

Solution:

When the Deduction condition is defined with 'Is Not Required' then no commissions or any other deductions should be calculated on the cessions when the ACIs on any premium is calculated
 

Declination Reason:

Workaround:

Root Cause:

Problem:
SQL Error :- Claim is not referenced when created through loader
Solution:

When the referencing identifies duplicate claims with the same policy number/ life id/ cedent cession number and cedent ref or claim id then use the claim event date to identify the correct cession on which the claim is to be created
Create the claim on the cession benefit which has the effective period within with the claim event date lies in
If such an effective period does not exist on any of the claims then reject the claim record that is loaded with the existing message message 'Cession not found'

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Abend when there are both ceded and non-ceded cessions in the same RPO

Solution:
When the RPO picks up cessions with and without the ceded flag the system should not abend
If the classifications of the cessions are valid then all the cessions should be processed through the RPO as per existing functionality
If the classifications on the cessions i.e if the cessions without the ceded flag do not have the mandatory classifications that are required to process them through the OCC/ RPO then these cessions should be rejected with the existing error message 'Unable to process... due to missing classification' and should be listed in the failed assignments

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Possible to create retro detail without link to Source Business even it is mandatory

Solution:

When the system parameter 'Mandatory Retro Booking Link' is selected it should not be possible to close a technical worksheet if there is a detail on a technical worksheet without a link to the source business

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Joint Life details not copied to the Joint Life retrocession created by the RPO

Solution:
All details from the joint life cession benefit on all the tabs should be copied to the joint life created by the RPO

When the OCC has specific age calculations or premium calculations for joint life defined on the PM condition then these calculations should be applied to the age on the joint life benefit and these values should be used to calculate the ACIs

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Abend when adding Outward business in Renewal for Fac Standalone retrocession Order

Solution:

On a Renewal for Fac Standalone Retrocessions Order it should be possible to add an OCC that is not linked to a PP without an abend

When an OCC that is linked to a PP is added the error message 'The OCC is linked to a Protection Program and cannot be included in the Order' should appear

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Policy Year field is not present for Joint life cessions

Solution:

Add the field Policy Year on the Joint Life Cession Benefit - Term and IO details tab
All functionality pertaining to Policy year that is available on the individual cession should be extended to Joint Life Cessions

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Solution:

1. For single and joint life cessions the policy year should be updated only on each yearly anniversary of the cession benefit. The policy year should be updated as previous policy year + 1 after the end of each yearly anniversary of the cession benefit

The policy year should not be updated with each transaction. 

This should be copied to the retrocessions and placement cessions

2. Issue age and adjusted issue age should never be updated throughout the life cycle of the cession benefit. Only the transction age should be updated based on the transaction effective date + date of birth using the age calculation basis on the PM condition

 
This is applicable to individual single life cession benefit and the individual information of each IO on the joint life cession benefits

When the Age calculation basis is not original the calculation should happen on the retrocession cessions 

3. The ACI on the Other transaction when it is based on Age as one of the parameters, should be calculated using the transaction age as on date of the other transaction.

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

IO Details are not updated to Retrocession for Joint life cessions

Solution:

All the life related details such as smoker status, occupation class etc that are available for each individual insurable object on the Individual Life specific tab should be copied to the retrocession and placemennt cession benefit transactions of the retrocessions that are created when running the RPO

These details should also be made available on the claim when the claim is created for the respective insurable objects

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Cession Status should be Active if there is any one Active benefit

Solution:
The status of the cession should always remain active if any one cession benefit linked to the cession is active

If all the cession benefits on the cession are inactive then the status of the cession will also be inactive

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Unable to load batches with other mappings when batch processing is done through a database upload

Solution:

It should be possible to link the database batch to any existing valid mapping that is available

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Abends in Facultative Standalone individual Retrocessions when UDF is added

Solution:

It should be possible to add a UDF on a Facultative standalone retrocession or any other manually created standalone retrocession on both the cession and cession benefit level
The UDFs that are added should be copied to the placement level

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Abends in Facultative Standalone individual Retrocessions when there is a loading

Solution:

It should be possible to create manual facultative standalone retrocessionns for both single and joint life cessions with all the loadings and process the ACIs without abend.

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Getting an Abend when try to edit Expenses in claims and The claim Expenses is editable from the Edit menu

Solution:

For a Ceded Paid/ Ceded Outstanding claim:

Edit Expenses should only be allowed when the expense is edited on right click on the Expenses Tab for expenses that have the status of Suspended and Released

Once the status is Included it should not be editable from anywhere

When the user selects Edit on the main window and goes to the Expenses tab then the options on right click should be disabled and the values should remain uneditable

Declination Reason:

Workaround:

Root Cause:

Problem:

Allow Origin of Business as a selectable classification on the cession when the ceded flag is selected.

Solution:

The values from the Origin of Business on the AB should be allowed to be selected on the inward cession when the Ceded flag is selected. Only one value should be allowed to be selected on the inward cession benefit.

Any rules that are applicable for different basis of Origin of Business (eg- allowing SAR = 0 only if origin of business = Coinsurance )must be applied on the cession benefit that has the respective value selected

When processing the retrocessions this value should be validated against the classifications of the PP and OCC

Declination Reason:

Workaround:

Root Cause:

Problem:

Policy year field is not available on Retrocession and Placement Level of Single life and Joint life cession benefit

Solution:

The fields Policy Year should be available on the retrocession cession and placement level on cessions where the ceded flag is selected or not

The value from the inward cession transaction should always be copied to the retrocession cession transaction and placements

Declination Reason:

Workaround:

Root Cause:

Problem:

Possible to create cession with expiry date earlier than start date

Solution:

It should never be possible to create a cession benefit with the expiry date earlier than the benefit start date

If an invalid expiry date is entered then the error message 'Expiry Date cannot be earlier than the Benefit Reinsurance Start date' should be thrown
Declination Reason:

Workaround:

Root Cause:

Problem:

ACI Date, Transaction No. is not Updating Correctly, and Retro Claim created date field is not available on the Inward Claim when Sum reinsured type is Income Benefit Per Frequency

Solution:

1. When the Sum Reinsured Type is Income Benefit Per Frequency- update the Retroceded Date on the Ceded Paid claim that is created

2. When the system parameter 'Transaction number of cession and claim' is selected all ceded paid statuses on the same claim should be updated with the transaction number as entered or as incremented with +1 from the previous transaction number if not specifically entered

3. The As of Date of the ACI should be the payment due date of the respective Ceded Paid status and NOT the correspondence/ notification date

Declination Reason:

Workaround:

Root Cause:

Problem:

Retrocession claim processing order is not picking multiple cpaid status on one claim and other issues

Solution:

The RCPO should pick up all the Ceded Paid statuses that are available on the claim based on the payment due date. If there is more than one ceded paid status that falls within the payment due date on the order then all the statuses should be picked up, and the respective ceded paid recovery claim should be created as a retro claim with the same number of ceded paid statuses

When ceded paid statuses on an inward claim is picked up by the order separately, the corresponding ceded paid recovery transaction on the outward claim should be created on the same retro claim 

Declination Reason:

Workaround:

Root Cause:

Problem:

Age validation error when loading type Total mortality is selected on joint life cession.

Solution:

Extra mortality premium should be calculated based on the basic premium calculated for the cession irrespective of the age calculation basis.

The should be applicable to joint life cession benefits for any premium basis where the basic premium can be calculated automatically

Declination Reason:

Workaround:

Root Cause:

Problem:

Missing Classification- Origin of Business on the OCC

Solution:

Origin of Business should be a classification on the PP and the OCC and all available values from the reference data 00048 should be allowed for selection

Declination Reason:

Workaround:

Root Cause:

Problem:

The SAR net sum retained is not displaying correctly on retrocession information tab of cession benefit for proportional retrocessions

Solution:

Net Sum Retained as per the calculated value should be displayed on the Retrocession Tab of each transaction after the RPO is Run

Only when the system parameter 'Sum at Risk Reinsured proportionally in excess of retention is selected'

Since the Retro Sum at Risk is recalculated during each run of the RPO the Net Sum Retained can be calculated and populated as SAR- Retro SAR

Declination Reason:

Workaround:

Root Cause:

Problem:

The SAR net sum retained is calculating incorrectly on renewal transaction of cession even the OCC retention is fully utilized

Solution:

The retention that has been utilised by any transaction on the cession should remain the same throughout the life cycle of the cession on all subsequent transactions if there is no change in the sum at risk

If the sum at risk on the transaction has increased or decreased on the transaction AND there is available retention, then the retention should be updated with the recalculated retention

When the system parameter Sequencing as per the Sequencing number is selected, then sequencing for determining the available retention should be as below

Use the reinsurance start date

When there are more than one cession benefit with the same reinsurance start date, then use the sequence number within the cessions having the same reinsurance start date

Declination Reason:

Workaround:

Root Cause:

Problem:

Incorrect message related to ACI calculation when benefit term table is selected and no benefit term is given

Solution:

When no benefit term (or any value for the respective LUT parameter is available ) then the correct error message ' no value found for <LUT parameter> should be thrown.

Declination Reason:

Workaround:

Root Cause:

Problem:

No Validation message showed When claim liability is changed on a Paid claim status'

Solution:

When the claim liability is changed on a claim that has a Paid status and this amount exceeds the sum at risk on the cession - the error message 'Claim liability cannot exceed the sum at risk' should appear (this message appears correctly when the notified reinsurer's liability field is changed to exceed the sum at risk)

only on giving ok to this message the claim should revert to the claim liability value that was defaulted from the notified reinsurer;s liability (or any value that was updated which is less than the sum at risk on the cession benefit)

Note: For claims with a status of Ceded Paid there should be no validation

Declination Reason:

Workaround:

Root Cause:

Problem:

Getting abend when loading a cession batch without a sum reinsured type

Solution:

When a cession is created on a section where the Sum Reinsured Type is blank the batch should not fail. When the cession is created WITH OR WITHOUT the Ceded flag: The message 'Missing Sum Re/ Insured Type' should be given for the records that are referenced to a section without the Sum Reinsured type

Declination Reason:

Workaround:

Root Cause:

Problem:

Group Cession without individual member list Flag should not be editable on the claim

Solution:

Group Cession without individual member list Flag should not be editable on the claim at any level- inward claim, retroclaim or placement claims

Declination Reason:

Workaround:

Root Cause:

Problem:

Manual Ceded Paid Claim- Do not validate Cause of Loss

Solution:

It should be possible to create a manual ceded paid claim without having to give a Cause of Loss or Cause of Loss Group

Declination Reason:

Workaround:

Root Cause:

Problem:

RCPO is not picking the historical claim when retrocessions are not linked to the cession benefit

Solution:

When the RCPO is run all claims that have the payment due date within the order dates should be picked up

If the claim event date is linked to an active cession transaction effective period it should be processed through the order

If there is no active transaction period on the cession AND the historical ceded claim flag is selected then this claim should also be picked up and processed through the order if there is a standalone retrocession on the cession

When there is no linked retrocession cession to the claim that is picked up the error message should be 'No active standalone retrocession exists' and not '’Unable to process claim due to missing ceded factor’

When there is a linked retrocession cession, but there is a ceded factor present on the claim AND the flag historical claim is selected- then the ceded factor should be used to calculate the retrocession claim ACI

Declination Reason:

Workaround:

Root Cause:

Problem:

Batch is getting failed when GSR and SAR amounts are less than auto cover limit due to rounding off issues

Solution:

When the autocover limit is being calculated during the validation of the gross sum reinsured on a cession always round off the autocover limit to the number of decimal places as defined in the system parameter 'Sum at Risk in Decimals'

When the equivalent values are applied and an exchange rate is to be applied :

First calculate the autocover limit in the main currency and round it off, then apply the exchange rate and round it off to the same number of decimals as defined in the system parameter 'Sum at Risk in Decimals'

Use this calculated value to validate whether the gross sum reinsured is within the autocover limit

Declination Reason:

Workaround:

Root Cause:

Problem:
Retroceding and Retention amounts are not showing on the Retrocession Information Tab

Solution:

The net sum retained and the retro sum at risk should be updated on the retrocession information tab for each transaction of the cession benefit after each run of the RPO

Declination Reason:

Workaround:

Root Cause:

Problem:
Payment Due Date of subsequent Ceded Paid statuses should not be earlier than the payment due date of the previous status

Solution:

Do not allow a payment due date on a ceded paid claim to be less than the payment due date of the previous ceded paid claim status on the same claim

Manual claim or when the claim is created through the loader:

Throw a validation error 'Payment Due date should be greater than or equal to <payment due date of the previous status>

Declination Reason:

Workaround:

Root Cause:

Problem:
RPO is calculating ACI's with wrong Entry code for newly added benefits

Solution:

ONLY FOR CEDED CESSIONS:

Use the value in the Policy Year field to determine the entry code to be used. If the Policy Year = 1 then always use the entry codes pertaining to first year in the calculation model. else use subsequent year entry codes

Always use the deductions (commissions and other deductions) rates as defined for the respective policy year. If there is no rate for the policy year, then do not calculate the deductions.

If policy year = 1, use the basic commission rates to calculate the commissions
Declination Reason:

Workaround:

Root Cause:

Problem:
Commission for Loading is not getting reversed for Lapse transaction

Solution:
When the Unearned Premium Returnable option is selected on the AC condition of the OCC then when there is a termination transaction the reversal of all ACIs should be done as per the calculated date

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Cash claim option is not copied to the SAIR

Solution:
All details including the Cash Claim option selection from the inward claim should be copied to the retro claim and placement claims

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
System abends after defining Total Reinsured Sum at Risk field on Joint life cession

Solution:
When the flag Sum at Risk in Our Share is selected the share percentage from the ceded share on the Share condition should be applied to the value in the Total Sum Reinsured on the joint life cession to calculate the Gross Sum Reinsured and Sum at Risk

If there is no value in the field Total Sum Reinsured then the share percentage should be applied to the value in the field Gross Sum Reinsured
Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Validation message for Limits LUT is not given correctly when the LUT parameter is not available

Solution:

Any error message that is thrown to specify that the value that is available on the cession is not available on the referenced lookup table should mention the Type of Table and Table name

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Incorrect Entry codes are picked when the Description of Account is Selected as ‘Cash Claim Account’ in the worksheet generated through RCO

Solution:

Only entry codes that have been flagged as Cash Claim should be picked up when the description of account is Cash Claim in the Cession order or Retrocession Cession Order

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Getting ABEND while creating REINSTATEMENT transaction with same effective date as of Lapse transaction

Solution:

When a Reinstatement transaction is created through the loader the transaction effective date should never be considered even if mapped. The reinstatement should always be created with the same effective date as the termination transaction that is being reinstated. The system should not abend

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

In Claim Expenses tab, added expenses fields values are removing when we click on the field

Solution:

The claim Expenses fields should not be editable in view mode. Clicking on any field should not remove the value in the field. This is applicable to any claim status where the Expenses tab is available

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Failed assignments should be listed only for that RPO- previous listing should not reappear

Solution:

Any cession that has been picked up by the RPO for the respective PP and AB and already listed in the failed assignments should not appear in subsequent runs of the RPO

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Account Group not copied while copying business

Solution:

The account group of the source business should be copied when copying the business

The field account group should be available in the Copy Business window while copying it so that it can be updated

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Referencing Error when there is a duplicate IO

Solution:

The SQL error message that appears needs to be made more descriptive

'More than one insurable object with the same unique identifier available'

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Getting negative amount in SAR Net Sum Retained limit for Surplus business

Solution:

Once the retention is fully utilized and the SAR goes below the retention in subsequent transactions or due to any other change in the SAR that will involve the retention to be recalculated when the RPO processes these cessions, the retention should never be set to negative.

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

RPO- Sequential Retrocession When Running Single RPO for Subsequent Renewals.

Solution:

Irrespective of whether the cession transactions are picked up by a single RPO or by individual RPOs the sequence of retrocession should always be based on the respective system parameter selected. When the system parameter 'Method of retrocession sequential in excess of maximum retention' is selected all transactions that are picked up by the RPO will be retroceded based on the transaction effective date

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Abend in RPO when loading duration is Period from Inception

Solution:

ALL Loadings should be calculated/ updated on the inward cession as per the mapped/ entered values for duration.
When the loadings are calculated on the inward cessions they should be calculated as per the loading duration

The loadings should be copied to the retrocession when the RPO is run
When the RPO processes the ACIs the loading ACIs should be calculated on the retrocession cessions and placements based on the duration option selected for each loading
If a loading cannot be calculated due to missing or invalid data then that particular loading ACI should not be calculated with any error or warning message handled in the background when the RPO processes the cession, but the system should not abend

Declination Reason:

Workaround:

Root Cause:

Problem

SAR decrement field is not displaying correctly when creating a cession
Solution:

The ACIs on the historical ceded claim should be calculated using the value in the field 'ceded percentage' when the RCPO is run

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Visibility of business conditions depending on the security

Problem:

RPO is picking the cessions again even the retroceded date is set

Solution:

The RPO should not pick up the cession transactions that have the Retroceded Date updated
Any previously unplaced amount calculated on a transaction with the retroceded date already set should not be listed in unplaced assignments
 

Declination Reason:

Workaround:

Root Cause:

Problem:

Sequencing by the RPO when the system parameter 'Sequencing with Original Transaction Date' is not selected

Solution:

When sequencing the RPO based on the Sequence number always consider the Transaction effective date as the Original Transaction date

Declination Reason:

Workaround:

Root Cause:

Problem:
Abend when no transaction code mapped during the batch upload

Solution:
When the input file has only a transaction effective date and no transaction code:
If the cession benefit does not already exist, a new business transaction is created with the reinsurance start date and transaction effective date as per the mapped values
If the cession benefit already exists and the transaction effective date as mapped = next renewal date as per the renewal frequency, a renewal transaction is created
If the cession benefit already exists and the transaction effective date as mapped != the next renewal date, then an Other transaction is created.

When the input file has a transaction code but no transaction effective date:
When the cession benefit already exists and the input file has a transaction code= Renewal, then the transaction is created as a renewal transaction and the transaction effective date is defaulted as per the next renewal date

For any other transaction code, the transaction effective date will be defaulted as per the online functionality when the specific transaction code is selected.
 

Declination Reason:

Workaround:

Root Cause:

Problem:

Premium is getting reversed when ‘Other’ transaction is created without change in the SAR amount

Solution:

When an Other transaction is created on an inward or an outward cession (manually or through the RPO) and there is no change in the SAR (or any other parameter on the cession or IO that will result in a change of premium or other ACIs) then the transaction should be created without any ACIs being calculated

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Not able to add the assumed business on Retrocession Processing Group Order

Solution:

It should be possible to add an assumed business to the RPGO

Do not validate the classifications of the AB against the PPs that are included in the RPGO

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Abend when creating a duplicate insurable object manually

Solution:

If a duplicate IO is created either manually or through the cession loader with the same unique identifier then a error message 'Individual Insurable Object with the same identifier exists' and prevent it from being created

When this is created through the loader, the message should be answered as No and the record should fail

If the duplicate IO is created with only duplicate first name, last name, DOB then the existing confirmation message can remain as it is

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Abend when loading transactions without a transaction code

Solution:

When there are more than once transactions on the input file and the refrerenced cession benefit is a valid benefit for subsequent transactions then the transactions should be processed as mapped

When there is only a transaction code Renewal mapped, then the transaction effective date should be defaulted to the next renewal date

When there is only a transaction effective date mapped, then if the date = the next renewal date a renewal transaction should be created an if it is not = the renewal date then an Other transaction should be created

Any additional benefit that is created as a new business transaction on the same cession should be created as mapped

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Ceded Policy-Claim Event Date outside the Cession Benefit Expiry Date is not validated

Solution:

For all claims: When the claim event date is greater than the cession expiry date give the validation error CH0102 'Claim event date is greater than the benefit expiry date of the cession'

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Retention and Unplaced Amount are Incorrectly Calculated when Cession is created using an Additional Allowable Currency

Solution:
When the OCC has limits defined in a different currency than the cession currency and equivalent values are defined:
Convert the sum at risk on the cession into the main limit currency of the OCC. Perform all calculations using the exchange rates as per the Daily Rate.
If the calculated Sum at Risk < than the retention, then update the retention on the cession in the same currency as the inward cession
If the calculated SAR > the retention:

Calculate the Retention, Retro sum at Risk and Unplaced amount in the OCC currency.
Process the retrocession cessions with the retro SAR in the OCC currency
Calculate the retention and unplaced amount in the cession currency and update the existing fields

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Aim of function

The aim of the enhancement:

a) To be able to define parameters such as 'preferred life classification' that would be applicable to the joint life insurable object and use these parameters for validations of limits and any other calculation that are dependent on the joint life insurable object

b) To be able to define loadings applicable to the joint life insurable object

c) To calculate the accumulation based on the sum at risk of the primary life on the joint life cession

System Parameters Affected

None

Existing functionality affected

New tab for joint life insurable object:

• A new tab 'Joint Life Data' is available on a joint life cession benefit
• All fields in this tab are open for input/ selection and are independent of the values from the individual insurable objects that are part of the joint life cession
• When no values are specifically entered in this tab, all values from the individual insurable object which is flagged as the primary life will be copied to this tab

Please note that as per the current implementation, the Age fields on the Joint Life Data tab are informational and will not be used for any calculations or validations

Loading for Joint Life Insurable Object:

In addition to the loadings that can be imposed on individual insurable objects, it is now possible to add loadings that will be applicable for the joint life insurable object

Please note that any Age Loading will not be applicable to a joint life insurable object

Cession Loader- New Output Pattern Fields

• IS_JL_LOADING_ : This output pattern field will be applicable for the respective loadings that are applicable to the joint life loadings

Note: For a joint life cession benefit the Life for Loading should always be mapped

• New output data fields for the Joint Life Data are now part of the Cession Output Pattern. 
• When specifically mapped to a value, the values will be updated on the respective fields in the Joint Life Data tab. When not mapped, all fields, where available, from the Primary Life data will be copied to the Joint Life Data tab

Aim of function

The aim of this function is to allow the following additional statuses on Ceded Claims

• Ceded Outstanding
• Transaction Reversal

System Parameters Affected

None

Existing functionality affected

The following statuses will now be allowed on a Ceded Claim

• Ceded Outstanding: The ACIs will be calculated from the claim liability field or the mapped ACI amount using the Claim Reserve entry code for this status
• Ceded Outstanding to Ceded Paid : When the status of the Ceded Outstanding claim is changed to Ceded Paid the claim reserve ACIs will be reversed and converted into an actual loss entry code for the Ceded Paid status
• Transaction Reversal: This status will automatically reverse the last active claim status and reverse all ACIs and also automatically create a reversal transaction on the outward claims if any. Once the last active status transaction on the claim is reversed then the next Transaction Reversal status will cancel the claim and the claim status will be set to Cancelled

Aim of function

The aim of this enhancement is to be able to default all values including the Claim Liability Amount from the Decision Liability Tab of the Ceded claims and use the entry codes from the Calculation Model and Claims Entry Code Maintenance to calculate the ACIs when no ACI is specifically mapped

System Parameters Affected

None

Existing functionality affected

When no claim ACIs are entered or mapped, the value from the Claim Liability field will be calculated as the claim ACI using the respective default entry code

In addition to the defaulted ACI, it will also be possible to manually add other ACIs

Aim of function

The aim of the enhancement is to be able to create cession benefits with a benefit term of one day.

System Parameters Affected

None

Existing functionality affected

When the Short Term flag is selected on the cession benefit, it is now possible to create cessions with the benefit term of one day.

Aim of function

The aim of the enhancement is to be able to handle cession benefits that are entirely retained and entirely unplaced when the retroprocessing is done and to be able to view the unplaced amounts on the cession benefit

System Parameters Affected

None

Existing functionality affected

• A new field 'Unplaced amount' is available on the Retrocession Tab of the cession benefit

• The list of Unplaced amounts after the RPO run will now list fully unplaced cessions also
• Once a cession is listed as Unplaced, it will not be listed in subsequent runs of the RPO with the same Protection Program.

Aim of function

The aim of this enhancement is to use the cession reinsurance start date to process all retrocessions and validate the terms and conditions on the business when there are benefits on the cession that have different benefit start dates

System Parameters Affected

New system parameter 'Use Reinsurance Start Date for Retroprocessing'

Existing functionality affected

When the system parameter is selected:

When there is a cession that has more than one cession benefit which has a benefit reinsurance start date later than the cession reinsurance start date, then on running the RPO all benefits will be retroceded based on the cession reinsurance start date.

This will mean that even if the OCC has been terminated and the cession benefit start date is beyond the OCC termination date, the benefit will continue to be retroceded based on the cession reinsurance start date (if it falls within the active insured period of the OCC)

All the terms and conditions that the cession benefits will reference to will also be the terms and conditions linked to the insured period/ amendment effective period on the OCCC within with the cession reinsurance start date falls in

When the system parameter is not selected:

Each benefit will be retroceded based on the benefit reinsurance start date of the cession benefit. If the cession benefit start date falls outside the active insured period of the OCC then it will not be retroceded even if there are other cession benefits on the same cession that have been retroceded through the same OCC

Aim of function

The aim of this enhancement is to be able to process retrocessions on inward cessions where the sum at risk = 0 and use the ceded percentage to only retrocede premiums

System Parameters Affected

None

Existing functionality affected

Only on cessions where the Ceded flag is selected:

It will be possible to create cession benefits with the Sum at Risk entered as 0 and add premium and other ACIs manually

When the Retrocession Processing Order processes the cession benefits and the outward business is a quota share contract, then the ACIs from the inward cession benefit will be retroceded using the quota share percentage and the retrocession cession will be created with the retro sum at risk = 0

A new field Ceded Percentage will be available on the inward cession to pass the ceded percentage that needs to be used while processing the retrocessions and this value will be used when the outward business is not a quota share

Aim of function

The aim of this function is to be able to capture the value for 'Deductible' and 'Payment Ratio' on the cession benefit 

System Parameters Affected

None

Existing functionality affected

A new field 'Deductible' and 'Payment Ratio' are now available on the cession benefit transactions

The fields are also available as output pattern fields on the cession output pattern