[ 
https://issues.apache.org/jira/browse/FINERACT-2151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17901122#comment-17901122
 ] 

Bharath Gowda commented on FINERACT-2151:
-----------------------------------------

[~ruhiu]  Thanks for sharing your understanding, Adding the charge related 
options here for better understanding

{*}Edit charge{*}- an option that performs exactly how you have described- 
editing the charge amount for *unpaid* charges

*Waive Charge* is another option- that waives the *unpaid* charges.

*Charge-adjustment* -this is used to adjust the charge that is already paid but 
organization do not want to do backdated reversals and adjustments.

 

If in case if you wish to add a behavior where it has to go to Charge portion 
only- then you can create a new sub-enhancement that can work the way you are 
describing with a global configuration..It would be lovely if you could 
contribute that change as well.

Hope it helps.

> Charge adjustment should only affect the charge adjusted not other charges, 
> interest, principal, etc. Linked to 
> https://issues.apache.org/jira/browse/FINERACT-1761
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: FINERACT-2151
>                 URL: https://issues.apache.org/jira/browse/FINERACT-2151
>             Project: Apache Fineract
>          Issue Type: Bug
>          Components: Accounting, Charges
>    Affects Versions: 1.9.0
>            Reporter: John Ruhiu
>            Priority: Critical
>             Fix For: 1.10.0
>
>         Attachments: Charge adjustment transaction type bug 
> clarification.mp4, Charge adjustment transaction type bug.mp4
>
>
> When a charge is adjusted using the charge adjustment transaction type, 
> amount entered as adjustment value is applied to principal,fees,penalties and 
> interest. It should only affect fees.
>  
> Watch the video attached for steps to replicate the bug
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to