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

8.20.3.1  (10-15-2014)
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.

8.20.3.2  (10-15-2014)
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.

8.20.3.3  (10-15-2014)
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.

8.20.3.3.1  (10-15-2014)
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.

8.20.3.3.2  (10-15-2014)
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.

8.20.3.3.3  (10-15-2014)
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.

8.20.3.3.4  (10-15-2014)
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.

8.20.3.3.5  (10-15-2014)
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)

8.20.3.3.6  (10-15-2014)
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.

8.20.3.3.7  (10-15-2014)
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

8.20.3.3.8  (10-15-2014)
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.

8.20.3.3.9  (10-15-2014)
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.

8.20.3.3.10  (10-15-2014)
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.

8.20.3.3.11  (10-15-2014)
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).

8.20.3.3.12  (10-15-2014)
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.

8.20.3.3.13  (10-15-2014)
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.

8.20.3.3.14  (10-15-2014)
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.

8.20.3.3.15  (10-15-2014)
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.

8.20.3.3.16  (10-15-2014)
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.

8.20.3.3.17  (10-15-2014)
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.

8.20.3.3.18  (10-15-2014)
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.

8.20.3.3.19  (10-15-2014)
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.

8.20.3.3.20  (10-15-2014)
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.

8.20.3.3.21  (10-15-2014)
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).

8.20.3.3.22  (10-15-2014)
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.

8.20.3.3.23  (10-15-2014)
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.

8.20.3.3.24  (10-15-2014)
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.

8.20.3.3.25  (10-15-2014)
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.

8.20.3.3.26  (10-15-2014)
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.

8.20.3.3.27  (10-15-2014)
Repname2 (Second Representative's Name)

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

8.20.3.3.28  (10-15-2014)
Repname3 (Third Representative's Name)

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

8.20.3.3.29  (10-15-2014)
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.

8.20.3.3.30  (10-15-2014)
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.

8.20.3.3.31  (10-15-2014)
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.

8.20.3.3.32  (10-15-2014)
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.

8.20.3.3.33  (10-15-2014)
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.

8.20.3.3.34  (10-15-2014)
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.

8.20.3.3.35  (10-15-2014)
DATECLSD (Date Closed)

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

8.20.3.3.36  (10-15-2014)
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.

8.20.3.3.37  (10-15-2014)
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.

8.20.3.3.38  (10-15-2014)
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.

8.20.3.3.39  (10-15-2014)
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.

8.20.3.3.40  (12-27-2011)
NOTE (Notes)

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

8.20.3.3.41  (10-15-2014)
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.

8.20.3.3.42  (10-15-2014)
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.


More Internal Revenue Manual