HRM Module - Gap Analysis & Missing Features

What's missing, what's broken, and what needs to be fixed in the Frontend

Generated: 2026-04-08 | Analysis based on Backend v0.6.0 vs Angular Frontend

Navigation: Scorecard Critical Gaps High Priority Medium Priority Bugs & Mismatches Missing Form Fields Missing Feature Matrix Industry Comparison Implementation Roadmap ← Full Analysis

1. Overall Scorecard

72%
Overall Frontend Coverage
19/27
Sub-Modules with UI
5
Completely Missing
3
Partially Implemented
9+
Missing Form Fields
3
Value Mismatches (Bugs)

Coverage by Category

CategoryBackend EndpointsFrontend CoverageScore
Core Organization (Departments, Positions, Shifts, Settings) 18
100%
 Complete
Employee Management 8
60%
 Partial
Schedules 4
0%
 Missing
Attendance + Corrections 7
71%
 Partial
Leave (Types + Balances + Requests) 15
80%
 Partial
Salary (Components + Structures) 8
63%
 Partial
Payroll 9
100%
 Complete
Loans 6
100%
 Complete
Recruitment (Openings + Candidates + Applications + Offers) 21
55%
 Partial
Performance (KPIs + Templates + Reviews) 17
100%
 Complete
Training (Programs + Sessions + Enrollments) 13
100%
 Complete
EOS 6
100%
 Complete
Reports 6
100%
 Complete

2. Critical Gaps (Completely Missing Features)

These features have full backend API support but zero frontend implementation.

GAP-01: Shift Schedules

CRITICAL | Backend: 4 endpoints | Frontend: 0%

What's missing: No component, service, model, or route for shift schedule management.

Backend supports:

  • List schedules with filters (employee, department, shift, date range)
  • Bulk create schedules (assign multiple employees to a shift for date range + specific weekdays)
  • Update individual schedule records
  • Delete schedules

Business impact: Cannot assign employees to shifts. Shifts are defined but never used. Attendance has no reference shift to compare against. Overtime/late calculations are unreliable without schedule data.

Files needed:

src/app/features/hr/schedules/hr-schedules.component.ts   (new)
src/app/core/services/hr-schedule.service.ts               (new)
src/app/core/models/hr-schedule.model.ts                   (new)
+ route in app.routes.ts
+ nav item in sidebar config

GAP-02: Attendance Corrections

CRITICAL | Backend: 2 endpoints | Frontend: 0%

What's missing: No UI to submit or approve attendance corrections. No model, no service methods, no dialog.

Backend supports:

  • Submit correction request (corrected check-in/out times + reason)
  • Approve/reject correction (with rejection reason)

Business impact: Employees cannot correct incorrect attendance records. Managers cannot review correction requests. Late/absent records cannot be disputed. This is a standard HR requirement.

Implementation: Can be added as a sub-feature within the existing Attendance component (tab or dialog).

GAP-03: Leave Balances

CRITICAL | Backend: 3 endpoints | Frontend: 0%

What's missing: No component, service, or model for leave balance management.

Backend supports:

  • List balances per employee/fiscal year/leave type
  • Initialize balances for all active employees (respects gender, service months)
  • Adjust balance (add/subtract days with reason)

Business impact: Cannot initialize annual leave quotas. Cannot view how many days employees have remaining. Cannot adjust balances for exceptions. Leave requests work but don't validate against available balance. EOS leave payout is manually entered instead of calculated.

Implementation: New standalone component or integrate into Leave Types/Requests screen.

GAP-04: Salary Structure Assignment

CRITICAL | Backend: 3 endpoints | Frontend: 0%

What's missing: No UI to assign salary components to individual employees or apply mandatory components.

Backend supports:

  • View employee's current salary structure
  • Assign specific component to employee (with amount, effective dates)
  • Bulk-apply all mandatory components to active employees

