Duplicative IRS Notices Create Double Trouble for Partnerships

This article was originally published by Bloomberg Law, Duplicative IRS Notices Create Double Trouble for Partnerships

A final notice should be exactly what it claims to be — final. But a US Tax Court dismissal last month shows what can happen when the IRS sends a partnership two supposedly final notices for the same tax year.

In Arindel Farm LLC v. Commissioner, the IRS reportedly mailed a Florida horse-breeding partnership two nearly identical notices of final partnership adjustment, or FPAs, only two days apart — one on July 31, 2024, and another on Aug. 2, 2024.

Arindel Farm petitioned the Tax Court that October to contest the July 31 notice, which ultimately ended with a stipulated decision reflecting no adjustments or penalties. The court later dismissed the Aug. 2 notice proceeding for lack of jurisdiction, determining that, under Section 6231(c), the second notice was automatically rescinded because both FPAs related to the 2020 tax year.

The centralized partnership audit regime under the Bipartisan Budget Act of 2015 allows a defective notice to determine whether a court ever considers the merits. While Arindel managed to untangle this administrative knot, its case exposes a deeper, systemic issue where parallel notices create conflicting legal obligations and hidden procedural traps.

‘Ticket’ Into Court

An FPA isn’t just an IRS closing letter; it’s the jurisdictional ticket that grants a partnership the right to challenge IRS adjustments.

Section 6234 generally gives a partnership 90 days from the FPA mailing date to petition the Tax Court, a federal district court, or the Court of Federal Claims. However, opting for one of the latter two typically requires the partnership to first deposit the imputed underpayment, penalties, and associated interest.

This risk is compounded by the expansive statutory authority granted to the partnership representative. This designated individual maintains exclusive authority to bind the partnership and its partners to any action taken during an administrative proceeding and to its final resolution.

As a result, an inadequate or disorganized response to the dual notices creates systemic exposure, binding even passive partners who lacked notice or knowledge of the underlying proceedings.

‘Final,’ Not Singular

The underlying rules for FPAs are deceptively complex, bearing little resemblance to the straightforward nature of their label.

Treas. Reg. Section 301.6231-1(e) allows the IRS to issue more than one FPA for the same partnership and tax year before a partnership files a timely petition. Once a petition has been filed, however, Section 6231(c) generally prohibits the IRS from issuing another FPA for that year, barring fraud, malfeasance, or a material misrepresentation.

Under Section 6231(d), the IRS maintains the authority to rescind an FPA, subject to the partnership’s consent. A rescinded notice carries no legal effect and is treated ab initio — as though it were never issued and won’t support a subsequent judicial proceeding.

While these provisions may seem logical in isolation, their intersection creates a dangerous procedural trap. A partnership receiving a second FPA can’t safely assume it replaces the original. Unless the first notice is formally rescinded, both may remain legally operative, with each independent notice carrying its own distinct deadlines for a court petition or a push-out election, alongside standalone underpayment assessments and penalty determinations.

Inaction carries substantial procedural risk. Under Section 6234, certain judicial dismissals operate as final decisions sustaining the underlying FPA. A partnership shouldn’t be forced to guess whether contesting a single notice adequately preserves its legal rights regarding a separate, concurrent notice.

Symptom of Ambiguity

The most risk-averse approach is to file protective petitions for every facially valid FPA and ask the court later to consolidate the matters or declare which notice controls. While this strategy safeguards jurisdictional rights, it introduces redundant litigation costs and creates unnecessary procedural burdens for both the taxpayer and the court.

Rather than relying on standard procedures, partnership representatives and controversy counsel must adopt a specialized duplicate-notice protocol:

• Preservation of Proof: Maintain all notices and corresponding envelopes, recording the dates of mailing and receipt.
• Comparative Analysis: Contrast all individual adjustments, penalty determinations, attached computations, tax periods, and procedural deadlines.
• Formal Inquiry: Request a written determination from the IRS specifying whether the subsequent notice supplements, amends, or replaces the initial FPA.
• Statutory Rescission: Request a formal, consensual rescission of the duplicate FPA instead of relying on an examiner’s nonbinding informal assurances.
• Jurisdictional Safeguards: Analyze the utility of filing protective petitions prior to the expiration of either 90-day jurisdictional window.
• Comprehensive Settlement Language: Ensure that any settlement itemizes every relevant FPA, docket number, adjustment, and penalty for the applicable tax year.
• Definitive Confirmation: Require confirmation that the settlement extinguishes all notices, preventing any residual entity-level assessments or partner-level push-out obligations.

IRS Clarification Needed

The IRS has the inherent authority to resolve these procedural ambiguities administratively, without the need for legislative action from Congress.

To eliminate confusion, it should implement a system where every FPA is assigned a unique notice identifier. When multiple FPAs are issued for the same partnership taxable year, any subsequent notice should prominently declare its exact relationship to the prior document — explicitly stating whether it serves as an addition, correction, or replacement.

To ensure procedural integrity, the IRS also should refrain from issuing any replacement notice until the original FPA has been formally rescinded pursuant to statutory consent requirements.

Corresponding settlement documents must incorporate a comprehensive schedule itemizing every FPA issued for the taxable year alongside its final disposition. Achieving systemic finality requires absolute structural consistency: The administrative file, final settlement agreement, and judicial docket must reflect an identical procedural history.

Although the centralized partnership audit regime was created to improve examination efficiency, administrative expediency can’t come at the expense of procedural clarity on final agency action. A partnership confronted with two conflicting notices shouldn’t be forced to initiate parallel litigation to determine which one holds legal weight.

The case is Arindel Farm, LLC v. Comm’r, 2026 BL 347003, T.C., No. 16836-24., decided 9/3/26.