8.20.3 Appeals Centralized Database System (ACDS)

Manual Transmittal

October 15, 2014

Purpose

(1) This transmits revised IRM 8.20.3, Account and Processing Support (APS), Appeals Centralized Database System (ACDS).

Material Changes

(1) Editorial changes have been made throughout this chapter.

(2) Links to other IRM chapters, Exhibits, Form and Documents were added.

(3) New Appeals Centralized Database System (ACDS) fields "Date DKTAD" are now available on ACDS to track when the skeletal record or dummy file are created, and when the original administrative file (tax return) is received.

(4) References have been changed from Appeals Officer, Settlement Officer, Tax Computation Specialist, etc. to Appeals Technical Employee (ATE).

(5) IRM 8.20.3.3.16 is updated to add the Request Appeal Date (REQAPPL) for potentially defaulted Offer In Compromise (OIC) cases.

(6) References to the Collection Due Processing Tracking System (CDPTS) have been removed.

(7) IRM 8.20.3.57 is deleted to remove obsolete information regarding the Issue Tracking Indicator field.

Effect on Other Documents

This IRM supersedes the information in IRM 8.20.3 Account and Processing Support, Appeals Centralized Database System (ACDS), dated September 25, 2013.

Audience

Appeals

Effective Date

(10-15-2014)

John V. Cardone
Director, Policy, Quality and Case Support

Appeals Centralized Database System (ACDS)

  1. The Appeals Centralized Database System (ACDS) is a computerized case control system used to control and track cases throughout the appeal process.

  2. Information input into ACDS is used as follows:

    1. To control cases during the unassigned period.

    2. To control and track cases in inventory until final closing.

    3. For statute control.

    4. To record key actions taken as the case moves through the appeal process.

    5. To record Appeals Technical Employee (ATE), Appeals Account Resolution Specialist (AARS), and Account and Processing Support (APS) time applied to cases, status of cases, etc.

    6. To automate the process of changing, updating and modifying statutes.

    7. To further improve statute control and data accuracy.

  3. ACDS combines various database systems into one centralized web-based system. Although each area retains "ownership" of its cases, a centralized data repository is shared. This means that when a case is created on ACDS, various data fields become shared, available to each part of the system that needs the information. By using a centralized data repository, the functionality from all sub-systems is integrated into a single application for all users. The database can only be accessed using an IRS computer.

  4. ACDS is a role based application and your role will determine which permissions you have in the system. To get access to ACDS, you must submit an On Line 5081 (OL5081). Your ACDS account name will reflect your official name as shown on the OL5081 system unless you have an officially designated pseudonym as verified by the Discovery Directory.

  5. APS employees will have access to a variety of functions to enable them to do their job, based on the permissions authorized by their manager. Employees may be authorized to log on to ACDS and access different offices. The following is a listing of the functions that are available to APS employees if permissions have been granted:

    • CASES - This allows an APS Tax Examiner (APS TE) to establish, update, transfer, close, etc. a case in ACDS

    • PERSONNEL - This allows an employee to update his/her personnel file.

    • DIMS - Docket Information Management System - This allows access to DIMS which is the system used by APS to identify Tax Court cases and monitor them until they are received in Appeals and updated on ACDS.

    • APS - This function provides access to the Processing Employee Automated System (PEAS), the inventory and timekeeping system used by APS

    • APGOLF - This provides the ability to generate forms and letters using taxpayer data found in ACDS

    • AMATCH - This allows access to generate various types of validation reports for the Audit Information Management System (AIMS) and the Innocent Spouse Tracking System (ISTS)

    • PCS - Partnership Control System - This allows access to generate PCS reports

    • REPORTS - This allows access to various reports, transmittal Form 3210 and case summary cards

    • ADMIN - This allows an employee to perform various administrative functions if permissions have been granted

  6. These additional functions are available to all ACDS users:

    • Home - This returns the user to the ACDS home page and identifies your home area in relationship to the Field and Campus Areas

    • ACDS Memos - Allows access to all ACDS memorandums that have been issued

    • SEARCH - This allows an employee access to search the ACDS open or closed database using various options such as Taxpayer Identification Number (TIN), Taxpayer Name (TPName), i.e. TIN, TPName, docket number, etc.

    • Utilities - This has a variety of selections, such as a calendar, statute date computation, number of days, target date, Julian date, RRA 98 SN Expiration, Name/UserID Lookup and Forms/Letters Generator

    • Print- This prints the current screen

    • Validation - This allows APS and Appeals Technical Employees to update critical data fields and change the statute date, statute code, and tax period.

    • Validation Tracking Log - This log shows all updates that have been input and validated.

    • LOGOUT - It is a security requirement for employees to log out when exiting ACDS.

Researching ACDS Before Establishing Cases/Returns

  1. When new receipts are established on CASES, a work unit number (WUNO) will automatically be generated.

  2. The APS TE will search both the open and closed databases prior to establishing a new receipt to determine if:

    1. The taxpayer has a previous case on ACDS and if so,

    2. Whether or not it is part of another WUNO.

  3. The above steps will help to eliminate additional case updates such as:

    1. Changing the WUNO.

    2. Adding a key taxpayer name and key TIN.

    3. Changing the key tax period.

    4. Duplicating cases that are already on ACDS.

INPUT Case/Returns

  1. When establishing cases on ACDS, eCase functionality will provide the ability to pick a case from the source systems of Automated Offer In Compromise (AOIC), Integrated Collection System (ICS), Automated Collection System (ACS), and Examination Returns Control System (ERCS) if available in the eCase holding tank. The interface extracts data from the source systems and populates fields in ACDS to reduce data entry when establishing cases. However, the APS TE must validate the information appearing on the screen against the physical administrative file. If any of the information appears to be incorrect, the critical data fields must be updated as part of the Create Validation process. Refer to IRM 8.20.5.3.2 for more information on the Create Validation process.

Case Inventory Screen - TPName

  1. Taxpayer's name as shown on the latest documents in the administrative file such as the tax return, AIMS print, ENMOD/INOLES, etc.

  2. Individual Master File (IMF) cases should be entered in Last Name, First Name format and Business Master File (BMF) cases should be entered as they appear on the Master File.

Street, Street2, City, State, Zip, Country

  1. This is the taxpayer's most current address from documents in the file such as the ENMOD print, INOLE print, tax return, correspondence, etc.

  2. This is a required entry.

