The Trap the Regulators Set by Accident.

That last feature, the exclusion under Internal Revenue Code § 101(a)(1), is so familiar that planners tend to treat it as a constant. It is not. It is a rule with exceptions, and one of those exceptions — the transfer-for-value rule of § 101(a)(2) — has a way of catching sophisticated families precisely because they were doing something ordinary.

On July 9, 2026, the Treasury and the IRS finalized a set of regulations, T.D. 10052 (91 Fed. Reg. 42345), that closes an inadvertent trap of their own making — a trap that, read literally, could have converted a routine, tax-free § 1035 policy exchange into the event that made the entire death benefit taxable. The fix is welcome, technical, and quietly important for anyone holding cash-value life insurance inside an irrevocable trust. It also carries a planning lesson that has nothing to do with the fine print: the tax integrity of a life-insurance strategy depends on documentation, ownership, and reporting discipline that must be in place before the policy ever changes hands — not reconstructed afterward.

Under § 101(a)(1), amounts received under a life insurance contract paid by reason of the insured’s death are excluded from the beneficiary’s gross income. This is the engine of insurance-based planning. But § 101(a)(2) provides that where a contract (or an interest in it) has been transferred for valuable consideration, the exclusion is capped: only the consideration paid plus subsequent premiums is excludable, and the balance of the death benefit is taxed as ordinary income. There are two long-standing carve-outs that restore the full exclusion — a transfer in which the transferee takes the transferor’s basis (a carryover-basis transfer), and a transfer to the insured, to a partner of the insured, to a partnership in which the insured is a partner, or to a corporation in which the insured is a shareholder or officer.

The 2017 Tax Cuts and Jobs Act added a third layer. It created the concept of a reportable policy sale (“RPS”) — broadly, the acquisition of an interest in a life insurance contract by someone with no substantial family, business, or financial relationship to the insured, the machinery aimed at the life-settlement and stranger-owned-insurance markets. A death benefit attributable to an interest transferred in a reportable policy sale loses the exclusion even if one of the old carve-outs would otherwise have applied, and Congress backed the regime with a new information-reporting section, § 6050Y, requiring Forms 1099-LS, 1099-SB, and 1099-R to trace these transactions.

The regulations implementing all of this were finalized in 2019 as T.D. 9879 (84 Fed. Reg. 58460). They did their job on life settlements. But in defining when a policy is “transferred,” they swept in a transaction Congress never meant to reach.

Section 1035 is the provision that lets a policyholder swap one life insurance contract for another — old policy for new, often at a different carrier — without recognizing gain. It is the everyday plumbing of insurance planning: replacing an underperforming policy, consolidating coverage, moving to a stronger carrier, restructuring a contract as circumstances change. A trustee holding insurance for a family does this as a matter of ordinary prudence.

The problem the 2019 regulations created was subtle. In treating the issuance of the new contract in a § 1035 exchange as itself a “transfer” of the policy for these purposes, the regulations set up a structural mismatch: the new contract could fail to fit cleanly within the basis-carryover exception, which meant that a plain-vanilla exchange — no life settlement, no stranger, no sale to anyone — could be read to strip the death benefit of its § 101(a)(1) exclusion. As the Treasury itself acknowledged, this was entirely unintended. The regulatory intent had only ever been to stop a taxpayer from laundering a tainted policy — one already carrying a reportable-policy-sale history or a transfer-for-value limitation — by running it through a § 1035 exchange into a “clean” new contract and thereby erasing the taint.

T.D. 10052 resolves the mismatch directly. It removes the language that treated mere issuance of a contract in a § 1035 exchange as a transfer, so that an ordinary exchange no longer triggers the transfer-for-value analysis at all. At the same time, it preserves the anti-abuse purpose through a carryover-of-attributes rule: the tax character of the surrendered policy follows into the new one. A clean policy exchanged for a new policy stays fully excludable; a tainted policy — one that already carried a reportable-policy-sale status or a transfer-for-value limitation — carries that same limitation forward into the replacement contract. You cannot wash the history off a policy by exchanging it.

