[jira] [Comment Edited] (FINERACT-2284) Charge should check Money inMultiplesOf settings and enforce it!

["Ashok Auty (Jira)" <ji...@apache.org>]

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

Ashok Auty edited comment on FINERACT-2284 at 8/31/25 4:02 PM:
---------------------------------------------------------------

Hi [~adamsaghy] , I’d like to get some clarification on the scope of this ticket before proceeding with implementation:
 # Is the expectation that charge amounts should be validated/adjusted against the currency’s {{{}inMultiplesOf{}}}configuration, similar to how loan amounts are already enforced?

 # Since charge amounts are *system-calculated* (based on charge calculation type – flat, % of amount, % of outstanding, etc.), rejecting them may not be practical. Instead, the correct approach seems to be to *round off the final calculated amount* to the nearest multiple of the configured currency value. Could you please confirm if this is the intended behavior?

 # Should this rounding logic apply to *all types of charges* (disbursement, penalty, due date, etc.) or only to specific categories?

 # Should this rule rely solely on the {*}currency configuration ({{{}inMultiplesOf{}}}){*}, or do we foresee the need for a separate override/configuration at the {*}charge or product level{*}?

 # Can you also share a *real-world use case* where enforcing {{inMultiplesOf}} for charges is required? For example, in some markets certain currencies/products only allow transactions in fixed multiples (e.g., 100), so understanding the exact scenario will help align the implementation with business needs.


was (Author: JIRAUSER310364):
Hi, I’d like to get some clarification on the scope of this ticket before proceeding with implementation:
 # Is the expectation that charge amounts should be validated/adjusted against the currency’s {{{}inMultiplesOf{}}}configuration, similar to how loan amounts are already enforced?

 # Since charge amounts are *system-calculated* (based on charge calculation type – flat, % of amount, % of outstanding, etc.), rejecting them may not be practical. Instead, the correct approach seems to be to *round off the final calculated amount* to the nearest multiple of the configured currency value. Could you please confirm if this is the intended behavior?

 # Should this rounding logic apply to *all types of charges* (disbursement, penalty, due date, etc.) or only to specific categories?

 # Should this rule rely solely on the {*}currency configuration ({{{}inMultiplesOf{}}}){*}, or do we foresee the need for a separate override/configuration at the {*}charge or product level{*}?

 # Can you also share a *real-world use case* where enforcing {{inMultiplesOf}} for charges is required? For example, in some markets certain currencies/products only allow transactions in fixed multiples (e.g., 100), so understanding the exact scenario will help align the implementation with business needs.

> Charge should check Money inMultiplesOf settings and enforce it!
> ----------------------------------------------------------------
>
>                 Key: FINERACT-2284
>                 URL: https://issues.apache.org/jira/browse/FINERACT-2284
>             Project: Apache Fineract
>          Issue Type: New Feature
>    Affects Versions: 1.12.1
>            Reporter: Adam Saghy
>            Priority: Major
>
> Charge should check Money inMultiplesOf settings and enforce it!
> Issue:
> - Currency set 100 multiples of.
> - Charge with amount that is not multiple of 100 should not be allowed!
> *Example*
> - Currency set 100 multiples of.
> - Add charge with amount of $20, should not be allowed!



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