Release documentation - Life - Enhancements and requests

Problem:
Incorrect Accounting Classification being created and selected by Retrocession Cession Order while creating the worksheet

Solution:
1. Do not copy the accounting classification from the inward cession/ business to the outward bookings worksheet when the retrocession cession order is run
2. If there is only one Accounting classification on the outward business section to which the retrocession cession is linked, then default this AC to the bookings created by the retrocession cession order
3. If there is more than one valid AC on the outward business section to which the retrocession cession is linked, then do not close the worksheet and allow the user to select the AC on the worksheet detail before closing it
Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Reinstatement ignores transaction number and renewal after reinstatement is not retroceded

Solution:
ONLY when the system parameter 'Allow transaction number on cession transactions' is selected
Allow the transaction number to be updated on a reinstatement transaction also
This should be possible for both manual cessions and cessions transactions created through the loader
The reinstatement transaction number should be copied to the retrocession cession and the placement

No other field on the reinstatement transaction should be editable except the transaction number field.

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

When one of the AC in a Business is marked as 'Default', all the others disappear from the list

Solution:

When an accounting classification is marked as Default on any business section- Agreement section or child sections- when the flag Display Valid and Active classifications only is selected, all the valid and active accounting classifications should continue to be listed when viewing the ACs from the respective sections

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Issues found for the cession on SR Decremental basis when the Our Share flag is selected

Solution:

Any Sum at Risk Decrement when it is automatically calculated should be applied to the Sum at Risk amount on the previous transaction

When the transaction has been reinstated then all the factors/ parameters that are involved in the calculation of the Sum at Risk- eg Reserves, Elapsed Duration, Mortgage decrement factor, SAR decrement factor etc should be reinstated as per the reinstated transaction
Any further transaction that happens after the reinstatement should continue using the values from the reinstated transaction

This should happen irrespective of whether the Sum at Risk was created by applying the 'Our Share' percentage from the Share condition of the business or not

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Accounting Information from teh accounts created from ACIs not extracted.

Solution:

ACIs included in a Cession Worksheet has FK_LEDGER_DETAIL that can be used to join BOAC_LF_FACT.
Implement this join.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
We have a life universe issue where a client would like to look back in time and see specific benefits on reports. Attached is our issue and an example.
Solution:

object added.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Use the 'Accounting Year/Period' of the booked Accounts to refer to the linked ACIs and report on the Policy Benefit transactions and Claims

Solution:
Object for AYRP from linked account,

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Multi GAAP calculation functions 'Portfolio Estimates for Accounting Period' and 'Portfolio Estimates for Accounting Period (default)' does not retrieve correct values when Protection Basis is 'Yearly'

Solution:

For Yearly projections, the functions should retrieve the Default Period Estimate value (on the Portfolio Program) for the year and period corresponding to the year and period shown in the Period Estimates header on the business when Estimation View = Accounting Year

Workaround:

Root Cause:

Original implementation

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

• Problem:*
  Commission is not reversing for the Lapse transaction after Renewal

Solution:

For all termination transactions- where the unearned premium returnable option is applicable, all ACIs - Premiums, commissions, other deductions -should be calculated for the reversal transaction as per the definition on the AC condition.

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
For Single premium commission is not calculated for the Loadings
Solution:

For all Single Premiums - calculate the commission on the loadings as defined for the entire single premium
If there is any Other transaction on single premium cessions where there is a premium calculated, the commissions for the respective premiums should be calculated for the actual premium ACI- both basic premiums and extra premiums

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

No validation of base company against the assumed business added to the cession renewal order

Solution:

Disable the option 'Add Business' or 'List Business' on the Cession Renewal Order if a Base Company is not selected

If the user for some reason manages to add a business that does not pertain to the selected base company (by deleting the defaulted base company then adding a business) give a warning message ' Base company of the selected Assumed Business does not match the Base company of the Cession Renewal Order. Do you want to continue' - Yes will add the business and process the cessions. No will cancel the Add business operation.

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
The Life cession loader with a sizable upload file on a large existing database is slow. The referencing step takes a particularly long time.

