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
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
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
3
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
4
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
5
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
6
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 begenerated and sent to the trading
partner’s bank.
Thetrading 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
7
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:
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
oService Type is presented in the NM1 loop at HL3.
GCS F&E (Cycle 8) - International Frame Relay
oService Type is presented in the NM1 loop at HL3.
GCS GIS (Cycle 9) - Global Inbound Service - US
oCalls Details are not currently available on the VB811: IT1 SV~0500
will not contain details
GIS EMEA (Cycle 10) - Global Inbound Service - Europe
oCalls Details are not currently available on the VB811: IT1 SV~0500
will not contain details
GIS ASIA PAC (Cycle 11) - Global Inbound Service - Asia
oCalls Details are not currently available on the VB811: IT1 SV~0500
will not contain details
ASIA PAC VOIP (Cycle 15 & 16) - Direct Voice - Asia
oCalls 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
8
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
9
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
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
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 the master-account and sub-accounts.
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
10
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
11
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
12
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:
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) STTransaction 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) IEAInterchange 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
14
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
15
Segment ID
Segment Description
GS
Functional Group Header
GE
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 CodeETRAK-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
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
16
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)
17
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.
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.
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.
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)
18
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:
oHL~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.
oHL~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)
19
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
20
HL9
HL8
HL9
HL9
HL8
HL9
HL9
HL8
HL9
HL8
HL9
HL8
HL8
HL9
HL9
HL8
HL9
HL9
HL8
HL9
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
HL8
HL8
HL8
HL8
HL8
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
21
Segment
ID
Position
Segment Description
Loop
Max
Use
O/M
ST
010
Transaction Set Header
N/A
1
M
BIG
020
Beginning Segment for Invoice
N/A
1
M
NTE
030
Note
N/A
100
O
CUR
040
Currency
N/A
1
O
REF
050
Reference Numbers
N/A
>1
M
ITD
070
Terms of Sale/Deferred Terms
N/A
1
M
DTM
080
Date/Time, From/Thru Dates
N/A
>1
O
TXI
090
Tax Information
N/A
>1
O
N1
100
Name Payor/Payee
N1
2
M
N2
110
Additional Name Information
N1
2
O
N3
120
Address Payor/Payee
N1
2
O
N4
130
Geographic Location
N1
1
O
REF
140
Reference Numbers
N1
1
O
PER
150
Administrative Communications
Contact
N1
3
O
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:
ST~811~0001|
BIG~20061006~00001604911720061006~~~~~DI|
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.|
REF~ZZ~EBID|
REF~11~3042733576267|
REF~12~000016049117~3042733576267|
REF~U1~01234567|
REF~AP~00001604911743|
REF~RE~VERIZON RELEASE NUMBER|
REF~06~04|
August 2017
Verizon
811 – Transaction Set
EDI Billing
Version 004010
Implementation Guide
Detail Section
SV*0200: Monthly Service Charge
22
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
23
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
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
25
Segment
ID
Position
Segment Description
Loop
Max
Use
O/M
HL
010
Hierarchical Level
HL1
1
M
LX
020
Sequentially Assigned Number
LX
1
O
PID
040
Product/Item Description
LX
30
O
AMT
060
Monetary Amount
LX
>1
O
NM1
110
Service Provider Name
NM1
1
O
N2
120
Additional Name Information
NM1
2
O
N3
130
Address Information
NM1
2
O
N4
140
Geographical Information
NM1
1
O
REF
150
Reference Identifier
NM1
2
O
PER
160
Contact Telephone Numbers
NM1
>1
O
TXI
170
Tax Information
NM1
>1
O
ITA
180
Allowance, Charge or Service
ITA
>1
O
DTM
190
Date/Time Reference
ITA
1
O
TXI
200
Tax Information
ITA
>1
O
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.
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|
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
Verizon
811 – Transaction Set
EDI Billing
Version 004010
Implementation Guide
Detail Section
SV*0200: Monthly Service Charge
28
ITA14
150
Special Allowance/Charge Code
SUR = Surcharge $
ITA16
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
3.50 = Dollars/Cents
ITA14
150
Special Allowance/Charge Code
LPC = Late Payment Charge #
ITA16
662
Relationship Code
A = Add (for summing and auditing)
Element ID
Data Element
Element Names / Values
ITA01
248
Allowance or Charge Indicator
N = No Charge or Allow ance
ITA02
559
Agency Qualifier Code
TI = Telecommunications Industry
ITA04
331
Method of Handling
15 = Information Only
ITA05
341
Contract ID
121287-00
ITA07
360
Amount
999,999.96= Dollars/Cents
ITA13
352
Specific charge description
TOTAL AMOUNT COMMITTED TO ON CONTRACT
TOTAL AMOUNT CONTRIBUTED TO THE
COMMITMENT FOR THE LIFE OF THE
CONTRACT
AMOUNT CONTRIBUTED IN: 200602 BY: X35
$ Refer to Additional Code Lists Used by OBF/ETB (Section 10.4) for values.
ITA (Allowance, Charge or Service) Sample: ITA~C~TI~~06~~~350~~~~~~~LPC~~A|
# Exception: Due to Legacy Verizon South system constraints, Late Payment Charges will continue
to appear in Additions & Changes (OC&C) until conversion to expressTRAK.
ITA (Allowance, Charge or Service) Sample:
ITA~N~TI~~15~121287-00~~99999996~~~~~~TOTAL AMONT COMMITED TO ON CONTRACT~ZZZ~~O|
ITA~N~TI~~15~121287-00~~16673046~~~~~~TOTAL AMOUNT CONTRIBUTED TO THE COMMITMENT FOR
THE LIFE OF THE CONTRACT~ZZZ~~O|
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|
August 2017
Verizon
811 – Transaction Set
EDI Billing
Version 004010
Implementation Guide
Detail Section
SV*0200: Monthly Service Charge
29
AMOUNT CONTRIBUTED IN: 200604 BY: X35
ITA14
150
Special Allowance/Charge Code
ZZZ = Mutually Defined – Contract Info
7.1.2 HL2 – Sub-Account Charges on the Master Account’s Bill
The Billing Arrangement level is used with Consolidated Billing also referred to as Summary Billing in Verizon.
Consolidated Billing/Summary Billing is an arrangement where multiple single bills or components, referred to as
sub-accounts or Invoice Points, are combined into one master bill. Billing Arrangement provides a list of
component accounts (sub-accounts or Invoice Points) and their associated total amount billed. Each component
bill has a billing account number where charges are accumulated. The component current amount due is shown
in the summary section of the component and is included in the consolidated bill total. The components are
separate ‘memo’ 811 transaction sets and the term ‘memo’ indicates that the purpose of the transaction set is to
provide additional detail for an invoice as opposed to an actual invoice.
On a consolidated bill, each component is represented by Billing Arrangement Level segment for the account
number and Group Level segment for the amount due. These segments are subordinate to the Verizon Service
Provider Level.
IT1 (Baseline Item Data (Invoice)) Sample: IT1~~1~M4~30.36~~SV~2050~ZZ~4|
August 2017
Verizon
811 – Transaction Set
EDI Billing
Version 004010
Implementation Guide
Detail Section
SV*0200: Monthly Service Charge
31
IT104
212
Unit Price #
30.36 = Dollars/Cents
IT106
235
Product/Service ID Qualifier
SV = Service Rendered
IT107
234
Product/Service ID
2050 = Total Amount Billed, consolidated
component ( sub-account)
IT108
235
Product/Service ID Qualifier
ZZ = Telecom Service Type
IT109
234
Product/Service I
4 = Summary/Combined Charges
Segment
ID
Position
Segment Description
Loop
Max
Use
O/M
HL
010
Hierarchical Level
HL3
1
M
LX
020
Sequentially Assigned Number
LX
1
O
REF
050
Reference Numbers
LX
>1
O
AMT
060
Monetary Amount
LX
5
O
TXI
080
Tax Information
LX
>1
O
QTY
090
Quantity
LX/QTY
1
O
NM1
110
Service Provider Name
NM1
1
O
N2
120
Additional Name Information
NM1
2
O
N3
130
Address Information
NM1
2
O
N4
140
Geographical Information
NM1
1
O
REF
150
Reference Identifier
NM1
2
O
TXI
170
Tax Information
NM1
>1
O
ITA
180
Allowance, Charge or Service
ITA
>1
O
DTM
190
Date / Time Reference
ITA
1
O
TXI
200
Tax Information
ITA
>1
O
# Included in Total Amount Billed.
7.1.3 HL3 – Location / Account
The Sub-Billing Arrangement level is used to provide Location / Account (NODE ID) information. The Location
Account is identified by an NM1~A0 segment. HL3 can contain the following information about the Location /
Account, such as: PO number, bill amount, charges, taxes, service period, charges, quantity….
A Group Level (HL4) indicates each type of charge and contains information that identifies the content of the
detail that follows. When detail is provided by the billing system the information is available in EDI. When
“Summary-Level format” or “High-Level format” is chosen details are excluded and charges appear at the Group
Level with the Hierarchical Child Code set to zero (‘0’) to indicate no supporting detail.
The IT104 element contains the total charge amount for the charge type. When details (HL 5 – 9) are present,
the sum of each applicable detail amount equals the IT104 amount (see Summing Rules, Section 8.2). This
allows the user to balance the detail amounts to the total charge amount. The sum of all IT104 charge amounts,
plus certain taxes and surcharges, equals The Total Current Charges (TDS01). See Summary Section, Section
7, for specific details.
SAMPLE MAPPING: HL~3~1~4~1|
IT1~~1~M4~30.50~~SV~0200~ZZ~1|
PID~F~~~~Description of IT107|
ITA~C~TI~~06~~~161~~~~~~~SUR~I|
August 2017
Verizon
811 – Transaction Set
EDI Billing
Version 004010
Implementation Guide
Detail Section
SV*0200: Monthly Service Charge
36
Element ID
Data Element
Element Names / Values
HL01
628
Hierarchical ID Number
HL02
734
Hierarchical Parent ID Number
HL03
735
Hierarchical Level Code
4 = Group
HL04
736
Hierarchical Child Code
1 = Subordinate Segments
Element ID
Data Element
Element Names / Values
IT102
358
Quantity Invoiced
1 = Unit Price is Total Charge
IT103
355
Unit of Measurement Code
M4 = Monetary Value
IT104
212
Unit Price #
30.50 = Dollars/Cents
IT106
235
Product / Service ID Qualifier
SV = Service Rendered
IT107
234
Product / Service ID
0200 = Monthly Service Charge
IT108
235
Product / Service ID Qualifier
ZZ = Telecom Service Type
IT109
234
Product / Service ID
1 = Recurring Charge
Element ID
Data Element
Element Names / Values
PID01
349
Item Description Type
F Free-form
PID05
352
Description of IT107
Element ID
Data Element
Element Names / Values
ITA01
248
Allowance or Charge Indicator
C = Charge
ITA02
559
Agency Qualifier Code
TI = Telecommunications Industry
# Included in Total Amount Billed.
PID (Product/Item Description) Sample: PID~F~~~~Description of IT107|
ITA (Allowance, Charge or Service) Sample: ITA~C~TI~~06~~~161~~~~~~~SUR~I|
August 2017
Verizon
811 – Transaction Set
EDI Billing
Version 004010
Implementation Guide
Detail Section
SV*0200: Monthly Service Charge
37
ITA07
360
Allowance/Charge Total Amount
161.00 = Dollars/Cents
ITA14
150
Special Allowance/Charge Code
SUR = Surcharge $
ITA16
662
Relationship Code
I = Included (for summing and auditing)
Segment
ID
Segment
Position
Segment Description
Loop
Max
Use
O/M
HL
010
Hierarchical Level
HL5
1
M
LX
020
Sequentially Assigned Number
LX
1
M
SI
030
Service Characteristic
LX
1
M
PID
040
Product/Item Description
LX
200
O
REF
050
Reference Numbers
LX
>1
O
DTM
070
Date / Time Reference
LX
8
O
QTY
090
Quantity
LX/QTY
1
O
$Refer to Additional Code Lists Used by OBF/ETB (Section 10.4) for values.
7.2 Detail-Level (HL5 through HL9) Examples:
Hierarchical Levels 5 - 9 are only included in the “Detail-Level format”. The detail levels contain supporting
information for each service type and are not included if “Summary-Level format” or “High Level format” are
chosen. Because of the diversity in supporting details associated with services billed by Verizon, this portion of the
Detail Section presents only an overview of the detail levels, HL 5 - 9.
The remaining portions of this section provide examples of the use and structure of HL 5 – 9 with information and
presentation of specific service types.
Hierarchical Level 5 Category, Level 6 Sub-category and Level 7 Type are used to group related details together.
For example, Itemized Calls are grouped by telephone line number presented once by a Level 7 Type that applies
to all subordinate Level 9 line details. When the telephone line number changes, a new Level 7 is created along
with the Level 9 line details. This process is repeated for all itemized calls. Levels 5 - 7 are used under different
conditions for the various service types and their uses are explained in the following sections addressing service
types.
Hierarchical Level 8 Charge Detail and Level 9 Line Detail are used to present detail items and supporting usage
detail for the various service types. Level 8 provides a breakdown of group level charges for product codes
(USOC, ISOC or POE) and Level 9 provides supporting usage details for group and charge level information
(itemized calls and local calls). The uses for Levels 8 and 9 are explained in the following sections addressing
service types.
7.2.1 HL5 – Circuit, Switch Board and/or Centrex
HL5, category level, is used to group details together by circuit number, Switch Board number and/or Centrex
number.
Structure of HL5 Circuit, Switch Board and/or Centrex:
August 2017
Verizon
811 – Transaction Set
EDI Billing
Version 004010
Implementation Guide
Detail Section
SV*0200: Monthly Service Charge
38
NM1
110
Individual or Organization Name
NM1
1
O
N3
120
Address Information
NM1
>1
O
N4
130
Geographic Information
NM1
1
O
Element ID
Data Element
Element Names / Values
HL01
628
Hierarchical ID Number
HL02
734
Hierarchical Parent ID Number
HL03
735
Hierarchical Level Code
5 Category
HL04
736
Hierarchical Child Code
1 Subordinate HL present
Element ID
Data Element
Element Names / Values
LX01
554
Assigned Sequential Number
Element ID
Data Element
Element Names / Values
SI01
559
Agency Qualifier Code
SI02
1000
Service Characteristics Qualifier
CN Circuit Number ID
SI03
234
Circuit Number – primary
SI04
1000
Service Characteristics Qualifier
NP NPA code
SAMPLE MAPPING of HL5 Circuit, Switch Board and/or Centrex:
HL~11~3~5~1|
LX~1|
SI~TI~CN~Z123X4501~NP~213~CO~344~OL~CITY, TX 76118~99~123 STREET~99~4TH
FLOOR~SD~IR~LF~DROP|
SI~TI~ES~123X4501~NP~213~CO~344~TL~DALLAS, TX 76118~99~123 ANY STREET~99~4TH FLOOR|
PID~F~~~~CUSTOMER REFERENCE TEXT AND CIRCUIT DESCRIPTION|
REF~OW~~DS0 Service|
QTY~01~24~DH|
NM1~C3~2~New York DS1|
N3~123 AnyStreet~4th Floor Room 100|
N4~City~ST~11223|
HL (Hierarchical Level) Sample: HL~11~3~5~1|
LX (Assigned Number) Sample: LX~1|
SI (Service Characteristic ID) Sample: SI~TI~CN~Z123X4501~NP~213~CO~344~OL~CITY, TX 76118~99~123
STREET~99~4TH FLOOR~SD~IR~LF~DROP|
August 2017
Verizon
811 – Transaction Set
EDI Billing
Version 004010
Implementation Guide
Detail Section
SV*0200: Monthly Service Charge
39
SI05
234
Origination NPA
SI06
1000
Service Characteristics Qualifier
CO NXX code
SI07
234
Origination NXX
SI08
1000
Service Characteristics Qualifier
OL Originating Location
SI09
234
Origination City, ST, Zip
SI10
1000
Service Characteristics Qualifier
99 Continuation of Origination Loc
SI11
234
Origination Location Address Line 1
SI12
1000
Service Characteristics Qualifier
99 Continuation of Origination Loc
SI13
234
Origination Location Address Line 2
SI14
1000
Service Characteristics Qualifier
SD Settlement code (Orig only)
SI15
234
Settlement Code
IR = Interstate
SI16
1000
Service Characteristics Qualifier
LF Line Class code – sw itching type
SI17
234
SDLC indicator/switching type
DROP
Element ID
Data Element
Element Names / Values
SI01
559
Agency Qualifier Code
TI Telecommunications Industry
SI02
1000
Service Characteristics Qualifier
ES Term exchange Circuit ID
SI03
234
Termination Circuit ID
SI04
1000
Service Characteristics Qualifier
NP Terminating NPA code
SI05
234
Termination NPA
SI06
1000
Service Characteristics Qualifier
CO Terminating NXX code
SI07
234
Termination NXX
SI08
1000
Service Characteristics Qualifier
TL Terminating Location
SI09
234
Termination City, ST, Zip
SI10
1000
Service Characteristics Qualifier
99 Continuation of Termination Loc
Notes: 1. SI segment with “CN” pair contains “Origination” circuit information.
2. SI segment with “”ES” pair contains “Termination” circuit information.
SI (Service Characteristic ID) Sample: SI~TI~ES~123X4501~NP~213~CO~344~SE~AB3245~TL~DALLAS, TX
76118~99~123 ANY STREET~99~4TH FLOOR|
August 2017
Verizon
811 – Transaction Set
EDI Billing
Version 004010
Implementation Guide
Detail Section
SV*0200: Monthly Service Charge
40
SI11
234
Termination Location Address Line 1
SI12
1000
Service Characteristics Qualifier
99 Continuation of Termination Loc
SI13
234
Termination Location Address Line 2
Element ID
Data Element
Element Names / Values
PID01
349
Item Description Type
F Free-form
PID05
352
Description of circuit / Customer Reference Text
Element ID
Data Element
Element Names / Values
REF01
128
Reference Identification Qualifier
OW Service Number
REF03
352
Service Type Description
Element ID
Data Element
Element Names / Values
QTY01
673
Quantity Qualifier
01 Discrete Quantity
QTY02
380
Circuit miles, Line Speed, or quantity
QTY03
355
Unit or Basis of Measure Code
DH Miles
Notes: 1. SI segment with “CN” pair contains “Origination” circuit information.
2. SI segment with “”ES” pair contains “Termination” circuit information.
PID (Product/Item Description) Sample:
PID~F~~~~CUSTOMER REFERENCE TEXT AND CIRCUIT DESCRIPTION|
HL7, type level, is used to group details together by earning number, WTN, billing number, Calling Card, Conference
and/or other Billing Information.
Note on Circuit Number: We are currently presenting the Circuit number at HL5 & HL7. Please create your data maps to
use HL5 only for the Circuit numbers. In the future we plan to remove the Circuit Number from HL7 and only provide in
HL5.
Agency Qualifier Code
TI = Telecommunications Ind.
SI02
1000
Service Characteristics Qualifier $EN = Earning Number
SI03
234
Product/Service ID
4107529999 = WTN that generated the charge
SI04
1000
Service Characteristics Qualifier $TN = Telephone Number
SI05
234
Product/Service ID
4107529999647 = Associated Billing N umber (A
telephone number associated w ith the account
number being billed)
SI06
1000
Service Characteristics Qualifier $BN = Billing Number
SI07
234
Product/Service ID
000614899992 = Bill ing Number (account number
being billed for the charge)
Element ID
Data Element
Element Names / Values
NM101
98
Entity Identification Code
77 = Service Location
NM102
1065
Entity Type Qualifier
HL (Hierarchical Level) Sample: HL~4~1~7~1|
LX (Assigned Number) Sample: LX~2|
SI (Service Characteristic ID) Sample: SI~TI~EN~4107529999~TN~4107529999647~BN~000614899992|
$ Refer to Additional Code Lists Used by OBF/ETB (Section 10.4) for values associated w ith DE 1000.
NM1 Loop (Service Location) Sample: NM1~77~2~BUILDING 1|
August 2017
Verizon
811 – Transaction Set
EDI Billing
Version 004010
Implementation Guide
Detail Section
SV*0200: Monthly Service Charge
48
2 = Non-Person Entity
NM103
1035
Name
Building 1 = Name of Service Location
Element ID
Data Element
Element Names / Values
N301
166
Address Information
12 FIRST STREET = First line of address
2 FLOOR = Second line of address
Element ID
Data Element
Element Names / Values
N401
19
City
YOUR CITY = City of address
N402
156
State
NY = Sate of address
N403
116
Postal Code
33333 = Zip Code of address
Segment
ID
Segment
Position
Segment Description
Loop
Max
Use
O/M
HL
010
Hierarchical Level
HL5
1
M
~
N/A
For list of segments used at HL4, see
the HL4 section of this guide
N/A
N/A
N/A
HL
010
Hierarchical Level
HL6
1
M
N3 (Address Information) Sample: N3~12 FIRST STREET|
N3~2 FLOOR|
Recurring Details (SV~0110) is used to provide the monthly charges on the ARBOR, IBRS, IX Plus and Vision
bills. Recurring Details are essentially the same as the Monthly Service Charge details, except the IT1 at HL4
contains 0110. See paragraph 7.2.5 for specific details of segments used and samples.
7.2.5 SV~0200: Monthly Service Charge
Monthly Service Charge details represents the recurring service and product charges (USOC, ISOC or
POE). This information is presented using HL 5, 6 and 7 for grouping related detail items and HL 8 for each
individual detail item. HL 5, Category, is used to group charges by Switchboard/PBX/SYS Account Code(s) and
Centrex Location or Location Group as applicable. HL 6, Sub-category, is used to group data by Billing Agency
Code (department number). HL 7, Type, is used to group data by Telephone/Circuit Number.
The SLN06 element contains the cost of the detail item. The sum of all SLN06 amounts equals the IT104 amount
for Monthly Service (IT107 = 0200). This permits the user to verify the IT104 amount for Monthly Services.
Structure of Monthly Service Charge Details:
August 2017
Verizon
811 – Transaction Set
EDI Billing
Version 004010
Implementation Guide
Detail Section
SV*0200: Monthly Service Charge
49
~
N/A
For list of segments used at HL5, see
the HL5 section of this guide
N/A
N/A
N/A
HL
010
Hierarchical Level
HL7
1
M
~
N/A
For list of segments used at HL7, see
the HL7 section of this guide
SI (Service Characteristic Identification) Sample: SI~TI~SW~A~CX~00121|
$ Refer to Additional Code Lists Used by OBF/ETB (Section 10.4) for values associated w ith DE 1000.
HL (Hierarchical Level) Sample: HL~4~3~6~1|
August 2017
Verizon
811 – Transaction Set
EDI Billing
Version 004010
Implementation Guide
Detail Section
SV*0200: Monthly Service Charge
51
Element ID
Data Element
Element Names / Values
LX01
554
Sequentially Assigned Number
Element ID
Data Element
Element Names / Values
REF01
128
Reference Number Qualifier
CR = Customer Reference Number
REF02
127
Reference Number = 00046
Element ID
Data Element
Element Names / Values
HL01
628
Hierarchical ID Number
HL02
734
Hierarchical Parent ID Number
HL03
735
Hierarchical Level Code
7 = Type
HL04
736
Hierarchical Child Code
0 = No Subordinate Segments
Element ID
Data Element
Element Names / Values
LX01
554
Sequentially Assigned Number
Element ID
Data Element
Element Names / Values
SI01
559
Agency Qualifier Code
TI = Telecommunications Ind.
SI02
1000
Service Characteristics Qualifier $EN = Earning Number
SI03
234
Product/Service ID
4107529999 = WTN that generated the charge
SI04
1000
Service Characteristics Qualifier $TN = Telephone Number
SI05
234
Product/Service ID
4107529999647 = Associated Billing N umber (A
telephone number associated w ith the account
LX (Assigned Number) Sample: LX~2|
REF (Reference Number) Sample: REF~CR~00046|
HL (Hierarchical Level) Sample: HL~5~4~7~0|
LX (Assigned Number) Sample: LX~3|
SI (Service Characteristic Identification) Sample:
SI~TI~EN~4107529999~TN~4107529999647~BN~000614899992|
August 2017
Verizon
811 – Transaction Set
EDI Billing
Version 004010
Implementation Guide
Detail Section
SV*0200: Monthly Service Charge
52
number being billed)
SI06
1000
Service Characteristics Qualifier $BN = Billing Number
SI07
234
Product/Service ID
000614899992 = Bill ing Number (account number
being billed for the charge)
Element ID
Data Element
Element Names / Values
NM101
98
Entity Identification Code
77 = Service Location
NM102
1065
Entity Type Qualifier
2 = Non-Person Entity
NM103
1035
Name
Building 1 = Name of Service Location
Element ID
Data Element
Element Names / Values
N301
166
Address Information
12 FIRST STREET = First line of address
2 FLOOR = Second line of address
Element ID
Data Element
Element Names / Values
N401
19
City
YOUR CITY = City of address
N402
156
State
NY = Sate of address
N403
116
Postal Code
33333 = Zip Code of address
Element ID
Data Element
Element Names / Values
HL01
628
Hierarchical ID Number
HL02
734
Hierarchical Parent ID Number
HL03
735
Hierarchical Level Code
8 = Charge Detail
$ Refer to Additional Code Lists Used by OBF/ETB (Section 10.4) for values associated w ith DE 1000.
NM1 Loop (Service Location) Sample: NM1~77~2~BUILDING 1|
N3 (Address Information) Sample:N3~12 FIRST STREET|
# Included in IT104 amount.
SI (Service Characteristic Identification) Sample: SI~TI~SC~00000906|
$ Refer to Additional Code Lists Used by OBF/ETB (Section 10.4) for values associated w ith DE 1000.
@Product/Service ID associated w ith Service Category “SC” may be a USOC or ISOC (maximum of five
characters) or a locally defined field. expressTRAK w ill populate this element w ith values for Product
Offering Element (POE) at eight positions long.
Example: Product Offering Element could be 00000906 for call waiting. The description is in the PID in this SLN loop
# Included in IT104 amount.
SI (Service Characteristic Identification) Sample: SI~TI~SC~00001061|
$ Refer to Additional Code Lists Used by OBF/ETB (Section 10.4) for values associated w ith DE 1000.
@ Product/Service ID associated w ith Service Category “SC” may be a USOC or ISOC (maximum of five
characters) or a locally defined field. Only available with expressTRAK, Verizon will populate
this element with values for Product Offering Element (POE). This item is eight (8) characters.
Example: Product Offering Element could be call waiting.
August 2017
Verizon
811 – Transaction Set
EDI Billing
Version 004010
Implementation Guide
Detail Section
SV*0200: Monthly Service Charge
55
Element ID
Data Element
Element Names / Values
PID01
349
Item Description Code
X = Semi-Structured (Code & Text)
PID02
750
Product/Process Characteristic Code
ZZ = Mutually Defined
PID03
559
Agency Qualifier Code
AS = Assigned by Seller
PID04
751
Product Description Code
SC Service Category Code
PID05
352
Description
Item Description = Description of SLN Charge
Element ID
Data Element
Element Names / Values
REF01
128
Reference Number Qualifier
OW = Serial Number
REF02
127
Reference Number
855573928 = Last Service Order Number
Element ID
Data Element
Element Names / Values
DTM01
374
Date/Time Qualifier
007 = Effective
DTM02
373
Date = CCYYMMDD
Element ID
Data Element
Element Names / Values
SLN01
350
Identification Assigned =
Sequentially Assigned Number
Agency Qualifier Code
TI = Telecommunications Ind.
SI02
1000
Service Characteristics Qualifier $SC = Service Category Code
SI03
234
Product/Service ID
00000087 = P roduct Offering Element
Element ID
Data Element
Element Names / Values
PID01
349
Item Description Code
X = Semi-Structured (Code & Text)
PID02
750
Product/Process Characteristic Code
ZZ = Mutually Defined
PID03
559
Agency Qualifier Code
AS = Assigned by Seller
PID04
751
Product Description Code
SC Service Category Code
PID05
352
Description
Item Description = Description of SLN Charge
Element ID
Data Element
Element Names / Values
TXI01
963
Tax Type Code
FD = Federal Tax
TXI06
441
Tax Exempt Code
1 = Tax Exempt
Element ID
Data Element
Element Names / Values
REF01
128
Reference Number Qualifier
SE = Serial Number
REF02
127
Reference Number = Serial Number = A
SI (Service Characteristic Identification) Sample: SI~TI~SC~00000087|
$ Refer to Additional Code Lists Used by OBF/ETB (Section 10.4) for values associated w ith DE 1000.
@ Product/Service ID associated w ith Service Category “SC” may be a USOC or ISOC (maximum of five
characters) or a locally defined field. Only available with expressTRAK, Verizon will populate
this element with values for Product Offering Element (POE). This item is eight (8) characters.
Example: Product Offering Element could be call waiting.
7.2.5.1 Centrex Addendum to SV~0200 (IT107 = 0200 and (SLN10 = 220 or 225))
Centrex Summary Charges are only provided to Verizon South Legacy system Centrex customers in
Pennsylvania and Delaware.
Centrex Summary information is provided by Account and Location using HL 8, Charge Detail, for each
individual detail item. The Account summary contains the number of centrex lines and total amount for those lines. The
Location summary contains the number of centrex lines assessed a mileage charge and the total amount for those lines.
The SLN06 element contains the cost of the detail item. The sum of all SLN06 amounts equals the IT104
amount for Monthly Service (IT107 = 0200). This permits the user to verify the IT104 amount for Monthly Services.
SI (Service Characteristic Identification) Sample: SI~TI~SC~RM24K|
$ Refer to Additional Code Lists Used by OBF/ETB (Section 10.4) for values associated with DE 1000.
QTY (Quantity) Sample: QTY~01~3~AL|
QTY~94~9~DH|
August 2017
Verizon
811 – Transaction Set
EDI Billing
Version 004010
Implementation Guide
SV*2050: Total Amount Billed
(for Summary/Consolidated Billing Only)
62
Segment
ID
Position
Segment Description
Loop
Max
Use
O/M
HL
010
Hierarchical Level
HL4
1
M
*
N/A
For list of segments used at HL4,
see the HL4 section of this guide
N/A
N/A
N/A
HL
010
Hierarchical Level
HL5
1
M
*
N/A
For list of segments used at HL5,
see the HL5 section of this guide
N/A
N/A
N/A
HL
010
Hierarchical Level
HL6
1
M
*
N/A
For list of segments used at HL6,
see the HL6 section of this guide
N/A
N/A
N/A
HL
010
Hierarchical Level
HL7
1
M
*
N/A
For list of segments used at HL7,
see the HL7 section of this guide
N/A
N/A
N/A
HL
010
Hierarchical Level
HL8
1
M
SLN
390
Subline Item Detail
SLN
>1
M
SI
400
Service Characteristic
SLN
>1
M
PID
410
Product/Item Description
SLN
200
O
7.2.6 SV~0305: Service and Equipment Information
Service and Equipment Information Details (SV~0305) is used to provide the monthly charges on CABS bills.
Service and Equipment Information Details are essentially the same as the Monthly Service Charge details,
except the IT1 at HL4 contains 0305. See paragraph 7.2.5 for specific details of segments used and samples.
7.2.7 SV~0400: Other Charges & Credits /Additions & Changes
Additions & Changes (OC&C) represent one-time charges and credits in addition to fractional charges and
credits. Additions & Changes Detail is the term used with Verizon expressTRAK while the Verizon Legacy
systems still use the term Other Charges & Credits (OC&C).
The information is presented using HL 5, 6, and 7 for grouping related detail items and HL 8 for each individual
detail item. HL 5, Category, is used to group charges by Switchboard Code (PBX Code, SYS Account Code) and
Centrex Location/Location Group where applicable. HL 6, Sub-category, is used to group data by Billing Agency
Code (department number) and Service Order Number. HL 7 is used to group data by Telephone/Circuit
Number.
The SLN06 element contains the cost of the detail item. The sum of all SLN06 amounts, plus all ITA 07 amounts
(see NOTE below), equal the IT104 amount for Additions and Changes Detail IT107 = 0400. This allows the user
to verify the IT104 amount for Additions and Changes.
NOTE: Due to Legacy Verizon South system constraints, Late Payment Charges may continue to appear in
Additions & Changes (OC&C) until conversion to expressTRAK and the ITA07 would contain the Late Payment
Charge amount.
# Included in IT104 amount.
SI (Service Characteristic Identification) Sample: SI~TI~OD~0000051083~OC~H01|
$ Refer to Additional Code Lists Used by OBF/ETB (Section 10.4) for values associated w ith DE 1000.
August 2017
Verizon
811 – Transaction Set
EDI Billing
Version 004010
Implementation Guide
SV*2050: Total Amount Billed
(for Summary/Consolidated Billing Only)
67
Element ID
Data Element
Element Names / Values
PID01
349
Item Description Type
F = Free Form
PID05
352
Description
Item Description Line 1 = Description of SLN Charge
Item Description Line 2 = Continuation of Description
Item Description Line 3 = Continuation of Description
Element ID
Data Element
Element Names / Values
DTM01
374
Date/Time Qualifier
007 = Effective Date
DTM02
373
Date = Service Period Start = CCYYMMDD
Element ID
Data Element
Element Names / Values
SLN01
350
Assigned Identification
SLN03
662
Relationship Code
I = Included
SLN04
380
Quantity = 1
SLN05
355
Unit or Basis for Measurement Code
M4 = Monetary Value
SLN06
212
Unit Price #
2.40 = Dollars/Cents
SLN08
662
Relationship Code
I = Included
Element ID
Data Element
Element Names / Values
SI01
559
Agency Qualifier Code
TI = Telecommunications Ind.
SI02
1000
Service Characteristics Qualifier
OD = Description Code
SI (Service Characteristic Identification) Sample:
SI~TI~OD~00300003079~OC~C01~SC~00003079~SA~A|
August 2017
Verizon
811 – Transaction Set
EDI Billing
Version 004010
Implementation Guide
SV*2050: Total Amount Billed
(for Summary/Consolidated Billing Only)
68
SI04
1000
Service Characteristics Qualifier $OC = Category Code
SI05
234
Product/Service ID
C01 = Monthly Recurring Changes
SI06
1000
Service Characteristics Qualifier
SC = Service Category Code
SI07
234
Product/Service ID @
00003079 = P roduct Offering Element
SI08
1000
Service Characteristics Qualifier
SA = Service Activity Code
SI09
234
Product/Service ID
A = Add
Element ID
Data Element
Element Names / Values
PID01
349
Item Description Type
F = Free Form
PID05
352
Description
Item Description = Description of SLN Charge
Element ID
Data Element
Element Names / Values
TXI01
963
Tax Type Code
ST = State Sales Tax
TXI06
441
Tax Exempt Code
1 = Tax Exempt
Element ID
Data Element
Element Names / Values
REF01
128
Reference Number Qualifier
PO = Purchase Order Number
REF02
127
Reference Number
123456 = Purchase Order Number
$ Refer to Additional Code Lists Used by OBF/ETB (Section 10.4) for values associated w ith DE 1000. @ Product/Service ID associated w ith Service Category “SC” may be a USOC or ISOC (maximum of five
characters) or a locally defined field. Only available with expressTRAK, Verizon will populate
this element with values for Product Offering Element (POE). This item is eight (8) characters.
Example: Product Offering Element could be call waiting.
PID (Product/Item Description) Sample: PID~F~~~~Item Description line 1|
TXI (Tax Information) Sample: TXI~ST~~~~~1|
REF (Reference Number) Sample: REF~PO~123456|
August 2017
Verizon
811 – Transaction Set
EDI Billing
Version 004010
Implementation Guide
SV*2050: Total Amount Billed
(for Summary/Consolidated Billing Only)
69
Element ID
Data Element
Element Names / Values
DTM01
374
Date/Time Qualifier
150 = Service Period Start
151 = Service Period End
DTM02
373
Date = Service Period Start = CCYYMMDD
Date = Service Period End = CCYYMMDD
Element ID
Data Element
Element Names / Values
AMT01
522
Amount Qualifier Code
AP = Amount Prior to Fractionalizing
AMT02
782
Monetary Amount
5.00 = Dollars/Cents
Element ID
Data Element
Element Names / Values
QTY01
673
Quantity Identifier
94 = Billable Quantity
QTY02
380
Quantity = 1
Segment
ID
Position
Segment Description
Loop
Max
Use
O/M
HL
010
Hierarchical Level
HL4
1
M
~
N/A
For list of segments used at HL4,
see the HL4 section of this guide
N/A
N/A
N/A
HL
010
Hierarchical Level
HL5
1
M
~
N/A
For list of segments used at HL5,
see the HL5 section of this guide
Itemized Calls, local and long distance, information is presented using HL 6 and 7 for grouping related detail items
and HL 9 for each individual detail item. HL 6, Sub-Category, is used to group charges by Billing Agency Code
(department number). HL 7, Type, is used to group data by telephone line number.
Itemized calls associated with Interexchange Carrier Billing, Optional Calling Plans and Local Usage are
informational which is reflected by a value of “O” in element TCD16. See specific section(s) for more information.
Note: For SingleView, the Line/Circuit Service Attributes can be found with the Monthly Recurring Charges
Structure of Itemized Call Detail:
August 2017
Verizon
811 – Transaction Set
EDI Billing
Version 004010
Implementation Guide
SV*2050: Total Amount Billed
(for Summary/Consolidated Billing Only)
70
HL
010
Hierarchical Level
HL6
1
M
~
N/A
For list of segments used at HL6,
see the HL6 section of this guide
N/A
N/A
N/A
HL
010
Hierarchical Level
HL7
1
M
~
N/A
For list of segments used at HL7,
see the HL7 section of this guide
Monetary Amount # ¢
(Undiscounted in Dollars/Cents)
1.06 = Charge for Call
TCD13
782
Monetary Amount # ¢
(Net Amount After Discount in Dollars/Cents)
Not depicted in this sample.
TCD16
662
Relationship Code
I = Included
Element ID
Data Element
Element Names / Values
SI01
559
Agency Qualifier Code
TI = Telecommunications Ind.
SI02
1000
Service Characteristics Qualifier $MT = Message Type
SI03
234
Product/Service ID
SP = Sent Paid / DDD
SI04
1000
Service Characteristics Qualifier
RP = Rate Period Code
SI05
234
Product/Service ID
03 = Rate Period = Day
SI06
1000
Service Characteristics Qualifier
TM = To/Terminating Station Telephone No.
SI07
234
Product/Service ID
6165552210 = Telephone Number
SI08
1000
Service Characteristics Qualifier
FN = From/Originating Station Telephone No.
SI09
234
Product/Service ID
2155551011 = Telephone Number
SI10
1000
Service Characteristics Qualifier
MC = Message or Rate Class
SI11
234
Product/Service ID
DS = Day Station
SI12
1000
Service Characteristics Qualifier
SD = Settlement Code
SI13
234
Product/Service ID
IA = Intrastate
# Included in IT104 amount. If TCD13 is populated, use TCD13 for balancing. If TCD13 is not
populated use TCD12 for balancing.
¢ Foreign State and local taxes, if applicable, are reported in TCD12 for non-Optional Call Plan calls
or in TCD13 for Optional Call Plan calls. The TXI segment shows the individual tax amounts.
SI (Service Characteristic Identification) Sample:
SI~TI~MT~SP~RP~03~TM~6175552210~FN~5085551011~MC~DS~SD~IA|
$ Refer to Additional Code Lists Used by OBF/ETB (Section 10.4) for values associated with DE 1000.
August 2017
Verizon
811 – Transaction Set
EDI Billing
Version 004010
Implementation Guide
SV*2050: Total Amount Billed
(for Summary/Consolidated Billing Only)
75
Element ID
Data Element
Element Names / Values
TXI01
963
Tax Type Code
ST = State Sales Tax
TXI02
782
Monetary Amount
0.06 = Dollars/Cents
TXI07
662
Relationship Code
A = Added
Element ID
Data Element
Element Names / Values
TCD01
350
Assigned Identification number
TCD02
373
Date of Call = CCYYMMDD
TCD03
337
Time of Call = HHMMSS
TCD04
309
Location Qualifier Code for ‘To’ PlaceZZ = Mutually Defined
TCD05
310
Location Identifier for ‘To’ Place
Stock Info = ‘To’ Place
TCD06
156
State or Province Code f or ‘To’ StateNot depicted in this sample.
TCD07
309
Location Qualifier Code for ‘From’ PlaceCI = City
TCD08
310
Location Identifier for ‘From’ Place
New York = ‘From’ Place
TCD09
156
State or Province Code f or ‘From’ State
NY = ‘From’ State
TCD10
739
Measurement Value
180 =Duration of call in minutes and tenths of
minutes
TCD12
782
Monetary Amount # ¢
(Undiscounted in Dollars/Cents)
5.98 = Charge for Call
TCD13
782
Monetary Amount # ¢
(Net Amount After Discount in Dollars/Cents)
¢ Foreign State and local taxes, if applicable, are reported in TCD12 for non-Optional Call Plan calls
or in TCD13 for Optional Call Plan calls. The TXI segment shows the individual tax amounts.
# Included in IT104 amount. If TCD13 is populated, use TCD13 for balancing. If TCD13 is not
populated use TCD12 for balancing.
August 2017
Verizon
811 – Transaction Set
EDI Billing
Version 004010
Implementation Guide
SV*2050: Total Amount Billed
(for Summary/Consolidated Billing Only)
76
Element ID
Data Element
Element Names / Values
SI01
559
Agency Qualifier Code
TI = Telecommunications Ind.
SI02
1000
Service Characteristics Qualifier
TM = Terminating Telephone Number
SI03
234
Product/Service ID
900 562-8600 = Terminating StationTelephone
Number
SI04
1000
Service Characteristics Qualifier $
MT = Message Type
SI05
234
Product/Service ID
SP = Sent Paid
SI06
1000
Service Characteristics Qualifier
MC = Message/Rate Class
SI07
234
Product/Service ID
DS = Dial Station
SI08
1000
Service Characteristics Qualifier
RP = Rate Period Code
SI09
234
Product/Service ID
05 = Night/Weekend
SI10
1000
Service Characteristics Qualifier
FN = From/Originating Telephone Number
SI11
234
Product/Service ID
508 555-2210=From/Originating Telephone Number
Segment
ID
Position
Segment Description
Loop
Max
Use
O/M
HL
010
Hierarchical Level
HL4
1
M
~
N/A
For list of segments used at HL4,
see the HL4 section of this guide
N/A
N/A
N/A
HL
010
Hierarchical Level
HL7
1
M
~
N/A
For list of segments used at HL7,
N/A
N/A
N/A
SI (Service Characteristic Identification) Sample:
The WATS Summary is broken down into two components; Charge Detail and Line Detail. The WATS Charge
detail contains rates, usage and charges. The WATS Line Detail contains tapers for hourly rates and time ranges;
time and messages used and number of inward calls to 800 Service that could not complete due to a busy
condition. Each WATS Service is summarized by service group and is presented using a HL 8, Charge Detail and
a HL 9, Line Detail.
The SLN06 element contains the billed amount for WATS Services. The amount is included in the IT104 for
Itemized Calls (IT107 = 0500).
Structure of WATS:
August 2017
Verizon
811 – Transaction Set
EDI Billing
Version 004010
Implementation Guide
SV*2050: Total Amount Billed
(for Summary/Consolidated Billing Only)
77
see the HL7 section of this guide
HL
010
Hierarchical Level
HL8
1
M
SLN
390
Subline Item Detail
SLN
>1
M
SI
400
Service Characteristic
SLN
>1
M
ITA
440
Allowance, Charge or Service
SLN
10
O
QTY
510
Quantity
SLN/QTY
>1
O
HL
010
Hierarchical Level
HL9
1
M
QTY
510
Quantity
SLN/QTY
1
O
USD
620
Usage Sensitive Detail
USD
>1
O
SI
625
Service Characteristics
USD
>1
O
TRF
640
Rating Factors
USD
1
O
QTY
650
Quantity
USD/QTY
>1
O
Element ID
Data Element
Element Names / Values
HL01
628
Hierarchical ID Number
HL02
734
Hierarchical Parent ID Number
HL03
735
Hierarchical Level Code
8 = Charge Detail
HL04
736
Hierarchical Child Code
1 = Subordinate Segments
SAMPLE MAPPING WATS:
HL~7~1~4~1|
IT1~~1~M4~68.26~~SV~0500~ZZ~3|
HL~8~7~8~1|
SLN~27~~I~1~M4~68.28~~I~SV~1000|
SI~TI~SD~AB|
HL~9~8~9~0|
USD~O~1~~~HR~11.38~~0|
SI~TI~RP~09~WN~18887779999~BA~9|
TRF~AE~03~30~HR~8.78|
QTY~94~11.38~HR|
QTY~99~1054~C0|
USD~O~2~7.2~~~~~0~~HR~~20| First 20 hours at 7.20 / hr
USD~O~3~6~~~~~0~~HR~20.01| Over 20 hours at $6.00 / hr
HL (Hierarchical Level) Sample: HL~8~7~8~1|
August 2017
Verizon
811 – Transaction Set
EDI Billing
Version 004010
Implementation Guide
SV*2050: Total Amount Billed
(for Summary/Consolidated Billing Only)
78
Element ID
Data Element
Element Names / Values
SLN01
350
Sequentially Assigned Number
SLN03
662
Relationship Code
I = Included
SLN04
380
Quantity
1 = Unit price is total charge
SLN05
355
Unit or Basis for Measurement Code
M4 = Monetary Value
SLN06
212
Unit Price #
SLN08
662
Relationship Code
I = Included
SLN09
235
Product/Service ID Qualifier
SV = Service Rendered
SLN10
234
Product/Service ID
1950 = InWATS/800 Service
Element ID
Data Element
Element Names / Values
SI01
559
Agency Qualifier Code
TI = Telecommunications Ind.
SI02
1000
Service Characteristics Qualifier
SD = Settlement Code
SI03
234
Product/Service ID
AB = Intra - US/US
Element ID
Data Element
Element Names / Values
HL01
628
Hierarchical ID Number
HL02
734
Hierarchical Parent ID Number
HL03
735
Hierarchical Level Code
9 = Line Detail
HL04
736
Hierarchical Child Code
0 = No Subordinate Segments
Agency Qualifier Code
TI = Telecommunications Ind.
SI02
1000
Service Characteristics Qualifier $RP = Rate Period
SI03
234
Product/Service ID
09 = Regular (Non time of day WATS)
SI04
1000
Service Characteristics Qualifier $WN = WATS Number
SI05
234
Product/Service ID
18887779999 = WATS Number
SI06
1000
Service Characteristics Qualifier
BA = WATS Band
SI07
234
Product/Service ID
9 = Intrastate Domestic Service
Element ID
Data Element
Element Names / Values
TRF01
673
Quantity Qualifier
AE =Min. Avg. Time Requirement (MATR)
TRF02
355
Unit of Measurement Code
03 = Seconds
TRF03
380
Quantity Minimum Period
TRF04
355
Unit of Measurement Code
HR = Hours
TRF05
380
Quantity = Equivalent time
(formula: number of calls (QTY02 w here QTY03 =
C0) times minimum period (TRF03) and then
converted to the same Unit of Measurement)
Element ID
Data Element
Element Names / Values
QTY01
673
Quantity Qualifier Code
94 = Billable Quantity
QTY02
380
Quantity
SI (Service Characteristic Identification) Sample: SI~TI~RP~09~WN~18887779999~BA~9|
$ Refer to Additional Code Lists Used by OBF/ETB (Section 10.4) for values associated w ith DE 1000.
TRF (Rating Factors Sample: TRF~AE~03~30~HR~8.78|
QTY (Quantity) Sample: QTY~94~11.38~HR|
August 2017
Verizon
811 – Transaction Set
EDI Billing
Version 004010
Implementation Guide
SV*2050: Total Amount Billed
(for Summary/Consolidated Billing Only)
80
QTY03
355
Unit of Measurement
HR = Hours
Element ID
Data Element
Element Names / Values
QTY01
673
Quantity Qualifier Code
99 = Quantity Used
QTY02
380
Quantity
QTY03
355
Unit of Measurement
C0 = Calls
Element ID
Data Element
Element Names / Values
USD01
662
Relationship Code
O = Informational
USD02
350
Assigned Identification
USD03
118
Rate
7.2 = $7.20 per hour for first 25 hours
USD08
782
Monetary Amount
USD10
355
Unit of Measurement Code
HR = Hours
USD11
740
Range Minimum
Not populated when zero for first range
USD12
741
Range Maximum
20 = Range Maximum, first 20 hours
Element ID
Data Element
Element Names / Values
USD01
662
Relationship Code
O = Informational
USD02
350
Assigned Identification
USD03
118
Rate
6 = $6.00 per hour for over 20 hours
USD08
782
Monetary Amount
USD10
355
Unit of Measurement Code
HR = Hours
USD11
740
Range Minimum
20.01 = Range Minimum, over 20 hours
USD12
741
Range Maximum
Not populated when open-ended for last range
ISDN account level charges are presented at HL8.
ISDN Itemized Calls, local and long distance, information is presented using HL 7 for grouping related detail items
and HL 9 for each individual detail item. HL 7, Type, is used to group data by telephone line number.
$ Refer to Additional Code Lists Used by OBF/ETB (Section 10.4) for values associated w ith DE 1000.
August 2017
Verizon
811 – Transaction Set
EDI Billing
Version 004010
Implementation Guide
SV*2050: Total Amount Billed
(for Summary/Consolidated Billing Only)
86
Segment
ID
Position
Segment Description
Loop
Max
Use
O/M
HL
010
Hierarchical Level
HL8
1
M
SLN
390
Subline Item Detail
SLN
>1
M
SI
400
Service Characteristic
SLN
>1
M
PID
410
Product/Item Description
SLN
200
O
ITA
440
Allowance Charge or Service
SLN
10
O
Element ID
Data Element
Element Names / Values
HL01
628
Hierarchical ID Number
HL02
734
Hierarchical Parent ID Number
HL03
735
Hierarchical Level Code
8 = Charge Detail
HL04
736
Hierarchical Child Code
0 = No Subordinate Segments
7.2.8.3 CLASS Addendum to SV~0500 (IT107 = 0500, SLN10 = 1615)
Custom Local Access Switch Service (CLASS) account level charges are presented at HL8. The SLN06 element
contains the rate; SLN04 element contains the quantity. Since the SLN05 value is not “M4”, the SLN06 value
must be multiplied by the SLN04 value to determine the billed amount. The sum of all billed amounts (SLN06
times SLN04) is included in the IT104 amount.
Structure of Custom Local Access Switch Services (CLASS):
Sample Mapping of Custom Local Access Switch Services (CLASS):
# Included in IT104 amount, multiply SLN04 by SLN06 to determine billed amount.
SI (Service Characteristic Identification) Sample: SI~TI~SC~15~SF~15~DS~TBCR|
$ Refer to Additional Code Lists Used by OBF/ETB (Section 10.4) for values associated w ith DE 1000. ø Reference Code Lists for DE 1000 value of “SF” in Appendix A.
August 2017
Verizon
811 – Transaction Set
EDI Billing
Version 004010
Implementation Guide
SV*2050: Total Amount Billed
(for Summary/Consolidated Billing Only)
88
Element ID
Data Element
Element Names / Values
PID01
349
Item Description Code
X = Semi-Structured (Code & Text)
PID02
750
Product/Process Characteristic Code
ZZ = Mutually Defined
PID03
559
Agency Qualifier Code
AS = Assigned by Seller
PID04
751
Product Description Code
SC Service Category Code
SF Service Feature/Option Code
DS Discount Planned Code
¢ Foreign State and local taxes, if applicable, are reported in TCD12 for non-Optional Call Plan calls
or in TCD13 for Optional Call Plan calls. .
# Included in IT104 amount. If TCD13 is populated, use TCD13 for balancing. If TCD13 is not
populated use TCD12 for balancing.
August 2017
Verizon
811 – Transaction Set
EDI Billing
Version 004010
Implementation Guide
SV*2050: Total Amount Billed
(for Summary/Consolidated Billing Only)
90
Element ID
Data Element
Element Names / Values
SI01
559
Agency Qualifier Code
TI = Telecommunications Ind.
SI02
1000
Service Characteristics Qualifier
MT = Terminating Telephone Number
SI03
234
Product/Service ID
SP = Sent Paid/DDD
SI04
1000
Service Characteristics Qualifier $
RP = Message Type
SI05
234
Product/Service ID
03 = Day
SI02
1000
Service Characteristics Qualifier
TM = Terminating Telephone Number
SI03
234
Product/Service ID
8157779999 = Term inating StationTelephone
Number
SI10
1000
Service Characteristics Qualifier
FN = From/Originating Telephone Number
SI11
234
Product/Service ID
8156668888 =From /Originating Telephone N umber
SI06
1000
Service Characteristics Qualifier
MC = Message/Rate Class
SI07
234
Product/Service ID
DS = Dial Station
SI08
1000
Service Characteristics Qualifier
SD = Settlement Code
SI09
234
Product/Service ID
LO = Local
SI10
1000
Service Characteristics Qualifier
DS = Discount Planned Code
SI11
234
Product/Service ID
TBCR = Miscellaneous Calling Services
SI (Service Characteristic Identification) Sample:
SI~TI~MT~SP~RP~03~TM~8157779999~FN~8156668888~MC~DS~SD~LO ~DS~TBCR|
$ Refer to Additional Code Lists Used by OBF/ETB (Section 10.4) for values associated w ith DE 1000.
7.2.8.4 Extended Area Addendum to SV~0500 (IT107 = 0500, SLN10 = 1830)
Extended Area Service is limited to Maryland, Washington DC, Virginia and West Virginia, and is applicable to
Verizon Legacy South and expressTRAK. The data for Extended Area Service is provided at account summary
level only. There is no line level presentation. Account Level data is presented using HL8, Charge Detail.
The SLN06 element contains the sub-total of charges by associated service code with the type of service in
element SI. This amount is included in the IT104 amount for the appropriate Product/Service ID.
August 2017
Verizon
811 – Transaction Set
EDI Billing
Version 004010
Implementation Guide
SV*2050: Total Amount Billed
(for Summary/Consolidated Billing Only)
91
Segment
ID
Position
Segment Description
Loop
Max
Use
O/M
HL
010
Hierarchical Level
HL8
1
M
SLN
390
Subline item Detail
SLN
1
M
SI
400
Service Characteristics
SLN
1
O
QTY
510
Quantity
SLN/QTY
>1
O
Element ID
Data Element
Element Names / Values
SLN01
350
Identification Number =
Sequentially Assigned Number
SLN03
662
Relationship Code
I = Included
SLN04
380
Quantity
1 = Unit price is total charge
SLN05
355
Unit or Basis for Measurement Code
M4 = Monetary Value
SLN06
212
Unit Price #
72.8 = Dollars/Cents
SLN08
662
Relationship Code
I = Included
SLN09
235
Product/Service ID Qualifier
SV = Service Rendered
SI (Service Characteristic Identification) Sample:
SI~TI~ZK~00183399999~ZM~00183399999~UC~INS~PQ~AUDIO|
August 2017
Verizon
811 – Transaction Set
EDI Billing
Version 004010
Implementation Guide
SV*2050: Total Amount Billed
(for Summary/Consolidated Billing Only)
96
SI04
1000
Service Characteristics Qualifier $ZM = Suite
SI05
234
Product/Service ID
00183399999 = Suite
SI06
1000
Service Characteristics Qualifier $UC = Class of Service
SI07
234
Product/Service ID
INS = Instant
SI08
1000
Service Characteristics Qualifier $PQ = Major Product Code
SI09
234
Product/Service ID
AUDIO = Major Product Code
Element ID
Data Element
Element Names / Values
PID01
349
Item Description Code
X = Semi-Structured (Code & Text)
PID02
750
Product/Process Characteristic Code
ZZ = Mutually Defined
PID03
559
Agency Qualifier Code
AS = Assigned by Seller
PID04
751
Product Description Code
PQ = Major Product Code
PID05
352
Audio Conferencing = Description
Element ID
Data Element
Element Names / Values
REF01
128
Reference Number Qualifier
11 = Account Number
CR = Customer Reference Number
BN =Booking Number
REF02
127
Reference Number
93333333 = CUSTOMER ID
5555 1111= Customer Reference Number
00183399999 = CONFERENCE NUMBER
REF03
352
Description
$ Refer to Additional Code Lists Used by OBF/ETB (Section 10.4) for values associated w ith DE 1000.
PID (Product/Item Description Code) Sample: PID~X~ZZ~AS~PQ~Audio Conferencing|