Control No. 1505-0080
CONTRACT ID CODE PAGE OF PAGES
AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT 1 48
2. AMENDMENT/MODIFICATION NO. 3. EFFECTIVE. DATE
0001 See Block 16C
4. REQIIISITION/PIIRCHASE REQ. NO. 5. PROJECT NO (If applicable)
W-6-W2-03-TP-R03 005
6 ISSUED) BY CODE IRS0088
Internal Revenue Service
6009 Oxon Hill Road, Suite 500
Oxon Hill, MD 20745
7. ADMINISTERED BY (If other than Item 6) CODE
See Item 6
8. NAME AND ADDRESS OF CONTRACTOR No. Street. county State and ZIP: Code)
OFFICIAL PAYMENTS CORPORATION 00051397
2333 SAN RAMON VALLEY BOULEVARD STE# 450
SAN RAMON, CA 945834456
OFFICIAL PAYMENTS CORPORATION
10A. AMENDMENT OF SOLICITATION NO
10B DATED (SEE ITEM II)
x
10A. MODIFICATION OF CONTRACT/OROISR NI) TIRNO-09-C-tJOOl 9
10B. DATFI) (SEE ITE3I 13,1 04/23/2009
CODE            FACULTY CODE
[]. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS
The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for
receipt of Offers []is extended, [] is not extended Offers
must acknowledge receipt of Ibis amendment prior 10 the hour and dale specified in the
solicitation or as intended, by one of the following methods:
(a) By completing Items 8 md 15, and returning copies of the amendment; (b) By acknowledging
receipt of this amendment on each copy of the offer submitted; or(c) By separate letter or telegram
which includes a reference to the solicitation and amendment numbers.
FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATEI) FOR THE RECEIPT OF
OFFERS PRIOR TO THE HOUR AND DATA SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of
this amendment you desire to change an offer already submitted, such change may he made by telegram
or letter, provided each Telegram or letter makes reference to the solicitation and this amendment,
and is received prior to the opening hour and damn specified.
12. ACCOUNTING AND APPROPRTION DATA f required)
None Net Increase: $0.00
13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS
IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED EN ITEM 14.
[X]
A.
THISC CHANGE ORDER ISISSUED PURSUANT TO (Specify authority/ THE HANGES SFT FOR 14 ARE MADE IN
THE CONTRACT ORDRER NO IN ITEM I0A
B
THE AISOVE NUMBER CONTRACT ORDER IS MODIFIED TO REFLECT ADMINISTRATIVE CHANGES (SUCH AS CHANGES
IN PAYING OFFER ,ETC) SET FORTH IN ITIM 14)PURSUANT TO THE AUTHORITY OF FAR 43.103(B)
C.THE SUPPLEMENTAL AGREEMENT IS ENTERED 1410 PIIRSIJANE TO AIITIIORI1 V OF
D
OTHER Specify type of modification and authority) Mutual Agreement Between The Parties
F.
IMPORTANT: Contractor is not, E is required to sign this document and return copies to the issuing
office.
4. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF.section headings. including
        ,solicitation /contract subject matter where feasible.) The purpose of this Modification is as
follows:
l6A. NAME AND TITI.I/ OF CONTRACTING OFFICFR (Type or print)
DIANNE L GOOSBY 202-283-1207 / CONTRACT SPECIALIST
STANDARD FORM 30 (REV. 10-83)
Except at provided herein, all Icons and conditions of the document referemmced in them 9A or 10A,
as heretofore changed. renmain unchanged and in fall force and effect.
I5A. NAME AND TITlE OF SIGNER (Type or print)
16B NAME AND TITLE OF CONTRACTING OFFER (type or print)
DIANNEL L GOOSBY 202-283-1207/ CONTRACT SPECILIST
15B CONTRACTOR/OFFICER
15C DATED SIGNED 10/27/09
16B. UNITED STATES OF AMERICA
BY (signature of contracting officer)
16C. DATED SIGNED
10-32009
30-105
Computer Generated
STANDARD FORM 30 (REV.10-83)
Prescribed by GSA
FAR (48 CFR) 53.243




---



##### 



1.
    
    The convenience fee for Option Years One (1) through four (4) are changed From 2.39%
to 2.35% (CLINS  Convenience Fee  1026, 2026, 3026, and 4026) with a $3.95 minimum
fee.2.
    
    Add CLINS 1027, 2027, 3027, and 4027 entitled: Debit Card
Flat Fee  fixed with
a price of $3.95.3.
    
    Add under C.10 Schedule of Performance, to read as follows:IRS Final Sign Off on Functional Requirements/User Interface
Documentation  08/21/2009.4.
    
    The
9th
Contractors event to read as follows: Deliver Final Test Plans
And Test Cases  08/31/2009.5.
    
    The 10th Contractors event to read as follows: Begin internal
application Testing  09/07/2009.6.
    
    Section 2.3 is hereby changed as follows:Natalie Boston
Internal Revenue Service
SE:W:CAS:SP:ATP:EP
5000 Ellin Road C8-437
New Carrollton, MD 207067.
    
    Section C.1.5  Contract Requirements are hereby included in the contract.8.
    
    Section 2.3 is hereby changed effective 01/01/2010 as follows:
Steve Greenspan will be the Project Manger.9.
    
    All other terms and conditions remain unchanged.
 Page - 2




---



##### 



TABLE OF CONTENTS
    PAGE NOS.1. SF 1449 FORM
    
    
    1 - 22. ATTACHMENT 1, SUPPLIES OR SERVICES AND
PRICES/COSTS
    
    
    5 - 82.1
    
    NO-COST, FIXED CONVENIENCE FEE RATE CONTRACT52.2
    
    CONTRACT PRICING (CONVENIENCE FEE)
    
    
    52.2.1 BASE PERIOD
    
    
    52.2.2 OPTION PERIOD 1
    
    
    62.2.3 OPTION PERIOD 2
    
    
    62.2.4 OPTION PERIOD 3
    
    
    72.2.5 OPTION PERIOD 4
    
    
    82.3
    
    AUTHORITY  CONTRACTING
OFFICER, CONTRACTING OFFICERS TECHNICAL REPRESENTATIVE AND
CONTRACTORS PROJECT MANAGER
    
    
    92.4
    
    PERIOD OF PERFORMANCE
    
    
    102.5
    
    PREPARATION FOR DELIVERY
    
    
    102.6
    
    MARKING OF SHIPMENTS
    
    
    103. CLAUSES
    
    
    11 - 24
 FAR 52.252-2 CLAUSES INCORPORTATED BY REFERENCE52.203-6
    
    Restrictions on Subcontractor Sales
to the Government (ALT 1) (FEB 2007)52.204-4
    
    Printed or Copied Double-Sided on
On Recycled Paper (AUG 2000)52.212-4
    
    Contract Terms and Conditions (FEB 2007)52.233-4
    
    Applicable Law for Breach of
Contract Claim (OCT 2004)FAR 52.212-5 CONTRACT TERMS & CONDITIONS REQUIRED TO IMPLEMENT STATUTES OR EXECUTIVE
 Page - 3




---



##### 



TABLE OF CONTENTS

PAGE NOS.ORDERS  COMMERCIAL ITEMSFAR 52.216-1 CONTRACT TYPEFAR 52.217-8 OPTION TO EXTEND SERVICESFAR 52.217-9 OPTION TO EXTEND THE TERM
OF THE CONTRACTFAR 52.237-3 CONTINUITY OF SERVICESFAR 52.227-19 COMMERCIAL COMPUTER SOFTWARE 
RESTRICTED RIGHTSFAR 52.232-33 PAYMENT BY ELECTRONIC
FUNDS TRANSFER  CENTRAL CONTRACTOR REGISTRATION1052.204-9003 INFORMATION SECURITY TRAINING REQUIREMENT1052.224-9000a DISCLOSURE OF INFORMATION-SAFEGUARDS1052.224-9000(d) DISCLOSURE OF
SENSITIVE  BUT UNCLASSIFIED INFORMATION SAFEGUARDS1052.224-9001(a) DISCLOSURE OF INFORMATION  CRIMINAL/CIVIL SANCTIONS1052.224-9001(b) DISCLOSURE OF INFORMATION  SENSITIVE BUT UNCLASSIFIED
USE ONLY1052-204-9003 INFORMATION SECURITY TRAINING REQUIREMENTS1052.224-9002 DISCLOSURE OF INFORMATION  INSPECTION
 ATTACHMENTS1. SUPPLIES/SERVICES AND PRICES/COSTS, ATTACHMENT 1
(SEE SECTION 2)
    
    
    5 - 82. SECTION C, ATTACHMENT 2
    
    
    25 - 473. APPENDIX A through C, ATTACHMENT 3
    
    
    48
 Page - 4




---



##### 



ATTACHMENT 1
 2. SUPPLIES OR SERVICES AND PRICES/COSTS
 2.1 NO COST, FIXED CONVENIENCE FEE RATE
  2.2 CONTRACT PRICING (CONVENIENCE FEE)
2.2.1 BASE PERIOD  (April 2, 2009 through December 31, 2009)
  CLIN DESCRIPTION
    
    PRICE0001 Electronic Payments
    
    $
    00002 Monthly Development Status Reports
    
    $
    00003 Daily Transaction Reports
    
    $
    00004 Monthly Transaction Reports
    
    $
    00005 Chargeback Reports
    
    $
    00006 Exception Handling Reports
    
    $
    00007 Ad Hoc Reports
    
    $
    00008 Findings Reports
    
    $
    00009 Marketing Reports
    
    $
    00010 Capacity Analysis
    
    $
    00011 System Security Plan
    
    $
    00012 Security Features Users Guide
    
    $
    00013 Configuration Management Plan
    
    $
    00014 Risk Assessment Plan
    
    $
    00015 Disaster Recovery Plan
    
    $
    00016 Network Design and Architecture Schematic
    
    $
    00017 Trusted Facilities Manual
    
    $
    00018 Process and Data Flow Schematic
    
    $
    00019 Funds Settlement Timeline
    
    $
    00020 System Development Life Cycle Plan
    
    $
    00021 Test Plans, Test Cases and Test Results
    
    $
    00022 Functional Requirements/User Interface Documentation
    
    $
    00023 Scripts/Call Flows/Screen Shots/Business Rules
    
    $
    00024 Work Breakdown Structure/Schedule
    
    $
    00025 Incident Reports
    
    $
    00026 Convenience Fee  Fixed
    
    $
    0TOTAL NO COST, FIXED PRICE
    
    $
    0
 Page - 5




---



##### 



2.2.2 OPTION 1  (January 1, 2010 through December 31, 2010 )
 CLIN DESCRIPTION
    
    PRICE1001 Electronic Payments
    
    $
    01002 Monthly Development Status Reports
    
    $
    01003 Daily Transaction Reports
    
    $
    01004 Monthly Transaction Reports
    
    $
    01005 Chargeback Reports
    
    $
    01006 Exception Handling Reports
    
    $
    01007 Ad Hoc Reports
    
    $
    01008 Findings Reports
    
    $
    01009 Marketing Reports
    
    $
    01010 1001 Capacity Analysis
    
    $
    01011 System Security Plan
    
    $
    01012 Security Features Users Guide
    
    $
    01013 Configuration Management Plan
    
    $
    01014 Risk Assessment Plan
    
    $
    01015 Disaster Recovery Plan
    
    $
    01016 Network Design and Architecture Schematic
    
    $
    01017 Trusted Facilities Manual
    
    $
    01018 Process and Data Flow Schematic
    
    $
    01019 Funds Settlement Timeline
    
    $
    01020 System Development Life Cycle Plan
    
    $
    01021 Test Plans, Test Cases and Test Results
    
    $
    01022 Functional Requirements/User Interface Documentation
    
    $
    01023 Scripts/Call Flows/Screen Shots/Business Rules
    
    $
    01024 Work Breakdown Structure/Schedule
    
    $
    01025 Incident Reports
    
    $
    01026 Convenience Fee  Fixed
    
    
    2.35
    %**(There is a $3.95 minimum fee)1027 Debit Card Flat Fee  Fixed
    
    $
    3.95TOTAL FIXED PRICE
    
    $
    0
 2.2.3 OPTION 2  (January 1, 2011 through December 31, 2011)
 CLIN DESCRIPTION
    
    PRICE2001 Electronic Payments
    
    $
    02002 Monthly Development Status Reports
    
    $
    02003 Daily Transaction Reports
    
    $
    02004 Monthly Transaction Reports
    
    $
    02005 Chargeback Reports
    
    $
    02006 Exception Handling Reports
    
    $
    0
 Page - 6




---



##### 



2007 Ad Hoc Reports
    
    $
    02008 Findings Reports
    
    $
    02009 Marketing Reports
    
    $
    02010 Capacity Analysis
    
    $
    02011 System Security Plan
    
    $
    02012 Security Features Users Guide
    
    $
    02013 Configuration Management Plan
    
    $
    02014 Risk Assessment Plan
    
    $
    02015 Disaster Recovery Plan
    
    $
    02016 Network Design and Architecture Schematic
    
    $
    02017 Trusted Facilities Manual
    
    $
    02018 Process and Data Flow Schematic
    
    $
    02019 Funds Settlement Timeline
    
    $
    02020 System Development Life Cycle Plan
    
    $
    02021 Test Plans, Test Cases and Test Results
    
    $
    02022
Functional Requirements/User Interface Documentation
    
    $
    02023 Scripts/Call Flows/Screen Shots/Business Rules
    
    $
    02024 Work Breakdown Structure/Schedule
    
    $
    02025 Incident Reports
    
    $
    02026 Convenience Fee  Fixed
    
    
    2.35
    %**(There is a $3.95 minimum fee)2027 Debit Card Flat Fee  Fixed
    
    $
    3.95TOTAL FIRM FIXED PRICE
    
    $
    0
 2.2.4 OPTION 3  (January 1, 2012 through December 31, 2012)
 CLIN DESCRIPTION
    
    PRICE3001 Electronic Payments
    
    $
    03002 Monthly Development Status Reports
    
    $
    03003 Daily Transaction Reports
    
    $
    03004 Monthly Transaction Reports
    
    $
    03005 Chargeback Reports
    
    $
    03006 Exception Handling Reports
    
    $
    03007 Ad Hoc Reports
    
    $
    03008 Findings Reports
    
    $
    03009 Marketing Reports
    
    $
    03010 Capacity Analysis
    
    $
    03011 System Security Plan
    
    $
    03012 Security Features Users Guide
    
    $
    03013 Configuration Management Plan
    
    $
    03014 Risk Assessment Plan
    
    $
    03015 Disaster Recovery Plan
    
    $
    03016 Network Design and Architecture Schematic
    
    $
    03017 Trusted Facilities Manual
    
    $
    03018 Process and Data Flow Schematic
    
    $
    03019 Funds Settlement Timeline
    
    $
    03020 System Development Life Cycle Plan
    
    $
    0
 Page - 7




---



##### 



3021 Test Plans, Test Cases and Test Results
    
    $
    03022 Functional Requirements/User Interface Documentation
    
    $
    03023 Scripts/Call Flows/Screen Shots/Business Rules
    
    $
    03024 Work Breakdown Structure/Schedule
    
    $
    03025 Incident Reports
    
    $
    03026 Convenience Fee  Fixed
    
    
    2.35
    %**(There is a $3.95 minimum fee)3027 Debit Card Flat Fee  Fixed
    
    $
    3.95TOTAL FIXED PRICE
    
    $
    0
 2.2.5 OPTION 4  (January 1, 2013 through December 31, 2013)
 CLIN DESCRIPTION
    
    PRICE4001 Electronic Payments
    
    $
    04002 Monthly Development Status Reports
    
    $
    04003 Daily Transaction Reports
    
    $
    04004 Monthly Transaction Reports
    
    $
    04005 Chargeback Reports
    
    $
    04006 Exception Handling Reports
    
    $
    04007 Ad Hoc Reports
    
    $
    04008 Findings Reports
    
    $
    04009 Marketing Reports
    
    $
    04010 Capacity Analysis
    
    $
    04011 System Security Plan
    
    $
    04012 Security Features Users Guide
    
    $
    04013 Configuration Management Plan
    
    $
    04014 Risk Assessment Plan
    
    $
    04015 Disaster Recovery Plan
    
    $
    04016 Network Design and Architecture Schematic
    
    $
    04017 Trusted Facilities Manual
    
    $
    04018 Process and Data Flow Schematic
    
    $
    04019 Funds Settlement Timeline
    
    $
    04020 System Development Life Cycle Plan
    
    $
    04021 Test Plans, Test Cases and Test Results
    
    $
    04022 Functional Requirements/User Interface Documentation
    
    $
    04023 Scripts/Call Flows/Screen Shots/Business Rules
    
    $
    04024 Work Breakdown Structure/Schedule
    
    $
    04025 Incident Reports
    
    $
    04026 Convenience Fee  Fixed
    
    
    2.35
    %*(There is a $3.95 minimum fee)4027 Debit Card Flat Fee  Fixed
    
    $
    3.95TOTAL FIXED PRICE
    
    $
    0
 Page - 8




---



##### 



2.3
AUTHORITY  CONTRACTING OFFICER, CONTRACTING OFFICERS TECHNICAL REPRESENTATIVE AND CONTRACTORS PROJECT MANAGER
  
    
       Page - 9




---



##### 



2.4 PERIOD OF PERFORMANCE
  Base Period:
    
    April 2, 2009
    
    through
    
    December 31, 2009Option Period I :
    
    January 1, 2010
    
    through
    
    December 31, 2010Option Period II:
    
    January 1, 2011
    
    through
    
    December 31, 2011Option Period III:
    
    January 1, 2012
    
    through
    
    December 31, 2012Option Period IV:
    
    January 1, 2013
    
    through
    
    December 31, 2013
 2.5 PREPARATION FOR DELIVERY
 
 2.6 MARKING OF SHIPMENTS
   (1)
    
    IRS Contract Number and Title,(2)
    
    Delivery Address,(3)
    
    Point of Contact (including Name and Telephone Number) (see Delivery
Order Block No. 6)(4)
    
    Sequential container Contents.(5)
    
    Identification of Container Contents.
 Page - 10




---



##### 



3. CLAUSES
 FAR 52.252-2 CLAUSES INCORPORATED BY REFERENCE (FEB 1998)
   ClauseNumber
    
    Title
    
    Date52.203-6
    
    Restrictions on Subcontractor Sales to the Government (ALT 1)
    
    (FEB 2007)(OCT 1995)52.204-4
    
    Printed or Copied Double-Sided on
    
    (AUG 2000)On Recycled Paper52.212-4
    
    Contract Terms and Conditions
    
    (FEB 2007)52.233-4
    
    Applicable Law for Breach of Contract Claim
    
    (OCT 2004)
 FAR 52.212-5 Contract Terms And Conditions
