Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: "LOCK" at month end to prevent backdated transactions #137

Open
dentm42 opened this issue Jun 7, 2019 · 1 comment
Open

Comments

@dentm42
Copy link

dentm42 commented Jun 7, 2019

  1. Provide a setting that disallows adding new transaction with dates prior to a certain date or the editing transaction with dates prior than a certain date.
  2. Provide a user permission to allow certain users to "override" and enter backdated transactions - but also requires that an annotation field be filled out to explain the need for the backdated transaction.

This would be helpful to prevent accidental (or intentional but unauthorized!) restatement of past accounting periods during the year. It would be better in most cases to enter transactions in the current (sub)-period to correct errors to previous periods than to go back and edit previous entries that have already been reported out to boards and others.

Likewise, the ability to lock specific transactions from changes and/or provide an audit trail for edits to transactions would be beneficial.

@prashants
Copy link
Owner

Log is available for audits. You can even check mysql logs for more through audits.

Other things are possible but you have to customize it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants