April 3, 2026 – Release Notes

To mark the release of this latest version of coog, we are pleased to share the following updates:

  • the new portal providing access to all documentation and information related to the use of our APIs,
  • enhancements to existing APIs,
  • the creation of new APIs, particularly for the HR portals of our end customers in group insurance.

We are also presenting regulatory updates. Several changes have been implemented for the DSN (Déclaration Sociale Nominative), specifically regarding the processing of payment and allocation reliability.

coog API

Creation of a new API portal

Need: to centralize all relevant information in one place for customers using coog APIs.

Update: A new portal is now available via VPN, providing access to all documentation and information related to the use of coog APIs.

  • REST Documentation – API v2 and v3
    • REST documentation is accessible via a Swagger/OpenAPI interface, featuring:
      • An unauthenticated mode allowing free browsing,
      • An authenticated mode allowing testing of endpoints.
  • GraphQL Documentation – API v4 (GraphiQL)
    • The GraphQL APIs feature a GraphiQL interface, allowing you to:
      • Explore the schema,
      • Test query requests.

Contracts

Contract API Enhancements

Update: Added the status (terminated, active, suspended) of the covered item to the contract APIs.

Use of PostgreSQL’s ROLLBACK TO SAVEPOINT for contract simulations

Requirement

Currently, certain processes are triggered upon transaction commit*. As a result, the first commit can trigger asynchronous processes while the original transaction continues to run. This leads to concurrent access issues between the original transaction and the asynchronous task.

Update: Use of the PostgreSQL database’s ROLLBACK TO SAVEPOINT mechanism.

*“Commit” is a technical term in PostgreSQL (database) that refers to the actual saving of a transaction.

Billing

Payment

New API for viewing claims reimbursements

Requirement: enable searching for claims reimbursements to display them in an HR portal.

Development

Creation of an API to view:

  • Reimbursement information (account.invoice),
  • Third parties (payment recipient and beneficiary),
  • The parent company,
  • Payment information (wire transfer/check, etc.),
  • Compensation details,
  • Line item information, including the link to the compensation period.

The filters for searching for reimbursements are as follows:

  • The billing date,
  • The payee on the receipt,
  • The parent company.

Claim

Enhancements to the Claims Creation API

Update: Creation of third-party relationships when creating claims files.

Tasks

Update to the “Create Task” action by event type

Context

When a task is created automatically as part of an event-based action or via the API, the task is created as a draft. It must be manually updated to the appropriate status.

Update: Ability to configure the task status in event-based actions to avoid manual processing.

Third Parties

New API for querying third parties

Update: Creation of an API to retrieve a third party’s COOG ID based on a search using the third party’s external identifier.

New API for adding external identifiers to contracts

Update: Ability to add contract identifiers during the contract’s lifecycle.

Propagation of address changes to third-party amendments via API

Update: Recording of an end date set to D-1 for the old address when entering an address change amendment.

Propagation of address creation to related parties via API

Update

Propagation of an address change amendment to all third parties associated with the policyholder.

In practice, the API user is in control. They list the third-party codes to which they want to propagate the new addresses.

New API for modifying social security information

Development

Creation of an API to modify:

  • Social security data (main scheme, fund, etc.),
  • The TNS code,
  • The tax year.

Enhancement of amendment APIs

Development

Addition of two amendments:

  • Change of date of birth,

Change of Social Security number.

 

coog Back-Office

Regulatory

DSN

DSN Direct Debit

Requirement

In the context of the DSN, the amount in the direct debit order may sometimes differ from the third-party balance.

The presence of a negative third-party balance should not affect the amounts deducted; the amounts to be taken into account are those included in the submitted DSN.

Updates

  • Creation of a new processing method

  • Creation of a new processing batch that integrates DSN payments, which will generate (depending on the configuration) SEPA direct debits. A second batch integrates the DSN allocations that assign these payments to payment schedules, enabling them to be paid automatically.

DSN Contribution Base

Development

Creation of processes to:

  • Read payroll information used as the basis for contributions under the group contract,
  • Extract this information using a data-loading mechanism,
  • Apply it to the covered items for employees under the group contract.

This information will be available in the rules engine to estimate the amounts on payment slips, for example.

SEPA

Enhancement of BIC presence checks during SEPA mandate creation

Requirement

