VERSION | date | comment | change |
---|---|---|---|
0.1 | 06-2021 | idea | |
0.2 | 08-2021 | slight update by Project: 2021.T3 Payment Layer | add workarround in the batch run to use account payable calculation rules without payment plan |
This module will host the different payment mechanism to calculate the amount due to third parties
Current Batch run Screen (picture below) should will be removed in rework inb the long run
...
but in a close future the Batch Run page will be used for manual trigger for generating Account payable from payment calulcation rule as long as there is no Payment plan , but will be replaced once the real
Project: 2021.T3 Payment Layer project cannot develop the payment plan be and fe but will develop payment calculation rules that would be trigger by batch runs with this update :
...
area: if not national, will take only the product define on the level selected or below
...
type: the type below could be checked
supplier payment method (notion not yet existing)
Claim valuation (fee for service - batchRun): https://openimis.atlassian.net/browse/OTC-10
Capitation payment: https://openimis.atlassian.net/browse/OTC-10
operation fee payment method (notion not yet existing)
Commission payment:
Payment fees
insuree Cash payment (doesn’t exist yet)
an account payable param report will be generated for each of the bellow Item when required by the payment method
...
Product / payment period for “supplier payment method”
...
actor / payment period for “operation fee payment method”
...
to, Account will be remove, Relative index will need to be reworked to be future proof (those are “calulated/saved“ payment plan paramters like capitation params)
...
Payment plan will define which calculation will be used for which claim meaning that the “ValidForObject“ function of the calculation must be precises, below is the overalprocess fro valuation: two stage Valuation and payment with 2 possible mode each individual or in batch
...
The batch run takes the “Processed” time to know which claim should be part of any batch this ensure that all the claim are part of a batch (as long as the batch are run after the period they are covering)
The batch will also tag the contribution but the date to be used is to be defined, my proposal is to add a date “Matched and Paid“ to ensure all contribution will be part of a batch.
...
Once the payment calculation are run, the invoices should be available
...
Authorities
To manage the group insurance several authorities will be added,the prefix of this module will be 151
PaymentPlan, prefix 1570
Search →157101
Create → 157102
Update → 157103
Delete → 157104
Replace → 157106
Entities
PaymentPlan(HistoryBusinessModel)
Code (varchar 32)*
name(varchar 256)*
CalculationUUID*
BenefitPlanUUID (fk_product )*
Periodicity (int)*
Number of month between 2 payment
All fields are mandatory
Search tab
search on all columns
Type (config Enum)
name
Calculation rule
DateValidFrom
DateValidTo
product
search results
name
Type (config Enum)
Calculation rule
DateValidFrom
DateValidTo
product
one edit button
one delete button
one replace button
3 dot menu
“General Account Payable“ “Create Bill“ on selected line / query that will ask dateFrom/DateTo
“Export Account Payable“ on selected line / query that will ask dateFrom/DateTo and third party: user(EnrolmentOffice)/HF/”insuree”
1 new button
card page/modal
name
Calculation rule
DateValidFrom
DateValidTo
product
calculation params
Save/update button
calculated Account payable
search page
search on all colums
result
the list of payment plan calculated (payment plan/date exe / dateFrom / dateTo)
doubleclick / click on edit will display the details in readonly
delete
button
can be use to delete the Account payable (only for admin)card
Standard params:
Type (config Enum)
Payment plan
DateFrom
dateTo
calculation params
list of param used by the calculation
calculated params
list of results if any (e.g. relative index)
Number of item included:
claims
policy
payment