The 2023 proposed version of these rules would have done something administratively heavy: it would have expanded the definition of “issuer” to capture both the old and the new carrier in a § 1035 exchange and required each to file information returns (Form 1099-SB) with the IRS and furnish statements to the policyholder every time a policy was exchanged. Insurers objected that this was duplicative and would bury both carriers and the Service in paper for transactions that were, in the ordinary case, entirely tax-free.

The final regulations agreed. T.D. 10052 eliminates the IRS-filing requirement for ordinary § 1035 exchanges and replaces it with a targeted, carrier-to-carrier notice. Under the new Reg. § 1.6050Y-3(h), when a policy that carries a reportable-policy-sale taint is exchanged into a contract issued by a different carrier, the old issuer must hand the new issuer the information needed to keep the reporting chain intact — the policyholder’s investment in the contract and whether reportable death benefits would have to be reported — using “any reasonable method.” The tracking survives; the paperwork does not metastasize. A distinct Form 1099-R distribution code is contemplated to flag the tax-free exchange of a tainted contract when the benefit is eventually paid.

There is also a narrow de minimis exception for corporate-owned life insurance (“COLI”) that changes hands in a § 368(a) reorganization between C corporations: where the insurance is no more than 5 percent of the target’s gross assets before the deal and no more than 5 percent of the acquirer’s assets after, and both are active operating businesses rather than insurance-investment vehicles, the acquisition is not treated as a reportable policy sale. The IRS declined to widen it to taxable acquisitions or non-C-corporation targets, but invited further comment.

For once, the effective-date rules cut in the taxpayer’s favor. The substantive provisions apply prospectively to exchanges and acquisitions occurring on or after July 9, 2026 — but taxpayers may elect to apply them retroactively to all exchanges and acquisitions occurring after December 31, 2017, the date the TCJA regime took effect. That election matters. A family or trustee who completed an ordinary § 1035 exchange during the years the 2019 regulations were on the books — and who might, on a literal reading, have worried about the exclusion — can elect back into the corrected rules and put the question to rest. This is a point to raise affirmatively with the family’s tax counsel where a policy inside a trust was exchanged at any point since 2018.

The pattern in that table will look familiar to readers of this series. The transactions that survive scrutiny are the ones whose character was fixed, on the record, before anyone had a reason to worry about them. The ones that fail are the ones where the paperwork is assembled after the fact to support a conclusion the taxpayer needs. That is as true of a life-insurance exclusion as it is of a creditor-protection trust: the integrity of a structure is established at inception, not defended at audit.

Three practical lessons follow for families holding insurance inside their planning structures.

First, know the provenance of every policy in the trust. An irrevocable life insurance trust (“ILIT”) that acquired a policy, took an assignment of an existing contract, or received insurance in a business succession may be holding a contract with a transfer-for-value or reportable-policy-sale history the current trustee has never examined. Because T.D. 10052 makes that status follow the policy through a § 1035 exchange, a trustee cannot cure a tainted contract simply by exchanging it — and cannot afford to assume a policy is clean without checking. The moment to establish and paper the policy’s status is when it enters the trust, not when a death benefit is claimed.

Second, treat a § 1035 exchange as a decision with tax character, not merely an insurance upgrade. The exchange itself is now safely tax-free for ordinary contracts, which is the good news. But the trustee should confirm the contract’s clean status before exchanging, preserve the carrier’s basis and RPS information, and — where a tainted contract is moving to a new carrier — make sure the § 1.6050Y-3(h) notice actually passes between the two insurers rather than assuming it will.

Third, revisit exchanges done since 2018. If a trust exchanged a policy while the 2019 regulations were in force, the retroactive election back to post-2017 transactions is a tool worth using deliberately, in coordination with the family’s tax advisor, to lock in the corrected treatment.

None of this is exotic. It is the same discipline that runs through everything we counsel: legitimate structures are documented at inception, administered on their own terms, and transparent when the record is properly examined. A life-insurance strategy that meets that standard has nothing to fear from the transfer-for-value rule. One that depends on a favorable reading of a thin or reconstructed record is exposed — and T.D. 10052, by making a policy’s history travel with it, has made that exposure harder to outrun.