Employer-Owned Life Insurance: Notice, Consent, and Tax Rules

Why employer-owned coverage has a separate tax rule

A company can buy life insurance on an employee for a legitimate business reason. If a key salesperson dies, for example, the company might face a revenue gap while it replaces that person. An owner may also insure an employee who is central to a succession or loan arrangement. In these cases the business, rather than the employee’s family, may own the policy and receive at least part of the death benefit. That ownership arrangement is often called employer-owned life insurance, or EOLI.

The tax question is not only whether the policy is valid or whether the company has a business reason for buying it. Federal law also asks whether the employer can exclude the death proceeds from income. Section 101(j) was enacted to limit tax-free treatment for certain employer-owned policies. It generally caps the employer’s exclusion at premiums and other amounts paid unless a statutory exception applies. The notice-and-consent process is one of the gates to those exceptions.

The practical lesson is simple: a business should not wait until an employee dies or until tax returns are prepared to look for consent forms. The notice and written consent must generally be completed before the policy is issued. A missing form can change the tax result on a large benefit, and a later signature does not automatically repair the original timing failure.

What counts as employer-owned life insurance

For the Form 8925 instructions, an employer-owned life insurance contract is generally a contract owned by a policyholder and covering the life of that policyholder’s employee on the date the contract is issued. The policyholder is generally the person that owns the coverage, conducts a trade or business employing the insured, and is a direct or indirect beneficiary. Related entities under common control or specified relationships can also be treated as policyholders, so the name printed on the policy is not always the end of the analysis.

The insured must be a U.S. citizen or resident for this particular federal definition, and “employee” is broader than a rank-and-file payroll label. The IRS instructions say it includes an officer, director, or highly compensated employee under the relevant tax rules. A policy covering joint lives can require careful treatment of both insureds. These definitions are technical; a company should not decide a contract is outside the rule merely because it calls the coverage key-person insurance, split-dollar insurance, or executive benefits.

A typical business-owned policy may insure a founder, a person with specialized client relationships, a senior manager, or a worker whose absence would interrupt a critical operation. Those examples explain why an employer might want coverage; they do not determine the tax result. The entity, related persons, ownership, beneficiary designation, issue date, insured’s status, and destination of proceeds all matter. A trust or affiliate can change who is treated as the policyholder, which is why ownership diagrams and policy documents matter more than a casual description.

Do not confuse EOLI with ordinary employee group-term coverage where a worker receives a certificate and can name a personal beneficiary. Group coverage can have its own employee income-inclusion rules under Section 79. EOLI instead focuses on a business-owned contract and the employer’s treatment of death proceeds under Section 101(j). A company can have both arrangements, but one set of rules does not replace the other.

The general Section 101(j) limit

The baseline rule is that the employer’s exclusion from gross income for proceeds received because of an insured employee’s death cannot exceed the premiums and other amounts paid by the applicable policyholder for the contract. In plain language, if the employer receives a death benefit that is larger than its qualifying investment in the policy and no exception applies, the amount above that investment may be taxable to the employer. The rule concerns the policyholder’s exclusion; it does not say the beneficiary employee paid tax on every premium or that the entire death benefit is automatically taxable.

Suppose a company receives a policy benefit of $600,000 and it has paid $180,000 in premiums and other amounts for that contract. If no exception applies, the general rule limits the exclusion to the policyholder’s paid-in amount. The $420,000 difference is the amount potentially exposed to income tax under this simplified illustration. Actual tax basis and reporting must be determined from the contract history and applicable law; the numbers here are only to make the rule visible.

That is different from the usual rule for an individual beneficiary. Life insurance death proceeds are generally excluded from a recipient’s gross income, although interest paid with proceeds can be taxable and transfers for valuable consideration can limit the exclusion. Section 101(j) adds a special limit for the employer-policyholder. If proceeds are paid to the employee’s family or another designated beneficiary, the separate statutory exception may protect that amount, but the consent requirement still matters.

Which exceptions can remove the cap

Section 101(j) provides exceptions to the general cap when notice and consent requirements have been met. One route depends on the insured’s status. An exception can apply when the insured was an employee of the policyholder at some time during the twelve-month period before death. Another can apply if, when the contract was issued, the insured was a director, a highly compensated employee under Section 414(q), or a highly compensated individual under Section 105(h)(5), subject to the statutory definitions.

