Skip to main content

Payroll Freeze, Unfreeze, and Advance Troubleshooting

Summary

This page records confirmed payroll freeze, unfreeze, and advance troubleshooting behavior and marks incomplete boundaries explicitly.

Audience

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

Symptoms

Freeze/unfreeze is unavailable or fails, or an advance/recovery transaction is rejected.

Cause

Freeze can fail for ineligible/already Frozen state, no details, duplicate recovery, missing advance balance, or recovery above balance. Unfreeze requires Frozen state. Advance creation requires employee and positive amount; recovery cannot exceed remaining balance.

Resolution

Confirm route ownership, run state, detail count, advance summary, prior recovery/reversal evidence, and user UI feature. Correct the source record through approved application flows. Never force statuses or balances in the database.

Validation

Confirm the expected Frozen or Unfrozen/Draft compatibility state, audit/timeline evidence, recovery/reversal records, and refreshed UI balance without disclosing amounts.

Source References

  • UI/salary-ui/apps/client-hrms-portal/src/pages/salary/CalculateSalaryPage.tsx
  • UI/salary-ui/apps/client-hrms-portal/src/pages/salary/AdvanceSalaryPage.tsx
  • microservices/src/payroll-service/Application/PayrollCalculationService.cs
  • microservices/src/payroll-service/Application/PayrollCompatService.cs

See Also

Keywords

  • Payroll troubleshooting
  • Payroll Freeze, Unfreeze, and Advance Troubleshooting

Revision Information

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