Business impact: Salary components are defined but never assigned to employees. Payroll calculation relies on mandatory flag only; per-employee customization is impossible. Housing allowance, transportation, etc. cannot be configured per employee.

Implementation: Add as a tab in Employee detail view OR within Salary Components screen.

GAP-05: Job Offers Management

CRITICAL | Backend: 5 endpoints | Frontend: Service only, NO UI

What exists: HrOfferService with all methods (CRUD + send + accept + reject). Model HrOffer is defined.

What's missing: No component, no route, no navigation menu item. The complete offer lifecycle is inaccessible from the UI.

Backend supports:

  • Create offer from job application (salary, start date, position, terms)
  • Send offer to candidate
  • Accept offer → auto-create employee from candidate data
  • Reject/withdraw offer

Business impact: The full recruitment pipeline is broken. Cannot formalize offers to candidates. Cannot auto-create employee records from accepted offers (the most powerful recruitment feature). Must manually create employees.

Implementation: New component OR integrate into Candidates component as an additional dialog/tab.

3. High Priority Gaps (Partially Implemented)

GAP-06: Employee Documents (Upload/View/Delete)

HIGH | Backend: 2 endpoints | Frontend: 0%

What's missing: No file upload UI for employee documents. Backend supports uploading contracts, certificates, visas, medical records (max 5MB) and deleting them.

Exists: photo field in model but no upload control. Backend has POST /employees/{id}/documents and DELETE /employees/{id}/documents/{doc}.

Needed: File upload section in employee form (ideally a new "Documents" tab) showing uploaded documents with type, title, issue/expiry dates, and delete action.

GAP-07: Employee Emergency Contacts

HIGH | Backend: Multiple contacts | Frontend: Single contact only

Current state: Form has only 2 fields: emergency_contact_name and emergency_contact_phone. Only one contact supported.

Backend supports: Multiple emergency contacts per employee, each with: name, relationship, phone, alternative_phone, address.

Needed: Replace single fields with a repeatable section (add/remove contacts) or nested table.

GAP-08: Employee Dependents

HIGH | Backend: Full CRUD | Frontend: 0%

What's missing: Completely absent from frontend. No model, no service, no UI fields.

Backend supports: Employee dependents with: name, relationship (spouse/child/parent/sibling/other), date_of_birth, national_id, notes.

Used for: Insurance beneficiaries, family allowances, visa sponsorship, tax deductions.

GAP-09: Employee Termination Workflow

HIGH | Backend: Dedicated endpoint | Frontend: No UI

Current state: Service has terminate(id, data) method. Form has status dropdown but no dedicated termination dialog.

What's missing:

  • Dedicated termination dialog with date + reason fields
  • termination_date and termination_reason form fields
  • Proper workflow: select employee → "Terminate" button → dialog with required fields → confirmation

Currently: Can only change status dropdown to "terminated" which sends a basic update, not the proper /status endpoint.

GAP-10: Recruitment Pipeline View

HIGH | Backend: Pipeline endpoint exists | Frontend: List view only

Backend has: GET /api/hr/applications/pipeline returns candidate counts by stage (screening, interview, assessment, offer, hired).

Frontend missing: No visual pipeline/Kanban/funnel view. Applications are nested inside candidates as a sub-dialog only.

Needed: Visual pipeline showing candidates flowing through stages, possibly as a Kanban board or funnel chart on the recruitment dashboard.

4. Medium Priority Gaps

GAP-11: Leave Calendar View

MEDIUM | Backend: Calendar endpoint | Frontend: Not used

Backend has GET /api/hr/leave-requests/calendar returning approved leaves in date range. Frontend doesn't display a calendar view of who is on leave when.

GAP-12: Attendance Bulk Import

MEDIUM | Backend: Bulk endpoint | Frontend: Not implemented

Backend supports POST /api/hr/attendance/bulk for batch check-in of multiple employees. Frontend has no bulk import UI.

GAP-13: Attendance Summary View

MEDIUM | Backend: Summary endpoint | Frontend: Not used

