Effect on Other Documents

Audience

This IRM is intended for use by the Ogden Campus Exempt Organization Entity and Unpostable personnel.

Effective Date

(01-01-2015)

Maria Hooke,Director, BusinessSystems PlanningSE:T:BSP

3.12.278.1
(01-01-2015)Overview

This IRM section provides instructions for the correction of Exempt Organization (EO) unpostables. These cases may be resolved
in either the Entity function or the Unpostable function.

These procedures were formerly contained in both IRM 3.12.179, IMF/BMF/IRAF/CAWR Unpostable Resolution and IRM 3.13.222, Entity Control unpostables for IMF and BMF.

This IRM contains instructions for the Unpostable functions as they pertain to Exempt Organizations. Some unpostable codes
contain both EO and non-EO conditions. This IRM only covers EO and EO-related unpostable conditions and resolutions.

Local management may decide to allow either function to correct these unpostable cases.

Whenever an unpostable case is transferred between functions, it is imperative all research be notated and attached. This
allows the receiving function to determine what actions to take.

This IRM includes information and instructions to resolve EO unpostable cases and can not cover all situations, so judgment
may be needed to work the case. Contact your Manager or Lead tax examiner to determine if your decision is valid. You should
request an IRM change to add instructions if you encounter repeated problems or issues which are not currently in the IRM.

The following IRMs are used in conjunction with this section:

IRM 3.12.32., General Unpostable Framework (GUF);

IRM 2.3, IDRS Terminal Responses;

IRM 2.4, IDRS Terminal Input;

IRM 3.13.12, Exempt Organization Account Numbers;

IRM 3.13.2, BMF Account Numbers;

IRM 3.13.222, BMF Entity Unpostable Correction Procedures;

IRM 3.12.279, BMF/CAWR/PMF Unpostable Resolution;

IRM 3.0.273, Administrative Guide;

IRM 3.11.12, Exempt Organization Returns;

IRM 3.12.12, Exempt Organization Returns;

IRM 3.17.179, Accounting Refund Transactions;

IRM 21.4.4, Refund Inquiries;

3.12.278.1.1
(01-01-2015)CADE 2

The Customer Account Data Engine (CADE) 2 Program Office in Headquarters is charged with the primary goal to implement a single,
modernized programming solution which provides daily processing of taxpayer accounts.

Note:

The CADE Master File, as it existed from 2004 – 2011, will transition from Production and be retired at the end of 201152.

The CADE 2 solution is comprised of several components, to modernize the IRS to a daily processing environment with several
Transition States.

With CADE 2 there will be changes to campus cycles which will begin with cycle 201201. The new BMF, EO and EPMF campus cycles are:

Transactions will be viewable using CFOL command codes on Saturday following the weekly Master File processing run on Thursday.

Transactions will be viewable as posted transactions using IDRS command codes on Monday following the weekly Master File processing
run on Thursday.

Note:

With the acceleration of the IDRS weekly analysis being performed the weekend directly after the Master File processing on
Thursday, transactions will be posted instead of in pending status on Monday.

Cycle posting dates will reflect a format of YYYYCCDD. YYYY will indicate the year. CC will indicate the posting cycle. For
IMF transactions, the following values for DD are defined:

01 = Friday

02 = Monday

03 = Tuesday

04 = Wednesday

05 = Thursday

Note:

BMF, EO and EPMF cycle posting dates on BMFOL will continue to reflect YYYYCC. YYYY will indicate the year. CC will indicate
the posting cycle. BMF cycle posting dates in TXMOD will reflect a format of YYYYCCDD. The DD value will be 08.

3.12.278.1.2
(01-01-2015)Glossary of Terms

Account - One taxpayer identified by a Social Security Number (SSN) or Employer Identification Number (EIN). Each account is a record
of the type of returns filed and the related tax periods.

Accounts Maintenance Transcripts - A transcript generated when an unresolved credit or condition is identified on the Master File.

Amended Return - A second return filed which changes the information submitted on the original return.

Asset Code - The code used to identify end of year total assets.

Automated Collection System (ACS) - An automatic calling system for tax periods within an account which is in taxpayer delinquent investigation (TDI) or taxpayer
delinquent account (TDA) status.

Automatic Data Processing (ADP) - The handling and processing of data from electronic machines with a minimum of human intervention.

Batch - A group of work of like documents within a program code.

Block - Returns or documents grouped together for filing purposes; the ninth, and digits of the DLN indicate the blocking series where
the return is filed. The eleventh digit of the DLN is the blocking series for examination purposes. It identifies whether
the return was an original return, copy of the return, BRTVU/RTVUE print or no return and whether it was a survey or examined
case file.

Blocking Series - The blocking series is a three digit numeric field associated to the document or returns for posting to Master File.

Business Operating Divisions (BOD) - Effective 01/01/2000, all IMF and BMF taxpayers will be systemically assigned to a BOD code based on the characteristics
of the tax return. IMF taxpayers will either be assigned to the SE (Small Business/Self-employed) BOD or to the WI (Wage and
Investment) BOD. BMF taxpayers will be assigned to the LB & I (Large Business & International) BOD, to the TE (Tax Exempt)
BOD or to the SE BOD.

Calendar Year - The twelve month period from January 1 through December 31.

Centralized Authorization File (CAF) - A file which contains information regarding the type of authorization taxpayers have given representatives for the various
modules within their accounts.

Check Digit - Consisting of two alphabetic characters, the check digit is determined by the application of a mathematical formula to the
SSN or EIN.

Command Code (CC) - A five character code used to input data and requests on IDRS.

Computer Paragraph (CP) - Computer generated notices used to request information from or give information to an organization regarding certain aspects
of their tax return. Also, certain notices are generated to inform the campus of posting to the Master File which require
additional action.

Consolidate - The moving of data when one organization has erroneously been given more than one TIN.

Credit Balance - A term noting a credit outstanding on a tax module. It is identified by a minus sign (−) after the amount.

Cycle - One week's processing at the campuses, the Martinsburg Computing Center (MCC), and Tennessee Computing Center (TCC). The cycle
is expressed as a six (6) digit code: the first four digits represent the processing year and the last two digits represent
the processing week within the year.

Document Code (DOC CODE) - A two digit code which identifies the specific type of return or document which was filed or processed; it is the fourth and
fifth digits of the DLN.

Document Locator Number (DLN) - A control number assigned to every return, document or transaction input through the ADP system. The fourteenth (last) digit
is the year of processing and is assigned by the campus computer program at the time of original input. The DLN is used to
control, identify and locate documents and transactions processed in the ADP system.

Dummy Return - An input return not prepared by the organization or an input document treated as a return.

Employee Number - A ten digit number assigned to each employee authorized to access IDRS.

Employer Identification Number (EIN) - An assigned nine digit number used to identify a business tax account.

Entity - The portion of the Master File record which identifies the organization. It contains the name, address, social security or
employer identification number, employment code if applicable, name control, location codes, filing requirement codes, fiscal
period and date of establishment.

Excess Collections - An account of unapplied credits transferred from an unidentified or Master File account.

Federal Tax Deposit System (FTD) - Payments received by the Internal Revenue Service from a Federal Reserve Bank, indicating deposits made by an organization.

Note:

As of January 2011, FTDs are no longer accepted at Federal Reserve Banks or the Internal Revenue Service.

Fiduciary - A person or institution entrusted to act on behalf of a taxpayer.

File Source - A one digit code which follows the taxpayer identification number (TIN). The values are:

Blank

Valid SSN or EIN

0

Invalid SSN on IMF

V

Valid SSN on BMF

W

Invalid SSN on BMF

D

Temporary TIN

P

Valid IRA SSN valid EPMF EIN

X

Invalid IRA SSN invalid EPMF EIN

Filing Requirement Code (FRC) - This code identifies the type of return an organization must file.

Fiscal Year Month (FYM) - Any month an organization elects to be the ending month of its accounting year.

Group Exemption Number (GEN) - A four digit number issued to a parent organization and its subordinate chapters under a blanket "GROUP RULING."

Group Exemption Roster (GER)/CC EOGEN - An alphabetic and numeric listing of organizations which were issued Group Exemption Numbers. Published semiannually as Document
6023, it was replaced by CC EOGEN, which allows on-line research using the GEN number of the group.

Group Return - Form 990 filed by a parent organization for all of its subordinates which have elected to be covered by the group return.
This return with its own EIN is filed in addition to the parent organizations own return.

Income Code - A code used to identify yearly receipts for EO/BMF returns.

Integrated Data Retrieval System (IDRS) - A computer system with the capability to instantaneously retrieve or update stored information which will work in harmony
with our Master File or organization accounts. This system is aimed at quick resolution of problems and inquiries concerning
current and prior taxpayer accounts.

Julian Date - The numeric day of the year the return or document was numbered for processing; for example, January 15 would be shown as
015. The sixth, seventh and eighth digits of the DLN represent the Julian Date.

Note:

If the DLN is computer generated, the Julian Date is inflated by 400, so January 15 is shown as 415.

Martinsburg Computing Center (MCC) - The Martinsburg Computing Center, located in Martinsburg, WV, is where both business and individual transactions are posted
to the various Master Files.

Master File (MF) - A record containing all information with respect to the organizations filing of returns and related documents. The Business
Master File (BMF) contains records on each organization, divided into two sections, the entity section and the returns section.

Master File Tax Account Code (MFT) - A two digit number which identifies the type of tax form.

Merger - When two or more corporations combine and one is the successor corporation, the other corporation files final returns on their
number. DO NOT confuse this with Consolidation (TC 011).

Microfilm - A media to provide photographic records of tax data on a reduced scale.

Name Control (NC) - The first four letters of an entity's last name (in the case of an individual) or the first four letters of an entity's business
name (in the case of corporations, etc.). The name control is used to check the Master File and ensure the TIN corresponds
with the proper organization.

Name Search Facility (NSF) - This facility provides the capability to search a national data base for an unknown TIN (EIN or SSN) using name and address
information. The NSF provides search capability for primary, secondary and Doing-Business-As (DBA) filers. The command codes
used to search the NSF are CC NAMES (SSN) and CCs NAMEE (EIN)/NAMEB.