WUNO (Work Unit Number)

  1. This is a computer generated 10 digit number that identifies a unique grouping of one or more related cases. The format of the WUNO is xxyydddnnn. Each set of letters represent specific information as follows:

    • xx = the two digit Appeals Office Code (AOC)

      Appeals Office Code Appeals Office
      10 Atlanta
      12 Greensboro
      13 Jacksonville/Tampa
      14 Fort Lauderdale/Miami
      15 Nashville
      20 Buffalo
      21 Boston
      22 Hatrford, Connecticut
      23 New York City
      24 Long Island
      31 Chicago
      33 Milwaukee
      35 St. Louis, Missouri
      36 St. Paul, Minnesota
      41 Cincinnati
      43 Detroit
      44 Indianapolis
      50 Dallas
      51 Denver
      53 New Orleans
      54 Oklahoma City
      55 Austin
      60 Los Angeles
      61 Phoenix
      63 Laguna Niguel
      64 San Francisco
      65 Seattle
      68 San Jose
      71 Baltimore
      72 Newark
      73 Philadelphia
      75 Richmond
      93 Fresno Campus
      95 Brookhaven Campus
      96 Covington Campus
      97 Memphis Campus
      98 Ogden Campus
      99 Philadelphia Campus
    • yy = represents the year the case was created in Appeals, i.e., 2014 = 14

    • ddd = the Julian date that the case was established, i.e., if a case was established on January 2, ddd = 002

    • nnn = a sequential number identifying when the case was established for a specific day, i.e., the first case established on a specific day, nnn = 001, the second case, nnn = 002, etc.

  2. To link the case to an existing WUNO, enter the WUNO in the format described above.

  3. The WUNO originally generated will remain constant for the life of the case in Appeals. If the case is transferred, the WUNO will not be changed by the receiving Appeals Office.

  4. An example of the WUNO entry is as follows: Taxpayer B's case is received in the New York Appeals Office on February 5, 2014. It is the first case to be established on ACDS on February 24, 2014. The computer generates the number as 2314055001.

TIN & TIN2 (Taxpayer SSN or EIN)

  1. Enter the primary Taxpayer Identification Number (TIN) in the first TIN field. This is the Social Security Number (SSN) or Employee Identification Number (EIN) of the primary taxpayer shown from documents in the administrative file such as the tax return, AIMS print , etc.

  2. Enter TIN2 when there is a secondary taxpayer on the account such as when a joint returned is filed.

  3. Special instructions apply for innocent spouse and non-petitioning spouse cases. See IRM 8.20.5.30.5 for innocent spouse carding information and see IRM 8.20.5.5.5 for non-petitioning spouse carding information.

TIN Modifiers

  1. Unique modifiers are sometimes added to the TIN to identify special cases. They are as follows:

    • N - used to identify non-master file cases

    • P - used to identify an Employee Plan (EP) revocation case

    • V - used to identify estate and gift tax cases

    • A through J - used to allow multiple use of TINs within the same WUNO

  2. The following modifiers are systemically (computer) generated based on an action taken on ACDS:

    • R - used to identify a reassigned case

    • S - used to identify a reject

    • T - used to identify a transfer in case

    • Y - used to identify a case closed using closing code 42 or 43

    • Z - used to identify a recalled case (other than a reject)

MFT (Master File and Non-Master File Tax Code)

  1. Enter the two digit code representing the type of tax.

  2. A complete list of all MFT codes can be found in Document 6209 Section 4, Page 17.

TPType

  1. TP Type is valid only with MFT 30 and indicates the TIN controlling the Appeal.

  2. The codes used are consistent with those used for controlling cases on the ISTS and posting of Collection Statute Expiration Date (CSED) extensions to the Integrated Data Retrieval System (IDRS).

  3. Valid entries are:

    • P - primary TIN only is at issue in the case

    • B - both TINs are part of the case

    • S - secondary TIN only is at issue in the case

TYPE

  1. 1) Enter the code which represents the type of tax or penalty. This information is generally determined by the type of return filed.

  2. See Exhibit 8.20.3-1 for a list of type codes. In addition, a complete list of valid type codes can be found on the ACDS Utilities menu.

FEATRCD (Feature Code)

  1. Enter the two digit code(s) that identify all special features of the case.

  2. Up to eight (8) special Feature Codes can be shown on a case at one time.

  3. The information can be obtained from documents in the administrative file, i.e., revenue agent's report, etc.

  4. A complete list of valid Feature Codes can be found on the ACDS Utilities menu.

    Note:

    Feature Codes should be entered by the APS TE when they are identified at the time of carding, or may be entered by the ATE when they identify additional applicable codes during their review of the administrative files.

SOURCE

  1. This field is used to identify the function forwarding the case to Appeals. The valid entries for this field reflect the old IRS structure prior to the formation of the current IRS operating divisions.

  2. This a required entry on ACDS.

  3. Determine and enter the two character code that identifies the source of the case based upon analysis of the administrative file. This code should remain constant throughout the appeal process.

  4. The following codes apply:

    • FE - Field Exam - All cases with employee group code (EGC) of 1XXX on the AMDISA

    • OE - Office Exam - All cases with EGC of 2XXX on the AMDISA

    • CO - Collection - All cases received from the Compliance Collection function (see Transmittal Forms)

    • EP - Employee Plans - All cases with EGC of 71XX or 73XX on the AMDISA

    • EO - Exempt Organizations - All cases with EGC of 72XX on the AMDISA

    • SC - Campus - All cases received directly from a Campus Compliance function (see Transmittal Forms)

    • CE- Coordinated Industry Cases (CIC) have a "CIC Case indicator on line 3 of the AMDISA" . A case can be manually included in this type code by changing the Issue Tracking Indicator (ITIND) on the CASES screen.

DO (District Office or Service Center Code)

  1. The AIMS Assignee Code replaced the District Office (DO) Code. The DO code is no longer a required entry on ACDS.

    Note:

    See Document 6209, Chapter 12, for a complete description of the AIMS Assignee Code, Primary Business Code (PBC) and Secondary Business Code (SBC).

PART

  1. This item is computer generated and displays the number 1, 2, or 3 based on whether the case is docketed or non-docketed and who has jurisdiction.

    • 1 = non-docketed, Appeals jurisdiction

    • 2 = docketed, Appeals jurisdiction

    • 3 = docketed, Counsel jurisdiction

      Note:

      The Part is blank if the case is unassigned.

AO - Appeals Officer (userid/POD/Group)

  1. Reflects the ATE assigned the case.

  2. The reference includes the following employees:

    • Appeals Officer (AO)

    • Settlement Officer (SO)

    • Appeals Account Resolution Specialist (AARS)

  3. Next to the employee's name appears the:

    • userid = a systemically generated number specifically assigned to that account

    • POD = the employee's post-of-duty location

    • Group = designates the employee's group number

  4. On a docketed case where an answer to a petition is required by Counsel and an assignment is not being made, leave this field blank.

  5. A case will not be considered in the staffing model as a receipt and not considered for any measure that starts or stops with the date the case is assigned to an ATE.

