In our previous Furlough blog we highlighted how important it is to check furlough payment claims, and that HMRC had announced a 90 day ‘amnesty period’ for employers to put right any errors. This applies to furlough claims submitted prior to 22 July 2020. Furlough claims raised after 22 July each have a 90-day amnesty period.
The deadline of 22 October 2020 isn’t far away now – so this blog is a timely reminder for internal audits/checks to make sure everything is in line with the scheme rules.
Naturally, given the speed at which the Coronavirus Job Retention Scheme (CJRS) was introduced and that the rules emerged over time, some employers will have inadvertently made incorrect claims. There are, of course, others who have deliberately claimed fraudulently.
Under HMRC’s amnesty period, employers that have found claims to be either wrong or fraudulent, can put their claims right without fear of prosecution, investigation or fines. What’s more, there’s no limit on how many ‘honest Joe’ amnesty updates you can make.
Failure to take advantage of the amnesty period could lead to HMRC audits, penalties, public naming and even prosecutions. HMRC have already made numerous arrests for furlough fraud.
HMRC have advised that they will adopt a ‘risk-based’ approach to identifying incorrect or fraudulent claims.
This could, for example, focus on certain sectors that show an historical trend for errors and fraud. A key factor will be whether the claim ‘looks right’. Where errors are found, HMRC will write to employers giving them an opportunity to rectify their claim.
Letters started to be issued by HMRC from mid-August, with thousands sent to employers each week. HMRC have also started following up 8,000 furlough fraud accusations received via their portal. All large employers are receiving letters encouraging them to check and correct their claims.
A clear message is that, for honest mistakes, HMRC will work with you to correct your claim rather than trigger an investigation.
The most common reasons why furlough claims are likely to be wrong or invalid are as follows:
There is no doubt that business leaders and payroll teams have done their best to interpret the emerging rules around the CJRS. Payroll professionals have faced the most difficult period in their careers trying to ensure correct compliance with limited information.
Mike Kealey is Managing Director of Vero, the company behind Vero Pay’s outsourced payroll services. He said: “I for one am proud of our payroll team. They have worked so hard during these unprecedented times to support our clients with their furlough claims”.
The additional complexity too of flexible furlough, whilst welcomed by many employers, added to the risk of unintentional errors in calculations. This is one more important reason to review whether claims have been submitted correctly.
We recommend that employers undertake audits so all is in order should they be subjected to an HMRC audit in the next five years.
When undertaking an internal audit the following tips should be kept in mind:
Many organisations understandably took up the CJRS in anticipation of financial impact, but for some, the impact has not been as at first feared. For a fortunate few, financial results have in fact been better than expected.
One major American owned business that has prospered from the crisis has pledged to donate all its above-budget profits to the US treasury.
Some UK employers have also promised to repay some or all of their furlough claims to HMRC. HMRC will be setting up a facility for employers to donate claims legitimately claimed but in hindsight not needed.
If you would like further advice on any of the issues discussed here, then email us at enquiries@verohr.co.uk
Cookie | Duration | Description |
---|---|---|
cookielawinfo-checkbox-advertisement | 1 year | Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category . |
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
elementor | never | This cookie is used by the website's WordPress theme. It allows the website owner to implement or change the website's content in real-time. |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
Cookie | Duration | Description |
---|---|---|
bcookie | 2 years | LinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser ID. |
lang | session | This cookie is used to store the language preferences of a user to serve up content in that stored language the next time user visit the website. |
lidc | 1 day | LinkedIn sets the lidc cookie to facilitate data center selection. |
Cookie | Duration | Description |
---|---|---|
_ce.cch | session | CrazyEgg |
_ce.gtld | session | CrazyEgg |
_ce.s | 1 year | CrazyEgg |
_ga | 2 years | The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors. |
_gat_UA-174055290-1 | 1 minute | A variation of the _gat cookie set by Google Analytics and Google Tag Manager to allow website owners to track visitor behaviour and measure site performance. The pattern element in the name contains the unique identity number of the account or website it relates to. |
_gid | 1 day | Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously. |
_hjAbsoluteSessionInProgress | 30 minutes | Hotjar sets this cookie to detect the first pageview session of a user. This is a True/False flag set by the cookie. |
_hjFirstSeen | 30 minutes | Hotjar sets this cookie to identify a new user’s first session. It stores a true/false value, indicating whether it was the first time Hotjar saw this user. |
_hjid | 1 year | This is a Hotjar cookie that is set when the customer first lands on a page using the Hotjar script. |
_hjIncludedInPageviewSample | 2 minutes | Hotjar sets this cookie to know whether a user is included in the data sampling defined by the site's pageview limit. |
li_gc | 2 years | Used to store consent of guests regarding the use of cookies for non-essential purposes. |
li_sugr | 3 months | LinkedIn Insight Tag, when IP address is not in a Designated Country. |
vuid | 2 years | Vimeo installs this cookie to collect tracking information by setting a unique ID to embed videos to the website. |
Cookie | Duration | Description |
---|---|---|
bscookie | 2 years | This cookie is a browser ID cookie set by Linked share Buttons and ad tags. |
Cookie | Duration | Description |
---|---|---|
AnalyticsSyncHistory | 1 month | No description |
UserMatchHistory | 1 month | Linkedin - Used to track visitors on multiple websites, in order to present relevant advertisement based on the visitor's preferences. |
wmc | 10 years | No description available. |