Skip to main content

Salary Components and Statutory Settings UI

Summary​

This page records confirmed salary components and statutory settings ui behavior and marks incomplete boundaries explicitly.

Audience​

Payroll users, developers, QA and support engineers, architects, and implementation reviewers.

Reference Content​

This screen inventory reflects the reviewed React route and component implementation.

Purpose​

Maintain salary components and statutory settings exposed by the client portal.

/salary/components and /salary/statutory-settings.

Users​

Component visibility accepts settings-salary-components or settings; statutory visibility also accepts statutory-payroll. Navigation targets Payroll/HR administrators.

Permissions​

The role, module, and feature conditions summarized above govern UI visibility. They do not prove API or gateway authorization; those enforcement boundaries are Requires confirmation unless separately confirmed in source.

Components​

DeductionsAllowancesPage, ImportExportToolbar, component form/list/delete confirmation, StatutorySettingsPage, statutory form/list/delete controls.

Fields and filters​

Components expose name, category, basis, default value, recurrence/effective/employee scope where implemented. Statutory forms expose the workspace fields returned by HR Operations.

Actions​

Load, create/update/delete components, validate/import/export component rows, and create/delete statutory settings.

Validation​

Component name and source-defined form fields are validated. Backend component rules and workspace validation remain authoritative.

Business rules​

Salary-component compatibility data and statutory workspace data have different ownership boundaries. A client-side import/export toolbar does not establish a Payroll bulk API, and a saved configuration is not versioned or approved by a Payroll workflow.

Success and failure states​

Confirmed states include loaded and empty configuration, save/delete success followed by refresh, import validation results, and load/save/delete errors. On failed validation, no successful configuration change should be inferred.

API usage​

Components use compatibility salary-component routes. Statutory settings use HR Operations workspace routes, not confirmed Payroll Service statutory endpoints. UI ownership is therefore split across compatibility and HR Operations boundaries.

Known limitations​

No approval/version-history UI exists for configuration changes.

Screenshot placeholder​

Capture the two configuration lists with synthetic component names and no rates or amounts.

Source References​

  • UI/salary-ui/apps/client-hrms-portal/src/App.tsx
  • UI/salary-ui/apps/client-hrms-portal/src/components/AppLayout.tsx
  • UI/salary-ui/apps/client-hrms-portal/src/utils/ProtectedRoute.tsx
  • UI/salary-ui/apps/client-hrms-portal/src/pages/hr/PayrollFeaturePages.tsx
  • microservices/src/payroll-service/Application/PayrollCompatService.cs

See Also​

Keywords​

  • Payroll ui
  • Salary Components and Statutory Settings UI

Revision Information​

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