National Account Profile (NAP) - A national TIN file of entities on the IMF, BMF, EPMF and IRAF. It is used to validate the TIN or TIN/name control for IDRS
input command codes and for researching with CC INOLE.

Parent - The governing body of a controlled group of corporations or an exempt organization with a group ruling.

Pending Transaction - A transaction input to IDRS but not yet effective on the Master File account.

Pilot Voucher - An Exempt Organization/BMF Entity voucher prepared for processing group exemptions. This is a file copy only.

Pilot Voucher File (PVF) - This file of all pilot vouchers is kept in GEN order. The pilot vouchers are used in establishing new subordinates of a group
ruling.

Power Of Attorney (POA) - The authorization of a third party by a taxpayer to represent the taxpayer in certain tax matters. See CENTRALIZED AUTHORIZATION
FILE (CAF).

Primary Location Code (PLC) - The PLC is the Area Office code based on the address where the taxpayer receives mail. The BMF should generate the PLC, or
we can create or change it by CC BNCHG, Document Code 50 or 63. The PLC is issued to identify the service center controlling
the account.

Prior Year - A tax period which precedes the current processing year.

Re-Input - The reentry into the processing system of a return or document which has not posted to the Master File.

Refile - A refile is sending the return or document back to Files to be filed in its original position in the block.

Reject - A return or document which was not accepted by the campus computer because of incorrect or incomplete information.

Reprocessable - The reentry into the processing system of a return or document which previously posted to the Master File.

Resequence - A resequence occurs when a transaction cannot be posted or processed until the following week (cycle) at MCC.

Return - A legal form or written evidence used by an organization to record tax information.

Revocation - A revocation is an organization initiated correspondence used to revoke the election to be exempt.

Subordinate - A subordinate is a local affiliate of a Parent organization.

Subsection Code - This code designates the type of exemption an organization has received.

Supplemental Group Ruling Information (SGRI) - An SGRI is a letter submitted to the IRS each year by the Parent organization of a group ruling detailing any changes to its
subordinates.

Tax Module - A tax module is part of an organizations account which reflects tax data for each type of tax and tax period.

Tax Period - This is the period of time for which a return is filed. The Service uses a six digit code to indicate the end of the tax period
for a given return. The first four digits represent the year and the last two digits represent the month.

Taxpayer Delinquent Account (TDA) - A TDA is a tax module in collection status in which a return was filed but not fully paid.

Taxpayer Delinquency Investigation (TDI) - A TDI is a tax account in collection status which has a filing requirement for which a return has not been received.

Taxpayer Identification Number (TIN) - The TIN is a generic term representing either an EIN or SSN.

Transaction Code (TC) - This three digit code is used to identify transactions being processed, to maintain a history of actions posted to taxpayer
accounts on the Master File, and to identify actions being taken on an organizations account.

Transcript - A transcript is a copy of entity and tax data from the Master File concerning an organizations account.

Unpostable (UP) - An unpostable is an input return or transaction which attempted to post to the Master File but could not because of inconsistencies
with prior posted transactions, filing requirements or the input data.

Unprocessable - An unprocessable is a document which is incomplete, illegible or otherwise unsatisfactory for input.

3.12.278.1.3
(01-01-2015)IRC 3705(a), IRS Employee Contacts

Background

The Restructuring and Reform Act of 1998, IRC 3705 provides identification requirements for all IRS employees working tax–related
matters.

IRS employees are required to give their name and unique identification number during taxpayer telephone, face-to-face and
manually generated correspondence. In addition a telephone number the taxpayer may contact is required on all taxpayer correspondence.

This will provide taxpayers with enough information to identify an IRS employee who previously assisted with tax-related matters.

All IRS employees, in the field, national, and regional office, who communicate by telephone, correspondence, or face-to-face
with taxpayers or their personal representatives on tax-related matters are required to provide (at a minimum) the following
information:

Face-to-Face - title (e.g., Mr., Mrs., Ms., Miss), last name and badge identification (ID card) number provided at the appropriate time
during the conversation

Correspondence - title (e.g., Mr., Mrs., Ms., Miss); last name; IDRS, letter system or badge identification (ID card) number; and telephone
number where the taxpayer's question can be answered

Note:

The IDRS number and numbers for some other letter systems are automatically generated. If it is not generated, or a handwritten
note is prepared, the ID card (badge) number must be used.

Employees on toll-free customer service lines may also provide their location for identification purposes. email and faxes
to taxpayers on tax-related matters, are considered manually-generated correspondence and must include the required information.

Manually generated correspondence, whether sent directly to the taxpayer or to the taxpayer's personal representative, must
contain the required information.

When a taxpayer insists on speaking with a specific employee who previously handled their inquiry or request, or complains
about the level of service previously provided, every attempt should be made to resolve the taxpayer's inquiry. If the issue
cannot be resolved, the employee should refer the inquiry using established procedures to his or her manager.

Correspondence letters will require a specific employee name and telephone number only if the employee initiating the correspondence
is in the best position to respond to any questions the taxpayer may have about the correspondence, or the employee is asking
the taxpayer to provide additional case-related information. Otherwise, if the taxpayer does not need to contact a specific
employee, the correspondence needs only an IRS telephone number and standard signature.

It is not necessary to repeat the ID card (badge) number on a subsequent contact, when the nature of an employee's work involves
multiple contacts with the same taxpayer and the employee has given the taxpayer (either by telephone or in person) their
ID card (badge) number on the first contact.

Before disclosing any tax information in all types of taxpayer contact, you must be sure you are speaking with an authorized
representative of the organization.

3.12.278.1.4
(01-01-2015)National Service Level Agreements (SLAs)

National Service Level Agreements (SLAs) were established between Operating Divisions. This section contains specifics regarding
SLAs which pertain to activities performed by use of this IRM.

3.12.278.1.4.1
(01-01-2015)Taxpayer Advocate Service Level Agreement

National Service Level Agreements (SLAs) were established between the Taxpayer Advocate Service (TAS) and each Operation Division.
The SLAs contain basic requirements for handling TAS-referred cases, and include specific action to take on a TAS referral
and specific time frames for completing those actions.

The SLAs can be found at http://tas.web.irs.gov/ under Policy/Procedures/Guidance.

The Taxpayer Advocate Service (TAS) is an independent organization within the IRS whose employees assist taxpayers who are
experiencing economic harm, who are seeking help in resolving tax problems which have not been resolved through normal channels,
or who believe an IRS system or procedure is not working as it should. TAS criteria include economic burden, systemic burden,
best interest of the taxpayer, and public policy (as determined solely by the National Taxpayer Advocate (NTA)). TAS is responsible
for assisting taxpayers who have unresolved problems within the IRS See IRM 13.1.7, Taxpayer Advocate Service (TAS) Case Criteria if additional information is required.

While the Internal Revenue Service (IRS) is continually working to serve customers in a quality manner, some taxpayers still
have difficulty getting solutions to their problems or getting timely and appropriate responses to their inquiries. Per IRC
7803(c), Congress established the office of the NTA and its functions within the IRS to assist these taxpayers. TAS has identified
criteria that qualifies taxpayers for TAS assistance. The Case Advocate will conduct an independent review of actions taken
or need to be taken to resolve the problems taxpayers are experiencing.

Employees should not view TAS Case Criteria as a means of excluding taxpayers from TAS, but rather as a guide to TAS case
acceptance. The criteria under which TAS accepts a case should not govern whether a taxpayer is entitled to relief.

Refer taxpayers to TAS when the contact meets TAS criteria. ( IRM 13.7.1, Taxpayer Advocate Service (TAS) Case Criteria ) and you cannot resolve the taxpayer's issue on the same day. The definition of same day is within 24 hours. Same day cases
include cases you can completely resolve in 24 hours, as well as cases in which you have taken steps within 24 hours to begin
resolving the taxpayer's issue. Do not refer these cases to TAS unless they meet TAS criteria and the taxpayer asks to be
transferred to TAS. When referring cases to TAS, use Form 911, Request for Taxpayer Advocate Service Assistance (and Application
for Taxpayer Assistance Order), and forward it to TAS in accordance with your local procedures. Check the TAS box on AMS,
if applicable.

Note:

It is important all IRS employees handle potential TAS cases with the taxpayer's best interest in mind. Refer to IRM 21.1.3.18,
Taxpayer Advocate Service (TAS) Guidelines for more information.

Provide the taxpayer with the NTA toll-free case intake line, 1-877-777-4778 or TTY/TDD 1-800-829-4059. The taxpayer should
be advised TAS is available if the taxpayer is not satisfied with the service received.

An IRS employee should make a referral to a TAS office if the employee receives a taxpayer contact, and cannot initiate action
to resolve the inquiry or provide the relief requested. A taxpayer does not have to specifically request TAS assistance to
be referred to TAS. IRS employees will advise taxpayers of the option to seek TAS assistance when appropriate. TAS will request
documentation from the taxpayer if it is needed to support the requested relief or required by the IRM.

The following types of cases should NOT be referred to TAS:

The taxpayer's complaint or inquiry only questions the constitutionality of the tax system.

Cases where the focus of the taxpayer's inquiry is solely to employ frivolous tax strategies to avoid or delay filing or paying
federal taxes.

Any taxpayer contact that meets any of the criteria listed below should be forwarded to the local Taxpayer Advocate for special
handling using a Form 911, Request for Taxpayer Advocate Service Assistance (and Application for Taxpayer Assistance Order).

The taxpayer is experiencing economic harm or is about to suffer economic harm.

The taxpayer is facing an immediate threat of adverse action.

The taxpayer will incur significant costs if relief is not granted (including fees for professional representation).

The taxpayer will suffer irreparable injury or long - term adverse impact if relief is not granted.

The taxpayer has experienced a delay of more than 30 days to resolve a tax account problem.

The taxpayer has not received a response or resolution to their problem or inquiry by the date promised.

A system or procedure has either failed to operate as intended, or failed to resolve the taxpayer's problem or dispute within
the IRS.

The manner in which the tax laws are being administered raise considerations of equity, or have impaired or will impair the
taxpayer's rights.

The NTA determines compelling public policy warrants assistance to an individual or group of taxpayers.

Note:

The case criteria listed above is not meant to be all inclusive; each taxpayer situation should be evaluated based on the
unique facts and circumstances of each case.

The Operation Assistance Request (OAR) process is used to refer TAS cases when TAS either lacks the statutory or delegated
authority to resolve a taxpayer's problem. TAS utilizes Form 12412, Operations Assistance Request, to initiate the OAR process.

The Operating Divisions and Functions will acknowledge receipt and provide the name and phone number of the IRS employee assigned
to work the case within one (1) workday of receipt of the OAR involving an economic hardship case. The Operating Divisions
and Functions will provide a relief/no relief decision with three (3) workdays of acknowledging receipt of an OAR. The decision
will be in writing, via facsimile, or hand delivery to the TAS case advocate.

the Operating Divisions and Functions will acknowledge receipt and provide the name and phone number of the IRS employee assigned
to work the case within three (3) workdays of receipt of the OAR involving a systemic or procedural hardship. The TAS employee
will then negotiate a reasonable time frame with the IRS employee to resolve the case.

In cases requiring an OAR, TAS will complete Form 12412 and forward the case to the Operating Division Liaison via Form 3210.
The Operating Division Liaison will review the case, assign it to the appropriate area, and monitor the case through its conclusion.

Every effort must be made to expedite completion of OAR cases. Time frames for the assigned area to complete the case will
be indicated on Form 12412.

If resolution of the taxpayer's case cannot be completed by the requested time frame or by a negotiated extension date, the
employee will immediately notify his or her manager.

The manager/employee will work with the Taxpayer Advocate contact listed on Form 12412 to arrive at agreed upon time frames
for follow-up based on the facts and circumstances of the particular case.

The manager/employee assigned the case will discuss his or her findings and recommendations on the final disposition of the
case with the appropriate TAS contact. The TAS contact is responsible for communicating the final decision on the case to
the taxpayer; however, this does not prohibit the manager/employee from also communicating the decision to the taxpayer.

If the TAS contact and the manager/employee assigned the case cannot agree upon the resolution to the taxpayer's problem,
the TAS employee will elevate this disagreement to his or her manager who will discuss it with the appropriate Operating Division
manager. The manager/employee assigned the case will also elevate any disagreement to his or her manager.

Refer to IRM 13.1.7, Taxpayer Advocate Service (TAS) Case Criteria , for Taxpayer Advocate case criteria. If during a taxpayer contact it appears a hardship situation may exist, complete Form
911, Application for Taxpayer Assistance Order, and refer the taxpayer to the Taxpayer Advocate Service (TAS). See IRM 21.1.3.18, Taxpayer Advocate Service (TAS) Guidelines, for more information.

3.12.278.2
(01-01-2015)Manual Refunds

Refer to IRM 21.4.4, Manual Refunds, IRM 3.17.79, Accounting Refund Transactions, and IRM 3.13.222.15, Unpostables Requiring Manual Refunds, to identify the need for a manual refund. Also, refer to the Servicewide Electronic Research Program (SERP) for the most
current and accurate manual refund alerts and IRM procedural updates (IPU).

Any unpostable return can potentially require a manual refund. Unpostable employees are required to identify when a manual
refund is necessary and take actions to initiate the manual refund.

Common criteria for issuing a manual refund include:

A hardship situation requires an expeditious refund (TAS)

The 45 day interest free period is in jeopardy and the refund is ≡ ≡ ≡ ≡ ≡ ≡ or more

Note:

A refund is in jeopardy if the current date is 20 days beyond the later of the Return Due Date, Return Received date or Correspondence
Received date (CRD) also referred to as the Return Processable Date (RPD).

The refund is one million dollars or more

Note:

Manual refunds are no longer input by EO Unpostables. Manual refunds should be sent to Rejects for input.

IDRS Command Codes which create posting transactions have their TIN and name control combinations validated prior to the "Request
Completed"
response. These transactions are passed against the Taxpayer Identification File (TIF) and the National Account Profile
(NAP) to ensure the transaction will post properly at the Master File.

If the return is not provided with the F4251, online SEIN should be used to resolve unpostables and initiate correspondence
if necessary to resolve unpostables timely. If SEIN is not available order Document with the D2, D3 process.

Complete analysis of each unpostable return is necessary to ensure all unpostable conditions are corrected to avoid unnecessary
repeating of unpostable returns.

If a return from SEIN is used, leave a history on ENMOD indicating a return from SEIN was used including the MFT and Tax Period
of the SEIN return.

In 2006, congress mandated all tax-exempt organizations, except churches and church related groups, file annual return starting
in the 2007 tax year. Congress also mandated any organization that failed to file for three consecutive years would automatically
lose their tax-exempt status. Beginning May 17, 2010, exempt organizations who fail to file for three consecutive years will
lose their tax exempt status. The organization's status will automatically be changed to Status 97 and Form 1120 or 1041 filing
requirements will be added to their account beginning in 2011. Those organizations who file Form 990–N were given an extension
of time to file until October 15, 2010. In order to ensure organization's whose return is in an unpostable condition are not
erroneously revoked, a transaction 599 cc 18 should be input on every unpostable 990 or 990-PF return if the return was received
by the due date or extended return due date. and if the unpostable condition is not corrected within 12 weeks of the revocation
process. Use the table below to determine when to input the TC 599 cc 18.

Due Date Month of the return:

Input TC 599/18 if you are working the unpostable 12 weeks or less of:

May 17, 2010

November 1 , 2010

June 15, 2010

December 1, 2010

July 15, 2010

January 1, 2011

August 16, 2010

February 1, 2011

September 15, 2010

March 1, 2011

October 15, 2010

April 1, 2011

November 15, 2010

May 1, 2011

December 15, 2010

June 1, 2011

January 17, 2011

July 1, 2011

February 15, 2011

August 1, 2011

March 15, 2011

September 1, 2011

April 15, 2011

October 1, 2011

3.12.278.3.1
(01-01-2015)Corporate Files On-Line (CFOL)

CFOL provides nationwide access, meaning information processed through any area office or campus and posted to any Master
File is available.

CFOL command codes are available even when IDRS is not; however, you still need a password to sign on and access the command
codes.

CFOL command codes do not show pending transactions, case controls, history items or unpostables. IDRS research must be performed
in addition to CFOL research.

Some of the more common CFOL command codes you will use include:

BMFOL - The B usiness M aster F ile O n–L ine provides research of nationwide entity and tax data information posted to the BMF. It displays a summary or index (definer
code I) of tax modules, showing the tax years available. The Business Master File is updated every Thursday morning at MCC.
Therefore, any transaction which is updating the BMF can be seen on BMFOL on Thursday prior to the weekend campus update.

BRTVU - BRTVU provides a display of the transcribed line items on all business tax returns and their accompanying schedules or
forms as the returns are processed at the campuses. Use BRTVU in lieu of ordering returns whenever possible.

EOGEN - EOGENP can find a Parent organization using the GEN of the group. EOGENS will also provide a list of subordinate organizations
for the parent organization. This list is limited to 30 pages, with 20 subordinates per page. You can narrow the search for
subordinates by entering the optional state abbreviation ("."
for foreign addresses). This is especially helpful when researching large organizations such as Little League, Lions Club
International, etc. EOGEN will not research by EIN. If you know the EIN but not the GEN, research CC BMFOL definer O to get
the GEN, then research CC EOGEN. EOGEN does not provide full entity information for subordinates. It provides a starting point
for further research.

INOLE - INOLE provides access to the NAP, which contains selected entity information for all Master File accounts. The NAP contains
vital information which can identify the taxpayer, but does not contain all of the entity data for the taxpayer. Additional
research must be done using CC ENMOD or CC BMFOL. CC INOLE is updated each Wednesday at the computing centers.

3.12.278.3.2
(01-01-2015)IDRS

Integrated Data Retrieval System (IDRS): IDRS is a computer system with the capability to retrieve and update stored taxpayer account information on the Master Files.
You perform research on IDRS through the use of various command codes (CC) input to an IDRS terminal.

3.12.278.3.2.1
(01-01-2015)Common IDRS Research Command Codes

NAMEE/NAMEB is used to search for an EIN.

ENMOD is used to display the entity information of a specific TIN.

SUMRY is used to display a list of the tax modules (TXMODs) currently available via IDRS.

TXMOD is used to display specific tax module information for a specific TIN.

UPTIN is used to display all open cases and cases which were closed within the last 90 days for a specific TIN.

3.12.278.3.2.2
(01-01-2015)Universal IDRS Access

Universal IDRS Access is part of the Tax Systems Modernization (TSM) effort to provide IDRS users the ability to research
data on another campus' Taxpayer Information File (TIF) database. It allows the user to access the most current account data
available, including pending transactions, unpostables, facts of filings, etc.

"Remote Access"
allows the IDRS user to input certain research command codes in other campus databases by rerouting the request. This is
done by the input of the command code followed by the routing symbol ("@"
), the two digit campus location code, and transmitting.

The "National Account Index (NAI)"
is a national index which tracks the campus location of all IDRS TIF accounts where the account is up. If there is "no data
available"
on the local database, the NAI will automatically search for other locations where the account is up. If another location
is found, a message will be displayed at the bottom of the screen.

For more information, See IRM 2.3, IDRS Terminal responses..

3.12.278.3.2.3
(01-01-2015)Common IDRS Input Command Codes

BNCHG is used to input entity information changes to the BMF.

ENREQ is used to generate the screen format for BNCHG.

LETER is used to input information and generate a C letter.

EOCHG is used to input changes to the EO sub-module of BMF accounts.

EOREQ is used to generate the screen format for EOCHG;.

FRM49 is used to input TC 59X transactions.

REQ49 is used to generate the screen format for FRM49.

UPDIS is used to display a specific unpostable case and generates command code UPRES.

UPRES is used to input closing action(s) on an unpostable case.

3.12.278.3.2.4
(01-01-2015)IDRS Pending Codes

Transactions which are pending are identified on IDRS with a unique code. The most common of these pending codes are:

Unnn - the transaction has unposted (nnn represents the number of the unpostable code).

CU - the transaction is a corrected unpostable.

DU - the transaction unposted and was deleted (will not post to Master File).

