You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@fineract.apache.org by "Mihaly Dallos (Jira)" <ji...@apache.org> on 2022/12/06 16:00:00 UTC
[jira] [Updated] (FINERACT-1829) Storage of overpaid date
[ https://issues.apache.org/jira/browse/FINERACT-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mihaly Dallos updated FINERACT-1829:
------------------------------------
Labels: PepperSoup (was: )
> Storage of overpaid date
> ------------------------
>
> Key: FINERACT-1829
> URL: https://issues.apache.org/jira/browse/FINERACT-1829
> Project: Apache Fineract
> Issue Type: Improvement
> Reporter: Mihaly Dallos
> Priority: Minor
> Labels: PepperSoup
>
> h3. Description
> Add {{m_loan.overpaidon_date}} field and realtime handling to Fineract.
> m_loan.overpaidon_date stores the date the loan was overpaid the *last time!* It is {{{}NULL{}}}'d when loan isn't overpaid any more.
> {panel}
> {*}Acceptance criteria{*}{{{}{}}}
> # {{m_loan.overpaidon_date}} is added
> # {{m_loan.overpaidon_date}} is filled for all existing loans at deployment
> # When loan becomes overpaid, business date is stored
> # In case a loan isn’t overpaid any more the field value {{{}NULL{}}}d.
> # {{overpaidOnDate}} is available on the loan API
> # Transaction reversal may impact the state of the loan, can go from overpaid to active. This time the overpaid date should {{{}NULL{}}}ed.
> {panel}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)