<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:googleplay="http://www.google.com/schemas/play-podcasts/1.0"><channel><title><![CDATA[Tax Coda]]></title><description><![CDATA[Clear, independent coverage of the rulings, guidance, and shifts shaping U.S. tax. Weekday updates plus a Sunday digest.]]></description><link>https://taxcoda.com</link><image><url>https://substackcdn.com/image/fetch/$s_!5cG2!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fab017102-2a2e-414e-9b4e-111a7d2ed1c6_500x500.png</url><title>Tax Coda</title><link>https://taxcoda.com</link></image><generator>Substack</generator><lastBuildDate>Mon, 07 Sep 2026 11:07:56 GMT</lastBuildDate><atom:link href="https://taxcoda.com/feed" rel="self" type="application/rss+xml"/><copyright><![CDATA[Tax Coda]]></copyright><language><![CDATA[en]]></language><webMaster><![CDATA[taxcoda@substack.com]]></webMaster><itunes:owner><itunes:email><![CDATA[taxcoda@substack.com]]></itunes:email><itunes:name><![CDATA[Tax Coda]]></itunes:name></itunes:owner><itunes:author><![CDATA[Tax Coda]]></itunes:author><googleplay:owner><![CDATA[taxcoda@substack.com]]></googleplay:owner><googleplay:email><![CDATA[taxcoda@substack.com]]></googleplay:email><googleplay:author><![CDATA[Tax Coda]]></googleplay:author><itunes:block><![CDATA[Yes]]></itunes:block><item><title><![CDATA[Court denies social media marketing deductions for celebrity experiences]]></title><description><![CDATA[Suleiman Sami v. Commissioner. United States Tax Court No. 8834-23 and No. 16512-23. T.C. Memo. 2026-69.]]></description><link>https://taxcoda.com/p/court-denies-social-media-marketing</link><guid isPermaLink="false">https://taxcoda.com/p/court-denies-social-media-marketing</guid><dc:creator><![CDATA[Adam Parr]]></dc:creator><pubDate>Wed, 26 Aug 2026 11:03:47 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!5cG2!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fab017102-2a2e-414e-9b4e-111a7d2ed1c6_500x500.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>Just because you post your brunch with a celebrity on Instagram doesn&#8217;t mean the IRS will let you write it off. If the main reason you spent the money was personal, it&#8217;s not a business expense&#8212;no matter how many followers you pick up.</p><h3>Holding</h3><p>The Tax Court took one look at Suleiman Sami&#8217;s expense list&#8212;celebrity selfies, award shows, charity galas, streaming subscriptions, the works&#8212;and said, nice try. Posting about your run-in with Benedict Cumberbatch doesn&#8217;t magically turn it into a business deduction. The court did let him keep some transportation costs, credit card fees, a slice of his phone bill, and the QBI deduction. But the accuracy penalty? That stuck too.</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://taxcoda.com/p/court-denies-social-media-marketing?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://taxcoda.com/p/court-denies-social-media-marketing?utm_source=substack&utm_medium=email&utm_content=share&action=share"><span>Share</span></a></p><h3>Why It Matters</h3><ul><li><p>The court didn&#8217;t buy the influencer special pleading. Regular business expense rules still apply, even if your &#8216;business&#8217; is posting about your VIP lifestyle. Just because you can monetize your personal life doesn&#8217;t mean the tax code suddenly gets more generous.</p></li><li><p>The key question: Why did you spend the money in the first place? If it was mostly for yourself, the fact that you later got more followers or engagement doesn&#8217;t turn brunch with Matt Damon into a business write-off.</p></li><li><p>This is a recurring headache for influencers: when your &#8216;business&#8217; is basically living large, it&#8217;s hard to convince the IRS that your spending isn&#8217;t just personal consumption with a filter slapped on. Just because something is vaguely business-adjacent doesn&#8217;t make it deductible.</p></li><li><p>The court also floated the idea that if you&#8217;re spending before your influencer gig actually makes money, maybe those are startup costs, not regular business expenses. But Sami didn&#8217;t have the paperwork to even argue that point, so the court left it hanging.</p></li><li><p>This case is also a recordkeeping clinic. When Sami actually kept trip logs for his driving business, he got the deduction. When he just waved around credit card statements with no details, the court shrugged. If you can&#8217;t show what you bought or why it mattered for your business, good luck.</p></li></ul><h3>Key Facts</h3><p>Suleiman Sami worked full-time in JetBlue&#8217;s IT department from 2019 through 2021. He also operated S Sami Services LLC, a single-member LLC treated as a disregarded entity for federal income tax purposes.</p><p>Sami described the business as having three components:</p><ul><li><p>transportation services;</p></li><li><p>resale of event tickets; and</p></li><li><p>social media influencing.</p></li></ul><p>He reported the combined activities on Schedule C.</p><p>S Sami Services reported gross receipts of $169,532 for 2019, $93,229 for 2020, and $133,252 for 2021. Most, if not all, of those receipts came from transportation services. Some may have come from ticket sales. None came from social media influencing during the years before the Court.</p><p>By October 2025, Sami had approximately 520,000 TikTok followers, 140,000 Instagram followers, and 4,200 followers on X. He testified that he later earned about $25,000 annually from social media advertising revenue sharing. The record did not establish how many followers he had from 2019 through 2021.</p><p>Sami spent significant amounts on celebrity encounters and exclusive events. Among other expenditures, he paid:</p><ul><li><p>$10,000 for two Grammy tickets;</p></li><li><p>$2,700 for two Emmy tickets;</p></li><li><p>$8,912 for an interaction with Benedict Cumberbatch;</p></li><li><p>$4,151 for an interaction with Matt Damon;</p></li><li><p>$2,600 for an interaction with Mark Ruffalo;</p></li><li><p>$2,025 for a personalized Chris Evans video;</p></li><li><p>$6,500 to attend Tiger Jam 2019;</p></li><li><p>$831 to catch a pass from Drew Brees;</p></li><li><p>$779 to return a John McEnroe serve;</p></li><li><p>$425 for training and lunch with Chuck Liddell; and</p></li><li><p>$6,317 for signed Kobe Bryant game-issue shoes.</p></li></ul><p>He also paid for other celebrity and sporting experiences, including an opportunity to catch a pass from Tom Brady.</p><p>Sami generally purchased these experiences through charities. He originally claimed many of the payments as charitable contribution deductions. After the IRS disallowed them, he changed his position and argued that they constituted marketing expenses for his business.</p><p>He photographed or recorded many of the experiences and posted the content on social media. He testified that some posts increased attention to his accounts and generated inquiries from users interested in similar celebrity experiences.</p><p>The IRS determined deficiencies of $63,219 for 2019, $27,421 for 2020, and $39,910 for 2021. It also determined 20% &#167;6662(a) penalties of $12,644, $5,484, and $7,982, respectively.</p><h3>Statutory and Regulatory Framework</h3><p>Section 162(a) allows a taxpayer to deduct ordinary and necessary expenses paid or incurred in carrying on a trade or business. Section 262(a) generally prohibits deductions for personal, living, and family expenses.</p><p>An expense with both business and personal characteristics must be primarily undertaken for business purposes to qualify under &#167;162.</p><p>Section 274(d) imposes heightened substantiation requirements for specified categories of expenses, including certain listed property. When &#167;274(d) does not apply, the rule from <em>Cohan v. Commissioner</em> permits a Court to estimate a deductible expense if the taxpayer proves that a deductible expense occurred and supplies a reasonable evidentiary basis for estimating the amount.</p><p>Section 195 generally requires capitalization of startup expenditures incurred before an active trade or business begins, subject to the deductions permitted under that section.</p><p>Section 199A allows eligible taxpayers a deduction based in part on qualified business income from a qualified trade or business.</p><h3>Arguments</h3><p>Taxpayer argued:</p><ul><li><p>The celebrity encounters, entertainment events, and charitable event purchases were treated as marketing expenses because he used them to create social media content.</p></li><li><p>Celebrity content increased views, followers, and user engagement, and could eventually increase advertising revenue.</p></li><li><p>Comparable social media influencers routinely pay to attend events, premieres, and similar experiences to create content.</p></li><li><p>His transportation records supported substantial vehicle expenses even though he had not recorded exact mileage.</p></li><li><p>His phone, streaming subscriptions, and other expenses supported his transportation, ticket resale, and social media activities.</p></li><li><p>His Schedule C income qualified for the &#167;199A deduction.</p></li><li><p>The IRS failed to establish proper supervisory approval for the 2019 and 2020 penalties.</p></li><li><p>He had reasonable cause and acted in good faith regarding the disputed tax positions.</p></li></ul><p>Government argued:</p><ul><li><p>Sami failed to establish that many claimed expenses had a business purpose.</p></li><li><p>Bank and credit card statements established that payments occurred but generally did not establish what Sami purchased or how the expenditure related to his business.</p></li><li><p>The celebrity experiences and entertainment expenditures were personal rather than ordinary and necessary business expenses.</p></li><li><p>Sami failed to satisfy the applicable substantiation requirements for numerous deductions.</p></li><li><p>The &#167;6662(a) penalties were properly approved and applied.</p></li></ul><h3>Court&#8217;s Reasoning</h3><ul><li><p><strong>The celebrity experiences were primarily personal.</strong> The Court focused on Sami&#8217;s purpose in purchasing the experiences rather than on their potential later effect on his social media accounts. Grammy tickets, celebrity encounters, sporting experiences, and similar purchases offered obvious personal enjoyment, prestige, or status. The Court found that those personal motives predominated.</p></li><li><p><strong>Generating useful content did not make a personal expense deductible.</strong> Sami showed that some celebrity posts produced attention and engagement. The Court found that insufficient. A personal expenditure can generate useful business material without being treated as a business expense. The relevant question remained why the taxpayer primarily incurred the expense.</p></li><li><p><strong>Influencers remain subject to ordinary &#167;162 rules.</strong> The Court stated that a social media influencer business is no different from another for-profit enterprise for purposes of applying the general business-expense rules. An expense commonly incurred by influencers still must satisfy &#167;162.</p></li><li><p><strong>The timing of the influencer activity created an additional problem.</strong> Sami earned no social media advertising revenue from 2019 to 2021. The Court observed that if the disputed expenditures represented costs of developing a future revenue-producing social media business, they could constitute startup expenditures governed by &#167;195 rather than currently deductible &#167;162 expenses. The Court did not resolve that issue.</p></li><li><p><strong>Sami did not adequately substantiate most claimed marketing expenses.</strong> His bank and credit card statements often contained only merchant names, payment processors, usernames, or transaction numbers. They generally did not identify what he purchased, establish a business purpose, or connect a specific purchase to particular social media content.</p></li><li><p><strong>General marketing expenses failed for the same evidentiary reason.</strong> Charges involving PayPal transfers, events, ticket vendors, Cameo, music purchases, and services that appeared to increase social media follower counts lacked enough documentation for the Court to determine which expenses were business-related.</p></li><li><p><strong>Television and streaming expenses remained personal.</strong> Sami claimed that subscriptions including DirecTV, cable service, Netflix, Hulu, WWE, and Apple helped him monitor entertainment trends and identify events. The Court found no sufficiently direct relationship between those subscriptions and his business.</p></li></ul><h3>Transportation Expenses</h3><p>The transportation deductions produced a materially different result because Sami maintained substantial contemporaneous records.</p><p>He recorded individual trips on paper vouchers showing dates, customer information, starting and ending locations, fares, tolls, taxes, and total charges. The vouchers did not contain the exact mileage.</p><p>Sami later used the recorded locations and Google Maps to estimate mileage. He claimed 62,533 business miles for 2019, 20,574 for 2020, and 38,869 for 2021.</p><p>The IRS argued that the strict substantiation requirements of &#167;274(d) applied.</p><p>The Court disagreed. Section 280F excludes from the definition of a passenger automobile a vehicle used directly in the business of transporting people or property for compensation or hire. Sami used his vehicles to transport paying customers directly. The heightened &#167;274(d) substantiation rule therefore did not control those vehicle expenses.</p><p>The Court applied <em>Cohan</em> instead.</p><p>Because Sami had contemporaneous evidence of the trips but had failed to record exact pickup and drop-off addresses, the Court reduced his estimates by 20%.</p><p>It allowed vehicle deductions of:</p><ul><li><p>$29,015 for 2019;</p></li><li><p>$9,464 for 2020; and</p></li><li><p>$17,414 for 2021.</p></li></ul><p>The Court applied the same 80% allowance to substantiated toll and parking expenses, allowing $11,101 for 2019, $5,042 for 2020, and $35 for 2021.</p><p>This part of the opinion reinforces the distinction between imperfect records and records that are not usable. Sami&#8217;s transportation documentation gave the Court a factual basis for estimating expenses. His marketing records generally did not.</p><h3>Other Expense Rulings</h3><p>The Court denied $730 of the claimed 2021 cost of goods sold for event tickets. Sami showed purchases from SeatGeek and Ticketmaster but did not establish that he resold the particular tickets.</p><p>The Court denied the claimed contract labor deductions of $600, $600, and $900 for 2019 through 2021. It accepted that Sami sometimes paid relatives to drive, but lacked evidence to determine or estimate the amounts.</p><p>The Court declined additional office-expense deductions because the claimed expenditures represented supplies, and Sami had already received unchallenged deductions for supplies on the returns.</p><p>The Court allowed credit card processing fees of $10,904 for 2019, $6,749 for 2020, and $9,186 for 2021. Sami established that the charges related to customers paying for transportation and ticket purchases.</p><p>For cell phone service, the Court accepted that Sami needed at least one phone for his transportation business but found four phones and multiple service providers excessive without evidence establishing their business use. Applying <em>Cohan</em>, 25% of the claimed cell service expenses were allowed.</p><p>The Court denied deductions for phone equipment because Sami failed to establish that the equipment was for business rather than personal use.</p><h3>Qualified Business Income</h3><p>The Court held that Sami&#8217;s Schedule C income from transportation and event ticket sales constituted qualified business income under &#167;199A.</p><p>Those activities were neither specified service trades or businesses nor services performed as an employee. The income, therefore, came from qualified trades or businesses for purposes of &#167;199A.</p><p>The Court&#8217;s ruling on the QBI deduction was separate from its rejection of the claimed influencer expenses.</p><h3>Accuracy-Related Penalties</h3><p>The IRS imposed &#167;6662(a) penalties based on substantial understatements of income tax.</p><p>Sami challenged supervisory approval of the 2019 and 2020 penalties because the manager&#8217;s signature on a penalty approval form did not contain a date.</p><p>The Court rejected that argument. The same manager had signed the 30-day letter asserting the penalties before the IRS issued the notice of deficiency. That written approval satisfied &#167;6751(b)(1) under controlling Second Circuit precedent.</p><p>The parties agreed that approval of the 2021 penalty was proper.</p><p>Sami also asserted reasonable cause and good faith under &#167;6664(c).</p><p>The Court rejected the defense. Sami had bachelor&#8217;s and master&#8217;s degrees in accounting and had previously worked at PricewaterhouseCoopers. Despite that background, he kept no business books, used accounts that mixed personal and business expenditures, lacked receipts for many purchases, and could not establish the business purpose of many of the claimed expenses.</p><p>The Court concluded that he did not exercise ordinary business care and prudence.</p><h3>Result</h3><p>The Tax Court allowed portions of Sami&#8217;s transportation, toll, credit card processing, cell phone, and &#167;199A deductions, denied the disputed influencer and other inadequately substantiated expenses, sustained the &#167;6662(a) penalties, and directed the parties to compute the final deficiencies under Rule 155.</p><h3>The Takeaway</h3><p>You can&#8217;t just snap a selfie, post it, and call your life a business expense. If you&#8217;re advising influencers, focus on the basics: what was the real reason for the spending, when did the business actually start, and do you have records that tie the expense to actual revenue? Otherwise, expect the IRS to call your bluff.</p><h3>List of Citations</h3><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://taxcoda.com/subscribe?&quot;,&quot;text&quot;:&quot;Upgrade&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">This post has bonus content for paid subscribers. Upgrade to get full access.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Upgrade"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p></p>]]></content:encoded></item><item><title><![CDATA[Court denies interest abatement because IRS case processing involved no unreasonable delay]]></title><description><![CDATA[Andrew Tabaka v. Commissioner. United States Tax Court No. 16687-24. T.C. Memo. 2026-70.]]></description><link>https://taxcoda.com/p/court-denies-interest-abatement-because</link><guid isPermaLink="false">https://taxcoda.com/p/court-denies-interest-abatement-because</guid><dc:creator><![CDATA[Adam Parr]]></dc:creator><pubDate>Tue, 25 Aug 2026 11:57:02 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!5cG2!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fab017102-2a2e-414e-9b4e-111a7d2ed1c6_500x500.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>Just because your tax case drags on doesn&#8217;t mean you get out of paying interest. If you want relief under &#167;6404(e), you need to show the IRS actually messed up on some routine paperwork or admin&#8212;not just that the process took a while.</p><h3>Holding</h3><p>The Tax Court sided with the IRS. No, they didn&#8217;t abuse their discretion by refusing to wipe out $1,649 of interest on Andrew Tabaka&#8217;s 2016 tax bill. The IRS moved the case along at a normal pace, and the stuff Tabaka complained about was all about figuring out his actual tax&#8212;not some clerical slip-up.</p><h3>Why It Matters</h3><ul><li><p><strong>The decision applies a narrow statutory standard.</strong> Section 6404(e) does not authorize interest abatement whenever an IRS examination, Appeals proceeding, or Tax Court case takes longer than the taxpayer believes necessary. The taxpayer must connect the interest to an unreasonable IRS error or delay involving a qualifying ministerial or managerial act.</p></li><li><p><strong>Normal litigation time generally does not qualify.</strong> The Court treated the approximately 16 months between the IRS&#8217;s first written contact and entry of the stipulated Tax Court decision as routine, particularly because the case moved through examination, Appeals, IRS counsel, and settlement.</p></li><li><p><strong>Disputes over substantive tax liability fall outside &#167;6404(e).</strong> Determining whether reported Forms 1099-R correctly reflected taxable retirement distributions required legal and factual judgment. Those decisions were not ministerial or managerial acts.</p></li><li><p><strong>The decision also illustrates an important jurisdictional rule.</strong> When the IRS does not issue a formal final determination on an interest-abatement claim, &#167;6404(h)(1)(A)(ii) allows an eligible taxpayer to petition the Tax Court after 180 days have passed from filing the claim. The absence of a formal denial, therefore, does not leave the taxpayer without judicial review.</p></li></ul><h3>Key Facts</h3><p>Andrew Tabaka and his wife filed their 2016 federal income tax return in March 2017.</p><p>The IRS identified $93,200 of retirement income reported by third parties on two Forms 1099-R but not reported on the return. On April 16, 2018, the IRS issued a CP2000 proposing:</p><ul><li><p>A $23,960 income tax deficiency.</p></li><li><p>A $4,792 accuracy-related penalty.</p></li></ul><p>The IRS did not receive an adequate response and issued a notice of deficiency on July 9, 2018.</p><p>Tabaka petitioned the Tax Court on October 10, 2018. He also paid $10,590 toward the disputed 2016 liability that day.</p><p>The case went to the IRS Independent Office of Appeals in December 2018. Appeals scheduled a conference for January 2019 and warned Tabaka that interest would continue accruing until the liability was paid.</p><p>Appeals could not resolve the dispute and returned the docketed case to IRS counsel in April 2019 for trial preparation.</p><p>The Tax Court scheduled a trial on June 5, 2019. Tabaka made an additional payment of $7,848 on July 3, bringing his total payments to $18,438.</p><p>The parties then settled. They stipulated that:</p><ul><li><p>Tabaka owed an $18,438 deficiency for 2016.</p></li><li><p>No accuracy-related penalty applied.</p></li><li><p>Interest would be assessed as provided by law.</p></li></ul><p>The Tax Court entered the stipulated decision on August 6, 2019.</p><p>The IRS initially calculated interest of $2,246 without properly accounting for Tabaka&#8217;s earlier payments. After recognizing the payments, the IRS abated $614 of interest and made minor account adjustments. The remaining interest liability was $1,649, which Tabaka paid in December 2019.</p><p>Fast forward to June 2020. Tabaka files Form 843, asking for his $1,649 back. His pitch? The IRS dragged its feet and turned a simple tax issue into a marathon.</p><p>The IRS never bothered to send a formal denial. So Tabaka took his shot in Tax Court in October 2024.</p><h3>Statutory and Regulatory Framework</h3><p>Interest on an income tax deficiency generally begins accruing on the original due date of the return and continues until the liability is paid. Interest compounds daily. &#167;&#167;6151(a), 6601(a), and 6622(a).</p><p>Section 6404(e)(1) permits the IRS to abate interest attributable to an unreasonable error or delay by an IRS officer or employee in performing a <strong>ministerial or managerial act</strong>.</p><p>A ministerial act is a procedural or mechanical task that requires no judgment or discretion after all prerequisites have been completed. Treas. Reg. &#167;301.6404-2(b)(2).</p><p>A managerial act involves administrative matters such as personnel management or the temporary or permanent loss of records. Treas. Reg. &#167;301.6404-2(b)(1).</p><p>A decision involving the proper application of federal tax law is neither ministerial nor managerial.</p><p>An error or delay counts under &#167;6404(e) only when:</p><ul><li><p>No significant part of the error or delay is attributable to the taxpayer.</p></li><li><p>The error or delay occurs after the IRS first contacts the taxpayer in writing regarding the deficiency.</p></li></ul><p>Under &#167;6404(h)(1), the Tax Court reviews the IRS&#8217;s refusal to abate interest for abuse of discretion. The Court may order an abatement if the IRS relied on an erroneous interpretation of law or a clearly erroneous assessment of the evidence.</p><h3>Arguments</h3><p><strong>Taxpayer argued:</strong></p><ul><li><p>The IRS dragged things out way too long for what Tabaka saw as a simple 2016 tax issue.</p></li><li><p>The period between the 2017 return due date and the November 2019 interest notice was marked by multiple IRS errors and delays.</p></li><li><p>The IRS unnecessarily prolonged the case by moving it through Appeals and later referring it to IRS counsel for trial preparation.</p></li><li><p>The resulting $1,649 of interest should therefore be refunded under &#167;6404(e).</p></li></ul><p><strong>Government argued:</strong></p><ul><li><p>Interest accrued automatically because Tabaka had not paid the full 2016 tax liability by the return due date.</p></li><li><p>The IRS handled the examination and subsequent Tax Court proceeding within a reasonable period.</p></li><li><p>Referral of the docketed case to Appeals and then back to IRS counsel followed normal procedures.</p></li><li><p>Any time spent resolving the correct tax treatment of the Forms 1099-R involved substantive tax determinations rather than ministerial or managerial acts.</p></li><li><p>The IRS therefore had no statutory basis to abate the remaining interest.</p></li></ul><h3>Court&#8217;s Reasoning</h3><ul><li><p><strong>The relevant period began with the IRS&#8217;s first written contact.</strong> Section 6404(e) does not treat delays occurring before the IRS contacts the taxpayer in writing about the deficiency as grounds for abatement. The relevant starting date was therefore April 16, 2018, when the IRS issued the CP2000.</p></li><li><p><strong>The IRS moved the case forward without unreasonable inactivity.</strong> The IRS issued the notice of deficiency less than three months after the CP2000. Tabaka petitioned the Tax Court 93 days later. Appeals then received the docketed case, scheduled a conference, and attempted settlement.</p></li><li><p><strong>Returning the case to IRS counsel was not an improper delay.</strong> Appeals could not reach an agreement with Tabaka. Because the case was already pending in Tax Court, Appeals had to return it to IRS counsel for trial preparation. The Court rejected Tabaka&#8217;s characterization of that referral as unnecessary.</p></li><li><p><strong>The underlying dispute was resolved relatively quickly.</strong> The Tax Court scheduled a trial in June 2019, and the parties reached a settlement shortly afterward. The stipulated decision was entered on August 6, 2019. Less than 16 months elapsed between the first written contact from the IRS and the resolution of the deficiency proceeding.</p></li><li><p><strong>Elapsed time alone did not establish statutory delay.</strong> Citing <em>Lee v. Commissioner</em>, the Court emphasized that the ordinary passage of time during tax litigation does not by itself constitute an error or delay under &#167;6404(e). The Court characterized Tabaka&#8217;s case as having been resolved comparatively quickly.</p></li><li><p><strong>The challenged activity involved substantive tax determinations.</strong> The IRS had to determine the proper treatment of two Forms 1099-R reporting fully taxable retirement distributions. Resolving that issue required evaluating documentation and determining the taxpayer&#8217;s correct liability. Those functions required judgment and therefore were not ministerial or managerial acts.</p></li><li><p><strong>The IRS corrected the actual interest-computation error.</strong> The IRS initially failed to account for Tabaka&#8217;s prior payments when calculating interest. Once it identified that problem, it abated $614. Tabaka did not dispute the mathematical correctness of the remaining $1,649.</p></li></ul><h3>Jurisdiction</h3><p>The IRS never sent Tabaka a formal final determination denying his Form 843 claim.</p><p>That didn&#8217;t block the Tax Court from hearing the case.</p><p>Section 6404(h)(1)(A) provides two routes to Tax Court review. If the IRS issues a final determination, the taxpayer generally must petition within 180 days after the IRS mails it. If the IRS fails to issue a determination within 180 days after the taxpayer files an abatement claim, &#167;6404(h)(1)(A)(ii) permits the taxpayer to petition after that waiting period.</p><p>Tabaka filed his Form 843 on June 5, 2020, and did not petition until October 19, 2024. Because the IRS had never issued a formal final determination, he had satisfied the statutory waiting period.</p><p>The Court also noted that jurisdiction would exist even if the IRS&#8217;s July 9, 2024, letter were treated as a final determination because Tabaka filed his petition within 180 days of that letter.</p><p>This technicality didn&#8217;t change the outcome, but it&#8217;s a handy tip for anyone else stuck waiting on an IRS answer.</p><h3>Result</h3><p>Bottom line: the Tax Court sided with the IRS. Tabaka&#8217;s $1,649 interest bill stands.</p><h3>The Takeaway</h3><p>This case reinforces that &#167;6404(e) addresses specific administrative failures, <span>not just slow cases. If you want interest abated, you need to point to a specific clerical or management screw-up that actually cost you money. Routine audits, Appeals, and Court fights won&#8217;t cut it.</span></p><h3><span>List of Citations</span></h3><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://taxcoda.com/subscribe?&quot;,&quot;text&quot;:&quot;Upgrade&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">This post has bonus content for paid subscribers. Upgrade to get full access.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Upgrade"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p></p>]]></content:encoded></item><item><title><![CDATA[Court upholds tax deficiencies and penalties after attorney fails to contest unreported income]]></title><description><![CDATA[Jeffery Dieffenbach v. Commissioner. United States Tax Court. No. 940-24. 2026.]]></description><link>https://taxcoda.com/p/court-upholds-tax-deficiencies-and</link><guid isPermaLink="false">https://taxcoda.com/p/court-upholds-tax-deficiencies-and</guid><dc:creator><![CDATA[Tax Coda]]></dc:creator><pubDate>Mon, 17 Aug 2026 15:25:32 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!5cG2!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fab017102-2a2e-414e-9b4e-111a7d2ed1c6_500x500.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>If you argue the IRS audit was unfair but never actually dispute the numbers, you&#8217;re probably going to lose. That&#8217;s just how the system works.</p><h3>Holding</h3><p>The Tax Court <a href="https://www.taxnotes.com/research/federal/court-documents/court-opinions-and-orders/attorney-unreported-income-liable-deficiencies-penalties/7wk7t">sided</a> with the IRS on every front. Dieffenbach, a Connecticut attorney, got hit with tax bills, late-filing penalties, and accuracy penalties for five years straight. The IRS had the paperwork&#8212;W-2s, 1099s, Social Security statements. Dieffenbach had... nothing. No evidence, no counter-numbers, just arguments. The court wasn&#8217;t impressed.</p><h3>Why It Matters</h3><ul><li><p><strong><span>This is basic burden-of-proof territory.</span></strong><span>&nbsp;The IRS showed Dieffenbach got paid. After that, it was his job to prove the numbers were wrong. He didn&#8217;t.</span></p></li><li><p><strong><span>Procedural nitpicking is not a defense to owing tax.</span></strong><span>&nbsp;Dieffenbach spent his time arguing about the notice and whether the IRS ran two audits instead of one. None of that changed the fact that he never challenged the actual income numbers.</span></p></li><li><p><strong><span>As for the business expenses,</span></strong><span>&nbsp;Dieffenbach claimed a lot but proved nothing. He filed unsigned or amended returns with big Schedule C deductions, but didn&#8217;t back them up in court. The Tax Court gave him nothing.</span></p></li><li><p><strong><span>This case is a reminder:</span></strong><span>&nbsp;the Tax Court cares about evidence, not how the IRS ran the audit. If you want to win, bring receipts. Complaints about process won&#8217;t get you far.</span></p></li></ul><h3>Key Facts</h3><p>Jeffery Dieffenbach is a licensed attorney in Connecticut who also performed bookkeeping work.</p><p>The IRS examined his federal income tax liabilities for 2015 through 2019.</p><p>From 2015 through 2017, the IRS treated Dieffenbach as a nonfiler and prepared substitute returns under &#167;6020(b). Those returns relied on information reported by third parties.</p><p>Dieffenbach later submitted unsigned returns for 2015 through 2017 containing Schedule C deductions. The IRS did not accept those returns.</p><p>He filed a return for 2018 after the IRS examination began and timely filed his 2019 return. He later submitted amended returns for 2018 and 2019, but the IRS did not process them.</p><p>The IRS issued a notice of deficiency on October 24, 2023.</p><p>The notice determined the following deficiencies:</p><ul><li><p>2015: $7,620</p></li><li><p>2016: $19,499</p></li><li><p>2017: $12,212</p></li><li><p>2018: $16,124</p></li><li><p>2019: $16,948</p></li></ul><p>The notice also determined failure-to-file and failure-to-pay additions, an estimated tax addition for 2016, and accuracy-related penalties of $3,225 for 2018 and $3,390 for 2019.</p><p>Third-party information returns showed that Dieffenbach received income from several sources.</p><p>For 2015, he received:</p><ul><li><p>$3,927 of unemployment compensation from Rhode Island</p></li><li><p>$9,093 of wages from Network and Simulation Technologies</p></li><li><p>Social Security benefits</p></li><li><p>$14,610 of independent contractor income from Greenleaf Compassionate Care Center</p></li><li><p>$6,562 of independent contractor income from Malcom Company</p></li></ul><p>In later years, he received additional wages, Social Security benefits, and compensation as an independent contractor.</p><p>Greenleaf reported payments of $14,610, $24,855, $37,870, and $50,575 for 2015 through 2018, respectively.</p><p>Dieffenbach also claimed substantial Schedule C expenses. He reported approximately:</p><ul><li><p>$22,101 for 2015</p></li><li><p>$32,558 for 2016</p></li><li><p>$38,011 for 2017</p></li><li><p>$62,844 for 2018</p></li></ul><p>Those claimed expenses included advertising, vehicles and equipment, taxes and licenses, interest, office expenses, utilities, and self-employed health insurance.</p><p>He also claimed a $75,000 net operating loss carryforward deduction on his 2019 return.</p><h3>Statutory and Regulatory Framework</h3><p>Section 61 generally includes all income from whatever source derived in gross income.</p><p>The IRS is ordinarily presumed to have the amounts in a notice of deficiency correct. The taxpayer bears the burden of proving otherwise under Tax Court Rule 142(a).</p><p>For unreported income, however, the IRS must first establish an evidentiary connection between the taxpayer and the income. Third-party Forms W-2 and 1099 can satisfy that threshold requirement.</p><p>Section 6020(b) allows the IRS to prepare a substitute for return when a taxpayer fails to file.</p><p>Section 6651(a)(1) imposes an addition to tax for failing to file a required return on time unless the taxpayer establishes reasonable cause.</p><p>Section 6651(a)(2) imposes an addition for failing to pay tax shown on a return. A substitute for return prepared under &#167;6020(b) can constitute a return for purposes of that provision.</p><p>Section 6654 generally imposes an addition to tax when an individual fails to make required estimated tax payments.</p><p>Section 6662 imposes a 20% accuracy-related penalty on certain underpayments, including those attributable to negligence or a substantial understatement of income tax. A substantial understatement generally exists when the understatement exceeds the greater of 10% of the tax required to be shown or $5,000.</p><h3>Arguments</h3><p>Taxpayer argued:</p><ul><li><p>The notice of deficiency was invalid.</p></li><li><p>He had filed returns on time for 2015 through 2017.</p></li><li><p>The IRS improperly subjected him to multiple examinations.</p></li><li><p>The IRS&#8217;s actions were unconstitutional.</p></li><li><p>Res judicata barred the IRS from proceeding because it had previously filed a Tax Court case covering the same years.</p></li></ul><p>Government argued:</p><ul><li><p>Third-party information establishes Dieffenbach&#8217;s receipt of taxable income.</p></li><li><p>IRS records showed that he did not file valid returns for 2015 through 2017.</p></li><li><p>The examination remained a single examination even though a second revenue agent took over after the first agent retired.</p></li><li><p>The statutory period for assessing 2017 remained open because Dieffenbach executed Form 872, extending the period.</p></li><li><p>The earlier Tax Court proceeding did not create res judicata because the case was dismissed for lack of jurisdiction and no judgment on the merits was rendered.</p></li><li><p>Dieffenbach remained liable for the additions to tax and accuracy-related penalties because he failed to establish reasonable cause or otherwise rebut the IRS&#8217;s determinations.</p></li></ul><h3>Court&#8217;s Reasoning</h3><ul><li><p>The IRS established the required evidentiary connection to the unreported income through Forms W-2, Forms 1099, Forms SSA-1099, and Form 1099-G.</p></li><li><p>Once the IRS met that threshold burden, Dieffenbach had to show that the deficiency determinations were arbitrary or incorrect.</p></li><li><p>Dieffenbach did not offer testimony or other evidence disputing the income amounts. When the Court asked whether he had evidence addressing the deficiency determinations, he continued to argue only that the notice was invalid.</p></li><li><p>IRS records showed no valid returns for 2015 through 2017. Dieffenbach produced no persuasive evidence to overcome those records.</p></li><li><p>The limitation period for 2017 had not expired. Dieffenbach signed Form 872 extending the assessment deadline to December 31, 2023, and the IRS issued the notice on October 24, 2023.</p></li><li><p>The assignment of a second revenue agent after the first agent retired did not establish that the IRS conducted a prohibited second examination. Dieffenbach failed to prove that more than one examination occurred.</p></li><li><p>The prior Tax Court proceeding did not bar the case under res judicata because it was dismissed for lack of jurisdiction. The earlier case therefore produced no final judgment on the merits.</p></li><li><p>The Court found no substantial evidence of unconstitutional conduct by the IRS that would justify looking behind the notice of deficiency.</p></li><li><p>IRS account transcripts established that Dieffenbach failed to file timely returns for 2015 through 2018. He did not show reasonable cause, so the Court sustained the &#167;6651(a)(1) additions.</p></li><li><p>Certified substitutes for returns established the basis for the &#167;6651(a)(2) failure-to-pay additions for 2015 through 2017.</p></li><li><p>Dieffenbach filed no 2015 or 2016 return and made no required estimated payments for 2016, supporting the &#167;6654 addition.</p></li><li><p>The 2018 and 2019 understatements exceeded $5,000 and qualified as substantial understatements. Dieffenbach did not establish reasonable cause and good faith, so the Court sustained the &#167;6662 penalties.</p></li></ul><h3>Result</h3><p>The Tax Court sustained the IRS&#8217;s deficiency, addition-to-tax, and penalty determinations, with the final amounts to be calculated under Tax Court Rule 155.</p><h3>The Takeaway</h3><p>Here&#8217;s the real takeaway: you can complain about IRS procedures all day, but if you don&#8217;t actually dispute the numbers, you&#8217;re out of luck. The Tax Court wants evidence, not just arguments.</p><h3>List of Citations</h3><ul><li><p><strong>IRC &#167;61(a)</strong>: Defines gross income broadly as income from whatever source derived.</p></li><li><p><strong>IRC &#167;6020(b)</strong>: Authorizes the IRS to prepare substitutes for returns for nonfilers.</p></li><li><p><strong>IRC &#167;6651(a)(1)</strong>: Imposes the failure-to-file addition to tax.</p></li><li><p><strong>IRC &#167;6651(a)(2)</strong>: Imposes the failure-to-pay addition to tax.</p></li><li><p><strong>IRC &#167;6651(g)</strong>: Treats certain &#167;6020(b) substitutes for returns as returns for failure-to-pay purposes.</p></li><li><p><strong>IRC &#167;6654</strong>: Governs additions to tax for underpayment of estimated tax.</p></li><li><p><strong>IRC &#167;6662</strong>: Imposes the 20% accuracy-related penalty.</p></li><li><p><strong>IRC &#167;6664(c)(1)</strong>: Provides the reasonable-cause and good-faith exception to the accuracy-related penalty.</p></li><li><p><strong>IRC &#167;6751(b)(1)</strong>: Requires written supervisory approval for the initial determination of certain penalties.</p></li><li><p><strong>IRC &#167;7491(c)</strong>: Places the burden of production on the IRS for individual penalties and additions to tax.</p></li><li><p><strong>IRC &#167;7605(b)</strong>: Limits unnecessary examinations and multiple inspections of a taxpayer&#8217;s books.</p></li><li><p><strong>Welch v. Helvering, 290 U.S. 111 (1933)</strong>: Establishes the general presumption of correctness for deficiency determinations.</p></li><li><p><strong>INDOPCO, Inc. v. Commissioner, 503 U.S. 79 (1992)</strong>: Confirms that taxpayers must establish entitlement to deductions.</p></li><li><p><strong>New Colonial Ice Co. v. Helvering, 292 U.S. 435 (1934)</strong>: Treats deductions as matters of legislative grace.</p></li><li><p><strong>Weimerskirch v. Commissioner, 596 F.2d 358 (9th Cir. 1979)</strong>: Requires an evidentiary foundation connecting a taxpayer to alleged unreported income.</p></li><li><p><strong>Petzoldt v. Commissioner, 92 T.C. 661 (1989)</strong>: Applies the evidentiary foundation requirement in unreported-income cases.</p></li><li><p><strong>Silver v. Commissioner, T.C. Memo. 2021-98</strong>: Recognizes third-party information returns as sufficient evidence of income.</p></li><li><p><strong>Walquist v. Commissioner, 152 T.C. 61 (2019)</strong>: Explains the taxpayer&#8217;s burden after the IRS establishes receipt of unreported income.</p></li><li><p><strong>Greenberg&#8217;s Express, Inc. v. Commissioner, 62 T.C. 324 (1974)</strong>: Limits Tax Court review of the IRS&#8217;s administrative examination process.</p></li><li><p><strong>United States v. Powell, 379 U.S. 48 (1964)</strong>: Interprets &#167;7605(b) as imposing no severe restriction on IRS investigative authority.</p></li><li><p><strong>Hough v. Commissioner, 882 F.2d 1271 (7th Cir. 1989)</strong>: Addresses claims involving prohibited second examinations.</p></li><li><p><strong>Estate of Sower v. Commissioner, 149 T.C. 279 (2017)</strong>: Addresses the taxpayer&#8217;s burden to establish an improper second examination.</p></li><li><p><strong>Federated Department Stores, Inc. v. Moitie, 452 U.S. 394 (1981)</strong>: States principles governing res judicata.</p></li><li><p><strong>Monge v. Commissioner, 93 T.C. 22 (1989)</strong>: Addresses jurisdiction and the effect of a prior Tax Court dismissal.</p></li><li><p><strong>Higbee v. Commissioner, 116 T.C. 438 (2001)</strong>: Explains the IRS&#8217;s burden of production for penalties.</p></li><li><p><strong>Wheeler v. Commissioner, 127 T.C. 200 (2006), aff&#8217;d, 521 F.3d 1289 (10th Cir. 2008)</strong>: Addresses the IRS&#8217;s evidentiary burden for failure-to-pay and estimated-tax additions.</p></li><li><p><strong>Dieffenbach v. Commissioner, No. 3921-22 (T.C. May 4, 2023)</strong>: Earlier proceeding dismissed for lack of jurisdiction and therefore not a judgment on the merits.</p></li></ul>]]></content:encoded></item><item><title><![CDATA[FinCEN finalizes narrower BOI reporting rules for foreign companies]]></title><description><![CDATA[31 CFR Part 1010. RIN 1506-AB67]]></description><link>https://taxcoda.com/p/fincen-finalizes-narrower-boi-reporting</link><guid isPermaLink="false">https://taxcoda.com/p/fincen-finalizes-narrower-boi-reporting</guid><dc:creator><![CDATA[Tax Coda]]></dc:creator><pubDate>Thu, 13 Aug 2026 17:36:00 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!5cG2!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fab017102-2a2e-414e-9b4e-111a7d2ed1c6_500x500.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>FinCEN&#8217;s final rule makes the 2025 rollback of Corporate Transparency Act reporting permanent. U.S.-formed entities are still exempt from BOI reporting, U.S. persons generally no longer have BOI reporting duties, and only certain foreign entities registered to do business in the United States are still covered.</p><h3>Tell Me More</h3><p><span>FinCEN is&nbsp;</span><a href="https://www.fincen.gov/system/files/2026-08/BOIFinalRuleforFR.pdf"><span>making</span></a><span>&nbsp;its March 26, 2025 interim final rule permanent and adding more relief for U.S. persons. Domestic entities are no longer considered reporting companies. Foreign reporting companies do not need to report beneficial ownership information for U.S. person beneficial owners or company applicants. U.S. persons also do not have to update or correct information linked to their FinCEN identifiers.</span></p><p>The rule takes effect once it is published in the Federal Register. FinCEN has submitted the rule for publication and notes that the Federal Register version will be the official one.</p><h3>Why It Matters</h3><ul><li><p><strong>The CTA reporting regime is now overwhelmingly a foreign-entity reporting regime.</strong> Corporations, LLCs, and similar entities created under U.S. state or tribal law remain exempt from BOI reporting even if they previously would have qualified as domestic reporting companies.</p></li><li><p><strong><span>U.S. persons now get more relief than they did under the March 2025 interim rule.</span></strong><span>&nbsp;Foreign reporting companies already did not have to report U.S. person beneficial owners, and now the exemption also covers U.S. person company applicants.</span></p></li><li><p><strong><span>Current U.S. FinCEN ID holders no longer need to keep updating their information.</span></strong><span>&nbsp;FinCEN estimates that about 760,000 U.S. persons have FinCEN IDs and will no longer have to update or correct their details.</span></p></li><li><p><strong><span>Foreign reporting companies still have compliance requirements.</span></strong><span>&nbsp;A foreign entity formed under foreign law and registered to do business in a U.S. state or tribal area generally must still report BOI unless another exemption applies.</span></p></li><li><p><strong><span>The final rule does not remove customer due diligence requirements for financial institutions.</span></strong><span>&nbsp;FinCEN makes it clear that the CTA Reporting Rule is separate from the Customer Due Diligence Rule, and financial institutions must still follow the latter while FinCEN reviews possible changes.</span></p></li><li><p><strong><span>FinCEN plans to delete much of the U.S. person information already in its BOI database.</span></strong><span>&nbsp;The agency expects to do a one-time removal of information that would not have been required under the final rule.</span></p></li></ul><h3>Key Facts</h3><p>Congress enacted the Corporate Transparency Act in 2021 as part of the Anti-Money Laundering Act of 2020. The CTA added &#167;5336 to the Bank Secrecy Act and directed Treasury to create a federal beneficial ownership reporting system.</p><p>FinCEN&#8217;s original 2022 Reporting Rule generally required both domestic and foreign reporting companies to provide identifying information about themselves and their beneficial owners. Companies created or registered after January 1, 2024 also had to report certain company applicants.</p><p>Litigation disrupted implementation during late 2024 and early 2025. Treasury then announced on March 2, 2025, that it would stop enforcing CTA reporting requirements on U.S. citizens and domestic reporting companies and would narrow the rule to apply only to foreign companies.</p><p>FinCEN implemented that policy through an interim final rule effective March 26, 2025. The interim rule:</p><ul><li><p>removed domestic entities from the definition of reporting company;</p></li><li><p>exempted U.S. person beneficial owners from BOI reporting;</p></li><li><p>retained reporting for foreign entities registered to do business in the United States;</p></li><li><p>required those foreign reporting companies to report only non-U.S. beneficial owners; and</p></li><li><p>retained a 30-day filing framework for covered foreign companies.</p></li></ul><p>FinCEN received 118 comment letters on the interim rule. Forty clearly supported the narrowed reporting regime, 28 strongly opposed it, and 50 did not clearly support or oppose it.</p><p>The final rule retains the basic framework but provides two additional forms of relief for U.S. persons.</p><p>First, foreign reporting companies no longer have to identify applicants as U.S. persons. The interim rule had exempted U.S. beneficial owners but not necessarily U.S. company applicants.</p><p>Second, U.S. persons who obtained FinCEN identifiers no longer have to update or correct the identifying information associated with those identifiers.</p><h3>Statutory Framework</h3><p>The CTA generally requires reporting companies to provide BOI to FinCEN but gives Treasury substantial exemption authority.</p><p>Under 31 U.S.C. &#167;5336(a)(11)(B)(xxiv), Treasury may exempt an entity or class of entities when the Secretary, with written concurrence from the Attorney General and Secretary of Homeland Security, determines that requiring BOI would not serve the public interest and would not be highly useful for national security, intelligence, or law enforcement purposes.</p><p>Treasury also relies on 31 U.S.C. &#167;5318(a)(7), which authorizes appropriate exemptions from Bank Secrecy Act requirements.</p><p>The final rule modifies 31 CFR &#167;1010.380, FinCEN&#8217;s CTA reporting regulation.</p><h3>What the Final Rule Changes</h3><h4>Domestic entities remain exempt</h4><p>The most consequential provision remains unchanged from the interim rule.</p><p>Entities created under U.S. state or tribal law are excluded from the operative definition of reporting company. FinCEN therefore does not require the millions of corporations, LLCs, and similar domestic entities that originally fell within the CTA Reporting Rule to submit BOI reports.</p><p>FinCEN rejected requests to replace the broad exemption with narrower exemptions based on factors such as company size, ownership, nonprofit status, foreign ownership, or shell-company characteristics.</p><p>Treasury concluded that the blanket domestic exemption better satisfied what it views as the CTA&#8217;s required balancing of useful information against private compliance costs.</p><h4>Foreign reporting companies remain covered</h4><p>A reporting company now effectively means an entity that:</p><ul><li><p>is formed under the law of a foreign country; and</p></li><li><p>registers to do business in a U.S. state or tribal jurisdiction by filing a document with a secretary of state or similar office.</p></li></ul><p>Existing statutory and regulatory exemptions continue to apply.</p><p>FinCEN estimates approximately 28,000 foreign entities may ultimately qualify as nonexempt reporting companies. About 13,000 had already filed reports by the end of 2025, leaving an estimated 15,000 existing foreign companies still expected to report. FinCEN expects roughly 1,800 additional foreign reporting companies each year.</p><h4>U.S. beneficial owners remain exempt</h4><p>Foreign reporting companies do not have to report BOI for beneficial owners who are U.S. persons.</p><p>A foreign reporting company owned entirely by U.S. persons can therefore still have a filing obligation even though its report contains no beneficial owner information.</p><p>The final rule relocates this exemption within &#167;1010.380 but does not materially reverse the exemption adopted in 2025.</p><h4>U.S. company applicants are now exempt</h4><p>This is one of the principal changes to the final rule from the interim rule.</p><p>A company applicant generally includes the person who files the document registering the entity and, when applicable, the person primarily responsible for directing that filing.</p><p>Under the interim rule, a foreign company registered in the United States on or after January 1, 2024 could still have been required to report a U.S. person company applicant.</p><p>The final rule eliminates that requirement.</p><p>Reporting companies are exempt from reporting BOI for any U.S. person who is either:</p><ul><li><p>a beneficial owner; or</p></li><li><p>a company applicant.</p></li></ul><p>U.S. persons are correspondingly exempt from having to provide that information to the reporting company.</p><h4>U.S. FinCEN ID holders no longer have to update information</h4><p>The original rules required a person who obtained a FinCEN identifier to update or correct the underlying personal information when it changed.</p><p>That produced an odd result after the 2025 exemptions. A U.S. person could have no remaining BOI reporting obligation but still face a continuing obligation to maintain information associated with an old FinCEN ID.</p><p>The final rule eliminates that requirement for U.S. persons.</p><p>Only individuals who are not U.S. persons remain subject to the FinCEN ID update and correction requirement in revised 31 CFR &#167;1010.380(b)(4)(iii)(A).</p><p>For non-U.S. persons, changes generally must be reported within 30 calendar days.</p><h3>Filing Deadlines</h3><p>FinCEN did not change the 30-day filing framework established under the interim rule.</p><p>A newly covered foreign reporting company generally must file its initial BOI report within 30 days after the earlier of:</p><ul><li><p>receiving actual notice that it has been registered to do business in the United States; or</p></li><li><p>the relevant state or tribal office first providing public notice of the registration.</p></li></ul><p>Covered reporting companies generally must also update or correct required information within 30 days after the relevant change or discovery of an error.</p><p>FinCEN rejected requests to extend the general filing period to 90 days.</p><h3>Previously Reported U.S. BOI</h3><p>The final rule addresses a major practical issue left unresolved by the interim rule: what FinCEN intends to do with information already submitted by U.S. companies and U.S. individuals.</p><p>Millions of domestic entities filed BOI reports before Treasury changed course.</p><p>FinCEN now states that privacy, information security, and public trust support removing, as practicable, information that would not have been required if the final rule had been in effect as of January 1, 2024.</p><p>FinCEN anticipates working with the National Archives and Records Administration to conduct a one-time deletion project.</p><p>The agency expects to identify domestic companies and U.S. persons using information already contained in BOI filings, including identification documents such as U.S. passports and U.S. driver&#8217;s licenses.</p><p>FinCEN does not expect U.S. companies or individuals to submit deletion requests.</p><p>It also does not plan to issue individual confirmations when records are deleted. FinCEN instead intends to announce publicly on its website once the deletion process is complete.</p><p>The contemplated deletion process has an important limitation. FinCEN says that if U.S. person information is submitted after a date 180 days following publication of the final rule, whether intentionally or inadvertently, the agency does not anticipate conducting additional periodic sweeps to delete it.</p><h3>Customer Due Diligence Remains Separate</h3><p>The final rule does not eliminate the collection of beneficial ownership information by banks and other covered financial institutions.</p><p>FinCEN emphasizes that the CTA Reporting Rule and its Customer Due Diligence Rule serve different purposes and derive from different legal authorities.</p><p>Covered financial institutions may therefore still be required to collect beneficial ownership information from legal-entity customers, even if the same domestic business has no obligation to file a CTA BOI report with FinCEN.</p><p>FinCEN acknowledges that this creates questions about how the two regimes interact.</p><p>The agency says it remains legally required to revise the CDD Rule and intends to return its attention to that rule now that the BOI Reporting Rule revisions have been completed.</p><h3>Enforcement</h3><p>The final rule does not amend the CTA&#8217;s existing reporting violation provisions.</p><p>Civil and criminal liability <span>may be available for&nbsp;willful&nbsp;violations by persons and entities&nbsp;</span>subject to reporting requirements.</p><p>FinCEN states that inadvertent mistakes and simple lack of awareness should not form the basis for enforcement because the statute requires willfulness.</p><p>That distinction matters primarily for foreign reporting companies and non-U.S. persons, as domestic companies and U.S. persons have largely been removed from the reporting regime.</p><h3>Regulatory Impact</h3><p>FinCEN treats the rule as a major deregulatory action.</p><p>The agency estimates that approximately 27.5 million domestic reporting companies were relieved of filing obligations through the 2025 interim rule.</p><p>Using the assumptions from its original Reporting Rule, FinCEN estimates that the rollback has eliminated approximately:</p><ul><li><p><strong>53 million reporting burden hours per year</strong>, on average; and</p></li><li><p><strong>$9 billion in reporting costs per year</strong>, on average.</p></li></ul><p>FinCEN estimates roughly $18 billion in aggregate reporting cost savings for entities relieved from reporting since the interim rule took effect.</p><p>The additional changes made by this final rule produce much smaller incremental savings because the major deregulation already occurred in March 2025.</p><p>FinCEN estimates that eliminating U.S. FinCEN ID updates and U.S. company applicant reporting will save approximately:</p><ul><li><p>$233,439 during the first year; and</p></li><li><p>$209,105 annually thereafter.</p></li></ul><p>The table on page 50 summarizes the regulatory changes. It identifies three affected groups: reporting companies, U.S. persons generally, and U.S. persons holding FinCEN IDs. The rule eliminates reporting of U.S. beneficial owners and company applicants and removes ongoing FinCEN ID updates for U.S. persons.</p><p>FinCEN permanently adopts the 2025 narrowing of the Corporate Transparency Act reporting regime and expands it by eliminating BOI reporting for U.S. company applicants and ongoing FinCEN ID update requirements for U.S. persons.</p><h3>The Takeaway</h3><p>For most U.S.-formed businesses, CTA beneficial ownership reporting is now essentially finished under FinCEN&#8217;s current rule. Practitioners should focus BOI compliance efforts on foreign-organized entities registered to do business in the United States, and remember that financial institution customer due diligence requirements remain separate.</p><h3>List of Citations</h3><ul><li><p><strong>31 U.S.C. &#167;5336</strong>: Corporate Transparency Act beneficial ownership reporting requirements and Treasury exemption authority.</p></li><li><p><strong>31 U.S.C. &#167;5336(a)(11)(B)(xxiv)</strong>: Authorizes Treasury to exempt additional entities or classes of entities from the definition of reporting company.</p></li><li><p><strong>31 U.S.C. &#167;5336(b)(4)(A)</strong>: Authorizes Treasury to establish procedures and standards governing FinCEN identifiers.</p></li><li><p><strong>31 U.S.C. &#167;5336(h)</strong>: Establishes civil and criminal consequences for willful BOI reporting violations.</p></li><li><p><strong>31 U.S.C. &#167;5318(a)(7)</strong>: Provides Treasury authority to grant appropriate exemptions from Bank Secrecy Act requirements.</p></li><li><p><strong>31 CFR &#167;1010.380</strong>: FinCEN regulation implementing CTA beneficial ownership reporting requirements.</p></li><li><p><strong>90 FR 13688 (March 26, 2025)</strong>: Interim final rule that initially narrowed CTA reporting primarily to foreign reporting companies.</p></li><li><p><strong>Loper Bright Enterprises v. Raimondo, 603 U.S. 369 (2024)</strong>: Cited by commenters challenging whether Treasury&#8217;s broad domestic-company exemption is consistent with the CTA.</p></li><li><p><strong>McHenry v. Texas Top Cop Shop, Inc., 145 S. Ct. 1 (2025)</strong>: Supreme Court order staying a nationwide preliminary injunction involving CTA enforcement.</p></li><li><p><strong>Texas Top Cop Shop, Inc. v. Garland, 758 F. Supp. 3d 607 (E.D. Tex. 2024)</strong>: CTA litigation that disrupted implementation of FinCEN&#8217;s original reporting deadlines.</p></li><li><p><strong>Smith v. U.S. Department of the Treasury, 761 F. Supp. 3d 952 (E.D. Tex. 2025)</strong>: Additional litigation affecting implementation of the CTA Reporting Rule.</p></li><li><p><strong>National Small Business United v. U.S. Department of the Treasury, 161 F.4th 1323 (11th Cir. 2025)</strong>: Appellate CTA litigation referenced in FinCEN&#8217;s procedural history.</p></li><li><p><strong>Flowers Title Co. v. Bessent, No. 6:25-CV-127-JDK, 2026 WL 782283 (E.D. Tex. Mar. 19, 2026)</strong>: Decision cited by FinCEN concerning the separate Real Estate Reporting Rule.</p></li></ul>]]></content:encoded></item><item><title><![CDATA[Court denies couple’s charitable deduction for lack of substantiation]]></title><description><![CDATA[Ehimwenma E. Aimiuwu v. Commissioner. United States Tax Court. No. 5576-24S. 2026 TC Memo.]]></description><link>https://taxcoda.com/p/court-denies-couples-charitable-deduction</link><guid isPermaLink="false">https://taxcoda.com/p/court-denies-couples-charitable-deduction</guid><dc:creator><![CDATA[Tax Coda]]></dc:creator><pubDate>Wed, 12 Aug 2026 17:17:30 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!5cG2!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fab017102-2a2e-414e-9b4e-111a7d2ed1c6_500x500.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>Taxpayers are not allowed to claim expenses that belong to someone else. To deduct a charitable contribution, they must show proof of both the payment and that the recipient qualifies under &#167;170.</p><h3>Holding</h3><p>The Tax Court rejected the Schedule C deductions related to the taxpayers&#8217; corporation and denied the $49,986 charitable contribution deduction. The couple did not provide the necessary written proof or show that the recipient met &#167;170(c) requirements.</p><h3>Why It Matters</h3><ul><li><p>This decision follows established law. A corporation and its shareholders are separate taxpayers, so shareholders usually cannot deduct corporate expenses on their own tax returns.</p></li><li><p>The charitable contribution issue turned on substantiation, not merely on where the deduction appeared on the return. Moving an expense from Schedule C to Schedule A does not fix the problem if the &#167;170 documentation requirements are not met.</p></li><li><p>This opinion is a small tax case under &#167;7463 and cannot be used as precedent.</p></li></ul><h3>Key Facts</h3><p>Ehimwenma E. Aimiuwu and Kehinde F. Aimiuwu filed a joint 2021 federal income tax return.</p><p>Ehimwenma Aimiuwu owned Edofolks, Inc., a Georgia corporation that sold books. The corporation reported no income for the year.</p><p>The couple claimed a $79,136 Schedule C loss on their individual return&#8212;most of the expenses related to Edofolks rather than to a separate business conducted personally by the taxpayers.</p><p>The Schedule C also included a $49,986 expense labeled &#8220;Donation.&#8221; The couple said the payment went to an organization identified as Aimiuwu.com. Inc.</p><p>The taxpayers attributed the reporting errors to their paid return preparer, who allegedly advised them to deduct the corporation&#8217;s expenses personally because the corporation had no income.</p><p>By trial, the taxpayers conceded that the corporate expenses did not belong on their individual return. They continued to claim that the $49,986 payment should instead qualify as an itemized charitable contribution deduction on Schedule A.</p><p>They produced no canceled check, contribution receipt, acknowledgment from the recipient, or other written record supporting the payment. They also produced no evidence showing that Aimiuwu.com Inc. qualified as an eligible charitable organization.</p><h3>Statutory and Regulatory Framework</h3><p>A corporation ordinarily constitutes a taxpayer separate from its shareholders. One taxpayer generally cannot deduct expenses paid or incurred by another taxpayer.</p><p>Section 170 allows a deduction for qualifying charitable contributions. For cash contributions, &#167;170(f)(17) requires a bank record, written communication from the charitable organization, or another qualifying written record showing the recipient, date, and amount of the contribution.</p><p>The taxpayer must also establish that the recipient qualifies under &#167;170(c), which defines the organizations and entities eligible to receive deductible charitable contributions.</p><h3>Arguments</h3><p>Taxpayer argued:</p><ul><li><p>The return preparer incorrectly placed corporate expenses on the couple&#8217;s Schedule C.</p></li><li><p>The $49,986 donation should have appeared on Schedule A rather than Schedule C.</p></li><li><p>The payment therefore remained deductible despite the original reporting error.</p></li></ul><p>Government argued:</p><ul><li><p>The expenses associated with Edofolks were the corporation's and could not be deducted by its shareholders.</p></li><li><p>The taxpayers failed to provide the documentation required to substantiate the alleged charitable contribution.</p></li><li><p>The taxpayers also failed to establish that the recipient qualified under &#167;170(c).</p></li></ul><h3>Court&#8217;s Reasoning</h3><ul><li><p>Edofolks, Inc. existed as a separate corporate taxpayer from the Aimiuwus.</p></li><li><p>The taxpayers conceded that nearly all expenses claimed on Schedule C belonged to Edofolks.</p></li><li><p>Longstanding federal tax principles prevent shareholders from deducting expenses attributable to their corporation.</p></li><li><p>Moving the $49,986 donation from Schedule C to Schedule A would not establish entitlement to the deduction.</p></li><li><p>Section 170 requires written substantiation for cash contributions.</p></li><li><p>The taxpayers offered only testimony regarding the alleged payment and produced no required written evidence.</p></li><li><p>They also failed to establish that Aimiuwu.com Inc. qualified as an eligible recipient under &#167;170(c).</p></li></ul><h3>Result</h3><p>The Tax Court sustained the IRS&#8217;s disallowance of the corporate expenses and the $49,986 charitable contribution deduction, with the final deficiency to be computed under Rule 155.</p><h3>The Takeaway</h3><p>This decision does not change the law, but it highlights two key rules: corporate expenses must stay with the corporation, and charitable deductions need documentation showing both the payment and the recipient&#8217;s eligibility.</p><h3>List of Citations</h3><ul><li><p><strong>IRC &#167;170</strong>: Allows deductions for qualifying charitable contributions.</p></li><li><p><strong>IRC &#167;170(c)</strong>: Defines organizations and recipients eligible to receive deductible charitable contributions.</p></li><li><p><strong>IRC &#167;170(f)(17)</strong>: Establishes substantiation requirements for cash contributions.</p></li><li><p><strong>IRC &#167;7463</strong>: Governs small tax cases and provides that the resulting opinion is nonprecedential and generally not appealable.</p></li><li><p><strong>Moline Properties, Inc. v. Commissioner, 319 U.S. 436 (1943)</strong>: Establishes that a corporation generally remains a taxpayer separate from its shareholders.</p></li><li><p><strong>Deputy v. du Pont, 308 U.S. 488 (1940)</strong>: Supports the principle that a taxpayer generally may deduct only that taxpayer&#8217;s own expenses.</p></li><li><p><strong>Columbian Rope Co. v. Commissioner, 42 T.C. 800 (1964)</strong>: Applies the separate-taxpayer principle to deductions claimed by different taxpayers.</p></li></ul>]]></content:encoded></item><item><title><![CDATA[Tax Court upholds fraud penalties after business owner disguises personal expenses as corporate costs]]></title><description><![CDATA[Walter Prezioso v. Commissioner. United States Tax Court. Memo. 2026-63, No. 1727-24.]]></description><link>https://taxcoda.com/p/tax-court-upholds-fraud-penalties</link><guid isPermaLink="false">https://taxcoda.com/p/tax-court-upholds-fraud-penalties</guid><dc:creator><![CDATA[Adam Parr]]></dc:creator><pubDate>Thu, 06 Aug 2026 16:27:03 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!5cG2!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fab017102-2a2e-414e-9b4e-111a7d2ed1c6_500x500.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>If a business owner uses company funds to pay personal expenses and tries to hide them as business costs, they can face civil fraud penalties when there is clear evidence of intentional concealment instead of just sloppy bookkeeping.</p><h3>Holding</h3><p>The Tax Court upheld &#167;6663 civil fraud penalties for 2009 through 2012 after finding strong evidence that he intentionally hid taxable income by having his company pay his personal expenses and recording them as business costs.</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://taxcoda.com/subscribe?coupon=e729ad49&amp;utm_content=209586640&quot;,&quot;text&quot;:&quot;Get 40% off forever&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://taxcoda.com/subscribe?coupon=e729ad49&amp;utm_content=209586640"><span>Get 40% off forever</span></a></p><h3>Why It Matters</h3><ul><li><p>The decision uses established fraud rules and is based on a strong record of concealment. The court looked at several signs of fraud, not just one bookkeeping mistake.</p></li><li><p>Having two sets of accounting records can be seen as evidence of fraud, even if one set was supposedly made for a reason unrelated to taxes.</p></li><li><p>A taxpayer cannot avoid responsibility by blaming their tax preparer if they provided records that wrongly list personal expenses as business expenses.</p></li><li><p>The ruling makes clear the difference between careless bookkeeping and intentional hiding of information. The court decided that repeatedly changing records, using fake payee names, leaving out payments, and not reporting personal benefits did not look like honest mistakes.</p></li></ul><h3>Key Facts</h3><p>Walter Prezioso owned 25% of GSP Precision, Inc., a California aerospace manufacturing company, and became its chief executive officer in 2007.</p><p>GSP began paying some of Prezioso&#8217;s personal expenses in 2007. Corporate minutes authorized several categories of personal expenditures, including leased vehicles, insurance, medical coverage, life insurance, and certain credit card expenses.</p><p>The company paid substantially more than those expressly identified expenses. Payments included:</p><ul><li><p>Personal credit cards.</p></li><li><p>Home renovations.</p></li><li><p>A home-equity line of credit.</p></li><li><p>Landscaping.</p></li><li><p>Tennis Court and pool contractors.</p></li><li><p>Home audio and visual equipment.</p></li><li><p>Boat and recreational vehicle loans.</p></li><li><p>Vehicle leases.</p></li></ul><p>GSP issued more than 400 checks for Prezioso&#8217;s personal expenses during the years at issue.</p><p>Prezioso remained on GSP&#8217;s payroll and received a regular salary. GSP did not report the additional personal expenses on Forms W-2 or Forms 1099 issued to him.</p><p>Prezioso nevertheless understood that the payments increased his economic compensation. On an application for a Ferrari lease, he reported $52,950 of &#8220;Verifiable&#8221; W-2 income and $275,000 of &#8220;Actual&#8221; income.</p><p>Prezioso handled much of GSP&#8217;s bookkeeping. The company maintained two sets of charts of accounts.</p><p>The internal charts were available for shareholder review. Those records often replaced the true payees of Prezioso&#8217;s personal expenses with names of legitimate GSP vendors.</p><p>The accountant charts were provided to GSP&#8217;s outside accountant. Prezioso generally restored the correct payee names before generating those records, but personal expenses still carried business expense codes such as equipment repair, material purchases, and outside processing.</p><p>Those codes flowed into GSP&#8217;s financial statements and tax reporting. At least some of the personal expenses were ultimately included in cost of goods sold.</p><p>Prezioso and his wife filed joint individual income tax returns for 2009 through 2013. They reported his W-2 wages but did not report income arising from GSP&#8217;s payment of personal expenses.</p><p>The IRS determined deficiencies and fraud penalties for 2009 through 2013.</p><p>The Preziosos conceded all underlying deficiencies and conceded the fraud penalty for 2013. The only remaining dispute involved the &#167;6663 fraud penalties for 2009 through 2012.</p><h3>Statutory and Regulatory Framework</h3><p>Section 6663(a) imposes a penalty equal to 75% of the portion of an underpayment attributable to fraud.</p><p>The IRS must prove fraud by clear and convincing evidence under &#167;7454(a) and Tax Court Rule 142(b).</p><p>For each year, the IRS must establish:</p><ul><li><p>An underpayment of tax.</p></li><li><p>Fraudulent intent with respect to at least part of that underpayment.</p></li></ul><p>Fraud means intentional wrongdoing designed to evade tax the taxpayer knows or believes is due.</p><p>Because direct evidence of intent is uncommon, courts evaluate circumstantial evidence commonly called badges of fraud. Relevant indicators include consistently understated income, concealed income or assets, misleading books and records, false information supplied to tax preparers, implausible explanations, and false tax returns.</p><p>A corporation&#8217;s payment of a shareholder&#8217;s personal expenses generally creates taxable income to that shareholder, depending on the circumstances, as compensation or a constructive distribution.</p><h3>Arguments</h3><p>Taxpayer argued:</p><ul><li><p>The company legitimately paid certain personal expenses as part of Prezioso&#8217;s compensation arrangement.</p></li><li><p>Prezioso supplied substantially accurate accounting information to GSP&#8217;s outside accountant.</p></li><li><p>The company&#8217;s outside accountant knew about or approved the bookkeeping treatment.</p></li><li><p>The internal accounting records concealed personal expenses from employees rather than from the IRS or the company&#8217;s accountant.</p></li><li><p>Prezioso did not understand at the time that GSP&#8217;s payment of his personal expenses created taxable income.</p></li><li><p>Any understatements resulted from mistake rather than fraudulent intent.</p></li></ul><p>Government argued:</p><ul><li><p>Prezioso deliberately maintained misleading accounting records.</p></li><li><p>He substituted legitimate vendor names for the true payees of personal expenditures.</p></li><li><p>He classified personal expenses under business expense codes.</p></li><li><p>Those classifications resulted in the payments being treated as corporate costs rather than compensation.</p></li><li><p>Prezioso supplied incomplete or misleading information to the tax preparer.</p></li><li><p>The repeated concealment, understatement of income, and double bookkeeping established fraudulent intent.</p></li></ul><h3>Court&#8217;s Reasoning</h3><ul><li><p>The Court rejected Prezioso&#8217;s explanation that the company&#8217;s accountant authorized the bookkeeping system. The record contained no documents showing that the accountant knew personal expenses were being coded as ordinary business expenses.</p></li><li><p>The available expense codes included specific categories for officer compensation, shareholder draws, and shareholder loans. The Court found it implausible that the accountant would instead instruct Prezioso to record home improvements, landscaping, personal credit card charges, and similar expenditures as material purchases or equipment repairs.</p></li><li><p>The Court did not believe Prezioso created the misleading internal records merely to prevent employees from seeing his compensation. Prezioso repeatedly changed actual payees to legitimate company vendors and sometimes omitted direct payments entirely.</p></li><li><p>The Court viewed the internal records as evidence that Prezioso sought to conceal both the frequency and the amount of personal expenditures from other shareholders.</p></li><li><p>The existence of two sets of books supported a fraudulent intent, even if the misleading records originally served a non-tax purpose. The Court relied on prior cases treating double bookkeeping and falsified financial records as circumstantial evidence of fraud.</p></li><li><p>The accountant charts did not cure the problem. Personal expenses continued to be recorded under misleading business expense codes, causing them to flow through the company&#8217;s books as ordinary corporate expenses.</p></li><li><p>The Court found that Prezioso gave his return preparer incomplete or misleading information. Nothing in the accounting records clearly identified the personal expenditures as compensation or shareholder benefits.</p></li><li><p>The consistent understatement of income also supported the finding of fraud. Prezioso failed to report substantial economic benefits, even though his Ferrari lease application showed he understood that his actual income substantially exceeded his reported W-2 wages.</p></li><li><p>The Court rejected Prezioso&#8217;s claim that he did not know the payments constituted taxable income. His bookkeeping practices, failure to question the company&#8217;s recurring losses, and substantial difference between reported and actual income supported an inference of willful blindness at minimum.</p></li><li><p>Taken together, the double bookkeeping, concealment, implausible explanations, inaccurate expense classifications, and repeated understatement of income satisfied the IRS&#8217;s clear and convincing evidence burden for each year from 2009 through 2012.</p></li></ul><h3>Result</h3><p>The Tax Court sustained the &#167;6663 fraud penalties for 2009 through 2012, with the final deficiency and penalty amounts to be computed under Rule 155.</p><h3>The Takeaway</h3><p>This case is important for closely held businesses where owners use company accounts to pay personal expenses. While there can be debates about how to treat certain payments for tax purposes, intentionally hiding personal expenses as business costs can turn a simple tax adjustment into a 75% fraud penalty.</p><h3>List of Citations</h3><ul><li><p><strong>IRC &#167;6663(a)</strong>: Imposes the 75% civil fraud penalty on the portion of an underpayment attributable to fraud.</p></li><li><p><strong>IRC &#167;7454(a)</strong>: Places the burden of proving fraud on the IRS.</p></li><li><p><strong>IRC &#167;7491(c)</strong>: Establishes the IRS&#8217;s burden of production for penalties imposed on individuals.</p></li><li><p><strong>IRC &#167;6751(b)</strong>: Requires written supervisory approval for certain penalties.</p></li><li><p><strong>IRC &#167;6013(d)(3)</strong>: Makes spouses filing jointly jointly and severally liable for the tax due on the joint return.</p></li><li><p><strong>Neely v. Commissioner, 116 T.C. 79 (2001)</strong>: Defines fraud as intentional wrongdoing designed to evade tax believed to be owing.</p></li><li><p><strong>Petzoldt v. Commissioner, 92 T.C. 661 (1989)</strong>: Explains that fraud cannot rest on suspicion and may be proven through circumstantial evidence.</p></li><li><p><strong>Parks v. Commissioner, 94 T.C. 654 (1990)</strong>: Addresses concealment and misleading conduct as evidence of fraudulent intent.</p></li><li><p><strong>Bradford v. Commissioner, 796 F.2d 303 (9th Cir. 1986)</strong>: Identifies commonly used badges of fraud.</p></li><li><p><strong>Niedringhaus v. Commissioner, 99 T.C. 202 (1992)</strong>: Explains that multiple badges of fraud can provide persuasive circumstantial evidence.</p></li><li><p><strong>Podlucky v. Commissioner, T.C. Memo. 2022-45</strong>: Supports treating double bookkeeping as evidence of fraudulent intent even when the false records also serve nontax purposes.</p></li><li><p><strong>Truesdell v. Commissioner, 89 T.C. 1280 (1987)</strong>: Treats consistent and substantial understatement of income as strong evidence of fraud.</p></li><li><p><strong>Helvering v. Horst, 311 U.S. 112 (1940)</strong>: Supports taxation of income to the person who earns or enjoys its economic benefit.</p></li><li><p><strong>Butler v. Commissioner, 114 T.C. 276 (2000)</strong>: Addresses joint and several liability arising from a joint federal income tax return.</p></li></ul>]]></content:encoded></item><item><title><![CDATA[Court denies consolidated NOL deductions because predecessor losses remain subject to SRLY limits]]></title><description><![CDATA[HBM Holdings Co. v. Commissioner United States Tax Court. No. 19735-23No. 3881-24.]]></description><link>https://taxcoda.com/p/court-denies-consolidated-nol-deductions</link><guid isPermaLink="false">https://taxcoda.com/p/court-denies-consolidated-nol-deductions</guid><dc:creator><![CDATA[Adam Parr]]></dc:creator><pubDate>Wed, 05 Aug 2026 14:16:21 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!5cG2!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fab017102-2a2e-414e-9b4e-111a7d2ed1c6_500x500.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>A consolidated group cannot use a predecessor corporation&#8217;s pre-group NOLs to offset other members&#8217; income if those losses are still limited by the separate return limitation year rules and the successor parent does not have its own taxable income.</p><h3>Holding</h3><p>The Tax Court <a href="https://www.taxnotes.com/research/federal/court-documents/court-opinions-and-orders/tax-court-denies-consolidated-nol-deductions/7whr5">determined</a> that HBM Holdings Co. could not use about $108 million in net operating loss carryovers from Delavau Holdings, LLC for consolidated NOL deductions in 2018, 2020, and 2021. Delavau was considered HBM&#8217;s predecessor under the consolidated return rules, and its preliquidation tax years were still separate return limitation years. HBM&#8217;s founding group members also did not qualify as an SRLY subgroup. The Court granted partial summary judgment to the IRS.</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://taxcoda.com/subscribe?coupon=e729ad49&amp;utm_content=209585103&quot;,&quot;text&quot;:&quot;Get 40% off forever&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://taxcoda.com/subscribe?coupon=e729ad49&amp;utm_content=209585103"><span>Get 40% off forever</span></a></p><h3>Why It Matters</h3><ul><li><p>This decision highlights an important limit on &#167;381 attribute succession. An acquiring corporation can take on a liquidated corporation&#8217;s NOLs, but those losses do not automatically become unrestricted for the acquirer.</p></li><li><p>The common parent exception to the SRLY rules does not cover losses created by a predecessor of the common parent. This difference was key to the outcome.</p></li><li><p>The SRLY subgroup rules require that members were previously part of the same affiliated group. Simply having common ownership or economic ties before consolidation is not sufficient.</p></li><li><p>This decision is especially important for restructurings that involve S corporations, QSubs, entity classification elections, &#167;332 liquidations, and forming a consolidated group later on. The order of these transactions can affect whether inherited NOLs can be used to offset group income.</p></li></ul><h3>Key Facts</h3><p>HBM Holdings Co. was the common parent of a consolidated corporate group.</p><p>Mississippi Lime Co. acquired Delavau Holdings, LLC in 2012. Delavau had approximately $78 million of NOL carryovers at that time and was treated as a loss corporation under &#167;382.</p><p>HBM was formed in 2014 through an F reorganization and elected S corporation status. Several subsidiaries, including Mississippi Lime, later operated as qualified subchapter S subsidiaries, or QSubs.</p><p>HBM revoked its S corporation election effective July 1, 2018. The QSub status of four subsidiaries ended on the same date.</p><p>Delavau elected to be disregarded as a separate entity from HBM, effective July 1, 2018. That election caused Delavau to be deemed liquidated into HBM as of June 30, 2018.</p><p>The parties agreed that &#167;&#167;332 and 381 applied to the deemed liquidation. HBM therefore succeeded to Delavau&#8217;s NOL carryovers, which had grown to approximately $108 million.</p><p>HBM then became the common parent of a consolidated group beginning July 1, 2018. Delavau was never a member of that consolidated group.</p><p>HBM had no taxable income on a separate-entity basis for the short 2018 tax year through 2021.</p><p>The consolidated group nevertheless used Delavau&#8217;s NOL carryovers to claim CNOL deductions of approximately:</p><ul><li><p>$13.55 million for the short 2018 tax year.</p></li><li><p>$14.97 million for 2020.</p></li><li><p>Approximately $1.1 million for 2021.</p></li></ul><p>The IRS disallowed the deductions under the SRLY rules.</p><h3>Statutory or Regulatory Framework</h3><p>Section 381 generally allows an acquiring corporation in certain tax-free corporate transactions, including qualifying &#167;332 liquidations, to succeed to specified tax attributes of the distributor or transferor, including NOL carryovers.</p><p>The coThe consolidated return rules add another limit through the separate return limitation year (SRLY) rules. An SRLY usually includes a separate return year of a group member or its predecessor.<span> Treas. Reg. &#167;1.1502-21(c), an NOL generated during an SRLY generally may offset consolidated taxable income only to the extent that the consolidated group&#8217;s income is attributable to the member that generated or succeeded to the loss.</span></p><p>Treas. Reg. &#167;1.1502-1(f)(2)(i), known as the lonely parent rule, excludes some separate return years of the current common parent from being considered SRLYs.</p><p>The subgroup rules offer another exception. Members can usually combine their income for SRLY purposes if they joined the current group together after being in the same affiliated group before.</p><h3>Arguments</h3><p>Taxpayer argued:</p><ul><li><p>Section 381 caused HBM to inherit Delavau&#8217;s NOL carryovers as HBM&#8217;s own tax attributes.</p></li><li><p>Because HBM was the common parent of the consolidated group, the lonely parent rule should prevent Delavau&#8217;s historical separate return years from being treated as SRLYs.</p></li><li><p>Delavau should not qualify as HBM&#8217;s predecessor because HBM was not yet a member of the consolidated group when the &#167;381 transaction occurred.</p></li><li><p>Alternatively, HBM and the other founding members should qualify as an SRLY subgroup because they were jointly controlled prior to the formation of the consolidated group.</p></li></ul><p>Government argued:</p><ul><li><p>Delavau remained the source of the NOLs even after HBM succeeded to them under &#167;381.</p></li><li><p>Delavau was HBM&#8217;s predecessor under Treas. Reg. &#167;1.1502-1(f)(4).</p></li><li><p>The lonely parent exception applies to the common parent&#8217;s own separate return years, not the separate return years of its predecessor.</p></li><li><p>The founding members could not form an SRLY subgroup because they had never previously belonged to another affiliated group together.</p></li><li><p>Since HBM did not have its own taxable income during the relevant years, the SRLY limitation stopped the inherited Delavau losses from being used to offset the income of other group members.</p></li></ul><h3>Court&#8217;s Reasoning</h3><ul><li><p>Section 381 allows tax attributes to be transferred, but their origin still matters. The regulations still treat NOL carryovers inherited from another company differently from those created by the acquiring company.</p></li><li><p>Delavau met the regulatory definition of a predecessor because it distributed assets to HBM in a transaction to which &#167;381 applied. The regulations did not require that HBM be a consolidated group member when the liquidation occurred.</p></li><li><p>The Court rejected HBM&#8217;s proposed timing limitation because Treas. Reg. &#167;1.1502-1(f)(4) contains no such requirement.</p></li><li><p>Delavau&#8217;s preliquidation years remained separate return years of HBM&#8217;s predecessor. Those years therefore fell within the general definition of SRLYs.</p></li><li><p>The lonely parent rule did not apply. Its text refers to separate return years of the common parent itself and does not include separate return years of a predecessor.</p></li><li><p>The founding members did not qualify as an SRLY subgroup. Before July 2018, HBM was an S corporation and the other entities were QSubs disregarded as separate from HBM. They therefore had not previously belonged to another affiliated group.</p></li><li><p>Because HBM generated no separate taxable income during the years at issue, there was no HBM-attributable income against which the Delavau SRLY NOLs could be used. Income earned by the other founding members could not expand the limitation.</p></li></ul><h3>Result</h3><p>The Tax Court approved the IRS&#8217;s request for partial summary judgment, denied HBM&#8217;s cross-motion, and did not allow the consolidated NOL deductions related to Delavau&#8217;s NOL carryovers for 2018, 2020, and 2021.</p><h3>The Takeaway</h3><p>Section 381 succession does not make inherited NOLs the same as a successor corporation&#8217;s own losses for consolidated return purposes. Groups that acquire or inherit losses before consolidation must check the SRLY rules separately before assuming those losses can offset other members&#8217; income.</p><h3>List of Citations</h3><ul><li><p><strong>I.R.C. &#167;332</strong>: Governs qualifying liquidations of subsidiaries into parent corporations.</p></li><li><p><strong>I.R.C. &#167;381</strong>: Governs succession to specified tax attributes, including NOL carryovers, in qualifying corporate transactions.</p></li><li><p><strong>I.R.C. &#167;382</strong>: Limits the use of NOLs following certain ownership changes.</p></li><li><p><strong>I.R.C. &#167;1361</strong>: Governs S corporations and qualified subchapter S subsidiaries.</p></li><li><p><strong>I.R.C. &#167;1504</strong>: Defines affiliated groups for consolidated return purposes.</p></li><li><p><strong>Treas. Reg. &#167;1.1502-1(e)</strong>: Defines a separate return year.</p></li><li><p><strong>Treas. Reg. &#167;1.1502-1(f)</strong>: Defines SRLYs, predecessors, successors, and relevant exceptions.</p></li><li><p><strong>Treas. Reg. &#167;1.1502-21</strong>: Governs consolidated NOL deductions and the SRLY limitation.</p></li><li><p><strong>Treas. Reg. &#167;1.381(c)(1)-1</strong>: Governs treatment of NOL carryovers succeeded to under &#167;381.</p></li><li><p><strong>Treas. Reg. &#167;301.7701-3</strong>: Governs entity classification elections and deemed transactions resulting from changes in classification.</p></li><li><p><strong>Wolter Construction Co. v. Commissioner, 68 T.C. 39 (1977), aff&#8217;d, 634 F.2d 1029 (6th Cir. 1980)</strong>: Supports applying SRLY restrictions to predecessor losses inherited by a successor common parent.</p></li><li><p><strong>Dover Corp. &amp; Subsidiaries v. Commissioner, 122 T.C. 324 (2004)</strong>: Addressed succession to business history under &#167;381 but did not establish that inherited NOLs become indistinguishable from the acquirer&#8217;s own attributes.</p></li><li><p><strong>AptarGroup Inc. v. Commissioner, 158 T.C. 110 (2022)</strong>: Supports interpreting consolidated return regulations according to their text and structure.</p></li><li><p><strong>Florida Peach Corp. v. Commissioner, 90 T.C. 678 (1988)</strong>: States the Tax Court&#8217;s standard and purpose for summary judgment.</p></li></ul>]]></content:encoded></item><item><title><![CDATA[Tax Court denies COVID-19 leave credits after taxpayer fails to prove self-employment]]></title><description><![CDATA[Lawrence Hubbard v. Commissioner. United States Tax Court. No. 10585-24. T.C. Memo., filed July 27, 2026.]]></description><link>https://taxcoda.com/p/tax-court-denies-covid-19-leave-credits</link><guid isPermaLink="false">https://taxcoda.com/p/tax-court-denies-covid-19-leave-credits</guid><dc:creator><![CDATA[Adam Parr]]></dc:creator><pubDate>Tue, 04 Aug 2026 15:09:17 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!5cG2!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fab017102-2a2e-414e-9b4e-111a7d2ed1c6_500x500.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>A taxpayer cannot claim refundable COVID-19 sick and family leave credits using only unverified payment logs, screenshots, or testimony that do not prove a real trade or business or a COVID-19-related inability to work.</p><h3>Holding</h3><p>The Tax Court upheld a 2021 income tax deficiency against Lawrence Hubbard because he did not report $22,925 in unemployment compensation, could not prove he ran a trade or business, and did not provide enough evidence for $31,890 in refundable COVID-19 sick and family leave credits. The IRS dropped a $6,378.40 penalty under &#167;6676 for an incorrect refund or credit claim.</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://taxcoda.com/subscribe?coupon=e729ad49&amp;utm_content=209584806&quot;,&quot;text&quot;:&quot;Get 40% off forever&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://taxcoda.com/subscribe?coupon=e729ad49&amp;utm_content=209584806"><span>Get 40% off forever</span></a></p><h3>Why It Matters</h3><ul><li><p><strong>The decision is primarily a case of substantiation.</strong> The Court applied established burden-of-proof rules rather than announcing a new interpretation of the COVID-19 credit provisions.</p></li><li><p><strong>Self-employment was a threshold issue.</strong> The COVID-19 sick and family leave credits depended on income from a trade or business. Hubbard could not establish that his barber, music, and cooking activities met that requirement.</p></li><li><p><strong>Payment records alone did not prove business activity.</strong> Screenshots showing Zelle, Cash App, and cash deposits did not identify the business purpose of the payments or connect them to services performed.</p></li><li><p><strong>A fraud allegation does not overcome a Form 1099-G without supporting evidence.</strong> Hubbard disputed unemployment compensation reported by California EDD, but evidence that he filed a bank fraud claim did not establish that he never received the income.</p></li></ul><h3>Key Facts</h3><p>Lawrence Hubbard filed a 2021 federal income tax return reporting self-employment activity as a barber.</p><p>His Schedule C reported:</p><ul><li><p>$10,344 of gross business income.</p></li><li><p>$5,509 of business expenses.</p></li><li><p>$4,835 of net business income.</p></li></ul><p>He also claimed $31,890 of refundable COVID-19 sick and family leave credits:</p><ul><li><p>$14,960 for leave before April 1, 2021.</p></li><li><p>$16,930 for leave after March 31, 2021.</p></li></ul><p>Hubbard did not attach Form 7202, Credits for Sick Leave and Family Leave for Certain Self-Employed Individuals, to support the credits.</p><p>California EDD issued Hubbard a Form 1099-G reporting $22,925 of unemployment compensation and $1,260 of federal income tax withholding. Hubbard did not report either amount on his return.</p><p>The IRS issued a notice of deficiency determining $32,938 of additional income tax and initially imposed a $6,378.40 penalty under &#167;6676. The IRS later conceded the penalty.</p><h3>Regulatory Framework</h3><p>Gross income generally includes income from all sources under &#167;61.</p><p>Under &#167;162, taxpayers may deduct ordinary and necessary expenses incurred in carrying on a trade or business. A taxpayer must conduct an activity with continuity and regularity and primarily for income or profit for the activity to qualify as a trade or business.</p><p>Section 6001 and Treas. Reg. &#167;1.6001-1 require taxpayers to maintain records sufficient to establish their tax liability and substantiate deductions and credits.</p><p>Congress created refundable sick and family leave credits for qualifying self-employed individuals under the Families First Coronavirus Response Act, or FFCRA, and later extended similar credits through the American Rescue Plan Act, or ARPA.</p><p>The credits depended on self-employment income and required taxpayers to establish a qualifying COVID-19-related reason for not working. Required documentation generally included the dates of leave, the qualifying reason, written support for that reason, and a statement that the taxpayer could not work because of it.</p><h3>Arguments</h3><p><strong>Taxpayer argued:</strong></p><ul><li><p>He did not receive the $22,925 of unemployment compensation reported by California EDD for 2021.</p></li><li><p>Fraud involving unemployment benefits occurred, and he filed a fraud claim with his bank and California EDD.</p></li><li><p>He worked as a self-employed barber, musician, and chef.</p></li><li><p>He received customer payments through Zelle, Cash App, and cash.</p></li><li><p>He used part of his residence for barber services and as a music studio.</p></li><li><p>His self-employment activity supported his claimed COVID-19 sick and family leave credits.</p></li></ul><p><strong>Government argued:</strong></p><ul><li><p>The Form 1099-G established Hubbard&#8217;s receipt of $22,925 of unemployment compensation.</p></li><li><p>Hubbard did not provide adequate evidence proving that the reported unemployment compensation resulted from fraud.</p></li><li><p>His records did not establish that he operated a qualifying trade or business.</p></li><li><p>His reported Schedule C income and expenses lacked adequate substantiation.</p></li><li><p>He failed to establish either the self-employment or qualifying-leave requirements for the COVID-19 credits.</p></li></ul><h3>Court&#8217;s Reasoning</h3><ul><li><p>California EDD&#8217;s Form 1099-G provided the required evidentiary connection between Hubbard and the reported $22,925 of unemployment compensation. That shifted the burden to Hubbard to establish that the amount was not taxable to him.</p></li><li><p>Hubbard produced evidence that he filed a fraud claim with Bank of America, but he did not document the outcome of that claim or provide evidence of a fraud determination from the California EDD.</p></li><li><p>Screenshots from his EDD account, primarily related to unemployment compensation received in another tax year. They did not establish that the 2021 Form 1099-G was incorrect.</p></li><li><p>Hubbard&#8217;s business records did not demonstrate that he conducted a trade or business with continuity and regularity. His payment log showed transactions from several individuals but did not explain what services generated the payments.</p></li><li><p>His expense records listed amounts paid but did not say what business purpose they served. For example, a $337 Airbnb payment and a $3,400 check were not explained.</p></li><li><p>The payment log did not match his Schedule C. The log showed $9,330.69 in income, $5,452 in expenses, and $3,878.69 in net income, but his tax return reported $10,344, $5,509, and $4,835 for these amounts.</p></li><li><p>Since Hubbard could not prove he ran a trade or business, he did not meet the basic requirement for the COVID-19 sick and family leave credits. Even if he had shown he had a business, he did not provide enough documents to show qualifying leave dates, a COVID-19 reason, or when he could not work.</p></li></ul><h3>Result</h3><p>The Tax Court ruled in favor of the IRS on the income tax deficiency and in favor of Hubbard on the &#167;6676 penalty, which the IRS had already dropped.</p><h3>The Takeaway</h3><p>Practitioners working on self-employed COVID-19 leave credit claims should treat proof of a trade or business and proof of qualifying leave as separate requirements. Screenshots and payment logs may show money was received, but they do not explain what the income was for, why an expense was business-related, or why the taxpayer qualified for the credit.</p><h4>List of Citations</h4><ul><li><p><strong>&#167;61(a)</strong>. Defines gross income broadly to include income from all sources unless an exclusion applies.</p></li><li><p><strong>&#167;162(a)</strong>. Permits deductions for ordinary and necessary trade or business expenses.</p></li><li><p><strong>&#167;6001</strong>. Requires taxpayers to maintain records supporting their tax liability.</p></li><li><p><strong>&#167;6201(d)</strong>. Addresses disputes involving information returns when taxpayers reasonably contest reported income.</p></li><li><p><strong>&#167;6676(a)</strong>. Provides a penalty for certain erroneous claims for refund or credit. The IRS conceded this penalty.</p></li><li><p><strong>&#167;7491(a)</strong>. Provides circumstances in which the burden of proof may shift to the IRS.</p></li><li><p><strong>Treas. Reg. &#167;1.6001-1(a)</strong>. Requires taxpayers to maintain adequate books and records.</p></li><li><p><strong>Welch v. Helvering, 290 U.S. 111 (1933)</strong>. Establishes the general presumption of correctness for IRS deficiency determinations.</p></li><li><p><strong>Commissioner v. Groetzinger, 480 U.S. 23 (1987)</strong>. Defines the continuity, regularity, and profit requirements for a trade or business.</p></li><li><p><strong>Weimerskirch v. Commissioner, 596 F.2d 358 (9th Cir. 1979)</strong>. Requires an evidentiary foundation connecting a taxpayer to alleged unreported income before the presumption of correctness applies.</p></li><li><p><strong>Hardy v. Commissioner, 181 F.3d 1002 (9th Cir. 1999)</strong>. Recognizes third-party information returns as sufficient evidence connecting a taxpayer to income.</p></li><li><p><strong>FFCRA &#167;&#167;7002 and 7004</strong>. Created refundable sick and family leave credits for qualifying self-employed individuals.</p></li><li><p><strong>ARPA &#167;&#167;9642 and 9643</strong>. Extended and modified refundable sick and family leave credits for qualifying self-employed individuals.</p></li></ul>]]></content:encoded></item><item><title><![CDATA[Court upholds tax on unreported Social Security benefits]]></title><description><![CDATA[Charmaine A. Gray v. Commissioner. United States Tax Court. No. 11390-25. 2026.]]></description><link>https://taxcoda.com/p/court-upholds-tax-on-unreported-social</link><guid isPermaLink="false">https://taxcoda.com/p/court-upholds-tax-on-unreported-social</guid><dc:creator><![CDATA[Adam Parr]]></dc:creator><pubDate>Mon, 03 Aug 2026 16:04:09 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!5cG2!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fab017102-2a2e-414e-9b4e-111a7d2ed1c6_500x500.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>Up to 85% of Social Security benefits can be taxed if a taxpayer&#8217;s modified income is above the limits set in &#167;86. The $25,000 threshold does not mean benefits below that amount are always tax-free.</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://taxcoda.com/subscribe?coupon=e729ad49&amp;utm_content=209581975&quot;,&quot;text&quot;:&quot;Get 40% off forever&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://taxcoda.com/subscribe?coupon=e729ad49&amp;utm_content=209581975"><span>Get 40% off forever</span></a></p><h3>Holding</h3><p><span>The Tax Court&nbsp;</span><a href="https://www.taxnotes.com/research/federal/court-documents/court-opinions-and-orders/tax-court-upholds-deficiency-unreported-social-security-benefits/7whr0"><span>agreed</span></a><span>&nbsp;with a $4,917 tax deficiency after Charmaine Gray did not report $26,268 in Social Security benefits on her 2022 tax return. The Court found that $22,328, or 85% of her benefits, was taxable under &#167;86.</span></p><h3>Why It Matters</h3><ul><li><p>The decision applies settled law. It does not change the taxation of Social Security benefits or create a new interpretation of &#167;86.</p></li><li><p>The $25,000 statutory base amount for most single taxpayers does not mean the first $25,000 of Social Security benefits is tax-free. The calculation depends on modified adjusted gross income plus one-half of Social Security benefits.</p></li><li><p>Taxpayers with substantial wages or other income may have up to 85% of their Social Security benefits included in gross income.</p></li><li><p>Arguments that Social Security taxation constitutes unconstitutional double taxation remain foreclosed by established Tax Court precedent.</p></li></ul><h3>Key Facts</h3><p>Gray received $65,085 of wages from Stine Seed Co. during 2022.</p><p>She also received $26,268 in Social Security benefits, as reported by the Social Security Administration on Form SSA-1099.</p><p>Gray reported the wages on Form 1040-SR but reported none of the Social Security benefits.</p><p>She claimed the standard deduction, reported no adjustments to adjusted gross income, and reported taxable income of $50,385.</p><p>The IRS issued a notice of deficiency on June 23, 2025. It determined that $22,328 of Gray&#8217;s Social Security benefits was taxable and calculated a $4,917 deficiency.</p><p>Gray disputed the deficiency, claiming her Social Security benefits should not be taxed.</p><h3>Statutory Framework</h3><p>Section 61 says that income from all sources counts as gross income. Section 86 sets the rules for taxing Social Security benefits.</p><p>For most single taxpayers, &#167;86 sets a $25,000 base amount and a $34,000 adjusted base amount. Social Security benefits become taxable when modified adjusted gross income plus half of the benefits is more than the base amount.</p><p>If this combined income is over the adjusted base amount, &#167;86 may require up to 85% of Social Security benefits to be taxed.</p><p>The law does not say that Social Security benefits are excluded from tax just because the amount is under $25,000.</p><h3>Arguments</h3><p>Taxpayer argued:</p><ul><li><p>Her Social Security benefits were not taxable.</p></li><li><p>She understood the $25,000 threshold enacted in 1983 to exempt benefits below that amount.</p></li><li><p>Taxing her Social Security benefits after she had already paid Social Security taxes through payroll withholding amounted to double taxation.</p></li><li><p>She also challenged the constitutionality of taxing the benefits.</p></li></ul><p>Government argued:</p><ul><li><p>Gray received $26,268 of Social Security benefits and stipulated that she received the income.</p></li><li><p>Her wages and Social Security benefits exceeded the statutory thresholds in &#167;86.</p></li><li><p>The statutory formula required $22,328 of her benefits to be included in gross income.</p></li></ul><h3>Court&#8217;s Reasoning</h3><ul><li><p>Gray stipulated that she received the Social Security benefits. That evidence satisfied the IRS&#8217;s initial burden to connect her with the unreported income.</p></li><li><p>Section 86 expressly requires taxpayers to include a portion of Social Security benefits in gross income when income exceeds statutory thresholds.</p></li><li><p>Gray&#8217;s modified adjusted gross income was $65,085, since there were no adjustments shown in the record.</p></li><li><p>Half of her $26,268 in Social Security benefits was $13,134.</p></li><li><p>When $13,134 is added to her $65,085 modified adjusted gross income, the total is $78,219. This is much higher than the $34,000 adjusted base amount for her filing status.</p></li><li><p>Because of this, the &#167;86 formula required her to include up to 85% of her Social Security benefits as taxable income.</p></li><li><p>85% of $26,268 is $22,328. This was the correct amount to include in her gross income.</p></li><li><p>The Court did not accept Gray&#8217;s argument about the $25,000 threshold. It explained that this amount is part of the income calculation, not a general exclusion.</p></li><li><p>The Court also rejected her double-taxation and constitutional arguments, citing long-standing precedent supporting &#167; 86.</p></li></ul><h3>Result</h3><p>The Tax Court upheld the IRS&#8217;s $4,917 deficiency for Gray&#8217;s 2022 tax year.</p><h3>The Takeaway</h3><p>This case is a standard use of &#167;86, but it clears up a common misunderstanding. The Social Security thresholds are used to figure out how much of the benefits are taxable. They do not mean that benefits below $25,000 are automatically excluded from tax.</p><h4>List of Citations</h4><ul><li><p><strong>IRC &#167;61(a)</strong>: Defines gross income broadly as income from all sources.</p></li><li><p><strong>IRC &#167;86</strong>: Governs the inclusion of Social Security benefits in gross income and establishes the applicable income thresholds.</p></li><li><p><strong>IRC &#167;86(d)</strong>: Defines Social Security benefits for purposes of &#167;86 and addresses reductions for repayments.</p></li><li><p><strong>Rule 122, Tax Court Rules of Practice and Procedure</strong>: Allows parties to submit a case for decision based on stipulated facts without trial.</p></li><li><p><strong>Rule 142(a)(1), Tax Court Rules of Practice and Procedure</strong>: Generally places the burden of proof on the taxpayer.</p></li><li><p><strong>Welch v. Helvering, 290 U.S. 111 (1933)</strong>: Establishes the general presumption that the Commissioner&#8217;s deficiency determination is correct.</p></li><li><p><strong>Walquist v. Commissioner, 152 T.C. 61 (2019)</strong>: Explains the IRS&#8217;s initial evidentiary burden in unreported-income cases.</p></li><li><p><strong>Day v. Commissioner, 975 F.2d 534 (8th Cir. 1992)</strong>: Requires some evidence connecting a taxpayer to unreported income before the presumption of correctness applies.</p></li><li><p><strong>El v. Commissioner, 144 T.C. 140 (2015)</strong>: Confirms that stipulated receipt of income satisfies the IRS&#8217;s initial burden.</p></li><li><p><strong>Jelle v. Commissioner, 116 T.C. 63 (2001)</strong>: Applies the &#167;86 formula when income exceeds the adjusted base amount.</p></li><li><p><strong>Cotroneo v. Commissioner, T.C. Memo. 2024-70</strong>: Applies the 85% Social Security inclusion rules under &#167;86.</p></li><li><p><strong>Lin v. Commissioner, T.C. Memo. 2023-37</strong>: Applies &#167;86 to determine the taxable portion of Social Security benefits.</p></li><li><p><strong>Holland v. Commissioner, T.C. Memo. 2021-129</strong>: Rejects arguments attempting to avoid the express taxation of Social Security benefits.</p></li><li><p><strong>Kelley v. Commissioner, T.C. Memo. 2021-2</strong>: Rejects challenges to the statutory Social Security taxation rules and emphasizes that the Tax Court must apply the statute enacted by Congress.</p></li><li><p><strong>McAdams v. Commissioner, 118 T.C. 373 (2002)</strong>: Rejects constitutional challenges to &#167;86.</p></li><li><p><strong>Clark v. Commissioner, T.C. Memo. 1998-280</strong>: Upholds the constitutionality of taxing Social Security benefits.</p></li><li><p><strong>Roberts v. Commissioner, T.C. Memo. 1998-172</strong>: Rejects constitutional objections to &#167;86.</p></li></ul>]]></content:encoded></item><item><title><![CDATA[IRS sets August 2026 applicable federal rates]]></title><description><![CDATA[Rev. Rul. 2026-13]]></description><link>https://taxcoda.com/p/irs-sets-august-2026-applicable-federal</link><guid isPermaLink="false">https://taxcoda.com/p/irs-sets-august-2026-applicable-federal</guid><dc:creator><![CDATA[Adam Parr]]></dc:creator><pubDate>Mon, 03 Aug 2026 05:33:21 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!5cG2!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fab017102-2a2e-414e-9b4e-111a7d2ed1c6_500x500.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<h3>Reader Takeaway</h3><p>The IRS has set the annual applicable federal rates for August 2026 at 4.10% for short-term, 4.35% for mid-term, and 4.92% for long-term obligations.</p><h3>Holding</h3><p><span>Revenue Ruling 2026-13&nbsp;</span><a href="https://www.irs.gov/pub/irs-drop/rr-26-13.pdf"><span>sets</span></a><span>&nbsp;the federal interest and tax rates for August 2026. These rates apply to sections 42, 382, 1274, 1288, and 7520.</span></p><h3>Why It Matters</h3><ul><li><p>The AFRs establish minimum interest benchmarks for many related-party loans, installment sales, below-market financing arrangements, and other debt instruments.</p></li><li><p>The &#167;7520 rate increases to 5.20% for August 2026 and applies when valuing annuities, life estates, term interests, remainders, and reversions.</p></li><li><p>The &#167;382 long-term tax-exempt rate is 3.77% for ownership changes occurring during August. That rate can affect the annual limitation on the use of pre-change tax attributes following an ownership change.</p></li><li><p>The ruling also supplies monthly rates used for low-income housing tax credit calculations. These are routine monthly updates rather than a change in tax policy.</p></li></ul><h3>Key Rates</h3><p>For annual compounding, the AFRs for August 2026 are:</p><ul><li><p>Short-term AFR: <strong>4.10%</strong></p></li><li><p>Mid-term AFR: <strong>4.35%</strong></p></li><li><p>Long-term AFR: <strong>4.92%</strong></p></li></ul><p>The ruling also lists AFR multiples for provisions that require 110%, 120%, 130%, 150%, or 175% of the standard AFR.</p><p>For example:</p><ul><li><p>120% short-term AFR: <strong>4.93%</strong></p></li><li><p>120% mid-term AFR: <strong>5.23%</strong></p></li><li><p>120% long-term AFR: <strong>5.91%</strong></p></li></ul><p>The ruling also includes monthly, quarterly, and semiannual compounding equivalents.</p><h3>Adjusted AFRs</h3><p>The annual adjusted AFRs for August 2026 are:</p><ul><li><p>Short-term adjusted AFR: <strong>3.10%</strong></p></li><li><p>Mid-term adjusted AFR: <strong>3.29%</strong></p></li><li><p>Long-term adjusted AFR: <strong>3.72%</strong></p></li></ul><p>Adjusted AFRs are used for certain tax-e<span>Adjusted AFRs apply to certain tax-exempt obligations and other calculations under &#167;1288.</span></p><ul><li><p>Adjusted federal long-term rate: <strong>3.72%</strong></p></li><li><p>Long-term tax-exempt rate: <strong>3.77%</strong></p></li></ul><p>The long-term tax-exempt rate is the highest adjusted federal long-term rate from the current month and the previous two months. This rate matters when applying &#167;382 after an ownership change.</p><h3>Low-Income Housing Credit Rates</h3><p>The &#167;42(b)(1) appropriate percentages for August 2026 are:</p><ul><li><p>70% present value credit: <strong>8.08%</strong></p></li><li><p>30% present value credit: <strong>3.46%</strong></p></li></ul><p>The ruling notes that for qualifying non-federally subsidized new buildings placed in service after July 30, 2008, the applicable percentage cannot be less than 9% under &#167;42(b)(2).</p><h3>Section 7520 Rate</h3><p>The &#167;7520 rate for August 2026 is <strong>5.20%</strong>.</p><p>Practitioners use this rate to determine the present value of:</p><ul><li><p>Annuities</p></li><li><p>Life interests</p></li><li><p>Interests for a term of years</p></li><li><p>Remainder interests</p></li><li><p>Reversionary interests</p></li></ul><p>This is a routine monthly rate ruling, but the numbers matter whenever a transaction closes or a valuation date falls on or after August 2026. Practitioners handling related-party financing, &#167;382 limitations, estate-planning valuations, or housing credit calculations should use the August rates rather than carry forward rates from prior months.</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://taxcoda.com/p/irs-sets-august-2026-applicable-federal?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://taxcoda.com/p/irs-sets-august-2026-applicable-federal?utm_source=substack&utm_medium=email&utm_content=share&action=share"><span>Share</span></a></p>]]></content:encoded></item><item><title><![CDATA[Court grants innocent spouse relief after IRS fails to prove actual knowledge of disallowed deduction]]></title><description><![CDATA[Trisha Anderson v. Commissioner. United States Tax Court. T.C. Summary Opinion. Filed July 22, 2026.]]></description><link>https://taxcoda.com/p/court-grants-innocent-spouse-relief</link><guid isPermaLink="false">https://taxcoda.com/p/court-grants-innocent-spouse-relief</guid><dc:creator><![CDATA[Adam Parr]]></dc:creator><pubDate>Wed, 29 Jul 2026 13:07:09 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!5cG2!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fab017102-2a2e-414e-9b4e-111a7d2ed1c6_500x500.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>A divorced spouse may qualify for innocent spouse relief if the IRS cannot show she knew the facts that made a deduction improper, even if she signed the joint return.</p><h3>Holding</h3><p>The Tax Court decided that Trisha Anderson qualified for innocent spouse relief under IRC section 6015(c). The IRS could not prove she knew the facts behind the disallowed mortgage interest deduction, so her former husband was assigned the entire deficiency.</p><h3>Why It Matters</h3><ul><li><p>This decision reinforces that the IRS bears the burden of proving a requesting spouse had <strong>actual knowledge</strong> of the item causing the deficiency under section 6015(c).</p></li><li><p>The case distinguishes knowledge that a transaction occurred from knowledge that a tax deduction was legally unsupported.</p></li><li><p>It shows that deficiencies arising from a failure to substantiate a deduction are treated differently from deficiencies caused by knowingly claiming an improper deduction.</p></li><li><p>The opinion also demonstrates that allocation under section 6015(c) is determined without applying community property rules, even when the taxpayers lived in California.</p></li></ul><h3>Key Facts</h3><ul><li><p>Trisha Anderson and her husband filed a joint federal income tax return for 2016.</p></li><li><p>Her husband earned all of the couple&#8217;s income and managed the family&#8217;s finances, including preparing and filing their tax returns.</p></li><li><p>The couple sold their home in 2016 after placing it into a family trust.</p></li><li><p>Their joint return claimed approximately $108,220 of mortgage interest.</p></li><li><p>During an audit, the IRS disallowed the deduction because the taxpayers failed to establish that the claimed interest was deductible and paid.</p></li><li><p>The notice of deficiency was mailed only to Mr. Anderson. Ms. Anderson never received it.</p></li><li><p>The couple divorced in 2021, and their divorce agreement required Mr. Anderson to pay the 2016 federal tax liability.</p></li><li><p>Ms. Anderson requested innocent spouse relief in 2023 after the IRS began collection efforts.</p></li></ul><h3>Statutory Framework</h3><p>IRC section 6015 provides three avenues for relief from joint and several liability on a joint return.</p><p>Section 6015(c) allows a divorced or separated spouse to allocate a deficiency between the spouses as if they had filed separate returns.</p><p>Relief is unavailable if the IRS proves the requesting spouse had <strong>actual knowledge</strong>, meaning knowledge of the facts that made the deduction improper, not merely knowledge that the underlying transaction occurred.</p><h3>Arguments</h3><p><strong>Taxpayer argued:</strong></p><ul><li><p>She had no involvement in managing the family&#8217;s finances.</p></li><li><p>She believed the mortgage interest had been paid.</p></li><li><p>She did not receive the notice of deficiency.</p></li><li><p>The deficiency resulted from her former husband&#8217;s handling of the audit, not from any knowing misconduct on her part.</p></li></ul><p><strong>Government argued:</strong></p><ul><li><p>Ms. Anderson had actual knowledge of the item giving rise to the deficiency.</p></li><li><p>Because she knew about the mortgage interest deduction, she should remain jointly liable for the resulting tax.</p></li></ul><h3>Court&#8217;s Reasoning</h3><ul><li><p>The IRS had the burden of proving actual knowledge by a preponderance of the evidence.</p></li><li><p>The evidence showed the mortgage interest was in fact paid through the home sale, as reflected on the settlement statement.</p></li><li><p>The deficiency appeared to result because Mr. Anderson failed to substantiate the deduction during the audit rather than because the interest had not been paid.</p></li><li><p>Knowing that mortgage interest existed is not the same as knowing the deduction would ultimately be disallowed.</p></li><li><p>Ms. Anderson credibly testified that she believed the interest had been paid.</p></li><li><p>The Court found no evidence that she knew the deduction lacked adequate substantiation.</p></li><li><p>Because only Mr. Anderson was liable on the mortgages and managed the financial affairs, the deduction would have belonged entirely to him if separate returns had been filed.</p></li><li><p>As a result, the entire deficiency was allocated to Mr. Anderson, leaving Ms. Anderson fully relieved of liability.</p></li></ul><h3>Result</h3><p>The Tax Court granted Ms. Anderson innocent spouse relief under IRC section 6015(c) and relieved her of the entire 2016 deficiency.</p><h3>The Takeaway</h3><p>This case applies existing innocent spouse rules rather than changing the law. It confirms that the IRS must prove a spouse actually knew the facts that made a deduction improper, not just that the spouse knew about the transaction. It also shows that if one spouse handled the finances and the other was not involved, a lack of audit proof may support relief.</p><h4>List of Citations</h4><ul><li><p><strong>IRC &#167; 6015(c)</strong>, governing allocation of joint liabilities between divorced or separated spouses.</p></li><li><p><strong>IRC &#167; 6015(e)</strong>, granting Tax Court jurisdiction over innocent spouse determinations.</p></li><li><p><strong>Thomas v. Commissioner, 162 T.C. 9 (2024)</strong>, addressing the Tax Court&#8217;s standard and scope of review in innocent spouse cases.</p></li><li><p><strong>Porter v. Commissioner, 132 T.C. 203 (2009)</strong>, discussing de novo review under section 6015.</p></li><li><p><strong>Cheshire v. Commissioner, 115 T.C. 183 (2000), aff&#8217;d, 282 F.3d 326 (5th Cir. 2002)</strong>, explaining actual knowledge under innocent spouse provisions.</p></li><li><p><strong>Culver v. Commissioner, 116 T.C. 189 (2001)</strong>, confirming the IRS bears the burden of proving actual knowledge.</p></li><li><p><strong>Treas. Reg. &#167; 1.6015-3</strong>, defining actual knowledge for purposes of section 6015(c).</p></li><li><p><strong>Golder v. Commissioner, 604 F.2d 34 (9th Cir. 1979)</strong>, addressing mortgage interest deductions by liable taxpayers.</p></li><li><p><strong>Treas. Reg. &#167; 1.163-1(b)</strong>, explaining when an owner who is not personally liable on a mortgage may deduct mortgage interest.</p></li></ul>]]></content:encoded></item><item><title><![CDATA[IRS waives Form 990 filing for qualifying foreign World Cup teams]]></title><description><![CDATA[Foreign soccer associations that qualify and compete in the 2026 FIFA World Cup do not need to file Form 990 or Form 990-N for a tax year if their only U.S.-related income comes from taking part in the tournament.]]></description><link>https://taxcoda.com/p/irs-waives-form-990-filing-for-qualifying</link><guid isPermaLink="false">https://taxcoda.com/p/irs-waives-form-990-filing-for-qualifying</guid><dc:creator><![CDATA[Adam Parr]]></dc:creator><pubDate>Tue, 28 Jul 2026 13:26:18 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!5cG2!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fab017102-2a2e-414e-9b4e-111a7d2ed1c6_500x500.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>Foreign soccer associations that qualify and compete in the 2026 FIFA World Cup do not need to file Form 990 or Form 990-N for a tax year if their only U.S.-related income comes from taking part in the tournament.</p><h3>Holding</h3><p>The IRS used its authority under section 6033(a)(3)(B) to let some foreign FIFA member associations skip the annual Form 990 filing. This relief is for associations whose national teams play in the 2026 FIFA World Cup and whose only U.S. income is from the tournament.</p><p>This rule applies to tax years starting on or after January 1, 2025.</p><h3>Why It Matters</h3><ul><li><p>This relief removes a major U.S. reporting requirement for foreign soccer associations whose only U.S. activity is taking part in the 2026 World Cup.</p></li><li><p>The exception means qualifying associations do not have to file Form 990, Form 990-EZ, or the Form 990-N electronic notice for those years.</p></li><li><p>This relief does not exempt associations from federal income tax, cover unrelated U.S. activities, or remove other possible tax reporting duties.</p></li><li><p>The exception is limited. If an association earns other U.S. income or does business in the U.S. outside the World Cup, it must still file the required annual return or notice.</p></li></ul><h3>Key Facts</h3><p>The 2026 FIFA World Cup will have foreign national teams playing matches that are partly hosted in the United States.</p><p>Each national team takes part through its FIFA member association. The IRS calls a foreign association whose team plays in the tournament a participating member association, or PMA.</p><p>Some foreign PMAs may qualify as tax-exempt under section 501(a). Without this special relief, they would have to file Form 990 and report on their worldwide activities, even if their only U.S. presence is for the World Cup.<span> Filing full Form 990 filings would impose a compliance burden that exceeded the value of the information collected.</span></p><p>This relief started on July 24, 2026, and applies to tax years beginning on or after January 1, 2025.</p><h3>Organizations Covered</h3><p>The revenue procedure applies to a foreign PMA that:</p><ul><li><p>Has a national team competing in the 2026 FIFA World Cup.</p></li><li><p>Qualifies for exemption from federal income tax under section 501(a).</p></li><li><p>Is not a private foundation.</p></li><li><p>Is not a section 509(a)(3) supporting organization.</p></li><li><p>Has no U.S.-source gross income or income effectively connected with a U.S. trade or business, other than income related to participating in the 2026 World Cup.</p></li></ul><p>An association can still qualify even if it has not applied for or received an IRS letter confirming its tax-exempt status.</p><h3>Income Covered by the Relief</h3><p>This exception lets a qualifying PMA get income from World Cup participation without having to file Form 990.</p><p>The revenue procedure identifies the following examples:</p><ul><li><p>Prize money paid by FIFA.</p></li><li><p>Promotional income paid by third parties in connection with the association&#8217;s participation in the tournament.</p></li><li><p>Income arising from administrative or financial arrangements necessary or appropriate to facilitate tournament participation.</p></li></ul><p>The relief only applies if the income is tied to World Cup participation. It does not give a general exemption for all U.S. income earned by a foreign soccer association.</p><h3>Statutory and Regulatory Framework</h3><p>Section 6033(a)(1) generally requires organizations exempt from federal income tax to file an annual information return, usually Form 990, Form 990-EZ, or Form 990-PF.</p><p>Section 6033(a)(3)(B) allows the Treasury Secretary or the Secretary&#8217;s delegate to waive the annual filing requirement when the filing is unnecessary for efficient tax administration. Treasury regulations delegate that authority to the IRS Commissioner.</p><p>Congress removed that waiver authority for section 509(a)(3) supporting organizations. The IRS therefore cannot extend this relief to those organizations.</p><p>Private foundations also remain outside the revenue procedure.</p><p>Section 6033(i) generally requires certain organizations excused from filing a full annual return because of low gross receipts to submit Form 990-N, commonly called the e-Postcard. The IRS determined that qualifying PMAs do not have to submit Form 990-N because this exception turns on the nature of their gross income, not merely the amount of their gross receipts.</p><h3>Source Rules</h3><p>The revenue procedure relies on existing tax rules to determine whether income comes from U.S. sources.</p><p>Gifts, grants, contributions, and membership fees received directly or indirectly from a U.S. person generally count as U.S.-source income under Treasury Regulation section 53.4948-1(b).</p><p>Other categories of income are sourced under sections 861 through 865 and the related regulations.</p><p>A U.S. person generally includes:</p><ul><li><p>A U.S. citizen or resident.</p></li><li><p>A domestic partnership.</p></li><li><p>A domestic corporation.</p></li><li><p>A nonforeign estate.</p></li><li><p>Certain trusts subject to U.S. Court supervision and substantial control by U.S. persons.</p></li></ul><p>For this revenue procedure, the term United States includes the 50 states and the District of Columbia.</p><h3>IRS Rationale</h3><p>The IRS gave three principal reasons for waiving the filing requirement.</p><ul><li><p>The associations are not expected to earn recurring U.S.-source income or repeatedly conduct a U.S. trade or business. Their U.S. activity arises from a discrete international sporting event.</p></li><li><p>Their presence in the United States results from FIFA membership and World Cup participation, not from independent or continuing domestic operations.</p></li><li><p>Form 990 asks for details about an organization&#8217;s worldwide operations. For these associations, most activities and revenue are outside the U.S., so filing a full return would be a lot of work for little benefit.</p></li></ul><h3>Filing Consequences</h3><p>A qualifying foreign PMA does not have to file Form 990 or Form 990-EZ for a covered year.</p><p>It also does not have to submit Form 990-N for that year.</p><p>The relief applies separately to each taxable year. An association must test its eligibility annually.</p><p>If tIf the association gets other U.S. income or does business in the U.S. outside the World Cup, it must file the required annual return or notice unless another exception applies.</p><p>The revenue procedure addresses only the annual information-return requirement under section 6033.</p><p>It does not state that:</p><ul><li><p>World Cup income is excluded from gross income.</p></li><li><p>Tournament income is exempt from federal income tax.</p></li><li><p>Foreign players, coaches, employees, contractors, or other individuals receive personal tax relief.</p></li><li><p>FIFA itself qualifies for the exception.</p></li><li><p>Domestic soccer organizations qualify for the exception.</p></li><li><p>Employment tax, withholding, information reporting, or unrelated business income requirements do not apply.</p></li></ul><p>The practical effect is therefore narrower than an exemption from income reporting. <span>In practice, this is not a full exemption from income reporting. It only removes one filing requirement for qualifying foreign tax-exempt associations. Certain foreign organizations are exempt from filing Form 990 when they normally receive no more than $50,000 in annual gross receipts from U.S. sources and have no significant U.S. activity.</span></p><p>The new rule expands on the earlier guidance for World Cup associations. It gives relief even if the association&#8217;s U.S. income from the World Cup is over $50,000.</p><p>Revenue Procedure 2011-15 remains in effect and is amplified rather than replaced.</p><h3>The Takeaway</h3><p>Tax advisers working with foreign national soccer associations should separate tournament-related receipts from all other U.S. income and activity. The filing relief is useful but conditional, and any unrelated U.S. income can restore the annual reporting requirement.</p>]]></content:encoded></item><item><title><![CDATA[GAO urges Treasury to address IRS transformation, enforcement, and taxpayer service failures]]></title><description><![CDATA[GAO-26-108992 IRS Priority Recommendations]]></description><link>https://taxcoda.com/p/gao-urges-treasury-to-address-irs</link><guid isPermaLink="false">https://taxcoda.com/p/gao-urges-treasury-to-address-irs</guid><dc:creator><![CDATA[Adam Parr]]></dc:creator><pubDate>Mon, 27 Jul 2026 13:22:26 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!5cG2!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fab017102-2a2e-414e-9b4e-111a7d2ed1c6_500x500.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>The GAO found 27 important recommendations that the IRS has not yet addressed. These issues affect how the IRS updates its systems, enforces tax laws, closes the tax gap, and serves taxpayers.</p><h3>GAO&#8217;s Action</h3><p><span>The Government Accountability Office&nbsp;</span><a href="https://www.gao.gov/assets/gao-26-108992.pdf"><span>asked</span></a><span>&nbsp;Treasury Secretary Scott Bessent to focus immediately on three main IRS reform areas: managing the agency&#8217;s changes, reducing the tax gap, and improving the taxpayer experience.</span></p><p>GAO made recommendations, not rules. The letter does not change tax laws, taxpayer duties, audit procedures, or how the IRS enforces rules.</p><h3>Why It Matters</h3><ul><li><p><strong>This is a consequential oversight warning, not routine administrative correspondence.</strong> GAO identified weaknesses that affect the IRS&#8217;s core enforcement, modernization, and taxpayer-service functions.</p></li><li><p><strong>IRS modernization has lost both funding and centralized leadership.</strong> Congress rescinded or restricted more than half of the approximately $79.4 billion originally appropriated under the Inflation Reduction Act. The IRS also disbanded the office that had led its transformation program.</p></li><li><p><strong>Enforcement capacity remains a central concern.</strong> GAO specifically highlighted shortages of employees qualified to examine high-income and high-wealth taxpayers, whose returns often involve complex entities, transactions, and valuation issues.</p></li><li><p><strong>Service improvements lack adequate performance measurement.</strong> GAO concluded that the IRS needs clearer goals, measures, and targets to determine whether taxpayer-service projects actually improve taxpayer outcomes.</p></li><li><p><strong>The letter signals likely congressional scrutiny.</strong> GAO expressly noted that Congress may use hearings, appropriations, legislation, and funding restrictions to press agencies to implement priority recommendations.</p></li></ul><h3>Key Facts</h3><ul><li><p>GAO issued the letter on June 24, 2026.</p></li><li><p>The letter was addressed to Treasury Secretary Scott Bessent.</p></li><li><p>The IRS had <strong>238 open GAO recommendations</strong> as of June 2026.</p></li><li><p>GAO classified <strong>27 recommendations as priorities</strong>, meaning implementation could materially improve government operations, reduce waste or abuse, generate significant savings, or address a high-risk area.</p></li><li><p>The IRS had implemented only one of the priority recommendations identified in GAO&#8217;s September 2025 letter.</p></li><li><p>The IRS&#8217;s implementation rate for recommendations made five years earlier was <strong>72 percent</strong>, compared with a government-wide rate of <strong>77 percent</strong>.</p></li><li><p>Congress originally provided approximately <strong>$79.4 billion</strong> to the IRS under the Inflation Reduction Act of 2022.</p></li><li><p>Subsequent legislation rescinded or restricted the use of more than half of that funding.</p></li></ul><h3>Priority Area One: Managing IRS Transformation</h3><p>The IRS began a broad transformation program covering technology, organizational structure, taxpayer services, enforcement, and resource allocation. Its 2023 Strategic Operating Plan relied heavily on the multiyear funding provided by the Inflation Reduction Act.</p><p>That plan now operates under materially different conditions.</p><p>Congress reduced the available funding through later legislation. The administration&#8217;s fiscal year 2027 budget proposal recommended additional reductions. IRS officials also reported in March 2025 that the office responsible for leading the transformation had been disbanded.</p><p>GAO said the IRS was still determining which projects would continue and who would lead them.</p><p>GAO recommended that the IRS apply established organizational-reform practices, including:</p><ul><li><p>Setting clear and measurable transformation goals.</p></li><li><p>Establishing an effective implementation process.</p></li><li><p>Assigning responsibility for specific initiatives.</p></li><li><p>Engaging Congress and other affected stakeholders.</p></li><li><p>Allocating sufficient personnel and funding to the projects the agency decides to retain.</p></li></ul><p>The issue is bigger than just saving certain technology projects. The IRS needs to figure out how to use its smaller budget to support enforcement, taxpayer service, cybersecurity, staffing, and old systems in a clear overall plan.</p><h3>Priority Area Two: Addressing the Tax Gap</h3><p>The tax gap is the difference between the amount of federal tax legally owed and the amount paid voluntarily and on time.</p><p>GAO described reducing that gap as a pressing IRS challenge. It also noted that tax-law enforcement has remained on GAO&#8217;s High-Risk List since 1990 because of its vulnerability to revenue loss, noncompliance, mismanagement, and operational weakness.</p><p>Audits are still a key part of how the IRS checks compliance. GAO found that insufficient staffing makes it hard for the IRS to handle complex audits, especially for high-income and wealthy taxpayers.</p><p>Those examinations often require specialized knowledge involving:</p><ul><li><p>Partnerships and pass-through entities.</p></li><li><p>Closely held businesses.</p></li><li><p>International transactions.</p></li><li><p>Trusts and estates.</p></li><li><p>Valuation issues.</p></li><li><p>Related-party transactions.</p></li><li><p>Complex ownership structures.</p></li></ul><p>GAO previously reported that the IRS had lost a significant number of employees capable of handling these cases. That problem existed before the workforce reductions that occurred in 2025.</p><p>GAO recommended that the IRS:</p><ul><li><p>Develop and implement a strategy to recruit personnel qualified to examine complex returns.</p></li><li><p>Train employees to handle high-income and high-wealth examinations.</p></li><li><p>Evaluate the effectiveness of the models used to select returns for audit.</p></li></ul><p>Choosing which returns to audit is important because the IRS has limited resources. Poor selection methods can waste skilled staff on less important cases and miss returns that are more likely to have problems.</p><p>GAO said that following these recommendations could strengthen enforcement, increase federal revenue, and ease the burden on taxpayers who already follow the rules.</p><p>The letter does not mean that any specific taxpayer is more likely to be audited. Instead, it points out problems in how the IRS chooses and reviews complex returns.</p><h3>Priority Area Three: Improving the Taxpayer Experience</h3><p>GAO also identified persistent weaknesses in IRS taxpayer service.</p><p>The IRS had planned numerous service projects using Inflation Reduction Act funding. Those projects were intended to improve taxpayer interactions with the agency, including access to assistance and the resolution of tax-account problems.</p><p>In April 2025, however, IRS officials told GAO that the office overseeing those efforts had been disbanded. The IRS was reassessing the projects because of funding and staffing constraints.</p><p>GAO identified several continuing problems:</p><ul><li><p>Limited evidence showing whether service initiatives improve taxpayer outcomes.</p></li><li><p>Inadequate performance measures.</p></li><li><p>Uncertain funding.</p></li><li><p>Staffing limitations.</p></li><li><p>Frequent changes in tax law.</p></li></ul><p>GAO recommended that the IRS establish an evidence-based system for evaluating taxpayer-service improvements. That system should connect each initiative to defined performance goals, measurable targets, and reliable data.</p><p>The goal is not just to track activity. Numbers like calls answered or accounts created do not always show that taxpayers got correct answers or had their issues resolved.</p><p>A better way to measure results would help the IRS decide which service projects deserve more funding, which ones need changes, and which ones should end.</p><h3>Additional Operational Concerns</h3><p>GAO linked the priority recommendations to several broader government-management risks.</p><p>Cybersecurity is very important because the IRS holds a lot of sensitive taxpayer and financial information. Decisions about updating systems affect both how the IRS serves people and how it protects data.</p><p>GAO also cited fragmentation and duplication within IRS operations. It specifically noted that IRS business units could improve coordination when using artificial intelligence.</p><p>The problem is not just that different IRS units might buy the same technology. If AI development is not coordinated, it can lead to mixed-up controls, extra costs, systems that do not work together, or conflicting uses of taxpayer data.</p><h3>Significance for Tax Professionals</h3><p>The letter does not change filing, reporting, or procedures right now. Its main value is in showing what the IRS can and cannot do.</p><p>Tax professionals should distinguish between three separate effects.</p><p>First, reduced funding and changes at the IRS may slow updates and service projects. Tax professionals might still see uneven service, slow problem-solving, and trouble reaching IRS staff.</p><p>Second, GAO still sees enforcement for high-income and wealthy taxpayers as a top priority. Even though staffing is lower, the main goal is to address complex cases of noncompliance.</p><p>Third, new IRS projects may need to show clear results. Congress and GAO will probably judge programs by what they actually achieve, not just by plans or spending.</p><h3>Limits of the Letter</h3><p>GAO does not direct IRS operations and cannot compel implementation of its recommendations.</p><p>The letter also does not:</p><ul><li><p>Announce a new IRS enforcement campaign.</p></li><li><p>Change audit-selection criteria.</p></li><li><p>Suspend any modernization project.</p></li><li><p>Restore or rescind IRS funding.</p></li><li><p>Establish taxpayer-service standards.</p></li><li><p>Impose deadlines on Treasury or the IRS.</p></li></ul><p>The letter&#8217;s real impact comes from Congress watching over the IRS. GAO said Congress might turn recommendations into laws, check on progress in hearings, or use funding to push for changes.</p><h3>The Takeaway</h3><p>The letter shows that the IRS is trying to update and enforce the tax system despite having less money, leadership changes, fewer staff, and weak ways to measure progress. There are no new rules for tax professionals right now, but the problems GAO described will keep affecting audits, case handling, and taxpayer service.</p>]]></content:encoded></item><item><title><![CDATA[D.C. Circuit upholds five-year sentence for mass disclosure of taxpayer records]]></title><description><![CDATA[United States v. Charles Edward Littlejohn. United States Court of Appeals for the District of Columbia Circuit. No. 24-3019. 2026.]]></description><link>https://taxcoda.com/p/dc-circuit-upholds-five-year-sentence</link><guid isPermaLink="false">https://taxcoda.com/p/dc-circuit-upholds-five-year-sentence</guid><dc:creator><![CDATA[Adam Parr]]></dc:creator><pubDate>Wed, 22 Jul 2026 11:28:05 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!5cG2!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fab017102-2a2e-414e-9b4e-111a7d2ed1c6_500x500.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>The D.C. Circuit ruled that courts can give the maximum sentence for unauthorized disclosure of tax records if the case involves deliberate targeting, many victims, sophisticated concealment, and ongoing harm&#8212;even if the defendant pleads guilty, cooperates, and has no prior record.</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://taxcoda.com/subscribe?coupon=acf79b7f&amp;utm_content=208015050&quot;,&quot;text&quot;:&quot;Get 60% off forever&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://taxcoda.com/subscribe?coupon=acf79b7f&amp;utm_content=208015050"><span>Get 60% off forever</span></a></p><h3>Holding</h3><p><span>The D.C. Circuit&nbsp;</span><a href="https://www.taxnotes.com/research/federal/court-documents/court-opinions-and-orders/d.c-circuit-affirms-tax-record-leaker-littlejohns-sentence/7wdr5"><span>upheld</span></a><span>&nbsp;Charles Littlejohn&#8217;s five-year prison sentence for unlawfully disclosing tax returns under section 7213(a)(1). The court found the sentence reasonable, even though it was higher than the recommended 12 to 18 months.</span></p><h3>Why It Matters</h3><ul><li><p>This decision gives courts more freedom to impose longer sentences in large tax disclosure cases when the Guidelines do not fully reflect the seriousness or impact of the conduct.</p></li><li><p>The court saw the number of victims, targeting a sitting president, trying to influence policy and an election, and the risk of more disclosures as separate reasons to increase the sentence.</p></li><li><p>Pleading guilty, cooperating, accepting responsibility, and having no criminal record do not stop a court from giving the maximum sentence if it explains why other factors are more important.</p></li><li><p>The opinion explains that an upward departure under the Guidelines is different from an upward variance under section 3553(a). Courts can use both if they address different aspects of the case.</p></li><li><p>The ruling does not mean every unauthorized disclosure deserves the maximum sentence. The court stressed that Littlejohn&#8217;s case was unusual because of its scale, planning, political motive, and ongoing effects.</p></li></ul><h3>Key Facts</h3><p><a href="https://open.substack.com/pub/taxcoda/p/charles-littlejohn-appeals-five-year?r=27e79&amp;utm_campaign=post-expanded-share&amp;utm_medium=web">Charles Littlejohn</a> worked as a contractor with access to IRS systems.</p><p>He sought the position in part to obtain and disclose President Donald Trump&#8217;s tax information. He used broad search parameters to gather the information without triggering detection controls.</p><p>Littlejohn transferred the information through a private website, moved it to a personal computer, and stored copies in multiple locations. He later provided Trump&#8217;s tax information to a New York Times reporter and assisted with the reporter&#8217;s analysis.</p><p>The New York Times published articles based on the information shortly before the 2020 presidential election.</p><p>Littlejohn also obtained tax information concerning approximately 600 entities and about 7,600 wealthy individuals. He disclosed that information to ProPublica.</p><p>ProPublica used information concerning at least 152 taxpayers in approximately 50 articles. It retained additional unpublished taxpayer information at the time of sentencing.</p><p>Victims reported reputational damage, lost business, threats, emotional harm, and concerns for their families&#8217; safety. Taxpayers whose information had not yet been published remained uncertain whether ProPublica might disclose it later.</p><p>Littlejohn attempted to conceal his conduct. He destroyed virtual machines, canceled the private website&#8217;s domain registration, and deleted nearly all files from his IRS laptop before returning it.</p><p>The government charged Littlejohn with one count of unauthorized disclosure of tax returns and return information under section 7213(a)(1).</p><p>He pleaded guilty.</p><p>The advisory Guidelines calculation, after an upward departure, produced a range of 12 to 18 months.</p><p>The district court imposed:</p><ul><li><p>Five years in prison</p></li><li><p>Three years of supervised release</p></li><li><p>300 hours of community service</p></li><li><p>A $5,000 fine</p></li><li><p>A $100 special assessment</p></li></ul><p>Five years was the statutory maximum.</p><h3>Statutory and Sentencing Framework</h3><p>Section 7213(a)(1) makes it a felony for certain federal employees and other covered persons to willfully disclose tax returns or return information without authorization.</p><p>Return information includes taxpayer-identifying and tax-related information held by the IRS in connection with a filed return or potential tax liability.</p><p>Federal sentencing involves two related but distinct concepts.</p><p>An upward departure changes the advisory Guidelines range based on circumstances recognized in the Guidelines.</p><p>An upward variance imposes a sentence outside the final Guidelines range based on the broader sentencing factors in 18 U.S.C. section 3553(a).</p><p>Section 3553(a) requires the court to consider:</p><ul><li><p>The nature and circumstances of the offense</p></li><li><p>The defendant&#8217;s history and characteristics</p></li><li><p>The seriousness of the offense</p></li><li><p>Respect for the law</p></li><li><p>Just punishment</p></li><li><p>Deterrence</p></li><li><p>Protection of the public</p></li><li><p>Available sentences</p></li><li><p>The advisory Guidelines and policy statements</p></li><li><p>Avoidance of unwarranted sentencing disparities</p></li></ul><p>An appellate court reviews the substantive reasonableness of a sentence for abuse of discretion. It does not replace the district court&#8217;s weighing of the sentencing factors with its own.</p><h3>Arguments</h3><p>Taxpayer argued:</p><ul><li><p>The district court predetermined the sentence before the sentencing hearing.</p></li><li><p>The court improperly concluded that the offense was politically motivated and directed at a sitting president.</p></li><li><p>The court incorrectly characterized the conduct as an attack on constitutional democracy.</p></li><li><p>The court improperly found that Littlejohn intended to harm thousands of taxpayers.</p></li><li><p>The court considered a letter from 25 members of Congress requesting the maximum sentence.</p></li><li><p>The court failed to explain adequately why it imposed a sentence above the Guidelines range.</p></li><li><p>The court relied on factors already accounted for through the upward departure.</p></li><li><p>The five-year sentence created an unwarranted disparity compared with sentences in other disclosure cases.</p></li></ul><p>Government argued:</p><ul><li><p>The district court kept an open mind and considered both aggravating and mitigating evidence.</p></li><li><p>Littlejohn&#8217;s own statements supported the findings that he acted for political and policy-related purposes.</p></li><li><p>The congressional letter had no effect on the sentencing decision.</p></li><li><p>The district court gave detailed reasons for imposing the statutory maximum.</p></li><li><p>The Guidelines did not fully account for the scale, sophistication, targeting, and continuing effects of the conduct.</p></li><li><p>The comparison cases involved fewer victims, less serious conduct, or materially different mitigating circumstances.</p></li></ul><h3>Court&#8217;s Reasoning</h3><ul><li><p>The district court did not predetermine the sentence. It expressed sympathy for Littlejohn, reviewed letters supporting him, acknowledged his positive personal characteristics, questioned both parties, and stated that it had not decided the sentence before hearing argument.</p></li><li><p>The district court&#8217;s off-the-record communications should have occurred on the record. The appellate court nevertheless found no prejudice and no evidence that the court had already fixed the sentence.</p></li><li><p>The record supported the finding that Littlejohn acted for political purposes. He stated that he wanted voters to see the president&#8217;s tax returns before voting and wanted the public to understand how wealthy taxpayers minimized their tax burdens.</p></li><li><p>The district court reasonably treated the conduct as targeting a sitting president and attempting to influence an election through unlawful activity.</p></li><li><p>The court also reasonably concluded that the offense harmed confidence in the impartial administration of government institutions.</p></li><li><p>Littlejohn&#8217;s own admissions supported the finding that he intentionally violated the privacy of thousands of taxpayers. The district court did not need proof that he intended every specific business, reputational, or personal consequence experienced by each victim.</p></li><li><p>The district court did not rely on the congressional letter. It expressly stated that the letter had no effect on the sentence and contained no material information that was not already in the record.</p></li><li><p>The district court adequately explained the upward departure. The disclosure involved a substantial number of individuals, caused or risked substantial nonmonetary harm, and produced a significant invasion of privacy.</p></li><li><p>The court separately justified the upward variance. It relied on Littlejohn&#8217;s targeting of the president, the targeting of thousands of other taxpayers, the calculated and multi-year nature of the scheme, his sophisticated efforts to avoid detection, and the continuing risk that unpublished information could appear in future articles.</p></li><li><p>The departure and variance did not improperly duplicate the same facts. The departure primarily addressed the large number of affected taxpayers and the invasion of privacy. The variance addressed additional aggravating circumstances, including political targeting, technical sophistication, deliberate concealment, and ongoing harm.</p></li><li><p>Littlejohn&#8217;s professional experience increased the seriousness of the offense. His training and access gave him detailed knowledge of taxpayer confidentiality requirements and the consequences of unauthorized disclosure.</p></li><li><p>The district court considered his lack of criminal history, guilty plea, cooperation, acceptance of responsibility, and positive personal relationships. It had discretion to conclude that those considerations did not outweigh the seriousness of the offense and the need for deterrence.</p></li><li><p>The court could impose the statutory maximum without finding that Littlejohn was the most culpable person who could violate section 7213. A statutory maximum necessarily applies to defendants whose conduct may differ in degree.</p></li><li><p>General deterrence carried substantial weight because Littlejohn used trusted access to government systems to obtain confidential taxpayer information. The district court could reasonably conclude that a severe sentence was necessary to deter other employees and contractors from using government access to pursue personal or political objectives.</p></li><li><p>The district court acknowledged that public protection and correctional treatment weighed against an upward variance. It nevertheless found that the remaining factors justified the maximum sentence.</p></li><li><p>Littlejohn failed to identify a sufficiently similar case involving comparable scale and circumstances. Most cited cases involved fewer records, fewer victims, different offenses, greater cooperation, mental health considerations, or other material differences.</p></li><li><p>None of the comparison cases involved disclosure of a sitting president&#8217;s tax information together with information concerning thousands of additional taxpayers.</p></li></ul><h3>Procedural Reasonableness</h3><p>A sentence is procedurally unreasonable when the district court commits a significant error in calculating the Guidelines, treating the Guidelines as mandatory, relying on clearly erroneous facts, failing to consider the statutory factors, or failing to explain the sentence.</p><p>The D.C. Circuit found no such error.</p><p>The district court correctly calculated the Guidelines range, considered the relevant sentencing factors, addressed the parties&#8217; arguments, and explained why the statutory maximum better reflected the offense than the advisory range.</p><p>The appellate court criticized the use of off-the-record communications but found that those communications showed uncertainty rather than prejudgment. Littlejohn also failed to object at the time.</p><h3>Substantive Reasonableness</h3><p>A sentence is substantively unreasonable only when it falls outside the range of permissible outcomes under the facts and sentencing law.</p><p>The D.C. Circuit held that the five-year sentence remained within that range.</p><p>The opinion treated Littlejohn&#8217;s conduct as materially more serious than a routine disclosure offense because it involved:</p><ul><li><p>Entry into government service with an intent to obtain confidential information</p></li><li><p>A multi-year plan</p></li><li><p>Deliberate targeting of a president</p></li><li><p>Disclosure involving thousands of taxpayers</p></li><li><p>Coordination with media organizations</p></li><li><p>Technical measures designed to evade detection</p></li><li><p>Destruction of evidence</p></li><li><p>Concrete harm to identified victims</p></li><li><p>Continuing uncertainty for taxpayers whose information remained unpublished</p></li></ul><p>The court viewed the sentence as severe but not outside the district court&#8217;s discretion.</p><h3>Limits of the Decision</h3><p>The decision does not create a presumption that section 7213 violations require a five-year sentence.</p><p>It does not hold that disclosure to a journalist automatically supports an upward variance.</p><p>It does not hold that political motivation alone justifies the statutory maximum.</p><p>It does not eliminate the need for a sentencing court to calculate the Guidelines correctly or explain why the Guidelines do not adequately address the offense.</p><p>The result depended on the combined effect of scale, intent, planning, concealment, victim harm, and continuing exposure.</p><p>The opinion also leaves the government&#8217;s charging decision largely outside the appellate issue. The district court questioned why prosecutors charged only one count, but the D.C. Circuit reviewed the sentence imposed on that count rather than the wisdom of the charging arrangement.</p><h3>Result</h3><p>The D.C. Circuit affirmed the five-year prison sentence, supervised release, community service requirement, fine, and special assessment.</p><h3>The Takeaway</h3><p>Tax professionals, government contractors, and advisers who handle protected taxpayer information should see this decision as a clear warning. Courts may give the maximum sentence when someone with inside access deliberately discloses information on a large scale, especially if the effects go beyond the first release.</p><h4>List of Citations</h4><ul><li><p><strong>26 U.S.C. &#167;7213(a)(1)</strong>: Criminalizes willful unauthorized disclosure of tax returns and return information by covered persons.</p></li><li><p><strong>18 U.S.C. &#167;3553(a)</strong>: Lists the factors federal courts must consider when imposing a criminal sentence.</p></li><li><p><strong>U.S.S.G. &#167;2H3.1, Application Note 5</strong>: Authorizes an upward departure for disclosures involving substantial numbers of individuals, substantial nonmonetary harm, or substantial invasions of privacy.</p></li><li><p><strong>United States v. Miller, 35 F.4th 807 (D.C. Cir. 2022)</strong>: Provides the clear-error standard for factual findings.</p></li><li><p><strong>United States v. Flores, 912 F.3d 613 (D.C. Cir. 2019)</strong>: Addresses review of preserved and unpreserved procedural sentencing objections.</p></li><li><p><strong>United States v. Fry, 851 F.3d 1329 (D.C. Cir. 2017)</strong>: Applies abuse-of-discretion review to substantive sentencing challenges.</p></li><li><p><strong>United States v. Abney, 957 F.3d 241 (D.C. Cir. 2020)</strong>: Explains that a sentencing judge must approach the decision with an open mind.</p></li><li><p><strong>United States v. Pyles, 862 F.3d 82 (D.C. Cir. 2017)</strong>: Recognizes that active questioning may show that a judge considered the parties&#8217; positions.</p></li><li><p><strong>United States v. Brown, 857 F.3d 403 (D.C. Cir. 2017)</strong>: Requires specific and legitimate grounds for a sentence above the Guidelines.</p></li><li><p><strong>United States v. Williamson, 903 F.3d 124 (D.C. Cir. 2018)</strong>: States the standard for determining whether a sentence is substantively unreasonable.</p></li><li><p><strong>United States v. Johnson, 934 F.3d 498 (6th Cir. 2019)</strong>: Explains that a statutory maximum need not be reserved for a single hypothetical category of the most culpable offenders.</p></li></ul>]]></content:encoded></item><item><title><![CDATA[Tax Court allows IRS levy after erroneous refund caused by faulty assessment]]></title><description><![CDATA[Hough Beck & Baird Inc. v. Commissioner. United States Tax Court. No. 19128-24L. 2026.]]></description><link>https://taxcoda.com/p/tax-court-allows-irs-levy-after-erroneous</link><guid isPermaLink="false">https://taxcoda.com/p/tax-court-allows-irs-levy-after-erroneous</guid><dc:creator><![CDATA[Adam Parr]]></dc:creator><pubDate>Wed, 15 Jul 2026 11:11:04 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!5cG2!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fab017102-2a2e-414e-9b4e-111a7d2ed1c6_500x500.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>If the IRS&#8217;s original assessment significantly understated a taxpayer&#8217;s actual liability, it can recover an erroneous refund by making a supplemental assessment and using its usual collection methods.</p><h3>Holding</h3><p>The Tax Court decided that the IRS was right to make a supplemental assessment under &#167;6204 after it mistakenly set Hough Beck &amp; Baird Inc.&#8217;s employment tax liability at zero. The court ruled in favor of the IRS and allowed the proposed levy.</p><h3>Why It Matters</h3><ul><li><p>The decision confirms that the IRS need not file an erroneous refund suit under &#167;7405 to recover money it mistakenly returned to a taxpayer.</p></li><li><p>The method of recovery depends on the source of the error. The IRS may use a supplemental assessment when the original assessment materially misstated the tax liability.</p></li><li><p>A different rule may apply when the IRS correctly assessed and fully collected the tax but later issued a refund because of an unrelated payment-processing or accounting error.</p></li><li><p>The decision gives the IRS access to the ordinary administrative collection process, including liens and levies, when a timely supplemental assessment corrects a materially defective original assessment.</p></li><li><p>The holding does not authorize reassessment of every erroneous refund. The IRS must identify a material defect in the original assessment and act within the applicable assessment period.</p></li></ul><p>The decision is consequential because the Tax Court had not directly resolved when an IRS calculation error makes an assessment &#8220;imperfect&#8221; under &#167;6204. The Court adopted the approach already used by the Second, Seventh, and Ninth Circuits.</p><p>At the same time, the outcome largely follows established appellate precedent. Hough Beck &amp; Baird was based in Washington, so an appeal would ordinarily go to the Ninth Circuit. The Ninth Circuit had already approved a supplemental assessment in materially similar circumstances.</p><h3>Key Facts</h3><p>Hough Beck &amp; Baird Inc. is a Seattle landscape architecture firm.</p><p>The company timely filed Form 941 for the quarter ending March 31, 2021. It correctly reported federal employment tax of $121,003 and made three deposits totaling the same amount.</p><p>The company did not claim an employment tax credit.</p><p>The IRS nevertheless treated the company as entitled to a credit. It assessed the company&#8217;s employment tax liability as zero and treated the $121,003 in deposits as an overpayment.</p><p>The IRS refunded $121,003 to the company, plus $89 of interest.</p><p>After learning about the refund, the company&#8217;s accountant contacted the IRS. An IRS representative stated that the refund resulted from COVID-related employee retention credits available to certain employers.</p><p>In May 2023, the IRS sent Letter 6552 stating that the company might have received a refund to which it was not entitled. The company did not respond or repay the amount.</p><p>On July 17, 2023, the IRS reversed the credit and made a supplemental assessment of $121,003. The IRS also charged $12,582 of interest as of that date.</p><p>The company did not pay the assessed balance.</p><p>In April 2024, the IRS issued a final notice of intent to levy. The company requested a collection due process hearing and disputed the underlying liability.</p><p>The IRS Independent Office of Appeals sustained the proposed levy. The company then petitioned the Tax Court.</p><h3>Statutory Framework</h3><p>Section 6201 authorizes the IRS to determine and assess taxes imposed by the Internal Revenue Code.</p><p>An assessment records the taxpayer&#8217;s liability in the government&#8217;s accounts. When the IRS rejects the liability shown on a return, it may calculate and record a different amount.</p><p>Section 6204 permits the IRS to make a supplemental assessment when an existing assessment is &#8220;imperfect or incomplete in any material respect.&#8221;</p><p>A supplemental assessment generally must comply with the three-year assessment limitation period under &#167;6501.</p><p>After making a timely assessment, the IRS generally has ten years to collect the liability under &#167;6502.</p><p>Section 7405 separately authorizes the government to file a civil action to recover an erroneous refund. Different limitation periods apply to those suits under &#167;6532(b).</p><p>The dispute concerned which recovery mechanism applied. The company argued that the IRS had issued an erroneous refund after the tax was correctly assessed and paid. The IRS argued that its original assessment was materially defective because it recorded the liability as zero.</p><h3>Arguments</h3><p>Taxpayer argued:</p><ul><li><p>The company correctly reported and fully paid its employment tax liability.</p></li><li><p>The original assessment was complete and accurate in all material respects.</p></li><li><p>The IRS later returned money that the company had already paid.</p></li><li><p>Once a correctly assessed tax has been paid, the liability is extinguished.</p></li><li><p>The refund created a separate erroneous refund claim rather than a continuing employment tax liability.</p></li><li><p>The government could recover the money only by filing a civil erroneous refund action under &#167;7405.</p></li><li><p>Because the government did not file such an action, the IRS could not collect the amount through a levy.</p></li></ul><p>Government argued:</p><ul><li><p>The IRS did not correctly assess the company&#8217;s reported employment tax liability.</p></li><li><p>The IRS mistakenly applied a credit and assessed the liability as zero.</p></li><li><p>The zero assessment understated the actual liability by the entire $121,003 reported on the return.</p></li><li><p>That error made the original assessment imperfect in a material respect.</p></li><li><p>Section 6204 authorized the IRS to correct the error through a supplemental assessment.</p></li><li><p>The timely supplemental assessment supported the IRS&#8217;s administrative collection action.</p></li></ul><h3>Court&#8217;s Reasoning</h3><ul><li><p>The IRS recorded the company&#8217;s original employment tax assessment as zero. It did not merely issue a refund after correctly assessing the reported liability.</p></li><li><p>The zero assessment resulted from the IRS&#8217;s mistaken application of an employment tax credit that the company had never claimed.</p></li><li><p>The assessment understated the company&#8217;s liability by $121,003, which represented the full amount shown on the company&#8217;s return.</p></li><li><p>An assessment that records no liability when the taxpayer actually owes $121,003 contains a material defect.</p></li><li><p>Section 6204 does not limit supplemental assessments to taxpayer errors or newly discovered facts. The provision also applies when the IRS itself causes the material defect.</p></li><li><p>The Ninth Circuit&#8217;s decision in <em>Brookhurst, Inc. v. United States</em> closely matched the facts. There, the IRS mistakenly assessed employment taxes at an amount below the amount reported and paid, issued a refund, and later made a supplemental assessment. The Ninth Circuit upheld the reassessment and collection by levy.</p></li><li><p>The Seventh Circuit reached a similar result in <em>United States v. Frontone</em>. The IRS miscalculated the taxpayers&#8217; liability, issued a refund, and later made an accurate supplemental assessment. The Court treated the continuing claim as one for the original tax liability.</p></li><li><p>The Second Circuit also recognized in <em>Johnson v. United States</em> that the IRS may use a supplemental assessment to replace an invalid or defective original assessment.</p></li><li><p>These cases establish that an IRS calculation error can make an assessment imperfect or incomplete in a material respect.</p></li><li><p>The company relied heavily on <em>O&#8217;Bryant v. United States</em>, but the Tax Court found that case materially different.</p></li><li><p>In <em>O&#8217;Bryant</em>, the IRS correctly assessed the negotiated tax liability and the taxpayers paid it in full. The IRS later posted the payment twice and issued a refund because its records incorrectly showed an overpayment.</p></li><li><p>The error in <em>O&#8217;Bryant</em> concerned the posting of a payment, not the assessment amount. The original assessment remained correct.</p></li><li><p>Hough Beck &amp; Baird&#8217;s account presented the opposite sequence. The IRS first calculated and recorded the tax liability incorrectly, then issued a refund because the defective assessment created an apparent overpayment.</p></li><li><p>The distinction determines the available recovery mechanism. A refund caused by a defective assessment may support a supplemental assessment. A refund caused solely by a payment-posting error may require an erroneous refund action.</p></li><li><p>The company&#8217;s original payment did not extinguish the liability because the IRS returned the same amount after incorrectly recording the liability.</p></li><li><p>The ultimate source of the government&#8217;s claim remained the company&#8217;s first-quarter 2021 employment tax liability. The government was not attempting to collect a new or unrelated obligation.</p></li><li><p>The IRS made the supplemental assessment within the applicable assessment period.</p></li><li><p>The supplemental assessment therefore supported the proposed levy under the ordinary collection rules.</p></li></ul><h3>Result</h3><p>The Tax Court granted the IRS&#8217;s motion for summary judgment, denied the company&#8217;s cross-motion, and sustained the proposed levy.</p><h3>The Takeaway</h3><p>Tax professionals should first figure out why the IRS issued an erroneous refund before assuming a lawsuit is needed. If the assessment was seriously wrong, the IRS may be able to fix it under &#167;6204 and use its usual collection process.</p><p>This decision does not remove the difference between reassessments and erroneous refund lawsuits. The key difference now depends on the type of accounting error, not just on whether the taxpayer got money from the IRS.</p><h4>List of Citations</h4><ul><li><p>&#167;6201: Authorizes the IRS to determine and assess federal taxes.</p></li><li><p>&#167;6203: Governs the method of assessment by recording the taxpayer&#8217;s liability.</p></li><li><p>&#167;6204(a): Authorizes a supplemental assessment when an assessment is materially imperfect or incomplete.</p></li><li><p>&#167;6501(a): Generally requires the IRS to assess tax within three years after the return is filed.</p></li><li><p>&#167;6502(a)(1): Generally gives the IRS ten years after assessment to collect the liability by levy or Court proceeding.</p></li><li><p>&#167;7405: Authorizes the government to bring a civil action to recover an erroneous refund.</p></li><li><p>&#167;6532(b): Establishes the limitation period for erroneous refund suits.</p></li><li><p><em>United States v. Galletti</em>, 541 U.S. 114 (2004): Explains that an assessment records the taxpayer&#8217;s liability in the government&#8217;s books.</p></li><li><p><em>Brookhurst, Inc. v. United States</em>, 931 F.2d 554 (9th Cir. 1991): Upholds a supplemental assessment after the IRS materially understated employment tax and issued a refund.</p></li><li><p><em>United States v. Frontone</em>, 383 F.3d 656 (7th Cir. 2004): Treats a refund resulting from an understated assessment as part of the original tax liability rather than as a separate refund claim.</p></li><li><p><em>Johnson v. United States</em>, 123 F.3d 700 (2d Cir. 1997): Recognizes the IRS&#8217;s authority to make a supplemental assessment after a defective original assessment.</p></li><li><p><em>O&#8217;Bryant v. United States</em>, 49 F.3d 340 (7th Cir. 1995): Distinguishes an erroneous refund resulting from a duplicate payment posting from a refund resulting from an incorrect assessment.</p></li><li><p><em>Estate of Wilbanks v. Commissioner</em>, T.C. Memo. 1991-45: Applies &#167;6204 when an earlier assessment omitted a material addition to tax.</p></li><li><p><em>Golsen v. Commissioner</em>, 54 T.C. 742 (1970): Requires the Tax Court to follow controlling precedent from the appellate circuit to which the case is appealable.</p></li></ul>]]></content:encoded></item><item><title><![CDATA[Court finds Trump IRS lawsuit lacked a genuine dispute and imposes sanctions]]></title><description><![CDATA[President Donald J. Trump v. IRS. United States District Court for the Southern District of Florida No. 1:26-cv-20609.]]></description><link>https://taxcoda.com/p/court-finds-trump-irs-lawsuit-lacked</link><guid isPermaLink="false">https://taxcoda.com/p/court-finds-trump-irs-lawsuit-lacked</guid><dc:creator><![CDATA[Adam Parr]]></dc:creator><pubDate>Tue, 14 Jul 2026 11:04:02 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!5cG2!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fab017102-2a2e-414e-9b4e-111a7d2ed1c6_500x500.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>A federal Court decided that President Trump could not create an Article III controversy by suing executive agencies he controlled. The Court also imposed sanctions after finding the lawsuit was used to support a settlement the parties had already agreed on.</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://taxcoda.com/subscribe?coupon=acf79b7f&amp;utm_content=206980228&quot;,&quot;text&quot;:&quot;Get 60% off forever&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://taxcoda.com/subscribe?coupon=acf79b7f&amp;utm_content=206980228"><span>Get 60% off forever</span></a></p><h3>Holding</h3><p>The U.S. District Court for the Southern District of Florida <a href="https://www.taxnotes.com/research/federal/court-documents/court-opinions-and-orders/court-holds-there-was-no-controversy-trump-suit-against-irs/7wdcj">found</a> that President Trump, the IRS, and the Treasury Department were not truly on opposing sides, which is required for an Article III case. The court said the <a href="https://open.substack.com/pub/taxcoda/p/trump-and-trump-organization-voluntarily?r=27e79&amp;utm_campaign=post-expanded-share&amp;utm_medium=web">lawsuit</a> was filed for the wrong reasons, gave nonmonetary sanctions under Rule 11, and allowed for possible monetary sanctions to cover costs caused by the parties&#8217; actions.</p><h3>Why It Matters</h3><ul><li><p><strong>This is not a routine jurisdictional ruling.</strong> The Court concluded that a sitting President cannot establish a genuine federal controversy by suing agencies that remain subject to his supervision and control.</p></li><li><p><strong>The order limits the legal value of the purported settlement.</strong> The parties may not cite or use the agreement as evidence of a settlement reached in the federal case.</p></li><li><p><strong>The Court treated the litigation process itself as sanctionable conduct.</strong> The voluntary dismissal ended the merits proceeding but did not eliminate the Court&#8217;s authority to examine Rule 11 violations and other abuses of the judicial process.</p></li><li><p><strong>The ruling does not decide whether every provision of the private agreement is independently valid.</strong> It addresses the absence of a judicial controversy, the improper use of the lawsuit, and the parties&#8217; ability to characterize the agreement as a court-connected settlement.</p></li></ul><h3>Key Facts</h3><p>Charles Littlejohn, an IRS contractor employed by Booz Allen Hamilton, unlawfully <a href="https://open.substack.com/pub/taxcoda/p/charles-littlejohn-appeals-five-year?r=27e79&amp;utm_campaign=post-expanded-share&amp;utm_medium=web">disclosed</a> tax information associated with President Trump and thousands of other taxpayers. He pleaded guilty in 2023 and received a five-year prison sentence in January 2024.</p><p>President Trump, Donald Trump Jr., Eric Trump, and the Trump Organization <a href="https://open.substack.com/pub/taxcoda/p/trump-family-sues-the-irs-over-unauthorized?r=27e79&amp;utm_campaign=post-expanded-share&amp;utm_medium=web">sued</a> the IRS and Treasury Department on January 29, 2026. They sought at least $10 billion under IRC &#167;7431, which permits taxpayers to recover damages for unauthorized inspections or disclosures of tax return information.</p><p>The complaint arrived more than two years after an attorney representing Trump appeared at Littlejohn&#8217;s October 2023 plea hearing and identified Trump as a victim. IRC &#167;7431 generally requires a taxpayer to file suit within two years after discovering the unauthorized inspection or disclosure.</p><p>The government never filed an appearance, an answer, a motion to dismiss, or any other substantive response. Instead, the parties requested additional time to discuss settlement.</p><p>The Court questioned whether it had subject matter jurisdiction because President Trump headed the executive branch and exercised authority over the defendant agencies. It ordered the parties to brief whether a genuine case or controversy existed.</p><p>Neither side submitted the required jurisdictional briefing. Plaintiffs instead voluntarily dismissed the case with prejudice on May 18, 2026.</p><p>The Justice Department then announced an agreement that included:</p><ul><li><p>A formal apology to the plaintiffs.</p></li><li><p>A proposed $1.776 billion Anti-Weaponization Fund financed through the Treasury Judgment Fund.</p></li><li><p>A separate Justice Department release purporting to protect Trump, his relatives, affiliated businesses, and others from broad categories of existing and potential government claims.</p></li><li><p>Restrictions on future IRS audits and investigations involving the plaintiffs.</p></li></ul><p>Acting Attorney General Todd Blanche later told Congress that the Anti-Weaponization Fund would not proceed. He did not provide the Court with the settlement for review before the dismissal.</p><p>Thirty-five former federal judges and other nonparty movants asked the Court to reopen the matter or grant related relief. They alleged that the litigation and settlement resulted from collusion and constituted a fraud on the Court.</p><p>The Court ordered the plaintiffs to respond to questions regarding collusion, adverse conduct, deception, and possible misuse of the judicial process.</p><h3>Procedural Framework</h3><p>Article III limits federal judicial power to genuine cases and controversies. A case must involve parties with adverse legal interests. Nominally placing parties on opposite sides of a caption does not establish adverseness when one party controls both sides of the litigation.</p><p>Federal Rule of Civil Procedure 41(a)(1) permits a plaintiff to voluntarily dismiss an action before the opposing party files an answer or motion for summary judgment. The dismissal generally ends the Court&#8217;s authority over the merits but does not eliminate jurisdiction over collateral matters such as sanctions, costs, attorney fees, and contempt.</p><p>Federal Rule of Civil Procedure 11 requires attorneys and parties to certify that filings serve a proper purpose and have a reasonable legal and factual basis. A Court may impose sanctions when a party files an action to achieve an improper objective rather than obtain a legitimate judicial resolution.</p><p>Federal courts also possess inherent authority to sanction bad-faith conduct that abuses the judicial process. Unlike Rule 11, this authority does not depend entirely on the timing and procedural requirements of a sanctions motion.</p><p>IRC &#167;7431 authorizes damages for unauthorized inspections or disclosures of return information. The statute generally provides statutory damages of $1,000 for each unauthorized act, plus actual and punitive damages when the statutory requirements apply.</p><p>IRC &#167;7217 prohibits specified executive branch officials from requesting that the IRS begin or terminate an audit or investigation of a particular taxpayer.</p><h3>Arguments</h3><p>Taxpayer argued:</p><ul><li><p>The voluntary dismissal automatically ended the Court&#8217;s jurisdiction.</p></li><li><p>The Court could not continue reviewing the underlying dispute after plaintiffs dismissed the case.</p></li><li><p>The lawsuit involved ordinary settlement activity between parties that had the power to resolve their disputes without judicial involvement.</p></li><li><p>Donald Trump Jr., Eric Trump, and the Trump Organization held claims distinct from President Trump&#8217;s official authority over the executive branch.</p></li><li><p>The parties remained sufficiently adverse because plaintiffs sought damages from government agencies.</p></li><li><p>Rule 11 restricted the Court&#8217;s ability to impose sanctions after the voluntary dismissal.</p></li><li><p>The nonparty movants raised political grievances rather than legally cognizable objections.</p></li></ul><p>Government argued:</p><ul><li><p>The government filed no appearance or substantive position in the litigation.</p></li><li><p>Justice Department officials defended the agreement publicly but did not present the agreement or the government&#8217;s legal analysis to the Court.</p></li><li><p>Acting Attorney General Blanche asserted that the dismissal left no judge or mechanism available to review the agreement.</p></li></ul><p>Nonparty movants argued:</p><ul><li><p>President Trump controlled the officials of the IRS, the Treasury Department, and the Justice Department who acted for the defendants.</p></li><li><p>The parties filed the lawsuit to create legal cover for an agreement they had already decided to reach.</p></li><li><p>The government abandoned defenses that it had asserted in similar unauthorized disclosure cases.</p></li><li><p>The proposed settlement provided remedies far beyond the relief available under IRC &#167;7431.</p></li><li><p>The litigation lacked genuine adverseness and therefore never presented an Article III case or controversy.</p></li><li><p>Plaintiffs and government officials used the lawsuit to give apparent judicial legitimacy to an agreement involving taxpayer funds, audit restrictions, and broad governmental releases.</p></li></ul><h3>Court&#8217;s Reasoning</h3><ul><li><p><strong>President Trump controlled the defendant agencies.</strong> The Constitution places executive power in the President. The Treasury Department and IRS operate within the executive branch, and their senior officials remain subject to presidential supervision and removal authority.</p></li><li><p><strong>The administration&#8217;s executive order reinforced that control.</strong> Executive Order 14215 required executive branch employees to follow legal interpretations established by the President and Attorney General, including positions advanced in litigation. The Court concluded that the order restricted the government defendants&#8217; ability to take a litigation position contrary to President Trump.</p></li><li><p><strong>The parties&#8217; conduct showed no genuine adverseness.</strong> The IRS and Treasury Department never appeared, defended the case, disputed damages, raised the statute of limitations, or challenged whether the government was the proper defendant. The same agencies had vigorously asserted those defenses in similar disclosure litigation brought by private taxpayers.</p></li><li><p><strong>The other plaintiffs did not create an independent controversy.</strong> Donald Trump Jr., Eric Trump, and the Trump Organization shared counsel, interests, ownership relationships, and settlement objectives with President Trump. They did not present distinct positions that restored a sense of adversity.</p></li><li><p><strong>The settlement extended far beyond the pleaded tax disclosure claims.</strong> The agreement proposed a $1.776 billion fund for undefined weaponization and lawfare claims involving unidentified third parties. A separate release purported to restrict audits, investigations, and other government actions involving the plaintiffs and their affiliates.</p></li><li><p><strong>The timing supported an improper-purpose finding.</strong> Plaintiffs filed the case after President Trump returned to office. The government remained silent. The parties dismissed the action shortly after the Court ordered jurisdictional briefing. They then announced the settlement without submitting it for judicial review.</p></li><li><p><strong>The Court viewed the lawsuit as a mechanism for legitimizing a predetermined agreement.</strong> Because the parties lacked adverse interests, the lawsuit could not provide the judicial foundation the agreement appeared designed to claim.</p></li></ul><h3>Article III Adverseness</h3><p>The Court treated adverseness as a constitutional requirement rather than a discretionary procedural consideration.</p><p>A federal Court may decide only disputes between parties with genuinely conflicting legal interests. Courts must examine the parties&#8217; actual relationship and cannot rely solely on labels such as plaintiff and defendant.</p><p>The Court applied decisions holding that Article III jurisdiction does not exist when:</p><ul><li><p>The parties seek the same result.</p></li><li><p>One party controls the nominal opposing party.</p></li><li><p>The litigation asks a Court to approve or validate an agreed outcome rather than resolve an actual dispute.</p></li><li><p>A party effectively operates as the controlling litigant on both sides.</p></li></ul><p>President Trump served as both the lead plaintiff and the official responsible for supervising the executive agencies named as defendants. The Court concluded that this authority prevented the IRS and Treasury Department from functioning as genuinely adverse litigants.</p><p>The Court therefore found that the action never presented a case or controversy and that no party could properly obtain judicial approval of the settlement through the proceeding.</p><h3>Rule 11 Sanctions</h3><p>The voluntary dismissal did not prevent the Court from considering sanctions. Rule 11 violations occur when a party files the offending pleading. A later dismissal does not erase the violation.</p><p>The Court found that plaintiffs used the lawsuit for an improper purpose. It concluded that the action sought to confer judicial legitimacy on a settlement rather than to obtain an adjudication of a genuine dispute.</p><p>Rule 11 limited the Court&#8217;s ability to impose monetary sanctions on its own initiative because plaintiffs dismissed the case before the Court issued a sanctions show-cause order. The Court therefore imposed nonmonetary sanctions under Rule 11:</p><ul><li><p>Attorney Alejandro Brito was referred to The Florida Bar for possible disciplinary review.</p></li><li><p>Daniel Epstein may not obtain pro hac vice admission in the Southern District of Florida for one year or until further Court order.</p></li><li><p>The parties may not describe, introduce, cite, or rely on the purported agreement as evidence of a settlement reached in the federal case.</p></li></ul><p>The final restriction applies to President Trump, Donald Trump Jr., Eric Trump, the Trump Organization, the IRS, the Treasury Department, and related agents, affiliates, representatives, and persons acting under their control.</p><h3>Inherent-Authority Sanctions</h3><p>The Court separately invoked its inherent authority, which permits sanctions for subjective bad faith and broader abuses of the judicial process.</p><p>The Court found that plaintiffs acted in bad faith by:</p><ul><li><p>Filing claims that appeared untimely.</p></li><li><p>Seeking damages with no demonstrated relationship to the remedies authorized by IRC &#167;7431.</p></li><li><p>Using the litigation to obtain benefits unavailable through an ordinary adjudication.</p></li><li><p>Dismissing the case after the Court raised jurisdictional questions.</p></li><li><p>Announcing a purported settlement without permitting judicial review.</p></li></ul><p>The Court also criticized the government&#8217;s failure to defend the public fisc, assert available defenses, or explain its legal position.</p><p>The Court concluded that monetary sanctions could include attorneys' fees incurred by amici whose participation became necessary due to the parties&#8217; conduct.</p><p>The court-appointed amici declined reimbursement. Other amici, including former federal judges who filed the motion that led to the order, may submit reimbursement requests. Plaintiffs may respond to any such request.</p><p>The order also directed the clerk to send copies to:</p><ul><li><p>The Florida Bar regarding Alejandro Brito.</p></li><li><p>The New York disciplinary authorities, where Todd Blanche is admitted.</p></li><li><p>The District of Columbia disciplinary authorities, where Stanley Woodward is admitted.</p></li></ul><p>The Court did not impose a final monetary amount in the order.</p><h3>Limits of the Decision</h3><p>The order does not adjudicate the underlying merits of the unauthorized disclosure claims. Plaintiffs dismissed those claims with prejudice before the government responded.</p><p>The Court did not definitively decide whether the settlement agreement remains enforceable as a purely private executive branch agreement. It instead prohibited the parties from treating it as a settlement reached through the federal lawsuit.</p><p>The Court also declined to make a final determination under Rule 60(d)(3), which permits relief for fraud on the Court. It left open the possibility of future proceedings under that rule.</p><p>The decision comes from a federal district Court. It does not establish binding precedent outside the case in the same manner as a federal appellate decision.</p><h3>Result</h3><p>The Court found no Article III case or controversy, imposed nonmonetary Rule 11 sanctions, permitted possible monetary sanctions, and barred the parties from using the agreement as evidence of a Court settlement.</p><h3>The Takeaway</h3><p>Tax professionals should see this order mainly as a decision about constitutional issues and litigation sanctions, not as a detailed interpretation of IRC &#167;7431. The main point is that the court refused to accept a tax settlement when the plaintiff controlled the government agencies being sued and there was no real adversarial review.</p><h4>List of Citations</h4><ul><li><p>U.S. Constitution, Article III, &#167;2: Limits federal judicial power to genuine cases and controversies.</p></li><li><p>U.S. Constitution, Article II, &#167;1: Vests executive power in the President and supported the Court&#8217;s control analysis.</p></li><li><p>IRC &#167;7431: Authorizes civil damages for unauthorized inspections or disclosures of tax return information.</p></li><li><p>IRC &#167;7431(d): Establishes the two-year limitations period for unauthorized disclosure actions.</p></li><li><p>IRC &#167;7217: Prohibits executive branch influence over specific IRS audits and investigations.</p></li><li><p>IRC &#167;7803(a): Governs appointment and removal authority for the IRS Commissioner.</p></li><li><p>Federal Rule of Civil Procedure 11: Authorizes sanctions for filings presented for an improper purpose.</p></li><li><p>Federal Rule of Civil Procedure 41(a)(1): Governs voluntary dismissals before a defendant files an answer or summary judgment motion.</p></li><li><p>Federal Rule of Civil Procedure 60(d)(3): Preserves judicial authority to address fraud on the Court.</p></li><li><p>Lord v. Veazie, 49 U.S. 251 (1850): Rejects jurisdiction where nominally adverse parties share the same interests.</p></li><li><p>Muskrat v. United States, 219 U.S. 346 (1911): Requires actual adverse parties for an Article III controversy.</p></li><li><p>Aetna Life Insurance Co. v. Haworth, 300 U.S. 227 (1937): Defines a justiciable controversy as concrete and involving adverse legal interests.</p></li><li><p>GTE Sylvania Inc. v. Consumers Union, 445 U.S. 375 (1980): Explains that no controversy exists when parties seek the same result.</p></li><li><p>South Spring Hill Gold Mining Co. v. Amador Medean Gold Mining Co., 145 U.S. 300 (1892): Rejects litigation when the same persons control both sides.</p></li><li><p>Cooter &amp; Gell v. Hartmarx Corp., 496 U.S. 384 (1990): Holds that voluntary dismissal does not eliminate Rule 11 jurisdiction.</p></li><li><p>Absolute Activist Value Master Fund Ltd. v. Devine, 998 F.3d 1258 (11th Cir. 2021): Confirms that courts retain jurisdiction over collateral sanctions issues after dismissal.</p></li><li><p>Chambers v. NASCO Inc., 501 U.S. 32 (1991): Recognizes the federal courts&#8217; inherent authority to sanction bad-faith litigation conduct.</p></li><li><p>Trump v. Clinton, 640 F. Supp. 3d 1329 (S.D. Fla. 2022): Supports sanctions for litigation filed for an improper or performative purpose.</p></li></ul>]]></content:encoded></item><item><title><![CDATA[DOJ asks Seventh Circuit to rehear Hyatt loyalty fund income ruling]]></title><description><![CDATA[Hyatt Hotels Corp. v. Commissioner. United States Court of Appeals for the Seventh Circuit. No. 24-3239. 2026.]]></description><link>https://taxcoda.com/p/doj-asks-seventh-circuit-to-rehear</link><guid isPermaLink="false">https://taxcoda.com/p/doj-asks-seventh-circuit-to-rehear</guid><dc:creator><![CDATA[Adam Parr]]></dc:creator><pubDate>Thu, 09 Jul 2026 09:25:06 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!5cG2!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fab017102-2a2e-414e-9b4e-111a7d2ed1c6_500x500.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>The DOJ wants the Seventh Circuit to reverse a <a href="https://open.substack.com/pub/taxcoda/p/court-vacates-tax-court-ruling-on?r=27e79&amp;utm_campaign=post-expanded-share&amp;utm_medium=web">ruling</a> that favors taxpayers. This ruling could let taxpayers claim that money they control is not income just because they deny having a claim of right to it.</p><h3>Holding</h3><p>The DOJ <a href="https://www.taxnotes.com/research/federal/court-documents/court-petitions-and-briefs/doj-seeks-rehearing-hotel-loyalty-rewards-dispute/7wd2b">asked</a> for a new hearing after the Seventh Circuit said the claim of right doctrine could be used to exclude certain payments from income. The court sent Hyatt&#8217;s loyalty fund case back to the Tax Court.</p><h3>Why It Matters</h3><ul><li><p>This is consequential because the government frames the panel decision as a threat to the basic definition of gross income under &#167;61.</p></li><li><p>The petition argues that the claim-of-right doctrine is a rule of income inclusion, not a taxpayer election to exclude controlled receipts from income.</p></li><li><p>The dispute matters beyond Hyatt because many businesses receive and administer funds tied to customer programs, vendor arrangements, rebates, deposits, or restricted-use accounts.</p></li><li><p>The government&#8217;s concern is administrative. If the panel decision stands, taxpayers may try to avoid income recognition by denying a claim of right while still controlling and benefiting from the funds.</p></li></ul><h3>Key Facts</h3><p>The IRS issued Hyatt a notice of deficiency asserting an additional $70 million in corporate income tax for the years between 2005 and 2012.</p><p>The deficiencies arose from payments made into a fund used to administer Hyatt&#8217;s Gold Passport customer loyalty program. Most payments came from third-party hotel owners.</p><p>Hyatt administered the fund. The IRS determined that Hyatt improperly omitted those payments from income.</p><p>The Tax Court addressed three issues:</p><ul><li><p>whether payments into the fund were income to Hyatt</p></li><li><p>whether the IRS could make an accounting adjustment based on Hyatt&#8217;s earlier omission of that income</p></li><li><p>whether Hyatt could use a Treasury regulation to reduce the amount it had to include in income</p></li></ul><p>The Tax Court ruled for the Commissioner on the income inclusion and regulation issues. It ruled against the Commissioner on the accounting adjustment issue.</p><p>Hyatt appealed. The Seventh Circuit did not resolve the Tax Court&#8217;s analysis of the trust fund doctrine. It instead held that the claim of right doctrine may provide an independent and broader basis for income exclusion.</p><p>The panel remanded the case to the Tax Court to consider whether the fund payments were income to Hyatt under the claim-of-right doctrine.</p><h3>Statutory or Regulatory Framework</h3><p>Section 61 defines gross income broadly as all income from whatever source derived. The claim of right doctrine generally requires inclusion of income when a taxpayer receives earnings under a claim of right and without restriction on disposition, even if the taxpayer may later have to repay the money.</p><p>The trust fund doctrine can exclude funds from income when a taxpayer merely holds funds for another party and lacks beneficial ownership. The DOJ&#8217;s petition treats that doctrine as a narrow exclusion and argues that the panel&#8217;s claim-of-right analysis would make it largely unnecessary.</p><h3>Arguments</h3><p>Taxpayer argued:</p><ul><li><p>Hyatt did not have to include the loyalty fund payments in income.</p></li><li><p>The claim of right doctrine provided an independent basis for excluding the payments.</p></li><li><p>The fund payments should not be treated as Hyatt&#8217;s income if Hyatt lacked the required claim of right over the money.</p></li></ul><p>Government argued:</p><ul><li><p>The claim of right doctrine is a rule of inclusion.</p></li><li><p>Failure to satisfy the claim-of-right test does not automatically exclude a receipt from income.</p></li><li><p>The panel's decision conflicts with Supreme Court precedent that broadly defines income.</p></li><li><p><em>Indianapolis Power</em> did not convert the claim-of-right doctrine into an exclusionary rule.</p></li><li><p>The decision would allow taxpayers to control and benefit from funds while denying income treatment by disclaiming a claim of right.</p></li></ul><h3>Court&#8217;s Reasoning</h3><p>The petition challenges the panel&#8217;s reasoning. It does not announce a new Court ruling.</p><p>The DOJ makes these points:</p><ul><li><p>The claim-of-right doctrine identifies one situation in which a taxpayer must include disputed receipts in income for the year of receipt.</p></li><li><p>The doctrine does not define the outer boundary of income.</p></li><li><p>The panel allegedly confused a sufficient condition for income inclusion with a necessary condition for income recognition.</p></li><li><p>The DOJ argues that the panel revived the error of <em>Commissioner v. Wilcox</em>, which treated the presence of a claim of right as a condition for taxable income.</p></li><li><p>The DOJ argues that <em>James v. United States</em> rejected that approach by overruling <em>Wilcox</em> and holding that unlawful gains can constitute taxable income even absent a bona fide claim of right.</p></li><li><p>The DOJ contends that <em>Indianapolis Power</em> turned on dominion and an obligation to repay customer deposits, rather than on an exclusionary version of the claim-of-right doctrine.</p></li><li><p>The DOJ argues that the panel's decision could weaken broader income principles grounded in control, dominion, and readily realizable economic value.</p></li></ul><h3>Result</h3><p>The DOJ wants the Seventh Circuit to rehear the case, cancel the panel&#8217;s decision, and not allow the claim of right doctrine to be used as a way to exclude income.</p><h3>The Takeaway</h3><p>Tax professionals should see this as an important case about gross income, not just a loyalty program issue. The main question is whether the Seventh Circuit will let the claim of right doctrine become a broader way for taxpayers to exclude income when they handle disputed or restricted funds.</p><h4>List of Citations</h4><ul><li><p>&#167;61: Defines gross income broadly as income from whatever source derived.</p></li><li><p><em><a href="https://open.substack.com/pub/taxcoda/p/court-vacates-tax-court-ruling-on?r=27e79&amp;utm_campaign=post-expanded-share&amp;utm_medium=web">Hyatt Hotels Corp. v. Commissioner</a></em>, 174 F.4th 535: Seventh Circuit panel decision that the DOJ seeks to rehear.</p></li><li><p><em>James v. United States</em>, 366 U.S. 213: Central Supreme Court authority cited by the DOJ for the broad definition of income and the rejection of <em>Wilcox</em>.</p></li><li><p><em>Commissioner v. Wilcox</em>, 327 U.S. 404: Overruled case that treated claim of right as a condition for taxable income.</p></li><li><p><em>Rutkin v. United States</em>, 343 U.S. 130: Supreme Court case holding that unlawful gains are taxable income when the taxpayer has control and economic value.</p></li><li><p><em>Commissioner v. Glenshaw Glass Co.</em>, 348 U.S. 426: Foundational case defining income as undeniable accessions to wealth, clearly realized, over which the taxpayer has complete dominion.</p></li><li><p><em>Commissioner v. Indianapolis Power &amp; Light Co.</em>, 493 U.S. 203: Customer deposit case that the panel relied on and that the DOJ argues the panel misread.</p></li><li><p><em>United States v. Skelly Oil Co.</em>, 394 U.S. 678: States the classic claim-of-right formulation and ties it to annual accounting.</p></li><li><p><em>North American Oil Consolidated v. Burnet</em>, 286 U.S. 417: Original claim-of-right case requiring inclusion of income in the year of receipt despite ongoing entitlement litigation.</p></li><li><p><em>Healy v. Commissioner</em>, 347 U.S. 278: Applies the claim-of-right doctrine to salary received without restriction, even though a later repayment liability arose.</p></li><li><p><em>Macias v. Commissioner</em>, 255 F.2d 23: Seventh Circuit authority cited by DOJ as rejecting claim of right as an exclusion doctrine.</p></li><li><p><em>Commissioner v. Schleier</em>, 515 U.S. 323: Cited for the sweeping scope of gross income.</p></li></ul>]]></content:encoded></item><item><title><![CDATA[AI Drafted the Tax Argument. The Practitioner Still Owns It.]]></title><description><![CDATA[In tax law, being fast only matters after you make sure everything is accurate.]]></description><link>https://taxcoda.com/p/ai-drafted-the-tax-argument-the-practitioner</link><guid isPermaLink="false">https://taxcoda.com/p/ai-drafted-the-tax-argument-the-practitioner</guid><dc:creator><![CDATA[Adam Parr]]></dc:creator><pubDate>Wed, 08 Jul 2026 13:34:04 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!5cG2!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fab017102-2a2e-414e-9b4e-111a7d2ed1c6_500x500.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>In tax law, being fast only matters after you make sure everything is accurate.</p><p>Generative AI changes how we work, but it does not change legal responsibility. A tool that quickly creates a polished memo can also make up citations, invent safe harbors, or suggest transaction structures that look right but miss the real requirements. In tax, this is not just a drafting issue&#8212;it is a compliance issue.</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://taxcoda.com/subscribe?coupon=acf79b7f&amp;utm_content=205980560&quot;,&quot;text&quot;:&quot;Get 60% off forever&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://taxcoda.com/subscribe?coupon=acf79b7f&amp;utm_content=205980560"><span>Get 60% off forever</span></a></p><p>People often say AI is risky because it sometimes makes things up. That is true, but it is not the whole story. AI works by guessing what is likely, while tax law relies on clear authority, rules, and checking facts. The system does not care if an answer sounds correct&#8212;it cares if you can trace it to a real law, regulation, ruling, case, or record.</p><h2>The Event</h2><p>Generative AI is now used to read statutes, draft memos, summarize legal sources, and help with tax analysis. It really does save time and makes complicated material easier to handle.</p><p>But this same ability also changes the risks. Large language models do not perform legal reasoning as tax professionals do. They predict what text should come next. When asked about rules like IRC &#167;351 or &#167;199A, the model might give an answer that looks finished but actually makes up a safe harbor, gets a Treasury Regulation wrong, or invents a precedent. The real risk is not messy output&#8212;it is a polished answer that is actually wrong.</p><p>Courts have already seen what can go wrong. There are examples of AI-generated legal filings that cited fake cases, leading to sanctions, thrown-out memos, and disciplinary actions. In tax, these mistakes are even more serious because the system relies on people following the rules themselves. Fake authority does not just mislead a Court&#8212;it also adds misinformation to a system that is already very complex.</p><p>This issue became even more important after <a href="https://open.substack.com/pub/taxcoda/p/transfer-pricing-enters-a-new-era?r=27e79&amp;utm_campaign=post-expanded-share&amp;utm_medium=web">Loper Bright</a>. Now that Chevron has been overruled, courts must interpret ambiguous laws on their own, without relying on agency explanations. This means the actual text, structure, legislative history, and real records matter even more. AI can quickly find and summarize lots of material, but finding information is not the same as interpreting it. If AI invents a Senate report or Treasury explanation, it is not just harmless background&#8212;it can actually distort the record.</p><h2>The Real Driver</h2><p>The real reason behind these changes is not technology itself&#8212;it is the incentives people face.</p><p>Tax professionals are under pressure to work faster, cut costs, and get more done in less time. AI fits these needs well. It makes it seem like you have more help. You can ask for a memo, a transaction outline, or a list of citations and get something that looks professional. Because the output looks smart, people are more likely to trust it without checking.</p><p>That is the trap. AI is not a junior associate or a paralegal. It is not someone you can supervise like a regular team member. You give it prompts, but it is not trained in the same way. It lacks loyalty, cannot exercise judgment, and does not understand what happens if it is wrong. Treating AI like a legal assistant is misleading and reduces accountability.</p><p>The better model is instrumentality. It is better to think of AI as a tool that helps people do more. But unlike a calculator or a word processor, AI can create legal claims. If a calculator makes a mistake, you can usually see it. If AI makes a mistake, it might look convincing even though it is wrong. Because of this, the human practitioner must check every legal point before it goes out. As <span>drawn from United States v. Boyle, reliance on another actor does not excuse failure to perform a non-delegable duty. The source material applies that principle to AI verification. Checking whether a case exists, whether a quotation is accurate, and whether a cited authority supports the proposition is not the kind of judgment that can be outsourced to a machine. It is ordinary professional diligence.</span></p><p>Circular 230 points in the same direction. Section 10.22 requires due diligence in determining the correctness of representations made to Treasury. A large language model is not a person who can be supervised within the meaning of that framework. The current rules were built to account for human error and misconduct. AI changes scale. One practitioner can make an isolated mistake. One AI workflow can generate thousands of plausible errors.</p><h2>The Pattern</h2><p>The recurring pattern is institutional lag.</p><p>A new tool is used in professional practice before rules and controls are in place. People start using it because it saves time. Firms allow it because it cuts costs. Regulators and courts react only after problems surface in filings, client advice, or public records. By that point, the issue has grown from a single mistake to a bigger process risk.</p><p>Tax is especially at risk because technical details matter a lot. AI is good at getting the form right. For example, it can describe a &#167;351 exchange with property transferred, stock received, and control met. But tax law also considers whether the deal has real economic substance, a business purpose, and an actual economic impact. These questions depend on intent, context, and real facts. AI can replicate the language of these rules, but it cannot determine whether the facts actually fit.</p><p>That produces synthetic compliance. A transaction can appear properly assembled yet fail the doctrine that matters. Under IRC &#167;7701(o), economic substance requires meaningful economic change and substantial non-tax purpose. A model can draft business justifications from common patterns, but those justifications are not facts. They are generated language. The same problem appears in step transaction analysis. AI can sequence steps neatly. A Court may collapse them if they were part of a fixed plan. This pattern also shows up in jurisdictional analysis. AI often misses important differences because it learns from the most common patterns in its training data. Federal tax rules might be overrepresented, while state, local, and international rules are less visible. This can cause mistakes, such as using the wrong Court circuit, treating OECD guidance as U.S. law, or mixing up VAT with U.S. sales tax. Tax law needs specific answers, but AI often turns specifics into general responses.</p><h2>Implication</h2><p><span>The responsibility stays with the practitioner, not the tool.</span></p><p>If AI creates a fake authority, the Court does not punish the software. If client data is put into a public model, the privilege problem is not the model&#8217;s fault. If an AI-generated structure fails the economic substance test, the machine is not penalized under &#167;6662 or subject to promoter issues under &#167;6700. The person is responsible for the submission, the advice, and any breach of confidentiality.</p><p>The privilege issue is especially clear. Most generative AI tools run in the cloud. Putting client facts, return positions, or tax strategies into these tools can send sensitive information to a third-party provider. If that provider logs, stores, or reuses the data, confidentiality can be lost. The Kovel analogy does not fix this. Kovel protects some non-lawyer helpers who work under a confidential relationship. Public AI tools do not fit this model because they lack agency, loyalty, or a clear confidentiality framework.</p><p>IRC &#167;7216 brings up a similar concern when tax return information is shared without permission. The source material says this is more than just an ethics issue&#8212;it is a structural problem caused by data being stored, hidden, or reused. The main lesson is simple: a public AI prompt box is not a private conference room, no matter how friendly it seems.</p><h2>Lessons for Practitioners</h2><ul><li><p>When using AI, the real work is in verifying the results. The draft might come from the tool, but responsibility for accuracy lies with the practitioner.</p></li><li><p>Just because something sounds fluent does not mean it is reliable. A polished list of citations is risky because it makes it look like someone has already checked it.</p></li><li><p>Anti-abuse rules show the limits of drafting based only on form. AI can put steps together, but economic substance and step transaction analysis rely on facts, purpose, and context.</p></li><li><p>Confidentiality risks begin as soon as you enter information. Putting client facts into a public or poorly controlled AI system can cause privilege and disclosure problems before you even draft a memo.</p></li><li><p>Governance is more than just a policy memo in a folder. Good controls include keeping records of source checks, usage logs, and version histories; using restricted tools; having zero-retention contracts; and ensuring a human reviews everything before it goes to a client, Court, or agency.</p></li></ul><h2>Human Element</h2><p>When people are under pressure, they are more likely to take shortcuts if those shortcuts look professional. AI makes this easier by hiding the rough parts of early drafts. The draft comes out looking finished and confident, which makes people trust it before they have checked it.</p><h2>Forward View</h2><p>The continuing pattern is not prohibition. AI will remain in tax practice because the efficiency gains are too large to ignore. The profession will not stop using tools that can summarize material, organize research, and accelerate drafting. The question is whether those tools are placed within a system that makes errors harder to detect. That system must make human review the main checkpoint. Courts might require proof that AI-assisted filings have been checked. Treasury could update Circular 230 to cover generative AI. Firms might limit public tools and require verified databases for legal work. All these steps lead to the same point: AI can help with tax work, but it cannot take on legal responsibility.</p><p>The tax system can handle faster tools, but it cannot handle unverified information that appears to be professional judgment.</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://taxcoda.com/p/ai-drafted-the-tax-argument-the-practitioner?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://taxcoda.com/p/ai-drafted-the-tax-argument-the-practitioner?utm_source=substack&utm_medium=email&utm_content=share&action=share"><span>Share</span></a></p>]]></content:encoded></item><item><title><![CDATA[Tax Court allows limited Schedule C deductions but rejects personal travel]]></title><description><![CDATA[Gregory A. Rodrigues v. Commissioner. United States Tax Court. No. 7902-24S. 2026.]]></description><link>https://taxcoda.com/p/tax-court-allows-limited-schedule</link><guid isPermaLink="false">https://taxcoda.com/p/tax-court-allows-limited-schedule</guid><dc:creator><![CDATA[Adam Parr]]></dc:creator><pubDate>Tue, 07 Jul 2026 12:00:52 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!5cG2!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fab017102-2a2e-414e-9b4e-111a7d2ed1c6_500x500.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>Taxpayers need to show that Schedule C expenses have a real business purpose and back them up with solid records. This is especially important for travel and meals<span>. </span></p><h3>Holding</h3><p><span>The Tax Court </span><a href="https://www.taxnotes.com/research/federal/court-documents/court-opinions-and-orders/individual-cant-deduct-unsubstantiated-business-expenses/7w8qv"><span>agreed</span></a><span> with the IRS and denied the taxpayer&#8217;s deductions for travel, meals, entertainment, security, telephone, and duplicate fees. However, it allowed some deductions for bank charges, dues and subscriptions, taxes and licenses, and postage. The final amount owed will be calculated under Rule 155.</span></p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://taxcoda.com/subscribe?coupon=acf79b7f&amp;utm_content=204794916&quot;,&quot;text&quot;:&quot;Get 60% off forever&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://taxcoda.com/subscribe?coupon=acf79b7f&amp;utm_content=204794916"><span>Get 60% off forever</span></a></p><h3>Why It Matters</h3><ul><li><p>This is a routine substantiation case, but it is useful because the taxpayer had receipts, credit card records, and spreadsheets. Those records still failed where they did not prove business purpose.</p></li><li><p>The opinion reinforces that travel with friends, romantic partners, or family members invites scrutiny when the taxpayer claims business deductions.</p></li><li><p>Post-examination reconstruction had limited value. The Court gave little weight to emails created in 2024 to support travel taken in 2021.</p></li><li><p>The Court allowed expenses when the taxpayer tied them directly to the business. It rejected expenses when the evidence showed personal use or no allocation.</p></li></ul><h3>Key Facts</h3><p>Gregory Rodrigues filed a 2021 federal income tax return reporting $575,232 of W-2 wages from Ecologic Brands.</p><p>He also reported income and expenses from Western Land Financial, LLC, a real estate investment company he founded in 2003.</p><p>Western Land Financial reported:</p><ul><li><p>$1,999 of gross receipts.</p></li><li><p>$52,426 of expenses.</p></li><li><p>A Schedule C loss of $50,427.</p></li></ul><p>The disputed deductions included:</p><ul><li><p>$16,206 for travel.</p></li><li><p>$6,218 for meals and entertainment.</p></li><li><p>$12,683 for &#8220;Other&#8221; expenses.</p></li></ul><p>The &#8220;Other&#8221; expenses included bank charges, dues and subscriptions, fees, postage, security, taxes and licenses, and telephone expenses.</p><p>Rodrigues traveled in 2021 to West Palm Beach, Miami, San Jose del Cabo, Carmel, Healdsburg, and California&#8217;s Central Valley. He also booked a canceled trip to Austin and a later &#8220;Backroads&#8221; trip scheduled for 2022.</p><p>He claimed the travel was related to real estate investment activity, including efforts to sell land in Anza, California, and interests in land in Holbrook, Arizona.</p><p>Some travel involved members of a Harvard Business School friend group called the Loveshack Investors. Some members worked in real estate.</p><p>Jennifer George, an attorney employed by PwC, accompanied Rodrigues on several trips. Rodrigues and George shared a residence and had a child together. They did not have a retainer agreement for legal services during 2021.</p><p>Rodrigues did not maintain contemporaneous travel logs. He later prepared spreadsheets using receipts, credit card records, and bank statements.</p><h3>Statutory or Regulatory Framework</h3><p>&#167;162 allows deductions for ordinary and necessary business expenses. &#8220;Ordinary&#8221; means common in the taxpayer&#8217;s business. &#8220;Necessary&#8221; means appropriate and helpful to that business.</p><p>&#167;262 disallows deductions for personal, living, or family expenses.</p><p>&#167;274(d) imposes strict substantiation rules for travel, meals, entertainment, gifts, and listed property. A taxpayer must prove the amount, time, place, business purpose, and, for entertainment or gifts, the business relationship.</p><p>&#167;6001 and the regulations require taxpayers to keep records sufficient to establish their deductions.</p><p>The Cohan rule allows courts to estimate some business expenses when the taxpayer proves the expense occurred but not the exact amount. The rule does not apply when strict substantiation is required or when the Court lacks a reasonable basis for allocation.</p><h3>Arguments</h3><p>Taxpayer argued:</p><ul><li><p>The travel expenses related to Western Land Financial&#8217;s real estate business.</p></li><li><p>The trips involved meetings with investors and real estate professionals.</p></li><li><p>George accompanied him as his attorney.</p></li><li><p>The Loveshack Investors trips had a business purpose because some members were real estate professionals.</p></li><li><p>The &#8220;Other&#8221; expenses were ordinary and necessary expenses of Western Land Financial.</p></li></ul><p>Government argued:</p><ul><li><p>Rodrigues failed to prove that the disputed expenses were paid or business-related.</p></li><li><p>The travel appeared personal.</p></li><li><p>The records did not satisfy &#167;274(d).</p></li><li><p>Several expenses were personal, duplicative, or inadequately allocated.</p></li></ul><h3>Court&#8217;s Reasoning</h3><ul><li><p>The Court accepted that Rodrigues paid many of the expenses. Payment alone did not establish deductibility.</p></li><li><p>The Court did not find Rodrigues&#8217;s spreadsheets reliable as proof of business purpose.</p></li><li><p>The Court found his testimony regarding the business purpose of the travel and meals not credible.</p></li><li><p>The Court treated the travel as predominantly personal because it involved friends and George, with whom Rodrigues shared a residence and child.</p></li><li><p>The Court rejected the claim that George traveled as his attorney because there was no documentary evidence of an attorney-client relationship for the trips.</p></li><li><p>The Court gave little weight to 2024 emails sent to Loveshack Investors members because they were not contemporaneous with the 2021 travel and were created after the IRS examination began.</p></li><li><p>The Court found that a 2005 concept plan for the Anza property did little to prove that 2021 travel had a business purpose.</p></li><li><p>The Court held that Rodrigues failed the &#167;274(d) business-purpose requirement for travel and meals.</p></li><li><p>The Court allowed bank charges because Rodrigues substantiated $120 in wire transfer fees associated with real estate loans.</p></li><li><p>The Court allowed $4,758 of dues and subscriptions because the record tied the HOA fees, Wall Street Journal subscription, and Ring subscription to Western Land Financial&#8217;s business or property security.</p></li><li><p>The Court denied a separate $168 fee deduction because it duplicated amounts included in taxes and licenses.</p></li><li><p>The Court allowed $577 for substantiated taxes and licenses.</p></li><li><p>The Court allowed $336 for postage because the record linked the expense to the shipping and notarization of real estate documents.</p></li><li><p>The Court denied the $216 security expense because Rodrigues failed to substantiate its business purpose.</p></li><li><p>The Court denied telephone expenses because the charges included personal cable television services and Rodrigues did not provide a reasonable allocation between personal and business use.</p></li></ul><h3>Result</h3><p>Decision will be entered under Rule 155 after allowing limited deductions and sustaining the IRS&#8217;s remaining disallowances.</p><h3>The Takeaway</h3><p>This decision is a clear reminder that receipts and spreadsheets alone are not enough to prove a deduction unless they show a business purpose. Accountants should treat travel, meals, mixed-use subscriptions, and home-related expenses as high-risk for Schedule C unless the taxpayer has up-to-date records and a solid way to separate business from personal use.</p><h4>List of Citations</h4><ul><li><p>Welch v. Helvering: burden-and-necessity standard for business expenses.</p></li><li><p>INDOPCO, Inc. v. Commissioner, deductions are a matter of legislative grace.</p></li><li><p>Cohan v. Commissioner, estimation allowed only when the record provides a basis.</p></li><li><p>Vanicek v. Commissioner, estimation requires a reasonable evidentiary foundation.</p></li><li><p>Sanford v. Commissioner: strict substantiation limits on &#167;274(d) expenses.</p></li></ul>]]></content:encoded></item><item><title><![CDATA[IRS levy fails after DOJ settlement covers same tax liabilities]]></title><description><![CDATA[Joseph White v. Commissioner. United States Tax Court. No. 7838-25L. 2026.]]></description><link>https://taxcoda.com/p/irs-levy-fails-after-doj-settlement</link><guid isPermaLink="false">https://taxcoda.com/p/irs-levy-fails-after-doj-settlement</guid><dc:creator><![CDATA[Adam Parr]]></dc:creator><pubDate>Mon, 06 Jul 2026 12:00:48 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!5cG2!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fab017102-2a2e-414e-9b4e-111a7d2ed1c6_500x500.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>The IRS acted improperly by upholding a levy that would have sped up collection of restitution-based assessments, even though the DOJ had already settled those same tax debts through a court-approved payment plan.</p><h3>Holding</h3><p>The Tax Court refused to allow the proposed levy. It denied the IRS&#8217;s request for summary judgment, treated the taxpayer&#8217;s response as a cross-motion, and ruled in favor of the taxpayer.</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://taxcoda.com/subscribe?coupon=acf79b7f&amp;utm_content=204794627&quot;,&quot;text&quot;:&quot;Get 60% off forever&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://taxcoda.com/subscribe?coupon=acf79b7f&amp;utm_content=204794627"><span>Get 60% off forever</span></a></p><h3>Why It Matters</h3><ul><li><p>The decision limits the IRS's collection discretion when the DOJ has already resolved the same tax liabilities through a settlement agreement.</p></li><li><p>The ruling does not invalidate restitution-based assessments, or RBAs. It limits how the IRS may collect them when collection conflicts with a later DOJ compromise.</p></li><li><p>The case turns on timing and consistency, not double collection. The Tax Court accepted that payments against RBAs would be credited against civil tax liabilities.</p></li><li><p>The practical point is procedural. Appeals must consider whether a levy is more intrusive than necessary when the government has already agreed to installment payment rights.</p></li></ul><h3>Key Facts</h3><p>Joseph White owed federal income tax liabilities for 2000 through 2011.</p><p>In 2017, he was convicted under &#167;7201 for willfully attempting to evade payment of those taxes. The sentencing Court ordered $1.2 million in restitution to the IRS. The IRS then made RBAs under &#167;6201(a)(4) for the same $1.2 million.</p><p>In 2022, DOJ brought a civil collection action under &#167;6502 to reduce White&#8217;s unpaid 2000 through 2011 tax liabilities to judgment. By August 2023, the liabilities had grown to about $1.893 million with interest and additions to tax.</p><p>DOJ and White settled that action in September 2023. White agreed to a judgment of about $1.893 million. DOJ agreed to treat the judgment as satisfied and take no further collection action for the 2000 through 2011 income tax liabilities if White paid $1.6 million by July 1, 2027, under a specified payment plan.</p><p>White stayed current on the payment plan. By March 2026, he had paid almost $1 million.</p><p>While the civil collection case was pending, the IRS issued a levy notice to collect about $1.102 million of unpaid RBAs. Appeals sustained the levy.</p><h3>Statutory Framework</h3><p>Section 6201(a)(4) allows the IRS to assess and collect criminal tax restitution as if it were tax. An RBA is a tax collection assessment issued pursuant to a restitution order. Section 6201(a)(4)(C) bars the taxpayer from challenging the amount of restitution by disputing the underlying tax liability in a tax proceeding.</p><p>Section 6330 requires Appeals to verify legal requirements, consider issues the taxpayer raises, and decide whether the proposed collection action balances efficient collection with the taxpayer&#8217;s legitimate concern that collection be no more intrusive than necessary.</p><h3>Arguments</h3><p>Taxpayer argued:</p><ul><li><p>The RBAs matched the same unpaid income tax liabilities for 2000 through 2011 that were covered by the DOJ settlement.</p></li><li><p>The levy conflicted with the settlement because DOJ agreed to accept $1.6 million over time.</p></li><li><p>Immediate collection of the levy would disregard his contractual right to pay through July 2027.</p></li><li><p>The levy would be more intrusive than necessary.</p></li></ul><p>Government argued:</p><ul><li><p>The RBAs were separate and distinct from White&#8217;s civil income tax liabilities.</p></li><li><p>DOJ&#8217;s settlement resolved only the civil tax liabilities reduced to judgment.</p></li><li><p>Appeals properly sustained the levy because White could not challenge the restitution assessment under &#167;6201(a)(4)(C).</p></li><li><p>White did not provide financial information supporting a collection alternative.</p></li></ul><h3>Court&#8217;s Reasoning</h3><ul><li><p>The Tax Court reviewed the Appeals for abuse of discretion because White could not challenge the underlying RBA liability in the CDP proceeding.</p></li><li><p>The Court rejected White&#8217;s double collection theory. The IRS could not collect the same tax loss twice, but any RBA collection would be credited against the related tax liabilities.</p></li><li><p>The Court found that the RBAs were distinct in assessment procedure, but not separate in economic substance. They represented the same 2000-2011 income tax liabilities.</p></li><li><p>DOJ had already agreed to a different collection mechanism for those same liabilities. The settlement gave White until July 1, 2027, to complete payment.</p></li><li><p>Appeals sustained a levy that would have collected the remaining balance immediately, and potentially more than the unpaid balance under the settlement.</p></li><li><p>The settlement officer failed to account for White&#8217;s ongoing compliance with the DOJ payment plan.</p></li><li><p>The levy conflicted with the government&#8217;s settlement and was more intrusive than necessary under &#167;6330(c)(3).</p></li></ul><h3>Result</h3><p>Decision entered for White, and the proposed levy was not sustained.</p><h3>The Takeaway</h3><p>This case is not a sweeping victory for taxpayers against restitution assessments. Instead, it says the IRS cannot use an RBA levy to get around a DOJ settlement that covers the same tax debts and payment plan.</p><p>Practitioners should pay attention to how the tax debts, the settlement terms, and the taxpayer&#8217;s payment plan fit together. This is the important part of the case, since it shows that different parts of the government may not always coordinate their actions.</p><h4>List of Citations</h4><ul><li><p>Klein v. Commissioner, 149 T.C. 341, supports the treatment of RBAs and limits on interest or additions assessed on restitution.</p></li><li><p>Carpenter v. Commissioner, 152 T.C. 202, addresses RBA procedures and limitations.</p></li><li><p>Zuch v. Commissioner, 145 S. Ct. 1707, cited for mootness after liabilities were fully paid.</p></li></ul>]]></content:encoded></item></channel></rss>