Mar 2022
22
BrightPay 2022/23 is now available (for new customers and existing customers).
Over the past year, we have continued to focus the majority of our development efforts on bringing a version of BrightPay to the cloud, which we plan an announcement on soon. But work on BrightPay for Windows and macOS continues. Here’s an overview of what’s new in 2022/23:
BrightPay for Windows is now a 64-bit application. This does not make any difference to the experience of using BrightPay or its functionality, but it comes with a few nice optimisations:
A 32-bit version of BrightPay for Windows will continue to be made available for those who need it.
(This does not affect BrightPay for macOS, which has always natively supported 64-bit Macs where applicable.)
Here's a quick reminder of some of the main areas of improvement:
We're continually at work on the next version of BrightPay, developing new features and making any required fixes and improvements. See our release notes to keep track of what has been changed to date at any time.
Mar 2021
22
BrightPay 2021/22 is now available (for new customers and existing customers).
2020 was challenging. Many of our development plans for the year had to be changed or postponed due to the need to cater for the Coronavirus Job Retention Scheme (CJRS) and the Coronavirus Statutory Sick Pay Rebate Scheme (CSSPRS) in BrightPay (not to mention the withdrawn-at-the-last-minute Job Support Scheme (JSS), which we invested many development hours on to no avail). We also have an Irish version of BrightPay, which likewise required additional time and attention on the equivalent schemes in the Republic of Ireland. And of course all of this had to be done in suboptimal conditions, with staff working remotely from home, often with young children. Demanding as it was, our team really stepped up, and as a company we were awarded with the COVID Hero Supplier Award at the Accounting Software Excellence Awards 2020.
At the same time, we have been working hard to bring a version of BrightPay to the cloud. While we have nothing to announce just yet, I can confirm it's going well, but it is still very much in development. We have a beta version planned, but cannot yet commit to a timeframe.
And so, given the time spent on COVID-19 features, along with that on cloud development, there hasn't been as much time as in previous years to spend on new features for BrightPay 2021/22. But we do have some new features, and we hope you'll find them useful. Rest assured that time-constraints have not caused any sacrifices to be made on quality – our goal to make the best payroll software continues as usual.
Here’s a quick overview of what’s new in 2021/22:
You can now create and send payment requests to Modulr directly from BrightPay, provided you have an active Modulr account that is set up for making payments. Payee information and amounts are automatically populated using the data from your payroll, making it a simple, fast and efficient way to pay your employees (or subcontractors).
BrightPay 2021/22 now supports posting journals directly via API to FreshBooks, QuickFile and ClearBooks.
Although 2020/21 updates were primarily focused on the CJRS, we did add a few other enhancements, all of which are of course included in BrightPay 2021/22. See our release notes for full details. Here's a quick reminder of some of the main areas of improvement:
We're continually at work on the next version of BrightPay, developing new features and making any required fixes and improvements. See our release notes to keep track of what has been changed to date at any time.
Oct 2020
26
BrightPay is built on a technology called WPF, which is part of Microsoft’s very popular .NET Framework. For .NET development on Windows, WPF has been the first-choice framework for over a decade, and is still very much going strong.
From its beginnings, WPF has included the ability to display and interact with web-based content in a special user interface component called WebBrowser
. BrightPay uses WebBrowser
to display the “log in” web pages that are required for certain API integrations (e.g. when submitting pension contributions or posting payroll journals to certain providers). WebBrowser
has worked well, but it has one aspect that is beginning to cause problems.
WebBrowser
is based on Microsoft’s Internet Explorer browser, which has an end-of-life support date of 21 August 2021, meaning that from then on it will no longer receive security updates. Apart from that, Internet Explorer lacks support for many modern technologies, and the web development community has been cheering on its deprecation for years.
In September 2020, BrightPay customers started to notice that our integration with QuickBooks (for posting payroll journals) is no longer working – the log in process results in a blank screen. This is happening because Intuit (the creators of Quickbooks) have dropped their support for Internet Explorer – they are now using technology that is simply too modern for Internet Explorer (and therefore BrightPay's use of WebBrowser
) to handle. In the coming months and years, one by one, many other cloud-based software providers will no doubt be doing the same.
So where does this leave BrightPay? Well, you might be aware that in 2015, Microsoft released the first version of their successor to Internet Explorer: the Edge browser. It wasn’t until 2019 that a WPF component for using Edge in Windows applications was made available. This component, called WebView
, is not perfect, however, and comes with some technological shortcomings that made us decide to not adopt it right away.
Despite the shortcomings with WebView
, when Intuit made their announcement that they would not support Internet Explorer anymore, we created a version of BrightPay that uses WebView
and began testing it internally. But not long after, Intuit revised their announcement, confirming that they would not be supporting the Edge browser either. This left us in a bit of a quandary.
Earlier this year, Microsoft released a new version of Edge, based on the same technology that powers the Google Chrome browser. Although it has the same name as the Edge browser from 2015, it is completely different (and Intuit have confirmed that the new Edge will be supported by Quickbooks). Microsoft have also since announced that they will be releasing a component to allow WPF applications to use the new Edge browser, called WebView2
, in Q4 2020. This is a much better component than WebView
, with wider support, less restrictions and improved deployment. It’s the obvious solution to our Quickbooks problem, except that at the time of writing this, it has still not been released. But it will be soon.
And so, our only real choice is to wait until the WebView2
component is available. As soon as it is, we will prioritise its integration. When that's done, BrightPay customers who need to post journals to Quickbooks should no longer have any issues.
In the meantime, BrightPay version 20.6 contains the WebView
component (based on the legacy Edge browser), as we have found that despite Intuit’s claim to not support legacy Edge, it seems to still work for posting journals to Quickbooks anyway. Hopefully, it will continue to do so until WebView2
is available.
Please note that to use WebView
in BrightPay 20.6, you (i) must have Windows 10 version 1803 or higher and (ii) you must not run BrightPay in administrator mode. Otherwise, BrightPay will fall back to using the Internet Explorer-based WebBrowser
, and the Quickbooks integration will not work. Also, to be able to support WebView
(and in preparation for supporting WebView2
), BrightPay now requires the .NET Framework version 4.7.2 or higher. If your computer does not already have this version, you will need to download and install it manually to be able to continue using BrightPay.
NOTE: BrightPay for Mac users are not affected by any of this.
UPDATE (January 2021): WebView2
was released in November 2021, and we were able to integrate it into BrightPay and complete a successful pilot test run with some of our customers. I'm pleased to confirm that BrightPay 20.8 (now available for everybody) contains WebView2
, and so should put an end to browser incompatibility problems for once and for all.
Jul 2020
1
When guidance for the Coronavirus Job Retention Scheme (CJRS) was first published in April 2020, HMRC did not provide comprehensive instructions on how to calculate the amounts for every scenario. Like other software providers, we were left to make certain assumptions with very little time for development.
One such scenario for which no official guidance was initially provided by HMRC was the handling of pay reference periods that are only partly encapsulated by a CJRS claim period (e.g. the week ending 3 May in a claim for 1–31 May).
BrightPay's initial handling of this scenario was to ignore the pay reference period start and end dates, and work solely from the pay date, i.e. if a pay date was encapsulated by a claim period, then BrightPay would include the full amount in the claim, regardless of whether the pay reference period start and end dates were fully or partially within the claim period. This reasoning is consistent with other payroll calculations (e.g. that for average weekly earnings for statutory pay), and was deemed adequate by HMRC in our communications with them.
Later, HMRC published new guidance on how to handle part pay reference periods that involved apportioning the pay by the number of encapsulated days in a claim period. For example, if an employee was paid £500 for the week ending 3 May, then the new guidance stated that only £500 ÷ 7 × 3 (£214.29) should be accounted for in a claim for 1–31 May (with the other 4 days in a previous claim).
At first, there was no urgency to update BrightPay, as claim period dates were flexible anyway, and as long as claim period dates were selected that aligned with the pay reference period dates (including the pay date), everything worked out.
But from July 2020, things are changing again.
From July 2020 onwards, to support flexible furlough, HMRC require that claim dates are strictly within a single calendar month. And so to meet this new obligation, we have had no choice but to change the CJRS calculation in BrightPay 20.5 to work the updated way, splitting pay reference periods where required and apportioning them by the number of days, regardless of pay date. (BrightPay 20.5 also supports flexible furlough, as well as the updated rules and rates for August, September and October.)
For many of our customers, this calculation change will not make a difference. But those who pay in lieu (e.g. a July pay date for June payroll), or those for whom an already submitted claim period ending 30 June did not actually cover all of June's earnings, will need to check and ensure that all reclaimable amounts are accounted for and submitted to HMRC prior to making July claims. Going forward, depending on the pay schedule and CJRS claim dates, it may also be necessary to finalise pay periods further in advance of when they would normally be finalised, to ensure that amounts from the beginning of such periods are picked up in a CJRS claim.
Mar 2020
19
BrightPay 2020/21 is now available (for new customers and existing customers). Here’s a quick overview of what’s new:
Along with the API support added for Sage, Quickbooks and Xero in 2019/20, BrightPay 2020/21 now supports posting journals directly via API to FreeAgent, Kashflow, Twinfield and AccountsIQ. The option to create a CSV journal is also still available where supported.
BrightPay has traditionally only allowed new employees to be added from a CSV file. Now, you can both add new employees and update existing employees from a CSV file. (The same has been done for subcontractors).
While we have traditionally focused our announcements of new features and updates in each new tax year version of BrightPay, it doesn't mean we're not busy during the rest of the year. In 2019/20, we released many updates and enhancements throughout the tax year, all of which are of course included in BrightPay 2020/21. See our release notes for full details. Here's a quick reminder of some of the main areas of improvement:
We're continually at work on the next version of BrightPay, developing new features and making any required fixes and improvements. See our release notes to keep track of what has been changed to date at any time.
Mar 2019
20
BrightPay 2019/20 is now available (for new customers and existing customers). Here’s a quick overview of what’s new:
A popular customer request has been to create a 'departmental' payroll journal in BrightPay. We've went one step further, allowing not only for a simple departmental mapping of nominal account codes, but for an advanced multi-option mapping as well.
For example, if you want to map commission paid to directors on a weekly basis in the sales department to a particular account code, you now can.
For Xero journals, BrightPay now supports including the department as the Xero tracking option, including where employees are split across multiple departments.
To make all this easier to manage, the Create Journal window in BrightPay now remembers it's size and position between usages.
BrightPay now supports posting journals directly to Sage, Quickbooks and Xero via API (while continuing to offer the creation of a CSV journal as an option if need be).
We have significantly improved the power and flexibility of how pay records are imported from CSV, effectively allowing an entire pay run to be imported from a single CSV file if need be.
A popular customer request has been for BrightPay to better handle the definition, carry-over and adjustment of annual leave in the situation where the annual leave year is offset from the tax year.
In BrightPay 2019/20, you can now enter the annual leave settings for each overlapping year individually, giving you full control and helping you work out entitlements more accurately.
In late 2018 we introduced a powerful new feature for Bureau customers of BrightPay Connect: the ability to request client payroll entry and/or approval for a payroll run, which is then automatically facilitated though a secure, GDPR-compliant process within the BrightPay Connect dashboard.
Sign in to your BrightPay Connect account and click the Requests header link to find out more.
While we have traditionally focused our announcements of new features and updates in each new tax year version of BrightPay, it doesn't mean we're not busy during the rest of the year. In 2018/19, we released many updates and enhancements throughout the tax year, all of which are of course included in BrightPay 2019/20. See our release notes for full details. Here's a quick reminder of some of the main areas of improvement:
We're continually at work on the next version of BrightPay, developing new features and making any required fixes and improvements. See our release notes to keep track of what has been changed to date at any time.
Mar 2018
20
BrightPay 2018/19 is now available (for new customers and existing customers). Here’s a quick overview of what’s new:
A popular customer request has been to show columns for number of hours worked and pension contributions on the BrightPay period summary view. In BrightPay 2018/19, you can now easily include these, as well as many more additional column options.
There is a new Email button in the print preview of documents and reports in BrightPay which allows you to easily send it as a PDF attachment in an email. Where and when applicable, BrightPay makes it easy and quick to select the relevant employee, client or previously used recipient.
Note: In version 18.0, there are a few document types for which email support is not yet available (e.g. P45, SMP1, etc) – we will be adding support for these very soon.
There is a new employer-wide calendar in the EMPLOYER section of BrightPay which amalgamates all the employee events along with other key payroll dates into a single view:
Several new Client Details fields have been added:
In BrightPay Agent Settings, you can now enter your own NEST delegate ID and password to use globally in NEST submissions:
While we have traditionally focused our announcements of new features and updates in each new tax year version of BrightPay, it doesn't mean we're not busy during the rest of the year. In 2017/18, we released many updates and enhancements throughout the tax year, all of which are of course included in BrightPay 2018/19. See our release notes for full details. Here's a quick reminder of some of the main areas of improvement:
We're continually at work on the next version of BrightPay, developing new features and making any required fixes and improvements. See our release notes to keep track of what has been changed to date at any time.
Here’s some of the new things coming in April/May 2018:
Mar 2017
20
BrightPay 2017/18 is now available (for new customers and existing customers). Here’s a quick overview of what’s new:
BrightPay 2017/18 enables you to produce a CSV payroll journal for import into your accounting software. This feature is accessed via the new Journal button on the payroll toolbar, and provides the following:
Several accounting software providers can accept a direct upload of a payroll journal via an API, negating the need to export/import a CSV file. We plan to add this functionality for supporting providers soon.
Please get in touch if you'd like to see built-in support for any other accounting software providers.
BrightPay 2017/18 includes several new features specifically targeted at accountants, bookkeepers, or other payroll bureau service providers. These bureau features are exclusive to the bureau version of BrightPay.
The columns on the BrightPay startup window can now be customised, and you can order the list of employers on the startup screen by any column. To help make this personalisation more useful, the size and position of the startup window will now be remembered between launches.
The data on the startup window now more reliably updates by itself - you no longer have to open a file to get it to do so.
You can now record the following client information for each employer in BrightPay:
This information can be edited directly from the startup window by right-clicking on an employer and selecting the new View/Edit Client Details menu option (this menu also includes a quick one-click link to set a label colour), or it can be entered via the new Client Details tab in Edit Employer Details when a file is opened in BrightPay.
Perhaps most usefully, these client details can be shown as columns on the BrightPay startup window, enabling you to more effectively manage your client workflows as an individual or across a team.
A new Batch Operation tab on the BrightPay startup window enables you to process or perform a task on multiple employer files with a single click.
The first supported batch operation is to send all outstanding RTI and CIS submissions.
We have plans to add more batch operations in future.
In BrightPay 2017/18, exported documents and files (e.g. payslips, P30s, reports, pension CSV files, journals, snapshots, etc.) are automatically organised into a separate folder structure for each of your clients by default. (If you don't want this, you can revert back to the previous functionality of exporting all files to a single location in BrightPay Preferences.)
In case you missed it, we launched "BrightPay Cloud" in summer 2016. We have now rebranded this as BrightPay Connect. It works exactly as it has to date, including some further refinements and new features for 2017/18.
We have a detailed web page about BrightPay Connect here. Here's a quick overview of what it's all about:
BrightPay Connect is built for security, reliability and stability, and costs just £49 per employer. Bulk pricing is available for bureaus.
While we have traditionally focused our announcements of new features and updates in each new tax year version of BrightPay, it doesn't mean we're not busy during the rest of the year. In 2016/17, we released many updates and enhancements throughout the tax year, all of which are of course included in BrightPay 2017/18. See our release notes for full details. Here's a quick reminder of the main areas of improvement:
17.0, 17.1, 17.2, 17.X... we're continually at work on the next version of BrightPay, developing new features and making any required fixes and improvements. See our release notes to keep track of what has been changed to date at any time.
Aug 2016
11
We’re pleased to announce that BrightPay Cloud is now available.
BrightPay Cloud brings several new features to BrightPay. These are described over on the dedicated BrightPay Cloud section of our website, and they aren’t covered in the same detail here. In this article, I’ll give you a background to BrightPay Cloud, where it currently stands, and where we’re heading next.
When we launched BrightPay in the UK back in 2011, the payroll software landscape was different. There was no RTI, and Auto Enrolment was still half a decade away for most employers. After noticing that the majority of payroll software product options had stagnated and were drawing many complaints from their customers, we entered BrightPay into the market as a nice, modern, easy to use and fairly priced alternative. We had our work cut out for us over the subsequent years adding features and responding to the big industry changes as they transpired. We’re very pleased to have been successful in our endeavours, as attested to by a browse through the BrightPay customer testimonials.
One feature area that has been trending in recent years is cloud functionality. BrightPay has always had a certain amount of cloud connectivity – software updates, licensing, emailing payslips and help documentation are all powered via the cloud, as are features like RTI and NEST submissions, as well as Auto Enrolment staging date checking. But there have been a number of big requests from customers over the years that we have not provided a solution for.
Until now.
Your payroll data is important. You need it to pay your employees accurately and on-time and to comply with HMRC reporting requirements. It’s not something you want to lose.
But backing up this important data often succumbs to human error. For example, we’ve heard from many customers over the years who requested that BrightPay would regularly remind them to backup their payroll data, simply because they forget. But a problem with a solution like this is that manually backing up data adequately is complicated. It’s not good enough to keep a backup of your files on your computer, as you can lose everything if your computer breaks. USB keys are handy, but they get lost. An off-site storage solution with data redundancy and geo-replication works great, but not everyone’s an IT expert.
So we wanted to provide a backup solution for BrightPay that just works.
With BrightPay Cloud, your payroll data gets automatically backed up to a secure cloud repository without you having to do anything – it’s that simple. As you run your payroll or make any other changes to data in BrightPay, it synchronises in the background. And it doesn’t just keep the latest backup - it keeps a history of backups, so even if you accidentally delete or change anything only to realise the mistake much later, you’re still covered. You can restore a cloud backup onto your current computer, or onto a new computer, at any time.
Many employers have already transitioned from printed payslips to digital payslips, often delivered via email. But wouldn’t it be great if employees had somewhere they could go to not only get their latest payslip, but to also access their entire history of payslips and other payroll documents at their own convenience? And what if they could easily see their own calendar of leave and personal tax details without having to contact HR?
BrightPay Cloud provides this facility through a feature called Employee Self Service. Using Employee Self Service, employees can do all the aforementioned tasks using their PC, Mac or smartphone. They can also make requests for leave and submit updates to their personal details, which, if approved, automatically synchronise back down to BrightPay on your PC or Mac.
You can set up Employee Self Service for your entire workforce or just a subset of employees, and you can control what they see and which features they have access to. Self Service will automatically notify your employees via email when their latest payslip or P60 is available.
How does BrightPay Cloud ensure employees always have access to the latest data? Well, as mentioned above, BrightPay Cloud automatically backups up your data to the cloud as you make changes. Self Service is powered by your most recent backup, and so, it just works.
Accountants and payroll bureaux get both of the above features with BrightPay Cloud – employer data files are automatically backed up, and your client’s employees can all get access to Employee Self Service.
But there’s more. Using BrightPay Cloud, you can provide an Employer Dashboard for your clients as well, allowing them to not only view their employees’ information, but also see an employer-wide calendar, access payroll reports that you define in BrightPay, and view the schedule of HMRC payments and liabilities.
Your clients can also use their Employer Dashboard to approve the leave requests and personal details update requests made by their employees, all of which synchronises back down to your data in BrightPay. You can give access to as many contacts for your clients as need be.
Our number one priority when creating BrightPay Cloud has been security. We spent a lot of time getting the best possible foundation and architecture in place before doing anything else.
The various data repositories and services which make up BrightPay Cloud are built using a compartmentalised design that maximises security. Strong encryption is used to store all data, as well as in communication with your PC or Mac. All popular kinds of attack are protected against. Your data is accessible only by you.
We selected the Microsoft Azure platform to power BrightPay Cloud, giving us reliability, scalability, data redundancy, geo-replication and timely security updates out of the box.
It’s worth noting that the most common weakness in any system like BrightPay Cloud is a poor password, so when choosing a password please remember to select something adequate, keep it safe, and change it often.
BrightPay Cloud costs just £49 per employer, per tax year (plus VAT). That price gives you a full year of cloud backups and Self Service for ALL your employees. When you renew BrightPay Cloud in the following year (at the same price), we will maintain the previous year’s data.
Bureau users, who may wish to purchase BrightPay Cloud for multiple clients, can get a bulk discount depending on how many employers they require (see pricing for details). The BrightPay Cloud pricing model is employer-based, unlike that for BrightPay on your PC or Mac, because it runs on a cloud platform that costs us in direct proportion to its usage. But we're competitively priced, and you still get the same support at no extra cost.
Our immediate plan is to continue making improvements to BrightPay, while enhancing BrightPay Cloud with advanced configurability, more features and additional access options.
We received a lot of responses to our recent BrightPay customer survey, which we have used to build a prioritised development plan. You can expect see several more BrightPay upgrades during the 16/17 tax year, and some nice new features for 17/18.
We’ve started building Self Service mobile apps for BrightPay Cloud to make it even easier and more convenient for employees to access their payroll information. And we have plans for improved branding and customisation, timesheets and more HR features.
We get asked from time to time about any plans we may have for a complete cloud version of BrightPay which could be used entirely via your web browser. While this is something we are continually looking at as we monitor the industry and customer expectations, we don’t have any announcements at this stage. Rest assured that even if we do go down that route in the future, the existing PC/Mac version is not something that would go away any time soon – we foresee a long lifespan for BrightPay and BrightPay Cloud, and look forward to working with you for many years to come.
Mar 2016
23
BrightPay 2016/17 is now available (for new customers and existing customers). Here’s a quick overview of what’s new:
BrightPay 2016/17 allows you to record all types of reportable expenses and benefits that you provide to your employees:
BrightPay can produce a P11D for sending to HMRC after year end which includes your Class 1A NICs declaration and details of the expenses and benefits provided including cash equivalents.
If you register for payrolling of benefits by 5 April 2016, BrightPay 2016/17 also supports calculating the PAYE on expenses and benefits in each pay period.
We will be back-porting some of the expenses and benefits features to BrightPay 2015/16 to allow you to send your P11D for the 2015/16 tax year. Look out for an upgrade in April/May.
Note: Expenses/benefits and P11D are not available for Free Licence customers.
BrightPay 2016/17 has full support for paying subcontractors under the Construction Industry Scheme (CIS):
Note: CIS is not available for Free Licence customers.
If you have not yet entered your Automatic Enrolment Staging Date in BrightPay, you can now connect directly to the Pensions Regulator and retrieve it automatically from within BrightPay.
BrightPay 2016/17 now tracks the number of enrolment/contributions submissions that you have not yet submitted to your pension scheme provider. The number is shown on the main PENSIONS tab, and contributes to the total number shown on the Open Employer screen (which also includes RTI and CIS).
We'll be continuing to update Automatic Enrolment during the 2016/17 tax year and provide dedicated support for more pension scheme providers.
BrightPay Cloud will allow you to connect your BrightPay employer data to a web based service that provides:
Automatically backs up your BrightPay data to the cloud. A historical set of backups is maintained. Your data file can be restored from an online backup at any time.
Enables employees to log in to a web-based portal using their PC, Mac or smartphone to retrieve payslips, view their calendar, request annual leave, view/update personal information, and more.
Enables payroll bureaux to provide an online portal not only for their customer's employees (i.e. employee self-service as described above), but also an employer portal for direct use by their employer customers, enabling them to view payroll reports, P30s, calendar, all employee information, and more.
BrightPay Cloud will work directly with BrightPay 2016/17, but also allow you to upload your BrightPay 2015/16 data to immediately have a full year of historical data to power the self-service features.
BrightPay Cloud will cost £49 per employer per tax year (with discounted bulk pricing for bureaux also available).
We'll have more news very soon. As a BrightPay customer, you'll be the first to know. Watch this space!
BrightPay 16/17 is the same price as BrightPay 15/16 (including FREE for small employers with up to three employees). Support will continue to be free of charge for all users.