3.17.277 Electronic Payments

Manual Transmittal

November 28, 2016

Purpose

(1) This transmits revised IRM 3.17.277, Accounting and Data Control, Electronic Payments.

Material Changes

(1) IPU 16U0663 issued 04-01-2016 IRM 3.17.277.1.4.12.1(3) b Specified the credit card payment validation process

(2) change IRS EFTPS to Electronic Federal Payment Posting System (EFPPS) throughout entire IRM

(3) change Main Menu to Home Page throughout entire IRM

(4) IRM 3.17.277.1.1 added Taxpayer Bill of Rights (TBOR)

(5) IRM 3.17.277.1.4.12.1(2) change WorldPay US telephone number

(6) IRM 3.17.277.1.4.17.4 (3) removed amended return information

(7) IRM 3.17.277.3(1) change Login procedures

(8) IRM 3.17.277.3(2) and (3) removed

(9) IRM 3.17.277.3(4) change procedures to ‘press continue’

(10) IRM 3.17.277.3(5) added new paragraph for successful Login procedures

(11) IRM 3.17.277.3(6) through (8) removed

(12) IRM 3.17.277.3.1(2) change where menu items will appear on Home Page

(13) IRM 3.17.277.3.1(3)b removed last sentence

(14) IRM 3.17.277.3.1 (3)d removed and resequenced remaining paragraphs

(15) IRM 3.17.277.3.1(4)a changed arrow to tab

(16) IRM 3.17.277.3.1.(4)b changed enter to space

(17) IRM 3.17.277.3.2(1) changed logout procedure

(18) IRM 3.17.277.3.3 removed section

(19) IRM 3.17.277.3.4 removed section

(20) IRM 3.17.277.3.4.1 removed section

(21) IRM 3.17.277.3.4.2 removed section

(22) IRM 3.17.277.3.4.3 removed section

(23) IRM 3.17.277.3.4.4 removed section

(24) IRM 3.17.277.4.3 changed fax number in the IF/Then table row 2 and 8

(25) IRM 3.17.277.8.2 Changed access procedures for EFT Correction Screen and rearranged order for entire section

(26) IRM 3.17.277.8.2(1) added new procedures for Research/Correction screen

(27) IRM 3.17.277.8.2.(1)a removed

(28) IRM 3.17.277.8.2.(1)b removed

(29) IRM 3.17.277.8.2(2)a removed

(30) IRM 3.17.277.8.2(2)b removed

(31) IRM 3.17.277.8.2(3) paragraphs a through c new procedures

(32) IRM 3.17.277.8.2.1(1) added Unassigned Unresolved access procedures

(33) IRM 3.17.277.8.2.1(1)a through h removed

(34) IRM 3.17.277.8.2.2(1)change window to option and change procedures

(35) IRM 3.17.277.8.2.2(1)a change procedures

(36) IRM 3.17.277.8.2.2(2)a changed how invalid field appears

(37) IRM 3.17.277.8.2.2(2)b changed wording to unresolved number of elements

(38) IRM 3.17.277.8.2.2(2)c added new procedures

(39) IRM 3.17.277.8.2.3 added new section for Enter EFT Number

(40) IRM 3.17.277.8.2.4(1)a and b changed Correction Entry Screen access procedures and resequence paragraphs.

(41) IRM 3.17.277.8.2.5(1) change access procedures

(42) IRM 3.17.277.8.2.5(2)removed

(43) IRM 3.17.277.8.2.7(1)b removed

(44) IRM 3.17.277.8.2.8(1)a through c change procedures

(45) IRM 3.17.277.8.2.9(2) change procedures

(46) IRM 3.17.277.8.3(4)a change procedures

(47) IRM 3.17.277.8.3(4)b removed

(48) IRM 3.17.277.8.4 changed Note:

(49) IRM 3.17.277.8.5(2) removed paragraph

(50) IRM 3.17.277.8.5(3) resequence paragraph

(51) IRM 3.17.277.8.7(1)a change procedures

(52) IRM 3.17.277.9.2(2) change seventh bullet to commit changes

(53) IRM 3.17.277.10.1(1)a change access procedures

(54) IRM 3.17.277.10.1(1)b and c removed

(55) IRM 3.17.277.10.1.1(1) change access procedures, change ENTER to TAB

(56) IRM 3.17.277.10.1.1(3)a removed and resequence remaining paragraphs

(57) IRM 3.17.277.10.1.1.2(2) change how multiple records are displayed, delete last sentence

(58) IRM 3.17.277.10.1.1.2(5) change procedures

(59) IRM 3.17.277.10.1.1.2(6) change procedures

(60) IRM 3.17.277.10.2 change access procedures

(61) IRM 3.17.277.10.2(1) change wording

(62) IRM 3.17.277.10.2.3(1) change where screen appears

(63) IRM 3.17.277.10.2.3(1)a removed

(64) IRM 3.17.277.10.2.3(1)b removed

(65) IRM 3.17.277.12.1.1(1)a changed access procedures

(66) IRM 3.17.277.12.1.1(1)b changed access procedures

(67) IRM 3.17.277.12.1.1(1)c removed

(68) IRM 3.17.277.12.1.1(2) added sentence how to save list

(69) IRM 3.17.277.12.1.1(3)a through d change procedures

(70) IRM 3.17.277 12.1.1.(3)e added new paragraph

(71) IRM 3.17.277.12.1.2(1)a change access procedures

(72) IRM 3.17.277.12.1.2(1)b removed

(73) IRM 3.17.277.12.2.2(a) change access procedures

(74) IRM 3.17.277.12.2.2(b) though (d) removed

(75) IRM 3.17.277.12.2.1(1)a through d change procedures

(76) IRM 3.17.277.12.2.2(1) add sentence stating you must have a manager profile

(77) IRM 3.17.277.12.2.2(1)a through d change procedures

(78) IRM 3.17.277.12.2.2(1)e added paragraph

(79) IRM 3.17.277.12.3(1)a through d change access procedures

(80) IRM 3.17.277.12.3(1)e change select to submit paragraph and added Figure

(81) IRM 3.17.277.12.4(1)change procedures

(82) IRM 3.17.277.12.4(1)a through c change procedures

(83) IRM 3.17.277.12.4(3)a change procedures

(84) IRM 3.17.277.12.4(3)b removed

(85) IRM 3.17.277.12.4(3)c change procedures

(86) IRM 3.17.277.12.4(4)a and b change procedures

(87) IRM 3.17.277.12.4(5)change procedures

(88) IRM 3.17.277.12.4(6)change procedures

(89) IRM 3.17.277.12.4.1(1) 1) through 3) change procedures in table

(90) IRM 3.17.277.12.4.1(3) change EFT to Serial

(91) IRM 3.17.277.12.5(2)a through c change procedures

(92) IRM 3.17.277.12.5(2)d removed

(93) IRM 3.17.277.12.5(2)f change reject procedures

(94) IRM 3.17.277.12.8(1) change Retrieve Quality Review to Corrected EFT for entire section

(95) IRM 3.17.277.12.8(3) change access procedures

(96) IRM 3.17.277.13.1(1)a through c change access procedures

(97) IRM 3.17.277.13.1(2) remove generate

(98) IRM 3.17.277.13.2(1)a change sub-menu to page

(99) IRM 3.17.277.13.2(1)b through d change procedures

(100) IRM 3.17.277.13.2(1)e through I removed

(101) IRM 3.17.277.13.2.1 removed section

(102) IRM 3.17.277.13.4(1) procedure change to add EFTIRSREPORTS available on shared drive

(103) IRM 3.17.277.13.4.1 (2) and (3) procedure change to view reports for EFPPS application on shared drive

(104) IRM 3.17.277.13.4.1(3) steplist removed

(105) IRM 3.17.277.13.4.1(4) and (5) procedure change

(106) IRM 3.17.277.14 removed and added 3.17.277.13.1

(107) IRM 3.17.277.14.1 removed and added 3.17.277.13.1

(108) IRM 3.17.277.14.2 removed and added 3.17.277.13.1

(109) IRM 3.17.277.16.(13)b change PayrollOne telephone number

Effect on Other Documents

IRM 3.17.277, Electronic Payments, dated November 26, 2014, is superseded. This IRM incorporates the following IRM Procedural Updates (IPU’s): 15U0049, 15U0170, and 15U1096.

Audience

All IRS employees involved with electronic payments

Effective Date

(01-01-2017)

Related Resources

IRM deviations must be submitted in writing following instructions from IRM 1.11.2.2., Internal Management Documents System - Internal Revenue Manual (IRM) Process, IRM Standards, and elevated through appropriate channels for executive approval.

Linda J. Brown
Director, Submission Processing
Wage and Investment Division

Electronic Federal Tax Payment System (EFTPS)

  1. The Electronic Federal Tax Payment System (EFTPS) is a free service offered by the Department of Treasury. EFTPS decreases the cost of collecting and processing tax revenue.

  2. EFTPS processes the following payments:

    • Federal Tax Deposits (FTD) — All businesses required to make FTDs must make the payment electronically.

    • Voluntary electronic payments — Any taxpayer has the option of using EFTPS to submit any federal tax payment to IRS.

    • IRS e-file Electronic Funds Withdrawal — Individual and business taxpayers who e-file a federal tax return or extension request can elect to have their bank account debited for balance due or estimated payment(s). See IRM 3.17.277.1.5.1, IRS e–File Electronic Funds Withdrawal.

    • Credit or Debit card payments— Individual and certain Business balance due payments may be made by credit or debit card. ATM/Debit card payment option is available through the service providers. See IRM 3.17.277.1.5.12 , Credit or Debit Card Payments.

    • Federal Payment Levy Program Payments (FPLP) — Levy payments are received from the Treasury Offset Program. See IRM 3.17.277.2.1, Federal Payment Levy Program (FPLP).

    • Bureau of Alcohol, Tobacco and Firearms (ATF) Payments - Payments erroneously received for ATF. These payments will need to be transferred to ATF via Intra-governmental Payments and Collection System (IPAC). See IRM 3.17.277.2.4 , Bureau of Alcohol, Tobacco and Firearms (ATF) Payments.

    • Electronic Bill Payment System (EBP) - These are tax payments received through an electronic bill paying service, currently Fiserv. See IRM 3.17.277.1.5.3 , Electronic Bill Payment (EBP) System.

    • State Income Tax Levy Program (SITLP)- Levy payments received from individual states on behalf of taxpayers. See IRM 3.17.277.1.5.9 , State Levy Programs.

    • Social Security Administration Levy (SSA Levy)- Levy payments received from SSA benefits on behalf of taxpayers. See IRM 3.17.277.2.2 , Social Security Administration (SSA) Levy Program.

    • Remittance Strategy for Paper Check Conversion (RS-PCC) - RS-PCC is the process of converting paper checks into electronic ACH (Automated Clearing House) Debits. These are tax payments received in Brookhaven, Memphis, Philadelphia, Atlanta, Andover, and all Field Assistance Taxpayer Assistance Centers (TAC). RS-PCC also processes Insolvency payments at the Philadelphia Campus), Offer In Compromise (OIC) payments at the Brookhaven and Memphis Campuses, and Offshore Voluntary Disclosure Payments (OVDP) at the Austin Submission Processing Center. For tax payments that are received in TACs refer to IRM 3.17.277.2.3 , Remittance Strategy for Paper Check Conversion (RS-PCC).

    • IRS Direct Pay - Individual taxpayers can initiate ACH debit payments from www.irs.gov for any payment on Master File Tax (MFT) 30. This payment method does not require a prior enrollment.

    • Alaska Permanent Fund Dividend (AKPFD) - Levied dividend payments received from Alaska on behalf of individuals and businesses. See IRM 3.17.277.1.5.10 , Alaska Permanent Fund Dividend.

    • Municipal Tax Levy Program (MTLP) - Levy payments received from state municipalities on behalf of taxpayers. See IRM 3.17.277.1.5.11 , Municipal Tax Levy Program.

  3. IRS EFTPS processing is located only in Enterprise Computing Center - Memphis at the Memphis IRS Campus. Effective July 1, 2005, balancing and error resolution functions were incorporated into EFTPS operations in the Ogden Submission Processing Center Accounting Branch.

Taxpayer Bill of Rights (TBOR)

  1. The IRS Restructuring and Reform Act of 1998 (IRS RRA 98), Section 3705(a), provides identification requirements for all IRS employees working tax related matters. NOTE: The Taxpayer Bill of Rights (TBOR) adopted by the IRS in June of 2014, provides that taxpayers have the right to receive prompt, courteous and professional assistance in their dealings with the IRS. They are to be spoken to in a manner that is understood and any correspondence from the IRS must be clear and understandable. They have the right to speak to a supervisor whenever quality service is not received.

Financial Agent Responsibilities

  1. Bank of America Merrill Lynch (BAML), along with its primary subcontractor First Data Corporation, is authorized to operate EFTPS as its Treasury financial agent. Effective November 14, 2004, Bank of America took over complete operation of EFTPS.

  2. The Financial Agent:

    1. Enrolls taxpayers in EFTPS.

    2. Establishes a taxpayer database, which includes entity information and tax types.

    3. Operates the www.eftps.gov web site to accept payment and enrollment information from taxpayers and government agencies.

    4. Receives payment information from the taxpayers or their banks.

    5. Initiates the transfer of the tax payment amount from taxpayer's bank account upon a taxpayer's request.

    6. Validates the entity information and selected elements of the payment data.

    7. Transmits the necessary payment information for each taxpayer to EFTPS.

    8. Performs balancing activities to ensure that the detailed payment records match the sum of the money moved into the Treasury's Account at the Federal Reserve.

    9. Generates the Deposit Ticket and Debit Voucher and relates that information to each payment transaction.

    10. Responds to taxpayer inquiries about the electronic payment process.

    11. Receives and processes Electronic Data Interchange (EDI).

    12. Develops and transmits reports to IRS and FS.

    13. Accepts, processes, and transmits taxpayer data to the IRS for Automated Clearing House (ACH) Debits, ACH Credits, and same day Federal Tax Collection Service (FTCS) transactions.

    14. Provides Voice Response Unit, operator assistance, and Internet application payment methods to the taxpayers.

    15. Registers service providers, and receives, processes, and acknowledges enrollment and payment files using the bulk, batch, and single debit applications.

    16. Provides payment warehousing and categorization of data by amount and subcategory, verification, and validation of tax data.

    17. Provides accessibility to entity and transaction data for authorized IRS employees.

    18. Initiates, receives and processes tax payments within the fifty United States and protectorates, Canada, Mexico, and the international community.

    19. Makes changes, adds or deletes certain elements, data, or records as required by the IRS to comply with legislative or regulatory changes timely and as needed.

    20. Maintains and updates an enrollment database upon receipt of weekly entity information from the IRS.

    21. Operates a system for all financial institutions.

Financial Agent Customer Service Telephone Numbers

  1. Taxpayers are directed to call the financial agent for assistance on EFTPS.

  2. Bank of America assistance numbers are:

    • 800-555-4477 (Business)

    • 800-316-6541 (Individual)

    • 800-555-8778 (EFTPS OnLine)

    • 888-353-4537 (Voice Response System (VRS) for Electronic Funds Withdrawal (EFW))

    • 800-244-4829 (Spanish)

    • 800-733-4829 (Telecommunication Device for the Deaf (TDD))

    • 303-967-5916 (International direct dial)

    • 800-605-9876 (Financial institutions)

    • 866-684-6556 (Bulk Providers)

    • 800-945-0966 (Batch Providers)

    • 877-333-8292 (EFTPS for Federal Agencies)

  3. Enterprise Computing Center - Memphis (ECC-MEM) may call any of the financial agent numbers listed above or call Bank of America at 866-684-6556 (Core Hours of Operation: Sunday 10:00 PM MT thru Friday 10:30 PM MT) to report production problems.

  4. Taxpayers with EFTPS enrollment entity issues that the financial agent cannot resolve may be referred to the IRS e-help Desk at 866-255-0654 (EFTPS is option 3).

  5. Other IRS entity questions may be referred to the IRS Business and Specialty Tax Line at 800-829-4933 (for businesses) or 800-829-1040 (for individuals).

EFTPS Customer Service Responsibilities

  1. IRS Accounts Management (AM) Contact Representatives should use Command Code (CC) EFTPS and other Integrated Data Retrieval System (IDRS) research command codes such as BMFOL and IMFOL to research electronic payments. Refer to IRM 2.3.70, IDRS Terminal Responses - Command Code EFTPS for details of CC EFTPS.

  2. AM contact representatives may use the financial agent phone numbers for additional research.

  3. EFTPS employees are not authorized to provide banking or other taxpayer information to Compliance or other IRS employees for enforcement purposes. However, Compliance and other IRS employees using CC EFTPS definer E, can obtain the Depositary Financial Institution (DFI) number indicating the financial institution used to make taxpayer payments. Looking up the DFI number in public banking industry references (e.g., American Financial Directory) will yield the specific bank name, address, and phone number.

  4. Anyone can look up the DFI number at the Federal Reserve Bank Services website (www.frbservices.org/EPaymentsDirectory/search.html). Enter the DFI number in the Routing Number field and press "search" .

  5. 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 that have not been resolved through normal channels, or who believe that 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 with the IRS. See IRM 13.1.7, Taxpayer Advocate Service (TAS) Case Criteria, if additional information is required.

EFTPS Payment Methods

  1. EFTPS payment methods are identified by the second position of the Electronic Funds Transfer (EFT) number. See IRM 3.17.277.5.3, EFT Number.

  2. A description of each payment type is included in 3.17.277.1.4.1 through 3.17.277.1.4.18.

