...

Save the different account receivable

Ideally the “batchrun“ would be rename “close accounts payable”, closing account will be on a defined scope:

1. area: if not national, will take only the product define on the level selected or below

2. type: the type below could be checked

   1. supplier payment method (notion not yet existing)

      1. Claim valuation (fee for service - batchRun): https://openimis.atlassian.net/browse/OTC-10

      2. Capitation payment: https://openimis.atlassian.net/browse/OTC-10

   2. operation fee payment method (notion not yet existing)

      1. Commission payment:

      2. Payment fees

   3. insuree Cash payment (doesn’t exist yet)

3. an account receivable param report will be generated for each of the bellow Item when required by the payment method

   1. Product / payment period for “supplier payment method”

   2. actor / payment period for “operation fee payment method”

   3. insuree for the insuree payment period

Convert the different account receivable following the new structure

...

Claim valuation (batchRun):

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

Capitation payment:

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

...

1. Population living in catchments area of the health facility

2. Number of families living in catchments area of the health facility

3. Insured population living in catchments area of the health facility

4. Insured number of families living in catchments area of the health facility

5. Number of claims (contacts) with the health facility by insured in the catchment area

6. Adjusted amount

...

asset (line) per product with the detail of the calculation as asset description

...

Commission payment:

1. one accountPayable per EO,

   1. one asset (line) per product/commission, sum of policy value as quantity, commission as unit price, product account code as ledger account

   2. one asset (line) per policy : policy value as quantity, commission as unit price, product account code as ledger account (dependent detail as asset description)

...

Payment fees

1. one accountPayable per type of payment (TBC)

   1. one asset (line) per product/commission, sum of policy value as quantity, Payment fees as unit price, product account code as ledger account

   2. one asset (line) per policy : policy value as quantity, Payment fees as unit price, product account code as ledger account (dependent detail as asset description)

...

insuree Cash payment (doesn’t exist yet)

1. one accountPayable per insuree (for all dependant), one line per cash payment (level of Item and service)

2. one accountPayable per period, one line per cash payment claim

Create a FHIR interface for the accounting systems

...

https://www.hl7.org/fhir/invoice.html

Front end

Image Removed

Current Batch run Screen (picture above) should be rename account receivable

Launch Batch Run section will become “account receivable“ with those parameters

...

Either drop down as current screen

• General account receivable section

  • Select “account receivable”

  • Payment plan picker in the future data model

    • can be a static drop down list for the old model: Valuation / Capitation / Commission fees / payment fees + Product picker

    • Or calculation for payment plan using the product configuration could be created, then payment plan could be created for each products

  • two datetime entries: DateFrom/DateTo

  • Location picker

• Export account receivable section

  • Payment plan picker in the future data model

    • can be a static drop down list for the old model: Valuation / Capitation / Commission fees / payment fees + Product picker

    • Or calculation for payment plan using the product configuration could be created, then payment plan could be created for each products

  • two datetime entries: DateFrom/DateTo

  • Location picker

  • group by: Product or third party

  • third party: user(EnrolmentOffice)/HF/”insuree”

• section “payment plan calculated” that will display all “account receivable generated” with there input detail in 1 column, working var in a second and the result in the third (relative index)

or use the Payment plan pages instead

...

search tab

• search on all columns

• 3 dot menu “General account receivable“ on selected line / query that will ask dateFrom/DateTo

• 3 dot menu “Export account receivable“ on selected line / query that will ask dateFrom/DateTo and third party: user(EnrolmentOffice)/HF/”insuree”

Tab with payment plan calculated

...

search on all colums

will display the list of payment plan calculated (payment plan/date exe / dateFrom / dateTo)

...

doubleclick / click on edit will display the details in readonly

...

Account receivable, using the same structure as account receivable, when associated to the contract might also replace the “contribution/premium“

...