Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

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

Highlights of the database scheme:

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

  • No labels

Did you encounter a problem or do you have a suggestion?

Please contact our Service Desk


This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License. https://creativecommons.org/licenses/by-sa/4.0/