The partners were great at serving clients, they were just stretched. If you have ever felt that same pit in your stomach during busy season, this guide is for you.
You are about to get a field tested, step by step breakdown of Form 8925, what counts as employer owned life insurance, how to count heads and coverage, and how to lock down notice and consent so your filings are audit ready. I will point to the exact IRS and Code sections as we go, and I will flag the small details that create big problems.
Key Takeaways
- You must file Form 8925 for every tax year you have employer owned life insurance, EOLI, issued after August 17, 2006, in force, and you attach it to your income tax return for that year.
- Report four things each year, total employees at year end, number insured under EOLI, total insurance in force, and whether valid written notice and consent exist for each insured, including a count of any missing consents.
- To keep death benefits tax free, you must meet the written notice and consent rules before issuance and fit within the exceptions in §101(j), for example recent employment or highly compensated status. Missing or late consent can make death proceeds taxable to the extent they exceed premiums.
- Electronic notice and consent can work if your system meets IRS requirements. Inadvertent pre issuance mistakes have limited relief if corrected by the return due date, not after death.
- Keep a contemporaneous consent log, reconcile HR, payroll, and carrier data, and document headcount methodology. This is the fastest way to pass an exam and avoid rework.
What Form 8925 Covers and Why It Exists
Form 8925 is the annual information return that tells the IRS how many employees you insured under employer owned life insurance contracts issued after August 17, 2006, how much total coverage is in force at year end, and whether you hold valid notice and consent for each insured. The current IRS page confirms the purpose, and it links to the form and Notice 2009 48, the core guidance on EOLI compliance.
Under §6039I, every applicable policyholder that owns one or more EOLI contracts must file a return each year those contracts are owned, reporting year end employees, the number insured, total insurance in force, the policyholder’s identity and business type, and whether valid consent exists, or the count of missing consents. Regulations at §1.6039I 1 spell out the same annual reporting and recordkeeping duties.
Form 8925 ties directly to §101(j). That section limits the normal death benefit exclusion when a business owns life insurance on an employee unless specific notice, consent, and exception rules are met. In other words, fail the rules, and the death benefit in excess of premiums can be taxable to the employer.
Who Must File and When
If you own EOLI contracts issued after August 17, 2006, you file Form 8925 for each tax year those policies remain in force, and you attach it to your income tax return for that year, including extensions. This is not a one time filing, it is annual for as long as coverage continues. The IRS form itself and final regulations both make that timing clear.
- Policyholder types, C corps, S corps, partnerships, LLCs, and other trades or businesses that own the contracts, including certain related persons under §267(b), §707(b), and common control rules in §52.
- Master contracts, if you add covered lives later, those additions are treated as new contracts only for the new lives, so you keep reporting annually and track additions carefully.
- §1035 exchanges, if you exchange a pre 8 18 2006 contract into a new one, the form says you generally do not have to file for that exchange, but any material increase in death benefit or other material change creates a new contract, which brings you back into filing.
Quick memory hook, if a policy is in force and was first issued after 8 17 2006, assume you must attach Form 8925 with your return for that tax year unless a clearly documented exception applies.
What Counts as Employer‑Owned Life Insurance, EOLI
At its core, EOLI is any life insurance contract owned by a person engaged in a trade or business, where that person, or a related person, is directly or indirectly a beneficiary, and the insured was an employee on the issue date. The statute defines employer owned life insurance contract, applicable policyholder, and related persons, and it includes officers, directors, and highly compensated employees within the employee definition.
This scope reaches many common designs, for example individual policies owned by an employer on executives, master contracts with certificates for multiple employees, and split dollar arrangements where the employer is an owner or beneficiary. The split dollar regulations define the arrangement and explain owner and non owner treatment, which is why policy ownership and beneficiary designations must be crystal clear in your file.
One more practical point, issue date matters a lot. The IRS recognizes that the issue date for consent timing is the later of the application date, the effective date, or formal issuance, which gives you a narrow window to get signatures right. Document how you determined the issue date for each insured.
Form 8925 Reporting Checklist, Do Not File Without This
Use this short pre filing routine to keep your return clean and your review cycle fast.
| Control | Action |
| Identification | Confirm legal name, TIN, address, and type of business match the income tax return. |
| Coverage metrics | Reconcile year end total employees, insured employees under post 8 17 2006 EOLI, and total insurance in force to carrier schedules. |
| Consent evidence | Validate written notice and consent for each insured was obtained before the issue date, and flag any exceptions for line 4b. |
| Policy vintage | Tag pre 8 17 2006 policies and any §1035 exchanges, then test for material changes that create a new contract. |
| Filing deadline | Calendar the return due date, including extensions, for the year the policies are in force, and attach Form 8925. |
Those five checks mirror what §6039I and the form instructions require, they also mirror how examiners read your file.
How to Count Employees and Insureds Correctly
The cleanest approach starts with payroll. Anchor your year end headcount to common law employees on payroll at year end, include full time, part time, and seasonal employees who meet the employer employee relationship, and exclude independent contractors. Then reconcile that headcount to benefits rosters and carrier lists so your totals match what the insurer shows as in force. Keep a short memo explaining your method and any variances.
Counting insureds under EOLI
- Include only employees insured under employer owned policies that were in force at year end and first issued after August 17, 2006.
- Tag grandfathered policies, issued on or before that date, and keep them separate unless a material change created a new contract.
- For master contracts, treat each covered life like a separate contract for notice and consent and for your consent log.
- Sum the total face amount in force for the insured employees on line 2, tie to carrier statements, and store the tie out with the consent log.
Avoiding double counts
If you run multi entity groups, make sure only the policy owner that actually owns the contract files Form 8925. Notice 2009 48 confirms that related persons are included in the definition of applicable policyholder, but the filer is the owner of the contract. Clarifying this up front stops duplicate filings across a controlled group.
The Notice and Consent Rules You Must Get Right, §101(j)
To preserve the death benefit exclusion, you must meet the written notice and consent requirements before the contract is issued. The notice must tell the employee you intend to insure their life, disclose the maximum face amount, in dollars or as a multiple of salary, and state that you will be a beneficiary. The employee must give written consent to be insured and to allow coverage to continue after employment ends.
Two details trip people up:
- The face amount in the notice must be a number or a multiple of salary you reasonably expect to purchase during the employee’s tenure. If you later exceed that amount, get new notice and consent.
- The consent must be dated before the issue date. The IRS treats the issue date for this purpose as the later of the application date, effective date, or formal issuance, so build your process around that definition.
Electronic systems are fine if they meet IRS standards that ensure the right person saw the exact notice, consented, and you can print a hardcopy on request. If you make an inadvertent pre issuance error, Notice 2009 48 provides narrow relief if you fix it by the return due date. There is no fix after the insured dies.
How to Document Consents That Stand Up in Audit
Create a centralized consent log and keep the original signed notices and consents, electronic or wet, in a retrievable folder structure. Tie each insured employee on your policy list to a consent record that shows the notice date, consent date, maximum face amount disclosed, policy number, and the contract issue date. This is your single source of truth for Form 8925 line 4 and for §101(j).
Any gap between consent date and the IRS definition of issue date is an audit magnet. Close that gap before you file.
Valid Consent Elements, A Quick Builder
Here is a simple template you can adapt with your counsel. Confirm state law and carrier requirements, then keep originals.
- The employer’s written notice states intent to insure, includes the maximum face amount, in dollars or multiple of salary, and states the employer will be a beneficiary.
- The employee’s written consent acknowledges being insured, agrees coverage may continue after employment ends, and is signed and dated before the issue date.
- If you later increase coverage beyond the disclosed maximum, obtain new notice and consent.
Consent Log, an Audit Ready Model
| Field | Example entry |
| Employee name | Jordan Lee |
| TIN, last 4 | 1234 |
| Notice date | 02 12 2026 |
| Consent date | 02 13 2026 |
| Max face amount disclosed | 2 times base salary |
| Policy number | ABC 778899 |
| Issue date, per IRS definition | 02 20 2026 |
| Valid Y N | Y |
| Evidence file path | /EOLI Consents 2026 JordanLee.pdf |
| Reviewer initials date | KL 02 21 2026 |
If you find a missing or late consent, report the count on line 4b, keep a note of your good faith collection efforts, and assess exposure under §101(j). You cannot cure consent after death, so train HR and benefits to capture consent before the carrier issues coverage.
Safe Harbors That Preserve Tax Free Death Benefits
Even with perfect consent, §101(j) still requires you to fit an exception. The two most common are, the insured was an employee at any time during the 12 months before death, or the insured was a director, a 5 percent owner, one of the five highest paid officers, or within the top 35 percent of paid employees at issue, a cross reference to the highly compensated rules in §414(q). Document whichever path you rely on at issuance and keep it with the consent.
A note on “highly compensated” pay thresholds
The compensation threshold for §414(q) is indexed, and plans use a look back year. Because that dollar amount changes over time, confirm the threshold for the policy year before you stamp a file as safe harbor. For definitions, see §414(q) and the temporary regulations that explain what counts as compensation.
Heirs and buy sell paths
If the employer is not the beneficiary, for example proceeds go to the insured’s family or a trust for family, or proceeds fund a buy sell purchase from a qualifying beneficiary, §101(j) provides additional exceptions. If you expect to rely on these, align your beneficiary designations, keep a signed buy sell agreement, and preserve records that show proceeds were actually used for the buyout. Form 8925 still applies while the employer owns the contract.
Split‑Dollar Arrangements, Why Ownership and Beneficiary Records Matter
Split dollar plans can be employer owned, employee owned, or trust owned. The split dollar regulations define these arrangements and how ownership and economic benefit rules apply. When an employer is the owner or a direct or indirect beneficiary, the contract can fall within EOLI, which brings you back to §101(j) notice, consent, and Form 8925 reporting. This is why you should store the split dollar agreement, the policy declaration page, and any collateral or endorsement filings with your consent packet.
Quick test, if your business can receive any part of the death proceeds, directly or indirectly, treat the policy as EOLI for documentation and reporting until counsel says otherwise.
Filing Mechanics, Clean Attachments Every Year
Attach Form 8925 to your income tax return each year the EOLI contracts are in force, and file by the return due date, including extensions. Keep copies of the form, the consent log, and the tie outs to payroll and carrier statements in your permanent file. The form, the instructions on the form, and the regulations all point to this simple rhythm, in force, then attach.
Penalties, Audit Risks, and Late Filing Fixes
There is no separate penalty section for Form 8925, but the big risk is that you can lose the death benefit exclusion and turn proceeds into taxable income under §101(j) to the extent they exceed premiums and other amounts you paid. That means additional tax, interest, and potentially accuracy related penalties if proceeds were previously treated as excluded.
If you discover a missed filing, attach Form 8925 to the original or amended return as soon as possible and document your reasonable cause. For pre issuance consent errors, Notice 2009 48 provides narrow relief for inadvertent failures if corrected by the return due date, not after death. Keep your correction memo with the consent file.
Common Mistakes You Can Avoid
- Treating this as a one time filing instead of an annual attachment for each year policies are in force.
- Missing the pre issuance timing of notice and consent or failing to disclose a real maximum face amount in dollars or a multiple of salary.
- Counting everyone on the carrier list without reconciling to payroll and your policy vintage, which can double count pre 2006 policies or exclude new covered lives added under a master contract.
- Filing in multiple entities within a controlled group for the same contract, rather than filing only by the owner of the contract.
Roles, Your Advisor and Your CPA
Your advisor should inventory all in force employer owned policies issued after August 17, 2006, deliver notice and consent templates to HR, and send clean copies to your CPA each year with a consent log. Your CPA should attach Form 8925 to the return, test headcounts and amounts in force, and confirm safe harbor documentation is on file for each insured. If anything breaks, escalate fast. You cannot fix consent after an insured dies, and large proceeds can swing your tax exposure quickly.
Where Accountably Fits, Light Support Without Losing Control
When firms are buried in production work, small compliance steps like EOLI notice, consent, and year end reconciliations are the first to slip. If you use structured offshore support, treat it as an operations system, not just extra hands. That means SOP driven execution, document control, and a central consent log that maps to payroll and carrier data. This is exactly how our team at Accountably plugs in, we work inside your systems, keep your templates, and maintain year over year continuity so Form 8925 stays boring and on time. Mentioned here only because discipline, not heroics, keeps §101(j) clean.
Frequently Asked Questions
What is the purpose of Form 8925?
Form 8925 reports employer owned life insurance for contracts issued after August 17, 2006, including how many employees are insured, total coverage in force, and whether valid consent exists. It is the reporting mechanism for §6039I and ties to the §101(j) rules on tax treatment of death benefits.
Do I file every year or only in the first year?
File every year the contracts are in force, and attach the form to your income tax return, including extensions. This repeats annually for as long as coverage continues.
Can I use electronic signatures for consent?
Yes, if your electronic system ensures the employee received the same notice you sent, authenticates the employee, records consent, and can produce a hardcopy for the IRS. Treat this as you would HR onboarding systems with audit trails.
What happens if I miss consent before issuance?
You risk losing the death benefit exclusion for that insured. Notice 2009 48 offers limited relief for inadvertent pre issuance failures if corrected by the return due date, but there is no fix after death.
How do the safe harbors work in practice?
Document your path at issue. Either the insured satisfies the recent employment test, within 12 months before death, or qualifies under the highly compensated or key person categories cross referenced to §414(q). Keep payroll rankings, officer lists, board minutes, or ownership ledgers in the file.
Conclusion
If you take nothing else, remember this rhythm, identify the owner, confirm the issue date, get written notice and consent before issuance with a real maximum face amount, keep a consent log, reconcile to payroll and the carrier, and attach Form 8925 every year policies remain in force. Build a 30 minute month end routine so year end is just validation, not a scramble. If you missed a year, attach as soon as possible and document reasonable cause. For consent timing issues, move quickly while Notice 2009 48 relief may still be available.