c
 

  
c 
 
 
c
 
  
c 

c  
  

The Remittance Processing System (RPS) is an automated system for remittance data. RPS
primarily transforms the records transcribed by the Lockbox Banks and Integrated Submission
and Remittance Processing (ISRP) system into the prescribed format for Generalized Mainline
Framework (GMF) mainline processing, performs error flagging, creates deposit reports and
generates master control records used in Service Center Control File processing for each deposit
block

  


      



 !  
 
 


 
 "#$ %&

 % 

Taxpayer, Employee, Other:

The RPS system processes only one taxpayer identification item and from one to three payment
amounts. The other data is a string of internal use codes that are discernable only by trained
IRS business users, and which are used as triggers and controls for subsequent IRS pipeline
processing. There is no employee or other data processed by RPS.

'(  
!  
 


 
)

'(c     ! )

Business Taxpayer Information File (BTIF)

The RPS system accesses the BTIF database to perform entity validation. RPS reads
information from the Taxpayer Information File (TIF).

Integrated Submission and Remittance Processing System (ISRP)

Remittance information is provided from ISRP on two files, one containing deposit data and
one containing transaction data.

Lockbox Banks
The IRS contracts with banks that process taxpayer payment (remittance) data called
LOCKBOX Banks. The LOCKBOX banks provide Deposit data and Transaction data to the
RPS system.

DED EDIT (DED01P)

When a LOCKBOX bank provides Transaction data on tape, that file is taken into the first
batch program in a string of daily batch programs (DED01P) for validation and reformatting
before being output as the RPS0505 file. The RPS0505 file is input to the RPS system.
'(*     

!  
)

None. RPS does not receive data from other Federal Agencies.

'(  +

   

!  
)

None. RPS does not receive data from Local governments or entities.

'*


   
!   
  )

RPS receives data from IRS contracted LOCKBOX bank sites.

' (


 
  

 $ ,

 )

The RPS system processes one identification item and from one to three payment amounts that
come from taxpayer submissions. RPS does not process employee data.

-.
 
  


!  
 c  
 $  
   
! )

This is not applicable to the RPS system.

-.
  / 


   )

Completeness will be verified further downstream in the payment matching and posting
process. Incomplete submissions will not post and will be identified on error reports.

- ! ).



!/
)

RPS payment records contain a payment received date.

0   
    

!
 )  % 


 
!
)

Yes, The data elements used by the RPS system are described in the data dictionary section of
the Functional Specification Package [Link].

 
 

(
  
  
1 %2 % 


 
%  
 % )

Only IRS production personnel who have authorization can gain access to the RPS input and
output data tapes or discs by accessing the UNISYS system and requesting file dumps.

IRS Error Resolution Tax Examiners:

IRS error resolution Tax Examiners correct errors identified by downstream processing.

IRS Accounting Staff:

Have access to RPS reports that are used in the accounting of cumulative deposit and
transaction information.

IRS Applications Developers:

IRS Applications Developers can gain access to RPS data when researching software problems.
IRS guidelines and procedures for accessing live taxpayer data are enforced at all times.

IRS Managers:
Managers of the above types of employees, except for applications developers, have the same
level of access to data as their employees.

'.
 
 !  
 )

Access is determined by functional business needs.

'   %
 ! %

% 
    
!
 )

Yes. All IRS functional areas operate within strict and enforced guidelines surrounding access
needs, authorization and control. Systemic audit trails exist where applicable and audit reports
are reviewed by management in the functional business units.

-(!   


 

 ! 3  
  )&$

Users have access to data as needed to capture and perfect payment data.

0(

  
   
!  


 
 )

There are no browsing applications for accessing payment data in the RPS arena. Otherwise,
the IDRS system contains a multitude of on-line command codes that have specific browse and
update functionality for taxpayer accounts, including those which RPS payments are posted
to. There are internal systemic audit trails in effect for all IDRS command codes, and
management is provided with audit reports for action as necessary.

4

 
 
  

)  % $

Yes, there are a number of secured downstream IRS pipeline systems that use data output by
RPS.

4(
  
 

    
 $ 


      )
The owners and business users of the interfacing systems are responsible for protecting
taxpayer and employee rights.

(
    
  

 
%
*  %  %+
% )

No other State, International, Local, or other kinds of agencies share data or have access to RPS
data.

.
  !   )

This is not applicable to the RPS system as stated above.

(
 
 
! 
 ! 
 )

