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

Vishwas Babu A J commented on FINERACT-239:
-------------------------------------------

[~edcable] : All the business scenarios are valid. However, it might be better 
from a usability perspective to provide more graceful support at the portfolio 
level for handling the same rather than allowing debits/credits.

For Ex: *Scenario Credit Principal*. This allows you to correct an erroneous 
posting of disbursement, whether a wrong amount was posted for the disbursement 
or it was posted to a wrong account.

You can do the same on Fineract 1.x by 
 * Undoing the disbursal
 * Making a new disbursal on the same account or another loan account

The core underlying issue that needs to be fixed on Fineract 1.x (and possibly 
Fineract CN ?) for this to work in all scenarios is that the system tracks only 
two dates for transactions and associated journal entries, namely
 # Created Date: Timestamp on which the transaction was created
 # Transaction Date: Date on which the change is affected due to the 
transaction. The same is carried over as the "Entry date" on the Journal 
(affects accounting books). This common terminology for this being "value date"

However, this leads to complications when accounting closures are done 
(typically on a daily basis is mature organizations). The branch would now need 
to remove the accounting closure to correct such mistakes in the past as the 
"Transaction date" on the loan/savings and the "Entry" date on the journal are 
the same.

The change needed for addressing the same would be to optionally delink these 
dates, i.e a separate "Entry date" which can be associated with transactions 
and then carried over to the journal entries that need to be made on a 
different day than the transaction date.

If this isn't already a part of Fineract-CN, then we should definitely 
prioritize the same.

 

> Ability to adjust Principal and Interest as a super user
> --------------------------------------------------------
>
>                 Key: FINERACT-239
>                 URL: https://issues.apache.org/jira/browse/FINERACT-239
>             Project: Apache Fineract
>          Issue Type: Improvement
>          Components: Loan
>            Reporter: Dayna Harp
>            Assignee: Markus Geiss
>            Priority: Major
>              Labels: Fineract-CN, gsoc, large, p3
>
> https://mifosforge.jira.com/browse/MIFOSX-2518
> This should allow you to make adjustments on the principal and/or interest 
> balances of a loan account for correction purposes. The adjustment process 
> should always be a voucher transaction not cash and should be fixed by 
> default.
> *Credit Principal*. This allows you to correct an erroneous posting of 
> disbursement, whether a wrong amount was posted for the disbursement or it 
> was posted to a wrong account.
> *Debit Principal*. This allows you to correct an erroneous posting of a 
> repayment, whether a wrong amount was posted or it was posted to a wrong 
> account.
> *Credit Accrual. *This allows you to correct erroneous posting of loan 
> accruals—interest, penalties and charges—to an account or to waive penalties. 
> This is also used to reduce accruals whenever there was a delay in the 
> posting of a repayment.
> *Debit Accrual.* This allows you to apply loan accruals—interest, penalties 
> and charges—to an account in cases of repayment cancellation. This is 
> particularly necessary if the cancellation occurred after the day that the 
> repayment was posted



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to