| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Lines of code | 648 |
| Technical Name |
byn_period_lock_governance |
| License | OPL-1 |
| Website | https://bynify.com |
| Versions | 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Lines of code | 648 |
| Technical Name |
byn_period_lock_governance |
| License | OPL-1 |
| Website | https://bynify.com |
| Versions | 18.0 19.0 |
Accounting Governance Toolkit
Accounting Period Lock
Control accounting period reopen requests with strict approval workflow, lock window governance, and audit-ready event logs.
Overview
Accounting Period Lock prevents uncontrolled unlock actions after period close. Each reopen request is tracked with requester, approver, start/end window, and relock trace.
Designed for finance and controllership teams that need compliant period lock governance without slowing correction workflows during month-end and year-end close.
Use Cases
- Period-end adjustment entry with approval.
- Short reopen window for audit correction.
- Controlled fix for account classification issues.
Business Impact
- Lower audit risk from undocumented unlocks.
- Clear accountability across finance roles.
- Traceability of postings during unlock window.
Features
- Request lifecycle: Draft, Submitted, Approved, Active, Rejected, Done, Expired.
- Policy by company with approver setup and max unlock duration.
- Self-approval prevention and strict governance mode.
- Manual relock + automatic relock cron.
- Event logs and posted-entry capture during unlock windows.
- Role-based approval control with clear separation of duties.
Installation
- Place addon in your Odoo addons path.
- Update Apps list.
- Install Accounting Period Lock.
- Configure policy in Accounting > Period Lock Governance > Policies.
Usage
- Create Request: define reason, target period, and unlock start/end window.
- Submit: request goes to approver queue with request context and risk window.
- Approve/Reject: approver validates policy and either rejects or approves.
- Activate Unlock: approved request opens controlled posting window.
- Monitor Activity: review entries posted during unlock window for reconciliation.
- Relock: relock manually any time or rely on auto-relock at end datetime.
Recommended production setup: enable self-approval prevention and separate requester/approver users.
Access Rights
- Period Lock User: create and track requests.
- Period Lock Approver: approve, activate, relock, review logs.
- Period Lock Admin: manage policy and governance settings.
FAQ
Can requester self-approve?
No, when self-approval prevention is enabled.
What if no one relocks manually?
Auto relock cron restores lock state automatically at unlock end.
Does this send accounting data outside Odoo?
No. Data stays inside your Odoo environment.
Why Teams Buy This
Audit-ready close process
Controlled reopen window
Approval accountability
Lower finance risk
Support
Need implementation support? Contact support@bynify.com.
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module