Sarah starts with Company Profile because she knows every other module depends on this setup. If timezone is wrong, attendance becomes confusing; if currency is wrong, payroll and billing reports become misleading.
She carefully enters the legal company name, uploads the brand logo, updates office address, sets tax identification details, defines the fiscal year, and confirms the local timezone and operating currency.
The form validates cleanly, saves successfully, and immediately reflects the updated profile across admin-facing screens.
From this point, new attendance entries, report filters, and future payroll calculations use these defaults without requiring per-module manual setup.
| Failure | What the user sees | What happens next |
|---|---|---|
| Invalid tax ID format | Field highlighted with required format | User corrects and resubmits |
| Invalid currency code | Supported currency hint shown | User selects valid currency and retries |
| Fiscal year end date in the past | Warning shown | User can proceed or adjust date |
| Logo file too large or unsupported | Upload rejected with size/type message | User uploads a valid file |
| Scenario | Behavior | Why |
|---|---|---|
| Timezone changed after attendance data exists | Existing records unchanged; new records use new timezone | Preserves historical accuracy |
| Currency changed after payroll already ran | Applies to future payroll only | Avoids historical drift |
ZettaHRM
A modern HRM workspace for employee management, attendance tracking, leave approvals and structured day-to-day HR operations.