8.19.6  Investor Cases

Manual Transmittal

October 01, 2012

Purpose

(1) This transmits revised IRM 8.19.6, Investor Cases.

Material Changes

(1) Revised IRM to reflect new organizational titles resulting from the Appeals 2012 Alignment Project.

Effect on Other Documents

IRM 8.19.6 dated June 25, 2010 is superseded.

Audience

All Appeals employees working with TEFRA investor returns.

Effective Date

(10-01-2012)


Kirsten B. Wielobob
Director, Specialty Operations

8.19.6.1  (06-01-2007)
Overview

  1. IRM 8.19.6 deals with investor cases in Appeals for consideration of non-TEFRA issues. These cases may be considered by one appeals officer before, after, or at the same time that the appeals officer or another appeals officer is considering the TEFRA partnership or S corporation key case.

  2. Although the investor case may be in Appeals at the same time as the key case, they are controlled as two separate and unrelated cases since the partnership items are considered in the unified proceeding.

  3. IRM 8.19.6 also deals with investor cases in Appeals for which Appeals has jurisdiction of the computation and assessment of the TEFRA adjustment.

8.19.6.2  (06-01-2007)
Campus Suspense Files

  1. Generally, the returns of investors in TEFRA partnerships and S corporations are not sent to Appeals with the TEFRA key case return for consideration of the partnership/subchapter S items. The investor cases are suspensed and controlled at the key case Campus TEFRA Function (CTF) if the investor cases are controlled on PCS.

    Note:

    For older cases, the investor returns may be suspensed and controlled at a CTF other than the key case CTF.

  2. The appeals officer will evaluate the TEFRA key case at the partnership level. The tax computations and assessments for investors are the responsibility of the investor CTF (also referred to as the report CTF) for investors who are not Coordinated Industry Cases (CIC) corporation, Joint Committee or other corporate specialty cases.

  3. For CIC corporation, Joint Committee or other corporate specialty cases, tax computations, assessments and statute controls are the responsibility of the Compliance function or Appeals, whichever has jurisdiction over the investor. This is true even if the key case return is in Appeals.

  4. The investor CTF also has the responsibility for TEFRA statute controls on investor returns for investors who are not CIC corporation, Joint Committee or other corporate specialty cases.

8.19.6.3  (06-25-2010)
Investor Case Statutes

  1. For any taxpayer who invests in a TEFRA entity, the Service has a minimum of two dates of expiration for the period of limitations for assessments on the taxpayer's tax return. IRC section 6501 provides the period of limitations for assessing all taxes assessed under the Code, while the period under IRC section 6501 for assessing any income tax attributable to partnership items (or affected items) for a partnership taxable year may be extended by IRC section 6229. The taxpayer will have additional expiration dates for the period of limitations if he/she is an investor in more than one TEFRA entity.

  2. Non-TEFRA issues on a taxpayer's return are always controlled by IRC section 6501. Generally, the period for assessment under IRC section 6501 is the later of three years from the date the return is due or filed, unless extended by consent. Other exceptions may apply to extend the time the IRS has to assess. See IRM 25.6.5 for more information.

  3. The limitations period for partnership items and affected items is controlled by the partner's statute under IRC section 6501, as extended by IRC section 6229(a) until such time as the partnership items become non-partnership items under IRC section 6231(b). The most common circumstance listed in subsection (b) is a TEFRA settlement executed by the Service. See IRM 8.19.1.6.9.2.1 for additional information.

  4. Once the conversion to non-partnership items occurs, the statute on the investor's return relative to such items becomes the one-year assessment statute period under IRC section 6229(f). This statute may be extended with either Form 872-F, Form 872,Form 872-A , The special language which covered items relating to TEFRA partnerships, including partnership items and affected items has now been incorporated in Forms 872 (Revision 10–2009) and 872-A (Revision October 2009). Form 872-I and Form 872-IA are obsolete.

  5. For defaulted FPAAs and entered court decisions, the statute on the investor's return is the one-year assessment statute period controlled by IRC section 6229(d). This statute may be extended with either Form 872 or Form 872A. Form 872-I and Form 872-IA are now obsolete See IRM 8.19.6.3(4) above. Form 872-F cannot be used in this situation.

  6. At least 180 days must remain on all one-year assessment dates for TEFRA investor cases which are CIC corporation, Joint Committee or other corporate specialty cases. Examination is responsible for computing and assessing the tax from all TEFRA linkages which have a one-year assessment date before the case reaches Appeals for CIC corporation, Joint Committee and other corporate specialty cases. It is at the discretion of the appeals team manager whether to accept an investor case with a one-year assessment date or to return the case to Examination for computation and assessment of the tax for TEFRA linkages with a one-year assessment date before returning the case to Appeals for consideration of the non-TEFRA issues. See IRM 8.19.6.17 for an explanation of other corporate specialty cases.

8.19.6.3.1  (06-25-2010)
Securing Investor Case Consents

  1. Form 872-F, Consent to Extend the Time to Assess Tax Attributable to Items of a Partnership or S Corporation That Have Converted to non-partnership items under IRC section 6231(b), will extend the statute of limitations for partnership items and S corporation items that have converted to non-partnership items under IRC section 6231(b). Form 872-F will also extend the statute for affected items on these partnership or S corporation items. Form 872-F is limited to one partnership or S corporation, though multiple years may be included. The most common situation where items are converted under IRC section 6231(b) is a settlement agreement. A defaulted FPAA or entered court decision does not result in the conversion of partnership items to non-partnership items. Thus, Form 872-F cannot be used in these situations.

  2. Form 872, (Revision 10-2009) Consent to Extend the Time to Assess Tax, will extend the statute for non-TEFRA adjustments (regular income tax adjustments), partnership items, affected items, partnership items converted to non-partnership items under IRC section 6231(b) (including such items arising from defaulted FPAAs and entered court decisions during the statute period under IRC section 6229(d)). Form 872 is not limited to one partnership and may include multiple years. In addition the Form 872 covers non-TEFRA adjustments. Form 872-I previously used for this purpose is obsolete.

  3. Form 872-A (Revision 10–2009), Special Consent to Extend the Time to Assess Tax, is an open-ended version of Form 872. Form 872-IA previously used for this purpose is obsolete.

  4. In Ginsburg, 127 T. C. 75 (2006), the Tax Court held that a consent that did not reference tax attributable to partnership items was not sufficient to extend the statute for affected items. As a result of Ginsburg, the Service has developed revised consents, Form 872 (Revision 10-2009) and Form 872-A (Revision 10–2009) that extends the statute of limitations when the taxpayer was either a direct or indirect partner in one or more entities that file (or should file) a Form 1065 (including a limited liability company), in the event that there are affected items at issue. This consent also extends the statute of limitations for non-TEFRA adjustments from a taxpayer's return unrelated to a partnership or a S Corporation.

    Note:

    As stated above, Form 872-F will also extend the statute for affected items, but is limited to one partnership or S corporation.

    1. If the partnership proceeding is still open as to the taxpayer, and the taxpayer declines to sign a Form 872 (Revision 10–2009) or Form 872-A (Revision 10–2009) (Form 872-F would not be applicable at this time), an affected item notice of deficiency should not be issued as it would be premature. The IRS employee who is considering the partnership case is responsible for the partnership's IRC section 6229(a) statute, which includes any affected items.

    2. If the partnership proceeding is closed as to the taxpayer (by defaulted FPAA, settlement agreement, or Court decision), and the taxpayer declines to sign a Form 872 (Revision 10–2009) or Form 872-A (Revision 10–2009) (or Form 872-F for each settled partnership or S corporation), an affected item notice of deficiency should be issued for any affected items (assuming that the taxpayer has not previously agreed to them) before the expiration of the applicable one-year statute date that was triggered by the closure of the partnership proceeding.

    3. If the partnership proceeding is closed as to the taxpayer (because a proceeding was never opened or was closed as a no-change), and the taxpayer declines to sign a Form 872 (Revision 10–2009) or Form 872-A (Revision 10–2009), an affected item notice of deficiency should be issued for any affected items (assuming that the taxpayer has not previously agreed to them) before the expiration of the IRC section 6229(a) statute date of the partnership.

  5. Any additional tax resulting from the partnership item adjustments must be assessed by the one-year statute date that was triggered by the closure of the partnership proceeding.

  6. If the taxpayer declines to sign a statute extension, the case activity record should be documented accordingly.

  7. The Service must notify the taxpayer (or authorized representative executing a consent) on each occasion when the taxpayer is requested to extend the statute by consent as to the following rights as required by IRC section 6501(c)(4)(B):

    1. The right to refuse to extend the limitations period.

    2. The right to request the extension to be limited to particular issues held open for further examination or appeal.

      Note:

      The taxpayer or their representative may request, verbally or in writing, restrictive wording on the Form 872. The Appeals employee will review the return for other issues and verify the use of a restrictive paragraph. If the use of a restrictive paragraph is approved, refer to IRM 25.6.22.8 for instructions in preparing the restrictive paragraph consent.

    3. The right to request the limitations period.

    4. Separate notification must be made to each spouse on joint returns

8.19.6.3.1.1  (06-25-2010)
Executed by Power of Attorney

  1. The power of attorney must comply with Treas. Reg. section 301.6223(c)-1(e) when signing the extension for an individual partner on either Form 872-F, Form 872 (Revision 10–2009) or Form 872-A (Revision 10–2009). See IRM 8.19.6.5.

8.19.6.3.1.2  (06-25-2010)
Consolidated Returns

  1. For consolidated corporate returns for tax years beginning before June 28, 2002, Treas. Reg. section 1.1502-77A(a) provides in part:

    "The common parent, for all purposes (other than the making of the consent required by paragraph (a)(1) of § 1.1502-75, the making of an election under section 936(e), the making of an election to be treated as a DISC under § 1.992-2, and a change of the annual accounting period pursuant to paragraph (b)(3)(ii) of § 1.991-1) shall be the sole agent for each subsidiary in the group, duly authorized to act in its own name in all matters relating to the tax liability for the consolidated return year. Except as provided in the preceding sentence, no subsidiary shall have authority to act for or to represent itself in any such matter" .

  2. For consolidated corporate returns for tax years beginning on or after June 28, 2002, Treas. Reg. section 1.1502-77(a)(1) sets forth essentially the same general rule as Treas. Reg. section 1.1502-77A(a) (quoted above), but in addition Treas. Reg. section 1.1502-77(a)(6)(iii) provides in part:

    "Members as partners in partnerships. The Commissioner generally will deal directly with any member in its capacity as a partner of a partnership that is subject to the provisions of sections 6221 through 6234 and the accompanying regulations (but see paragraph (a)(2)(ix) of this section regarding the mailing of a final partnership administrative adjustment to the common parent)" .

  3. In all cases, the consent (Form 872-F, Form 872 [Revision 10—2009], or Form 872-A [Revision 10–2009], whichever is used), should be prepared in the name of (and for the signature of) the common parent corporation as agent for the consolidated group.

    1. The name in the caption of the consent should reference both the common parent corporation and the affiliated companies. For example, where the common parent of the group is ABC Corporation, a proper caption would read: ABC Corporation and Subsidiaries.

    2. The name of the common parent should be followed by the signature and title of an officer who is authorized to bind the common parent corporation.

  4. For consolidated corporate returns beginning on or after June 28, 2002, if a subsidiary corporation that filed as part of the consolidated return was the partner in the TEFRA partnership, it is recommended that the consent also be signed on behalf of the subsidiary corporation.

    1. The name of the subsidiary corporation should be followed by the signature and title of an officer who is authorized to bind the subsidiary corporation.

    2. If there was more than one subsidiary corporation that was a partner in a TEFRA partnership, Form 13923 and Form 13924 may be used (as attachments to Forms 872 [Revision 10–2009] and 872-A [Revision 10–2009], respectively), to secure the signatures of behalf of the subsidiary corporations.

      Note:

      If either of these forms is used as an attachment, it should be referenced below the signature on behalf of the common parent on the Form 872 (Revision 10–2009) or Form 872-A (Revision 10–2009). Language such as "See Attachments 1 and 2 for additional corporate officer signatures" may be inserted below the signature on behalf of the common parent.

    3. If it is unknown whether a subsidiary corporation was a partner in a TEFRA partnership, have all of the subsidiaries that filed as part of the consolidated return sign the attachment (Form 13923 or Form 13924) to the consent (Form 872 [Revision 10–2009] or Form 872-A [Revision 10–2009]), if practical (i.e., when there are only a few subsidiaries).

