The compliance statement (form EIS1 under the Enterprise Investment Scheme, SEIS1 under the Seed Enterprise Investment Scheme) is what your company files with HMRC after it's issued the shares, and it decides whether your investors get their relief. Until HMRC authorises it, the company can't issue the SEIS3 or EIS3 certificates investors need to claim. So when the round closes and the money's in the bank, there's still one job left, and it's the company's, not theirs.
You can't always file it on day one, though. There's a gate to reach first (4 months of trading or, for SEIS, 70% of the money spent), and for EIS there's a deadline at the other end. Get either wrong and every investor waits, or loses out.
What a compliance statement is and why the company files it
After the shares are issued, the company files a compliance statement with HMRC confirming that it and the share issue have met the scheme conditions since the issue. You do it online, with a separate statement for each share issue (shares of the same class issued on the same day count as one issue). If HMRC's satisfied, it sends the company an authorisation (form SEIS2 or EIS2) with a unique investment reference, and the company then issues a certificate to each investor. That certificate is what your investors use to claim. Without the company's statement, nobody can claim.
Want this checked against your specific situation?
Leave your details and a one-line summary. One of our specialists will come back to you, with no obligation.
Where this sits in the SEIS and EIS journey
It's an easy step to lose track of, because it comes after the round, when you're busy spending the money. Here's the whole sequence.
| Stage | What happens | Who acts |
|---|---|---|
| Qualify | Company checks it meets the SEIS or EIS qualifying tests | Company |
| Advance assurance | HMRC pre-clears that the proposed share issue is likely to qualify | Company applies, HMRC responds |
| Raise | Shares issued to investors; funds received | Company |
| Qualifying period | Company reaches the filing gate: SEIS, 4 months' trading or 70% of the money spent; EIS, 4 months carrying on the activity | Company |
| Compliance statement | Company files SEIS1 or EIS1 with HMRC | Company |
| HMRC authorises | HMRC reviews and, if satisfied, sends the company an SEIS2 or EIS2 with a unique investment reference | HMRC |
| Relief certificates issued | Company completes SEIS3 or EIS3 certificates and gives one to each investor | Company |
| Investor claims | Investor uses certificate to claim relief on their Self Assessment return | Investor |
If you're earlier in the process, the advance assurance guide and the SEIS vs EIS comparison cover the lead-up.
From company statement to investor certificate: the SEIS1/EIS1 to SEIS3/EIS3 flow
The process moves in three stages after the round closes.
- Company files the compliance statement. The company submits the SEIS1 (for an SEIS issue) or EIS1 (for an EIS issue) on HMRC's online form, which you'll find from the SEIS and EIS apply pages. A director, the company secretary or an authorised agent can submit it, and it lists every investor who's asked for a certificate.
- HMRC reviews and authorises. HMRC checks the compliance statement against the qualifying conditions. If it's satisfied, it sends the company an SEIS2 or EIS2, which carries a unique investment reference for that share issue and authorises a set number of certificates, only for the investors named on the statement. If it has questions, it'll write to the company before it decides.
- Company issues relief certificates. HMRC provides the SEIS3 or EIS3 as a PDF alongside the authorisation. The company fills in the investment details and the unique investment reference and gives a completed certificate to each investor, who then claims on their Self Assessment return or through a change to their tax code. Our guide to EIS3 and SEIS3 certificates has the detail.
The SEIS3 and EIS3 aren't HMRC's to hand out. In law the company issues them (ITA 2007 s257EC for SEIS, s204 for EIS), and it mustn't do so without HMRC's authority. It's up to the company to get them right and get one to every investor.
What HMRC checks at this stage
HMRC checks that the qualifying conditions have been met since the shares were issued and still are. For SEIS, that means the company qualifying tests: when the shares were issued, the company had gross assets of no more than £350,000 (measured immediately before the issue), fewer than 25 full-time-equivalent employees, and a trade that was no more than three years old, if it had started trading at all. The total raised under SEIS can't exceed £250,000, and that includes any other de minimis state aid in the three years up to the investment.
For EIS, it's the EIS company qualifying tests: no more than £10m raised in any 12 months and £24m over the company's lifetime across the venture capital schemes (£20m and £40m for a knowledge-intensive company), gross assets of no more than £30m before the issue and £35m after, fewer than 250 full-time-equivalent employees (500 for a knowledge-intensive company), and normally a first commercial sale no more than 7 years before the first scheme investment (10 years for a knowledge-intensive company).
On both schemes HMRC also looks at where the money went. If it's gone into an activity the schemes exclude, or been used in a way the rules don't allow, HMRC can refuse authorisation or withdraw it.
And having advance assurance before the round doesn't mean HMRC has pre-approved the compliance statement. The assurance was a view on the proposed issue; the statement is judged on what actually happened. HMRC checks whether anything you told it at the assurance stage has turned out to be wrong, and where it only saw drafts (a draft information memorandum, say) it'll want the final documents. So flag every change when you file.
Timing: when can we file?
You can't always file the moment the round closes. There's a gate the company has to reach first, and it differs by scheme.
For SEIS, either the new qualifying trade has to have been carried on for at least four months, or at least 70% of the money raised by the issue has to have been spent on the qualifying business activity it was raised for (ITA 2007 s257ED(3)) before the company can file the SEIS1. Either limb opens the door, and the statement has to say which one you're relying on. A company that spends the round quickly can hit 70% well before four months are up, and one that's already been trading for four months can file as soon as the shares are issued.
For EIS, there's no spend test. The trade (or the R&D the money was raised for) has to have been carried on for at least four months before the company can file the EIS1, and those four months can start before the issue (ITA 2007 s176).
EIS also has a deadline at the other end. The EIS1 has to go in within two years of the end of the tax year the shares were issued in or, if the four-month point falls after that tax year ends, within two years of the four-month point (ITA 2007 s205(4)). After that, HMRC can't accept it, so your investors don't get relief. The SEIS1 has no statutory end date (s257ED sets only the gate), but don't sit on it: your investors can't claim until they've got their certificates, and their own window to claim closes five years after the 31 January following the tax year they invested in (gov.uk).
So put both dates in the diary the day the shares are issued. File before the gate and HMRC can't accept the statement; sit on it after the gate and every investor's claim waits.
Common failures at the compliance statement stage
Here's what gets statements rejected or held up.
- Filing too early. The company submits the compliance statement before the required trading or fund-deployment period has elapsed. HMRC rejects it, and the company must refile, delaying relief for every investor.
- Missing the EIS1 deadline. Two years after the end of the tax year of issue (or after the four-month point, if that's later) is a hard stop. Past it, HMRC can't accept the statement and the relief's gone.
- Money not going where the scheme says it must. Money still in the bank is fine (an EIS company doesn't have to have spent it all before it files), but money spent on excluded activities, or on things the rules bar, such as buying shares in a company that isn't a qualifying 90% subsidiary, isn't. If you're relying on the SEIS 70% limb, HMRC will want to see that 70% has actually been spent on the activity it was raised for.
- A qualifying-test breach after the round. The company changes its activities, takes on a disqualifying trade, or breaches another condition between the share issue and the filing date. A breach after investment can invalidate the compliance statement for some or all investors, and HMRC won't authorise certificates once a condition's been broken.
- Assuming advance assurance means automatic authorisation. It doesn't. HMRC judges the statement on what actually happened, so if the facts moved after the assurance, the answer can move too.
- Handing out certificates before HMRC authorises. The company mustn't issue SEIS3 or EIS3 certificates without HMRC's authority, and until it has that authority there's no unique investment reference to put on them. Anything sent out before then isn't a valid certificate, and investors who claim on it may run into problems with their own returns.
A worked ordering example
Here's a seed-stage software company raising £150,000 under SEIS from three angels, £50,000 each, with dates attached.
| When | Step | Company | HMRC | Investor |
|---|---|---|---|---|
| 1 March 2026 | Trading starts | Starts selling its product | ||
| 10 March 2026 (tax year 2025/26) | Round closes; shares issued | Issues SEIS shares for £150,000 and receives the money | Pays for shares | |
| By 30 April 2026 | Gate met: 70% spent | Has spent £105,000 (70% of £150,000) on the trade; the four-month trading point wouldn't arrive until the end of June | Waits for certificate | |
| May 2026 | Company files compliance statement (SEIS1) | Files SEIS1 online, relying on the 70% limb and listing the three investors | Receives statement; reviews it | |
| When HMRC decides (it publishes no turnaround time, as at November 2026) | HMRC authorises | Receives SEIS2 with the unique investment reference, and the SEIS3 form | Issues authorisation to company | |
| Straight after | Company issues relief certificates (SEIS3) | Completes a SEIS3 certificate, with the reference, for each of the three investors | Receives SEIS3 certificate | |
| 2025/26 return (due 31 January 2027); last date to claim 31 January 2032 | Investors claim relief | Claims 50% SEIS income tax relief using SEIS3: £25,000 each on £50,000, if they've that much income tax to set it against, or carried back to 2024/25, in which case that part has to be claimed by 31 January 2031 |
The same sequence applies for EIS, with EIS1 as the compliance statement, EIS2 as HMRC's authorisation and EIS3 as the investor certificate, but two things change. There's no spend test, so this company's gate would be the four-month point at the end of June 2026. And because that falls after the 2025/26 tax year ended on 5 April 2026, its EIS1 deadline would be the end of June 2028; had it been trading since October 2025, the gate would have been met on the issue date and the deadline would be 5 April 2028. Investors can claim 30% EIS income tax relief on up to £1m invested per tax year (rising to £2m where the excess is invested in knowledge-intensive companies).
Get the filing right so your investors get their relief
Your investors put money in partly for the relief, and they can't have it until this filing's done. In practice it comes down to four checks: the gate's been reached, the money's gone on the right things, the statement matches the facts, and every investor gets a correct certificate with the right reference on it.
If you've recently closed an SEIS or EIS round and need to work through the compliance statement, the SEIS and EIS service covers the company-side filing from round close to certificate issue. You can also explore the SEIS company checklist and the SEIS vs EIS guide for context on the qualifying conditions the compliance statement must confirm.