Required To Implement Statutes Or Executive
OrdersCommercial Items (Sept 2008
  52.233-3 31 U.S.C. 3553
 52.233-4
  Contracting Officer check as appropriate
 þ 52.203-6 41 U.S.C. 253g 10 U.S.C. 2402
 o 52.219-3 15 U.S.C.
657a
 þ 15 U.S.C. 657a
 o
 Page - 11




---



##### 



o 52.219-6 15
U.S.C.
 o 52.219-6
 o 52.219-6
 o 52.219-7 15
U.S.C. 644
 o 52.219-7
 o 52.219-7
 o 52.219-8
 o 52.219-9 15
U.S.C. 637(d)(4)
 o 52.219-9
 o
 o 52.219-14 15 U.S.C.
637(a)(14)
 o 15
U.S.C. 637(d)(4)(F)(i)
 o 52.219-23 10 U.S.C. 2323
 o 52.219-23
 o 52.219-25 10 U.S.C.
2323
 o 52.219-26 10 U.S.C. 2323
 o 52.219-27 15 U.S.C. 657 f
 o 52.219-28 15 U.S.C. 632(a)(2)
 o 52.222-3
 þ 52.222-19
 o 52.222-21
 þ 52.222-26
 þ 52.222-35 38 U.S.C. 4212
 þ 52.222-36 29 U.S.C. 793
 þ 52.222-37 38 U.S.C. 4212
 Page - 12




---



##### 



o 52.222-39
 o 52.222-50
 o 52.222-50
 o 52.223-9 42 U.S.C. 6962(c)(3)(A)(ii)
 o 52.223-9 (42 U.S.C. 6962(i)(2)(C)
 o (DEC 2007) 42
U.S.C. 8259b
 o 52.223-16 (DEC 2007)
 o 52.223-16
 o 41 U.S.C. 10a-10d
 o 52.225-3 41 U.S.C. 10a-10d, 19 U.S.C. 3301 19 U.S.C. 2112
 o 52.225-3
 o 52.225-3
 o 52.225-5 (NOV 2007) 19 U.S.C. 2501 et
seq 19 U.S.C. 3301
 o 52.225-13
 o 52.226-4 42
U.S.C. 5150
 o 52.226-5 42 U.S.C. 5150
 þ 52.232-29 41 U.S.C. 255(f), 10 U.S.C. 2307(f)
 o 52.232-30 41
U.S.C. 255(f), 10 U.S.C. 2307(f)
 þ 52.232-33 31 U.S.C. 3332
 o 52.232-34 31 U.S.C. 3332
 þ 52.232-36 31 U.S.C. 3332
 þ 52.239-1 5 U.S.C. 552a
 o 52.247-64 46 U.S.C. Appx. 1241(b) U.S.C. 2631
 o 52.247-64.
 Page - 13




---



##### 



Contracting Officer check as appropriate.
 o 41 U.S.C. 351, et seq
 o 52.222-42 29 U.S.C. 206 U.S.C. 351 et seq
 o 52.222-43 29 U.S.C. 206 41
U.S.C et seq
 o 52.222-44 (29 U.S.C. 206 41 U.S.C. 351 et seq
 o 52.222-51 41 U.S.C.
351 et seq.
 o 52.222-53, 41 U.S.C. 351 et seq.
 o 52.237-11 31
U.S.C. 5112(p)(1)
 Comptroller General Examination of Record 52.215-2
  Subpart 4.7
   Page - 14




---



##### 



52.219-8 15 U.S.C.
637(d)(2) 52.219-8
 52.222-26
 52.222-35 38 U.S.C. 4212
 52.222-36 29 U.S.C. 793
 52.222-39
 52.222-41 41 U.S.C. 351 et
seq
 52.222-50 22 U.S.C.
7104(g) 52.222-50
 52.222-51 41 U.S.C. 351 et seq.
 52.222-53 41 U.S.C. 351 et seq.
 52.247-64 46 U.S.C. Appx. 1241(b 10 U.S.C. 2631 52.247-64
   Alternate I (Feb 2000) 12.301(b)(4)
 FAR 52.216-1 TYPE OF CONTRACT (APR 1984)
   Page - 15




---



##### 



52.217-8 Option to Extend Services.
 17.208(f),
 Option to Extend Services (Nov 1999)
   52.217-9 Option to Extend the Term of the Contract.
 17.208
 Option to Extend the Term of the Contract (Mar 2000)
     52.227-19 Commercial Computer Software License.
 27.409
 Commercial Computer Software License (Dec 2007)
  Page - 16




---



##### 



52.232-33
Payment by Electronic Funds Transfer  Central Contractor Registration.
 32.1110
 Payment
by Electronic Funds Transfer  Central Contractor Registration  ct
     Page - 17




---



##### 



Contractors EFT information
 Mechanisms for EFT payment
 Suspension
of payment
         EFT and prompt payment
 EFT and assignment of claims
 Page - 18




---



##### 



Subpart 32.8
 Liability for change of EFT information by financial agent
 Payment information
  52.237-3 Continuity of Services.
 37.110
 Continuity of Services (Jan 1991)
     Page - 19




---



##### 



i.e.,
  1052.224-9000(a) Disclosure of Information-Safeguards (January 1998)
       1052.224-9000(d) Disclosure of Sensitive but Unclassified Information Safeguards (March 2008)
  Page - 20




---



##### 



1052.2249001A
IRSAP 1052.224-9001(a) Disclosure of Information  Criminal/Civil Sanctions (January 1998)
    Page - 21




---



##### 



employee of a contractor, who by virtue of his/her employment or official
position, has possession of or access to agency records which contain individually
identifiable information, the disclosure of which is prohibited by the Privacy Act
or regulations established thereunder, and who knowing that disclosure of the
specific material is so prohibited, willfully discloses the material in any manner
to any person or agency not entitled to receive it, shall be guilty of a
misdemeanor and fined not more than $5,000.
  1052.224-9001(b) Disclosure of Information-Sensitive but Unclassified Use Only (March 2008)
   1052.224-9002
IRSAP 1052.224-9002 Disclosure of Information  Inspection (December 1988)
   1052.204-9003 Information Security Training Requirements (Mar 2008)
   Page - 22




---



##### 



Page - 23




---



##### 



Page - 24




---



##### 



ATTACHMENT 2
 STATEMENT OF WORK
 Entitled
 Electronic PAYMENT
 (E-PAYMENT)
 Page - 25




---



##### 



C.1 STATEMENT OF WORK
 C.1.1 INTRODUCTION
 1
   e-file
 C.1.2. SCOPE
     
 1
    
    The data was derived from the IRS 2005 Data Book. Page - 26




---



##### 



C.1.3. OBJECTIVE
   C.1.4. BACKGROUND
   Page - 27




---



##### 



INDIVIDUAL ELECTRONIC PAYMENT AVERAGE AMOUNT (FY 2005)
 Electronic Funds Withdrawal
    
    Credit CardForm 1040
    
    $
    2,188
    
    
    $
    1,823Form 4868
    
    $
    14,734
    
    
    $
    3,236Form 1040ES
    
    $
    4,105
    
    
    $
    3,619
 Income Tax Returns (TY 2003)
    
    Number of Returns
    
    AmountTotal returns
    
    
    130,423,626Returns with Income tax withheld
    
    
    114,861,706
    
    
    $
    703,758,484Payment with Extension Request
    
    
    1,333,579
    
    
    $
    38,303,188Estimated tax payments
    
    
    11,576,2132
    
    
    $
    182,906,911Tax due at time of filing
    
    
    21,072,333
    
    
    $
    73,741,408
  
 2
    
    Approximately, 34 million distinct Form 1040ES payments were made which were
applied to the above returns. Business Tax Returns  Balance
Due (Processing Year 2003)
    
    Number of Returns
    
    Amount (in thousands)Annual Federal Unemployment Tax Returns (F940)
    
    
    2,393,865
    
    
    $
    329,781,163Quarterly Employment Tax Return (F941)
    
    
    6,121,496
    
    
    $
    8,531,515,026Corporate Tax Return (1120 series)
    
    
    482,434
    
    
    $
    7,397,069,148Highway Use Tax (Form 2290)
    
    
    428,408
    
    
    $
    774,685,778
  C.1.5 CONTRACT REQUIREMENTS
  www.officialpayments.com/fed
    Page - 28




---



##### 



C.2 MINIMUM MANDATORY BUSINESS REQUIREMENTS
  C.2.1
 C.2.2 only
 C.2.3
 C.2.4
 C.2.5
 C.2.6
 C.2.7
 C.2.8
 C.2.9
 C.2.10
 Page - 29




---



##### 



C.2.11
 C.2.12
 C.2.13 The Contractor shall forward settlement files to
the TFA one business day prior to settlement.
 C.2.14
 C.2.15
 C.2.16
 C.2.17
 C.2.18
 C.2.19
 C.2.20
 C.2.21
 C.2.22
 Page - 30




---



##### 



C.2.23
 C.2.24
 C.2.25
 C.2.26
 C.2.27
 C.2.28 Funds Settlement Timeline
 C.2.29
 C.2.30 Configuration control and management shall be exercised and documented as system and
functionality changes occur
 C.2.31
 C.2.32
 C.2.33
 Page - 31




---



##### 



th th
 C.2.34
 C.2.35
 C.2.36
 C.2.37
 C.2.38
 C.2.39
 C.2.40 annual
 C.2.41
 C.2.42
 C.2.43
 Page - 32




---



##### 



C.2.44
 C.2.45
 C.2.46 e-file e-file
 C.2.47
 C.2.48
 C.3 REHABILITATION ACT OF 1973, SECTION 508 IT ACCESSIBILITY REQUIREMENTS
    Page - 33




---



##### 



(b) Section 508 requires that when Federal agencies develop, procure, maintain, or use electronic
and information technology, Federal employees with disabilities have access to and use of
information and data that is comparable to the access and use by Federal employees who are not
individuals with disabilities, unless an undue burden would be imposed on the agency. Section 508
also requires that individuals with disabilities, who are members of the public seeking
information or services from a Federal agency, have access to and use of information and data
that is comparable to that provided to the public who are not individuals with disabilities,
unless an undue burden would be imposed on the agency.
      C.4
1052.239-9008 Section 508 Information, Documentation, and Support (SEP 2006)
 36 CFR 1194, Subpart D, Architectural and Transportation Barriers Compliance Boards Electronic and Information
Technology Accessibility Standards .
 (c)
    
    Product support documentation provided to end-users shall be made available in alternate
formats upon request, at no additional charge.(d)
    
    End-users shall have access to a description of the accessibility and compatibility
features of products in alternate formats or alternate methods upon request, at no
additional charge.(e)
    
    Support Services for products shall accommodate the communication needs of end-users
with disabilities.
 Page - 34




---



##### 



End of clause
 C.5 1052.239-9009 Section 508 Conformance (SEP 2006)
 standards at 36 CFR 1194
  o 1194.21, Software applications and operating systems.
 o(a)
    
    o(b) o(c) o(d) o(e) o(f) o(g) o(h)
o(i) o(j) o(k) o(l)
 þ 1194.22, Web-based intranet and internet information and applications.
 þ(a)
    
    þ(b) þ(c) þ(d) þ(e) o(f) þ(g)
þ(h) þ(i) þ(j) o(k) þ(l) þ(m) þ(n) þ(o) o(p)
 þ 1194.23, Telecommunications products.
 o(a)
    
    o(b) þ(c) þ(d) o(e) o(f) o(g) o(h)
o(i) þ(j) o(k)
 o 1194.24, Video and multimedia products.
 o(a)
    
    o(b) o(c) o(d) o(e)
 o 1194.25, Self contained, closed products.
 o(a)
    
    o(b) o(c) o(d) o(e) o(f) o(g) o(h)
o(i) o(j)
 o 1194.26, Desktop and portable computers.
 o(a)
    
    o(b) o(c) o(d)
  36 CFR 1194.31
 þ
    
    (a) At least one mode of operation and information retrieval that does not
require user vision shall be provided, or support for assistive technology used by people
who are blind or visually impaired shall be provided.þ
    
    (b) At least one mode of operation and information retrieval that does not require
visual acuity greater than 20/70 shall be provided in audio and enlarged print output
working together or independently, or support for assistive technology used by people who
are visually impaired shall be provided.þ
    
    (c) At least one mode of operation and information retrieval that does not require
user hearing shall be provided, or support for assistive technology used by people who
are deaf or hard of hearing shall be provided.
 Page - 35




---



##### 



þ
    
    (d) Where audio information is important for the use of a product, at least one mode
of operation and information retrieval shall be provided in an enhanced auditory fashion,
or support for assistive hearing devices shall be provided.þ
    
    (e) At least one mode of operation and information retrieval that does not require
user speech shall be provided, or support for assistive technology used by people with
disabilities shall be provided.þ
    
    (f) At least one mode of operation and information retrieval that does not
require fine motor control or simultaneous actions and that is operable with limited reach
and strength shall be provided.
 End of clause
 C.6 HIGHLY DESIRABLE FEATURES
  C.6.1 System Design
 C.6.1.1
 C.6.2 System Security and Test
 C.6.2.1
 C.6.3 Management and Customer Service
 C.6.3.1
 C.6.3.2
 C.6.3.3
 C.6.3.4
 C.6.4 Marketing and Deliverables
 C.6.4.1
 C.6.4.2
 Page - 36




---



##### 



C.7 DUTIES AND RESPONSIBILITIES OF THE GOVERNMENT
  C.7.1
 C.7.2
 C.7.3
 C.7.4
 C.7.5
 C.7.6
 C.7.7
 C.7.8
 C.7.9
 C.8 KEY PERSONNEL
 C.8.1 CONTRACTORS KEY PERSONNEL
  C.8.2 SUBSTITUTION OF KEY PERSONNEL
 Page - 37




---



##### 



C.9 DELIVERABLES
 Documentation formatting and contents are subject to inspection, verification and approval by the
Contracting Officers Technical Representative
(COTR) and/or IRS representative.
 Deliverables Summary:
 C.9.1 ELECTRONIC PAYMENTS
  7
    
    a nine character Taxpayer Identification Number [first social security number (SSN) asshown on the tax return for the year for which the payment applies or the employer
identification number (EIN)],
 Page - 38




---



##### 



8
    
    four character name control (provided to Contractor in the entity validation response file, 824
transaction set),9
    
    payment type,10
    
    tax period ending date (six character date field),11
    
    payment amount,12
    
    payment authorization date,13
    
    daytime telephone number, and14
    
    confirmation number.
 C.9.2 MONTHLY DEVELOPMENT STATUS REPORTS
 th
 3
    
    date of report,4
    
    project manager name,5
    
    project manager telephone number, fax number and e-mail address,6
    
    a brief description of the work accomplished, emphasizing the progress made since the last
reporting period,7
    
    a description of any unresolved and/or anticipated problems, if any (include schedule
impacts),8
    
    an estimate of the percent of work accomplished to date, and9
    
    a statement on the status of the program as it relates to the work breakdown schedule, either
confirming that milestones are on schedule or explaining the nature and extent of the pending
delay.
 C.9.3 DAILY AND MONTHLY TRANSACTION REPORTS
 th
 4.
    
    date of report,5.
    
    period covered,6.
    
    total number of transactions,7.
    
    dollar amount of transactions,8.
    
    total number of successful (authenticated) attempts,9.
    
    dollar amount of successful (authenticated) attempts,10.
    
    volume by tax type,11.
    
    dollars by tax type,
 Page - 39




---



##### 



12.
    
    volume by card type,13.
    
    dollars by card type14.
    
    average payment amount,15.
    
    largest dollar payment amount,16.
    
    total number of failed (unauthenticated) attempts, abandoned or incomplete transactions,17.
    
    reasons for failed (unauthenticated) attempts,18.
    
    customer service activity,19.
    
    report of entity rejects, where the user has provided invalid entity information,20.
    
    aggregate payment volumes by payment type and dollar amount shall be provided daily, and21.
    
    historical data should also be provided to compare changes in volumes from the prior year.
 C.9.4 CREDIT CARD CHARGEBACK REPORTS (IF APPLICABLE)
  C.9.5 EXCEPTION HANDLING REPORTS
 th
 C.9.6 AD HOC REPORTS
  C.9.7 FINDINGS REPORT
 initial supplemental
 a.
    
    The program features,b.
    
    conduct and findings of the program as they relate to the
Contractors and any subcontractors performance (including
a summary of all payment transactions, special  features
such as Spanish language, recurring payments and payment reminders, any


problems, changes made during the filing season and lessons learned),
 Page - 40




---



##### 



c.
    
    recommendations for improvement including changes to the
Contractors and/or IRS processes,d.
    
    practitioner and/or client feedback including customer satisfaction survey results,e.
    
    customer service activity based on automated and live assistance provided; andf.
    
    summary of trends or patterns of suspicious activity.
 initial supplemental initial
 C.9.8 MARKETING REPORTS
 initial supplemental initial supplemental
 C.9.9 CAPACITY ANALYSIS
  C.9.10 SYSTEM SECURITY PLAN
             Page - 41




---



##### 



C.9.11 SECURITY FEATURES USER GUIDE
         C.9.12 CONFIGURATION MANAGEMENT PLAN
         C.9.13 RISK ASSESSMENT PLAN
        Page - 42




---



##### 



C.9.14 DISASTER RECOVERY PLAN
       C.9.15 NETWORK DESIGN AND ARCHITECTURE SCHEMATICS
   C.9.16 TRUSTED FACILITY MANUAL
   a.
    
    Provides specific guidance to administrators on how to configure and install the systemb.
    
    How to administer and operate the system in a secure mannerc.
    
    How to avoid risks and improper use of administrative functions that would compromise the systemd.
    
    Procedures for examining and maintaining the audit files as well as the detailed audit record
structure for each type of audit shall be givene.
    
    Management commitment and approval (authorization to operate)
 C.9.17 PROCESS AND DATA FLOW SCHEMATIC
  C.9.18 FUNDS SETTLEMENT TIMELINE
  C.9.19 SYSTEM DEVELOPMENT LIFE CYCLE
  Page - 43




---



##### 



C.9.20 TEST PLANS, TEST CASES AND TEST RESULTS
  C.9.21
FUNCTIONAL DOCUMENTATION  SCRIPTS, SCREENS, CALL FLOWS, USER GUIDES, ETC.
  C.9.22 REFERENCE:
 Public Laws
         Information on Public Laws is available at: http://thomas.loc.gov
 Executive Orders
   Presidential Decision Directive
  Office of Management and Budget (OMB)
     OMB Memorandum
    Federal Regulation
  Department of Treasury
    Treasury Memorandum & IRS Documentation
 TBD
 Page - 44




---



##### 



Internal Revenue Manuals (IRMs)
 TBD
 General Accounting Office (GAO)
    The GAO Publications noted above are available on GAO website: http://gao.gov
 National Institute of Standards and Technology (NIST) Special Publications (SP) 800 Series website: http://csrc.nist.gov
 C.10 SCHEDULE OF PERFORMANCE
  Responsible
    
    Event
    
    AnticipatedParty
    
    
    
    Due DatesContractor
    
    Provide UNAX briefing documentation
    
    04/10/2009All
    
    Annual Requirements Review for FS 2010
    
    04/20/2009Contractor
    
    Provide draft WBS (including requirements, development, testing
and implementation phases)
    
    05/11/2009IRS
    
    Provide comments on draft WBS
    
    05/18/2009Contractor
    
    Deliver base lined WBS
    
    06/01/2009Deliver Initial Functional Requirements/User InterfaceContractor
    
    Documentation and workflow schematics; including scripts, web
text & screen shots, business rules, etc.
    
    06/08/2009IRS
    
    Provide initial comments on draft Functional Documentation
(iterative process)
    
    06/22/2009Contractor
    
    Obtain signed contracts with other participating subcontractors, if
applicable
    
    06/30/2009Contractor
    
    Deliver Transaction Processing Network Documentation
    
    07/20/2009Contractor
    
    Deliver Final Functional Requirements/User Interface
Documentation
    
    08/17/2009IRS
    
    Final Sign Off on Functional Requirements/User Interface
Documentation
    
    08/21/2009Contractor
    
    Deliver Trusted Facility Manual
    
    08/24/2009Contractor
    
    Deliver Final Test Plans and Test Cases
    
    08/31/2009Contractor
    
    Begin internal application testing
    
    09/07/2009Contractor
    
    Deliver FS 2010 Marketing Plan
    
    09/21/2009IRS
    
    Provide comments on Marketing Plan
    
    09/28/2009IRS
    
    Provide revised credit card chargeback procedures, if applicable
    
    10/05/2009Contractor
    
    Complete internal application testing
    
    10/30/2009
 Page - 45




---



##### 



Responsible
    
    Event
    
    AnticipatedParty
    
    
    
    Due DatesContractor
    
    Begin full circle integrated test with IRS/TFA (subject to change)
    
    11/02/2009Contractor
    
    Complete full circle integrated test with IRS/TFA (subject to
change)
    
    11/13/2009Contractor
    
    Complete all testing and obtain bulk provider certification from
TFA
    
    12/07/2009Contractor
    
    Implement Electronic Payment Services for FS 2010
    
    01/01/2010IRS
    
    Provide hyperlink from the IRS web
site to the Contractors Web page
    
    01/08/2010Contractor
    
    Deliver Initial FS 2010 Findings Report
    
    06/01/2010Contractor
    
    Deliver Initial FS 2010 Marketing Report
    
    06/01/2010Contractor
    
    Deliver Supplemental FS 2010 Findings Report
    
    02/01/2011Contractor
    
    Deliver Supplemental FS 2010 Marketing Report
    
    02/01/2011
  C.11 INSPECTION AND ACCEPTANCE
  C.11.1 REVIEW OF REPORTS AND RECORDS
  
    
    The Service Provider shall make the necessary modifications that will allow the
Government to accept the final product within five (5) days from date of notification.
 C.12 PUBLIC RELEASE OF INFORMATION
   Page - 46




---



##### 



Page - 47




---



##### 



Attachment 3
 LIST OF APPENDICES
 Appendix  No.
    
    Title
    
    Doubleclicktoopen fileA.
    
    FAR 2.101  Definition Of A Commercial Item
    
    (PDF LOGO)B.
    
    2009 Credit Card Bulk Provider Requirements
    
    (PDF LOGO)C.
    
    Treasury Regulations 301.6311-2 Payment by Credit Card or Debit Card
    
    (PDF LOGO)
 Page - 48




---



##### 



FAR 2.101  Definition of Commercial Item
    
    Attachment 3, Appendix A




---



##### 



FAR 2.101  Definition of Commercial Item
    
    Attachment 3, Appendix A




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 CREDIT
 CARD
 
 BULK
 PROVIDER
 REQUIREMENTS
 Revised 03/05/08
 1




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 Nature of Changes
 Date/Version
    
    Page
    
    Paragraph
    
    Change Description03/05/2008 v7
    

    74-78,
112
    
    
    
    
    Annual Updates  addition of five tax types for stand-
alone payments.03/05/2008
    

    103
    
    
    
    
    Update to Federal Reserve Holiday Schedule
 Revised 03/05/08
 2




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 TABLE OF CONTENTS
 Page1. General Interest ItemsA. EFTPS Bulk Provider Registration
    
    
    5B. Letter of Agreement
    
    
    8C. Project Schedules
    
    
    9D. Customer Service
    
    
    132. Specific Processing RequirementsA. EDI Translation Status
    
    
    14B. IRS Entity Validation (Direct Credit Card Payments only)
    
    
    18C. Payments
    
    
    19D. Testing Plan
    
    
    203. Telecommunications ConcernsA. Data Transmission Specifications
    
    
    29B. Telecommunication Set-Up
    
    
    30C. Disaster Recovery
    
    
    31D. Bulk Provider Disaster Recovery Plan
    
    
    324. EDI Record FormatsA. General
    
    
    33B. Chapter 3 - Taxpayer Entity Validation
    
    
    34C. Chapter 4 - ACH Bulk Debits
    
    
    60D. Chapter 9  Return and Exception Item Reporting
    
    
    93E. Chapter 10  Daily Operations Procedures
    
    
    1015. IRS Requirements for Integrated File and Pay CC Processors
    
    
    104Credit Card Bulk Provider Registration
    
    
    111Credit Card Bulk Provider Agreement
    
    
    112
 Revised 03/05/08
 3




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 1.
    
    General Interest Items
 TREASURY FINANCIAL AGEMENT (TFA) CONTACT LIST
 To be provided upon registering with the Treasury Financial Agent
 Revised 03/05/08
 4




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 A.
    
    EFTPS BULK PROVIDER REGISTRATION
 1.
    
    Each Credit Card Bulk Provider must complete the standard EFTPS Business Enrollment form (IRS
Form 9779) and the attached TRADING PARTNER REGISTRATION FORM. The Treasury Financial Agent
(TFA) will use the enrollment and Registration forms to initially set up the Credit Card Bulk
Provider on the Electronic Federal Tax Payment System (EFTPS) and to track activity. The
completed forms will be mailed to the address provided by the TFA.2.
    
    In the Integrated File and Pay Credit Card Program, a balance due return is associated with
an accepted e-file return. The approved credit card payment must wait for the acceptance of
the e-file return. Upon acceptance of the e-file return, the credit card payment can be
submitted using the Credit Card Bulk Provider Requirements and the approved entity and tax
identifying information accepted by the IRS. In order to use this program, the credit card
bulk provider must annually register with the IRS and sign an agreement indicating the
companys adherence to the IRS requirements. In addition, the bulk provider must register and
test with the assigned Treasury Financial Agent. For subsequent years, the bulk provider must
annually test with the TFA to be recertified. All testing is required to be completed and
certification to be submitted by December 28 of each year. If December 28 falls on a Saturday
or Sunday, the preceding workday will be the due date.3.
    
    For stand-alone credit card programs, the IRS requires a proposal to be submitted in
reference to an IRS Request for Proposal. The IRS will issue contract awards based on the best
solutions for increasing e-file and electronic payment volumes.
 Revised 03/05/08
 5




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 TRADING PARTNER REGISTRATION FORM
 Company Profile
 Company Name  Your corporate name (up to 30 characters).Address (up to 30 characters)
 City
    
    State
    
    Zip
    
    Country
 Business Unit  Your division name (up to 30 characters)
    
    Business HoursDescribing a specific business unit under the company name.
 EDI Envelope Information
 Interchange Receiver ID (up to 15 characters)
    
    Function group ID (up to 15 characters)
 Communications Contact
 Communications Contact Name
    
    Title
    
    Phone (xxx-xxx-xxxx)(Up to 30 characters)
    
    (Up to 30 characters)
 EDI Contact
 EDI Contact Name
    
    Title
    
    Phone (xxx-xxx-xxxx)(Up to 30 characters)
    
    (Up to 30 characters)
 Revised 03/05/08
 6




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 GENERAL INFORMATION
 Please list the following:Hardware Platform:Operating System:Database:Communications Software Protocol:Translator:Dedicated or Dial Up ConnectionType of Modem:Modem Speed:Production site area code
and exchange number:Disaster recovery site
area code and exchange number:Company business hours:Contact name:Contact Business Hours:Contact Telephone Number:
 Revised 03/05/08
 7




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 B.
    
    LETTER OF AGREEMENT
    Revised 03/05/08
 8




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 C. PROJECT SCHEDULES
 BULK PROVIDER & TREASURY FINANCIAL AGENT
DEVELOPMENT SCHEDULE
 TARGET
    
    
    TARGETPHASE
    
    START DATE
    
    
    END DATE
    
    
    STATUSEDI SOFTWARE INSTALLATIONBUSINESS SYSTEM DESIGN
 ENTITY VALIDATION (Required for Credit Card processors who are contacted directly by the taxpayer)
 
 DEBIT PAYMENTS
 
 Revised 03/05/08
 9




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 TREASURY FINANCIAL AGENT TESTING SCHEDULE
 
 Earliest Available
    
    ExpectedStart Date
    
    Start DateTELECOMMUNICATIONENTITY VALIDATION(Entity Validation for Name Control)DEBIT PAYMENT
  Revised 03/05/08
 10




---



##### 



(EFTPS LOGO)
    
    Attachment 3, Appendix B2009 Credit Card Bulk Provider Requirements
 FINANCIAL AGENT ENTITY VALIDATION PROCESS SCHEDULE
(For Credit Card Transactions Initiated Directly by Taxpayers)
 BULK PROVIDER NAME
 DESCRIPTION OF VALIDATION APPROACH
 
 
 
 
 
 
 
 
 
 
 
 
 EXPECTED START DATEEXPECTED END DATENUMBER OF TRANSMISSIONSFREQUENCY
 Revised 03/05/08
 11




---



##### 



(EFTPS LOGO)
    
    Attachment 3, Appendix B2009 Credit Card Bulk Provider Requirements


TFA PAYMENT LIVE DATES
 
 
 
 Payment Method
    
    Bulk DebitExpected Live dateExpected Initial VolumeExpected FrequencyExpected Growth
 Revised 03/05/08
 12




---



##### 



(EFTPS LOGO)
    
    Attachment 3, Appendix B2009 Credit Card Bulk Provider Requirements
 D.
    
    CUSTOMER SERVICE1.
    
    The EFTPS support staff hours for Credit Card Bulk Providers are from 8:30 a.m. ET to 8:00
p.m. ET, Monday through Friday. It is imperative that all calls regarding operational concerns
come through the Bulk Provider Customer Service line.2.
    
    EFTPS needs to know the business hours of all Bulk Providers. Please be prepared to exchange
this information at the time of the individual conference calls.3.
    
    The Bulk Provider procedures for inquiring about an entity validation file and/or payment are as
followed
 STEP 1.
    
    Do notautomatically resubmit the entity validation and /or payment.STEP 2.
    
    Call Customer Service at the toll free 800 number to check on the status of the entity validation and/or
payment.STEP 3.
    
    The Customer Service Center will be able to give status information on the entity
validation and/or payment by looking to our Customer Service Application Database.
 Revised 03/05/08
 13




---



##### 



(EFTPS LOGO)
    
    Attachment 3, Appendix B2009 Credit Card Bulk Provider Requirements
 2.
    
    SPECIFIC PROCESSING REQUIREMENTS
 A.
    
    EDI TRANSLATION
 1.
    
    If you are using an EDI translation software package, review where you are in the
implementation process for the initial review conference call.2.
    
    If you are doing your own EDI development, review your intended support of all EFTPS
transaction sets. (NOTE: We continue to recommend that you purchase EDI translation software.
Historically, in-house development of EDI translators have elongated the testing process for
EDI newcomers, and complications may jeopardize your live date.)3.
    
    Note that all data must be compliant with the 3050 version of the ANSI x12 EDI standards. To
obtain a copy of the standards, visit www.ANSI.org. There is a cost.4.
    
    Updates to new versions of the ANSI Standard will be reviewed as they become available. If
EFTPS determines that the new standard will be utilized the change control procedures will be
followed.
 a.
    
    Six months notice will be given prior to implementing a new standard.b.
    
    Old standards will be supported for a minimum of 6 months following the implementation
of a new standard.
 5.
    
    Review shared understanding of the contents of the ISA and GS segments (see attached). (e.g.
  potential use of EINs or Dunns numbers for Sender and Receiver IDs)6.
    
    Bulk provider must verify that they use EFTPS EDI standards
 A.
    
    The tilde ~ as a data element separator.B.
    
    The backslash \ as a segment separator.C.
    
    The greater than sign > as a sub-segment separator.
 Revised 03/05/08
 14




---



##### 



(EFTPS LOGO)
    
    Attachment 3, Appendix B2009 Credit Card Bulk Provider Requirements
 ISA SEGMENTINTERCHANGE CONTROL SEGMENT  INCOMING TO THE TREASURY
FINANCIAL AGENT
 REF.
    
    
    
    Req.
    
    Elem.
    
    Elem.Element
    
    Nmbr
    
    Name
    
    Desig
    
    Type
    
    Length
    
    CommentsISA01
    
    I01
    
    Authorization Information Qualif.
    
    M
    
    ID
    
    2/2
    

    00ISA02
    
    I02
    
    Authorization Information
    
    M
    
    AN
    
    10/10
    
    blanksISA03
    
    I03
    
    Security Information Qualifier
    
    M
    
    ID
    
    2/2
    
    00ISA04
    
    I04
    
    Security Information
    
    M
    
    AN
    
    10/10
    
    blanksISA05
    
    I05
    
    Interchange ID Qualifier
    
    M
    
    ID
    
    2/2
    
    determined by bulk
providerISA06
    
    I06
    
    Interchange Sender ID
    
    M
    
    AN
    
    15/15
    
    determined by bulk
providerISA07
    
    I05
    
    Interchange ID Qualifier
    
    M
    
    ID
    
    2/2
    
    to be provided by TFAISA08
    
    I07
    
    Interchange Receiver ID
    
    M
    
    AN
    
    15/15
    
    to be provided by TFAISA09
    
    I08
    
    Interchange Date
    
    M
    
    DT
    
    6/6
    
    current dateISA10
    
    I09
    
    Interchange Time
    
    M
    
    TM
    
    4/4
    
    current timeISA11
    
    I10
    
    Interchange Control Standards ID
    
    M
    
    ID
    
    1/1
    
    UISA12
    
    I11
    
    Interchange Control Vers. Number
    
    M
    
    ID
    
    5/5
    


    to be provided by TFAISA13
    
    I12
    
    Interchange Control Number
    
    M
    
    N0
    
    9/9
    
    determined by bulk
provider*ISA14
    
    I13
    
    Acknowledgment Requested
    
    M
    
    ID
    
    1/1
    
    0ISA15
    
    I14
    
    Test Indicator
    
    M
    
    ID
    
    1/1
    
    T or PISA16
    
    I15
    
    Component Element Separator
    
    M
    
    AN
    
    1/1
    
    >
 
 *
    
    This number will be validated in duplication checks and must be unique. Revised 03/05/08
 15




---



##### 



(EFTPS LOGO)
    
    Attachment 3, Appendix B2009 Credit Card Bulk Provider Requirements
 GS SEGMENT  FUNCTIONAL GROUP HEADER  INCOMING TO THE TFA
 REF.
    
    
    
    Req.
    
    Elem.
    
    Elem.Element
    
    Nmbr
    
    Name
    
    Desig
    
    Type
    
    Length
    
    CommentsGS01
    
    
    479
    
    
    Functional Identifier Code
    
    M
    
    ID
    
    2/2
    
    838 = TD, 813 = TFGS02
    
    
    142
    
    
    Application Senders Code
    
    M
    
    AN
    
    2/15
    
    To be provided by
the TFAGS03
    
    
    124
    
    
    Application Receivers Code
    
    M
    
    AN
    
    2/15
    
    To be provided by
the TFAGS04
    
    
    373
    
    
    Date
    
    MIZ
    
    DT
    
    6/6
    
    current dateGS05
    
    
    337
    
    
    Time
    
    MIZ
    
    TM
    
    4/8
    
    current timeGS06
    
    
    28
    
    
    Group Control Number
    
    MIZ
    
    N0
    
    1/9
    
    determined by bulk
provider *GS07
    
    
    455
    
    
    Response Agency Code
    
    M
    
    ID
    
    1/2
    
    XGS08
    
    
    480
    
    
    Version/RIs/Industry ID Code
    
    M
    
    AN
    
    1/12
    
    003050
 
 *
    
    This number will be validated in duplication checks and must be unique. Revised 03/05/08
 16




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 GE SEGMENT
FUNCTIONAL GROUP TRAILER
 REF.
    
    
    
    Req.
    
    Elem.
    
    Elem.Element
    
    Number
    
    Name
    
    Desig.
    
    Type
    
    Length
    
    CommentsGE01
    
    
    97
    
    
    Number of
Transaction Sets
Inc.
    
    M
    
    N0
    
    1/6GE02
    
    
    28
    
    
    Group Control Number
    
    MIZ
    
    N0
    
    1/9
    
    (Must = GS06)
 IEA SEGMENT
INTERCHANGE CONTROL TRAILER
 REF.
    
    
    
    Req.
    
    Elem.
    
    Elem.Element
    
    Number
    
    Name
    
    Desig.
    
    Type
    
    Length
    
    CommentsIEA01
    
    I16
    
    Number of Included Funct
Group
    
    M
    
    N0
    
    1/5IEA02
    
    I12
    
    Interchange Control Number
    
    M
    
    N0
    
    9/9
 Revised 03/05/08
 17




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 B.
    
    ENTITY VALIDATION (Direct Taxpayer Contact with Credit Card Processor Only)
 e-file e-file
  1.
    
    Review the entity validation process. The entity validation process is located in the EFTPS
User Requirements document.New requests needing IRS validation in order to obtain name control can be transmitted
daily along with the payment files for previously validated taxpayers.2.
    
    Review of the bulk provider entity validation error codes (see the below list).
 EFTPS BULK PROVIDER ENTITY VALIDATION ERROR CODES
 Error Codes
    
    Description
    
    Comments0005
    
    TIN mismatched.
    
    IRS Critical Error
 Revised 03/05/08
 18




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 C.
    
    PAYMENTS
  1)
    
    Transmission Schedules:
 a)
    
    The deadline for processing debit payments is 7:00 p.m. ET on the calendar
day prior to settlement day. (Note: If a bulk provider wants to send in a file on
Saturday or Sunday, they must communicate with the FA during normal business hours.)b)
    
    Settlement will occur on banking days only, Monday through Friday, excluding
holidays.
 2)
    
    Rejects:
 a)
    
    The FA will provide you with complete payment reject codes and conditions. A few
possible reasons are:
 1)
    
    No name control2)
    
    Dollar amount over $99,999,999.99 per transaction set (1,000 payments)3)
    
    File format error
 3)
    
    Returns:
  4)
    
    Duplicate File
   Revised 03/05/08
 19




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 D. TESTING PLAN
 Below is a general test plan which should be used only as a guide to what will be expected.
The final test plan will be provided by the bulk provider.
 EDI Transmission Test
  
 Entity Validation Test
 
 
 
 Payments
 
 
 Invalid Debit
   Revised 03/05/08
 20




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 SAMPLE BULK PROVIDER TEST CASES
 FUNCTIONALITY
    
    TEST SCENARIOSFile Transmission Testing
    
    VALID: The bulk provider will send through 1 file with a valid
sender listed on the ISA segment. (NOTE: This will be an entity
validation file with 1 - 5 entity validation requests. This
will only b e used for EDI file transfer testing.)The TFA will return a 997 Functional Acknowledgment to the bulk
provider within 1 hour of receipt of the 838 file. The TFA and
the bulk provider will work together to confirm the results.INVALID: The bulk provider will send through 1 file with an
invalid sender listed on the ISA segment. (NOTE: This will be
an entity validation file with 1 - 5 entity validation
requests. This will only be used for EDI file transfer
testing.)The TFA will return a 997 Functional Acknowledgment to the bulk
provider within 1 hour of receipt of the 838 file. The TFA and
the bulk provider will work together to confirm the results.Valid Entity Validation
X12 Format (Syntax)
    
    The bulk provider will send a file to the TFA. This file will be