Following the execution of the SEPA mandate creation batch, it is not possible to create a SEPA mandate if the mandate header contains a BIC when the legal entity does not have one. The account.payment.sepa.mandate.create batch fails with the error: “No bank found with the BIC.”

Update

The mandate creation rules have been updated to account for the following scenarios:

  • If a BIC is present in the header and the legal entity does not have a BIC, the mandate will be created.
  • If a BIC is present in the header and the same BIC is present for the legal entity, the mandate will be created.
  • If a BIC is present in the header and a different BIC is present for the legal entity, an error is raised.
  • If the BIC is missing from the header, the mandate will be created.

These rules also apply to revoked mandates.

PASRAU

Addition of a consistency check on the NIR

Update: addition of a consistency check between the NIR and the INSEE code of the municipality of birth to verify whether digits 6 through 10 of the NIR match the INSEE code of the municipality of birth.

Adjustment Management

Requirement: Ability to generate block S21.G00.56 – Withholding Tax Adjustment, enabling the reporting of adjustments in PASRAU data flows introduced by standard P20V02.

Update: Enhancement of the adjustment entry wizard to allow selection of error types.

The tags included in the PASRAU feed will depend on the error type selected during the adjustment.

Contracts

Group Contracts

Service Contact Management Wizard

Update: Creation of an action from within the contract that allows you to modify service contacts without having to go through the Contribution Contact Management Wizard.

Contract Amendments

Batch for Deleting Obsolete Draft Amendments

Update: Creation of a batch to delete draft amendments based on a configurable time period.

Health

almerys

Consolidation of V3 Flow Transactions

Requirement: When multiple amendments are made for the same third party, a single transaction must be sent.

Update: Consolidate all events related to a third party to send a single record in the V3 flow.

Request Issuance of a Third-Party Payment Card

Update: Creation of an action from a contract to request the issuance of a Third-Party Payment Card from a contract.

Noémie

Enhancement of Event Logs

Requirement: Enhance the event log in the event of a Noémie rejection or notification.

Update: Add the rejection code and description to the Noémie event log.

Enhancement of 929 Transactions

Update: Ability to include 929 returns of type “M” (Modification) in addition to types “A” (Cancellation) and “C” (Creation).

Transactions of type “M” will be included in unreconciled 929 transactions.

Third Party

Check for changes to bank account details for a third party

Update: Addition of an error message when adding a bank account for a third party if that bank account belongs to a third party in the configuration.

Display of the signature date in the list view of a legal entity’s mandates

Third-party amendments

Allow changes to mandatory regime (RO) information to be made as of a date prior to the current date within the Noémie management system

Example

Offer a new single amendment allowing the special regime (e.g., Alsace-Moselle) and/or self-employed status information to be modified with a retroactive effective date. This allows the health insurance contract to be recalculated and the resulting rate changes to be applied without affecting Noémie compliance.

Blocking of benefits following the insured’s death

Update: Implementation of a blocking message to prevent the erroneous entry, calculation, and payment of a benefit when calculating a benefit for a deceased insured.

Addition of a linked record for claims

Update: A linked record for claims has been added to view the benefits associated with that claim.

Changes to the Automatic Pension Calculation Process

Requirement

Certain recurring pension-type benefits may require occasional manual intervention by an administrator. For example, continuing the calculation or determining the amount to be paid may require decision-making and the entry of additional information.

Business Case Example

Education pensions are paid as long as the beneficiary continues their studies. Payment of the pension therefore requires requesting a certificate of enrollment each year. If the certificate is not received, payment is suspended.

Changes:

  • Creation of a rule to automatically suspend annuity-type benefits,
  • Creation of a new batch to suspend annuity calculations,
  • Creation of a wizard to manually suspend annuities,
  • Creation of a closing date for issued benefits (the automatic annuity calculation batch no longer considers closed benefits).

Creating an event for billing a service

Update: Creation of an event for billing a service in order to trigger an action.

Management of aggravations

Requirement: To be able to report aggravations of claims (e.g., transition from temporary disability to permanent disability) while reducing the workload for the claims administrator.

Development

Creation of a worsening reporting wizard that allows:

To finalize the worsened/initial claim and, if necessary, close the claim file,
To open a new claim within the existing file or in a new file.

The following information is carried over:

  • The start date of the new claim (this date is, by default, the day after the closed claim ends),
  • The date the initial claim occurred,
  • The amounts of the insured’s various wages and premiums,
  • Supplementary benefits,
  • Any additional data, when identical between the two claims.

