Automatic Lock Date

Accounting teams want to prevent back-dated postings but updating the lock date by hand is forgotten. This module updates the normal Global Lock Date every day through a scheduled action so that only the last N days remain open (for example on the 16th the lock becomes the 13th when N is 3). Selected users can be exempted through standard lock exceptions. The hard lock date is never touched. It plugs into Accounting settings and is used by accounting managers.

1. 1

   Open Accounting settings

   Go to Accounting > Configuration > Settings and find the Automatic Lock Date block. The settings belong to the current company. Each company is configured separately.

   • Company-level settings
   • Per company
2. 2

   Enable and set the open days

   Tick "Enable Automatic Lock Date" and set Open Days. The value cannot be negative. With 3 days, on the 16th the Lock Everything date becomes the 13th.

   • osloop_auto_lock_enabled
   • osloop_auto_lock_days
3. 3

   Choose exempt users

   Add users who may still post in locked periods to Exempt Users. The module creates and revokes standard lock exceptions to match the list when settings are saved. Removing a user revokes the exception.

   • Exempt users
   • Lock exceptions synced on save
4. 4

   Scheduled update runs daily

   A scheduled action computes today minus Open Days in the company time zone and writes it to the lock date. A failure in one company is logged and reported in the chatter without stopping others. The hard lock date is never changed.

   • Daily cron
   • Company time zone
   • Errors logged, others continue

Back to version applications