Accessibility Skip to Top Navigation Skip to Main Content Home  |  Change Text Size  |  Contact IRS  |  About IRS  |  Site Map  |  Español  |  Help  

4.31.6  NonTEFRA Examinations-CTF Procedures

4.31.6.1  (05-31-2004)
NonTEFRA Linkage and Suspense

  1. The following subsection covers non-TEFRA linkage and suspense.

4.31.6.1.1  (05-31-2005)
Linkage Criteria

  1. A linkage package should be submitted to the campus within 60 days of the key case being under examination. The campus needs sufficient time between linking and closing in order to secure the investor returns. Failure to timely link cases creates processing problems in the campus.

  2. The written approval of the Area Director (SB/SE) or Director of Field Operations (LMSB) is required to start the examination (input of Form 8341) or to issue Form 6658 for a key case entity with less than 12 months remaining on the statutory period of limitations for assessment of the tax for any investor. ( IRM 4.31.5.9 covers the field procedures)

    1. The approval of the Area Director (SB/SE) or Director of Field Operations (LMSB) should be granted only when extenuating circumstances require the commencement of an examination with less than 12 months, but more than 7 months, remaining on the statutory period of limitations of any investor.

    2. A copy of this approval must be transmitted with Form 8341 to the PCS Coordinator for input.

    3. A copy of the approval will be transmitted with the Form 5546, Examination Charge-Out, or Form 6658, Notice of Special Investor Action, as applicable.

    4. The circumstances surrounding the late start of the examination will be set forth in the memorandum of approval.

    5. The memorandum of approval must identify the key case entity and contain the original signature (a facsimile stamp is not acceptable) of the Area Director/Director of Field Operations.

    6. A copy of this approval will be sent to the key case CTF with the linkage package.

    7. Additional approval is not required to start the examination of a second-tier entity where the examination is limited to making adjustments stemming from the examination of the first-tier entity. However, approval is required for the second-tier entity where another issue (an issue generated from its own return) is examined.

  3. In those instances where there are less than 210 days remaining on the statutory period of limitations for assessment of the tax for any investor, the key case area is responsible for securing extensions of the statutory period of limitations on all related investor returns, including tier returns and their related investors. This must be done before the linkage package is sent to the CTF for input.

    1. The key case area is responsible for securing the necessary information from the investor area regarding any other key cases or tier entities in which the investor may have an interest.

    2. This information is required to ensure adherence to the Service policy to only secure an extension of the statutory period of limitations for those key case returns that are currently under examination (see IRM 25.6.22.8).

      Note:

      Form 872-I, not Form 872 or Form 872-A, should be used to secure investor statute extensions, if the investors will ultimately be controlled by the campus after linkage.

4.31.6.1.2  (02-22-2008)
Linking NonTEFRA Investors

  1. After meeting nonTEFRA key case linking criteria, the key case examiner will forward the Form 8341, PCS TEFRA Establish or Add, to the CTF through the field office PCS Coordinator when a nonTEFRA key case examination is initiated. A complete Form 8341 package includes:

    1. A completed Form 13824, NonTEFRA Linkage Package Check Sheet verifying all required items are included in the linkage package.

    2. Form 8341 completed through box 12. (For instructions see IRM 4.29.2 and IRM Exhibit 4.29.2-3.)

    3. A complete copy of the nonTEFRA key case return, including all attachments, all Schedules K-1 and all Schedule K-1 attachments.

    4. One additional copy of all Schedules K-1 with all attachments with the MFT of the investor properly annotated on each Schedule K-1 in either the top margin or the investor name and address area. If the year-end of the investor is other than 12/31, the year-end must also be annotated.

    5. An adding machine tape or spreadsheet reflecting the reconciliation of the income or loss on the Schedules K-1 to the total income or loss of the key case return.

    6. A current AMDISA print to verify that the key case is on AIMS and matches the AIMS key case information.

  2. The Form 8341 packages will be transmitted via a Form 3210 to the CTF (Ogden for LMSB and Brookhaven for SB/SE).

  3. The CTF will input an "H" freeze code on the key case AIMS record using command code AMFRZ.

  4. The CTF will establish a key case administrative file after reviewing the package for completeness, statute consideration, and compliance with procedures.

  5. The CTF will perform basic research of the Schedules K-1 before establishing linkage, including where applicable:

    1. Spouses SSN

    2. Parent/Subsidiary

    3. EP/EO investors

    4. Grantor Trusts

    5. NMF investors

  6. The CTF will input command code (CC) TSLOD, using Form 8341, PCS Establish or Add. Command code TSLOD accesses the Master Files to verify the investor TIN, name control, and MFT. It rejects any input that does not match. A successful linking of the key case on the partnership control system will generate AIMS control and two Forms 5546 (Examination Return Charge Out) for each investor. These are referred to as a "Notification Charge-Out" and a "Flow Through Notification Charge-Out " . If there is no AIMS record anywhere prior to the link, the investor will go to the key case CTF to be suspensed. If the investor has an AIMS record prior to the linkup, the link will go to the existing AIMS record. Linking the record creates a PICF code of 6 on the investor account record.

  7. The CTF will process the linkage package within 30 days after receipt. After 30 days, the local PCS Coordinator will verify the investor linkages by pulling up a TSUMYP. A copy of the TSUMYP will be forwarded to the examining agent to verify that all investors were properly linked, and then placed in the key case file.

4.31.6.1.2.1  (05-31-2004)
CTF Employee Group Codes

  1. All nonTEFRA investor returns in the CTF are maintained in AIMS status 33; however, status codes 22 and 24 should be used for returns in process that have penalty or other affected item issues.

  2. The CTF will use the following AIMS organization codes to control their inventories. No other organization codes may be used.

    Employee Group Code Description Aging Criteria
    5400-5499 nonTEFRA Returns None
    5400 Newly Established Investor Returns 60 days
    5401-5409 Incomplete Files 90 days
    5410 Classification (local option) 60 days
    5416 Dual Status (TEFRA linkage also) None
    5417 Transfers-In (incoming to the CTF) 60 days
    5418 Regular Suspense Files None
    5419 Carryback or Carryover (local option) None
    5420-5439 Report Writing 60 days
    5440-5449 30-Day Letter 45 days
    5450-5459 90-Day Letter 120 days
    5460-5469 Tiers None
    5470-5479 District Court and Court of Federal Claims controlled investors, after assessment None
    5490 Key Case Suspense None
    5480-5499 Reserved for future use None

  3. Where EGC ranges are provided (except 5480-5489 and 5491-5499), codes within the range may be assigned at local option. Organization Codes 5000-5399 are reserved for Correspondence Examination; 5800-5899 are for TEFRA (See IRM 4.31.3.); 5500-5699 and 5900-5999 are available for local option.

