...

referenceActor {
  "label":"",
  "code":"",
  "type": "contribution/contract/funding",
  "id":"UUID",
  "address":{"text":"",...}
}

referenceSource {
  "label":"",
  "code":"",
  "type": "Insuree/PH/payer/User",
  "id":"UUID",
  "address":{"text":"",...}
}

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

...

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

...

InvoicePayments

To document the payment done on the invoice. out of scope: a payment done for 2 invoice, to support such scenario an “generalPayment“ table need to be created, this table will have sub table with relationships to inboundInvoicePaymentsinvoicePayments, once the reconciliation between the different invoice will be done.

...

[Nice to have]

...

invoicedocuments

...

Integration:

Services

• invoicePaymentRefRecieved

• invoicePaymentRejected

• invoicePaymentRecieved

• invoicePaymentRefunded

• invoiceCreate (called on save)

• invoiceUpdate (called on save)

• invoiceDelete

• invoiceItemCreate

• invoiceItemUpdate

• invoiceItemDelete

• invoiceAmend

• invoiceValidateItems

• invoiceMatchItems

Payment specific module(s)

Contribution:

the grouping will be done per Head of family, therefore such invoice will have only 1 detail.

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

• contributionCreated

Converters:

Contract:

the invoice of a contract will match the contract value and details.

Registration on signals from other module(existing or not)

• contractApproved

Converters:

[out of scope]Claim Co-paiment:

Registration on signals from other module(existing or not)

• claimSubmitted

Converters:

TBC - (Product payment module)Funding:

Manually filled invoice for a payer, the details of the pool/product to be funded will be in the details

Converters: Convert the different account receivable following the new structure

Contribution:

Contract:

...

new  signals are use to trigger action in another module:

• [one signal per service]

• invoiceValidated (all invoiceItemMatched and invoiceItemAmountValidated)

• invoiceFullyPaid

• invoicePaymentRefRequested

Create a FHIR interface for the accounting systems (change FHIR_R4 ?)

...

1. Insurance clerk generates informal sector insurance invoice per head of family for a given time period

2. Insurance clerk generates formal sector insurance invoice per Policyholder for a given time period

3. Insurance clerk generates a funding invoice for a product/pool

4. Insurance clerk display the invoice with details

5. Insurance clerk add a payment on the invoice

6. Insurance clerk print the invoice

7. Insurance clerk delete an invoice (this won’t delete the generating Item)

8. [should have] access invoice via FHIR invoice resource. (read only)

Front end

The front end will have the same layout as the contract

Search page

search criteria

• type for invoice

• recipients (NTH: Ideally contribution from the specific payment module based on type)

• code

• date_invoice

• amount_total

• status

search result

• type for invoice

• recipients (NTH: display only the recipient attached )

• code

• date_invoice

• amount_total

• status

No add new button , All invoice MUST be generated using specific payment module

card page

general information

...

All schema fields but UUID

if not payed:

• Delete button

if payed show no button

tabs

invoiceLines

read only, All invoice MUST be generated using specific payment module

search filters on All schema fields but UUID

colunm to show All schema fields but UUID

invoicePayment

search filters on All schema fields but UUID

• Add Payment button near the search (see add contract insuree)

colunm to show All schema fields but UUID

• on each line:

  • delete payment

  • edit payment (modal popup), all fields but UUID can be modified

invoiceEvent

search filters on All schema fields but UUID

• Add Comment button near the search (see add contract insuree) modal popup with a text field

colunm to show All schema fields but UUID

[Nice to have]InvoiceDocument

search filters on All schema fields but UUID

• upload document button near the search (see add contract insuree)

• add linked document button near the search (see add contract insuree)

colunm to show All schema fields but UUID

...