Solution:
Testing of the performance in a dedicated test environment with sizable data comparable to a client's production environment to be done to track and monitor performance

Workaround:
Root Cause:
Extent of Impact:
Impact on Existing Data
Recovery Method for Existing Data Affected

Problem:

Life MTK does not support Period Estimates

Solution:

The Life MTK loader is to be enhanced to support handling of migration of Period Estimates

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
RPO sequence is wrong acording to rider becuase of incorrect cession number

Solution:

When the system parameter 'Cession Benefit Identifier series in use' is selected then the cession loader should always assign the first cession benefit identifier to the base benefit and then to the remaining riders
When the RPO is run, the Base Benefits should always be processed first and then the riders even if the benefit covered is the same on different cessions

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
The selection for the fields 'Financing Reinsurance Arrangement' checked in the OCC of life cannot be taken to the state 'Financing Reinsurance Arrangement' in the ORP

Solution:

Copy the selections from the option 'Financing Reinsurance Arrangement' and Financial Risk/ Re Combo from the OCC to the placements and from the RP to the IABs when the options are selected on the parent business

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

When adding a new Projection on a business which already have at least one Projection, overwritten values on the previous Projections are not kept on the new Projections

Problem only when manually creating new Projections. It works fine when running the Protection Calculation Order

Solution:

When adding a new Projection on a business which already have at least one Projection, any overwritten values on the last existing Projection should remain the same on the new Projection, and Ow. flag should also remain as Yes on the estimation item(s) on the new Projection

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Business list in Multi GAAP Retrocession Order are not always correctly refreshed when the Order is saved

Solution:

Make sure the business list always shows the correct listing as soon as the Order is saved

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Full recapture transaction on retrocessions is creating as per the RPO effective date

Solution:

When the Calculation Frequency in the PM condition is defined as Original then the effective date of any termination transaction on the retrocession cession should be the same as that of the inward cession's termination transaction
The effective date on the RPO should be used ONLY to pick up the valid cessions up to that date

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

To enable relation of aggregate entries to same entry code groups as their originating entry codes.

Solution:

This case was previously reported and solved as 4.9.2 Hotfix SICSR17038, however in version test 21.2 this fix is not included.

Problem:
RPO not picking up Joint Life Benefits when part of a cession
Solution:

The RPO should process the retrocessions on all the benefits on a cession benefit irrespective of whether it is an individual life or joint life cession

Declination Reason:

Workaround:
Create each cession benefit as a separate cession with the same policy number and different cedent cession numbers

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Abend when running the They bill cession Order from TW
Solution:

The They Bill Order should run without abend and pick up any valid cession benefit ACIS that fall within the dates on the order

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Extra Mortality Premium Calculation is incorrect on the retrocessions is not correct when the reason for loading is 'above free cover limit'

Solution:
When the reason for loading is Above Free Cover Limit always take the Inward ACI (for Extra Mortality Premium) and multiply by the Retroceded share%
This should be done when the PM condition on the OCC is risk premium or original

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Error messages when running the Retrocession Cession Order

Solution:

Only the released ACIs that have an As of Date that falls within the Acct As of Date From and To (both dates included) should be picked up when running the Cession order or the Retrocession Cession order
When there is no As of From Date- then all Released ACIs that have a date that falls within the As of To date (date included) should be picked up by the CESSION ORDER AND RETROCESSION CESSION ORDER and the status should be changed to included

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Deduction ACI not calculated when Transaction Type = Increase/Decrease

Solution:

For ANY Premium ACI that is calculated on any type of cession transaction whenter it isBasic premium or extra premium, if there is any deduction defined on the Deduction conditions that deduction should be calculated on the calculated premium ACIs

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Error when Calculating the Prorated Premium since Premium Paying Term is incorrect

Solution:

When the Premium Paying Term is not explicitly mapped in the loaded batch, default the value from the benefit term to the premium paying term on the cession benefit

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