4.31.6.1.3  (05-31-2005)
Form 5546, Examination Return Charge-Out

  1. The key case CTF will receive a Form 5546 labeled "Flow Through Notification" for each investor that is successfully linked on PCS and established on AIMS. If the investor's return was not previously established on AIMS, the investor's Form 5546 will generate with employee group code 5400 and will cause the income tax return to be pulled from files and sent to the key case CTF.

    1. A copy of the investor's Schedule K-1 should be attached to the carbon copy (copy 2) of the Form 5546 .

    2. Copy 2 of the Form 5546 with the Schedule K-1 attached will be forwarded to be associated with the investor's file. Generally the investor file will be controlled in the same CTF as the key case. A contact point in each CTF will be established to send the Form 5546 with Schedule K-1 attached when the investor file is located in the other CTF.

    3. The original of the Form 5546 is filed in the key case administrative file.

  2. An investor Form 5546 labeled "Related Investor Notification" is generated to notify the function (field office or CTF) in possession of the investor return that a nonTEFRA flow-through linkage is present.

    1. This Form 5546 identifies the flow-through return as nonTEFRA and identifies the AIMS PICF code as 6.

    2. The Form 5546 will show the assigned primary business code, employee group code and status code.

4.31.6.1.4  (05-31-2005)
Using AIMS Reports to Perfect Rejects

  1. When accounts loaded through command code TSLOD do not match at Master File, they are listed on the AIMS transaction code 424 reject register as status 99 rejects.

    1. These accounts do not establish on AIMS and do not produce a Form 5546.

    2. This condition may be caused by an incorrect TIN, name control, or MFT (a name control error will reject at terminal input if the LAP/NAP was up). This condition may also be caused by the lack of a TC 150 (filing of a tax return) posting on the tax module or when the requested module has moved to retention.

    3. The TC 424 Reject Register is distributed weekly to each CTF.

    4. Status Code 99 rejects must be worked promptly by each CTF.

    5. See IRM 4.4 AIMS/Processing Handbook for instructions on resolution of TC 424 rejects.

  2. The AIMS Duplicate Records Report is generated through the AIMS program if an attempt is made to link a taxpayer account through PCS while the account is in status 90.

    1. These accounts are identified by the " CLP" message.

    2. A TC 421 must be input to the Master File, allowed to cycle in, and then the account must be reestablished on AIMS using CC AM424.

  3. The key case CTF will perform the basic research to verify that no return has been filed by using CC IMFOL and CC BMFOL. If no TC 150 posted on the Master File, the investor return is established on non-Master File (NMF) AIMS and linked to the key case.

    1. The User Special Message can be used to identify specific problems or unique situations. An example would be to enter the literal "Parent" and its TIN where a subsidiary is the investor in a flow-through entity. Another example would be to enter "TE/GE " for a tax-exempt entity that is an investor.

    2. The AIMS non-Master File database is retained in the key case CTF, and research performed utilizing Nation Access Information (NAI), CFOL command codes, NAMEE and NAMES. SSNAD and EINAD can be accessed through NAI.

    3. The key case CTF will send a non-filer letter to obtain information regarding the loss, income or deduction taken on the corporation, partnership, trust or individual return.

4.31.6.1.5  (05-31-2004)
Non-Filer Procedures

  1. If the key case CTF cannot secure the return from the investor, the CTF will request an Information Returns Processing (IRP) transcript from the Information Returns Master File (IRMF). Use command code IRPTR to order the transcript. When the transcript is received, the CTF will associate it with the case file.

  2. The transcript and Schedule K-1 will be screened to determine if a Substitute for Return (SFR) needs to be established. If it is determined that an SFR is needed, one will be prepared and sent for processing. A linkage will be established to the key case after the TC 150 posts to Master File.

  3. The NMF record will be closed after the Master File linkage is in place. If there is not a filing potential, the case will remain as a NMF record.

4.31.6.1.6  (05-31-2004)
Key Case Administrative and Tier File Maintenance

  1. Monthly, each CTF will receive PCS Report 22-3, National Directory, for each flow-through record for which it has an administrative file and for which one or more investors were linked during that month. This report will be generated quarterly for all flow-through entities even if no new investors were linked to that flow-through entity during that quarter. Report 22-3 shows the key case or tier record's AIMS and PCS data elements and information about each newly linked investor. Report 22-3 is used to monitor investor linkages and must be worked monthly as follows:

    1. Investor linkages without a full AIMS data base which appear with a name control and no statute date must be perfected before they drop off the data base;

    2. Each Schedule K-1 investor that does not appear on Report 22-3 must be re-established;

    3. Investors in status 90 must be checked to ensure that they have not closed prematurely; and

    4. The Reports 22-3 must be filed in the key case (tier) administrative file.

  2. Report 21-3 TEFRA Key Case Action Report CTF, is a weekly report listing key cases whose status codes have been updated to 8X or 90.

    1. The CTF should follow up on key cases, which were updated, to status 90 to ensure that an RAR was received by the CTF.

    2. The administrative files of the key cases that have been updated to status 82 should be flagged to show that the case is in docketed status.

  3. PCS reports are covered in IRM 4.29.4.

4.31.6.1.7  (05-31-2004)
Notification of the Beginning of a Flow-Through Audit

  1. Letters similar to the TEFRA NBAP letters were created for nonTEFRA investors. The nonTEFRA versions are not required by law, but are available to send as a courtesy to taxpayers that may not otherwise be aware of a partnership audit.

  2. Unlike TEFRA, there are no TMP notice requirements. Investors may be unaware of an examination until they receive an audit report or a request to extend the statute. These letters were created to help keep taxpayers informed and avoid any surprises.

  3. A notification of the beginning of a partnership, S corporation or trust audit will be issued to each nonTEFRA investor controlled by the campus.

  4. The key case examiner will send the letters to investors they control as they deem appropriate.

  5. The follow letters are available:

    1. Letter 3457 (DO) for Field/ Letter 3457 (SC) for Campus – Notification of Beginning of Partnership Audit

    2. Letter 3458 (DO) for Field/ Letter 3458 (SC) for Campus – Notification of Beginning of S Corporation Audit

    3. Letter 3459 (DO) for Field/ Letter 3459 (SC) for Campus – Notification of Beginning of Trust Audit

4.31.6.1.8  (02-22-2008)
Verification of Schedule K-1 Income (Loss)

  1. The distributive share of income or loss and other flow-though items reflected on the copy of the Schedule K-1 received from the key case CTF will be matched against the amount of the flow-through items reflected on the investor's return.

    1. Where the amounts do not reconcile, appropriate action will be taken to clarify mismatched information through taxpayer contact.

    2. This mismatch may be attributed to a variety of situations (i.e., the name on the Schedule K-1 may be a nominee, actual losses may exceed the allowable loss limitation, etc.)

    3. After contact, any pertinent information will be provided to the key case field examiner and/or key case CTF. Only information that would impact the audit computations should be forwarded.

    4. If the taxpayer has not reported income or loss consistent with the Schedule K-1, and has not responded with information, which explains the difference, the file will be referred to a revenue agent for consideration of the IRC 6662 penalty.

  2. In some instances, investors of a principal (key case) can be trusts or nominees. It is possible to have several tiers.

    1. Any adjustments to the principal entity may flow to individual taxpayers (i.e., the shareholders of the S corporation, and the beneficiaries of the trust, etc.) through the particular entities of which they are members and not directly from the principal entity.

    2. When a tiering situation is found, necessary steps to control the additional returns should be taken. This includes the preparation and submission of Form(s) 8341 for the additional tier(s).

    Note:

    It is important to remember that a nominee will result in a partnership failing the small partnership exception. IRC 6231(a)(9) and Treas. Reg. section 301.6231(a)(1)-1(a)(2) explain the definitions of pass-through entities. If there is a nominee situation, and the partnership key case is being processed as a nonTEFRA entity, then a TEFRA partnership proceeding will have to be initiated. The field agent in charge of the case must be contacted immediately.

4.31.6.1.9  (05-31-2004)
Non-Pass-Through Issues on Investor Cases

  1. Newly secured investor returns must be screened for non-pass-through issues. If issues are identified, the CTF will coordinate with the key case examiner for the possible working of the issue(s).

  2. Investor returns and transcripts will be screened to identify any adjustment documents, amended returns, carryback, and carryover returns that will be needed to process the nonTEFRA adjustment. If the investor is a minor child, the parent's return will need to be worked with it. These must be secured before the investor file is considered perfected.

4.31.6.1.10  (05-31-2005)
Returns With TEFRA and NonTEFRA Issues

  1. A case containing both nonTEFRA flow-through and TEFRA flow-through issues will be suspensed in the CTF in EGC 5416 (dual status). The CTF will monitor the statute on the nonTEFRA case and the one-year date on the TEFRA issue. A Form 3198 (Special Handling Notice) will be prepared and attached to the case folder. The "Other" block will be checked and the following statement added: "Dual Status Case: NonTEFRA Flow-Through Issue EIN(s) and TEFRA Flow-Through Issue EIN(s)." Applicable EIN(s) will be listed on the form.

    Note:

    If multiple linkages exist, a copy of a TSUMYI print can be attached in lieu of writing out all of the EINs on the form.

  2. When dual linkages exist, the key case campus must ensure that all campus controlled investors are in a nonTEFRA EGC even if the investor is in another CTF.

4.31.6.1.11  (05-31-2004)
Statute Control

  1. The campus maintains the statute of limitations of each investor return controlled by the campus. The field is responsible for maintaining the statute control on flow-though entity returns and all investor returns controlled by the field.

    1. If the investor returns are not linked, the key case examiner assumes total responsibility for the statute control for all of the investor returns. The key case examiner is responsible for securing extensions of the statutory period of limitations on all investor returns, including tier returns and their related investors. Investors returns cannot be linked to a nonTEFRA key case if less than 7 months remain on the investor statute of limitations.

    2. The CTF is responsible for IRC 6501 statute control of returns controlled by the campus that are linked to a nonTEFRA key case.

    3. A Form 895 is prepared for each return. One copy is attached to the case file, the other will be maintained in a file for the monitoring of the statute of limitations date. ( IRM 25.6.23)

4.31.6.1.12  (02-22-2008)
Extension of Investor Statute

  1. The CTF will coordinate with the key case examiner on the progress of the examination. When it is determined that the linked investor return has less than 210 days on the statute of limitations and the examination will not result in a no change, an extension is needed to extend and protect the assessment period. ( IRM 25.6 Statute of Limitations)

    1. The CTF will prepare a Form 872-Ifor each tax period and Letter 907(DO) to send to the investor(s) at the most current address. On a joint return, a separate Form 872-I must be prepared and mailed to each spouse. One copy is maintained in the case file, two copies will be mailed to each spouse.

      Note:

      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 6501(c)(4)(B):

      a. The right to refuse to extend the limitations period.
      b. The right to request the extension be limited to particular issues held open for further examination or appeal.
      c. The right to request the limitations period be extended only to a particular period of time.

      The notification should be provided by sending or presenting Letter 907(DO) and Publication 1035.

    2. The returned consent should be signed by the taxpayer, as it appears on the return, unless there was a name change. The consent should then be prepared as "Jane Smith, formerly Jane Brown" on the name line with the new name on the signature line.

    3. If the consent is not received in the allotted time, the examiner will prepare Letter 928(DO) to send to the taxpayer.

      Note:

      An authorized Service official must sign the consent before the ASED.

    4. If the consent is returned with a change noted, Letter 1817(DO) should be sent to the taxpayer with the appropriate paragraph selected.

    5. The taxpayer or their representative may request, verbally or in writing, restrictive wording on the extension. The CTF nonTEFRA coordinator 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.

  2. When the signed consent is received by the CTF, it will be reviewed for accuracy and to ensure that the appropriate number of copies have been received. The consent will be signed by one authorized to sign on behalf of the Commissioner.

    1. One executed original consent form will be mailed to the taxpayer with Letter 929(DO). One will be retained in the case file.

    2. The copy of the executed original consent and a copy of Letter 907(DO) will be attached to the back of the front page of the return.

    3. The Letter 907(DO) serves as documentation that the taxpayer was provided with their rights as required by IRC 6501(c)(4)(B).

    4. The AIMS database statute should be updated with the extended date. When this is done, a TC 560 is automatically generated to Master File to reflect the new date.

    5. The Letter 895 will be updated to the date extended.

  3. In the case of consolidated corporate returns where the subsidiary is a partner in a TEFRA partnership, consent to extend the statute using Forms 872-I or 872-IA must be in the name of the parent and not the subsidiary. The parent of the consolidated group will sign the partner-level Forms 872-I or 872-IA pursuant to the consolidated return rules under Treas. Reg. section 1.1502- 77. In situations where the parent wishes to restrict the Form 872-I or 872-IA or have the subsidiary, who is the actual partner, sign instead, the examiner must contact local area Counsel before executing such a consent.

  4. In the case of consolidated corporate returns where the parent is partner, the consent should be in the name of the parent and signed by the parent. It is a best practice to have both the parent and the subsidiary partner sign the extension. If any known subsidiary partner is also a partner in another TEFRA partnership, it is a best practice to secure a separate signature from them. This can be done on an attachment to the Form 872-I or 872-IA using Form 13924 or 13923.

    Note:

    It may not be practical to know if all subsidary partners are part of another TEFRA partnership. In that case, ensure the parent signs the waiver.

    For tax years ending on or after June 28, 2002 (see Treas. Reg. section 1.1502- 77), if we have the subsidiary, who is the actual partner under state law, insisting on being the sole signatory on the waiver, the examiner should contact local area Counsel before executing the waiver.

4.31.6.1.12.1  (08-01-2006)
Restricted Consents

  1. Restricted consents are quite common with nonTEFRA investor cases. Care must be taken to ensure all restricted issues are covered.

  2. Research the investor for other linkages. If other linkages exist, contact the examining agent to see if other restrictions exist.

  3. There is a restricted consent indicator on AIMS that signifies if a restricted consent is secured. An "R" will follow the Statute Date if a restricted consent was secured. If an extension was secured with no restriction, an "X" will follow the Statute Date.

  4. More than one restricted consent can be secured for a taxable period(s). Once the original IRC 6501 statute is gone, each existing restricted consent may be extended timely. No other restricted issues may be added after the IRC 6501 statute has passed.

    Note:

    The original statute may be, for example, the six-year period for a return with a substantial omission under IRC 6501(e).

4.31.6.1.12.2  (08-01-2006)
Tier Extensions

  1. Under normal circumstances, the statute of limitations is not controlled at the tier level, but at the bottom line investor level.

  2. Statute extensions should be secured for trusts and, in some cases, S-Corporations. Both trusts and S-corps can be subject to tax.

4.31.6.1.13  (05-31-2004)
Related Return Suspense Files

  1. The CTF must maintain all campus controlled nonTEFRA partner tax returns in suspense.

  2. Minimum requirements for returns held in suspense are:

    1. Protection of the statute of limitations.

    2. Contact the key case examiner when an investor is past 29/30 months from the due date of the return or from the date the return was filed, whichever is later, and a status report was not received. This time period coincides with the statute of limitations expiration listings.

    3. Contact the key case examiner when an estimated completion date has passed and the key case office has not furnished a report of adjustments or a new status report.

4.31.6.1.14  (05-31-2004)
Receipt of Form 6657, Related Return Examination Report

  1. The CTF will receive the Form 6657 listing all investors and a copy of the completed examination reports and the key case file when the examination of the key case is completed. The CTF will update the status to 56 and the EGC to 5490 upon receipt of the key case file.

    Note:

    A TSUMYP print can be attached to the Form 6657 in lieu of listing all investors on the form.

    1. The Form 6657 will reflect the closing status (agreed, no-change, unagreed) of the flow-through entity.

    2. The examination report and the Form 6657 will be reproduced and a copy associated with each investor file when they are received.

    3. A copy of the examination report should also be sent to the Centralized RAR File.

4.31.6.2  (08-01-2006)
NonTEFRA Report Writing

  1. The following subsections cover the nonTEFRA report writing procedures. Also refer to IRM 4.19 and Training Guide 5715 as needed.

4.31.6.2.1  (05-31-2004)
Introduction

  1. In general, each linked investor return must have a report written disclosing the results of the examination of the flow-through return to which the investor is linked. Even though the flow-through entity agrees to the adjustments, the Service must still secure signed agreements from each investor. One or more of the investors may chose to dispute the proposed adjustments independent of the flow-through entity. The report provides the investor the opportunity to agree or appeal the adjustment.

  2. This subsection also includes the procedures for processing the written reports.

4.31.6.2.2  (02-22-2008)
Non-TEFRA Report Writing Tolerances

  1. See LEM 4.31.6.2.2 for information on tolerances.

4.31.6.2.3  (05-31-2004)
Preparing Case for Report Writing

  1. The receipt of the RAR (Revenue Agents Report) by the investor campus will indicate a need for report writing activity.

  2. Prior to the assignment of an investor file to a report writer the following actions should be taken:

    1. Acknowledge the Form 3210 which transmitted the Key case and the RAR within 3 days;

    2. Verify the statute date or extended statute date;

    3. Associate documents with the investor file, and obtain IMFOLT (or BMFOLT) and TSUMYI prints, and;

    4. Note the investor case file, and if the CTF (Campus TEFRA Function) has control of the database, update to AIMS status code 33, exam group code 542X or 543X.

4.31.6.2.3.1  (05-31-2005)
Case File Requirements

  1. Upon assignment, the report writer should check the case file to ensure it includes the following items:

    1. The original tax return or copy;

    2. An Information Returns Processing (IRP) transcript (if available) if the investor is a non-filer;

    3. The RAR, or Appeals Case Memorandum with Form 4605-A, for the key case;

    4. Form 886-X, Form 886-Z, Form 886-S or Form 886-W showing the corrected ordinary income/loss and any other examined issues;

    5. Any penalty information;

    6. An IMFOLT (or BMFOLT), TSUMY prints and CAFOL (for POA information);

    7. Schedule K-1;

    8. Form 895 Statute control ( IRM 25.6.23);

    9. Examiners must perform IDRS research to check for validity of current AIMS and PCS data and to ensure that no activity has taken place on the taxpayer's account that may affect the case such as prior assessment information (a Form 1040X, partial assessments, or other changes to the investor's account). All research performed must be documented on Form 4700 or Form 4318 Examination Work papers ( IRM 4.19.1 , Liability Determination, Campus Examination Operations); and

    10. Any related tax returns for a net operation loss, investment tax credit or foreign tax credit carryback and/or carryover, related tax returns for Passive loss, Alternative Minimum Tax Credit or Capital Loss carryover and any related tax returns for Tax for Children Under Age 14.

    11. If penalties are applicable, verify that appropriate penalty language was provided by the field.

  2. If any of these items are not present in the investor case file, the report writer must secure the information necessary for the preparation of the examination report. Depending on the statute, this may require returning the case file to another unit to secure the necessary information.

4.31.6.2.3.2  (05-31-2004)
Referring Complex Issue to the Field

  1. If, due to the complexity of the case, an employee believes that they cannot adequately prepare an investor audit report, the employee should consult with the campus TEFRA or nonTEFRA Coordinator. The campus TEFRA or nonTEFRA coordinator will provide the employee with assistance, or work with the appropriate field TEFRA coordinator in order to have the case worked in the field. Campus personnel should make every effort to work all campus controlled investors at the campus. However, there are times when the complexity of the case will require assistance from the field. It is the complexity of the issues, not the size of the case, that will dictate whether a case gets sent back to the field.

4.31.6.2.4  (08-01-2006)
Report Writing Procedures

  1. The investor's return file with the key examination report will be assigned to a tax examiner to prepare an adjustment report.

    Note:

    All investors in the same key case need to be worked together to ensure that if they require a Statutory Notice of Deficiency, it is issued simultaneously. (See IRM 4.31.6.2.6.1) Also refer to IRM 4.19 and Training Guide 5742 - Catalog Number 11662K as needed.

  2. The report writer must verify the statute date (considering the Form 872-I), and statute control using local procedures using Form 895.

  3. The report writer must determine whether penalties were recommended for the key case.

  4. The report writer will complete Form 4700, Examination Workpaper, on all cases (see IRM 4.19.1, Liability Determination, Campus Examination Operations) to reflect the investor's applicable adjustment from the flow-through entity. The report writer will attach Form 886-X, Form 886-Z, Form 886-S or Form 886-W, RAR and any other documents received from the key case examination to the Form 4700 as part of the workpapers.

  5. The investor return will normally be adjusted to reflect the amount shown on the Form 886-X, Form 886-Z, Form 886-S or Form 886-W unless the adjustment document reflects an allowable loss and the investor did not report any activity from this flow-through return on the original return.

    1. In this situation, the report writer must consider the correspondence in the file, which explains the difference between the amounts shown on the Schedule K-1 and the return.

    2. If the investor did not respond to the inquiry or responded that the loss was not claimed because of a limited basis or previous execution of a Form 906, the examiner should allow no loss as a result of the examination of the flow-through return.

  6. If the key case examination resulted in a no change, the examiner will prepare a no change letter to issue to the taxpayer.

4.31.6.2.5  (02-22-2008)
Preparation of Examination Report

  1. The report writer will input and generate three copies of Form 4549, Income Tax Examination Changes, for tax and any applicable penalties. The 4549 must include the name, telephone number and the unique identifying number of the person to contact.

4.31.6.2.5.1  (05-31-2004)
Special Computations for Oversheltered Returns (IRC Section 6234)

  1. Special computations exist for oversheltered returns related to a partnership return with a taxable year after ending August 5, 1997.

  2. An oversheltered return is an income tax return which will have no tax due after applying the proposed adjustments.

  3. A notice of adjustment, Letter 4151, may be sent to the taxpayer if:

    1. the taxpayer files an oversheltered return,

    2. adjustments are proposed (for other than partnership items) for the taxable year, and

    3. the adjustments being proposed do not create a deficiency, but would create a deficiency if there were no net partnership losses.

  4. A notice of adjustment must be sent to the taxpayer via certified or registered mail.

  5. The law allows the taxpayer to petition the Tax Court even though no deficiency exists.

  6. If the taxpayer does not petition the Court, or the court upholds the adjustments, the adjustments will be taken into account in determining the amount of any computational adjustment in connection with a subsequent partnership proceeding.

4.31.6.2.5.2  (08-01-2006)
Special Computation for Non-Oversheltered Returns (Munro Decision)

  1. Non-oversheltered returns (and oversheltered returns related to partnership returns with tax years ending before August 6, 1997) are returns that will have a taxable amount owing after the proposed adjustments (for other than partnership items).

  2. For non-oversheltered returns, Munro computations will continue to be used.

    1. When adjusting a taxpayers return for nonTEFRA flow-through issues and the Form 4549 results in a reduced deficiency because of large TEFRA partnership losses, the report writer will prepare a report without consideration of any TEFRA partnership income or losses.

    2. Prepare a report starting with the original return, or as amended, and remove all TEFRA issues from open TEFRA proceedings. Label this report as: "Information Only – Do Not Process" . Using this report as the starting point, prepare a report making the nonTEFRA flow-through adjustment.

  3. When there is an open TEFRA proceeding, the following paragraph should be used on the statutory notice of deficiency:

    In computing the deficiency attributable to the adjustments in this notice, which adjustments are neither partnership items nor affected items, as defined by IRC 6231, all TEFRA partnership items subject to an open TEFRA proceeding, whether income, loss, deduction or credits have been ignored exclusively for the purpose of computing the deficiency which is attributable to the adjustments set forth herein. All TEFRA partnership items subject to an open TEFRA proceeding have been ignored in this notice of deficiency for computational purposes only and this notice is not a substitute for any Notices of Final Partnership Administrative Adjustment (FPAA) which may be issued in regard to the TEFRA partnerships. This computation is being made pursuant to the Tax Court decision in Munro v. Commissioner, 92 T.C. 71 (1989).

  4. The following sample paragraph should be included in the explanation of items:

    The following TEFRA partnerships are subject to partnership level proceedings pursuant to the partnership audit and litigation procedures of IRC 6221 through 6234 with respect to the taxable year(s) and accordingly, all partnership items, whether income, loss, deductions or credits, have been disregarded for purposes of computing a deficiency attributable to the adjustments in this notice:

      ABC Partnership $(30,000.00)
      XYZ Partnership (7,000.00)
      HIJ Partnership (27,700.00)
      Total $(64,700.00)

  5. A Munro computation may result in an inflated deficiency due to a change in tax bracket until treatment of the TEFRA items is finally determined.

4.31.6.2.5.3  (08-01-2006)
Special Computations for Non-Filers

  1. Special computations exist for non-filer investors.

    1. Non-filer investors with an Information Returns Processing (IRP) transcript in the case file will have a substitute for return processed and the account will be controlled and adjusted on Master File. The report writer should input a Form 4549 containing both the IRP adjustments and the nonTEFRA pass-through adjustments. Continue processing per the nonTEFRA procedures.

    2. Non-filer investors without an IRP transcript will be controlled and adjusted on non-Master File. The report writer will prepare a Form 4549 for the nonTEFRA pass-through adjustment applying the highest tax bracket applicable for the tax period without benefit of exemptions or deductions. Continue processing per the nonTEFRA procedures.

4.31.6.2.5.4  (02-22-2008)
IRC Section 6404(g), Suspension of Interest and Certain Penalties

  1. In general, the notice date for purposes of IRC 6404(g) is the date adequate notice is mailed or provided to the individual investor. For TEFRA purposes it is the date a report is given to the entity. All other IRC 6404(g) rules apply.

  2. The entity notification rules only apply to TEFRA cases where audit determinations are made at the partnership level. Notification will be deemed to have been made to the partners in a TEFRA case when the 60 day letter or FPAA (if no 60-day letter is sent) is sent to the TMP. Notification for nonTEFRA investors will be their initial audit report. Typically, this will be a 30 day letter.

  3. In the case of an individual who files a return before the due date for the return (including extensions), the Service has an 36-month (18 months effective on or before November 25, 2007, and one year for tax years beginning before January 1, 2004.) period beginning on the later of:

    1. the date on which the return is filed; or

    2. the due date of the return without regard to extensions,

    in which to provide notice to the taxpayer specifically stating the taxpayer's liability.

  4. If notice is not provided to the taxpayer before the close of the 18-month period, then any imposition of interest, penalty, additions to tax or additional amounts that are calculated in reference to the 36-month time frame (18 months effective on or before November 25, 2007, and one year for tax years beginning before January 1, 2004.) are suspended.

  5. The term suspension period means the period:

    1. beginning on the day after the close of the 18-month period under (3) above and

    2. ending on the date which is 21 days after the date on which notice is provided to the taxpayer.

  6. The exceptions to the 36-month notice requirement (18 months effective on or before November 25, 2007, and one year for tax years beginning before January 1, 2004.) are:

    1. any penalty imposed by IRC 6651;

    2. any interest, penalty, addition to tax, or additional amount in a case involving fraud;

    3. any interest, penalty, addition to tax, or additional amount with respect to any tax liability shown on the return

    4. any interest, penalty, addition to tax, or additional amount with respect to any gross misstatement;

    5. any interest, penalty, addition to tax, or additional amount with respect to any reportable transaction with respect to which the requirement of section 6664(d)(2)(A) is not met and any listed transaction (as defined in 6707A(c)); or

    6. any criminal penalty.

  7. The notice date must be annotated on the history sheet in the case file, and also annotated on the case file copy of the Examination report in the "Other Information" area with the following statement: "IRC section 6404(g) does apply and notice was provided on (mail out date)."

  8. TC 971 with Action Code 64 will be input on Master File for the identified cases to record the notice date. Master File will automatically compute the interest with only one notice date. Cases with additional notice dates will require manually computed restricted interest (TC 340).

  9. If IRC 6404(g) applies, a TC 971 with reason code 064 must be input on the tax module using the notification date.

  10. All IRC 6404(g) cases where a second assessment is being made will require special instructions on Form 3198. If a second assessment is necessary, it must be stated whether IRC 6404(g) applies, and if it does, the notice date for the second assessment must be entered in the " Special/Restricted Interest Features" section.

4.31.6.2.5.5  (02-22-2008)
Passive Activity Losses (PAL)

  1. Examiners need to ensure that all applicable forms are completed when computing the PAL adjustments. The Form 8582 worksheets do not need to be completed for all cases, but should be completed when needed. For example, they should be completed to communicate changes to the taxpayer in the case of dispositions or PAL carryovers.

4.31.6.2.5.6  (02-22-2008)
Carryover/Carryback Adjustments

  1. Case files for carryback and carryover years need to have copies of the workpapers from the source year supporting the adjustments. Adjustments such as Schedule A (contributions), NOL, possibly credits and PAL Credits would also require the closing documentation from the source year and computations for any carryback or carryover.

  2. When there are PAL carryovers, for example, the case files for those years need to have all of the necessary work papers to support the PAL adjustment. The carryover case file should have the closing documents from the source year as well as the Form 8582 reflecting the PAL carryover changes. Without the source documentation, there is nothing in the carryover year file to support the changes. This information is necessary in the event a subsequent taxpayer inquiry is made.

4.31.6.2.6  (05-31-2005)
30-Day Letter Procedures

  1. The report writer will send a 30-day letter and two copies of Form 4549 to the investor to secure agreement to the flow-through issue(s). Report writers should always consider IRC 6404(g) and input a TC 971 with reason code 064 whenever applicable.

  2. The case file will be suspensed for 45 days awaiting response from the taxpayer.

  3. Generally, the 30 day letter will act as notification for purposes of IRC 6404(g).

4.31.6.2.6.1  (05-31-2005)
Agreement Received

  1. The assessments must be made as soon as possible after the agreement is received.

    1. Prepare and input Form 8339 , PCS Change, to enter the amount of the assessment. Box 11, Change(s), will be completed with Item 5, (the investor one-year date field) with 22222222, assessment amount and time. The investor case will not be allowed to close without this entered on the investor linkage.

      Note:

      The PCS will not allow anything other than 22222222 to be entered in the one year date field. An attempt to enter a real date will result in an error message.

    2. If the case is to be full closed (no other TEFRA or nonTEFRA linkages), the case is prepared for final closure. If there are open linkages (either TEFRA or nonTEFRA), a partial assessment will be made and the case will be sent to suspense to await additional packages. (See the Form 5344 procedures at See IRM 4.31.6.3. )

4.31.6.2.6.2  (05-31-2005)
Acceptance of Faxed Agreements

  1. Consents to assess additional tax ( Form 4549 , Form 870, and others) of $25,000 or less can be accepted by fax if taxpayer contact has been made and the case history documents the date of contact and the desire of the taxpayer to submit the consent by fax. Consents to assess tax in excess of $25,000 should be secured with original signatures and delivered in person or by mail.

  2. For purposes of estimating tax for flow-through adjustments, the tax is figured by multiplying the partner's share of the adjustment by the highest tax bracket percentage. The estimated tax figure will be used for figuring the $25,000 limit for the acceptance of faxed agreements.

4.31.6.2.6.3  (02-22-2008)
Request for Appeals

  1. If an investor does not agree to the proposed key case adjustments and files a protest, both the key case and the investor return will be sent to the Appeals office named in the closing package sent to the CTF. This will usually be the Appeals office that services the operation unit that examined the key case return. There must be at least 180 days remaining on the statute of limitations of any investor return sent to Appeals. See Appeals IRM 8.21.2.3. Only those investors that file a protest should be sent to Appeals. All other investor returns should be held in suspense, even if the investor does not respond to the 30-day letter. To conserve the Service’s overall resources, only a principal investor case(s) should be sent to Appeals for review of protested issues. Other investor’s cases should be kept in suspense. As a general rule, the key case and one protested case will be sent to Appeals. Exceptions are:

    1. If investors have different representatives, one case from each representative should be sent to Appeals.

    2. If an investor has no representative and files a protest, the investor case should be sent to Appeals.

    3. If there are unagreed non flow-through issues.

    All other investor returns should be held in suspense, even if the investor does not respond to the 30-day letter.

  2. Form 8339, PCS Change, will be input updating item 22 to the literal "A" on all investors. This will identify that the investor is suspensed awaiting Appeals determination.

  3. Only issue a statutory notice of deficiency when all of the investors decline the opportunity to file a protest, and there is a statute problem. It is difficult to successfully resolve disputed issues when some investors are nondocketed and others are docketed.

