The Freelancer & Contractor Services Association is seeking to ensure that all agency workers, including umbrella workers, receive furloughed pay calculated on average earnings. It is possible that some may only receive 80% of National Minimum Wage compared to others who do the same job but might receive 80% of their average wages. This difference is fundamentally unfair and must not be allowed to happen.
On 26 March 2020, the Chancellor, Rishi Sunak unveiled details of a Job Retention Scheme to help all UK employers retain their employees whose role has been adversely affected by coronavirus for at least 3 months starting 1 March 2020.
Whilst the scheme is welcomed by the FCSA, we are urgently seeking clarification on a number of key points relating to the calculation of pay of furloughed umbrella employees.
“Having looked closely at the information we currently have available to us, we are very concerned about how the pay rate of furloughed workers, whose income varies, such as umbrella employees, will be calculated under the Job Retention Scheme, and have requested urgent clarification from government on this matter,” said Julia Kermode, Chief Executive of FCSA.
“Most temporary workers secure their work through a recruitment agency. Once secured, the workers decide whether to be paid through agency payroll, an umbrella employer or through their own limited company, often called a Personal Service Company (PSC), if the worker is “in business”. Both agency payroll and umbrella employers provide PAYE solutions for their contingent workers with full tax paid on all variable earnings. “
“Umbrella employers guarantee to pay workers at least National Minimum Wage for hours worked even if the agency does not pay the umbrella. This is a contractual commitment which is intended to give umbrella employees additional stability and certainty. The balance of funds received from agencies is also paid to the workers and is often referred to as a discretionary commission or bonus (although it is not related to performance but rather to the umbrella having received the funds.).”
“We therefore believe that umbrella employees should be classified as “employees whose pay varies” in the same way as agency workers are categorised. To classify umbrella employees differently would be unfair as they are also agency workers. We are very concerned that, in guaranteeing National Minimum Wage and simply referencing the balance of the pay as bonus or commission, it may be argued at a later date that the 80% payment should only be based on National Minimum Wage and that balance of the pay is misconstrued as a performance-related bonus. Logically agency workers should be treated the same whether they have chosen umbrella or agency payroll as the method of being paid.”
“However, until we have confirmation from the government, then it is impossible for umbrellas to calculate furloughed pay based on an average of all earnings because there is a significant risk that this amount will not be reimbursed by the government.”
“We are actively lobbying on behalf of the circa 625,000 umbrella employees who would be affected by this guidance to ensure that they fairly receive furloughed pay based on their average earnings and not solely on 80% of NMW.”
The Freelancer & Contractor Services Association is strongly encouraging any affected umbrella employees to write to their local MP to make them aware of this situation and to represent their concerns to the Treasury.
To help you, we have created a letter template for you to send to your local MP – Download Now >
© 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 |