'Document Category' option is not required on Attachment form if 'DMS Interface' is not enabled.

Solution:
Prequsite:
if on System Parameter for 'Document Handling'
check 'Enable DMS interface for Attachments' is not enabled.

Then On Attachments form Label 'Document Category' and drop down will not be shown.

Currently, Label 'Document Category' and drop down are shown irrespective of option 'Enable DMS interface for Attachments'. <<ERROR>>

Problem:

Subsequent RPO Keeps creating incorrect transactions on a Fully Recaptured Retrocession

Solution:

Once the Retroceded Date has been updated on a cession benefit transaction the RPO should not pick up the cession benefit in subsequent runs

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Multi GAAP Retrocession Order is missing in Extended Booking Terms

Solution:

Make sure Multi GAAP Retrocession Order is available to select in Extended Booking Terms. When selected, the period(s) open in Extended Booking Terms should be used instead of general booking terms

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Renewal After Reinstatement is not Retroceded Correctly

Solution:

ONLY WHEN THE CEDED FLAG IS SELECTED:

1. Allow any termination transaction to be created with a transaction effective date later than the latest effective period. (The message LCH153 should be answered Yes by default) - Existing functionality

Set the inward cession to inactive - Existing functionality-

eg:

NB = 1.1.2016 to 31. 12. 2016

Renew 1= 1.1.2017 to 31.12.2017

Renew 2= 1.1.2018 to 31.12.2018

Lapse = 1.1.2019 which will set the cession to inactive and the effective period for this Lapse transaction will be displayed as 1.1.2019 to 31.12.2019

2. Do not update the retrocession cession that is linked to this cession. When an RPO is run this inactive inward cession transaction should not be picked up by the RPO even though the Retroceded Date is not set- Existing functionality

3. When the inward cession is reinstated create the reinstatement with the same effective date as the termination date in step 1- Existing functionality

The inward cession should now be set to active and the effective period of the reinstated transaction should be - Existing functionality.

Reinstatement = 1.1.2019

Now the cession is active with the transaction code as 'Reinstatemnet' and will have the effective period as

1.1.2019 - there will be no end date.

4. The Reinstatement transaction should NOT be picked up by the RPO

5. When a renewal transaction is loaded on the inward cession renewal transaction effective date as per the mapped value (Here again LCH0153 will be answered as yes) should be accepted and the cession OR the renewal date should be defaulted to 'Renewal Date just passed'

6. When the RPO is run again all the active transactions AFTER the Reinstatement transaction should be picked up by the RPO and processed as per existing functionality. The RPO should ignore any Termination or Reinstatement transaction prior to the latest active transaction even if the Retroceded Date is not set.

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Incorrect effective period dates when retro new business is created from a renewal on the inward cession

Solution:
ONLY WHEN THE CEDED FLAG IS ON
When the RPO is run and it picks up a transaction on the inward cession to create a retrocession new business transaction (since the SAR of the inward transaction is now greater than the retention) the effective period of the retrocession transaction should be the same as the effective period of the linked inward cession transaction

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Unable to create cessions linked to an earlier amendment after coverage/classification amended

Solution:

When a cession benefit transaction is created the effective period within which the reinsurance start date / transaction effective date falls should be used to reference to the agreement section and the classifications within the section 

When a technical worksheet is created the agreement sections that are listed for selection should pertain the the selected amendment

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

The drop down for Estimation Basis in Multi GAAP / General system parameters is almost not visible if screen resolution is 125%, 150% or 175%.

Solution:

Make sure the drop down is always fully visible

Workaround:

Root Cause:

SE-6452

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

'Original AYP' column not displayed in the Business Ledger of Non Prop Business

Solution:

The column 'Original Accounting Year' and 'Original Accounting Period' should be available on the business ledger details container on all types of business- both Proportional and Non-Proportional, both inward and outward, when the flag 'Original Accounting Year an Period' is selected on the Insured Period tab of the business.

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Aim of function

