Release Notes for Jane HR Version 2.10
IMPORTANT
Jane Payroll users must install this upgrade before running the final calculation, period end and FPS of 2014-15.
Payroll
Global Tax Code Update – New Tax Code Suffixes
Payroll > Functions > Global Tax Code Update
The new tax code suffixes, M and N have been added to the Payroll > Functions > Global Tax Code Update window.
Change to Regulatory Limit
New legislation for the 2015 tax year requires that the previous basis of operation for K codes is now applied to all tax codes and the maximum amount of an employee’s gross pay that will be liable to income tax will not exceed 50%. The calculation has been enhanced to reflect the change in legislation.
New NI Categories
Payroll > Module Setup > Module Definitions > NI Table
HR Record > Payroll > Payroll Details > NI & PAYE
From 6 April 2015 employers with employees under 21 years old will no longer have to pay Class 1 secondary National Insurance contributions on earnings up to the Upper Secondary Threshold (UST) for those employees. Therefore, HMRC have introduced the following new NI categories:
- M – not contracted-out standard rate contributions
- Z – not contracted-out deferred rate contributions
- Y – mariners not contracted-out standard rate contributions
- P – mariners not contracted-out deferred rate contributions
- V – mariners contracted-out salary related contributions
- I – contracted-out salary related standard rate contributions
- K – contracted-out salary related deferred rate contributions
The software has been altered to facilitate these new categories.
Upper Secondary Threshold (UST)
Payroll > Module Setup > Module Definitions
Payroll > Module Setup > Template
As above, the new Upper Secondary Threshold (UST) has been added to input and display windows and the payroll calculation. For the 2015-2016 the value is the same as the Upper Earnings Limit (UEL). The new value of this field is imported as part of the Parameter Import function which you will do as part of your year end procedures. Alternatively, it can be entered manually.
SCON
Payroll > Definitions > Pension Scheme
The entry of an SCON has been extended to other NI categories as part of HMRC legislative changes.
Full details of rates and threshold for 2015-16 can be found at:
https://www.gov.uk/rates-and-thresholds-for-employers-2015-to-2016
Payslip – Printing Salary Sacrifice Pensions
If an employee’s pension part of a salary sacrifice scheme, it is now possible to show the pension value paid on their payslip in either the payments or the deductions column. To use this feature, on the Payroll > Definitions > Module Setup > Template window, select the Payslip tab and click Pensions(s) under the Deduction Column Includes list.
Reporting Salary Sacrifice Pensions on FPS
Payroll > Definitions > Module Set Up > Pension Scheme > Controls
If you select the Exclude Contributions from FPS check box for a particular pension scheme, then all pension contributions calculated for the employee for that scheme will not be included in the Full Payment Submission (FPS) to HMRC. This may typically be used for salary sacrifice pension schemes.
Automating Overtime Rates Paid
Payroll > Definitions > Fixed Payments/Deductions
A new feature has been added to the software to automate the rates paid to an employee for overtime depending on how many hours at each band they have worked. Using the self service portal, an employee may enter a single figure of overtime and this will be apportioned accordingly. For example, an employee entering 17 hours overtime may see this be split into 10 hours at normal rate and 7 hours at time and a half.
You may use this for employees who are paid a salary for fixed number of hours per week, normal time up to the standard hours in a working week and then overtime for anything which exceeds the standard hours.
You may also use this for non-salaried employees who are simply paid variable rates which increase in bands over the number of hours worked.
To set up, select Payroll > Definitions > Fixed Payments/Deductions and create a payment for overtime. On the General tab select Rate from the Type dropdown. On the Defaults tab select one of the Units – Accumulated – options from the Limit Type dropdown. Enter the total number of hours at the standard rate into Upper Limit. Select the next payment code to use when the Upper Limit is exceeded from the Calculation Code dropdown. On the Calculation tab enter the details for how to calculate this overtime rate (for example, Hourly WTE * 1.5 for time and a half). For more details on setting up payments and deductions refer to the software’s Information Centre.
The upper limit (of hours worked at the standard rate) set up on the payment may be overridden for individual employees. Enter an individual upper limit into Direct Hours on the HR Record > Employment > Employment History > Terms tab.
Personnel
Absences Entry
HR Record > Personal > Absences
The Absence entry window has been enhanced to allow multiple absences to be entered on the same day, for example, an absence of holiday in the morning and sickness in the afternoon. The start and end times of absences are checked and you will be warned if you try to enter absences with time clashes. This enhancement is also reflected in the Self Service and Authorised User Portals.
Absence Review in Hours
HR Record > Personal > Absence Review
You can now set a default absence duration of hours (instead of days) for each employee so that the summary displayed on HR Record > Personal > Absences Review window is always accumulated in hours. Previously you were required to select a duration as part of the search criteria.
To set up the default as Hours, first set up a Query to select all the employees you wish this to apply it to. This may simply be “all employees”. Select the System Setup > Housekeeping > System Definitions > Absences tab and select your Query from the Display Hours – Qualifying Query dropdown.
Staff Development
Training Events Attendees
Staff Development > Functions > Event Workbench > Attendees
A data confirmation prompt has been removed to facilitate quicker data entry.
System Setup
Creating Data Import Templates
System Setup > Authorisation Centre > Workbench
A new feature has been added to the Authorisation Centre to provide templates for importing data. These can be particularly useful during data migration exercises as part of your initial set up. To obtain a template, on the System Setup > Authorisation Centre > Workbench > Function tab select the data you will be importing from the Source drop down (for example Appraisals). Select the Authorise tab and click the Template button. You need to give the output file a name with a .csv suffix. For example, Appraisals.csv.
The resulting file created has two rows of headings. The first row is a meaningful description and the second row is the actual database field name. Your template can now be populated with data using, for example, Excel. The first row (of meaningful descriptions) must be deleted before using the Authorisation Centre’s Import function to import the data.
HESA
HR Record > Credentials > HESA
The HESA module has been updated to the 2014-15 specification in readiness for this year’s submissions and the flooding and mapping functionality updated accordingly. The following fields have been added:
- HR Record > Credentials > HESA Person > Qualification – Current Academic Discipline
- HR Record > Credentials > HESA Person > Employment – ORCID identifier
- HR Record > Credentials > HESA Contracts > Terms – Research Assistant
- HR Record > Credentials > Additional Activity
Workflow
System Setup > Housekeeping > Diary Rules
A new option of Minutes has been added to the Units drop down on this window. If you create a diary rule with Type = Event (Workflow) and Units = Minutes you can impose a delay between the trigger and the start of a workflow.
This can be used to resolve a situation where a workflow is triggered by the update of a particular field but needs to include information which may not be updated until later.
Example. An employee updates their address through the self service portal and a workflow to email the new information to their line manager and confirmation to themselves is trigger by the change of their postcode. At the point the postcode field is updated and the workflow is triggered, the other lines of address may still be the original address. Adding a delay (of, say, 5 minutes) ensures that all the address fields have been updated to the new ones before the email is sent.