Verizon EDI 811 User Manual

EDI Billing Implementation Guide

811 Transaction Set

EDI 811 Invoices from Verizon

August 2017 Verizon 811 Guide – v17.4

Trading Partners Business Customers

Verizon

Transmission Process

997 Transaction Set

811 Transaction Set

August 2017

2.0

Disclaimers

This document and the information contained within are provided by Verizon1 subject to the limitations of liability and other terms of its related service agreement(s) and without warranty of any kind. Further and without limitation, Verizon and its affiliated companies disclaim all warranties, express or implied, including without limitation, warranties of fitness for a particular purpose, against infringement, or merchantability. In addition to and without limitation of any other limitation of liability of Verizon or its affiliated companies set forth in an applicable tariff or elsewhere, in no event shall Verizon or its affiliated companies, or their agents or suppliers, be liable under contract, warranty, tort, or any other legal theory, for any incidental, consequential, punitive, special or indirect damages arising from or relating to this document or its contents, even if advised of the possibility of such damages.

Confidentiality

This document and the information contained within represent proprietary information of Verizon or its affiliated companies and suppliers. No use, reproduction or disclosure is permitted except as expressly authorized in an applicable tariff of, or written agreement with, Verizon or its affiliated companies.

Trading Partner Information

Verizon bills customers for services provided by Verizon and other service providers on a monthly basis (except as otherwise agreed). There is no connection between Verizon and other, non-affiliated service providers.

Residential customer accounts should refer disputes or discrepancies to your business office/service representative or consult the Rights and Responsibilities section of your local telephone book for

information

The Verizon names and logos and all other names, logos and slogans identifying Verizon's products and services are trademarks and service marks or registered trademarks and service marks of Verizon Trademark Services LLC or its affiliates in the United States and/or other countries. All other trademarks and service marks are the property of their respective owners

“Verizon” refers to the Verizon entities that provide the services to which the EDI and other billing-related

services addressed in this document apply.

August 2017

2.0

Verizon

811 – Transaction Set

EDI Billing

Version 004010

Implementation Guide

Introduction

TABLE OF CONTENTS:

1. Introduction...................................................................................................................3

1.1 Overview ........................................................................................................................3

1.2 Purpose of Guide................................................................................................ .............3

1.3 Scope and Applicability.....................................................................................................3

1.4 Document Contact Information ..........................................................................................4

1.5 Implementation Considerations ................................ ..........................................................4

1.6 Modes of Operation .........................................................................................................4

1.7 Recovery Procedures ................................ .......................................................................4

1.8 How to use the EDI Billing Implementation Guide .................................................................5

2. Telecommunications Billing Overview.............................................................................6

2.1 Verizon’s Business Model .................................................................................................6

2.2 Verizon Bill Presentation ...................................................................................................7

2.3 Formats of Bills Provided ................................................................ ..................................9

2.3.1 Summary-Level Format ..........................................................................................9

2.3.2 High-Level Format .................................................................................................9

2.3.3 Summarized Detail-Level Format .............................................................................9

2.3.3.1Summarized Detail-Level Format – Call Details ..........................................................9

2.3.3.1Summarized Detail-Level Format – Conference Call.................................................. 10

2.3.4 Full Detail-Level Format ........................................................................................ 10

2.4 Structure of the 811 ....................................................................................................... 10

2.5 Use of the 820............................................................................................................... 11

2.6 Information to Have When Contacting Verizon ................................................................... 12

2.7 Data Element Separator, Segment Terminator and Component Element Separator ................. 12

2.8 ASC x12 Extended Character Set .................................................................................... 12

3. Envelope Control Structure .......................................................................................... 13

3.1 Interchange Envelope .................................................................................................... 13

3.2 Functional Group Envelope ............................................................................................. 15

3.3 Transaction Set Envelope ............................................................................................... 16

4. Understanding Hierarchical Levels (HL) ........................................................................ 17

5. Verizon’s Use of the EDI 811 Hierarchical Levels (HL) .................................................... 20

6. Heading Section of the EDI 811 ..................................................................................... 21

7. Detail Section of the EDI 811......................................................................................... 25

7.1 High-Level (HL1 through HL4) Examples:.......................................................................... 25

7.1.1 HL1 – Service Provider ......................................................................................... 25

7.1.2 HL2 – Sub-Account Charges on the Master Account’s Bill .......................................... 29

7.1.3 HL3 – Location / Account ...................................................................................... 31

7.1.4 HL4 – Type of Charge – IT1 .................................................................................. 35

7.2 Detail-Level (HL5 through HL9) Examples: ........................................................................ 37

7.2.1 HL5 – Circuit, Switch Board and/or Centrex ............................................................. 37

7.2.2 HL6 – Circuit Component, Customer Reference Number, Vendor Order Number, Service

Number and/or BAC.) ..................................................................................................... 42

7.2.3 HL7 – Earning Number, WTN, Billing Number, Calling Card, Conference and/or other Billing Information. 46

7.2.4 SV~0110: Recurring ................................ ............................................................ 48

7.2.5 SV~0200: Monthly Service Charge ................................ ........................................ 48

7.2.5.1 Centrex Addendum to SV~0200 (IT107 = 0200 and (SLN10 = 220 or 225)) 58

August 2017

Verizon

811 – Transaction Set

EDI Billing

Version 004010

Implementation Guide

Introduction

7.2.6 SV~0305: Service and Equipment Information ......................................................... 62

7.2.7 SV~0400: Other Charges & Credits /Additions & Changes ........................................ 62

7.2.8 SV~0500: Itemized Call........................................................................................ 69

7.2.8.1 WATS Addendum to SV~0500 (IT107 = 0500, SLN10 = 1000) 76

7.2.8.2 ISDN Addendum to SV~0500 (IT107 = 0500, SLN10 = 1420) 81

7.2.8.3 CLASS Addendum to SV~0500 (IT107 = 0500, SLN10 = 1615) 86

7.2.8.4 Extended Area Addendum to SV~0500 (IT107 = 0500, SLN10 = 1830) 90

7.2.8.5 Conferencing Charges under SV~0500 92

7.2.9 SV~0510: Interexchange Carrier Invoice Billing ..................................................... 115

7.2.10 SV~0600: Directory Advertising........................................................................... 119

7.2.11 SV~0700: Usage............................................................................................... 121

7.2.12 SV~0705: Measured Service .............................................................................. 128

7.2.13 SV~0710: Message Rate Service ................................................................ ........ 134

7.2.14 SV:0715: CABS Usage ...................................................................................... 138

7.2.15 SV~0800: Optional Call Plan / Discount Plan......................................................... 142

7.2.16 SV~0900: Directory Assistance ........................................................................... 147

7.2.17 SV~1000: WATS............................................................................................... 153

7.2.18 SV~1400: Other Voice Service ............................................................................ 158

7.2.19 SV~1420: ISDN Service ................................ ..................................................... 163

7.2.20 SV~1600: Non-Voice Service.............................................................................. 167

7.2.21 SV~1605: Packet Switching ................................................................................ 170

7.2.22 SV~1740: Miscellaneous .................................................................................... 171

7.2.23 SV~1820: Voice Mail ......................................................................................... 172

7.2.24 SV~1830: Extended Area ................................ ................................................... 176

7.2.25 SV~1990: Other Line Charge .............................................................................. 178

7.2.26 SV~2600: Late Payment Charges........................................................................ 178

7.3 Summary/Consolidated Billing ....................................................................................... 184

7.3.1 expressTRAK Summary Billing ............................................................................ 185

7.3.2 CBSS Summary Billing ....................................................................................... 186

7.3.3 CRIS Summary Billing ........................................................................................ 188

7.3.4 IX Plus Summary Billing ...................................................................................... 188

7.3.4.1 IX Plus Master Account with Full Financial Responsibility 189

7.3.4.2 IX Plus Master Account with Partial Financial Responsibility 191

7.3.5 Mega Audio Summary Billing ............................................................................... 199

7.3.6 Vision V5 Summary Billing .................................................................................. 202

SV~2050: Total Amount Billed (for Summary/Consolidated Billing Only) .............................. 204

8. Summary Section of the EDI 811 ................................................................................. 208

9. Auditing the EDI 811 .................................................................................................. 213

August 2017

9.1 Determining Segment Amount ....................................................................................... 213

9.1.1 Detail Section: ................................................................................................... 213

9.1.2 Summary Section:.............................................................................................. 214

9.2 Auditing the Detail Section ................................ ............................................................ 214

9.2.1 8.2.1 Balancing the SLN Segment Amount ............................................................ 214

9.2.2 Balancing the IT1 Segment Amount ...................................................................... 215

9.2.3 Balancing the TDS Segment Amount .................................................................... 215

9.3 Auditing the Summary Section ....................................................................................... 216

9.3.1 Balancing to the Total Transaction Amount “TT” Segment Amount ............................ 216

9.3.2 Balancing to the Service Provider Net Adjustment................................................... 217

Verizon

811 – Transaction Set

EDI Billing

Version 004010

Implementation Guide

Introduction

1. Introduction

1.1 Overview

Verizon provides Electronic Data Interchange (EDI) and Electronic Funds Transfer capabilities for telephone billing invoices. Verizon uses the Consolidated Services Invoice/Statement, 811 Transaction Set as developed by ASC (Accredited Standards Committee) X12 with the assistance of the Alliance for Telecommunications Industry Solutions (ATIS)-sponsored Ordering and Billing Forum (OBF) EDI Telecommunications Billing (ETB) which was formerly called TCIF.

Verizon is a member of OBF. This customer guide adheres wherever possible to the EDI Guidelines as set forth by that organization. However, it may be necessary to deviate from those guidelines in order to present specific charges. Verizon will continue to work with the EDI Telecommunications Billing (ETB) committee to provide an industry-consistent version of the 811 Transaction Set.

1.2 Purpose of Guide

This document, the Verizon EDI Billing Implementation Guide, provides an overview of Verizon’ EDI billing

processes. It serves as a “guide” in assisting trading partners with implementation and operation of the 811

Telephone Billing Transaction Set with Verizon. The EDI 811 is available at no additional charge to customers. The EDI 811 files are delivered as an

electronic transmission. The official copy of the invoice remains the paper invoice and/or the PDF version available to you via the Verizon Enterprise Center

The purpose of this guide is to provide trading partners with a standardized definition of the information Verizon provides on the 811 Telephone Bill.

It is intended to serve as a means of achieving consistency in implementation as well as in documenting the EDI capabilities of Verizon's telephone billing systems. This EDI Billing Implementation Guide is specific to Verizon use of the 811 Transaction Set and provides information about the structure and values associated with a Verizon bills.

Verizon has many billing systems. We provide one EDI 811 format/structure for these bills. However, each of the billing systems have their own peculiarities that cause the data content within the Verizon standard EDI 811 structure to vary. Because of the uniqueness or each billing system, Verizon identifies the originating billing system via the sender DUNS number and via a REF~06 in position 050 of the header.

This guide should be used in conjunction with the ASC X12 Version 4 Release 1 standards and the OBF/ETB EDI Guidelines - Telecommunications Billing Issue 9, Revision 4. Use both the ASC X12 and the

OBF/ETB as a reference for general questions about the 811 Transaction Set. A comprehensive list of

segments, data elements, and element values used by Verizon is provided in Appendix A of this guide. NOTE: Normal and customary updates to OBF/ETB Section 10.4 Telecommunications Additional Code

Lists, are done (completed) quarterly. Verizon can implement value additions or changes immediately after approval (publication or issuance). Trading Partners need to be familiar with these quarterly updates and be prepared to accept the changes.

1.3 Scope and Applicability

Verizon has produced this EDI Billing Implementation Guide for use by their EDI trading partners and is responsible for its content. This guide contains the information necessary for EDI implementation related to billing of telecommunication services with Verizon.

August 2017

Verizon

811 – Transaction Set

EDI Billing

Version 004010

Implementation Guide

Introduction

1.4 Document Contact Information

Comments or questions about this guide as well as technical questions about the EDI interface, EDI transmissions or Electronic Funds Transfer may be sent in an email to EDI-Implementation@verizon.com.

OBF/ETB EDI Guidelines - Telecommunications Billing Issue 9, Revision 4 may be obtained by calling the Alliance for Telecommunications Industry Solutions (ATIS) at 202-628-6380 and are available on the Internet within the Electronic Telephone Billing home page at http://www.atis.org.

ASC X12 forms and documents may be obtained from Data Interchange Standards Association, Inc. (DISA) by calling (703) 970-4480 or through the home page at http://www.disa.org.

1.5 Implementation Considerations

When a customer is ready to receive telephone billing transaction sets, Verizon will discuss a pilot program plan and develop a schedule for test transmissions. This is necessary to maintain system integrity and avoid any misunderstandings when implementing telephone billing. The pilot program will allow Verizon to test in-house system capability to meet the customer's telephone billing requirements, our EDI translation placement of the standards information and the negotiated method of transmission. Our trading partners will be able to test their method of transmission, their translation interface and their in-house system's ability to handle the telephone billing information. This guide will help clarify the data presentation by identifying where the telephone billing information will be placed in the 811 transaction set so that trading partners are able to prepare for the testing and implementation.

1.6 Modes of Operation

Verizon is prepared to begin telephone billing pilot programs with trading partners using the 811 transaction set as described in this customer guide. A pilot program sets time frames for testing in a parallel mode until our trading partners verify the EDI transmission and the ability of their systems to process the telephone bill. A parallel mode means that hard copy paper bills are sent in the normal production mode while EDI test transmissions are received. Once a consistent processing environment has been attained, Verizon will set up an implementation date for a cutover to a production mode.

1.7 Recovery Procedures

Verizon endeavors to provide an accurate and responsive EDI environment but occasionally errors may occur or data maybe lost or destroyed. Each trading partner should be prepared for and capable of reproducing any electronic transmission and/or providing backup paper documents within a reasonable time in order to fulfill business requirements.

Requests for assistance with EDI or the eFTP data communications application may also be addressed to Verizon Enterprise Center Support by calling toll free: 1-800-569-8799 or sending an email to vec-

support@verizon.com.

Your Verizon account team, Sales or Service representative, remains your resource for resolution or obtaining appropriate resources.

Verizon requires a 997 Functional Acknowledgment for each telephone billing transmission, as indicated in the ISA segment (ISA14) of the EDI transmission envelope. This is our standard operating procedure, which helps to track transmissions and verify receipt.

August 2017

Verizon

811 – Transaction Set

EDI Billing

Version 004010

Implementation Guide

Introduction

1.8 How to use the EDI Billing Implementation Guide

Verizon’s EDI Billing Implementation Guide is divided into several sections.

Section 1, Introduction, gives an overview of Verizon perspective, addresses some business issues and provides a description of this guide.

Section 2, Telephone Billing Overview explains the formats and types of Verizon telephone bills and provides the structure of the 811.

Section 3, Transaction Set Conventions contains the envelope requirements and control structure, the 811 transaction set which includes the segment listings and all of the data segments and data elements used by Verizon.

Section 4, Understanding Hierarchical Levels contains the structure and outlines the dependencies of hierarchical levels of telephone billing information provided in the Detail Area of the 811 transaction set. Section 4 provides a hierarchical level chart for the nine billing levels and the information found on each level.

Section 5, Heading Section provides a table of segments depicting the structure of the heading section of the 811. After the structure table a sample mapping for the heading section is displayed with an explanation of each segment.

Section 6, Detail Section provides a sample mapping and explanation of each segment for the respective Hierarchical Levels/services. Section 6 contains three sub-sections:

6.1 High-Level (HL1 through HL4): Provides a table of segments depicting the structure of the 811 detail portion for Hierarchical Levels 1 - 4.

6.2 Detail-Level (HL5 through HL9: Provides an overview of Hierarchical Levels 5 - 7 and sample mapping and explanation for specific services depicting the use of hierarchical levels 5 - 9.

6.3 Summary/Consolidated Billing: Provides a table of segments depicting the structure of the Summary/Consolidated billing 811. After the structure table a sample mapping is displayed and is followed with an explanation of each segment.

Section 7, Summary Area provides a table of segments depicting the structure of the summary section of the 811. After the structure table a sample mapping for the summary section is displayed and is followed with an explanation of each segment.

Section 8, Auditing the 811 Transaction Set explains the “summing rules” and how to balance supporting detail charges to the appropriate summary level charge.

Appendix A, Detailed Segment and Data Element provides definitions and usage rules.

August 2017

Verizon

811 – Transaction Set

EDI Billing

Version 004010

Implementation Guide

Overview

Trading

Partners

Remittance

Information

Financial Institutions

Telephone Bill (811)

Remittance Information

Payment Order/Remittance Information (820)

Verizon Telephone Billing

Information Flowchart

EFT

Trading

Partner

Verizon

Functional Acknowledgment (997)

Verizon

2. Telecommunications Billing Overview

2.1 Verizon’s Business Model

The business model diagram below shows the transaction flow between Verizon and their trading partners (TP) for telecommunications billing information.

 A telecommunications bill, 811 transaction set, is initiated by Verizon and sent to the trading

partner.

 The trading partner receives the 811 transaction set, verifies the transmission's syntax and control

structure information and sends a functional acknowledgment (997) to Verizon.

 Trading partner processes the 811 transaction set, verifies the information and approves for

payment. A payment order/remittance advice (820) may be generated and sent to the trading

partner’s bank.

 The trading partner’s bank renders payment to Verizon's bank by Electronic Funds Transfer (EFT)

and forwards the remittance advice to Verizon.

 Alternate methods of payment include:

August 2017

Verizon

811 – Transaction Set

EDI Billing

Version 004010

Implementation Guide

Overview

 Payment order may be sent to the trading partner's bank and the remittance advice may be

transmitted to Verizon Accounts Receivable.

 Paper check may be sent directly to Verizon with paper remittance advice.  Online payment through a variety of options may be managed through the Verizon Customer

Center portal.

2.2 Verizon Bill Presentation

Verizon provides one implementation for the 811 transaction set across the entire national footprint. However, the data presented in the 811 transaction set can vary by the different billing systems. It is important to be aware of these various systems. For example, to identify billed products some billing systems use USOCs, others Product Elements, POEs, and others ISOCs (similar to USOCs). Verizon also uses ANSI X12 Special Charge or Alliance Codes in the EDI 811 to assist with categorization of charges. A complete list of codes is available from the X12 Standards Guide. While Verizon is in the process of collapsing the number of billing systems used, the different supported billing systems today are:

 CABS - Carrier Access Billing.  CBSS - Local Exchange Carrier (LEC) billing for former GTE footprint (AZ, CA, FL, ID, IL, IN, KY,

MI, MO, NC, NJ, NV, NY, OH, OR, PA, SC, TX, VA, VC, WA and WI).

 CRIS - Local Exchange Carrier (LEC) billing for Connecticut, Delaware, Maine, Massachusetts,

New Hampshire, New Jersey, New York, Pennsylvania, Rhode Island and Vermont.

 expressTRAK - Local Exchange Carrier (LEC) billing for District of Columbia, Maryland, Virginia

and West Virginia.

 GCS – the GCS billing system is composed of following billing subsystems:

 GCS (Cycle 1 - 4) - International Private Line, Hyperstream, Mexico GDL, GBL, IPL

Internet Service, VSAT

o Service Type is presented in the NM1 loop at HL3. o Circuit ID is included in the Service Type and presented in NM1 loop at

HL3. There is only one circuit per location.

 GCS (Cycle 5) - Managed Services

o Service Type is presented in the NM1 loop at HL3.

 GCS F&E (Cycle 8) - International Frame Relay

o Service Type is presented in the NM1 loop at HL3.

 GCS GIS (Cycle 9) - Global Inbound Service - US

o Calls Details are not currently available on the VB811: IT1 SV~0500

will not contain details

 GIS EMEA (Cycle 10) - Global Inbound Service - Europe

o Calls Details are not currently available on the VB811: IT1 SV~0500

will not contain details

 GIS ASIA PAC (Cycle 11) - Global Inbound Service - Asia

o Calls Details are not currently available on the VB811: IT1 SV~0500

will not contain details

 ASIA PAC VOIP (Cycle 15 & 16) - Direct Voice - Asia

o Calls Details are not currently available on the VB811: IT1 SV~0500

will not contain details

 GCS (Cycle 30) - International Private Line

o The circuit termination locations is presented in the NM1 loop at HL3.

August 2017

Verizon

811 – Transaction Set

EDI Billing

Version 004010

Implementation Guide

Overview

 Global Voice VPN (GVV) (Cycle 32) - International Global Voice VPN billing

system. (Global Outbound Service)

 GCS Mega (Cycle 36) - Frame Relay  Global Managed Mobility (Cycle 40) - Global Managed Mobility

 ICI Credit Notes - Credit notes issued against previous invoices. Certain countries require that

adjustments to a previous invoice be issued as a separate document.

 ICI Credit Notes are only issued against Prime Biller (REF*06*MU) or Prime Biller Next

Gen (REF*06*PO).

 ICI Debit Notes - Debit notes issued against previous invoices. Certain countries require that

adjustments to a previous invoice be issued as a separate document.

 ICI Debit Notes are only issued against Prime Biller (REF*06*MU) or Prime Biller Next Gen

(REF*06*PO).

 IX Plus - Voice and integrated Billing including local, internet dial, audio conferencing, integrated

frame relay, and integrated private line, etc.

 Mega Voice - Conferencing (audio and net) billing.  Millennium - International audio and video conferencing.  NBBE - Billing for Verizon Long Distance.  NCBS (IBRS) - Integrated Billing & Reporting Solution, formerly known in former MCI as Vnet®, is

a strategic billing platform that bills a wide range of integrated services including long distance, toll free, local, switch digital services (domestic and international), Internet dial with voice, conferencing (audio, video, net and document) private line, data services, security services and web/collation/managed hosting, etc.

 NCBS (Vision) - Voice billing that includes long distance, local, switched digital services,

conferencing, etc.

 Prime Biller – International Billing

Notes:

1. Currently, the VB811 only processes Prime Biller standalone accounts. In a future

release we plan to add Prime Biller Parent / Child accounts.

2. ICI Credit Notes & ICI Debit Notes can be issued against Prime Biller accounts.

Customers that have Prime Biller accounts need to be prepared to receive VB811s for ICI Credit Notes & ICI Debit Notes. Please ensure your communications and translator is setup to for ICI Credit Notes & ICI Debit GS02s.

 Prime Biller Next Gen – US and International Billing

Notes:

1. Currently, the VB811 only processes Prime Biller standalone accounts. In a future

release we plan to add Prime Biller Parent / Child accounts.

2. ICI Credit Notes & ICI Debit Notes can be issued against Prime Biller Next Gen accounts. Customers that have Prime Biller Next Gen accounts need to be prepared to receive

August 2017

Verizon

811 – Transaction Set

EDI Billing

Version 004010

Implementation Guide

Overview

VB811s for ICI Credit Notes & ICI Debit Notes. Please ensure your communications and translator is setup to for ICI Credit Notes & ICI Debit GS02s.

 Prime Biller Extended Edition (PBEE) (formerly SingleView – Networx)  SSB - Customer Premise Equipment billing.  Vision V5 - Billing for Verizon Online, FiOS TV and FiOS Digital Voice

 WIN – Wholesale Invoicing Network billing system.

Types of Bills Provided: Billing accounts are provided in one of two arrangements (this is controled by the billing system).

 Stand-Alone Account Billing - This billing arrangement produces one bill per account number.  Consolidated Billing Account - This billing arrangement consolidates several single accounts

under one CBA (master) account number and produces one Summary Master bill and supporting component bills. The CBA is the bill invoice and each single account is presented as a memo invoice. Examples are shown in the section “Consolidated 811”. Bill invoice versus memo invoice is further explained in Appendix A of this document under BIG07.

2.3 Formats of Bills Provided

Billing accounts are provided in one of four (4) formats:

2.3.1 Summary-Level Format

Includes the EDI 811 Heading Section, Summary Section, and Detail Section HL 1 (Service Provider) through HL 4 (Group). These levels provide the information needed to pay the bill. For each service provider, total charge amount and a summary of charges by service type are presented. Supporting details for Levels 5 - 9 are not furnished with Summary Format. For summary billing arrangement, this format includes only the master-account and does NOT include the sub-accounts.

2.3.2 High-Level Format

2.3.3 Summarized Detail-Level Format

Includes the EDI 811 Heading Section, Summary Section, and Detail Section HL 1 (Service Provider) through HL 8 (Charge Detail). A summarization of charges is provided when details are not available. For summary billing arrangement, this format includes the master-account and subaccounts.

2.3.3.1 Summarized Detail-Level Format – Call Details

August 2017

Verizon

811 – Transaction Set

EDI Billing

Version 004010

Implementation Guide

Overview

For call details, we create the HL8-level VB811 by sorting and summarizing the TCDs into SLNs at HL8. To do this we use the following SI pairs from the TCDs (and then show these same SI pairs on the SLN we create):

SI Pair used in Detail-Level Format BA Band CE Cellular Air Time Package Code CT Common Segment Hops CZ Cellular Usage Indicator DS Discount Planned Code MC Message or Rate Class MT Message Type P0 Pricing Plan Type Indicator R2 Call Routing Termination Code RJ Rate Zone for Taxing (Switch / Taxing Geo code) RP Rate Period Code RS Rate Schedule RY Local / Toll Indicator SD Settlement Code SF Service Feature -- Advanced Card Feature Codes: SS Service Sub-category Code TE Transmission Speed TT Transmission Type ZC Service Method || Entry Code ZD Call Termination ZE Access Code for Conferencing. ZF Operator Assisted Code

If the call originates or terminates outside the US, we include the origination country in a SI Pair OL in the SLN loop and the termination country in the SI Pair TL in the SLN loop. The origination and/or termination country is used in the sorting and summarizing of the calls at HL8-level.

2.3.3.1 Summarized Detail-Level Format – Conference Call

For conferencing, we create the HL8-level VB811 by sorting and summarizing the conference caller charges by conference call. Note: we only summarize the SV*0500 usage.

2.3.4 Full Detail-Level Format

Includes the EDI 811 Heading Section, Summary Section, and Detail Section HL 1 (Service Provider) through HL 8 (Charge Detail) and/or HL 9 (Line Detail). A summarization of charges is provided when details are not available. For summary billing arrangement, this format includes the master-account and sub-accounts.

2.4 Structure of the 811

The 811 transaction set is divided into three tables that are the basic structure of most EDI transaction set standards. The three tables are:

Table 1, Heading Section provides information about the billing provider and the customer billed, the account billed, the nature and type of bill rendered. The Heading Section also contains billing terms and

August 2017

Verizon

811 – Transaction Set

EDI Billing

Version 004010

Implementation Guide

Overview

conditions and tax information applicable to the entire bill. There are no billing amounts in the Heading Section.

Table 2, Detail Section provides details of charges that appear on the current month's bill. These charges may include; monthly services, additions and changes (OC&C), optional calling plans, volume discount plans, long distance, other usage, taxes, surcharges and special allowances. The detail section is divided into 9 hierarchical levels.

Level 1 - Service Provider level, contains information about the actual company rendering the services. Since Verizon provides billing services for other carriers, it is common for one bill and/or account to have multiple service providers.

Level 2 - Billing Arrangement level, references information on the individual component bills (subaccounts) to the Master.

Level 3 - Sub-billing Arrangement level, is used to provide the location/account (Node ID) information.

Level 4 - Group level, contains summary charges for services billed. Level 5 - Category level, is used to group details together by circuit number, Switch Board number

and/or Centrex number.

Level 6 - Sub-category level, is used to group details together by circuit component number, Customer Reference Number, Vendor Order Number, Service Number and/or BAC.

. Level 7 - Type level, is used to group details together by WTN, earning number, billing number, call

card, conference or other sort breaks.

Level 8 - Charge Detail level, contains supporting details for charges at the Group level.

Level 9 - Line Detail level, contains supporting usage and charge detail for charges at either Level 4 or Level 8.

NOTE: Verizon’ use of the hierarchical levels is explained in the Detail Section, Section 7 of this document.

Table 3, Summary Section, summarizes the amount billed. The summary section contains total current charges, payments, adjustments, previous billed amount and net amount due after payments and adjustments. There are key amounts contained in the summary section that can be used for validation. Section 8 of this document provides the ‘summing rules’.

2.5 Use of the 820

The 820 transaction set, Payment Order/Remittance Advice, is used to provide authorization for payment and detailed information about the payment. As previously mentioned, there are several methods of handling the payment process. Verizon encourages the use of the 820 transaction set and provides

complete remittance information in REF02 where REF01 is ‘AP’. As explained previously in the Business

Model section, Verizon does not receive 820s directly. Verizon uses the Financial EDI model where the 820 goes to the Verizon customer’s bank.

August 2017

Verizon

811 – Transaction Set

EDI Billing

Version 004010

Implementation Guide

Overview

2.6 Information to Have When Contacting Verizon

Traditionally when a customer has questions about their bill, they contact a Verizon representative for assistance. The representative needs the billing date, billing account number, and the nature of the question in order to be of assistance. The required information is provided in the 811 Transaction Set. The following data elements are required for billing inquiry:

Bill Date BIG Segment – BIG01 Invoice Number BIG Segment – BIG02 Billing Account Number REF Segment – REF02 when REF01 = ‘11’ REF Segment – REF02 when REF01 = ‘12’ REF Segment – REF02 when REF01 = ‘14’ Billing System REF Segment – REF02 when REF01 = ‘06’ Corp ID REF Segment – REF02 when REF01 = ‘U1’

2.7 Data Element Separator, Segment Terminator and Component Element Separator

When displaying mapping examples in this guide, the tilde (~) is used as the data element separator, the vertical line (|) is used as the segment terminator and the low line (__) is used as the component element separator. Verizon 811 transaction set production files may use different data element separator and segment terminator values. These values can be negotiated with each trading partner. The “at” symbol (@) cannot be used as an EDI separator because Verizon uses the character in email address fields.

2.8 ASC x12 Extended Character Set

The VB811 uses the ASC x12 Extended Character Set. The ASC x12 standard supports the following Special characters under the Extended Character Set:

ISO Document 8859-1 (Latin-1 Alphabet):

À, Á, Â, Ä, à, á, â, ä È, É, Ê, è, é, ê, ë Ì, Í, Î, ì, í, î, ï Ò, Ó, Ô, Ö, ò, ó, ô, ö Ù, Ú, Û, Ü, ù, ú, û, ü Ç, ç, Ñ, ñ, ¿, i

August 2017

Verizon

811 – Transaction Set

EDI Billing

Version 004010

Implementation Guide

Conventions

Segment ID

Segment Description

ISA

Interchange Control Header

IEA

Interchange Control Trailer

Element ID

Data Element

Element Name / Actual Value(s)

ISA01

I01

Authorization Info Qualifier 00 (No authorization info present)

ISA02

I02

Authorization Info 10 spaces

3. Envelope Control Structure

Each EDI interchange must occur in a predefined sequence in order to ensure the information can be read and understood. The envelope control structure used to transmit a group of EDI transaction sets is comprised of the Interchange Control Header (ISA), Interchange Control Trailer (IEA), Functional Group Header (GS), and Functional Group Trailer (GE) as follows:

ISA Interchange Control Header (starts electronic interchange) GS Functional Group Header (starts group of related transaction sets) ST Transaction Set Header (starts a transaction set)

Telephone Bill Invoices (811) Transaction Set Segments

SE Transaction Set Trailer (ends a transaction set)

GE Functional Group Trailer (ends group of related transaction sets) IEA Interchange Control Trailer (ends electronic interchange)

3.1 Interchange Envelope

The Interchange Envelope identifies the start and the end of an EDI transmission. It also identifies the sender and receiver of the interchange and provides control information. The Interchange Envelope consists of an Interchange Control Header (ISA) and an Interchange Control Trailer (IEA).

Interchange Control Header

The ISA Interchange Control Header is the first segment of an EDI transmission. It is used to start and identify an interchange of one or more functional groups and interchange-related control segments. The information provided by Verizon in the ISA segment follows.

ISA Example: ISA~~00~~00~~01~107212169ESG~01~1234567890123~990401~2331~U~00401~000000018~0

~P~_||

August 2017

Verizon

811 – Transaction Set

EDI Billing

Version 004010

Implementation Guide

Conventions

ISA03

I03

Security Info Qualifier 00 (No security info present)

ISA04

I04

Security Information 10 spaces

ISA05

I05

Interchange ID Qualifier 01 (DUNS)

ISA06

I06

Interchange Sender ID 107212169ESG (Verizon expressTRAK or NBBE)

ISA07

I05

Interchange ID Qualifier 01 (DUNS)

ISA08

I07

Interchange Receiver ID

ISA09

I08

Interchange Submit Date (YYMMDD)

ISA10

I09

Interchange Submit Time (HHMM)

ISA11

I10

Interchange Control Stds ID U (U.S. EDI Community of X12)

ISA12

I11

Interchange Ctrl Version No 00401 (ANSI Version 4, Release 1)

ISA13

I12

Interchange Control Number

ISA14

I13

Acknowledgment Requested 0 (No Acknowledgment Requested)

ISA15

I14

Test/Production Indicator T (Test Data ) or P (Production Data)

ISA16

I15

Sub Element Separator _

Element ID

Data Element

Element Name

IEA01

I16

Number of Included Functional Groups

IEA02

I12

Interchange Control Number (as in ISA13)

Interchange Control Trailer:

The IEA Interchange Control Trailer is the last segment of an EDI transmission. It is used to end and identify an interchange of one or more functional groups and interchange-related control segments. The information provided by Verizon in the IEA segment follows.

IEA Example: IEA~1~000000018|

August 2017

Verizon

811 – Transaction Set

EDI Billing

Version 004010

Implementation Guide

Conventions

Segment ID

Segment Description

Functional Group Header

Functional Group Trailer

Element ID

Data Element

Element Name / Actual Value(s)

GS01

479

Functional Identifier Code CI (Consolidated Invoice)

GS02

I42

Application Sender’s Code ETRAK-V1 (Verizon expressTRAK or NBBE)

GS03

I24

Application Receiver’s Code (same as in ISA08)

GS04

029

Functional Group Date (CCYYMMDD)

GS05

030

Functional Group Time (HHMM)

GS06

028

Functional Group Control Number

GS07

455

Responsible Agency Code X = Accredited Standards Committee X12

GS08

480

Version/Release = 004010

Element ID

Data Element

Element Name / Actual Value(s)

GE01

097

Total Number of Transaction Sets

GE02

028

Functional Group Control Number (as in GS06)

3.2 Functional Group Envelope

All 811 transaction sets provided will be enveloped within a functional group. The purpose of the functional group is to indicate the beginning of a functional group and to provide control information. The functional group consists of a Functional Group Header (GS Segment) and a Functional Group Trailer (GE Segment).

Functional Group Header:

The Functional Group Header is the first segment of an 811 transaction set. It is used to indicate the start and identification of one or more 811 transaction sets. The information provided by Verizon in the

GS segment follows.

GS Example: GS~CI~ETRAK-V1~123456789012~19990401~2331~152~X~004010|

Functional Group Trailer:

The Functional Group Header is the last segment of an 811 transaction set. It is used to indicate the end and identification of one or more 811 transaction sets. The information provided by Verizon in the

GE segment follows. GE Example: GS~2~152|

August 2017

Verizon

811 – Transaction Set

EDI Billing

Version 004010

Implementation Guide

Conventions

Element ID

Data Element

Element Name / Actual Value(s)

ST01

143

Transaction Set ID Code 811 = Consolidated Service Invoice/Statement

ST02

329

Transaction Set Control Number (The value in ST02 must match the value in SE02 of the transaction set trailer.)

Element ID

Data Element

Element Name / Actual Value(s)

SE01

096

Number of included segments

SE02

329

Transaction Set Control Number (The value in SE02 must match the value in ST02 of the transaction set header.)

3.3 Transaction Set Envelope

Transaction Set Header:

The Transaction Set Header is used to indicate the start of and identify a transaction set and assigns a control number. The information provided in the ST segment follows.

ST Example: ST~811~0204|

Transaction Set Trailer:

The Transaction Set Trailer is used to indicate the end of a transaction set, to provide the count of the transmitted segments which include the beginning (ST) and ending (SE) segments and to provide the Assigned control number. The information provided in the SE segment follows.

SE Example: SE~45~0204|

August 2017

Verizon

811 – Transaction Set

EDI Billing

Version 004010

Implementation Guide

Understanding Hierarchical Levels (HL)

4. Understanding Hierarchical Levels (HL)

The hierarchical levels used by Verizon and other members of the telecommunications industry reflect the needs of the service providers in responding to the billing requests of their trading partners.

The hierarchical levels are dependent on billing data. For further information reference Ordering and Billing Forum (OBF) EDI Telecommunications Billing (ETB) (formerly TCIF) EDI Guidelines - Telecommunications Billing Issue 9, Revision 4.

The hierarchical structure contains a parent/child relationship, which establishes the levels of billing data. For example, the bill data is organized by Service/Billing Provider (HL 1), within service provider by Group charge (HL 4) and within each Group by Charge Detail (HL 8). In this example, the Service/Billing Provider is the parent to each Group and each Group is a parent to each of its Charge Detail items. Information provided at a parent level applies to all children associated with that parent.

The following provides a description of the nine hierarchical levels used in the 811 transaction set. In the following descriptions the HL numeric value represents the Hierarchical Level Code (HL03) of the HL segment.

Hierarchical Level 1 (HL 1) - Service/Billing Provider

At least one occurrence of HL 1 is required for each 811. Within the HL 1 one occurrence of the NM1 loop is required. The NM1 is used to designate the company providing the billing and/or services. The ITA loop, when used at this level, depicts speci al charges, surcharges, credits and allowances that apply to this Service/Billing provider.

Hierarchical Level 2 (HL 2) - Billing Arrangement (used by Summary Master-Accounts) Hierarchical Level 3 (HL 3) - Sub-Billing Arrangement (used for Location Account (NODE ID))

HL 2 and HL 3 are optional and allow for the flexible segregation of charges under billing arrangements. This segregation is achieved through the use of the LX loop by using LX/SI segments. If needed the QTY/SI segments may also be used. The ITA loop, when used at this level, depicts special charges, surcharges, allowances and credits which apply to this Billing Arrangement/Sub-Billing Arrangement Level.

Hierarchical Level 4 (HL 4) - Group

At least one occurrence of HL 4 is required for each Service/Billing Provider (HL 1). At HL 4 only the IT1 loop is valid. It is used to display the Group charges for the services billed. When this hierarchical level has no children (HL04 value of '0') multiple IT1 loops may appear within the HL 4 structure. When there are children (HL04 value of '1') only one IT1 loop can be presented within the hierarchical level.

Hierarchical Level 5 (HL 5) - Category (Circuit, Switchboard and/or CENTREX) Hierarchical Level 6 (HL 6) - Sub-Category (circuit component number, Customer Reference

Number, Vendor Order Number, Service Number and/or BAC.) Hierarchical Level 7 (HL 7) – Type (Earning Number, WTN, Conference ID, BTN, call card,

conference or other sort breaks)

HL 5, 6, and 7 are optional. They are similar to HL 2 and HL 3 in that they provide further flexibility in segregating charges. If HL 6 and/or HL 7 are present, there may or may not be an associated HL 5 or HL 6. The LX, NM1 and ITA loops can be used to provide a breakdown of charges displayed at HL 4.

August 2017

Verizon

811 – Transaction Set

EDI Billing

Version 004010

Implementation Guide

Understanding Hierarchical Levels (HL)

Hierarchical Level 8 (HL 8) - Charge Detail

HL 8 is optional. When used, it will provide a breakdown of HL 4 charges. The SLN loop, which can be used only at HL 8, provides the sub line item detail. When HL 8 has no children (HL04 value of '0') multiple SLN loops may appear within this hierarchical level. When there are children (HL04 value of '1') only one SLN loop can be presented within the hierarchical level.

Hierarchical Level 9 (HL 9) - Line Detail

HL 9 is optional. The TCD and USD loops, which can be used only at HL 9, will provide usage details associated with toll calls, optional call plans, etc.

Section 7.2.5 of the OBF/ETB /EDI Guideline for the 811 has a diagram of the possible relationships of the Hierarchical levels within the 811 Transaction Set. Each of the services describe later in this documentation illustrates the structure and dependencies of the hierarchical levels of the telephone billing information provided in the Detail Section of the 811 transaction set.

In order to understand the 811 transaction set, it is necessary to understand the use of the hierarchical level segments as they reflect the 811 structure. The hierarchical levels provide a parent/child relationship that organizes the invoice into billing levels (parent) that have sub-levels (child) providing detailed information about the billing level.

The parent/child relationship is established between levels of billing data using data elements in the HL segment and are represented as:

HL~ ID Number~ Parent ID Number~ Level Code~ Child Code|

 HL01 (ID Number) is a unique number assigned by the provider to identify a particular data

segment within the hierarchical structure.

 HL02 (Parent ID Number) is the HL01 value of the parent HL loop.  HL03 (Level Code) identifies the hierarchical level of 1 - 9.  HL04 (Child Code) indicates if there are additional child (supporting detail) HL segments

associated with the hierarchical level. HL04 is a requirement. The value of ‘1’ indicates that the

hierarchical level has children/supporting detail. The value of ‘0’ indicates that the hierarchical level has no children/supporting detail.

o For example, if billing is organized by service provider and the service provider detail is

organized by charge type at the group level, the service provider is the Parent HL. The charge type at the group level becomes the Child HL to the service provider level Parent HL.

 Examples illustrating use of the HL segment in the 811:

o HL~1~0~1~1| This is the initial HL segment. HL02 is not provided at this level because

the information does not have a parent HL loop. HL03 signifies HL 1, Service Provider level. HL04 value of ‘1’ indicates that there is supporting detail.

o HL~2~1~4~0| HL02 indicates that this information supports and is related to HL number 1.

HL03 signifies HL 4, Group Level. HL04 value of ‘0’ indicates that there is no supporting

detail.

August 2017

Verizon

811 – Transaction Set

EDI Billing

Version 004010

Implementation Guide

Understanding Hierarchical Levels (HL)

Additional examples and further information regarding the use of the HL segment in the 811 can be found in the ASC X12 Version 4 Release 1 standards and the (OBF/ETB) (formerly TCIF) EDI

Guidelines - Telecommunications Billing Issue 9, Revision 4. Use both the ASC X12 and the OBF/ETB as a reference for general questions about the 811 Transaction Set.

August 2017

Verizon

811 – Transaction Set

EDI Billing

Version 004010

Implementation Guide

Heading Section

HL9

HL8

HL9

HL8

HL9

HL8

HL9

HL8

HL9

HL8

HL9

HL8

HL9

HL8

HL9

HL8

HL9

Header Section

Account Invoice

Bill Payer Invoice

HL7

Earning Number / WTN / BTN

HL7

Earning Number / WTN / BTN

HL7

Earning Number / WTN / BTN

HL7

Earning Number / WTN / BTN Conf erence ID / Calling Card

HL8

HL9

HL6

Circuit Component #

BAC, SO, VN, CR

HL6

Circuit Component #

BAC, SO, VN CR

HL4

SV*2050

HL4

Service Rendered

HL4

Service Rendered

HL2

Sub-Accounts

HL3

Location/Account (NODE)

HL1

Service Provider

HL5

Circuit # Switch Board #, Centrex #

HL9

HL3

Location/Account (NODE)

HL4

SV*2050

5. Verizon’s Use of the EDI 811 Hierarchical Levels (HL)

August 2017

Verizon

811 – Transaction Set

EDI Billing

Version 004010

Implementation Guide

Detail Section

SV*0200: Monthly Service Charge

Segment ID

Position

Segment Description

Loop

Max Use

O/M

010

Transaction Set Header

N/A

BIG

020

Beginning Segment for Invoice

N/A

NTE

030

Note

N/A

100

CUR

040

Currency

N/A

REF

050

Reference Numbers

N/A

ITD

070

Terms of Sale/Deferred Terms

N/A

DTM

080

Date/Time, From/Thru Dates

N/A

TXI

090

Tax Information

N/A

100

Name Payor/Payee

110

Additional Name Information

120

Address Payor/Payee

130

Geographic Location

REF

140

Reference Numbers

PER

150

Administrative Communications Contact

6. Heading Section of the EDI 811

The purpose of the Heading Section of the 811 is to provide information about the bill rendered, the recipient of the bill (Verizon trading partner) and the provider of the bill (Verizon).

The format for this section provides a table of segments depicting the structure of the portion of the 811 being explained. After the structure table, a sample mapping for the respective area of the 811 is displayed. The example does not include all the Segments and Codes that could be used in any 811 Transaction Set. Please refer to Appendix A for a full list of Segments and Codes that can be used. The sample mapping reflects telephone billing data for a single expressTRAK account.

A comprehensive list of segments, data elements, and element values used by Verizon is provided in Appendix A of this guide.

Structure of the Heading Section:

SAMPLE MAPPING OF THE HEADING SECTION:

August 2017

Verizon

811 – Transaction Set

EDI Billing

Version 004010

Implementation Guide

Detail Section

SV*0200: Monthly Service Charge

Element ID

Data Element

Element Names / Values

ST01

143

Transaction Set ID Code = 811

ST02

329

Transaction Set Control Number

Element ID

Data Element

Element Names / Values

BIG01

373

Invoice Date = Bill Date = CCYYMMDD

BIG02

076

Invoice Number = Billing Account Number and Invoice Date

BIG07

640

Transaction Type Code DI = Debit Invoice

Element ID

Data Element

Element Names / Values

NTE01

363

Note Reference Code GEN = Entire transaction set

NTE02

352

Description A late payment charge of 1.5 applies to any portion of the bill not paid before the next month's bill.

ST (Transaction Set Header) Sample: ST~811~000000001|

BIG (Beginning Segment for Invoice) Sample: BIG~20061006~00001604911720061006~~~~~DI|

NTE (Note/Special Instruction) Sample:

NTE~GEN~A LATE PAYMENT CHARGE OF 1.5 APPLIES TO ANY| NTE~GEN~PORTION OF THE BILL NOT PAID BEFORE THE NEXT MONTH'S BILL.|

August 2017

Verizon

811 – Transaction Set

EDI Billing

Version 004010

Implementation Guide

Detail Section

SV*0200: Monthly Service Charge

Element ID

Data Element

Element Names / Values

REF01

128

Reference Identification Qualifier ZZ = Verizon Electronic Billing ID (EBID) RE= Verizon Internal Release Number

11 = Old Account Number Legacy System 12 = Billing Account Number U1 = Regional Account Number

- Customer Number (Corp ID)

AP = Accounts Receivable Number 06 = System Number

REF02

127

Reference Number EBID = Verizon Internal Electronic Billing ID Verizon Release Number = Verizon Internal Release #3042733576267 = Old Account Number Legacy 000016049117 = Billing Account Number

01234567 = Customer Number (Corp ID)

00001604911743 = Accounts Receivable Number 04 = expressTRAK

Element ID

Data Element

Element Names / Values

ITD01

336

Terms Type Code 03 = Fixed Date

ITD02

333

Terms Basis Date Code 3 = Invoice Date

ITD06

446

Payment Due Date = CCYYMMDD

Element ID

Data Element

Element Names / Values

DTM01

374

Date / Time Qualifier

186 = Invoice Period Start 187 = Invoice Period End

DTM02

373

Date = CCYYMMDD

REF (Reference Numbers) Sample: REF~ZZ~EBID| REF~11~3042733576267| REF~12~000016049117~3042733576267|

REF~U1~01234567|

REF~AP~00001604911743|

REF~RE~Verizon Release number|

REF~06~04|

ITD (Terms of Sale/Due Date) Sample: ITD~03~3~~~~20061105|

DTM (Service From and Thru Dates) Sample: DTM~186~20061006|

DTM~187~20061105|

August 2017

Verizon

811 – Transaction Set

EDI Billing

Version 004010

Implementation Guide

Detail Section

SV*0200: Monthly Service Charge

Element ID

Data Element

Element Names / Values

TXI01

963

Tax Type Code ST = State Sales Tax

TXI06

441

Tax Exempt Code 1 = Yes Tax Exempt

Element ID

Data Element

Element Names / Values

N101

098

Entity Identifier Code = PR = Payor

N102

093

Name

N301

166

Address Information

N302

166

Address Information, line 2

N401

019

City Name

N402

156

State

N403

116

Postal Code = Zip + 4

Element ID

Data Element

Element Names / Values

N101

098

Entity Identifier Code = PE = Payee

N102

093

Name

N301

166

Address Information

N401

019

City Name

N402

156

State

N403

116

Postal Code = Zip + 4

Element ID

Data Element

Element Names / Values

REF01

128

Reference Number Qualifier IS = Invoice Number Suffix

REF02

127

Reference Number 025 = Revenue Accounting Office (RAO)

TXI (Tax Information) Sample: TXI~ST~~~~~~1|

Note: The TXI Element in the Heading Section is only used to convey account tax exempt status.

N1 (Payor Name) Sample: N1~PR~CUSTOMER NAME| N3 (Payor Address): N3~CUSTOMER ADDRESS1~CUSTOMER ADDRESS2| N4 (Payor City, State, Zip+4): N4~CITY~STATE~222221234|

N1 (Payee Name and Duns Number Sample): N1~PE~VERIZON| N3 (Payee Address): N3~PO BOX 28007| N4 (Payee City, State, Zip+4): N4~ LEHIGH VALLEY~PA~ 180028007|

REF (Reference Numbers) Sample: REF~IS~025|

August 2017

Verizon

811 – Transaction Set

EDI Billing

Version 004010

Implementation Guide

Detail Section

SV*0200: Monthly Service Charge

Segment ID

Position

Segment Description

Loop

Max Use

O/M

010

Hierarchical Level

HL1

020

Sequentially Assigned Number

PID

040

Product/Item Description

AMT

060

Monetary Amount

NM1

110

Service Provider Name

NM1

120

Additional Name Information

NM1

130

Address Information

NM1

140

Geographical Information

NM1

REF

150

Reference Identifier

NM1

PER

160

Contact Telephone Numbers

NM1

TXI

170

Tax Information

NM1

ITA

180

Allowance, Charge or Service

ITA

DTM

190

Date/Time Reference

ITA

TXI

200

Tax Information

ITA

7. Detail Section of the EDI 811

The purpose of the Detail Section of the 811 is to provide information about services and charges that are being billed. The activity included in the 811 is generally dated from the previous invoice period, as specified in the DTM segments of the heading. Examples of activity that may be included in the detail section are Monthly Service, Additions and Changes (OC&C), Optional Calling Plans, Discount Plans, Itemized Calls, Taxes, Surcharges, and Late Payment Charges.

At least one Service Provider Level (HL1) is required for each 811 and at least one Group Level (HL4) for each HL1. The Service Provider Level (HL1) groups the billing information by service provider and by the associated charges, which are presented by type of charge in HL4. Consolidated accounts have a Billing Arrangement Level (HL2) and a Group Level (HL4) to present charges by component account.

The format for this section provides a table of segments depicting the structure of the portion of the 811 being explained. After the structure table a sample mapping for the respective area of the 811 is displayed.

A comprehensive list of segments, data elements, and element values used by Verizon is provided in Appendix A of this guide.

7.1 High-Level (HL1 through HL4) Examples:

Hierarchical Levels 1 through 4 are only included in the “Summary-Level format”, “High-Level Format” and “DetailLevel format”. The high levels contain information up to summarized service type charges (HL4).

7.1.1 HL1 – Service Provider

The Service Provider Level (HL1) gives information about the company rendering billing and/or services. There may be several Service Providers in one bill since Verizon provides billing services for multiple carriers.

August 2017

Verizon

811 – Transaction Set

EDI Billing

Version 004010

Implementation Guide

Detail Section

SV*0200: Monthly Service Charge

Element ID

Data Element

Element Names / Values

HL01

628

Hierarchical ID Number

HL03

735

Hierarchical Level Code 1 = Billing/Service Provider

HL04

736

Hierarchical Child Code 1 = Subordinate Segments

Element ID

Data Element

Element Names / Values

LX01

554

Sequentially Assigned Number

Element ID

Data Element

Element Names / Values

AMT01

522

Amount Qualifier Code SC = Total Service Charge

AMT02

782

Monetary Amount

283.12 = Dollars/Cents

SAMPLE MAPPING:

HL~1~0~1~1| LX~1| AMT~SC~283.12| NM1~SJ~2~Verizon~~~~~42~0698| PER~BI~~TE~18002225555| PER~OC~~TE~18002226666| TXI~FD~16.6~~~~~~A| ITA~C~TI~~06~~~752~~~~~~~SUR~~A| ITA~C~TI~~06~~~350~~~~~~~LPC~~A| ITA~N~TI~~15~121287-00~~99999996~~~~~~TOTAL AMONT COMMITED TO ON CONTRACT~ZZZ~~O| DTM~276~20040115~~~RD8~20040115-20080115| ITA~N~TI~~15~121287-00~~16673046~~~~~~TOTAL AMOUNT CONTRIBUTED TO THE COMMITMENT FOR THE LIFE OF THE CONTRACT~ZZZ~~O| DTM~276~20040115~~~RD8~20040115-20080115| ITA~N~TI~~15~121287-00~~7188345~~~~~~AMOUNT CONTRIBUTED IN: 200602 BY: X35~ZZZ~~O| ITA~N~TI~~15~121287-00~~9484701~~~~~~AMOUNT CONTRIBUTED IN: 200604 BY: X35~ZZZ~~O|

HL (Hierarchical Level) Sample: HL~1~0~1~1|

LX (Assigned Number) Sample: LX~1|

AMT (Monetary Amount) Sample: AMT~SC~283.12|

August 2017

Verizon

811 – Transaction Set

EDI Billing

Version 004010

Implementation Guide

Detail Section

SV*0200: Monthly Service Charge

Element ID

Data Element

Element Names / Values

NM101

098

Entity Identifier Code SJ = Billing/Service Provider

NM102

1065

Entity Type Qualifier

NM103

1035

Service Provider Name

NM108

066

Identification Code Qualifier

41 = Carrier CIC Code 42 = Pseudo Carrier ID Code

NM109

067

Identification Code = Bellcore CIC Code 0698 = Verizon Pseudo CIC Code

Element ID

Data Element

Element Names / Values

PER01

366

Contact Function Code

BI = Bill Inquiry Contact OC = Order Contact

PER03

365

Communication Number Qualifier TE = Telephone

PER04

364

Communication Number 1 NPA NNX NNNN

Element ID

Data Element

Element Names / Values

TXI01

963

Tax Type Code FD = Federal Tax

TXI02

782

Monetary Amount

16.60 = Dollars/Cents

TX107

662

Relationship Code A = Add (for summing and auditing)

Element ID

Data Element

Element Names / Values

ITA01

248

Allowance or Charge Indicator C = Charge

ITA02

559

Agency Qualifier Code TI = Telecommunications Industry

ITA04

331

Method of Handling 06 = Charge paid by Customer

ITA07

360

Allowance/Charge Total Amount

7.52 = Dollars/Cents

NM1 (Service Provider Name) Sample: NM1~SJ~2~Verizon~~~~~42~0698|

PER (Contact Telephone Numbers) Sample: PER~BI~~TE~18002225555|

PER~OC~~TE~18002226666|

TXI (Tax Information) Sample: TXI~FD~16.6~~~~~~A|

ITA (Allowance, Charge or Service) Sample: ITA~C~TI~~06~~~752~~~~~~~SUR~~A|

August 2017

+ 190 hidden pages