1. When the Original Accounting Year and Period flag is selected on an Assumed Business or OCC and where bookings are made with values in the OYRP fields, it should be possible to view the Online Statistics for both actual and estimates based on the Original Accounting Year and Period as one of the criteria
2. When the Projection Basis = Yearly AND the Original Accounting Year and Period flag is selected on the business, the Accruals will be calculated as the estimates for each year in the Period Estimates, less the accounted amounts for each corresponding Original Accounting Year.

System Parameters Affected

None

Existing functionality affected

Business Online Statistics:

• A new selection criteria option 'Original Accounting' is available on the Business Online Statistics. 
• When selected (or set as default as per the user preferences) the online statistics for both actuals and estimates are displayed based on the Original Accounting Year and Period of the bookings made on the business/ businesses included in the statistics view
• If the business included in the statistics view does not have the Original Accounting Year and Period flag selected or bookings that have been made do not contain values in the respective fields, then the statistics will not be displayed for those bookings

Multi GAAP Accounting Order and Multi GAAP Retrocession Order:

• Normally when Projection Basis = Yearly, the Multi GAAP Accounting and Retrocession Orders calculate Accruals as the Period Estimate amounts for each year, less the accounted amounts for the corresponding Accounting Year. However, when the Original Accounting Year and Period flag is selected on the business (Insured Period tab), Accruals will be calculated as the Period Estimate amounts for each year, less the accounted amounts for the corresponding Original Accounting Year. In addition, Original Accounting Year and Original Accounting Period are populated on the Accrual details. They are set equal to the Accounting Year and Accounting Period.

Aim of function

The aim of this enhancement was to use the Coverage Indicator defined on the cession benefit to prioritize cession benefits during the retroprocessing

System Parameters Affected

None

Existing functionality affected

When there is more than one cession benefit on the same life having the same benefit covered and all the cession benefits have the same reinsurance start date, the benefits having the coverage indicator 'Base' will be retained on priority over the 'Rider' when the Retrocession Processing Order is run

When the Coverage Indicator is None or Unknown then there will be no sequencing of the cession benefits within the same reinsurance start date.

Aim of function

The aim of this function is to allow the flow of estimates and actual bookings that have been made on a technical worksheet from the inward business to an outward business that is attached to the Proportional Protection Assignment as a QSR OCC even when the accounts administration basis on the business is Individual

System Parameters Affected

None

Existing functionality affected

Entry Codes:

Only in SICS Life, a flag is available on the entry code 'Allowed in Retroaccounting when Acct Admin basis is Individual'

When this flag is selected, any actual bookings made on an inward business where the Acct Admin Basis is individual will flow to the linked outward business as As Original bookings, similar to a bulk administered business.
Irrespective of this flag, all estimates will always flow to the outward business

Proportional Protection Assignment on an Assumed Business:

When the Quota Share Retrocession flag is selected, it is now possible to attach an OCC that is part of a Protection Program as a Quota Share Assignment, but only when the flag 'Retro Accounting Only' is selected

When an OCC is linked to the AB with this flag selected, then all estimate bookings made on the inward business and all actual bookings made with entry codes flagged as ''Allowed in Retroaccounting when Acct Admin basis is Individual' will flow from the inward business to the OCC as As Original bookings similar to a Bulk Administered business.

This will not impact the cession ACIs and all cession and claim ACIs will be included in accounting through the We Bill/ They Bill processing as per the definition on the business.

Aim of function

The aim of this enhancement is for the Retrocession Processing Order to pick up all cession benefits within the cession even when one benefit pertains to a joint life and the other benefit pertains to a single life within the joint life insurable object

 System Parameters Affected

None

Existing functionality affected

When the cession is a joint life cession and the cession benefits within the cession pertain to individual lives, joint lives or/ and both, the Retrocession Processing Order now  processes all the cession benefits and creates the retrocession cessions for each benefit 

Aim of function

