Hi fineract developer am new here.....how can I contribute to this
platform...

On Fri, 20 Nov 2026, 15:42 Ádám Sághy, <[email protected]> wrote:

> Hi Inar,
>
> Thanks for the detailed write-up. Your reading of the current behaviour is
> correct. Before answering your questions, here are the tools Fineract
> offers for a collections or negotiation case:
> Tool What it does
> *Interest waiver*(waiveinterest) Forgives interest, including a partial
> amount. It reduces only the outstanding interest.
> *Charge waiver* (waive on a loan charge) Forgives a whole charge, or a
> whole charge installment. It can’t waive a partial amount (FINERACT-591).
> It reduces only the charge you pick.
> *Charge adjustment*(CHARGE_ADJUSTMENT) A partial, current-date
> transaction on a fee or penalty. It is payment-like and follows the loan’s
> allocation rules.
> *Interest payment waiver*(INTEREST_PAYMENT_WAIVER) A payment-like
> transaction on the interest side that follows the allocation rules. It is
> the closest existing counterpart to charge adjustment.
> *Re-aging* Rebuilds the repayment schedule for the outstanding balance,
> with a new start date, frequency and number of installments.
> *Re-amortization* Spreads the overdue amounts over the remaining
> installments.
>
> *Accounting side effects: waiver vs adjustment*
>
> This is where the two families differ most, so it should drive which one
> you choose.
> Accrual accounting Cash accounting
> *Interest waiver / Charge waiver* *Dr* Losses Written Off (or the account
> mapped to the write-off reason) / *Cr*Interest, Fee or Penalty
> Receivable. Income already accrued stays booked, and the forgiven amount
> shows as a *loss*. No journal entry, because the income was never
> recognised.
> *Charge adjustment* *Dr* Income from Fees or Income from Penalties (the
> charge’s income account) / *Cr* whatever the allocation rules hit: Loan
> Portfolio, Interest/Fee/Penalty Receivable, or Overpayment. The forgiven
> amount is a *reduction of income*. *Dr* fee/penalty income / *Cr *whatever
> the allocation rules hit.
> *Interest payment waiver* *Dr* Interest Income / *Cr* whatever the
> allocation rules hit: Loan Portfolio, Receivables, or Overpayment. The
> forgiven amount is a *reduction of income*. Booked like a repayment.
>
> In practice:
>
>    - *What a waiver does:* it reduces only the selected component and
>    books the amount as a loss or expense. Gross income stays as it was.
>    - *What an adjustment does:* it reverses income. Because it follows
>    the allocation rules, the credit can land on principal, or create an
>    overpayment liability, instead of the component you meant to reduce.
>    - *Charged-off loans:* both families post to the charge-off income and
>    expense accounts instead of the ones above.
>
> So “partial interest waiver + partial charge adjustment” does reduce the
> right totals. But the two halves of one negotiated settlement then land in
> different places in the P&L: one as a loss, the other as reduced income.
>
> If consistent P&L treatment matters to you, pair the operations
> deliberately:
>
>    - *Both booked as a loss:* use the interest waiver and the charge
>    waiver.
>    - *Both booked as reduced income:* use the interest payment waiver and
>    charge adjustment.
>
> Either way, please validate the result against your chart of accounts.
>
> *Interest-side counterpart to CHARGE_ADJUSTMENT*
>
> There is no dedicated INTEREST_ADJUSTMENT type, and as far as I know none
> is planned. INTEREST_PAYMENT_WAIVER is the closest equivalent, both in
> behaviour and in accounting (Dr Interest Income), and may already fit your
> case.
>
> *Why a current-date interest adjustment needs careful design*
>
> Nothing rules it out in principle. The difficulty is that interest is not
> a fixed item the way a charge is. It is derived from the schedule,
> especially on progressive loans with interest recalculation. A new
> transaction would need clear answers to these questions:
>
>    - *Recalculation:* how does it interact with recalculation, so that
>    interest that was forgiven isn’t recalculated back onto the loan later?
>    - *Accounting:* how does it differ from the two existing interest
>    options? One books a loss (the interest waiver), the other reduces income
>    (the interest payment waiver).
>    - *Backdating:* how does it behave when an earlier transaction is
>    entered and later transactions are reprocessed (reverse-replay)?
>    - *Reporting:* how is it kept apart from the existing interest
>    options, so that nothing is double-counted?
>
> If you have a concrete design, please raise it on the dev list or in a
> JIRA ticket. We’d be happy to discuss it.
>
> *Re-aging and re-amortization*
>
> Collections cases often need a change to *when* the customer pays, not
> only to *how much* they owe. Both re-aging and re-amortization let you
> choose how interest is handled, including a WAIVE_INTEREST option and
> equal-amortization variants.
>
> A common pattern is to reduce the amount owed first, using the waivers or
> adjustments above. Then re-age or re-amortize what is left into an
> affordable schedule.
>
> Best regards,
> Adam S
>
> On Nov 20, 2026, at 6:13 AM, 星空下的雨 via dev <[email protected]>
> wrote:
>
>
> Hello Fineract community,
>
> We are looking at a collections/negotiation scenario where, after agreeing
> with the customer, part of the loan interest and part of the penalty or fee
> charges should no longer be payable. We would like to understand the
> community's recommendation for modeling this with the existing waive and
> adjustment mechanisms.
>
> As I understand the current behavior:
>
> 1. waiveinterest supports a partial amount through transactionAmount.
>
> 2. Loan charge waive does not support a partial amount. It waives either
> the full outstanding amount of the selected non-installment charge, or the
> full amount of the selected charge installment. This was previously raised
> in FINERACT-591.
>
> 3. Charge adjustment supports a partial amount and creates a
> CHARGE_ADJUSTMENT transaction. However, its behavior is closer to a loan
> transaction adjustment that follows the configured transaction allocation
> rules, rather than an operation that only reduces the selected charge
> component. This was also discussed in FINERACT-2151.
>
> 4. On the interest side, there does not appear to be a dedicated
> INTEREST_ADJUSTMENT transaction type comparable to CHARGE_ADJUSTMENT. The
> generic transaction adjustment modifies an existing transaction by
> reversing it and creating a replacement transaction, so it is not
> equivalent to a standalone current-date interest adjustment.
>
> So while interest can be partially waived and charges can be partially
> adjusted, the two mechanisms are asymmetric in terms of component coverage,
> balance impact, accounting treatment, and audit semantics. For a business
> case that requires partial reduction of both interest and penalty/fee
> charges, it is not clear that current standard Fineract provides a
> consistent end-to-end solution.
>
> My questions are:
>
> 1. For a scenario requiring partial interest reduction plus partial
> penalty/fee reduction, is the currently recommended approach to use
> waiveinterest and charge adjustment separately?
>
> 2. Is there any existing plan or design direction for an
> INTEREST_ADJUSTMENT transaction similar to CHARGE_ADJUSTMENT?
>
> 3. From an accounting, reversal, re-amortization, or reporting
> perspective, is there a reason why a current-date interest adjustment
> similar to charge adjustment should not be introduced?
>
> Thanks,
> inar
>
>
>

Reply via email to