used to verify that the format of the entity validation file
mirrors the EFTPS EDI trading partner profile standards. The
TFA will check the following (but not limited to) on the 838
Entity Validation and 997 Functional Acknowledgment Files:Proper Enveloping:Content format of ISA and IEA SegmentsContent format of GS and GE SegmentsContent format of ST and SE SegmentsBulk Provider TINFile Creation Date / TimeBulk Provider Name / Telephone NumberTaxpayer Name / TINInvalid Entity
    
    The bulk provider will send a second file to the TFA. This file
 Revised 03/05/08
 21




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 FUNCTIONALITY
    
    TEST SCENARIOSValidation X12 Format
(Syntax)
    
    will contain errors with the format of the
file in order for the TFA to send the bulk
provider a REJECTED 997 Functional
Acknowledgment. The TFA will check the
following (but not limited to) on the 838
Entity Validation:Improper Enveloping or X12 Format Errors:Content format of ISA and IEA SegmentsContent format of GS and GE SegmentsContent format of ST and SE SegmentsValid Entity Validation
    
    The bulk provider will create an 838 Entity
Validation file with 50 taxpayers. Place at
least 5 Entity Validation requests containing
primary/secondary names on the file.The TFA will return a 997 Functional
Acknowledgment to the bulk provider within 24
hours of receipt of the 838.Valid Entity Validation
    
    The TFA will return an 824 Application Advice
to the bulk provider within 3 days of receipt
of the 838.(continued)The bulk provider will return a 997
Functional Acknowledgment to the TFA within 1
hour of receipt of the 824.Invalid Entity
Validation
    
    The bulk provider will create an invalid
838 Entity Validation file with 50 taxpayers.
Please be sure to include the following
invalid TINs:Blank TIN (Element N101 should be left blank)999999999345A24436The TFA will return a 997 Functional
Acknowledgment to the bulk provider within 24
hours of receipt of the 838.The TFA will return an 824 Application Advice
to the bulk provider within 3 days of receipt
of the Entity validation file.The bulk provider will return a 997
Functional Acknowledgment to the TFA within 1
hour of the 824.
 Revised 03/05/08
 22




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 FUNCTIONALITY
    
    TEST SCENARIOSOn DAY 2 the TFA will return an 824 (reject) Application
Advice to the bulk provider. This 824 will be the rejection file
containing all invalid TINs.Conditional
Testing
    
    The bulk provider will return a 997 Functional Acknowledgment to the TFA within 1 hour of receipt of the 824. The bulk provider
will send an Entity Validation file to the TFA containing at
least 50% of your largest Entity Validation file.Entity
Validation Volume TestingThe TFA will return a 997 Functional Acknowledgment to the bulk
provider within 24 hours of receipt of the 838.The TFA will return an 824 Application Advice to the bulk
provider within 3 days of receipt of the 838.The bulk provider will return a 997 Functional Acknowledgment to
the TFA within 1 hour of receipt of the 824.Valid Bulk ACH Debit
Format (Syntax)
    
    The bulk provider will send 2 files to the TFA. This file will be
used to verify that the format of the BULK ACH debit files
mirror the EFTPS EDI trading partner profile standards. The TFA
will check the following (but not limited to) on the 813 Tax
Payment and 997 Functional Acknowledgment files:Proper Enveloping:Content format of ISA and IEA SegmentsContent format of GS and GE SegmentsContent format of ST and SE SegmentsReference InformationFile Creation DateDate Sent to TFADollar AmountPayment MethodPayment / Account InformationSettlement DateTax Form InformationTaxpayer TIN
 Revised 03/05/08
 23




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 FUNCTIONALITY
    
    
    
    
    
TEST SCENARIOSTax Period DateInvalid Bulk ACHDebit Format (Syntax)
    
    The bulk provider will send 2 additional
files to the TFA. This file will contain
errors with the format of the file in order
for the TFA to send the bulk provider a
REJECTED 997 Functional Acknowledgment. The
TFA will check the following (but not limited
to) on the 813 Entity Validation:Proper Enveloping:Content format of ISA and IEA SegmentsContent format of GS and GE SegmentsContent format of ST and SE SegmentsReference InformationFile Creation DateDate Sent to the TFADollar AmountPayment MethodPayment / Account InformationSettlement DateTax Form InformationTaxpayer TINTax Period DateValid ACH Debits
    
    The bulk provider will send a file of 50
payments. Be sure the transaction sets range
from $.01 - $99,999.999.99 using various
dollar amounts and cents.The TFA will return a 997 Functional
Acknowledgment to the bulk provider within 1
hour of receipt of the 813 Tax Payment.The TFA will return a 151 Electronic Filing
of Tax Return Data Acknowledgment to the bulk
provider within 3 hours of receipt of the
813 Tax Payment.The bulk provider will send the TFA a 997
Functional Acknowledgment within 1 hour of
receipt of the 151.Invalid ACH Debits
    
    The bulk provider will send a file of 50
payments. Include the following TINs:
 Revised 03/05/08
 24




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 FUNCTIONALITY
    
    TEST SCENARIOS00000000034533ABCD410700000345558219 (valid TIN but unenrolled)452782525, tax type 941a (invalid tax type)345251872 (this will be returned as NSF)Be sure the transaction sets range from $.01 - $99,999.999.99 using
various dollar amounts and cents with one transaction set for
$100,000,000.00.The TFA will return a 997 Functional Acknowledgment to the bulk provider
within 1 hour of receipt of the 813 Tax Payment.Invalid ACH Debits(continued)
    
    The TFA will return a 151 Electronic Filing of Tax Return Data
Acknowledgment within 3 hours of receipt of the 813 Tax Payment. This file
will include the invalid TINs and the valid TIN with the invalid tax type.The bulk provider will send the TFA a 997 Functional
Acknowledgment within 1 hour of receipt of the 151.Payment Return  Part I
    
    The TFA will send the bulk provider an 827 Financial Return Notice for TIN
345251872 that was used in the invalid ACH debit test case. This will be
returned as NSF. (The payment reversal will occur on DAY 2).The bulk provider will send a 997 Functional Acknowledgment to the TFA
within 1 hour of receipt of the 827.Conditional Testing
ACH Bulk
Debit Volume
Testing
    
    The bulk provider will send a debit file reflecting 50% of the expected high volume day. This file will run through as a normal ACH debit.The TFA will return a 997 Functional Acknowledgment to the bulk provider
within 1 hour of receipt of the 813.The TFA will return a 151 Electronic Filing of Tax Return Data
Acknowledgment within 3 hours of receipt of the 813.
 Revised 03/05/08
 25




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 FUNCTIONALITY
    
    TEST SCENARIOSThe bulk provider will send the TFA a 997 Functional
Acknowledgment within 1 hour of receipt of the 151.Conditional Testing
Bulk Debit
Transaction
Set Limit
    
    The bulk provider will send the TFA a bulk debit file with at least 1 transaction set with at least 1001 transactions.The TFA will return a 997 Functional Acknowledgment to the bulk
provider within 1 hour of receipt of the 813.The TFA will return a REJECTION 151 Electronic Filing of Tax Return
Data Acknowledgment within 3 hours of receipt of the 813.The bulk provider will send the TFA a 997 Functional Acknowledgment
within 1 hour of receipt of the 151.Conditional Testing
    
    The bulk provider will send a debit file with 21 (813) transaction sets.File LimitsThe TFA will return a 997 Functional Acknowledgment to the bulk
provider within 1 hour of receipt of the 813.The TFA will return a REJECTION 151 Electronic Filing of Tax Return
Data Acknowledgment within 3 hours of receipt of the 813.The bulk provider will send the TFA a 997 Functional Acknowledgment
within 1 hour of receipt of the 151.Conditional Testing
    
    The bulk provider will send the debit file used in the Valid ACH debit
scenario. Change ONLY the settlement date. Do not make any changes to
the ISA or GS control numbers.Duplicate FileThe bulk provider will receive a NEGATIVE 997 Functional
Acknowledgment from the TFA within 1 hour of receipt of the
813.
 Revised 03/05/08
 26




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 NOTES
   Other Optional Test Scenarios:
  
    
    Bulk Provider sends 813 file containing at least 1 ST with at least 2 payment records (1
payment with tax type code 10401 and another with code 10402) and a tax period end date (TFS
segment, TFS07 element) other than the current year  1.
    
    TFA returns an accepted 997 along with a 151 file containing rejected acknowledgement type
and error code. Notice that all STs on the file (ISA) are rejected with error code 1104.
    
    Bulk Provider returns an accepted 997.
  
    
    Bulk Provider sends 813 file containing at least 1 ST and 1 payment with tax type code
10402 and the Credit Card Authorization Date (DTM segment w/in the TFS Loop, DTM02 element)
after 06/30/xx.
    
    TFA returns an accepted 997 along with a 151 file containing rejected acknowledgement type
and error code. Notice that all STs on the file (ISA) are rejected with error code 1104.
    
    Bulk Provider returns an accepted 997.
  
    
    Bulk Provider sends an 813 file including at least 1 ST and one payment record
    
    TFA processes the 813 file and sends back a 151 confirmation file to the Bulk Provider.
    
    Bulk Provider returns an accepted 997 in response to the 151 confirmation file.
    
    TFA returns an accepted 997 acknowledgment (for the 813 payment file) to the Bulk
Provider.
 Revised 03/05/08
 27




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
  
    
    Bulk Provider sends 1 Entity Validation file with at least two (2) 838 transaction sets
(STs)
    
    TFA returns an accepted 997 and validates Entity Validation requests with IRS (simulated)
    
    TFA creates two (2) confirmation files, each containing an 824 ST that confirms each 838 ST
and returns to Bulk Provider (Note: Based upon the timing of the 838 transaction sets that are
sent will determine if the 824 sets are on one file or multiple files.)
    
    Bulk Provider returns an accepted 997 in response to the 824 confirmation file.
    
    Bulk Provider sends an 813 file with all validated Entity Validation requests.
    
    TFA returns a 997 acknowledging the 813 and also a 151 confirmation file to the Bulk
Provider.
    
    Bulk Provider returns an accepted 997 in response to the 151 confirmation file. No
duplicate payment file is generated and/or sent by the Bulk Provider.
 Revised 03/05/08
 28




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 3.
    
    TELECOMMUNICATIONS CONCERNS
 A.
    
    Data Transmission Specifications1.
    
    Communications Protocol
  2.
    
    Line Service
  3.
    
    Initiation Function
  4.
    
    Common Carrier Interface
  5.
    
    Line Type
  6.
    
    Transmission Speeds
  7.
    
    Security: Identification-Authentication-Encryption
   8.
    
    Value Added Networks (VAN)
  Revised 03/05/08
 29




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 B. Telecommunications Set-Up
 Vendor NameInitiation FunctionCommunication ProtocolsLine TypeCredit Card Bulk Provider:IP Address
    
    To be provided by the FALine SpeedNumber of Locations
 Debit Payments
 Transmission Frequency
    

DailyTransmission VolumeWednesdayFriday15th of MonthQuarter EndTransmission Times
 Entity
Validation Files (Only for Processors who are contacted directly by
the taxpayer)
 Conversion VolumeTransmission FrequencyTransmission VolumeTransmission Times
 Revised 03/05/08
 30




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 C. Disaster Recovery
 Treasury Financial Agent (TFA)
  Revised 03/05/08
 31




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 D. Bulk Provider Disaster Recovery Plan
 
    
    High level description of Disaster Recovery Plan as it impacts EFTPS
    
    Do you have a back-up modem at primary site?
    
    Is there a back-up site (Hot back-up or Cold start)?
    
    How long is the outage before moving to back-up site?
    
    How will the TFA be notified to dial the back-up site or back-up modem?
    
    Who is the primary contact?
    
    Back-up Site
    
    Where is the back-up site located (city, state)?
    
    What is the hardware/telecom setup (Is this different from the primary site)?
    
    If hot back-up, are the modems always active?
    
    What are the back-up phone numbers?Disaster Recovery Testing
    
    When can we schedule initial test?
    
    Is periodic testing at the back-up site required? How often?
 Revised 03/05/08
 32




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 4.
    
    EDI Record Formats
 A.
    
    General
 Important notes regarding the following material...
 
    
    Chapters 3, 4, 9 and 10 are extracted from the Implementation Guide for EFTPS Bulk Providers
and edited for credit card processors. Material from the remaining Chapters of the Guide, if
applicable to credit card processing, is included in earlier portions of this document.
    
    All Electronic Data Interchange transaction set layouts in Chapters 3, 4 and 9 are in ANSI
X12 version 003050.
 Revised 03/05/08
 33




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 
  Overview
 Attachments 3A-3C
 Taxpayer Entity Validation Process
   Step 
 
    
    The taxpayer authorizes the credit card processor/bulk provider to process
the payment and to exchange information with the IRS necessary to process the
payment.
 Step

 
    
    The credit card processor/bulk provider transmits an entity validation file
to the TFA. The format is ANSI X12 EDI 838-transaction set. Each
838-transaction set is limited to a maximum of 1,000 Entity Validation
requests.
    
    Within one hour after receipt of entity validation file, the TFA will send
the Credit Card Bulk Provider an acknowledgment of receipt of file. The format
for the acknowledgment is ANSI X12 EDI 997-transaction set.
 Revised 03/05/08
 34




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 
 Step

 
    
    The Treasury Financial Agent exchanges an entity file with the IRS. The
entity file will include only the critical fields of data collected from the
bulk provider, including the taxpayers SSN.
 Step

 
    
    After the TFA receives the entity validation file from the IRS, the TFA
notifies the bulk provider about acceptance or rejection of taxpayer Entity
Validation requests. The acceptance file will contain the name control and ZIP
code (may be present) of approved taxpayers. Rejected Entity Validation
requests will include a reason code. The format is ANSI the X12 EDI
824-transactionset. Process the IRS entity validation files whether a zip code is supplied or not (where the zip is blank ). If the zip code field is received blank, the FA shall create the EDI 824 enrollment confirmation transaction set. The EDI 824 REF03 element will be blank and sent back to the Credit Card Processor without a zip code. For EDI 813 payments, the FA will not reject the payment transaction set if the zip code field is blank (Again, the REF03 element will be blank on the 813).
    
    Within one hour after receipt of receipt of this file, the bulk provider
will return the TFA an acknowledgment of receipt of file to the TFA. The
format is ANSI X12 EDI 997-transaction set.
 Revised 03/05/08
 35




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 TRANSACTION SET 838
 TRADING PARTNER PROFILE
 VERSION 003050
 SEND FROM BULK PROVIDER
 REQUEST FOR ENTITY VALIDATION
 ATTACHMENT 3A
 838  TRADING PARTNER PROFILE
 Revised 03/05/08
 36




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 VERSION 003050
 REQUEST FOR ENTITY VALIDATION SENT FROM BULK PROVIDER
 TABLE
3A-1
 SEG. ID
    
    NAME
    
    REQ. DES.
    
    MAX. USE
    
    
    LOOP REPEATST
    
    Transaction Set Header
    
    M
    
 1BTP
    
    Beginning Segment for Trading Partner Profile
    
    M
    
 1PER
    
    Administrative Communications Contact
    
    O
    
 1LOOP ID - LX
    
    
    
 
    
    
 >1LX
    
    Assigned Number
    
    O
    
 1LOOP ID - N1
    
    
    
 
    
    
 >1N1
    
    Name
    
    O
    
 1N9
    
    Reference Number
    
    O
    
 >1SE
    
    Transaction Set Trailer
    
    M
    
 1
 
 
 Revised 03/05/08
 37




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 838  TRADING PARTNER PROFILE
VERSION 003050
 ST SEGMENT
TRANSACTION SET HEADER
 TABLE 3A-2
 REF.
    
    
    
    Req.
    
    Elem.
    
    Elem.Element
    
    Number
    
    Name
    
    Desig.
    
    Type
    
    Length
    
    CommentsST01
    
    
    143
    
    
    Transaction Set Identifier Code
    
    MIZ
    
    ID
    
    3/3
    
    838ST02
    
    
    329
    
    
    Transaction Set Control Number
    
    M
    
    AN
    
    4/9
     Revised 03/05/08
 38




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 838  TRADING PARTNER PROFILE
VERSION 003050
 BTP SEGMENT
BEGINNING SEGMENT FOR TRADING PARTNER PROFILE
 TABLE 3A-3
 REF
    
    
    
    Req.
    
    Elem
    
    ElemElement
    
    Number
    
    Name
    
    Desig
    
    Type
    
    Length
    
    CommentsBTP01
    
    
    353
    
    
    Transaction Set Purpose Code
    
    MIZ
    
    ID
    
    2/2
    
    35 Request AuthorityBTP02
    
    
    127
    
    
    Reference Number
    
    MIZ
    
    AN
    
    1/30
    
    To be provided by the TFABTP03
    
    
    373
    
    
    Date
    
    MIZ
    
    DT
    
    6/6
    
    (YYMMDD)BTP04
    
    
    337
    
    
    Time
    
    M
    
    TM
    
    4/8
    
    (HHMM)BTP05
    
    
    640
    
    
    Transaction Type Code
    
    M
    
    ID
    
    2/2
    
    S4 SubmissionBTP06
    
    
    353
    
    
    Transaction Set Purpose Code
    
    OIZ
    
    ID
    
    2/2
    
    00 (Original)BTP07
    
    
    127
    
    
    Reference Number
    
    XIZ
    
    AN
    
    1/30
    
    CREDIT CARDBTP08
    
    
    373
    
    
    Date
    
    XIZ
    
    DT
    
    6/6
    
    Not UsedBTP09
    
    
    337
    
    
    Time
    
    O
    
    TM
    
    4/8
    
    Not UsedBTP10
    
    
    591
    
    
    Payment Method Code
    
    O
    
    ID
    
    3/3
    
    Not Used
        Revised 03/05/08
 39




---



##### 



2009 Credit Card Bulk Provider Requirements
 838  TRADING PARTNER PROFILE
VERSION 003050
 PER SEGMENT
