Versions Compared

Key

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

...

The link with the Source and actor won’t be in a form a database foreign keys because those could be from different table.

...

accountPayable

field

type

comment

source

json

Code Block
languagejson
referenceActor {
  "label":"",
  "code":"",
  "type": "batchRun/commissionOverview/capitationReport",
  "id":"UUID",
  "address":{"text":"",...}
}

 third_party

json 

Code Block
languagejson
referenceSource {
  "label":"",
  "code":"",
  "type": "HF/Insuree/PH/payer/user",
  "id":"UUID",
  "address":{"text":"",...}
}

 id

 UUID

 code

 str 

or reference for the insurance

 code_rcp

 str 

or reference for the recipient

 code_ext

 str 

if required for external system integration

 date_due

 date 

date on which the payment is due

 date_invoice

 date 

Date of the “invoice“

 date_from

 date 

invoice covering service/item from

 date_to

 date 

invoice covering service/item to

 date_payed

 date 

Date on which the payment was actually documented as Done

 amount_discount

 float 

total of the detail discount

 amount_net

 float 

Total without tax

 tax_analysis

 json 

Code Block
languagejson
tax details {
  "lines": [
    {"label":"", "rate":"", "base":"", "amount":""}]
    …
  ],
  "total":""
}

 amount_total

 float 

total net + tax total

 status

 int 

ENUM: draft, validated, payed, cancelled, deleted

 currency_rcp_code

 str 

currency of the recipient (if different)

 currency_code

 str 

currency of insurance

 note

 bigttext 

 terms

 bigttext 

conditions

...

assets

field

type

comment

code

 str 

reference

invoiceIdaccountPayableId

UUID

reference to outInvoiceaccountPayable

description

 str 

details

 json 

depend of the type, TBD

ledger_account

 int 

from config

quantity

 float 

unit_price

 type 

discount

 float 

to document difference between the std price and the price to be paid, usefull for relative pricing

 tax_rate

 Calculation uuid 

Calculation to calculate the tax

tax_analysis

json

Code Block
languagejson
tax details {
  "lines": [
    {"label":"", "rate":"", "base":"", "amount":""}]
    …
  ],
  "total":""
}

amount_total

float

net +tax

amount_net

qty * unitprice - discount

Save the different account payable

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

    Fee-for-service
    1. insuree Cash payment (doesn’t exist yet)

  3. an account payable 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 payable following the new structure

  1. Claim valuation (batchRun):

  2. Capitation payment: ​

  3. Commission payment

  4. Payment fees

  5. Fee-for-service

    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

  6. Capitation payment:

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

      1. one asset (line) per weighted indicator I for product P : Allocated contribution/ Sum(indicator for P) as unit price , indicator I as quantity, (1-weight) as discount;

        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

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

  7. 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)

  8. 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)

  9. 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

...