8.19.6.4  (06-01-2007)
Investor Case Research

  1. The Partnership Control System (PCS) is a separate database for pass-through entity information. PCS interfaces with Master File and AIMS. The information in PCS includes TEFRA and non-TEFRA information for linked pass-through entities and their investors.

    1. Use the PCS database to assist in resolving an investor's case.

    2. See IRM section 8.19.5.19 for an overview of PCS and references to complete PCS information.

8.19.6.5  (06-01-2007)
Investor Power of Attorney

  1. An investor power of attorney for other tax matters such as non-TEFRA items does not cover partnership items and affected items unless the power of attorney so states. See Treas. Reg. section 301.6223(c)-1(e), in respect of partnership proceedings that began on or after January 2, 2002.

  2. For a Form 2848 to cover both partnership items and non-partnership items, the partner should state in the power of attorney that authority for both matters is granted to the representative. Authority to represent a partner for penalties and other affected items is granted to the representative in the same way as is representation on partnership items.

  3. On the Form 2848 a partner may indicate his intent to delegate representation on his partnership items. The Form 2848 should show the following:

    • Type of tax: "Partnership items" and Tax form number: "Form 1065" or

    • "The acts authorized by this power of attorney include representation for the purposes of subchapter C of Chapter 63 of the Internal Revenue Code."

    If the partnership items and Form 1065 or the authorization language are not included on the power of attorney, the representative may not be authorized to discuss partnership items, penalties, and other affected item issues.

8.19.6.6  (10-01-2012)
Receiving Investor Cases

  1. Investor cases will be established as separate work units on ACDS and will be closed separately when a decision is reached on the non-TEFRA issues.

  2. If the investor's case is received in Appeals after the partnership examination is started, the file will contain the following documents:

    1. Form 5546 (Notification Charge Out) and/or Form 6658 (Notice of Special Investor Action) stamped "TEFRA."

    2. Schedule K-1.

  3. If the investor's case is received in Appeals before the partnership examination is started, the key case CTF will notify Appeals when the partnership examination is started. They will mail to Account and Processing Support the documents shown in paragraph (2) above, and the CTF may also request a copy of the return. The appeals officer will send a copy of the requested return as soon as it is requested.

8.19.6.7  (06-01-2007)
Settlement Computations and Agreement Forms

  1. For investor cases linked on PCS which are not CIC corporation, Joint Committee or other corporate specialty cases:

    1. The CTF has the responsibility to prepare computations on investor cases to reflect TEFRA key case adjustments.

    2. Appeals will prepare computations of the non-TEFRA adjustments only for these investor cases.

    3. In the event that Appeals does a courtesy computation for the investor to show the tentative tax from TEFRA adjustments before the CTF completes its calculations, no assessment of the tax should be made by Appeals.

  2. For investor cases which are CIC corporation, Joint Committee or other corporate specialty cases:

    1. Appeals prepares computations and makes assessments if the investor is in Appeals jurisdiction.

    2. If the case is in Compliance jurisdiction, the Compliance function makes the computations and assessments on the investor cases to reflect TEFRA key case adjustments.