ADMINISTRATIVE COMMUNICATIONS CONTACT
 TABLE 3A-4
 REF.
    
    
    
    Req.
    
    Elem.
    
    Elem.Element
    
    Number
    
    Name
    
    Desig.
    
    Type
    
    Length
    
    CommentsPER01
    
    
    366
    
    
    Contact Function Code
    
    M
    
    ID
    
    2/2
    
    AA Authorized
RepresentativePER02
    
    
    93
    
    
    Name
    
    O
    
    AN
    
    1/35PER03
    
    
    365
    
    
    Communication Number Qualifier
    
    X
    
    ID
    
    2/2
    
    TEPER04
    
    
    364
    
    
    Communication Number
    
    X
    
    AN
    
    1/80
 
 
 Revised 03/05/08
 40




---



##### 



2009 Credit Card Bulk Provider Requirements
 838  TRADING PARTNER PROFILE
VERSION 003050
 LOOP ID  LX
LX SEGMENT
ASSIGNED NUMBER
 TABLE 3A-5
 Req.
    
    ElemElement
    
    REF Number
    
    Name
    
    Desig.
    
    Type
    
    Elem.Length
    
    CommentsLX01
    
    
    554
    
    
    Assigned Number
    
    M
    
    NO
    
    1/6
    
 
 Revised 03/05/08
 41




---



##### 



2009 Credit Card Bulk Provider Requirements
 838  TRADING PARTNER PROFILE
VERSION 003050
 LOOP ID  N1
N1 SEGMENT
NAME
 TABLE 3A-6
 REF.
    
    
    
    Req.
    
    Elem.
    
    Elem.Element
    
    Number
    
    Name
    
    Desig
    
    Type
    
    Length
    
    CommentsN101
    
    
    98
    
    
    Entity Identifier Code
    
    M
    
    ID
    
    2/2
    
    TP Primary TaxpayerN102
    
    
    93
    
    
    Name
    
    X
    
    AN
    
    1/35
    
    SpaceN103
    
    
    66
    
    
    Identification Code
    
    X
    
    ID
    
    1/2
    
    24 Employer Identification
Number, or
34 Social Security NumberN104
    
    
    67
    
    
    Identification Code
    
    X
    
    ID
    
    2/20
    
    EIN or SSNN105
    
    
    706
    
    
    Entity Relationship Code
    
    O
    
    ID
    
    2/2
    
    Not UsedN106
    
    
    98
    
    
    Entity Identifier Code
    
    O
    
    ID
    
    2/2
    
    Not Used
    
  
 Revised 03/05/08
 42




---



##### 



2009 Credit Card Bulk Provider Requirements
 838  TRADING PARTNER PROFILE
VERSION 003050
 LOOP ID  N1
N9 SEGMENT
REFERENCE NUMBER
 TABLE 3A-7
 REF.
    
    
    
    Req.
    
    Elem.
    
    Elem.Element
    
    Number
    
    Name
    
    Desig
    
    Type
    
    Length
    
    CommentsN901
    
    
    128
    
    
    Reference Number Qualifier
    
    M
    
    ID
    
    2/2
    
    VU PreparersVerification NumberN902
    
    
    127
    
    
    Reference Number
    
    X
    
    AN
    
    1/30
    
    8655N903
    
    
    369
    
    
    Free-Form Description
    
    X
    
    AN
    
    1/45
    
    Not UsedN904
    
    
    373
    
    
    Date
    
    O
    
    DT
    
    6/6
    
    Not UsedN905
    
    
    337
    
    
    Time
    
    X
    
    TM
    
    4/8
    
    Not UsedN906
    
    
    623
    
    
    Time Code
    
    OIZ
    
    ID
    
    2/2
    
    Not Used
    Revised 03/05/08
 43




---



##### 



2009 Credit Card Bulk Provider Requirements
 838  TRADING PARTNER PROFILE
VERSION 003050
 SE SEGMENT
TRANSACTION SET TRAILER
 TABLE 3A-8
 REF.
    
    
    
    Req.
    
    Elem.
    
    Elem.Element
    
    Number
    
    Name
    
    Desig.
    
    Type
    
    Length
    
    CommentsSE01
    
    
    96
    
    
    Number of Segments Included
    
    M
    
    NO
    
    1/10SE02
    
    
    329
    
    
    Transaction Set Control Number
    
    M
    
    AN
    
    4/9
    Revised 03/05/08
 44




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 TRANSACTION SET 997
 FUNCTIONAL ACKNOWLEDGMENT
 VERSION 003050
 ATTACHMENT 3B
 Revised 03/05/08
 45




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 997  FUNCTIONAL ACKNOWLEDGMENT
VERSION 003050
 TABLE 3B-1
 SEG.
    
    
    
    REQ.
    
    MAX.
    
    LOOPID
    
    NAME
    
    DES
    
    USE
    
    REPEATST
    
    Transaction Set Header
    
    M
    
    
    1AK1
    
    Functional Group Response Header
    
    M
    
    
    1LOOP  ID AK2
    
    
    
    
    
    
    
    
    999999AK2
    
    Transaction Set Response Header
    
    O
    
    
    1AK5
    
    Transaction Set Response Trailer
    
    M
    
    
    1AK9
    
    Functional Group Response Trailer
    
    M
    
    
    1SE
    
    Transaction Set Trailer
    
    M
    
    
    1
 Revised 03/05/08
 46




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 997  FUNCTIONAL ACKNOWLEDGMENT
VERSION 003050
 ST SEGMENT
TRANSACTION SET HEADER
 TABLE 3B-2
 REF
    
    
    
    Req.
    
    Elem.
    
    Elem.Element
    
    Number
    
    Name
    
    Desig.
    
    Type
    
    Length
    
    CommentsST01
    
    
    143
    
    
    Transaction Set Identifier Code
    
    MIZ
    
    ID
    
    3/3
    
    997ST02
    
    
    329
    
    
    Transaction Set Control Number
    
    M
    
    AN
    
    4/9
     Revised 03/05/08
 47




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 997  FUNCTIONAL ACKNOWLEDGMENT
VERSION 003050
 AK1 SEGMENT
FUNCTIONAL GROUP RESPONSE HEADER
 TABLE 3B-3
 REF.
    
    
    
    Req.
    
    Elem
    
    Elem.Element
    
    Num.
    
    Name
    
    Desig
    
    Type
    
    Length
    
    CommentsAK101
    
    
    479
    
    
    Functional
    
    MIZ
    
    ID
    
    2/2
    
    AG Application Advice (824)Identifier
    
    
    
    
    
    
    
    FR Financial Reporting (827)Code
    
    
    
    
    
    
    
    TA Elec. Filing of Tax Return Data Ack. (151)TD Trading Partner Profile (838)TF Elec. Filing of Tax Return Data (813)TI Tax Information Reporting (826)AK102
    
    
    28
    
    
    Group Control
Number
    
    MIZ
    
    N0
    
    1/9
     Revised 03/05/08
 48




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 997  FUNCTIONAL ACKNOWLEDGMENT
VERSION 003050
 LOOP ID  AK2
AK2 SEGMENT
TRANSACTION SET RESPONSE HEADER
 TABLE 3B-4
 REF.
    
    
    
    Req.
    
    Elem.
    
    Elem.Element
    
    Number
    
    Name
    
    Desig.
    
    Type
    
    Length
    
    CommentsAK201
    
    
    143
    
    
    Trans. Set Identifier
Code
    
    MIZ
    
    ID
    
    3/3
    
    824 Application Advice827 Financial Reporting151 Elec. Filing of Tax Return
Data Ack.838 Trading Partner Profile813 Elec. Filing of Tax Return
Data826 Tax Information
ReportingAK202
    
    
    329
    
    
    Trans. Set Control
Number
    
    MIZ
    
    AN
    
    4/9
    
    From Trans. Set Identifier Code
being acknowledged.ST segment, element ST02
   Revised 03/05/08
 49




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 997  FUNCTIONAL ACKNOWLEDGMENT
VERSION 003050
 LOOP ID  AK2
AK5 SEGMENT
TRANSACTION SET RESPONSE TRAILER
 TABLE 3B-5
 REF.
    
    
    
    Req.
    
    Elem.
    
    Elem.Element
    
    Number
    
    Name
    
    Desig
    
    Type
    
    Length
    
    CommentsAK501
    
    
    717
    
    
    Transaction Set Ackn. Code
    
    M
    
    ID
    
    1/1
    
    A AcceptedR RejectedAK502
    
    
    718
    
    
    Transaction Set Syntax Error Cd
    
    O
    
    ID
    
    1/3
    
    Not UsedAK503
    
    
    718
    
    
    Transaction Set Syntax Error Cd
    
    O
    
    ID
    
    1/3
    
    Not UsedAK504
    
    
    718
    
    
    Transaction Set Syntax Error Cd
    
    O
    
    ID
    
    1/3
    
    Not UsedAK505
    
    
    718
    
    
    Transaction Set Syntax Error Cd
    
    O
    
    ID
    
    1/3
    
    Not UsedAK506
    
    
    718
    
    
    Transaction Set Syntax Error Cd
    
    O
    
    ID
    
    1/3
    
    Not Used
   Revised 03/05/08
 50




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk
Provider Requirements
 997
 FUNCTIONAL ACKNOWLEDGMENT 
VERSION 003050
 AK9
SEGMENT
FUNCTIONAL GROUP RESPONSE TRAILER
 TABLE 3B-6
 REF.
    
    
    
    Req.
    
    Elem.
    
    Elem.Element
    
    Number
    
    Name
    
    Desig.
    
    Type
    
    Length
    
    CommentsAK901
    
    
    715
    
    
    Functional Group Acknow Code
    
    M
    
    ID
    
    1/1
    
    A AcceptedR RejectedAK902
    
    
    97
    
    
    Number of Trans. Sets Included
    
    M
    
    N0
    
    1/6AK903
    
    
    123
    
    
    Number of Trans. Sets Received
    
    M
    
    N0
    
    1/6AK904
    
    
    2
    
    
    Number of Accepted Tran Sets
    
    M
    
    N0
    
    1/6AK906
    
    
    716
    
    
    Functional Group Syntax Error
    
    O
    
    ID
    
    1/3
    
    Not UsedAK907
    
    
    716
    
    
    Functional Group Syntax Error
    
    O
    
    ID
    
    1/3
    
    Not UsedAK908
    
    
    716
    
    
    Functional Group Syntax Error
    
    O
    
    ID
    
    1/3
    
    Not UsedAK909
    
    
    716
    
    
    Functional Group Syntax Error
    
    O
    
    ID
    
    1/3
    
    Not Used
   Revised 03/05/08
 51




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 997  FUNCTIONAL ACKNOWLEDGMENT
VERSION 003050
 SE SEGMENT
TRANSACTION SET TRAILER
 TABLE 3B-7
 REF.
    
    
    
    Req.
    
    Elem.
    
    Elem.Element
    
    Number
    
    Name
    
    Desig
    
    Type
    
    Length
    
    CommentsSE01
    
    
    96
    
    
    Number of Included Segments
    
    M
    
    No
    
    1/10SE02
    
    
    329
    
    
    Transaction Set Control Number
    
    M
    
    AN
    
    4/9
    
    From ST Segment
of 997 element
ST02
   Revised 03/05/08
 52




---



##### 



(EFTPS LOGO)
    
    Attachment 3, Appendix B2009 Credit Card Bulk Provider Requirements
 TRANSACTION SET 824
 APPLICATION ADVICE
 VERSION 003050
 SEND FROM TFA
 CONFIRM/REJECT ENTITY REQUEST
 ATTACHMENT 3C
 Revised 03/05/08
 53




---



##### 



(EFTPS LOGO)
    
    Attachment 3, Appendix B2009 Credit Card Bulk Provider Requirements
 824  APPLICATION ADVICE
VERSION 003050
 TABLE 3C-1
 SEG. ID
    
    NAME
    
    REQ. DES.
    
    MAX. USE
    
    LOOP REPEATST
    
    Transaction Set Header
    
    M
    
    1BGN
    
    Beginning Segment
    
    M
    
    1
 TABLE 3C-2
 SEG. ID
    
    NAME
    
    REQ. DES
    
    MAX. USE
    
    LOOP REPEATLOOP ID  OTI
    
    
    
    
    
    
    
    >1OTI
    
    Original Transaction Identification
    
    O
    
    1REF
    
    Reference Numbers
    
    O
    
    12SE
    
    Transaction Set Trailer
    
    M
    
    1
 Revised 03/05/08
 54




---



##### 



(EFTPS LOGO)
    
    Attachment 3, Appendix B2009 Credit Card Bulk Provider Requirements
 824  APPLICATION ADVICE
VERSION 003050
 ST
TRANSACTION SET HEADER
 TABLE 3C-3
 REF.
    
    
    
    Req.
    
    Elem.
    
    Elem.Element
    
    Number
    
    Name
    
    Desig.
    
    Type
    
    Length
    
    CommentsST01
    
    143
    
    
    
    Transaction Set Identifier Code
    
    MIZ
    
    ID
    
    3/3
    
    824ST02
    
    329
    
    
    
    Transaction Set Control Number
    
    M
    
    AN
    
    4/9
     Revised 03/05/08
 55




---



##### 



(EFTPS LOGO)
    
    Attachment 3, Appendix B2009 Credit Card Bulk Provider Requirements
 824  APPLICATION ADVICE
VERSION 003050
 BGN
BEGINNING SEGMENT
 TABLE 3C-4
 REF.
    
    
    
    Req.
    
    Elem.
    
    Elem.Element
    
    Num.
    
    Name
    
    Desig
    
    Type
    
    Length
    
    CommentsBGN01
    
    
    353
    
    
    Transaction Set Purpose Code
    
    M
    
    ID
    
    
    2/2
    
    
    00 OriginalBGN02
    
    
    127
    
    
    Reference Number
    
    MIZ
    
    AN
    
    
    1/30
    
    
    Assigned by transaction originator.The same as element BGN06BGN03
    
    
    373
    
    
    Date
    
    MIZ
    
    DT
    
    
    6/6
    
    
    YYMMDD Transaction Set DateBGN04
    
    
    337
    
    
    Time
    
    XIZ
    
    TM
    
    
    4/8
    
    
    Not UsedBGN05
    
    
    623
    
    
    Time Code
    
    OIZ
    
    ID
    
    
    2/2
    
    
    Not UsedBGN06
    
    
    127
    
    
    Reference Number
    
    OIZ
    
    AN
    
    
    1/30
    
    
    Control Number from 838s ST02BGN07
    
    
    640
    
    
    Transaction Type Code
    
    O
    
    ID
    
    
    2/2
    
    
    Not UsedBGN08
    
    
    306
    
    
    Action Code
    
    O
    
    ID
    
    
    2
    
    
    CF ConfirmU Reject
     Example:
   All Accepted:
    
    BGN~00~567898~061115~~~45678~~CF\Some TINs rejected:
    
    BGN~00~567898~061115~~~45678~~U\
 Revised 03/05/08
 56




---



##### 



(EFTPS LOGO)
    
    Attachment 3, Appendix B2009 Credit Card Bulk Provider Requirements
 824  APPLICATION ADVICE
VERSION 003050
 LOOP ID  OTI
OTI SEGMENT
ORIGINAL TRANSACTION IDENTIFICATION
 TABLE 3C-5
 REF.
    
    
    
    Req.
    
    Elem
    
    Elem.Element
    
    Num.
    
    Name
    
    Desig
    
    Type
    
    Length
    
    CommentsOTI01
    
    
    110
    
    
    Application Acknow. Code
    
    M
    
    ID
    
    
    2
    
    
    IA Item AcceptIR Item RejectOTI02
    
    
    128
    
    
    Reference Number Qualifier
    
    M
    
    ID
    
    
    2/2
    
    
    2I Tracking NumberOTI03
    
    
    127
    
    
    Reference Number
    
    M
    
    AN
    
    
    1/30
    
    
    1 to 6 Digit Number from
LX01 in 838OTI04
    
    
    142
    
    
    Application Senders Code
    
    O
    
    AN
    
    
    2/15
    
    
    Not UsedOTI05
    
    
    124
    
    
    Application Receivers Code
    
    O
    
    AN
    
    
    2/15
    
    
    Not UsedOTI06
    
    
    373
    
    
    Date
    
    OIZ
    
    DT
    
    
    6/6
    
    
    Not UsedOTI07
    
    
    337
    
    
    Time
    
    OIZ
    
    TM
    
    
    4/8
    
    
    Not UsedOTI08
    
    
    28
    
    
    Group Control Number
    
    X
    
    N0
    
    
    1/9
    
    
    Not UsedOTI09
    
    
    329
    
    
    Transaction Set Control Number
    
    O
    
    AN
    
    
    4/9
    
    
    Not UsedOTI10
    
    
    143
    
    
    Transaction Set Identifier Code
    
    O
    
    ID
    
    
    3/3
    
    
    Not UsedOTI11
    
    
    480
    
    
    Version/Release/Industry
    
    OIZ
    
    AN
    
    
    1/12
    
    
    Not Used
  Examples:
    
    Enrollment Reference Number = 999Transaction Set Accepted:
    
    OTI01~IA~2I~999\One Transaction Accepted, One Rejected:
    
    OTI01~IR~2I~999\
 Revised 03/05/08
 57




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 824  APPLICATION ADVICE
VERSION 003050
 LOOP ID  OTI
REF SEGMENT
REFERENCE NUMBERS
 TABLE 3C-6
 REF.
    
    
    
    Req.
    
    Elem
    
    Elem.Element
    
    Num.
    
    Name
    
    Desig
    
    Type
    
    Length
    
    CommentsREF01
    
    
    128
    
    
    Reference Number Qualifier
    
    M
    
    ID
    
    2/2
    
    1Q Error Identification CodeBB Authorization NumberREF02
    
    
    127
    
    
    Reference Number
    
    X
    
    AN
    
    1/30
    
    Name Control for valid TINs;Error Code for invalid TINsREF03
    
    
    352
    
    
    Description
    
    X
    
    AN
    
    1/80
    
    ZIP Code
      Revised 03/05/08
 58




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 824  APPLICATION ADVICE
VERSION 003050
 SE SEGMENT
TRANSACTION SET TRAILER
 TABLE 3C-7
 REF.
    
    
    
    Req.
    
    Elem.
    
    Elem.Element
    
    Number
    
    Name
    
    Desig.
    
    Type
    
    Length
    
    CommentsSE01
    
    
    96
    
    
    Number of Included Segments
    
    M
    
    No
    
    1/10SE02
    
    
    329
    
    
    Transaction Set Control Number
    
    M
    
    AN
    
    4/9
  
  Revised 03/05/08
 59




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
  ACH Bulk Debits (One Debit Posted to Bulk Providers Account)
 Overview
 Attachments 4A-B
 ACH Bulk Debit Process
     Any payment rejects may result in the entire file rejecting back to the Credit Card Bulk
Provider, for additional detail contact the FA.
     Step
 
    
    Taxpayers initiate the credit card payment through the electronic filing
system or by contacting the credit card processor directly.
    
    As part of the credit card approval process, the taxpayer must certify that
the credit card processor is authorized to process the payment and to exchange
information with the IRS necessary to process the payment.
 Revised 03/05/08
 60




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 Step
 
    
    The credit card processor/bulk provider completes a transmission to the TFA
with payment detail. To settle on the next banking date, the file must be
transmitted by 7:00 pm ET. Attachment 4A shows the format for the
ANSI X12 EDI 813-transaction set.
    
    For each 813-transaction set, one bulk debit will be originated.
    
    Each 813-transaction set is limited to a maximum of 1000 transactions.
There is a limit of 50 (fifty) 813-transaction sets to a file, for a maximum
of 50,000 transactions per file.
 Step
 
    
    Within one hour of receipt of the payment file, the TFA will send the bulk
provider an acknowledgment file. Attachment 3B shows the format for
the ANSI X12 EDI 997-transaction set
    
    Upon receipt of the payment file, the TFA will begin the validation and
editing process. The first level of validation is on a file level:
 Ø
    
    Validate that the detail totals to the header record. If the
totals do not equal the TFA rejects the file.
 
    
    The second level of validation is at the transaction set level:
 Ø
    
    Validate for the dollar limit of $99,999,999.99 per
813-transaction set. If the dollar amount is greater than
$99,999,999.99, the TFA rejects the transaction set.Ø
    
    Validate that the tax type for the payment is a valid IRS tax
type. If a tax type is invalid, the TFA rejects the transaction
set.
 All rejects will have to be corrected and retransmitted the TFA.
 
    
    Within three hours of receipt of the payment file, the TFA will
send the bulk provider a confirmation file that provides the detail and status
of each payment record. Attachment 4B shows the format for the ANSI
X12 EDI 151-transaction set.
    
    Within one hour after receipt of receipt of this file, the bulk
provider will return the TFA an acknowledgment of receipt of file to the TFA.
Attachment B shows the format for the ANSI X12 EDI 997-transaction set.
 Revised 03/05/08
 61




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 Step For all files received before 8:00 PM ET step 4 will occur on same day file received.
 
    
    The TFA will initiate an ACH debit to the bulk providers account at the
bulk providers financial institution for each 813-transaction set.
 Step Step 5 & 6 will occur on Bulk Debit Settlement date.
 
    
    The Federal Reserve Bank will deposit the bulk payment into the Treasury
account.
    
    The Federal Reserve Bank will withdrawal the bulk payment from the Credit
Card Bulk Providers Financial Institution and the Financial Institution will
withdrawal the Bulk Payment from the Credit Card Bulk Providers account.
 Step
 
    
    The TFA passes the payment detail to the IRS.
 Revised 03/05/08
 62




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 TRANSACTION SET 813
 ELECTRONIC FILING OF TAX RETURN DATA
 VERSION 003050
 SEND FROM BULK PROVIDER
 TAX PAYMENT
 ATTACHMENT 4A
 Revised 03/05/08
 63




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 813  ELECTRONIC FILING OF TAX RETURN DATA
VERSION 003050
 TABLE 4A-1
 SEG. ID
    
    NAME
    
    REQ. DES.
    
    
    MAX. USE
    
    LOOP REPEATST
    
    Transaction Set Header
    
    M
    
    
    1BTI
    
    Beginning Tax Return
    
    M
    
    
    1DTM
    
    Date/Time Reference
    
    M
    
    
    10TIA
    
    Tax Information
    
    M
    
    
    1000REF
    
    Reference Numbers
    
    O
    

    >1BPR
    
    Beginning Segment for Payment
Order/Remittance Adv
    
    O
    
    
    1000
 Revised 03/05/08
 64




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 813  ELECTRONIC FILING OF TAX RETURN DATA
VERSION 003050
 TABLE 4A-2
 SEG. ID
    
    NAME
    
    REQ. DES.
    
    
    MAX. USE
    
    
    LOOP REPEATLOOP ID  TFS
    
    
    
    
    
    
    
    
    50000TFS
    
    Tax Form
    
    O
    
    
    1REF
    
    Reference Numbers
    
    O
    
    
    10DTM
    
    Date/Time Reference
    
    O
    
    
    10LOOP ID  FGS
    
    
    
    
    
    
    
    
    100000FGS
    
    Form Group
    
    O
    
    
    1LOOP ID  TIA
    
    
    
    
    
    
    
    
    10000TIA
    
    Tax Information and Amount
    
    O
    
    
    1TABLE 4A-3SEG. ID
    
    NAME
    
    REQ. DES.
    
    
    MAX. USE
    
    

LOOP REPEATSE
    
    Transaction Set Trailer
    
    M
    
    
    1
 
 Revised 03/05/08
 65




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 813  ELECTRONIC FILING OF TAX RETURN DATA
VERSION 003050
 ST SEGMENT
TRANSACTION SET HEADER
 TABLE 4A-4
 Ref.
    
    
    
    
    
    Elem
    
    Elem.Element
    
    Num.
    
    Name
    
    Req. Design.
    
    Type
    
    Length
    
    CommentsST01
    
    
    143
    
    
    Transaction Set Identifier Code
    
    MIZ
    
    ID
    
    3/3
    
    813ST02
    
    
    329
    
    
    Transaction Set Control Number
    
    M
    
    AN
    
    4/9
 
   Revised 03/05/08
 66




---



##### 



(IMAGE)
    
    2009 Credit Card Bulk Provider Requirements
 813  ELECTRONIC FILING OF TAX RETURN DATA
VERSION 003050
 BTI SEGMENT
BEGINNING TAX SEGMENT
 TABLE 4A-5
 Ref.
    
    
    
    Req.
    
    Elem
    
    Elem.Element
    
    Num.
    
    Name
    
    Design.
    
    Type
    
    Length
    
    CommentsBTI01
    

    128
    
    
    Reference Number Qualifier
    
    MIZ
    
    ID
    
    2/2
    
    T6 Tax FilingBTI02
    
127
    
    
    Reference Number
    
    M
    
    AN
    
    1/30
    
    EFTPSBTI03
    
66
    
    
    Identification Code Qualifier
    
    MIZ
    
    ID
    
    2/2
    
    47 Tax Authority
IdentificationBTI04
    
67
    
    
    Identification Code
    
    M
    
    AN
    
    2/20
    
    IRSBTI05
    
373
    
    
    Date
    
    OIZ
    
    DT
    
    6/6BTI06
    
818
    
    
    Name Control Identifier
    
    O
    
    AN
    
    4/4
    
    Not UsedBTI07
    
66
    
    
    Identification Code Qualifier
    
    MIZ
    
    ID
    
    1/2
    
    48 Electronic Filer
Identification Number (EFIN)BTI08
    
67
    
    
    Identification Code
    
    X
    
    AN
    
    2/20
    
    Assigned by the TFABTI09
    
66
    
    
    Identification Code Qualifier
    
    XIZ
    
    ID
    
    1/2
    
    ZZBTI10
    
67
    
    
    Identification Code
    
    X
    
    AN
    
    2/20
    
    CREDIT CARDBTI11
    
66
    
    
    Identification Code Qualifier
    
    X
    
    ID
    
    1/2
    
    Not UsedBTI12
    
67
    
    
    Identification Code
    
    X
    
    AN
    
    2/20
    
    Not Used
 
 Example:
    
    ID Code-=999999999, File Creation Date = April 10, 2006BTI~T6~EFTPS~47~IRS~060410~~48~999999999~ZZ~CREDIT CARD\
 Revised 03/05/08
 67




---



##### 



(IMAGE)
    
    2009 Credit Card Bulk Provider Requirements
 813  ELECTRONIC FILING OF TAX RETURN DATA
VERSION 003050
 DTM SEGMENT
DATE/TIME REFERENCE
 TABLE 4A-6
 Ref.
    
    
    
    Req.
    
    Elem.
    
    Elem.Element
    
    Num.
    
    Name
    
    Design.
    
    Type
    
    Length
    
    CommentsDTM01
    
    374
    
    
    Date/Time Qualifier
    
    M
    
    ID
    
    3/3
    
    009 Process DateDTM02
    
    373
    
    
    Date
    
    X
    
    DT
    
    6/6
  Example:DTM~009~060411\
 Revised 03/05/08
 68




---



##### 



(IMAGE)
    
    2009 Credit Card Bulk Provider Requirements
 813  ELECTRONIC FILING OF TAX RETURN DATA
VERSION 003050
 TIA SEGMENT
TAX INFORMATION AND AMOUNT
 TABLE 4A-7
 Ref.
    
    
    
    Req.
    
    Elem
    
    Elem.Element
    
    Num.
    
    Name
    
    Design
    
    Type
    
    Length
    
    CommentsTIA01
    
    817
    
    
    Tax Information Identification Number
    
    M
    
    AN
    
    1/30
    
    EFTPSTIA02
    
    782
    
    
    Monetary Amount
    
    X
    
    R
    
    1/15
    
    (Element length limit is 10)TIA03
    
    449
    
    
    Fixed Format Information
    
    XIZ
    
    AN
    
    1/80
    
    Not UsedTIA04
    
    380
    
    
    Quantity
    
    X
    
    R
    
    1/15
    
    Not UsedTIA05
    
    355
    
    
    Unit or Basis for Measurement Code
    
    X
    
    ID
    
    2/2
    
    Not UsedTIA06
    
    954
    
    
    Percent
    
    X
    
    R
    
    1/10
    
    Not UsedTIA07
    
    782
    
    
    Monetary Amount
    
    XIZ
    
    R
    
    1/15
    
    Not Used
     Revised 03/05/08
 69




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 813  ELECTRONIC FILING OF TAX RETURN DATA
VERSION 003050
 REF SEGMENT
REFERENCE NUMBERS
 TABLE 4A-8
 Ref.
    
    
    
    Req.
    
    Elem
    
    Elem.Element
    
    Num.
    
    Name
    
    Design
    
    Type
    
    Length
    
    CommentsREF01
    
    128
    
    Reference Number Qualifier
    
    M
    
    ID
    
    2/2
    
    VU Preparers Verification
NumberREF02
    
    127
    
    Reference Number
    
    X
    
    AN
    
    1/30
    
    8655 (REF01 of VU)
     Revised 03/05/08
 70




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 813  ELECTRONIC FILING OF TAX RETURN DATA
VERSION 003050
 BPR SEGMENT
BEGINNING SEGMENT FOR PAYMENT ORDER/REMITTANCE ADVICE
 TABLE 4A-9
 Ref.
    
    
    
    Req.
    
    Elem
    
    Elem.Element
    
    Num
    
    Name
    
    Design
    
    Type
    
    Length
    
    CommentsBPR01
    
    305
    
    Transaction Handling Code
    
    M
    
    ID
    
    1/2
    
    Z Bulk DebitBPR02
    
    782
    
    Monetary Amount
    
    MIZ
    
    R
    
    1/15
    
    (Element length limit is 10)BPR03
    
    478
    
    Credit/Debit Flag
    
    M
    
    ID
    
    1/1
    
    D DebitBPR04
    
    591
    
    Payment Method Code
    
    M
    
    ID
    
    3/3
    
    ACH Automated Clearing HouseBPR05
    
    812
    
    Payment Format Code
    
    O
    
    ID
    
    1/10
    
    Not UsedBPR06
    
    506
    
    (DFI) ID Number Qualifier
    
    XIZ
    
    ID
    
    2/2
    
    Not UsedBPR07
    
    507
    
    (DFI) Identification Number
    
    X
    
    AN
    
    3/12
    
    Not UsedBPR08
    
    569
    
    Account Number Qualifier
    
    OIZ
    
    ID
    
    1/3
    
    Not UsedBPR09
    
    508
    
    Account Number
    
    X
    
    AN
    
    1/35
    
    Not UsedBPR10
    
    509
    
    Originating Company Identifier
    
    O
    
    AN
    
    10/10
    
    Not UsedBPR11
    
    510
    
    Originating Co. Supplemental Code
    
    O
    
    AN
    
    9/9
    
    Not UsedBPR12
    
    506
    
    (DFI) ID Number Qualifier
    
    XIZ
    
    ID
    
    2/2
    
    01 ABA Transit Routing # with Check Digits(9)BPR13
    
    507
    
    (DFI) Identification Number
    
    X
    
    AN
    
    3/12
    
    (9 digit RTN Number)BPR14
    
    569
    
    Account Number Qualifier
    
    OIZ
    
    ID
    
    1/3
    
    03 Checking AccountSG SavingsBPR15
    
    508
    
    Account Number
    
    XIZ
    
    AN
    
    1/35
    
    (Account Number)
 Revised
03/05/08
 71




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 Ref.
    
    
    
    Req.
    
    Elem
    
    Elem.Element
    
    Num
    
    Name
    
    Design
    
    Type
    
    Length
    
    CommentsSettlementBPR16
    
    373
    
    Date
    
    OIZ
    
    DT
    
    6/6
    
    Date(YYMMDD)BPR17
    
    1048
    
    Business Function Code
    
    OIZ
    
    ID
    
    1/3
    
    Not UsedBPR18
    
    506
    
    (DFI) ID Number Qualifier
    
    XIZ
    
    ID
    
    2/2
    
    Not UsedBPR19
    
    507
    
    (DFI) Identification Number
    
    X
    
    AN
    
    3/12
    
    Not UsedBPR20
    
    569
    
    Account Number Qualifier
    
    OIZ
    
    ID
    
    1/3
    
    Not UsedBPR21
    
    508
    
    Account Number
    
    XIZ
    
    AN
    
    1/35
    
    Not Used
 TABLE 4A-9 NOTES:
 
  1.
    
    For Debit Payments:RTN = 987654789            Checking Account Number = 8989898989Expected Settlement Date (Date of funds transfer to Treasury) = April 12, 2006
  Revised
03/05/08
 72




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 813  ELECTRONIC FILING OF TAX RETURN DATA
VERSION 003050
 LOOP ID  TFS
TFS SEGMENT
TAX FORM
 TABLE 4A-10
 Ref.
    
    
    
    Req.
    
    Elem
    
    Elem.Element
    
    Num.
    
    Name
    
    Design.
    
    Type
    
    Length
    
    CommentsTFS01
    
    128
    
    Reference Number Qualifier
    
    M
    
    ID
    
    2/2
    
    T6 Tax FilingTFS02
    
    127
    
    Reference Number
    
    M
    
    AN
    
    1/30
    
    5 Digit Tax Type Code (see note)TFS03
    
    128
    
    Reference Number Qualifier
    
    X
    
    ID
    
    2/2
    
    T9TFS04
    
    127
    
    Reference Number
    
    X
    
    AN
    
    1/30
    
    Bulk Provider Reference NumberTFS05
    
    66
    
    Identification Code Qualifier
    
    X
    
    ID
    
    2/2
    
    24 Employer Identification Number34 Social Security Number (Taxpayer TIN)TFS06
    
    67
    
    Identification Code
    
    X
    
    AN
    
    2/20
    
    9 Digit TINTFS07
    
    373
    
    Date
    
    O
    
    DT
    
    6/6
    
    Tax Period End DateTFS08
    
    818
    
    Name Control Identifier
    
    O
    
    AN
    
    4/4
    
    IRS Name Control
 Revised
03/05/08
 73




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 Notes for TABLE 4A-10:
 IMF
 Stand-Alone only
      Integrated efile and pay only
   BMF
 Stand-Alone only
      
   Integrated e-file and pay only
 
   Credit
Card Processors Validations:
  -
    
    Valid tax types shown above-
    
    Each processor will have specific valid tax types assigned to prevent
invalid tax types being submitted on the file.-
    
    Individual payments (1040) and business payments (94X and 1041) must be
on separate transaction files.
 Revised 03/05/08
 74




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 integrated file and pay
 -
    
    1040s  no limitation-
    
    941s  <$2,500.00-
    
    940s  =<$500.00-
    
    944s  <$2,500.00
 stand-alone processors
 -
    
    1040s  no limitation-
    
    TFRP  no limitation-
    
    94X  no limitation
   
  For stand-alone processors ONLY does not apply to integrated file and pay applications
 For Integrated file and pay,
       Treasury Financial Agent File Edits:
 06/30/XX
   -
    
    Shown above-
    
    Each processor will have valid tax types assigned  valid tax types not
assigned to a bulk provider are invalid and will cause the file to reject. (for BoA
only  reject the transaction not the file)
   Revised 03/05/08
 75




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
    For
Individual Tax Types:
 NOTE: Credit Card Processors must use the Processing Period Chart.
    or
            or
               For
Business Tax Types:
 NOTE: Credit Card Processors must use the Processing Period Chart.
 Revised 03/05/08
 76




---



##### 



