UI seems to be limited to straight Payment registering (with straight matching - aka ‘contribution’ -)

Highlights of the database scheme:

Questions:

• why “InsuranceNumber” field in PaymentDetail (matching is via Contribution, not insuree…)?

• in TZ, payment type “F” is related to funding (not contributions)… should we filter in this module (as we do filter the ‘funding’ --aka fake-- family)?

WARNINGS (to be refined):

• Payment matching (cfr. uspMatchPayment, …)

• Payment ‘intent’ (cfr. uspInsertPaymentIntent,…)

• Payment/Contribution ‘REST-API’ (cfr. uspAPIEnterContribution, uspReceivePayment…)

Out of scope

• outgoing payments

  • payment by capitation (cfr. uspSSRSCapitationPayment)

  • …

• operational reports

  • uspLastDateForPayment (necessary for policy expiry handling ?)

• Payers (contributions depends on Payers module, but managing payers is outside contribution module scope