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
>
