Status
All Systems Operational
We have implemented three key enhancements to the Pay Conditions Comparison (PCC) functionality to make managing employee comparison data smoother, clearer, and error-free. These enhancements include:
PCC commencement date validation:
Additional date validation now prevents a PCC record being created if the commencement date is earlier than an award’s first effective date. This is important so as to prevent eliminates unexpected PCC report generation failures later on.
For example, the SCHADS Award was published in our platform with a first effective date of 9/10/2014.
We will prevent a PCC record being created with a commencement date earlier than that because the system is unable to calculate comparison costs prior to that date.
Ending a PCC record:
You can now set an end date on an active PCC record. This gives you full control when employees transition from a salaried to an hourly paid engagement by ensuring the system automatically stops generating unnecessary comparison costs if they are no longer required.
Ending a record can be done via the UI or API.
We have introduced a new endpoint PUT .../payconditionscomparison/{id}/enddate, taking a single ComparisonEndDate field in the request body.
All PCC endpoints can be accessed via the API library.
Pay run breakdown in excel export:
When exporting the PCC report to excel, there is now an additional worksheet that includes the per pay run breakdown & variance data that already displays in the UI/PDF.
For more information:
