Using share option schemes to create more business value
For many entrepreneurs, your team is the single biggest asset in your business. Many of your staff will have displayed enduring loyalty and belief through the early years of your entrepreneurial journey.
Last updated: 8 January 2020
Equally, you need to fill the gaps in your team as your business grows to the next level. To incentivise early staff and attract talented new joiners, you should consider a share option scheme, which enables you to grant share options to your employees tax efficiently. The most popular scheme is the Enterprise Management Incentive (EMI) share scheme, because it’s the most tax efficient and easy to implement.
The key benefits of an EMI scheme:
It can create a clear financial alignment between you and your team, helping you to build value that both you and your staff will benefit from.
Set at the right price, the scheme can act as either a historic reward or a future performance incentive.
The EMI scheme is HMRC approved, meaning that: a) When you get it right, your employees will only pay 10% tax on the gain in value on their options when they sell them b) A valuation of the options can be agreed by HMRC, which removes uncertainty and later tax problems.
The scheme is easy to implement (with the right advice) and easy to tear up if an employee leaves.
Yes, the benefits are appealing, but there can be severe consequences if mistakes are made! We cannot reiterate enough how important it is to implement the scheme correctly. Failure to adhere to the legislative requirements could leave your employees with an income tax bill of up to 45%, opposed to a capital gains tax bill of 10%.
Common errors made when implementing an EMI scheme:
Trying to understand the rules of the scheme by browsing the internet instead of seeking professional advice. We recommend engaging an experienced lawyer to ensure that you avoid any errors.
Failing to update the company’s articles to reflect the new scheme.
Missing out key facts from the valuation that HMRC has ’agreed’ to. For example, if there was a historic offer for the business, or an investment made into it, the valuation ‘agreed’ cannot be relied upon and causes unnecessary uncertainty.
Messy paperwork, including option agreements not completed properly or not appropriately executed within the required deadlines, which can lead to uncertainty with the valuation of the options. In a worst-case scenario, certain administrative errors can cause the tax-advantaged status of the scheme to be jeopardised. For example, failing to inform HMRC about the options you have given to employees within the required time frame.
Changing the terms of the option agreement without getting appropriate clearance from HMRC.
If any of the above are incorrect, the scheme may not qualify as tax-advantaged and that £100,000 incentive you had planned for your most trusted and diligent employees will not have a tax bill of £10,000 but instead could be a tax bill of up to £45,000! Your company could also be left with an additional £13,800 National Insurance bill.
For many entrepreneurs, the planned total incentive for the team is often far greater than £100,000 and therefore if the scheme is not implemented correctly it can cause unnecessary tax liabilities, awkward conversations with your employees, additional monetary costs to make good to your employees, and it can (and does) derail transactions. However, the pros of implementing an EMI scheme far outweigh any cons for those business owners that seek advice and implement it correctly.
We use cookies for the best experience on our website and also to analyse web traffic. For more information see our Cookie notice. By clicking accept all you agree to our use of cookies. To alter the types of cookies we use click “Cookie settings”.
We use necessary cookies to make our site work. We’d also like to set optional analytics and marketing cookies. We won't set these cookies unless you choose to turn these cookies on. Using this tool will also set a cookie on your device to remember your preferences.
For more information about the cookies we use, see our Cookies page.
Please be aware:
— If you delete all your cookies you will have to update your preferences with us again.
— If you use a different device or browser you will have to tell us your preferences again.
Necessary cookies
Always active
Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.
rc::a
Persistent
This cookie is used to distinguish between humans and bots. This is beneficial for the website, in order to
make valid reports on the use of their website.
rc::c
Expires: Session
This cookie is used to distinguish between humans and bots.
PHPSESSID
Expires: Session
Preserves user session state across page requests.
Analytics cookies
Inactive
Analytics cookies help us to understand how visitors interact with our website by collecting and reporting information anonymously.
_dc_gtm_UA-#
Expires: 1 day
Used by Google Tag Manager to control the loading of a Google Analytics script tag.
_ga
Expires: 2 years
Registers a unique ID that is used to generate statistical data on how the visitor uses the website (Google Analytics).
_gat
Expires: 1 day
Used by Google Analytics to throttle request rate.
_gid
Expires: 1 day
Registers a unique ID that is used to generate statistical data on how the visitor uses the website (Google Analytics).
collect
Expires: Session
Used to send data to Google Analytics about the visitor’s device and behaviour. Tracks the visitor across
devices and marketing channels.
_hjClosedSurveyInvites
Expires: 1 year
Hotjar cookie that is set once a visitor interacts with a Survey invitation modal pop-up. It is used to ensure that the same invite does not reappear if it has already been shown.
_hjDonePolls
Expires: 1 year
Hotjar cookie that is set once a visitor completes a poll using the Feedback Poll widget. It is used to ensure that the same poll does not reappear if it has already been filled in.
_hjMinimizedPolls
Expires: 1 year
Hotjar cookie that is set once a visitor minimised a Feedback Poll widget. It is used to ensure that the widget stays minimised when the visitor navigates through your site.
_hjIncludedInSample
Expires: 1 year
Hotjar cookie that is set to let Hotjar know whether that visitor is included in the sample which is used to generate Funnels.
_hjShownFeedbackMessage
Expires: 1 year
Hotjar cookie that is set when a visitor minimised or completes Incoming Feedback. This is done so that the Incoming Feedback will load as minimised immediately if the visitor navigates to another page where it is set to show.
_hjid
Expires: 1 year
Hotjar cookie that is set when the customer first lands on a page with the Hotjar script. It is used to persist the Hotjar User ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID.
_hjRecordingLastActivity
Expires: Session
This should be found in Session storage (as opposed to cookies). This gets updated when a visitor recording starts and when data is sent through the WebSocket (the visitor performs an action that Hotjar records).
_hjTLDTest
Expires: Session
When the Hotjar script executes we try to determine the most generic cookie path we should use, instead of the page hostname. This is done so that cookies can be shared across subdomains (where applicable). To determine this, we try to store the _hjTLDTest cookie for different URL substring alternatives until it fails. After this check, the cookie is removed.
_hjUserAttributesHash
Expires: Session
User Attributes sent through the Hotjar Identify API are cached for the duration of the session in order to know when an attribute has changed and needs to be updated.
_hjCachedUserAttributes
Expires: Session
This cookie stores User Attributes which are sent through the Hotjar Identify API, whenever the user is not in the sample. These attributes will only be saved if the user interacts with a Hotjar Feedback tool.
_hjLocalStorageTest
Expires: 100ms
This cookie is used to check if the Hotjar Tracking Script can use local storage. If it can, a value of 1 is set in this cookie. The data stored in_hjLocalStorageTest has no expiration time, but it is deleted almost immediately after it is created.
_hjIncludedInSample
Expires: Session
Session cookie which is destroyed when user leaves the Hotjar site.
_gcl_au
Expires: 3 months
Used by Google AdSense for experimenting with advertisement efficiency across websites using their services.
ads/ga-audiences
Expires: Session
Used by Google AdWords to re-engage visitors that are likely to convert to customers based on the
visitor's online behaviour across websites.
Marketing cookies
Inactive
Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.
Category
Expires: 2 months
Used to remember your area of interest on Buzzacott.co.uk / Buzzacott.hk.