A second route looks at who receives or benefits from the proceeds. To the extent proceeds are paid to a member of the insured’s family, an individual designated by the insured as beneficiary other than the policyholder, a trust for such a person, or the insured’s estate, the exception may apply. A qualifying amount used to purchase an equity, capital, or profits interest in the policyholder from those people can also fit the statute. The exact recipient and destination should be traced rather than inferred from the company’s intention.

This article does not try to reproduce every related-party attribution rule or the separate definitions of highly compensated status. The phrase “highly compensated” is a tax-law term, not simply a manager’s opinion that someone earns a lot. A candidate should recognize the categories named by the statute and know that precise classification calls for the referenced definitions. A business designing coverage should have tax counsel verify the applicable employee category for the year and policy at issue.

For a test question, separate the gate from the exception. First ask whether the policy is within EOLI rules and whether the required notice and consent occurred before issue. Then ask whether the insured’s employment or executive status meets one exception, or whether proceeds go to an eligible recipient or qualifying purchase. A correct exception analysis does not skip the paperwork step.

The three parts of notice and consent

The employee must be given written notice before the policy is issued. The IRS instructions and Notice 2009-48 describe three core pieces. First, the employer tells the employee that it intends to insure the employee’s life and gives the maximum face amount for which the employee could be insured at issue. The notice must disclose the face amount in dollars or as a multiple of salary that the employer reasonably expects to purchase during the employee’s tenure. This is not a vague statement that the company may offer benefits someday.

Second, the employee must be told in writing that the employer may be a beneficiary of proceeds payable at the employee’s death. The employee should understand who may receive the benefit. A form that only says “the company is applying for insurance” can fail to communicate this essential fact if it does not identify the employer-beneficiary arrangement.

Third, the employee must provide written consent to being insured under the contract and to coverage continuing after employment ends. The consent is not the same as a group enrollment election or acknowledgment that the employee received a handbook. The written record should clearly match the policy and the person insured. IRS guidance allows electronic notice and consent if the system captures all required elements and maintains reliable records; merely sending an email without a signed or otherwise legally sufficient consent is not enough.

• Tell the employee in writing that the employer intends to insure the employee’s life.
• State the maximum face amount the employee could be insured for at issue and the amount or salary multiple reasonably expected during the employee’s tenure.
• Explain in writing that the employer may receive proceeds when the employee dies.
• Obtain written consent to the coverage and to the possibility that it continues after employment ends.
• Complete and retain the record before the applicable issue date, and connect it to the policy file.

Timing is strict. Publication 5035 explains that, for this requirement, the contract’s issue date is generally the latest of the application date, the effective coverage date, and the formal policy issuance date. That definition can surprise a business that assumes it only needs a signature before the insurer mails the policy. The safest administrative sequence is to provide the notice, collect and store consent, verify the amount and beneficiary explanation, and then submit or activate coverage under the company’s documented process.

If the expected aggregate face amount later exceeds what the employee was told and consented to, additional notice and consent may be required. Increasing one contract or stacking multiple contracts can push total coverage past the disclosed amount. The company should track the amount across policies and related arrangements, rather than treating each new application as unrelated. The IRS’s Notice 2009-48 discusses how maximum amounts and later coverage increases are handled.

What happens when the employee leaves

The consent language specifically includes the possibility that insurance continues after employment ends. The policy may remain owned by the employer, the employer may keep paying premiums, and the former employee may no longer work there when death occurs. This continuation feature is one reason the notice cannot be reduced to a simple acknowledgement of current employee benefits.

Leaving employment does not automatically remove the contract from Section 101(j). The employee’s status at death may matter for one exception, but the insured-status test includes whether the individual was an employee at any time during the twelve-month period before death. The original issue-date status and the proceeds recipient also have separate roles in the analysis. A former employee’s policy should therefore stay in the company’s EOLI records until the contract terminates or otherwise leaves the relevant reporting scope.

If the employee transfers the policy or the employer changes ownership, do not assume that old consent or old tax treatment follows automatically. A transfer, exchange, related-party ownership, or replacement contract can invoke additional rules. Notice 2009-48 addresses particular exchanges and transfers, but each transaction has facts that matter. Before moving ownership or substituting contracts, have counsel determine whether the transaction is treated as a new issuance and whether documentation is adequate.

