[
https://issues.apache.org/jira/browse/FINERACT-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17564336#comment-17564336
]
bharath gowda commented on FINERACT-1635:
-----------------------------------------
[~francisguchie] the business date function developed by [~adamsaghy] is at the
whole application layer and it will not solve the problem as the date would be
applicable to the closure date as well.
In short, this Business_date acts like a server date where the application
treats every entry as happening as of that Business_date.
This feature developed is very beneficial for any organization who would like
to do past days entries by setting the business date to that date where
Accounting Date, Transaction Data, and Accounting Closure Date will follow the
same date function and afraid will not solve our problem.
More details on the Implemented business date concept can be found in this
document
https://mifosforge.jira.com/wiki/spaces/PS/pages/3079733251/Introducing+Business+Date+into+Fineract+-+technical+version
The one that I mentioned in my first comment is a different type of
implementation where the business date and value date will be divided into two
sections where portfolio transaction can follow the business date whereas
accounting entry would follow the value date. for this, we will have to do more
brainstorming on each edge case to solve our closure problem
Hope this helps.
> Posting transactions in the past Vs Closing entries
> ---------------------------------------------------
>
> Key: FINERACT-1635
> URL: https://issues.apache.org/jira/browse/FINERACT-1635
> Project: Apache Fineract
> Issue Type: Bug
> Reporter: Francis Guchie
> Priority: Major
> Attachments: image-2022-06-08-18-22-24-540.png
>
>
> As opposed to many other systems, in Apache-fineract, there is not need to
> run end of day end of month procedures. Thanks to cron jobs under the
> scheduler jobs
> However, for users that are always lagging behind due to staffing and other
> challenges, the function of *closing entries* creates an avenue of fraud
> also, closing entries can be *DELETED*
> It would nice to add a global setting that restricts users from posting back
> dated entries
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
