13.1.11 Case and Inventory Management

Manual Transmittal

November 20, 2020

Purpose

(1) This transmits revised IRM 13.1.11, Taxpayer Advocate Case Procedures, Case and Inventory Management.

Material Changes

(1) Minor editorial, formatting and grammatical changes were made throughout the section.

(2) Replaced “Case Advocate” throughout with “TAS employee”.

(3) 13.1.11.1 Updated and renamed this subsection to incorporate internal controls. Program Scope and Objectives - Revised the title to properly reflect the information communicated in this subsection.

(4) Moved relevant content from 13.1.11.2 to new subsection 13.1.11.2.1.

(5) 13.1.11.2.1, Case Documentation, added new subsection.

(6) 13.1,11.2.1(2)(a),Case Documentation, added that employees should attach correspondence to the new TAMIS Attachment Screen.

(7) 13.1.11.2.1(2)(c), Case Documentation, added that employees should include on the TAMIS Attachment Screen any copies of ordered documents

(8) 13.1.11.2.1.2(1),Documenting Information Provided by The Taxpayer, added that employees should use the TAMIS Attachment Screen to include case file information.

(9) 13.1.11.2.1.4 Incorporated IPU 20U0663, Document Attachments

(10) 13.1.11.2.1.4.1 Attaching Documents in TAMIS When Not Assigned the Case

(11) 13.1.11.2.1.4.2 Temporary Creation of Sensitive But Unclassified (SBU) Subfolders Before Upload to TAMIS

(12) 13.1.11.2.1.4.3 Deleting Document Attachments

(13) 13.1.11.2.1.4.4 Restoring Document Attachments

(14) 13.1.11.3.1, Examples of Inventory Methods, minor editorial.

(15) 13.1.11.4(3), Case File Assembly, added using the TAMIS Attachment Screen.

(16) 13.1.11.4.1, Maintaining a TAS Case File, added minor editorial to include TAMIS Attachment Screen information.

(17) 13.1.11.2.2, Documenting Information Provided by The Taxpayer, added new subsection.

(18) 13.1.11.2.3, Documenting Analysis, added new subsection.

(19) 13.1.11.4, Case File Assembly, renamed subsection to remove “Suggested”.

(20) Added Exhibit 13.1.11-1, TAMIS Case Status Codes

(21) Added Exhibit 13.1.11-2, Case Action Table

(22) Added Exhibit 13.1.11-3, Acronyms

(23) Added Exhibit 13.1.11-4 TAMIS Permission Levels for Document Attachments

Effect on Other Documents

IRM 13.1.11 dated June 30, 2015 is superseded. IRM Procedural Update (IPU) 20U0663, issued June 2, 2020, has been incorporated into this IRM.

Audience

Taxpayer Advocate Service

Effective Date

(11-20-2020)

Bonnie Fuentes
Executive Director Case Advocacy – ITS

Program Scope and Objectives

  1. Purpose: The section provides employees with guidance on proper case file documentation and inventory management.

  2. Audience: These procedures apply to TAS Case Advocacy employees working TAS cases.

  3. Policy Owner: The Executive Director Case Advocacy, Intake and Technical Support (EDCA-ITS), who reports to the Deputy National Taxpayer Advocate (DNTA).

  4. Program Owner: The Director, Technical Analysis and Guidance (TAG), who reports to the EDCA-ITS.

Responsibilities

  1. All TAS employees working a taxpayer’s case are responsible for properly documenting all actions taken on the case and the details of discussions with taxpayers, representatives, TAS employees, and IRS employees pertinent to the case. All TAS employees working an inventory are responsible for properly managing their inventory.

  2. TAS employees should consider the issues from the taxpayer’s perspective and act with empathy as they work to resolve the taxpayer’s case and document the case accordingly.

  3. TAS managers of employees working cases are responsible for ensuring TAMIS histories are properly documented and assisting employees with inventory management, as needed.

Program Reports

  1. Program Reports: TAS employees will document case histories on TAMIS.

  2. Program Effectiveness: TAS uses a balanced measures system that includes measuring case quality. See IRM 13.5.1, TAS Balanced Measure System.

Terms

  1. The following table contains a list of terms used throughout this IRM or in a TAMIS History.

    Term Definition
    Estimated Completion Date (ECD) An estimated date for case resolution communicated to the taxpayer or representative and documented in the case history.
    Follow-up Date (FUD) A date used by TAS employees to manage the movement of a case toward resolution. A FUD is used to document when a TAS employee plans to take the next case action.
    Initial Research Research all relevant IRS systems, including IDRS, to determine the status of a case and location for assignment.
    Next Contact Date (NCD) A date given to the taxpayer or authorized individuals as to when the next contact will be made by the TAS employee.
    Systemic Advocacy Management System (SAMS) Is a computer-based system that taxpayers, practitioners, IRS, and TAS employees use to submit systemic issues.
    Taxpayer Advocate Management Information System (TAMIS) Is a computerized inventory control and report system developed for the Taxpayer Advocate Service to record, control, process and analyze cases received from taxpayers and their authorized representatives?

Acronyms

  1. See Exhibit 13.1.11-3, Acronyms, for a list of acronyms and definitions used throughout this IRM and to document TAMIS.

Related Resources

  1. This is a list of relevant IRMs TAS Case Advocacy employees will use when documenting a case:

    • IRM 13.1.16, TAS Intake and Case Receipt Process.

    • IRM 13.1.18, Processing TAS Cases.

    • IRM 13.1.21, TAS Case Closing and Reopen Case Procedures.

    • IRM 13.4, TAS TAMIS Guide.

    • IRM 13.6.1, Internal and External Communications.

Case Development

  1. Case development, documentation, and inventory management are important elements for quality casework and crucial for timely actions. Managers, analysts, and other TAS employees may have a need to review a case, and it is important that information is easily located. It is also important that the Taxpayer Advocate Service Management Information System (TAMIS) history can be followed during any point of resolution. Documentation of all actions taken in resolving the taxpayer's issue(s) is essential. In addition, TAS employees should develop a consistent, workable method for managing cases. Proper application of these elements will result in successful case resolutions and quality casework.

  2. Document how the issue impacts the taxpayer’s life in the TAMIS history. For example, the taxpayer is seeking TAS's assistance because the IRS levied 100 percent of the funds in the taxpayer's bank account. The taxpayer's only income is social security.

  3. The initial review of a new TAS case is THE most important steps in reaching a prompt and accurate resolution to the taxpayer's problem.

  4. Develop an initial action plan for resolving the case. List the actions that need to be taken to resolve the case on the TAMIS Action Plan screen. The more specific the action plan, the more efficiently the case will be worked. Refer to IRM 13.4.5.3.3, Action Plan Screen.

  5. The Case Actions screen facilitates inventory management because it creates a follow-up date (FUD), next contact date (NCD) or estimated completion date (ECD) entry in the Employee Inventory screen.

  6. When a more detailed narrative is required, use the History screen and enter the NCD and/or FUD there.

  7. Use FUDs, NCDs, and ECDs. (See IRM 13.1.18.2(6), Introduction to Initial Actions.)

    1. Clearly state and document the ECD provided to the taxpayer. The ECD should be revised as appropriate;

      Example:

      During the initial contact on July 7, the TAS employee advised the taxpayer that he expects to resolve the refund inquiry by July 30. On July 28, the adjustment input to generate the refund went unpostable. The TAS employee calls the taxpayer and advises it will be another week to resolve the issue and updates the ECD to August 4.

    2. Record FUDs, NCDs, and ECDs on the Case Actions screen so that these action dates will appear on inventory management reports; and

    3. Document the due date given to the taxpayer to submit required information.

