Checks that can be processed through OTCnet as Non-personal:

Checks that cannot be processed through PCC:

.

PCC can only be transmitted daily until 9:30 p.m. EST. All PCC System related inquiries should be directed to the Treasury OTCnet Support Center at either 1–866-945–7920 or 302–324–6442FMS.OTCChannel@citi.com. Treasury OTC Support Center support is available 24 hours a day, 7 days a week.

IRS users and managers of the OTCnet system must view and/or print the OTCnet Participant User Guide by accessing the OTCnet Web site at: https://www.otcnet.fms.treas.gov/index.html.

OTCnet is comprised of three elements:

https://www.otcnet.fms.treas.gov/index.html.

The following configurable input fields are required on the PCC input screen for COIC Payments:

The following payments are processed manually:

As of October, 2008, Memphis and Brookhaven Campus Support began processing Offer in Compromise payments using RS-PCC.

All checks that are unable to be scanned by OTCnet or RS-PCC will be transshipped to Cincinnati Submission Processing via overnight mail delivery to:


Internal Revenue Service
Stop 317
201 West Rivercenter
Covington, KY 41011


The PCC Manager lines through "Electronically Presented" on the front of the check if it is stamped. Campus Support will prepare a Form 3210 Document Transmittal and list each check that failed to scan through PCC. The following must be listed on each Form 3210:

.

The Form 3210 is attached with a copy of the related Form 2515, Record of Offer in Compromise, with the unprocessables item lined through. A copy of Form 3210 is faxed to Cincinnati using the designated Cincinnati fax number.

Campus Support receives checks back from COIC at the scheduled times set by Campus Support. The Manager/Lead or other authorized designee verifies that the information on the Form 3210, Document Transmittal matches the remittances. The COIC Clerk waits for Campus Support to verify all information, initials the Form 3210 and gives COIC a copy of the Form 3210.

The Manager/Lead or other authorized designee from Campus Support verifies the information on the Form 3210 with the remittances. The Form 3210 is marked in black with the letters 'PCC' on top left-hand corner or 'RS-PCC'. See: IRM 3.17.278.7.1 for processing RS-PCC Payments.

Campus Support batches remittances in batches of 20 or less. The operator signs on to PCC using their SEID and password after clicking on the POS icon on the desktop. If the user is using a temporary password, a new password needs to be created.

Campus Support operator determine if the check is Personal or Non-Personal (all money orders and third party checks must be input as 'Non-Personal'). Select 'Personal' or 'Non-Personal' from the 'Item Type Box' on the right side of screen.

Campus Support operator input the check received from COIC into the scanner. Place the check in the scanner with the MICR line of the check face up aligned with the right side of the scanner. The MICR line is the bank routing number found on the bottom of the check. Gently push the check forward to allow the scanner to grasp the check. Press the 'Enter' key or click 'Start Scan' button.

If the screen prompts you, "Are you sure this is a business check?" you must answer 'Yes' or 'No'. Select 'Personal' or 'Non-Personal' from the 'Item Type Box' on the right side of screen.

The check image will appear on the screen. Ensure that the check is readable.

Input the required fields from the source document, not the screen image or remittance.

After the required fields are entered, click "complete" and the scanner will complete the transaction and return the check.

The scanner will imprint "Electronically Presented" on the front of the check. If this does not appear, the Manager/Lead or another authorized designee needs to stamp the check manually with that stamp in a location that does not interfere with the dollar amount, financial institution information, or the signature.

Continue to input the remainder of the batch.

The clerk inputting the batch visually verifies that all checks are scanned properly, that the entire front of the check image is visible on the screen, and that the dollar amount is legible before signing out of the batch.

When finished, click "CLOSED" . Click the Print icon for a batch printout. Close POS and logoff.

It is recommended that the Manager/Lead or other authorized designee void a check input or fix an error. If a check was scanned incorrectly, alert the Manager/Lead that a check needs to be voided. The check will require re-scanning.

Procedures to void a check if the batch status is OPEN:

Procedures to void a check if the batch status is CLOSED:

If Campus Support is unable to complete a batch deposit within 24 hours, PCC Management/Campus Support must inform the HQ Account Management CS and RS-PCC HQ analysts. immediately via telephone or E-mail. The Account Management analyst will then contact the Chief Financial Office (CFO).

When all checks for a batch have been scanned, the clerk will print a batch list. Clerks must balance their scanned checks against the batch list before transmitting their batch.

The Manager/Lead or another authorized designee adds up the checks on a calculator and prints the calculator tape. Attach the calculator tape to the Batch List that will be sent to Redesign Revenue Accounting Control System (RRACS). Verify the total money amount and the total number of checks against those totals on the Batch List. If the total money amounts/checks agree, the next step is to quality review all required fields. If the total money amounts/checks do not agree, check the total money amounts/checks against the Form 3210 Document Transmittal and the Batch List. If they still do not agree, the Manager/Lead must do a verification check and make changes accordingly.

An authorized user must validate the total deposit on the Batch List that Campus Support keeps by indicating on the top right corner Deposit = Number of Checks = Total Money Amount. An additional Log Book is kept within Campus Support that has 7 columns:

The steps to balance a batch are:

Logon through Batch Manager and scroll to find the specific input clerk's batch. Click it and then click "CLOSE BATCH" . A new batch printout will be printed. Click "UPLOAD" . This will transmit the batch to Treasury OTC.

After transmission of a batch is complete, click "ACKNOWLEDGE" to ensure the batch was sent. Staple the batch printout and calculator tape to a copy of the Form 3210. Place in a United Parcel Service (UPS) mailing envelope. Attach a UPS approval form and mail to Cincinnati RRACS. Staple the PCC clerk's copy of the batch printout to a copy of the Form 3210 with checks, and file in date order.

When an error is discovered prior to the batch transmission from POS to OTCnet, the clerk must alert the Manager/Lead. The Manager/Lead or other authorized designee signs on to the OTCnet and makes the appropriate correction to the dollar amount, or voids and re-scans the item.

When a error is discovered after the batch has been transmitted to OTCnet, the operator alerts the Manager/Lead. The Manager/Lead calls Treasury OTC Support Center immediately to resolve this problem. Also, coordination is required with RRACS.

Always ensure both sides of payment, including the MICR line, are readable and there are no black lines on OTCnet screen when initial scan is done.

If the Treasury OTCnet Support Center can not collect the funds upon initial presentment, it may try to collect them through re-presentment up to two additional times.

Occasionally the Treasury OTCnet Support Center will try to resubmit a check if it is unreadable. Treasury OTCnet Support Center will contact the OTCnet Manager within the 14 days to request that the OTCnet Manager re-scan a second time.

All Managers and authorized users of the OTCnet System in Campus Support Sites must familiarize themselves with the following IRMs 21.1.7 Campus Support, 3.8.44 Campus Deposit Activity and 3.8.45 Manual Deposit Process to ensure accuracy, timely deposits, and adherence to internal controls.

See: IRM 3.17.278.5.1.

See: IRM 3.17.278.5.2.

See: IRM 3.17.278.5.3.

See: IRM 3.17.278.4.

The following configurable input field is required on PCC input screen for Insolvency Payments.

Vouchers with an MFT 17, 20, 28, Non Master File (NMF) or any vouchers that are not able to be processed through OTCnet are pulled from the batch that is being worked. These vouchers become manual vouchers.

A new calculator tape is printed without these manual payments.

Campus Support must use Command Code (CC) Correct a Block (CRBLK) to input the new voucher and check totals from the tape receipt without the manual payment.

Campus Support takes the manual voucher and writes "Manual Payment" and the Check ID number in red ink, in the upper right corner of the voucher. A copy of the voucher is placed in the Insolvency bucket.

The voucher itself is then tagged with an upside down Post-It note in the upper right corner of the voucher with the word "Manual" and the Check ID number written on the Post-it note. The voucher is placed on top back in the batch it came from.

The manual voucher amount will appear with the Check totals but not with the Command Code (CC) PYBAL totals. The Manual Voucher is faxed along with the Document Transmittal Form 3210 and Recapitulation of Document Register Form 813A to Ogden.

Insolvency payments or Bankruptcy Trustee checks are sent to the Philadelphia Campus Support for processing. The Chief Financial Office (CFO) established and authorized the use of a "suspense" Account 4625 for depositing these remittances prior to the research and application of the payment to the taxpayers’ accounts. The purpose of this process is to expedite the government's availability of funds for large dollar payments.

Trustees should mail the Insolvency checks to a Post Office Box designated specifically for these checks. The address is:

Trustee payments sent by overnight mail are sent to:

The Campus Support retrieves mail from the Insolvency PO Box and the Campus street address. Campus Support extracts the mail from the envelope. The envelope and any enclosures are attached to the check. The envelopes are stamped with the IRS received date and given to Centralized Insolvency Operation (CIO) employees in Campus Support.

CIO employees review the checks and divide the checks into two categories:

Trustees send checks for both single and multiple cases. A single payment is defined as one check for one taxpayer. Multiple check is defined as one check that is intended for multiple taxpayers.

CIO employees take the following actions on single case checks processed by Philadelphia Campus Support:

CIO employees take the following actions on multiple case checks processed by Philadelphia Campus Support

The Campus Support verifies the Form 3210 Document Transmittal against the checks received from CIO.

The Campus Support scans Insolvency checks and transmits the check information daily to the Treasury/Fiscal Service via the OTCnet. See IRM 3.278.5.1, Checks That Cannot be Processed Through OTCnet.

Ensure the check image is readable by visually verifying that all checks are scanned properly, that the entire front of the check image is visible on the screen, and that the dollar amount is legible.

Input the required fields from the source document or voucher. Verify that the source document or voucher is equal to the check amount.

The scanner will imprint “Electronically Presented” on the front of the check. If this does not appear, the Lead Clerk needs to stamp the check manually. The stamp needs to be placed in a location that does not interfere with the dollar amount, the financial institution information, or the signature.

When finished, click “CLOSED”. Click the Print Icon for a batch printout. Close POS and logoff.

Any checks cannot successfully be scanned via PCC must be transshipped. Campus Support must transship CIO payments and vouchers to Ogden Submission Processing Campus. See IRM 3.17.278.6.7(16). The checks and vouchers MUST be identified as Insolvency checks, so that they are not processed as regular remittances and insure they are deposited into the 4625 suspense account.

When OTCnet is down, Account Management (AM) Headquarter Campus Support Analyst and Submission Processing (SP) Headquarter RS-PCC Analyst must be notified immediately. If OTCnet is down for more than one day, Campus Support must transship the CIO payments and the vouchers to Ogden Submission Processing at the address below. The checks and vouchers MUST be identified as Insolvency checks, so that they are not processed as regular remittances and to insure they are deposited into the 4625 suspense account.


Deposit Team Stop 6094
Attn: Debbie Brown
Internal Revenue Center
1973 North Rulon White Blvd.
Ogden, UT 84404

Campus Support is responsible for taking steps to deposit checks as follows: Verifies the Form 3210 Document Transmittal against the checks received from CIO.

Campus Support inputs checks and transmits the information daily to the Treasure/Fiscal Service. See IRM 21.1.7.10.2 Checks that Cannot be Processed Through PCC.

Campus Support inputs checks received from CIO into scanner (EC6000i or EC7000i). Place the check in the scanner with the MICR line of the check face up aligned with the right side of the scanner. The MICR line is the bank routing number found on the bottom of the check. Gently push the check forward to allow the scanner to grasp the check. Press the enter key or click Start Scan button. The scanner will automatically flip the check and scan the back.

The check image will appear on the screen. Ensure the check is readable.

Campus Support inputs the required fields from the source document not the screen or remittance.

The scanner will imprint "Electronically Presented" on the front of the check. If this does not appear, the Lead Clerk needs to stamp the check manually. The stamp needs to be placed in a location that does not interfere with the dollar amount, the financial institution information, or the signature.

The clerk inputting the batch visually verifies that all checks are scanned properly, that the entire front of the check image is visible on the screen, and that the dollar amount is legible before signing out of the batch.

When finished, click "CLOSED." Click the Print Icon for a batch printout. Close POS and logoff.

See: IRM 3.17.278.5.7

If Campus Support (CS) is unable to complete a batch deposit within 24 hours, PCC Management/Campus Support will inform PCC Headquarters analyst by telephone or E-mail immediately. PCC Headquarters Analyst will contact the CFO.

Once a Batch is complete, the clerk will print out the Batch List that has all the information for every check that was scanned. The Batch List is kept with the checks and the Form 3210 Document Transmittal for quality review. Clerks must balance their scanned check against the batch list before transmitting their batch.

The PCC Manager/Lead or another authorized designee must quality review the checks that are scanned. Using Batch Manager on the PCC System, the reviewer will view the scanned checks. If an error has occurred, the reviewer will correct it through Batch Manager and print a new batch list with the correction. When the batch has been verified, the reviewer will upload and acknowledge the information to the Treasury OTC Support Center.

CS will retrieve the OTCnet Deposit Ticket Report information from the OTCnet each day for the prior day’s scanned checks. The Deposit Ticket is generated by Treasury OTC Support Center at 9:30 am each day. The report has the total amount of money deposited to Treasury OTC Support Center from the previous day.

Insolvency PCC valid Agency Location Code (ALC) plus 2 - The agency identifying code plus a unique two digit number that is used in POS to identify a cashflow. This number is assigned by Treasury OTC Support Center. The ALC+2 for PCC Insolvency: 20092900 00 = PCC Insolvency

The OTCnet Deposit Ticket Report lists all items being deposited into TRS on that day. The following item list is:

,

Each morning the Campus Support Manager/Lead or other authorized designee must print and compare the previous day's checks transmitted to ELVIS to the OTCnet Deposit Ticket Report. The Deposit Ticket Report shows a total of checks deposited for each employee. The combined total for all employees must match the Deposit Ticket Report. If the total does not match, follow the instruction below:

CS receives and acknowledges the Form 3210, Document Transmittal, and accompanying vouchers with a copy of the checks annotated with the Trace ID Number from CIO. For more detai: See Accounts Management IRM 21.1.7.10.4.2.1 (1)

Voucher packages are sorted by the Julian date of deposit and CC PAYMT is utilized to credit the taxpayer's account and generate tax class totals. For more detail: See Accounts Management IRM 21.1.7.10.4.2.1 (2).

All completed work is rubber banded and put in baskets with the CC PYBAL sheets waiting to be balanced.

See: Accounts Management IRM 21.1.7.10.4.2.2.

Only a Manager/Lead has permission to attempt to edit the account/routing string on the check itself through OTCnet. If the check fails to scan once again, perform the following:

See: IRM 3.17.278.5.10

See: IRM 3.17.278.5.11

See: IRM 3.17.278.5.12.

In the event that RS-PCC is not available to users due to technical issues, the RS-PCC HQ Analyst will consult with the RS-PCC Technical Team to determine when the system will be available to the users. The RS-PCC HQ Analyst will then consult with the HQ Analyst for Campus Support, FA TAC and SP Austin (OVDP) to determine a plan of action weather to transship payments to the SP sites for processing.

On December 2010, RS-PCC RL II was implemented. This is a new web-based system that enables Consolidated Campuses and Taxpayer Assistance Centers (TAC) to electronically process paper remittances at the point of receipt.

As of July 2011, RS-PCC RL II was deployed in 401 TAC and Accounts Management Campus Support in Atlanta.

On March 2012, Austin Submission Processing Campus begin processing RS-PCC payments for Overseas Voluntary Disclosure Program (OVDP).

RS-PCC payments are identified by the literal EFT- TRACE and a DLN beginning with "81"

Posting information for RS-PCC is sent to EFPPS for master file posting. These payments are identified on master file with a 17 digit Electronic Funds Transfer (EFT) Trace number on IDRS. The Tape Edit Processor (TEP) assigns two leading digits to denote the Submission Processing Center Code (29 for Ogden) to which makes the EFT number 17 positions for master file and IDRS research (except CC EFTPS). The Submission Processing Center Codes 29, will only be seen on IDRS. On the RS-PCC Check Detail screen the EFT number has 15 positions. The components which identify a EFT number:

See IRM 3.17.278.7.1.(8) for Campus Support Number below. See IRM Exhibit 3.17.278-4 for Field Assistance TAC Areas Originating Location Number.

The eighth and ninth positions of the EFT-Trace Number for Campus Support and Submission Processing sites:

The Service is committed to ensuring a 24 hour deposit standard. It is of the utmost importance to deposit the largest amount of money in the shortest possible time frame

Remittances of $50,000 and over must be deposited by the next business day of the campus received date. All attempts must be made to deposit these items the same day of extraction or no later than the next business day.

Remittances of $100,000 or more must be deposited on the day of receipt. Remittances of $100 million or more must be deposited by Close of Business (COB) on the day of receipt. When checks of $100 million or more are received, the check must be photocopied and immediately faxed to the deposit support site. Management at all levels must monitor the flow of receipts to ensure that this objective is achieved.

Checks that can be processed through RS-PCC.

Checks that cannot be processed through OTCnet or RS-PCC.

In order for payments to be on the next business day's deposit ticket, Fiscal Service OTCnet must receive them by 9:30 p.m. EST. Fiscal Service OTCnet only processes payments Monday - Friday. All PCC OTCnet System related inquiries should be directed to the Fiscal Service OTCnet Support Center at either 1–866-945–7920 or 302–324–6442 or via E-mail at: FMS.OTCChannel@citi.com. Fiscal Service OTCnet Support Center support is available 24 hours a day, 7 days a week.

IRS users and managers of the PCC OTCnet system must view and/or print the Fiscal Service OTCnet Participant User Guides (Check Capture and Check Processing) by accessing the PCC OTCnet web site at: https://www.otcnet.fms.treas.gov/index.html.

There are two important major components in OTCnet that are used to process a check from presentment to collection. OTCnet/CIRA used for researching and printing check images and Point of Sale (POS) is the software used on the Agency's computer to process check transactions. In order to use OTCnet, you are required to have Internet access, as it is accessible only through the PCC OTCnet web site at: https://www.otcnet.fms.treas.gov/index.html

The PCC OTCnet / RS-PCC Security Contact is Valerie Jones: 202-283-4167, Valerie.Jones@irs.gov.

To request access to RS-PCC RL ll users must :

"All" users with RS-PCC access must register with the Employee User Portal Access is needed by all RS-PCC users in order to access the Negative TIN (NTIN) list. The list is used to help prevent UNAX violations.

To request access to RS-PCC RL II users must : submit a request via Online 5081 system https://ol5081.enterprise.irs.gov/.

RS-PCC RL II is a TIVOLI installation package which is requested through OS GetServices. https://kisamess.web.irs.gov/webtier-7.11/ess.do An icon for the RS-PCC Webb application will be added to your workstation or laptop after installation to the terminal where a scanner will be placed. All other terminals that are not connected to a scanner will have to use the RS-PCC RL II URL for access: https://rspcc.enterprise.irs.gov:4443/rspccweb/index.jsp

A scanner is necessary for a user to scan the taxpayer remittance in RS-PCC. The scanner must be connected to the workstation desktop or laptop to be able to scan the taxpayer remittance. The scanner may be moved, as needed, between workstations where the RS-PCC Web application has been installed.

To Login to RS-PCC RL II, you will enter your Standard Employee Identification Number (SEID) and Local Area Networks (LAN) password and press the Login button. Any changes to your password are made through the Password Management System (PWM). If a user account becomes locked, or the user has forgotten their password, they must use the PWM to unlock themselves.

Three failed attempts to access the system will lock your LAN account preventing access to the system. You may unlock your account if you are registered with PWM. Otherwise, you will be required to contact the Enterprise Service Desk 1–866–743–5748 for assistance.

Password Management is a self-service tool that enables employee to reset their own LAN password at anytime. You will need Identity Management Suite Direct software to utilize PWM.

When requesting access to RS-PCC through Online 5081, there are 3 levels of access depending on the function you perform:

The following are configurable input fields for Insolvency, Misdirected and OIC Payments. An "*" indicates a required input field.

RPSID Range

Valid MFT Codes

Designated Payment Code

Primary and Secondary Transaction Codes

Received Date:

Remittance Processing System Identification (RPSID)

Check Amount:

Name Control:

TIN (Tax Identification Number):

MFT (Master File Transaction Code). See IRM 3.17.278.7.7(3):

Tax Period:

Amount 1, Amount 2, Amount 3 Transaction Amount:

TC 1, TC 2, TC 3 (Transaction Code):

DPC:

Remittances are batched with 1 - 25 remittances per batch with a RPSID number Sheet. Campus Support includes a calculator tape of the total of counts and amounts for the batch.

After successfully logging into the RS-PCC RL II application, the user is ready to begin entering the remittance information.

From the RS-PCC RL II Home Page, click "Payment Entry" .

On the Payment Entry Menu the operator will chose New Batch, this allows the operator to input the check information for processing.

Input the Received Date from the payment source document (MMDDYYYY) and RPSID number from the RPSID sheet. Both numbers will carry the rest of the batch.

The operator will then chose if the remittances will be processed as a Single or Multi/Split.

Click "Scan Check" button to activate the scanner. A green light on the scanner indicates that it is ready to receive checks. The scanner will automatically flip the check and scan the back. The check image will appear on the screen. Ensure the check is readable. The remittance is placed in the scanner with the Magnetic Ink Character Recognition (MICR) line of the check face up aligned with the right side of the scanner. The MICR line is the bank routing number found on the bottom of the check. Gently push the check forward to allow the scanner to grasp the check.

When the scanner identifies a problem with the remittance MICR Data, the operator will make corrections to the MICR Line. Each of the symbols that are before and after the routing numbers, account number and check number represents either a "T" "O" "A" or "D," See Exhibit 3.17.278-5.

Once the entry operator has corrected the MICR Line, they will continue to input the payment information.

Input the identified fields needed to process a payment. See IRM 3.17.278.7.7(1).

When the "Check Amount" field and the "Primary Transaction Amount" field are not the same, an error will appear at the bottom of the screen. The check amount and the transaction amount must be equal. Otherwise, you will not be able to complete the payment.

If the written amount and numeric amount on the check do not match, See IRM 3.8.45.4.5Manual Deposit Process.

The scanner will imprint "Electronically Presented" or "Electronically Processed" on the front of the check. If this does not appear, the Manager/Lead or other authorized designee needs to stamp or write "Electronically Presented" or "Electronically Processed" on the check manually. This needs to be in a place that does not interfere with the dollar amount, the financial institution information or the signature.

The clerk inputting the batch visually verifies that all checks are scanned properly, that the entire front of the check image is visible on the screen, and that the dollar amount is legible before scanning the next check or signing out of the batch.

.

When all payments for a batch have been scanned, click "Finish" . This action prepares the batch for Key Verification.

If there was a MICR Line correction or a Duplicate check issue during the processing of the batch, the batch goes to Awaiting Supervisor Approval. The supervisor must approve the batch before it goes to Ready for Key Verification.

When the operator has processed all payments in a batch, Click on Finish to close the batch.

Once a user has click "Finish" to close the batch, they will have the options of either printing the Batch Listing, Completing the Batch or Editing the Batch using the following icons

If you need to correct an error or delete a payment, Click List Payment navigate within the list payment screen to correct or delete the payment. You must now Click on Finish again to close the batch.

To complete the batch, Click on Print and Complete. This completes the batch and prints the Batch List See Exhibit 3.17.278-8

The Batch List reports shows all transactions included in the batch. The report consists of the detail and summary pages and changes the status of the batch to Ready for Key Verification, if it is printed after clicking Complete Batch.

The Batch List is kept with the remittance, source documentation, payment vouchers and calculator tape (Campus Support), completed RPSID sheet, and initiated copies of all Forms 795 (TAC) for Key Verification.

The operators perform quality review on payments through an electronic method called Key Verification (KV). All batches "must" be Key Verified before they can be transmitted to Treasury/FS for deposit.