This is not applicable to the RPS system as stated above..

.
 
 !   
  


    

! c56-)

This is not applicable to the RPS system as stated above.

 ! 
 

 ! 
 
     
 ! 
 
 

   )

Yes. All data processed through the RPS system is relevant and necessary. The system is
responsible for receiving, validating, and formatting remittance data, and supporting IRS
employees who need the data. The summary reporting data that is used by IRS Accounting
functions in the Processing Centers and the reports are used by Management to review
programs and processing procedures.

'( 
   

   
!! 
!
!
! 


 



  )

No, the RPS system does not pull data from several sources in order to build records on
individuals taxpayers, employees, or other groups of taxpayers. However, summary reporting
data are derived from the remittance amounts from taxpayer¶s data.

'(     !7 

$ 


 )

This is not applicable as stated above.

2.c. Can the system make determinations about taxpayers or employees that would not be
possible without the new data? No.
'.
     
   ! )

Inaccurate data will be identified in subsequent matching and posting processing, and error
resolution is an integral part of the downstream pipeline.

-   


 %

  

  
  !!
8  )&$

This is not applicable to the RPS system.

- 
    

 %  
 


 


    !!
8  )&$

The scheduled IDRS TIF consolidation is retaining the same data protections as those which
exist in the current TIF.

0.
      )5      
   )  %
$

RPS data can be retrieved by using the UNISYS system in order get prints of files or summary
reporting data. Data can also be retrieved by authorized business users via one or more IDRS
command codes.

0(  
  
 ! 
  
$ 

 
"

5


/ 
  
9
RPS does not consolidate data. Systemic changes are transparent to taxpayers and employees,
and they are kept within privacy and disclosure guidelines.

 

9
No harmful derivations can result from capturing, perfecting and posting tax payments.

   



  

/9
IRS processing center management use RPS summary data to make decisions involving
processing volume and error resolution. IRS accounting personnel in the processing centers use
RPS summary data to account for remittances. No harmful effects can result from the use of
RPS data in this manner.

1 
  

 9
No. The use of new technologies will not create new needs to protect the data, as access will
remain constrained to secured IRS and FDB computer systems and authorized business users.

.
   
 
 )

Per the above, there will be no situation where mitigation will be necessary.
2  

  5



&$
 
!  !  :!  

$ 


 

The system exists for the purpose of posting taxpayer payments to their respective accounts as
quickly and as accurately as possible.

The RPS system does not process employee data, nor does it apply to the treatment of
employees.

  


  


  %

 ! 
 

 
  )

The RPS system employs identical batch programs for use at all processing sites. The RPS
processing stream is designed for a specific execution sequence. Deviations in application
execution will result in highly visible negative results.

&$

   

!

!

Systemic errors and operational errors will result in highly visible negative results, internally. If
this occurs, applications developers and or business users take immediate action to correct and
reprocess data as necessary before there is an impact on taxpayers.

'(    

 


)

RPS does not hold data in a database. However, retention periods on output files are 1 day, 7
days, 15 days and 30 days as deemed appropriate for the nature of the data.

'(  
 ! 
 
   
   

 
)(   
 ! 
!
 )

The Computing centers are responsible for erasing tapes or deleting files at the end of the
retention periods. The procedures are documented in the Computer Operators handbooks
(COH).

'(     
%   :!


 
 
 !  !  %  %
%

  
 !    

/ 

)

Not applicable to RPS. Payment data is posted to taxpayer accounts to permanently reconcile
tax liabilities.

- 
! 


  c 
 
!

  
5 ) No.
-.

 ! 
 

 $ ,

  )

Not applicable to the RPS system.

0(

  
  %
 %


!) 
 % $

No. RPS is not designed to identify, track, locate, or monitor individuals.

0(

  
  %
 %



!


 )  % $

No. RPS is not designed to identify, track, locate, or monitor groups of people.

0(

 ! 
  !!
8 


)

RPS file access is restricted to authorized applications development staff and to authorized
computing center operations staff through internal controls which include audit trails. In
addition, IT management is held to the standards and guidelines developed for protection of
taxpayer data, protection of computer processing systems and protection of computer
equipment.

41  

c 

  c
 

  )
 
!
 


Treasury-IRS 34.037 IRS Audit Trail and Security Records.

Treasury-IRS 24.046 CADE Business Master File

4  
 

  %  c :! 


 
)
&$

The system is not being modified.

?