1、 ATIS-0401003-0003 ORDERING AND BILLING FORUM (OBF) DISPUTE FILE SPECIFICATIONS DOCUMENT ISSUE 3 DECEMBER 2005 ATIS is a technical planning and standards development organization that is committed to rapidly developing and promoting technical and operations standards for the communications and relat
2、ed information technologies industry worldwide using a pragmatic, flexible and open approach. Over 1,100 participants from more than 350 communications companies are active in ATIS 22 industry committees, and its Incubator Solutions Program. www.atis.orgATIS 0401003-0003 Small Exchange Carrier Acces
3、s Billing (SECAB) Guidelines Is an ATIS standard developed by the following committee(s) under the ATIS Ordering and Billing Functional Group: Ordering and Billing Forum Published by ATIS 1200 G Street, NW, Suite 500 Washington, DC 20005 Copyright 2005 by Alliance for Telecommunications Industry Sol
4、utions All rights reserved. No part of this publication may be reproduced in any form, in an electronic retrieval system or otherwise, without the prior written permission of the publisher. For information contact ATIS at 202.628.6380. ATIS is online at . Printed in the United States of America. ATI
5、S-0401003-0003 Issued December 2005 Notice of Disclaimer and Limitation of Liability The information provided in this document is directed solely to professionals who have the appropriate degree of experience to understand and interpret its contents in accordance with generally accepted engineering
6、or other professional standards and applicable regulations. No recommendation as to products or vendors is made or should be implied. NO REPRESENTATION OR WARRANTY IS MADE THAT THE INFORMATION IS TECHNICALLY ACCURATE OR SUFFICIENT OR CONFORMS TO ANY STATUTE, GOVERNMENTAL RULE OR REGULATION, AND FURT
7、HER, NO REPRESENTATION OR WARRANTY IS MADE OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR AGAINST INFRINGEMENT OF INTELLECTUAL PROPERTY RIGHTS. ATIS SHALL NOT BE LIABLE, BEYOND THE AMOUNT OF ANY SUM RECEIVED IN PAYMENT BY ATIS FOR THIS DOCUMENT, WITH RESPECT TO ANY CLAIM, AND IN NO EVEN
8、T SHALL ATIS BE LIABLE FOR LOST PROFITS OR OTHER INCIDENTAL OR CONSEQUENTIAL DAMAGES. ATIS EXPRESSLY ADVISES ANY AND ALL USE OF OR RELIANCE UPON THIS INFORMATION PROVIDED IN THIS DOCUMENT IS AT THE RISK OF THE USER. Dispute File Specifications TABLE OF CONTENTS 1.0 PREFACE 1 2.0 GENERAL DESCRIPTION.
9、3 2.1 SCOPE 3 2.2 DOCUMENT REVISIONS 3 2.3 RELATED OBF ISSUES .3 2.4 DATA ELEMENT REQUIREMENTS .3 3.0 DISPUTE DATA .5 3.1 INTENT OF SPECIFICATION .5 3.2 DISTRIBUTION5 3.3 PAPER DISPUTE NOTIFICATION 5 3.4 ELECTRONIC DISPUTE NOTIFICATION IMAGE.5 3.5 MECHANIZED FILE RECORDS.6 4.0 FILE REQUIREMENTS7 4.1
10、 MECHANIZED FILE ORGANIZATION .7 4.2 MECHANIZED DATA FORMAT 7 4.3 MECHANIZED FILE RECORDS.7 4.3.1 Dispute File Header7 4.3.2 Dispute File Data7 4.3.3 Dispute Trailer Record .7 4.3.4 Resolution File Header .8 4.3.5 Resolution File Data .8 4.3.6 Resolution Trailer Record.8 APPENDIX A - OBF ISSUES INCL
11、UDED IN REVISIONS9 APPENDIX B PAPER DISPUTE TEMPLATE11 APPENDIX C - DATA ELEMENT DEFINITIONS13 A. INFORMATION PROVIDED ON THE DISPUTE LAYOUT .13 B. INFORMATION PROVIDED ON THE RESOLUTION LAYOUT.30 B.1. Data Elements to be included on the Appended Resolution File Layout.31 B.2. Data Elements to be in
12、cluded on the Stand-alone Resolution.34 APPENDIX D DISPUTE FILE LAYOUT.35 ILLUSTRATION 1 35 ILLUSTRATION 2 35 APPENDIX E RESOLUTION FILE LAYOUT38 ILLUSTRATION 1 38 ILLUSTRATION 2 38 APPENDIX E RESOLUTION FILE LAYOUT (CONTD) 39 ILLUSTRATION 3 39 ILLUSTRATION 4 39 APPENDIX F DISPUTE REASON CODES .40 A
13、PPENDIX G RESOLUTION REASON CODES .41 Issued: November, 2000 Revised: December, 2005 Dispute File Specifications THIS PAGE LEFT INTENTIONALLY BLANKIssued: November, 2000 Revised: December, 2005 Dispute File Specifications 1.0 PREFACE This document represents the Ordering and Billing Forum (OBF) Bill
14、ing Committee requirement to create a document of Dispute File Specifications for disputes other than PICC. These procedures were cooperatively developed in the OBF. They were written in response to OBF Issue 2002. All changes to this document must be presented to the OBF Billing Committee and accep
15、ted by consensus. The OBF Billing Committee is responsible for the on-going maintenance and distribution of this document based on resolved issues. The OBF is a voluntary, self-policing group of participants who meet together to identify, discuss and resolve issues which are national in scope, invol
16、ving ordering and billing of access services. The OBF functions under the auspices of the Alliance for Telecommunications Industry Solutions (ATIS). The Federal Communications Commission (FCC) authorized ATIS in a January 17, 1985 Memorandum Opinion and Order. Issued: November, 2000 Revised: Decembe
17、r, 2005 Page 1 Dispute File Specifications THIS PAGE LEFT INTENTIONALLY BLANK Issued: November, 2000 Revised: December, 2005 Page 2 Dispute File Specifications 2.0 GENERAL DESCRIPTION 2.1 Scope The Dispute File Specifications are guidelines for providing standard paper and mechanized file layouts fo
18、r facility, usage, resale, UNE and other invoice disputes except for PICC, which follows the PICC Dispute File Specifications. Implementation of these outputs such as timing and media for the mechanized file layouts (CD-ROM, Diskette, e-mail, etc.) used to provide this information will be negotiated
19、 between the individual customers and providers. While it is anticipated that the data outlined in this document will be provided, as applicable, by the customer and accepted by the provider, it is also recognized that the provision of additional data may be required for dispute resolution. 2.2 Docu
20、ment Revisions This document will be updated as necessary based upon resolved OBF Issues as identified by the OBF Billing Committee. All text revisions will be identified by a “|” in the right margin. The “|” will be placed to the immediate right of each line of revised text. All revisions to this d
21、ocument will have version numbers (displayed as the “Issue” number on the document cover page) and associated implementation time lines. 2.3 Related OBF Issues OBF issues incorporated into this document are displayed as Appendix A of this document. 2.4 Data Element Requirements The data element requ
22、irements (including data attributes and other pertinent information) are documented within the text of each field defined in Appendix C. Issued: November, 2000 Revised: December, 2005 Page 3 Dispute File Specifications THIS PAGE LEFT INTENTIONALLY BLANK Issued: November, 2000 Revised: December, 2005
23、 Page 4 Dispute File Specifications 3.0 Dispute Data 3.1 Intent of Specification The paper and mechanized file specification is intended to provide, per OBF Issue 2002, Dispute Information, including all information needed to support and resolve facility, usage, resale, UNE and other invoice dispute
24、s except for PICC, which follows the PICC Dispute File Specifications. 3.2 Distribution Dispute files are provided in support of a dispute. As such, a paper document or mechanized file should be produced each time the customer identifies a dispute situation. As negotiated between the individual cust
25、omers and providers, if the customer is using a mechanized file, a file may be sent separately for each processing center within a company, or one file representing the entire company may be sent. Customers will distribute the delimited text file based on the notification process and timeline in acc
26、ordance with individual customer and provider agreements. 3.3 Paper Dispute Notification Recognizing that not all customers will be able to send and not all providers will be able to receive an electronic image or mechanized loadable file, a paper format has been provided as Appendix B of this docum
27、ent. This appendix should be printed and sent as paper via fax, US Mail, or other paper mailing option. Since, it is possible for a dispute to include more than one BAN, circuit, CLLI, or TN, separate pages may be sent with the dispute form stating the dispute details pertaining to each item. This f
28、ormat should be used and distributed based on the notification process and timeline in accordance with individual customer and provider agreements. 3.4 Electronic Dispute Notification Image Recognizing that not all customers will be able to send and not all providers will be able to receive a mechan
29、ized loadable file, an electronic dispute notification image has been provided as Appendix B of this document. This format can be sent as a Microsoft Word document or another word processing package document via email or diskette. Since, it is possible for a dispute to include more than one BAN, cir
30、cuit, CLLI, or TN, a separate document (spreadsheet or file) may be sent with the dispute form stating the dispute details pertaining to each item. This format should be used and distributed based on the notification process and timeline in accordance with individual customer and provider agreements
31、. Issued: November, 2000 Revised: December, 2005 Page 5 Dispute File Specifications 3.5 Mechanized File Records As per the resolution to OBF Issue 2002, the mechanized file is to be provided as a delimited text file. The delimited text file was chosen because it allows the receiver of the file to vi
32、ew and manipulate the data into most PC software applications (such as Microsoft Excel or Microsoft Access). Expected delivery mediums include, but are not limited to CD-ROM, Diskette, or e-mail. Both the customer and the provider should agree upon the specific delivery medium. Section 4 of this doc
33、ument further discusses the mechanized file records. Issued: November, 2000 Revised: December, 2005 Page 6 Dispute File Specifications 4.0 File Requirements 4.1 Mechanized File Organization Each file will contain data in support of the dispute(s). The data contained within a file should be presented
34、 in the same order as discussed in Appendices C, D, and E of this document. 4.2 Mechanized Data Format The data format is a text-delimited file. Each record in the dispute file consists of data elements (“fields”) separated by commas. Depending on individual customer and provider agreements, a provi
35、der may respond to a dispute in one of two ways: by appending resolution information to the dispute file record(s) received from the customer; or by creating a stand-alone resolution file. The dispute and resolution files should contain the data elements identified in Appendix C. Appendix D describe
36、s the layouts of the delimited text file to be used for the customers Dispute. Appendix E describes the choice of two layouts for the delimited text file to be used for the providers response. 4.3 Mechanized File Records Each data file is comprised of three sections (File Header, File Data, and File
37、 Trailer) as follows: 4.3.1 Dispute File Header To indicate the beginning of a file, the first record should have eight 0s (zeros) in the first field and the Version Number of the Dispute File Specification document in the second field. (The Version Number should reflect the value and format of the
38、“Issue Number” appearing on the Title Page of this document.) The remaining fields of the first record will be empty, represented by a series of commas. 4.3.2 Dispute File Data The dispute data fields are listed in section Appendix C Part A of this document. The Appendix includes the name and defini
39、tion of the field as well as the data attributes, length of the field, and the appearance of the data. 4.3.3 Dispute Trailer Record To indicate the end of a file, the last record should have eight 9s (nines) in the first field and the total number of records in the file (including header and trailer
40、) in the second field. The Disputed Amount field should be populated with the total dispute amount for the file. The remaining fields should be empty, represented by a series of commas. Issued: November, 2000 Revised: December, 2005 Page 7 Dispute File Specifications 4.3.4 Resolution File Header To
41、indicate the beginning of a resolution file, the first record should have eight 0s (zeros) in the first field and the Version Number of the Dispute File Specification document in the second field. (The Version Number should reflect the value and format of the “Issue Number” appearing on the Title Pa
42、ge of this document.) The remaining fields of the first record will be empty, represented by a series of commas. 4.3.5 Resolution File Data The resolution data fields are listed in section Appendix C Part B of this document. The Appendix includes the name and definition of the field as well as the d
43、ata attributes, length of the field, and the appearance of the data. 4.3.6 Resolution Trailer Record To indicate the end of a resolution file, the last record should have eight 9s (nines) in the first field and the total number of records in the file (including header and trailer) in the second fiel
44、d. The Resolution Amount field should be populated with the total amount resolved for the file. All other fields should be empty, represented by a series of commas. Issued: November, 2000 Revised: December, 2005 Page 8 Dispute File Specifications APPENDIX A - OBF ISSUES INCLUDED IN REVISIONS This ap
45、pendix contains a record of all resolved OBF Issues incorporated in revisions to this document. OBF Issue Description PDFS Version Number Implementation Time Frame 2002 Standard Dispute Template 1 11/2000 2307 Develop a New Template for the Dispute File Specifications Document 2 11/2002 2348 Dispute
46、 Format Modifications 2 11/2002 2861 Billing Committee GTDD Normalization - Name 3 12/2005 2862 Billing Committee GTDD Normalization Date 3 12/2005 2863 Billing Committee GTDD Normalization - Address 3 12/2005 Issued: November, 2000 Revised: December, 2005 Page 9 Dispute File Specifications THIS PAG
47、E LEFT INTENTIONALLY BLANK Issued: November, 2000 Revised: December, 2005 Page 10 Dispute File Specifications APPENDIX B PAPER DISPUTE TEMPLATE Provider Company Contact Information Section: 1. Provider Company Name: 2. Provider Contact Name: 3. Provider Contact Address: 4. Provider Contact Phone: 5.
48、 Provider Contact Fax #: 6. Provider Contact Email: Customer Company Contact Information Section 7. Customer Billing Name: 8. Customer Contact Name: 9. Customer Contact Address: 10. Customer Contact Phone: 11. Customer Contact Fax #: 12. Customer Contact Email: General Dispute Section: 13. Date of Claim: (yyyy-mm-dd): 14. Status: 15. Claim/Audit Number: 16. Service Type: 17. ACNA: 18. OCN: 19. CIC: 20. BAN: 21. Invoice Number: 22. Short Paid Bill Date: 23. Billed Amount: $_ 24. Dispute Reason Code: 25. Dispute Desc: 26. Disputed Amount: $
