HMRC announced in July that a 57-year-old male had been arrested as part of an investigation into a suspected £495,000 Coronavirus Job Retention Scheme Fraud. The individual was also suspected of multi-million-pound tax fraud and alleged money laundering.
The Job Retention Scheme put in place at great speed in March of this year was openly recognised by employers and HMRC as being at risk of being abused. HMRC rapidly established a “whistle-blowing” portal for employees and others to report deliberate abuse of the scheme.
Prosecutions were always to be expected, then, but what perhaps is a surprise is the speed at which the first one has occurred.
The latest figures from HMRC reveal that more than £27.4 billion has been claimed by over 1.1 million employers, covering in excess of 9.4 million furloughed jobs.
Under the Finance Bill 2020 (which became law on 22 July 2020) HMRC now has the statutory right to claw back payments not due under income tax and corporation tax at 100%. The clawback mechanism will not only apply to instances of deliberate abuse, but also in cases of non-compliance including genuine errors. In cases of intentional wrongdoing, where cases are “deliberate and concealed” penalties of up to 100% of the amount claimed will also be imposed.
It’s very likely that some employers may have inadvertently breached the rules. The speed at which the scheme was introduced, the urgency of the situation for employers, lack of clarity from the outset and growing complexity as the scheme has evolved all have had a role to play. Some of the scheme’s rules were only announced by HMRC well after employers had implemented their schemes.
To help unpick the situation, HMRC have advised employers to retain records for up to five years and have made it clear that inspections will follow.
There is some good news for employers. HMRC have announced a 90 day amnesty period allowing employers to avoid sanction or penalty if they put right errors no later than from 90 days when the Bill was granted Royal Assent (22 July 2020) or the income tax becomes chargeable.
It is, therefore, prudent for employers – even where they believe they have acted in good faith – to check that all records and payments received are in line with the scheme rules. Any unintentional breaches should be put right immediately as penalties even for genuine errors under existing legislation can be raised by HMRC.
Your internal review should look at furlough records and payments, and consider whether to undertake employee sampling to check they were not instructed to work by line managers whilst on furlough. Such audits will provide useful evidence of compliance if employers are subject to HMRC inspections in the future.
This continues to be a unique and challenging time for businesses, where decisions have been made rapidly and not always with the full picture of potential implications. Taking time now to review and verify your actions is important to protect your organisation’s reputation and choose the right future path.
Vero HR offer professional outsourced payroll services and employment law services if you are looking for help and advice, get in touch.
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. |