The aggressive micro-captive insurance company industry is at severe risk of decimation. The Internal Revenue Service (IRS) initially issued Notice 2016-66 to designate certain micro-captives as transactions of interest, which allowed the IRS to garner information about a micro-captive to measure if it is an abusive tax shelter. However, Notice 2016-66 was overly broad in scope, forcing participants of non-abusive micro-captives to waste time and money on sending information to the IRS that the IRS never deserved to obtain. Therefore, certain taxpayers brought challenges to Notice 2016-66, and it was overturned in CIC Services, LLC v. Internal Revenue Service following a U.S. Supreme Court opinion allowing the challenge to proceed. In the end, the death knell for the Notice was the IRS’s failure to properly follow the Administrative Procedure Act (APA) when issuing the Notice, as well as the arbitrary and capricious manner in which the Notice was issued.
On April 10, 2023, the IRS issued proposed regulations that revive parts of Notice 2016-66 with certain changes, including designating certain micro-captives as listed transactions, while maintaining the transaction of interest designation for certain other micro-captives. The new listed transaction designation places a massive target on certain micro-captives as abusive tax shelters. Given the heightened penalties for unreported or improperly reported listed transactions, the proposed regulations pose a much bigger threat to the aggressive micro-captive world than the now-defunct Notice.
This Article (1) reviews Notice 2016-66 and the CIC Services case that ruled the Notice violated the APA and was issued in an arbitrary and capricious manner; (2) outlines the IRS Proposed Regulations that replace the Notice (Proposed Regulations); (3) describes the differences between the Notice and the Proposed Regulations, including the heightened penalty regime and increased scrutiny that results from the Proposed Regulations; and (4) analyzes the likely effect the Proposed Regulations will have on the aggressive micro-captive industry.
Certain micro-captive insurance companies have been on the Internal Revenue Service’s (IRS’s) radar for the last twenty years. For purposes of this rticle, the term “micro-captive” refers to captive insurance companies who have opted for Internal Revenue Code (IRC) § 831(b) status. The IRS has long been concerned with the fact that covered businesses obtain a tax deduction for premium payments made to its micro-captive, but the micro-captive pays no tax on its receipt of the premiums, while paying out zero to minimal claims. That being said, the IRS has repeatedly said it is not seeking to destroy all micro-captives. Thus, the IRS has sought to ensure that properly structured and run micro-captives are not overburdened, while catching and penalizing aggressive micro-captives that operate as abusive tax shelters.
Two of the most important attempts at combatting micro-captive tax abuse are Notice 2016-66 and the new Proposed Regulations. The goal of Notice 2016-66 was to ensure that taxpayers and material advisors disclose enough about their micro-captive transactions for the IRS to determine whether the micro-captives were actual insurance or abusive tax transactions. However, Notice 2016-66 created confusion and elicited challenges to it due to its vagueness on who must submit disclosures. The result of one of these challenges was CIC Services, LLC v. Internal Revenue Services, in which the U.S. Supreme Court allowed a challenge to Notice 2016-66 under the Administrative Procedure Act (APA) to proceed.
Rather than seeking to revise the Notice, the IRS instead issued Proposed Regulations to substantively keep much of Notice 2016-66 alive while improving its strategy for catching abusive micro-captives. The Proposed Regulations elevate certain micro-captives from a “transaction of interest” (under the Notice) to a “listed transaction” while leaving other micro-captives under the transaction of interest designation. Those micro-captives that met the Proposed Regulations’ standard for listed transactions now potentially face a much more severe penalty structure and an IRS-painted target on their backs. It is likely that the elevated potential penalties and scrutiny will deter aggressive micro-captives from continuing the practices that lead to listed transaction status.
Congress requires (through the IRC) that certain taxpayers provide the IRS with information regarding “reportable transaction[s].” Reportable transactions are those where “information is required to be included with a return or statement because . . . such transaction is of a type which the Secretary determines as having a potential for tax avoidance or evasion.” The Secretary of the Department of Treasury has the authority to issue regulations to carry out the IRC, such as defining what may be a reportable transaction. Further, the IRS may penalize those taxpayers and material advisors who fail to submit information as required for reportable transactions.
The Secretary has designated different types of reportable transactions, two of which are most important for micro-captive transactions under the Proposed Regulations: (1) listed transactions and (2) transactions of interest. Listed transactions are those “that [are] the same as or substantially similar to one of the types of transactions that the Internal Revenue Service has determined to be a tax avoidance transaction and identified by notice, regulation, or other form of published guidance as a listed transaction.” On the other hand, transactions of interest are those that the IRS has deemed substantially similar to those the IRS is concerned about but are not necessarily determined to be tax avoidance transactions.
Notably, the difference between these two designations significantly impacts penalties for taxpayers and material advisors. With listed transactions, the maximum fine for those participating may be up to $200,000 for a corporate taxpayer or $100,000 for an individual taxpayer who is a natural person. For any other reportable transaction, including transactions of interest, the maximum penalty is $50,000 for corporate taxpayers and $10,000 for individual taxpayers. This distinction is enormous, as there can be a $150,000 gap for corporate taxpayers and a $90,000 gap for individual taxpayers, depending on the type of transaction.
On the other hand, for material advisors who fail to file accurate information or file late regarding a listed transaction, the penalty will be the greater of 50% of the income the material advisor derived from aiding with the listed transaction or $200,000. Material advisors who fail to furnish information regarding a transaction of interest or file late could face a $50,000 penalty. Here, material advisors face a significant difference in penalties of $150,000 between the transaction designations. Still, this penalty could quickly rise due to the “greater of” language, whereby a loss of 50% of the income could render a massive penalty for listed transactions.
Finally, there are also disclosure requirements for taxpayers participating in activities regarding reportable transactions. Material advisors would also fall under this disclosure requirement. The IRS has three reasons for mandating these disclosures for reportable transactions: (1) to raise red flags for abusive tax transactions; (2) to communicate to taxpayers the types of transactions that the IRS deems abusive; and (3) to “detect and deter abusive tax shelter activity.”
Whenever the IRS makes use of the reportable transaction regime, there is a risk that the IRS will promulgate too narrow or too broad a notice. The IRS errs on the side of disclosure by adding that transactions should be reported that are “substantially similar” to the described transaction. Of course, this addition has the potential to cause non-abusive transactions to submit information the IRS was never entitled to receive. While the IRS has to review transactions that never should have been submitted, taxpayers and material advisors of non-abusive transactions also must expend unnecessary time and resources on IRS compliance. The IRS seeks to avoid this problem by being very specific in describing which transactions are abusive and require disclosure. As described above, the use of notices for this purpose has led to numerous challenges, and the result for micro-captives was a ruling from the Eastern District of Tennessee that Notice 2016-66 failed to follow the APA and was issued in an arbitrary and capricious manner.
A micro-captive insurance company’s role is to write insurance policies. Often, the insured is a business whose shareholders also own the micro-captive. A micro-captive insurance company is a small captive insurance company that “makes a section 831(b) election to be taxed only on its investment income, not on its underwriting income.” The main tax advantage of this arrangement is the ability to deduct premiums paid to the captive as deductible business expenses, while the captive does not pay tax on the same premiums received in the form of underwriting income (the “difference between an insurance company’s earned premiums and its expenses and claims”). In return for not being taxed on its underwriting income, the micro-captive may not deduct any underwriting income losses. To be considered a micro-captive insurance company, the captive must receive less than the annually adjusted threshold ($2.65 million as of 2023). Micro-captives must still pay tax on the investment income the micro-captive earns from the accumulated premiums.
IRC § 831(b) captives must still act as insurance companies. However, the IRC does not define the term “insurance.” That being said, the IRS and courts apply several critical factors to determine whether a company is truly an insurance company. A proper insurance company must “involve risk-shifting[,] involve risk-distribution[,] involve insurance risk[,] and meet commonly accepted notions of insurance.”
The IRS has taken several actions to battle captives that it does not deem to be insurance companies. For example, the IRS included these transactions on its “Dirty Dozen” list of tax scams. The IRS also launched an “audit and investigation campaign against aggressive § 831(b) [micro-]captive promoters and operators.” The IRS eventually issued Notice 2016-66 to describe which micro-captives were reportable transactions and who was required to disclose these transactions to IRS.
On November 1, 2016, the IRS issued Notice 2016-66. The IRS designated certain micro-captive transactions as transactions of interest. However, the IRS struggled to identify which § 831(b) arrangements were tax avoidance transactions. Participants were thus required to disclose certain information to the IRS using Form 8886 if they were substantially similar to a transaction of interest. All participants were to give sufficient detail to aid the IRS in understanding the tax structure for the reportable transaction. The IRS issued several key distinctions to assist those handling micro-captive transactions.
The IRS did not clearly define which micro-captive transactions were subject to disclosure in Notice 2016-66. Notice 2016-66 described situations that make a micro-captive a reportable transaction. First, an individual directly or indirectly owns an entity or an interest in an insurance coverage entity. Second, there exists a contract between the captive and the insured individual or company that owns the captive. Third, the captive must elect under § 831(b) to be taxed solely on its investment income and not its underwritten income. Fourth, the insured owns at least 20% of the voting power of the outstanding micro-captive stock. Finally, if the captive’s most recent five taxable years is less than 70% of captive’s premiums earned, or the captive used a loan or guarantee to the insured, this would likely be an abusive micro-captive transaction. If the captive has been in existence for less than five taxable years, the 70% rule would apply to the entire period of the micro-captive’s existence.
In addition to the above factors, IRS also looks at the contract coverage. The IRS noted several characteristics that could signify that a micro-captive transaction was acting as a tax avoidance transaction by looking at the contract coverage. The IRS discussed the following type of coverage issues that could arise:
(1) the coverage involves an implausible risk; (2) the coverage does not match a business need or risk of Insured; (3) the description of the scope of the coverage in the Contract is vague, ambiguous, or illusory; or (4) the coverage duplicates coverage provided to Insured by an unrelated, commercial insurance company, and the policy with the commercial insurer often has a far smaller premium.
If a participant has any one of the above characteristics, the IRS likely would consider it to be an abusive reportable transaction.
The general rule is that all micro-captive participants must use Form 8886 to “identify and describe the transaction in sufficient detail” to help alleviate any confusion for the IRS in determining whether this is an abusive transaction. This information would include the tax structure and all the participants involved in the transaction.
Micro-captives must provide “whether [the] Captive is reporting because”: (1) the micro-captive failed the 70% low ratio factor; or (2) the micro-captive provided benefits by financing to an insured through a loan, guarantee, or transfer; or (3) both (1) and (2) are met. The micro-captive must also provide information regarding: (1) under what authority the micro-captive is chartered; (2) descriptions of the type of coverage provided by the micro-captive during the years of participations; (3) an explanation of how the micro-captive determined how much premium is to be paid for each coverage; (4) a report of claims paid; and (5) a description of any assets the micro-captive held. The discloser must provide all this information for each year of the micro-captive’s existence. Procedurally, all this information must be disclosed by attaching Form 8886 to its tax return for each year of the micro-captive’s existence. The taxpayer would also send this disclosure statement to the Office of Tax Shelter Analysis.
Taxpayers and material advisors who failed to comply with these disclosure requirements regarding micro-captives that are transactions of interest would be subject to penalties. For failing to disclose a transaction of interest, corporate taxpayers would face a maximum fine of $50,000, while individual taxpayers would face a maximum fine of $10,000. The IRS could also impose additional penalties on a taxpayer, such as an accuracy-related penalty equal to 20% of the underpayment. For example, if a taxpayer failed to accurately relay information regarding a transaction creating $100,000 in income but submitted a tax form for only $10,000, the understatement would be $90,000. The IRS’s accuracy-related penalty of 20% of $90,000 would thus create an additional fine of $18,000.
Further, material advisors may be subject to additional penalties. Material advisors who failed to file or furnish information regarding a transaction of interest could face a penalty of $50,000. Additionally, the Secretary could request a written list of advisees from a material advisor. If a material advisor failed to submit the advisee list within twenty days of the Secretary’s written request, the material advisor would face an additional $10,000 penalty for each day missed after the initial twenty-day period.
Many micro-captive participants were perplexed by Notice 2016-66. Participants felt the IRS had not given clear guidelines to differentiate abusive from legitimate transactions. Many of the Notice’s guidelines seemed to implicate legitimate transactions. In particular, there was little guidance on the breadth of the term “substantially similar,” potentially causing legitimate micro-captives to make unnecessary reporting due to unclear guidelines to avoid potential penalties. Additionally, the breadth of Notice 2016-66 likely caused certain tangential third parties affiliated with these transactions to submit Form 8886.
Some commentators noted that micro-captives must file a Form 1120-PC (U.S. Property and Casualty Insurance Company Income Tax Return), and that form would capture the same information that the IRS sought from Notice 2016-66. Solely using Form 1120-PC for insurance companies would create less administrative work by using one form instead of two. Unfortunately, Notice 2016-66 created unclear guidelines that led taxpayers affiliated with legitimate transactions to make unnecessary reports. Also, potentially over-burdensome reporting requirements were costing taxpayers time and money. With these issues of unclear, unnecessary, and unduly burdensome reporting requirements, certain taxpayers decided to get the courts involved over Notice 2016-66.
The determinative case surrounding Notice 2016-66 began on March 27, 2017, just four months after the IRS issued Notice 2016-66 on November 1, 2016. CIC Services, a manager of micro-captive insurance companies, initiated this action against the IRS. CIC Services noted that adhering to the Notice 2016-66 disclosure requirements caused them to incur significant costs. Therefore, CIC Services challenged Notice 2016-66, raising two issues. First, they argued that the IRS failed to adhere to the mandatory notice-and-comment requirements under the APA in issuing Notice 2016-66. Second, they argued that the IRS issued Notice 2016-66 “arbitrar[ily] and capricious[ly]. . . .” CIC Services pleaded with the court to administer an injunction to prohibit the IRS from enforcing the disclosure requirements under Notice 2016-66 and to eventually set aside Notice 2016-66 completely. Ultimately, CIC would win on both issues on March 21, 2022, whereby the United States District Court of Eastern District Tennessee granted the requested injunction.
Beginning with the first issue, the APA requires that legislative rules be administered through a mandatory notice-and-comment requirement. While the IRS agreed with its failure to follow the APA’s procedure, the IRS argued that Congress exempted the IRS from this procedure. According to the IRS, Notice 2016-66 would be an interpretive rule and not a legislative rule. Therefore, Congress did not intend to place this requirement upon the IRS.
The court quickly disregarded the IRS’s contention by following precedent from an earlier decision decided in the Sixth Circuit. In Mann Construction, the Sixth Circuit disagreed with the IRS when using this exact argument. Mann Construction also challenged another notice (for a different transaction) due to the IRS’s failure to adhere to the notice-and-comment procedure. With an identical response to that made in CIC Services, the IRS argued that Congress had exempted the IRS from this APA procedure. The Sixth Circuit disagreed and held that the notice was a legislative rule and that Congress did not exempt the IRS from the APA’s procedure.
In CIC Services, the court held that the Sixth Circuit’s analysis was binding and “applie[d] equally to the arguments advanced by the IRS regarding Notice 2016-66 in this case.” Therefore, the court invalidated Notice 2016-66 for the IRS’s failure to adhere to the APA’s procedures.
To determine if an agency implemented an action arbitrarily and capriciously, courts must decide if the agency “examined ‘the relevant data’ and articulated ‘a satisfactory explanation’ for [its] decision, ‘including a rational connection between the facts found and the choice made.’” A court examines the administrative record to review an agency’s action for arbitrary or capricious findings. The administrative record would signify the data and facts the IRS focused upon when finding that micro-captive transactions should be considered transactions of interest. The court would look at the administrative record to see whether the agency:
has relied on factors which Congress has not intended it to consider, entirely failed to consider an important aspect of the problem, offered an explanation that runs counter to the evidence before the agency, or is so implausible that it could not be ascribed to a difference in view or the product of agency expertise.
From these factors, a court would “narrow[ly]” review the agency’s reasoning and uphold the action if the agency’s reasoning could “reasonably be discerned.”
Here, the focus was on the IRS’s administrative records in implementing Notice 2016-66. Congress does require taxpayers to give information to the IRS regarding reportable transactions, and the IRS may promulgate regulations requesting such specific details. Nonetheless, the IRS must do so with an actual basis “to designate micro-captive transactions as a ‘transaction of interest’ based on the potential for tax avoidance or evasion.” The court ultimately found that the IRS failed to include relevant data in the administrative record for indicating micro-captives as transactions of interest, which are reportable transactions. The court looked explicitly at the language used in Notice 2016-66 and other evidence from the IRS, such as cases, news releases, and federal statutes.
The court honed in on the IRS’s language in Notice 2016-66 for designating micro-captive transactions as transactions of interest. The IRS seemingly used general language, such as stating that they “are aware of a type of transaction” and “believe this transaction ([‘]micro-captive transaction[’]) has a potential for tax avoidance or evasion.”’ Further, the IRS and Department of Treasury stated that they “lack[ed] sufficient information to identify which § 831(b) arrangements should be identified specifically as a tax avoidance transaction and may lack sufficient information to define the characteristics that distinguish the tax avoidance transactions from other § 831(b) related-party transactions.” Essentially, the court noted that the IRS has confessed that it has no clear reasoning other than hopeful beliefs and suspicions. The IRS’s concern must be accompanied by relevant data or facts, which were not present in the administrative record in Notice 2016-66.
The IRS then pointed to litigation cases with some of these transactions. Still, the court noted that these cases failed to sway them because not all of them focused on micro-captive transactions, and not all concluded that they were abusive transactions. Additionally, the IRS had pointed to two IRS news releases, federal statutes, legislative history, and the IRS’s emails regarding the Notice. This IRS argument failed because the IRS did not substantiate how these were relevant in its decision-making.
Ultimately, the court looked for relevant facts and data, but the IRS had none to show in its administrative record, which is vital when issuing a regulation. While this does not mean that micro-captive transactions can never be abusive transactions, the IRS still ultimately failed to disprove that Notice 2016-66 was promulgated arbitrarily and capriciously.
Since the IRS failed to complete the notice-and-comment procedures and issued Notice 2016-66 arbitrarily and capriciously, the court had to administer the appropriate relief, which was to invalidate and set aside Notice 2016-66 and destroy the material taken already by the IRS. The APA’s text allows a reviewing court to “hold unlawful and set aside agency action” when it is found to be arbitrary and capricious. While the Sixth Circuit held that it must invalidate the action, the court noted that the United States Court of Appeals for the District of Columbia held that it “depends on the seriousness of the order’s deficiencies . . . .” While the court in this case did not specify what it deemed was the most consistent approach, the court found that vacating Notice 2016-66 was appropriate. The court would not give the IRS the benefit of keeping Notice 2016-66 in place while it took necessary actions to comply with the APA due to the IRS’s poor history of complying with the APA. This would not be the sole remedy, as the court noted how the taxpayers and material advisors expended time and resources for the past four years, whereby the IRS gained information that it was not entitled to receive. Therefore, the IRS had to return the information it wrongfully acquired, in addition to the court invalidating and setting aside Notice 2016-66.
After the decision in CIC Services, the IRS decided not to enforce the disclosure requirements or penalties dependent upon Notice 2016-66. Instead, the IRS and Department of Treasury issued proposed regulations to identify certain micro-captive transactions as listed transactions and certain others as transactions of interest. While Notice 2016-66 may be procedurally obsolete, it substantively lives on in these proposed regulations with some additional changes.
Certain micro-captive transactions will now be divided into two categories: (1) listed transactions and (2) transactions of interest instead of solely transactions of interest. Both transactions will involve direct or indirect ownership over a captive, which may include a derivative interest. The IRS deemed two features of micro-captive transactions as triggering a listed transaction designation, both of which were initially considered features of transactions of interest. The first feature is focused on a financing factor, while the second feature is determined by a loss ratio factor. A micro-captive transaction lacking either of these factors will be deemed a transaction of interest whereby the IRS will require more information, discussed below.
Under the Proposed Regulations, the IRS expanded Notice 2016-66’s definition of micro-captive ownership to ensure that it took into account derivatives and interests of the micro-captive. In keeping with Notice 2016-66, the Proposed Regulations maintain that ownership includes micro-captives with “20 percent” over at least “the voting power or the value of the outstanding stock or equity interest.” In addition, the Proposed Regulations include those who attempt to hide ownership through derivatives or as beneficiaries from trusts and estates. According to the IRS, this change will presumably ensure that it can track down those using the micro-captives as shams but who attempt to argue that they do not have ownership over a captive.
With the first feature, micro-captive transactions with a financing factor will now be deemed listed transactions. A financing factor would include micro-captives that have financed, loaned, or guaranteed any amount to a recipient whereby the recipient received the money free of taxable income during the computation period. The IRS has noted that the computation period would entail the most recent five years or all the taxable years if the micro-captive has existed for less than five taxable years. Ultimately, the presence of a financing factor, according to the IRS, exemplifies a tax abuse sham or avoidance.
With the second feature, micro-captive transactions with a certain loss ratio factor will now be deemed listed transactions. The loss ratio factor exists when a micro-captive’s insured losses and claims for administration expenses during the loss computation period are less than 65% of the premiums earned, reduced by policyholder dividends paid during the same period. Thus, the IRS reduced the original 70% loss ratio in Notice 2016-66 to 65%. Additionally, the loss computation period would no longer be five years, as in Notice 2016-66, but rather the most recent ten years of the micro-captive or all of the micro-captive’s years if the micro-captive has existed for less than ten years. This change allows a micro-captive to have a history to prove itself as a legitimate insurance company.
The IRS has proposed this percentage change be applied to both listed transactions and transactions of interest. The IRS noted that it was unaware of any non-abusive transactions that had to disclose due to the 70% rule. However, the loss ratio factor aids the IRS by demonstrating tax avoidance schemes through little to no claims and excessive premium pricing. Since premiums are present to cover potential loss for claims, the premiums should naturally reflect the losses. Hence, according to the IRS, the loss ratio factor is an excellent tool for exposing abusive transactions. However, the IRS did note that it would like to hear comments on potentially adopting a combined ratio factor instead of a loss ratio factor.
There are exceptions for micro-captive transactions that the IRS would not deem listed transactions. The transaction must involve (1) a consumer coverage insurance contract or (2) insurance for employee benefits where the Employee Benefits Security Administration of the U.S. Department of Labor has exempted these transactions. These exceptions apply to micro-captive transactions of interest.
The IRS will continue to find certain micro-captive transactions as transactions of interest. Specifically, these include transactions that are the same or substantially similar to a transaction involving a micro-captive with a contract and where the insured losses and claim administration expenses are less than 65% of the premiums earned minus the policyholder dividends paid by the micro-captive during the transactions of interest computation period. The transactions of interest computation period is the most recent nine taxable years of the micro-captive or all of the years if the micro-captive’s existence is less than nine years. According to the IRS, this allows them to seek more information on any potential transactions used for tax abuse schemes. The two exceptions described above for listed transactions also apply to transactions of interest. The IRS also made it clear that once any particular transaction becomes listed, it need not additionally disclose as a transaction of interest. According to the IRS, material advisors who are unsure how to categorize the transaction should still disclose the transaction as a listed transaction.
The IRS’s proposed regulations require disclosure statements under Form 8886 for both listed transactions and transactions of interest. However, the IRS has reduced the information required in this form compared to the information needed in Notice 2016-66. The IRS noted that certain information is no longer required to be disclosed. In particular, information such as “identify[ing] which factors of the proposed regulations apply, stat[ing] under what authority Captive is chartered, describ[ing] how amounts treated as premiums for coverage provided by Captive were determined, provid[ing] the amounts of reserves reported by Captive on its annual statement, or describ[ing] the assets held by Captive” is no longer required. However, the proposed regulations do require disclosure requirements about the insurance policies the micro-captive uses, the amount from claims, and the amount for premiums.
The Proposed Regulations set forth a disclosure safe harbor for owners of an insured company in a contract with a micro-captive. If an individual has direct or indirect ownership over the insured company, the individual may not need to disclose. The individual would need written or electronic proof that the insured company will adhere to or already has adhered to the disclosure requirements under the Proposed Regulations. Owners may use Form 8886 as acknowledgment. However, an owner would be required to timely file disclosures if the insured company failed to do so.
Taxpayers, material advisors, and other participants in micro-captive transactions may face higher penalties now that certain micro-captive transactions are listed transactions instead of solely transactions of interest. This new designation will create a much larger penalty scheme for taxpayers and materials advisors while echoing some penalties discussed in Notice 2016-66. Additionally, the Proposed Regulations emphasized several other penalties (not discussed in Notice 2016-66) that can affect all participants in the micro-captive transactions. The Secretary may also use an extra year of tax assessment for those who fail to include information about a micro-captive.
In addition to the potential for “listed transaction” penalties, taxpayers may also be subject to the 20% accuracy-related penalty described in Notice 2016-66. Taxpayers who fail to file or file false or incomplete information on a tax return regarding a micro-captive listed transaction may face an initial maximum penalty of $200,000 as a corporate taxpayer or $100,000 as an individual taxpayer. Additionally, the IRS may impose a 20% penalty on any taxpayer who received a deduction by filing inaccurate information on a tax return about the transaction. For example, a taxpayer may have filed a tax form for $20,000 gained from a micro-captive but was supposed to file for $200,000. The IRS’s accuracy penalty would charge 20% from the understatement, which would be the $180,000 difference. Therefore, the taxpayer would need to pay an additional $36,000 as this is 20% of the understatement, which would get added to a potential maximum penalty of $200,000 or $100,000.
Second, material advisors will face higher penalties if they are involved with listed transaction micro-captives, in addition to the same penalties noted in Notice 2016-66 for failure to disclose an advisee list requested by the Secretary. With the new listed transaction designation, material advisors who fail to furnish information (or timely file) can face a higher penalty equal to the greater of 50% of the income derived for assisting in the transaction or a flat fee of $200,000. Further, the Secretary may request a written list of the material advisor’s advisees, which the material advisor would have twenty days from the Secretary’s notice to send this list. The material advisor could face penalties of up to $10,000 each day after the twentieth day of failure to disclose, unless the advisor fails for reasonable cause.
Third, the Proposed Regulations also detail other penalties for participating taxpayers and material advisors who take part in an abusive micro-captive scheme. For promoting abusive tax shelters through intentionally false statements, using statements that one would reasonably know are false, or giving a gross valuation overstatement, Section 6700 designates a penalty of $1,000 for each arrangement and an additional 50% penalty for any income derived from these statements. There is also a knowledge requirement that the IRS must prove unless the individual made a gross valuation overstatement, which is when the fair market value would exceed 200% of what was on the tax return.
As an example of a Section 6700 penalty, if an individual organized a micro-captive and encouraged five corporations to buy an interest in the entity to gain a supposedly lawful deduction, there would be a $5,000 penalty. Since there were five arrangements with five different corporations, the IRS could impose a $5,000 fine if it proved the statements were false or should be reasonably known as false. If the corporation also paid the individual $10,000 for the arrangement, there would be an additional $5,000 penalty on the individual due to the 50% penalty for income gained. However, if the IRS found a gross valuation overstatement, it could skip proving any falseness of statements. With the prior example, if the amount placed on the tax return were $50,000 but, in actuality, the number should have been $200,000, there would be a gross valuation overstatement, which means the IRS could automatically penalize $1,000 for each arrangement.
Other penalty regimes contained in the Proposed Regulations (but not in Notice 2016-66) are Section 6700 through Section 6701. The IRS may penalize an individual $1,000 (or $10,000 for a corporation) for aiding and abetting an understatement on a tax return. The aiding and abetting penalty is helpful for the IRS when the IRS cannot prove the falseness of a statement or find the presence of a gross valuation overstatement. In the last example from the previous paragraph, the IRS, through Section 6701, could penalize a natural person $1,000 for the understatement on the tax return. Section 6701 is essentially a catch-all penalty that allows the IRS to punish those handling micro-captive transactions with reporting understatements.
Finally, another factor could allow the IRS more room to penalize participants required to file tax information about micro-captive transactions. Suppose a participant fails to include micro-captive details on a tax return or statement. In that case, the Secretary automatically gains one additional year of tax assessment because of the new listed transaction designation. This extra year begins the earlier of once the Secretary receives the required information or when the material advisor sends the Secretary the necessary lists about the micro-captive’s transaction history.
The new Proposed Regulations will likely deter individuals from participating in micro-captive transactions for two key reasons: higher penalties and heightened scrutiny. The biggest new factor in this regard is the potential for micro-captive participants to get ensnared in a listed transaction. As discussed above, the listed transaction potential penalties have increased greatly over what non-compliant micro-captive participants previously faced under Notice 2016-66. For example, material advisors and taxpayers have a $150,000 and $90,000 increase, respectively, as a base penalty for failing to disclose a micro-captive listed transaction over the Notice penalties. Additionally, all micro-captive participants also may end up being assessed the catch-all penalty included in the Proposed Regulations. This catch-all penalty under Section 6701 for aiding or abetting an understatement of tax liability is easily administered since it only requires an understatement on a tax return. As such, micro-captive participants and material advisors need to think hard on whether the compliance costs and potential assessable penalties for disclosure missteps are worth the benefits of the transaction.
In addition to the increased potential penalties, the Proposed Regulations also bring greater scrutiny to certain aggressive micro-captive transactions. The IRS generally reserves listed transaction status for transactions that it wants to take a hard look at and nearly presume to be abusive and non-compliant. This type of scrutiny is a strong deterrent to potential material advisors since it comes with (1) increased compliance costs; (2) self-reporting that they know the IRS will review very carefully; and (3) the heightened potential that the IRS will litigate the material advisor’s transactions. In addition to the scrutiny of material advisors, listed transaction status leads to additional scrutiny of the micro-captive participants. As discussed above, material advisors must produce a list to the IRS of all participants in any micro-captive transactions and provide certain information about the transaction. The list must be maintained for seven years and some of this information may include (1) identifying and describing the transaction; (2) the tax benefits from the transaction; and (3) who the material advisor aided. As discussed above, material advisors must provide accurate information to avoid any accuracy-related penalties. Thus, the IRS will be provided with everything it needs to know to launch audits and litigation upon micro-captive participants. The risk is too significant for most reasonable taxpayers to believe that the potential tax savings are worth the IRS compliance risk. Aggressive micro-captive transactions will no longer be desirable because “[w]hen the IRS announces that a tax strategy is a listed transaction or transaction of interest, market demand for that strategy among taxpayers typically ceases.”
The IRS sought to resolve its loss in CIC Services by issuing the Proposed Regulations. As taxpayers were quick to challenge Notice 2016-66, there may be court challenges to the Proposed Regulations. The two challenges taxpayers brought in CIC Services were the failure to follow the notice-and-comment procedures under the APA and the issuance of a guidance done arbitrarily and capriciously. Reviewing the case of CIC Services, one may see how the IRS’s Proposed Regulations would stack up against these two potential challenges.
The notice-and-comment procedure under the APA will likely not be an issue for the IRS. The IRS has complied with the APA by having a notice period in the Proposed Regulations, stating that the IRS will have a public hearing for comments on July 19, 2023, at 10:00 a.m. through teleconference. Further, individuals may submit written comments electronically. Therefore, the IRS likely has properly complied with the APA’s notice-and-comment procedure, as the IRS has given notice.
Taxpayers could also challenge the Proposed Regulations as being arbitrary and capricious. This time, however, the IRS has prepared for arbitrary or capricious challenges by describing how it arrived at the provisions in the Proposed Regulations (unlike what was contained in Notice 2016-66). For example, when discussing how the IRS arrived at its original 70% for the loss ratio factor in Notice 2016-66, the IRS noted its basis for this number by looking at IRC § 833(c)(5) for Blue Cross and Blue Shield organizations. Congress enacted an 85% medical loss ratio test in § 833(c)(5). The IRS and Treasury Department also “considered data from the National Association of Insurance Commissioners (“NAIC”) in determining the applicable loss ratio factor.”
Further, in arriving at the new 65% threshold in the Proposed Regulations, the IRS noted that it did not wrongfully penalize any non-abusive micro-captives at 70% and that 65% would help the IRS crack down on abusive micro-captives while not requesting wrongful disclosures from non-abusive micro-captives. Therefore, the 65% threshold would be better for the IRS and non-abusive micro-captives. Ultimately, the IRS has, at a minimum, likely demonstrated that its choice of percentage under the Proposed Regulations was arrived at by using relevant data and not done so arbitrarily.
The IRS also noted research regarding the costs for disclosure requirements under Form 8886 and a chart to display the safety of the micro-captive insurance economy. The study regarding disclosures included the average time and money expended in filing Form 8886. The IRS’s Research, Applied Analytics, and Statistics division went as far as to calculate the price for the disclosure requirements to demonstrate that it would not be burdensome or economically harmful. Further, the IRS used a chart to illustrate how these Proposed Regulations would not tank the micro-captive transaction economy. The IRS will likely use this research and data to prepare for arbitrary and capricious challenges by demonstrating that the IRS issued its new regulations with relevant data.
There currently does not appear to be any calls for court challenges to the Proposed Regulations. However, should a CIC Services-type challenge arise, the IRS would likely prevail on both of the challenges, as the IRS has given notice and an actual basis for its decisions in its administrative record. Time will tell on what type of court challenges may arise (if any), but, for now, the IRS is likely safe from a CIC Services-type case.
How the Proposed Regulations will ultimately affect the micro-captive industry is yet to be fully seen. Certain commentators have already expressed that they do not favor the Proposed Regulations changes to the micro-captive industry. The IRS will hear comments during the notice-and-comment procedure for the Proposed Regulations, and many will be eager to see whether the IRS takes account of these comments in the final regulations. Yet, the IRS has set its sights on stopping abusive micro-captives, and the Proposed Regulations are a great deterrent to material advisors and potential participants to entering aggressive micro-captive transactions.