Backend has GET /api/hr/attendance/summary returning per-employee totals (present days, late count, overtime hours, etc.) for a date range. Could enhance attendance reporting.

GAP-14: Payslip Generation

MEDIUM | Backend: Payslip endpoint | Frontend: Unknown

Backend has GET /api/hr/payroll/{id}/payslip?employee_id=X. Need to verify if the frontend payroll component uses this for individual payslip viewing/printing.

GAP-15: Auto-Hire from Offer

MEDIUM | Backend: hire() endpoint | Frontend: Not implemented

Backend's POST /api/hr/offers/{id}/hire automatically creates an Employee record from the candidate + offer data. This powerful feature has no frontend trigger. Depends on GAP-05 (Offers UI).

GAP-16: NgRx Store Underutilization

LOW | Architecture concern

8 NgRx store slices (24 files) exist but are largely bypassed. Components call services directly using signals. This is a deliberate design choice but creates dead code. Either fully adopt NgRx or remove unused slices.

5. Bugs & Value Mismatches

These are actual bugs where frontend values don't match backend expectations.

#LocationIssueFrontend ValueBackend ValueSeverity
BUG-01 Employee Form → Contract Type Mismatched enum values 'full_time', 'part_time', 'contract', 'temporary', 'probation' 'permanent', 'contract', 'part_time', 'probation' HIGH
Impact: Selecting "full_time" sends an invalid value to backend. "permanent" is never selectable. "temporary" doesn't exist in backend.
Fix: Replace 'full_time' with 'permanent'. Remove 'temporary'. Backend ContractType enum: permanent, contract, part_time, probation.
BUG-02 Employee Form → Status Dropdown Missing status option 'active', 'inactive', 'suspended', 'terminated' 'active', 'on_leave', 'suspended', 'terminated', 'resigned' HIGH
Impact: Cannot set employee status to "on_leave" or "resigned". "inactive" doesn't exist in backend EmployeeStatus enum.
Fix: Replace 'inactive' with 'on_leave'. Add 'resigned'. Backend enum: active, on_leave, suspended, terminated, resigned.
BUG-03 Candidates → Application Stage Mismatched stage names 'pending', 'shortlisted', 'interviewed', 'offered', 'hired', 'rejected' 'applied', 'screening', 'interview', 'assessment', 'offer', 'hired', 'rejected' MEDIUM
Impact: Stage values sent to backend don't match ApplicationStage enum. Pipeline view (if added) would be broken.
Fix: Align frontend options with backend ApplicationStage enum: applied, screening, interview, assessment, offer, hired, rejected.

6. Missing Form Fields (Employee Component)

Fields that exist in the backend model but are absent from the frontend employee form.

FieldTypeForm TabWhy It MattersPriority
contract_start_date DatePicker Employment Separate from hire_date; contract may start later. Important for contract/probation tracking. HIGH
probation_end_date DatePicker Employment Critical for probation management. Determines when employee becomes permanent. HIGH
currency_id Dropdown (FK) Salary & Bank Multi-currency salary support. Important for companies with branches in different countries. MEDIUM
payment_method Dropdown Salary & Bank How salary is paid: bank_transfer, cash, or check. Affects payroll processing. HIGH
passport_number Text Personal Required for visa processing and travel. Standard HR data point. MEDIUM
country Dropdown/Text Personal Country of residence. Different from nationality. LOW
termination_date DatePicker Employment/Termination Required when status is terminated/resigned. Currently no way to record this. HIGH
termination_reason Textarea Employment/Termination Legal requirement in many jurisdictions. Important for EOS calculation context. HIGH
photo File Upload Personal Employee photo/avatar. Field exists in model but no upload UI. LOW

7. Complete Missing Features Matrix

