Thanks 👍.

On Thu, 12 Nov, 2026, 6:25 pm Ádám Sághy, <[email protected]> wrote:

> I yield :)
>
> New “Business scenarios” section was added:
> https://cwiki.apache.org/confluence/spaces/FINERACT/pages/462817154/FSIP-14+Charge+Amortization+Deferred+Charge+Income+Recognition#FSIP14%3AChargeAmortization(DeferredChargeIncomeRecognition)-Businessscenarios
>
> Regards,
> Adam S
>
> On Nov 12, 2026, at 12:24 PM, Aman Mittal <[email protected]>
> wrote:
>
> Hi Adam,
>
> While I am also not sure if the "Proposal" should contain such an example,
> But I'm also not sure if including functional requirements (at the product
> level) in stories is appropriate. This could become a concern because it
> will segment many discussions into stories instead of the dev list.
>
> I am not blocking anything on a technical level. However, I think the
> Business Scenario Example can be included for greater transparency, as this
> will provide a clearer idea. (Maybe we can start a separate thread
> regarding this? Due to suggesting a potential change in process)
>
> It would be great as long as business processes are discussed or
> communicated on the dev list before technical implementation.
>
> Just my thoughts here.
>
> Regards,
> Aman
>
>
>
>
>
> On Thu, Nov 12, 2026 at 5:35 PM Ádám Sághy <[email protected]> wrote:
>
>> Hi Aman,
>>
>> Thank you for your feedback.
>>
>> While I agree with your points, i am not so sure the “proposal” should
>> contains such examples, but rather, if accepted, the created stories should
>> provide all high and low level details.
>>
>> I was focusing on the functional requirements only at this stage.
>>
>> Regards,
>> Adam S
>>
>> On Nov 12, 2026, at 11:58 AM, Aman Mittal <[email protected]>
>> wrote:
>>
>> Hi Adam,
>>
>> Thanks for raising this FSIP. For new features, it would be better if we
>> could simplify the financial terminology. This will help new contributors
>> who are not well versed in the finance domain relate to it better.
>>
>> Walking through how a user configures and experiences this in Fineract
>> step-by-step would make the business process much clearer
>> (Note Just a example : We can make it much more simpler or adding
>> relevant references )
>>
>> Create a Loan Product: Enable the enableChargeAmortization flag, map the
>> required GL accounts (Fee Receivable, Deferred Income Liability,
>> Fee/Interest Income), and attach the amortized charge.
>>
>> Create & Disburse a Loan: Apply the charge to the loan. Upon disbursement
>> (or when the charge becomes effective), the fee is booked to the deferred
>> income liability rather than immediately recognized as income.
>>
>> Daily Recognition (COB): Explain what happens day-to-day during the Close
>> of Business job (a small portion of the fee is moved from deferred
>> liability to recognized income each day).
>>
>> Loan Lifecycle Events: Briefly illustrate what the user sees on early
>> repayment/closure, write-off, or charge waiver (the remaining deferred
>> balance is released/adjusted accordingly).
>>
>> Including a simple numerical example (e.g., a $120 origination fee on a
>> 12-month / 360-day loan showing Day 1 booking, daily COB recognition, and
>> early payoff) would also go a long way in helping developers visualize the
>> exact journal entries and API outputs.
>>
>> Thanks,
>>
>> Aman
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> On Thu, Nov 12, 2026 at 5:02 PM Ádám Sághy <[email protected]> wrote:
>>
>>> Hi all,
>>>
>>> I’ve published a new proposal, FSIP-14: Charge Amortization (Deferred
>>> Charge Income Recognition)
>>>
>>> It lets loan fees, such as origination or arrangement fees, be deferred
>>> and recognized as income over the loan term, as IFRS 9 and ASC 310-20
>>> require. Fineract can’t do this today. The design reuses the Capitalized
>>> Income and Buy-down Fee model, and the feature is opt-in and off by
>>> default, so existing behaviour does not change.
>>>
>>> *Please read the full proposal here:*
>>>
>>> https://cwiki.apache.org/confluence/spaces/FINERACT/pages/462817154/FSIP-14+Charge+Amortization+Deferred+Charge+Income+Recognition
>>>
>>> Feedback is welcome on the wiki page or in this thread.
>>>
>>> Thanks,
>>> Adam S
>>>
>>
>>
>

Reply via email to