To be able to navigate from the cession batch to a Reinsurance Program
To be able to find cessions linked to a Reinsurance Program by selecting Reinsurance Program as the level of business in the Find Cessions window

System Parameters Affected

None

Existing functionality affected

Find Cession window:

It is now possible to select a Reinsurance Program under the Agreement and find all cessions linked to all the Assumed Businesses that are part of the Reinsurance Program

Cession Batch :

When a cession batch is created using a Reinsruance Program, it is now possible to click on the Business icon on the batch to navigate to the Reinsurance Program

Aim of function

When an input file has duplicate column headers or blank column headers, during the Import and Retrieve process, the cession batch loader should not throw exceptions and allow the user to process the file by defaulting values to the duplicate or blank column headers

System Parameters Affected

None

Existing functionality affected

**During the cession loading process:

• When the input file has duplicate column headers, during the import process the duplicate column headers are updated with the column header name appended with _1
• When the input file has blank column headers, during the import process the blank column headers are updated with a header BLANK_1, BLANK_2 etc.
• Any leading and trailing spaces in a column header is ignored

Aim of function

To be able to input a Reporting Date on the cession batch while loading the data source and default this date within the input pattern block in the  mapping.

To default the Reporting Date on the cession batch to the created cession benefit transaction

To default the date on which the batch was successfully closed as the 'Created Date' on the cession benefit transactions that were created by the batch

 System Parameters Affected

New system parameter 'Reporting Date mandatory on Cession Batch'

When this parameter is selected the field Reporting Date is mandatory 

Existing functionality affected

On the cession benefit transaction a new tab 'Dates and Sequence Options' is available

The value from the Cession Batch is defaulted to 'Reporting Date' and the date on which the batch was closed to create the cession transaction is defaulted to 'Created Date'

The field Reporting Date is not mandatory on manual cessions irrespective of the system parameter.

Aim of function

The aim of this enhancement is to be able to load a cession with the same policy number as a new business transaction without having to do a reinstatement after a cession has been terminated with a 'Ceded in Error', 'Setup in Error' or 'Cancelled from Inception' transaction

System Parameters Affected

None

Existing functionality affected

When a cession benefit is terminated from inception through a transaction such as 'Ceded in Error', 'Setup in Error' or 'Cancelled from Inception' and there are no more active cession benefits on the same cession, then the policy number on the cession is updated with the termination transaction appended to the policy number.

This way, when the same policy number is loaded and processed again through the cession loader as a 'redo' transaction which is a fresh New Business transaction, the existing cession is not referenced again and a new cession can be loaded without having to reinstate the previously terminated cession.

The terminated cession will not be part of any accumulation calculations when the RPO is run

Aim of function

The aim of this function is to never calculate unearned premium on a cession or retrocession cession benefit when the termination is due to a maturity transaction

System Parameters Affected

None

Existing functionality affected

On the Agreement Clauses condition on the business a new option 'Unearned Prms Ret.Exc. Maturity is available

When this is selected, the unearned premiums will be calculated and returned based on the Pro Rata Return Type selected for all termination transactions except when the termination transaction on the cession benefit is Maturity or Maturity by Marriage

Aim of function

The aim of the function is to be able to define the benefit term and premium paying term in days only and use this value to calculate the premiums when the linked premium rate table is defined in days

System Parameters Affected

None

Existing functionality affected

A new flag 'Short Term' is available on the Group Information Tab

When this flag is selected, it will be possible to enter the benefit term and the premium paying term in only days and not years

When there is a corresponding premium rate table linked to the business where the rate is defined with benefit term in days as one of the parameters, then the premium on the cession benefit will be calculated using the days value in the benefit term/ premium paying term field

The flag 'Short Term' will not be selected by default and when this is not selected, it will not be possible to define a benefit term of greater than 365 days as per existing functionality

Aim of function

The aim of this function is to be able to define a percentage on the claim and use this value to calculate the claim recovery, overriding the original ceded percentage on the cession benefit

System Parameters Affected