Attachment 3, Appendix B(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 For 940

     subsequent/bal due/IA (09407) Month = 12;
Year = prior year through prior year minus 10 (2008 through 1998)
Day = 31
 For 941

     amended or adjusted rtn payment (94100) 
Month = 03, 06, 09, or 12.
Year = current year through current year minus 3 (2009 through 2006). Use the following table to determine the valid tax period:
  Jan, Feb, March
    
    Apr, May, June
    
    July, Aug, Sept
    
    Oct, Nov, DecTax 03
    
    CY-1 thru CY-3
    
    CY thru CY-3
    
    CY thru CY-3
    
    CY thru CY-3Quarter 06
    
    CY-1 thru CY-3
    
    CY-1 thru CY-3
    
    CY thru CY-3
    
    CY thru CY-3Ending 09
    
    CY-1 thru CY-3
    
    CY-1 thru CY-3
    
    CY-1 thru CY-3
    
    CY thru CY-3Months 12
    
    CY-1 thru CY-3
    
    CY-1 thru CY-3
    
    CY-1 thru CY-3
    
    CY-1 thru CY-3
 For 941

     subsequent/bal due/IA (94107) Month = 03, 06, 09, or 12.
Year = current year through current year minus 11 (2009 through 1998). Use the following table to determine the valid tax period:
  Jan, Feb, March
    
    Apr, May, June
    
    July, Aug, Sept
    
    Oct, Nov, DecTax 03
    
    CY-1 thru CY-11
    
    CY thru CY-11
    
    CY thru CY-11
    
    CY thru CY-11Quarter 06
    
    CY-1 thru CY-11
    
    CY-1 thru CY-11
    
    CY thru CY-11
    
    CY thru CY-11Ending 09
    
    CY-1 thru CY-11
    
    CY-1 thru CY-11
    
    CY-1 thru CY-11
    
    CY thru CY-11Months 12
    
    CY-1 thru CY-11
    
    CY-1 thru CY-11
    
    CY-1 thru CY-11
    
    CY-1 thru CY-11
 For 943
 amended or adjusted rtn payment (09430) 
Month = 12; 
Year = prior year through prior year minus 2 (2008 through 2006) Day = 31For 943
 subsequent/bal due/IA (09437) Month = 12;
Year = prior year through prior year minus 10 (2008 through 1998) Day = 31
 Revised
03/05/08
 77




---



##### 



Attachment 3, Appendix B(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 For 944
  subsequent/bal due/IA (94407), Month = 12;
Year = previous year or previous year minus one
Day = 31For 945
  amended or adjusted rtn payment (09450) Month = 12;
Year = prior year through prior year minus 2 (2008 through 2006) Day = 31For 945
  subsequent/bal due/IA (09457) Month = 12; 
Year = prior year through prior year minus 10 (2008 through 1998) Day = 31For 1041,
 Month = 01-12
Year must equal previous year
 Revised 03/05/08
 78




---



##### 



Attachment 3, Appendix B(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 813  ELECTRONIC FILING OF TAX RETURN DATA
VERSION 003050
 LOOP ID  TFS
REF SEGMENT
REFERENCE NUMBERS
 TABLE 4A-11
 Ref.
    
    
    
    Req.
    
    Elem.
    
    Elem.Element
    
    Num.
    
    Name
    
    Design.
    
    Type
    
    Length
    
    CommentsREF01
    
    128
    
    
    
    Reference Number Qualifier
    
    M
    
    ID
    
    2/2
    
    F8 Original Reference NumberREF02
    
    127
    
    
    
    Reference Number
    
    M
    
    AN
    
    1/30REF03
    
    352
    
    
    
    Description
    
    X
    
    AN
    
    1/80
    
    ZIP Code
          Revised 03/05/08
 79




---



##### 



Attachment 3, Appendix B(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 813  ELECTRONIC FILING OF TAX RETURN DATA
VERSION 003050
 LOOP ID  TFS
DTM SEGMENT
DATE/TIME REFERENCE
 TABLE 4A-12
 Ref.
    
    
    
    Req.
    
    Elem.
    
    ElemElement
    
    Num.
    
    Name
    
    Design.
    
    Type
    
    Length
    
    CommentsDTM01
    
    374
    
    
    
    Date/Time Qualifier
    
    M
    
    ID
    
    3/3
    
    009 Process DateDTM02
    
    373
    
    
    
    Date
    
    X
    
    DT
    
    6/6
    
    Credit Card Authorization Date
    Revised 03/05/08
 80




---



##### 



Attachment 3, Appendix B(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 813  ELECTRONIC FILING OF TAX RETURN DATA
VERSION 003050
 LOOP ID  FGS
FGS SEGMENT 
FORM
GROUP
 TABLE 4A-13
 Ref.
    
    
    
    Req.
    
    Elem.
    
    Elem.Element
    
    Num.
    
    Name
    
    Design.
    
    Type
    
    Length
    
    CommentsFGS01
    
    350
    
    
    
    Assigned Identification
    
    M
    
    AN
    
    1/11
    
    Sequential number assigned
by sender
   Revised 03/05/08
 81




---



##### 



Attachment 3, Appendix B(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 813  ELECTRONIC FILING OF TAX RETURN DATA
VERSION 003050
 LOOP ID  TIA
TIA SEGMENT
TAX INFORMATION AND AMOUNT
 TABLE 4A-14
 Ref.
    
    
    
    Req.
    
    Elem
    
    Elem.Element
    
    Num.
    
    Name
    
    Design
    
    Type
    
    Length
    
    CommentsTIA01
    
    817
    
    
    
    Tax Information Identification Number
    
    M
    
    AN
    
    1/30
    
    Tax Type CodeTIA02
    
    782
    
    
    
    Monetary Amount
    
    X
    
    R
    
    1/15
    
    Element length limit is 10TIA03
    
    449
    
    
    
    Fixed Format Information
    
    XIZ
    
    AN
    
    1/80
    
    Not UsedTIA04
    
    380
    
    
    
    Quantity
    
    X
    
    R
    
    1/15
    
    Not UsedTIA05
    
    355
    
    
    
    Unit or Basis for Measurement Code
    
    X
    
    ID
    
    2/2
    
    Not UsedTIA06
    
    954
    
    
    
    Percent
    
    X
    
    R
    
    1/10
    
    Not UsedTIA07
    
    782
    
    
    
    Monetary Amount
    
    XIZ
    
    R
    
    1/15
    
    Not Used
    
 Revised 03/05/08
 82




---



##### 



Attachment 3, Appendix B(EFTPS LOGO)
    
    2009 Credit Card Bulk
Provider Requirements
 813  ELECTRONIC FILING OF TAX RETURN DATA
VERSION 003050
 SE SEGMENT
TRANSACTION SET TRAILER
 TABLE 4A-15
 Ref.
    
    
    
    Req.
    
    Elem.
    
    Elem.Element
    
    Num.
    
    Name
    
    Design.
    
    Type
    
    Length
    
    CommentsSE01
    
    96
    
    
    
    Number of Included Segments
    
    M
    
    NO
    
    1/10SE02
    
    329
    
    
    
    Transaction Set Control Number
    
    M
    
    AN
    
    4/9
   Revised 03/05/08
 83




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 TRANSACTION SET 151
 ELECTRONIC FILING OF TAX RETURN DATA
ACKNOWLEDGMENT
 VERSION 003050
 SEND TO BULK PROVIDER
 CONFIRM/REJECT TAX PAYMENT
 ATTACHMENT 4B
 Revised 03/05/08
 84




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 151  ELECTRONIC FILING OF TAX RETURN DATA ACKNOWLEDGMENT
VERSION 003050
 TABLE 4B-1
 MAX.
    
    LOOPSEG. ID
    
    NAME
    
    REQ. DES.
    
    USE
    
    REPEATST
    
    Transaction Set Header
    
    M
    
    1BTA
    
    Beginning Tax Acknowledgment
    
    M
    
    1BTI
    
    Beginning Tax Information
    
    M
    
    1
 TABLE 4B-2
 MAX.
    
    LOOPSEG. ID
    
    NAME
    
    REQ. DES.
    
    USE
    
    REPEATLOOP ID - TFS
    
    
    
    
    
    50000TFS
    
    Tax Form
    
    O
    
    1
 TABLE 4B-3
 MAX.
    
    LOOPSEG. ID
    
    NAME
    
    REQ. DES.
    
    USE
    
    REPEATSE
    
    Transaction Set Trailer
    
    M
    
    
    1
 
 Revised 03/05/08
 85




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 151  ELECTRONIC FILING OF TAX RETURN DATA ACKNOWLEDGMENT
VERSION 003050
 ST SEGMENT
TRANSACTION SET HEADER
 TABLE 4B-4
 REF.
    
    
    
    Req.
    
    Elem.
    
    Elem.Element
    
    Number
    
    Name
    
    Desig
    
    Type
    
    Length
    
    CommentsST01
    
    143
    

    
    
    Transaction Set Identifier Code
    
    MIZ
    
    ID
    
    3/3
    
    151ST02
    
    329
    

    
    
    Transaction Set Control Number
    
    M
    
    AN
    
    4/9
 
   Revised 03/05/08
 86




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 151  ELECTRONIC FILING OF TAX RETURN DATA ACKNOWLEDGMENT
VERSION 003050
 BTA SEGMENT
BEGINNING TAX ACKNOWLEDGMENT
 TABLE 4B-5
 REF.
    
    
    
    Req.
    
    Elem
    
    ElemElement
    
    Number
    
    Name
    
    Desig
    
    Type
    
    Length
    
    CommentsBTA01
    
    587
    
    
    
    Acknowledgment
Type
    
    M
    
    ID
    
    2/2
    
    AD Acknowledge  With Detail, No Change
AC Acknowledge  With Detail and Change
RD Reject with Detail
RJ Rejected  No DetailBTA02
    
    373
    
    
    
    Date
    
    O
    
    DT
    
    6/6
    
    Acknowledgment Date YYMMDDBTA03
    
    522
    
    
    
    Amount Qualifier
    
    X
    
    ID
    
    1/2
    
    AB Adjusted Collected BalanceBTA04
    
    782
    
    
    
    Monetary Amount
    
    X
    
    R
    
    1/15
    
    Element limit length of 10
 BTA01:

    AD  used to acknowledge 813 as processed. Will receive one EFT Number per Tax Transaction
AC  used to ID that the 813 were accepted but one or more transactions were rejected.
          Will see EFT number or error number for each tax transaction.
RD  used to identify rejection of single debit
transactions.
RJ  used to identify that the entire 813 was rejected.
   
 All tax transactions processed as received:
    
    BTA~AD~061125\Some Tax transactions rejected, Debit adjusted accordingly:Bank of America Example:
    
    BTA~AC~061125~AB~450.00\Entire 813 rejected
    
    BTA~RJ~061125\
 Revised 03/05/08
 87




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 151  ELECTRONIC FILING OF TAX RETURN DATA ACKNOWLEDGMENT
VERSION 003050
 BTI SEGMENT
BEGINNING TAX INFORMATION
 TABLE 4B-6
 REF
    
    
    
    Elem.
    
    ElemElement
    
    Num
    
    Req. Name
    
    Desig.
    
    Type
    
    Length
    
    CommentsBTI01
    
    128
    
    
    
    Reference Number Qualifier
    
    MIZ
    
    ID
    
    2/2
    
    BT Batch NumberBTI02
    
    127
    
    
    
    Reference Number
    
    M
    
    AN
    
    1/30
    
    Original Transaction Control
Number (ST02)BTI03
    
    66
    
    
    
    Identification Code Qualifier
    
    MIZ
    
    ID
    
    1/2
    
    SV Service Provider NumberBTI04
    
    67
    
    
    
    Identification Code
    
    M
    
    AN
    
    2/20
    
    Assigned by the TFABTI05
    
    373
    
    
    
    Date
    
    OIZ
    
    DT
    
    6/6
    
    Not UsedBTI06
    
    818
    
    
    
    Name Control Identifier
    
    O
    
    AN
    
    4/4
    
    Not UsedBTI07
    
    66
    
    
    
    Identification Code Qualifier
    
    XIZ
    
    ID
    
    1/2
    
    93 Code Assigned by Originator
of TransactionBTI08
    
    67
    
    
    
    Identification Code
    
    X
    
    AN
    
    2/20
    
    Confirmation NumberBTI09
    
    66
    
    
    
    Identification Code Qualifier
    
    XIZ
    
    ID
    
    1/2
    
    Not UsedBTI10
    
    67
    
    
    
    Identification Code
    
    X
    
    AN
    
    2/20
    
    Not UsedBTI11
    
    66
    
    
    
    Identification Code Qualifier
    
    X
    
    ID
    
    1/2
    
    Not UsedBTI12
    
    67
    
    
    
    Identification Code
    
    X
    
    AN
    
    2/20
    
    Not Used
 
 Example:

    Control Number from 813 = 323232, ID code = 999999999
Confirmation Number for Debit = 485954349484944
BTI~BT~323232~SV~999999999~~~93~485954349484944\
 Revised 03/05/08
 88




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 151  ELECTRONIC FILING OF TAX RETURN DATA ACKNOWLEDGMENT
VERSION 003050
 LOOP ID  TFS
TFS SEGMENT
TAX FORM
 TABLE 4B-7
 REF.
    
    
    
    Req.
    
    Elem
    
    Elem.Element
    
Number
    
    Name
    
    Desig.
    
    Type
    
    Length
    
    CommentsTFS01
    
    128
    
    
    Reference Number Qualifier
    
    M
    
    ID
    
    2/2
    
    F8 Original ReferenceNumberTFS02
    
    127
    
    
    Reference Number
    
    M
    
    AN
    
    1/30
    
    (REF02 FROM TFSLOOP)TFS03
    
    128
    
    
    Reference Number Qualifier
    
    X
    
    ID
    
    2/2
    
    93 Funds Authorization1Q Error IdentificationCodeTFS04
    
    127
    
    
    Reference Number
    
    X
    
    AN
    
    1/30
    
    Acknowledgment EFTNumber or Error CodeTFS05
    
    66
    
    
    Identification Code Qualifier
    
    X
    
    ID
    
    1/2
    
    ZZTFS06
    
    67
    
    
    Identification Code
    
    X
    
    AN
    
    2/20
    
    Bulk Provider ReferenceNumberTFS07
    
    373
    
    
    Date
    
    O
    
    DT
    
    6/6
    
    Not UsedTFS08
    
    818
    
    
    Name Control Identifier
    
    O
    
    AN
    
    4/4
    
    Not Used
 Revised 03/05/08
 89




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 Notes for TABLE 4B-7
  
  1.
    
    Accept and process debit as Transmitted  Payment Initiated through e-file
 Reference Number
    
    Amount
    
    Acknowledgment Number
    
        Document Control Number55566644
    
    
    100.00
    
    
    
    168910688123456
    
    
    
    0012345612301955566645
    
    
    300.00
    
    
    
    168910688123457
    
    
    
    00123456123020
 
 2.
    
    Accept and process debit as transmitted  Payment Initiated through Credit Card Processor
 Reference Number
    
    Amount
    
    Acknowledgment Number
    
Authorization Number55566644
    
    
    200.00
    
    
    
    168910699123456
    
    
    
    1234567855566645
    
    
    400.00
    
    
    
    168910699123457
    
    
    
    12345679
 
  Revised 03/05/08
 90




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 151  ELECTRONIC FILING OF TAX RETURN DATA ACKNOWLEDGMENT
VERSION 003050
 SE SEGMENT
TRANSACTION SET TRAILER
 TABLE 4B-8
 REF.
    
    
    
    Req.
    
    Elem.
    
    Elem.Element
    
    Number
    
    Name
    
    Desig.
    
    Type
    
    Length
    
    CommentsSE01
    
    
    96
    
    
    Number of Segments Included
    
    M
    
    NO
    
    1/10SE02
    
    
    329
    
    
    Transaction Set Control Number
    
    M
    
    AN
    
    4/9
   Revised 03/05/08
 91




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 EDI 151 Payment Response Confirmation Error Codes
(EDI TRS Segment: TFS04 value when TFS is 1Q)
 EDI Error Code
    
    EDI Message1123
    
    Name control required; cannot be blank1125
    
    Invalid TIN1126
    
    File cannot contain business and individual payments1127
    
    Bulkfiler is set up for business processing and individual paymentswere received1128
    
    Bulkfiler is set up for individual processing and business paymentswere received
 Revised 03/05/08
 92




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 D. Chapter 9 Return and Exception Item Reporting
 Overview
 
 
    
    Single ACH Debit Posted to the Bulk Providers Account
    
    ACH Return Transactions
    
    Record Layouts
    
    Attachment 9, ANSI X12 EDI Transaction Set 827: Financial Return Noticeshows the file
layout for ACH return items.
 Single ACH Debit Posted to the Bulk Providers Account
 
    
    Within 3 hours of receipt of the bulk providers transmission of an ACH debit file, the TFA
validates that the batch totals equal the sum of the detail; otherwise, the TFA rejects the
813 (see Chapter 4, Attachment 4A).
    
    No 813 for an ACH transmission may exceed $99,999,999.00 (the amount field limit for ACH)
or the 813 will be rejected.
    
    If an individual transaction within an 813 transaction set fails the enrollment edit (no
name control), that transaction will be rejected with the appropriate reject reason code. The
total amount of the debit to be created will be recalculated by the TFA based on the sum of
the valid transactions contained within the 813.
    
    If the TFA rejects any item, the bulk provider must fix the problem transaction and
resubmit it by 8:00 p.m. ET.
    
    The TFA subsequently sends the bulk provider a confirmation file using the ANSI EDI
standard 151 acknowledgment format (see Chapter 4, Attachment 4Band ACH Return Transactions).
 ACH Return Transactions
 Revised 03/05/08
 93




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 
    
    An ACH transaction may be returned to the TFA by the Receiving Financial Institution
(RDFI), for a valid reason such as Insufficient or Uncollected Funds.
    
    The TFA will initiate an ANSI X12 EDI Transaction Set 827 Financial Return Notice to the
bulk provider (see Attachment 9at the end of this chapter). The 827 will contain:
 Ø
    
    Return reasonØ
    
    Dollar amountØ
    
    Transaction type (credit or debit)Ø
    
    Original transaction confirmation number (see Record Layouts, below).
 
    
    The 827 transaction set will be transmitted to the bulk provider no later than 24 hours
after the return settles.
    
    Once the 827 is received, the bulk provider will initiate a 997 Functional Acknowledgment
(see Chapter 3, Attachment 3B) to the TFA indicating receipt of the returned transaction(s).
    
    The 997 will include an acceptance code as well as the functional group number being
acknowledged.
    
    The bulk provider is expected to send the 997 immediately upon receipt of the 827 to ensure
timely processing.
 Record Layouts
 Table 9-1.
 Table 9-1 EDI Transaction Sets Used for Return and Exception Item Reporting
 Transaction Set Number and Name
    
    Chapter
    
    Attachment827 Financial Return Notice
    
    
    9
    
    
    
    9151 Electronic Filing of Tax Return Data Acknowledgment
    
    
    4
    
    
    
    4B997 Functional Acknowledgment
    
    
    3
    
    
    
    3B
 Revised 03/05/08
 94




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 TRANSACTION SET 827
 FINANCIAL RETURN NOTICE
 VERSION 003050
 SEND TO BULK PROVIDERS
 NOTIFICATION OF FINANCIAL RETURNS
  Revised 03/05/08
 95




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 827  FINANCIAL RETURN NOTICE
VERSION 003050
 TABLE 9-1
 SEG. ID
    
    NAME
    
    REQ. DES.
    
    MAX. USE
    
    LOOP REPEATST
    
    Transaction Set Header
    
    M
    
    
    1RIC
    
    Financial Return
    
    M
    
    
    1REF
    
    Reference Numbers
    
    O
    
    
    10SE
    
    Transaction Set Trailer
    
    M
    
    
    1
 Revised 03/05/08
 96




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 827  FINANCIAL RETURN NOTICE
VERSION 003050
 ST SEGMENT
TRANSACTION SET HEADER
 TABLE 9-2
 REF.
    
    
    
    Req.
    
    Elem.
    
    Elem.Element
    
    Number
    
    Name
    
    Desig
    
    Type
    
    Length
    
    CommentsST01
    

    143

    
    Transaction Set Identifier Code
    
    MIZ
    
    D
    
    3/3
    
    827ST02
    

    329

    
    Transaction Set Control Number
    
    M
    
    AN
    
    4/9
     Revised 03/05/08
 97




---



##### 

\

(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 827  FINANCIAL RETURN NOTICE
VERSION 003050
 RIC SEGMENT FINANCIAL
RETURN
 TABLE 9-3
 REF.
    
    
    
    Req.
    
    Elem.
    
    Elem.Element
    
    Number
    
    Name
    
    Desig
    
    Type
    
    Length
    
    CommentsRIC01
    

    647

    
    Application Error Condition Code
    
    M
    
    ID
    
    1/3
    
    830 Refused 011 Not MatchingRIC02
    

    782

    
    Monetary Amount
    
    M
    
    R
    
    1/15RIC03
    

    478

    
    Credit/Debit Flag
    
    M
    
    ID
    
    1/1RIC0 4
    

    508

    
    Account Number
    
    X
    
    AN
    
    1/35
    
    Not UsedRIC05
    

    569

    
    Account Number Qualifier
    
    OIZ
    
    ID
    
    1/3
    
    Not UsedRIC06
    

    506

    
    (DFI) ID Number Qualifier
    
    X
    
    ID
    
    2/2
    
    Not UsedRIC07
    

    507

    
    (DFI) Identification
Number
    
    X
    
    AN
    
    3/12
    
    Not Used
         Revised 03/05/08
 98




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 827  FINANCIAL RETURN NOTICE
VERSION 003050
 REF SEGMENT REFERENCE
NUMBERS
 TABLE 9-4
 REF.
    
    
    
    Req.
    
    Elem.
    
    Elem.Element
    
    Number
    
    Name
    
    Desig.
    
    Type
    
    Length
    
    CommentsREF01
    
    128
    
    
    Reference Number
Qualifier
    
    M
    
    ID
    
    2/2
    
    93 Funds Authorization 1Q Error Code ZZ Mutually DefinedREF02
    
    127
    
    
    Reference Number
    
    X
    
    AN
    
    1/30
            Revised 03/05/08
 99




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 827  FINANCIAL RETURN NOTICE
VERSION 003050
 SE SEGMENT
TRANSACTION SET TRAILER
 TABLE 9-5
 REF.
    
    
    
    Req.
    
    Elem.
    
    Elem.Element
    
    Number
    
    Name
    
    Desig.
    
    Type
    
    Length
    
    CommentsSE01
    
    96
    
    
    Number of Segments
Included
    
    M
    
    NO
    
    1/10SE02
    
    329
    
    
    Transaction Set Control
Number
    
    M
    
    AN
    
    4/9
   E. Chapter 10 Daily Operation Procedures
 Overview
  Revised 03/05/08
 100




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
   Ø
    
    Federal Reserve Bank HolidaysØ
    
    Input File Delivery/VerificationØ
    
    InquiriesØ
    
    EFTPS Bulk Provider Tax Payment Processing Deadlines
 Federal Reserve Bank Holidays
 not
 Input File Delivery/Verification
 1.
    
    ACH Debits (Single Debit Posted to the Bulk Providers) Account
    
    ACH Debit files transmitted directly to a TFA must be completely received by the TFA
between the hours of 7:00 am ET and 7:00 pm ET on the banking day prior to the settlement
date.
    
    Within three (3) hours after receipt of the bulk providers transmission, the TFA validates
that the batch totals equal the sum of the detail and the amount for an individual 813 and
that the total amount is not greater than $9,999,999,999.99 in accordance with NACHA rules.
Otherwise, the TFA rejects the 813.
    
    If any items are rejected by the TFA, the bulk provider must fix the problem transactions
and resubmit them by 8:00 pm ET.For further information, see also Chapter 4, ACH Bulk Debits.
 Return Item Handling
   Inquiries
 .
 Revised 03/05/08
 101




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 EFTPS Bulk Provider Tax Payment Processing Deadlines
  Process
    
    DeadlineBulk provider transmits ACH single debitfile to TFA
    
    7:00 a.m.  7:00 p.m. ET on the
banking day prior to the
settlement dateBulk provider retransmits previously rejected ACH
single debits to TFA
    
    8:00 p.m. ET on the banking day prior to the settlement date
 Revised 03/05/08
 102




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 2008
    
    2009
    
    2010
    
    2011
    
    2012New Years Day
    
    January 1
    
    January 1
    
    January 1
    
    January 1*
    
    January 2Birthday of
Martin Luther King, Jr.
    
    January 21
    
    January 19
    
    January 18
    
    January 17
    
    January 16Presidents Day
    
    February 18
    
    February 16
    
    February 15
    
    February 21
    
    February 20Memorial Day
    
    May 26
    
    May 25
    
    May 31
    
    May 30
    
    May 28Independence Day
    
    July 4
    
    July 4*
    
    July 5
    
    July 4
    
    July 4Labor Day
    
    September 1
    
    September 7
    
    September 6
    
    September 5
    
    September 3Columbus Day
    
    October 13
    
    October 12
    
    October 11
    
    October 10
    
    October 8Veterans Day
    
    November 11
    
    November 11
    
    November 11
    
    November 11
    
    November 12Thanksgiving Day
    
    November 27
    
    November 26
    
    November 25
    
    November 24
    
    November 22Christmas Day
    
    December 25
    
    December 25
    
    December 25*
    
    December 26
    
    December 25
 
 *
    
    Saturday   Revised 03/05/08
 103




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 5. IRS Requirements for Integrated File and Pay Credit Card
Processors
  June 30
 Internal Revenue Service
    
    Email address: debbie.a.mccollister@irs.govAttn: Debbie McCollister C8-377SE:W:CAS:SP:TPM:EP
    
    Fax Number: (202) 283-25315000 Ellin RoadLanham, MD 20706
  1)
    
    Convenience Fees: Taxpayers must be notified of the dollar amounts of all
fees to be charged to their credit card in relation to the federal tax payment
including convenience fees and surcharges imposed by software developers. An
acknowledgment or acceptance by the taxpayer of the fees shall be obtained prior to
initiating credit authorizations. The Government shall be notified of the method of
obtaining taxpayers acknowledgement before the program commences. The software or
instructions should note that the convenience fee is not charged or received by the
IRS.2)
    
    General Information: Taxpayers will be provided, upon request, IRS general
information in an easily accessible, readable and print ready form through the return
transaction software used by participating tax practitioners/taxpayers.3)
    
    Confirmation Number: All taxpayers shall be provided an electronic
confirmation of payment transactions through the return transmission software used by
participating electronic return originators, tax practitioners or taxpayers.
Taxpayers shall also be notified electronically through the return transmission
software if the credit card authorization is denied.
 Revised 03/05/08
 104




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 4)
    
    Reporting Requirements: Documentation formatting and content are subject to inspection,
verification and approval by the IRS Point of Contact (POC). All reports are to be submitted
to the IRS POC via email.
 A)
    
    Schedule of Performance  This includes a project schedule (WBS) of the development,
testing and implementation critical milestones and beginning and ending dates for each
milestone.B)
    
    Monthly Development Status Reports  The credit card bulk provider shall provide monthly
status reports on the 10th day of each month through the implementation date of the pilot. The
last Monthly Status Report is due in the month following implementation. The report shall cover
the overall progress of the pilots development. The report shall contain the following
information:
 1.
    
    date of report,2.
    
    project manager name,3.
    
    project manager telephone number, fax number and e-mail address4.
    
    a brief description of the work accomplished, emphasizing the progress made since
the last reporting period,5.
    
    a description of any unresolved and/or anticipated problems, if any
(include schedule impacts),6.
    
    an estimate of the percent of work accomplished to date; and a statement on the
status of the pilot as it relates to the work breakdown schedule, either confirming
that the task is on schedule or explaining the nature and extent of the pending
delay.
 C)
    
    Daily and Monthly Production Reports  The Credit Card Bulk Provider must report
