Payment refactoring



in legacy model the contribution serves as both a contract and a payment, when the epayement was added additionnal layer (payment) was created BUT this is only used in case of epayment.

the group insurance (aka format sector) added the invoice and therefore the payment linked to contribution could not be used or modified (migration to modular was on its way for this module)

several tables and wording to document a payment

  • contribution (named Premium in the database)

  • Payment linked to contribution

  • Payment linked to contract

here the example of the informal sector that used contribution and payment

the proposal for refactoring will be to use the contract approach develop in the group insurance and to drop the contribution and legacy payments

in addition to streamline the payment parts it will also bring the contract capacities (contribution plan - to be renamed enrollment plan) for the informal sector


Did you encounter a problem or do you have a suggestion?

Please contact our Service Desk

This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.