RS (Records Status)

  1. The following Records Status can be used for a case assigned to APS. The case will not be considered in the staffing model as a receipt and not considered for any measure that starts or stops with the date the case is assigned to an ATE:

    • 98 --- Transfer-in cases are automatically assigned to Employee Number 98 when a case is receipted from the INBOX. This is a temporary assignment and is only intended to assist APS in retaining the original ASGNDATE on CASES. The case should be assigned to an ATE as soon as assignment can be determined.

    • 99 - is systemically generated when a case is reactivated as a reject.

ASGNDATE (Date Assigned)

  1. The assigned date will be entered by the Appeals Team Manager (ATM) or the ATM Secretary when the case is assigned to an ATE. The date will be entered in MMDDYYYY format such as June 15, 2014 is entered as 06/15/2014.

  2. For Collection Due Process Offer in Compromise (CDP OIC) cases, enter the date the new WUNO was assigned to the ATE.

  3. If the AO field is blank, this item is bypassed.

  4. This date remains constant throughout the appeal process.

REQAPPL (Request Appeal - Date Taxpayer Requested Appeal)

  1. For non-docketed cases:

    1. If the request was written, the date of the protest should be used. If it is undated, use the postmark date, and if that is not available, use the date the protest was received.

    2. If the request was verbal and is documented in the administrative file, that date should be used.

    3. For Offer in Compromise cases, the REQAPPL date is the postmark date of the taxpayer's request for appeal.

    4. For potential defaulted OICs, use the date from Form 2209, Courtesy Investigation.

    5. This is a required entry for all CDP cases (Type equal to Due Process Lien or Due Process Levy, DPL) cases. The REQAPPL date can be found on Form 14461 for Field CDP cases on page 2 (the 4th column) or on Form 12153-B for ACS cases in box 4.

    6. For CDP/OIC cases, the REQAPPL date is the earliest date the Form 656 was received by the Internal Revenue Service (date stamped in the upper right hand corner). The Tax Increase Prevention and Reconciliation Act (TIPRA) statute will be two years from this date. See IRM 8.23.2.3 for additional information regarding the TIPRA statute date.

    7. If there is no documentation in the file, this item should be left blank.

  2. For docketed cases, use the date the petition was filed.

  3. For Reference Return (RFRTN) cases, leave this date blank.

  4. This field is a required entry as indicated above.

RECDATE (Received Date)

  1. Enter the date the administrative file was received in Appeals. This date should remain constant throughout the appeal process with the exception of the following information for the Received Date on docketed cases.

    Note:

    See IRM 8.20.5.5.2.1 for additional information on the Received Date for docketed cases. If the original administrative file is received before ASGNDATE is input, change the RECDATE to the date the administrative file is received in Appeals. If the original administrative file is received after ASGNDATE is input, change the RECDATE to the same date as ASGNDATE. This practice creates a more accurate P1 measure.

  2. The RECDATE for Offer in Compromise (OIC) cases is date the case was received in Appeals.

  3. The RECDATE for CDP/OIC cases is the date the ATE's request for a new CDP/OIC WUNO was received in APS.

  4. A new WUNO will be established for premature referrals when returned to Appeals.

PROJCD (Project Code)

  1. This field is systemically populated based on programming criteria.

  2. The source of the information is from AIMS.

  3. The information is visible on the CASES inventory screen but is not available for edit by APS.

