Payment plan calculation rule: Fee-for-service

version = 1
status = active
UUID = 0a1b6d54-eef4-4ee6-ac47-2a99cfa5e9a8
calculation_rule_name = “payment: fee for service “

type = account_payable

sub_type = third_party_payment

dateValidTo = None

dateValidFrom = 2000-01-01

Registration on signals from other module(existing or not):

• billCreationFromCalculation

Only the “valuated“ claims are eligible for bill generation meaning that the batch run might be triggered before in case .

Batchrun will trigger billCreationFromCalculation and will send: when the payment plan would be deliver the batch run page could be replaced by payment plan (this page could call billCreationFromCalculation service on selected payment plans) page and bill page.

• date_from

• date_to

• type

• sub_type

billCreationFromCalculation will have a variable that will tell the signal listener to be activated or not: this will be activated based on type and subtype

Converter

[to be updated]

1. two way of creating the accountPayable are possible for the valuation, in both case there will be one “accountPayable” per HF

   1. One asset (line) per claim, claim details as asset description: claimed amount as unit price, net amount as net price, discount calculated based on net and unit price

   2. one asset (line) per item or service with claim detail as asset description: item/service claimed unit price as unit price, net as valuated price, quantity as quantity, discount calculated based on net and unit price