1、ORDERING AND BILLINGFORUM (OBF)DISPUTEFILE SPECIFICATIONSDecember, 2002 ISSUE 2THIS PAGE LEFT INTENTIONALLY BLANKCopyright 2002 by the Alliance for Telecommunications Industry SolutionsInc. All rights reserved.The Dispute File Specifications document, Issue 2 dated December, 2002, iscopyrighted, pri
2、nted and distributed by the Alliance for TelecommunicationsIndustry Solutions (ATIS) on behalf of the ATIS-sponsored Ordering and BillingForum (OBF).Except as expressly permitted, no part of this publication may be reproduced ordistributed in any form, in an electronic retrieval system or otherwise,
3、 withoutthe prior express written permission of ATIS. Permission may be obtained bycontacting ATIS at 202-628-6380. OBF Funding Companies (which are definedin the OBF Guidelines) should refer to the OBF Guidelines (accessible from:http:/www.atis.org/atis/clc/obf/obfhom.htm) regarding their rights to
4、reproduce this publication.For ordering information, please contact:ATIS1200 G Street N.W., Suite 500Washington, DC 20005(800) 387-A complete OBF Document Catalog and On-line Document Store is available onthe ATIS Web Site at: http:/www.atis.org/atis/docstore/index.aspNOTICEThis document was develop
5、ed by the Billing Committee of the Alliance forTelecommunications Industry Solutions (ATIS) Ordering and Billing Forum (OBF). TheOBF provides a forum for customers and providers in the telecommunications industryto identify, discuss and resolve national issues which affect ordering, billing,provisio
6、ning and exchange of information about access services, other connectivity andrelated matters. The Billing Committee is responsible for identifying and incorporatingthe necessary changes into this document. All changes to this document shall be madethrough the OBF issue resolution process and adopte
7、d by the Billing Committee as setforth in the OBF Guidelines.Disclaimer and Limitation of LiabilityThe information provided in this document is directed solely to professionals who havethe appropriate degree of experience to understand and interpret its contents inaccordance with generally accepted
8、engineering or other professional standards andapplicable regulations. No recommendation as to products or vendors is made orshould be implied.NO REPRESENTATION OR WARRANTY IS MADE THAT THE INFORMATION ISTECHNICALLY ACCURATE OR SUFFICIENT OR CONFORMS TO ANY STATUTE,GOVERNMENTAL RULE OR REGULATION, A
9、ND FURTHER NO REPRESENTATION ORWARRANTY IS MADE OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULARPURPOSE OR AGAINST INFRINGEMENT OF INTELLECTUAL PROPERTY RIGHTS. ATISSHALL NOT BE LIABLE, BEYOND THE AMOUNT OF ANY SUM RECEIVED IN PAYMENTBY ATIS FOR THIS DOCUMENT, WITH RESPECT TO ANY CLAIM, AND IN NO EV
10、ENTSHALL ATIS BE LIABLE FOR LOST PROFITS OR OTHER INCIDENTAL ORCONSEQUENTIAL DAMAGES. ATIS EXPRESSLY ADVISES THAT ANY AND ALL USEOF OR RELIANCE UPON THE INFORMATION PROVIDED IN THIS DOCUMENT IS ATTHE RISK OF THE USER.Dispute File SpecificationsIssued: November, 2000 Revised: December, 2002TABLE OF C
11、ONTENTS1.0 PREFACE12.0 GENERAL DESCRIPTION32.1 SCOPE.32.2 DOCUMENT REVISIONS.32.3 RELATED OBF ISSUES32.4 DATA ELEMENT REQUIREMENTS33.0 DISPUTE DATA53.1 INTENT OF SPECIFICATION 53.2 DISTRIBUTION 53.3 PAPER DISPUTE NOTIFICATION 53.4 ELECTRONIC DISPUTE NOTIFICATION IMAGE53.5 MECHANIZED FILE RECORDS 64.
12、0 FILE REQUIREMENTS .74.1 MECHANIZED FILE ORGANIZATION 74.2 MECHANIZED DATA FORMAT74.3 MECHANIZED FILE RECORDS 74.3.1 Dispute File Header 74.3.2 Dispute File Data.74.3.3 Dispute Trailer Record74.3.4 Resolution File Header.84.3.5 Resolution File Data84.3.6 Resolution Trailer Record 8APPENDIX A - OBF
13、ISSUES INCLUDED IN REVISIONS9APPENDIX B PAPER DISPUTE TEMPLATE. 11APPENDIX C - DATA ELEMENT DEFINITIONS 13A. INFORMATION PROVIDED ON THE DISPUTE LAYOUT. 13ACNA. 13BILLED AMOUNT. 13BILLING CONTACT ADDRESS. 14BILLING CONTACT EMAIL 14BILLING CONTACT FAX . 14BILLING CONTACT NAME. 14BIP BILLED. 15BIP COR
14、RECT 15BUSINESS/RESIDENCE INDICATOR 15CIC . 16CIRCUIT LOCATION. 16CLAIM/AUDIT NUMBER. 16CONTRACT NAME OR NUMBER 16DIRECTIONALITY INDICATOR 17DISPUTE DESCRIPTION 17DISPUTE REASON CODE 17DISPUTED AMOUNT WITHHELD. 18DISPUTED BILL DATE FROM 18Dispute File SpecificationsIssued: November, 2000 Revised: De
15、cember, 2002DISPUTED BILL DATE THRU. 18DISPUTING CONTACT ADDRESS . 19DISPUTING CONTACT EMAIL. 19DISPUTING CONTACT FAX 19DISPUTING CONTACT NAME 19DISPUTING CONTACT PHONE 20EC CIRCUIT ID. 20EO CLLI. 20FACILITIES THRU DATE 20IC CIRCUIT ID 21MILEAGE BILLED 22OC&C PON. 23OC&C SON. 23OTHER FACTOR 23OTHER
16、FACTOR CORRECT 24PIU BILLED 24PIU CORRECT 24PLU BILLED. 24PLU CORRECT 25POINT CODE 25QUERY 25RATE CORRECT 26RATE ELEMENT/USOC 26SERVICE TYPE 26SON 27TAX DISPUTE AMOUNT 28TWO-SIX CODE. 29USOC QUANTITY 30B. INFORMATION PROVIDED ON THE RESOLUTION LAYOUT 30ADJUSTMENT BAN 30ADJUSTMENT BILL DATE 30ADJUSTM
17、ENT PHRASE CODE. 31ADJUSTMENT SON 31AMOUNT CREDITED . 31BILL SECTION ADJUSTMENT WILL APPEAR ON. 31RESOLUTION AMOUNT 31RESOLUTION DATE . 32RESOLUTION REASON . 32RESOLUTION REMARKS 32NEW -APPENDIX D DISPUTE FILE LAYOUT. 33ILLUSTRATION 1 33ILLUSTRATION 2 33NEW -APPENDIX E DISPUTE FILE LAYOUT. 35ILLUSTR
18、ATION 1 35ILLUSTRATION 2 35APPENDIX E RESOLUTION FILE LAYOUT 37ILLUSTRATION 1 37ILLUSTRATION 2 37APPENDIX F DISPUTE REASON CODES. 39Dispute File SpecificationsIssued: November, 2000 Revised: December, 2002APPENDIX G RESOLUTION REASON CODES 41Dispute File SpecificationsIssued: November, 2000 Revised:
19、 December, 2002THIS PAGE LEFT INTENTIONALLY BLANKDispute File SpecificationsIssued: November, 2000 Revised: December, 2002Page 11.0 PREFACEThis document represents the Ordering and Billing Forum (OBF) Billing Committeerequirement to create a document of Dispute File Specifications for disputes other
20、 thanPICC.These procedures were cooperatively developed in the OBF. They were written inresponse to OBF Issue 2002. All changes to this document must be presented to theOBF Billing Committee and accepted by consensus. The OBF Billing Committee isresponsible for the on-going maintenance and distribut
21、ion of this document based onresolved issues.The OBF is a voluntary, self-policing group of participants who meet together toidentify, discuss and resolve issues which are national in scope, involving ordering andbilling of access services. The OBF functions under the auspices of the Alliance forTel
22、ecommunications Industry Solutions (ATIS). The Federal CommunicationsCommission (FCC) authorized ATIS in a January 17, 1985 Memorandum Opinion andOrder.Dispute File SpecificationsIssued: November, 2000 Revised: December, 2002Page 2THIS PAGE LEFT INTENTIONALLY BLANKDispute File SpecificationsIssued:
23、November, 2000 Revised: December, 2002Page 32.0 GENERAL DESCRIPTION2.1 ScopeThe Dispute File Specifications are guidelines for providing standard paper andmechanized file layouts for facility, usage, resale, UNE and other invoice disputesexcept for PICC, which follows the PICC Dispute File Specifica
24、tions.Implementation of these outputs such as timing and media for the mechanized filelayouts (CD-ROM, Diskette, e-mail, etc.) used to provide this information will benegotiated between the individual customers and providers.While it is anticipated that the data outlined in this document will be pro
25、vided, asapplicable, by the customer and accepted by the provider, it is also recognized that theprovision of additional data may be required for dispute resolution.2.2 Document RevisionsThis document will be updated as necessary based upon resolved OBF Issues asidentified by the OBF Billing Committ
26、ee.All text revisions will be identified by a “|” in the right margin. The “|” will be placed tothe immediate right of each line of revised text.All revisions to this document will have version numbers and associated implementationtime lines.2.3 Related OBF IssuesOBF issues incorporated into this do
27、cument are displayed as Appendix A of thisdocument.2.4 Data Element RequirementsThe data element requirements (including data attributes and other pertinentinformation) are documented within the text of each field defined in Appendix B.Dispute File SpecificationsIssued: November, 2000 Revised: Decem
28、ber, 2002Page 4THIS PAGE LEFT INTENTIONALLY BLANKDispute File SpecificationsIssued: November, 2000 Revised: December, 2002Page 53.0 Dispute Data3.1 Intent of SpecificationThe paper and mechanized file specification is intended to provide, per OBF Issue2002, Dispute Information, including all informa
29、tion needed to support and resolvefacility, usage, resale, UNE and other invoice disputes except for PICC, which followsthe PICC Dispute File Specifications.3.2 DistributionDispute files are provided in support of a dispute. As such, a paper document ormechanized file should be produced each time th
30、e customer identifies a disputesituation. As negotiated between the individual customers and providers, if thecustomer is using a mechanized file, a file may be sent separately for each processingcenter within a company, or one file representing the entire company may be sent.Customers will distribu
31、te the delimited text file based on the notification process andtimeline in accordance with individual customer and provider agreements.3.3 Paper Dispute NotificationRecognizing that not all customers will be able to send and not all providers will be ableto receive an electronic image or mechanized
32、 loadable file, a paper format has beenprovided as Appendix B of this document. This appendix should be printed and sent aspaper via US Mail or other paper mailing option. Since, it is possible for a dispute toinclude more than one BAN, circuit, CLLI, or TN, separate pages may be sent with thedisput
33、e form stating the dispute details pertaining to each item.This format should be used and distributed based on the notification process andtimeline in accordance with individual customer and provider agreements.3.4 Electronic Dispute Notification ImageRecognizing that not all customers will be able
34、to send and not all providers will be ableto receive a mechanized loadable file, an electronic dispute notification image has beenprovided as Appendix B of this document. This format can be sent as a MicrosoftWord document or another word processing package document via email or diskette.Since, it i
35、s possible for a dispute to include more than one BAN, circuit, CLLI, or TN, aseparate document (spreadsheet or file) may be sent with the dispute form stating thedispute details pertaining to each item.This format should be used and distributed based on the notification process andtimeline in accor
36、dance with individual customer and provider agreements.Dispute File SpecificationsIssued: November, 2000 Revised: December, 2002Page 63.5 Mechanized File RecordsAs per the resolution to OBF Issue 2002, the mechanized file is to be provided as adelimited text file. The delimited text file was chosen
37、because it allows the receiver ofthe file to view and manipulate the data into most PC software applications (such asMicrosoft Excel or Microsoft Access). Expected delivery mediums include, but arenot limited to CD-ROM, Diskette, or e-mail. Both the customer and the provider shouldagree upon the spe
38、cific delivery medium.Section 4 of this document further discusses the mechanized file records.Dispute File SpecificationsIssued: November, 2000 Revised: December, 2002Page 74.0 File Requirements4.1 Mechanized File OrganizationEach file will contain data in support of the dispute(s). The data contai
39、ned within a fileshould be presented in the same order as discussed in Appendices C, D, and E of thisdocument.4.2 Mechanized Data FormatThe data format is a text-delimited file. The file should contain the data elementsidentified in Appendix C. See Appendices D and E for the layouts of the delimited
40、 textfile for Disputes and Resolutions.4.3 Mechanized File RecordsEach data file is comprised of three sections (e.g., Dispute File Header, Dispute FileData, and File Trailer) as follows:4.3.1 Dispute File HeaderThe first record in the file should have eight 0s (Zeros) in the Date of Claim field. Th
41、eVersion Number will reside in the Audit Number field. This would indicate thebeginning of the file.4.3.2 Dispute File DataThe dispute data fields are listed in section Appendix C of this document. The Appendixincludes the name and definition of the field as well as the data attributes, length of th
42、efield, and the appearance of the data.4.3.3 Dispute Trailer RecordThe trailer record identifies the data just processed. The Date of Claim field shouldhave 8 9s (nines) populated to identify that the record is a trailer record. In addition,the Audit Number field should be populated with the total n
43、umber of records includedin this file (including Header and Trailer). The Dispute Amount field in the Dispute FileLayout should be populated with the total dispute amount for the file.Dispute File SpecificationsIssued: November, 2000 Revised: December, 2002Page 84.3.4 Resolution File HeaderThe first
44、 record in the file should have eight 0s (Zeros) in the Date of Claim field. Thiswould indicate the beginning of the file.4.3.5 Resolution File DataThe resolution data fields are listed in section Appendix C of this document. TheAppendix includes the name and definition of the field as well as the d
45、ata attributes,length of the field, and the appearance of the data.4.3.6 Resolution Trailer RecordThe trailer record identifies the data just processed. The Date of Claim field shouldhave 8 9s (nines) populated to identify that the record is a trailer record. In addition,the Audit Number field shoul
46、d be populated with the total number of records includedin this file (including Header and Trailer). The Resolution Amount field in the ResolutionFile Layout should be populated with the total resolution amount for the file.Dispute File SpecificationsIssued: November, 2000 Revised: December, 2002Pag
47、e 9APPENDIX A - OBF ISSUES INCLUDED IN REVISIONSThis appendix contains a record of all resolved OBF Issues incorporated in revisions tothis document.OBFIssueDescription PDFS VersionNumberImplementationTime Frame2002 Standard Dispute Template 1.0 11/20002307 Develop a New Template for the DisputeFile
48、 Specifications Document2.0 11/20022348 Dispute Format Modifications 2.0 11/2002Dispute File SpecificationsIssued: November, 2000 Revised: December, 2002Page 10THIS PAGE LEFT INTENTIONALLY BLANKDispute File SpecificationsIssued: November, 2000 Revised: December, 2002Page 11APPENDIX B PAPER DISPUTE T
49、EMPLATEBilling Company Contact Information Section:1. Billing Company Name: 2. Billing Contact Name: 3. Billing Contact Address: 4. Billing Contact Phone: 5. Billing Contact Fax #: 6. Billing Contact Email: Disputing Company Contact Information Section:7. Disputing Company Name: 8. Disputing Contact Name: 9. Disputing Contact Address: 10. Disputing Contact Phone:
