Computing the Reportable Transaction Penalty

The Section 6707A reportable transaction penalty can be difficult to work with given the more limited avenues for contesting the penalty. The court addressed this in Bitter v. Commissioner, T.C. Memo. 2017-46, in the context of a Section 412(i) plan. Tax advisors have been waiting for an answer to the very question about how to compute the penalty that is posed in the Bitter case. That question is whether the amount listed on the tax return must be used to compute the penalty or if the true decrease in tax is to be used.

The 6707A Reportable Transaction Penalty

The Section 6707A reportable transaction penalty applies if the taxpayer fails to report certain transactions to the IRS on a Form 8886, Reportable Transaction Disclosure Statement, with their tax return. The IRS determines which transactions are reportable by identifying transactions and designating them as listed transactions. Unlike most other tax penalties, the Section 707A reportable transaction penalty is an assessable penalty. This means that the IRS can assess the penalty without going through the statutory notice procedures. This also means that taxpayers generally cannot contest the penalty in U.S. Tax Court. So taxpayers have to pay the penalty, file a refund claim, wait for the refund claim to be denied, and then sue for a refund in U.S. District Court or the Federal Claims Court.

Section 412(i) Plans

Section 412(i) plans are a type of retirement plan where the plan purchases life insurance on the participants and the participants receive death benefits from the plan. Unlike traditional pensions, Section 412(i) plans have the advantage of not requiring the business to made additional contributions if the investments held by the plan lose money or do not perform well.

The IRS’s View of Section 412(i) Plans

Section 412(i) plans were popular in the late 1990s and early 2000s. Their popularity waned shortly thereafter given the IRS’s tough stance on these plans. The then new Section 6707A reportable transaction penalty all but killed Section 412(i) plans, as the IRS designated the plans as listed transactions that had to be reported to the IRS.

The IRS has taken the position that the full amount of the deductions taken for the plan are to be used to determine the amount of the Section 6707A penalty. Tax advisors have wondered whether the amount for the portion of the deductions for contributions that would be deductible under another Code section should be removed when calculating the Section 6707A penalty. The IRS takes the position that the penalty is computed based only on the amount listed on the tax return. So for example, if the taxpayer made an error and grossly overreported the amount of the Section 412(i) deduction, the IRS would say that the penalty is computed based on this amount–which would produce a larger penalty. The same would be true if the taxpayer grossly underreported the deduction on his return–which would produce a smaller penalty. This issue has not been considered by the courts, which is probably due in large part to the Section 6707A penalty not being subject to challenge in U.S. Tax Court.

Challenging the Section 6707A Penalty

This brings us to the Bitter case. The taxpayer in Bitter was asking the U.S. Tax Court to consider this question for the penalty as part of a challenge to a collection due process (“CDP”) hearing. As noted by the court, the U.S. Tax Court can consider whether a taxpayer is liable for this penalty, but it can only do so if the taxpayer has not previosly had an opportunity to contest his liablity for the penalty. The court noted that the taxpayer had challenged this penalty adminsitratively by having a conference with the IRS Office of Appeals. Since the taxpayer was afforded this opportunity, he was precluded from challenging the penalty in the U.S. Tax Court. So the question remains as to whether the Section 6707A penalty is to be computed using the full deduction amount under Section 412(i) (which has been re-numbered in the Code) or the difference between this amount and the amount of the deduction that would otherwise be allowable even though not reported on the taxpayer’s tax return.


  1. Computing the Reportable Transaction Penalty – Empowered Tax says:

    […] Read More: Computing the Reportable Transaction Penalty […]

  2. Computing the Reportable Transaction Penalty – Kreig Mitchell says:

    […] Read More: Computing the Reportable Transaction Penalty […]

Leave a Comment:

Houston Tax Attorney Press
houston tax attorney | sitemap | terms | resources | contact us

IRS Tax Trouble
7500 San Felipe St.
Houston, Texas 77063
(713) 909-4906

New! Get Updates by Email!

Texas: Abilene, Addison, Alamo, Alamo Heights, Aledo, Alice, Allen, Alpine, Alvarado, Alvin, Amarillo, Andrews, Angleton, Anna, Aransas Pass, Arcola, Argyle, Arlington, Atascocita, Athens, Atlanta, Austin, Azle, Balch Springs, Barstow, Bastrop, Bay City, Baytown, Beaumont, Bedford, Bellaire, Benbrook, Big Lake, Big Spring, Bonham, Bowie, Brady, Bridgeport, Brownfield, Brownsville, Bryan, Buda, Canton, Carrizo Springs, Carrollton, Cedar Hill, Cedar Park, Channelview, Childress, Chillicothe, Cinco Ranch, Cisco, Cleburne, Clute, Cockrell Hill, Colleyville, College Station, Colorado City, Commerce, Copperas Cove, Corpus Christi, Corsicana, Crane, Crockett, Crowley, Dalhart, Dallas, Deer Park, Decatur, Del Rio, Denison, Denton, DeSoto, Dickinson, Eagle Mountain, Eagle Pass, Edinburg, El Campo, El Paso, Ennis, Fairfield, Falfurrias, Farmers Branch, Flower Mound, Forney, Fort Davis, Fort Stockton, Fort Worth, Fredericksburg, Freeport, Fresno, Frienswood, Frisco, Gainesville, Galveston, Georgetown, Glen Rose, Grand Prairie, Grandview, Grapevine, Haltom City, Harlingen, Highland Park, Highland Village, Hillsboro, Hitchcock, Hondo, Houston, Huntsville, Hurst, Hutchins, Irving, Itasca, Jacinto City, Jasper, Jersey Village, Johnson City, Joshua, Junction, Justin, Katy, Kemah, Kennedale, Kermit, Killeen, Kingsville, Krum, La Feria, Lake Dallas, Lake Jackson, La Marque, Lake Worth, Lamesa, La Porte, Laredo, Las Colonias, League City, Levelland, Lewisville, Lindale, Little Elm, Live Oak, Lockhart, Longview, Los Fresnos, Lubbock, Lufkin, Lumberton, McAllen, McKinney, Mansfield, Marfa, Marshall, Mesquite, Midland, Midlothian, Millsap, Mineral Wells, Mission, Missouri City, Monahans, Montgomery, Mount Pleasant, Nacogdoches, Navarro, Nederland, Navasota, Needville, New Braunfels, New Territory, Nocona, Northlake, North Richland Hills, Oak Grove, Odessa, Orange, Ozona, Palestine, Palmhurst, Palmview, Pampa, Pantego, Paris, Parker, Pasadena, Pearland, Pecos, Pelican Bay, Pflugerville, Pharr, Pilot Point, Pinehurst, Pittsburg, Plainview, Plano, Pleasanton, Port Aransas, Port Arthur, Portland, Port Lavaca, Post, Prairie View, Ranger, Rankin, Raymondville, Red Oak, Refugio, Rhome, Rice, Richardson, Richland, Richland Hills, Richmond, Rio Grande City, River Oaks, Riverside, Roanoke, Robstown, Rockport, Rockwall, Rosenburg, Round Rock, Rowlett, Royse City, Rusk, Saginaw, San Angelo, San Antonio, San Benito, Sanger, San Juan, San Marcos, Santa Fe, Schertz, Schulenburg, Seagoville, Sealy, Seguin, Shiner, Sienna Plantation, Simonton, Snyder, Sonora, Southlake, South Padre Island, Splendora, Spring, Springtown, Stafford, Stephenville, Sugarland, Sulphur Springs, Temple, Terrell, Texarkana, Texas City, Texhoma, The Woodlands, Three Rivers, Tomball, Trophy Club, Troy, Tyler, University Park, Uvalde, Victoria, Waco, Watauga, Waxahachie, Weatherford, Webster, Weslaco, West, Westlake, Whitesboro, White Settlement, Wichita Falls, Willis

© 2005-present all rights reserved

Not certified by the Texas Board of Legal Specialization.