4.31.6.2.7  (08-01-2006)
Statutory Notice of Deficiency

  1. If there is no response to the 30-day letter, and all investors have declined the opportunity to file a protest, the report writer will research for other open nonTEFRA linkages. Only one stat notice may be issued to a taxpayer for a given tax year. If no other linkages exist, issue a statutory notice of deficiency for all investors. (See IRM 4.8.9.) If other nonTEFRA linkages exist, then that examiner will have to be contacted in order to include their adjustments in the stat notice.

  2. Once the stat notice is issued, the case file will be suspensed for 90 days awaiting a response from the taxpayer.

    1. If an agreement to flow-through issues is received, assessments must be made as soon as possible after the agreement is received. The statute expiration date must be recalculated based on the Statutory Notice of Deficiency.

    2. Prepare and input Form 8339 , PCS Change, to enter the amount of the assessment. Box 11, Change(s), will be completed with Item 5, (the investor one-year date field) with 22222222, assessment amount and time. The investor case will not be allowed to close without this.

      Note:

      The PCS will not allow anything other than 22222222 to be entered in the one year date field. An attempt to enter a real date will result in an error message.

    3. If the case is to be full closed (no other TEFRA or nonTEFRA linkages), the case is prepared for final closure. If there are open linkages (either TEFRA or nonTEFRA), a partial assessment will be made and the case will be sent to suspense to await additional packages. (See Form 5344 procedures at See IRM 4.31.6.3.)

4.31.6.2.7.1  (05-31-2005)
Non-TEFRA Key Cases With Outside Investors

  1. If a statutory notice will be issued, and there are impacted investors open outside the campus, the key case campus should request a copy of those investor's returns from the function controlling the investor. Once a copy is secured, all statutory notices should be issued at once.

  2. A copy of the statutory notice should be sent to be associated with the live investor file.

  3. Only one statutory notice may be issued on nonTEFRA cases. If an investor is open in the field, the examiner must be contacted, not only to secure a copy of the return, but also to make the examiner aware that a statutory notice is about to be issued on the investor. The issuance of a statutory notice may adversely impact the examination. Special considerations may need to be made in these instances. Contact the TEFRA or nonTEFRA Coordinator to discuss any options.

4.31.6.2.7.2  (05-31-2005)
Petition Filed

  1. If a petition is filed with the Tax Court, both the key case and the investor case will be sent to the requesting area. Other investors should be held in suspense awaiting the Tax Court decision (taking into consideration any statute problems). When the petitioned case is settled or decided, the non-petitioning investors will be sent notices consistent with the court decision.

  2. Prepare and input Form 8339, PCS Change, to enter the amount of the assessment. Box 11, Change(s), will be completed with Item 5, (the investor one-year date field) with 22222222, assessment amount and time. The investor case will not be allowed to close without this.

    Note:

    The PCS will not allow anything other than 22222222 to be entered in the one year date field. An attempt to enter a real date will result in an error message.

  3. If the case is to be full closed (no other TEFRA or nonTEFRA linkages), the case is prepared for final closure. If there are open linkages (either TEFRA or nonTEFRA), a partial assessment will be made and the case will be sent to suspense to await additional packages. (See Form 5344 procedures at See IRM 4.31.6.3..)

4.31.6.2.7.3  (05-31-2005)
No Response

  1. If no response is received from any of the investors, and no petition to the Tax Court is filed, the Statutory Notice of Deficiency will be defaulted and the tax assessed per the Statutory Notice of Deficiency. The statute expiration date will need to be recalculated based on the defaulted Statutory Notice of Deficiency.

  2. Prepare and input Form 8339, PCS Change, to enter the amount of the assessment. Box 11, Change(s), will be completed with Item 5, (the investor one-year date field) with 22222222, assessment amount and time. The investor case will not be allowed to close without this.

    Note:

    The PCS will not allow anything other than 22222222 to be entered in the one year date field. An attempt to enter a real date will result in an error message.

  3. If the case is to be full closed (no other TEFRA or nonTEFRA linkages), the case is prepared for final closure. If there are open linkages (either TEFRA or nonTEFRA), a partial assessment will be made and the case will be sent to suspense to await additional packages. (See Form 5344 procedures at See IRM 4.31.6.3.)

4.31.6.3  (05-31-2004)
Form 5344, Closing Procedures

  1. Form 5344, Examination Closing Record, is prepared by the investor CTF to process partner or shareholder return flow-through adjustments each time an agreement is received by the investor CTF.

    1. A copy of the Form 5344 will remain in the file until all flow-through issues have been resolved.

    2. The closing function will input the PCS CC TSCLS as part of the final AMCLSE procedure.

