To assist users in transitioning to tax year 2026-27 we have compiled a list of frequently asked questions below.
a) Is it ok to import my data into 2026-27 BrightPay before my payroll is finished for the 2025-26 tax year?
- We advise waiting until your payroll is fully completed for the current tax year before importing into the new tax year version. This will ensure the most accurate and up-to-date information is being imported from the previous tax year.
b) How do I import my data from 2025-26 BrightPay into 2026-27 BrightPay for the new tax year?
- Please see our step by step guide on how to import your data into the new tax year here.
- Your employer and employee details will now be imported into 2026-27 BrightPay.
c) Do I need to set up my payment schedule for the new tax year?
- No your payment schedule will automatically be created based on the settings in the previous tax year that you have imported. You will be ready to start processing your payroll.
d) Are employees that were leavers in the previous tax year imported?
- No employees that were processed as leavers in BrightPay in the previous tax year will not be imported. You can still access this information in the previous tax year.
e) Do I need to send a new Employer Payment Summary to HMRC to claim the Employment Allowance?
- Yes. Since 6th April 2020, Employment Allowance does not auto renew for an employer as it did in previous tax years.
- An employer now has to submit an Employer Payment Summary to HMRC every tax year to notify HMRC that they will be claiming the Employment Allowance.
- Once this EPS is sent to HMRC, the employer can then enable the Employment Allowance in the first tax period within the 'HMRC Payments' utility in BrightPay.
-
Please note: HMRC must also be notified via an Employer Payment Summary if you are no longer eligible for the Employment Allowance.
- Further guidance on operating the Employment Allowance in BrightPay is available here.
f) Why am I receiving an error message "The pay schedule has a first pay date before of the 2026/27 tax year. This is not allowed, you must go back and fix the schedule before you can continue" when I try to set up my schedule?
- This message is relating to the Pay date not being set in the new tax year (not the period end). The period end can be in the previous tax year ie week ending Sunday 5th April 2026, but the pay date must be on 6th April 2026 or later for it to fall in the 2026/27 tax year.
- It is the payment date, not the period end which dictates which tax year the payment falls into.
- If you receive this message, check the 'By default, the pay date should be' field when setting up your schedule & ensure that this date falls into the 26/27 tax year:
If you cannot see the 2026/27 tax year option in the dropdown menu, ensure that you are in the 'Browse Employers' screen to be able to access the new tax year. If it is still not showing, try to refresh your browser and then click on the tax year dropdown again to switch tax years.
Important: Once you move to a new year, make sure to bookmark it. This will simplify things each time you log in.
In BrightPay Cloud, you are only billed for employers that are active in the current tax year. If you have an employer that you do not wish to process payroll for in the new tax year, simply do not import that employer when starting the new tax year. If the employer is not imported, you will not be charged for them in that tax year. There is no need to delete the employer unless you want to permanently remove all their data from your account.
Important:
If you no longer wish to process payroll for an employer in the new tax year, do not delete the employer.
Simply do not import the employer into the new tax year during the rollover process. This will keep all historic payroll records safe in BrightPay Cloud for reference and audit purposes.
Only delete an employer if you are absolutely certain that all their payroll data, including all previous years, should be permanently removed from the system. Deletion is permanent and cannot be undone.
Comments
0 comments
Article is closed for comments.