[
https://issues.apache.org/jira/browse/FINERACT-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17564562#comment-17564562
]
Francis Guchie commented on FINERACT-1635:
------------------------------------------
[~bgowda]
this helps a lot more than i expected
1- Let us have the business date merged and completed first
2- While we have it working, we will then move to the next steps as you have
clearly explained above. This means while we brain storm, we are going to wait
and see the business date in action first
> 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)