CREATED (Created Date

  1. The CREATED (Created Date) is the date the case was established on ACDS by the original office.

  2. This is computer generated and cannot be changed.

DKTNO (Docket Number)

  1. The docket number (DKTNO) is used by the Tax Court when a petition is filed or by District or Claims Court when a complaint is filed for control purposes.

  2. This item is to be completed for docketed cases and see IRM 8.19.9.1.1(6) for additional information for the docket number of non-TEFRA key cases.

  3. The information for this can be obtained from various documents in the administrative file such as the TLCATS screen print and also on DIMS.

  4. The docket number for Tax Court cases is written in NNNNN-YY format, with "N" being the number and "Y" being the year docketed. If it is a small tax case, enter "S" after the year.

  5. For District or Claims Court cases use the characters and numbers shown on the filed complaint.

DC OFFICE (Counsel Office)

  1. This item is to be completed only on docketed cases.

  2. Enter the three digit code identifying the Counsel Office assigned to the case. See Exhibit 8.20.3-3 for a list of Counsel Office codes.

  3. The information for this item can be obtained from documents in the administrative file such as the petition or from DIMS or from the Tax Litigation Counsel Automated Tracking System (TLCATS).

ATTORNEY (Counsel Attorney)

  1. This item is to be completed only on docketed cases. Enter the name of the Counsel Attorney assigned to the case, last name first.

  2. This information can be obtained from TLCATS or Form 1734 , Transmittal Memorandum.

KEYTP (Key Taxpayer Case of the WUNO)

  1. If the case is the key case, leave this item blank.

  2. If there is more than one case in the WUNO, enter the name of the key case in this field on the related case summary card to create a related record within the same WUNO.

KEYTIN (Key TIN)

  1. If the case is the key case, leave this item blank.

  2. If the case is not the key case, enter the TIN (SSN or EIN) of the key taxpayer.

KEYPER (Key Tax Period)

  1. This is a required entry. Enter the key tax period of the key taxpayer case, in YYYYMM format. If the key case contains multiple tax periods, the earliest tax period will be the key. For Estate Tax cases, use the date of death in YYYYMM format for this field.

Repname (Representative's Name)

  1. Enter the name of the taxpayer's representative per Form 2848, Power of Attorney and Declaration of Representative, or the attorney of record from the Tax Court petition or CFINK.

  2. Format is last name, first name.

  3. This is a required entry when the information is available.

  4. Additional information for APS TEs regarding representative information on ACDS:

    IF: THEN:
    Form 2848 is included in the administrative file Enter the name of the taxpayer's representative from the Form 2848
    If CFINK is included in the administrative file Enter the name of the attorney of record
    If both Form 2848 and CFINK are included in the administrative file Determine which date is more current and enter that information on ACDS. If you are unable to determine which information is more current, then alert the ATE.
    If the case is DOCKETED Enter the attorney of record as shown on the Tax Court petition. Please note the attorney of record may not match the representative information shown on the Form 2848. When unsure, alert the ATE.

    Note:

    If Form 8821 is present in the administrative file, annotate this in the NOTES field on ACDS.

Repname2 (Second Representative's Name)

  1. Enter the name of the second representative if it is available from information in the administrative file.

Repname3 (Third Representative's Name)

  1. Enter the name of the third representative if it is available from information in the administrative file.

ADDRESS (Representative's Address)

  1. Enter the address of the taxpayer's representative from CFINK research or from the Form 2848, or the address of the attorney of record from the Tax Court petition, if available.

  2. This is a required entry when the information is available.

RepStreet2 (Second Representative's Address)

  1. Enter the address of the taxpayer's second representative per Form 2848, Tax Court petition or from CFINK research.

  2. This is a required entry when the information is available.

SNTYPE (Source and Type of Notice of Deficiency/Determination Letter Issued)

  1. This item is to be completed on all cases in 90 or 150 day status in which a notice of deficiency or a notice of determination letter has been issued, including docketed cases received in from Compliance or the Campus.

    • 030A - Appeals issued CDP notice of determination letter

    • 090A - Appeals issued notice of deficiency

    • 150A - Appeals issued notice of deficiency to taxpayer residing outside the United States

    • 180A - Appeals issued notice of final determination of partial or full disallowance of an abatement of interest claim

    • 090D - Compliance issued notice of deficiency

    • 150D - Compliance issued notice of deficiency to taxpayer residing outside the United States

    • 090S - Campus issued notice of deficiency

    • 150S - Campus issued notice of deficiency to taxpayer residing outside the United States

    • FPAA -Tax Equity and Fiscal Responsibility Act of 1982 (TEFRA) Appeals Issued Final Partnership Administrative Adjustment (FPAA)

    • FPAD - TEFRA Compliance Issued FPAA

    • FPAS - TEFRA Campus Issued FPAA

    • FSAD - TEFRA Compliance Issued FSAA

    • FSAS - TEFRA Campus Issued FSAA

    Note:

    In the event the notice of deficiency is rescinded under Rev. Proc. 98-54, follow the instructions set forth in IRM 8.2.2.14.

SNDATE (Notice of Deficiency/Determination Letter Date)

  1. Date the notice of deficiency or notice of determination letter was issued (or the date that an FPAA is mailed to the Tax Matters Partner (TMP)).

  2. This item is to be completed on cases received, in 90 or 150 day status, from Compliance or the Campus, or on Appeals issued notices of deficiency, or Appeals issued notice of determination letters.

  3. The date stamped on the notice of deficiency or notice of determination letter is the issue date.

SNEXPDATE (Statutory Notice Expiration Date)

  1. This item is computer generated and reflects the appropriate expiration date based on the type of notice and date issued.

  2. On 30 day notices of determination, the expiration date is 30 days from the issue date.

  3. On 90 day notices, the expiration date is 90 days from the issue date.

  4. On 150 day notices, the expiration date is 150 days from the issue date. The expiration date for an FPAA or FSAA is 150 days from the issue date.

  5. On 180 day abatement of interest determinations, the expiration date is 180 days from the issue date.

CLOSINGCD (Closing Code)

  1. The closing code entered represents the type of closing such as agreed, defaulted, premature referral, etc...

  2. Closing codes are also entered for other reasons, including:

    1. transfer to another Appeals office (closing code 30)

    2. premature referrals (closing code 20)

    3. reassignment to another ATE (closing code 40)

    4. change in jurisdiction from Appeals to Counsel and from Counsel to Appeals (closing code 43 or 42 respectively). Refer to IRM 8.20.6.18 and 8.20.6.24.3, IRM 8.20.6.31.7 for additional information on change in jurisdiction between Appeals and Counsel.

    5. removal from inventory (closing code 99)

  3. A complete list of closing codes can be found in Exhibit 8.20.7-1 in IRM 8.20.7 and also on the ACDS Utilities Menu.

DATECLSD (Date Closed)

  1. This item represents the date a case was closed and is manually entered on ACDS by the APS TE.

TOTHRS (Total Hours)

  1. This field is updated via the ATE case activity record (CARATS).

  2. It represents the total direct hours expended on the WUNO.

ACKLTR (Acknowledgement Letter)

  1. This represents the date the acknowledgement or substitute acknowledgment letter is generated.

  2. The entry is systemically entered at the time the letter is generated by the ATE, ATM, or ATM Secretary.

ACAPDATE (ATM Approval Date)

  1. Date the case is approved for closing (after any required outside review or concurrence has been obtained) on the Form 5402, by the ATM or other designated official. The ACAPDATE is entered by the ATM.

  2. The date entered must be on or after the ASGNDATE and will be entered by the ATM.

    Note:

    The above rule also applies for cases going to Counsel for Trial Preparation, Closing Code 43. If a Trial Preparation case is returned for reconsideration, the ACAPDATE will NOT be changed.

AIMSCLSD (Date Closed on AIMS)

  1. This date reflects the date all returns in the WUNO are in status 90 on AIMS.

  2. This date is systemically entered when all returns in a WUNO are closed on AIMS.

NOTE (Notes)

  1. For local use. Enter notations as appropriate. The field allows for the input of up to 250 characters (letters or numbers).

OfrNum (Offer Number)

  1. Represents the Offer Number for an OIC case.

  2. Entered manually or automatically when the case is created from the AOIC cases in the eCase holding tank.

WUpropsdOfrAmt (Workunit Proposed Offer Amount)

  1. Amount is automatically entered when the case was created from the AOIC cases in eCase holding tank.

  2. Manual entry if the case is not in eCase.

WUaccptOfrAmt (WUNO Accepted Offer Amount)

  1. Accepted offer amount entered at the time the case is closed.

ACTION (Action Taken on a Case)

  1. Action codes represent the actions taken on a case as it moves through Appeals.

  2. A new docketed case sent to Counsel to answer the petition should have an action of ANSWER.

    Note:

    If the current ACTION code is shown as DECENT or ORDENT, it should ONLY be overwritten or updated with ACTION Code ACKCLS (Acknowledged Closure).

  3. Action codes ACKCLS and SHIPPED open a separate box which is populated with the Post of Duty (POD) information.

    • ACKCLS POD information represents the location of the employee closing the case.

    • SHIPPED POD information represents the location the case is being sent to within the Appeals organization.

  4. See Exhibit 8.20.3-4 for a list of action codes.

TODATE (Date ACTION Began)

  1. This field represents the date when an action on the case began, meaning the date the case was sent TO another Appeals office, Counsel, etc.

  2. Required entry when the ACTION field is entered.

FROMDATE (Date ACTION Ended)

  1. Enter the date a specific action on the case ended.

  2. This field is a manual entry and made by the sending office (APS TE) when acknowledgement of the case is received.

  3. Exceptions:

    1. The FROMDATE on a transferred case (ACTION = TRXXX) is automatically entered when the case is accepted by the receiving office from the INBOX.

    2. For cases with ACTION Code ANSWER, the FROMDATE is automatically populated when assigned to the ATE.

LACTION (Local Action)

  1. Action taken on a case - same as ACTION field but is reserved for local definition.

LTODATE (Local TO DATE)

  1. The date the Local Action began.

LFROMDATE (Local FROM DATE)

  1. The date the Local Action ended.

CORWUGR (Corrected WUNO Grade)

  1. The WUNO grade is manually entered by the ATM when the case is assigned.

TFRCorp (Trust Fund Recovery Corporation Name)

  1. Name of the Trust Fund Corporation related to the taxpayer on TFRP cases.

TFRTin (Trust Fund Recovery TIN)

  1. The TIN of the TFRP case where the tax or penalty at issue has been generated.

FOIANum (Freedom of Information Act Number)

  1. If ACDS Type Code "FOIA" is selected, the FOIA Number for the case will be a required entry on ACDS. If Type Code "FOIA" is not selected, the FOIA field cannot be entered on ACDS. For more information refer to IRM 8.7.14.6.1.

Date DKTAD Skeletal

  1. The DIMS Team must enter the Date DKTAD Skeletal record created. Do not edit this field or remove this field at any time.

Date DKTAD Dummy

  1. The DIMS Team will enter this date if applicable when the dummy file is created. Do not edit this field or remove this field at any time.

Date DKTAD Original

  1. Any APS Tax Examiner who receives an original docketed administrative file must enter the date this file is received.

CIRCTRIDE (Circuit Ride)

  1. If the case will be handled at a circuit riding location, enter the appropriate locally designated city code.

STATUS (Status of WUNO)

  1. This item is updated by the ATE from the AO function CARATS in ACDS to reflect the current status of the WUNO in their inventory.

  2. The following status codes are computer generated based on the entry of an action code on the case in ACDS:

    • E/DD - Inactive, waiting action/info by Compliance

    • E/STP - Inactive, to Counsel for stipulation filing

    • E/T - Inactive, to Counsel for trial preparation

    • E/TSN - Inactive, waiting TP action on SND

  3. See the ACDS Utilities Menu for a list of current status codes.

DESICONF ( Desired Conference Date)

  1. This field is updated by the ATE from their CARATS activity record.

AQMSSELECT

  1. Indicator automatically set when the case is selected for AQMS review based on programmed criteria.

LOC1 through LOC11

  1. LOC1 - Local use field

  2. LOC2 - Local use field

  3. LOC3 - Local use field

  4. LOC4 - Tracks transfer information. Systemic updates occur to insert the AOC of the transferring office.

  5. LOC5 - Local use field

  6. LOC6 - Local use field

  7. LOC7 - defined by headquarters to track CDP issues

  8. LOC8 - Q W-4 PROJECT - defined by headquarters to identify Questionable W-4 Project determination cases

  9. LOC9 - Local use field

  10. LOC10 - defined by headquarters to track Breakthrough Initiative cases

  11. LOC11 - Local use field in MM/DD/YYYY format

Specific Item Instructions - RETURNS Screen

  1. Information and definitions for fields on the RETURNS level information screen.

AIMS
  1. Enter the correct AIMS indicator code for all cases as follows:

    1. Y = Yes, return should be controlled on AIMS and is on AIMS at the time of receipt. An AMDISA print should be included in the administrative file.

    2. N = No, return should be controlled on AIMS but is not on AIMS at the time of receipt. IDRS Command Code AM424A is used by Appeals to establish the AIMS control.

    3. E = Exempt, return should NOT be controlled on AIMS and no AIMS controls were established at the time of receipt. There are no AIMS controls for CDP, OIC, penalty appeals, trust fund recovery penalty cases, abatement of interest claims, campus disallowed claims, etc.

    Note:

    The AMATCH validation program is keyed to these codes. It is very important to use them correctly to avoid having cases on the IVL lists needlessly, meaning if the match program reads "E" , the AIMS listing will not be searched. See IRM 8.10.1.10 for additional information regarding the AMATCH reports.

Tax Period/Tax Period Modifiers
  1. Item includes all tax periods (years) associated with the case.

  2. The format is YYYYMM.

  3. The information can be obtained from documents in the administrative file including the tax returns, revenue agent's report, etc.

  4. For Estate Tax cases, Form 706, use the date of death as the tax period.

  5. Tax period modifiers - No tax period modifier is entered if the original return is in the file. The following is entered when the original return is not included in the administrative file:

    • N - no original return

      Note:

      For electronically filed returns such as IDRS command code TRPRT, if the Document Locator Number (DLN) appears in the upper right hand corner, then the TRPRT is considered to be the original tax return. Refer to Document 6209, Chapter 12 for additional information regarding TRPRT prints.

  6. The following definers are entered as a separate return line to control the statute when it is different from the rest of the return.

    • 199912F - Federal Insurance Contributions Act (FICA) tip tax

    • 199912P - prepayments credits

  7. When an ATE inputs a change to the statute-critical data fields of tax period, statute date, or statute code, the entry will trigger the Statute Validation System (SVS). When the original return is received on a case with a tax period modifier, the tax period must be updated in the SVS via the AIVP Validation Menu (which is accessible from the CAR or the Case Summary Card). All changes in SVS for the tax period critical data field is considered a Normal Update (N). Once the validation is submitted, ACDS will be updated and an automatic entry of VA (Validation Accepted) will be made in the CAR.

  8. If the APS Tax Examiner is requested to remove a tax period from ACDS because it is not part of the case, the APS Tax Examiner MUST CONSIDER THE STATUTE IMPLICATIONS AND UPDATE ALL APPLICABLE DATABASE SUCH AS IDRS, AIMS, AOIC, etc.

Statute Date
  1. Next to each tax period, enter the expiration date of the statutory period for assessment. if there is an open statute (live or non-assessed), the date must be entered.

  2. When an ATE inputs a change to the statute-critical data fields of tax period, statute date, or statute code, the entry will trigger the Statute Validation System (SVS). All changes must be designated as either a Normal Update (N) or an Error Correction (E). Once the validation is submitted, ACDS will be updated and an automatic entry of VA (Validation Accepted) will be made in the CAR.

  3. If the case involves a FICA tax adjustment, the FICA tax may carry a different statute date. Two statute dates can be entered for the same tax period by using a tax period modifier for FICA tax, as follows:

    • 201312

    • 201312F

  4. For non-petitioning spouse cases, also see IRM 8.20.5.30.5.

  5. If the notice of deficiency is rescinded under Rev. Proc. 98-54, the statute date must be recomputed. Generally the statute date that existed prior to the issuance of the notice is reinstated. The recomputed statute date will be provided by the ATE. See also IRM 8.2.2.14.

  6. The statute date field is also used to track the CSED (Collection Statute Expiration Date) for Collection cases (CDP, OIC and TFRP). The statute date field is only entered for late CDP cases with Feature Code EH or retained jurisdiction CDP cases with Feature Code RJ. See IRM 8.20.5.13, post-assessment TFRP claim cases. See IRM 8.20.5.39.2.3. The statute date field will be blank for non-CDP OICs. See IRM 8.20.5.30. The statute date field will be completed for CDP OIC cases. See IRM 8.20.5.13.1.5.1 but the date is two years from the REQAPPL date for the offer, not the CSED.

Statute Code
  1. Enter the appropriate code to denote the special period of limitations. Remember, if there is a valid statute code, it must be entered. See IRM 8.21.2-2 for a complete listing of all valid statute codes.

  2. When an ATE inputs a change to the statute-critical data fields of tax period, statute date, or statute code, the entry will trigger the Statute Validation System (SVS). All changes must be designated as either a Normal Update (N) or an Error Correction (E). Once the validation is submitted, ACDS will be updated and an automatic entry of VA (Validation Accepted) will be made in the CAR.

  3. Follow the rules below to determine the code:

    1. If the period of limitations is extended by special consent Form 872–A , Special Consent to Extend the Time to Assess Tax, enter 872–A.

    2. In bankruptcy cases, enter BKRUP, however, the actual statute date must also remain in the "statute date" field.

    3. If the statutory period for assessment has expired and the year is open only by reason of the filing of a claim, enter the word CLAIM.

    4. If the statutory period for assessment has expired and the return is open only because of the assertion of a fraud penalty, enter the FRAUD. If the statutory period for assessment has not expired in a year for which there is an assertion of a fraud penalty, the open statute date must also be entered.

    5. If the return being established is docketed before the tax court, enter DOCKT.

    6. If there is an omission from gross income which is in excess of 25% of the gross income stated on the return, enter 6501E. If there is a valid open statute date, it must also be entered. If the statute date has expired and the case is being held open only by the 6501E issue, then the six year statute date should be entered.

    7. If the statute is only open because of a carryback enter CBYYYYMM (YYYY MM represents the year and month creating the carryback). The following chart will help identify the proper entry for multiple scenarios where a carryback is involved:

      • How to control the statute where there is an open ASED for the Net Operating Loss (NOL) year(s) which carries back to years where the statute is only open resulting from the CB:

        Tax Period Statute Date Statute Code Comments
        201012 CBYYYYMM = CB201212
        • Open only on a carryback

        • The YYYYMM identifies the year with the open statute

        • No statute date will be entered

        200912 CB201212
        • Open only on a carryback

        201212 04/15/2016
        • No code would be entered as this is the NOL year where the CB comes from

      • How to control the statute when the CB years have open ASEDs but are also covered by the NOL:

        Tax Period Statute Date Statute Code Comments
        201012 12/31/2013
        • Statute date is entered because there is a valid 872 in the file for this year

        • Even though this year is covered by the CB only the open ASED is entered on ACDS

        201112 04/15/2015 Even though this year is covered by the CB only the open ASED is entered on ACDS
        201212 4/15/2016
        • No code would be entered as this is the NOL year where the CB comes from

      • How to control statute when the NOL year is open on an 872A:

        Tax Period Statute Date Statute Code Comments
        200712 CB200912
        • Open only on a carryback

        • No statute date will be entered

        • Entering the date could lead one to believe the ASED is open for the entire case as shown in the example above

        200812 CB200912 Same as example above for 200712
        200912 872-A
        • 872-A code entered on the NOL year as that is what is keeping the case year open

    8. To ensure that a control is maintained on reference returns with the same name as the case being established, enter RFRTN in the statute code field. If there is a valid open statute date, it must also be entered in the statute date field. For reference returns with a name different from the case being established, a separate case summary card must be generated, and linked to the key case.

    9. On occasion, AIMS will reflect alpha statute codes (AA-ZZ) in the day field of the statute date, to identify a special reason for keeping the statute open. See Document 6209, Section 12 for a complete listing of AIMS alpha statute codes.

    10. See Exhibit 8.21.2-1 for a complete list of ACDS statute codes.

BodCd (Business Operating Division Code)
  1. The Business Operating Division Code (BodCd) is comprised of three specific fields that are each input separately. Those fields are:

    • PRIBUSCD (Primary Business Code) - 3 digits

    • SECBUSCD (Secondary Business Code) - 5 digits

    • EMPGRCD (Employee Group Type Code) - 4 digits

  2. The three fields combined are also referred to as the AIMS Assignee Code for AIMS cases. The AIMS Assignee Code can be found on the AMDISA.

  3. For AIMS cases input the 12 digit AIMS Assignee Code of the originating office in each of the specific fields.

  4. For non-AIMS cases, determine and input the PRIBUSCD of the originating office only.

  5. Currently, the BODCD and SOURCE fields will be input to identify the source of our work.

PRIBUSCD (Primary Business Code)
  1. A three digit code to identify the source of the return. This code should remain constant throughout the appeal process. This is a required field. For AIMS cases, input the PBC of the originating office as shown on the AMDISA in the closing PBC field. For non-AIMS cases, the listings below are provided to assist you in determining the PRIBUSCD.

  2. Digit 1 is the AIMS BOD Code. The following is a list of valid codes to identify the source of work:

    • 1 - Wage and Investment

    • 2 - Small Business/Self Employed

    • 3 - Large Business and International

    • 4 - Tax Exempt/Government

  3. Digits 2 and 3 are referred to as the "Industry-Area-Type-Code" .

    1. SB/SE and W & I identifies "Area"

    2. LB & I identifies "Industry"

    3. TE/GE identifies "Area" or "Type" of case.

  4. The Compliance Collection Campuses and their PBCs are:

    • Andover 190

    • Atlanta 191

    • Austin 192

    • Fresno 193

    • Kansas City 194

    • Brookhaven 295

    • Cincinnati 296

    • Memphis 297

    • Ogden 298

    • Philadelphia 299

  5. The Compliance ACS "Remote" or Field sites and associated campuses are:

    • Buffalo (Andover 190)

    • Denver (Ogden 298)

    • Des Moines (Memphis 297)

    • Detroit (Cincinnati 296)

    • Jacksonville (Atlanta 191)

    • Nashville (Memphis 297)

    • Oakland (Ogden 298)

    • Puerto Rico (Austin 192)

    • Seattle (Fresno 193)

  6. For Bank Secrecy Act cases (IRC 6721 penalties for Form 8300 violations), the PBC is 217.

  7. Refer to Document 6209, IRS Processing Codes and Information for additional information regarding PBCs.

SECBUSCD (Secondary Business Code)
  1. A five digit code to further identify the source of the return. Input the SBC of the originating office as shown on the AMDISA. The SBC will not be updated from the prior code when a return is closed to Appeals. This field is not required for non-AIMS cases. See Document 6209 for additional information.

EMPGRCD (Employee Group Code)
  1. A four digit code to further identify the source of the return. Input the EGC of the originating office as shown on the AMDISA. The EGC will not be updated from the prior code when a return is closed to Appeals. This field is not required for non-AIMS cases. See Document 6209 for additional information.

SND (Statutory Notice of Deficiency)
  1. Enter Y if the SND was issued and the tax period was included.

  2. Enter N if the SND was not issued or the tax period was not included.

PAYCODE (Payment Code)
  1. This item is used to record whether a payment was received by Appeals for the tax period being closed and the type of payment. This item is optional based on the APS Lean Six Sigma recommendations during Fiscal Year 13.

PropdTax (PROPOSED$ TAX DEF/-OA)
  1. Enter the proposed deficiency or overassessment (rounded to whole dollars) for each tax period established.

  2. The amount should reflect the NET amount of tax and credits including withholding, earned income, etc. and should generally agree with Line 6, Page 2, of the AMDISA print ("Unagreed Amount Appealed/Petition" ).

  3. In those instances where the AMDISA amount reflects only $1, refer to the RAR to determine the correct amount.

  4. Claim amounts are not included in this item and are discussed below in IRM 8.20.3.3.62.12, Claims.

  5. Where a partial agreement (assessment) has been secured by Compliance, only the net proposed deficiency should be entered. The case file should contain two Examination reports (Form 4549) - one for the AGREED issues and one for AGREED AND UNAGREED issues (referred to as UNAGREED below).

  6. On cases where the special tax period modifiers are entered separately to control a different statute, follow procedures in (1) above. Do- not enter dollar amounts on the separate line.

PropdPen (PROPOSED$ PENALTY DEF/-OA)
  1. The proposed penalty(s) for each tax period established.

  2. The information can be obtained from various documents in the administrative file including the RAR, etc... (round all amounts to the nearest whole dollar).

RevsdTax (REVISED$ TAX DEF/-OA)
  1. Generally, this item is completed at closing.

  2. Appeals revised determination of tax liability, rounded to whole dollars, including any Appeals partial assessments.

  3. Amount can be taken from the Form 5402, audit statement, SND, etc.

  4. Penalty amounts are excluded.

  5. There are two special situations that determine the amount entered in revised dollars. They are as follows:

    1. If the case is settled by Counsel, or it is tried, enter the total amount of NET tax and credits shown on the Tax Court Decision.

    2. If the case is dismissed, enter the total amount of NET tax and credits shown on the statutory notice of deficiency.

RevsdPen (REVISED$ PENALTY DEF/-OA)
  1. Generally, this item is completed at closing.

  2. Enter Appeals results only and round all amounts to the nearest whole dollar.

CLAIMS
  1. The following claim fields reflect amounts for Revenue Base Protection (RBP).

  2. RBP applies only if tax has been assessed and paid.

  3. All other claim amounts are reflected in proposed tax and penalty fields.

DDAMTCL (Amount of the claim received by the former District Director now referred to as Compliance Examination that was disallowed)
  1. Enter the amount of the claim considered by Compliance Examination and subsequently disallowed. This amount can be verified on page 2 of the AMDISA.

DD AMTDIS (Amount of the claim received by the former District Director now referred to as Compliance Examination that Appeals disallowed)
  1. Entered at closing, this is the amount of DDAMTCL disallowed by Appeals.

APPEALS AMTCLM (Amount of the claim received while the return was in Appeals' jurisdiction)
  1. The amount of the claim received directly from the Campus or filed while the return was in Appeals' jurisdiction.

APPEALS AMTDIS (Amount of the claim received in Appeals that was disallowed)
  1. Entered at closing, this is the amount of APPEALS AMTCLM disallowed.

RETURN DUPLICATION
  1. Duplication involves more than one taxpayer for the same income or deduction adjustment if it is certain that the adjustment is proper for at least one taxpayer. The deficiency attributable to the non-key should be shown as a duplication such as whipsaw, alimony, etc.

  2. Partial assessment dollars secured by Compliance will not be shown as duplication.

  3. When adding new returns to either a new or existing case, the input for duplicate dollars is duplication for that return (NOT FOR THE ENTIRE CASE). When updating a return, the duplicate dollars shown are for the entire case.

Total DD CLAIM (Total amount of the DDAMTCL fields)

  1. This field is computer generated. It represents the total amount of dollars input in the DDAMTCL fields. No manual input is required. This field is printed on the case summary card or visible on the search screen.

Total APP CLAIM (Total amount of the Appeals AMTCLM fields)

  1. This field is computer generated. It represents the total amount of dollars input in the Appeals AMTCLM fields. No manual input is required. This field is printed on the case summary card or visible on the search screen.

Total Case Deficiency (TOTPRODEF)

  1. This field is computer generated. No manual input is required. This field is only printed on the case summary card.

Total Case Overassessment including Penalty (TOTPROASS)

  1. This field is computer generated. This field is printed on the case summary card or visible on the search screen.

TOTAL WORK UNIT (WUDOLRS)

  1. Total dollars for all cases in the WUNO.

  2. This field is computer generated.

  3. This field is printed on the case summary card or visible on the search screen.

CASE SUMMARY CARD

  1. After the CASES and RETURNS level information has been input on the screens, the computer will display a prompt to ask if you want to print a case summary card.

  2. The case summary card displays all information for the case just established. The system will compute the total work unit dollars.

  3. The case summary card will be used by the ATE to identify and control cases in his/her inventory.

ACDS TYPE Codes

Code Description Source Document
ABINT Abatement of Interest Claim Form 843
CAPIA Collection Appeals Program Installment Agreement Form 4442, Form 9423
CAPLN Collection Appeals Program Lien Form 9423
CAPLV Collection Appeals Program Levy Form 9423
CAPSZ Collection Appeals Program Seizure Form 9423
CDPTD CDP Timeliness Determination Form 14461 and Form 12153-B
DOP Director of Practice Case
DPL2 Collection Due Process Lien & Levy case Form 14461 and Form 12153-B
DPLN Collection Due Process Lien Form 14461 and Form 12153-B
DPLV Collection Due Process Levy Form 14461 and Form 12153-B
EMPL Employment Tax Case Form 941, Form 940
EOD Exempt Organization Determination Case Form 1023, Form 1024, Form 1028 (EO)
EOE Exempt Organization Examination Case Form 990, Form 990BL, Form 990C, Form 990T
EOR Exempt Organization Revocation Case Final Adverse Determination Letter
EPD Employee Plan Determination Case Form 5300, Form 5301, Form 5303, Form 5307, Form 5310, Form 6406EP
EPE Employee Plan Examination Case Form 5500, Form 5500C, Form 5500R (EP)
EPR Employee Plan Revocation Case Final Adverse Determination Letter
ES Estate Tax Case Form 706
EX Excise Tax Case Form 720
FBAR Foreign Bank Account Reporting
FOIA Freedom of Information Act Case Form 3210
G Gift Tax Case Form 709
I Income Tax Case Form 1040 or Form 1120
OIC Offer in Compromise Form 656
OTHPEN Other IRC Penalty Code Sections not Identified Form 8278
PENAP Penalty Appeal Case Form 5880, Form 8278, etc.
REF Reference Return Form 941, Form 1065 (except TEFRA), etc.
TEFRA TEFRA Key Case Form 3198
TEFRAI TEFRA Investor Only Case Form 3198
TEFRAP TEFRA Penalty Only Case Form 3198
TFRP Trust Fund Recovery Penalty Case Form 2751
USBANK Bankruptcy Appeals Process (Test Program)
WPT Windfall Profits Tax Case Form 6407, Form 6248, Form 6249, etc.
6161 Extension of Time for Prepayment of Estate Tax
6166 Extension of Time for Payment of Estate Tax Form 706 & various Counsel documents
6676 Erroneous Claim for Refund or Credit Penalty Case Form 8278
6694A Tax Preparer Conduct Penalty ($250) Form 8278, Form 3198
6694B Tax Preparer Conduct Penalty ($1000) Form 8278, Form 3198
6695 Tax Preparer Penalty Form 8278, Form 3198
6695A IRC 6695A Appraiser's Penalty Cases
6700 Abusive Tax Shelter Penalty Form 8278, Form 3198
6701 Understatement of Tax Liability Form 8278, Form 3198
6702 Frivolous Income Tax Return Form 8278, Form 3198
6703 IRC Section 6703 Form 3198
6704 Failure to Keep Records Form 3198
6705 Failure of Broker to Provide Notice to Payor Form 8278
6706 Original Issue Discount Information Form 3198
6707 Failure to Furnish Tax Shelter Information Form 8278
6707A Failure to Include Reportable Transaction with Return Form 3198
6708 Failure to Maintain List of Investors in Abusive Tax Shelter Form 8278
6709 Penalties with Respect to Mortgage Credit Certificates Form 3198
6715 Dyed Diesel Fuel Form 3210
6721 IRC 6721 Bank Secrecy Case Form 8278, Form 3645, Form 3198
7430 Administrative Costs Form 3198

Historical District Office (DO) and Service Center (SC) Codes

Code Description
04 New England
06 Connecticut-Rhode Island
07 Atlanta Service Center (ATSC)
08 Andover Service Center (ANSC)
09 Kansas City Service Center (KCSC)
11 Brooklyn, NY
13 Manhattan, NY
16 Upstate NY
17 Cincinnati Service Center (CSC)
18 Austin Service Center (AUSC)
19 Brookhaven Service Center (BSC)
22 New Jersey
23 Pennsylvania
28 Philadelphia Service Center (PSC)
29 Ogden Service Center (OSC)
31 Ohio
33 Southern California
35 Indiana
36 Illinois
38 Michigan
39 Midwest
41 North Central
43 Kansas-Missouri
49 Memphis Service Center (MSC)
52 Delaware-Maryland
54 Virginia-WestVirginia
56 North-South Carolina
58 Georgia
59 North Florida
62 Kentucky-Tennessee
65 South Florida
66 Puerto Rico
72 Gulf Coast
73 Arkansas-Oklahoma
74 South Texas
75 North Texas
76 Houston
77 Central California
84 Rocky Mountain
86 Southwest
89 Fresno Service Center (FSC)
90 Detroit Computing Center (DCC)
91 Pacific Northwest
94 Northern California
95 Los Angeles, CA
98 A/C International

Counsel Office Codes

Office Name Office Code Office Name Office Code
Anchorage ANC Los Angeles LA
Atlanta ATL Louisville LOU
Austin AUS Manhattan MAN
Baltimore BAL Miami MIA
Birmingham BIR Milwaukee MIL
Boston BOS Nashville NAS
Brooklyn BRO New Orleans NO
Buffalo BUF Newark NEW
Chicago CHI Oklahoma City OKL
Cincinnati CIN Omaha OMA
Cleveland CLE Philadelphia PHI
Dallas DAL Phoenix PNX
Denver DEN Pittsburgh PIT
Detroit DET Portland POR
Fort Lauderdale FTL Richmond RCH
Greensboro GBO Sacramento SAC
Hartford HAR Salt Lake City SLC
Honolulu HON San Diego SD
Houston HOU San Francisco SF
Indianapolis IND San Jose SJ
Jacksonville JAX Seattle SEA
Kansas City KCY St Louis STL
Laguna Niguel LN St Paul STP
Las Vegas LV Thousand Oaks THO
Washington WAS

ACDS ACTION Codes

Code Description To Date From Date
ACKCLS Closing of case Date sent to APS, etc. Date Form 3210 was acknowledged
ANSWER Unassigned case sent to Counsel to answer petition Date sent to Counsel Date returned from Counsel
APPEALED Tax Court Decision that has been appealed Date of Appeal Date Court of Appeals Decision is received
COURT Case Tried in Tax Court Date case was tried Leave blank
DCJUR Case transferred to Counsel Jurisdiction Date sent to Counsel Leave blank
DCOTHER Case sent to Counsel for review suspense Date sent to Counsel Date return from Counsel
DDJRET Case sent to Compliance (Appeals retains jurisdiction) Date case was sent Date case was returned
DECENT Decision entered by Tax Court Date of Decision Leave blank
DKTLSTXXX Docket list/number Date of docket list Leave blank
FILERCVD Administrative file received- awaiting petition Date admin file received Leave blank
INTERIM Interim assessment or abatement requested Date sent to APS Date verification of assessment/abatement
ORDENT Order of dismissal by Tax Court Date order entered Leave blank
PETNRCVD Petition received-awaiting administrative file Date petition received Leave blank
PREPSTIP Stipulation sent to Counsel for preparation Date sent to Counsel Leave blank
REJECT Case reject from APS Date corrected case returned to APS Date of acknowledgement
SNDC Statutory Notice of Deficiency sent to Counsel for concurrence Date case sent to Counsel Date case returned to Appeals
SHIPPED Ship cases between offices/PODs in the same Area Date case was sent Date case received in new location
STIPFF Filing of stipulations by Counsel Date case sent to Counsel Leave blank
TRXXX Case transferred from one Area to another Area Date case transferred Leave blank