Form 8925: annual reporting, not employee permission

A policyholder uses Form 8925 to report the number of employees covered by EOLI contracts issued after August 17, 2006, the total amount of EOLI in force on those employees at year-end, and whether valid consent exists for each employee. If not all covered employees have consent, the form asks for the number without valid consent. The form is attached to the policyholder’s tax return. IRS guidance points filers to the current Form 8925 page for developments; the form currently linked there is the September 2017 revision, while the IRS’s December 2025 Publication 5035 reproduces its general instructions and reporting fields.

That distinction between form and consent matters. Form 8925 is filed by the policyholder as an information return. It does not serve as the employee’s consent and it is not permission to insure someone. Nor does checking a box that consent was received prove the statutory exception if the underlying records are missing, late, or fail to give the required information. The signed notice, the policy, coverage amounts, and the return should tell a consistent story. As checked for this article in September 2026, the IRS Form 8925 page reports no recent developments and links to the September 2017 form revision; the IRS’s December 2025 Publication 5035 reproduces the current general reporting instructions and Form 8925 fields.

Build a repeatable file process. Maintain an inventory by insured, policy number, issue date, current face amount, policyholder, beneficiary, employee status, notice date, consent date, and expected use of proceeds. Reconcile that inventory with the Form 8925 figures at year end. Keep the records with the business return documentation and update them after coverage increases, entity reorganizations, or employment changes. The form’s line for employees with missing consent is not a substitute for preventing a missed consent.

Employer tax deduction and employee income are separate questions

People often use “tax treatment” to mean several different things at once. Whether the employer deducts premiums is not the same issue as whether the employer excludes death proceeds from income. It is also separate from whether an employee includes employer-paid coverage in wages. The premium-deduction article explains the general business-beneficiary restriction. Here, the central question is the Section 101(j) income limit and the pre-issue consent condition.

A business that owns a policy and is entitled to proceeds may generally be unable to deduct premiums when it is a direct or indirect beneficiary. IRS Publication 334 describes a broader disallowance for many life, endowment, and annuity contracts when the business is a beneficiary; it separately says some employee life insurance costs can be deductible if the business is not a beneficiary and general business expense requirements are met. Loan-protection coverage has its own nondeductible rule. These premium rules do not answer whether Section 101(j)’s proceeds exception is satisfied.

For group-term coverage, the employee may have taxable imputed income for employer-provided coverage above the statutory exclusion amount, subject to Section 79’s rules and exceptions. That rule is about compensation during life, not whether the employer can exclude the proceeds of a separate employer-owned contract at death. The Texas group-life coverage guide addresses the state exam’s group life provisions; keep its policy-coverage questions separate from this federal income-tax analysis.

A candidate should be able to recognize these separate questions even if the exam does not ask for a return calculation. Is the employer trying to deduct what it paid? Is the employee reporting a benefit as wages? Is the employer receiving death proceeds? Which party owns the policy and receives payment? One fact pattern may raise all three issues. Answer only the one the question asks, then apply the matching rule.

A worked example: the missing consent

Imagine a company buys a permanent policy on a senior employee. The company owns the contract and is named as beneficiary. The employee’s manager discussed the coverage informally, but the personnel file contains no written notice or consent. Years later, the employee dies while the policy is in force. The company receives the benefit. The tempting answer is that the proceeds are tax-free because life insurance death benefits usually are excluded. But the company must first test Section 101(j), including the general cap and whether it has valid pre-issue notice and consent.

The fact that the insured was a senior employee does not repair the missing consent. Nor does the company’s business need for the coverage. The potentially relevant exception still carries the notice-and-consent requirement. The company may have to limit its exclusion to premiums and other amounts paid, potentially leaving excess proceeds taxable. A tax professional must compute the actual treatment from contract records and any applicable exception, but for exam reasoning the missing written consent is the decisive warning.

Now change one fact: before issue, the employer delivered a written notice describing its intent to insure the employee, the maximum expected face amount, its potential beneficiary status, and the possibility the coverage could continue after employment. The employee signed written consent. If the insured also fits a status exception or the proceeds are paid or used in a qualifying way, the normal cap may not apply. Notice and consent are necessary to access these exceptions, but they are not themselves proof that one applies.