Case Documentation

  1. TAMIS history documentation should be clear, specific, and complete. Documentation in TAMIS histories is an important element of every case. There are practical reasons for clear and complete TAMIS histories:

    1. The assigned TAS employee may not be the only person involved with resolving the taxpayer’s issue;

    2. A manager may need to discuss the case with the taxpayer or an Operating Division employee;

    3. The case may be reassigned to another TAS employee or transferred to a different TAS office; and

    4. The contents may be used as an advocacy tool for the taxpayer in a tax related court case.

    Note:

    Anyone reviewing the case should be able to follow the progress of the action plan, know what actions have been taken, what the next anticipated action will be, and when follow-up actions are required.

  2. Abbreviations may be used in the narrative. It is important that the abbreviations are meaningful so reviewers of the case history will understand the documentation. See Exhibit 13.1.11-3, Acronyms, for a list of accepted abbreviations.

    1. Correspondence sent to and received from the taxpayer should be added to the TAMIS Attachment Screen. All initial taxpayer correspondence should be date stamped with the TAS received date. The original should not be included in the case file. Subsequent correspondence should be date stamped, unless received via fax or e-mail with an electronic date stamp. It is not necessary to date stamp each page of a fax if the cover sheet with the transmission date is included in the case file. If the facsimile electronic date stamp is incorrect, use the TAS date stamp to show the correct date of receipt. See IRM 13.6.1.14(4), Facsimile (Fax) Policy.

      Caution:

      If the taxpayer sends a return to TAS, the TAS employee should handle it in accordance with IRM 13.1.18.6.3, Taxpayers Delivering Returns to TAS and TAS Date Stamp.

    2. If the TAS employee issued a Spanish version of a TAS letter, the TAMIS history should be documented with a summary of what was contained in the fill-in portion of the Spanish letter.

    3. Include in the TAMIS Attachment Screen, copies of any documents that were ordered (e.g., tax returns, MFTRAs, etc.). If the documents are voluminous, only copy the pertinent sections that are needed to support any decisions made.

  3. Documentation should be statements of fact. Do not include derogatory statements, opinions or comments on workload or office issues.

  4. TAMIS history should not include any evaluative recordation but may include direction relevant to actions needed to move the case to resolution.

Documenting Conversations
  1. Clearly summarize content of all discussions with the taxpayer, representative, the IRS and TAS employees concerning the case. Be sure to document how the issue affects the taxpayer’s everyday life, if applicable.

  2. If supporting documentation is requested from the taxpayer, provide a specific description of what was requested.

  3. Include timeframes or dates discussed with the taxpayer.

Documenting Information Provided by the Taxpayer
  1. Use the TAMIS Attachment Screen to input the case file name, description of the document the taxpayer submitted, the date received, and date created.

    Note:

    The 508 Perfection checkbox is automatically checked. Users can uncheck the box, but for now should leave it checked. This box was put in for future functionality of document attachment. See Document Attachment User Guide for more information.

  2. Summarize key facts relevant to resolving the taxpayer’s issue found within the documents received from the taxpayer.

Documenting Analysis
  1. Summarize results of IRS systems research.

    Example:

    When working collection issues where ICS or AMS history is researched and reviewed for RO and ACS activity, the TAS employee should summarize relevant information found in these histories such as the Revenue Officer (RO) or Automated Collection System (ACS) financial analysis conclusions, whether expenses were not allowed, if they determined the taxpayer met Currently Not Collectible (CNC) criteria, and/or if they are going to or have issued a levy notice.

    Example:

    When working collection issues that require financial analysis, the TAS employee should provide a quick summary of their financial analysis which should include at a minimum, the gross income, the allowed expense amount, and the minimum monthly payment amount (include the CNC closing code if they meet CNC). The TAS employee may use the SB/SE Allowable Expense Calculator for this purpose, and copy/paste their calculation into the TAMIS history to show their analysis and conclusion.

  2. Summarize procedural information from IRS sources such as IRMs, IGMs, regulations, etc.

  3. Summarize conclusions and next steps to resolve the issue.

  4. Summarize identification of systemic issues. Document if the issue was input on SAMS and include the SAMS issue number. See IRM 13.1.21.1.2.1.5.1, Systemic Issue.

Document Attachments
  1. The intent of Document Attachment is to move TAS towards paperless files; therefore, the types of documents that must be scanned and uploaded via Document Attachment include:

    • Any documents that will be submitted to an IRS Operating Division (OD)/Function as supporting documents for an Operations Assistance Request (OAR) or Taxpayer Assistance Order (TAO), including documents provided by the taxpayer or IRS administrative files;

    • Any documents that will be submitted to an IRS OD/Function to take an account action when an OAR is not required, e.g., manual refund request;

    • All TAOs sent to an OD/Function, including subsequent OD/function responses and DEDCA/EDCA/NTA Sustaining Memorandum;

    • All correspondence received from taxpayers (and their representatives) relevant to resolving the issue(s);

    • All correspondence to taxpayers (and their representatives) created by TAS, must now be converted to PDF prior to uploading to TAMIS Attachments. Employees will save those files with a file-naming convention that begins with “TA” followed by the TAMIS number of the case, a short description of the category, and include the date. For instructions about converting TAS letters to PDF, see the TAMIS Document Attachments User Guide at https://organization.ds.irsnet.gov/sites/tas/PEARL/CourseAssets/71314-103-05.pdf#search=tamis%20document%20attachments.

    • E-mails and correspondence sent to and received from IRS ODs/Functions (unless the e-mail or correspondence is copied into the TAMIS History);

    • E-mails sent to and received from other TAS employees pertaining to the case (unless the research is copied into the TAMIS History); and

    • Results of IRS systems research (unless the research is copied into the TAMIS History) relevant to resolving the issue (e.g., Automated Lien System (ALS) prints, Correspondence Imaging System (CIS) documents; copies of tax returns). If the results of the research have been summarized in the TAMIS history, it is not necessary to add a document attachment.

  2. TAS employees should upload documents to TAMIS within two workdays of receiving or sending the documentation. In the instance of e-mail chains, the two workdays are measured from the last e-mail in the chain rather than from each individual e-mail. TAS employees should refrain from adding duplicate information.

    Note:

    When TAMIS is not operational, upload the documents to TAMIS once it becomes operational. Once a document is uploaded, TAMIS will generate a systemic history. This should not take the place of detailed TAMIS histories.

  3. Once documents have been successfully uploaded to TAMIS, it is generally not necessary to retain hard copies of the documents in a paper case file. When closing a case or transferring a case to another office on TAMIS, TAS employees will also access their SBU folder and delete the folder associated with that TAMIS case file. This action will ensure that employees do not retain PII on their computers for taxpayers for which they no longer have an open case, protecting those taxpayers from possible data loss or inadvertent disclosure of PII.

    Exception:

    TAS employees will continue to retain hard copies of documents in the paper case file where the original document is needed to resolve the case, e.g., passports, original returns mailed to TAS, etc.

  4. For documents that are voluminous and not practical to scan and store electronically (e.g., documents exceeding 100 pages, or, once scanned, exceed the file size limitations for e-mailing), TAS will continue to retain hard copies in a paper case file and follow existing document retention guidelines, per Document 12990, Records Controls Schedule.

Attaching Documents in TAMIS When Not Assigned the Case
  1. There are times when a TAS employee may attach documents to TAMIS cases that they are not assigned. For example, an office receives a document from a taxpayer on a case transferred to another office. The office can load the document to TAMIS for the Case Advocate assigned the case.

  2. When a document is added to the TAMIS case, a systemic history is generated, but TAMIS is not currently programmed to alert the Case Advocate that documentation has been added to the case. Therefore, when an employee not assigned the case loads documentation to TAMIS, he or she will add a TAMIS history entry describing the activities taken on the case and set a Follow Up Date (FUD) for five workdays from the date the documentation was received or sent. Inserting a history and setting a FUD will add an alert indicator to the TAMIS Inventory screen and add an action to the Case Action Screen.

    Note:

    If the employee not assigned the case is located in another Organization Code from where the case is assigned, he or she may have to request a TAMIS permission level deviation in order to set a FUD. See IRM 1.4.13.4.9.1.1, Making Deviations from a TAMIS Permission Level.

Safeguarding Sensitive but Unclassified (SBU) Information Uploaded to TAMIS
  1. TAS employees must protect the documents temporarily stored on their computer before they are uploaded to TAMIS. All employees have a Sensitive But Unclassified (SBU) folder on their computer. Employees uploading SBU information into TAMIS will use this SBU folder to temporarily store the documents until they are uploaded to TAMIS. Consider creating sub-folders for each case with uploaded documents, so you can easily delete them once you close the case.

  2. As correspondence is scanned, e-faxed, or created in Word, all must now be converted to PDF prior to uploading to TAMIS Attachments. Employees will save those files with a file-naming convention that begins with “TA” followed by the TAMIS number of the case, a short description of the category, and include the date. For instructions about converting TAS correspondence to PDF, see the TAMIS Document Attachments User Guide. Keep in mind that TAMIS will not accept a file name longer than 50 characters. For example:

    Filename Category
    TA1234567_Corr For correspondence from the taxpayer to TAS or from TAS to the taxpayer.
    TA7654321_Supp_Doc For copies of utility shut off notices, eviction notices, medical bills, or other expense or hardship documentation.
    TA4523671_FXXX For copies of returns, schedules, financial statements, or other completed IRS forms necessary to resolve the issue.
    TA6742352_IDRS_06152018 TXMOD

  3. If multiple files are stored within the same category, they can be numbered or differentiated with a date or further description. For example:

    Filename Category
    TA1234567_Corr_TAS(1) TA1234568_TAS_03092018 For correspondence from TAS to the taxpayer.
    TA7654321_Supp_Doc(1) TA7654321_Supp_Doc_03092018 TA7654321_Supp_Doc_Evic_Notice TA7654321_Supp_Doc_Lease TA7654321_Supp_Doc_DL_SS TA7654321_Supp_Doc_Medical For copies of utility shut off notices, eviction notices, medical bills, copies of identity verification or other expense or hardship documentation.
    TA4523671_F1040X
    TA4523671_F433F TA4523671_F14039
    For copies of returns, schedules, financial statements, or other completed IRS forms necessary to resolve the issue.
    TA6742352 IDRS 08212018 TXMOD

Deleting Document Attachments
  1. There may be times when a TAS employee will delete a document previously uploaded to TAMIS. When deleting a document, the TAS employee should identify the reason for the deletion. The Delete Reason Codes are:

    • Document uploaded to the wrong case;

    • Duplicate document;

    • Unnecessary document attached; and

    • Other.

  2. TAMIS will systemically populate the TAMIS History with the File name, the user who deleted the file, and the reason the document was deleted. In addition to the systemic TAMIS History, the TAS employee will add a TAMIS History providing further explanation as to why the document was deleted when selecting the “Unnecessary document attached” and “Other” Delete Reason Codes. See Exhibit 13.1.11-4, TAMIS Permission Levels for Document Attachments, to determine who within your organization has permission to delete a Document Attachment.

Restoring Document Attachments
  1. In the rare instance a deleted Document Attachment should be restored on TAMIS, only certain TAS employees can restore the document. When a document is restored, TAMIS will generate a systemic history. See Exhibit 13.1.11-4, TAMIS Permission Levels for Document Attachments, to determine who within your organization has permission to restore a Document Attachment.

Managing an Inventory

  1. An effective system is needed to enable the TAS employee to manage an inventory that can vary in size and ensure that timely actions are taken for successful case resolution. What is important is that the TAS employee develops a workable method for consistently managing his or her cases.

  2. There are a variety of inventory management methods. One method may work for one TAS employee but not for someone else. It is important to organize cases so they can be quickly located for follow-up actions. Cases should be worked promptly, so establish priorities. Document the cases with actions taken and when follow-up actions should be made. See IRM 13.1.18.2(6) , Introduction to Initial Actions. Adherence to established FUDs is essential for timely case processing. Seek immediate assistance from a Lead Case Advocate (LCA) or manager if you need assistance determining the next action.

  3. There are general guidelines to maintain efficient case inventory management:

    1. Use available Case Advocacy reports (Business Objects Enterprise(BOE), Tableau);

    2. Develop a daily plan to work through scheduled action dates;

    3. Allow time in each workday to handle unexpected tasks or taxpayer contacts;

    4. Take all actions possible on a case before putting it aside;

    5. Establish FUDs and NCDs every time you work on the case;

    6. Keep only the cases currently being worked on your desk;

    7. Stay on top of the progress of the cases;

    8. Keep the taxpayer informed of the actions taken and when the next contact will be (this will help the TAS employee to control unanticipated taxpayer contacts);

    9. Call the taxpayer if additional information is needed. If the taxpayer cannot be reached by telephone, send a letter requesting the information needed; and

    10. If a case is completely workable — Work it and Close it.

Examples of Inventory Methods

  1. The Employee Inventory screen on TAMIS is designed to assist employees with inventory management. The Employee Inventory screen can be accessed by the "Inventory" button on TAMIS. Cases are listed in priority order based on various factors, such as Criteria 1-4, Criteria 5-7, Criteria 9, NCD and FUD. See IRM 13.4.5.3.1, Employee Inventory Screen.

  2. BOE and Tableau reports are available for employees to assist in prioritizing tasks and identifying cases that need immediate attention.

  3. A "Calendar File" method can be used. Cases are filed under days 1 through 31.

    1. Cases are placed in the file according to the next scheduled action;

    2. Once the action is completed, a new action date is established, and the case file is moved to the next appropriate date.

  4. An "Alpha File" method can be used. Cases are filed together alphabetically.

    1. Cases are pulled from the file based on action dates identified from the TAMIS Inventory screen or Case Advocacy reports.

  5. Regardless of the inventory control method used, cases should be filed so they are easily accessible on the specific FUD.

