With the company structure ready, Sarah begins bringing real employees into the system so teams can start taking shape inside the platform with the correct department, designation, shift, and access role assignments from day one.
Invitations are then sent to employees so they can activate their accounts, verify their identity securely, and immediately access attendance, payroll, approvals, and self-service workflows.
Employee onboarding flows smoothly when identity, structure, and access information are configured correctly.
Once invitations are accepted, employees immediately become active participants in attendance, leave, payroll, and approval workflows.
| Failure | What the user sees | What happens next |
|---|---|---|
| Duplicate work email | "User with this email already exists" | Use a unique work email address |
| Duplicate employee code | "Employee code already in use" | Assign a unique employee code |
| Missing required onboarding field | Field-level validation errors | Complete all required employee details |
| Invalid role assignment | "Role not available for this company" | Assign a valid role within company scope |
| Department or designation not found | Validation rejects assignment | Select valid department and designation records |
| Invitation email delivery fails | Invite remains pending | Admin can resend the invitation |
| Invitation OTP expires before verification | "OTP expired" | Admin can resend a fresh invitation |
| Employee never accepts invitation | Pending invite visible in onboarding dashboard | Admin may resend or revoke the invitation |
| Incorrect employee email entered during onboarding | Invitation delivered to wrong recipient | Correct the email and resend invitation |
| Maximum employee seat limit reached | "Upgrade plan to add more employees" | Upgrade subscription or free unused seats first |
| Terminate employee with pending leave requests | Warning shown during separation flow | Reject or resolve pending leave requests before completion |
| Terminate employee with unprocessed payroll | Final settlement payroll required | Complete payroll settlement before termination |
| Terminate employee with active company loans | Outstanding balance warning shown | Resolve or transfer remaining liabilities first |
| Scenario | Behavior | Why |
|---|---|---|
| Employee already exists under another company | User is linked to the new company without creating a duplicate account | Supports multi-company employment scenarios |
| Previously removed employee is invited again | System sends a fresh onboarding invitation | Allows controlled reactivation workflows |
| Bulk onboarding through CSV import | Import validates rows individually and reports partial failures | Improves operational efficiency during mass onboarding |
| Employee rehired after separation | Existing employee profile is reactivated with a new employment record | Preserves employment and payroll history |
| Employee terminated but historical records are needed | Past attendance, payroll, and audit records remain preserved | Supports compliance and reporting requirements |
| Invitation link opened after revocation | Access is blocked and employee is asked to contact administrator | Prevents unauthorized onboarding access |
ZettaHRM
A modern HRM workspace for employee management, attendance tracking, leave approvals and structured day-to-day HR operations.