Overview
This article explains the impact of renaming an existing Pay Component Sub Type (PCST) in ZonePayroll and whether historical payroll data or employee setup is affected.
A common scenario is renaming a PCST (e.g., “Normal Time”) to align with internal terminology (e.g., “Ordinary Rate”).
Question
What happens if I rename an existing PCST code?
Do I need to update employee records or historical payroll entries?
Should I create a new PCST instead?
Answer
Renaming an existing PCST (changing the label/name only) is safe and will not impact historical payroll data.
Historical payslips will remain unchanged
Past payroll runs will continue to reference the original underlying PCST record
Only the displayed name in the system will be updated going forward
This means you can rename “Normal Time” to “Ordinary Rate” without affecting previously processed payroll results.
Impact on employee records
There is no need to update individual employee profiles when only the PCST name is changed.
Employees already assigned to the PCST will automatically see the updated name
No manual reassignment is required
No changes are required to existing pay configurations
Creating a new PCST vs renaming
You may consider creating a new PCST only if you need a functionally different pay component, for example:
Different tax treatment
Different calculation rules
Separate reporting requirements
Needing to preserve the old PCST as-is for audit or contractual reasons
If the change is purely cosmetic (naming consistency), renaming is the recommended approach.
Summary
Renaming a PCST only updates the display name
Historical payroll data is not affected
Employee setup does not need to be updated
Creating a new PCST is only required for functional changes, not naming changes