None

Existing functionality affected

For a claim with a status of 'Ceded Paid' AND the Liability is selected as 'Partial Payment' and a value is defined in the field For Payment % , then when the Retrocession Claim Processing Order is run, the recovery claims will be created by applying the value in the field 'For Payment %' to the inward claim ACIs

The value in the 'Ceded %' on the linked cession benefit will not be considered for calculation of the retro claim ACIs

This is applicable ONLY to claims with the status of Ceded Paid

Aim of function

The aim of this enhancement is to be able to handle the ES condition and the period estimates through the MTK functionality

System Parameters Affected

None

Existing functionality affected

It is now possible to export and import Period Estimates through the MTK loader

Aim of function

The aim of this enhancement is to be able to create an Adjustment Reversal transaction on a Ceded Paid Claim and reverse any Retrocession Claim that was recovered

System Parameters Affected

None

Existing functionality affected

When the existing system parameter 'Allow transaction number of cession and claim transactions is selected'

• It is possible to define a mandatory transaction number on all Ceded Paid claims, the number is defaulted as 1 and can be overridden. This field is optional on non-Ceded Paid claims.
• A new transaction 'Adjustment Reversal' is available on Ceded Paid claims, both manually and through the loader
• When an Adjustment Reversal is created on an inward Ceded Paid claim, the adjustment reversal transaction is created for the transaction number specified and all linked outward Ceded Paid claim transactions are also reversed automatically
• It will be possible to have more than one Ceded Paid transaction on a Ceded claim and when reversed, each Ceded Paid transaction will need to have its corresponding Adjustment Reversal transaction 
• The reversed transactions will have the same as of date and ACIs as the source transaction, but with the reversed signs and the release indicator will be Released. 

Aim of function

The aim of this function is to be able to process and recover ceded paid claims when the claim event date of the ceded paid claim falls outside the active cession effective period

System Parameters Affected

None

Existing functionality affected

Creation of Ceded Paid Claims

It is now possible to create a claim with the status of 'Ceded Paid' where the claim event date is later than the latest active effective period of the inward cession benefit.

This will not be possible in the following scenarios:

• When the status of the claim is NOT Ceded Paid
• When the status of the claim is Ceded Paid, but the Liability Reason is Installment Recovery or Lumpsum Recovery

Retrocession Claim Processing Order

When the Retrocession Claim Processing Order is run and the retrocession claims are created and there is no active effective period on the inward cession for the claim event date and therefore no linked retrocession cession, then the Ceded % from the last active effective period is used to calculate the retro claim ACIs 

Aim of function

The aim of this function was to test and analyse the cession loader performance 

System Parameters Affected

None

Existing functionality affected

None

Aim of function

When a termination transaction is created with the transaction effective period that is later than the effective period end date of the latest cession transaction, the RPO does not pick up the termination transaction to process a Full Recapture. The aim of this function is to be able to process the termination transactions with the transaction dates outside the latest effective period

This epic covered the specification of the functionality to be implemented to support the above mentioned requirement

System Parameters Affected

None

Existing functionality affected

None

Aim of function

The aim of this enhancement is to be able to process and recover all the installments that are due to be paid on a later date as a lumpsum amount if a death claim is reported on the cession benefit where the payments are currently being paid out and recovered as installments

System Parameters Affected

None

Existing functionality affected

When a Ceded Paid claim is created with the Liability Basis selected as 'Installment Recovery', the outward claim is created with one Ceded Paid status for each installment that will be recovered from the reinsurer. 

When there is a death claim that is reported on the same benefit where installment recovery claims are being processed, one new inward claim transaction with the Liability Basis 'Lumpsum Recovery' will be created on the same Installment Recovery claim 

When this claim transaction is picked up by the RCPO. all the future installments that have the accounted status as Released will be deleted, and the claim ACI amounts of all these deleted installments will be summed up to create one Lumpsum Recovery claim status with the As of Date as per the payment due date of the RCPO that created the claim transaction