#FeatureBackendServiceModelComponentRoutei18nPriority
1Shift Schedules Ready Missing Missing Missing Missing Missing CRITICAL
2Attendance Corrections Ready Missing Missing Missing N/A (within attendance) Missing CRITICAL
3Leave Balances Ready Missing Missing Missing Missing Partial CRITICAL
4Salary Structures Ready Missing Missing Missing N/A (within employee/component) Missing CRITICAL
5Job Offers UI Ready Exists Exists Missing Missing Missing CRITICAL
6Employee Documents Ready Missing Missing Missing N/A (within employee) Missing HIGH
7Emergency Contacts (multi) Ready Missing Missing Partial N/A Missing HIGH
8Employee Dependents Ready Missing Missing Missing N/A (within employee) Missing HIGH
9Termination Workflow Ready Exists Partial Missing N/A Missing HIGH
10Recruitment Pipeline Ready Exists Exists Missing N/A Missing HIGH
11Leave Calendar Ready Missing N/A Missing N/A Missing MEDIUM

8. Industry Standard Comparison (HRMS)

Comparing Moon ERP HRM against standard HRMS features found in systems like SAP SuccessFactors, BambooHR, Odoo HR, and ERPNext HR.

Feature CategoryIndustry StandardMoon ERP BackendMoon ERP FrontendAssessment
Organization Structure Departments, positions, hierarchy, org chart Has all Has all On par. Missing: visual org chart component.
Employee Lifecycle Hire, probation, promotion, transfer, terminate Has most Partial Hire and terminate workflows incomplete on frontend. No promotion/transfer tracking.
Time & Attendance Check-in/out, overtime, corrections, biometric integration Has all Partial Missing corrections UI and bulk import. Biometric source supported but no integration UI.
Shift Management Shift definitions + schedule assignment + rotation Has definitions + schedules Definitions only Schedule assignment completely missing from frontend. Rotation not supported.
Leave Management Types, balances, requests, approvals, calendar Has all Missing balances + calendar Core leave workflow works. Balance management and calendar view missing.
Payroll Components, structures, processing, accounting, payslips Has all Missing structures Payroll processing complete. Per-employee salary structure assignment missing.
Recruitment Job postings, candidates, pipeline, offers, onboarding Has all except onboarding Missing offers + pipeline Job postings and candidates work. Offer management and pipeline view missing.
Performance KPIs, templates, reviews, 360-degree feedback Has most Has most Solid implementation. Missing: 360-degree feedback, goal tracking.
Training Programs, sessions, enrollments, certificates Has most Has most Good implementation. Missing: certificate generation, LMS integration.
Self-Service Portal Employee self-service for leave, attendance, payslips Settings exist Not implemented Settings for self-service exist but no employee portal. All admin-only currently.
Document Management Employee files, contracts, certificates, expiry alerts CRUD exists Not implemented Backend ready. No frontend upload/view. No expiry alerts.
Compliance Labor law, GOSI, WPS, tax calculations EOS only EOS only EOS follows Saudi Labor Law. No GOSI, WPS, or tax modules.

Industry Maturity Score

AreaScoreNotes
Backend API completeness85/100Comprehensive. Missing: promotion/transfer tracking, GOSI, onboarding, employee self-service API
Frontend implementation65/100Good foundation but 5 features completely missing, 5 partially implemented, 3 bugs
Data model coverage90/10033 models covering most HRMS needs. Missing: promotions, transfers, warnings/disciplinary
Workflow coverage75/100Good approval workflows. Missing: onboarding, offboarding, probation reviews
Reporting70/1006 reports. Missing: headcount forecasting, compensation analysis, compliance reports

9. Implementation Roadmap

Recommended order of implementation based on business impact and dependencies.

Phase 1: Bug Fixes (1-2 days)

  1. BUG-01: Fix contract_type enum values in employee form (full_time → permanent)
  2. BUG-02: Fix status dropdown values (add on_leave, resigned; remove inactive)
  3. BUG-03: Fix application stage enum values to match backend

Impact: Immediate data integrity fix. Prevents invalid data from reaching backend.

