SmartERP Documentation An Ashewa Technology Solutions Platform

Timesheet compliance and period locking

How SmartERP enforces timely timesheet submission, automates multi-tier manager escalations, locks historical accounting periods, and audits privileged overrides.

Accurate project costing and client billing require timely, reliable timesheet submissions. SmartERP Enterprise Timesheets (smart_enterprise_timesheet) provides compliance rules that compare logged hours against expected resource calendars, escalate chronic delays, and prevent backdated modifications through strict period locks.

Swimlane diagram of timesheet compliance. The administrator creates a rule with escalation levels. Every day SmartERP finds employees whose logged project hours are below the hours their calendar expects, emails reminders up to a maximum, and emails the configured recipients once the escalation level's days overdue is reached. The employee logs hours; the approver follows up. SmartERP writes every reminder and escalation to the history as sent, failed or skipped.
How timesheet reminders and escalations run.

Timesheet compliance rules#

Timesheet Compliance & Submission Board

Administrators configure compliance rules (smart.timesheet.control.rule) to establish organizational expectations for time tracking:

  • Target Hours: Evaluated dynamically against each employee's assigned working calendar (resource.calendar), accounting for approved leaves and Ethiopian public holidays.
  • Evaluation Frequency: Daily background scan identifies employees whose logged hours fall below expectations for the preceding day or week.
  • Gentle Reminders: An automated email reminder is dispatched directly to the employee prompt them to log missing hours (capped at a configurable maximum per week).

Multi-tier escalation engine#

When timesheet delays persist beyond acceptable thresholds, SmartERP triggers escalation lines defined in the compliance rule:

Escalation levelThreshold (Days overdue)Action takenRecipients
Level 12 days overdueWarning notification with list of unlogged dates.Employee and direct Line Manager
Level 24 days overdueHigh-priority escalation activity and email alert.Line Manager and Project Manager
Level 37 days overdueGovernance non-compliance flag on employee dashboard.Department Head and PMO Controller

Every notification and escalation event is permanently recorded in the notification history (smart.timesheet.notification.history) as sent, failed, or skipped.

Period locking and audit controls#

At fiscal period close (weekly, monthly, or quarterly), the finance team or PMO sets a Timesheet Lock Date (smart.timesheet.period.lock). Once locked, historical timesheet records are protected against tampering.

Decision diagram of the timesheet period lock. When a project timesheet line is created, edited or deleted, SmartERP checks whether its date is on or before the lock date. If not, the change is saved. If so, and the user holds the Override Locked Timesheet Periods group, the change is saved and written to the audit log; otherwise a message says the period is locked.
What happens when someone changes a timesheet line in a locked period.

Editing in a locked period#

When a user attempts to create, update, or delete a timesheet line with a date on or before the lock date:

  1. Standard Users: SmartERP immediately rejects the operation with a validation error stating that the accounting period has been locked.
  2. Authorized Supervisors: Users belonging to the privileged security group Override Locked Timesheet Periods (group_smart_timesheet_override) can modify locked records via a dedicated override wizard.
  3. Immutable Audit Log: Every override requires a mandatory justification reason. SmartERP writes the previous values, new values, timestamp, and author to the audit log (auditlog.log / smart.timesheet.period.lock.override).

Caution

Bypassing period locks without formal financial clearance can distort already-filed VAT returns, client billings, and recognized revenue reports.

Last updated: 2026-10-16