Week 56 cannot be entered into Report generator

Pro rata payments calculated incorrectly when a new starter started in a previous pay period when using the 260 day year rule

Note: this error only applies to Pay groups using the Count Mondays to Fridays based on a 260 day year rule (the option that treats all months across the tax year as an equal length). This can be found in the Modify pay group window:

Prior to Flexipay version 2.53.1.0, while using this rule, the calculation would be incorrect when calculating a payment for New starters with a Pro rata salary if they were being paid for a number of days that covers two Pay periods (for example when a New starter began in the previous month).

For example, an Employee may have begun work in the final week of April 2020, and then were added to a Pay cycle for their first payment in May 2020. Flexipay was calculating the standard length of the two Pay periods as if it were one month (e.g. 21.67 days instead of 43.33 days). When the Employee was viewed in the Enter payroll details screen, their Std. period days Field would display this incorrect value. Due to Flexipay having already doubled the full pay value for two Pay periods, this was causing Flexipay to divide the correct number of days worked by the wrong number of Std. period days, leading to incorrect Pro rata values.

This error has been corrected for version 2.53.1.0. Now, when this situation would occur, Flexipay correctly accounts for two Pay periods and the Pro rata will now be correct.

Employees are now excluded from HMRC P60 submissions correctly

If an Employee is marked as Exclude from HMRC in their Employee details, Flexipay now correctly excludes them from the Employee selection when producing P60s:

 

Class 1A NI now shows on the Analysis of Payment details report

As of version 2.53.1.0 Flexipay will now display Class 1A National Insurance contributions on the Analysis of Pay Elements report, such as those generated by a Sporting fee:

Email and password Anonymisation

When creating an anonymised Flexipay data copy prior to version 2.53.1.0, Flexipay was not correctly randomising entries in an Employee's Email address and Password fields. This has now been corrected so that these two pieces of information are randomised. 

P46(Car) submission errors for an incorrect Range of electric car

Prior to Flexipay version 2.53.1.0, it was possible to submit an erroneous P46(Car) submission to HMRC. Flexipay would not properly validate whether a car had correctly set up its Range of electric car in relation to their CO2 emissions. Under HMRC guidelines, the Range of electric car must only be submitted if its CO2 emissions are between the appropriate values.

Similarly, if the CO2 emissions of a car are outside this range of values, then the Range of electric must contain a value. 

New errors have been added to the P46(Car) submission log to catch these errors before they are sent to HMRC. 

If a car is set to have a Range of electric car when their CO2 emissions do not fall between the appropriate values, then the following error will appear:

If a car does not have a Range of electric car when their CO2 emissions fall between the appropriate values, then the following error will appear: