Transcription
EDI Implementation GuideEDI Bill Payment820 Transaction SetRelease 2.0Release 2.0November, 2000CB CS-20
Ameritech Electronic Data Interchange (EDI)820 Implementation GuideRelease 2.0NOTICESAmeritech 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 herein.This 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 characteristics.Nothing contained herein shall be construed as conferring by implication, estoppel, or otherwise alicense or right under any patent, whether or not the use of any information herein necessarily employsan invention of any existing or later issued patent.Ameritech reserves the right not to offer any or all of these services, and to withdraw any or all of themat any future time.For further information, contact your Ameritech representative. 2000, Ameritech. All rights reserved.
Ameritech EDI Payment Program820 Implementation GuideRelease 2.0Table of ContentsTable of Contents1 Ameritech EDI Billing Program . 1.11.11.21.31.41.52Ameritech EDI Processing Overview . 2.12.12.22.32.42.52.62.72.83Introduction . 1.1EDI Overview . 1.1Ameritech EDI Billing Products . 1.3Ameritech and the Telecommunications Industry Forum . 1.5Ameritech Contacts for EDI. 1.5Process Overview. 2.1The Ameritech Gateway. 2.1EDI Billing Transmission. 2.1EDI Enveloping. 2.2EDI Transactions. 2.2EDI Acknowledgment Processing. 2.3EDI Billing Options . 2.3Paper Bill Options . 2.3EDI Implementation Steps. 3.13.1Preparation and Assessment. 3.13.2Payment Requirements. 3.13.3EDI Platform Selection . 3.23.4Translator Mapping and Coding. 3.23.5Application Development. 3.23.6Connectivity Testing . 3.33.7End-to-End Testing . 3.33.8Maintenance . 3.33.9Implementation Forms . 3.33.9.1Trading Partner Survey . 3.43.9.2Implementation Timeline . 3.63.9.3Trading Partner Profile. 3.73.9.4Trading Partner Agreement . 3.94EDI Payment Methods . 4.14.14.25Payment Overview . 4.1CTX Payment Method . 4.2Ameritech 820 Technical Specifications . 5.15.1820 Transaction Set. 5.15.2820 Versions: BPS vs. BPR . 5.15.3820 Section Description . 5.15.4820 BPS Series. 5.35.4.1Technical Specification: 820 Version 3010. 5.35.4.2Complete ANSI X12 Specification, Version 3010 . 5.45.4.3Segment Layouts, Version 3010/Table 1 (Header) . 5.55.4.4Segment Layouts, Version 3010/Table 2 (Detail). 5.75.4.5Segment Layouts, Version 3010/Table 3 (Summary) . 5.85.5820 BPR Series . 5.95.5.1Technical Specification: 820 Version 3020. 5.95.5.2Complete ANSI X12 Specification, Version 3020 . 5.101
Ameritech EDI Payment Program820 Implementation GuideRelease 2.05.5.35.5.45.5.55.5.65.5.75.5.85.5.95.5.10Table of ContentsSegment Layouts, Version 3020/Table 1 (Header) . 5.12Segment Layouts, Version 3020/Table 2 (Detail). 5.14Segment Layouts, Version 3020/Table 3 (Summary) . 5.16Technical Specification: 820 Version 4010. 5.17Complete ANSI X12 Specification, Version 4010 . 5.18Segment Layouts, Version 4010/Table 1 (Header) . 5.20Segment Layouts, Version 4010/Table 2 (Detail). 5.22Segment Layouts, Version 4010/Table 3 (Summary) . 5.242
Ameritech EDI Payment Program820 Implementation GuideRelease 2.01Section 1Ameritech EDI Billing ProgramAmeritech EDI Billing Program1.1IntroductionThe 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 experience.The following is a brief description of the Implementation Guide Sections:1.21.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 BillingProducts.2.Ameritech EDI Processing Overview:This section specifically describes the procedures Ameritech will use to receive and manage theEDI payment program.3.Ameritech EDI Implementation Procedures:This section contains the steps necessary to implement the 820 transaction set with Ameritech.A 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 accruacy.4.EDI Payment Methods:This section describes the method currently used by Ameritech to accept payment usingElectronic Data Interchange.5.Ameritech EDI Technical Specifications:This section contains detailed information on the structure of the Payment Order/RemittanceAdvice. This section is intended as a requirements document for translator and applicationprogrammers.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 bank.1.1
Ameritech EDI Payment Program820 Implementation GuideRelease 2.01.2Section 1Ameritech EDI Billing ProgramEDI Overview, ContinuedThere are four major technical components to EDI systems: Standards, Translators, CommunicationLinks and Application Interfaces. Each will be briefly described below:1. StandardsStandards refer to ANSI X12 Transactions or structured computer readable business documents.Standards 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).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 below.It 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 releasedversions.X12 ReleaseVersion 2.0Version 2.1Version 2.2Version 2.3Version 2.4Version 3.1Version 3.2Version 3.3Version 3.4Version 4.1Ameritech 811NoNoNoNoNoNoNoNoNoYesAmeritech 820NoYesYesYesYesYesYesYesYesYesStandards 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. 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 transfer.1.2
Ameritech EDI Payment Program820 Implementation GuideRelease 2.01.2Section 1Ameritech EDI Billing ProgramEDI 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. 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 prohibitive.3. 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 environment.Time independence is possible through the use of electronic mailboxes where transactions arestored until retrieved by a trading partner.4. Application InterfaceThe application interface is used to connect the EDI system to existing or new applications. Anapplication interface can be a manual or automated interface. The application interface canprovide outbound data or receive inbound data. For the Ameritech EDI Billing Products, thetrading partner will need to provide an application interface to process EDI data in order toaccept bills (811 transactions) or issue payments (820 transactions). Combinationtranslator/application interface packages are available on various computer platforms, includingPCs, from third party vendors. Section 3 of this guide will describe each of these components asit relates to implementing EDI with Ameritech.1.3Ameritech EDI Billing ProductsAmeritech offers three EDI Billing Products: the EDI Summary Bill, the EDI Detail Bill and the EDIBill Payment. This Implementation Guide addresses EDI Bill Payment. The EDI Detail Bill and theEDI Summary Bill use a separate Implementation Guide available upon request from an Ameritech EDIRepresentative. All three products are briefly described below:EDI Summary BillThe EDI Summary Bill is sent to Ameritech EDI trading partners using the ANSI X12 811Transaction Set. The objective of the EDI Summary Bill is to provide Ameritech tradingpartners with summary level bill information in an electronic format. The EDI Summary Bill isintended for Ameritech trading partners who wish to perform high level bill processing andelectronic bill payment.1.3
Ameritech EDI Payment Program820 Implementation GuideRelease 2.0Section 1Ameritech EDI Billing Program1.3 Ameritech EDI Billing Products, ContinuedThe EDI Summary Bill contains three sections. The header section contains account informationsuch as invoice number, invoice date and payment terms. The detail section contains bill sectionsubtotals for each service provider with no additional detail information. The summary sectioncontains bill balance, payment and adjustment amounts. A detailed description of this product isprovided in Section 4.3 of the EDI 811 Transaction Set Implementation Guide.EDI Detail BillThe EDI Detail Bill is sent to Ameritech EDI trading partners using the ANSI X12 811Transaction Set. The objective of the EDI Detail Bill is to provide Ameritech trading partnerscomplete billing information in an electronic format. Ameritech trading partners who intend toperform detail analysis of telecommunication usage and billing are the intended subscribers ofthis product offering. The EDI Detail Bill is offered at no charge (with the eventual eliminationof the paper bill) to the trading partner when delivered through the Ameritech Gateway.The EDI Detail Bill contains three sections. The header section contains account informationsuch as invoice number, invoice date and invoice terms. The detail section contains bill sectionsubtotals for each service provider with supporting detail information such as Toll Call detail,Optional Calling Plan information. Other Charges and Credit line items, Directory Assistanceinformation and other billing data. The Summary section contains bill balance, payment andadjustment amounts. A detailed description of this product is provided in Section 4.4 of the 811Transaction Set Implementation Guide.EDI Bill PaymentThe EDI bill payment is sent to Ameritech from their EDI trading partners using the ANSI X12820 transaction set. The EDI bill payment uses a process known as EDI/EFT or Financial EDI,whereby the 820 transaction is routed through banks capable of processing EDI transactions(known as Value Added Banks, or VABs). While Ameritech does not charge for this service, thetrading partners bank may charge a fee for EDI/EFT transaction processing. The EDI billpayment can be used in conjunction with the EDI Detail Bill or EDI Summary Bill.The EDI bill payment also contains three sections. The header section contains payee and payerinformation including the total payment amount. The detail section contains information on oneor more invoices that are to be paid by this transaction. The summary section containstransaction control information only. This 820 Implementation Guide provides all of the detailson Ameritech’s EDI Payment Program.1.4
Ameritech EDI Payment Program820 Implementation GuideRelease 2.01.4Section 1Ameritech EDI Billing ProgramAmeritech and the Telecommunications Industry ForumAmeritech is an active member of the TCIF (Telecommunications Industry Forum) EDI Committee.The ANSI X12 811 standards described in this document conform to the guidelines defined by theTCIF. The ANSI X12 820 transaction, like other standards, is evolving and Ameritech is committed toremaining current with changes recommended by the TCIF EDI committee.1.5Ameritech Contacts for EDIIf you have questions about the Ameritech EDI Billing Program, please contact your accountrepresentative or the Alternate Bill Media Helpdesk @888-800-6325, Option #2.1.5
Ameritech EDI Processing Overview820 Implementation GuideRelease 2.022.1Section 2Ameritech EDI Processing OverviewAmeritech EDI Processing OverviewProcess OverviewFor the purposes of this guide, EDI bill payment is executed when a trading partner electronicallyauthorizes their bank to debit funds from their account by a specified amount, and authorizesAmeritech’s bank to credit Ameritech’s account by that same amount. There are three methods forperforming this that employ EDI 820 Payment Order/Remittance Advice transactions. These methodsare described more fully in Section 4.The bill payment process operates slightly differently than Ameritech’s EDI billing process, because itdeals with actual payment of funds and requires communication with financial institutions rather thandirectly with Ameritech. This is the case whether the trading partner currently receives their Ameritechbill in paper form or via EDI. The Ameritech trading partner transmits an EDI 820 PaymentOrder/Remittance Advice to a bank, either the trading partner’s or Ameritech’s. Notification that thetransaction was successfully received comes back from the bank, not Ameritech. Please see Section 4for more information on the payment methods available.2.2The Ameritech GatewayThe Ameritech Gateway is an electronic bridge between companies, networks and third party providers.It is a full function store and forward mailbox with interconnections to major networks. Ameritechprovides trading partners a mailbox and free access to the Gateway for sending and receiving EDIBilling Products. If a trading partner wishes to use their existing VAN to send the 820 transaction,interconnections to these VANs can be arranged.2.3EDI Billing TransmissionThe EDI Billing Transmission consists of one or more 820 transactions and the required EDIEnveloping as shown in the following diagram. A trading partner may transmit 820s whenever desired;during the business day or at any other time, and as many times per day as desired. Ameritech’s bank,and most value-added banks, will process the 820s they receive once per business day.2.1
Ameritech EDI Processing Overview820 Implementation GuideRelease 2.02.4Section 2Ameritech EDI Processing OverviewEDI EnvelopingEDI Enveloping has two components, the Interchange Envelope (ISA/IEA) and the Functional GroupEnvelope (GS/GE). The Interchange Envelope is used to route the transaction throughtelecommunication links from the sender to receiver. It also has security and authorization codes andtransaction version information. The Functional Group envelope is used to group a series of liketransactions into a single envelope. The 820 Transaction Set uses the “PG” Functional Group Identifier.2.5EDI TransactionsEDI Transactions are a series of data segments and elements used to represent common businessdocuments in a standardized computer readable format. Ameritech uses the 820 transaction set asdefined by the national EDI standards setting committee called ANSI X12. Ameritech also followsindustry guidelines established by the Telecommunication Industry Forum (TCIF) EDI Committee andis an active member of this industry group.The 820 transaction consists of the payment amount and one or more invoices to be satisfied by thispayment. A detailed description of the EDI Payment Order/Remittance Advice can be found in section5 of this document.2.2
Ameritech EDI Processing Overview820 Implementation GuideRelease 2.02.6Section 2Ameritech EDI Processing OverviewEDI Acknowledgment ProcessingEDI Acknowledgments are used as a control mechanism to ensure the successful delivery of EDIdocuments through telecommunication links. Acknowledgment protocols will be coordinated betweenthe trading partner and the trading partner’s Value-Added Bank (VAB). The 997 transaction set is themost common acknowledgment document and the one recommended by Ameritech. The purpose of the997 Functional Acknowledgment is to communicate to the sender of a document the successful receiptof an EDI transaction. The 997 transaction set also communicates that the received document is incompliance with X12 standards, but does not authorize the content of the transaction. Oneacknowledgment per functional group can be expected from Ameritech’s bank or your own bank within24 hours of a transmission, depending on the payment method you select. Most commercial translatorsoftware provides automatic acknowledgment processing as an option.2.7EDI Billing OptionsAmeritech offers a number of billing media, including paper, magnetic tape, and electronic delivery.The 820 transaction is offered as a payment method for all billing options.2.8Paper Bill OptionsAmeritech offers three options for receiving a paper bill. The first option is the one you are most likelyreceiving today, the full detail paper bill. The second option is for trading partners who receive theAmeritech bill in an electronic format (like EDI), but wish to pay using traditional methods (the papercheck). For these trading partners, only the first page of the bill containing the payment stub is mailed.The third option eliminates all paper bills and is only available to trading partners who payelectronically, or via another automated method, and those trading partners receive a bill electronicallyor in some other non-paper format.2.3
Ameritech EDI Payment Program820 Implementation GuideRelease 2.03Section 3EDI Implementation StepsEDI Implementation StepsAmeritech’s EDI Billing Program breaks down the implementation of EDI into nine major phases. Eachphase is described below and the EDI Implementation Forms can be found in the following pages.3.1Preparation and AssessmentThe objective of the EDI Preparation and Assessment phase is to gain an understanding of what isinvolved in an EDI implementation, identify the benefits to be achieved, secure commitment from allstakeholders and to assemble a plan for implementation.This phase can take from a few weeks to several months depending on your company’s experience withEDI and your management’s commitment to implementing EDI systems. EDI offers great benefits, butimplementations are complex and require the cooperation of many different departments within acompany. Implementation of an EDI system for the first time within a company has often required theefforts of an “EDI champion”. EDI champion is a common term given to the person who sees thebenefits of EDI and commits to its implementation despite the obstacles.Ameritech requests that you submit the Trading Partner Survey during this phase of theimplementation. The Trading Partner Survey will provide us with EDI contact information and help usdetermine your EDI experience and the level of assistance you may require from the EDI TradingPartner Support team.3.2Payment RequirementsThe objective of this phase is to establish the requirements of your payment applications.Section 4 of this guide describes the EDI payment method Ameritech will support. The selection of anEDI payment method will depend heavily on existing systems. If your bank is not a VAB (see section1.3), then it cannot process transactions like the 820. Ameritech urges you to consult your bank on thebest method to pursue.Once you have established your requirements and are aware of your general implementation plan,Ameritech requests that you submit the Implementation Timeline form. This will allow Ameritech toschedule the activities to support your implementation. Ameritech will be very flexible concerningthese dates -- delays can be expected -- but this timeline will provide us with a general time frame towork from.3.1
Ameritech EDI Payment Program820 Implementation GuideRelease 2.03.3Section 3EDI Implementation StepsEDI Platform SelectionThis phase is only applicable to first time EDI implementations or companies that will use a separateEDI system for their payment processing. The objective of this phase is to evaluate and select thecomponents required to perform EDI transmissions. The major components are an EDI translator and aCommunication Link.The EDI translator, as described in Section 1, converts application data to EDI formatted data or viceversa. There are several commercially available translator packages on the market and based on therequirements established in the previous phase, trading partners will need to evaluate and select thetranslator that will best meet their needs. The custom development costs of this component cannot bejustified for most companies.The Communication Link refers to the communication software package, the modem hardware, thetelephone line, and the Value Added Network. There are many communication software packages onthe market that each trading partner will need to evaluate to be able to select a package that meets theirindividual requirements. The trading partner must also select one of two types of phone lines, dial-up ordirect. For most companies dial-up is more than adequate. If data volume is very high, a direct line maybe cost justified. As for a value added network, Ameritech offers access to the Ameritech Gateway at nocost for their EDI Billing Products
This Implementation Guide addresses EDI Bill Payment. The EDI Detail Bill and the EDI Summary Bill use a separate Implementation Guide available upon request from an Ameritech EDI Representative. All three products are briefly described below: EDI Summary Bill The EDI Summary Bill is sent to Ameritech
