Skip to main content

Employee Offboarding

Verified process​

Initiation and decisions​

An employee with self-create access submits a required reason and requested last working date. Resignation date is fixed to the current date. The requested date defaults to the configured positive notice period or 90 days and cannot precede resignation. A second active exit request is rejected.

Authorized team managers can decide direct-report requests; tenant-wide administrators can decide same-tenant requests and confirm the last working date. An actor cannot approve or reject their own exit. A rejection reason is mandatory.

Rollback and final status​

An approved exit can be moved to RollbackRequested before the last working date. An authorized manager or administrator can approve it, making the request Cancelled and null-and-void, or reject it and restore the original active exit state. After the effective last working date has passed, an authorized administrator explicitly processes pending revocations. Processing disables the login user, marks its employment status Exited, deactivates the linked labor record when found, marks the request Completed, and records audit evidence.

Clearance, asset return, and final settlement​

The exit record has free-text notice, clearance, and final-settlement status fields, but the governed employee request flow does not update or enforce them. Asset Service can calculate a read-only clearance verdict from open issued, damaged, lost, or repair assets; the exit controller does not call it. Asset return, payroll settlement, leave closure, attendance closure, document issue, and clearance sign-off are Not implemented as an integrated offboarding flow.

Termination and separation​

Employee Service separately supports Terminated and soft deletion. The resignation flow uses Exited on the monolith login record and does not invoke Employee Service termination. Employer-initiated termination, retirement, contract end, relieving, archived state, and a general separation taxonomy Require confirmation.

Notifications​

An approval invokes the Exit.Approved notification path for an active employee. No source-backed notification was found for submission, rejection, rollback, access revocation, or completion.

Source References​

  • Controllers/HrOperationsController.cs
  • Models/ExitRequest.cs
  • Models/ExitRequestAuditLog.cs
  • microservices/src/employee-service/Domain/Employees/Employee.cs
  • microservices/src/asset-service/Application/Queries/AssetQueries.cs
  • Controllers/NotificationTemplatesController.cs
  • UI/salary-ui/apps/client-hrms-portal/src/pages/hr/HrOperationsPage.tsx

Revision Information​

  • Status: Draft
  • Last reviewed: 2026-07-20
  • Review cycle: Quarterly