DN - the transaction was deleted during IDRS batch processing.

RJ - the transaction is in Reject status.

NU - the transaction unposted and was nullified (sent to the Reject function for resolution).

DC - the transaction was deleted by Rejects.

Note:

See LEM 3.27.68 or Document 6209, IRS Processing Codes & Information, for more information on these and additional pending
transaction codes.

3.12.278.3.3
(01-01-2015)TE/GE (EP/EO) Determination System (EDS)

EDS is an automation of certain segments of the EP/EO determination process. EDS is a menu-driven system. The Inventory Control
Subsystem and the Letter Generation Subsystem are the two segments the EO Unpostable Unit will use.

EDS research is required to determine correct status for most exempt organization unpostable accounts. EDS information should
be used to update an exempt organization's filing status. EDS research should be used in conjunction with all other research
tools to ensure accounts reflect current and accurate exempt organization data.

The Inventory Control System replaces the Exempt Organization Application Control System (EACS) as the system which tracks
cases from opening to closing; however, EACS, which is renamed Master File Pipeline System continues to function in the campuses
as the link between EDS and Master File.

The Letter Generation Subsystem provides a means to automatically generate requests for additional information and the viewing
and generation of closing letters.

The following is a list of the Open Status Codes:

Open Status Codes

Definition

31

In Review

32

Returned on Review Memo

33

Return from Review

34

Area Council Approval

35

30 Day Letter Sent

37

Group Suspense

38

Review Suspense

39

Technical Screening Suspense

40

Proposed Adverse Determination

41

Proposed Technical Advice

50

Area Office Receipt

51

Unassigned Inventory (Non-merit)

52

Assigned to Specialist (Non-merit)

53

Manager Returned to Specialist

54

Transferred to Appeals

55

Waiting for Closing Approval

56

Technical Advice Transfer (Suspense)

57

TEDS Awaiting Closure on EDS

58

Workload Transfer

59

EDS Manual Process (Case is no longer being processed on TEDS)

60

Open in Technical Screening

61

Unassigned Inventory (Merit)

62

Assigned in Technical Screening (now reflects the associated Specialist Number on the case history page)

63

New Case Establishment (TEDS) (Cases established on EDS have an initial status of 50.)

Revoked - Failure meet their filing requirements for three consecutive years. (Organizations lose exempt status and are required
to file Form 1120. All EO return filing requirements will be removed.)

98

Terrorist Organization - No Exemption

99

Dump Code - No Exemption

3.12.278.3.5.1
(01-01-2015)EO Status Code 01

When an organization is granted an exemption, Cincinnati EO Determinations or NO SE:T:EO will input the information on the
BMF to create the EO account, or add the exemption data to an already existing account. When Status Codes 01 or 02 are present
on the BMF/EO account, they indicate an exemption was granted to the organization. IRC 501(c)(3), 501(c)(9), 501(c)(17), and
501(c)(20) organizations are required to notify the Service they are seeking tax-exempt status; therefore, they must file a Form 1023 or 1024 as applicable with
EO Determinations.

Exception:

Churches, conventions of churches, integrated auxiliaries of churches, and organization with gross receipts of less than $5,000
are not required to apply for tax-exempt status.

Note:

IRC 501(c) organizations other than IRC 501(c)(3), IRC 501(c)(9), IRC 501(c)(17), and IRC 501(c)(20) organizations are not required to file an application for exemption, though they may do so. They are considered exempt even though they do not
apply for exemption.

Note:

Beginning January 2004 a Form 990-T or a payment for a Form 990-T will automatically post to an account in EO Status 01-02
if the name control and EIN on the return or payment match the name control and EIN on Master File. A Form 990-T filing requirement
will be added to the module.

If research of EDS on first screen indicates status 01, 06 or 09 update the BMF for the EO section, using the procedures in
IRM 3.13.12.5, EO/BMF.

Caution:

If the status code on EDS is other than 01, 06 or 09 do not update the EO Status Code to 01.

If the entity is an Non-Integrated Auxiliary (NIA), the Form 990 FRC should be 13, with SS 03 and Type of Foundation Code
10. Research CC ENMOD.

Add the account to the BMF. Use CCs EOREQ/EOCHG with Doc. Code 80, TC 000 and use the pilot voucher or EDS as the source information
to update the BMF.

The ruling date is available,

Use the ruling date when returning the EO Status to 01.

3.12.278.3.5.2
(01-01-2015)EO Status Code 06

Use Status Code 06 to create an EO section on the BMF for an account which is a state operated university or college or a
Re-insurance company, required to file Form 990-T for unrelated business income.

Note:

To identify a Re-insurance company, check the top of Form 990-T for the words "Re-insurance Company" or similar wording. If
unable to determine whether the 990-T is filing for a re-insurance company, put the account in the appropriate status code.

When a Form 990-T is received for this type of entity and research shows it does not have an exemption, use EO Status 06 to
add an EO section to the EIN on the BMF. Input a TC 971 AC 319 for the tax period indicated on the return.

Input this status code with a TC 012 or 016 using CC EOREQ/CC EOCHG. If a return is received without an EIN and research does
not locate an EIN, assign an EIN.

The following items must be present for EO Status 06:

Doc. Code 80

TC 012 or 016

Definer Codes - AB

STS-CD/DT - 06YYYYMM

FYM

Filing Requirements 990-T - 1

REMARKS

3.12.278.3.5.3
(01-01-2015)EO Status Code 07

When the EO section is not on the BMF, use Status Code 07 to create an EO section for an account which is a church filing
Form 990-T.

When a Form 990-T for a church is received and research does not reveal an exemption, use Status Code 07.

Never use this status code under the following conditions:

The GEN is shown in item F on the return. In these cases, use the pilot voucher.

