Home » Steps To Accreditation
If you are considering applying for FCSA Accreditation, you may have questions about what is involved in the compliance review process:
The FCSA is the UK’s leading membership body dedicated to raising standards and promoting supply chain compliance for the temporary labour market. The scope of FCSA’s Accreditation covers 6 types of business operations in the UK: umbrella employment, limited company advisors, professional employment organisations, worker, fixed term employment, and self-employed/CIS contractor providers.
All companies which, by common ownership or common directorship, fall within scope of FCSA’s compliance codes, must be put forward for assessment.
In order to be eligible for FCSA Accreditation, all applicants must meet, and evidence, all of the following criteria:
The above minimum criteria are essential for FCSA to be able to assess applicants’ business operations in practice, not just in theory. It is important to realise that FCSA Accreditation is not just a tick-box exercise.
A Fit and Proper Person Form is required to be completed for each director of the business. Upon receipt of payment and the completed forms, the due diligence checks can be undertaken. Application for membership is to be made for all companies within the group, and/or with common ownership or directorship, that offer services falling within the scope of FCSA Accreditation, even if they are separate companies and/or are branded separately. Once the FCSA Chief Executive and its Board have approved the initial application, you will be invited to engage with an assessor.
In order to achieve FCSA Accreditation, applicants are independently assessed against our published standards. The process requires applicants to provide documentary evidence of how they adhere to each and every standard. In addition to the paperwork element, assessors conduct in-depth interview with the applicant business to interview their staff, test scenarios, undertake random checks, listen to on-boarding calls and assess that all policies and procedures are being implemented in practice.
FCSA will select assessors for the accreditation compliance check process from the list below. Should there be a conflict of interest or impartiality, the Assessor will not be eligible to assess that applicant. All FCSA Code assessors are either appropriately qualified tax professionals or solicitors and have at least five years of demonstrable experience of specialising in the freelance sector.
Financial Assessors
Legal Assessors
All applications require the completion of the Mandatory Code of Compliance and therefore both financial and legal assessors are required. The services you offer defines which other compliance codes you will be asked to complete. The cost of the application is the same whichever assessors you select. Upon payment to FCSA of the invoice, FCSA will ask the chosen assessor to commence the review.
The review involves a 3 stage review process:
Once all their queries have been answered, your assessors will report their findings to FCSA, who will then make the final decision, based on the evidence supplied. You will be informed of the outcome as soon as possible thereafter.
Should there be non-conformities, you will be invited to correct the issues, and present new documentation and evidence to the Assessors for re-assessment. This may incur additional costs.
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 |