[ https://issues.apache.org/jira/browse/FINERACT-1761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mihaly Dallos updated FINERACT-1761: ------------------------------------ Description: {panel} *As a* user with 'NEW'“ permission *I want to* _add a new charge adjustment transaction_ *in order to* post the charge adjustment benefit provided to the customer {panel} *User Cases/Background and details:* The previous solution provided by Fineract of Charge waive (for an unpaid charge) and charge refund(for a paid charge) had its own constraints with respect to # Restrictions on reversal of previous transactions. # Reverse replays for charge refunds # Accounting. Proposed the new solution will satisfy all the requirements with new adjustment transaction: # A single transaction can be used for waiving both paid and unpaid charges. # Since it is always posted at the current date, reversal of the previous transaction should not be a problem. # The proper linkage between the new charge adjustment transaction with the loan charge. *Linking* * The new charge adjustment transaction type requires a reference to the charge to which it is being adjusted. This will be the transaction ID added as a link to the loan_charge. Only the new transaction points to an existing loan_charge. * Details of the existing loan charge should be provided manually by the user {panel:title=Acceptance Criteria} # New charge adjustment transaction behaviour is the same as the goodwill credit transaction Behaviour # Only difference is “charge adjustment transaction should be linked to the “loan charge account”.{panel} was: {panel} *As a* user with 'NEW'“ permission *I want to* _add a new charge adjustment transaction_ *in order to* post the charge adjustment benefit provided to the customer {panel} *User Cases/Background and details:* The previous solution provided by Fineract of Charge adjustment (for an unpaid charge) and charge refund(for a paid charge) had its own constraints with respect to # Restrictions on reversal of previous transactions. # Reverse replays for charge refunds # Accounting. Proposed the new solution will satisfy all the requirements with one transaction: # A single transaction can be used for waiving both paid and unpaid charges. # Since it is always posted at the current date, reversal of the previous transaction should not be a problem. # The proper linkage between the new charge adjustment transaction with the loan charge. *Linking* * The new charge adjustment transaction type requires a reference to the charge to which it is being adjusted. This will be the transaction ID added as a link to the loan_charge. Only the new transaction points to an existing loan_charge. * Details of the existing loan charge should be provided manually by the user {panel:title=Acceptance Criteria} # New charge adjustment transaction behaviour is the same as the goodwill credit transaction Behaviour # Only difference is “charge adjustment transaction should be linked to the “loan charge account”.{panel} > New Charge-adjustment Transaction > --------------------------------- > > Key: FINERACT-1761 > URL: https://issues.apache.org/jira/browse/FINERACT-1761 > Project: Apache Fineract > Issue Type: New Feature > Reporter: Mihaly Dallos > Assignee: Adam Saghy > Priority: Major > Labels: PepperSoup > > {panel} > *As a* user with 'NEW'“ permission > *I want to* _add a new charge adjustment transaction_ > *in order to* post the charge adjustment benefit provided to the customer > {panel} > *User Cases/Background and details:* > The previous solution provided by Fineract of Charge waive (for an unpaid > charge) and charge refund(for a paid charge) had its own constraints with > respect to > # Restrictions on reversal of previous transactions. > # Reverse replays for charge refunds > # Accounting. > Proposed the new solution will satisfy all the requirements with new > adjustment transaction: > # A single transaction can be used for waiving both paid and unpaid charges. > # Since it is always posted at the current date, reversal of the previous > transaction should not be a problem. > # The proper linkage between the new charge adjustment transaction with the > loan charge. > *Linking* > * The new charge adjustment transaction type requires a reference to the > charge to which it is being adjusted. This will be the transaction ID added > as a link to the loan_charge. Only the new transaction points to an existing > loan_charge. > * Details of the existing loan charge should be provided manually by the user > {panel:title=Acceptance Criteria} > # New charge adjustment transaction behaviour is the same as the goodwill > credit transaction Behaviour > # Only difference is “charge adjustment transaction should be linked to the > “loan charge account”.{panel} -- This message was sent by Atlassian Jira (v8.20.10#820010)