Exam traps and a reliable order of analysis

The Texas Life Agent outline places federal tax treatment of insurance premiums, proceeds, and dividends in the life portion covering retirement and other life concepts. The exam tests insurance knowledge, not preparation of a corporate income-tax return. Expect the tested concept to be a clean distinction: employer owns and benefits from employee coverage; Section 101(j) may cap the exclusion; written notice and consent must be obtained before issue for an exception to apply; Form 8925 reports the coverage and consent status.

1. Identify the policyholder, insured, and beneficiary. Do not infer ownership from who paid the premium alone.
2. Ask whether the contract covers an employee of the policyholder when issued and falls within the EOLI definition.
3. Check whether written notice and consent occurred before the applicable issue date, including the required amount, beneficiary disclosure, continuation statement, and consent.
4. Test the statutory exception: insured status or qualifying payment/use of proceeds.
5. If no exception fits, remember the employer’s exclusion is generally limited to premiums and other amounts it paid; do not say the entire benefit is always taxable.
6. Keep Form 8925 separate from the consent form: one is annual policyholder reporting; the other is a pre-issue requirement.

A common wrong answer is “the company gets a tax-free death benefit because life insurance proceeds are tax-free.” That overlooks the special rule for employer-owned policies. Another wrong answer is “the company’s premiums are deductible because this is key-person insurance.” A business-beneficiary rule can prevent that deduction. A third wrong answer treats Form 8925 as the consent itself. The right response depends on the role and timing facts in the stem.

If you need to review the wider tax categories that sit around this rule, start with life insurance premium deductions and then compare qualified plans, MECs, and life insurance tax practice questions. For business coverage context, key-person and buy-sell practice questions work through the underlying insurance need. The links are study aids; current tax forms, policy documents, and professional advice govern actual filings.

What an agent should explain without giving tax advice

An agent discussing business-owned coverage should explain the policy structure accurately: who owns it, who is insured, who receives the death benefit, what the policy does, and whether coverage may continue after employment. If the employer intends to rely on tax treatment tied to Section 101(j), the business must coordinate its written notice, consent, records, and filing with qualified tax and legal advisers. The agent should not promise that proceeds are tax-free or that premiums are deductible based only on a sales illustration.

The employee should have a clear opportunity to understand the arrangement. A notice is not meaningful if it hides the employer’s beneficiary role in vague language or does not describe the contemplated amount. Employers should not pressure a worker to sign a form that does not match the proposed coverage. A well-designed administrative process gives the employee the necessary information, captures consent in a durable format, and reconciles any later change to the original disclosure.

This is an area where a small procedural detail can matter years later. That does not mean every employer-owned policy is suspect or that every failed form creates the same tax bill. It means the policy should be designed around a documented business purpose and administered with the statutory timeline in mind. For licensing questions, identify the required disclosure. For a real company’s tax return, use its own facts and professional review.

How this connects to the Texas Life Agent exam

Pearson VUE’s September 2026 outline includes tax treatment of life insurance premiums, proceeds, and dividends in the general life content. It does not turn a test taker into a tax preparer. Learn what makes employer-owned insurance different from personal life coverage: employer ownership and beneficiary status can create a special limit on the employer’s exclusion; advance written notice and consent are tied to exceptions; and the IRS requires annual reporting for covered contracts issued after the statutory effective date.

Memorize the sequence, not an oversimplified slogan. “Business owns it” is only a starting clue. Determine whether the business or related entity is the beneficiary and whether the insured was an employee at issue. Then ask when notice and consent happened, and whether the facts support a Section 101(j) exception. Finally, distinguish taxability of proceeds from premium deductibility and group-term wage inclusion. These separations turn a dense tax topic into a manageable insurance question.

The strongest exam answer will usually respect the timing word “before.” A conversation after issuance is not the same as written notice and consent before issuance. Likewise, an annual return filing is not a substitute for the original employee consent. Read every role carefully. When an employer is named as both owner and beneficiary, the question is pointing you toward employer-owned life insurance rules rather than the ordinary family-beneficiary rule.