401(a) trust is checked on the return or the name contains words such as "Pensions,"
"Retirement,"
"Welfare,"
or " Profit Sharing Plans."
See IRM 3.13.12.9.12.4, Form 990-T (401(a) and 408 IRA Trust for information on 401(a) and 408 IRA Trusts filing Form 990-T.

The organization name does not clearly indicate a church, or you are in doubt whether the organization is a church. In these
cases, use Status Code 40.

Add the EO section to the BMF with CCs EOREQ/EOCHG. The items shown below must be present when processing a TC 016.

Doc. Code 80

TC 016

Definer Codes - AB

STS-CD/DT - 07YYYYMM

FYM

Filing Requirements 990-T - 1

REMARKS

If

Then

The account is not on the BMF,

Use CC EOREQ/CC EOCHG with Doc. Code 80 and TC 000.

The account is on the BMF,

Use CC EOREQ/CC EOCHG with Doc. Cod 80, TC 016 and Definer Codes AB.

3.12.278.3.5.4
(01-01-2015)EO Status Code 10

Use Status Code 10 to create an EO section for a church which was examined by the EO Area Office in Dallas.

The Form 990 which will be received will be prepared by the EO Area Office Examination. It will be a dummy return, input to
create a tax module on the BMF to allow the examination closing record to post.

Add the EO section to the BMF through IDRS with CC EOREQ/CC EOCHG.

If

Then

The account is not on the BMF,

Use CC EOREQ/CC EOCHG with Doc. Code 80 and TC 000.

The account is on the BMF,

Use CC EOREQ/CC EOCHG with Doc. Code 80, TC 016 and Definer Codes A and B. The items shown below must be present.

Doc. Code 80

TC 016

Definer Codes - AB

STS-CD/DT - 10YYYYMM

FYM

Filing Requirements 990-06

REMARKS

3.12.278.3.5.5
(01-01-2015)EO Status Code 12

Use Status Code 12 to create an EO section for returns filed under IRC 4947(a)(1) or 4947(a)(2) or Taxable Farmer's Cooperatives
when the EO section is not on the BMF.

If Forms 990 or 990-PF under IRC 4947(a)(1), 990-C/1120-C or 5227 are received and research does not reveal an exemption,
use Status Code 12.

Note:

Use Status Code 12 for a Form 990 filer if EDS shows a 1071 Letter was sent to the organization.

Add the EO section to the BMF through IDRS with CC EOREQ/CC EOCHG.

If the account is not on the BMF, use CC EOREQ/CC EOCHG with Doc. Code 80 and TC 000.

If the account on the BMF is without an EO section or with an incorrect EO section due to a Form 5227 or Form 1120 FRC, use
CC EOREQ/CC EOCHG with Doc. Code 80, TC 016 and Definer Codes AB. To correct, do the following:

Use the applicable subsection codes as shown above.

For Forms 5227, check line B and G.

If

Then

Line G indicates the trust has unrelated business income, or box 1 or 4 is checked on line B,

use FRC 2. Research BMF to ensure a Form 1041 FRC is present, adding if necessary.

Line G indicates the trust has no unrelated business income, or box 2 or 3 is checked on line B

Use FRC 1. Research BMF and delete any Form 1041 FRC, if present.

For Forms 990 and 990-PF:

If

Then

The BMF has an EO section for Form 5227,

Delete the Form 5227 and 1041 FRC on the same input as adding the Forms 990 or 990-PF FRC. Always enter ST 12 and use the current date.

A Form 1041-A FRC is also present on the BMF,

You must input a TC 591, Closing Code 20, to the tax period of the latest posted MFT 36 tax module.

3.12.278.3.5.6
(01-01-2015)EO Status Codes 18 and 19

Status Codes 18 and 19 are input by Cincinnati when a private foundation exemption is revoked. The organization is required
to continue filing the Form 990-PF return.

Status 18 is used when the organization is a trust. Cincinnati will change the Type of Organization to a 6 and the Subsection Code
to a 92. The type of foundation code will be deleted by the BMF. The organization will be required to file both a Form 990-PF
and a Form 1041.

Status Code 19 is used when the organization is a corporation. The organization will be required to file both a Form 990-PF and a Form 1120.

3.12.278.3.5.7
(01-01-2015)EO Status Code 20

Status Code 20 ("Terminated/Out of Business"
) is used when the organization with an individual ruling is terminated or out of business. The filing requirement for
all EO returns will be updated to zero automatically.

This status can be input by the campus when correspondence from the organization contains statements such as "out of business"
, "no longer in operation"
, or "terminated"
.

Note:

Status 20 is only used for organizations with individual rulings. If the organization is a subordinate of a group and the
parent indicates it is no longer part of the group, the subordinate is put in Status 36 or 40 depending on the subsection.

Input this status with a Doc. Code 80, TC 016 and Definer Code B. and the current date is input for the status date (YYYYMM).

If the organization has a 501(c)(3) exemption with end of year assets greater than $100,000 (see Line 21 Part l on Form 990,
Line 27 Part l on Form 990-EZ, Line 6 Part lll on Form 990-PF), do not input Status 20. Forward the case to Cincinnati. Annotate on the transmittal to establish a T case.

When the organization responds to a delinquency notice with statements such as "out of business"
, "no longer in operation"
, "terminated,"
etc., a TC 591 cc 20 will be input. When this transaction posts to the tax module which is a primary return, the EO Entity
Status will be updated to 20 with the date the TC 591 posted.

Exception:

If the BMF shows the account to be a subordinate of a group ruling; i.e., a GEN is present and the AF is 7 or 9, the update
will be to a Status Code 28.

When a final return is filed and Computer Condition Code F is input, the EO Entity Status is automatically updated to 20.

Exception:

If the BMF shows the account to be a subordinate of group ruling; i.e., a GEN is present and the AF is 7 or 9, the update
will be to a Status Code 28.

When the EO status must be changed from Status 20 to any other EO status for a central organization (Affiliation code 6),
IT programmers for the GEN file must take action before any updates will post to Masterfile.

Once a need for status change has been identified, ensure all subordinate groups of the GEN have been removed or are in an
inactive status.

Input TC 590 CC 020 on Form 1120.

Inform the TEGE analyst with oversight of this program of the Employer Identification Number (EIN) and GEN.

No additional actions should be taken until further instructions are given by the TEGE analyst.

Once the additional instructions are sent, the actions must be taken within 24 hours of receipt. If actions are not taken
timely, the entire update process will be in jeopardy.

Final closing instructions will be different for each case and must be given on a case by case basis.

Once the Central organization had been re-established and all final actions have posted to masterfile, all subordinates must
be added back to the GEN.

3.12.278.3.5.9
(01-01-2015)EO Status Code 21

Status Code 21 ("Unable to locate "
) is used when we are unable to locate the organization. Status Code 21 is generated by the input of CC FRM49 with a TC
593 cc 082. The posting of the TC 593 cc 082 removes all EO filing requirements.

When working an unpostable return which requires the updating of the EO Status Code from 21 to 01:

Check EDS for a "T"
case. If a "T"
case is found, update the Status Code to 40. Notify the organization they have terminated and must apply for a formal
exemption.

If no "T "
case is found, update the EO Status to 01 and post the return. Research CC BMFOLI to determine for what years the organization
did not file a return and input a TC 474 to create a tax liability for those years.

Update the filing requirements as follows:

If the return indicates gross receipts greater than $50,000, update the 990 filing requirements to 990-01.

If the return indicates gross receipts less than or equal to $50,000, update the 990 filing requirements to 990-02.

If there is no indication or you are unable to determine the gross receipts, update the 990 filing requirements to 990-02.

3.12.278.3.5.10
(01-01-2015)EO Status Code 22

Status Code 22 ("Revocation"
) is used when the organization's exemption is revoked. This status will generate a Form 1120 filing requirement. If the
Form 1120 FR is missing, add it to the account.

Note:

An organization in EO Status 22 cannot become a member of a group ruling without receiving an individual ruling first.

If the organization files a Form 990-PF but there is an Form 1120 FR, change the status to 01 to post the Form 990-PF, return
the account to its previous status after the return has posted. If the organization files a Form 990 but there is a Form 1120
FR, check the Docketed Case listing to determine the disposition of the return. Check the Docketed Case List for the assigned
attorney and contact the attorney for information on how to dispose of the case.

Follow the lawyer's instructions given and do not correspond with the organization. If not, on the Docketed Case listing,
continue working the unpostable using the normal procedures.

3.12.278.3.5.11
(01-01-2015)EO Status Codes 23 and 24

Status Code 23 ("Termination Under 507(a)"
) is used when the organization is terminated under 507(a). The filing requirements of all EO returns will be updated to
a zero, except Form 990-PF which will not change.

Status Code 24 ("Termination Under 507(b)(1)(A)"
) is used when the organization is terminated under 507(b)(1)(A). The filing requirement for all EO returns will be updated
to zero, except Form 990-PF which will not change.

3.12.278.3.5.12
(01-01-2015)EO Status Code 25

Status 25 Background Information

Status 25 represents private foundations which have received an advance ruling letter from Cincinnati indicating they are
terminating under 507(b)(1)(B), also known as a 60-month termination. Cincinnati will update the EO Status to 25 and input
an Advance Ruling Date using Form 2363A. There will be a TC 016 with Cincinnati's DO code on CC BMFOLE to indicate the EO
status was changed and advance ruling date input.

These organizations will continue to file a Form 990-PF for 5 years, but may elect not to pay tax on net investment income. If they elect not to pay tax, a Form 872B (Consent to Extend the Time to Assess Miscellaneous
Excise Taxes) must be attached to the Form 990-PF when filed. The interest on the tax should continue to accumulate in this case, but the organization
should not receive notices or penalties. At the end of the 5 years, the organization must show they meet public support test.

If they do meet the public support test, Cincinnati will issue a new determination letter, update the EO Status to 01, change
the FR to Form 990 and remove the advance ruling date. If the organization did not choose to pay their excise tax, they will
not owe the interest which has accumulated. If the organization chose to pay the tax during the 60-month termination, they may
apply for a refund.

If the organization does not meet the public support test, Cincinnati will remove the advance ruling date, update the EO Status
to 01 and the filing requirement will remain a Form 990-PF. If the organization did not pay any excise tax during the 60-month
termination, the organization will owe back taxes plus interest.

In the last year of the 60-month termination, the organization may file a Form 990 if they provide the necessary information
to Cincinnati as stated in the Form 990-PF instructions and Cincinnati determines they meet the public support test and issues
them a new determination letter. Process as follows:

If

Then

The organization files a Form 990 for the final year of their termination period:

Research EDS to determine if they were approved as a public charity.

If they were approved, update the BMF with a TC 016 Doc. Code 80 Definer Codes AB. Input URC 0 to release the unpostable and
cycle to post after the TC 016.

If they have not been approved, correspond with the organization indicating they are required to supply Cincinnati with the
necessary information to determine if they are a public charity before they can file a Form 990. Also indicate if they have
supplied the necessary information to Cincinnati to please send a copy along with their response. If they did not supply Cincinnati
with the necessary information, they are required to file a Form 990-PF for the last year of their termination period.

The organization responds with a copy of the information supplied to Cincinnati,

If Cincinnati indicates the organization is a public charity, update the BMF with a Form 990 filing requirement and EO Status
of 01 with a TC 016 Doc. Code 80 Definer Codes AB. Input URC 0 to release the unpostable and cycle to post after the TC 016.

If Cincinnati indicates the organization is still a private foundation, update the BMF with a Form 990 filing requirement
an EO Status of 01 with a TC 016 Doc. Code 80 Definer Codes AB. Input URC 0 to release the unpostable and cycle to post after
the TC 016. Monitor for posting. After the return posts, input a TC 016 and update the filing requirements to 990-PF.

The organization responds with a completed Form 990-PF:

URC 8 to release the unpostable. Ask Rejects to cancel the DLN.

Attach the Form 990 to back of the Form 990-PF and send the Form 990-PF through for processing.

.

The organization does not respond:

Update the BMF with a Form 990 filing requirement an EO Status of 01 with a TC 016 Doc. Code 80 Definer Codes AB. Input URC
0 to release the unpostable and cycle to post after the TC 016.

Monitor for posting. After the return posts, input a TC 016 and update the filing requirements to 990-PF.

If a Form 990-PF with the 60 - month termination box checked is received from Code & Edit, research EDS to determine if an
Advance Ruling Letter 2245 was issued. There will be no advance ruling date on EDS. Also research IDRS with CC INOLE to determine
if the EO Status is 25 and if there is an advance ruling date present. If no advance ruling date is present, it can be found
by reprinting the 2245 Letter through the Letter Generation system on the Inventory Control System Menu on EDS.

If an Advance Ruling Letter 2245 was issued to the organization as shown on EDS and the termination period began prior to
January 1, 2002, but Master File has not been updated, update the advance ruling date as indicated in the advance ruling letter
using CC EOREQ/EOCHG, TC 016 Doc. Code 80. It is not necessary to update the EO Status to 25 because the Termination Code
1 will update the status systemically. Edit Termination Code 1 on the return if Code & Edit has not already done so.

Caution:

It is imperative these instructions are followed. Otherwise, there is adverse impact on the taxpayer as well as other processing
areas.

If no advance ruling letter was issued to the organization, the EO Status is 25, and there is no advance ruling date on Master
File, notify the organization with Letter 4588C they must apply for an advance ruling to qualify for the 507(b)(1)(B) termination
per Publication 578. Also notify the organization they will receive a balance due notice. Input a TC 016 Definer Code B to
update the EO Status to 01. Circle out the Termination Code 1 on the return.

3.12.278.3.5.13
(01-01-2015)EO Status Code 26

Status Code 26 ("Termination/Merger "
) is used for the account which is no longer in existence when two exempt organizations are merged (both accounts were
exempt either by individual rulings or by a group ruling). All the EO filing requirements will be updated to zero.

Note:

When returning an account to Status 01, use the ruling date as the status date, if available.

When updating an account to EO Status Code 26, always input the x-reference EIN if available.

3.12.278.3.5.14
(01-01-2015)EO Status Code 28

Status Code 28 ("No longer a member of a group ruling"
) is input systemically if a parent account is placed into Status 29. All the EO filing requirements will be updated to
zero.

If an account is in Status Code 28 on Masterfile, update the account to Status 36 or 40. Status 40 should be used if the subsection
is 501(c)(3), (9) or (17). Status 36 should be used for all subsections other than 501(c)(3), (9) or (17).

An organization in Status 28 must file an application for exemption if their subsection is 03, 09, or 17. If these organizations
file a return, update the Status to 40 and post the return. If the organization in Status 28 has a subsection other than 03,
09, or 17, update the Status to 36 to post the return. If the organization has already filed for and received exempt status
as indicated on EDS, update the Status to 01, using the ruling date as the status date.

3.12.278.3.5.15
(01-01-2015)EO Status Code 29

Status Code 29 is used when a group ruling was dissolved. All the EO filing requirements will be updated to zero.

Do not place organization in Status 29 during campus processing. See IRM 3.13.12.12.7, Dissolving a Group Ruling for information on dissolving a group ruling.

3.12.278.3.5.16
(01-01-2015)EO Status Codes 30 - 33

Status Code 30 applies to churches, their integrated auxiliaries, and conventions or associations of churches as described in IRC 501(c)(3)
who voluntarily file Form 990 though not required to file returns or apply for exemption.

When the church without an exemption files the Form 990, it will unpost as a UPC 366.

Establish the EO section with EO Status Code 30 using the current month and year as the status date with TC 016 Doc. Code
80 Definer Code B. No filing requirement is necessary. Status Code 30 will bypass the UPC 329 check and allow the Form 990
to post in the future.

Caution:

If a church has filed for and received an exemption, do not update the EO Status from 01 to 30

Note:

Beginning January 2004 a Form 990-T or a payment for a Form 990-T will automatically post to account in EO Status 30 if the
name control and EIN on the return or payment match the name control and EIN on Master File. A Form 990-T filing requirement
will not be added to the module.

Status Code 31 applies to small organizations other than churches and private foundations who normally have annual gross receipts less then
$5,000 and who voluntarily file Form 990 though not required to file returns or apply for exemption.

When these types of small organizations file their Form 990, it will unpost as a UPC 366.

Establish the EO section with EO Status Code 31 using the current month and year as the status date with TC 016 Doc. Code
80 Definer CodeAB and add the appropriate filing requirement.

If an organization applied under a particular subsection and was denied (Status 70), do not update the Status to 31 under
the denied subsection.

Caution:

Do not update an account to EO Status 31 unless the following criteria is met: During the first taxable year the organization
received gross receipts of $7,500 or less, or during the first two taxable years, the organization's aggregate gross receipts
were $12,000 or less, or during the first three taxable years or if the organization is in existence for three or more years,
the aggregate gross receipts received by the organization in the immediately preceding two taxable years plus the current
year are $15,000 or less.

Note:

. Status 31 applies to 501(c)(3) organizations (excluding churches) with gross receipts normally $5,000 or less which have filed
a Form 990.

Status 31 Transcripts will be issued weekly if a Form 990 posts to an account in EO Status 31 and the gross receipts are $50,000 or greater. The
transcripts will be titled "Status 31 over $50,000"
and contain the following information: organization name, EIN, tax period of the Form 990 and gross receipts. Process
the transcripts as follows:

Research CC BRTVU to determine the gross receipts for the last three years.

An organization's gross receipts are considered normally not more than $5,000 if:During the first taxable year it receives gross receipts of $7,500 or less, During the first two taxable years, its aggregate gross receipts are $12,000 or less, andDuring the first three taxable years or if the organizations was in existence for three or more years, the aggregate gross
receipts received by the organization in the immediately preceding two taxable years plus the current year are $15,000 or
less.

If the organization's gross receipts are found to be greater than $5,000, update the EO Status Code to 40 with a TC 016 Doc.
Code 80 Definer Code B if the subsection is 03/09/17/20. If the subsection is other than 03/09/17/20, update the EO Status
to 36.

If the organization's gross receipts are found to be less than $5,000, continue processing.

Check EDS for any change in the organization's status code. Update if necessary with a TC 016 Doc. Code 80 Definer Code B.

After the transcript is worked, destroy per local service center procedures.

Status Code 32 applies to CP 140s and CP 144s with no response to the notice. If no TC 150, 460, 590, 591, 594-599 has posted to a tax module
with a Form 990 filing requirement within 90 days of the issuance of the notice, the system will automatically update the
EO Status to 32 with a TC 016 Doc. Code 80 Definer Code B.

Note:

Due to the difference between the receipt of a return and the posting of a return, EO Status Code 32 may not be updated to
01 Status. If a return is received and account is in Status 32, update the account to Status 01.

Note:

Status Code 32 should not be used after January 1, 2008 since the CP 140 and 144 notices are obsolete.

Status Code 33 applies to foreign private foundations described in IRC 4948(b) which are not required to apply for exemption but are required
to file a Form 990-PF to pay 4% tax on gross investment income derived from sources with the United States.

When these types of foreign private foundations file their Form 990-PF, it will unpost as UPC 366.

Establish the EO section with EO Status Code of 33 using the current month and year as the status date with TC 016 Doc. Code
80 Definer B. No filing requirement is necessary. Status Code 33 will bypass the UPC 329 and will allow the Form 990-PF to
post in the future.

3.12.278.3.5.17
(01-01-2015)EO Status Code 34

Status Code 34 applies to political organizations operating under the rules of IRC 527. Generally, there are two types of 527 organizations:

Type

Description

Federal Organizations

FEC political committee: A political organization (including federal candidate committees, political party committees and
PACs) which is required to report as a political committee under the Federal Election Campaign Act.

Other federal political organization: A political organization attempting to influence federal elections which is not required
to report as a political committee under the Federal Election Campaign Act.

State/Local Organizations

Candidate committee: A campaign committee of a state or local candidate.

Party committee: A state or local committee of a political party.

Qualified state or local political organization (QSLPO): A state or local committee whose political activities relate solely
to a state or local public office, is subject to state law which requires it to report to a state agency information about
contributions and expenditures, makes reports publicly available, and no federal candidate or office holder controls it, participates
in its direction, or solicits contributions for it.

Caucus or association: a group of state or local officials attempting to influence elections.

Other political organization: any other state or local political organization.

Filing Requirements: The filing requirements in the chart below apply to those tax-exempt political organizations which receive or expect to receive
$25,000 or more in gross receipts in any taxable year.

If the Organization is a

It May Be Required to File

FEC political committee, state or local candidate committee or state or local committee of a political party,

Form 1120POL.

Qualified state or local political organization (QSLPO)*,

Form 8871; Form 1120POL; and Form 990.

Caucus or association of state or local officials*,

Form 8871; Form 8872; and Form 1120POL.

Any other political organization, including other federal political organizations and other state or local political organizations,

Form 8871; Form 8872; Form 1120POL; and Form 990 or Form 990-EZ.

*An organization may be both a QSLPO and a caucus or association of state or local officials. If so, it is not required to
file Form 8872 and Form 990.

Note:

If the political organization does not have gross receipts of at least $25,000, it must file Form 1120 POL if it has taxable
income after taking the $100 specific deduction for any taxable year.

See IRM 3.13.12.14.1, Form 8871/8453X for Form 8871/8453X instructions. See IRM 3.13.12.14.3, Form 8872 for Form 8872 instructions.

3.12.278.3.5.18
(01-01-2015)EO Status Code 35

Status Code 35 applies to foreign entities the IRS has agreed are exempt by treaty with the participating country but have no foundation
code. For example, Canadian charities would be set up on Master File with an EO Status Code of 35.

When this type of foreign entity files a Form 990-PF, Form 990 or Form 990-T, it will unpost as UPC 366.

Establish the EO section with EO Status Code 35 using the current month and year as the status date with TC 016 Doc. Code
80 Definer B. No filing requirement is necessary. Status Code 35 will bypass the UPC 329 check and will allow the return to
post in the future.

3.12.278.3.5.19
(01-01-2015)EO Status Code 36

Status Code 36 applies to Form 990 filers with a Subsection other than (3), (9), (17), or (20).

If

Then

The return is an Unpostable 366:

Determine the classification code using Document 6379 (II-3) if the return is marked with a Subsection other than (3), (9),
(17) or (20). Establish the EO Section with a Form 990FR of 01, EO Status Code 36 using the current month and year as the
status date, FYM, subsection code as indicated on the return, classification code and remarks with a TC 016 Doc. Code 80 Definer
Codes AB.

If the return does not have a subsection, put the account in Status 40 using a TC 016, Definer code B. URC 0 code the unpostable
and cycle to post after the TC 016.

Note:

Beginning January 2004 a Form 990-T or a payment for a Form 990-T will automatically post to account in EO Status 36 if the
name control and EIN on the return or payment match the name control and EIN on Master File and the Type or Organization code
is 3 and a Form 990 FRC of 01/02/04/06 or Form 990-PF FRC of 01. A Form 990-T filing requirement will be added to the module.

3.12.278.3.5.20
(01-01-2015)EO Status Code 40

Use Status 40 to create an EO section for a return marked with SS 03, 09, or 17 which has not been granted an exemption at
the time the return was filed.

Each month (except January) "Status 40"
information is downloaded from Master File to the EO Status 40 System in Ogden.

If Forms 990 (SS 03/09/17/20) or Forms 990-PF (other than 4947(a)(1)) are received and research does not reveal an exemption,
use Status 40. If a BMF FRC for Forms 1041, 1065 or 1120 is on the BMF account, zero out the applicable FRC.

3.12.278.3.5.21
(01-01-2015)EO Status Codes 41 and 42

Status Code 41 ("Failed to Reply to Solicitation for Application"
) is used by Entity for purported 501(c)(3)/(9)/(17)/(20) organizations which have finished the Status 40 process. When
processing "Status 40"
cases, the organization is contacted with a CP 120 to solicit an application for exemption. If the organization does not
apply and receive a form exemption, the system will automatically update the account to Status 41. When inputting this status,
a filing requirement for Forms 1041or 1120 will be input. . If an organization in Status Code 41 files a subsequent return, process following the specific instructions for the type
of unpostable.

Status Code 42 will no longer be used as of September 2011.

3.12.278.3.5.22
(01-01-2015)Eo Status Codes 70 - 72

Status Code 70 ("Exemption Denied "
) is input by Cincinnati when, on the merits of the application, an exemption cannot be granted. This status will generate
a Form 1120 filing requirement of 01.

Status Code 71 application is incomplete and a response to a request was not received.i This status will generate a Form 1120 filing

Status Code 72 ("Refusal to Rule "
) is input by Cincinnati when the applicant is unable to furnish a detailed description of its planned activities. This
description would clearly indicate whether the organization was exempt or not. This status will generate a Form 1120 filing
requirement of 01.

3.12.278.3.5.23
(01-01-2015)EO Status Code 97

Status 97 is automatically updated on Master File when an organization fails to file Forms 990/990EZ, 990-N or 990–PF for three consecutive
years. All EO filing requirements will be removed. This status will automatically generate a Form 1120 filing requirement.

An account in Status 97 is required to file Form 1120 or 1041 or re-apply for tax exempt status by filing Form 1023 or 1024
and paying all applicable fees.

Note:

Do not update any accounts to or from Status 97. If any correspondence is received stating erroneous revocation and requesting reinstatement
and research indicates the account should be updated, close the case as no action (URC 0 to post return) and forward to the
TEGE Analyst at M/S 1110. Do not update the status.

When the EO status must be changed from Status 97 to any other EO status for a central organization (Affiliation code 6),
IT programmers for the GEN file must take action before any updates will post to Masterfile.

Once a need for status change has been identified, ensure all subordinate groups of the GEN have been removed or are in an
inactive status.

Input TC 590 CC 020 on Form 1120.

Inform the TEGE analyst with oversight of this program of the Employer Identification Number (EIN) and GEN.

No additional actions should be taken until further instructions are given by the TEGE analyst.

Once the additional instructions are sent, the actions must be taken within 24 hours of receipt. If actions are not taken
timely, the entire update process will be in jeopardy.

Final closing instructions will be different for each case and must be given on a case by case basis.

Once the Central organization had been re-established and all final actions have posted to masterfile, all subordinates must
be added back to the GEN.

3.12.278.3.5.25
(01-01-2015)EO Status Codes 98 and 99

Status 98 is input when an organization is identified as a terrorist organization by National Office. This status will automatically
generate a Form 1120 filing requirement. When an organization Status 98 files an exempt organization return, it will unpost.
Process the unpostable as follows:

URC 8 and request Rejects cancel the DLN.

Give the return to the Lead so the return can be forwarded to EO Classification in Dallas.

Status 99 is input when an organization in EO Status 22, 41, 70-72 files another exempt organization return and they still do not have
an exemption. The status will automatically generate a Form 1120 filing requirement. All exempt organization returns and any
associated payments filed in future tax years will automatically post . This status code will replace the procedure of shelving
status 22, 41, 70-72 returns which could not be posted in the past. EO or SBSE Examination will use Status 99 to determine
what organizations require an audit. When a return unposts because the Status is 22, 41, 70-72, process as follows:

Research EDS to determine if the organization has filed a new application for exemption is pending on EDS. If new application
is pending, input a TC 016 Definer Codes AB to update the Status Code to 40 and remove the Form 1120 filing requirement. URC
0 to post the return and cycle to post after the TC 016.

Note:

EO applications are imaged and available through MEDS Documentum.

If EDS shows an F case, input a TC 016 Doc. Code 80 Definer Codes AB to remove the 1120 filing requirement and add the information
on EDS to Master File. URC 0 to post the return and cycle to post after the TC 016.

If EDS does not show a good exemption, correspond with the organization using the 3909C Letter for Status 41 organizations
or the 3877C Letter for Status 70-72 organizations. If a determination letter is provided ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ If a determination
letter is not provided, or a new application for exemption submitted, or there is no reply, update the EO Status to 99 with
a TC 016 Doc. Code 80 Definer Code B; URC 0 to post the return and cycle to post after the TC 016. If the organization provides
information indicating exemption, update Master File per the organization's response with a TC 016; URC 0 to post the return
and cycle to post after the TC 016. Occasionally, both Form 1120 and 1041 filing requirements will post to the account. If
this occurs, remove the EO subsection with TC 022. You may then remove the incompatible filing requirement and close the unpostable
with URC 0.

3.12.278.3.6
(01-01-2015)EO Foundation Codes

The following table is a list of EO Foundation Codes:

Foundation Codes

Description

00

4947(a)(1)

02

Exempt Operating Foundation with an ruling under 4940(d)(2)

03

Private Operating Foundation

04

Private Non-Operating Foundation

09

Suspense (a specific type not identified)

10

Church - IRC 170(b)(1)(A)(i)

11

School - IRC 170(b)(1)(A)(ii)

12

Hospital - IRC 170(b)(1)(A)(iii)

13

Organizations operated for the benefit of a College or University -170(b)(1)(A)(iv)

14

Federal State or Local Government unit (IRC 170(b)(1)(A)(v)

15

Organization receiving support from governmental unit or general public (IRC 170(b)(1)(A)(vi)

Note:

For instructions on inputting the Affiliation Code (AF) with CC EOREQ/EOCHG, See IRM 3.13.12.6.16, Affiliation Code.

3.12.278.3.8
(01-01-2015)Type of Organization

The following table lists type of organizations:

Type of Organization

Description

1

Corporation

2

Trust

3

Cooperative

4

Partnership

5

Association

6

Non-Exempt Charitable Trust - NECT

3.12.278.3.9
(01-01-2015)Processing Time Frames

The GUF 1140 report is accessed on Control-D. The GUF 1140 report shows all new unpostables received in GUF.

Unpostables should be closed within 60 days of appearing on the 1140 report or they will age.

The acceptable old age for Exempt Organization unpostables is 10%.

3.12.278.3.10
(01-01-2015)Accessing the GUF

GUF is accessed by the employee via IDRS. Sign on to IDRS using your password prior to attempting GUF access. You are authorized
to access only those accounts necessary to resolve your assigned cases. You are forbidden to access your own or your spouse's
account, the account of a friend, relative or coworker, or any account in which you have a financial interest.

Employees who engage in unauthorized access or browsing of tax accounts are subject to disciplinary actions and possible criminal
prosecution. BROWSING is defined as looking at a tax account to satisfy a personal curiosity or for fraudulent reasons.

3.12.278.3.10.1
(01-01-2015)Unpostable Command Codes

CC UPTIN displays all open unpostables for a specific TIN and will maintain the unpostable on its file for display purposes for 90
days after it is closed.

CC UPBAT is used to batch (mass) close non-RPS unpostable cases.

CC UPASG is used to assign or reassign an unpostable case or group of unpostable cases.

CC UPCAS/UPCASZ, is used to suspend a case, request research, order missing documents and add history items to the screen display. EO Clerical
should use the following procedures to obtain missing documents:

If the Form 4251 is received without the return, check SEIN to see if return is available before proceeding with the instructions
below.

If the first or second request does not have a document attached, check to see if the document is charged out to another area.
If the document is charged out, contact the area by phone for a copy of the return. Otherwise, take no action.

If the third request does not have a document attached, initiate a special search to Files by stamping in red "SPECIAL SEARCH"
on the Form 4251. Indicate SPECIAL SEARCH in the Remarks of CC UPCAS.

The fourth request automatically results in an URC 8 to Rejects have the DLN cancelled.

Note:

Tax Examiners should not ask Rejects to do a special search on the fourth request.

CC UPDIS/UPRES is valid for all Master Files, and is used to display an unpostable record.

When UPDIS is input, the automatic screen display shown will be UPRES. UPDIS will display the unpostable information which
was previously displayed on UPCAS.

The following table lists the Unpostable Resolution Codes for CC UPRES.

URC

USE

0

No change made to transaction; the information on UPCAS will match the Master File.

1

Transaction to be re - input with same DLN.

2

Void - Transaction to be deleted. Creates IDRS control base.

6

Change name control; add name line or identification number; or a combination of TIN, name control, transaction code, transaction
date, computer condition code, tax period or MFT (if transaction code and tax class are compatible.

8

A transaction will be corrected by Rejects or when the DLN should be voided.

A

Automatic correction of name control.

B

Special closure made by the Unpostable-GUF.

D

VOID - Transaction deleted when no further action is necessary. Does not create an IDRS control base.

The valid unpostable command code definers and definer- modifiers are as follows:

Display unpostable case. When CC UPDIS is input the displayed CC UPRES will be shown displaying all previous standard UPCAS
information. Also, if there are other cases on CC UPTIN with the same TIN as the unpostable case, GUF will display the message
"other cases with the same TIN on UPTIN."

Places or updates a case in suspense status. Valid on all Master Files.

M

S

Entity module - for valid and invalid account MRS - display.

M

T

Entity module - for valid and invalid account MRS - hard copy.

D

1

Original request for charge - out document (Form 4251).

D

2

2nd request for charge - out document.

D

3

3rd request for charge - out document.

D

4

4th request (special search) Form 4251 and GUF will automatically close the case with URC 8.

S

B

Places or updates a case in suspense status because of a document request not directly related to the unpostable case. Valid
on all Master Files.Note: Tax Examiners will need to input in the remarks field the specific type of document you are requesting.

S

C

Places or updates a case in suspense status because of correspondence action with the taxpayer. Valid on all Master Files.

Z

blank

Request to display update/modify an unpostable history section.

UPRES

D

blank

Transaction to be deleted (voided). Valid on all Master Files. NO IDRS control base established.

0

blank

No change made to unpostable transaction. Attempt to repost at Master File. Valid on all Master Files. GUF will validate all
TIN and name controls through the NAP for UPCs 151, 152, 153, 156, 301, 303, 701, and 703 only. All TINS and name controls
must validate or GUF will not allow the closure.

0

B

Use to bypass the NAP checks.

1

blank

Transaction to be re–input. Valid on all Master Files except CAWR and PMF.

2

blank

Transaction to be deleted (voided). Valid on all Master Files. An IDRS control base is established.

Transaction sent to reject register or error resolution system (ERS) suspense status. Valid on all Master Files except CAWR,
IRAF (TC 150) and PMF. NOTE: It will not be necessary to close the unpostable case with URC 8 for 4th request action. GUF
will automatically close the case with URC 8 with CC UPCAS with Definer D and Definer-Modifier 4 is input.

A

blank

Correction of name control, using Master File name control. Valid on all Master Files but only for Unpostable Code 003 (CAWR),
152, and 156 (IMF), 303 (BMF), 703 (IRAF). If UPC 152/156, the TC must be 140, 150, or 430 and the entity code must be a 2
or 3. NOTE: The input definer URC A will convert and equal URC 6 with the unpostable record is updated.

B

blank

Special closure of open, assigned cases. Valid only IMF and BMF.

UPTIN

blank

NONE

Displays all open and closed (up to 3 months) unpostables.

3.12.278.3.10.2
(01-01-2015)Unpostable Resolution Codes (URC)

Unpostable resolution codes (URC) are used as definers with CC UPRES to correct/close an unpostable case.

The valid URCs for MF unpostables are listed below along with a brief definition.

URC A is used to correct unpostable name control to read exactly the same as the Master File name control.

URC B - See IRM 3.12.32, General Unpostables.

URC D deletes (voids) transactions and is valid for all Master Files. A URC D removes the record from the SCUPMF and should be used for transactions with no money amounts. Use a URC D to void a transaction when no further action is necessary. A URC D will not create an IDRS control base. Always enter remarks (line 8 of UPRES) when closing an unpostable with URC D. If remarks are not entered, the system will not accept the correction and display an error message. Remarks must state why
the case is being voided with a URC D.

URC 0 allows the unpostable record to attempt to post again with no change at the Master File.

URC 1 allows transactions to be re-input with the same DLN. It is valid for all Master Files except CAWR and PMF. A URC 1 removes the record from the S.C. Unpostables Master File (SCUPMF). These records are not corrected (at this time) for an
attempted second posting at Master File as would URC 0, 5 and 6.

Each unpostable record which is corrected with URC 1 is placed in "re-input"
status on the Service Center Control Files (SCCF). If the document is to be re-input, enter Nullify Area Code 01, prepare
Form 3893 and route to Batching for input. No further action is needed on the SCCF. If the document is not to be re-input,
enter the appropriate Nullify Area Code and route the Nullified Distribution List to the function which is responsible for
the next action.

The other times URC 1 can be used are when there are program problems or when an IRA TC 150 needs to be input to IMF.

Do not route re-inputs (URC 1) documents to Data control, except at the request of the function.

Always enter remarks (Line 8 of CC UPRES) when closing an unpostable with URC 1. If remarks are not entered, the system will not accept the correction and display an error message. Remarks must state why
the unpostable is being closed with URC 1.

URC 2 deletes (voids) a transaction and creates an IDRS control base and should be used for transactions with no money amounts.

Changing MFT. The following table shows MFT, Doc. Code and Form for BMF.

MFT Code

Doc. Code

Form

02

20

1120POL

01

41

941

02

09

1120A

02

10

1120

02

16

1120S

06

65

1065

09

11

CT-1

10

40

940

11

43

943

12

25

1042

14

49

944

15

23

8752

16

37/97/44

945

34

93

990T

36

81

1041A

37

83

5227

44

91

990PF

46

61

8038

46

62

8038G

46

72

8038GC

46

74

8038T

47

61

Form 8871

49

62

Form 8872

50

71

4720

56

88

990BL

67

90

990

67

09

990EZ

67

89

990N

67

92

990EZ (2008 revision)

67

93

990 (2008 revision)

72

02

CT-2

76

35

5330

77

29

706GST

78

59

706GSD

84

01

Form 8703

85

85

Form 8038-B

86

86

Form 8038-TC

URC 8 is used to reject a transaction (see IRM 3.12.32, General Unpostables). Attach a completed Form 13271 to the document.

If the document is not a final return and a CCC F is edited on the return , request Rejects remove the CCC F. Indicate on
the Form 13271 the CCC F should be removed and circle out the CCC F on the return.

Note:

When using URC 1, 2 or 8, you must include a nullification code and remarks on the CC UPRES screen. SeeIRM 3.12.278.3.10.4,
Nullified Area Codes for the Nullified Area Codes.

3.12.278.3.10.3
(01-01-2015)Unpostable Status Codes

The use of the command codes and definers, and definer modifiers will establish or update the "Status Code"
of an unpostable case. The status code identifies what action was taken on an unpostable case. The status date indicates
when this action was taken.

The following is a list of status codes and their definitions:

A - assigned, not corrected

C - corrected, not removed from the SCUPMF

H - Quality Assurance hold

S - Suspense, input when return has to be held (e.g., corresponding with taxpayer)

Q - Accepted by Quality Assurance

The status code and date will appear on line two of the CC UPCAS screen display following the literal "ST"
.

Note:

Refer to IRM 3.12.32, General Unpostables, for more detailed information concerning status codes and dates.

3.12.278.3.10.4
(01-01-2015)Nullified Area Codes

Whenever closing an unpostable with URC 1, 2, or 8, a nullified area code must be entered to identify the receiving area for
closed unpostables. A Nullified Distribution listing will be printed for each of these areas based on nullification code used.

The nullify area code is entered on Line 2, in positions 6 and 7 of the new CC UPRES screen.

If an nullification code is not entered, an error message will be displayed.

The table below shows the nullify area codes which can be used for specific resolution codes.

See Nullified Distribution Listing procedures in IRM 3.12.32, General Unpostables for further information.

Resolution Code

Nullify-Definer (Area) Code

Receiving Area Literal

Comments

1

01

Re-input - No further action

Only use when case is being re-input

23

Dishonored checks

30

FTD Function - Accounting

31

Data Controls

32

RACS

41

Accounting

50

Customer Service

D

Blank/01

Void - No further action

Only used on cases which do not need to be worked by any other area.

2

02

Adjustments

03

Collection/SCCB

04

Statute

Only used for cases which need to be closed to Statutes.

05

Examination

Only used for cases closed to SC Examination.

06

IRP

07

Disclosure Officer

08

Taxpayer Relations

09

Notice/Output Review

10

Unpostables

Should only include cases prepared by Unpostables

11 *

Auto-Void-Emp# problem

Should only include cases which are auto voided.

12

Refund Inquiry

13*

Manual Void-Emp# problem.

Should only include cases manually voided.

14

CAF

15

CAWR

16

URP

17

CI

19

Collection DO

20

Exam DO

21

Taxpayer Service DO

22

SCWR–SC

23

Dishonored Checks

24

Technical

25

Entity

40

Unidentified/Excess Collections

41

Accounting

42

Transhipped to PSC

43

TEGE

44

PRP

45

Electronic Filing

46

CI/DO

47

TEGE AO

48

PRP/DO

49

ERS/Rejects

50

Customer Service

8

01

Reject Resolution

Should only include cases to be resolved by Rejects. NO OTHER AREA WILL WORK CASE.

02

Adjustments

03

Collection/SCCB

04

Statutes

05

Examination

06

IRP

07

Disclosure Office

08

Taxpayer Relations

09

Notices/Output Review

12

Taxpayer Service refund inquiry

Can be used for refund inquiry cases which go to Accounting or Taxpayer Service. Notate area in REMARKS for easy association.

14

CAF

15

CAWR

16

URP

17

CI

19

Collection DO

20

Exam DO

21

TPS DO

22

SCWR–SC

23

Dishonored Checks

24

Technical

25

Entity

40

Unidentified/Excess Collection

41

Accounting

42

Transhipped to PSC

43

TEGE

44

PRP

45

Special EPMF Processing

46

CIB/DO

47

EP/EP DO

48

PRP/DO

49

ERS/Rejects

50

Customer Service

* Nullify Area Code 11 and 13 are computer generated for the purpose of routing nullified unpostable cases for which a control
base cannot be established due to a problem with the IDRS employee number. These codes are not to be input by an individual
tax examiner.

Photocopy any unpostable case which needs to be routed to an office outside the campus.

To ensure proper control, do the following steps:

Form 3499 is used to route documents. Three types were prepared in advance.

If you are sending cases to Cincinnati which are out of business, mergers, or amendments, use the Form 3499 which has IRS
TEGE, PO BOX 2508, CINCINNATI, OHIO, 45201 in the "TO"
section at the top of the form. At the bottom of the form, circle any action codes if necessary, check the appropriate
type of case in "Remarks"
, your name in the "From"
section, and indicate your location, phone and date.

If the taxpayer is requesting a determination letter, use the Form 3499 which has IRS TEGE, 550 MAIN ST, RM 4024, ATTN: RECORDS
UNIT, CINCINNATI, OHIO, 45201 in the "TO"
section at the top of the form. At the bottom of the form, circle any action codes if necessary, check the appropriate
type of case in "Remarks"
, your name in the "From"
section, and indicate your location, phone and date.

If you are forwarding a Form 1023, Form 1024, Form 8718, or Form 8734, use the Form 3499 which has CINCINNATI SERVICE CENTER,
PO BOX 12192, COVINGTON, KY, 41012, in the "TO"
section at the top of the form. At the bottom of the form, circle any action codes if necessary, check the appropriate
type of case in "Remarks"
, your name in the "From"
section, and indicate your location, phone and date.

Route the copies of returns and Forms 3499 to the Dallas Office or Cincinnati using Form 3210, Document Transmittal. List
each case on the Form 3210.

Retain a suspense copy of each Form 3499 and the Form 3210 on which they were sent.

If you are expecting a response from Cincinnati or Dallas, suspend the unpostable case using Command Code UPCAS, Definer "S"
, modifier "A"
, and enter remarks. Upon receipt of the case back from the Dallas Area Office/Cincinnati, follow their instructions for
final disposition of the case. Since Dallas, in many cases, may attempt to contact the organization to determine its proper
status, it may take some time for Dallas to close each case.

To recharge the document to the Dallas Area Office/Cincinnati, if necessary, use CC ESTABDT via IDRS. The computer will generate
the necessary paperwork for Files.

3.12.278.5
(01-01-2015)Editing Returns

In the unpostable resolution process, it may be necessary to edit entity information on the return. Refer to IRM 3.11.12,
Exempt Organization returns for the placement of edited information on the return.

If you receive correspondence with a return attached while working any unpostable, take the following actions:

Edit the correct name control, EIN, Tax period, Received date from the return and TE date stamp

Edit CCC RV when appropriate.

Edit the Correspondence Received Date (CRD) and Correspondence Code on the form.

Edit a Computer Condition Code (CCC) of 3 in the upper right margin of the return if necessary.