You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@fineract.apache.org by "Francis Guchie (Jira)" <ji...@apache.org> on 2022/07/07 16:56:00 UTC

[jira] [Assigned] (FINERACT-1635) Posting transactions in the past Vs Closing entries

     [ https://issues.apache.org/jira/browse/FINERACT-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Francis Guchie reassigned FINERACT-1635:
----------------------------------------

    Assignee:     (was: Rahul Pawar)

> 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)