coog version 22.41 released

In the latest version of coog, coopengo announced the start of the development of collective health and provident contributions. In coog 22.41, the call mode for these self-billed collective contributions is now finalized!

We have added the notion of call mode to the product and contract levels. New call modes have been created, such as the blank contribution call and the self-billing call. The latter allows the calculation of receipts based on actual collections. The data communicated is adjusted at the end of the year.

Two other particularly useful new features, covering both individual and group business, for all business lines (Loan Insurance, Health and Personal Protection):

• Generate and apply amendments en masse without having to go through each individual contract, thanks to the new contract amendment template,
• Create a task manually and assign it to a coog user with the creation of the task mechanics module.

Oct. 14, 2022 Release notes

coog Back-Office

Product settings

• When setting up formulas in a product, it is now possible to set up complementary formulas. In coog, either the product has no formulas and the user assembles the coverages himself, or the product has formulas and the administrator must subscribe to a formula. And a formula can entitle the user to subscribe to a complementary formula.
  • In the example below, the Premium plan contains three mandatory benefits (Death, Disability and Permanent disability) and one optional benefit (Total disability). This Premium package entitles the policyholder to subscribe to a complementary assistance package that includes domestic help and childcare.

To sum up, coog 22.41 allows you to add, validate and subscribe to complementary formulas, not forgetting the evolution of the formula management rider.

• A filter has been added to the formulas in the Product Lab to prevent the display of formulas linked to products other than group products: the screen only displays formulas linked to group products.

• Distinguish between statuses for each product configuration validation area: there are now three statuses “Draft”, “In validation” and “Valid” for the three configuration areas (subscription, pricing and service).

Contracts

• Addition of a warning message when modifying a formula that is subscribed by at least one contract. If the parameters of a formula are modified and there is at least one subscribed benefit that is not in “no effect” status, a warning message is displayed:

“Guarantees have already been subscribed with this plan; modifications may cause an inconsistency in the settings”.

• Copy and validate additional data from formulas on contract coverages: this involves copying the data defined in the formulas onto the coverages, and adding a validation to check that they still comply with the product’s parameters.
• Validate contract benefit formulas to check contract and formula consistency: add a validation function for benefit versions in relation to formula settings (compliance with compulsory/optional benefits, supplementary/main formulas, supplementary data, etc.).
• Link the version of a benefit to its formula: in the contract’s “Coverage” tab, each benefit is linked to the formula on which it depends.

• Added the ability to add multiple discounts, cancel discounts and change their date in the commercial discount creation wizard.
• Management of overlapping excluded benefits: ability to define a list of other benefits (trans-product) on a benefit, in order to prohibit overlapping benefits in the event of coverage on several contracts.
• Addition of configurable icons on risk descriptors used in the form view of contracts.
• Wizard-based selection of contracts to be transferred to a new set of existing contracts.
• Unfold the elements covered view as soon as the use is selected in the additional data update wizard: when opening the wizard to update additional data by use (from the “Update additional data by use” action), by selecting the use, each level of additional data unfolds automatically.

• The new “Update additional data by use” action is available from the “Contract” entry point. This new feature allows you to make changes to additional data for each use (the use identifies the context in which the additional data is used).

Endorsements

• Enable you to generate and apply mass endorsements from a contract modification template: this functionality enables you to configure a “contract modification template”, for example to terminate coverage on all contracts taken out from a given product. Practical example:
  • You decide to remove a warranty from a product.
  • We’re going to modify its settings so that the benefit is no longer offered for subscription.
  • However, on 01/01/2023, we also want to terminate it from all active contracts underwritten using this product.
  • Thanks to the ‘contract modification template’, we can generate mass amendments without having to go through each of these contracts.

• As part of this mass rider logic, it is also possible to generate requests for printing documents on contracts via modification templates. In fact, the mass rider generation function is also capable of generating mass mailings: it is now possible to very simply send a mailing to policyholders for a given product.

• When a product’s parameters are changed (for example, when a warranty is added), the updates are applied to all or part of the existing contracts (existing stock). A message is displayed to alert the user before the action is taken.
• Management of additional formulas within the framework of a contract in the process of being underwritten, and of an endorsement on the formulas of the elements covered by a contract.

• Addition of a step in the “option management” rider to manage the formulas of the elements covered by the contract.

• Be able to modify a legal entity’s administrative information by means of a rider (entry point for initiating a legal entity rider).

Quotes

• The special clauses of a contract are now read-only when the contract’s quotation status is validated.
• Addition of the “Declined estimates” tab in the “Estimates” entry point for declined estimates, and their removal from the “All” tab of the “Contracts” entry point (individual).

Group contracts

• When an individual is a member of a group policy, his or her claims summary is enhanced with the following information:
  • Contract number(s)
  • For each contract, the parent population group of the person concerned
  • At the next level down, the legal entity to which the individual is affiliated.
  • For each of these levels, the effective dates

• Update the list of risks covered when the subscribing legal entity changes during the contract creation process.
• Added the possibility of managing subsidiaries when the contract is active: instead of using an endorsement, it is now possible to add subsidiaries directly from the active contract.

• Creation of an affiliation process for group contracts: from the contract, affiliation is possible with an input and validation process. The first step is to set the risk descriptor to create the individual.

• Improved wizard for affiliating third parties to a covered company.

• Display the risks of subsidiaries already covered in the wizard for adding subsidiaries to a contract: as part of the underwriting process, it is possible at the “Personnel category” stage to view the elements covered and rectify any errors.

• Displays contract, covered entity and population information after adding subsidiaries during the underwriting process in the created covered elements view.

• Creation of a wizard for adding subsidiaries to a contract.

• Display additional risk descriptor data at contract level to quickly identify contract population groups. In the example below, the additional data are the college, the status of insured persons and the plan.

Claims

• Handles the case where the effective date of the amendment to the global benefit account is equal to the initial effective date of the contract.
• Calculate the reason for rejection from the benefit eligibility rule.

• Addition of a shortcut to claims from a claim reimbursement: Added “Claims” to the “Relation” button menu, making it easier to access the associated claim from the “Claim reimbursements” tab.

• Addition of an optional “maximum amount” argument to the “Calculation of prorated periods for an amount” rule engine function.

• Added support for the CTIP concentrator in the Prest’IJ module.
• Improved non-regression scenarios, in particular for checking claims forms for insurers.
• Configuration of individual Prévoyance benefit management tools in the rule engine, to enable easy parameterization/maintenance of annuity-type benefits:
  • • Creation of default annuity benefit rules in the coog product;
    • Creation of a Non-Regression Test (NRT) base for individual provident benefits (annuities) and medical analysis, in order to have a complete business tool.
• Enable the date of death of an insured to be updated when the date of death damage changes.
• Automatic filling of the injury descriptor if the current claim has only one possible injury descriptor.
• Delegation of action differentiable by object added: it is now possible to delegate the control and validation of claims to other users, whatever the method of settlement.

Health

NOEMIE

• Let the user choose which covered elements of a contract to “renoemize”.

almerys

• Allow overloading of the risk carrier in the almerys flow.
• The recalculation of delegation periods must be triggered even if the contract is terminated, as long as the endorsement takes place during the coverage period. This means, for example, that coog sends a flow back to almerys.

Billing

Contributions

• Addition of a warning message when generating a direct debit on a contract with a payment suspension in progress.

• Discharge of contracts by item covered: a new setting lets you define the level at which contracts are discharged (for each period or by item covered).

• Added management of the processing date parameter (in working days or not) on the release batch chain.

Group contract contributions

• Addition of an entry point for group call slips.
• Added a statement entry wizard for call slips.
• Order call slips by descending start date.
• Verification of breakdown rates entered on a contract.
• Modification of the values expected in the additional data for breakdown rates by the default breakdown rule: the rule now expects values to be expressed as a percentage.
• Added the possibility of self-billing for the manager.
• Improved ergonomics of the warranty view for self-billing.
• Possibility of using lines from parent company / related third parties for self-billing payment.

Payment

• Filter payments by reason for rejection.

• Third-party management of a beneficiary’s legal representative. This representative can collect benefit payments or reimbursements on behalf of the beneficiary. Example of use: transfer of a contribution refund to a research firm following the death of a policyholder. The firm is the policyholder’s legal representative.

• Premium exemption rules can now be set so that users manually determine the exemption rate when entering the exemption period.

• Improved processing of withholding tax return files
• Verification of the existence of the information used by direct debit payment methods before applying the amendment modifying the payment method.
• A new setting in the statement journal allows you to choose whether the accounting date for transactions generated by a statement will be the statement date or the line date.

Commissions

• Addition of the “Bordereau Assureur” business type to the list of supplier invoices.

Documents

Desktop publishing

• Make it possible to configure the type of event issued when a mail is generated. This adds flexibility to the parameterization of actions by event type, depending on the model of mail printed, if you wish to chain them with other actions.

Reports