to the IRS on a daily basis during the timeframe of accepting payments. The daily volume
and dollars report is due to the IRS by 9:00 am each business day. Monthly cumulative
reports will be submitted by the
5th day of each month. The reports shall
contain the following information:
 1.
    
    date of report2.
    
    period covered3.
    
    total number of transactions4.
    
    dollar amount of transactions5.
    
    total number of successful attempts (good authorizations)6.
    
    dollar amount of successful attempts (good authorizations)7.
    
    total number of failed attempts (failed authorizations)
 Revised 03/05/08
 105




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 8.
    
    dollar amount of failed attempts (failed authorizations)9.
    
    reasons for failed attempts10.
    
    volume and dollars by tax type11.
    
    volume and dollars by card type12.
    
    customer service activity13.
    
    largest dollar amount14.
    
    aggregate payment volumes by payment type and dollar amount  provided daily15.
    
    historical data should also be provided to compare changes from the prior year
 Each report file shall have its own unique name which includes the application
transaction date. Daily reports should include the daily as well as YTD volumes and
dollars. Monthly reports should include the monthly as well as YTD volumes and
dollars.D)
    
    Workflow  Schematic/Specifications  A detailed description of the functional work
processes and data flow from payment initiation through confirmation,
authorization/denial and taxpayer notification shall be provided to the Government before
the pilot commences.E)
    
    Funds Settlement Timeline  Provide the best-case scenario timeline beginning with
transaction authorization through ACH debit activities.F)
    
    Certification of Test Results  Once the credit card bulk provider/processor has
successfully completed a full circle integrated test (internally and with external
trading partners), the bulk provider shall certify in writing their readiness for use
status to the IRS before commencing production.G)
    
    Incident Report  Any incident that results in any material outages, work stoppages, or
other payment processing problems shall be reported to the IRS POC. The incident will be
documented and emailed to the IRS POC.
The credit card bulk provider will notify the IRS of all incidents within 24 hours of
occurrence or awareness. The incident report is due within 5 business days of occurrence
or awareness of the incident.Documentation should include a description of the incident,
the cause, number of taxpayers impacted and dollars involved, duration and actions taken
to rectify the situation.
 Revised 03/05/08
 106




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 H)
    
    Findings Report  The Credit Card Bulk Provider (along with subcontractors)
shall provide an initial and supplemental findings report. .
The report shall describe:
 1.
    
    the program/application features,2.
    
    the conduct and findings of the program/application as they relate to the
Contractors and any subcontractors performance (including a summary of all payment
transactions, any problems, changes made during the pilot and lessons learned)3.
    
    recommendations for improvement including changes to the Contractors and/or IRS processes, and4.
    
    practitioner and/or client feedback including customer satisfaction survey results.
 The initial report (due June 15) will include activity occurring between January and
April. The supplemental report (due November 30) will include a summary of the initial
reports findings and activity from May through October.
 I)
    
    Web Site Statistics  Monthly Report of the number of unique visits to its Web site by
way of a hyperlink from IRS.gov or hyperlink connections to IRS.gov. The report will be
due on the 10th of the following month after the hyperlink is activated.J)
    
    Chargebacks  Provide weekly reports of all chargeback actions identifying the
transaction, date, dollar amount, action request date, and reason for action. These
actions shall be in conformance with chargeback procedures issued by the IRS and meet the
definition of chargebacks provided. These reports are due by close of business each
Friday.
 5)
    
    The credit card bulk provider shall ensure that a merchant descriptor on the cardholders
credit card statement indicates the tax payment amount as a unique line item entitled U S
Treasury Tax Payment. The convenience fee must be separately stated on the statement. A
unique identifier, such as the confirmation number, should be posted on the card holders
statement to facilitate error resolution.6)
    
    The credit card bulk provider shall ensure that ACH Debit authorizations are initiated
only upon acceptance of the e-filed tax return.
 Revised 03/05/08
 107




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 7)
    
    The credit card bulk provider shall ensure that credit card payment transactions are settled
within 48 hours of acceptance of the e-file return. If unable to comply with the settlement
timeframe, an exception must be requested. The exception must outline why the settlement
timeframe cannot be met. FMS charges interest on any funds held overnight from one business
day to the next and shall be reported to FMS. IRS/FMS must approve an exception process
before funds are held overnight.8)
    
    Settlement files shall be forwarded to the Treasury Financial Agent each business day.The
credit card bulk provider shall ensure that settled credit card payments, where the
authorization date is less than 11 days prior to the date the settlement file are forwarded
to the Treasury Financial Agent (TFA).9)
    
    The credit card bulk provider shall ensure that credit card authorization logs are retained
for 72 months from the date of each transaction. The information in such logs shall include
the transaction dates, times cardmember account number and expiration date, amount of
transaction, and approval code. Retention of e-file information for 36 months following the
end of each tax filing season.10)
    
    The credit card bulk provider shall ensure an accuracy rate to the Government of 99% or
higher for transmitted transaction data as provided by the taxpayer. This includes accuracy of
electronic payment data resulting from intermediate actions taken by the Credit Card Bulk
Provider necessary for coding, applying and transmitting payment data to the Government.11)
    
    The credit card bulk provider must provide only guaranteed payments to the Government
for the ACH debit file.12)
    
    Forward settlement files to the TFA one business day prior to settlement.13)
    
    Funds must be available in the credit card bulk providers designated bank account one
business day after the settlement file is submitted.14)
    
    The credit card bulk provider shall schedule testing with the TFA as early as possible.
Provide the TFA with a test plan and test cases if need be. Once completed, provide the
certification, from the TFA, to the IRS point of contact by the date specified by the IRS. Ensure
that the TFA is aware of the certification date when coordinating the test effort.
 Revised 03/05/08
 108




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 15)
    
    The credit card bulk provider shall ensure that all credit card discount fees
and other transaction fees are paid.16)
    
    The credit card bulk provider shall inform the IRS of plans to market the program
and provide copies of all materials such as newsletters, software packaging, inserts, and
ads for approval.17)
    
    Disclosure  The confidentiality of any information relating to Federal credit card
payments completed in a single transaction must be maintained. This includes absolutely no
disclosure or use of information collected during this transaction for any purpose other
than processing the transaction to the U.S. Treasury. Information collected during this
transaction shall not be disclosed or used for any purpose prohibited by Section 6311 of
the Internal Revenue Code or Treasury Regulation section 301.6311-2.18)
    
    The credit card bulk provider and its subcontractors are subject to and shall comply
with Section 6311 of the Internal Revenue Code or Treasury Regulation section 301.6311-2
regarding credit card payments.19)
    
    Chargebacks  Process chargeback actions in accordance with the IRSs written
procedures. This shall include reimbursing the Contractor for unauthorized charges that are
substantiated by the cardholder and approved by the Contractors duly authorized management
representative. The Contractor must have completed and delivered the appropriate IRS
chargeback form and supporting documentation to the IRS as described in IRS chargeback
procedures. Such chargeback requests shall be processed based on the Contractors
determination of the appropriateness of this action as signified by its authorized
claimants signature. IRS reserves the right to deny any chargeback request that does not
conform to the requirements
  1)
    
    An electronic copy of General Information for Taxpayers which is required to
be included in the software.2)
    
    A hyperlink from the IRS Web site to the credit card bulk providers web
site. The link will be established within the electronic services page of www.irs.gov.3)
    
    Provide chargeback procedures for handling erroneous credit card payments.
 Revised 03/05/08
 109




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 D.
    
    The IRS in conjunction with FMS will determine the Treasury Financial Agent (TFA), that the
credit card bulk provider will be assigned; currently Bank of America.E.
    
    Non-compliance with any of the requirements may result in the termination of the agreement and
the termination of acceptance of credit card payments.
 Revised 03/05/08
 110




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 IRS Annual Credit Card Bulk Provider Registration
 Company Name
    
    Employer Identification Number
 
 
 City
    
    State
    
    Zip
 
 Tax Types Accepted (1040, 4868s, etc.)
    
    Type /Brand Name of Software to be Used
 
 
 Projected Volumes
    
    CC Application Implementation Date
    
    Ending date
 
 Project Managers Name
    
    Telephone #
    
    e-mail address
 Revised 03/05/08
 111




---



##### 



(EFTPS LOGO)
    
    2009 Credit Card Bulk Provider Requirements
 IRS CREDIT CARD BULK PROVIDER AGREEMENT
 In accordance with the specifications and requirements of the 2009 Credit Card Bulk Provider
Requirements and the related Registration, the undersigned (Credit Card Bulk Provider) hereby
acknowledge, in agreement with the IRS, to the following:
 (1) All requirements listed in the Credit Card Bulk Provider Requirements will be complied with.
 (2) Any non-compliance with the requirements may result in termination of this agreement and
ability to participate in the credit card bulk provider application.
 Name of the Bulk Provider By:Name:Title: ACCEPTED AS OF ___(date)______,
 Internal Revenue
ServiceBy:Name:Title: Revised 03/05/08
 112




---



##### 



Treasury Regulation 301.6311-2
    
    Attachment 3, Appendix C
 [4830-01-p]
    
    Published December 14, 2001
          Effective Date
 Applicability Date




---



##### 



Treasury Regulation 301.6311-2
    
    Attachment 3, Appendix C
  Background
  Federal Register Federal Register
 2




---



##### 



Treasury Regulation 301.6311-2
    
    Attachment 3, Appendix C
 Explanation of Provisions
   3




---



##### 



Treasury Regulation 301.6311-2
    
    Attachment 3, Appendix C
    4




---



##### 



Treasury Regulation 301.6311-2
    
    Attachment 3, Appendix C
    5




---



##### 



Treasury Regulation 301.6311-2
    
    Attachment 3, Appendix C
    6




---



##### 



Treasury Regulation 301.6311-2
    
    Attachment 3, Appendix C
  Summary of Comments
   7




---



##### 



Treasury Regulation 301.6311-2
    
    Attachment 3, Appendix C
    8




---



##### 



Treasury Regulation 301.6311-2
    
    Attachment 3, Appendix C
 commercial transactions commercial
 sale or exchange exchange exchange transfer for
consideration
 Explanation of Other Revisions
  9




---



##### 



Treasury Regulation 301.6311-2
    
    Attachment 3, Appendix C
 additional
amounts
 Special Analyses
  10




---



##### 



Treasury Regulation 301.6311-2
    
    Attachment 3, Appendix C
  Drafting Information
  List of Subjects in 26 CFR Part 301
  Adoption of Amendments to the Regulations
 Accordingly, 26 CFR part 301 is amended as follows:
       11




---



##### 



Treasury Regulation 301.6311-2
    
    Attachment 3, Appendix C
 §301.6103(k)(9)-1 Disclosure of returns and return information relating to payment of tax by
credit card and debit card.
  §301.6103(k)(9)-1T [Removed]
  §301.6311-1 [Amended]
   §301.6311-2 Payment by credit card and debit card
 Authority to receive Payments by credit card and
debit card
 12




---



##### 



Treasury Regulation 301.6311-2
    
    Attachment 3, Appendix C
 tax
 Payments by electronic funds transfer other than payments by credit card and
debit card
 Definitions Credit card
 Debit card
 13




---



##### 



Treasury Regulation 301.6311-2
    
    Attachment 3, Appendix C
  When payment is deemed made
 Payment not made Continuing liability of taxpayer
 Liability of financial institutions
 14




---



##### 



Treasury Regulation 301.6311-2
    
    Attachment 3, Appendix C
  Resolution
of errors relating to the credit card or debit card
account In general
 Matters covered by error resolution procedures
     15




---



##### 



Treasury Regulation 301.6311-2
    
    Attachment 3, Appendix C
   Return of funds pursuant to error resolution procedures
 Matters not subject to error resolution procedures
 16




---



##### 



Treasury Regulation 301.6311-2
    
    Attachment 3, Appendix C
 Section 170 of the Truth in Lending Act not applicable
 Fees or charges
 Authority to enter into contracts
 Use and disclosure of information relating to payment of taxes by credit card and
debit card
 17




---



##### 



Treasury Regulation 301.6311-2
    
    Attachment 3, Appendix C
          18




---



##### 



Treasury Regulation 301.6311-2
    
    Attachment 3, Appendix C
           19




---



##### 



Treasury Regulation 301.6311-2
    
    Attachment 3, Appendix C
    20




---



##### 



Treasury Regulation 301.6311-2
    
    Attachment 3, Appendix C
 Effective date
 301.6311-2T [Removed]