Case File Assembly

  1. Each IMF case will be placed in a folder with the taxpayer's last name, first name, and case file number shown on the outer label. Each BMF case will be placed in a folder with the business name and case file number on the outer label.

  2. Secured to the left side of the folder from top to bottom:

    1. TAS Correspondence (descending date order), including any attachments sent to the taxpayer or representative e.g., transcripts, copies of returns, etc.

    2. OAR (if applicable), including supporting documentation submitted with the OAR;

    3. Incoming taxpayer correspondence, date stamped (descending date order); and

    4. Form 911 (if applicable) or Taxpayer Initial Correspondence.

    Note:

    If the documentation has already been pasted to the TAMIS History Screen, it does not need to be included in the paper case file.

  3. Secured to the right side of the folder from top to bottom:

    1. IDRS prints;

    2. e-trak Control Ticket (if applicable);

    3. Copies of tax returns; and

    4. Additional/Pertinent Information.

    Note:

    If the documentation has already been pasted to the TAMIS History Screen, it does not need to be included in the paper case file.

  4. It may be necessary to deviate from these procedures when correspondence or case supporting documentation become voluminous or TAMIS Attachment Screen is not available. Consider using divider tabs or additional labeled folders to organize the case file.

Maintaining a TAS Case File

  1. TAMIS case histories should be documented within two workdays of when you take an action. It is important to document the case timely so that key details are not forgotten and other TAS employees can follow what is happening with the case in your absence. If the action is not documented, the assumption is that the action was not taken. See IRM 13.1.18.1(3), Processing Taxpayer Advocate Service (TAS) Cases.

  2. All information secured from the taxpayer or representative should be date stamped and associated with the case upon receipt.

  3. Include in the case file copies of any documents that were ordered (e.g., tax returns, MFTRAs, etc.) and not attached to the TAMIS Attachment Screen. If the documents are voluminous, only copy or (copy and scan when using the TAMIS Attachment Screen) the pertinent sections that are needed to support any decisions made.

  4. Scanned images and other electronic files that contain Personally Identifiable Information (PII) must be stored on the TAS employee’s computer in an encrypted, Sensitive but Unclassified (SBU) folder. See IRM 10.5.1.2.2, Sensitive But Unclassified (SBU) Data.

  5. Proper assembly of the case should be maintained throughout the resolution and closing of the case.

Closing Actions

  1. Complete the TAMIS case history and input the required fields, as discussed in IRM 13.1.21.1.2, Closing Actions.

  2. Ensure Form 2848, Power of Attorney and Declaration of Representative or Form 8821, Tax Information Authorization, secured during the case is forwarded to the CAF unit and processed.

    Note:

    Verify Form 2848 is posted correctly to the account prior to closure.

  3. Properly dispose of all duplicate or unnecessary information at closing (e.g., draft letters and duplicate IDRS prints).

  4. If original documents have been secured from files, return them to the refile unit prior to closing the case.

  5. Ensure that all documents are uploaded on the TAMIS Attachment Screen before removing them from the employee's SBU folder.

  6. Delete electronic files containing PII from your computer once the case is closed include hard copies of such files in the paper case file to meet document retention requirements. See Document 12990, Records and Information Management Records Control Schedules.

    Caution:

    If you have received a litigation hold notice from the Office of Chief Counsel, you have a legal duty to preserve evidence that is relevant or potentially relevant to the litigation (even if that means retention beyond the normal record retention period). Thus, in certain situations you may not be able to delete files once the case is closed. For more information, see IRM 25.3.1.7, Preserving Electronically Stored Information In Litigation Cases.

  7. If documents or files were secured from other IRS Operating Divisions, such as TFRP Files, Exam Files, RO Closed Case Files, etc., return them to their originating office prior to closing the case. Document in the TAMIS history what file was returned and to which operating division.

TAMIS Case Status Codes

Status Codes Definitions
O Open
C Closed
R Referral
M Monitor
S Suspend

The 911h Status Log on the database, may also contain:

Status Codes Definitions
X Transfer
P Reopen

