Hi there, I have a suggestion for simplifying the logic a bit:
Instead of using past and current month concepts, I would rather use `number of days till it is allowed` concept. However, I have a feeling that a follow-up requirement will soon be introduced to allow “force” transactions that ignore this restriction in case of edge case situations. I’d love to hear your thoughts on this. Regards, Adam Saghy > On Jul 13, 2026, at 6:27 AM, Abhishek Chaudhary <[email protected]> > wrote: > > Thanks, Anu! > > I think both are valid use cases. > > James' proposal fits organisations that reconcile monthly—a calendar-month > boundary is simple and predictable ("nothing before the previous calendar > month"). A rolling N-day window works better for organisations that reconcile > daily or weekly and need tighter control. > > Since GlobalConfigurationProperty already has a numeric value, we could > support both with a single config: > > Enabled with no value → allow transactions within the current and previous > calendar month. > > Enabled with value = N → allow transactions within the last N days (relative > to the business date). > > The config would still be disabled by default, so there's no behaviour change > for existing deployments. > > I already have a PR implementing the calendar-month behaviour > (https://github.com/apache/fineract/pull/6124). If everyone is okay with this > approach, I can fold the optional N-day support into the same PR. > > Regards, > Abhishek Chaudhary >