4.31.6.3.1  (08-01-2006)
Proper Completion of Form 5344

  1. Special attention must be given to certain entry items on Form 5344.

    1. Notate in RED, on the top of the Form 5344, "NonTEFRA" .

    2. CC TSCLS - this block should be checked when an investor return is linked on PCS.

      Note:

      this portion will only be completed at the time of final closing.


    3. Item 8 - Agreement Date (partial or final closings). This entry will be completed for tax years ending after August 5, 1997 ( IRC 6601(c)). Enter the date as reflected on the signed Form 4549. The date the agreement was received is required to be entered on agreed deficiency cases if the disposal code is 03, 04, or 09 and Item 12 contains an increase in tax and the MFT is 02, 05, 30, 51 or 52. See IRM 4.4.12.4.18. For partnership tax years ending before August 6, 1997, cases will be closed using disposal code 08 and no agreement date.

    4. Item 13 - Disposal Code. Cases closed no change should use disposal code 01 or 02. The adjustment amount on the Form 5344, Examination Closing Record, should be blank. Cases closed agreed or unagreed will generally use disposal codes 03, 04, 07 or 08. The adjustment amount on the Form 5344, Examination Closing Record, requires an entry other than zero. If you have a situation where the adjustments made to the entity net to zero, enter $1. After issuance of a 90-day letter, use disposal codes 09 or 10.
      01 - No Change with Adjustments
      This code should be used when no changes are made to the entity's ordinary income, loss, or separately stated items reflected on the return or Schedule K-1, and an investor's return is adjusted as a result of the flow-through examination. This would include adjustments to basis, at-risk, passive loss rules, taxable loan repayments, or adjusting the investor's return to match the Schedule K-1 flow-through amounts.

      Note:

      An audit report is not required for most cases closed below the tax tolerance in the Campus TEFRA Function (CTF). An exception will be when the tax changes impact a prior or subsequent tax year (NOL, PAL, etc).


      02- No Change
      This code should be utilized when the examination results in no changes to the entity or any investor. This would also be appropriate if you make adjustments to one of the investor's returns as a result of compliance checks which are not related to the flow-through examination.
      03 - Agreed Prior to 30-Day Letter
      04- Agreed After the 30-Day Letter
      Flow-through examinations that are closed agreed should use 03, or 04 as the disposal code. An agreed case is one where an agreement is obtained from all owners. If all signatures are received from the owners, you can close the case by indicating on the flow-through report that an agreement was obtained from the investors.
      Form 875 can be used to obtain an agreement at the flow-through level, but it is non-binding. If the case is linked and agreement is obtained at the entity level and there is no indication of an owner not in agreement, one of the agreed disposal codes can be used.
      07 - Unagreed - Appeals
      08 - Unagreed - Does not Agree or Requested an Appeal
      Disposal codes 07 and 08 are used for flow-through cases that have one or more owners who do not agree. This disposal code is also used for unagreed refund cases.
      09 - Agreed - Notice of Deficiency
      Disposal code 09 is used when a taxpayer agrees to the statutory notice of deficiency.
      10 - Default - Notice of Deficiency
      Applies only to returns if the taxpayer fails to file a petition or sign an agreement after the issuance of a 90-day letter or FPAA, or the notice goes unclaimed by the taxpayer.
      13 - Undeliverable - Notice of Deficiency

    5. Item 14 - Statute Extended to Date (partial or final closings). Because of extensions on nonTEFRA cases, care should be used to ensure that the correct information is shown on the database. If the IRC 6501 statute date has sufficient time remaining to make the necessary adjustment, no entry will be required. If the IRC 6501 statute has insufficient time remaining to allow an adjustment to be made, or the IRC 6501 statute, without regard to any consents, has expired, the Statute Extended to Date should reflect the Form 872-I date. On partial assessments, after the partial closure has been completed, the statute date on AIMS must be corrected to the original date.

    6. Item 28 - Examiner's Time (final closing only). Enter the technical time spent processing the return. This will include the report writing time. If prior partial closures were processed, the entry will be the total of all technical time spent on the case by the area and/or the CTF. Local procedures must be developed to record the cumulative time applied to each return by the CTF technical employees so Form 5344 will record all time applied (except the 631 or 632 "below the line" time) by technical employees, whether in the area or in the CTF.

    7. Item 30 - Examination Technique (final closing only). See IRM 4.4, AIMS/Processing Handbook.

    8. Item 31 - Examiners Grade (final closing only). Enter the grade of the examiner that corresponds to the employee group code entered in item 29.

    9. Item 48 - Primary Business Code (final closing only). Enter the Primary Business Code of the CTF making the adjustment.

    10. Item 411 - Payment Code (final closing only). The payment code indicates if there is a payment or partial payment on the account. The codes are as follows:
      •"F" Full Paid
      •"P" Part Paid
      •"N" No Payment
      •"O" Total Offset

    11. Item 412 - Collectibility Code (final closing only). Indicates if the taxpayer has an installment agreement.
      •" I" Installment Agreement received.
      •"C" Installment Agreement requires coordination with Collection.
      •" N" No Installment Agreement was received.

4.31.6.3.1.1  (02-22-2008)
Case File Assembly

  1. After completion of the required reports, Form 4549-A or Form 1902-B and closing documents, Form 5344 and Form 8339 (if return is linked on PCS), the report writer should prepare the case for processing by clerical personnel. The case file should contain the following documents:

    1. A Form 5344; (required)

    2. Original Return or RTVUE, 6020(b); (required)

    3. Amended Return (if one is in the case);

    4. Form 5546 (Charge out) or AMDIS print; (required)

    5. An Examination Report ( Form 4549-A, a PC Report, or computer report input documents) or No-Change Letter; (required)

    6. The closing document with the Agreement Date; (required)

    7. Correspondence and Telephone Communications (in date order with most current date first); (if present)

    8. Form 4700, Work papers, closing package with Current TSUMY attached to the top, and Schedule K-1, in descending date order of OYD’s(required);

    9. Misc. papers; (if present)

    10. A Form 8339 for each key case adjustment impacting the assessment; or in lieu of the Form 8339 a TSCHG print notated with the name of the person who did the input; (required)

    11. Form 3198; (if present)

    12. Form 5600; (if present)

    13. History Sheet (12616). Place the RGS case history to the back of the 12616; (required) and

    14. Form 895. (if present)

  2. The report writer will indicate on the history sheet what letters should be issued or any additional actions that may be required. The history sheet will also indicate the appropriate closing action. The report writer is responsible for instructing clerical and closing operators of the appropriate actions required based on the type of closure.

4.31.6.3.2  (05-31-2004)
Reports and Accomplishment

  1. The Partnership Control System (PCS) generates the administrative reports used to monitor the suspensed returns and the related key cases.

  2. The level to which unit and dollar accomplishments are distributed is now restricted to the National Headquarters and the Area.

4.31.6.3.2.1  (05-31-2005)
Reports

  1. Each CTF will use PCS reports to monitor linked returns. Specific information is provided on PCS reports in IRM 4.29, Partnership Control System (PCS) Handbook. The CTF personnel should use the Handbook if they have questions about PCS generated reports.

  2. Cases in status code 33, Employee Group Code 54XX, will be included on the CTF PCS reports. These criteria, although not all will be used for every report, are also used to determine CTF staffing levels and for specific measurements.

    1. NonTEFRA related partner or shareholder returns that are in area office possession for examination issues will not be in the CTF physical inventory.

    2. However, these returns (not Joint Committee, CIC corporate, or other corporate specialty cases) are sent to the CTF for suspense if the nonTEFRA examination is completed before a TEFRA entity examination, if any.

    3. Centralized Case Processing will update the case to Employee Group Code 5417, Status Code 33, and the Primary and Secondary Business Codes of the CTF before shipping the case.

    4. When received, the Employee Group Code should be updated to any other valid 54XX employee group code.

4.31.6.3.2.2  (05-31-2004)
Accomplishments and Inventory

  1. Accomplishments for CTF closures where the report writing was done in the campus (TEFRA and nonTEFRA) will be closed in employee group code 54XX according to the designated breakouts.

  2. The results for returns are found on AIMS Table 38 .

    1. PCS Report 8-3(N) reflects CTF nonTEFRA results by links closed; it also reflects inventory as of the report period for report writing and Suspense.

    2. PCS Report 2-3(N) is the weekly Report Writing nonTEFRA inventory; the inventory differs from the PCS Report 8-3(N) in that returns with a package indicator are not included in the 2-3(N) Report.

    3. Report 8-3(N) is a weekly report, and Table 38 is a monthly report.

    Note:

    Remember: PCS reports deal with linkages; AIMS Tables deal with returns.


More Internal Revenue Manual