Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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) will be rework inb the long run 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

Image RemovedImage Added

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

    • “Create Bill“ on selected line / query that will ask dateFrom/DateTo

  • 1 new button

card page/modal

  • name

  • Calculation rule

  • DateValidFrom

  • DateValidTo

  • product

  • calculation params

  • Save/update button