Home » FAQs
We’ve put together a selection of FAQs where we try to answer, erm, your FAQs
No, FCSA is not a regulator. We are a not-for-profit membership organisation and our members have to comply with our Charter and Codes as well as undergo rigorous and regular compliance assessments carried out by nationally renowned professional services firms.
FCSA members therefore have a legally-binding contractual obligation to abide by our Charter and Codes.
In fact, we support appropriate and relevant regulation.
Whilst FCSA is not a regulator, we do believe that the industry could become regulated in a well-informed and carefully considered manner. That’s why we work with BEIS, HMT, HMRC and other stakeholders to ensure that our Codes are fully up-to-date with both tax and employment law and often go above and beyond what is currently required.
Yes. We do ask that the provider’s own grievance/complaint procedure has been exhausted and we do need to know precisely which of our Codes the worker believes to have been breached and, of course, we cannot intervene in a dispute where the Courts or Tribunals are already involved, but we aim to deal with legitimate grievances in a fair and open manner as soon as we can.
We carefully consider every grievance or complaint we receive and to date we’ve upheld about 50% of them and, so far, almost all of the resolutions have met with approval from the original complainant.
Most grievances are actually just a misunderstanding of the way umbrella providers are obliged to work and a lot of those arise from misunderstanding of HMRC rules and guidelines. These can usually be resolved very quickly.
For example we often receive queries about salary sacrifice, especially when the worker wants to make changes but hasn’t been allowed to by their provider. This is usually because HMRC do not permit changes midway through the year unless there’s been a significant life event (e.g. marriage, divorce) – once we explain that to the worker then we have to conbsider the matter closed.
No, members have to undertake a significant and rigorously checked application process, including due diligence on the applying company and its directors as individuals and then undergo the assessment process. Only about 50% of applicants pass through the entire process.
These checks are repeated on a regular basis and “mystery shopping” takes place to ensure continued compliance.
No. In fact, most of our members are relatively small companies and about 25% of them have less than 1000 umbrella employees.
No. Existing members have no say on new members joining.
Provided that a new applicant can pass all our checks and fulfil the obligations placed on them by our Charter and Codes, then they will be accepted as a member.
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 |