Tag: Notice Partner Petition

  • Computer Programs Lambda, Ltd. v. Commissioner, 89 T.C. 198 (1987): Impact of Bankruptcy on Partnership Proceedings

    Computer Programs Lambda, Ltd. v. Commissioner, 89 T. C. 198 (1987)

    Bankruptcy of a partner converts partnership items to nonpartnership items, severing the partner’s interest in the partnership proceeding.

    Summary

    In this case, the U. S. Tax Court addressed the effect of a partner’s bankruptcy on partnership proceedings. Pyke International, Inc. (PII), the tax matters partner of Computer Programs Lambda, Ltd. (CPL), filed for bankruptcy, which triggered the automatic stay under the Bankruptcy Code. The court held that PII’s bankruptcy converted its partnership items to nonpartnership items, thereby removing PII from the partnership proceeding. The court also dismissed petitions filed by PII and another partner, W. P. Builders, due to the bankruptcy stay, but allowed the case to proceed based on a valid notice partner petition filed by William C. Mitchell. The decision underscores the importance of the tax matters partner’s role and the need for a substitute when the original partner enters bankruptcy.

    Facts

    Computer Programs Lambda, Ltd. (CPL) was a Texas limited partnership with Pyke International, Inc. (PII) as the tax matters partner. On March 11, 1986, the IRS issued a notice of final partnership administrative adjustment to PII for CPL’s 1982 taxable year. William A. Pyke, president of PII but not a CPL partner, filed a petition on June 13, 1986, claiming to be the tax matters partner. On June 17, 1986, PII filed for Chapter 11 bankruptcy, listing W. P. Builders as a division and co-debtor. Pyke attempted to amend the petition on August 7, 1986, to substitute PII as petitioner. Notice partners W. P. Builders and William C. Mitchell filed a joint petition on August 11, 1986, and James C. Bearden filed a separate petition on August 12, 1986.

    Procedural History

    The Commissioner moved to dismiss the petitions filed by Pyke, PII, W. P. Builders, and Bearden. The Tax Court considered the impact of the automatic stay under the Bankruptcy Code and the conversion of partnership items to nonpartnership items due to PII’s bankruptcy filing. The court granted the motions to dismiss the petitions filed by Pyke, PII, and W. P. Builders, but allowed the case to proceed based on Mitchell’s valid notice partner petition.

    Issue(s)

    1. Whether Pyke’s petition as an individual tax matters partner commenced a valid partnership action.
    2. Whether PII’s amended petition to substitute itself as petitioner was valid given its bankruptcy filing.
    3. Whether W. P. Builders’ petition as a notice partner was valid given its status as a debtor in PII’s bankruptcy proceeding.
    4. Whether the automatic stay under the Bankruptcy Code prevented the partnership proceeding from going forward.
    5. Whether Bearden’s petition should be dismissed as duplicative of Mitchell’s petition.

    Holding

    1. No, because Pyke was not a partner of CPL and thus could not commence a partnership action.
    2. No, because the automatic stay provision of the Bankruptcy Code barred PII from commencing an action after filing for bankruptcy.
    3. No, because W. P. Builders, as a named debtor in PII’s bankruptcy, could not commence an action in the Tax Court.
    4. No, because PII’s and W. P. Builders’ partnership items became nonpartnership items upon bankruptcy, severing their interest in the proceeding and allowing it to go forward.
    5. Yes, because Mitchell’s petition was filed first, but Bearden was allowed to file an election to participate in the action that went forward.

    Court’s Reasoning

    The court applied the automatic stay provision of the Bankruptcy Code (11 U. S. C. § 362(a)(8)) and IRS regulations under 26 U. S. C. § 6231(c) that convert partnership items to nonpartnership items upon a partner’s bankruptcy filing. The court reasoned that Pyke’s petition was invalid because he was not a partner, and PII’s amended petition was ineffective due to the automatic stay. W. P. Builders’ petition was also invalid due to its status as a debtor in PII’s bankruptcy. The court emphasized that the conversion of partnership items to nonpartnership items severed PII’s and W. P. Builders’ interest in the proceeding, allowing it to go forward. The court also highlighted the crucial role of the tax matters partner and the need for a substitute when the original partner enters bankruptcy. The court dismissed Bearden’s petition but allowed him to participate in the proceeding based on Mitchell’s valid petition.

    Practical Implications

    This decision clarifies that a partner’s bankruptcy filing converts partnership items to nonpartnership items, severing the partner’s interest in the partnership proceeding and allowing it to continue. Practitioners must be aware of the automatic stay’s impact on partnership proceedings and the need to appoint a new tax matters partner when the original partner files for bankruptcy. The case also underscores the importance of filing timely notice partner petitions to preserve the partnership’s ability to challenge IRS adjustments. Subsequent cases have followed this precedent in handling partnership proceedings involving bankrupt partners.

  • Transpac Drilling Venture 1982-22 v. Commissioner, 87 T.C. 874 (1986): Timing of Partner Petitions in Partnership Audits

    Transpac Drilling Venture 1982-22 v. Commissioner, 87 T. C. 874, 1986 U. S. Tax Ct. LEXIS 32, 87 T. C. No. 57 (1986)

    A notice partner’s petition to readjust partnership items is only effective after the close of the 90-day period for the tax matters partner to file such a petition.

    Summary

    In Transpac Drilling Venture 1982-22 v. Commissioner, the U. S. Tax Court clarified the timing requirements for filing petitions by notice partners in partnership audits. The IRS issued a final partnership administrative adjustment, and the notice partners filed a petition on the last day of the tax matters partner’s 90-day filing period, which fell on a Sunday. The court held that the notice partners’ petition was ineffective because it was filed before the close of the 90-day period, which extended to the next business day. This ruling underscores the importance of precise timing in partnership litigation procedures.

    Facts

    The IRS issued a notice of final partnership administrative adjustment to Transpac Drilling Venture 1982-22 on April 14, 1986. The tax matters partner did not file a petition for readjustment within the 90-day period, which ended on July 13, 1986, a Sunday. Notice partners filed a petition on July 14, 1986, and an identical petition on July 15, 1986. The IRS moved to dismiss the latter as a duplicate petition.

    Procedural History

    The IRS issued a notice of final partnership administrative adjustment on April 14, 1986. No petition was filed by the tax matters partner within the 90-day period. Notice partners filed petitions on July 14 and July 15, 1986. The IRS moved to dismiss the July 15 petition as a duplicate. The Tax Court denied the motion, ruling that the July 14 petition was ineffective, making the July 15 petition the valid commencement of the action.

    Issue(s)

    1. Whether a notice partner’s petition filed on the last day of the tax matters partner’s 90-day period is effective to commence a partnership action.

    Holding

    1. No, because the notice partner’s petition was filed before the close of the 90-day period, which extended to the next business day due to the last day falling on a Sunday.

    Court’s Reasoning

    The court applied Section 6226 of the Internal Revenue Code, which allows the tax matters partner 90 days to file a petition for readjustment of partnership items. Since the last day of this period was a Sunday, it extended to the next business day, July 14, 1986, under Section 7503. Section 6226(b) permits notice partners to file only after the close of this 90-day period. The court ruled that the notice partners’ petition filed on July 14 was ineffective because it was filed before the period closed. Therefore, the petition filed on July 15 was the effective commencement of the partnership action. The court emphasized the statutory language and the legislative intent to ensure orderly proceedings in partnership audits.

    Practical Implications

    This decision clarifies that notice partners must wait until the close of the tax matters partner’s 90-day period before filing their own petition. This impacts how attorneys advise clients in partnership disputes, ensuring they adhere strictly to statutory deadlines. The ruling affects the timing of legal actions in partnership audits and underscores the need for precise calendar management in tax litigation. It also influences how businesses structure their partnership agreements and audit strategies to comply with these procedural requirements. Subsequent cases have followed this ruling, reinforcing the importance of timing in partnership litigation.

  • Transpac Drilling Venture 1982-22 v. Commissioner, T.C. Memo. 1988-280: Timing Requirements for Notice Partner Petitions in Partnership Tax Adjustments

    Transpac Drilling Venture 1982-22 v. Commissioner, T.C. Memo. 1988-280 (1988)

    A petition for readjustment of partnership items filed by notice partners before the expiration of the 90-day period granted to the tax matters partner for filing such a petition is ineffective to commence a partnership action.

    Summary

    In this Tax Court case, notice partners of Transpac Drilling Venture 1982-22 filed a petition for readjustment of partnership items on the 90th day after the Notice of Final Partnership Administrative Adjustment (FPAA) was mailed. The court considered whether this petition was timely and effective to commence a partnership action, given that the statute grants the tax matters partner 90 days to file first, and only then allows notice partners to file within the subsequent 60 days. The court held that because the notice partners filed their petition on the last day of the 90-day period afforded to the tax matters partner, it was premature and thus ineffective. Consequently, a second petition filed the following day was deemed the effective petition.

    Facts

    The Commissioner issued a Notice of Final Partnership Administrative Adjustment (FPAA) to Transpac Drilling Venture 1982-22 on April 14, 1986.

    This FPAA was sent to both the tax matters partner and all notice partners, including the petitioners in this case.

    The tax matters partner did not file a petition for readjustment within the initial 90-day period.

    The notice partners filed a petition for readjustment on July 14, 1986, which was exactly 90 days after April 14, 1986.

    They filed a second, identical petition on July 15, 1986.

    The Commissioner argued that the July 14th petition was valid and the July 15th petition was a duplicate and should be dismissed.

    Procedural History

    The Commissioner moved to dismiss the petition filed on July 15, 1986, arguing it was a duplicate of the petition filed on July 14, 1986, which the Commissioner contended was the effective petition.

    The Tax Court considered the Commissioner’s motion to dismiss.

    Issue(s)

    1. Whether a petition for readjustment of partnership items filed by notice partners on the 90th day after the mailing of the Notice of FPAA, the last day of the period allowed for the tax matters partner to file, is effective to commence a partnership action under I.R.C. § 6226(b).

    Holding

    1. No, because I.R.C. § 6226(b) explicitly allows notice partners to file a petition only if the tax matters partner does not file within the initial 90-day period, and the petition by the notice partners was filed on the last day of that 90-day period, not after it.

    Court’s Reasoning

    The court focused on the statutory language of I.R.C. § 6226. Subsection (a) grants the tax matters partner 90 days to file a petition. Subsection (b) then allows notice partners to file “within 60 days after the close of the 90-day period set forth in subsection (a).”

    The court noted that the 90th day from April 14, 1986, was July 13, 1986, a Sunday. Under I.R.C. § 7503, when the last day for performing an act falls on a weekend or holiday, the deadline is extended to the next business day. Therefore, the 90-day period for the tax matters partner extended to Monday, July 14, 1986.

    The court reasoned that because the notice partners filed their petition on July 14, 1986, they filed it during, not after, the 90-day period exclusively granted to the tax matters partner. Quoting the Conference Committee report, the court emphasized that notice partners can file only “if the tax matters partner does not file a petition within the 90-day period.” H. Rept. 97-760, at 603 (Conf. 1982), 1982-2 C.B. 600, 665.

    The court cited Tax Court Rule 240(c)(1)(h), which implies that a petition filed prematurely by a notice partner is not effective. Thus, the July 14th petition was ineffective, and the July 15th petition was the valid petition that commenced the partnership action.

    Practical Implications

    This case underscores the strict adherence to statutory deadlines in tax law, particularly in partnership tax matters. It clarifies that notice partners must wait until the full 90-day period afforded to the tax matters partner has completely expired before they can effectively file their own petition for readjustment of partnership items.

    Legal practitioners handling partnership tax disputes must meticulously calculate these deadlines, considering weekend and holiday extensions, to ensure petitions are filed timely and by the correct parties. Premature filings by notice partners will not be recognized, potentially jeopardizing the partners’ rights to challenge partnership adjustments.

    This ruling emphasizes the hierarchical structure established by TEFRA (Tax Equity and Fiscal Responsibility Act) for partnership litigation, giving the tax matters partner the primary window to initiate litigation before notice partners can act.