EDI Implementation Guide - AT&T® Official

1 Release , 2000CB CS-20 EDI Implementation GuideEDI Bill Payment820 Transaction SetRelease Electronic Data Interchange (EDI)820 Implementation GuideRelease reserves the right to revise this document for any reason, including but not limited to,conformity with standards promulgated by various agencies, utilization of advances in the state of thetechnical arts, or the reflection of changes in the design of any equipment, techniques, or proceduresdescribed or referred to herein. Liability to anyone arising out of use or reliance upon any informationset forth herein is expressly disclaimed, and no representations or warranties, expressed or implied, aremade with respect to the accuracy or utility of any information set forth document is not to be construed as a suggestion to any manufacturer to modify or change any of itsproducts, nor does this document represent any commitment by Ameritech to purchase any productwhether or not it provides the described contained herein shall be construed as conferring by implication, estoppel, or otherwise alicense or right under any patent.

2 Whether or not the use of any information herein necessarily employsan invention of any existing or later issued reserves the right not to offer any or all of these services, and to withdraw any or all of themat any future further information, contact your Ameritech representative. 2000, Ameritech. All rights EDI Payment ProgramTable of Contents820 Implementation GuideRelease of Contents1 Ameritech EDI Billing Program .. overview .. EDI Billing Products .. and the Telecommunications Industry Forum .. Contacts for EDI Processing overview .. overview .. Ameritech Billing Acknowledgment Billing Options.

3 Bill Options .. Implementation and Assessment .. Platform Selection .. Mapping and Testing .. Testing .. Forms .. Partner Survey .. Timeline .. Partner Profile .. Partner Agreement .. Payment Methods .. overview .. Payment Method .. 820 Technical Specifications .. Transaction Set .. Versions: BPS vs. BPR .. Section Description .. BPS Specification: 820 Version ANSI X12 Specification, Version Layouts, Version 3010/Table 1 (Header).. Layouts, Version 3010/Table 2 (Detail).. Layouts, Version 3010/Table 3 (Summary).. BPR Series .. Specification: 820 Version ANSI X12 Specification, Version EDI Payment ProgramTable of Contents820 Implementation GuideRelease Layouts, Version 3020/Table 1 (Header).

4 Layouts, Version 3020/Table 2 (Detail).. Layouts, Version 3020/Table 3 (Summary).. Specification: 820 Version ANSI X12 Specification, Version Layouts, Version 4010/Table 1 (Header).. Layouts, Version 4010/Table 2 (Detail).. Layouts, Version 4010/Table 3 (Summary).. EDI Payment ProgramSection 1820 Implementation GuideAmeritech EDI Billing ProgramRelease Ameritech EDI Billing IntroductionThe purpose of this Implementation Guide is to describe the EDI Billing Products in both business andtechnical terms. It is intended for those new to EDI as well as those experienced. The estimated time toimplement the EDI payment program with Ameritech is approximately 3 to 6 months depending on acompany s level of following is a brief description of the Implementation Guide Sections:1.

5 Ameritech EDI Billing Program:This section contains background information on EDI as well as a brief description ofAmeritech s EDI Billing Products. It is a non-technical representation of the EDI Ameritech EDI Processing overview :This section specifically describes the procedures Ameritech will use to receive and manage theEDI payment Ameritech EDI Implementation Procedures:This section contains the steps necessary to implement the 820 transaction set with separate 811 Implementation Guide will address Implementation of the Billing TransactionSet. It is important to complete and return all of the paperwork in this section so that Ameritechcan manage your account with speed and EDI Payment Methods:This section describes the method currently used by Ameritech to accept payment usingElectronic Data Ameritech EDI Technical Specifications:This section contains detailed information on the structure of the Payment Order/RemittanceAdvice.

6 This section is intended as a requirements document for translator and EDI OverviewElectronic Data Interchange is often described as the computer to computer exchange of businessdocuments in a standardized format. The EDI world has evolved significantly over the past 5 years withthe introduction of many new products and services to make the Implementation process easier and moresuccessful. Although gaining in flexibility and complexity, the 820 transaction set version 4010provides essentially the same capabilities as the first set, version 2001. All of these versions areaccepted by Ameritech s EDI Payment ProgramSection 1820 Implementation GuideAmeritech EDI Billing ProgramRelease overview , ContinuedThere are four major technical components to EDI systems: standards , Translators, CommunicationLinks and Application Interfaces.

7 Each will be briefly described below:1. StandardsStandards refer to ANSI X12 Transactions or structured computer readable business are managed by a national organization known as the American National StandardsInstitute or ANSI. There are several committees within ANSI. The group that defines EDItransactions for the US and Canada is known as X12. Industries may interpret transactionsdifferently based upon a particular industry need. Several industry based groups have beenformed for EDI standards development. The telecommunication industry group is known asTCIF or the Telecommunication Industry Forum. Ameritech supports and participates in thedevelopment of EDI guidelines including the development of the Consolidated ServiceInvoice/Statement (811 transaction set) and the Payment Order/Remittance Advice (820transaction set).

8 standards are evolving, and as of late 1993, several versions of the ANSI X12 standards havebeen released. A list of the versions released and those supported by Ameritech are listed is neither required nor anticipated that a company will change with every standard release. Alltransactions become part of a release whether or not they have changed from previously ReleaseAmeritech 811 Ameritech 820 Version are made up of four components: transactions, segments and data elements anddelimiters. Transactions are made up of a series of segments and are defined by transactionnumbers assigned by ANSI X12. Segments are made up of a series of related data elements andare equivalent to data processing records.

9 Data elements are the smallest component and areequivalent to data processing fields. Delimiters are special characters used to separate dataelements and segments. Before transmission, transactions are compressed to remove all spacesfor economical data EDI Payment ProgramSection 1820 Implementation GuideAmeritech EDI Billing ProgramRelease overview , Continued2. TranslatorsTranslators are commercial software packages that make the transmission of EDI data moreefficient. The most important functions include translation of application data to EDI formatteddata (and vice versa), X12 compliance checking, version control, acknowledgment processing,audit reports and journalizing, and trading partner profile management.

10 Translators are availablefor all major platforms (PC, Mini and Mainframe). Prices on translators range from $500 to$50,000. While the purchase of a translator is not mandatory, custom development of therequired EDI functionality may be cost Communication LinksCommunication Links consists of three major routes; direct, value added networks (VANs), andgateways, which are similar to VANs. The use of VANs and gateways are the most popularroute of transmission because they remove two communication barriers, namely, time andprotocol dependence. VANs and gateways provide multiple protocol links so that a tradingpartner can access EDI transmissions from a PC, client/server, mini or mainframe independence is possible through the use of electronic mailboxes where transactions arestored until retrieved by a trading Application InterfaceThe application interface is used to connect the EDI system to existing or new applications.