Released 06.22.2017
New Features & Improvements | Web
ASC - Customized Earning Codes
On Monday, June 26th, all existing Time & Attendance administrators will be able to customize their export earning codes so they won’t have to change the export before submitting it to their payroll company. From the Configure tab of the ASC, users can select Earning Codes.
![]() |
Currently, the three payroll companies available for customized earning codes are Paylocity, PayChex Flex, and Paycor. Users are able to view what the default earning codes for each is by clicking View, however, if they want to add a customized set of codes, they need to click the Add An Earning Code Set button.
![]() |
When adding a new Earning Code Set, users are required to name the set (1) and select the Payroll Type (2) the set is for. They can then use the text fields to create their new Earning Codes (3) before clicking Save. Although the fields are alphanumeric, each field must contain at least one character other than a space or a special character.
![]() |
Once saved, the Earning Code Set will display on the Earning Codes landing page with the default sets. Users are able to view the payroll type the set is for and when it was modified. Custom Earning Code Sets can be edited and/or deleted, when the default sets can only be viewed.
![]() |
When generating payroll, the set will be selectable with the other payroll exports.
![]() |
The custom Earning Codes can then be viewed in the exported payrolls.
![]() |
ASC - Custom PTO Reasons in the Paycor Export
Customers using customized Paid Time Off reasons will now see those reasons and the hours approved in their Paycor payroll exports. The reason will appear in the “hoursCode” column, and the amount of approved hours will appear in the “codedHours” column.
![]() |
ASC - Custom PTO Reasons in the Paychex Flex Export
![]() |
ASC - Custom PTO Reasons in the Paylocity Export
Customers using customized Paid Time Off reasons will now see those reasons and the hours approved in their Paylocity payroll exports. The reason will appear in the third column, and the amount of approved hours will appear in the sixth column.
![]() |
Default Break Penalties
Improvements have been made to what is deemed a default Break Penalty for customers. Previously, a shift would be flagged as an exception if a meal wasn’t taken before hitting five consecutive hours when the meal rule was set for five hours. Now, to better align with the California Meal & Rest Breaks laws, as long as the employee clocks out for his or her meal at any time within the shift (even if that means after the five-hour mark), the shift will not be flagged as an exception and will not add a penalty pay. We will still support the ability to configure a rolling meal break rule where we will flag an exception when a meal and/or break is not taken within a consecutive time frame.
******************
Comments
0 comments
Please sign in to leave a comment.