Premiums

Creating a sales discount without a defined period

Update: The end date of the sales discount must be entered when adding the sales discount to the contract.

Paybox

Implementation of the 3D Secure V2 protocol

Update: Integration of version 2 of the 3D Secure standard for communications with Paybox.

Billing

Accounting

Enhancement of the cost accounting file

Update

Addition of information to reconcile general ledger entries with cost accounting entries:

  • An indicator to identify that the entry has a cost accounting detail, along with the detail ID,
  • The general ledger entry ID to easily identify the grouping.

Documents

Wizard for modifying the document request date for claims

Requirement: In claims files, the document request date is set to the date the claim was opened. However, in some cases, this date is incorrect, and the document request is inaccurate.

Update: Creation of a wizard to modify the document request date.

Enhancements to the Management of Document Request Follow-ups

Requirement: Update the document request follow-up procedure so that the follow-up process no longer begins on the day the request is created.

Changes

Added a field to define the deadline for the first request.

The following existing fields have been reorganized on the view for better readability:

  • The time limit before the first request expires,
  • The frequency of reminders,
  • The maximum number of reminders.

Enhancements to the Bdoc workflow

Updates

  • Contract workflow: Added the date of postponement of the medical decision.
  • Batch payment workflow: Added the rejection date.

Electronic signature

Use of anchors for Docusign documents

Requirement: Replace the use of coordinates with an anchoring mechanism on documents.

Update: Added the anchoring mechanism for the signature and its date.

Rules Engine

Enhancement of the “Number of other contracts signed” function

Requirement: Ability to create a contract validation rule based on the status (e.g., “Terminated”) and the sub-status (e.g., “Litigious termination”).

Update: Creation of a rules engine function that takes the product code, status, and sub-status of the contract as parameters.

Creating a rule engine function to retrieve third-party claim numbers

Update: Creation of a rule engine function to retrieve a claim number.

Creation of a rule engine function for calculating periods

Requirement: Simplify the configuration of service rules by automatically splitting periods.

Development: Creation of a new rule engine function to enable automatic splitting.

Technical Core

Improvements to the usability of view configuration

Updates

Use a code editor to view XML code:

  • Custom steps and views for processes,
  • HTML-based email template templates.

Addition of a Warning to the account.payment.create batch

Update: Implementation of a Warning in the account.payment.create batch process in the event of an execution error.

Enable the generation of inventory reports via batch

Update: Generate inventory reports (contract, beneficiary, claim) via batch.

Enhancement of Batch Trigger Conditions

Requirement: The ability to configure batch triggers for specific dates.

Update: Creation of new batch trigger conditions via the rules engine.

Addition of a “CRON Status” entry point

Update: Creation of a “CRON Status” entry point to view any errors related to CRON.

Creating a Relate for Scheduled Actions

Update: Create a Relate for scheduled actions to view previously completed actions.

User Notifications

Updates

Creation of a tool to send notifications to all coog users. Users must have previously enabled notifications in their browser. Notifications can inform users of a restart, the completion of an asynchronous task, etc.

Creation of End-of-Batch Events

Requirement: Trigger events when a single batch is completed, not just a batch chain.

Development: Creation of 3 new event types.

Addition of an administrator action to clear the cache

Requirement

Certain configuration changes or error handling procedures require restarting the Back-Office. This action has consequences (such as a production outage). It is necessary to be able to clear the cache without requiring a restart.

Update: Creation of an action to clear all caches.

Enhancements to the Extraction Request Batch

Update: Group rows by third party to account for all versions associated with a single third party.

Migration

Wizard for counting migrated items

Requirement: Quickly extract the number of migration rows created following the execution of the Staging creation batch, as well as the number of items created following the execution of the migration batches.

Development: Creation of a wizard to count the items migrated per process.

Creating a Batch to Validate Supplementary Data

Requirement: Migrate supplementary data while applying validation rules based on configuration settings.

Solution: Create a batch that compares the supplementary data configured in the templates (e.g., product) with the data in the records (e.g., contract).

coog advance

PASRAU

Enhancement of the PASRAU Statement Entry Point

Requirement: Quickly view the amount on a PASRAU statement.

Update: Display amounts related to withholding tax and social security contributions in a list view.