*No other status types exist.

Case Action Table

The following table contains a list of codes and definitions used on the Case Action Screen.

Action Action Type Definition
C Contact This action indicates a contact is required.
E Estimated Completion Date This action indicates when actions on a case will be completed.
F Follow-Up Action This action indicates when a follow-up action will be taken on a case.
H Collection Hold This action indicates a follow-up to extend or close a collection hold is required.
I Initial Contact This action is systemically generated to alert employees of required taxpayer contact. The system will set a date 3 workdays from the TARD on criteria 1-4 cases and 5 workdays from the TARD on criteria 5-9 cases.
M Monitor This action indicates the case is being monitored for actions to take place on the taxpayer’s account. For example, adjustments made on account, release of Levy’s or Liens, etc.
O OAR This action is systemically generated when a Form 12412, Operations Assistance Request (OAR) is prepared and may be manually input to indicate a follow-up on OAR completion is necessary.
R Referral This action indicates a follow-up on a referral made to ITAP for technical assistance is necessary.
T TAO This action indicates a follow-up on the status of a TAO is necessary.

Acronyms

Acronyms Definitions
ACA Affordable Care Act
ACS Automated Collection System
Adj or adjmt Adjustment
AIMS Audit Information Management System
AM Accounts Management or Answering Machine
AMS Account Management Services
ANMF Automated Non-Master File
AP Action Plan
APR Apology rendered or Applicable Rate
APTC Advanced Premium Tax Credit (ACA)
ARC Annual Report to Congress
ATA Account Technical Advisor
ATAO Application for Taxpayer Assistance Order
AUR Automated Underreporter
BFS Bureau of Fiscal Service
BMF Business Master File
BOD Business Operating Division
BOE Business Objects Enterprise
CA Case Advocate
CABIC Case Assistance by Issue Code
CADE Customer Account Data Engine
CAF Centralized Authorization File
CAP Congressional Affairs Program or Collection Appeals Program
CAWR Combined Annual Wage Reporting
CC Canceled check(s), courtesy copy or carbon copy
CCI Centralized Case Intake
CEAS Correspondence Examination Automation Support
CEP Coordinated Examination Program
CI Criminal Investigation
CIS Collection Information Statement or Correspondence Imaging System
CK/CKD check/checked
CNTA Division Counsel/Associate Chief Counsel (National Taxpayer Advocate Program)
Cong Congress person or Congressional
CRU Centralized Reconsideration Unit
DA Delegated Authority
DBA Doing business as
DEDCA Deputy Executive Director Case Advocacy
DNTA Deputy National Taxpayer Advocate
DOA Delegation of Authority
DV Disclosure of Taxpayer/POA/TIA verified – Taxpayer/POA/TIA Authenticated
e-Trak Electronic Tracking System
ECD Estimated Completion Date
EDCA Executive Director, Case Advocacy
EDCA-ITS Executive Director Case Advocacy, Intake and Technical Support
EIR Early Intervention Review
EUP Employee User Portal
FATCA Foreign Account Tax Compliance Act
FP Fully paid
FPLP Federal Payment Levy Program
FU/FD Functional Unit/Division
FUD Follow-up Date
GAO Government Accountability Office
GL Governmental Liaison
GM Group Manager
HRA High Risk Authentication
HRDV High Risk Disclosure Verified
IA Intake Advocate or Installment Agreement
**IA ADJ** Input of an account adjustment (TAMIS History Literal) by Intake Advocate
**IA CHKCL** Initiate a Refund Trace (TAMIS History Literal) by Intake Advocate
**IA Stat 60** or generic **IADA** Input Streamline or Guaranteed Installment Agreement (TAMIS History Literal) by Intake Advocate
IAT Integrated Automation Technologies
ICS Inventory Control System or Integrated Collection System
ID/self/TAS Identified self, name, badge #, phone and fax # and TAS handling.
IDRS Integrated Data Retrieval System
IDTVA Identity Theft Victim Assistance
IGM Interim Guidance Memorandum
IMF Individual Master File
IPSU Identity Protection Specialized Unit
IRM Internal Revenue Manual
ITA Interactive Tax Assistant
ITAP Internal Technical Advisor Program
ITAR Identity Theft Assistance Request
IVO Integrity and Verification Operations
JRC June Report to Congress
LMOAM Left message on answering machine
LMTCB/LCBM Left message to call back/Left call back message
LTA Local Taxpayer Advocate
MEC Minimum essential coverage (ACA)
MF Master File
MSG Message
MTCB Message to call back
NCD Next Contact Date
NDA No data available
NFTL Notice of Federal Tax Lien
NLT No later than
NMF Non Master File
NTA National Taxpayer Advocate
OAR Operations Assistance Request
OBR Offset Bypass Refund
ODC Oral Disclosure Consent
OD/Function Operating Divisions or functions of the IRS that do not include TAS
OIC Offer in Compromise
OOO Out of office
P & I Penalties and Interest
PANG Phone, address, name given
**Pay EXT** Input an Extension of Time to Pay (TAMIS History Literal)
PCA Private Collection Agency
PCIC Primary Core Issue Code
PDC Private Debt Collection
**PDT** Potentially Dangerous Taxpayer indicator on IDRS
PFANG Phone, fax, address, name given
PFANBATCGA Phone, fax, address, name given, badge (ID), apology, TAS Confidentiality, TAS statement of independence given (including statement, TAS reports to Congress through the NTA) and TP authenticated
PFANBATGA Phone, fax, address, name given, badge (ID), apology, TAS statement of independence given (including statement, TAS reports to Congress through the NTA) and TP authenticated.
PI Positive identification
PII Personal(ly) Identifiable Information
POA Power of Attorney or Plan of Action
PSD Problem Solving Day
PTC Premium Tax Credit (ACA)
QC Quick Closure
QCTL Questions the constitutionality of the tax law
QRP Questionable Refund Program
RAMPI Request Answering Machine; Positive Identification
RATA Revenue Agent Technical Advisor
RDO Regular day off
Rec'd/recd received
Recon Audit Reconsideration
Rep Congressional Representative or Authorized Representative
R/O or RO Revenue Officer
ROTA Revenue Officer Technical Advisor
RPS Revenue Protection Strategy
SA Systemic Advocacy
SAMS Systemic Advocacy Management System
SBA Small Business Administration
SBREFA Small Business Regulatory Enforcement Fairness Act
SBU Sensitive but Unclassified
SCIC Secondary Core Issue Code
Sen Senator
SERP Servicewide Electronic Research Program
SFC Senate Finance Committee
SLA Service Level Agreement
SRP Shared Responsibility Payment (ACA)
**STAUP** Input a Collection hold (TAMIS History Literal)
TA INV Taxpayer Advocate involvement
TAG Technical Analysis and Guidance
TAGM Taxpayer Advocate Group Manager
TAMIS Taxpayer Advocate Management Information System
TAO Taxpayer Assistance Order
TARD Taxpayer Advocate Received Date
TAS Taxpayer Advocate Service
TBOR Taxpayer Bill of Rights
TC or PC Telephone call
TCM or PCM Telephone call made
TDC Taxpayer Digitation Communications
TECH Technical Advisor
TECH ADV Advice from a TECH
TECH CASE Case assigned to a TECH
TFRP Trust Fund Recovery Penalty
TIC Taxpayer Issue Code
TIGTA Treasury Inspector General for Tax Administration
TOP Treasury Offset Program
TP Taxpayer
TPH/TPW Taxpayer husband/wife
TPP Taxpayer Protection Program
TPPI Taxpayer phone inquiry
TPRQ Taxpayer request
w/ with
w/i within
w/o without
WOEA Warned of enforcement action

TAMIS Permission Levels for Document Attachments

The activities allowed on the Document Attachment screen depend on the permission level of the user. The TAMIS permission levels are as follows:

Permission Level Explanation
0 General
1 Case Advocate Limited
2 Case Advocate or Intake Advocate Full
3 TAS Manager or Lead Case Advocate (when performing duties of a TAS Manager)
4 Local Taxpayer Advocate (LTA) and LTA Staff (including acting assignments)
5 TAMIS Super User (Limited to four TAS Headquarters employees)

The following chart outlines how each permission level can use the Document Attachment screen:

Permission Level View in Same Org View in All Orgs Upload in Same Org Upload in All Orgs Delete in Same Org Delete in All Orgs Restore in Same Org Restore in All Orgs
0 X X            
1 X X X          
2 X X X   X      
3 X X X   X   X  
4 X X X   X   X  
5 X X   X   X   X