Week closure and locking
The week closure makes the reports recorded for a week binding. Afterwards, the entries are write-protected for employees and can be evaluated or exported.
For week closure, the lock refers to the whole week or row. A lock directly on an individual report can also be caused by forwarding, approval or missing edit permissions.
Even when the week is closed, reports can still move through the approval process: assigned supervisors can still approve or reject reports that are assigned to them for approval. What is locked is later editing or deletion by employees.
Process
- Forwarded: individual days are forwarded for approval (only possible in the day view).
- Closure: the entire week is closed.
- Approval process: reports go through the configured approval stages.
- Approved: once all approval stages are complete, the report is approved.
Who is allowed to close or open?
- Super User (SU): at any time.
- Admin/Master (FA): within their own company or branch office.
- System: optionally automatically at the start of a new accounting period.
Rules at closure
- Open rejections: rejected reports must be corrected or resubmitted.
- Rule checks: codeto report checks automatically (breaks, hours, compensation, etc.). Errors prevent closure, warnings do not.
- Lock: after closure, entries are write-protected for employees. Assigned supervisors can still approve or reject reports that are assigned to them for approval; SU and FA can reopen in exceptional cases.
Automatic closure
Previous periods can be closed automatically at the start of a new payroll or accounting period.
Reopening
Closed weeks can be reopened with permission. The reopening appears in the audit log.