To KV a batch, the operator selects the Key Verification Tab. This will display a list of all available batches that are "Ready for Key Verification" and "In Key Verification" . To KV a batch, the operator will select a batch with the status Ready for Key Verification.

You will not be able to KV any batches that you were the Approver or the Entry Operator. Therefore those batches will not be displayed when you are key verifying.

"cannot key verify" work if they have either processed the payments or approved the payments.

(TAC Only) TAC sites where the Manager is responsible for more than one TAC Site (Parent/Child relationships) has the ability to allow users with Supervisor access to KV work from one of their other TAC sites

The remittances and transactions data fields available for KV are based on the configurations set by the site Manager. Fields that have been configured for KV will not be pre-populated when users are KV'ing the remittances.

Once the batch is selected, the status will change to "In Key Verification" .

The operator will enter data for each payment field selected for KV into the KV edit page.

The operator will correct any errors encountered during KV.

If the RS-PCC approver makes a correction to the MICR line when the batch is in "Awaiting Supervisor Approval" , the MICR line of that payment must be verified in KV. The screen will prompt the user to validate the MICR line and the user will either accept the MICR or delete the payment.

If the operator accepts the MICR line, then it will process with the batch to the next status. If the payment is deleted it will either be re-scanned or transshipped. SeeIRM 21.1.7 Campus Support, IRM 21.3.4 Field Assistance

Upon completion of the KV process, the batch will be sent to Fiscal Service for deposit.

All documentation MUST remain with the batch.

The Batch Management function allows users with RS-PCC Supervisor access to perform the following:

The Batch Management function is also available to users with the RS-PCC Analyst role. The analyst are able to perform the following:

An analyst views payments and batches with read-only access.

The Deposit function displays all batches deposited through the FS.

The Deposit function allows the Manager/Lead or other authorized designee to perform the following:

Deposit Ticket States are:

All users have access to the Payment Search function.

Users will have access to search payments on their own site, the search is more specific when multiple criteria is entered. However, the search may take longer.

Users enter one or more criteria to perform a search.

The search criteria are:

An analyst is subject to unauthorized access to taxpayer account (UNAX) restrictions, and the system records UNAX in the audit logs.

All scanned work MUST be balanced daily.

The Manager/Lead or other authorized designee should balance their previous days work using the 215 Deposit Ticket, the Batch Listing from the scanned work and the RS-PCC End of Day Report (EOD). See Exhibit 3.17.278-10, Exhibit 3.17.278-8 and Exhibit 3.17.278-7.

RS-PCC Headquarters recommends that the RS-PCC End of Day Report be ordered at the beginning of each business day to use for balancing.

The Manager/Lead or other authorized designee compares the EOD to the 215 Deposit Ticket Report to ensure all scanned checks were deposited. Once it is determined that a batch is on the 215 Deposit Ticket Report update the Batch Cover Sheet with the deposit ticket date found on the top of the 215 Deposit Ticket Report.

If the two reports do not match, it is the Manager/Lead or other authorized designee's responsibility to determine what batches were not processed through to Fiscal Service.

When there is a discrepancy, the Manager/Lead or other authorized designee will determine which checks were not deposited and what corrective action is needed ASAP.

Batches that failed to process through to FS are placed in either the" Failed During Transmit" or "Failed to Transmit" status. The batch total will not be on the 215 Deposit Ticket. Manager/Lead or other authorized designee will determine what corrective action is needed in order to re-send the batch for deposit and monitor the status to ensure that the batch was re-transmitting for deposit.

Batches that were systemically stalled in the RS-PCC workflow can be in "Ready for Deposit" , "Sent for Deposit" or "Transmitted for Deposit" status. When this occur the batch did not go to FS for deposit and will not be on the 215 Deposit Ticket.

Manager/Lead or other authorized designee will check the batch for the payment status. If the payment status is not"posted" or "deposited" The payment did not go to deposit.

The Manager/Lead or other authorized designee is responsible for re-starting the batch for deposit and monitor the status to ensure that the batch was re-transmitting for deposit.