8.19.6.7.1  (10-01-2012)
TEFRA Issues Resolved Before Non-TEFRA Issues

  1. If the TEFRA partnership or S corporation key case is settled, the CTF will process the partnership or S corporation adjustments for the investors who are not CIC corporation, Joint Committee or other corporate specialty cases. The CTF will send a copy of the computations ( Form 5344 and Form 1902-C to Account and Processing Support. Account and Processing Support will forward these documents to the appeals officer. The appeals officer will associate these documents with the investor file for use in preparing settlement computations.

  2. If Appeals did not receive the Form 5344 and Form 1902-C, and there are indications in the case file that the taxpayer is a party to a TEFRA proceeding, the appeals officer or tax computation specialist will request a transcript for that investor prior to preparation of the audit statement or closing documents for the non-TEFRA adjustments. If necessary, request copies of the TEFRA computations from the taxpayer or the CTF.

    Note:

    In the very rare instance when Appeals will assess the TEFRA deficiency for an investor which is not a CIC corporation, Joint Committee or other corporate specialty case, see IRM 8.19.6.9. for the IRC section 6601(c) comment for the Form 5402.

  3. If the TEFRA adjustments have been made and assessed before the non-TEFRA adjustments, as noted in paragraphs (1) and (2) above, the tax computation specialist will combine the TEFRA examination results with taxable income to produce the corrected taxable income when the non-TEFRA adjustments are computed.

  4. If unagreed, follow normal procedures for preparation and issuance of a statutory notice of deficiency. The notice will show only non-TEFRA adjustments. Include TEFRA issues in taxable income as previously adjusted and tax as previously adjusted.

  5. If the taxpayer has an IRC section 6405(a) refund in excess of $2,000,000 and the criteria of IRM 8.9.1 are met, an expedited refund report should be submitted to the Joint Committee. See IRM 8.19.6.12.

8.19.6.7.2  (10-01-2012)
Non-TEFRA Issues Finalized Prior to Resolution of TEFRA Issues

  1. If non-TEFRA issues are settled when the TEFRA proceeding remains open and the case is in non-docketed status, take the following actions:

    1. Secure the normal closing documents (Form 870 or Form 870-AD).

    2. Calculate the partial computations taking into account TEFRA items as reported on the return.

    3. Type on the reverse side of the Form 870 or Form 870-AD language to the effect that any change to the deficiency caused by resolution of the TEFRA proceeding can be assessed at the conclusion of the TEFRA proceeding as a computational adjustment. See IRM Exhibit 8.19.4-27 for approved language.

    4. If the taxpayer will not sign the agreement form with this language, issue a statutory notice of deficiency, and, if issued, compute the deficiency using a Munro computation. See IRM 8.19.4.11 and IRM Exhibit 8.19.4-28.

    5. For partnership tax years ending after August 5, 1997, if the non-TEFRA adjustments do not create a deficiency because the return was over-sheltered under IRC section 6234, issue a notice of adjustment for over-sheltered returns. See IRM 8.19.4.11 and IRM Exhibit 8.19.4-30.

      Note:

      If the return is over-sheltered but the non-TEFRA adjustments create a deficiency, use a Munro computation instead of a notice of adjustment.

  2. If the non-TEFRA issues are settled when the TEFRA proceeding remains open and the case is in docketed status, take the following actions:

    1. Calculate the deficiency taking into account TEFRA items as reported on the return.

    2. Include in a stipulated decision document language to the effect that any change to tax liability caused by resolution of the TEFRA proceeding can be assessed at the conclusion of the TEFRA proceeding as a computational adjustment. IRM Exhibit 8.19.4-29 for the approved language.

    3. Secure an agreement from the taxpayer to use the Munro stipulation early in the proceeding. If the taxpayer does not agree, area counsel may need to move for an increased deficiency unless a Munro computation was used in the notice of deficiency.

  3. If the non-TEFRA issues are unagreed and it is necessary to issue a statutory notice of deficiency prior to the resolution of the TEFRA issues, prepare the notice of deficiency as discussed in IRM 8.19.4.10 and IRM 8.19.4.11.

    1. For partnership taxable years ending after August 5, 1997, if the return is over-sheltered, and the unagreed non-TEFRA adjustments do not create a deficiency, IRC section 6234 provides for issuance of a notice of adjustment. If the return is over-sheltered and the unagreed non-TEFRA adjustments create a deficiency, prepare a Munro computation as shown in IRM Exhibit 8.19.4-28.

    2. For partnership taxable years ending after August 5, 1997, if the return is not over-sheltered, prepare a Munro computation as shown in IRM Exhibit 8.19.4-28.

    3. For pass-through entity taxable years ending before August 6, 1997, prepare a Munro computation as shown in Exhibit 8.19.4-28.

  4. If the case is closed because the statutory notice (discussed in paragraph (3) above) has defaulted, take the following actions:

    1. Account and Processing Support will prepare a Form 3198 as discussed in IRM 8.19.5.18.4(1)(d) or IRM 8.19.5.18.4(2)(d), depending on the type of case. The tax computation specialist will clearly mark the Form 5278 in the audit statement or statutory notice as containing a Munro computation.

    2. Because we wish to retain unaltered copies of the documents sent to the taxpayers, the tax computation specialist will write the word Munro in large red letters on a separate slip of paper that then should be attached to the lower right-hand corner of the Form 5278 in the audit statement or statutory notice.

8.19.6.8  (06-01-2007)
Penalties on Investor Cases

  1. When a taxpayer is in Appeals for a penalty issue and the taxpayer remains a party to an open TEFRA proceeding, the appeals officer must consider the potential TEFRA adjustments to determine whether or not the penalty meets any required floor for assertion. In the ACM, the appeals officer will explain the consideration of potential TEFRA adjustments in computing the required floor for assertion of the penalty. When considering the hazards to litigation of the penalty, take into account the potential TEFRA adjustments in determining the floor for assertion.

  2. If the substantial valuation misstatement ( IRC section 6662(b)(3)) or the substantial understatement of income tax ( IRC section 6662(b)(2)) penalty applies but is mathematically zero for the partial audit statement, the tax computation specialist will make the necessary statement on the first page of the audit statement. See IRM 8.19.4.12(2) for the necessary statement.

  3. If the penalty does not apply to all the adjustments, the tax computation specialist will list the adjustments to which the penalty is attributable for future recomputation by the CTF when the TEFRA issues are resolved.

  4. Tax computation specialists will generally prepare the schedule of items to which the penalty will apply. See Treas. Reg. section 301.6231(a)(5)-1(e).

  5. For partnership tax years ending after August 5, 1997, the penalties determined at the partnership level must be assessed within the one-year period even if an affected item notice of deficiency to assess the deficiency resulting from partnership adjustments is required. Issuing a statutory notice of deficiency does not suspend the period for assessing the penalties.

8.19.6.9  (10-01-2012)
Investor Case Closings

  1. The appeals officer will determine the proper routing of the investor case file by researching PCS. The appeals officer will note the proper routing in the remarks of the Form 5402 for Account and Processing Support. After closing, Account and Processing Support will forward cases with an open TEFRA linkage to the appropriate destination as follows:

    1. CIC corporation, Joint Committee or other corporate specialty case files should be sent to the appropriate Examination Technical Services unit based on the location of the originating Examination group.

    2. All other case files should be sent to the key case CTF.

      Note:

      Account and Processing Support will determine the CTF to forward the case with a PICF code of 5 as follows: Order a TSINQP on each year of the key case. If the TSINQP shows OSC in the CTF-CD, then the CTF is Ogden. If the TSINQP shows BSC in the CTF-CD, then order a TXMODC on the key case. If there is data, look in the "Control Base and History Information" section; if the "Assign To" column has numbers that begin with 0179, then the CTF is Brookhaven. If there are no numbers in the "Assign to" column, then Ogden is the CTF.

  2. If a TEFRA audit remains open, the assessments to the non-TEFRA issues must be done as partials. However, the ACDS closings will be done as a full closure. For details on closing procedures, refer to IRM 8.19.5.18.

  3. For partnership tax years beginning after August 5, 1997, in the case of a partner's settlement under IRC section 6224(c), interest is suspended under IRC section 6601(c) starting 30 days after the settlement agreement is executed by the Commissioner's delegate and ending with notice and demand. See IRC section 6601(c). In the case of a CIC corporation, Joint Committee or other corporate specialty case, when the taxpayer enters into a TEFRA settlement, the appeals officer assigned the partner return will secure a computation and assessment of the deficiency as quickly as possible in order to minimize the loss of interest. If the appeals team case leader or appeals team manager deems it necessary to extend the one-year assessment date to avoid the expense of time consuming computations while the investor case is in Appeals for non-TEFRA consideration, the appeals officer will encourage an advance payment of tax.

    Note:

    The appeals officer will include a comment in the remarks of the Form 5402 asking Account and Processing Support to use restricted interest when interest suspension under IRC section 6601(c) applies. The comment will include the amount of deficiency from each TEFRA linkage to be assessed, the name of the TEFRA key case, and the date the settlement agreement accepted on behalf of the Commissioner. If multiple TEFRA linkages will be assessed, there must be an IRC section 6601(c) comment for each TEFRA linkage to which IRC section 6601(c) suspension of interest applies. The tax computation specialist may assist in the preparation of the IRC section 6601(c).

  4. In a very rare instance, Appeals will make the computation and assessment of a deficiency from TEFRA adjustments when the partner is not a CIC corporation, Joint Committee or other corporate specialty case. For timely filed individual returns for tax years ending after July 22, 1998, interest is suspended if IRS did not give a 6404(g) notice within 18 months of the filing date or due date (without regard to extensions), whichever is later. The interest suspension ends 21 days after 6404(g) notice is given. For TEFRA partnerships, 6404(g) notice is the earlier of the Form 5701, summary report, 60-day letter, Appeals Settlement Letter, or FPAA. Notice is deemed given to the partners when the notice is given to the TMP provided the notice includes the reason for the liability. Even though the TEFRA notice does not include the partner's liability, the partner can compute the liability from the adjustments to the partnership return. For timely filed individual returns with tax years ending after July 22, 1998, the appeals officer will note on the Form 5402 in remarks that 6404(g) applies and refer Account and Processing Support to the 6404(g) worksheet attached. The worksheet will include the following information in respect to the TEFRA partnership:

    1. Name of TEFRA partnership

    2. Section 6404(g) notice date and form of notice ( Form 5701, summary report, 60-day letter, Appeals Settlement Letter, or FPAA)

    3. Amount of deficiency to which 6404(g) applies for this TEFRA partnership

      Note:

      If multiple TEFRA partnership linkages will be assessed on a timely filed individual taxpayer with a tax year ending after July 22, 1998, a 6404(g) worksheet must be included for each partnership.

8.19.6.10  (02-05-2008)
Use of Closing Agreements

  1. When a closing agreement is entered into for non-TEFRA issues, the closing agreement should contain language which states that the taxpayer is an investor in a TEFRA partnership or S corporation, and that the closing agreement does not cover adjustments concerning the tax treatment of the TEFRA partnership or S corporation.

  2. For additional information refer to IRM 8.13.1, Processing Closing Agreements in Appeals, IRM 8.19.1.6.11, and IRM 8.19.2.10.4.

8.19.6.10.1  (02-05-2008)
Form 866 - Agreement as to Final Determination of Tax Liability

  1. Final determinations of tax liability pursuant to IRC section 7121 are ordinarily reflected on Form 866, Agreement As To Final Determination of Tax Liability.

  2. If the taxpayer is an investor in a TEFRA pass-through entity, the Form 866 should include the following statement in the Determination section:

    "This agreement does not cover a deficiency or overassessment resulting from adjustments made under Subchapters C and D of Chapter 63 in Subtitle F of the Internal Revenue Code concerning the tax treatment of partnership and Subchapter S items determined at the partnership and corporate level."

8.19.6.10.2  (02-05-2008)
Form 906 - Closing Agreement on Final Determination Covering Specific Matters

  1. Final determinations of specific matters pursuant to IRC section 7121 are ordinarily reflected on Form 906, Closing Agreement on Final Determination Covering Specific Matters.

  2. If the taxpayer is an investor in a TEFRA pass-through entity, Form 906 should include the following statement in the Determination section:

    "This agreement does not cover adjustments made under Subchapters C and D of Chapter 63 in Subtitle F of the Internal Revenue Code concerning the tax treatment of partnership and Subchapter S items at the partnership and corporate level."

8.19.6.11  (06-01-2007)
Innocent Spouse Relief

  1. A taxpayer may claim relief from joint and several liabilities under IRC section 6015 (sometimes called "Innocent Spouse Relief" ) as a defense to an adjustment.

  2. Unique issues arise in the context of the TEFRA provisions when applied to persons who file a joint return. The appeals officer may encounter a situation where a spouse of an investor in the TEFRA case seeks relief from joint and several liability. This situation may arise in any number of scenarios such as when an appeals officer is considering a claim filed for innocent spouse relief or a Collection Due Process case.

  3. For innocent spouse Appeals procedures, see generally IRM 25.15.12 (Relief from Joint and Several Liability, Appeals Procedures). For innocent spouse procedures relating to TEFRA closing agreements, see IRM 25.15.1.2.8 (Relief from Joint and Several Liability, TEFRA Settlement Agreements).

8.19.6.11.1  (06-01-2007)
Post Assessment Requests for Innocent Spouse Relief

  1. The Restructuring and Reform Act of 1998 (RRA 98) gave taxpayers the right to a due process hearing with Appeals when they receive a Notice of Federal Tax Lien Filing or a Notice of Intent to Levy. A taxpayer may raise any relevant issue related to the unpaid tax or proposed levy including spousal defenses, such as relief under IRC section 6015.

  2. Upon receipt of the computational adjustments, a spouse or former spouse of an investor in a TEFRA partnership or S corporation may request innocent spouse relief by filing Form 8857, Request for Innocent Spouse Relief. If the claim is denied it will be forwarded to an appeals officer for consideration of the innocent spouse issue.

  3. The appeals officer may find that the unpaid liabilities relate to adjustments of TEFRA partnership or S corporation items, including penalties, additions to tax, and affected items.

    Caution:

    The treatment of partnership items must be resolved before innocent spouse relief is granted. The appeals officer and appeals team manager must never propose to change the partnership item determination. The appeals officer will address only the innocent spouse issue.

  4. If the taxpayer entered into a specific matters closing agreement, innocent spouse relief is available unless the closing agreement addressed the innocent spouse issue. If the taxpayer entered into an agreement for final determination of tax liability, innocent spouse relief may or may not be available depending on whether the agreement was signed pursuant to IRC section 6224(c). See Treas. Reg. section 1.6015-1(c)(2).

8.19.6.11.2  (02-05-2008)
Pre-assessment Requests for Innocent Spouse Relief

  1. Innocent spouse relief cannot be granted prior to the assessment of the tax relating to TEFRA partnership or S corporation adjustments.

  2. Taxpayers requesting innocent spouse relief prior to the assessment of the deficiency should be directed to contact the IRS employee with jurisdiction of the pass-through entity return to resolve the issues raised in the TEFRA examination. Form 8857, Request for Innocent Spouse Relief, should be filed after the assessment is made.

  3. The existence of an open TEFRA linkage should not prevent resolution of the innocent spouse relief issue regarding non-TEFRA issues and TEFRA issues that have been assessed. If a taxpayer wants to obtain innocent spouse relief from potential liability due to the open TEFRA linkage, the taxpayer may file another Form 8857 to request innocent spouse relief from the TEFRA liability after the assessment for the open TEFRA linkage is made.

8.19.6.12  (02-05-2008)
Closing Joint Committee Investor Cases

  1. Special procedures have been developed to supplement the Joint Committee on Taxation reporting requirements of IRM 8.7.9 in situations where the return of one taxpayer involves both TEFRA and non-TEFRA issues.

  2. Also, see Delegation Order 4-18 (formerly D.O. No. 154), as revised in Delegation of Authorities for the Examining Process, IRM 1.2.43.4.

8.19.6.12.1  (06-01-2007)
Source of Refunds

  1. Prepare a report to the Joint Committee when any one of the following sources result in a refund to a taxpayer in excess of $2,000,000:

    1. Audit of a TEFRA partnership/S corporation return in which the taxpayer is an investor.

    2. Audit of the investor's return.

    3. AAR filed by a TMP on behalf of a partnership/S corporation in which the taxpayer is an investor.

    4. AAR filed by any partner/shareholder.

    5. Refund claim based on non-TEFRA items.

8.19.6.12.2  (06-01-2007)
Referral of Investor Cases to the Joint Committee When the Investor's TEFRA Issues are Completed Before the Non-TEFRA Issues

  1. The Appeals or Compliance employee with jurisdiction of the investor case is responsible for ensuring that a report is made to the Joint Committee when the TEFRA adjustments result in a refund in excess of $2,000,000 to the taxpayer. See Exhibit 8.19.6-3. and Exhibit 8.19.6-4. for sample Joint Committee on Taxation letters when the refund results from TEFRA partnership adjustments.

  2. The appeals officer who considered the appeal of the partnership, if applicable, should cooperate as much as possible with the employee preparing the Joint Committee on Taxation report for the investor, if so requested.

  3. When the investor case is in Appeals jurisdiction, the appeals officer should determine the need for a Joint Committee referral on TEFRA issues when the tax computations are made at the investor level. The appeals officer will not suspend a report to the Joint Committee for a refund from TEFRA issues waiting on the outcome of the non-TEFRA issues.

    Note:

    See IRM 8.19.6.17.1., Statute for Investor's Case, describes the Appeals Office responsibilities for statute protection.

  4. Do not add the refund from TEFRA adjustments to the refund from non-TEFRA adjustments to determine if a Joint Committee referral is needed. These are separate refunds and, if a referral to the Joint Committee is necessary, report the TEFRA refund to the Joint Committee separately from the report of the non-TEFRA refund.

    Example:

    If a case results in a refund due to TEFRA issues of $1,400,000 and a refund due to non-TEFRA issues of $800,000, do not refer the case to the Joint Committee. Both the TEFRA refund and the non-TEFRA refund are less than $2,000,001.

    Example:

    If a case results in a refund due to TEFRA issues of $300,000 and a refund due to non-TEFRA issues of $2,500,000, refer the non-TEFRA issues to the Joint Committee. Do not refer the TEFRA issues to the Joint Committee. It does not matter whether the TEFRA issues or the non-TEFRA issues are completed first for determining whether to refer to the Joint Committee.

    Example:

    If a case results in a refund due to non-TEFRA issues of $300,000 and a refund due to TEFRA issues of $2,500,000, refer the TEFRA issues to the Joint Committee. Do not refer the non-TEFRA issues to the Joint Committee. It does not matter whether the TEFRA issues or the non-TEFRA issues are finished first for determining whether to refer to the Joint Committee.

    Example:

    If a case results in a refund due to TEFRA issues of $2,500,000 and a refund due to non-TEFRA issues of $3,000,000, do not combine the TEFRA and non-TEFRA issues in the same report to the Joint Committee. Issue two separate reports, one for the TEFRA issues and one for the non-TEFRA issues.

    Note:

    If a case results in a refund due to TEFRA issues of $2,000,001 and a deficiency due to non-TEFRA issues of $3,000,000, refer the TEFRA issues to the Joint Committee. Do not net the TEFRA issues with the non-TEFRA issues for determining whether to refer to the Joint Committee.

8.19.6.12.2.1  (10-01-2012)
Closing Procedures for Investor Cases When the Investor's TEFRA Issues are Completed Before the Non-TEFRA Issues

  1. The Appeals or Compliance employee with jurisdiction over the investor will be responsible for seeing that a Joint Committee report is made when the TEFRA adjustments result in a refund in excess of $2,000,000 to the investor.

  2. The settlement agreement Form 870-P, Form 870-PT, Form 870-S, Form 870-P(AD), Form 870-PT(AD), Form 870-L(AD), Form 870-LT(AD), or Form 870-S(AD), showing the correct treatment of the partnership (S corporation) items, will have been secured from the partner (shareholder) and executed by the appeals team manager or appeals team case leader. Do not add the qualifying language referred to in IRM 8.9.1.2.5 to the agreements. Close the partnership case following established procedures.

  3. When the non-TEFRA issues are resolved (settled or litigated), the appeals officer will prepare an ACM and Form 5402 to close the case. Account and Processing Support will prepare a Form 5403.

  4. If the final determination on the investor's non-TEFRA issues results in a refund to the investor in excess of $2,000,000, prepare a report to the Joint Committee for the non-TEFRA issues. Also the appeals officer will secure from the investor the appropriate agreements (Form 870 or Form 870-AD ) with the qualifying language typed on the agreement as required by IRM 8.9.1.2.5.

  5. The procedures in IRM 8.7.9 will then be followed in submitting the report to the Joint Committee and closing the case. If the non-TEFRA issues do not create a refund in excess of $2,000,000, do not send a report to the Joint Committee for the non-TEFRA issues.

  6. If the taxpayer had an IRC section 6405(a) refund and the criteria of IRM 8.9.1.5.1.1 are met, an expedited refund report should be submitted to the Joint Committee.

    Note:

    Closing Agreements, if applicable, must not be executed on behalf of the Service until after the "Report and Wait" requirements of IRC section 6405 have been meet. Thus, the Service must not execute the Closing Agreement until the case clears Joint Committee.

8.19.6.12.3  (06-01-2007)
Referral of Investor Cases to the Joint Committee When the Investor's Non-TEFRA Issues are Completed Before the TEFRA Issues

  1. On all potential Joint Committee cases the appeals officer should secure an AMDISA and TSUMY to determine whether the taxpayer is a party to a TEFRA proceeding before making a report to the Joint Committee on Taxation on the non-TEFRA issues. If the taxpayer is a party to a TEFRA proceeding, the Joint Committee on Taxation report must be modified as discussed in IRM 8.19.6.12.3.1 . See also See Exhibit 8.19.6-1 and Exhibit 8.19.6-2..

  2. Appeals officers will not suspend Joint Committee referrals on investor cases under Appeals jurisdiction for non-TEFRA issues to wait for the results of a TEFRA proceeding.

8.19.6.12.3.1  (02-05-2008)
Closing Procedures for Investor Cases When the Investor's Non-TEFRA Issues are Completed Before the TEFRA Issues

  1. The appeals officer will secure from the partner a signed agreement ( Form 870 or Form 870-AD), as appropriate, for the non-TEFRA issues with the qualifying language typed on the agreement as required by IRM 8.7.9.5.5. Prepare an appeals case memorandum on the investor's case and complete all other documents necessary to close the case.

  2. Prepare a Joint Committee report, similar to Exhibit 8.19.6-1. or Exhibit 8.19.6-2, and forward to the Joint Committee for review of the non-TEFRA issues even though the review of the TEFRA partnership case has not been completed. Exhibit 8.19.6-1 may be used if the taxpayer has requested an expedited refund. See IRM 8.7.9 and IRC section 6405(a). The report for the expedited refund must include a brief explanation for the early submission.

    Example:

    The partner's subsequent year return is affected by the year under Appeals consideration.

    Example:

    The partner is awaiting an expedited refund and there are no expected collection problems.

    Example:

    The closing of the partnership case will be delayed because of litigation, a criminal investigation, bankruptcy, or for some other reason.

  3. After the unified TEFRA proceedings are completed, do not make a further Joint Committee report on the investor's case to cover these TEFRA proceedings unless the adjustments to the investor from the partnership case results in an additional refund to the investor in excess of $2,000,000. Follow this procedure even if the partnership items are treated as nonpartnership items with respect to the investor.

    Note:

    Closing Agreements, if applicable, must not be executed on behalf of the Service until after the "Report and Wait" requirements of IRC section 6405 have been met. Thus, the Service must not execute the Closing Agreement until the case clears Joint Committee.

8.19.6.13  (06-01-2007)
Failure to File Return – Investor

  1. If an investor does not file a return, it will be the responsibility of Compliance to take necessary action to secure the delinquent return. Local procedures may vary. See IRM 4.31.2.6.10 for information about procedures taken by the Compliance function when an investor fails to file a return.

  2. The filing date of an investor’s return starts the three-year assessment limitation period under IRC section 6501. The unextended IRC section 6501 statute and IRC section 6229(a) govern the period for assessment for any tax attributable to partnership items or affected items with respect to any partners.

  3. Adjustments made to an investor’s return for partnership items are computational, and the Service has one year to make the assessment. This one-year assessment period begins with one of the following events (whichever is applicable):

    1. The date of conversion to a non-partnership item (for example, by settlement, prompt assessment or jeopardy assessment).

    2. 150 days after an FPAA is mailed to a TMP if the FPAA defaults.

    3. The date a court decision becomes final.

  4. Failure to file allows the Service to assess at any time (i.e., after we generate a substitute for return and issue a notice of deficiency).

  5. An investor who contests a computational assessment may file a claim for refund under IRC section 6230(c).

8.19.6.14  (06-01-2007)
Working Investor Cases When Key Case File Is Destroyed

  1. The statute for collection of tax is 10 years and the retention period for key case administrative files is less. Because of this, investor cases (for example, offers in compromise and claims) may come to Appeals after IRS destroyed the key case administrative file under the retention period guidelines.

  2. To assist appeals officers with appeals of such investor cases, guidelines are provided for situations when part of the records needed are destroyed with the key case administrative file.

8.19.6.14.1  (06-01-2007)
Source of Investor Cases

  1. After tax from the adjustment of TEFRA partnership items is assessed, Appeals may receive the investor case for consideration from any of the following sources:

    1. Protest of 30-day letter adjusting affected items or penalties.

    2. Counsel referral of a Tax Court petition of a statutory notice of deficiency for affected items or penalties.

    3. Protest of the denial of an offer in compromise based on doubt as to liability.

    4. Protest of the denial of a claim for refund.

8.19.6.14.2  (06-01-2007)
Contents of Investor Case File

  1. The investor file generally includes these items:

    1. Investor’s return.

    2. Schedule K-1.

    3. Form 886-Z(C) for the investor from the key case.

    4. Investor campus workpapers and Form 4318.

    5. Penalty information.

  2. The file should also include documents that authorize the assessment of tax based on the adjustment of partnership/S corporation items:

    • Decision document

    • Settlement agreement

    • FPAA

  3. The file should also include TEFRA letters sent to the investor such as the following:

    1. Cover letter for computational adjustment.

    2. Investor’s tax computation for the TEFRA items adjusted (RAR).

    3. Statutory notice of deficiency for affected items or penalties, if applicable.

    4. Correspondence to or from the investor after the computational report.

8.19.6.14.3  (06-01-2007)
Additional Sources of Information

  1. Examine the investor case file carefully for documents. The investor case file may contain all the documents to complete Appeals consideration.

  2. Request the key case administrative file if needed. Do not assume it was destroyed or misplaced just because you did not receive it.

  3. Contact the key case CTF for the certified mailing records for its key cases. See IRM 4.29.5.2.2 for NBAPs and IRM 4.29.5.2.4 for FPAAs.

  4. The key case CTF maintains certain records for its key cases for a period after the final closing. Contact the key case CTF for records located in the CTF. Local procedures may vary.

  5. Additional actions to consider are these:

    1. Secure a transcript for statute information.

    2. Secure a TSINQI for the investor.

    3. Contact the key case appeals officer, key case attorney or key case revenue agent.

    4. Contact the TMP and/or the partnership’s representative.

    5. Research the tax services for previous litigation by other investors in this key case.

    6. Use the internet to find TMP’s and/or partnership’s representatives.

    7. Use the IRS global e-mail address book to find IRS employees associated with the key case.

  6. Contact your area TEFRA coordinator for additional guidance.

8.19.6.15  (06-01-2007)
Bankruptcy

  1. A bankruptcy filing by a key case entity has no effect on the administration of a TEFRA partnership proceeding. See Chef’s Choice Produce, Ltd. v. Commissioner, 95 T.C. 388 (1990). The applicability of the TEFRA procedures is determined at the end of the tax year with respect to which a partnership proceeding is conducted.

  2. The dissolution, termination or bankruptcy of a partnership in a later year has no effect on the outcome of a partnership action filed with respect to the years when the partnership was in existence. However, the bankruptcy of a partnership may require notice to a state official. Consult state law to determine the official to notify of legal proceedings concerning a dissolved partnership. This is usually the Secretary of State.

    Note:

    In Chef’s Choice, the Tax Court indicated that it might not be necessary to provide notice to state officials. Consult associate area counsel for specific guidance on this.

  3. A bankruptcy filing by a tier partnership should generally be treated the same as the bankruptcy of a key case partnership. The indirect partners should be treated as if the tier partnership was not named in a bankruptcy petition. However, if an indirect partner files for bankruptcy, treat the indirect partner the same as any other investor filing for bankruptcy.

  4. A bankruptcy filing by an investor can have a significant effect on the administration of a TEFRA partnership proceeding. The filing of the bankruptcy petition removes the investor from the TEFRA proceeding and converts the investor’s partnership items to non-partnership items. As a result, a bankrupt investor cannot serve as TMP.

    Note:

    Partnership items do not convert to non-partnership items, however, if the bankruptcy petition is filed after the partnership items have been finally determined under TEFRA procedures. Treas. Reg. section 301.6231(c)-3(a). For these purposes, a defaulted FPAA is considered a final determination of the partnership item.

8.19.6.15.1  (06-25-2010)
Effect of Bankruptcy on Investor Case

  1. The filing of a petition in bankruptcy is one of the special enforcement areas that convert the investor’s partnership items to non-partnership items (Treas. Reg. section 301.6231(c)-(7)(a)).

  2. Treas. Reg. section 301.6231(c)-7(a) can be reduced to a simple three-part test. The items convert if:

    1. the partnership taxable year has ended;

    2. the partner's taxable year in which the partnership items are reported has ended; and

    3. the bankruptcy proceeding is still open at the time the partner's year ends so that a claim (secured, administrative, priority, or general unsecured) could be filed against the partner.

  3. It may be difficult to determine whether a claim could be filed against the partner in a bankruptcy case where the debtor is an individual. In Katz v. Commissioner, 335 F.3d 1121 (10th Cir. 2003), a case involving an individual Chapter 7 debtor, the Court held that the debtors partnership items arising in 1990, the year that the bankruptcy petition was filed, did not convert on the petition date because the debtor did not elect to split the 1990 tax year into two short taxable years pursuant to IRC section 1398(d)(2). Thus, the debtor's 1990 taxes were treated as post-petition debt of the debtor that could not be claimed in the bankruptcy case. It followed that the latest taxable year of the debtor-partner with respect to which the United States could file a claim for income tax due in the bankruptcy proceeding was 1989, not 1990. The debtor's bankruptcy failed to convert the 1990 partnership items even though the partnership items may effect the bankruptcy estate's liability by virtue of the debtor's partnership interest having passed to the estate. If you have a Chapter 7 or Chapter 11 bankruptcy case and a post-petition tax year, please consult Area Counsel to determine whether a claim could be filed against the partner.

  4. The filing of a petition in bankruptcy also starts the one-year assessment period under IRC section 6229(f). Within one year of the filing of the bankruptcy petition, the tax must be assessed after the investor signs a waiver of assessment (Form 870 or Form 870-AD) under the deficiency procedures or the IRS must issue a statutory notice of deficiency. The one-year assessment date may be extended with Form 872-F, Form 872 (Revision 10–2009), or Form 872-A (Revision 10–2009).

    Note:

    For bankruptcy petitions filed on or after October 22, 1994, there is no longer a prohibition against assessing or collecting tax. Consequently, the period of limitation on assessment is not stayed by the bankruptcy filing. (See 11 U.S.C. 362(b)(9).)

  5. If a joint return is filed, and one spouse owns a separate interest in the partnership, and that spouse files for bankruptcy, the partnership items convert to non-partnership items for that spouse. The spouse who was a partner only by virtue of filing a joint return is no longer considered a partner in the partnership. See Treas. Reg. section 301.6231(a)(2)-1.

  6. If a joint return is filed, and one spouse owns a separate interest in the partnership, and the other spouse files for bankruptcy, the partnership items for the spouse who owns the interest do not convert to non-partnership items. However, the spouse that does not have an interest is no longer treated as a partner. See Treas. Reg. section 301.6231(a)(2)-1.

  7. If a husband and wife own a joint interest in a partnership, each spouse is treated as a separate partner. Therefore, if one spouse files for bankruptcy, only the partnership items of the spouse filing for bankruptcy convert to non-partnership items. The spouse who did not file for bankruptcy continues as a partner in the partnership proceeding. Deficiency procedures would apply to the spouse filing for bankruptcy. See Treasury Reg. section 301.6231(a)(2)-1.

    Caution:

    Both spouses may be treated as having a joint interest by virtue of living in a community property state.

  8. The bankruptcy of a consolidated group member converts that member's separately held partnership items to non-partnership items for all group members. The other members of the consolidated group will no longer be considered partners under IRC section 6231(a)(2)(B) with respect to the bankrupt corporation's separately held items.

    Example:

    A corporation that is a member of a consolidated group and holds a separate interest in a partnership declares bankruptcy. Its partnership items convert to non-partnership items. After these items convert to non-partnership items, the other non-partner members of the consolidated group who are severally liable for these items will no longer have their tax liability determined by reference to these items as "partnership items."

  9. IRC section 6229(h) provides for a suspension of the running of the period of limitations with respect to the bankrupt partner while the bankruptcy proceeding prohibits assessment plus 60 more days. There is no longer a prohibition against assessment, making this provision inapplicable. It is strongly recommended that a statutory notice of deficiency be issued. (See 11 U.S.C. 362(b)(9).)

  10. Treasury Reg. section 301.6229(b)-2 provides that a statute extension signed by a bankrupt partner who would be the TMP except for the bankruptcy is binding on all partners in the partnership unless the IRS was notified of the bankruptcy proceeding in accordance with Treasury Reg. section 301.6223(c)-1. (For partnership taxable years beginning prior to October 4, 2001, see Temporary Treas. Reg. section 301.6229(b)-2T.)

    Note:

    This pertains to extensions signed after August 5, 1997.

  11. Any agreement to extend the statute of limitations signed by a tax matters partner before the date of his personal bankruptcy remains valid.

  12. The TMP’s bankruptcy will not toll the statute of limitations. See Tempest Associates v. Commissioner, 94 T. C. 794 (1990).

8.19.6.15.2  (06-25-2010)
Effect of Investor Bankruptcy on Statute of Limitations

  1. When a partner files for bankruptcy, the bankrupt partner’s partnership items are converted to non-partnership items if the partnership items were not previously converted. The conversion to non-partnership items is permanent. There is no reinstatement even if the bankruptcy is dismissed or discharged.

  2. The one-year assessment date per IRC section 6229(f) begins on the day the petition naming the investor in a bankruptcy proceeding is filed. See Treas. Reg. section 301.6231(c)-(7)(a). The one-year assessment date may be extended with Form 872-F, Form 872 (Revision 10–2009) or Form 872-A (Revision 10–2009).

  3. If a partner’s one-year assessment date started before the bankruptcy petition, the one-year assessment date continues the same as if the bankruptcy petition had not been filed. The one-year assessment date could start before the bankruptcy petition due to the conversion of partnership items to nonpartnership items, by settlement or other conversion events. Issuing a statutory notice of deficiency on partnership items previously converted by an event other than the bankruptcy or previously made final by a defaulted FPAA or a final court decision will not suspend the period of limitations.

  4. Under IRC section 6871(b) the period for assessment under IRC section 6229(f) is not suspended by IRC section 6503(a)(1) if a statutory notice is issued for tax which may be assessed immediately. The deficiency from the previously converted or finalized partnership items can now be assessed immediately under IRC section 6871(b) and 11 U.S.C. 362(b)(9)(D) without having to ask the bankruptcy court to lift the stay of IRC section 362(a)(6) of the Bankruptcy Code. The deficiency must be assessed within one year of the settlement or the finalizing of the partnership items by default of the FPAA or entry of the final court decision, whichever is appropriate.

    Example:

    An investor and the government settle the partnership items with a Form 870-P(AD). Subsequently, the investor files for bankruptcy. The one-year assessment date is one year after the Form 870-P(AD) is executed. The bankruptcy filing does not change the one-year date. IRS must assess the deficiency from the settlement to protect the government. A statutory notice of deficiency cannot be issued on the settled partnership adjustments to protect the government. The only ways to protect the settled partnership’s adjustments are to assess the bankrupt investor or extend the one-year assessment date with a Form 872-F, Form 872 (Revision 10–2009), or Form 872-A .(Revision 10–2009)

8.19.6.15.3  (06-01-2007)
Appeals Has Key Case - Investor Files for Bankruptcy

  1. If an investor files for bankruptcy, the CTF will send a notice to the key case Appeals Office alerting them of that occurrence. The Appeals Office with the key case is not responsible for the investor case.

  2. If Appeals becomes aware of an investor bankruptcy for which no notice was received from the CTF, Appeals will notify the CTF of the occurrence.

  3. The appeals officer assigned the key case must determine if the bankrupt investor is the TMP. If the bankrupt investor is the TMP and the partnership does not select a new TMP, Appeals may have to designate a new TMP. If the case is docketed, consult with associate area counsel about asking the court to appoint a new TMP. Note on the Form 886-Z(C) that the investor was removed from the partnership proceeding by the bankruptcy.

  4. The CTF will notify Compliance that the investor filed for bankruptcy and will forward the investor case to the appropriate Compliance office to work the converted bankrupt investor case. Appeals should provide the key case adjustment information to the Compliance employee charged with the investor case.

    Caution:

    For Joint Committee, CIC corporation and other corporate specialty investor cases in Appeals jurisdiction, the appeals officer with the key case should notify the Appeals employee charged with the investor case. The Appeals employee with the investor case will work the converted bankrupt investor case.

8.19.6.15.4  (02-05-2008)
Investor Files for Bankruptcy - Appeals Has the Non-TEFRA Issues

  1. An investor may file for bankruptcy while the CTF has the TEFRA issues on the investor case and Appeals has the non-TEFRA issues on the investor case.

  2. Cooperate with the employee who has the TEFRA issues on the investor case to provide information for the adjustment to the investor case.

  3. The Compliance function may issue a statutory notice of deficiency on the investor including the pass-through entity adjustments.

    Caution:

    For Joint Committee, CIC corporation and other corporate specialty investor cases in Appeals jurisdiction, Appeals is responsible for working a converted bankrupt investor case.

  4. Additional statutory notices of deficiency may be issued even though the investor in Appeals jurisdiction already has been issued a statutory notice. See IRC section 6230(a)(2). Under IRC sections 6230(a)(2)(A) and (B) Compliance may issue a statutory notice of deficiency combining partnership items in multiple partnerships in one notice of deficiency (IRC sections 6230(a)(2)(A)(ii) and 6231(e)(1)(B)).

  5. If a statutory notice of deficiency is issued, this will terminate a Form 872-A. If you become aware that a partner in your inventory, whose statute is extended with a Form 872-A, filed for bankruptcy, and the compliance function will issue a statutory notice of deficiency, secure an extension of the statute with a Form 872 to protect the statute in your jurisdiction.

  6. See IRM 8.7.6 for additional requirements for a bankruptcy case.

8.19.6.15.5  (06-01-2007)
Determining if an Investor Is Named in a Bankruptcy Petition

  1. There is no one sure method to determine if an investor is named in a bankruptcy petition. Sometimes the taxpayer, representative or TMP may make remarks that raise questions about a partner filing for bankruptcy. These are suggestions to assist with the determination.

  2. Check for a bankruptcy indicator on a transcript or on AIMS.

    1. On a transcript, the bankruptcy indicator is a transaction code 520 with a closing code (cc) 83, 85, 86, 87, 88 or 89. Freeze codes "-V" or "-W" are bankruptcy freezes.

    2. On AIMS, the bankruptcy indicator is a freeze code "U" or "X" and is located on an AMDISA.

    3. See Document 6209 (ADP and IDRS Information) for additional bankruptcy indicators.

      Caution:

      The absence of a bankruptcy indicator is not a guarantee that the taxpayer has not filed for bankruptcy. If a taxpayer does not show the IRS as a creditor, then IRS will not receive notice of the bankruptcy filing.

      Note:

      Special Procedures Branch (SPB) inputs the bankruptcy indicator when they receive notice a taxpayer filed for bankruptcy. If you discover a taxpayer is bankrupt but there is no bankruptcy indicator, contact your local bankruptcy coordinator to assist you with having the indicator input.

  3. Call the Special Procedures Branch where the investor is most likely to file for bankruptcy. A taxpayer can file for bankruptcy almost anywhere.

  4. Research on Accurint. Accurint is a software program that provides bankruptcy information as well as other basic asset information on individuals and businesses.

  5. Research on PACER, if available in your office. PACER is software used by federal district and bankruptcy courts to identify bankruptcy cases whether or not IRS is a creditor. The information on PACER is controlled by the courts. There may be a charge to use PACER. Consult your local bankruptcy coordinator.

  6. Check with your Compliance bankruptcy coordinator.

  7. Ask the investor directly, and document the response. Attempt to obtain a written response from the investor.

  8. Search the administrative file for any indication of bankruptcy.

  9. Ask your local bankruptcy coordinator for other suggestions.

8.19.6.16  (02-05-2008)
Affected Items Cases in Appeals

  1. After the completion of a partnership proceeding, the CTF generally issues statutory notices of deficiency for affected items. These cases usually come to Appeals in docketed status.

  2. The CTF issues a different notice for each partnership in accordance with IRC section 6230(a)(2)(B). IRC section 6230(a)(2)(C) gives the authority to issue more than one statutory notice to an investor for a given year if the deficiency is attributable to affected items.

  3. For "pass-through" entity tax years ending before August 6, 1997, the statutory notice will cover penalties and other affected items. For partnership tax years ending after August 5, 1997, the statutory notice will cover affected items other than penalties because the applicability of the penalties is determined at the partnership level.

  4. The key case CTF maintains information on the key case for two years after the key case is completed. Contact the key case CTF or the Appeals Office responsible for the key case settlement for the key case affected item ACM.

8.19.6.16.1  (06-25-2010)
Statute of Limitations on Affected Items

  1. Sometimes an affected item case reaches Appeals in non-docketed status. The statute for the non-docketed affected item case is one year from the date one of the following events occurred:

    1. The partnership items were converted to non-partnership items for that investor.

    2. The FPAA defaulted.

    3. The decision of the court became final.

  2. The one-year date by which the period of limitations is suspended by a defaulted FPAA or a final court decision can be extended. See IRC section 6229(d). A Form 872 (Revision 10–2009) or a Form 872-A (Revision 10–2009) can be used in this instance to extend the IRC section 6229(a) statute.

  3. A one year date created by a conversation of partnership items to nonpartnership items as described in IRC section 6229(f) can be extended. Use Form 872-F, Form 872 (Revision 10–2009) or Form 872-A (Revision 10–2009).

8.19.6.16.2  (06-01-2007)
Affected Item Proceeding With No Partnership Proceeding

  1. A partnership proceeding is not necessarily required prior to an affected item proceeding. See Roberts v. Commissioner, 94 T. C. 853 (1990).

  2. In such an affected item proceeding, no partnership level item may be challenged. Only affected items and issues that require partner level determinations may be considered.

    Example:

    Appeals could receive an at risk issue case where the government challenges some aspect of at risk which requires looking to the partner’s records for a determination. The case cannot extend into the aspects of at risk that are determined at the partnership level such as whether a partnership note is non-recourse. See IRM 8.19.1.6.9.4, Issues With Both Partnership and Partner Level Elements, and IRM 8.19.3.11.1 for a discussion of partnership level aspects of some affected items and partner level aspects of those affected items.

  3. If there is no prior partnership proceeding, the statute of limitations for an affected item proceeding is determined under IRC section 6229(a) or IRC section 6501. The issuance of an affected item notice of deficiency suspends these periods under IRC section 6503.

8.19.6.16.3  (06-01-2007)
Affected Item Cases After a Partnership Proceeding

  1. In an affected item case after a partnership proceeding, neither the taxpayer nor the government may challenge a partnership level item. Only issues that require partner level determinations may be challenged.

  2. Consider the partnership level evaluation along with evidence and facts provided by the individual to arrive at a settlement position on the individual investor's case. If the investor does not present additional evidence and facts, follow the partnership level evaluation.

  3. If the investor's case is docketed, the decision documents should specify that the penalties or other affected items are attributable to a specific TEFRA partnership. See IRM 35.8.6.1.5.

  4. Appeals may not settle partnership items as part of an affected item proceeding. Doing so may reopen partnership items for all other partners under the consistent agreement rule of IRC section 6224(c)(2).

8.19.6.16.4  (02-05-2008)
Affected Item Cases With Overpayments

  1. A docketed affected item case may result in an overpayment. A statement of account is generally needed.

  2. For partnership tax years ending after August 5, 1997, IRC section 6230(c)(1)(C) and IRC section 6230(d) provide for the refund of penalties, additions to tax or additional amounts that related to an adjustment to a partnership item. Refunds for other affected items requiring deficiency procedures are provided under IRC section 6512(b). IRC sections 6230(c)(1) and 6230(d) provide for refunds of affected items which do not require deficiency procedures (computational affected items).

  3. For pass-through entity tax years ending before August 6, 1997, IRC section 6512(b) provides for refund of penalties and other affected items that require deficiency procedures. Alternatively, the partner may allow the notice of deficiency to default, pay the tax and sue for refund in a district court or the U.S. Court of Federal Claims.

8.19.6.17  (06-01-2007)
TEFRA Investor Coordinated Industry Case (CIC) Corporations, Joint Committee or Other Corporate Specialty Investor Cases

  1. Generally, the CTF makes the computational adjustments and assessments for partners in a TEFRA partnership, even when the partner’s case is in Compliance or Appeals jurisdiction for a non-TEFRA matter.

  2. The responsibility for making the computational adjustments and assessments for partners in a TEFRA partnership is transferred to Compliance or Appeals for these investor cases:

    • Coordinated Industry Cases (CIC) corporations

    • Joint Committee cases

    • Other corporate specialty cases

  3. For Appeals, other corporate specialty cases include:

    1. Form 1120 followed by a letter (for example, Form L, Life insurance company). However, Form 1120A, Form 1120S and Form 1120X are NOT corporate specialty cases.

    2. All corporations with AIMS activity codes of 219 or higher.

  4. When the partnership items are finalized by default of the FPAA, entry of the court decision, or are converted to non-partnership items, the responsibility for computational adjustments and assessments for these investors rests with Compliance or Appeals, depending on which function has jurisdiction of the investor case. Appeals is responsible for the computations and assessment if the investor is in Appeals when the one-year assessment statute date posts on PCS.

  5. Be aware that PCS software may sometimes have an incorrect PICF code. Appeals officers are encouraged to review all PICF codes other than 0, 1 and 2 to determine if there are open TEFRA linkages.

  6. A PICF code of 6 indicates the investor has at least one open non-TEFRA key case linkage but no open TEFRA linkages. When an investor case is received in Appeals, the results of the examination of all non-TEFRA partnerships should be included in the RAR. If the investor case is received in Appeals before the non-TEFRA partnership examination is finished, the investor case is prematurely in Appeals, unless the case is in Appeals under early referral procedures, Rev. Proc. 99-28, 19999-29 IRB 109, or the partnership is really a TEFRA partnership.

8.19.6.17.1  (10-01-2012)
Statute For Investor’s Case

  1. The non-TEFRA issue case statute of limitations is determined under IRC section 6501. This statute is shown on ACDS as the investor case statute.

  2. A separate statute applies to the investor for each TEFRA entity in which the taxpayer invested. Appeals now tracks the separate TEFRA statute for the CIC corporate investor, the Joint Committee investor and investors which are other corporate specialty cases.

  3. When a case is received in Appeals, Account and Processing Support will research all CIC corporation, Joint Committee and other corporate specialty cases for related TEFRA linkages.

  4. If the AMDIS or AMDISA has a PICF code of 5, this indicates that the investor has at least one open TEFRA key case linkage. If the PICF code is 5, take the following actions:

    1. Request a TSUMYI for each year in Appeals jurisdiction assigned to the appeals officer with a PICF code of 5 to determine the TEFRA key case linkages and the status of the linkages.

    2. Retain the AMDIS/AMDISA and TSUMYI in the administrative file for the appeals officer.

    3. See IRM 8.19.5, Figure 5-5 for an example of an AMDIS showing a PICF code of 5 and IRM 8.19.5, Figure 5-3 for an example of a TSUMYI.

8.19.6.17.1.1  (10-01-2012)
Carding In Investor Cases with Open TEFRA Linkage

  1. If there is an open TEFRA linkage to the CIC corporate, Joint Committee or other corporate specialty investor, Account and Processing Support will card in the linkage on ACDS for the purposes of tracking the statute of limitations and assessment. A sample case summary card is shown in Exhibit 8.19.6-5..

    Note:

    Be sure the TYPE code on ACDS for the investor case is "TEFRAI."

  2. If the one-year assessment statute date on the TSUMYI is either an eight-digit date or blank, there is an open TEFRA linkage. If the one-year assessment statute date on the TSUMYI is "11111111," this particular linkage is not an open TEFRA linkage. The entry "11111111" under the one-year assessment statute date indicates that a TEFRA linkage was closed, and the computational adjustment was made and assessed for this partnership. Do not card in the key linkages with a one-year date of "11111111."

  3. If there’s an open TEFRA linkage, Account and Processing Support will card each partnership case into ACDS as a related non-key case as follows:

    1. WUNO: WUNO of the investor case

    2. TP: Name of the partnership. If necessary, research IDRS for the full name of the partnership (INOLE, NAMEE or NAMES).

    3. TIN: Partnership TIN from TSUMYI, key linkage field

    4. MFT: MFT of partnership from TSUMYI, MFT field

    5. TYPE: REF

    6. FEATRCD: N/A

    7. AO: Same as the investor case

    8. ASNDATE: Actual date assigned

    9. REQAPPL: N/A

    10. RECDATE: Date case received

    11. CREATED: Computer generated

    12. SOURCE: Applicable source code of investor case

    13. Location: Same as the investor case

    14. KEYTP: Name of the investor case

    15. KEYTIN: TIN of the Investor case

    16. KEYPER: Enter the earliest tax period of the investor case.

    17. NOTE: "TEFRA LINKAGE"

  4. Input the following on the Case Return Information screen

    1. A (AIMS): "E" since these cases will not be controlled on AIMS.

    2. TAXPER: Enter all tax periods for which there’s an open TEFRA linkage for this partnership. Add a tax period modifier to each tax period. Usually, the modifier will be "N" (no return).

    3. STATDATE: If the one-year statute date is blank on the TSUMYI, leave STATDATE blank and input TFINV in CODE (statute code). If the one-year statute date on the TSUMYI is an eight-digit date other than "11111111" , input the one-year statute date from the TSUMYI as STATDATE and leave CODE (statute code) blank.

    4. CODE (statute code): If the one-year statute date is blank on the TSUMYI, input TFINV. If the one-year statute date is an eight-digit date other than "11111111" , leave CODE blank.

    5. PropdTax/PropdPen: Leave blank.

    6. RevsdTax/RevsdPen: Leave blank.

    7. DUPLICAT: Do not enter any duplication.

  5. Card in each partnership case that shows an open TEFRA linkage to the investor in Appeals assigned to the appeals officer. For example, if a CIC corporate investor has a PICF of 5 and the TSUMYI shows four open TEFRA linkages to this investor, input four different related non-key case summary cards following the instructions in paragraphs (3) and (4) above. See Exhibit 8.19.6-5 for a sample related non-key case summary card.

  6. Each case summary card may have more than one year if the CIC corporate, Joint Committee or other corporate specialty investor has an open TEFRA linkage to that partnership in more than one of the years for which Appeals has jurisdiction of the investor. However, only one partnership may be shown on each case summary card.

  7. Appeals team case leaders and appeals officers will do the following:

    1. Verify the AMDIS/AMDISA and if necessary TSUMYI against the case summary cards when a case is received.

    2. Submit corrections to the case summary cards to Account and Processing Support. If the TSUMYI shows a one-year date of "11111111," verify that the assessment was made.

    3. Every six months (March and September), research all cases assigned that have TEFRA linkages controlled on ACDS and CODE (statute code) = TFINV to determine if a one-year statute date appears on the TSUMYI. The appeals case leader or appeals officer should request Account and Processing Support to generate an Ad Hoc report based on CODE (statute code) = TFINV to assist in this determination.

      Note:

      The research can be done more often than every six months at the discretion of the appeals team case leader or appeals officer, and is highly recommended when there are several open linkages.

    4. If a one-year statute date appears on the TSUMYI, and the one-year statute date is not on ACDS, submit an ACDS related non-key case summary card update to Account and Processing Support. Also, secure a copy of the closing package from the CTF to ensure timely assessment of partnership adjustments.

8.19.6.17.1.2  (10-01-2012)
Assessment of TEFRA Partnership Issues

  1. Appeals may receive a TEFRA investor closing package from the CTF consisting of documents showing the resolution of the TEFRA partnership issues (decision document, defaulted FPAA or settlement agreement form), a Form 4605-A, and a Form 886-Z(C) showing the corrected amount on all issues for the investor under Appeals jurisdiction.

  2. If Appeals receives a TEFRA investor closing package from the CTF and the ACDS case record has a CODE = TFINV, Account and Processing Support will request a TSUMYI and update ACDS to reflect the one-year statute date and remove the TFINV code. Appeals Processing Services will give the TEFRA investor closing package and the updated case summary card, if appropriate, to the appeals officer or appeals team case leader.

  3. When the appeals officer or appeals team case leader receives a TEFRA investor closing package from the CTF, the appeals team case leader or appeals officer will request a computation of tax to reflect the adjustments from the completed TEFRA proceeding. This will be a partial computation as the non-TEFRA issues are still under Appeals consideration.

    Note:

    IRC section 6601(c) was amended for partnership years beginning after August 5, 1997, to provide that interest will be suspended 30 days after settlement during the period of computational adjustments. Weigh the risks of the complexities and cost of computing tax resulting from a partnership adjustment against the permanent loss of interest on the assessment from 30 days after settlement until the assessment is made. See IRM 8.19.6.9(3).

  4. The assessment must be made within the one-year assessment period. One-year assessment periods under IRC section 6229(f)(1), including settlements, can be extended on a Form 872-F, Form 872 (Revision 10–2009) or Form 872-A (Revision 10–2009) . One-year assessment periods under IRC section 6229(d) (defaulted FPAAs and court decisions) can be extended using Form 872 (Revision 10–2009) or Form 872-A (Revision 10–2009). One-year dates extended by Form 872-F, Form 872 (Revision 10–2009) or Form 872-A (Revision 10–2009) should be updated on both ACDS and on PCS. Formerly Form 872-I and Form 872-IA were used to extend the TEFRA statute but these forms are obsolete as of October 2009. See Exhibit 8.19.5-16 for a Form 8339 updating the one-year date and Exhibit 8.19.5-17 for a Form 8339 closing the linkage.

    Caution:

    You must determine if the event starting the one-year assessment permits extension before securing a Form 872-F.

  5. The appeals officer or appeals team case leader will prepare and submit Form 8339 to the Area PCS Coordinator to update the PCS system to reflect the extension or a one-year date or follow other local procedures for updating PCS.

    Note:

    PCS is not programmed to accept open-ended statute dates or dates more than 15 months in the future. Accordingly, the statute date on PCS will not necessarily correspond to the statute date on ACDS. The appeals officer will have to ensure the one-year statute date is updated on PCS as the actual one-year statute approaches.

    Example:

    If a Form 872-F is secured on 1/15/2006 extending the one-year statute date to 12/31/2007, use 3/31/2007 as the one-year statute date on PCS for this TEFRA linkage. If Form 872-A (Revision 10–2009) is secured on 1/15/2006, also use 3/31/2007 as the one-year statute date on PCS for this TEFRA linkage.

    Note:

    Copies of TEFRA investor consents (where a one-year statute is being extended) should be faxed to both CTFs by the appeals officer. See IRM Exhibit 8.19.2-2.

  6. Account and Processing Support should update ACDS to reflect an extension of a one-year date by Form 872-F, Form 872 (Revision 10–2009), or Form 872-A (Revision 10–2009) as follows:

    • If the consent is a Form 872-F or Form 872 (Revision 10–2009), enter the statute date on the form in STATDATE; for the Form 872-F, also enter "F" in CODE (Statute Code);

    • If the consent is a Form 872-A (Revision 10–2009), enter "A" in CODE (Statute Code)

  7. The appeals officer will forward the computation of tax, a Form 5402 requesting a partial assessment, a copy of the decision document, defaulted FPAA, or settlement agreement with a copy of the Form 886-Z (C) to Account and Processing Support for processing the partial.

  8. Refer to IRM 8.20.6 (Appeals Case Processing Manual, Interim Actions) for procedures to process a partial. In addition Account and Processing Support will update ACDS to reflect the assessment of the partial as follows:

    • ACTION: INTERIM (other local procedures may apply).

    • TODATE: Enter date case sent to Account and Processing Support/WRAPS.

  9. After Account and Processing Support receives verification from the appeals officer or appeals team case leader that the assessment was made, Appeals Processing Services will update ACDS by removing the STATDATE and entering the CODE "ASESD" for each TEFRA linkage tax period assessed. Use ACDS closing code 45 to close the related non-key case summary card.

  10. After verification that the assessment was made, Account and Processing Support will also update PCS using the Form 8339 prepared by the appeals officer or appeals team case leader to reflect the assessment and the amount, show the new one-year date of "11111111," and close the linkage. See IRM Exhibit 8.19.5-17 for an example Form 8339 to close a linkage. Local procedures may vary for updating the PCS system.

  11. If penalties or other affected items are applicable and the investor does not agree, issue a statutory notice of deficiency to the investor. Account and Processing Support will update the related non-key case summary card on ACDS to reflect the issuance of the statutory notice of deficiency per IRM 8.20.6. The case will remain a reference return at this time.

8.19.6.17.2  (10-01-2012)
Conforming the Investor Return with the TEFRA Partnership or S Corporation Return

  1. On no-change TEFRA key cases the appeals officer will verify that the amounts reported by the CIC corporate, Joint Committee, or other corporate specialty investor agree with the amounts shown on that taxpayer’s Schedule K-1. If the amounts do not agree, and the investor did not file a Form 8082 with its return (see below), a computational adjustment will be necessary to conform the investor's return to the items shown on the Schedule K-1.

  2. The appeals officer will complete the verification as soon as possible after receipt of the no-change closing package from the applicable TEFRA Campus. If the no-change closing package does not contain a copy of the taxpayer's Schedule K-1 from the TEFRA key case, a copy should be requested from either the TEFRA Campus or from the taxpayer. If the taxpayer's return or other information in the administrative file does not contain sufficient information in order to determine what amounts were reported by the taxpayer from the TEFRA key case, the appeals officer should request this information from the taxpayer.

    Note:

    If the taxpayer's return is in the possession of the tax computation specialist at the time that the appeals officer receives the no-change closing package from the applicable TEFRA Campus, the tax computation specialist will provide the appeals officer with copies of any schedules from the return or information from the file that are needed for the appeals officer to verify what was reported.

  3. If the investor did not file a Form 8082, Notice of Inconsistent Treatment, the adjustment to conform the investor's return to the Schedule K-1 does not require a settlement agreement. It should be made as a computational adjustment. The appeals officer will request that the tax computation specialist compute the related deficiency. The appeals officer will request Account and Processing Support to assess the deficiency to conform the investor return with the key case return prior to the expiration of the statute by so requesting in the remarks section of Form 5402 and submitting the Form 5402 and a copy of the computations to Account and Processing Support with the appropriate statute noted on the Form 5402. See Figure 6-1 to determine the statute of limitations for conforming the investor's return to the Schedule K-1. Account and Processing Support will make the interim assessment per IRM 8.20.6 and return the case to the appeals officer.

    Note:

    If the tax computation specialist discovers a situation where a CIC corporate, Joint Committee, or other corporate specialty investor did not report amounts shown on the taxpayer's Schedule K-1 and the key case examination resulted in a no-change, this should be brought to the attention of the appeals officer as soon as possible.

  4. The statute to assess the deficiency from the computational adjustment may be extended by securing either Form 872 (Revision 10–2009) or Form 872-A (Revision 10–2009) from the investor before the expiration of the applicable statute reflected in Figure 6-1.

  5. If the investor did file a Form 8082, Notice of Inconsistent Treatment, the investor's return cannot be corrected to agree with the Schedule K-1 unless the partnership or S corporation return is examined or the investor's partnership/S corporation items are converted to non-partnership/non-S corporation items by the Commissioner under IRC section 6231(b)(1)(A). If the Service did not convert the partnership/S corporation items under IRC section 6231(b)(1)(A), the adjustment to conform the investor's return to the Schedule K-1 requires a settlement agreement or an FPAA/FSAA. If the Service did convert the partnership/S corporation items under IRC section 6231(b)(1)(A), non-TEFRA deficiency procedures must be followed.

    Figure 8.19.6-1

    Last Date by Which Investor Return Can Be Conformed to the Partnership Return

    If status of partnership exam is… Then assessment must be made
    No adjustments letter issued Before the partnership statute date expires or in 3 years after investor return is filed, whichever is longer
    No change FPAA issued or no change settlement agreement Before the one-year statute date expires
    Partnership return examined and changes proposed Before the one-year statute expires (Include as part of computational adjustment when partnership issues are resolved).

8.19.6.17.3  (10-01-2012)
Closing the CIC Corporation, Joint Committee or Other Corporate Specialty Investor Case

  1. If the investor defaults on a statutory notice of deficiency for penalties or other affected items, Account and Processing Support will prepare the case for final closing.

    1. Use ACDS closing code 45 to close the related non-key case summary card.

    2. After verification that the assessment was made, Account and Processing Support should update PCS using the Form 8339 from the appeals officer to reflect the new one-year date of "11111111" , and close the linkage. See IRM Exhibit 8.19.5-17 for a sample Form 8339.

  2. If the investor petitions the Tax Court in response to a statutory notice of deficiency for penalties or other affected items, Account and Processing Support will take the following action:

    1. Create a new work unit for the docketed case. Use the date Appeals receives the petition for the date received.

    2. Close the related non-key case summary card on ACDS using closing code "45."

    3. Follow the general procedures for new case receipts.

  3. If the TEFRA issues are completed prior to the non-TEFRA issues, use interim procedures to process the TEFRA issues. See IRM 8.19.6.17.1.2.. The appeals officer will prepare a Form 8339 for PCS closing. See Exhibit 8.19.5-17 for a sample Form 8339 closing the linkage. The appeals officer will note on form 5402 in remarks that Account and Processing Support is to update PCS according to the Form(s) 8339 attached. See IRM 8.19.6.9. for instructions on interest suspension under IRC section 6601(c).

  4. When the non-TEFRA issues are subsequently completed (after the completion of the TEFRA issues discussed in paragraph (3) above) and there are no remaining open TEFRA linkages, prepare the case for final closing as follows:

    1. The appeals officer will prepare Form 5402 explaining to Account and Processing Support this is a final closing.

    2. Account and Processing Support will process Form 5403 following normal closing procedures in IRM 8.20.7.

    3. On Form 5403 mark the TSCLS box.

    4. Update ACDS with ACTION=ACKCLS, TODATE, Closing Code, Date Closed, Revised Tax & Penalty as appropriate.

    5. Close the related non-key case summary card for the investor case, using closing code "45" .

    Note:

    Form 8339 is not needed.

  5. When the TEFRA issues are completed prior to the non-TEFRA issues, and the computation of the partnership item adjustments causes no change in the investor’s tax (perhaps due to an unused net operating loss or credits) the procedures are different.

    1. If the investor does not wish to wait for the resolution of the nonpartnership issues, the appeals officer or appeals team case leader should send a copy of the notice of computational adjustment to the investor. This starts the running of the statute under IRC section 6230(c).

    2. The appeals officer should also submit a package to Account and Processing Support that includes a Form 5402 requesting an update of ACDS due to the no change, a copy of the audit statement and a Form 8339 to update the one-year assessment date on PCS to "11111111" and the dollars to NC. Note on Form 5402 in remarks that Account and Processing Support should update PCS according to Form(s) 8339 attached.

    3. Account and Processing Support should update PCS to show a new one-year assessment date of "11111111." Do not update AIMS because AIMS will not accept an interim assessment of transaction code 300 amount zero. Account and Processing Support will also update the related non-key case summary card to show a CODE of "ASESD" and remove the statute date.

  6. If the non-TEFRA issues are completed prior to the TEFRA issues, and there are open TEFRA linkages remaining, prepare the case for partial closing as follows:

    1. Prepare Form 5403 following partial procedures. In item A, Special Handling Instructions, write "TEFRA Linkage [Insert CIC 1120, Joint Committee, or Other Corporate Specialty Case] - After Partial Closing, Forward to Examination Technical Services." For this purpose, an other corporate speciality investor case only includes Form 1120 followed by a letter (other than A, S, or X)--it does not include corporations with AIMS activity codes of 219 or higher.

    2. Once the partial assessment has been input, Account and Processing Support will update the AIMS database to status 21. AIMS will reset to the closing PBC.

    3. Account and Processing Support will forward the administrative file via Form 3210 to the appropriate Examination Technical Services unit based on the location of the originating Examination group. Ensure a copy of the input Form 5403 is attached to the face of the return. Examination Technical Services will forward the case to the appropriate group, who will place the file in suspense awaiting the outcome of the TEFRA examination.

  7. If the non-TEFRA issues and the TEFRA issues are completed at the same time, prepare the case for final closing. The appeals officer will note on the Form 5402 in remarks that this is a final closing. The appeals officer will attach Form(s) 8339 to close the appropriate TEFRA linkages on PCS. Also the appeals officer will note in the remarks section of Form 5402 that Account and Processing Support is to update PCS according to Form(s) 8339 attached. See IRM 8.19.6.9(3) for instructions for interest suspension under IRC section 6601(c).

    1. Account and Processing Support will prepare the key case and the Form 5403 following general closing procedures in IRM 8.20.7.

    2. Close the related non-key case summary card with the corporate case using ACDS closing code "45."

  8. There should be two audit statements in the file, one for the non-TEFRA adjustments and the other for the TEFRA adjustments. If there is one combined statement, there should be a statement identifying the deficiency attributable to the TEFRA issues for each partnership for each tax year.

    1. Update ACDS to reflect the revised tax and penalties attributable to the non-TEFRA adjustments.

    2. Update PCS with a Form 8339 to reflect the revised tax attributable to the TEFRA adjustments and to close the linkage with a statute date of "11111111."

  9. If the non-TEFRA issues case is transferred to associate area counsel jurisdiction before all TEFRA partnership issues are resolved, Account and Processing Support will return the case to the appeals officer to take additional action. The appeals officer will take the following steps to ensure Counsel is aware of the transfer of statute responsibility for the TEFRA adjustments:

    1. On Form 5402 in remarks, request Account and Processing Support to assess all TEFRA partnership issues that are resolved but not assessed before transfer to associate area counsel. Include the computation for the assessment and prepare a Form 8339 for PCS closing of the resolved TEFRA linkages. See Exhibit 8.19.5-17 for a sample Form 8339 closing the linkage.

    2. Prepare and present to associate area counsel a written memorandum that lists the name of each TEFRA partnership with an open TEFRA linkage to the investor being transferred, the partnership TIN and years under examination. Explain that the responsibility for monitoring the TEFRA statutes is being transferred from Appeals to Counsel.

    3. Return the case to Account and Processing Support to transfer to Associate Area Counsel.

8.19.6.18  (06-01-2007)
TEFRA Investor Cases--Other Than Coordinated Industry Case (CIC) Corporations, Joint Committee or Other Corporate Specialty Investor Cases

  1. As noted in IRM 8.19.6.17.1, Appeals is not responsible for making the computational adjustments and assessments for partners in a TEFRA partnership for these types of cases.

  2. The procedures in IRM 8.19.6.17.1.1 for carding in any open TEFRA linkage on these cases do not apply. However, the TYPE code on ACDS should be "TEFRAI." This will allow instructions for sending these cases to TEFRA suspense (if applicable) to be generated using the customized Form 5402.

8.19.6.19  (10-01-2012)
Best Practices for Appeals Team Case Leaders and Appeals Officers

  1. Return an investor case to Compliance for assessment of any open TEFRA linkages that have one-year assessment dates on the TSUMYI when the case is received in Appeals with less than 180 days remaining on the one-year statute.

  2. Assess the tax from TEFRA partnership adjustments as soon as possible after settlement or other event triggers the one-year assessment date. This protects the interest assessment.

  3. If the taxpayer requests an extension of the one-year assessment date to avoid the expense of time consuming computations while the case is in Appeals for non-TEFRA consideration, advise the taxpayer as follows:

    1. For pass-through entity tax years beginning prior to August 6, 1997, interest is not suspended. Recommend an advance payment of tax.

    2. For partnership tax years beginning after August 5, 1997, when a settlement agreement has been executed, interest is suspended after 30 days while the computation of tax and the assessment are delayed. Encourage an advance payment of tax to avoid the loss of interest if the one-year assessment date is extended.

  4. Remember that the assessment of tax resulting from a defaulted FPAA or final court decision of the partnership cannot be extended using a Form 872-F.

  5. Keep all assessments and closings as partial on AIMS and IDRS until all TEFRA and non-TEFRA issues are resolved for this taxpayer.

  6. When Appeals resolves its issues (for CIC, Corporate, Joint Committee, and other corporate specialty cases) but there are open TEFRA linkages, do the following:

    1. Update ACDS and CIRS as if the case were a full closure whether or not there are open TEFRA linkages with no one-year date.

    2. Return the case to Examination Technical Services, status 21, if there are open TEFRA linkages. Examination will suspend the case pending the outcome of the TEFRA pass-through entity proceedings.

  7. When a case is transferred to Counsel jurisdiction and there are open TEFRA linkages with no one-year assessment date, notify associate area counsel by written memorandum that Counsel now has responsibility for the open TEFRA linkages.

  8. Before forwarding a case outside Appeals or issuing a statutory notice of deficiency, ensure that the tax from all open TEFRA linkages with one-year assessment dates are assessed and PCS updated.

  9. Review entries on ACDS to ensure accuracy of statute controls for both the non-TEFRA aspects of the case and the TEFRA aspects of the case.

  10. Ensure assessments of TEFRA adjustments that show "11111111" on the TSUMYI have been made. If not in the administrative file, secure closing packages or interim computations to reflect assessments showing on the transcript. This will be needed when Appeals makes its tax computation.

  11. Protect the affected items as well as the partnership level items. Ensure that the computational affected items are assessed with the partnership level items. For partner level affected items that are not computational, either assess if previously agreed, secure an agreement or issue a statutory notice of deficiency.

  12. Request assistance from your area TEFRA coordinator before contacting the Appeals Technical Specialist(s) for TEFRA.

Exhibit 8.19.6-1 
Sample Joint Committee Report
TEFRA Issues Unresolved--Expedited Refund Request

This image is too large to be displayed in the current screen. Please click the link to view the image.

Exhibit 8.19.6-2 
Sample Joint Committee Report
TEFRA Issues Unresolved

This image is too large to be displayed in the current screen. Please click the link to view the image.
This image is too large to be displayed in the current screen. Please click the link to view the image.

Exhibit 8.19.6-3 
Sample Joint Committee Report
TEFRA Issues Resolved--Expedited Refund Request

This image is too large to be displayed in the current screen. Please click the link to view the image.

Exhibit 8.19.6-4 
Sample Joint Committee Report
TEFRA Issues Resolved

This image is too large to be displayed in the current screen. Please click the link to view the image.
This image is too large to be displayed in the current screen. Please click the link to view the image.

Exhibit 8.19.6-5 
Case Summary Card for a Related Non-Key TEFRA Partnership Case

This image is too large to be displayed in the current screen. Please click the link to view the image.

More Internal Revenue Manual