IRS e–File Electronic Funds Withdrawal (EFT # 200)
  1. Taxpayers who file their tax returns electronically have the option of initiating an electronic funds withdrawal (ACH debit) to make a payment.

    1. Taxpayers enter their bank account information, amount of payment and requested payment date in a payment record that is associated with the e-filed return or form. A separate payment record should be completed for each payment record submitted with a return or form, when multiple payment records are allowed.

    2. Payment records are routed from the e-file programs to EFTPS for processing as ACH debits.

    3. All individual payments and most business payments can be scheduled for a future date, as long as the date is on or before the due date of the return or form. The financial agent will warehouse the payment request until the scheduled date.

    Note:

    For returns that cannot be scheduled, or for returns that are transmitted after the due date, the payment date must be the same as the date the return is transmitted, or within the previous five days.

  2. For additional information, such as allowable forms (tax types), tax periods, etc., please visit www.irs.gov/e-pay (Electronic Funds Withdrawal).

  3. Each e-file submission processing site receives payment record submissions and sends them to the assigned mainframe site (ECC-MEM or ECC-MTB) where data files are created and sent to the EFTPS Production Application for pick-up by the Treasury Financial Agent, via an electronic mailbox.

  4. If the payment file is rejected by the financial agent, it is returned to the ECC-MEM electronic mailbox with the specific reject code noted for the record in error. All rejected records are researched and resolved, usually by editing or deleting the rejected record(s). Knowledge Incident/Problem Service Asset Management (KISAM) tickets are issued as appropriate. Once resolved, the ECC-MEM System Administrator returns the file back to the financial agent, through the electronic mailbox, for processing.

    1. Taxpayers making Electronic Funds Withdrawal (EFW) payments using IRSe-file are not required to be enrolled in EFTPS.

  5. The financial agent will initiate an ACH debit transaction per the form payment request received and send ECC-MEM an acknowledgement file.

  6. The financial agent will include e-file debits, plus any returned payments (transaction indicator 1 or 4) in the regular EFTPS payment files sent to ECC-MEM.

    1. E-file payment records contain payment method 0 in position 2 of the EFT number.

  7. Payment record submissions may be researched using IDRS Command Code (CC) TRDBV for Legacy payments. The Employee User Portal (EUP) should be used to research payment requests submitted through Modernized e-file (MeF).

  8. Taxpayer inquiries regarding Electronic Funds Withdrawal payment requests and/or Letter 4870 should be directed to the IRS e-file Payment Inquiry Service and Cancellation Service at 888-353-4537. It usually takes 7-10 business days from when the IRS e-file return and payment were transmitted for EFTPS to access the payment information.

Automated Clearing House (ACH) Credits (EFT # 210)
  1. ACH credits, also known as EFTPS Through Your Financial Institution, are initiated by taxpayers who contact their bank to send payments to EFTPS.

    1. The credit transaction must be initiated at least one banking day before due date. Specific credit deadlines are determined by each financial institution.

    2. The taxpayer's bank assigns a reference number which remains part of the record and becomes the reference number on EFTPS. The bank should also provide this reference number to the taxpayer for an audit trail.

  2. ACH credits are identified by payment method 1 in the second position of the EFT number.

Electronic Bill Payment (EBP) System (EFT # 213)
  1. Electronic Bill Payments (EBP) can be identified by Position 2, Payment Method 1 and Position 3, Combined Payment Indicator 3 in the EFT number.

    1. The services that currently utilize this application at this time are identified in positions 8 and 9 of the EFT number as 01 for Fiserv. Prior to October 2007, 02 was used to represent payments from Household.

    2. EFTPS Accounting Technicians at the Ogden Campus should call the Fiserv Partner Assist Line at 877-570-7141 if any problems are encountered with Fiserv regarding an invalid TIN. Provide the representative with the TIN, payment date, and payment amount. The representative will try to provide the name, address, and other information they may have for the payment.

    3. If the Partner Assist Line is unable to provide additional information, Ryhan Clanton at First Data Corporation (303-967-8218) should be contacted. You should provide as much information that you have to assist with the research.

    4. If you are unable to resolve the payment issue, the payment must be deleted from EFTPS and sent to Unidentified Remittance File. See IRM 3.17.277.9.4 (3), Deleting Suspense Cases

Insolvency Payments - Chapter 13 Trustees (EFT # 214)
  1. The bankruptcy payment processing for IRS was centralized in October 2005. All chapter 7 and 13 payments have been processed at the Philadelphia Campus since that time. See IRM 5.9.15, Payments in Bankruptcy.

  2. Insolvency uses Data Exchange to transmit files, which is an internet based connection. Trustees and their financial institutions require credentials to access this site.

  3. Insolvency payments are identified by an EFT number beginning with 214.

Automated Clearing House (ACH) Debits (EFT # 22X)
  1. ACH Debits, also known as EFTPS Direct, represent the majority of payments processed by EFTPS.

  2. Enrolled taxpayers using ACH debit must schedule payment by 8:00 p.m. eastern time the calendar day before the payment is due.

    1. Taxpayers, or their representatives, may initiate an ACH debit using the Internet, voice response system or by talking with a customer service representative.

    2. A confirmation number for each payment is provided at the end of the call.

    3. The financial agent will then initiate a debit against the taxpayers routing transit number and bank account on the requested settlement date.

  3. The confirmation number given to the taxpayer is the last eight positions of the EFT number. Reconstruct the complete EFT number, as follows:

    EFT Number Position Name of EFT Number Position
    Position 1 2 - Bank of America
    Position 2 2 - ACH debit
    Position 3 0 through 9 - Combined Payment Indicator (See column 3 of IRM 3.17.277.5.3(4), EFT Number).
    Positions 4 - 7 Year/Julian date of settlement YDDD
    Positions 8 - 15 Confirmation number
  4. ACH debit business and individual taxpayers may also elect to warehouse their payments for settlement up to 365 days in advance.

  5. ACH debits are identified by payment method code 2 in the second position of the EFT number.

  6. Bulk providers may initiate a single ACH debit for multiple tax payments. These payments are identified by a combined payment indicator of 7,8, or 9 in position three of the EFT number. In addition, the specific Bulk Provider is identified by a Bulk Provider number in positions 8 and 9. See IRM 3.17.277.15 (13) for table of Bulk Provider numbers.

  7. EFTPS Single Debit payments are currently limited to fiduciaries who previously filed on magnetic tape. Single Debit payments are identified by combined payment indicator 6.

  8. A modified Single Debit application is available for states to submit payments for the State Income Tax Levy Program (SITLP) or for Alaska to submit payments for the Alaska Permanent Fund Dividend. These payments are identified by tax type codes ending with L (SITLP) or K (Alaska) and a payment method of 5.

Direct Debit Installment Agreement (DDIA) (EFT # 221)
  1. This program collects and processes Direct Debit Installment Agreement payments for taxpayers who have entered into an Installment Agreement with IRS. Files are provided by Collection to the Treasury Financial Agent (TFA), Bank of America. Taxpayer accounts are debited for the amount indicated and payment posting information is returned to the IRS.

    1. These taxpayers do not have to be enrolled in EFTPS.

    2. DDIA payments will be identified by the EFT number beginning with 221 and 02 in positions 8 and 9.

IRS Direct Pay (EFT # 222)
  1. IRS Direct Pay is a payment application that is available to Individual Master File (IMF) taxpayers through IRS.gov. It is a free service that allows taxpayers to make payments directly to the IRS from their checking or savings accounts. Unlike EFTPS, it does not require an enrollment. The taxpayer is, however, required to pass identity proofing in order to proceed through the payment process. EFTPS is used on the back end to process the ACH Debit payments.

  2. IRS Direct Pay is available only to IMF taxpayers. It is not set up for third party providers to make payments. The service can be used for the following payment types:

    1. Installment Agreement

    2. Tax Return (payment with recently filed original return)

    3. Estimated Tax

    4. Proposed Tax Assessment (payment for a proposed amount due based on a CP2000, Notice of Deficiency, or other proposed assessment)

    5. Extension

      Note:

      It is not necessary to file a paper Form 4868, Application for Automatic Extension of Time to File U.S. Individual Income Tax Return, if a taxpayer makes an extension to file payment with IRS Direct Pay.

    6. Amended Return

    7. Form 5329

    8. Shared Responsibility Payment

    9. Other (1040 Only) (payment for an amount owed including an amount shown on a balance due notice (e.g; CP14, CP501, CP503, CP504, CP71C; or a notice regarding a math error)

  3. Identity proofing is required. IRS Direct Pay is responsible for capturing proofing elements and passing them to the IRS through a web service (Return Preparer Registration Identity Verification Service, or RPR-IVS). Their web service sends a response indicating whether the proofing elements match IRS data. A match is required before the user is allowed to proceed. The proofing elements are:

    1. Name

    2. Address

    3. TIN

    4. Tax year

    5. Filing status

    6. Date of birth

    From the 'Verify Identity' page, the taxpayer selects the tax year for verification (within the last 6 years). They must provide the return information for the tax year selected.

  4. Guest users are able to enter their TIN and Confirmation Number (the EFT number) and look up the status of single payments. They are able to reschedule or cancel the payment, provided the settlement date is more than two days away. For example, if a payment is scheduled for a Wednesday, they would be able to reschedule or cancel the payment until midnight of the Monday before.

  5. If a payment is returned or rejected a letter will generate. Letter 5170 explains the reason for the return/reject with information on how to resolve it and that the taxpayer resubmit the payment to avoid penalties and interest accrual.

  6. You may find more information about this application in IRM 21.2.1.48.1, IRS Direct Pay, and, IRM 21.2.1.48.1.1, Responding to IRS Direct Pay Inquiries

IRS2GO
  1. There is a mobile way to make an electronic IMF payment through a smartphone. IRS2Go/Mobile App “Make a Payment” launched on August 20, 2015. It is fast and easy to make a payment. It is also 508 compliant. IRS2GO provides easy access to mobile-friendly payment options like IRS Direct Pay, offering taxpayers a free, secure way to pay directly from their checking, or savings bank account. Taxpayers can also make a credit or debit card payment through an approved payment processor. There will be a fee for the credit card usage. The user should check with the respective credit card providers. Users can access through Google play, download the App Store, or Amazon.

Federal Tax Collection Service (FTCS) Payments (EFT # 23X)
  1. Taxpayers who require same day settlement for an EFTPS payment may initiate the payment through the FTCS.

    • Payments must be initiated by 5:00 p.m. Eastern time.

    • US Bank validates the records and sends payment files to the financial agent.

    • Payments for enrolled and non-enrolled taxpayers are sent to Bank of America.

    • The financial agent sends the payment file to ECC-MEM by 10:30 p.m. on the settlement date.

    • Headquarter (HQ) EFTPS analysts may need to assist the taxpayer to make a same-day payment by providing the following information - To the Taxpayer: To make an electronic same-day Federal Tax deposit, please provide your financial institution with the information requested on the Same-Day Federal Tax Payments Worksheet available on www.eftps.gov. Please type or print clearly. Use the list of Valid IRS Tax Types and Subtypes in EFTPS (following the worksheet) to complete items 5, 7 and 11. You may wish to make photocopies of this blank worksheet for future use. Photocopy the completed worksheet before giving it to your financial institution. To the Taxpayer's Financial Institution: Provide the taxpayer with the most recent procedures outlined in the Making Same-Day Federal Tax Payments guidelines Chapter 3-1 Wire Format Instructions located in the Financial Institutions Handbook.

    • There are no written procedures for an Individual Master File (IMF) same-day payment. If the amount is under $2,000, it will not be cost beneficial for the individual taxpayer to pay using the same-day method. In such cases, encourage the taxpayer to pay through another electronic method such as EFTPS, IRS Direct Pay, or credit/debit card.

  2. All large deposits ($50 million or more), regardless of payment method, require Treasury notification. If a large payment is anticipated, email or call HQ EFTPS Analysts with the payment details. Send to annette.m.dean@irs.gov with a cc to stephanie.thomas@irs.gov.

  3. Per Treasury's Financial Manual Volume 1 Part 6 - Chapter 8500, T/L 563, dated April 1996, ...A minimum of two business days notice is required for deposits totaling $50 million or more. If a deposit of $500 million or more is anticipated, a minimum of five business days notice is required. HQ EFTPS analyst will notify Treasury via phone and send an email to tom.mosimann@treasury.gov.

  4. Treasury has also requested that we identify the industry (for disclosure reasons - do not include specific taxpayer information) when notifying them of these payments. Examples are: Heavy Manufacturing, Transportation, Retail, Food, Pharmaceuticals, Healthcare, Communications, Technology, Media, Natural Resources, Construction, Financial Services, etc.

  5. FTCS payments are identified by payment method 3 in the second position of the EFT number.

  6. The Ogden EFTPS Accounting Unit will access the FTCS database, Single Point, or send a service message requesting additional information if needed for research.

State Levy Programs (EFT #25X)
  1. State Income Tax Levy Program (SITLP) - Since 2004, 13 states have registered and participate in the EFTPS Single-Debit option offered to SITLP participants. Since 2007, an ACH Credit option has been offered to SITLP participants. Twenty one states and the District of Columbia currently use that option. All new states that decide to participate in SITLP are required to use one of the two electronic payment options. Most current states have converted to one of the two electronic options offered by EFTPS.

    1. States participating in SITLP have the option to electronically transmit payment files to the Treasury on behalf of qualified recipients of a state refund that owe a Federal obligation. Submitting the payments electronically eliminates the paper check and listing processing necessary for states that submit payment via paper check.

    2. The Single Debit option allows states to make multiple payments through one electronic transmission and generate a single debit from the state's bank account.

    3. The ACH Credit option allows states to submit ACH Credit transactions on behalf of taxpayers that have had a state refund levied by IRS. The state's financial institution submits the ACH Credit files to the Federal Reserve Bank (FRB). FRB sends the ACH Credit file information to EFTPS for processing. EFTPS then sends IRS payment posting detail information for each taxpayer whose state refund was levied, which is posted to IDRS.

    4. For more information, see IRM 3.17.277.11.6 , Single Debit Program. Also, refer to the EFTPS Single Debit Guide and the EFTPS State Levy Agency Programs ACH Credit User Guide, both of which can be obtained from the Electronic Payment Section of the Accounting and Tax Payment Branch.

Alaska Permanent Fund Dividend Program (EFT # 254)
  1. Alaska Permanent Fund Dividend Program (AKPFD) - EFTPS began processing AKPFD payments in 2014. These levy payments are currently submitted via a paper process. Alaska is the only state participating in the program. The ACH Credit option is used, and the process for AKPFD is very similar to how it works for SITLP. Information can be found in the EFTPS Levy Agency ACH Credit User Guide, noted in (1)(d) above for SITLP. Both IMF and BMF payments are received from Alaska and processed by EFTPS.

Municipal Tax Levy Program (EFT # 255)
  1. Municipal Tax Levy Program (MTLP) - EFTPS began processing MTLP payments in 2014. The program was introduced as a pilot with two agencies in Ohio. These agencies collect and process city income tax refunds for over 260 Ohio cities. The ACH Credit option is used, and the process for MTLP is very similar to how it works for SITLP. Information can be found in the EFTPS Levy Agency ACH Credit User Guide, noted in (1)(d) above for SITLP. As with SITLP, only IMF payments are received from MTLP participants and processed by EFTPS.

Credit or Debit Card Payments (EFT # 26X)
  1. Credit or debit card payments are accepted for:

    • Form 1040, U.S. Individual Income Tax Return - current balance due and current balance due notice

    • Form 1040, past due taxes, installment agreement and prior year payments up to 10 years

    • Form 1040, advance payment of determined deficiency

    • Form 1040, ES (Estimated Tax for Individuals)

    • Form 1040X, Amended U.S. Individual Income Tax Return

    • Form 4868, Application for Automatic Extension of Time to File U.S. Individual Income Tax Return

    • Form 5329, Additional Taxes on Qualified Plans (Including IRAs) and Other Tax-Favored Accounts

    • Trust Fund Recovery Penalty, installment agreement and prior year taxes up to 10 years

    • Form 940, Employer's Annual Federal Unemployment (FUTA) Tax Return - current balance due, installment agreement and prior year taxes up to 10 years, and amended or adjusted

    • Form 941, Employer's Quarterly Federal Tax Return - current balance due, installment agreement and prior year taxes up to 10 years, and amended or adjusted

    • Form 943, Employer's Annual Tax Return for Agricultural Employees - current balance due, installment agreement, and prior year taxes up to 10 years, and amended or adjusted

    • Form 944, Employer's ANNUAL Federal Tax Return - current balance due, prior year, and amended or adjusted

    • Form 945, Annual Return of Withheld Federal Income Tax - current balance due, installment agreement, and prior year taxes up to 10 years, and amended or adjusted

    • Form 1041, U.S. Income Tax Return for Estates and Trusts - current balance due, and prior year taxes up to 10 years

    • Form 1065, U.S. Return of Partnership Income - current balance due, and prior year taxes up to 10 years

  2. Credit and debit card payment options are available through the service providers. Information on fees and programs may vary; direct the taxpayer to the service provider’s websites for additional information on credit/debit card options via the phone or internet. You may also direct the taxpayer to www.irs.gov/epay.

  3. The service provider or software developer transmits the transaction on behalf of the taxpayer and charges a convenience fee which is not reflected in any Treasury revenues.

  4. Credit or debit card payments are identified by a 6 in the second position of the EFT number.

  5. All card payments are processed using modified bulk provider procedures.

    1. The TFA does not maintain any entity records for credit or debit card payments. The name control is provided by the IRS and added to the file by the service provider. The service provider will either add the zip code as provided by the taxpayer during the transaction or as provided by the IRS during the entity validation.

    2. If the social security number (SSN) or employer identification number (EIN) on a credit or debit card payment cannot be validated, the service provider will not forward the payment record to the TFA or the IRS. If any payment within the bulk file cannot be processed, the entire file may be rejected back to the service provider by the TFA to be corrected and resubmitted.

    3. Credit or debit card payments are processed with a payment date matching the date on which the service provider obtained the card authorization. This date is normally 1–3 days earlier than the settlement date. The TFA will process the bulk debit file one business day prior to the settlement date.

Credit or Debit Card Pay By Phone and Internet
  1. Three card processors are authorized by IRS to accept payments directly from the taxpayer:

    1. Link2Gov

    2. WorldPay US, Inc (VPS)

    3. Official Payments (OP)

  2. Taxpayers may initiate a credit card payment through Link2Gov at 1–888–PAY1040 (1–888–729–1040) or its web site, Pay1040 (www.pay1040.com), WorldPay US, Inc. at (844-729-8298) or its web site, payUSAtax (www.payUSAtax.com), or Official Payments at 1–888–UPAYTAX (1–888–872–9829) or its web site, OfficialPayments (www.officialpayments.com/fed).

  3. Taxpayers may initiate an ATM/Debit card payment through Link2Gov at 1–888–PAY1040 (1–888–729–1040) or its web site, Pay1040 (www.pay1040.com), or WorldPay US, Inc. at (1–888–872–9829) or its web site, payUSAtax (www.payUSAtax.com), or Official Payments at 1–888–U PAY TAX (844-729-8298) or its web site, OfficialPayments (www.officialpayments.com/fed).

    1. After processing the card authorization, the service provider sends a pseudo enrollment file of SSNs or EINs to the financial agent using the same electronic data interchange (EDI) formats used by bulk providers.

    2. The financial agent sends a modified enrollment validation file to be verified with the National Account Profile (NAP) at the IRS.

    3. For each valid taxpayer identification number (primary social security number or employer identification number), the returned enrollment validation file includes the name control and zip code of the individual or business.

    4. When the enrollment file is returned, the service provider prepares a debit file for all validated TINs, using bulk provider procedures.

  4. If the enrollment is rejected, the service provider reconciles the credit or debit card charges for rejected TINs and notifies the taxpayer of the rejection. No payment records are sent to the financial agent or to IRS.

  5. Reference numbers consist of a 7 digit confirmation number ending in a 1 for payments made through the Official Payments, a 3 for payments made through Link2Gov, or a 4 for payments made through WorldPay US, Inc. The complete 7 - digit confirmation number is given to the taxpayer at the time the payment is completed.

  6. For assistance resolving credit or debit card payment problems, taxpayers may contact the following credit card processor’s toll free numbers: Official Payments at 877-754-4413, Link2Gov at 888-658-5465, or WorldPay US, Inc at 844-729-8298.

  7. If other IRS employees need payment verification they must research the payment using CC EFTPS. If the employee does not have access to IDRS they may fax payment information to EFTPS Technical Unit Enterprise Electronic Fax (EEFAX) number at 855-295-0850.

  8. Only EFTPS employees can contact Shaneka Hooks of Official Payments at 334-321-4584, Dustin Jones of Link2Gov at 615-665-6731, or Jeff Gardner of WorldPay US, Inc at 615-730-6367 (ext. 330).

Service Provider Payment Inquiries
  1. The service providers will contact the IRS if it is determined that the taxpayer used either the wrong taxpayer identification number (SSN or EIN), tax form or tax period when making their credit or debit card payment or, the taxpayer wants to verify receipt or location of their payment.

  2. The service providers submit a spreadsheet daily to the Ogden Electronic Federal Tax Payment System (EFTPS) accounting technician. Each inquiry on the spreadsheet should contain the correct information for the following fields:

    1. Taxpayer’s name

    2. SSN or EIN (TIN) - From the original payment transaction.

    3. Tax form - From the original payment transaction.

    4. Tax period - From the original payment transaction.

    5. Payment amount

    6. Payment date

    7. Resolution/Comments

    Research and resolve each card payment inquiry. See IRM 21.5.7.4.7.15.1, Electronic Funds Withdrawal (Direct Debit) and Credit Card Payment Tracer, for helpful information. Generally, taxpayers should not receive a refund of the credit or debit card payment. Contact the service provider for clarification of the taxpayer’s request, when necessary (e.g., a credit card payment transfer will overpay the tax module).

  3. When completing the remarks section of the spreadsheet use the following abbreviations:

    Abbreviation Meaning
    PT Payment is there
    IM I moved the payment
    AM Already moved (MM-DD-YYYY)
    PUDMCT Payment unposted and did message and called tech
    PUHBF Payment unposted and has been fixed
    CM Computer moved payment
    PR Payment refunded
    NPF No payment found
  4. In cases where the misapplied card payment results in an erroneous refund, refer to IRM 21.4.5, Erroneous Refunds, for procedures to identify and resolve the issue.

  5. The IRS resolution, for each inquiry, should be notated on the spreadsheet and sent back to the service provider. If we cannot fully comply with the taxpayer’s request (due to offsets, etc.), then only notate that the service provider should advise the taxpayer to contact the IRS at 800-829-1040 (individual) or 800-829-4933 (business) or correspond with the Ogden campus at IRS, Attn: Accounts Management, 1973 N. Rulon White Blvd, Ogden UT 84404.

Integrated e-file and e-Pay
  1. Software developers and service providers accept and process credit or debit card payments as part of electronic filing.

    • A card authorization is initiated at the same time that the electronic return or form is submitted to IRS for validation.

    • Once the electronic return or form has been accepted, the card processor submits a payment file to the TFA using the modified bulk provider procedures.

    • If the electronic return is rejected, a payment record is not sent until the return is corrected and subsequently accepted.

  2. The electronic filing Declaration Control Number (DCN) of the return is sent to IRS in the reference number field. The DCN is a 14 - position number starting with "00" .

  3. IRS may call the e-help Desk at 866-255-0654 for assistance in resolving integrated e-file and pay card payments. In addition, research may be available using CC TRDBV.

  4. Taxpayers should be advised to call their credit card issuer or tax practitioner for assistance in resolving problems not related to the tax liability.

EFTPS Online (EFT # 27X)
  1. www.eftps.gov offers the following features over a Secure Sockets Layer (SSL) connection:

    • General information about EFTPS

    • EFTPS enrollment

    • ACH debit payments

    • Payment cancellation

    • Payment history research for up to 16 months; search, print, or download history by date, tax type, amount, tax form, and other factors

    • Schedule up to four estimated tax payments at once

    • Compliant with Section 508 (accessibility) standards

  2. EFTPS payments made through the EFTPS web site are processed by the financial agent like any other ACH debits, and will be identified by Payment Method "7" .

  3. Participants need a TIN, personal identification number (PIN) and Internet password to access the secure areas of the site.

Railroad Retirement Board (RRB) Payments (EFT # 280)
  1. Effective January 2008, railroads are required to submit Federal Tax deposits for Form CT-1, Employer's Annual Railroad Retirement Tax Return, and Form CT-2, Employee Representative's Quarterly Railroad Tax Return, directly through EFTPS. All prior RRB Link users were express enrolled in EFTPS based on information provided by US Bank.

  2. Prior to January 2008, payments were identified by payment method 8 in the second position of the EFT number.

  3. Railroads sent their federal tax deposits through RRB Link, operated by US Bank (formerly Firstar). RRB Link would forward payment classification information directly to the Railroad Retirement Board.

EFTPS for Federal Agencies (EFT #291)
  1. The FEDTAX system provided an electronic payment method for Federal Agencies of the United States to transmit FTD (Federal Tax Deposits) and to file required employment tax forms. At the end of calendar year 2009, Federal Agency users were transitioned to using EFTPS for Federal Agencies at https://www.eftps.gov/eftps which is operated by Bank of America. Federal Agency tax payments will be processed through the Collections Information Repository (CIR) and is driven by Agency Location Codes.

    1. The EFTPS online statistics report will include the EFTPS for Federal Agencies payments because this application is integrated into the EFTPS infrastructure.

    2. Each payment includes the ALC in the field normally used for the Routing Transit Number.

    3. Call 1–877–333–8292 for assistance in resolving problems with payments made through EFTPS for Federal Agencies, Personal Identification Number (PIN) inquiries or obtaining current contact information for the originating agency.

  2. Federal Agencies may make payments for Form 941, Employer's Quarterly Federal Tax Return, Form 945, Annual Return of Withheld Federal Income Tax, Form CT-1, Form 720, Quarterly Federal Excise Tax Return, and Form 1042, Annual Withholding Tax Return for U.S. Source Income of Foreign Persons, using EFTPS for Federal Agencies.

  3. Payments for federal agencies made through EFTPS for Federal Agencies are identified by the EFT number beginning with 291.

Bulk Provider
  1. A bulk provider is a large dollar payroll processor or reporting agent registered with an EFTPS financial agent to transmit 1,000 or more payments with a single ACH or FTCS transaction. Each set of up to 1,000 payment records is associated with a consolidated debit transaction. The bulk provider program is designed for payroll processors who initiate frequent payments and desire automated enrollment through an Electronic Data Interchange (EDI) compatible system. Because EDI requires a significant investment in software and programming, the Bulk Provider program is recommended only for companies that make payments for 1,000 or more taxpayers. See IRM 3.17.277.11, Bulk Provider Procedures for Bulk Provider Procedures.

Affordable Care Act (ACA) Payments
  1. The Affordable Care Act (ACA) was enacted in March of 2010. It consists of two pieces of legislation: the Patient Protections and Affordable Care Act and the Health Care & Education Reconciliation Act. Combined, they include over 500 provisions. Approximately 50 provisions have been assigned to the IRS for implementation. Some of these provisions are in effect and others will be implemented over the next several years.

Branded Prescription Drug Fee (BPDF)
  1. Section 9008 of the Affordable Care Act imposes a fee on covered entities engaged in the business of manufacturing or importing branded prescription drugs for sale to any specified government program or pursuant to coverage under any such program for each calendar year beginning after 2010. The BPD Fees collected under the section are credited to the Medicare Part B trust fund.

  2. For the whole drug industry, the fee was equal to $2.5 billion in 2011, will grow gradually to $4.1 billion in 2018, and decrease to $2.8 billion in 2019 and subsequent years. The fee will be apportioned among affected covered entities based on each covered entity's relative share of certain sales.

  3. Each covered entity's tax account will have a TC 971 with Action Code (AC) 339 to show they are subject to the fee.

  4. The BPDF payments are mandated to be paid electronically. The payment due date is September 30th. The tax type for the fee is 7200D and the tax period month is "08" . The payment transaction code is 670 with a Designated payment Code of 27.

  5. A TC 290/298 will post the cycle after September 30th.

Insurance Provider Fee (IPF)
  1. Section 9010 of the Affordable Care Act imposes an annual fee on each covered entity engaged in the business of providing health insurance.

  2. The aggregate fee amount for all covered entities (referred to as the applicable amount) is $8 billion for calendar year 2014, $11.3 billion for calendar years 2015 and 2016, $13.9 billion for calendar year 2017, and $14.3 billion for calendar year 2018. For calendar years beginning in 2019, the previous year's fee is increased by the rate of premium growth.

  3. The payment due date is September 30th of each calendar year. The tax type for the fee is 89637 and the tax period month is "09" . The payments will post with transaction code 670 and designated payment code 60 to BMF accounts under MFT 79.

Individual Shared Responsibility Payment
  1. Beginning in tax year 2014, IRC 5000A requires individuals to have minimum essential health coverage, qualify for an exemption, or make an individual shared responsibility payment when they file their federal income tax returns.

  2. The individual shared responsibility payment (SRP) will have its own Master File Type (MFT). The MFT is 35. The MFT 35 will be established with a TC 240 and a unique penalty reference number (PRN) 692 one cycle after the TC 150 posts to the 1040 (MFT 30). If a taxpayer makes an individual shared responsibility payment (SRP) with their federal tax return, the payment will post to their Form 1040 tax module. The SRP will be transferred to the SRP tax module under MFT 35 by master file.

  3. If the taxpayer reports an SRP, but doesn't pay it with their federal tax return, they will receive a balance due notice (CP14H) from the MFT 35 module. It is not mandatory that the taxpayer make the SRP electronically but it is an option.

  4. The tax type for the SRP is 5000X. The 5th position can either be ‘0’ for an amended return, ‘4’ for an advance payment of deficiency, or ‘7’ for a subsequent payment.

  5. The Designated Payment Code is ‘36’.

Employer Shared Responsibility Payment
  1. For 2015 and after, employers employing at least a certain number of employees (generally 50 full-time employees or a combination of full-time and part-time employees that is equivalent to 50 full-time employees) will be subject to the Employer Shared Responsibility provisions under IRC 4980H.

  2. Under the Employer Shared Responsibility provisions, if these employers do not offer affordable health coverage that provides minimum value to their full-time employees (and their dependents), the employer may be subject to an Employer Shared Responsibility payment if at least one of its full-time employees receives a premium tax credit for purchasing individual coverage on one of the new Affordable Insurance Exchanges, also called a Health Insurance Marketplace (Marketplace).

  3. The employer shared responsibility payment (ESRP) will have its own MFT. The MFT is 43. The tax type for the ESRP, is 4980X. The 5th position can either be ‘4’ for an advance payment of deficiency or ‘7’ for a subsequent payment. If an employer anticipates a balance due for the ESRP, EFTPS will accept an advance payment.

  4. The Designated Payment Code ‘43’.

Foreign Account Tax Compliance Act (FATCA)
  1. FATCA was enacted in 2010 by Congress to target non-compliance by U.S. taxpayers using foreign accounts. FATCA requires certain foreign financial institutions (FFIs) to report information about financial accounts held by U.S. taxpayers, or by certain foreign entities in which U.S. taxpayers hold a substantial ownership interest.

  2. EFTPS started processing FATCA payments in January 2015 with the following payment information:

    • Tax Type = 1042 (See Exhibit 3.17.277-1 for tax type codes)

    • Tax Class = 1

    • TIN Type = 2 (BMF)

Foreign Financial Institution (FFI)
  1. Under the FATCA, withholding agents must withhold and deposit tax on certain payments to certain foreign financial institutions (FFIs) that do not agree to report certain information about their U.S. accounts or accounts of certain foreign entities with substantial U.S. owners.

  2. An FFI may agree to report certain information about its account holders by registering to be FATCA compliant. An FFI that has registered and that has been issued a Global Intermediary Identification Number (GIIN) will appear on a published FFI List. The FFI List can be downloaded in its entirety or searched for specific information (FI name, GIIN or country). Search results can also be downloaded. Withholding agents may rely on an FFI’s claim of FATCA status based on checking the payee’s GIIN against the published FFI List. This FFI list search and download tool is available and will be updated monthly. A FATCA-compliant FFI may also be required in certain cases to withhold and deposit tax on payments under the terms of its applicable FATCA status.

Global Intermediary Identification Number (GIIN)
  1. When a withholding agent makes a Form 1042 payment through www.eftps.gov they will have the option to input the GIIN. See IRM 3.21.112.4 for more information about GIINs and their composition. Not every Form 1042 made in EFTPS will have a GIIN. When a GIIN is provided in EFTPS, then the GIIN is in the reference number field of the payment detail record. The reference number field is only 18 characters while the GIIN is defined as 19 characters (including three one-digit separators that are periods). Those separators are not stored in the reference number field, meaning each GIIN is represented by 16 characters in the reference number field. The GIIN will be used to match an FFI with its EIN. When the payment posts to master file, Transaction Code 971 Action Code (AC) 707 will copy the GIIN from the EFPPS Reference Number field into BMF.

Electronic Federal Payment Posting System (EFPPS)

  1. EFPPS is comprised of five major processing functions:

    1. Load and validating the payment transactions,

    2. Controlling the data for accounting purposes,

    3. Edit processing (corrections),

    4. Balancing, and

    5. Generating output transactions to be used for posting to the Master File and reporting to the Redesign Revenue Accounting Control System (RRACS).

  2. The EFPPS computing function is located at ECC-MEM. Four times daily, the FA transmits payment information and deposit data to ECC-MEM for processing through EFPPS. Each payment transaction is assigned a unique Electronic Funds Transfer (EFT) number by the FA.

  3. EFPPS performs "load and validate" checks for transmission, deposit, and batch errors. Examples of these errors are:

    1. Invalid financial agent number or transmission date.

    2. Invalid or duplicate deposit ticket number.

    3. Summary record count not equal to the number of detail records.

    4. Invalid or duplicate batch number.

  4. After the above edits, EFPPS system analysts compare transaction totals captured by EFPPS to totals reported by the financial agent to deposit ticket totals. IRS system analysts call the financial agent when data does not pass the checks so the agent can resubmit corrected data. After all corrections and balancing has occurred, a 20 digit unique trace ID is automatically assigned to all EFTPS payments.

  5. After payment data from individual and business taxpayers and federal agencies have undergone initial edits, transactions that are accepted undergo three additional edits to prepare data for ECC-MTB processing.

    1. The first edit, the On-Line Entity program, matches the TIN and name control against the Corporate Files (CFOL) at ECC-MTB.

    2. The second edit determines whether transactions recorded as FUTA payments are within acceptable range and flags large FUTA payments for further research.

    3. The third edit, the Auto Correct validation program, automatically corrects records such as those with an invalid tax period and assigns payments with no designates tax type to tax class 1.

      Note:

      See IRM 3.17.277.15 (87) for a list of all tax classes.

  6. EFPPS assigns data that did not pass the above edits to IRS Ogden EFTPS accounting technicians who use IDRS to research problems. Corrections are made on-line through theEFPPS Correction Screen. Corrected data goes through the validation routines again. If unresolved, errors continue to appear on the EFPPS Correction Screen whenever the technician accesses the screen. Errors not corrected within 7 days are reported on the CMS 27, EFTPS Age Report. Transactions that pass through all edits are ready for Tape Edit Processor (TEP) processing and transmission to ECC-MTB for Master File processing.

    Note:

    For additional information about the TEP, see IRM 3.17.277.6.7, Tape Edit Processor (TEP).

Federal Payment Levy Program (FPLP) (EFT # 391)

  1. EFPPS receives levy payments from the Fiscal Service (FS) Treasury Offset Program (TOP).

    1. IRS Compliance sends a weekly file of delinquent taxpayers to FS to be matched against Federal disbursement files.

    2. When a match is found, IRS issues a levy notice advising the taxpayer that 15 percent of future disbursements will be seized to satisfy the delinquent tax account.

    3. If the taxpayer has not made arrangements with IRS to settle the debt, FS will begin levying the payments after 30 days (60 days for Social Security).

    4. FS creates a payment file in the TOP format, and sends the file to the ECC-MTB.

    5. The money is transferred to IRS using the Intra-governmental Payments and Collections System (IPAC). The money is not reported on CIR.

    6. The EFTPS deposit tickets are identified by a "C" in the first position of the deposit ticket number. Debit vouchers have a "D" in the first position.

    7. ECC-MTB reformats the TOP file, using a record from IPAC to verify the money, and creates a file in the EFTPS format for processing in ECC-MEM.

    8. ECC-MEM processes the TOP file as its own financial agent (FA03 - "3" in position 1 of the EFT number).

  2. All of the reject conditions that are performed during EFPPS load and validate are included in the ECC-MTB conversion program.

    1. If any reject conditions are identified in ECC-MEM, the EFPPS system administrator should work with ECC-MTB to correct the invalid condition and/or reject the file back to FS.

    2. If any file must be rejected back to FS, Revenue Accounting should reverse the IPAC bill and related journal to send the money back to FS.

  3. Contact Field Compliance Services to resolve any problems with unresolved levy payments. To identify the source of the payment, contact the TOP call center at Fiscal Service at 800-304-3107 Monday - Friday 7:30 AM - 5:00 PM Central Standard Time or refer to IRM 5.11.7, Automated Levy Programs.

  4. Federal Payment Levy Program payments contain "39" in the first two positions of the EFT number.

Social Security Administration (SSA) Levy Program (EFT # 491)

  1. Social Security Administration (SSA) has entered into an agreement with the IRS to honor requests for levies on taxpayers who owe a Federal liability and receive SSA benefits.

    1. Payments are made using the IPAC.

    2. SSA deposit tickets are identified with an "E" in the first position of the ticket number.

    3. The FA Identification number (first position of the EFT number) is "4" .

    4. SSA Levy payments can be identified by an EFT number beginning with "491" .

    5. IRS employees with SSA Levy questions or individual taxpayer issues should refer to SSA Paper Levy Contacts on SERP (Who/Where tab).

    6. IRS employees with systemic related IRS Collection SSA Levy ONLY problems should contact James Maslanka, 630-390-0575. This information is for internal use only. See IRM 5.19, Liability Collection for more information regarding SSA Levies and the collection process.

Remittance Strategy for Paper Check Conversion (RS-PCC) (EFT # 520-524)

  1. This program provides the process for converting paper checks into electronic ACH (Automated Clearing House) Debits. All paper checks will be converted into electronic transaction at the point when they are received. RS-PCC will interface with EFPPS to post taxpayer payment information to Master File. Tax payments that are received at the Philadelphia (Insolvency), Memphis (Offer In Compromise), Brookhaven (Offer In Compromise), Andover, Austin (OVDP), and Atlanta Campuses and all Taxpayer Assistance Centers (TAC) are scanned; taxpayer accounts are debited by FRB-Cleveland; and the posting information is sent to the EFPPS for account posting.

    1. The financial agent designation for RS-PCC will be "5" (first position of the EFT number).

    2. RS-PCC payments can be identified by an EFT number beginning with "520" for campuses and "521" , "522" , "523" , and "524" for TACs.

    3. The 8th and 9th position of the EFT Numbers identifies a specific Campus or TAC. See Exhibit 3.17.277-3.

  2. As of July 2011, all Field Assistance TACs are processing RS-PCC tax payments.

  3. Electronic Federal Payment Posting System (EFPPS)/Remittance Strategy Paper Check Conversion (RS-PCC)/Processing Specifications:

    1. The objective is to process all RS-PCC payments received by EFPPS within 5 business days from date of receipt.

    2. Errors that can not be corrected using normal IDRS research will require additional information from Campus Support.

    3. Request for additional information from Campus Support will be made within 5 business days from date of receipt of the error in EFPPS. EFPPS will have an additional 2 business days to make corrections on RS-PCC payments after receiving additional information Campus Support.

    4. Campus Support will respond to EFPPS requests for additional information within 24 hours of the request.

    Note:

    For purposes of this IRM, EFPPS will be referred to EFPPS to distinguish from the Financial Agent's EFTPS.

Bureau of Alcohol, Tobacco and Firearms (ATF) Payments

  1. On rare occasions, the Bureau of Alcohol, Tobacco, and Firearms (ATF) may contact Ogden EFTPS regarding ATF payments that have already been sent to the IRS in error. A manual refund should not be done on these payments. They need to be transferred to ATF by Intra-Governmental Payment and Collection System (IPAC), located in the Redesign Revenue and Accounting Control System (RRACS). That way, the taxpayer will get credit from when the payment was originally made. When this occurs:

    1. Fill out Form 2424, Account Adjustment Voucher. Indicate in the right hand margin in red ink "1 - EFTPS PAYMENT" .

    2. Debit the taxpayer's account

    3. Credit the 4970 Account to be transferred to ATF by IPAC.

    4. In the explanation section of Form 2424, Account Adjustment Voucher, indicate "EFTPS Payment and the ATF Agency Location Code 2010 0003" . Ensure TXMOD print and email or fax from ATF is attached to Form 2424 for audit trail purposes. This transfers money out of the 4970 Account to ATF by IPAC.

    5. Take documentation to RRACS, who will take to Direct Data Entry (DDE) to input Transaction Code (TC) 652. Many of these are done erroneously as TC 651.

EFPPS Log in Procedures

  1. Once the workstation and monitor are powered up go to the EFPPS website and login. EFPPS login procedures are the same for all users.

  2. Press Continue

  3. Once you are successfully logged into EFPPS the EFPPS Home screen will appear as shown below. See Figure 3.17.277-1

    Figure 3.17.277-1

    This is an Image: 33928001.gif

    Please click here for the text description of the image.

Selecting Work Functions

  1. After the EFPPS Title Window closes, the EFPPS Home Page opens as shown. See Figure 3.17.277-2

    Figure 3.17.277-2

    This is an Image: 33928002.gif

    Please click here for the text description of the image.

  2. The menu items will appear across the top of the Home Page. This means the number of items in the options list may vary for each user based on the profile assigned by the EFPPS manager.

  3. To select one of the menu options using the mouse:

    1. Move the mouse so the screen cursor is on the selected option.

    2. Press the left key on the mouse once.

    3. If a different option is preferred, perform steps 1 and 2 once more.

    4. The EFPPS Home Page closes, and the window for the chosen function opens. Each Main Menu function is discussed in the subsequent chapters.

  4. To select one of the menu options using the keyboard:

    1. Use the [Tab] key until the selected option is surrounded by a dotted line.

    2. Press the [Space bar] .

EFPPS Log Off

  1. The recommended way to log off EFPPS is to select the Logout tab from the menu bar.

Enrollment Procedures

  1. All taxpayers who are required or volunteer to use EFTPS should go to www.eftps.gov to enroll. If internet access is not available, refer the taxpayer to EFTPS Customer Service at 800-555-4477 (business) or 800-316-6541 (Individual) to obtain an enrollment form. Taxpayers should be encouraged to enroll online. Online enrollment is the preferred method.

  2. Enrollment forms should be mailed to EFTPS Enrollment Processing Center, P.O. Box 173788, Denver, CO 80217-3788.

  3. The financial agent forwards the taxpayer entity data to ECC-MEM via electronic transmission. The following information is included on the incoming enrollment request file:

    • TIN (and EIN/SSN indicator)

    • Secondary Social Security Number (for joint IMF filers)

    • Name

    • Address

    • City

    • State

    • Zip Code

  4. "Express Enrollment" is used for all new businesses with a Federal Tax Deposit (FTD) requirement. Upon applying for an EIN via Form SS-4, Application for Employer Identification Number, the taxpayer is automatically enrolled in EFTPS. Enrollment information regarding EFTPS is sent to the taxpayer and the business is notified that activation is required before payments can be made.

Entity Validation of EFTPS Enrollment Requests

  1. The TINs on the enrollment request are matched to the Entity Data on the Corporate Files On-Line (CFOL) at ECC-MTB using command code EFTEA. This process is transparent to the EFPPS Accounting Function.

  2. Command Code EFTEA is generated from EFPPS programs and cannot be input manually. The taxpayer's name and TIN are verified against the Master File.

    If Then
    A matching TIN is found on CFOL, The taxpayer's name, address, fiscal year month, filing requirements (BMF), and filing status (IMF) are returned to EFTPS.
    No matching TIN is found on CFOL, A second check is made against the TIF files for a matching pending transaction, using command code EFTIA (for BMF entities only). If found, the same information is sent to EFTPS.
    The name control from CFOL or TIF matches the name from the financial agent, The taxpayer's Name Control, address, fiscal year month, filing requirements (BMF), and filing status (IMF) are sent to the financial agent coded as approved.
    The name and name control are a proximal match, The record is processed as approved.

    Note:

    A proximal match is any four consecutive non-blank characters in the first name line which match the name control on the Master File. A second proximal match ignores special characters and attempts to match on alpha and numeric characters only.

    No match is found,
    1. The enrollment request is rejected.

    2. The financial agent will notify the taxpayer of the reason for rejection.

    3. The taxpayer or the financial agent must submit a corrected enrollment request.

Enrollment Discrepancy Codes

  1. Enrollment records are returned to the financial agent with the following discrepancy codes:

    Discrepancy Code Accepted Enrollments Meaning/Description
    Code 0 The TIN and name match.
    Code 1 The primary and secondary TIN on the enrollment are reversed on the Master File.
    Code 2 The primary and secondary TINs are reversed. The names may mismatch but are determined to be correct.
    Code 4 The names mismatch but are determined to be correct. The name control from CFOL or TIF matches any four consecutive non-blank characters on the name line.
    Discrepancy Code Rejected Enrollments Meaning/Description
    Code 3 Primary and secondary TINs reversed and the name does not match.
    Code 5 The TIN does not match an existing TIN on CFOL or TIF.
    Code 6 Name mismatch - The name control received from CFOL or TIF does not match any four consecutive characters on the name line.
    Code 7 Secondary SSN mismatch and name mismatch - Financial agent will receive the matching name from the Master File and verify that it is correct.
    Code 8 Secondary SSN and name mismatch but determined to be correct primary taxpayer .
    Code 9 Secondary SSN mismatch and name mismatch.

Resolution of Rejected Enrollments

  1. Taxpayers who need assistance in resolving rejected enrollments are normally referred to the IRS e-help desk at 866-255-0654 (EFTPS is option #3).

  2. Before disclosing any tax information, you must be sure you are speaking with the taxpayer or authorized representative. See the Taxpayer Authentication guidelines in IRM 21.1.3.2.3, Required Taxpayer Authentication . Also, before leaving any messages on a taxpayer's answering machine, review IRM 11.3.2.6.1, Leaving Information on Answering Machines/Voice Mail . Fax procedures contained in IRM 11.3.1.11, Facsimile Transmission of Tax Information must be reviewed prior to faxing confidential information to the taxpayer.

    1. Use command code RFINK to verify that a business taxpayer is represented by the agent on the Reporting Agent File or ask the agent to fax a copy of Form 8655, Reporting Agent Authorization, (or approved substitute).

    2. Use command code CFINK to validate an agent's power of attorney, or ask for a fax copy of Form 2848, Power of Attorney and Declaration of Representative, or substitute.

    3. The EFTPS Batch Provider software includes a feature that requires a third party to initiate an electronic disclosure authorization for individuals within the software. The Form 9783T, EFTPS Batch Provider Individual Enrollment Form, will be provided to taxpayers by their authorized Third Party. The form is available within the EFTPS Batch Provider software only and will be generated at the completion of the enrollment. The signed form will be retained by the third party. For authentication purposes, the electronic authorization requires the taxpayer's 5 digit self-selected Signature PIN, Date of Birth and Prior Year Adjusted Gross Income. This disclosure authorization will be stored by the FA. If needed, ask for a fax copy of Form 9783T. Note, if the individual has a Form 2848 on file with the third party, no other authorization is required.

  3. The e-help desk researches the taxpayer's account to determine the cause of the reject.

  4. Following are some of the more common reasons for enrollments to be rejected and suggested resolutions:

    IF… THEN
    The taxpayer has used a business name rather than the legal name (if a sole proprietor, the legal name is normally the individual’s name) Ask the taxpayer to re-enroll with a new enrollment via the Web. There MUST be a change to the information before EFTPS will trigger a re-entity validation check with IRS (i.e., business or individual name). If there is no change, the enrollment on EFTPS will remain in reject status.
    The name is spelled wrong on IDRS or if IRS records contain a misspelled name, the taxpayer should be asked to enroll using the misspelled name to expedite the enrollment process Have the caller fax a request to correct the spelling on the account to the IRS Entity Department. Have BMF callers fax the request on Company Letterhead. When the name is corrected, EFTPS records will be automatically updated. Fax Numbers: 855-295-0850 (Ogden Entity) or 859-669-5748 (Cincinnati Entity).
    A name change is pending on IDRS, it may take two weeks or longer for a name change to post to the Master File after it has been input on IDRS Ask the taxpayer to wait and resubmit the enrollment in one month.
    Some EINs have aged off the Master File due to lack of usage Refer taxpayer to the Business and Specialty Tax Line number at 800-829-4933. These EINs may be reestablished by following TC 000 procedures.
    There are other problems, such as changes to the business structure or account merges These EINs should be referred to entity control for resolution by calling the Business and Specialty Tax Line at 800-829-4933.
    Internet "20" and "26" EINs are not complete Taxpayer’s on-line Form SS-4 was incomplete. Refer caller to the Business and Specialty Tax Line at 800-829-4933. They will be able to let them know what information is needed to issue the EIN. Encourage taxpayer to wait a minimum of two weeks before making an EFTPS payment before using EIN so it has time to post to Master File.
    Taxpayer calls and indicates that he is unable to input TIN with a "P" on the EFTPS Web. If IDRS shows there is a TIN with a "P" and the taxpayer is trying to make an EFTPS payment, inform the taxpayer that only numbers are allowed in the TIN field on EFTPS Refer taxpayer to Business and Specialty Tax Line at 800-829-4933 to assist them in determining proper TIN to use or if new TIN needs to be established.
    IRS records are wrong and taxpayer wants to correct IRS records before enrolling with EFTPS over the phone To correct IRS records have caller fax the corrections to IRS with any supporting documentation. Fax Numbers: 855-295-0850 (Ogden Entity) or 859-669-5748 (Cincinnati Entity). The updates will take 3 to 5 weeks before they can re-enroll to EFTPS. At that time the taxpayer may resubmit a web enrollment using the correct name. Enrollment changes cannot be made by EFTPS over the phone.
    IRS records are right and taxpayer wants to make the changes to EFTPS over the phone Have the caller re-enroll with a new enrollment via the Web or they can submit changes, in writing, to EFTPS-Denver.
    Taxpayer wants to fax the changes to EFTPS-Denver. Advise the taxpayer that faxes are not allowed to EFTPS-Denver.
    Taxpayer indicates they do not have a Confirmation/Update form. Explain the Confirmation/Update form is obsolete. Have the caller re-enroll with a new enrollment via the Web. For a new enrollment to trigger a re-entity validation check with IRS, there must be a change to the information (i.e., business or individual name changes) from the information they originally used with their first enrollment. If there is no change, the enrollment on EFTPS will remain in reject status.
  5. Other problems, such as changes to the business structure or account merges, should be referred to entity control for resolution.

Enrollment Status on Master File

  1. Each successful enrollment generates a transaction code 971 on the Master File to show that the taxpayer is enrolled in EFTPS, with an Action Code indicating the financial agent. The generated TC 971 will include a Document Locator Number (DLN) of 81977-777-77777. For taxpayers enrolled with Bank of America, the TC 971 action code is 085, and the Enrollment Code is 85.

  2. On rare occasions, it may be necessary to input the enrollment code manually. The enrollment code may have dropped off the Master File due to an account merge, while the taxpayer is still enrolled in EFTPS.

    1. Use command code REQ77/FRM77 to input the TC 971 with action 085 for Bank of America. Enter the transaction date of the original enrollment.

    2. REQ77/FRM77 can also be used to delete the enrollment code from the Master File with TC 972 and action code 084 or 085.

    3. Refer to IRM 2.4.19, Command Codes REQ77, FRM77 and FRM7A for specific command code instructions.

  3. The enrollment code is important because the Master File uses this code to select name, address, and filing requirement changes for the weekly entity update file sent to the financial agent.

Confirming EFTPS Electronic Payment Was Received by IRS

  1. Taxpayers who have questions regarding payments that have posted to Master File and/or want confirmation that an EFTPS payment was received by the IRS should call the IRS Customer Service Business and Specialty Tax Line at 800-829-4933 or IRS IMF Customer Service at 800-829-1040. A successful EFTPS payment will post to the EFPPS database the following day and can be researched using CC EFTPS.

    • Use CC EFTPS with definer "T" to research the database using the taxpayer identification number (TIN), payment date and payment amount.

    • Use CC EFTPS with definer "E" to research the database using the EFT number.

    • Use CC EFTPS with definer "R" to research the database using the reference number and payment year. The reference number may be used when payment was made with a credit card.

    Note:

    Refer to IRM 2.3.70 , Command Code EFTPS for more information regarding CC EFTPS.

  2. Before disclosing any tax information, you must be sure you are speaking with the taxpayer or authorized representative. See Taxpayer Authentication guidelines in IRM 21.1.3.2.3, Required Taxpayer Authentication . Also, before leaving any messages on a taxpayer's answering machine, review IRM 11.3.2.6.1, Leaving Information on Answering Machines/Voice Mail . Fax procedures are contained in IRM 11.3.1.11, Facsimile Transmission of Tax Information must be reviewed prior to faxing confidential information to the taxpayer.

EFTPS Transmission Files

  1. The Financial Agent will transmit EFTPS transaction data to ECC-MEM at least once each business day. In a normal schedule, the financial agent will send files four times each day by (Central Time):

    • 11:00 a.m.

    • 3:00 p.m.

    • 6:00 p.m.

    • 8:00 p.m.

Transmission Format

  1. Each transmission will consist of the following:

    Record Type Number of
    Records
    Required Information
    Transmission Header Record One Count of deposit tickets, debit vouchers, and batches.
    Deposit Ticket Summary Record One or more One record for each deposit ticket or debit voucher included in the transmission. Each deposit ticket may contain up to 9,999 batches of 5,000 transactions. Each deposit ticket or debit voucher may contain only one routing transit number and settlement date.
    Deposit Ticket Detail Record One or more One detail record for each batch of transactions associated with the deposit ticket or debit voucher.
    Batch Header Record One for each DT Detail Record Batches are sorted by Master File type and may contain up to 5,000 transactions. Sequentially, the Batch Header Record immediately follows the Deposit Ticket Detail Record.
    Payment Detail Record One or more One for each payment or debit transaction.
    Batch Trailer Record 1 One for each batch Count summary by tax class and total for each batch.
    Batch Trailer Record 2 One for each batch Amount totals for each batch.
    End of Day Record One or none Present only on the last transmission prior to 5:30 p.m. central time and on the last transmission of the day. It provides the total count and amount for the transmission date.

Financial Agent Rejects

  1. Each transmission from a financial agent is validated to ensure that the file is balanced and that the records do not contain invalid data.

  2. Any transmission, deposit ticket/debit voucher, batch, or enrollment file that fails a system validity check is identified on the Load and Validate Log. Rejects are shown on the Financial Agent Reject Report (CMS 1). See Exhibit 3.17.277-4.

    1. The financial agent should be immediately contacted at 866–684–6556 (Core Hours of Operation: Sunday 10:00 PM MT thru Friday 10:30 PM MT) with the details of the reject. Normally, the contact will be initiated by an EFPPS System Administrator.

    2. The financial agent should correct and retransmit the rejected records within four hours.

    3. For any reject from the Federal Payment Levy Program (Financial Agent 03), the EFPPS system administrator should coordinate with ECC-MCC before notifying FS of the reject condition. The invalid condition may have been caused by an error in the conversion run.

  3. There are four types of financial agent rejects:

    • Transmission rejects

    • Deposit ticket rejects

    • Batch rejects

    • Enrollment rejects

Transmission Rejects
  1. Following is a list of the reject codes for transmission rejects. The entire transmission is rejected and must be resubmitted by the financial agent.

    Reject Code Condition Description
    T 01 Invalid financial agent number The Financial Agent (FA) number in the Transmission Header Record is other than 02, 03, 04, 05 or does not match the agent number in the Deposit Ticket Summary Record or the first 2 positions of any associated batch number.
    T 02 Invalid Computing Center Code Must be 01 for ECC-MEM.
    T 03 Invalid Transmission Number Must be 01 - 99.
    T 04 Duplicate transmission number Must not match previous transmission number for same financial agent and date .
    T 05 Invalid transmission date Transmission date not in valid YYYYMMDD format or greater than current date.
    T 06 Invalid deposit ticket count Deposit ticket count in the Transmission Header Record is not equal to the count of Deposit Ticket Summary Records with record type 7 (deposit ticket).
    T 07 Invalid debit voucher count Debit voucher count in the Transmission Header Record is not equal to the count of Deposit Ticket Summary Records with record type 8 (debit voucher).
    T 08 Invalid batch count The batch count in the Transmission Header Record is not equal to the number of Batch Header Records in the transmission.
    T 09 Invalid record sequence The records in a transmission are not in a valid sequence or the records are the wrong length. (See table below)
    T 10 Out of Sequence Transmission Transmissions from the financial agent must be in sequence, starting with 01 for each transmission date. An out of sequence transmission is held without processing until the transmission(s) with intervening sequence numbers are received and processed. If the transmission still cannot be processed when the first transmission is received for the following day, the out of sequence transmission is rejected.
Transmission Reject Code 9
  1. Records are in an invalid sequence (Reject Code T 09) for any of the following conditions:

    Record Type Sequence
    Transmission Header Record This record must be present at the beginning of a transmission. This record must be followed by a Deposit Ticket Summary Record or End of Day Record. Exception: If resubmitting of a rejected batch, the next record must be a Deposit Ticket Detail Record.
    Deposit Ticket Summary Record All records that follow are assumed to be part of this deposit ticket until another Deposit Ticket Summary Record occurs. This record must be followed by a Deposit Ticket Detail Record.
    Deposit Ticket Detail Record This record must be followed by a Batch Header Record.
    Batch Header Record All Payment Detail Records that immediately follow are assumed to be part of this batch. This record must be followed by a Payment Detail Record.
    Payment Detail Record This record must be followed by another Payment Detail Record or a Batch Trailer Record 1.
    Batch Trailer Record 1 This record must be followed by Batch Trailer Record 2.
    Batch Trailer Record 2 This record must end a transmission or be followed by a Deposit Ticket Detail Record, Deposit Ticket Summary Record, or End of Day Record.
    End of Day Record This record can only end a transmission.
Deposit Ticket Rejects
  1. Following is a list of the reject codes for deposit ticket rejects. The financial agent must resubmit the deposit ticket or debit voucher and all associated batches and transactions.

    Reject Code Condition Description
    D 01 Invalid deposit ticket number The Deposit Ticket/Debit Voucher number on the Deposit Ticket Summary Record is not numeric, or the first position of the deposit ticket number is other than 1 - 9, or the first position of the debit voucher number is other than 0. For Federal Payment Levy Program payments, the deposit ticket number must be "C" for payments or "D" for reversals, followed by five numerics. For SSA Levy payments, the deposit tickets are identified with an "E" in the first position of the ticket number which is followed by a five digit number.
    D 02 Duplicate deposit ticket/ debit voucher number The same voucher number from the same financial agent for the same settlement date.
    D 03 Unmatched deposit ticket/ debit voucher number The Deposit Ticket/Debit Voucher number on the Deposit Ticket Summary Record must match the voucher number on all associated Deposit Ticket Detail Records and Batch Header Records.
    D 04 Invalid settlement date The deposit ticket settlement date:
    • Must be a valid YYYYMMDD date.

    • Cannot be a Saturday, Sunday, or legal holiday.

    • Must not be more than ten business days prior to the current system date.

      Exception:

      This check is bypassed for bulk provider emergency payments with Routing Transit Number (RTN) 021030004.

    • Must not be later than the current system date.

    • Must match the settlement date in all associated Batch Header Records.

    D 05 Invalid tax class amounts Sum of the tax class amounts on Deposit Ticket Summary Record does not equal the total Amount on the same record.
    D 06 Unmatched DT summary and detail amounts The total Amount on the Deposit Ticket Summary Record does not equal the sum of the amounts on the associated Deposit Ticket Detail Records.
    D 07 Unmatched batch count The Deposit Ticket Summary Record batch count does not equal the number of associated Deposit Ticket Detail Records.
    D 08 Invalid RTN The Routing Transit Number (RTN) on the Deposit Ticket Summary Record is not valid for the financial agent. The valid RTNs are:
    Bank of America: 061036013, 061036000.
    111000012 (FEDTAX/EFTPS for Federal Agencies) — Payment method must be "9" (government).
    061036084 (RRB Link).
    US Bank (FTCS): 091036164.
    091036177 (Emergency bulk provider).
    RS-PCC Deposit Ticket will have an RTN of 042000437. The deposit ticket will begin with "1" .
    Federal Payment Levy Program: 20180032 - First two positions of EFT number must be "39" .
    SSA Levy Program 28040001 - First three positions of EFT number must be "491" .
    D 09 Invalid Agency Location Code (ALC) Ogden Agency Location Code 20092900.
    D 10 Invalid tax class 9 amount The amount reported as tax class 9 on the Deposit Ticket Summary Record is not equal to the sum of the associated Deposit Ticket Detail Record Amounts for batches with Master File Type 7.

    Note:

    D08 lists the valid Routing Numbers (RTN). The numbers listed for the Federal Payment Levy Program (20180032) and the SSA Levy Program (28040001) are NOT RTNs, they are Agency Location Codes (ALC).

Batch Rejects
  1. Following is a list of batch reject codes. The financial agent must resubmit the batch header and all associated transactions.

    Reject Code Condition Description
    B 01 Invalid batch number The batch number in the Batch Header Record is:
    • Non-numeric.

    • For resubmitted batches, the first 2 positions of the batch number not equal to the financial agent number in the Transmission Header Record.

    • The 3rd position is not equal to the 4th position of the Transmission Header Record transmission date.

    • Positions 4 - 6 not equal to 001 - 366 or 401 - 766.

    B 02 Unmatched resubmitted batch A re-submission of a rejected batch fails to match the voucher number and money amount of a rejected original batch. Unless the original batch was rejected for invalid batch number, the resubmitted batch must also match on batch number.
    B 03 Duplicate batch number The batch number in the Batch Header Record is equal to a batch number that has already been processed.
    B 04 Invalid batch control date The batch control date on the Batch Header Record is not in a valid YYYYMMDD format.
    B 05 Invalid settlement date The settlement date on the Batch Header Record is an earlier date than the payment date on any associated Payment Detail Record.
    B 06 Invalid EFT number The batch is rejected if the EFT number matches the EFT number of any payment that has previously been processed or if any transaction in the batch is other than:
    Position 1 must equal the 2nd position of the Batch Header Record batch number.
    Position 2 must be numeric
    Position 3 must equal 0 - 9
    Positions 4 - 7 must equal the year digit/julian date (or julian date + 400) of the Batch Header settlement date
    Positions 8 - 15 must be numeric
    B 07 Invalid transaction amount The transaction amount on a Payment Detail Record is zero or non-numeric.
    B 08 Invalid transaction indicator The Transaction Indicator is invalid if it is:
    (a) Other than 0, 1, 4, 8, 9, A, B or R.
    (b) Indicator 1, 4, 9, A or B and the reference number is not present.
    (c) Indicator R with the second position of the EFT number other than 1, 3 or 4.
    (d) Included in the same batch with an incompatible indicator. The transaction indicators that may be combined in a batch are:
    • Indicators 1 and 4

    • Indicators 8 and B

    • Indicators 9, A and R

    Exception:

    For re-submission of a rejected batch, transaction indicator 8 may be mixed with any other credits and Transaction Indicator 9 may be mixed with any other debits.

    B 09 Batch out of balance The count of Payment Detail Records in the batch does not equal the batch total count on Batch Trailer Record 1, or the sum of the transaction amounts on the Payment Detail Records does not equal the batch total amount on Batch Trailer Record 2.
    B 10 Invalid Master File type The Master File Type Code on the Batch Header Record is other than 1 (IMF), 2 (BMF), 6 (NMF) or 7 (Miscellaneous).
    B 11 Unmatched batch number The batch number on the Deposit Ticket Detail Record and Batch Header Record does not match.
    B 12 Unmatched item count The item count on the Deposit Ticket Detail Record does not match the batch total count on Batch Trailer Record 1.
    B 13 Unmatched batch amount The amount on the Deposit Ticket Detail Record does not match the batch total amount on Batch Trailer Record 2.
    B 14 Unmatched credit reversal A credit reversal (transaction indicator R) fails to find an un-reversed original payment with a matching EFT number and money amount.
    B 15 Missing DPC EFTPS for Federal Agencies payments without Designated Payment Code 16 or 17; or Federal Payment Levy Program payment without Designated Payment Code 18 or 19.
    B 16 Unmatched offset reversal or payment offset A payment offset fails to find a matching unidentified payment or a reversal offset fails to find a matching unidentified return or credit reversal.
  2. Rejected batches are established on the control file and suspended, awaiting successful re-submission. See IRM 3.17.277.6.5, Control of Rejected Batches for details on the control of rejected batches.

  3. Re-submission of rejected batches must be on a separate transmission that contains no original payment batches or deposit ticket/debit voucher.

Enrollment Rejects
  1. Following is a list of entity validation reject codes. The financial agent submits enrollment files for validation against CFOL. If a reject occurs, the agent must resubmit the file:

    Reject Code Condition Description
    E 01 Invalid record sequence An Entity Validation Header Record is not followed by an Entity Validation Data Record, an Entity Validation Trailer Record is not the last record on the file or any records are of an incorrect length.
    E 02 Invalid FA ID number The Financial Agent ID number in the Entity Validation Header Record is other than 02.
    E 03 Invalid EIN/SSN Indicator The EIN/SSN Indicator in the Entity Validation Header Record is not equal to 1 or 2.
    E 04 Invalid entity count The count in the Entity Validation Trailer Record is not equal to the number of associated Entity Validation Data Records.

EFT Number

  1. The Treasury financial agent assigns a 15 digit Electronic Funds Transfer (EFT) number. The EFT number is a unique identifier and is used to research payments on the Master File and IDRS. Do not use the Document Locator Number (DLN) to perform research on EFTPS transactions. The EFT number is configured as shown in the following table.

    Position Name Description
    1 FA ID Number 2 - Bank of America
    3 - Federal Payment Levy Program (FPLP)
    4 - SSA Levy Program
    5 - RS-PCC
    2 Payment Method 0 - E-file Debit
    1 - ACH Credit
    2 - ACH Debit
    3 - FTCS (Same Day Wire)
    4 - (Reserved)
    5 - Levy
    6 - Credit Card
    7 - Online
    8 - Railroad Retirement Board (RRB)
    9 - Government Payment (EFTPS for Federal Agencies, FPLP or SSA Levy)
    3 Combined Payment Indicator See table in (4) below
    4 - 7 Year Digit/Julian Date Year digit plus 001 - 366. If overflow, 401 - 766 may be used. The date that the EFT number was assigned.
    8 - 9 Bulk Provider Number See table in (4) below
    8 - 15 (10 - 15 for bulk providers) EFT Sequence Number Randomly assigned number
  2. Whenever the combined payment indicator (position 3) is 7, 8 or 9, the first two positions of the sequence number (positions 8 and 9 of the EFT number) are used to identify the bulk provider who transmitted the payments. The financial agent assigns its own set of bulk provider numbers. See Bulk Provider Number in the glossary for a list of assigned codes.

  3. The Tape Edit Processor (TEP) assigns two additional leading digits to denote the Submission Processing Center Code to which makes the EFT number 17 positions for Master File and IDRS research (except command code EFTPS). The current code is "29" for Ogden. Prior to July 1, 2005 the code was "49" for Memphis.

  4. Positions 8 and 9 are specific to the Financial Agent ID Number, Payment Method, and Combined Payment Indicator. The value may have different meanings. Values in Italics are reserved for future use.

    Position 1
    FA ID number
    Position 2 Payment Method Position 3
    Combined Payment Indicator (Input Method)
    Positions 8-9 (10-11 in IDRS EFT Trace Number)
    Bulk Provider Number
    2 0 - e-file 0 - Null 00 - 99
    2 1 - ACH Credit 0 - Other
    2 - Invalid
    3 - Electronic Bill Payment
    4 - Insolvency
    00 - Null
    For Combined Payment Indicator 3:
    01 - Fiserv (previously Checkfree)
    02 - Household (prior to October 2007)
    03 - OLBP
    04 - Reserved
    2 2 - ACH Debit 0 - VRS, Voice/Rollout Operator
    1 - DDIA
    2 - IRS Direct Pay
    3 - Personal Computer (Prior to 2008)
    4 - API (Prior 2008 - Batch Provider - Now "274" )
    5 - Transmitter
    6 - Single Debit
    7, 8, 9 - Bulk Provider
    00 - Null
    For Combined Payment Indicator 1:
    01 - Paper FTD Conversion
    02 - Installment
    03 - Reserved
    04 - Unmatched
    05 - Instant Pay
    06 - 10 Reserved
    For Combined Indicator 4:
    01 - IRS2GO
    02 - 05 Reserved
    For Combined Payment Indicator 5:
    01 - 50 Reserved
    For Combined Payment Indicators 7, 8, 9:
    01 - 99 Bulk Provider Number
    2 3 - FTCS (Same Day Wire) 0 - Other
    1 - First payment of a split
    2 - Middle payment of a split
    3 - Last payment of a split
    7, 8, 9 - Bulk Provider
    00 - Null
    For Combined Payment Indicators 7, 8, 9:
    01 - 99 Bulk Provider ID Number
    See IRM 3.17.277.16 (13)
    2 5 - Levy 1 - SITLP
    2 - Bank
    3 - Corporate
    4 - AKPFD
    5 - MTLP

    For Combined Payment Indicator 1 (SITLP):
    01 - AL, 02 - AK, 03 - AZ, 04 - AR, 05 - CA, 06 - CO, 07 - CT, 08 - DE, 09 - DC, 10 - FL, 11 - GA, 12 - HI, 13 - ID, 14 - IL, 15 - IN, 16 - IA, 17 - KS, 18 - KY, 19 - LA, 20 - ME, 21 - MD, 22 - MA, 23 - MI, 24 - MN, 25 - MS, 26 - MO, 27 - MT, 28 - NE, 29 - NV, 30 - NH, 31 - NJ, 32 - NM, 33 - NY, 34 - NC, 35 - ND, 36 - OH, 37 - OK, 38 - OR, 39 - PA, 40 - RI, 41 - SC, 42 - SD, 43 - TN, 44 - TX, 45 - UT, 46 - VT, 47 - VA, 48 - WA, 49 - WV, 50 - WI, 51 - WY
    For Combined Payment Indicator 4 (AKPFD):
    02
    For Combined Payment Indicator 5 (MTLP):
    01 - OH-CCA
    02 - OH-RITA
    2 6 - Credit Card 7, 8, 9 - Bulk Provider
    31, 32 - L2G
    59, 60, 61 - OP
    64, 65 - FYT (File Your Taxes.com)
    70, 71 -WorldPay US, Inc
    2 7 - Online 0 - Single Payment
    1 - IPS
    3 - Private Label
    4 - Batch Provider
    5 - Trusted Partner Interface (TPI)
    00 - Null
    2 8 - RRB Link 0 - Null 00 - Null
    2 9 - Government 1 - FEDTAX/EFTPS for Federal Agencies 00 - Null
    3 9 - Government 1 - Federal Payment Levy Program 00 - Null
    4 9 - Government 1 - SSA Levy 00 - Null
    5 2 - ACH Debit 0 - RSPCC Campus 00 - Campus Discovered Remittance
    01 - PAMC Insolvency, 02 - PAMC Perfect, 03 - PAMC Imperfect, 04 - PAMC Field Office, 05 - BAMC Perfect, 06 - BAMC Imperfect, 07 - MAMC Perfect, 08 - MAMC Imperfect, 09 - BAMC COIC, 10 - MAMC COIC, 11 - ANAMC Perfect, 12 - ANAMC Imperfect, 13 - ATAMC Perfect, 14 - ATAMC Imperfect, 15 , 16, 17 - AUSPC (OVDP), 18 - PSC Disc Remit19 - PSC Mail Perfect, 20 - PSC Mail Imperfect, 21 - BSC Disc Remit, 22 - BSC Mail Perfect, 23 - BSC Mail Imperfect, 24 - MSC Disc Remit, 25 - MSC Mail Perfect, 26 - MSC Mail Imperfect, 27 - ANSC Disc Remit, 28 - ANSC Mail Perfect, 29 - ANSC Mail Imperfect, 30 - ATSC Disc Remit, 31 - ATSC Mail Perfect, 32 - ATSC Mail Imperfect
    5 2 - ACH Debit 1 - RS-PCC TAC
    2 - RS-PCC TAC
    3 - RS-PCC TAC
    4 - RS-PCC TAC
    See Table in Exhibit 3.17.277-3.

Transaction Indicators

  1. Transaction Indicators are assigned by the financial agent to distinguish between the different types of transactions. EFTPS also uses the transaction indicator to distinguish between debits and credits, and to assign the correct transaction code.

  2. The EFT Transaction Indicators are shown in the following table. See Exhibit 3.17.277-2 for exceptions.

    Transaction Indicator Meaning Debit or Credit Description
    0 Payment Credit Taxpayer payment, will normally post 6X0 transaction to taxpayer's account
    1 Return, Taxpayer Error Debit Dishonored payment, will normally be processed as a TC 6X1
    4 Return, Non-Taxpayer Error Debit Corrected payment, will normally be processed as a TC 6X2
    8 Unidentified Payment Credit Payment that cannot be connected to a taxpayer by the financial agent. The FA should send an offsetting record.
    9 Unidentified Return Debit Debit that cannot be connected to a taxpayer by the financial agent. The FA should send an offsetting record.
    A Payment Offset Debit Offset to Unidentified payment. EFTPS matches "A" record to "8" , then removes both from active status on the system and control file.
    B Return Offset Credit Offset to Unidentified Return or Credit Reversal. EFTPS matches "B" record to "9" or "R" , then removes both from active status on the system and control file.
    R Credit Reversal Debit Bank error. If reversal is accepted, the record will normally be processed as TC 6X2. If not accepted, the FA must submit a "B" offset record.
Electronic Reject/Offset Mismatch Report, CMS 2
  1. If an 8, 9, A or B record is received without a match, the record is sent to suspense to wait for the offset to arrive, and listed on the Electronic Reject/Offset Mismatch Report (CMS 2). See Exhibit 3.17.277-5.

  2. This report will be emailed by the System Administrator weekly (on Friday) to the financial agent at Rhonda.Lord@firstdata.com.

    1. Some records are listed only because of timing. The offset record may have already been initiated for settlement on the next day.

    2. The financial agent must review the list to ensure that an offset record is being generated.

    3. In some cases, a contested dishonored return cannot be offset. See IRM 3.17.277.9.1.1 , Contested Dishonored Returns for procedures.

    4. Cases more than one year old should be referred to Unidentified Remittance File.

  3. Transaction Indicator "8" records should NOT be moved out of suspense for seven calendar days. This allows time for the financial agent to possibly supply offsetting record. See IRM 3.17.277.6.4.3, Manual Suspense to Error.

Credit Reversals

  1. Financial institutions or taxpayers may initiate a reversal of an ACH credit or a same day FTCS payment.

    1. If there is an unpostable condition, make the same corrections, if any, to the payment reversal as was made to the original payment.

    2. IRS EFTPS technicians will only provide appropriate research for the Unpostable Unit.

    3. No other manual adjustments should be done by EFPPS technicians.

      Note:

      Refer to IRM 3.17.10.4, Deposit Discrepancies regarding Deposit Discrepancies.

  2. Credit Reversals are received by the financial agent and matched to the file of original payments. Reversals are automatically approved by the financial agent if:

    1. The reversal finds a payment with the same TIN and money amount,

    2. The matching payment had a settlement date within the five previous banking days, and

    3. The matching payment was not already reversed with a credit reversal.

    4. If more than one matching payment is found, the record with the latest settlement date is selected.

  3. Credit reversals that do not meet the above criteria are disapproved.

    1. A disapproved reversal is sent to IRS as an unidentified return, transaction indicator 9.

    2. The financial agent then initiates a return offset, transaction indicator B.

  4. Approved credit reversals are sent to IRS with:

    1. The same TIN, name control, tax type, tax period, and money amount that was present on the original payment.

    2. The Original Payment Date on the reversal record is set to the payment date of the original payment.

    3. The EFT number of the original payment in the Reference Number field.

    4. Transaction Indicator R.

  5. The EFPPS load and validate program matches the reversal to the original payment by EFT number.

    1. If unable to find the matching record, the money amount is different, or the payment has already been reversed, the batch is rejected back to the financial agent.

    2. If the match is successful and the original payment has already been processed (not in error, suspense, or still being validated), the reversal record is automatically corrected, if necessary, to match the information on the payment, then sent to TEP.

  6. At the time the reversal was validated, if the matching record was in error, suspense, or still being validated, the reversal is sent to unresolved status.

    1. Although the record is assigned to unresolved, it cannot be selected for correction.

    2. When the original payment is corrected, the next TEP will retrieve the reversal record and change the tax information to match the original payment.

    3. If the original payment is deleted, the reversal is also deleted during the TEP.

Electronic Payment Control File

  1. The Electronic Payment Control File (EPCF) provides control of electronic payments from the time of receipt from the financial agent until the payments are sent to the appropriate Master File for posting.

  2. Transaction files and deposit ticket records are received simultaneously from the financial agent.

    1. Each deposit consists of up to 9999 batches.

    2. Each batch is expected to be limited to 5,000 transactions, although this is not a systemic requirement.

    3. The batch is the basic unit of control on the Electronic Payment Control File.

Control File Suspense Accounts

  1. The Daily Trial Balance of Electronic Payment Control File is balanced to each of four EFPPS General Ledger Accounts using the EFPPS Daily Balancing screen.

  2. Balance the control file to the following general ledger accounts:

    Account Number Account Name
    4125 EFPPS Suspense for BMF
    4225 EFPPS Suspense for IMF
    4425 EFPPS Suspense for NMF
    4765 EFPPS Miscellaneous (MISC) Suspense
  3. Account 4765, Miscellaneous Suspense, is used for any payment that is determined to be erroneous (Transaction Indicator 8 or A for credits or 9 or B for debits), in which the financial agent already knows that a reversal will be sent and for "miscellaneous" payments (Master File 7).

    1. Miscellaneous payments are payments not identified as IMF, BMF or NMF by the financial agent, such as user fees or not recognized as valid IMF, BMF or NMF Tax Types in Load and Validate.

    2. Federal Payment Levy Program payments are initially journalized manually into Account 4765 from the IPAC record, without supporting data on the EFPPS Payment Control File. Until the data file is received by EFPPS and the automated journal processed, Account 4765 must be manually reconciled. See IRM 3.17.277.7, Revenue Accounting Procedures.

Procedures for Balancing to General Ledger Account using EFPPS Daily Balancing Screen
  1. To access the Daily Trial Balance Screen, click on the Daily Trial Balance tab on the Menu bar. See Figure 3.17.277-3

    Figure 3.17.277-3

    This is an Image: 33928003.gif

    Please click here for the text description of the image.

  2. To view the current date information click on the ‘Current Date’ button. See Figure 3.17.277-4

    Figure 3.17.277-4

    This is an Image: 33928004.gif

    Please click here for the text description of the image.

  3. choices are -
    Current Date - Report Date and CCycle are filled in with the most current information.

  4. Choose the account - BMF, IMF, NMF or MISC - you wish to work on. The related account information is displayed.

    • Section I subtotal is the sum of the previous day balance, CMS 30 DT/DV summary, CMS 24 Reclassification Summary and CMS 22 Trans Release Summary totals.

    • Section II subtotal is the sum of the Batch Control Inventory, Error Inventory and Suspense Inventory on the CMS 29 Daily Posting Summary.

    • The total sum(s) are the same as the subtotals. Section I and Section II are compared. If they do not agree, a message will display an out of balance condition and the amount of the out of balance. See Figure 3.17.277-5

      Figure 3.17.277-5

      This is an Image: 33928005.gif

      Please click here for the text description of the image.

    • The MANUAL ADJUSTMENTS and COMMENTS sections are provided for data entry. MANUAL ADJUSTMENTS amounts can only be a total of 21 characters. Commas are an option; do not use dollar signs. A minus sign "-" is used for negative amounts (the number will be displayed in brackets). If the number includes cents, use a decimal point (not required for whole numbers). The Section I total is recalculated if data is entered in this section. If an error occurs, a message will appear. See Figure 3.17.277-6

      Figure 3.17.277-6

      This is an Image: 33928006.gif

      Please click here for the text description of the image.

  5. In the event that manual balancing is needed, utilize the following procedures for each general ledger account to balance each day as follows:

    1. Start with the previous day's balance of the account;

    2. Add the deposit ticket totals;

    3. Subtract the debit voucher totals;

    4. Add or subtract the reclassification totals (add for a credit increase or subtract for a credit decrease);

    5. Subtract the net credit amount from the Trans Release Summary (add if a net debit). Bypass this step for account 4765 and 4425;

    6. The total is the ending balance for the general ledger account that you are balancing, and should equal the sum of the batch control, error, and suspense ending inventories on the Daily Posting Summary.

      Note:

      Currently, EFPPS completes the balancing. Follow the above procedures only if absolutely necessary.

  6. Upon completion of RRACS month-end processing, the RRACS function will provide EFPPS with a copy of the M-Trial (Monthly General Ledger Trial Balance of the EFPPS accounts) and EFPPS Activity Report.

    1. Review the EFPPS general ledger accounts dated the last day of the month to ensure that the EFPPS accounts agree with the M-Trial.

    2. If an out-of-balance condition occurs, immediately notify the RRACS function. The out-of-balance condition should be carried as a reconciled adjustment until the next processing month.

    3. An EFPPS Activity Report will be generated by RRACS and provided to EFPPS technicians on a daily basis. This report will include all automated and any manual journals that appear in each of the EFPPS accounts, i.e., 4125 (BMF), 4225 (IMF), 4425 (NMF) and 4765 (MISC). See Exhibit 3.17.277-31 .

    4. The CUR and CUM totals would be the same as the RRACS Report #051 - General Ledger Account Details that is currently provided for each of the four accounts.

Reports Needed for Balancing
  1. The following reports are needed for balancing:

    Report Number Report Name
    CMS 1 Financial Agent Reject Report (may be used if out of balance occurs)
    CMS 22 Trans Release Summary—Daily and Weekly
    CMS 24 Reclassification Summary
    CMS 29 Daily Posting Summary
    CMS 30 Deposit Ticket/Debit Voucher Summary Report
Deposit Tickets/Debit Vouchers, CMS 9
  1. Deposit tickets and debit vouchers are identified as follows:

    1. Bank of America deposit tickets are numbered with a 6, 7, or 8 in the first position and debit vouchers with a 7 or 8 in the second position. Bank of America vouchers have RTNs 061036000 and 071036210 for ACH credits or 061036013 and 071036207 for ACH debits and a 2 in the second position of the associated batch numbers.

    2. FTCS deposit tickets can be identified by Routing Transit Number 091036164.

    3. Bulk-provider same day payments are identified by Routing Transit Number 091036177.

    4. Railroad Retirement Board (RRB) deposit tickets, prepared by US Bank (formerly Firstar) and processed with Routing Transit Number 061036084, are numbered with a 5 in the first position and debit vouchers with a 6 in the second position. EFTPS for Federal Agencies (formerly FEDTAX, which is decommissioned) payments are identified by RTN 111000012.

    5. Federal Payment Levy Program deposit tickets are identified with a "C" in the first position and RTN 20180032. The RTN is actually the FS Federal Payment Levy Program agency location code, and the deposit ticket is not reported on CIR.

    6. SSA Levy Program deposit tickets are identified with a "E" in the first position and RTN 28040001. The RTN is actually the Social Security Administration's agency location code, and the deposit ticket is not reported on CIR.

    7. All RS-PCC Deposit Tickets begin with "1" .

  2. All debit vouchers are numbered with a zero in the first position and a number other than zero in the second position. The first position of a deposit ticket number is other than zero. Exception: Debit vouchers from the Federal Payment Levy Program contain a "D" in the first position.

Deposit Ticket/Debit Voucher Summary Report, CMS 30
  1. Provide a copy of the Deposit Ticket/Debit Voucher Summary Report as a check list for the deposit tickets and debit vouchers for the current process date to RRACS. RRACS will use the report to balance daily with CIR. In the event there are missing items, EFPPS in Ogden will contact EFPPS in Atlanta who will create emergency Ad Hoc DT/DV which will be emailed/faxed to EFPPS in Ogden and HQ.

Control Records

  1. The Electronic Payment Control File (EPCF) control balances are based on From and To codes, indicating counts and amounts passing through the control system on the way to Master File. This is an extremely large report and rarely printed.

    From Code To Code Purpose Description
    0 0 Master file change. Generated when financial agent has assigned payment to the wrong Master File or error correction changes tax type to a different Master File. System generated only.
    0 2 From batch control to delete Generated when an offset (transaction indicator A or B) finds a matching Unidentified record, or input from the Manual Delete screen.
    0 3 From batch control to error status Separate control record generated for each payment identified as error by system.
    0 4 From batch control to suspense Generated for each Unidentified, NMF and MISC batch. Also generated from Manual Suspend and Manual Delete for records in batch control status.
    0 5 From batch control to Master File Generated by TEP for all records sent to Master File.
    1 0 From financial agent to batch control Generated to establish control of batches received from the financial agent.
    2 4 From delete to suspense Record created from the Manual Undelete screen to move a deleted item back to suspense on the same day that the record was deleted.
    3 0 From error to batch control Corrected error record. One control record for each corrected error.
    3 4 From error to suspense Error record in which "suspend" option is selected or record selected on Manual Suspend screen.
    4 0 From suspense to batch control Manual control record created from Manual Unsuspend screen to return suspended record for re-validation and processing.
    4 2 From suspense to delete Manual record to delete from suspense using Manual Delete screen or generated deletion of Unidentified batch (trans indicator 8 or 9) when offset is received.
    4 3 From suspense to error Manual record to return erroneous "deletion" to error correction using the Manual Suspense to Error screen.
    9 9 Information record Manual record created from the Manual Remarks screen to provide audit trail information only.
  2. The Electronic Payment Control File maintains the following item count, debit and credit amount balances for each batch:

    Payment Control File From Code
    Batch Control Code 0
    Good Tape Code 5
    Error Code 3
    Suspense Code 4
  3. Every action on the EPCF is created by the posting of a control record with a from and to code.

  4. All control records are output to a Control Record List (CMS 25). See Exhibit 3.17.277-17. This listing is saved to a reports file, but printed only upon request.

  5. See IRM 3.17.277.10.2, Control File Research for instructions on control file research.

  6. Control records contain the following elements:

    Element Name Length Remarks
    Batch Number 10 Must be present
    Agent Number 2 Must be present on 1–0 record (Present only on the research screen).
    From Code 1 0, 1, 2, 3, 4, 9
    To Code 1 0, 2, 3, 4, 5, 9
    Master File Type 1 1, 2, 6, 7 or blank
    From Master File Type 1 1, 2, 6, 7 or blank. Present only for reclassifications.
    Control Date 9 Generated DD–MON–YYYY date the record was created.
    Item Count 8 Must be present. Zero for 9 - 9 control records.
    Amount 18 Must be present. Zeros for 9 - 9 control records. Stored as signed - for debits, displayed with sign reversed.
    Voucher Number 6 Deposit ticket/debit voucher number. Must be present on 1 - 0 control records.
    EFT number 15 Must be present on all records with from or to code of 3 and on manual control records with count of 1.
    Remarks Text 25 Must be present on manual control records.
    Employee Number 10 Generated into manual control records.
    Sequence Number 10 Generated number indicating the sequence in which records were created for a batch on the control file. (Not shown on CRL or research screen)
    Archived Indicator 1 Used to mark the record for removal from control file.
  7. All generated control records must contain the batch number, from-to code, Master File type, date, item count, amount and sequence number.

Batch Control Record
  1. The batch control record establishes control on the EPCF for each new batch.

  2. Additional required elements:

    • From Code (1 = Financial Agent)

    • To Code (0 = Batch Control Record)

    • Deposit ticket or debit voucher number 6 positions

Master File Change Record
  1. If records have been incorrectly identified by Master File, a control record is generated to assign count and amount to the correct file. It is determined during the initial balancing of a transmission that records in a batch have been incorrectly identified by Master File, a control record is generated to assign count and amount to the correct file.

    1. The record may be created during initial validation for records that have been batched incorrectly.

    2. This control record is also generated for records that have been reclassified due to changes from the correction screen.

    3. This control record is always system generated.

  2. Additional required elements:

    • From Code 0

    • To Code 0

    • New Master File type

    • From Master File type

    • Count and amount of change

Good Block Proof Record
  1. As each batch of transactions are cleared to Master File through the TEP, Good Block Proof Records are created as part of the transaction file sent to ECC-MTB. The Good Block Proof Record also posts to the EPCF with the following From and To codes:

    • From code 0

    • To code 5 (good tape)

Error Record
  1. A separate control record is generated for error items within each batch. Repeat ("loop" ) errors create separate control records each time the record is corrected and sent back to error. This control record contains the following:

    • From code 0

    • To code 3 (error)

    • Item count of 1 (EFPPS validates payment records individually and creates a new control record each time the record is sent to error or corrected from error)

    • EFT number

Corrected Error Record
  1. As each error record is corrected and returned to batch control status, an error correction control record is generated with the following:

    • From code 3

    • To code 0

    • Item count of 1

    • EFT number

Suspend Control Record
  1. Suspense status is used for items or batches that are being removed from normal processing to await deletion by Accounting or to await a generated offset from the financial agent.

    1. A suspend control record is generated for each item or batch that is sent to suspense status.

    2. See IRM 3.17.277.9, Suspense Inventory for procedures on correcting Suspense records or IRM 3.17.277.6.4.1, Manual Deletes for deletes.

  2. The following elements must be present for suspended batches:

    • From code 0 (from batch control) or From Code 3 (from error).

    • To code 4 (suspense)

    • EFT number if the item count is 1

  3. Suspended items are included on the New Suspense List and on the EFPPS Age Report until either a generated update or offset record is received from the financial agent or the record is manually deleted or corrected by Accounting.

Control File Error Codes

  1. The following invalid conditions should be identified by the EPCF and resolved by the Systems Analyst before transactions are sent to the Master File.

    Error Code Description
    1 A duplicate Batch number has been created.
    2 A Good Tape Record, Error Record or Suspense Record attempts to move more items or amount than the current count or amount for that status.
    3 Any Control Record other than a "1 - 0" fails to find a matching batch number.
    4 Any Control Record or change in status which would leave the Control File record with an open count and no amount or a zero count and an amount.
    5 The entire batch control balance (count and amount) is not reduced to zero by posting of generated Good Tape Records (0 - 5) associated with running the TEP. This check does not apply to manual control records.
  2. Many of these conditions are identified immediately and cause the records to be rejected without the control record being created.

  3. Error codes are listed at the top of the Control Record List (CMS 25). See Exhibit 3.17.277-17.

  4. Research the batch on the control file to identify the cause of the error. Manually enter any control records that are necessary to suspend or delete the invalid record or batch.

    1. In some cases it may be necessary to suspend the batch so that the TEP can be completed while the error code is being researched. If a specific transaction is identified as the cause of the error code, the EFT number can be manually deleted. Then the batch can be unsuspended to complete processing.

    2. Remember that any record that is manually deleted must be manually journalized into RRACS. If the transaction represents "real money" , the deleted record must be manually controlled on some other system, such as the Non-Master File or unidentified remittance file.

  5. Some error codes, such as error code "1" for a duplicate resubmitted batch number, require no corrective action.

Manual Control Records

  1. The EFPPS function has the sole responsibility for the input of manual control records to the Electronic Payment Control File.

  2. Authority to adjust or input manual control records is controlled by the EFPPS user profile, which is approved by the EFPPS Team Manager.

  3. Each manual control record must be carefully documented.

    1. Documentation on the control file must include sufficient information (e.g., EFT Number, DLN, SCCF) to locate the transaction on another system or to locate the offsetting record on EFPPS.

    2. Include necessary information in the "Remarks" field on the manual record or on a supplemental Manual Remarks record.

  4. All manual control records are listed at the top of the Control Record List (CMS 25). See Exhibit 3.17.277-17.

  5. From the EFPPS Home Page, select theResearch/Correction tab. Then select Control Menu tab. The Control Menu displays the following options: See Figure 3.17.277-7

    Figure 3.17.277-7

    This is an Image: 33928007.gif

    Please click here for the text description of the image.

    1. These are the control record options available for manual input.

    2. Each of the Control Menu input screens display the same fields. Depending on the screen selected, some of the fields will require input, some have optional input, some have generated value and some must be blank.

    3. Remember that debit amounts must be signed with a "−" . Credit amounts are not signed. Omit commas and leading zeros. Enter as follows:

    Amount Enter as:
    $1,000.00 credit 1000 or 1000.00
    $1,234.56 debit −1234.56
Manual Deletes
  1. The Manual Delete screen is used to remove records from active status on the control file and the data file. See Figure 3.17.277-8.

    Figure 3.17.277-8

    This is an Image: 33928008.gif

    Please click here for the text description of the image.

  2. The batch number, item count, amount, remarks and from code must be entered. The bottom of the screen shows the cursor field and data that has been entered in the field.

  3. The from code is normally "4" to delete items that are in suspense status. From code "0" may also be used to delete an item in batch control.

    • If from code "0" is used, the count must be 1 and the EFT number and amount must match an open item. A "0 - 2" control record is generated to delete the record.

    • From code "4" may be used to delete single items from suspense or to delete all of the suspense items within the batch.

    • Items in error status must be suspended before they can be deleted.

  4. For single items,

    • The EFT number must be entered and match a record in suspense or batch control status,

    • The item count must be 1 and

    • The amount must match the amount of the record being deleted.

  5. For batch deletes from suspense,

    • The EFT number must be blank and

    • The count and amount must match the total count and amount of the suspense status items within the batch.

  6. A "4 - 2" control record is generated for each Manual Delete record that is processed.

  7. In a rare case in which records for more than one Master File are in the batch being deleted, separate records are created for each Master File.

  8. Follow local procedures to prepare and number Form 3244, Payment Posting Voucher, for processing the transaction to another system. Be sure to include Electronic Payment Indicator "1" and the EFT number on the replacement document.

  9. Use the manual delete screen to remove items from EFPPS that must be controlled to some other file or system, such as the Unidentified Remittance File or Automated Non-Master File.

  10. As EFPPS deletes have no automated interface with RRACS, be sure that the appropriate journal record is prepared for RRACS.

  11. Use the EFPPS Deleted Records List (CMS 3) as a check list for controlling deleted records. See Exhibit 3.17.277-6.

  12. The deleted record list and supporting documentation should be held for 10 years.

Manual Undelete
  1. If you make a mistake and delete a record that should not have been deleted, the Manual Undelete screen can be used to retrieve the record on the same day only.

  2. This screen will return the record to its previous status.

  3. Enter the batch number, amount, remarks and EFT number on the screen and commit. See Figure 3.17.277-9

    Figure 3.17.277-9

    This is an Image: 33928009.gif

    Please click here for the text description of the image.

Manual Suspense to Error
  1. Use the Manual Suspense To Error option to:

    1. Apply suspended Transaction Indicator "0" .

    2. Reverse the decision made by error correction that a record should be suspended. See Figure 3.17.277-10.

      Figure 3.17.277-10

      This is an Image: 33928010.gif

      Please click here for the text description of the image.

    3. Bring a suspend "unidentified" or "offset" record (transaction indicator 8, 9, A or B) to unresolved status. Use this option only when the missing information is known and can be added to the record.

    4. Do not move transaction indicator "8" records out of suspense for seven calendar days. This allows time for a possible offset record. See IRM 3.17.277.5.4.1, Electronic Reject/Offset Mismatch Report, CMS 2.

    Note:

    If Manual Suspense to Error is used for a record with transaction indicator "8" or "B" , the transaction indicator is changed to "0" . Transaction indicator "9" or "A" is converted to "4" .

  2. Enter the batch number, money amount, remarks, and EFT number on the screen and commit.

    1. The EFT number must match the number of a record that was suspended.

    2. Item count 1, from code "4" , and to code "3" are generated.

  3. This control record will send the payment transaction back to error status with the same invalid condition that was previously on the record. Advise error correction of your proposed corrective action.

Manual Suspend
  1. Use the Manual Suspend option to remove a batch or single record from active processing and to prevent the record from being passed to the TEP. See Figure 3.17.277-11.

    Figure 3.17.277-11

    This is an Image: 33928011.gif

    Please click here for the text description of the image.

  2. Enter the following fields:

    • Batch number

    • Remarks - Enter any audit trail information.

    • EFT Number - must be entered if the count is 1, blank for an entire batch

  3. The system will generate a record with from-to-code "0 - 4" for items in batch control status and a separate "3 - 4" record for each item in error status.

  4. Use this option to prevent posting of any batch or record that is identified as a balancing error, duplicate record, or other potential balancing problem.

  5. When the problem is resolved, the records will be deleted or unsuspended.

Manual Unsuspend
  1. Use the Manual Unsuspend option to send suspended records back to their previous status. See Figure 3.17.277-12.

    Figure 3.17.277-12

    This is an Image: 33928012.gif

    Please click here for the text description of the image.

    1. Do not use this option to unsuspend records that were suspended by error correction or by initial validation by the EFPPS system.

    2. This option generates a "4 - 0" control record and sends the payment records back for initial validation. If any records were in error, the same error condition will send the records back to error with separate "0 - 3" records.

Manual Remarks
  1. Use the Manual Remarks option to add an addenda record to the control file as an audit trail. See Figure 3.17.277-13.

    Figure 3.17.277-13

    This is an Image: 33928013.gif

    Please click here for the text description of the image.

    1. Enter the batch number. The batch number must match an existing batch on the control file.

    2. Enter the additional audit trail information in the Remarks field.

    3. The from - to code is generated "9 - 9" .

    4. All other fields are blank or zero.

  2. If "1" is entered in the Remarks field, the system automatically fills it with "Unidentified to Error" . The Remarks field contains 25 positions. If more information is needed, use additional Remarks records.

    1. Remarks are listed in at least one current report, CMS 25 Report EFTPS Control Record List.

Control of Rejected Batches

  1. Each batch of EFPPS transactions that is rejected back to the financial agent is controlled on the Electronic Payment Control File. Control of rejected batches is essential because the deposit ticket has been accepted, and EFPPS would otherwise be out of balance with the RRACS general ledger.

    Exception:

    If the rejected batch contains a zero money amount, the batch is not controlled and a replacement batch is not required.

  2. Each rejected batch is established on the control file with a "1 - 0" control record, for the Master File designated on the record from the financial agent.

    1. If the batch has been rejected because of a duplicate batch number, a pseudo batch number with a leading minus sign "(−)" is assigned. The original batch number is shown in the remarks position on the "1 - 0" control record.

    2. If the original Master File is other than "7" (miscellaneous), a "0 - 0" control record assigns the batch to Master File "7" .

  3. The rejected batch is suspended with a "0 - 4" control record to wait for the corrected batch to be submitted. The remarks field on the "0 - 4" record contains the literal "Rejected Batch" .

    1. Use the Financial Agent Reject Report (CMS 1) to identify and monitor suspended batches that have not been resubmitted. See Exhibit 3.17.277-4.

    2. Do not attempt to manually delete the batch from suspense. The batch will be deleted automatically when the replacement batch is received.

    3. Payments from Rejected Batches will not appear on the New Suspense List (CMS 28) or the EFTPS Age Report (CMS 27) because no transactions are present in the data file. See Exhibit 3.17.277-20 and Exhibit 3.17.277-19, respectively.

    4. If Rejected Batch is shown on last page of CMS 28, notify System Administrator.

  4. Payments in rejected batches are assigned to tax class "9" .

    1. During initial EFPPS validation, all payments are added by tax class and compared to the classification on the deposit ticket.

    2. Any discrepancies, including differences caused by rejected batches, are included on the EFTPS Reclassification Summary (CMS 24).

    3. On CMS 24, if the Tax Class 9 amounts does NOT match Misc Total a re-class must be done on the RRACS system.

Resubmitted Rejected Batches
  1. When the corrected batch is received, the suspended batch (or pseudo batch) is deleted with a "4 - 2" control record and the replacement batch is established with a "1 - 0" record.

    1. If the replacement batch has a different batch number, the Remarks field of the control file will include the cross reference batch number.

    2. If the replacement batch has the same batch number, both "1 - 0" records will be present on the control file. The second record will be error coded as a duplicate on the Control Record List (CMS 25), but no correction is necessary once it is determined that the original batch was deleted without any transactions being processed.

  2. For each resubmitted batch, the payments are reclassified from tax class "9" to the tax classes of the resubmitted payments. If the resubmitted batch had the same tax class totals as the original batch and was received on the same day, the reclassifications will offset each other and not be shown on the Reclassification Summary (CMS 24).

Suspending Records Prior to Tape Edit Processor

  1. IRS EFPPS does not provide for deleting records from the TEP or after the TEP is completed. If a large number of erroneous or duplicate payments were included on the TEP, contact Information Technology (IT) to have the system restored to pre-TEP status.

  2. To prevent questionable records from being selected for the TEP and being sent to Master File, use the Manual Suspend option from the Control Menu. See IRM 3.17.277.6.4.4, Manual Suspend for procedures.

    1. To suspend an entire batch, enter the batch number and the total count and amount of the batch. Leave the EFT number blank.

    2. To suspend a single record, enter the batch number, EFT number, count of 1, and the amount of the payment record.

    3. In the remarks field, enter the reason for the suspend, plus any cross-reference information, such as the batch number of a duplicate batch.

  3. Once the Manual Suspend record is accepted by EFPPS, all of the records in the batch (or the selected single record), except records that have already gone to TEP, suspense, or delete, are moved to suspense status on the EFPPS data base and on the control file.

  4. To unsuspend the records, use the Manual Unsuspend option, and the records will be returned to their previous status. Records without error conditions will be selected for the next TEP.

  5. See IRM 3.17.277.9, Suspense Inventory for instructions on working the suspended records.

Tape Edit Processor (TEP)

  1. The EFPPS TEP converts batches of processed IMF and BMF transactions into the Revenue Receipt transaction record format acceptable to Master File processing.

    1. The TEP selects every IMF and BMF record that is in "resolved" or "awaiting quality review" status (process code "9" or "10" ).

    2. The TEP output file, EFT 1501 is identical in format to the file created by GMF-15-01 in normal IRS center processing.

    3. To ensure consistent reports, the TEP should be run with the same date as the validation and correction activity. That is, if the TEP is run at 2:00 a.m., the date on the TEP posting file should be the previous day's date. The date is set by the computer operator as part of the "Create TEP Posting File" menu option.

  2. It is important that no other activity occur on EFPPS from the time of nightly shutdown until the TEP is completed.

    1. This is necessary so that all of the nightly reports and TEP reports will reflect the same data.

    2. Accounting and Enterprise Operations will establish a schedule for nightly shutdown and TEP that will permit the TEP to be balanced without adversely affecting error correction or the loading and validation of new files from the financial agent.

  3. Balance the Daily Posting Summary (CMS 29) and EFPPS Control Record Summary (CMS 26) to the Trans Release Summary (CMS 22) and Revenue Receipts Control Sheet (CMS 23) prior to releasing the TEP. Never release the TEP to ECC-MTB without approval by Accounting.

  4. The TEP is initiated using an option from the EFPPS Home Page based on the operator profile.

Document Locator Number
  1. The DLN is assigned during TEP with the following positions:

    DLN Positions Description
    1 - 2 File Location Code - FLC 81, 82, and 83 for electronic payments processed in ECC-MEM but worked in Ogden.
    3 Tax class
    4 - 5 Document Code 19
    6 - 8 Julian date - Settlement Date. To avoid creating duplicate DLN's the Julian date will increase by 400 when all possible DLN's have been created with the normal Julian date under each FLC.
    9 - 11 Block number - numbers are assigned sequentially, then repeated. The block number does not have to be unique. IRC § 6603 Deposits, formerly known as Cash Bond payments (tax type code ending with "B" ) are assigned block number 990 - 999.
    12 - 13 Serial number - assigned sequentially, then repeated
    14 Year digit - the year of the Julian date
  2. The TEP blocks all payments by Master File type, tax class and settlement date in blocks of 100 or fewer payments for processing by ECC-MEM.

    1. Blocks are not linked to batches. The payment records assigned to a block could have originated in several different batches.

    2. Remember that EFPPS DLNs may not be unique. The EFT number is the unique number used for payment research and audit trails and is included in the revenue receipts record.

TEP Reports
  1. The Trans Release Summary and Revenue Receipts Control Sheet (RRCS) must be included with the tape release file.

  2. The Trans Release Summary (CMS 22) lists total counts and amounts for all Master Files on a single report. See Exhibit 3.17.277-14.

    1. The Daily Trans Release Summary (CMS 22) is automatically sent as part of the TEP file to ECC-MTB. This report is identified for ECC-MTB as file EFT1545.

    2. Send the Weekly Trans Release Summary (CMS 22) to ECC-MTB every Thursday.

  3. The Revenue Receipts Control Sheet (CMS 23) accumulates by tax class the amount of revenues that are being sent to Master File for posting. See Exhibit 3.17.277-15.

    1. This report provides separate debit and credit totals for each tax class for IMF and BMF.

    2. Revenue receipts are accumulated by fiscal year of the settlement date. The range of dates is set by EFPPS, based on the TEP date and the cycle calendar included in the program. The dates are from the beginning of the fiscal year to the last day of the current month. The "Current" field of the report shows the inclusive dates included as current revenue. "Future" revenues have settlement dates later than the "To" date, and "Prior" revenues have dates earlier than the "From" date.

    3. When the last TEP is run for a weekly cycle on Thursday morning, a separate Weekly RRCS accumulates the revenues from all of the TEPs that have been run during the week.

    4. When the weekly RRCS is received, add the daily tax classes and balance the sum of the daily tax classes to the weekly tax classes. Balance the sum of the Daily Total Debit and Daily Total Credit figures. If an imbalance condition exists, notify the EFPPS Systems Administrator immediately. See IRM 3.17.30.9.2.2, Weekly Revenue Receipts Control Sheet (RRCS) and Tape Edit Processor (TEP) and IRM 3.17.30.9.2.3, Weekly RRCS Balancing .

  4. The EFPPS cycles are based on a Thursday through Wednesday week. Ensure that any TEP file dated Thursday is not released until after ECC-MTB cycle cutoff time for the previous cycle.

  5. Both the Daily and Weekly Revenue Receipts Control Sheet (CMS 22) are required for balancing by the ECC-MTB Processing Validation Section. The reports are sent to ECC-MTB each week using the File Transfer Protocol (FTP).

  6. The Daily Trans Release Summary (CMS 22) and Revenue Receipts Control Sheet (CMS 23) are programmed to provide cumulative information based on the TEP date. If two or more TEPs are run for the same date, be sure to notify ECC-MTB. The final report for the date must be balanced to sum of the transaction records for all TEPs for the date.

Revenue Accounting Procedures

  1. The EFPPS provides a daily automated journal file for posting transactions to RRACS. The Accounting Technician contacts the Submission Processing RRACS Headquarters unit and the CFO RRACS OS:CFO:FM:A:S office to receive further instructions for journals that did not post to RRACS.

  2. If the EFPPS batch journal does not post to RRACS, the accounting technician must prepare a manual journal.

  3. IRS EFPPS creates four types of activity that require Redesign Revenue and Accounting Control System (RRACS) input to the general ledger.

    • Deposit ticket journals

    • Debit voucher journals

    • Deposit reclassification journals

    • TEP journals

  4. IRS EFPPS is designed to provide an automated journal file for daily posting to the RRACS database at the Detroit Computing Center (ECC-DET). RRACS journals may also be prepared manually from printed EFPPS reports. See IRM 3.17.63, Accounting and Data Control — Redesign Revenue Accounting Control System, for additional instructions.

  5. Journals are posted based on the month in which the activity occurred. For month end processing, deposit tickets and debit vouchers with settlement dates in the following month must be journalized separately. If it appears a delay in EFPPS payment processing will go beyond the second business day of the month, contact the HQ analyst regarding the potential of a large Month End Statement of Difference.

  6. RRACS will provide a daily EFTPS Activity Report # 143 to assist in balancing and reconciling the EFPPS accounts.

    1. The report will include all automated and any manual journals that appear in each EFPPS account, i.e., 4125 BMF, 4225 IMF, 4425 NMF and 4765 MISC.

    2. The report will be sorted by Journal Number, Process Date, and the Debits and Credits.

    3. Separate totals - Monthly Debit Amount Current, Monthly Credit Amount Current and Net Monthly Amount Current - will be given for each of the four EFPPS Accounts.

    4. Separate totals - FY Cum Debit Amount, FY Cum Credit Amount and Net FY Amount - will be given for each of the four EFPPS accounts.

    5. The CUR and CUM totals would be the same as the RACS Report 051 - General Ledger Account - that currently provides for each of the four accounts. See Exhibit 3.17.277-30.

Deposit Ticket Journal

  1. Each deposit ticket sent by EFPPS to RRACS is based on the classification provided by the financial agent.

  2. RRACS uses the Deposit Ticket/Debit Voucher Summary Report (CMS 30) as an index to make sure that all deposit tickets have been received and journalized, and to validate the journal totals.

  3. The automated journal is number 110. If a manual journal is required, prepare a 210 journal from a printed copy of the EFTPS Deposit Ticket to support each journal. The printed deposit ticket lists all of the batch numbers that have been included on the deposit. See Exhibit 3.17.277-9.

    1. Debit the appropriate 2100 tax class accounts or tax class "9" , revenue suspense.

    2. Credit one or more of the RRACS general ledger suspense accounts.

    Account Number Account Name
    4125 EFPPS Suspense for Master File-BMF
    4225 EFPPS Suspense for Master File-IMF
    4425 EFPPS Suspense for NMF
    4765 EFPPS Miscellaneous Suspense
  4. Deposit tickets are sorted by settlement date in the EFPPS system.

  5. The deposit ticket does not identify user fees and non-revenue items. Non-revenue deposit items are classified into account 4765, then reclassified.

  6. Deposit tickets from the Federal Payment Levy and Social Security Administration Levy Programs are journalized to different accounts because the money is received through IPAC, rather than CIR.

    1. When the money is received via IPAC, a manual 580 journal is completed to debit account 2910 and credit account 4765 by a RRACS Data Base Administrator (DBA).

    2. The EFPPS journal 114 debits account 4765 and credits 2910, and debits the account 2100 tax classes and credits the appropriate EFPPS suspense accounts.

    3. RRACS is programmed to recognize the Federal Payment Levy deposit ticket journal record by the Record Code "5" . Normal EFPPS deposit tickets contain record code "1" .

Debit Voucher Journal

  1. Each EFPPS Debit Voucher contains tax classification information provided by the financial agent.

  2. RRACS uses the Deposit Ticket/Debit Voucher Summary report (CMS 30) as an index to make sure that all debit vouchers have been received and journalized, and to validate the journal totals.

  3. RRACS uses the printed debit voucher as the source for journalization. See Exhibit 3.17.277-10.

  4. The automated journal is number 111. If a manual journal is required, prepare journal 221 to debit the appropriate suspense accounts and credit the 2100 tax class accounts.

  5. For Federal Payment Levy and Social Security Administration Levy Program debit vouchers, a manual journal from the IPAC record debits account 4765 and credits 2910. Then the EFPPS 114 journal debits 2910 and credits 4765, and debits the appropriate EFPPS suspense accounts and credits the 2100 tax classes. The journal record from EFPPS is identified by Record Code "6" .

Deposit Reclassification Journal

  1. The source document for the automated reclassification journal, number 112, is EFTPS Reclassification Summary (CMS 24). See Exhibit 3.17.277-16. Any payment or debit transaction that can be reclassified by the EFPPS system is included on the EFTPS Reclassification Summary, including the following types of transactions:

    1. Any payment or debit record that was mis-classified by the financial agent.

    2. Any record that was changed to a different tax class or Master File by error correction.

    3. Any record that was changed to a different tax class or Master File as a result of an auto correction during load and validate.

    4. Batches that have been rejected during EFPPS Load and Validate. The payments are reclassified to Master File "7" , until a corrected batch is resubmitted. Because the reclassification program is unable to determine the original Master File, the EFTPS Reclassification Summary will show rejected batches as coming from BMF.

    5. Special fund payments that were classified as tax class "9" , revenue suspense by the financial agent, but were assigned tax type codes that EFPPS is able to further classify. EFPPS assigns a pseudo tax class, which is printed on the Reclassification List. These include:

    Tax Type Code Pseudo Tax Class Description
    68770 P Photocopy fees
    01210 C Conscience Fund
    54321 O Installment Fee (original)
    54323 R Installment Fee (reinstatement)
    54324 E Enrolled Agent Fee
  2. Tax class "9" must equal Master File "7" (Miscellaneous Account 4765). If an imbalance occurs, RRACS should notify EFPPS in Ogden, who will alert EFPPS Programmer/HQ analyst as needed. EFPPS in Ogden will provide RRACS with manual journal information.

EFTPS Reclassification Summary
  1. The EFTPS Reclassification Summary (CMS 24) is divided into two parts: See Exhibit 3.17.277-16.

    1. Part 1 is the Tax Class Reclassification, containing the net change in tax classes, as identified by a comparison between the tax type codes and the deposit ticket, and by changes in tax types made by error correction or auto correction.

    2. Part 2 is the Master File Reclassification, based on a comparison between the tax type codes and the Master File in the batch header, plus Master File changes created by auto correction and error correction.

    3. Both parts include a Net Change column that can easily be used to create a reclassification journal.

    4. Verify Tax Class 9 Suspense Total amounts equals Misc Total on the CMS 24. If not, contact RRACS for manual reclassification.

  2. The EFTPS Reclassification List includes detail records with the following information:

    1. Deposit ticket or debit voucher reclassifications list the batch number, EFT number, amount, from and to tax class and tax type code for all items that are identified as tax class "9" , a special fund (alpha tax class), and are identified as "load and validate" .

    2. Auto corrections or error corrections that change the Master File or tax class include the batch number, EFT number, from and to tax class, from and to Master File, from and to tax type and a source of "load and validate" , "resubmitted" or "error correction" .

    3. Batch reclassifications, from a comparison to the batch header (that do not also affect the deposit ticket), contain the batch number, EFT number, from and to Master File and source "batch re-class" .

    4. Batch rejects are listed with the DT/DV number, batch number, to tax class "9" , to Master File "7" and "batch reject" .

    5. Resubmitted batch rejects are listed with the DT/DV number, batch number from tax class "9" and from Master File "7" .

Manual Reclassification
  1. Prepare a manual reclassification journal 250 or 400 for items not included in the reclassification summary. Be sure to document the changes with a manual reclassification list with the EFT numbers used in the reclassification and retain the list or worksheet as permanent documentation for the reclassification journal.

  2. A manual reclassification journal is only necessary for items not included on the Reclassification Summary, if the automated journal fails, or it contains an error.

Out of Balance/Reclassification/Manual Adjustments
  1. If the system is out of balance you will need to manually write the adjustment on CMS 24.

  2. You will need the following:

    1. A copy of each Daily Trial Balance (BMF, IMF, NMF, MISC) which has a manual adjustment,

    2. CMS 1, (Financial Agent Reject Report),

    3. First page of the CMS 24, and

    4. Part II of CMS 24 that lists the rejected batches.

  3. At the bottom right corner of CMS 24, page 1, write DR, the appropriate account #, and the amount for the account(s) that have a bracket around the money amount in the manual adjustment field of the Daily Trial Balance. Write CR, the appropriate account #, and the amount for the accounts that do not have a bracket around the money amount in the manual adjustment field of the Daily Trial Balance. Repeat for each Debit (DR) and Credit (CR).

  4. Using CMS 1 and the DT/DV Number, locate the unresolved batch rejects in Section II of CMS 24. Add the amounts for each tax class in the FROM column and include the totals of each one on the bottom right corner of the CMS 24. Include CR and the RRACS account number for each tax class. See IRM 3.17.277.16 (85) for the RRACS account numbers.

  5. Add all DR amounts and subtract all CR amounts. The total should be zero.

Tape Edit Processor (TEP) Journal

  1. A TEP journal record is prepared for each Master File as EFPPS records are sent to ECC-MTB.

  2. The automated journal is number 113. If a manual journal is required, use the EFTPS Revenue Receipts Control Sheet (CMS 23) to prepare journal 417 for BMF and 418 for IMF.

  3. For the normal credit balance, debit the ECC suspense account and credit the EFPPS suspense account.

    1. For BMF, debit account 4110 and credit 4125.

    2. For IMF, debit 4210 and credit 4225.

  4. If the report has a debit balance, debit and credit accounts are reversed.

Error Correction

  1. The correction screens allow the user to view a complete EFT transaction containing invalid elements and to identify and correct the invalid condition(s) causing the error.

  2. The following elements are correctable within an EFT transaction:

    • Taxpayer Identification Number (TIN)

    • Name Control

    • Tax Type Code

    • Tax Period

    • Origination Date

    • Payment Date

    • Original Payment Date

    Note:

    Origination Date, Payment Date, and Original Payment Date can only be corrected if they are in error status.

Four Types of Payment Validations

  1. Financial agent validation - The financial agent compares the TIN and tax type of the incoming payment to the enrollment database.

    1. If the TIN does not match an enrolled taxpayer, the payment may be rejected back to the taxpayer's financial institution immediately depending on the type of payment.

    2. If the tax type is inconsistent with the enrollment filing requirements or an accepted payment is for a non-enrolled taxpayer, an indicator is generated by the financial agent so that the record will be re-validated on CFOL by IRS.

  2. CFOL validation - Each payment record that is marked as invalid or not enrolled by the financial agent or the TIN has been changed by error correction is validated against CFOL to verify the TIN, name control, and tax type.

    1. Any payment record that is invalid on CFOL is sent to error correction.

    2. CFOL validation is performed by Command Code EFTPA. Command Code EFTPA can only be initiated by the EFTPS program.

  3. Auto correction - The following records are automatically corrected:

    1. For FTD payment types, the tax period is automatically corrected to match a valid year or quarter ending month.

    2. Form 1040-ES, Estimated Tax for Individuals, payments are changed to subsequent payments if the current date is more than 8 months later than the tax period.

    3. Taxlink tax types are corrected to their equivalent EFPPS tax types.

    4. Blank tax types for EIN taxpayers are changed to 94105 (Form 941 FTD).

    5. Form numbers in the tax type code field are converted to the equivalent FTD tax type code.

    Note:

    Auto corrected records are not sent to error correction. However, other types of errors are identified by the EFPPS program prior to the records being auto corrected. While correcting another error, you may notice that a tax period is incorrect. It is not necessary to correct the invalid tax period unless the field is identified as being in error.

  4. IRS EFTPS validity checks include other conditions which cause payments to be sent to error correction described in 3.17.277.8(2).

Access and Input Procedures

  1. To access the EFT Correction Screen from the Home Page using the mouse, click on the Research/Correction tab. See Figure 3.17.277-14.

    Figure 3.17.277-14

    This is an Image: 33928014.gif

    Please click here for the text description of the image.

  2. The Correction Screen appears showing the following options.

    1. Select the next unassigned unresolved payment by clicking 'Next',

    2. Select Assigned Unresolved EFT by selecting an EFT number from the drop down menu, or

    3. Enter the EFT number in the 'Enter EFT Number' field.

    Figure 3.17.277-15

    This is an Image: 33928015.gif

    Please click here for the text description of the image.

Unassigned Unresolved Payment
  1. Unassigned Unresolved Payment is the first option on the Correction Screen. When you click on the 'Next' button, the next available unresolved payment record will populate in the 'EFT Transaction Details/Correction section of the Correction Screen. After the payment is worked you will need to click the 'Next' button to access the next unassigned unresolved payment. When there are no more unassigned unresolved payments to correct you will receive an error message stating "There are no more Unresolved Records not Assigned" . See Figure 3.17.277-16.

    Figure 3.17.277-16

    This is an Image: 33928016.gif

    Please click here for the text description of the image.

Assigned Unresolved
  1. The Assigned Unresolved option will always be displayed. To select a previously assigned error record :

    1. Place the pointer on the drop box arrow and press the left mouse button once and scroll through the EFT number list to select the EFT number you want to open. See Figure 3.17.277-17.

    Figure 3.17.277-17

    This is an Image: 33928017.gif

    Please click here for the text description of the image.

  2. The EFT transaction is displayed on the Correction Screen.

    1. The invalid field is highlighted in yellow.

    2. The number of unresolved elements for this transaction is displayed at the bottom of the EFT Transaction Details/Corrections box.

    3. After a change is input to the record and the ‘Commit’ button is selected, the current value and previous value of the element corrected will show up at the bottom section of the screen (under the number of unresolved elements. See Figure 3.17.277-18.

      Figure 3.17.277-18

      This is an Image: 33928018.gif

      Please click here for the text description of the image.

Enter EFT Number
  1. The third option to view an unresolved payment record is to enter the EFT Number in the 'Enter EFT Number' field and click 'Submit'.

Correction Entry
  1. Correction Entry (Commit)—To correct a field in error, enter the correction data in the text entry box.

    1. Click the commit button at the bottom of the screen.

    2. A question pop up window appears. See Figure 3.17.277-19

      Figure 3.17.277-19

      This is an Image: 33928019.gif

      Please click here for the text description of the image.

    3. If the correction should be transmitted, position the pointer on the "Yes" button and press the left mouse key .

    4. If the correction entered is invalid, an error message appears across the top of the screen. Reenter the correction data and repeat the steps above.

    5. If the correction should not be transmitted and you would like to return to the correction screen, position the pointer on the no button and press the left mouse key .

    Note:

    Research IRM references 3.17.277.8.3 through 3.17.277.11 before committing any changes.

No Change
  1. If no change is necessary for an unresolved element click the commit button at the bottom of the screen. select "Yes" when the pop-up window asks: "Do you wish to commit record?" .

  2. If the record contained a CFOL error, it may be necessary to Commit the record a second time.

Resequence Indicator
  1. It may be necessary to delay the posting of the corrected EFPPS transaction due to another transaction pending at Master File, such as a name or TIN change. This indicator is activated when the TIN, Name Control or Type of Tax fields do not match CFOL.

    1. Select "Yes" if the correction must be re-sequenced for two cycles at the Master File to wait for an entity change to post.

    2. Select "No" if no entity change is necessary.

Undo Entry
  1. If correction data was entered inaccurately, the information from ALL text entry boxes can be cleared and returned to their original (error) field values by clicking the “Undo” button at the bottom of the screen. See Figure 3.17.277-20.

  2. If an incorrect entry has been committed, see IRM 3.17.277.12.8, Retrieve Record to be Reworked for instructions for the manager to retrieve the record.

    Figure 3.17.277-20

    This is an Image: 33928020.gif

    Please click here for the text description of the image.

Abort Entry
  1. If an unresolved payment needs further research before it can be worked, click the abort button at the bottom of the screen. See Figure 3.17.277-21

  2. Upon execution of the Abort key, the record will appear in the Assigned Unresolved drop down menu. See

    Note:

    The error record will remain in the unresolved inventory assigned to the employee that performed the Abort command. Only that employee can retrieve and continue work on the error correction record, unless reassigned. See IRM 3.17.277.8.2.2, Assigned Unresolved for instructions on retrieving records from the Assigned Unresolved window.

    Figure 3.17.277-21

    This is an Image: 33928021.gif

    Please click here for the text description of the image.

Suspend Record
  1. Certain situations, such as an item waiting for an offset, require records flagged for error to be removed from the error correction inventory and placed in suspense status on the control file.

  2. Click on the "Suspend" button at the bottom of the screen. See Figure 3.17.277-22. Then click on accept.

    Figure 3.17.277-22

    This is an Image: 33928022.gif

    Please click here for the text description of the image.

Taxpayer Identification Number (TIN)

  1. Description -The TIN is a unique number assigned for identification of a business taxpayer (EIN) or an individual taxpayer (SSN).

  2. Invalid Conditions -The TIN is invalid if:

    • Not equal to nine numeric digits

    • All nines

    • All zeros

    • Does not match a valid TIN on CFOL

  3. Research the invalid condition using IDRS (Integrated Data Retrieval System), RS-PCC, and/or the FTCS database.

  4. If it is necessary to exit EFPPS prior to initiating research:

    1. Click on the abort button on the bottom of the screen.

  5. The error record will remain in the unresolved inventory assigned to the employee that performed the Abort command.

TIN Research
  1. Research using the IDRS command codes.

    1. Use CC ENMOD to research for possible new EIN or recent EIN changes.

    2. Use CC INOLE or BMFOL/IMFOL to display Master File entity data for specific Taxpayer Identification Number (TIN) residing on the CFOL database.

  2. Research the FTCS database (Single Point) for taxpayer information or information about the bank at which the payment was initiated.

  3. If Single Point is not available, contact the FTCS coordinator at the US Bank on 800-382-0045. The FTCS Coordinator will need the EFT number, TIN, payment amount, and payment settlement date in order to research for the taxpayer's data.

  4. If you are unable to get into Single Point or the current day payment information has not been uploaded, contact Sherri Mccracken (primary) at 314-425-1848 or Mary Schulteis(secondary) at 314-425-1849. If Sherri and Mary are unavailable call Commercial Services at 877-224-8070. You will need to provide the EFTPS profile name.

  5. Based on information provided from the FTCS, it may be necessary to contact either the taxpayer or the taxpayer's financial institution.

    1. If sufficient taxpayer information is provided but a discrepancy is still present, contact the taxpayer to secure the correct information. If a telephone number or the taxpayer's identity is not available, contact US Bank Customer Service via a service message to contact the taxpayer's financial institution to secure the correct information.

    2. To send a service message, complete the Service Message Request Form. All fields are required. They include the name of the employee sending the request, their work phone number, the date of the wire, the dollar amount, the TIN (last four digits only), the EFT Number (if available), and a message to the originator (explain what information is needed in this field). Send the completed spreadsheet to: customer.care@usbank.com via secure email.

  6. If additional research is necessary for bulk provider payments, contact the bulk provider. Positions 8 and 9 of the EFT number will identify the bulk provider. See "Bulk Provider Number" in the glossary.

  7. When a valid TIN for the taxpayer has been secured, retrieve the transaction record from the Assigned Unresolved status. Enter the correct EIN/SSN in the TIN element box and commit the entry.

  8. If a record is committed and does not match CFOL, it will return as unresolved and be assigned to the same employee who worked the original unresolved record.

    1. Verify that the information is correct.

    2. If an entity change is required, initiate the change and select "yes" for the resequence indicator.

    3. If an entity change is not required, select "no" to the resequence indicator prompt.

  9. If a valid EIN is not located or needs verification, complete Form 4442, Inquiry Referral, as follows and FAX to Entity:

    Form 4442: Complete blocks:
    Part I
    • One - Employee Name

    • Two - Employee ID Number

    • Four - Location: EFTPS

    • Five - Referring to: Entity

    • Six - Date

    Part II
    • Eight - TP's Name on Return

    • Thirteen - Current Address

    • Fifteen - Form(s): Input all Filing Requirements

    • Twenty Four - TP's Telephone Number(s): if available

    Part III Section B Write: "Request EIN assignment" or "Request EIN verification" (whichever is applicable)

    Note:

    Write along the top of Form 4442 "5 Day Expedite Process" . Entity will FAX the assigned EIN or verification of EIN back to EFPPS within 5 business days.

Name Control

  1. Description -The Name Control is a four-position element used to validate the taxpayer's name against the TIN.

  2. Invalid Condition -this element is invalid if:

    • The first position not alpha or numeric

    • The second, third or fourth position not an alphabetic, numeric, ampersand, hyphen or blank

    • Intervening blanks between characters

    • Does not match the name control on CFOL for the TIN.

  3. Research this condition using IDRS, RS-PCC, and/or the FTCS database, or contact the Financial Agent.

    1. Click on the abort button on the bottom of the screen.

    Note:

    If further research is needed follow abort entry procedures in IRM 3.17.277.8.2.7

Name Control Research
  1. Research using the IDRS command codes.

    1. Use CC ENMOD to research for possible changes.

    2. Use CC INOLE to display Master File entity data for specific Name Control residing on the CFOL database.

  2. Research the FTCS database for taxpayer information or information about the bank at which the payment was initiated.

  3. If the FTCS database is not available, contact the FTCS coordinator at the US Bank on 1–800–382–0045. The FTCS Coordinator will need the taxpayer's EFT number, TIN, payment amount, and payment settlement date in order to research for the taxpayer's data.

  4. Based on information provided by the FTCS Coordinator, it may be necessary to contact either the taxpayer or the taxpayer's financial institution.

    1. If sufficient taxpayer information is provided but a discrepancy is still present, contact the taxpayer to secure the correct information. If a telephone number or the taxpayer's identity is not available, contact US Bank Customer Service via a service message to contact the taxpayer's financial institution to secure the correct information.

  5. If additional research is necessary for bulk provider payments, contact the bulk provider. Positions 8 and 9 of the EFT number will identify the bulk provider if the "Financial Agent ID number" is a "2" and the "Payment Method" is a "1" , "2" or "6" . See "Bulk Provider Number" in the glossary.

  6. After a Name Control has been secured, research IDRS to verify that the Name Control is valid for the taxpayer. Use CC INOLE or ENMOD to display Master File entity data for specific name control residing on the CFOL database.

  7. When a valid Name Control for the taxpayer has been secured, retrieve the transaction record from the Assigned Unresolved status. Enter the correct Name Control in the Name Control element box and commit the entry.

  8. If a record is committed and it does not match CFOL, it will return as an unresolved. Verify that the information is correct. If an entity change is required, initiate the change and select "yes" for the resequence indicator. If an entity change is not required, select "no" to the resequence indicator prompt.

    Note:

    Once the record has been accessed, it remains assigned to the employee who worked the original error, unless reassigned by a manager.

Origination Date

  1. Description -The Origination Date is used to identify the date the payment amount was reported to the financial agent by the taxpayer.

  2. Invalid Condition -

    • The Year is other than 0000 - 9999, or

    • The Month is other than JAN - DEC, or

    • The day is not valid for the month, or

    • The date is later than either the current date or payment date, or

    • The date is not in DD–MON–YYYY format.

  3. Correction Procedures:

    1. For ACH debits, enter the Payment Date minus 1 banking day in the Origination Date element box. Do not count holidays and weekends.

    2. For all other payments enter the Payment Date.

Payment Date

  1. Description -The Payment Date is the date that the taxpayer will be credited with making the deposit.

  2. Invalid Condition -The payment date is invalid if:

    • The date is later than either the current date or settlement date, or

    • The Year is greater than 2053, or

    • The Month is other than JAN - DEC, or

    • The day is not valid for the month, or

    • The date is not in valid DD–MON–YYYY format.

  3. On original validation, the Payment Date cannot be more than 30 days prior to the settlement date or 360 days prior to the current processing date.

  4. Correction Procedures: Determine the correct payment date. Contact the financial agent if necessary.

    1. If the correct payment date is different from the payment date on the unresolved screen, enter the correct payment date in the Payment Date element box and Commit.

    2. If the correct payment date is more than 30 days prior to the settlement date or 360 days prior to the current date, enter and commit the correct payment date.

    3. The response is a warning message that the payment date exceeds the 30 day or 360 day check. If the date is correct, select "Yes" to "Is this Correct?"

    Note:

    For RS-PCC payments, the correct payment date is the date the payment is received by the IRS, not the date on the check. DO NOT change the payment date if the date on the check does not match. If the received date is questionable, the manager or lead should contact an RS-PCC HQ analyst or the processing site for received date confirmation via email to the RSPCC HQ team.

Original Payment Date

  1. Description -The Original Payment Date will be blank, except for the following:

    1. For returned payments (transaction indicator "1" or "4" ), the date must be present and will be sent to Master File as the transaction date. If the date does not match the payment date of the original transaction, the record will unpost.

    2. For credit reversals (transaction indicator "R" ), the date is generated into this field from the payment date of the original transaction.

    3. For e-file debits (payment method "0" ), this date is the payment date requested by the taxpayer whenever the settlement is different from the requested date.

  2. Invalid Conditions -The Original Payment Date is invalid if:

    • The date is not present with transaction indicator "1" or "4" , or

    • The Year is other than 1954 - 2053, or

    • The Month is other than JAN - DEC, or

    • The Day is not valid for the month, or

    • The date is greater than either the current date or payment date, or

    • The date is not in valid DD–MON–YYYY format.

  3. Correction Procedures:

    1. Research the original EFT number on the EFPPS database, if present in the Reference Number field.

    2. Research IDRS to determine the date of the original payment.

    3. If the field is blank on an Indicator "1" or "4" transaction, contact the Financial Agent to request the date. (The financial agent is responsible for providing this date on all reversals.)

    4. Enter the corrected Original Payment Date in the Original Payment Date element box and Commit.

Tax Type Code

  1. Description -This code denotes the form number of the tax and the transaction code.

  2. Invalid Condition -The Tax Type Code is invalid if it does not match a valid 5 digit BMF or, IMF tax type or if the TIN is not consistent with the tax type.

    1. See Exhibit 3.17.277-1 for a list of the valid Tax Type Codes for each form.

    2. Because of Master File limitations, any IMF tax type code is invalid if the transaction amount is $100 million or greater.

  3. Correction Procedures:

    If Then
    The correct tax type code can be determined from the Form Number Table (Exhibit 3.17.277–1), Enter the code in the Tax Type Code element box and Commit.
    If a valid tax type code is in error due to a mismatch with CFOL and the tax type is 720, 940, 941, 943, 944, 945 or 1042, Ensure tax type code has appropriate suffix per Exhibit 3.17.277-1. Also, review the account to determine if an open account has been established in recent modules. Then, accept even if there is no filing requirement.
    If taxpayer is incorporated and the tax type is 1120, Accept 1120.
    If the tax type code on the correction screen does not match the appropriate filing requirement established on Master File, Review the payment history to identify a tax type and tax period consistent with the payment date and amount.
    If Master File indicates more than one filing requirement and the correct tax type cannot be determined by the payment history, Apply the payment to the current quarter 941 or the tax type selected by taxpayer (if it is a valid tax type).
    If the Master File shows that the payment was intended for a BMF or IMF account, Enter the correct tax type code (and tax period, if necessary) and Commit.
    If an IMF payment is $100 million or more, Send the record to suspense, where it will be manually deleted from EFPPS and sent to NMF.
  4. In some instances, the tax period may also have to be changed. If necessary, enter the correct tax period in the Tax Period element box. If a change is required for both the Tax Type Code and the Tax Period, enter the corrected data in both element boxes before Committing.

  5. If a record is committed and it does not match CFOL, it will return as an unresolved. Set the Resequence Indicator, if appropriate.

    Note:

    The record will return to the employee who worked the original unresolved.

Tax Period

  1. The Tax Period is invalid if:

    1. The tax period is greater than the current year/month plus one year, or

    2. The tax period month does not equal the fiscal year month on CFOL and/or the FA database for tax types indicated as "FY Month" in the Valid Months column Exhibit 3.17.277-1 or

    3. The tax period month does not equal one of the designated values for non-FTD tax types with Valid Months as shown in the same exhibit, or

    4. The Master File Type is "6" (Non-Master File Payment) or "7" (Miscellaneous Payment) and the tax period is not in YYYYMM format.

  2. Correction Procedures:

    1. For FTD tax types, the tax period is auto-corrected within EFPPS.

    2. For current year tax periods, change the tax type code to the appropriate FTD tax type. EFPPS will then auto correct the tax period.

    3. For prior year tax periods or non-FTD tax forms, research IDRS using command code BMFOL or other appropriate code for outstanding liabilities or payment history to determine where to apply the payment. If there are no prior liabilities, the tax type code may be changed to the FTD tax type.

    4. For tax type 10406 (Form 1040-ES) if the tax period is changed to a date older than 8 months from the current date, a warning message is a reminder that the tax type will be changed to 10407 (subsequent payment). If this is correct, select "Yes" . If "No" , you will need to make another correction to the record.

FUTA Payment Amount

  1. Description -Form 940, Federal Unemployment Tax (FUTA) Deposits.

  2. Invalid Condition -The FUTA Payment Amount is sent to error if the amount is equal to or greater than $100,000 except when the payment date is January 26 to February 5, April 25 to May 5, July 26 to August 5 and October 26 to November 5.

  3. Correction Procedures -Research IDRS to determine if the amount is consistent with the taxpayer's Form 940 filing history.

    If Then
    No change is necessary, Retrieve the record and Commit.
    The amount greatly exceeds any previous payment for Form 940 and appears to be consistent with the payment date and amount for another type of tax, Retrieve the record to enter the corrected tax type code and Commit.
    You are unable to determine the intent of the taxpayer, Accept the record and Commit.

Command Code Research Procedures

  1. Below is a list of IDRS research Command Codes, including their general formats. For additional format information, refer to the Command Code Job-Aids for BMF and IMF. Working in compliance with "one stop processing " , every effort should be made to resolve an error using the Command Codes below.

    1. NAMEB/NAMEE: Use to search for the correct EIN by entering the taxpayer's name and zip code.

    2. NAMEI/NAMES: Use to search for the correct SSN by entering the taxpayer's name and zip code.

    3. INOLE: Use with definers "T" , "X" , "G" , or "S" as appropriate to find the IMF/BMF Name Control, research SSA Name Controls, research filing requirements on BMF, or verify any entity information.

    4. FINDE: Use to find the business' name and address using EIN.

    5. CFINK: Use to research the Centralized Authorization File (CAF) for information regarding authorizations that taxpayers have given third parties for various tax matters within their accounts.

    6. RFINK: Use to research the Reporting Agent File.

    7. IMFOL: Use to review IMF account data, including posted transactions and adjustments, and entity information.

    8. BMFOL: Use to review BMF account data, including posted transactions and adjustments, entity information, and EFTPS enrollment code.

    9. TXMOD: Use to access specific tax modules which contain pending and posted transactions, and to determine the status of an account.

    10. ENMOD: Use to review pending and posted entity information.

    11. MFREQ: Use to request a specific entity module or tax module for a taxpayer.

    12. SUMRY: Use to review the summary of an account for a particular TIN.

    13. TRDBV:Use to display the electronically filed tax return and payment information submitted through IRS e-file (Legacy) systems such as Electronic Filing System (ELF).

    14. UPCAS:Program used to request tax module information.

    15. UPDIS:Program used to display all open unpostable cases for a specific sequence number. CC UPDIS must be used prior to CCs UPCAS, UPRES and UPREV.

    16. UPRES:Program used to correct an unpostable case.

    17. UPTIN:Program used to display data for all unpostables that are currently on the GUF data base for a requested TIN.

    18. URINQ: Identifies remittances which are received and cannot be positively identified.

    19. XSINQ: Research remittances that are over 1 year old.

  2. See IRM 2.3.70, IDRS Terminal Inquiries for CC EFTPS, and BMF and IMF Job-Aids for specific details on using the above command codes.

  3. See IRM 3.17.277.10, EFPPS Research for additional EFPPS research capabilities.

RS-PCC Research Procedures

  1. RS-PCC payments are payments that were processed through the Remittance Strategy for Paper Check Conversion System.

    1. RS-PCC payments are identified by an EFT number beginning with 520, 521, 522, 523 and 524.

    2. The 8th and 9th positions of the EFT number identify a specific Campus or TAC office.

  2. Invalid Elements and Conditions are the same as other payments processed through EFPPS. Refer to the following IRM references for each element.

    1. Taxpayer Identification Number (TIN) - IRM 3.17.277.8.3,

    2. Name Control – IRM 3.17.277.8.4

    3. Payment Date – IRM 3.17.277.8.6

    4. Tax Type Code – IRM 3.17.277.8.8

    5. Tax Period – IRM 3.17.277.8.9

    6. FUTA Payment Amount – IRM 3.17.277.8.10

  3. Research Procedures:

    1. Research RS-PCC errors the same as any other type of error as previously noted in the IRM under each invalid element.

    2. Also, access the RS-PCC system to see an image of the check that was processed, for any information that may be noted on the check before it was imaged.

  4. Correction Procedures:

    1. Review the information from IDRS and the RS-PCC system.

    2. If you are able to determine the correction from this information, input the correct information on the correction screen and commit the correction to Master File.

    3. If you are unable to resolve the invalid element contact the appropriate Campus Support using the RS-PCC contact list. They will provide you with any backup information they received with the check. If you need to contact a TAC office, send the required information to Marlene Sosa at marlene.sosa@irs.gov and Virginia Miller virginia.miller@irs.gov and cc RSPCC HQ team at &W&I CAS:SP:ATP:EP:RSPCC.

    4. Requests must be sent using secure email and include the following information: RPSID, SEID, money amount, date, TIN, name control, EFT number.

    5. The Campuses and TAC offices will fax the additional information within 24 hours of the request.

    6. Once Campus Support or the TAC offices respond to the backup request, review the information provided.

    7. Pull the error from the unresolved list and enter the correct element information. Commit the error to Master File

    8. In some instances, the TIN is invalid and a valid TIN cannot be located through IDRS research.

    9. For BMF, if a valid EIN cannot be located, complete Form 4442 and fax to Entity. Entity will assign a new EIN to the taxpayer. See IRM 3.17.277.8.3.1, TIN Research.

    10. If the taxpayer is using an invalid SSN and a valid number cannot be located through IDRS research, input a MFTRA U using IDRS.

    11. You should receive the MFTRA U print within 2 days. If the print indicates the SSN belongs to the taxpayer, input a TC 000 on the SSN and apply the payment.

    12. If the MFTRA U print shows a different taxpayer, input a TC 000 on the invalid side and post the payment.

    13. Every effort should be made to process RS-PCC errors within 5 business days. Two additional days are allowed for errors requiring backup information from campus support or TAC offices.

Unidentified Remittance Procedures
  1. If a payment is in error status with the EIN 00-0000001 or SSN 000-00-0001, research the payment on IDRS using the information from RS-PCC to locate the correct taxpayer.

  2. If you are able to locate the correct taxpayer account, update the TIN, Name Control, Tax Type Code, and/or Tax Period as necessary and commit the payment record.

  3. If you are unable to locate the correct taxpayer, review information received via UPS from the campus or TAC office.

    1. If you are able to locate the correct taxpayer, follow instructions in (2) above.

    2. If you are still unable to locate the correct taxpayer, change the TIN to 000000002 and commit the payment. You will have to commit the payment two times in order to push the payment through the system.

    Note:

    This will cause the payment to go to Unpostables. Unpostables will "8" code the payment which will send the payment to Rejects. Rejects will forward the payment to Unidentified. See 3.12.179.20, 3.12.279.48, and IRM 3.12.37.15.23.1.

Suspense Inventory

  1. The suspense inventory consists of records that have been identified for removal from EFPPS. The following types of records are included in the suspense inventory:

    1. "Unidentified" payments or reversals (transaction indicators "8" and "9" ) are automatically sent to suspense to await a generated offset (transaction indicator "A" or "B" ). When the reversing record arrives, the two records are both automatically closed off the control file.

    2. Offset records (transaction indicators "A" and "B" ) are systemically sent to suspense if no Unidentified record with the same money amount and FA ID number is present on the system.

    3. Error correction has selected the option "Suspend" , because the record should not be sent to Master File. The payment could be designated for the Unidentified Remittance File, Non-Master File, user fee, etc.

    4. NMF and Miscellaneous items with valid tax type codes are sent directly to Suspense.

  2. All records received in suspense, except those that are cleared on the same day, are included on the daily New Suspense List (CMS 28), which provides detailed information on the record or batch that has been suspended. See Exhibit 3.17.277-20.

Resolution of Offset and Unidentified Items

  1. "Unidentified" records (transaction indicators "8" and "9" ) should be automatically closed as a result of offsetting records being received from the financial agent. Use the Electronic Reject/Offset Mismatch Report (CMS 2) and the New Suspense List (CMS 28) to ensure that the offsetting records are received timely.

  2. Contact the financial agent for each unidentified ("8" or "9" ) or offset ("A" or "B" ) record that remains in suspense for five workdays.

    1. To expedite the notification process, the Electronic Reject/Offset Mismatch Report should be sent to the financial agents at least once each week.

    2. The financial agent will need to submit a new offsetting record ("8" , "9" , "A" or "B" ) to get the offset record closed, or provide the information necessary to post the transaction to Master File.

Contested Dishonored Returns
  1. For contested dishonored returns, the financial agent is often unable to provide an offsetting transaction.

  2. The only resolution may be to allow the record to post.

    1. Contact the financial agent and research EFPPS to identify the TIN name control, tax type, and tax period of the payment being reversed.

    2. If the information is available to process, use the Manual Suspense to Error option from the control menu.

    3. Then correct the record with the appropriate tax information.

  3. On rare occasions, a contested dishonored return cannot be associated with an original payment or with a taxpayer, and attempts by IRS and the financial agent to obtain information from the originating bank are unsuccessful.

    1. The FA will prepare a request for FS to debit the originating bank for an erroneous contested dishonored return.

    2. This request will include the bank's Routing Transit Number, settlement date, EFT number and amount, plus a record of unsuccessful attempts to resolve the issue with the bank. The request is then faxed to the FS Tax Collection Division at 202–874–8644.

    3. FS will send a notice to the originating bank, advising of an intent to debit the bank for an unauthorized return if the bank has not resolved the case within 45 days.

    4. The bank will be asked to wire an offsetting payment to the Federal Reserve Bank of New York, credited to the Ogden ALC 2009-2900.

    5. If the bank does not submit a payment, FS will initiate a charge back to the originating bank, crediting the Ogden ALC.

    6. When the credit is reported to RRACS, use the Manual Delete option to remove the offsetting debit record from EFPPS. Be sure to provide documentation of the offset.

    7. This procedure should be initiated as soon as it is determined that information to identify the original payment or the taxpayer is unavailable, normally within 60 days.

Resolution of Non Master File Items

  1. Non-Master File (NMF) payments cannot be posted electronically to the taxpayers account. NMF payments are transferred to Cincinnati Submission Processing Center (CSPC).

    1. Research to verify that the payment is NMF before transferring to the CSPC.

    2. For payments, if SUMRY does not identify an NMF account, change the tax type code to a Master File tax type code and post the payment to a Master File tax module.

  2. For each payment that is to be transferred to the CSPC prepare Form 3244 and complete the following:

    • Attach a print of CC's EFTPSE, ENMOD, and TXMOD showing where the payment belongs.

    • Give the information to the lead of the EFPPS team in Ogden to review.

    • The EFPPS lead in Ogden will take over to the lead of RRACS.

    • RRACS will return the item to the EFPPS lead with Form 2158, Credit Transfer Voucher, attached showing the journal number.

    • Place the payment into suspense on the correction screen.

    • Go to the Control Menu and Manually Delete the payment.

    • On the Manual Delete screen, enter the batch number, item count, amount, remarks, from code, and EFT number then commit the changes. Be sure to print a copy of the screen when prompted.

    • Attach all documentation together and place in the cabinet behind the lead.

  3. NMF payments should be transferred as quickly as possible to prevent erroneous notices from being issued. Guidelines require the credit transfer to be completed within ten work days and the RRACS journal within five work days.

Controlling the Aged Inventory

  1. The EFTPS Age Report (CMS 27) lists all records or batches that have been open on the control file for more than seven days. See Exhibit 3.17.277-19.

    1. Aged items are listed by Bulk Provider Number, then Financial Agent Number, with the oldest items listed first.

    2. Suspended batches are listed separately without the details on the individual payments.

    3. Every effort should be used to resolve aged items within 8 days.

    4. If an error/unresolved item cannot be resolved within 60 days (90 days for Bulk Provider payments) and all resources (Headquarters, Financial Agent, taxpayer, authorized third party, or other IRS department) have been exhausted, the aged item must be deleted and sent to the Unidentified Remittance File (URF) unless otherwise instructed by Headquarters. See IRM 3.17.277.9.4(3), Deleting Suspense Cases.

    5. Consider the amount of the payment before sending it to URF. High dollar payments (over $100,000) require HQ approval.

  2. Headquarters contacts are:

    1. For Bulk Providers contact Louis Trigg at louis.trigg@irs.gov.

    2. For Financial Agent "02" contact Pamela Plunkitt at pamela.y.plunkitt@irs.gov.

    3. For Financial Agent "03" or "04" contact Sonia Jacob at sonia.e.jacob@irs.gov.

    4. For Financial Agent "05" contact the RS-PCC mailbox at &W&I CAS:SP:ATP:EP:RSPCC.

Deleting Suspense Cases

  1. Review each suspense record that is to be manually deleted from EFPPS.

  2. The following manual control records may be used to remove items from Suspense:

    If Then
    The record should not be deleted and was erroneously suspended by error correction, Input a Manual Suspense to Error record to send the record back to unresolved status.
    The record was manually suspended in error, or the reason for manual suspension is now resolved, Input a Manual Unsuspend record to send the record back to its previous status.
    The record should be removed from EFPPS processing, Input a Manual Delete record.
  3. If the record should be deleted,

    1. Prepare any necessary journal documentation to have the payment established on the Unidentified Remittance File, transferred to NMF in another IRS center, etc.

    2. Input a Manual Delete record with "From Code: 4" to remove the item from EFPPS. In the remarks field of the Manual Delete record, enter any cross reference account or DLN information to show the disposition of the record.

    3. Prepare a separate Manual Delete record for each item to be deleted if the records were suspended one at a time. If the records were suspended as a batch, prepare a single Manual Delete for the entire batch.

    4. If more information is needed to document the delete action than is available in the remarks field, prepare a separate Manual Remarks record.

    5. Prepare the required source document according to local procedures. Be sure to enter the EFT number, along with any account information from the EFPPS record.

    Note:

    For Manual Suspend and Manual Unsuspend procedures please see IRM 3.17.277.6.4.4, Manual Suspend and IRM 3.17.277.6.4.5, Manual Unsuspend.

  4. Manual Suspense to Error records must be input for one record at a time, with the appropriate EFT number.

  5. Manual Unsuspend records should be input for one item at a time if they were suspended one record at a time. Records that were suspended as an entire batch may be unsuspended with a single record.

  6. Records that are being deleted from EFPPS must be carefully controlled to ensure that the proper journals are input to the RACS. Each manual deletion requires a journal to one of the general ledger EFPPS suspense accounts.

  7. To ensure that each transaction remains under the control of some system, never delete records from EFPPS until the next action is determined and any necessary documentation is prepared.

    1. Use the Manual Undelete option to recover, on the same day, any item deleted in error.

    2. After the end of the day, any record that has been deleted erroneously can only be re-input through the Distributed Input System/Integrated Submission and Remittance Processing (DIS/ISRP) and Generalized Mainline Framework (GMF) mainline system.

    3. IRS EFPPS does not have the capability of re-inputting or reprocessing deleted records.

  8. Retain the EFPPS Deleted Records List with other audit trail documentation of the deleted records. Print CMS 3 the following day and retain with the audit trail documentation.

EFPPS Research

  1. The following resources are available for research:

    1. IRS EFTPS system database - Research of the system payment file and control file is available to all EFPPS users. Ad hoc research of the EFPPS system is available to qualified personnel.

    2. Federal Tax Collection Service database - Procedures for the FTCS same day payment system have been issued by US Bank using SinglePoint.

    3. RS-PCC - Users may research the scanned check image at time of scanning.

  2. Access to FTCS' database must be arranged and authorized by FTCS' security administrator. Access will only be available to the EFTPS Accounting technicians.

Payment Research from the EFPPS Data Base

  1. To access the Research Request Screen from the Home Page,

    1. Click on the Research/Correction tab. This takes you to the Correction screen. Click on the Research Request tab located above the correction screen. See Figure 3.17.277-23 .

      Figure 3.17.277-23

      This is an Image: 33928023.gif

      Please click here for the text description of the image.

Research Request Input Parameters
  1. Enter the required fields on the Research Request Screen. Be sure to press TAB after each field and to initiate the request.

  2. Enter the required information for one of the three research options:

    1. Option 1 - EFT Number, or

    2. Option 2 - Reference Number and payment year, or

      Note:

      Option 2 is not available for bulk provider payments because the same reference number may be used for a large number of payments. This option is available for credit or debit card payments.

    3. Option 3 - TIN, Payment Date and amount.

    See Figure 3.17.277-24.

    Figure 3.17.277-24

    This is an Image: 33928024.gif

    Please click here for the text description of the image.

  3. Enter only the Search Parameter fields that are required for your option. Fields are validated as follows:

    1. EFT Number (15 positions)

    2. Reference Number (up to 18 positions) - See definition in Glossary.

    3. Payment Year (4 positions) - The calendar year (YYYY) that the payment was made.

    4. TIN (9 positions) - Numerics without hyphens

    5. Payment Date (11 positions) - Enter in DD-MON-YYYY format.

    6. Amount (up to 16 positions) - Enter the amount as follows:

    Amount Enter As
    Payment for $12,345.00 12345 or 12345.00
    Reversal for $5555.55 –5555.55
  4. If the record is not found, an error message is displayed. See Figure 3.17.277-25.

    Figure 3.17.277-25

    This is an Image: 33928025.gif

    Please click here for the text description of the image.

Research Request Response Screen
  1. If the requested record is found, a completed research request screen is displayed. See Figure 3.17.277-26 .

    Figure 3.17.277-26

    This is an Image: 33928026.gif

    Please click here for the text description of the image.

  2. If more than one record is found, there will be multiple rows of records displayed.

  3. The current status of the record is shown in the "Status" field. The status is identified as:

    1. Processing - The record is currently in load, validate, unresolved or awaiting review or TEP (process code "1" - "10" or "15" ).

    2. TEP - The record has completed EFPPS processing and been sent to Master File for posting (process code "11" ).

    3. Deleted - The record has been removed by an offset record or manual deletion (process code "0" or "13" ).

    4. Suspended - The record is suspended (process code "14" ).

  4. The section on the bottom is audit records. See Figure 3.17.277-27

    Figure 3.17.277-27

    This is an Image: 33928027.gif

    Please click here for the text description of the image.

    1. The Element Type is the number of the specific field on the record that was changed. See Element Type in the glossary.

    2. For element type "6" , the Original Text and Changed Text fields display numbers representing the "before" and "after" process codes. See Process Code in the glossary for a further definition.

    3. For other element types, a specific field was changed, such as the TIN or name control. The Original Text and Changed Text fields display the actual data that was changed.

  5. To return to a blank research request screen you can click the Back to Research Request Criteria button.

  6. To correct an unsuccessful request, clear the error message, click the 'clear' button at the bottom of the page. A new Research Request Screen (or no match message) will be displayed.

Command Code EFTPS
  1. Command Code EFTPS provides IDRS users who do not have direct access to the EFPPS system with the ability to request immediate research of the EFPPS database.

  2. Command Code EFTPS is used with the following definers:

    1. Definer E is used to request a specific EFT number.

    2. Definer R is used to request a specific reference number (not valid for bulk provider payments other than credit or debit cards).

    3. Definer T is used to request a specific TIN, payment date and amount.

  3. Complete instructions for the use of Command Code EFTPS are contained in IRM 2.3.70, Command Code EFTPS .

  4. Command Code EFTPS should provide real time access to all EFPPS payment records for the current year plus four prior years.

  5. If the settlement date equals the current date, the payment should show on CC EFTPS the following day. However, the specific posting to the tax module may take another two weeks or more.

  6. The payment information should be displayed on IDRS as "pending" within 24 - 48 hours.

  7. If the taxpayer has erroneously indicated the payment is for a previously satisfied module, CC BMFOL/IMFOL or CC TXMOD will show the payment came in with a zero money amount. The payment will continue to roll forward one module per cycle until it locates an unsatisfied module. This is where it will show up.

Control File Research

  1. To research the Electronic Payment Control File,

    1. Select Research PCF tab from the Research/Correction page. The response is a blank Research Payment Control screen. See Figure 3.17.277-28.

      Figure 3.17.277-28

      This is an Image: 33928028.gif

      Please click here for the text description of the image.

    2. Enter the 10 - digit batch number of the batch that you wish to research and select submit. If the number you have entered does not match an existing batch number on the control file, the response is: "Batch Number Not Found. Reenter Batch Number"

  2. If the system finds a batch number on the control file matching the number you have input, all control records for the batch are displayed in the sequence that they were created.

Control Record Contents
  1. All control records include:

    • From code

    • To Code

    • Control date - system generated date that the control record was created

    • Item count

    • Money amount

    • Master File type (1 = IMF, 2 = BMF, 6 = NMF, 7 = Miscellaneous)

  2. Each control record may include:

    • From Master File type (for reclassifications)

    • EFT number (if item count is 1)

    • Remarks (required for manual control records)

    • Employee number (generated for manual control records) - Use the horizontal scroll bar to see this field

From-To Code Summary
  1. There is a separate section that provides a count and amount summary for each from-to-code combination.

    1. This information can be used to determine the current status of the batch and identify the count and amount of any payments that have not been resolved.

    2. If a large number of control records are present, use the vertical scroll bar to see the summary section at the bottom of the screen.

Control File Balances
  1. The control file balances are shown on the bottom half of the screen.

Bulk Provider Procedures

  1. The bulk provider should have completed an IRS authorization form or the equivalent for each client before submitting enrollment or payments through EFTPS. The following are accepted IRS authorization forms. Refer to the IRM reference listed for additional information on each form.

    • Form 8655 - Reporting Agent Authorization. See IRM 21.3.9.3

    • Form 2848 - Power of Attorney. See IRM 21.3.7.5

    • Form 8821 - Tax Information Authorization. See IRM 21.3.7.5

    • Form 9783T, EFTPS Electronic Batch Provider Individual Enrollment Form. See IRM 3.17.277.4.3 .

    Note:

    With the exception of the Form 9783T, these forms are available from the IRS website www.irs.gov.

  2. Several specialized payment options enable bulk providers to submit large files of EFTPS payments.

    • Bulk ACH debit

    • Bulk same day payment

    • Catastrophic emergency bulk provider payment

  3. Bulk provider payments are identified by a 7, 8, or 9 in the third position of the EFT number. The EFT number is unique, but the reference number is the same for all payment transactions associated with one transfer of funds.

  4. Credit card or debit processors (service providers) submit payments as bulk providers.

  5. Positions 8 and 9 of the bulk provider payment EFT number will identify the bulk provider who transmitted the payment if the Financial Agent ID number is 2 and the Payment Method is a 1, 2, 3 or 6. See Bulk Provider Number in the glossary for a list of assigned codes and contact phone numbers.

  6. Two other programs are designed for multiple payers.

    1. The batch provider program is designed for payroll processors who make tax deposits for more than two clients. See IRM 3.17.277.11.5 , Batch Provider Program.

    2. The single debit program is designed for fiduciaries who make a large volume of payments a few times a year. See IRM 3.17.277.11.6 , Single Debit Program.

Bulk Provider Reports

  1. The Bulk Provider Payment Report, CMS 5, captures detailed information on volumes, errors, auto corrections and unenrolled payments for each bulk provider, plus a summary page. See Exhibit 3.17.277-7.

  2. The Financial Agent Bulk Provider Payment Report (IRS 21) provides count and amount payment information for each bulk provider by payment method and form number. See Exhibit 3.17.277-27.

  3. The Enrollment Summary Report (IRS 17) provides information on successful and unsuccessful enrollments for each bulk provider plus a summary page for each type of enrollment: bulk, batch, single debit, paper and Internet. See Exhibit 3.17.277-28 for the summary page.

  4. All of the bulk provider reports have been designed to enable the National Account Managers to assist and evaluate our service bureau stakeholders. The system administrator will provide copies of these reports by email to Scott Mezistrano at scott.mezistrano@irs.gov , and separate copies to other designated headquarters employees.

Bulk ACH Debit

  1. Each bulk provider is expected to submit electronic payment files to their financial agent the day before the tax due date.

    1. The financial agent receives the file, performs internal balancing and sends an acknowledgment message to the bulk provider.

    2. The financial agent matches the taxpayer information submitted with the bulk file to the file of approved enrollments.

    3. Any payment for a taxpayer who is not enrolled will be removed from the ACH debit transaction and will not be processed, reducing the amount of the debit.

    4. The financial agent initiates a single ACH debit to the account designated by the bulk provider for the sum of the accepted payment records.

    5. The financial agent then sends an acknowledgment file back to the bulk provider with an EFT number for each accepted record and an error code for rejected records.

Bulk Same Day Payments

  1. A second payment method customized for bulk providers is the bulk same day payment.

  2. Bulk same day payments can only be made for a taxpayer who is authorized to make a same day payment or for any bulk provider who reports a temporary emergency that made the bulk debit unavailable.

  3. Bulk same day payments can be identified by Routing Transit Number 091036177 for Bank of America.

  4. The bulk provider sends a payment detail file to the financial agent on the morning that the payment is due and receives a reference number to be inserted by the bulk provider's financial institution on the FTCS payment wire.

  5. When the payment is made, the financial agent matches the reference number and payment amount to the detail file that was received earlier.

  6. Twice a month (preferably the 1st and the 20th and additionally if necessary), the bulk providers should be notified of the unresolved payments that EFPPS accounting technicians have not been able to apply. A Structured Query Report can be generated from the Reports Generator Menu for this purpose. This report should show the EFT number, TIN, Amount, Payment Date, and Employee Number. Once generated, the Structured Query Report should be faxed to the applicable Bulk Provider. Bulk Providers should respond back via fax and/or secure email with a spreadsheet or screen prints of the name, address, contact name, and phone number.

  7. On September 17, 2007, Provisional I-EIN was replaced with Mod IEIN which is "real-time" . See IRM 21.7.13.3.4(1), Internet EIN Applications for additional information.

Catastrophic Emergency Bulk Provider Payments

  1. A bulk provider who reports a "catastrophic emergency" may be permitted to submit a same day payment wire without a payment detail file.

  2. The bulk provider, IRS and the financial agent will follow these steps to complete a catastrophic emergency payment:

    1. The bulk provider calls the financial agent to report the emergency and get a 5 digit disaster number "E" followed by four numerics.

    2. The bulk provider initiates a wire transfer to US Bank using the normal bulk same day payment procedures which is credited to ALC 20092900. The disaster number is included on the FTCS transfer.

    3. The bulk provider faxes signed documentation of the emergency with the settlement date and amount to FS, IRS headquarters and the Ogden Accounting Branch.

    4. Once the file of supporting payment information is completed, the bulk provider sends the detail file to the financial agent using same day bulk provider procedures with the disaster number as a reference. The payment detail file must match the amount of the emergency deposit, or the file will be rejected back to the bulk provider. The financial agent will then transmit the payment records to ECC-MEM with the original settlement date.

    5. IRS load and validate processing is the same as for a normal file, except that the reject check for an old settlement date is bypassed.

Batch Provider Program

  1. The batch provider program is designed for smaller payroll processors to enroll their clients and make multiple payments with a single transmission.

  2. Unlike bulk provider payments, each batch provider payment is associated with a separate ACH transaction. The batch provider submits an electronic file of separate payment records which may debit a single account, or may debit each taxpayers account.

  3. Batch provider payments are identified by an EFT number beginning with "274" .

Single Debit Program

  1. The EFTPS Single Debit program combines features of the bulk and batch provider programs. It is available to fiduciary banks, payroll processors, tax practitioners, and similar entities. It is also available to states participating in the State Income Tax Levy Program (SITLP).

    1. Single debit filers submit a large volume of enrollment or payment records on a "flat" file, avoiding the expense of using an EDI system.

    2. Up to 1000 payment records may be combined into a single ACH debit to one account.

    3. SITLP payments are identified by an EFT number beginning with "251" . All other single debit payments are identified by an EFT number beginning with "226" . See IRM 3.17.277.5.3, EFT Number.

    4. For more information about SITLP, see IRM 3.17.277.1.4.9 , State Levy Programs.

Trusted Partnership Interface (TPI)

  1. Trusted Partner Interface (TPI) affords financial institutions the capability to utilize EFTPS functionality within their existing online banking software by integrating TPI XML (Extensible Markup Language) schema into their program.

  2. Trusted Partner Interface (TPI) notifies EFTPS when payments are accepted and processed, then returns an Electronic Funds Transfer (EFT) Number. Funds received for TPI are transmitted directly to Treasury via Automated Clearing House (ACH) debit transaction.

  3. Providers requesting additional information should be referred to IRS EFPPS HQ Analyst Louis Trigg at 240-613-5891, louis.trigg@irs.gov, or Fiscal Service contact Phillis Suggs-Thomas at 202-874-5316,phillis.suggs-thomas@fiscal.treasury.gov .

  4. TPI payments are identified by an EFT number beginning with "275" .

Supervisor Duties

  1. Supervisory responsibilities associated with EFPPS include the following:

    • Monitor system inventories

    • Reassign work, when necessary

    • Review new employees' work

    • Research the current status of EFT transactions

    • Review all changes to both TIN and name control

    • Maintain Operator Profiles

    • Monitor Unauthorized Access

    • Retrieve records to be reworked

  2. These supervisory functions are performed by the EFPPS operational supervisor or by persons designated by that supervisor.

Monitor System Inventories

  1. IRS EFPPS provides two primary tools for managers to monitor system inventories.

    • Managers can review a list of all unresolved records.

    • The Manager Transaction Status option provides an immediate inventory count for the different process codes.

Unresolved List
  1. To receive a list of unresolved errors from the EFPPS Home Page,

    1. Select Research/Correctiontab.

    2. FClick the View Unresolved EFT’s button at the botom of the correction screen. See Figure 3.17.277-29.

      Figure 3.17.277-29

      This is an Image: 33928029.gif

      Please click here for the text description of the image.

  2. The Unresolved EFTs window opens displaying all EFTPS transactions with a current process code of Unresolved. Fields displayed in this window include the Element Type, EFT Number, Assigned Indicator and the Employee Number to whom the record is assigned. You can save the list to your computer by selecting the ‘File’ and ‘Save as’. An example of this window is shown below in Figure 3.17.277-30

    Figure 3.17.277-30

    This is an Image: 33928030.gif

    Please click here for the text description of the image.

  3. To list unresolved transactions for a specific employee, select the Research/Correction tab from the Home Page. The Manager screen will appear. You must have a manager profile in order to access this page. See Figure 3.17.277-31

    1. Step 1: Select the option List Unresolved for Employee.

    2. Step 2: Select an employee form the dropdown menu and click the ‘Submit’ button.

    3. A list of the unresolved EFT's will display for that employee. To see the details of a a specific EFT use the mouse to click on the serial number in the first column.

    4. To return to the unresolved EFT list for the employee click on the 'Back to EFT list Screen' button below the list.

    5. To return to the Manager Criteria screen, click on the 'Back to Manager Criteria Screen' button.

    Figure 3.17.277-31

    This is an Image: 33928031.gif

    Please click here for the text description of the image.

Current Inventory Volumes
  1. To monitor the current working inventories, click on the ‘View Transaction Status’ button from the manager screen. See Figure 3.17.277-32.

    Figure 3.17.277-32

    This is an Image: 33928032.gif

    Please click here for the text description of the image.

  2. The inventory categories are as follows. Only the "working" inventories of items that are ready for an action by an accounting technician, manager, or quality reviewer are counted on this screen. Items in process codes "0 - 7" and "10 - 13" are not included.

    1. Awaiting Manager Review - This category is process code "15" items in which both the TIN and name control have been changed by error correction. Records will remain in this inventory until approved by a manager. See IRM 3.17.277.12.4.1, Supervisor Review of Charged Errors for instructions.

    2. Unresolved - This is the total of all items currently in process code "8" (unresolved), including those listed as "Research" and "Returned Quality Errors" .

    3. Credit Reversals - This is the total of all items with transaction indicator "R" .

    4. Research - This is a subcategory of process code "8" (unresolved), which includes all records that have been controlled to a technician without being resolved.

    5. Awaiting Quality Review - These items have been selected for quality review, but not yet reviewed. When the TEP is run, any remaining items in this inventory will be removed and processed by the TEP.

    6. Returned Quality Errors - This is a subcategory of process code "8" (unresolved). When an error is assigned, the manager must review the record and either accept or reject the error.

    7. Suspended - This is a count of all items in process code "14" (suspense).

Reassigning EFT Transactions

  1. Certain situations may occur when it becomes necessary to reassign an EFT transaction to another employee in order to prevent aging.

  2. From the EFPPS Home Page,

    1. Click on the Research/Correction tab.

    2. Enter an EFT number in the top section of the screen and click on the ‘Submit’ button to bring up the payment record you wish to reassign. See Figure 3.17.277-33.

    3. Position the screen pointer on the Reassign EFT button. On the next screen, select the employee number from the drop down box for who the payment record will be reassigned and click on the ‘Commit’ button. A second pull-down menu appears. Next, press E to reassign EFT to new employee. See Figure 3.17.277-34.

    Figure 3.17.277-33

    This is an Image: 33928033.gif

    Please click here for the text description of the image.

    Figure 3.17.277-34

    This is an Image: 33928034.gif

    Please click here for the text description of the image.

Reassign An Employee's Inventory
  1. To reassign an employees entire inventory, (you must have a manager profile to perform this action),

    1. From the Home Page, select the Research/Correction tab. This brings you to the manager criteria screen.

    2. From the 'Manager Criteria' screen, click on the 'Reassign Employee Work' button. See Figure 3.17.277-35

      Figure 3.17.277-35

      This is an Image: 33928035.gif

      Please click here for the text description of the image.

    3. On the next screen, select the employee number that currently has the transactions assigned to them from the Old Employee Number drop down menu,

    4. Select the employee number to which the EFT transactions are to be assigned from the New Employee Number drop down menu.

    5. Click the 'Commit' button. See Figure 3.17.277-36.

    Figure 3.17.277-36

    This is an Image: 33928036.gif

    Please click here for the text description of the image.

Quality Assurance Selection

  1. These instructions apply to a quality assurance reviewer or to a manager reviewing an employees' work. To select records for quality review:

    1. From the Home Page, select the Research/Correction tab. This brings you directly to the "Quality Assurance' page.

    2. Select the employee ID you want to review from the Employee ID drop down menu. This will activate the 'Percent Volume and Select Count fields as well as populate the Total Audit Records available for the elected employee.

    3. Press the TAB key or click in the percent volume field to review a percentage of the employees work. Enter a whole percentage from 1 - 100 in this field. Or,

    4. Press the TAB key twice or click in the Select Count field to review a certain number of employee transactions. A count of 1 - 100 transactions for review are valid.

    5. Commit the quality review selection with the Submit button. See Figure 3.17.277-37.

    Figure 3.17.277-37

    This is an Image: 33928037.gif

    Please click here for the text description of the image.

Quality Assurance Review

  1. To examine the records selected for quality review, select the record you want to review by clicking on the number in the first column of the Quality Review List. See Figure 3.17.277-38.

    Figure 3.17.277-38

    This is an Image: 33928038.gif

    Please click here for the text description of the image.

  2. Review the displayed payment record to determine if the appropriate corrections were made.

  3. To charge an error,

    1. Select 'Error' from the drop down menu in the last column of the audit table.

    2. Then commit the record by clicking the ‘Commit’ button. See Figure 3.17.277-39.

    Figure 3.17.277-39

    This is an Image: 33928039.gif

    Please click here for the text description of the image.

  4. To accept the record without error,

    1. Select Reviewed from the drop down menu in the last column of the the table at the bottom of the screen.

    2. Then commit the record.

  5. To review another employee, click the 'Back to Quality Review Criteria' button to go back to the Research/Correction - Quality Assurance Criteria page.

  6. To exit the screen and return to the Home Page, click on the 'Home' tab. To Logout, click on the 'Logout' tab. If you logout, be sure to click the 'Yes' button on the Log Out Confirmation page.

Supervisor Review of Charged Errors
  1. Once an error has been "charged" in the quality review process, the supervisor or designee should review the error to verify its accuracy.

    If Then
    You determine that the error should not be charged,
    1. From the Manager Screen, select "List Unresolved for Employee" . Then select the employee number from the drop down menu in the 2nd step.

    2. The record flagged as an error by quality review is identified by an "E" in the Assigned Indicator field.

    3. Select the Serial number with the error indicator and click once. The payment and correction details will appear.

    4. Move the pointer to the "Reverse/Change Error" button and click once. The audits at the bottom of the record will show an "N" for no charge to employee. The EFT transaction is updated to resolved and will be selected for the next TEP.

    If the error should be charged, Notify the affected employee, who must enter the EFT number on the EFPPS Correction Screen to select the record and correct the error.

Review TIN/Name Control Changes

  1. Managers or designees are required to review and approve each payment record in which both the TIN and name control have been changed by error correction.

    1. Records will remain in error status on the control file and Awaiting Manager Review status on the Transaction Status screen until reviewed.

    2. On the transaction file, the record is updated from Unresolved to Awaiting Manager Review.

  2. The TIN Name Control Change List (CMS 20) provides a list of the items that have been reviewed. See Exhibit 3.17.277-13.

    1. Select "Modified TIN Name Control" from the Select an Option section of the Manager Criteria screen and click the Submit button.

    2. The Manager - Modified TIN/Name Control List will appear.

    3. Click the Serial Number in the first column of the record you wish to view. The response is a display screen for the record.

    4. To accept or reject the correction, select Accept or Reject. See Figure 3.17.277-40.

    5. If you reject the change, a screen will appear with the following question: "Would you like to reassign thse EFT number - nnnnnnnnnnnnnnn to another employee?" If you wish to reassign the EFT number to another employee click the 'Yes' button. To assign it back to the original employee click the 'No' button.

    Figure 3.17.277-40

    This is an Image: 33928040.gif

    Please click here for the text description of the image.

Maintain Operator Profiles

  1. Supervisors should ensure that profiles for their employees include only those functions that they are qualified to perform.

  2. Until the security profile system is completed, any profile changes should be submitted to your security administrator via an OnLine 5081, then input by the Database Administrator (DBA).

Monitor Unauthorized Access

  1. Each week, use the Reports Generator menu to request the Manager's Weekly Security Report (CMS 31).

  2. This report lists the access date, employee number, employee SSN and accessed SSN whenever an employee has accessed their own or spouse's SSN or another EFPPS user's or user's spouse's SSN.

  3. As this report contains sensitive information, the Manager's Weekly Security Report can only be generated and printed by a profiled manager.

Retrieve Record to be Reworked

  1. Use the “Corrected EFT” option to pull a record that has already been corrected and send the record back to unresolved status to be reworked by the same technician.

  2. Use this option whenever a technician has committed a correction then realizes that a mistake was made and needs to fix the record prior to running the next TEP.

  3. From the Correction Screen, click the Corrected EFTbutton at the bottom of the page (you don't need a manager profile to perform this action).

    1. The response is the Correction - View Corrected EFT Criteria page.See Figure 3.17.277-41

    2. Enter the EFT number of the record to be retrieved and select "Enter" .

    3. If the EFT number is in Awaiting Quality Review status, the response is "Record moved from Quality Review to Error" . The record has been reassigned to the same technician who previously worked the error.

    4. If an invalid EFT number is entered, the response is "Invalid EFT Number. EFT Number must be 15 positions. Please re-enter EFT Number."

    5. If the EFT number does not find a match on the database, the response is "Invalid EFT Number. Please re-enter EFT Number."

    6. If the EFT number is not in Awaiting Quality Review status (process code "9" ), the response is "Record is not in Quality Review. Please re-enter EFT Number."

    7. If both the TIN and name control are changed, the correction must be rejected through the TIN/Name Control review process.

    Figure 3.17.277-41

    This is an Image: 33928041.gif

    Please click here for the text description of the image.

EFPPS Reports

  1. Most EFPPS reports are created in a 2 step process. From the Reports option of the Main Menu:

    1. Select "Reports to Generate"

    2. Then, "Select Reports to Print"

  2. Depending on local procedures, the reports may be generated by Computer Operations and printed by the Accounting Branch.

  3. For additional instructions on creating EFPPS reports, refer to the Computer Operator Handbook (COH).

  4. Some reports are system generated at the end of the TEP run or the daily Write to History:

    Report Number Report Name
    CMS 1 Financial Agent Reject Report
    CMS 2 Electronic Reject/Offset Mismatch Report
    CMS 3 Deleted Records List
    CMS 9 EFTPS Deposit Ticket/Debit Voucher
    CMS 14 RS-PCC Error Volume Report
    CMS 20 TIN Name Control Change List
    CMS 22 Daily Trans Release Summary
    CMS 23 Daily Revenue Receipts Control Sheet
    CMS 24 Reclassification Summary
    CMS 28 New Suspense List
    CMS 29 Daily Posting Summary
    CMS 30 Deposit Ticket/Debit Voucher Summary Report
  5. Remember that each daily report, such as the Control Record List (CMS 25) or EFTPS Daily Trans Release Summary (CMS 22), will include all of the activity for the date selected, up to the time the report is created.

    1. If a report is requested twice for the same day, all of the information on the first report will be included again on the second report.

    2. It is important that daily reports be created after EFPPS activity for the day is completed.

Generate EFPPS Reports

  1. Select "REPORTS" from the menu bar.

    1. Select the report you wish to generate from the 'Select a report name' drop down menu in the Generate a report section of the Reports page. This includes structured query reports (AKA - Unresolved Payment Reports).

    2. Accept the displayed current date or overlay with the desired date, or click on the calendar to select the date.

    3. Click the Generate Report' button.

  2. To generate all daily or weekly reports from a single request, select the option Daily Reports or Weekly Reports.

    1. These group request options may not be available for all profiles.

    2. See IRM 3.17.277.13.3, EFPPS Internal Reports to identify the reports that will be generated using the Daily "D" or Weekly "W" option.

  3. Depending on the number of records in the system and the complexity of the report, it may take a significant amount of time to generate a report.

    1. If you attempt to read or print a report before it is finished, the response is a warning message rather than the requested report.

    2. To avoid unnecessary delays in receiving your reports, generate all reports first then read or print the report.

View or Print EFPPS Reports

  1. To view a report:

    1. From the REPORTS page, choose Select a report to print. From the 'Select a report name' drop down menu, select the report you wish to view and/or print.

    2. Then select a report from the 'Select a report/log file to view' and click the 'View Selected Report/Log' button.

    3. The report will open in a separate window.

    4. You can print and/or save the report by clicking on File in the top left corner of the window.

Report File Names
  1. Each time you select a report to print, the screen will display a list of the available files for the type or report. The report created most recently is listed first.

    1. The file name consists of a report "short-name" followed by mmddhhmmss. The date and time indicates when the report was generated. If the report has previously been printed, the file name is followed by "p" .

    2. For example: The file name assigned will be:
      CON__REC__LIS0430110012.p to a control record list that is generated on April 30, 2001, at 11:00:12 a.m., and printed at any time.

    3. A series of file directories will normally precede the file name on the File List.

EFPPS Internal Reports

  1. The following reports are created by the EFPPS system:

    Report Number Paper Size Freq. Report Name
    CMS 1 132 G Financial Agent Reject Report
    CMS 2 132 G Electronic Reject/Offset Mismatch Report
    CMS 3 132 H EFTPS Deleted Records List
    CMS 4 132 M EFTPS Branded Prescription Drug Fee
    CMS 5 80 M Bulk Provider Payment Report
    CMS 6 80 D Counts and Amounts
    CMS 7 80 D Daily Tax Class Receipts Report
    CMS 8 80 W EFTPS Report by Payment Method
    CMS 9 132 D, A EFTPS Deposit Ticket/Debit Voucher
    CMS 10 80 D EFTPS Daily Operations
    CMS 14 132 D RS-PCC Error Volume Report
    CMS 15 132 H EFT Audit Element Type Report
    CMS 16 80 D RS-PCC Error Inventory Report
    CMS 17 80 W Daily Counts and Amounts by Tax Type
    CMS 18 80 A Adhoc Report Summary
    CMS 19 132 W EFTPS Receipts Report
    CMS 20 132 D TIN Name Control Change List
    CMS 21 80 A EFTPS Errors by Type
    CMS 22 132 G
    W
    EFTPS Daily Trans Release Summary
    EFTPS Weekly Trans Release Summary
    CMS 23 132 G
    W
    EFTPS Daily Revenue Receipts Control Sheet
    EFTPS Weekly Revenue Receipts Control Sheet
    CMS 24 132 D EFTPS Reclassification Summary
    CMS 25 132 G EFTPS Control Record List Report
    CMS 26 80 G EFTPS Control Record Summary
    CMS 27 132 W EFTPS Age Report
    CMS 28 132 D New Suspense List
    CMS 29 132 G, A EFTPS Daily Posting Summary
    CMS 30 132 D, A EFTPS Deposit Ticket/Debit Voucher Summary Report
    CMS 31 80 A, W Manager's Weekly Security Report
    CMS 32 80 D AKPFD Report
  2. The frequency indicator of the above table is defined as follows:

    Frequency Code Description
    D Create daily prior to running the TEP
    G Computer generated at the end of TEP
    H Generated during daily Write to History
    W Weekly - Thursdays
    M Monthly - First day of following month
    A As needed or requested
  3. The report names shown above are intended to match the titles shown on the Reports Generator menu and may not match the actual title of the printed report.

  4. Most reports are listed numerically on the menu.

  5. Most of the reports should be created whenever data is present. However, printing is optional for large reports, such as the Control Record List.

CMS 1, Financial Agent Reject Report
  1. The Financial Agent Reject Report - Exhibit 3.17.277-4. This report lists each transmission, deposit ticket, batch or enrollment file that is being rejected back to the financial agent plus any batch reject from a previous day which has not been resubmitted.

    Note:

    While this report is rarely used, it is beneficial to run first if an out-of-balance condition exists.

CMS 2, Electronic Reject/Offset Mismatch Report
  1. This report lists any unidentified or offset transaction (Indicators 8, 9, A or B) for which the matching transaction that has not been received. See Exhibit 3.17.277-5.

  2. An electronic copy of this report will be emailed weekly, on Thursday, by the System Administrator to the Financial Agent at EFTPS_ACH_Ops@firstdata.com

  3. See IRM 3.17.277.5.4.1, Electronic Reject/Offset Mismatch Report, CMS 2 for additional instructions.

CMS 3, EFTPS Deleted Records List
  1. This report lists all records that have been manually deleted from EFPPS. See Exhibit 3.17.277-6.

  2. Use this report as an inventory check list to ensure that deleted records have been properly transferred or controlled on another system.

CMS 4, EFTPS Branded Prescription Drug Fee
  1. This report will list the number of payments and the total amount of payments received for the Branded Prescription Drug Fee for the 3 current tax periods.

  2. This report is sent to Headquarters and CFO by email on a monthly basis.

CMS 5, Bulk Provider Payment Report
  1. This monthly report shows the number and amount of payments for each bulk provider by payment method, plus the number and age of bulk provider errors. See Exhibit 3.17.277-7.

CMS 6, Counts and Amounts
  1. This report shows the number of payments and the total amount of payments received for each payment method and input method, including each TAC that receives RS-PCC payments.

  2. The report is issued to Headquarters daily and rolls up to a monthly and yearly report.

CMS 7, Daily Tax Class Receipts Report
  1. This report summarizes the EFTPS receipts by tax class with cumulative totals for the current day, month and fiscal year. See Exhibit 3.17.277-8. The report is in three parts: payments (all credits), reversals/adjustments (all debits) and net amount.

CMS 8, EFTPS Report by Payment Method
  1. This weekly report provides the count and amount and the error count and rate for each payment method. See Exhibit 3.17.277-29.

  2. The report is sent to Headquarters by email each Monday.

CMS 9, Deposit Ticket/Debit Voucher
  1. This report provides a printed record of each deposit ticket or debit voucher created by the financial agents for the designated processing date. See Exhibit 3.17.277-9 and Exhibit 3.17.277-10. See IRM 3.17.277.6.1.3, Deposit Tickets/Debit Vouchers, CMS 9 for instructions.

CMS 10, EFTPS Daily Operations Report
  1. The report provides numerous information relating to the daily operations of EFPPS. It is also used as an aid in balance checking. See Exhibit 3.17.277-31.

CMS 14, RS-PCC Error Volume Report
  1. This report lists the total RS-PCC errors by Site, TIN/Name Control, Tax Type, and Tax Period for each TAC.

  2. The report is sent via email to Headquarters daily.

CMS 15, EFT Audit Element Type Report
  1. This daily report lists the number of each type of error for the day and cumulative for the month, quarter and fiscal year for the financial agent. Part B lists statistics by payment method. See Exhibit 3.17.277-11.

CMS 16, RS-PCC Error Inventory Report
  1. This report lists the RS-PCC errors remaining in inventory at the end of each day. It includes the Julian date, actual date, and number of errors for each date.

  2. This report is sent to Headquarters via email daily.

CMS 17, Weekly Counts and Amounts by Tax Type
  1. This report shows the number of payments and total amount of the payments received each week. The counts and amounts are reported by each tax type, the payment method and input method.

  2. The report is generated weekly on the last business day after the TEP is run and distributed to Headquarters to be imported into an excel document and shared with Fiscal Service.

CMS 18, Adhoc Report Summary
  1. This is a report that lists each employee number, requested date and database query requested.

CMS 19, EFTPS Receipts Report
  1. This report provides the weekly, monthly, fiscal year and calendar year cumulative counts and amounts received from the financial agent. Weekly and monthly counts are also listed for each transaction indicator and for each tax type by financial agent. See Exhibit 3.17.277-12. This report is emailed weekly by the systems administrator to HQ.

CMS 20, TIN Name Control Change List
  1. This report lists every record in which both the TIN and name control have been changed by error correction, approved by a manager and processed by TEP. See IRM 3.17.277.12.5, Review TIN/Name Control Changes for instructions and Exhibit 3.17.277-13 for an example.

CMS 21, EFTPS Errors by Type
  1. This report shows the number of errors by element type (TIN, Name Control, Tax Type, Tax Period, Payment Date, and Origination Date) on a specific date or time period.

CMS 22, EFTPS Trans Release List Summary
  1. This report contains the total record count and debit and credit amount on each transaction file. An additional Weekly Trans Release Summary (on Thursday morning) includes the total count and amount of all transmittals made during the cycle. See Exhibit 3.17.277-14.

CMS 23, EFTPS Revenue Receipts Control Sheet
  1. This report summarizes by tax class and Master File the revenues being transmitted to ECC-MEM for a TEP or a cycle. See Exhibit 3.17.277-15.

  2. The Revenue Receipts Control Sheet is created daily for transmittal with the TEP and weekly (on Thursday morning) to include amounts for all of the TEPs for the cycle. See IRM 3.17.277.6.7.2(3)(d), TEP Reports regarding an imbalance condition.

CMS 24, EFTPS Reclassification Summary
  1. This is a daily report that summarizes all tax changes created as a result of error corrections or as a result of mis-classification by the financial agent. This report should mirror the EFPPS Deposit Reclassification Journal Record that is transmitted to RRACS for automated journalizing. See Exhibit 3.17.277-16.

  2. Part II contains detailed information about each reclassified record.

  3. Tax Class "9" must equal Miscellaneous Account 4765. If an imbalance occurs, refer to IRM 3.17.277.7.3.2, Manual Reclassification.

CMS 25, EFTPS Control Record List
  1. This report is produced daily showing all EPCF Control Records. Control records are sorted by batch number then chronologically in the sequence that the control record was created. Manual Control Records are listed separately. The listing may be maintained on-line with immediate printing available upon request. See Exhibit 3.17.277-17.

CMS 26, EFTPS Control Record Summary
  1. This report lists the count, payment amount and debit amount for each from - to code combination. Totals are provided for each Master File plus a grand total. See Exhibit 3.17.277-18.

CMS 27, EFTPS Age Report
  1. This report lists the EFT #, status, tax type, amount, # of days aged, and employee # for all transactions remaining in EFPPS for more than 7 days. It also lists the batch #, # item of aged items in the batch, total amount of aged items, and # of days aged for all aged batches. See Exhibit 3.17.277-19.

  2. See IRM 3.17.277.9.3, Controlling the Aged Inventory for instructions for reviewing the aged report. This report is emailed weekly to HQ.

CMS 28, EFTPS New Suspense List
  1. This report provides an inventory list of all payment records or batches that have been moved to suspense status. See Exhibit 3.17.277-20.

  2. The report contains the totals of suspended items and debit or credit amount for each Master File, any rejected batches and a grand total.

  3. See IRM 3.17.277.9, Suspense Inventory for instructions.

CMS 29, EFTPS Daily Posting Summary Report
  1. This report provides the daily or monthly count and amount of all records that have moved into or out of each control file status. See Exhibit 3.17.277-21.

CMS 30, EFTPS Deposit Ticket/Debit Voucher Summary Report
  1. This report provides a listing of all deposit tickets and debit vouchers for the process date by amount and voucher number plus summary totals by Master File for the process date and by financial agent for the settlement date. See Exhibit 3.17.277-22.

  2. See IRM 3.17.277.6.1.4, Deposit Ticket/Debit Voucher Summary Report, CMS 30 for instructions.

CMS 31, Manager's Weekly Security Report
  1. This report lists the access date, employee number and SSN of anyone attempting to access a record with their own or spouse's social security number or another EFPPS user's or spouse's SSN and the accessed SSN.

  2. Due to sensitive information, this report can only be generated and printed by a manager. See Exhibit 3.17.277-23.

CMS 32, AKPFD Report
  1. This report lists the total count and amount for the Alaska Permanent Fund Dividend as well as the count and amount for each master file (IMF and BMF).

  2. The report is emailed daily to Annette Dean, Stephanie Thomas, and Ina Smith.

Financial Agent Reports

  1. The following reports are created by the financial agent and are available on the 'EFTIRSReports' share drive.

    Bank of America
    Report Number
    Report Name
    IRS01, 02, 03 Daily Summary Report
    IRS04 Daily Exception Report
    IRS05 Part II Daily Exception Report
    IRS08 Monthly Enrollment Status Report Business Taxpayers
    IRS09 Monthly Enrollment Status Report Individual Taxpayers
    IRS10 Enrollment Status
    IRS11 Form 720 Abstract Report
    IRS13 ELF ACH Electronic Funds Withdrawal Report
    IRS16 EFTPS Filer Enrollment Report
    IRS17 EFTPS Enrollment Report
    IRS18 EFTPS Daily Credit Card Report
    IRS21 Bulk Provider Payment Report
    IRS22 EBP Quality Measures Weekly Report
    IRS23 State Levy Program Weekly Summary Report
    IRS24 Pre-Enrollment for Business Program Statistics Report
    IRS25 Pre-Enrollment for Business Reject Record Report
    IRS27 E-file Warehouse (Scheduling) Payments Report
    IRS34 Third Party Disclosure Authorization Report
    IRS35 Insolvency Program Voucher Report
    IRS36 Insolvency Program Voucher Detail Report
    IRS37 Insolvency Program Settlement Report
    IRS40 DDIA Payment Report
    IRS50 IMAD/EFT Report
    N 10A Funds Settlement Summary Report
    N 47/ IRS12 Monthly International Summary Report
    FI Assessment FI Assessment (Faxed to IRS)
  2. The financial agent report file contains two types of reports.

    1. Reports created for IRS use.

    2. Reports created for Fiscal Service that are also made available to IRS.

  3. In addition to the report file, all Financial Agent reports are retained on line for 120 days and archived for 7 years. On line reports are retrieved immediately, while archived reports are reactivated, then accessed directly.

View or Print Financial Agent Reports
  1. Financial agent reports are normally printed daily by Information Systems.

  2. Financial Agent reports will no longer be available on the EFPPS application. These reports can be found on the EFT IRS Reports Share Drive. You need to request permission for each report through Electronic payment headqueaters.

  3. Once you have access to the report on the share drive and have saved the EFT IRS Reports folder to your desktop you will be able to go into each report folder to access a report.

  4. The reports are listed in date order with the earliest at the top. The report files names are listed by report number, date and time as IRSnn.yymmddhhmmss. Double click on the report you wish to view. The report will open in a new window.

  5. To print a report, select the report as above and follow normal printing procedures.

Description of Financial Agent Reports Created for IRS
  1. Financial agent reports created for IRS are numbered with the prefix "IRS" from Bank of America.

  2. The Daily Summary Report (IRS01, 02, 03) is created by the financial agent, summarizing the deposit ticket totals for each day. See Exhibit 3.17.277-24.

    1. This report provides daily count and amount totals by tax class plus cumulative totals for the month and fiscal year.

    2. The report is in three parts: payments, reversals/adjustments and net.

  3. Daily Exception Report (IRS04) - This 2 - part report lists by reason code the exception items that have been processed by the financial agent. See Exhibit 3.17.277-25.

    • Part I - Current Date. Part I lists the item count and amount for each reason code for the current date and cumulative for the month and fiscal year.

    • Part I - Transaction Detail. Part II lists the originating depository financial institution (ODFI), TIN, effective date, tax type code, tax period and amount for each exception item.

    • See Glossary for a list of the reason codes.

  4. Form 720 Abstract Report (IRS11) - This quarterly report provides the count and amount reported for each Form 720 abstract number for each tax period quarter of a two year period. See Exhibit 3.17.277-26.

    1. The earliest period also includes any money reported for an earlier tax period; the latest period also includes future tax periods.

    2. Each taxpayer making a Form 720 payment is asked (but not required) to indicate the IRS numbers for the excise taxes being paid.

    3. This report is issued semi-monthly in addition to quarterly.

    4. This report must be sent by ECC-MEM via email to Dean Overman and Sharmeka Laney at the office of the Chief Financial Officer.

  5. Financial Agent Bulk Provider Payment Report (IRS21) - Exhibit 3.17.277-27.

    1. This monthly report provides a detailed analysis of the payments received from each bulk provider. The primary purpose of the report is to provide a tool for the National Account Managers to evaluate and assist the bulk providers.

    2. See IRM 3.17.277.11.1 (2), Bulk Provider Reports.

  6. EFTPS Enrollment Report (IRS17) - Exhibit 3.17.277-28.

    1. This report provides summary information of EFTPS enrollments received, approved and rejected for each enrollment method.

    2. See IRM 3.17.277.11.1 (3), Bulk Provider Reports.

  7. EFTPS Filer Enrollment Report (IRS16) - This report provides specific enrollment data on each bulk and batch provider that submitted enrollments during the month.

  8. Pre-Enrollment for Business Program Statistics Report (IRS24) - This report provides a detailed specifics and analysis of the different pre-enrollment programs in process.

  9. Insolvency Program Settlement Report (IRS37) - Exhibit 3.17.277-32.

    1. This report is generated daily by the EFPPS unit.

    2. If there is significant data on the report, the EFPPS unit will print the report and deliver it to RRACS the same day.

  10. DDIA Payment Report (IRS40) - Exhibit 3.17.277-33. This report provides payments received (volume and dollars) by tax type code both daily and fiscal year cumulative.

Description of Financial Agent Reports Prepared for Fiscal Service
  1. Reports prepared by the financial agent primarily for Fiscal Service, but available to IRS, are numbered as follows:

    • Position 1: "N" for Bank of America

    • Positions 2 - 3 or 2 - 4: Report number as shown below

    • Positions 4 - 9 or 5 - 10: Date of the report in MMDDYYYY format

    • Example of report numbers: N10A080502

  2. Fiscal Service report 10, Funds Settlement Summary Report - This report provides daily and cumulative count and amount totals for ACH debit, ACH credit and FTCS/ACH payment, return and reversal.

  3. Other reports are created by the system but not used by IRS.

Historical Reference/Audit Trail Information

  1. Prior to January 1, 1997, a File Location Code (FLC) of "71" was used.

  2. Prior to July 1, 2005, all EFPPS processing was done at the Memphis Campus. After this date, balancing and error resolution functions were relocated to the Ogden Campus. For research purposes, the following information is provided –

    • Memphis ALC – 20094900

    • "49" in the first two digits of the EFT number indicates Memphis

    • File Location Code (FLC) of "72" in the first two digits of the DLN indicates Memphis

  3. Prior to November 2004, two financial agents operated EFTPS. For research purposes, the following information is provided –

    • A "1" in position one of the EFT number (FA ID number) indicates a Bank One transaction.

    • An enrollment code of "84" indicates that the taxpayer originally enrolled with Bank One.

    • Bank One deposit tickets were numbered with a 2, 3 or 4 in the first position and debit vouchers had a 4 or 5 in the second position. Bank One vouchers had a Routing Transit Number 071036210 for ACH credits or 071036207 for ACH debits and a 1 in the second position of the associated batch numbers.

    • All bulk providers, with the exception of ADP, were processed through Bank One.

Glossary

  1. ABA Number - The routing and transit number that identifies a financial institution. The American Banking Association (ABA) number is assigned by Thompson Financial Publishing.

  2. ACH CREDIT (also known as EFTPS Through Your Financial Institution) - The payment method in which the taxpayer's financial institution initiates an electronic payment to the Treasury Financial Agent.

  3. ACH DEBIT - The payment method in which the taxpayer directs the Treasury Financial Agent to initiate an electronic debit of the taxpayer's bank account.

  4. ACH REASON CODES -

    Reason Code Description
    Return Reason Codes: Taxpayer Error (Transaction Indicator 1)
    R01 Insufficient funds
    R02 Account closed
    R07 Authorization Revoked by Customer (adj entries)
    R08 Payment stopped
    R09 Uncollected funds
    R16 Account frozen
    R29 Corporate customer advises not authorized
    Return Reason Codes: Non Taxpayer Error (Transaction indicator 4)
    R03 No account/unable to locate account
    R04 Invalid Account Number
    R05 Required Pre-notification Not Received
    R06 Returned per Depositary Financial Institution's (DFI) request
    R10 Customer advises not authorized
    R11 Check truncation entry return
    R12 Branch sold to another DFI
    R14 Account-holder deceased
    R15 Beneficiary deceased
    R17 File record edit criteria
    R20 Non-transaction account
    R21 Invalid company identification
    R22 Invalid individual id number
    R23 Payment Refused by biller
    R24 Duplicate entry
    R31 Permissible Return Entry
    R33 Return of XCK Entry
    Dishonored Return Codes
    R61 Misrouted Return
    R62 Incorrect Trace Number
    R63 Incorrect Dollar Amount
    R64 Incorrect Individual Identification
    R65 Incorrect Transaction Code
    R66 Incorrect Company Identification
    R67 Duplicate Return
    R68 Untimely Return
    R69 Multiple Errors
    R70 Permissible Return Entry Not Accepted
    Contested Dishonored Returns
    R71 Misrouted Dishonored Return
    R72 Untimely Dishonored Return
    R73 Timely Original Return
    R74 Corrected Dishonored Return
    Notification of Change Codes
    C01 Incorrect DFI Account Number
    C02 Incorrect Routing Number
    C03 Incorrect Routing and DFI Numbers
    C04 Incorrect Individual or Receiving Company Name
    C05 Incorrect Transaction Code
    C06 Incorrect DFI Number and Transaction Code
    C07 Incorrect Routing/DFI Number and Transaction Code
    C09 Incorrect Individual Identification Number
    C10 Incorrect Company Name
    C11 Incorrect Company Identification
    C12 Incorrect Company Name and Identification
    C13 Addenda Format Error
    Refused Notification of Change Codes
    C61 Misrouted Notice of Change
    C62 Incorrect Trace Number
    C63 Incorrect Company Identification Number
    C64 Incorrect Individual Identification Number
    C65 Incorrectly Formatted Corrected Data
    C66 Incorrect Discretionary Data
    C67 Routing Number Not From Original Entry Detail Record
    C68 DFI Number Not From Original Entry Detail Record
    C69 Incorrect Transaction Code
  5. AD HOC REQUEST - A research request initiated to the EFTPS or financial agent's data base, using a variable format, depending on the type of information requested. The request is entered on the ADHOC query screen.

  6. AGENCY LOCATION CODE (ALC) - A prescribed eight (8) digit numeric code identifying the government office involved in a financial transaction. For the Ogden Submission Processing Center, the ALC is 20092900.

  7. ASSIGNED INDICATOR - Indicator on the Manager's Screen list of Unresolved EFTs that identifies a record as assigned to an individual or function. Values:

    Assigned Indicator
    R Held by an error correction employee for further research.
    E Determined to be in error by quality review
    D Deleted
    N No error charged
    S Suspense status
    T Suspended from research status
    U Suspended after determined to be in error by quality review
  8. AUTO CORRECTION - Errors that are systemically corrected without review by a technician. If EFTPS sends a blank name control field to CFOL, EFPPS will use the returned name control data to auto-correct the blank name control field in the payment transaction. See IRM 3.17.277.8.9, Tax Period for tax period auto corrections and IRM 3.17.277.8.1 , Four Types of Payment Validations for tax type auto corrections.

  9. AUTOMATED CLEARING HOUSE (ACH) - The central clearing house facility where electronic funds transfer instructions are exchanged between banks.

  10. BATCH PROVIDER - A payroll processor, tax preparer, bank, fiduciary or large company that transmits payments for more than two TINs and is registered with an EFTPS financial agent to provide an accelerated system for transmitting enrollment and payment information.

  11. BATCH NUMBER - A 10 - position field number assigned by the financial agent that is included on the batch header, associated with each transaction and included with each deposit ticket or debit voucher received from the financial agent.

    Positions Description
    1 - 2 Financial Agent ID Number
    3 Year digit
    4 - 6 Julian Date
    7 - 10 Batch serial number
  12. BULK PROVIDER - A large payroll processor or reporting agent registered with an EFTPS financial agent to transmit 1,000 or more payments with a single ACH or FTCS transaction. Each set of up to 1,000 payment records is associated with a consolidated debit transaction.

  13. BULK PROVIDER NUMBER - Number assigned by the financial agent to each bulk debit and bulk same day payment received from a bulk provider and inserted into the EFT number in positions 8 and 9. This number identifies the originator of the payment whenever the Combined Payment Indicator (position 3 of the EFT number) is 7, 8, or 9. If the Combined Payment Indicator is other than a 7, 8, or 9, this number has other meanings and is dependent on both the Payment Method (position 2) and the Combined Payment Indicator (position 3). See the table in IRM 3.17.277.5.3(4), EFT Number for specific applications.

    1. Phone numbers shown below are for IRS use and should not be given to taxpayers.

    2. The following is a table listing the bulk providers, their EFT number range and contact telephone numbers.

      EFT number Range Bulk Provider Contact Phone Number
      01 - 05 ADP 909-480-7287 or 626-831-5440
      06 - 10 Dabco/Remit One/Click Tax 800-281-6570
      11 - 17 Trust Banks
      18 - 20 State Levies
      31 - 32 Link2Gov (credit cards) 877-513-5465 opt 2
      41 Advantage I 800-876-0178 (ext. 20500)
      41 Advantage II 585-336-7566, 585-336-7435
      N/A BTS Payright
      43 Ceridian STS 800-829-7761 (ext. 4785)
      44 Ceridian TaxTel 714-377-5528
      after hrs 714-377-5566
      45 Compupay 954-874-4800, 305-591-8627
      46 Intuit 800-446-8848
      N/A Interlogic Systems
      N/A Zurich Payroll Solutions (Pay USA)
      54 - 55 Paychex 585-336-7566, 585-336-7435, 585-336-7330
      56 Payroll One 248-731-1521
      after hrs 313-580-4462
      57 Payroll People 559-440-8280
      after hrs 559-970-1371
      59 - 61 Official Payments (credit cards) 925-855-5049 / 925-719-3764
      70 - 71 WorldPay US, Inc (credit cards) 615-730-6367 (ext. 380) / 615-417-9529
      62 Computer Language Research (Fast Tax) 972-250-8914 or 972-250-7385
      63 Northern Trust 312-444-4427 or 312-557-5984
      64 - 65 File Your Taxes 805-644-9398 / 805-469-4699
      66 - 67 PayCycle (Intuit) 775-424-8034
  14. CENTRALIZED AUTHORIZATION FILE (CAF) - An IRS file that contains information regarding the type of authorization that taxpayers have given representatives for various modules within their accounts.

  15. COMPUTER INTERFACE PROTOCOL SPECIFICATIONS (CIPS) - A document that describes the format of enrollment and tax deposit data sent and received by the FTCS system.

  16. COMPUTING CENTER CODE - Code to identify one of two IRS computing centers that will process electronic payments: ECC-MEM - 01 and ECC-MTB - 03. This code is validated on the Transmission Header Record to ensure that the file has been sent to the correct computing center.

  17. CONFIRMATION NUMBER - The 8 - digit number given to taxpayers who initiate an ACH debit by telephone or on-line. This number becomes the last eight digits of the EFT number.

  18. CONTESTED DISHONORED RETURN - An ACH Debit can be returned by the recipient financial institution (FI) for a variety of reasons. The initial FI can, in turn, disapprove of this return (Dishonored Return) and send it back. The last action allowed in this process is a refusal of the Dishonored Return by the recipient which is a Contested Dishonored Return.

  19. CORPORATE FILES ON LINE (CFOL) - The Master File data base that is used to validate EFTPS entity data for enrollment records and EFTPS entity data and filing requirements for payment records.

  20. DEBIT VOUCHER - The SF 5515 is the record of payments that are returned or reversed by the taxpayer's financial institution. EFTPS debit vouchers are received electronically from the financial agent, printed by EFPPS and sent to RRACS for posting as journal 111.

  21. DEPOSIT TICKET - The SF 215 or 215A is the official record of the amount of a deposit that has been credited to Treasury. For EFPPS, the deposit ticket is received electronically from the financial agent and printed by EFPPS. A separate electronic deposit ticket record is generated by EFPPS for automated posting to RRACS as a 110 journal.

  22. DEPOSIT TICKET SETTLEMENT DATE - The date in which a deposit is credited to IRS. The date must not be a Saturday, Sunday, or Federal Reserve holiday. The format on the incoming file and printed reports is YYYYMMDD, but the format on error correction windows is DD–MON–YYYY.

  23. DEPOSIT TICKET/DEBIT VOUCHER NUMBER - Six (6) digits assigned by the financial agent to uniquely identify a deposit ticket or debit voucher.

    1. A deposit ticket number always contains a number other than zero in the first position.

    2. A debit voucher contains a zero in the first position.

    3. Federal Payment Levy Program deposit tickets are identified by a "C" , followed by five numerics. Debit vouchers contain a "D" , followed by five numerics.

    4. SSA Levy Program deposit tickets are identified by an "E" , followed by five numerics.

  24. DEPOSITORY FINANCIAL INSTITUTION (DFI) - A member institution or ABA number which is responsible for the origination of ACH transactions. This institution may deposit items directly with an ACH or may work through a process center which is the actual sending point. The DFI number is a nine (9) digit number which identifies the bank where the taxpayer's account resides. For most ACH credits, the first 8 positions of the DFI number will match the first 8 positions of the reference number.

  25. DIRECT DEBIT INSTALLMENT AGREEMENT (DDIA) - program that collects and processes Installment Agreement payments for delinquent taxpayers. DDIA payments are identified by an eft number beginning with 221 and 02 in positions 8 and 9.

  26. DISCREPANCY CODE - This field is used on the EFTPS enrollment record to identify differences between the name and TIN submitted by the taxpayer and the taxpayer's name and TIN on CFOL. Incoming from the financial agent, the field will always be blank. EFPPS will insert one of the following codes to indicate a discrepancy. Codes 0, 1, 2 and 4 are accepted enrollments. Codes 3, 5, 6, 7, 8 and 9 are disapproved. See IRM 3.17.277.4.2, Enrollment Discrepancy Codes.

  27. DESIGNATED PAYMENT CODE - Code used by Collection to identify a specific fund, liability, or event associated with a payment. For EFTPS, the codes currently used are 12 for IRC § 6603 Deposits (formerly Cash Bonds), 18 for the Federal Payment Levy Program, 20 for all tax types ending in "L" (designated for SITLP payments), 22 for all tax types ending in "K" (designated for AKPFD payments), 30 for all tax types ending in "M" (designated for MTLP payments), 27 for Branded Prescription Drug Fee payments, 63 (converted to 03 on output) and 71 (converted to 11 on output) for RS-PCC payments. In addition, payments from Bank of America with a payment method of 9 and an SSN must include DPC 16 or 17.

  28. DOCUMENT LOCATOR NUMBER - Number assigned to each payment record by EFPPS prior to the transactions being sent to Master File. As of July 2012 the DLN of EFTPS payments is unique.

    Positions Description
    1 - 2 File Location Code - 81, 82, and 83 in ECC-MEM that are worked in Ogden Submission Processing Center. Other codes will be assigned if EFPPS expands to other locations.
    3 Tax class
    4 - 5 Document Code 19
    6 - 8 Julian date - The Settlement Date. If the number of payments exceeds the amount of DLN's issued in one day, the system will add 400 to the Julian date for any remaining payments.
    9 - 11 Block number - sequentially assigned number (does not have to be unique)
    12 - 13 Serial Number- sequential within a block
    14 Year digit - the year of the julian date
  29. ENTERPRISE COMPUTING CENTER (ECC) - there are two: ECC-MTB and ECC-MEM.

  30. EIN/SSN INDICATOR - A one (1) digit numeric to distinguish an SSN from an EIN. SSN - 1, EIN - 2. There are some SSNs on the BMF file.

  31. ELECTRONIC FUNDS TRANSFER NUMBER (EFT Number) [EFTPS System] - A unique 15 numeric field that is assigned by the financial agent and carried through the EFPPS system. This number must not be duplicated. The number shall consist of the following:

    Position Field Name Values
    1 Financial Agent ID 2 Bank of America
    3 Federal Payment Levy Program
    4 SSA Levy
    5 RS-PCC
    2 Payment Method 0 E–file Debit
    1 ACH credit
    2 ACH debit
    3 FTCS
    4 Reserved
    5 Levy
    6 Credit Card
    7 Online
    8 RRB Link
    9 Government
    3 Combined Payment Indicator An extended level of detail regarding the payment which is dependent on the Payment Method. For specific identification, see table in IRM 3.17.277.5.3(4), EFT Number.
    4 - 7 Year Digit/Julian date Year digit plus 001 - 366. If overflow, 401 - 766 may be used. The date that the EFT number was assigned.
    8 - 9 Bulk Provider Number
    RS-PCC
    Number assigned to identify the bulk provider who initiated the bulk debit or bulk same day payment (See Bulk Provider Number for list of bulk providers). It is also used to identify other payment detail when the Combined Payment Indicator is other than a 7, 8, or 9.
    For RS-PCC:
    00 - Campus Discovered Remittance, 01 - PAMC Insolvency, 02 - PAMC Perfect, 03 - PAMC Imperfect, 04 - PAMC Field Office, 05 - BAMC Perfect, 06 - BAMC Imperfect, 07 - MAMC Perfect, 08 - MAMC Imperfect, 09 - BAMC COIC, 10 - MAMC COIC, 11 - ANAMC Perfect, 12 - ANAMC Imperfect, 13 - ATAMC Perfect, 14 - ATAMC Imperfect, 15, 16, 17 - AUSPC (OVDP), 18 - Bulk KCSPC, 19 - Bulk OSPC
    8 - 9 Bulk Provider Number
    RS-PCC (TAC)
    For TAC Remittance see Exhibit 3.17.277-3
    8 - 15 or 10 - 15 EFT Sequence Number Unique number assigned by financial agent
  32. ELECTRONIC FUNDS TRANSFER NUMBER (EFT Number) [Master File and IDRS] - a unique 17 - position number used by Master File and IDRS. The number consists of a leading 2 digit submission processing center code, followed by a 15 position EFT number shown above.

    Position Field Name
    1 - 2 Submission processing center Code - 29 for Ogden
    3 Financial Agent ID
    4 Payment method
    5 Combined Payment Indicator (Input method)
    6 Year digit
    7 - 9 Julian date
    10 - 11 Bulk Provider Number/RS-PCC
    10 - 17 or 12 - 17 Serial Number
  33. ELEMENT TYPE - A number that identifies a field within a payment record, used on the EFPPS audit record to identify a field that was changed.

    Code Element Type
    1 TIN
    2 Name control
    3 Tax period
    4 Payment date
    5 Origination Date
    6 Status
    8 Tax type code
    9 FUTA
    10 Original Payment Date
    11 Transaction Indicator R
  34. EMPLOYEE NUMBER - A 10 digit number used to identify an employee. The first two digits of an employee number identify the office where an employee is assigned, such as district, campus, region or area office.

  35. EMPLOYER IDENTIFICATION NUMBER (EIN) - A unique nine (9) digit identifier issued by the IRS to business taxpayers for the purpose of reporting tax related information. An EIN may also be referred to as a Taxpayer Identification Number (TIN).

  36. END OF DAY TRANSMISSION RECORD (EOD) - The EOD is required with the last transmission for each transmission date. If no payments are transmitted, a zero count and amount is required.

  37. ENROLLMENT CODE - A code on the entity module (ENMOD, BMFOLE, IMFOLE) to indicate that a taxpayer is enrolled in EFTPS with a designated financial agent. The code is labeled "Enrollment Cd" on BMF and "EFTPS" on IMF.

    Enrollment Code Financial Agent
    84 Bank One
    85 Bank of America
    8485 Both financial agents
  38. ENTITY VALIDATION INDICATOR - A code assigned by the Financial Agent indicating that an inconsistency was found between the Name Control, TIN and/or filing requirements of a payment transaction and the information in the FAs entity database. When this indicator is present, the payment will be sent to CFOL for validation.

    Code Description
    I Invalid
    N Not Enrolled in EFTPS
    D Duplicate TIN on FA Database
    blank Valid
  39. FEDERAL PAYMENT LEVY PROGRAM (FPLP) - The Fiscal Service Treasury Offset Program sends a portion of Federal payments to EFPPS to satisfy delinquent tax debts. On EFPPS, these payments are identified by a "3" in the first position of the EFT number.

  40. Federal Tax Collection Service (FTCS) - Same day payment application operated by US Bank (ACH Credit Gateway). Funds are transferred from the originating financial institution at the same time as the payment detail. These also known as "Wire" payments.

  41. FEDERAL TAX DEPOSIT (FTD) - A mandatory periodic tax payment made by business taxpayers for various types of taxes such as withholding, unemployment and social security taxes.

  42. FEDLINE - The Federal Reserve's proprietary communications software for financial institutions.

  43. EFTPS for Federal Agencies - Program operated by Bank of America to process tax payments made by Federal agencies. On EFPPS, these payments are identified by "29" in the first two positions of the EFT number.

  44. FEDWIRE - The communication network owned and operated by the Federal Reserve System that supports various deposit and reporting applications, including the Funds Transfer application.

  45. FISCAL SERVICE Financial Management Service (FMS) and Bureau of Public Debt (BPD) became one consolidated agency named Bureau of the Fiscal Service, referred to in this IRM as Fiscal Service. See http://www.fiscal.treasury.gov.

  46. FTCS INDICATOR - An indicator identifying taxpayers who have enrolled listing the Federal Tax Collection Service (FTCS) as their primary payment method.

  47. FILE LOCATION CODE - A unique two position numeric code that identifies the originating IRS center. For EFPPS, the code also identifies the type of processing. See Document Locator Number.

  48. FILING REQUIREMENTS - All tax returns that a particular taxpayer is required to file. Each indicator that is not blank indicates that the taxpayer has this filing requirement.

  49. FINANCIAL AGENT (FA) - The financial institution selected to manage and operate the Electronic Federal Tax Payment System. Also known as the Treasury Financial Agent (TFA). Bank of America Merrill Lynch became the TFA November 14, 2004.

  50. FINANCIAL AGENT IDENTIFICATION NUMBER (FA ID) - A one or two digit number used to identify each financial agent.

    FA ID Number Description
    02 or 2 Bank of America
    03 or 3 Federal Payment Levy Program
    04 or 4 SSA Levy
    05 or 5 RS-PCC
  51. FISCAL YEAR MONTH - Tax year ending month used primarily for Form 1120, U.S. Corporation Income Tax Return, and Form 990, Return of Organization Exempt From Income Tax, series tax returns and payments. Calendar year taxpayer's fiscal year month is 12.

  52. Foreign Account tax Compliance Act (FATCA) - FATCA generally requires certain FFIs to report certain information about fi nancial accounts held by U.S. taxpayers as well as accounts held by certain foreign entities in which U.S. taxpayers hold a substantial ownership interest. FATCA requires withholding agents to withhold 30 percent of certain payments unless the FFI agrees to report certain information with respect to its U.S. accounts.

  53. FUTA VERIFICATION - FUTA (Form 940) payments amounts equal to or greater than $100,000 are sent to error to be verified, except during periods January 26 to February 5, April 25 to May 5, July 26 to August 5, and October 26 to November 5.

  54. Global Intermediary Identification Number (GIIN) - A 19 character identification number that is a composite of the following identifiers: FATCA ID, financial institution type, status code, and country identifier. A Financial institution registered to be FATCA compliant is issued a GIIN.

  55. INPUT MESSAGING ACCOUNTABILITY DATA (IMAD NUMBER) - A time stamp that is assigned to a Fedwire message when it is processed by the Federal Reserve Bank Funds Transfer application.

  56. INTERNAL REVENUE MANUAL (IRM) - A compilation of procedures and practices developed to implement the Code and policies for the IRS.

  57. JULIAN DATE - Julian Date is a three digit numeric identifying the day of the year. Example: February 1 would be shown as 032.

  58. MANDATED TAXPAYER (Required Taxpayer) - Taxpayers are required to submit their tax deposits and estimated tax remittances using electronic funds transfer, unless they are allowed to make their remittance with their return under existing regulations. The mandate year is displayed as the Electronic Deposit Year on BMFOLE (refer to Publication 15).

  59. MASTER FILE TYPE CODE - Code on the batch header record and on the control file used to designate the Master File assigned to the associated payment records.

    Code Master File
    1 Individual Master File (IMF)
    2 Business Master File (BMF)
    6 Non-Master File (NMF)
    7 Miscellaneous—Unclassified, unidentified, or user fee
  60. NAME - Taxpayer's legal business name recorded with IRS related to a unique Employer Identification Number, or for an individual the name registered with Social Security.

  61. NAME CONTROL - A 4 position code used to validate the taxpayer's name against the TIN. Incoming from the FA in the enrollment records, the field will always be blank. IRS sends the name control back to the FA on approved enrollment request records. The name control is then inserted by the FA on each payment record being passed to IRS.

  62. ORIGINAL PAYMENT DATE - For returns and reversals, this date is used to identify the payment date of the original transaction that is being offset. This date becomes the transaction date for Master File processing. In all other cases, this date is blank.

  63. ORIGINATION DATE - Identifies the date the payment amount was reported to the FA by the taxpayer. For ACH credits, this date is always the same as the payment date. The date is in YYYYMMDD format on the incoming file and on printed reports, and in DD-MM-YYYY format on error correction windows.

  64. PAYMENT DATE - The date that the taxpayer is credited with making the payment. The payment date can never be later than the settlement date. If the date is earlier than 30 days prior to the settlement date or 360 days prior to the current processing date, the record is sent to error where the date can be accepted or changed. The payment date should be the same as the settlement date unless:

    1. The financial agent has made a processing error.

    2. For credit or debit card payments, the payment date is the card authorization date.

  65. PAYMENT METHOD - The second position of the EFT number:

    Code Method
    0 IRS e-file payment (ACH debit)
    1 ACH credit (also known as EFTPS through your financial institution)
    2 ACH debit (also known as EFTPS Direct)
    3 FTCS
    4 Reserved
    5 Levy
    6 Credit Card
    7 Online
    8 Railroad Retirement Board (RRB) Link
    9 Government (FEDTAX/EFTPS for Federal Agencies, Federal Payment Levy Program or SSA Levy)
  66. POINT-OF-SALE (POS) REPORTING - A payment method in which a taxpayer enters tax payment instructions into an electronic terminal in an off-line mode and then transmits the instructions to the FA. (Not currently available on EFPPS)

  67. PROCESS CODE - A code that identifies the current status of a transaction on the EFPPS data base. Records with current process codes 1, 2, 3, 4, 5, 6, 7, 9, 10 and 11 are in batch control status on the control file. Process codes 8 and 15 are error status, and process code 14 is suspense status:

    Code Description
    0 Nullified
    1 Received
    2 Passed FUTA
    3 CFOL2
    4 CFOL3
    5 Passed CFOL
    6 Bypassed CFOL
    7 Passed field validation
    8 Unresolved
    9 Awaiting quality review
    10 Resolved
    11 TEP
    13 Deleted
    14 Suspended
    15 Awaiting Manager Review
  68. QUALIFIED INTERMEDIARY (QI) - A foreign institution (primarily banks or investment firms) approved by the IRS to withhold U.S. Federal taxes and assume primary responsibility for their clients to pay those U.S. Federal taxes.

  69. RECORD TYPE - The record type is a one character field used to identify the type of data record within a file received from the financial agent.

  70. REFERENCE NUMBER - A verification number that may be used to trace a payment through the banking system. The Reference number has a different meaning for each type of payment.

    Payment Type Reference
    ACH Debit or Credit ACH Trace Number, which is available to the taxpayer's bank and may be listed on the taxpayer's bank statement
    FTCS 18 - character IMAD number.
    e-file Electronic Funds Withdrawal debits e-file Declaration Control Number
    Integrated e-file and Pay card payments e-file Declaration Control Number
    Pay by Phone or Internet (credit card payments) 7 - digit confirmation number ending in a "1" for Official Payments a "3" for Link2Gov, or a "4" for WorldPay US, Inc. See IRM 3.17.277.1.4.12.1, Credit or Debit Card Pay By Phone and Internet for prior year exceptions.
    Federal Payment Levy Program Treasury Offset Program trace number
    Reversals EFT number of original payment
    GIIN See IRM 3.21.112.4, Global Intermediary Identification Number (GIIN).
    1. The ACH Trace number or any number, other than the EFT number, which is included in other payment options is termed "reference number" .

    2. For most ACH credits, the first 8 positions of the reference number are the first 8 positions of the DFI number.

    3. For FTCS payments, it is an 18 - character IMAD number which may or may not be given to the taxpayer.

    4. For e-file and "integrated e-file and pay" card payments, the reference number is the e-file declaration control number (DCN).

    5. For "pay by phone or internet" card payments, the number is the 7 - position confirmation number.

    6. For Federal Payment Levy payments, the reference number is the TOP Trace Number.

    7. For reversals, the reference number is the EFT number of the payment being reversed.

    8. While the GIIN is not a payment type, if a business taxpayer enters a GIIN into EFTPS (such as when making a payment related to a Form 1042), then the GIIN is stored in the refernce number field. See IRM 3.17.277.1.4.18.2 (3).

  71. REMITTANCE STRATEGY for PAPER CHECK CONVERSION (RS-PCC) - RS-PCC is the process of converting paper checks into electronic ACH (Automated Clearing House) Debits. These are tax payments received in Brookhaven, Memphis, Philadelphia, Atlanta, Andover, and Austin Campuses. Payments received include Insolvency (Philadelphia Campus). Offer in Compromise (Brookhaven and Memphis) and OVDP (Austin). It also includes tax payments that are received in Taxpayer Assistance Centers (TAC). RS-PCC will interface with EFPPS, which will send taxpayer payment information to the Master File for posting. RS-PCC EFT numbers begin with "520" (Campus) and "521" - "524" (TAC).

  72. REPORTING AGENT FILE (RAF) - An IRS file that contains information regarding the type of authorization that taxpayers have given to third parties to send and receive tax information with IRS. This file is researched using Command Code RFINQ.

  73. RETURN - In EFTPS, a return is a transaction not accepted by the receiving financial institution. For ACH debits, a return is a payment not accepted by the taxpayer's bank, due to insufficient fund, account closed, etc. For ACH credits, a return is a transaction not accepted by the financial agent.

  74. RETURN REASON CODES - See ACH Reason Codes.

  75. REVERSAL - A transaction created to cancel a previous Electronic Funds Transfer (EFT) transmitted to EFPPS. Used for the most part with duplicate entries.

  76. ROUTING TRANSIT NUMBER (RTN) - A nine (9) digit number (eight digits and a check digit) that identifies a specific Financial Institution.

  77. SAME-DAY DEPOSIT - A tax deposit sent to the FTCS system on the same day it is settled.

  78. SECONDARY NAME - The name that individual taxpayers list in the second position of the Entity portion of the tax document or transaction. For IMF the primary name specified should relate to the first SSN indicated; the secondary name relates to the second SSN indicated. A secondary name may be the spouse's name, a maiden name, or a hyphenated maiden and spouse name. The name must be the same as on record at the Social Security Administration.

  79. SECONDARY TAX IDENTIFICATION NUMBER - The Social Security Number (SSN) related to the secondary name.

  80. SEQUENCE NUMBER - An internal work field used to store selected settlement date groups.

  81. SETTLEMENT DATE - The day on which settlement occurs, i.e., funds actually change hands as a result of an ACH entry. In EFTPS, this is the day money moves to Treasury's Account. See Deposit Ticket Settlement Date for specifics on value.

  82. SINGLE DEBIT - The EFTPS Single Debit application is designed to enable trust banks and other providers to initiate a single ACH debit funds transfer for a file of up to 1,000 payment records. Single Debit payments are identified by a "6" in the third position of the EFT number, with the exception of SITLP payments, which are identified by a "1" .

  83. SOCIAL SECURITY ADMINISTRATION LEVY PROGRAM (SSA LEVY) - Social Security payments that are levied due to Federal obligations owed. Identified by an EFT number beginning with 491.

  84. STRUCTURED QUERY - A program developed by the EFPPS systems administrator to allow recurring ad hoc reports to be generated from the Reports menu.

  85. SUBMISSION PROCESSING CAMPUS - One of five (Austin, Cincinnati, Fresno, Kansas City, Ogden) IRS installations that process tax returns and related documents through the use of automated and manual data processing systems.

  86. SWIFT - Society for Worldwide Interbank Financial Telecommunication. An organization guiding international financial telecommunications (payments and payment instructions).

  87. TAX CLASS - Denotes the type of tax by broad category, as accumulated on the deposit ticket or debit voucher. The tax class is derived from the tax type code for each EFPPS payment:

    Tax Class RRACS Account # Description
    1 2110 Withholding and social security
    2 2120 Individual income or fiduciary
    3 2130 Corporate income
    4 2140 Excise
    5 2150 Estate and gift
    7 2170 Railroad retirement
    8 2180 Unemployment
    9 7001 Miscellaneous (not a revenue receipts tax class)
  88. TAXPAYER IDENTIFICATION NUMBER (TIN) - A unique nine digit identifier issued by IRS for business taxpayers (EIN) and by social security number for individual taxpayers (SSN).

  89. TAX PERIOD - The month and year in which the length of liability ends for a particular return or payment transaction. For Form 2290, Heavy Highway Vehicle Use Tax Return, the tax period is the beginning month of liability. For Form 706, U.S. Estate Tax Return, the tax period is 000000. The tax period cannot be later than the current year/month plus one year.

  90. TAX TYPE - Denotes the type of tax by specific category (such as Employer Quarterly Federal Income - 941, etc.)

  91. TAX TYPE CODE - A five (5) digit code used to indicate the tax type of the payment. This code is translated by the EFPPS TEP program into the MFT and transaction code for processing to Master File. See Exhibit 3.17.277-1.

  92. THRESHOLD AMOUNT - A payment maximum amount set either by the taxpayer or the FA's system. An amount over the set threshold will generate an automatic validation or reject condition before the payment is processed.

  93. TRANSACTION AMOUNT - The amount of a tax payment. The record received from the financial agent contains a 13 digit numeric with the last two digits for the cents. No decimal point is used to separate dollars and cents and no commas are used to separate dollars. If less than 13 digits, it should carry leading zeros for the field. Thirteen digits are required to accommodate FTCS; ACH transactions will never have more than 10 significant digits.

  94. TRANSACTION DATE - The date the EFT transaction is credited to the taxpayer's IRS account.

    1. This date is the same as the settlement date, except for credit or debit card payments, or if the financial agent or banking system has failed to process the transaction timely.

    2. On payments, the transaction date always matches the Payment Date from the incoming record.

    3. For returns and reversals, the transaction date matches the Original Payment Date.

  95. TRANSMISSION DATE - The date the data file is transmitted to the IRS.

  96. TRANSACTION INDICATOR - An indicator that denotes the type of transaction:

    Indicator Description
    0 Payment
    1 Return, Taxpayer error
    4 Return, non-taxpayer error
    8 Unidentified payment
    9 Unidentified return
    A Payment offset
    B Return offset
    R Credit reversal
  97. TRANSMISSION NUMBER - A two digit sequential number indicating the number of transmissions in a day.

  98. TREASURY INVESTMENT PROGRAM (TIP) - The centralized TTL application that collects and reports tax payments remitted and invests Treasury funds with participating FIs.

  99. TREASURY OFFSET PROGRAM - Program operated by Fiscal Service to offset payments made by a Federal agency to pay debts due to another Federal or state agency.

  100. TREASURY TAX and LOAN (TTL) - An account for Federal Taxes deposited with the Federal Reserve.

  101. UNIDENTIFIED PAYMENT - A transaction that does not contain entity information to post to a taxpayer's account. In EFPPSok , an Unidentified payment (transaction indicator "8" ) is moved to Suspense to await an offsetting transaction that must be sent by the financial agent.

  102. UNRESOLVED ELEMENT - An element of the EFT transaction identified as being incorrect or erroneous and must be manually corrected before the transaction can be posted to the taxpayer's account.

    Element Description
    1 Taxpayer Identification Number (EIN or SSN)
    2 Name Control
    3 Tax Period
    4 Payment Date
    5 Origination Date
    6 Status
    8 Tax Type
    9 FUTA
    10 Original Payment Date
    11 Credit Reversal
  103. VOUCHER DATE - An eight digit date assigned to each deposit ticket or debit voucher, which is the day the IRS is credited with the deposit.

  104. WAREHOUSING - The feature of ACH debit option payments that allows the taxpayer to enter the payment instructions up to 120 days prior to the payment date for businesses, 365 days for individuals.

  105. ZIP CODE - A 5 digit number related to the taxpayer's Post Office.

Form Number Table

Form Number Master File Type Tax Class MFT Code Valid Months Valid Payment Types Tax Type Codes
11-C 2 4 63 01–12 With Return
Subsequent
01111
01117
Also (see note d) : 01110, 01113, 01114, 01118, 01119, 0111B, 0111K
706 and 706NA


4768
2 5 52 00 With Return
Estimated
Subsequent
Extension
07061
07066
07067
07067
Also (see note d) : 07060, 07063, 07064, 07068, 07069, 0706B
706A, 706B, 706QDT 6 5 53 01–12 With Return
Subsequent
70611
70617
Also (see note d) : 70610, 70612, 70613, 70614, 70618, 70619, 7061B
706GS(D)

7004*
2 5 78 12 With Return
Extension
Subsequent
70621
70622
70627
Also (see note d) : 70623, 70624, 70628, 70629, 7062B
706GS(T)

7004*
2 5 77 12 With Return
Extension
Subsequent
70631
70632
70637
Also (see note d) : 70633, 70634, 70638, 70639, 7063B
709, 709A


8892 (used if extending F709 only)
2 5 51 12 With Return
Subsequent
Estimated
Extension
Extension (credit card)
07091
07097
07096
07097
07092
Also (see note d) : 07090, 07093, 07094, 07098, 07099, 0709B
720 2 4 03 03,06,09,12


08
With Return
Deposit
Subsequent
BPDF
72001
72005
72007
7200D
Also (see note d) : 72000, 72003, 72004, 72008, 72009, 7200B, 7200K
730 2 4 64 01–12 With Return
Subsequent
07301
07307
Also (see note d) :07303, 07304, 07308, 07309, 0730B, 0730K
926 6 4 81 12 With Return
Subsequent
09261
09267
Also (see note d) : 09263, 09264, 09268, 09269, 0926B
940 (Includes 940EZ,PR,V,and VEZ)


4666*,4667
2 8 10 12 With Return
Deposit
Subsequent
Advance
09401
09405
09407
09404
Also (see note d) : 09400, 09403, 09408, 09409, 0940B, 0940K
941 (Incl. 941E,PR,SS,and V)

941M,4219
4666*,4668*
CP251,CP252
2 1 01 03,06,09,12 With Return
Deposit
Subsequent
Advance
Amended
94101
94105
94107
94104
94100
Also (see note d) : 94103, 94108, 94109, 9410B, 9410K
943 (includes 943PR, SS, V)

4668*
2 1 11 12 With return
Deposit
Subsequent
Advance
09431
09435
09437
09434
Also (see note d) : 09430, 09433, 09438, 09439, 0943B, 0943K
944 2 1 14 12 With return
Deposit
Subsequent
Advance
Amended
94401
94405
94407
94404
94400
Also (see note d): 94403, 94408, 94409, 9440B, 9440K
945


CP543
2 1 16 12 With return
Deposit
Subsequent
Amended
09451
09455
09457
09450
Also (see note d) : 09453, 09454, 09458, 09459, 0945B, 0945K
990 990EZ 2 4 67 01–12
FY month
With return
Subsequent
09901
09907
Also (see note d) : 09900, 09903, 09904, 09908, 09909, 0990B
990–BL 6 4 56 01–12
FY month
With return
Subsequent
99011
99017
Also (see note d) : 99012, 99013, 99014, 99018, 99019, 9901B
990–C


7004*
2 3 33 01–12
FY month
Subsequent

Extension
With return
Estimated
99027

99022
99021
99026
Also (see note d) : 99020, 99023, 99024, 99028, 99029, 9902B
990–PF 2 4 44 01–12
FY month
With return
Estimated
Subsequent
Extension
99031
99036
99037
99032
Also (see note d) : 99030, 99033, 99034, 99038, 99039, 9903B
990–T



2758*,7004*
2 3 34 01–12
FY month
With return
Estimated
Subsequent
Extension
99041
99046
99047
99042
Also (see note d) : 99040, 99043, 99044, 99048, 99049, 9904B
1040 (A,C,EZ,NR,PC,PR,SS,TEL,V) 1 2 30 12
(or FY month)
With return
Subsequent
AKPFD
SITLP
MTLP
10401
10407
1040K
1040L
1040M
Also (see note d): 10403, 10408, 10409, 1040B
1040 ES Estimated 10406
4868* (credit card & Direct Pay) Extension 10402
4868*, 2688*, 2210*, 2350*, 2555, 8453, 9282, CP45 Subsequent 10407
CP2000, CP2501, EUR CP2000 Advance 10404
1040X, 1040X-V, 2031, 8082, 8379, 8615 Amended 10400
1040 Separate Assessment 1 2 31 12 (or FY month) Subsequent
AKPFD
SITLP
MTLP
10317
1031K
1031L
1031M
Also (see note d): 10311, 10313, 10314, 10316, 10318, 10319, 10310, 1031B
1040 Non Master File NMF Notice (3967, 4839, 4840, 6335) 6 2 20 01–12 Subsequent 01047
Also (see note d): 01043, 01044, 01048, 01049, 0104B
1040 1 2 35 12 (2014)
01-12 (2015 & subsequent)
Amended
Advance
Subsequent
50000
50004
50007
1041
2210*, 7004*
1041ES
2 2 05 01–12
FY month
With return
Subsequent
Estimated
Extension
10411
10417
10416
10412
Also (see note d): 10410, 10413, 10414, 10418, 10419, 1041B
1041A 2 4 36 01–12
FY month
With return
Subsequent
Amended
14111
14117
14112
Also (see note d): 14110, 14113, 14114, 14118, 14119, 1411B
1042 2 1 12 12 With return
Extension
Deposit
Subsequent
10421
10422
10425
10427
Also (see note d): 10420, 10423, 10424, 10428, 10429, 1042B
1065
7004*
2 2 06 01–12
FY month

Subsequent
Estimated
Extension

10657
10656
10652
Also (see note d): 10650, 10651, 10653, 10654, 10658, 10659, 1065B, 1065K
1066 (Includes 7004*) 2 3 07 01–12 Subsequent 10667
Also (see note d): 10660, 10662, 10663, 10664, 10668, 10669, 1066B
1120 (A,C,DF,F,FSC,H,L,ND,PC,POL,REIT,RIC,S, SF)
2220
7004*
1120X
2 3 02 01–12
FY month
With return
Estimated
Subsequent
Subsequent
Extension
Amended
11201
11206
11207
11207
11202
11200
Also (see note d): 11203, 11204, 11208, 11209, 1120B
1120 DISC IC DISC 6 3 23 01–12
FY month
With return
Subsequent
11211
11217
Also (see note d): 11210, 11213, 11214, 11218, 11219, 1121B
2290 2290V 2 4 60 01–12 With return
Subsequent
22901
22907
Also (see note d): 22900, 22903, 22904, 22908, 22909, 2290B, 2290K
2438 6 3 38 12 With return
Subsequent
24381
24387
Also (see note d): 24380, 24383, 24384, 24388, 24389, 2438B
4720 2 4 50 01–12 With return
Subsequent
47201
47207
Also (see note d): 47200, 47202,47203, 47204, 47208, 47209, 4720B
4980 2 4 43 12 Amended
Advance
Subsequent
49800
49804
49807
5227 2 4 37 01–12
FY month
With return
Subsequent
52271
52277
Also (see note d): 52270, 52272, 52273, 52274, 52278, 52279, 5227B
5329 1 4 (DLN tax class 0) 29 01–12
FY month
Subsequent
AKPFD
SITLP
MTLP
53297
5329K
5329L
5329M
Also (see note d): 53290, 53293, 53294, 53298, 53299, 5329B
6069 6 4 57 12 With return
subsequent
60691
60697
Also (see note d): 60690, 60692, 60693, 60694, 60698, 60699, 6069B
8038–T, G, GC, Q Assign Report/Plan Number 700 2 3 46 01–12 With return
subsequent
80381
80387
Also (see note d): 80383, 80384, 80388, 80389, 8038B
8288 2 1 17 01–12 With return
subsequent
82881
82887
Also (see note d): 82883, 82884, 82888, 82889, 8288B, 8288K
8404 6 3 23 01–12 With return
subsequent
84041
84047
Also (see note d): 84040, 84043, 84044, 84048, 84049, 8404B
8612 8831

7004*
6 4 89 01–12 With return
subsequent
86121
86127
Also (see note d): 86120, 86122, 86123, 86124, 86128, 86129, 8612B
8613

7004*
6 4 14 01–12 With return
subsequent
86131
86137
Also (see note d): 86130, 86132, 86133, 86134, 86138, 86139, 8613B
8697 6 3 69 01–12 With return
subsequent
86971
86977
Also (see note d): 86970, 86973, 86974, 86978, 86979, 8697B
8725

7004*
6 4 27 01–12 Subsequent 87257
Also (see note d): 87250, 87251, 87252, 87253, 87254, 87258, 87259, 8725B
8752 2 2 15 12 With return
Subsequent
87521
87527
Also (see note d): 87520, 87523, 87524, 87528, 87529, 8752B
8804, 8805, 8813 2 1 08 01–12 With return
Subsequent
88041
88047
Also (see note d): 88040, 88042, 88043, 88044, 88048, 88049, 8804B, 8804K
8876 6 4 27 01 - 12 Amended
With return
Extension
Estimated
Subsequent
88760
88761
88762
88766
88767
Also (see note d): 88763, 88764, 88768, 88769, 8876B
8963 (Insurance Provider Fee) 2 4 79 09 Subsequent 89637
CT-1 2 7 09 12 With return
Deposit
Subsequent
10001
10005
10007
Also (see note d): 10000, 10003, 10004, 10008, 10009, 1000B
CT-2 6 7 72 03,06,09,12 With return
Subsequent
00021
00027
Also (see note d): 00020, 00023, 00024, 00028, 00029, 0002B
Installment Agreement New 7 9 None None User Fee 54321
Installment Agreement Reinstated 54323
Enrolled Agent Increase 54324
Private Letter Ruling 58841
Photocopy Fees 68770
Public Debt (Account 20X5080) 7 9 None None Public Debt 05080
Conscience Fund (Account 20–1210) 7 9 None None Conscience Fund 01210
NMF Notice if tax form is shown on table with Master File 6: 6 See actual Form Number (XXXX = first 4 positions of Tax Type Code for tax form number.) Subsequent XXXX7
NMF Notice for other tax form number: 6 9 Subsequent 99997
Also (see note d): 99993, 99994, 99998, 99999, 9999B
Civil Penalty (8210, CP253, 1 SSN 2 55 01–12 Advance 84884
2 EIN 3 13 01–12 Advance 84894
Miscellaneous Penalties (CP215) 1 SSN 2 55 01–12 Subsequent 84887
1 SSN or 2 EIN 3 13 01–12 Subsequent 84897
Also: SSNs 84883, 84888, 84889, 8488B
EINs 84893, 84898, 84899, 8489B, 8489K
Miscellaneous Penalties (8278) 1 SSN 2 55 01 — 12 Subsequent
AKPFD
SITLP
MTLP
82787
8278K
8278L
8278M

Notes:

  1. * Forms which may be used for more than one tax form number. Payments received with these forms should also identify the tax form number.

  2. If "FY month" is listed in the "Valid Months" column, the MM portion of the tax period must match the fiscal year month on the Master File.

  3. Any user fee payment, such as a photocopy fee, installment agreement fee, fee for IRS publications, or special ruling fee is assigned Master File type 7 and tax class 9. No MFT code or transaction code is assigned. Account symbols (used by Accounting) are determined from the Tax Type Code.

  4. Payments identified by the taxpayer as any of the following are assigned the following codes:

    Payment Type Payment Code
    Payment with Amended Return XXXX0
    Payment with Return XXXX1
    Payment with Extension XXXX2
    Designated Payment of Fees and Collection Costs XXXX3
    Advance Payment of Determined Deficiency XXXX4
    Federal Tax Deposit XXXX5
    Estimated Tax Payment XXXX6
    Subsequent Payment XXXX7
    Designated Payment of Interest XXXX8
    Designated Payment of Penalty XXXX9
    IRC § 6603 Deposit (formerly Cash Bond) XXXXB
    Branded Prescription Drug Fee XXXXD
    Alaska Permanent Fund Dividend Program XXXXK
    State Income Tax Levy Program XXXXL
    Municipal Tax Levy Program XXXXM
    (XXXX = first 4 positions of Tax Type Code for actual tax form number)

Transaction Code Table

Last position of Tax Type Code Transaction Indicator
0 1 4 R
0 670 with secondary 570 671 672 672
1 610 611 612 612
2 (Form 1040 and Form 709) 670 with secondary 460 671 672 672
2 (Corporate Returns) 620 621 622 622
3 694 695 695 695
4 640 641 642 642
5 650 651 652 652
6 660 661 662 662
7 670 671 672 672
7 with DPC 63 or 71 670 with secondary 570 671 672 672
8 680 681 682 682
9 690 691 692 692
B 640 (blocking series 990–999) - Designated Payment Code 12 641 642 642
D 670 - Designated Payment Code 27 N/A 672 672
K 670 - Designated Payment Code 22 N/A 672 672
L 670 - Designated Payment Code 20 N/A 672 672

The Tax Type Code and Transaction Indicator are used to generate the Transaction Code for all payments that are sent to Master File.

Transaction Codes are not generated with Transaction Indicator 8, 9, A, or B, or Master File 6 or 7.

RS-PCC Taxpayer Assistance Centers

EFT Number 8th and 9th position Campus or TAC Site
Campus Support
520 00 Discovered Remits
520 01 PAMC Insolvency
520 02 PAMC Perfect
520 03 PAMC Imperfect
520 04 PAMC Field Office
520 05 BAMC Perfect
520 06 BAMC Imperfect
520 07 MAMC Perfect
520 08 MAMC Imperfect
520 09 BAMC OIC
520 10 MAMC OIC
520 11 ANAMC Perfect
520 12 ANAMC Imperfect
520 13 ATAMC Perfect
520 14 ATAMC Imperfect
520 15 Bulk AUSPC
520 16 Bulk CSPC
520 17 Bulk FSPC
520 18 Bulk KCSPC
520 19 Bulk OSPC
TAC's
521
521 00 CT- New Haven
521 01 CT- Hartford
521 02 NJ- Newark
521 03 MI- Detroit
521 04 MO- Kansas City
521 05 NC- Charlotte
521 06 PR- Guaynabo
521 07 TX- San Antonio
521 08 TX- Dallas
521 09 NV- Las Vegas
521 10 CA- San Francisco
521 11 CT- New London
521 12 CT- Danbury
521 13 CT- Waterbury
521 14 CT- Bridgeport
521 15 CT- Norwalk
521 16 DE- Dover
521 17 DE- Wilmington
521 18 MA- Boston JFK
521 19 MA- Springfield
521 20 MA- Brockton
521 21 MA- Stoneham
521 22 MA- Fitchburg
521 23 MA- Worcester
521 24 MA- Hyannis
521 25 MA- Quincy
521 26 MA- Pittsfield
521 27 ME- Augusta
521 28 ME- So. Portland
521 29 ME- Bangor
521 30 ME- Lewiston
521 31 ME- Presque Isle
521 32 NH- Nashua
521 33 NH- Portsmouth
521 34 NH- Manchester
521 35 NH- Keene
521 36 NJ- Trenton
521 37 NJ- Cherry Hill
521 38 NJ- Mountainside
521 39 NJ- Edison
521 40 NJ- Paterson
521 41 NJ- Jersey City
521 42 NJ- Mays Landing
521 43 NJ- Freehold
521 44 NJ- Fairfield
521 45 NJ- Paramus
521 46 NJ- Parsippany
521 47 NY- Brooklyn
521 48 NY- Rego Park
521 49 NY- Midtown
521 50 NY-Harlem
521 51 NY- Albany
521 52 NY- Syracuse
521 53 NY- Rochester
521 54 NY- Buffalo
521 55 NY- Hauppauge
521 56 NY- Garden City
521 57 NY-New York
521 58 NY- Bronx
521 59 NY- White Plains
521 60 NY-Queensbury
521 61 NY- Kingston
521 62 NY- Binghamton
521 63 NY- Utica
521 64 NY- Jamestown
521 65 NY- Elmira
521 66 NY- Riverhead
521 67 NY- Staten Island
521 68 NY- West Nyack
521 69 NY- New Windsor
521 70 NY- Poughkeepsie
521 71 PA- Philadelphia
521 72 PA- Pittsburgh
521 73 PA- Horsham
521 74 PA- Butler
521 75 PA- Warrendale
521 76 PA- Washington
521 77 PA- Monroeville
521 78 PA- Erie
521 79 PA- King of Prussia
521 80 PA- Media
521 81 PA- Scranton
521 82 PA- Wilkes-Barre
521 83 PA- Williamsport
521 84 PA- Bethlehem
521 85 PA- Altoona
521 86 PA-Johnstown
521 87 PA- State College
521 88 PA- Harrisburg
521 89 PA- Lancaster
521 90 PA- Reading
521 91 PA- York
521 92 RI- Providence
521 93 RI- Warwick
521 94 VT- Burlington
521 95 VT- Montpelier
521 96 VT- Rutland
521 97 VT- Brattleboro
521 98 AK- Anchorage
521 99 AK- Fairbanks
522
522 00 DC- Washington
522 01 DE- Georgetown
522 02 IL- Chicago
522 03 IL- Springfield
522 04 IL- Schiller Park
522 05 IL- Orland Park
522 06 IL- Decatur
522 07 IL- Quincy
522 08 IL- Mt. Vernon
522 09 IL- Champaign
522 10 IL- Galesburg
522 11 IL- Peoria
522 12 IL- Bloomington
522 13 IL- Rockford
522 14 IL- Downers Grove
522 15 IN- Indianapolis
522 16 IN- South Bend
522 17 IN- Merrillville
522 18 IN- Columbus
522 19 IN- Terre Haute
522 20 IN- Lafayette
522 21 IN-Evansville
522 22 IN- Muncie
522 23 IN- Fort Wayne
522 24 IN- Bloomington
522 25 KY- Louisville
522 26 KY- Prestonsburg
522 27 KY- Lexington
522 28 KY- Owensboro
522 29 KY- Hopkinsville
522 30 KY- Paducah
522 31 KY- Bowling Green
522 32 MD- Baltimore
522 33 MD- Wheaton
522 34 MD- Hagerstown
522 35 MD- LaVale
522 36 MD- Annapolis
522 37 MD- Salisbury
522 38 MD- Landover
522 39 MD- Frederick
522 40 MI- Grand Rapids
522 41 MI- Marquette
522 42 MI- Flint
522 43 MI- Traverse City
522 44 MI- Saginaw
522 45 NC- Wilmington
522 46 NC- Winston-Salem
522 47 NC- Greensboro
522 48 NC- Durham
522 49 NC- Greenville
522 50 NC- Raleigh
522 51 NC- Hickory
522 52 NC- Fayetteville
522 53 NC- Asheville
522 54 OH- West Chester
522 55 OH- Cincinnati
522 56 OH- Columbus
522 57 OH- Cleveland
522 58 OH-Dayton
522 59 OH- Akron
522 60 OH- Youngstown
522 61 OH- Canton
522 62 OH- Mansfield
522 63 OH- Toledo
522 64 OH- Lima
522 65 SC- Greenville
522 66 SC- Charleston
522 67 SC- Myrtle Beach
522 68 SC- Columbia
522 69 SC- Florence
522 70 VA- Richmond
522 71 VA- Norfolk
522 72 VA- Hampton
522 73 VA- Bailey's Crossroads
522 74 VA- Roanoke
522 75 VA- Fredericksburg
522 76 VA- Bristol
522 77 VA- Charlottesville
522 78 VA- Danville
522 79 VA- Staunton
522 80 VA- Lynchburg
522 81 WI- Milwaukee
522 82 WI- Appleton
522 83 WI- Green Bay
522 84 WI- Rothschild
522 85 WI- LaCrosse
522 86 WI- Eau Claire
522 87 WI- Madison
522 88 WV- Charleston
522 89 WV- Huntington
522 90 WV- Sophia
522 91 WV- Bridgeport
522 92 WV- Martinsburg
522 93 WV- Wheeling
522 94 WV- Parkersburg
522 95 AZ- Lake Havasu City
522 96 AZ- Bullhead City
522 97 CA- San Diego
522 98 CA- El Monte
522 99 CA- Los Angeles
523
523 00 AL- Birmingham
523 01 AL- Montgomery
523 02 AL- Mobile
523 03 AL- Dothan
523 04 AL- Florence
523 05 AL- Huntsville
523 06 AR- Little Rock
523 07 AR- Jonesboro
523 08 AR- Fayetteville
523 09 AR- Ft Smith
523 10 FL- Plantation
523 11 FL- Tampa
523 12 FL- Maitland
523 13 FL- Sarasota
523 14 FL- West Palm Beach
523 15 FL- Ocala
523 16 FL- Saint Petersburg
523 17 FL- Jacksonville
523 18 FL- Fort Myers
523 19 FL- Daytona
523 20 FL- Melbourne
523 21 FL- Port St. Lucie
523 22 FL- Panama City
523 23 FL- Pensacola
523 24 FL- Lakeland
523 25 FL- Gainesville
523 26 FL- Tallahassee
523 27 FL- Miami
523 28 GA- Atlanta
523 29 GA- Macon
523 30 GA- Columbus
523 31 GA- Koger Ctr
523 32 GA- Smyrna
523 33 GA- Athens
523 34 GA- Augusta
523 35 GA- Albany
523 36 GA- Gainesville
523 37 GA- Dalton
523 38 GA- Rome
523 39 GA- Savannah
523 40 IA- Des Moines
523 41 IA- Cedar Rapids
523 42 IA- Waterloo
523 43 IA- Davenport
523 44 IA- Fort Dodge
523 45 IL- Fairview Heights
523 46 LA- Baton Rouge
523 47 LA- New Orleans
523 48 LA- Monroe
523 49 LA- Alexandria
523 50 LA- Shreveport
523 51 LA- Lafayette
523 52 LA- Lake Charles
523 53 LA- Houma
523 54 MN- St. Paul
523 55 MN- Minneapolis
523 56 MN- Duluth
523 57 MN- St. Cloud
523 58 MN- Mankato
523 59 MN- Bloomington
523 60 MN- Rochester
523 61 MO- St. Louis
523 62 MO- Earth City
523 63 MO- Chesterfield
523 64 MO- Cape Girardeau
523 65 MO- Independence
523 66 MO- St. Joseph
523 67 MO- Jefferson City
523 68 MO- Joplin
523 69 MO- Springfield
523 70 MS- Jackson
523 71 MS- Clarksdale
523 72 MS- Gulfport
523 73 MS- Hattiesburg
523 74 MS- Tupelo
523 75 MS- Columbus
523 76 TN- Nashville
523 77 TN- Memphis
523 78 TN- Chattanooga
523 79 TN- Johnson City
523 80 TN- Jackson
523 81 TN- Knoxville
523 82 CA- Fresno
523 83 CA- Sacramento
523 84 CA- San Jose
523 85 CA- Oakland
523 86 CA- Santa Ana
523 87 CA- San Bernardino
523 88 CA- San Marcos
523 89 CA- Long Beach
523 90 CA- Bakersfield
523 91 CA- Modesto
523 92 CA- Santa Rosa
523 93 CA- Laguna Niguel
523 94 CA- Palm Springs
523 95 CA- Van Nuys
523 96 CA- Santa Barbara
523 97 CA- Santa Maria
523 98 CA- Camarillo
523 99 CA- Visalia
524
524 00 AZ- Phoenix
524 01 AZ- Tucson
524 02 AZ- Mesa
524 03 AZ- Glendale
524 04 AZ- Flagstaff
524 05 AZ- Prescott
524 06 AZ- Yuma
524 07 CA- El Centro
524 08 CO- Denver
524 09 CO- Ft. Collins
524 10 CO- Grand Junction
524 11 CO- Colorado Springs
524 12 IA- Sioux City
524 13 ID- Boise
524 14 ID- Idaho Falls
524 15 ID- Pocatello
524 16 KS- Wichita
524 17 KS- Overland Park
524 18 KS- Topeka
524 19 MT- Helena
524 20 MT- Kalispell
524 21 MT- Missoula
524 22 MT- Bozeman
524 23 MT- Great Falls
524 24 MT- Billings
524 25 ND- Fargo
524 26 ND- Grand Forks
524 27 ND- Bismarck
524 28 ND- Minot
524 29 NE- Omaha
524 30 NE- Scottsbluff
524 31 NE- Norfolk
524 32 NE- Lincoln
524 33 NE- North Platte
524 34 NM- Albuquerque
524 35 NM- Santa Fe
524 36 NM- Roswell
524 37 NM- Farmington
524 38 NM- Las Cruces
524 39 OK- Oklahoma Cty
524 40 OK- Tulsa
524 41 OK- Enid
524 42 OK- Lawton
524 43 SD- Sioux Falls
524 44 SD- Rapid City
524 45 SD- Aberdeen
524 46 TX- El Paso
524 47 TX- Ft. Worth
524 48 TX- Houston
524 49 TX- Houston NW
524 50 TX- Houston Leland
524 51 TX- Austin
524 52 TX- Harlingen
524 53 TX- Farmers Branch
524 54 TX- Lubbock
524 55 TX- Houston SE
524 56 TX- Corpus Christi
524 57 CA- Stockton
524 58 TX- Texarkana
524 59 TX- Longview
524 60 TX- Tyler
524 61 TX- Abilene
524 62 TX- Wichita Falls
524 63 TX- Amarillo
524 64 TX- Midland
524 65 TX- San Angelo
524 66 TX- Beaumont
524 67 TX- Waco
524 68 UT- Salt Lake City
524 69 UT- SLC Fed State
524 70 UT- Provo
524 71 UT- Ogden
524 72 WY- Casper
524 73 WY- Sheridan
524 74 WY- Cheyenne
524 75 CA- Salinas
524 76 CA- Walnut Creek
524 77 CA- Redding
524 78 CA- Chico
524 79 HI- Honolulu
524 80 HI- Hilo
524 81 HI- Wailuku
524 82 ID- Coeur d'Alene
524 83 NV- Reno
524 84 OR- Portland
524 85 OR- Salem
524 86 OR- Bend
524 87 OR- Eugene
524 88 OR- Medford
524 89 WA- Vancouver
524 90 WA- Silverdale
524 91 WA- Olympia
524 92 WA- Everett
524 93 WA- Bellevue
524 94 WA- Bellingham
524 95 WA- Richland
524 96 WA- Yakima
524 97 WA- Tacoma
524 98 WA- Spokane
524 99 WA- Seattle

Financial Agent Reject Report (CMS 1)

REPORT NO.: CMS 1 DATE: 06-10-2011
FINANCIAL AGENT REJECT REPORT
FA ID REJECT
CODE
TRANS/DT/BATCH
COUNT
BATCH
COUNT
ITEM
COUNT
AMOUNT DESCRIPTION
No rejects found for this reporting period
FA ID TOTAL FOR MONTH TOTAL FOR FISCAL YEAR
02 0 16
03 0 0
04 0 3
05 0 38
06 0 0
TOTAL 0 57
UNRESOLVED BATCH REJECTS
REJECT DATE BATCH NUMBER BATCH AMOUNT DT/DV NUMBER
NO UNRESOLVED BATCH REJECTS FOUND FOR THE CURRENT PERIOD

Electronic Reject/Offset Mismatch Report (CMS 2)

REPORT NO.: CMS 2 REPORT DATE: 06-10-2011
ELECTRONIC REJECT/OFFSET MISMATCH REPORT
FINANCIAL AGENT NO.: 02
TRANSACTION
INDICATOR
BATCH
NUMBER
EFT
NUMBER
EFT_TRANSACTION
AMOUNT
SETTLEMENT
DATE
9 0202579869 221065704123420 $-85.00 09/14/2010
9 0211540077 221155404123476 $-25.00 06/03/2011
9 0211570128 221155704123487 $-4,520.99 06/06/2011
9 0211570055 221155704123418 $-256.62 06/06/2011
9 0211590209 221155904123460 $-500.00 06/08/2011
9 0211590244 221155904123477 $-1,475.00 06/08/2011

Deleted Records List (CMS 3)

REPORT NO.: CMS 3 DATE: 10-25-2006
EFTPS DELETED RECORDS LIST
TIN N/C TAXPRD AMOUNT TAX TYPE PMTDATE BATCH NUMBER EFT NUMBER
000000 -$4,846.93 94105 10052006 0202790043 220027929123403
DFI NUM REFERENCE NUMBER ZIP MF ORIGIN SETTLE DT/DV NUM TRANS IND
122201222 210025941123483 2 10042000 10052006 076914 1
TIN N/C TAXPRD AMOUNT TAX TYPE PMTDATE BATCH NUMBER EFT NUMBER
000000 $4,846.93 94105 10052006 0202790059 220027937123403
DFI NUM REFERENCE NUMBER ZIP MF ORIGIN SETTLE DT/DV NUM TRANS IND
122201444 2 10052006 719361 0
Total Deleted Records 2
DEBIT AMOUNT CREDIT AMOUNT NET AMOUNT
-$4,846.93 $4,846.93 $0.00

Bulk Provider Payment Report (CMS 5)

REPORT NO.: CMS 5 DATE: 06-07-2011
BULK PROVIDER PAYMENT REPORT
MONTH OF MAY 2011
FA 02 BULK PROVIDER 01, ADP
PAYMENT COUNT 1,077,391
PERCENT OF EFTPS TOTAL 10.18%
PAYMENT AMOUNT $41,976,420,759.33
PERCENT OF EFTPS TOTAL 27.60%
AUTOCORRECTED COUNT 1,238
AUTOCORRECTED PERCENT 0.11%
ERROR COUNT 571
ERROR PERCENT 0.05%
DEBIT COUNT 1,016,254
DEBIT AMOUNT $9,524,094,652.91
CREDIT COUNT 0
CREDIT AMOUNT $.00
SAME DAY COUNT 61,137
SAME DAY AMOUNT $32,452,326,106.42
UNENROLLED COUNT 9
UNENROLLED ERROR COUNT 0
UNENROLLED ERROR PERCENT 0.00%
CURRENT ERROR COUNT 79
OLDEST ERROR (DAYS) 76
RETURNED/REVERSED COUNT 0
RETURNED/REVERSED AMOUNT $.00
Page 1

Daily Tax Class Receipts Report (CMS 7)

REPORT NO: CMS 7 DATE: 06-10-2011
DAILY TAX CLASS RECEIPTS REPORT
PART 1 - PAYMENTS
FINANCIAL AGENT ID: 02
VOLUME AMOUNT
TAX CLASS 1
CURRENT DATE 296,387 $5,925,007,884.28
MONTH 2,964,555 $52,629,189,869.15
FISCAL YEAR 66,894,899 $1,217,062,336,222.98
TAX CLASS 2
CURRENT DATE 39,765 $86,713,302.26
MONTH 284,270 $320, 114,748.92
FISCAL YEAR 11,298,867 $25,623,525,878.23
TAX CLASS 3
CURRENT DATE 6,326 $389,090,588.34
MONTH 25,380 $908,664,544.96
FISCAL YEAR 556,116 $161,617,862,959.99
TAX CLASS 4
CURRENT DATE 2,502 $504,230,237.67
MONTH 8,704 $624,545,338.02
FISCAL YEAR 198,302 $30,468,034,295.23
TAX CLASS 5
CURRENT DATE 3 $1,053.18
MONTH 9 $3,720.51
FISCAL YEAR 374 $1,567,721,402.50
TAX CLASS 7
CURRENT DATE 122 $48,305,140.63
MONTH 1,015 $112,416,768.60
FISCAL YEAR 22,058 $3,342,297,657.44
TAX CLASS 8
CURRENT DATE 7,444 $1,223,783.45
MONTH 60,632 $12,424,287.37
FISCAL YEAR 7,144,655 $5,596,972,402.52
TAX CLASS 9
CURRENT DATE 87 $4,941,966.20
MONTH 577 $35,339,801.27
FISCAL YEAR 29,566 $2,056,867,160.91
TOTAL
CURRENT DATE 352,636 $6,959,513,956.01
MONTH 3,345,142 $54,642,699,078.80
FISCAL YEAR 86,135,837 $1,447,335,617,979.80
PAGE # 1

EFTPS Deposit Ticket (CMS 9)

REPORT NO.: CMS 9 PROCESS DATE: 06-10-2011
EFTPS DEPOSIT TICKET PAGE # 39
DEPOSIT TICKET NUMBER: 801057
ROUTING TRANSIT NUMBER: 071036210
SETTLEMENT DATE: 10-JUN-2011
AGENCY LOCATION CODE: 20092900
DEPOSIT AMOUNT: $227,856,079.74
TAX CLASS 1 AMOUNT: $165,682,413.57 SUSPENSE ACCOUNTS:
TAX CLASS 2 AMOUNT: $0.00 IMF: $0.00
TAX CLASS 3 AMOUNT: $501,400.00 BMF: $227,824,830.34
TAX CLASS 4 AMOUNT: $24,339,600.27 NMF: $5,339.32
TAX CLASS 5 AMOUNT: $0.00 MISC: $25,910.08
TAX CLASS 7 AMOUNT: $37,278,850.88
TAX CLASS 8 AMOUNT: $27,904.94
TAX CLASS 9 AMOUNT: $0.00