Phase 2: Missing Employee Fields (1-2 days)

  1. Add contract_start_date, probation_end_date to Employment tab
  2. Add payment_method dropdown to Salary & Bank tab
  3. Add currency_id dropdown (linked to currencies)
  4. Add passport_number, country to Personal tab
  5. Add termination_date, termination_reason (shown conditionally)

Impact: Completes the employee data model. All fields already in TypeScript model.

Phase 3: Critical Missing Features (1-2 weeks)

  1. GAP-03: Leave Balances - New component + service + model + route
  2. GAP-04: Salary Structures - Add to employee view as tab or dialog
  3. GAP-01: Shift Schedules - New component with calendar/grid view + bulk assign
  4. GAP-02: Attendance Corrections - Add to attendance component as tab
  5. GAP-05: Job Offers - New component or dialog within recruitment

Impact: Enables core HR workflows. Leave balances and salary structures are prerequisites for correct payroll.

Phase 4: Employee Enhancement (3-5 days)

  1. GAP-06: Employee documents upload/view/delete (new tab)
  2. GAP-07: Multiple emergency contacts (repeatable section)
  3. GAP-08: Dependents CRUD (new tab)
  4. GAP-09: Dedicated termination dialog with proper workflow

Impact: Completes employee lifecycle management.

Phase 5: Recruitment Enhancement (3-5 days)

  1. GAP-10: Pipeline view (Kanban or funnel chart)
  2. GAP-15: Auto-hire from offer (trigger employee creation)
  3. Link offer management to candidate workflow

Impact: Completes the recruitment-to-hire pipeline.

Phase 6: Nice-to-Have (future)

  • Leave calendar view
  • Attendance bulk import UI
  • Employee self-service portal
  • Org chart visualization
  • Document expiry alerts
  • Promotion/transfer tracking
  • Clean up unused NgRx store slices

10. Quick Reference: Files to Create/Modify

New Files Needed

# Shift Schedules (GAP-01)
src/app/features/hr/schedules/hr-schedules.component.ts
src/app/features/hr/schedules/hr-schedules.component.html
src/app/features/hr/schedules/hr-schedules.component.scss
src/app/core/services/hr-schedule.service.ts
src/app/core/models/hr-schedule.model.ts

# Leave Balances (GAP-03)
src/app/features/hr/leave-balances/hr-leave-balances.component.ts
src/app/features/hr/leave-balances/hr-leave-balances.component.html
src/app/features/hr/leave-balances/hr-leave-balances.component.scss
src/app/core/services/hr-leave-balance.service.ts
src/app/core/models/hr-leave-balance.model.ts

# Job Offers (GAP-05) - could be standalone or within candidates
src/app/features/hr/offers/hr-offers.component.ts  (if standalone)

Files to Modify

# Bug fixes + missing fields
src/app/features/hr/employees/hr-employees.component.ts      (BUG-01, BUG-02, fields)
src/app/features/hr/employees/hr-employees.component.html     (add fields, docs tab, etc.)
src/app/features/hr/candidates/hr-candidates.component.ts     (BUG-03)
src/app/core/models/hr-employee.model.ts                      (add dependent/document types)

# Attendance corrections
src/app/features/hr/attendance/hr-attendance.component.ts     (add corrections tab)
src/app/features/hr/attendance/hr-attendance.component.html
src/app/core/services/hr-attendance.service.ts                (add correction methods)
src/app/core/models/hr-attendance.model.ts                    (add correction interface)

# Salary structure
src/app/features/hr/salary-components/hr-salary-components.component.ts  (add assignment UI)
src/app/core/services/hr-salary-structure.service.ts          (new service)

# Routes & Navigation
src/app/app.routes.ts                                         (add new routes)
src/app/layout/config/nav-items.config.ts                     (add nav items)
src/assets/i18n/ar.json                                       (new translation keys)
src/assets/i18n/en.json                                       (new translation keys)

← Back to Full Analysis

Moon ERP HRM Gap Analysis | Generated 2026-04-08 | Analysis by Claude