• The reports module now supports timestamp data.
• An entry point has been added to provide a global view of company management departments.

Task management

• Creation of a task module and task mechanics that allow you to create a task manually and assign it to a coog user. For example, to handle an insured’s telephone claim.

Rule engine

• Quotation status” added to rule engine: when setting up a rule, it is possible to use quotation status as a variable by retrieving it from quittancement.

• Added functions in the rule engine to access subscribed formulas for covered items.

• The “Number of items covered for warranty” rule engine function now accepts an optional parameter, enabling filtering of covered items with specific additional data. For example, the optional “date” parameter can be used to count covered items active on that date.

• Addition of a function in the rule engine to calculate the deferment period of a loan in months (Borrower’s Insurance).
• Added a warning message when attempting to use technical fields in a rule.

• Enhancement of rule engine functions so that messages returned by rules can contain more information.

• Added the possibility of using a rule to calculate charges (e.g. administration fees) on contracts. Fees can be dynamic, as in the case of guarantee premiums, for example. It is also possible not to apply fees automatically and dynamically.

Technique

Batch

• Import Zip archives via parameter import batch.
• From the “Batch plan configuration” entry point, in the “Condition” field, new values for the batch processing date are available.

• Relaunch a batch plan from a chain: a button has been added to relaunch a batch chain.
• Addition of a help message on the environment parameters overload field on batch configurations.
• In the “Batch configurations” entry point, a help message has been added to explain the purpose of the “Overwrite environment variables” button.

• Added a batch to clean up old batch logs.
• Creation of a batch to purge previous batch executions and operations, with a retention period. This batch is run every day.

• Addition of a processing completion method at the end of batch runs/chains/batch plans.
• Simplified batch status fields
• It is now possible to launch batch chains from within the application, transforming the daily chain into a task.
• Added batch configurations for pre-payment returns.
• Added batch for managing the creation, validation and issue of call slips.
• The recalculation endorsement batch can now be run in parallel: receipts are cancelled but not recreated. Receipts must be created and issued via dedicated batches.

Security

• As solution administrator, set up automatic password expiry and minimum password complexity to guarantee maximum security for access to the coog Back-Office.

RGPD

• Access control models are now technically historized.

coog-API

• v1 APIs are deprecated as of version 22.41, in favor of GraphQL lookup APIs. They will be permanently removed as of coog 23.14 (next major release). The reasons for this change are as follows:
  • Strong dependency on the data model, which introduces the risk of regression when updating the Back-Office application,
  • Impossibility of consulting data “in depth”, which implies a multiplication of calls to retrieve all the desired data, and therefore inadequate performance,
  • For modifications, risk of incomplete processing of requested changes due to the absence of a transactional process.

• The use of GraphQL for data queries addresses all three of these issues. The functional scope currently available, which has been gradually built up since coog version 2.8, covers standard requirements, including in particular the creation of a “policyholder space” website (consultation of contracts, payment deadlines, etc.). For modification / simulation operations, the corresponding APIs have been implemented in API v2.

Please contact your account manager to discuss the changes to be made to the APIs for your next version upgrade.

• Change database from Redis to MongoDB for architecture purposes.
• Pass without action an endorsement and expose this endorsement data via API.
• Execute the coverage amount rule for a warranty, when this does not depend on contract information: this enables the Front user to select the coverage amount proposed for a warranty.
• Enhanced the configuration of our partner Paybox by Verifone’s secure payment service with the addition of payment redirection URLs (success, refusal and cancellation).
• Creation of an API for manual statement creation.
• Enable queries on benefit bank account endorsements via the GraphQL API.
• Added filter criteria to GraphQL calls in the distributor area (B2B): it is now possible to refine the search for a third party by filtering on the basis of the insured’s surname, first name, date of birth and Social Security number. In this case, the search must return only one third party. A consistency check has been set up to detect an error if more than one third party is returned. The search must be performed as follows:
  • With code only
  • Call with Last name, First name, Date of birth
  • Call with Social Security Number
  • Call with Social Security number, First name, Date of birth
• Addition of risk analysis fields for the GraphQL API in the distributor space (B2B).
• Enrichment of the policyholder area (B2C) GraphQL: addition of payment types available for a contract: a new method has been added for the payment creation API so that coog can choose the dematerialized payment method for a contract.
• Extraction of additional quote details in API.
• Fields added for GraphQL API in B2B distributor space: document lines requested.
• Manage additional loan-to-value data in API for Loan Insurance.
• Enable queries on discharge information endorsements via the GraphQL API.