Blog post written in collaboration with Clipper Contracting.
Up until the start of the Covid-19 pandemic in 2020, the term ‘furlough’ was little known in the UK. Unlike our neighbours across the pond and other European nations, the UK didn’t have an existing ‘short-time work’ scheme and so the Coronavirus Job Retention Scheme (or CJRS) was announced by the Chancellor in late March 2020. This would become commonly referred to as ‘furlough’ and supported up to 11 million people at a cost of £53 million.
With the CJRS announced on the 20th of April 2020, the first national lockdown was announced shortly afterwards. The CJRS paved the way to allow workers to stay home without businesses having to make wholesale redundancies.
The announcement in the press led to a wave of questions from workers, especially temporary workers whose assignments were coming to an abrupt end. There was concern for workers on how they would survive the uncertainty. For umbrella companies, just like other businesses, there was an initial lag period as the official government guidance was digested.
As an employer, it seemed logical that umbrella companies would be able to access the scheme and use it to fund 80% of an employee’s normal income. And just like reputable businesses in other sectors, umbrella companies wanted to do the right thing and explore how to support their workers.
There was initial hesitation though; the HMRC guidance on the CJRS was so new, that legal opinion was required. Umbrellas could not find themselves in a situation where they had fallen foul of the guidance only to have HMRC asking for funds to be repaid. This liability had to be managed. The umbrella company sector pulled together at the time and through online discussions, organised by the FCSA and APSCo with various legal experts and individual private legal interpretation, Accredited Members were satisfied that they could implement furlough for workers that qualified.
Now whilst the CJRS was voluntary and not all companies chose to furlough workers, the vast majority of umbrella companies did, and by aggregating costs and processes, the contractors were able to access this government scheme.
There were also many uncompliant ‘umbrella’ companies whose contracts were not true employment contracts. Those using hybrid schemes missed out on this vital support whilst those offering genuine employment arrangements, such as those umbrella companies that adhere to the FCSA codes of compliance, were able to support workers.
It is important to note that umbrella companies could not provide the furlough scheme to some workers due to certain restrictions in place. The main being government legislation surrounding length of employment.
Of the FCSA Members who have been audited by HMRC for their furlough payments, all have passed.
–
Cost To Umbrella Companies
What many didn’t appreciate at the time, was the considerable cost involved in administering this voluntary scheme. The CJRS guidance didn’t allow the employer to hold funds back to cover their costs of implementation. These costs were borne by the umbrella companies alone.
For example, many could not furlough their own staff, in order to keep phone lines open and systems online to deal with the compliance and many queries relating to the furlough scheme. Legal costs were incurred in working out whether the scheme could be implemented. The umbrellas continue to bear the liability if they furloughed a worker against the CJRS guidance.
In employing workers, an umbrella company bears all the employment liabilities, even in the hard and unexpected times.
–
Clipper Contracting During Furlough
© Freelancer and Contractor Services Association Ltd 2022.
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". |
CookieLawInfoConsent | 1 year | Records the default button state of the corresponding category & the status of CCPA. It works only in coordination with the primary cookie. |
elementor | never | This cookie is used by our website to allow the us to implement or change the website's content in real-time. |
hubspotutk | 5 months 27 days | HubSpot sets this cookie to keep a record of the visitors to the website. This cookie is passed to HubSpot on form submission and used when deduplicating contacts. |
JSESSIONID | session | The JSESSIONID cookie is used by New Relic to store a session identifier so that New Relic can monitor session counts for an application. |
PHPSESSID | session | This cookie is native to PHP applications. The cookie is used to store and identify a users' unique session ID for the purpose of managing user session on the website. The cookie is a session cookies and is deleted when all the browser windows are closed. |
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. |
_GRECAPTCHA | 5 months 27 days | This cookie is set by the Google recaptcha service to identify bots to protect the website against malicious spam attacks. |
__hssc | 30 minutes | HubSpot sets this cookie to keep a record of sessions and to determine if HubSpot should increment the session number and timestamps in the __hstc cookie. |
__hssrc | session | This cookie is set by Hubspot whenever it changes the session cookie. The __hssrc cookie set to 1 indicates that the user has restarted the browser, and if the cookie does not exist, it is assumed to be a new session. |
__hstc | 5 months 27 days | This is the main cookie set by Hubspot, for recording visitors. It contains the domain, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session). |
Cookie | Duration | Description |
---|---|---|
__cf_bm | 30 minutes | This cookie, set by Cloudflare, is used to support Cloudflare Bot Management. |
__hssc | 30 minutes | HubSpot sets this cookie to keep a record of sessions and to determine if HubSpot should increment the session number and timestamps in the __hstc cookie. |
Cookie | Duration | Description |
---|---|---|
hubspotutk | 5 months 27 days | HubSpot sets this cookie to keep a record of the visitors to the website. This cookie is passed to HubSpot on form submission and used when deduplicating contacts. |
_gcl_au | 3 months | Provided by Google Tag Manager to experiment advertisement efficiency of websites using their services. |
_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. |
_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. |
_hjIncludedInSessionSample | 2 minutes | Hotjar sets this cookie to know whether a user is included in the data sampling defined by the site's daily session limit. |
__hstc | 5 months 27 days | This is the main cookie set by Hubspot, for recording visitors. It contains the domain, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session). |
Cookie | Duration | Description |
---|---|---|
test_cookie | 15 minutes | The test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies. |
Cookie | Duration | Description |
---|---|---|
baqend-speedkit-user-id | 5 months 27 days | No description available. |
heyzine_session | 3 months | No description |
_hjSessionUser_2855694 | 1 year | No description |
_hjSession_2855694 | 30 minutes | No description |