The
Automated
Underreporter
(AUR)
program
is
separated
into
three
phases:
Case
Analysis
(may
also
be
referred
to
as
Screening).
Response,
includes
both
CP
2501
and
CP
2000.
Statutory
Notice,
legally
required
final
notice.
Note:
See
Exhibit
4.19.2-1,
Glossary
,
that
includes
terms,
acronyms
and
abbreviations
used
in
AUR.
The
Case
Analysis
phase
is
the
initial
screening
of
a
case.
A
technical
determination
is
made
if:
A
notice
needs
to
be
generated.
A
case
needs
to
be
referred
and/or
researched.
A
case
can
be
closed
without
further
action.
A
case
should
be
transferred
to
another
function.
There
are
three
other
processes
that
are
completed
in
the
Case
Analysis
phase.
The
three
processes
are:
Correction
of
CP
2000
rejects.
Remail
of
undeliverable
or
erroneous
notices.
Completion
of
previously
referred
or
incomplete
cases.
The
clerical
functions
to
support
these
processes
are:
Building
batches
IDRS
input
of
manual
assessments
identified
by
tax
examiners
Associating
returns
and/or
transcripts
to
case
files
Refiling
closed
cases
Verifying
Process
Codes
Disassembling
batches
Associating
the
case
folder
and
return
Pulling
notices
identified
as
erroneous
from
the
notice
mailout
Pulling
and
batching
reject
cases
Preparing
cases
for
transfer
or
referral
to
other
areas
Setting
up
suspense
files
in
Notice
Date/CSN
order
The
Response
Phase
of
the
AUR
Program
is
the
resolution
of
the
AUR
issue
addressed
in
the:
CP
2501,
Initial
Contact
Letter,
CP
2000,
Notice
Proposing
Adjustment
to
Income,
Payments,
or
Credits,
Subsequent
30
Day
Letter
(e.g.,
Letter
2625C,
Letter
2626C,
Letter
1802C,
Letter
2627C),
or
Recomputed
CP
2000.
See
Exhibit
4.19.2-4
for
an
example
of
the
redesigned
CP
2000
for
TY
2003.
Note:
See
Exhibit
4.19.2-5
for
an
example
of
the
redesigned
CP
2501
for
TY
2003.
The
CP
2501
or
the
CP
2000
issues
can
be
resolved
by
a
response
from
the
taxpayer.
If
the
response
does
not
resolve
the
issue,
there
is
no
response,
or
the
notice
is
undeliverable,
a
CP
2000
notice
or
a
Statutory
Notice
will
be
issued.
The
response
may
result
in:
Closure
by
refile
Assessment
Miscellaneous
Referral
Research
(Unit
Suspense)
Transfer
to
another
area
(e.g.,
Examination
or
Criminal
Investigation)
Additional
correspondence
to
resolve
the
issue
The
clerical
functions
to
support
these
processes
are:
Building
batches,
Associating
responses
to
the
CP
2501s,
the
CP
2000s,
recomputed
notices,
and
letters
with
the
case
files,
Verifying
Process
Codes,
Disassembling
Batches,
Assessing
tax
deficiencies
to
taxpayers'
accounts,
Preparing
cases
for
transfer
or
referral
to
other
areas,
Mailing
additional
correspondence,
and
Sending
closed
cases
to
the
Federal
Records
Centers
(FRC)
to
be
refiled.
The
Statutory
Notice
phase
of
the
AUR
Program
is
the
resolution
of
the
AUR
issue
addressed
in
the
Statutory
Notice
of
Deficiency
(3219
Letter)
and
Waiver
(Form
5564).
See
Exhibit
4.19.2-12
for
examples
of
the
Statutory
Notice
cover
sheet,
3219
Letter,
and
Form
5564.
The
Statutory
Notice
issues
can
be
resolved
by
a
response
from
the
taxpayer.
The
case
is
defaulted
when:
Responses
from
the
taxpayer
do
not
resolve
the
issue(s),
and
the
Statutory
suspense
period
has
expired.
No
response
is
received.
The
Post
Office
has
returned
the
notice
as
undeliverable
and
IRS
has
no
record
of
a
better
address.
See
IRM
4.19.2.3.13
for
instructions
on
undeliverable
Statutory
Notices.
Note:
See
Exhibit
4.19.2-2,
Control
Flowchart.
4.19.2.1.1
(09-01-2004)
Taxpayer
Advocate
Service
Even
though
the
IRS
strives
to
improve
its
systems
and
provide
better
service,
some
taxpayers
still
have
difficulty
in
getting
solutions
to
their
problems
or
appropriate,
timely
responses
to
their
inquiries.
The
purpose
of
the
Taxpayer
Advocate
Service
(TAS)
is
to
give
taxpayers
someone
to
speak
for
them
within
the
IRS.
Service
Level
Agreements
between
TAS
and
the
Operating
Divisions
are
available
at
the
TAS
web
site.
4.19.2.2
(09-01-2003)
General
Case
Processing
This
section
deals
with
general
information
about
the
AUR
system,
the
Underreporter
program
and
case
processing.
4.19.2.2.1
(09-01-2004)
Chargeouts
(Form
4251)
Initial
chargeouts
(Form
4251)
are
produced
and
routed
to
the
Campus
Files
function.
See
Exhibit
4.19.2-8,
Form
4251.
If
the
return
has
not
been
retired
to
the
Federal
Records
Center
(FRC),
Campus
Document
Retention,
Files
Function,
pulls
the
return
and
routes
it
to
the
AUR
Operation.
If
the
return
has
been
retired
to
the
FRC,
Campus
Document
Retention,
Files
Function,
routes
the
chargeout
to
the
appropriate
FRC.
The
FRC
pulls
the
return
and
routes
it
to
the
AUR
Operation.
If
the
return
is
not
available,
the
FRC
clerk
notes
the
available
chargeout
information
on
the
Requestor
Copy.
The
Requestor
Copy
is
forwarded
to
the
appropriate
campus,
either
attached
to
the
return,
or
with
the
chargeout
information.
Chargeouts
with
a
File
Location
Code
of
14,
16,
35,
38,
64,
72,
75,
76,
92,
93
and
98,
designating
Electronically
Filed
(ELF)
returns,
are
printed
and
routed
to
the
Underreporter
Operation
by
Computer
Services.
Chargeouts
with
Document
Code
07,
which
designates
1040EZ
returns,
Document
Code
08,
and
Document
Code
28,
which
designate
1040EZ-TEL
returns,
are
printed
and
routed
to
the
AUR
Operation
by
Computer
Services.
Treat
the
chargeout
as
if
a
tax
return
was
attached
and
build
the
case
to
the
appropriate
batch.
The
tax
examiners
work
these
cases
with
the
tax
return
information
that
is
on
the
AUR
system.
Exception:
Auto-Generated
Notice
cases
will
not
generate
chargeouts.
4.19.2.2.2
(09-01-2003)
Complete
Cases
A
complete
case
includes
the
following:
A
tax
return
(or
tax
return
data
on
the
AUR
system),
Information
return
(IR)
data,
and
Tax
account
information.
Tax
returns
and
chargeouts
are
forwarded
to
the
AUR
Program
for
sorting,
batching
and
case
control
based
on
workload
demands.
4.19.2.2.3
(09-01-2003)
Bar
Coding
The
bar
code
printed
on
the
Form
4251
contains
the
SSN
and
tax
year
of
the
associated
case.
The
bar
code
is
scanned
to
build
batches
in
all
phases
of
the
program
and
can
be
used
to
verify
and
update
the
processing
of
cases
(e.g.,
batch
disassembly
of
cases
by
process
code).
If
response
batches
are
built
using
only
the
taxpayer
correspondence
as
the
input
document,
the
SSN
cannot
be
scanned;
the
SSN
must
be
key
entered.
Note:
It
is
important
not
to
dispose
of
Forms
4251
until
a
case
is
closed.
Keep
the
Form
4251
in
the
front
of
the
case
file
with
the
bar
code
visible
so
it
can
be
scanned
easily.
If
a
Form
4251
needed
for
processing
is
inadvertently
thrown
away,
follow
Campus
direction
to
create
a
substitute.
The
AUR
bar
code
on
the
CP
2501,
CP
2000/Recomp,
and
Statutory
Notice
contains
the
following:
SSN
in
the
first
position
Tax
Year
after
the
SSN
An
indicator,
in
the
final
position.
The
indicators
identify
the
copy
of
the
notice
and
are:
1
for
primary
taxpayer
2
for
the
spouse
or
secondary
taxpayer.
3
for
Power
of
Attorney
(POA).
4.19.2.2.4
(09-01-2004)
Case
Labels
Labels
are
initially
produced
for
cases
that
receive
a
CP
2000
Batch
Type
50,
a
CP
2501
Batch
Type
40,
or
a
Research
Request
Batch
Type
34
case
sequence
number
(CSN).
The
following
is
included
on
the
case
label:
Bar
code
Social
Security
Number
(SSN)
Taxpayer's
name
Case
Sequence
Number
(CSN)
Tax
Year
Exception:
Auto-Generated
Notice
cases
will
not
generate
case
labels
for
505xx
suspense.
The
labels
are
generated
during
the
weekend
batch
runs
and
routed
to
Machine
Services
to
be
attached
to
the
folders.
The
folders
are
received
by
batch
type
and
CP
notice
date,
if
applicable.
Verify
that
the
information
on
the
folder
matches
the
case
Place
the
case
contents
inside
the
case
folder,
and;
Place
the
completed
case
folder
-
keeping
in
strict
CSN
order
-
in
the
appropriate
suspense
file.
Subsequent
labels
are
produced
when
cases
are
moved
to
Letter
Suspense
Batch
Type
47,
Recomputed
CP
2000
Batch
Type
55,
CP
2000
Letter
Suspense
Batch
Type
60,
and
Statutory
Notice
Suspense
Batch
Type
70.
Note:
Cases
transferred
to
Unit
Suspense
Batches
(Batch
Types
45,
65,
and
75),
or
Research
Suspense
Batches
(Batch
Types
42,
62,
or
77)
and
cases
with
Process
Code
(PC)
95
and
Internal
Process
Code
8L
do
not
receive
new
labels
or
folders.
Machine
Services
attaches
the
labels
to
new
folders.
Clerks
remove
the
old
folders
for
recycling
and
place
the
case
in
the
new
folder.
4.19.2.2.5
(09-01-2003)
Locations
A
location
is
a
three
character
code
that
can
be
alpha
or
numeric.
It
identifies
the
place
where
batches
and/or
cases
are
located.
Local
management
determines
location
numbers
for
all
units
and
suspense
files.
There
are
two
locations
assigned
by
the
AUR
system:
Release
(RLS)
—
This
location
is
assigned
when
batches
and/or
cases
are
released
from
the
tax
examining
units.
Inactive
(INA)
—
This
location
is
assigned
when
extracts
(Batch
Types
01000–27000)
are
downloaded
into
the
AUR
system
and
to
closed
cases
in
Batch
Type
96000.
The
batches
remain
assigned
to
this
location
until
the
batch
status
is
updated
to
Scheduled
Transfer
(ST).
4.19.2.2.6
(09-01-2003)
Process
Codes
Clerks
are
restricted
to
using
specific
process
codes.
The
ONLY
process
codes
that
can
be
input
by
clerks
are
11–17,
21–29,
34–45,
54,
58,
60,
62–64,
66,
79,
80
and
82–88.
The
ONLY
internal
process
codes
(IPC)
that
can
be
input
by
clerks
are:
Lost
Case
(LC),
Unassociated
Response
(UR),
Lost
Response
(LR),
or
Refile
Case
(RF).
4.19.2.2.7
(09-01-2005)
Electronic
Filing
System
Returns
are
filed
electronically
by
electronic
transmitters,
telephone
(Telefile
System),
or
from
a
home
computer
through
a
third
party
vendor
(On-Line
Filing).
Individual
electronic
returns
are
transmitted
to
the
Andover,
Austin,
Cincinnati,
Memphis
and
Ogden
Campuses.
All
electronically
transmitted
returns
are
identified
by
a
unique
Document
Locator
Number
(DLN).
The
following
File
Location
Codes
(FLC)
have
been
designated
for
the
electronic
filing
of
individual
income
tax
returns.
The
second
number
listed
is
the
roll
over
FLC
used
when
a
site
exhausts
the
regular
FLC
for
a
given
processing
date.
Andover
Campus
(ANIRSC)
16;
14
Atlanta
Campus
(ATIRSC)
65
Austin
Campus
(AUIRSC)
76;
75
Brookhaven
Campus
(BIRSC)
22
Cincinnati
Campus
(CIRSC)
38;
35
Fresno
Campus
(FIRSC)
99
Kansas
City
Campus
(KCIRSC)
43;
70;
79
Memphis
Campus
(MIRSC)
72;
64
Ogden
Campus
(OIRSC)
93;
92
Philadelphia
Campus
(PIRSC)
30;
32
(and
sometimes
66
-
U.
S.
Possessions;
98
-
International)
Note:
The
system
will
not
allow
a
user
to
order
a
TC
150
document
with
the
above
FLC
codes.
Electronic
return
information
for
TY
1998
and
later
may
be
secured
from
the
Tax
Return
Data
Base
(TRDB).
The
TRDB
stores
tax
information
submitted
through
the
Electronic
Filing
System,
which
includes
ELF,
ETD,
Telefile,
Digest
and
On-Line.
Use
IDRS
Command
Code
(CC)
TRDBV
to
request
an
on-screen
display
of
the
tax
return
information
in
transcript
format.
If
a
paper
copy
is
required,
use
CC
TRPRT
to
request
a
print
in
graphic
format.
For
additional
information,
see
IRM
2.3
(IDRS
Terminal
Responses).
Electronic
return
information
for
TY
1997
and
prior
MAY
be
secured
through
the
ARF
GEL
print
process.
The
TRPRT
print
is
not
considered
the
original
return.
It
will
be
labeled
"TRPRT
PRINT
DO
NOT
PROCESS"
.
Electronically
filed
(ELF)
returns
do
not
have
paper
copies
stored
in
Campus
Document
Retention,
Files
Function,
for
associating
taxpayer
correspondence.
Therefore,
it
is
not
possible
to
send
copies
of
attachments/responses
to
Document
Retention,
Files
Function,
for
association
with
an
ELF
DLN.
4.19.2.2.8
(09-01-2003)
Employee
Cases
Access
to
Employee
Batch
Types
90,
91
and
92
is
restricted
by
the
AUR
system.
During
the
download
of
the
extract
tapes,
the
AUR
system
assigns
PC
06
cases
to
Batch
Type
90.
These
cases
are
batched
by
the
employee
designated
to
work
Employee
cases.
Notices
and
correspondence
continue
to
be
generated
and
mailed.
However,
when
any
notice
or
letter
is
issued,
the
system
assigns
the
case
Batch
Type
91.
Route
all
correspondence
received
for
Employee
Cases
to
the
tax
examiner
designated
to
work
this
type
of
case.
4.19.2.2.9
(09-01-2004)
Correspondex
Letters
A
miscellaneous
or
Correspondex
letter
is
issued
to
taxpayers
when
the
case
requires
additional
information
(e.g.,
Letter
2625C,
Letter
2626C
or
Letter
2627C).
The
system
assigns
the
mailout
date
when
the
batch
status
is
updated
to
RB
(Release
Batch).
The
system
assigns
these
cases
to
the
appropriate
suspense
batch.
CP
2501
Letter
Suspense
Batch
Type
47
CP
2000
Letter
Suspense
Batch
Type
60
Statutory
Notice
Suspense
Batch
Type
70
Letter
information
(cases
with
IPC
3L,
6L,
8L
and
8M)
is
uploaded
daily
to
Correspondex
and
generates
letters
from
the
AUR
system.
The
letters
are
dated
three
to
five
days
from
the
date
the
batch
status
was
updated
to
RB.
Example:
This
example
is
based
on
five
days:
if
the
batch
was
updated
to
RB
status
on
10/15/2004,
the
letters
will
be
dated
10/20/2004,
and
will
be
suspensed
for
the
week
ending
10/23/2004.
The
system
ages
the
letters
by
the
week
ending
date.
The
Suspense
Summary
report
displays
the
Saturday
week
ending
date
for
letters
released
from
Monday
to
Friday
in
the
Projected
Notice/Letter
Date
field
on
the
report.
The
week
ending
date
for
CP
2501
Letter
Suspense
Batch
Type
47
and
CP
2000
Letter
Suspense
Batch
Type
60
may
contain
more
than
one
letter
date.
Statutory
Notice
Letter
(IPC
8L
and
8M)
cases
are
filed
under
the
original
date
of
the
Statutory
Notice.
The
Suspense
Summary
report
also
displays
REFILE
in
the
Batch
field
to
indicate
these
cases
are
suspended
under
the
original
Statutory
Notice
date
in
CSN
order.
Caution:
The
terms
refile,
refiling
and
IPC
"RF"
refer
to
the
suspense
files
maintained
in
AUR
-
DO
NOT
SEND
THESE
CASES
TO
CAMPUS
FILES
FUNCTION
(DOCUMENT
RETENTION).
Cases
with
letter
IPCs
3S
or
6S
have
either
a
paper
letter
in
the
folder
or
a
letter
input
on
IDRS.
The
system
dates
these
letters
one
day
from
the
date
the
batch
is
updated
to
RB
status.
Note:
The
Suspense
Summary
report
displays
the
Saturday
week
ending
date
of
these
letters
in
the
Projected
Notice/Letter
Date
field.
4.19.2.2.10
(09-01-2003)
Recomputed
Notices
Whenever
a
taxpayer
response
causes
the
figures
on
the
original
CP
2000
to
change,
an
amended
or
recomputed
CP
2000
with
the
correct
figures
is
issued.
The
AUR
system
assigns
these
cases
to
Batch
Type
55,
based
on
the
PC
assignment.
Statutory
Notices
with
a
Recomputed
CP
2000
keep
the
Statutory
Notice
CSN
and
are
returned
to
Suspense
Batch
Type
70.
4.19.2.2.11
(09-01-2003)
Miscellaneous
Letters
The
tax
examiner
uses
a
miscellaneous
letter
when
it
is
appropriate
to
send
a
letter
to
the
taxpayer
and
take
another
action
on
the
case
at
the
same
time.
The
tax
examiner
assigns
a
process
code
other
than
a
3L,
3S,
6L,
6S,
8L,
8M
or
8S
on
these
cases.
Cases
are
filed
in
the
appropriate
AUR
suspense
file
based
on
the
process
code
assigned
by
the
tax
examiner.
The
letter
displays
the
CSN
of
the
process
code
action.
See
IRM
4.19.2.2.9
for
additional
information
on
Correspondex
letters.
Note:
Miscellaneous
letters
rejected
by
IDRS
are
not
batched;
transfer
to
the
tax
examiner
who
initiated
the
letter.
4.19.2.2.12
(09-01-2003)
Action
61
Guidelines
Action
61
Guidelines
are
the
result
of
a
task
force
initiated
to
provide
timely
and
quality
responses
to
taxpayer
correspondence.
The
general
guidelines
are:
A
QUALITY
RESPONSE
is
an
accurate
and
professional
communication
which,
based
on
information
provided,
resolves
the
taxpayer
issues,
requests
additional
information
from
the
taxpayer,
or
notifies
the
taxpayer
we
have
requested
information
from
outside
the
IRS.
A
quality
response
is
TIMELY
when
initiated
within
30
CALENDAR
DAYS
of
the
IRS
received
date.
When
a
quality
response
cannot
be
issued
timely,
an
INTERIM
RESPONSE
will
be
initiated
by
the
30th
calendar
day
from
the
IRS
received
date.
Use
letter
2645C.
All
interim
letters
should
inform
the
taxpayer
when
a
final
response
can
be
expected
and
should
provide
a
name
and
number
to
contact
to
resolve
additional
inquiries.
The
AUR
system
automatically
generates
a
an
interim
letter
2645C
when
the
IRS
received
date
exceeds
a
specific
number
of
days
as
determined
by
the
AUR
Coordinator.
A
2645C
letter
is
generated
for
cases
in
Batch
Types
41,
44,
52,
53,
58,
72,
74
and
99.
The
Batch
Status
must
be
Blank,
Associated
Batch
(AB),
Schedule
Pending
(SP),
Schedule
Transfer
(ST)
or
Suspense
Batch
(SB).
The
AUR
Coordinator
has
the
option
to
select
Assigned
Unit
(AU)
and
Batch
Finished
(BF)
status.
4.19.2.2.13
(09-01-2004)
Service
Center
Automated
Mail
Processing
System
(SCAMPS)
Received
Date
The
receipt
of
AUR
bar
coded
notices
is
no
longer
recorded
on
magnetic
tape
by
the
SCAMPS
system.
4.19.2.2.14
(09-01-2004)
Assessments
The
system
automatically
creates
an
assessment
record
on
all
cases
with
PCs
67,
87,
and
90–93
and
for
all
ELF,
1040EZ,
and
1040EZ-Tel
cases
with
PCs
47,
51,
52,
70,
71
and
73
up
until
a
locally
determined
date,
but
no
later
than:
January
12,
2007
for
all
PC
67
and
for
all
ELF,
1040EZ,
and
1040EZ-Tel
cases
with
PCs
47,
51,
52,
70,
71
and
73
May
11,
2007
for
PCs
87
and
90–93.
After
January
12
(for
TY
2003
CP
2000s),
or
May
11
(for
TY
2003
Statutory
Notices),
or
the
locally
determined
date,
ALL
assessments
must
be
input
via
IDRS.
Print
the
assessment
document
and
associate
it
with
the
case
after
the
process
codes
are
verified
and
before
the
batch
is
updated
to
RB.
Manual
assessments
should
receive
priority
handling
to
insure
that
the
assessment
is
input
on
IDRS
before
the
upload
of
the
corresponding
process
codes,
since
the
process
code
closes
the
IDRS
control
base.
The
tax
examiner
verifies
and/or
inputs
the
necessary
assessment
information
on
AUR
for
PCs
15,
20,
35–39,
40–53,
62–66,
70–71,
73–74,
80,
82–86,
88,
and
94–95.
The
AUR
system
creates
a
tape
to
upload
assessment
information
to
IDRS
—
except
on
cases
where
the
tax
examiner
has
determined
that
a
manual
assessment
should
be
done.
Manual
assessments
are
input
directly
to
IDRS.
AUR
assigns
a
sequence
number
to
each
assessment
record
based
on
the
order
the
process
code
verification
process
is
completed.
Assessment
volumes
are
limited
for
each
blocking
series.
The
AUR
Coordinator
and
the
Computer
Service
scheduler
insure
that
daily
limits
per
blocking
series
are
set
correctly,
and
that
the
combination
of
automated
and
IDRS
assessments
do
not
exceed
the
daily
input
limitations.
2,000
for
Blocking
Series
500–519
4,000
for
Blocking
Series
550–589
2,000
for
Blocking
Series
600–619
3,000
for
Blocking
Series
650–679
Ship
assessments
to
the
Files
Function
for
Form
5147
association.
Each
Campus
should
work
with
the
Files
Function
to
determine
Campus
directions
for
assembling
and
shipping
the
assessments.
Each
released
batch
has
its
own
adjustment
sequence
series
and
this
order
MUST
be
maintained
during
the
shipping
to
Files.
The
employee
number
is
composed
of
ten
digits
as
follows:
The
first
two
digits
represent
the
Campus.
The
next
three
digits
represent
the
AUR
Organization
(ORG)
Code
(890).
Note:
Prior
to
January
2002,
the
AUR
Organization
(ORG)
Code
was
459.
The
last
five
digits
represent
the
AUR
Batch
Number.
Taxpayers
generally
have
90
days
to
petition
the
Tax
Court
to
dispute
a
Statutory
Notice
of
Deficiency.
If
the
Statutory
Notice
of
Deficiency
is
addressed
to
a
person
outside
the
United
States,
the
time
is
extended
to
150
days.
Note:
Disaster
relief
may
also
extend
the
period
a
taxpayer
has
to
petition
Tax
Court.
The
system
identifies
these
cases
and
they
will
be
maintained
until
the
disaster
end
date
expires.
Campuses
receive
lists
of
newly
docketed
Tax
Court
cases
daily.
These
lists
contain
the
following
information:
Docket
number
Name
and
address
of
the
petitioner
TIN
(if
known)
Tax
Year
Name
of
office
issuing
the
CP
2000/Recomp
or
Statutory