electronic commerce customer guide - at&tw_sbct_ig.pdflevel , service provider level, contains...

Electronic Commerce Customer Guide

811 Transaction Set (Version/Release 004010)

SBC • Trading Partners• Business Customers

Payment System

Value AddedNetworks

Building Electronic Partnerships For The Future...Today

Electronic Data Interchange - Electronic Funds Transfer

Release: April 2004

© BY SBC - All Rights Reserved

Electronic Commerce Customer Guide 811 Implementation Guide Notice

October 2003 i

NOTICE

All references to ‘SBC operating company’ or ‘SBC operating companies’ in this guide refer to SBC operations in specific states depending on the SBC Billing System being referenced: CRIS Billing System SBC operations in all states other than California, Nevada, Illinois, Ohio, Indiana, Wisconsin, Michigan and Connecticut. CABS Billing System SBC operations in Missouri, Oklahoma, Kansas, Arkansas, Texas, California and Nevada.

Electronic Commerce Customer Guide 811 Implementation Guide Table of Contents

June 2003 1

Table of Contents

1 Overview................................................................................. 2 1.1 Schedule of 811 Versions........................................................... 2 1.2 Structure of the 811 .................................................................. 3 1.3 Format of Guide ........................................................................ 5 1.4 Bill and Transaction Formats Provided......................................... 6 1.5 Referencing Charges When Contacting SBC Operating Company ..8 1.6 Taxes, Surcharges, and Fees ..................................................... 9 1.7 Data Element Separator and Segment Terminator ........................ 9 1.8 Functional Group Information ...................................................... 10 1.9 Understanding Hierarchical Level (HL) Segments.......................... 11 2 Heading Area .......................................................................... 13 2.1 Structure ................................................................................. 13 2.2 Sample Mapping ....................................................................... 13 3 Detail Area .............................................................................. 14 3.1 Summary 811 .......................................................................... 14 3.2 Detail 811 ................................................................................ 18 3.3 Structure 1 - Itemized Calls / Itemized Charges ............................ 23 3.4 Structure 2 - Band Usage........................................................... 27 3.5 Structure 3 - WATS Usage......................................................... 28 3.6 Structure 4 - Directory Assistance ............................................. 33 3.7 Structure 5 - Other Charges and Credits ...................................... 34 3.8 Structure 6 - Optional Calling Plan Usage .................................... 36 3.9 Structure 7 - Common Line 800 Usage ........................................ 39 3.10 Structure 8 - Customer Service Record....................................... 46 3.11 Structure 9 - Feature Group A ................................................... 48 3.12 Structure 10 - Contracts and Discounts...................................... 49 4 Summary Area ........................................................................ 50 4.1 Structure ................................................................................. 50 4.2 Sample Mapping ....................................................................... 50 5 Consolidated 811..................................................................... 51 5.1 Structure ................................................................................. 52 5.2 Sample Mapping ....................................................................... 52 6 Auditing the 811 ...................................................................... 53 6.1 Rules of Extended Pricing .......................................................... 53 6.2 Defining and Determining Segment Amount ................................. 53 6.3 Auditing the Detail and Summary Area ....................................... 56 7 Technical Specifications......................................................... 57 811 TS - Segment and Data Element Use.......................................... 57

Electronic Commerce Customer Guide 811 Implementation Guide Overview

April 2004 2

1 Overview

The information in this section reflects the implementation of the Consolidated Service Invoice/Statement Transaction Set (811) by the SBC operating companies. EDI Telecommunications Billing (ETB), author of the 811, develops "standard structures” for providing detail bill information about service offerings. EDI Telecommunications Billing (ETB), author of the Issue 9 Telephone Billing Guidelines, has developed business models for providing detail bill information for common services. As a member of ETB, the SBC operating companies have taken an active role in the development of the “common services” models. For ease of reference, this 811 Implementation Guide is broken into several sections. This section gives an overview of this guide and the 811. Subsequent sections explain the implementation of the 811 by the SBC operating companies. Each section provides a comprehensive discussion of the information being provided for a particular area of the bill, the format of the segments being used to provide information, and a sample mapping. Bill and segment examples, which are used for illustrative purposes, are fictitious.

1.1 Schedule of 811 Versions This 811 Implementation Guide should be used in conjunction with the ASC X12 Draft Version 4 Release 1 standards, and the ETB Telephone Billing Guideline Issue 9 for the 811. The ETB Telephone Billing Guideline can be found on the World Wide Web at: http://www.atis.org/atis/tcif/edi/tbwg/5tc54hom.htm. The file format documented applies to all files that the SBC operating companies provide with a value of “004010” in GS08 to signify release 4 version 1 of the transaction set. The format of this file will be updated as billing changes impact the structure. Trading partners receiving the 811 will be given at least 30 days notice to review pending changes before a new format is delivered. The intention is to provide a stable transaction set for trading partners while working toward consistency of implementation in the telecommunications industry.

http://www.atis.org/atis/tcif/edi/tbwg/5tc54hom.htm


April 2004 3

1.2 Structure of the 811 The 811 is divided into three tables. The Heading Area (Table 1) contains information about the parties exchanging the bill. Some of the common data elements passed in the heading area are: Account number Nature of the bill Billing party (SBC operating company) Billed party (Customer) Invoice Date Due date for payment Section 2 of this implementation guide provides further detail on the data provided in the Heading Area. The Detail Area (Table 2) contains service usage and charge information. The detail area provides 9 hierarchical levels for data presentation. Level 1, Service Provider level, contains information about the provider of the

service. Note that while the information contained in the heading area refers to the provider of the bill (i.e., SBC operating company), information contained in Table 2/Level 1 refers to the actual entity providing the service. It is very common to have charges from several service providers for a given account (e.g., SBC operating company, AT&T, Sprint, and Worldcom charges can all appear on a bill provided by the SBC operating company). Aggregate tax information is also provided at this level.

Level 2, Billing Arrangement level, contains information about the billing

arrangement. This level is used to provide Consolidated Billing Account (CBA) information.

Level 3, Sub-Billing Arrangement level, can also contain information about the

billing arrangement. The SBC operating companies do not use level 3. Level 4, Group level, provides summary charge information for services rendered.

The information at this level relates to the Carrier summary pages of a paper bill. Level 5, Category level, provides segregation of Level 4 charges. Levels 5 and 6

are used to organize charges within the 811. For example, most itemized charges are sorted by station number at Level 5, while the OC&C section is sorted by Purchase Order Number at Level 5 and then by station number at Level 6.

Level 6, Sub-Category level, provides further segregation of Level 4 charges. Level 7, Type level, is similar to levels 5 and 6. Only the SBC operating

companies in California and Nevada use level 7. Level 8, Charge Detail level, contains supporting charge detail for charges provided

at the Level 4.


April 2004 4

Level 9, Line Detail level, contains supporting usage and charge detail for charges

at either Level 4 or Level 8. Section 3 of this implementation guide provides further detail on the data provided in the Detail Area. The Summary Area (Table 3) contains summary information about the 811. The summary area contains several key amounts which can be used to validate the 811. Individual service provider adjustments will also be shown in this area of the 811. • The TDS segment contains the charges for the current bill period. • The ITA segment contains any charges transferred from another account. • The ITA segment may also be used to provide information about miscellaneous

summary area charges or allowances. • A BAL segment with a value of “PB” in BAL02 contains the previous balance

amount on the account (i.e., the amount that was billed in the previous month). • A BAL segment with a value of “NA” in BAL02 contains the net adjustment amount

for the entire bill. • A BAL segment with a value of “TP” in BAL02 contains the total payment amount

applied to the account since the last bill. • A BAL segment with a value of “BT” in BAL02 contains the dishonored check (bank

reject) total amount. • A BAL segment with a value of “TT” in BAL02 contains the calculated amount due

on the account. The TDS segment is always provided, but ITA and BAL segments will only be provided when the applicable amount is not equal to zero. Below is the equation that can be used to calculate the amount due: TDS amount (Current Charges) + ITA amount (Transferred Charges) + BAL PB amount (Amount of Last Bill) + BAL NA amount (Net Adjustment) + BAL TP amount (Payments Applied) + BAL BT amount (Dishonored Check Total) = BAL TT amount (Amount Due)


April 2004 5

1.3 Format of Guide Section 2 of this implementation guide will provide a detailed description of the Heading Section within the 811 transaction set. Section 3 of this implementation guide will provide a detailed description of the Detail Area of the 811 transaction set, and the structure of various billed services. Section 4 of this implementaton guide will provide a detailed description of the Summary Area of the 811 transaction set. Section 5 discusses the Consolidated Billing Arrangement, a billing arrangement that consolidates bills into a single payable bill. Section 6 discusses the Audit Procedures followed to insure the accuracy of the EDI 811 transaction set. The Technical Specifications provide a comprehensive listing of segments, data elements, and code values utilized in producing the 811 transaction set. Since the same segment can be used in different sections of the 811 to provide different information, it is important to review the sample mapping associated with each area of the transaction set. An example of different uses of a segment can be demonstrated with the TXI segment. In the heading area, this segment is used to provide information about the tax exempt status of the billed party; while in the detail area at HL 1, the same segment is used to provide a taxable amount to the billed party.


April 2004 6

1.4 Bill and Transaction Formats Provided Several different bill formats and several different 811 formats are provided. It is important to be aware of which bill format and 811 format you have chosen to receive.

1.4.1 Bill Formats Provided Accounts can be set up in one of four arrangements described below. • Single Account Billing - CRIS Billing System This billing arrangement produces one bill per telephone number. • Group Billing Account - CRIS Billing System This billing arrangement combines several single accounts under one main account

number and produces one large bill. • Consolidated Billing Account (CBA) - CRIS Billing System This billing arrangement can be used in conjunction with both Single Accounts and

Group Billing Accounts. Single Accounts and/or Group Billing Accounts are consolidated under a single CBA number. This produces a special summary 811 of all accounts in the arrangement (see Section 5), followed by a separate 811 for each subordinate account.

• Bill Account Number (BAN) - CABS Billing System This is the only billing arrangement for bills out of the CABS billing system. Like

the Group Billing Account, this billing arrangement can combine several single numbers under one main account number and produces one large bill.

1.4.2 811 Formats Provided The 811 is provided in one of the following formats: Summary 811 Accounts Payable 811 (CRIS billing system only) Carrier Summary 811 (CRIS billing system only) Consolidated Billing Account Summary 811 (CRIS billing system only) CABS Summary 811 (CABS billing system only) Detail 811 Without Customer Service Record With Customer Service Record While the heading and summary areas of these formats are identical, the detail areas differ in the level of detail provided. Summary 811s The summary 811 formats provide high level account information. The advantages of these formats are a less complex programming effort and lower VAN charges. Summary information is provided within HLs 1 - 4.


April 2004 7

The Accounts Payable 811 provides a break out of taxes by jurisdiction and a single charge amount for all current charges. Charges and taxes are not broken out by carrier. This is the smallest and simplest 811 provided. The Carrier Summary 811 provides a break out of charges by carrier. It also provides a break out of taxes by jurisdiction within each carrier. The billing information provided is very similar to the carrier summary pages of a paper bill. While this option does not provide as much information as a Detail 811, it provides more information than the Accounts Payable 811. The Consolidated Billing Account (CBA) Summary 811 provides the bill for the Master consolidated account, but does not provide the ‘memo’ bills for each of the subordinate accounts. The CABS Summary 811 provides high level charges. It also provides a break out of taxes by jurisdiction. Note: This format is the only option for CABS accounts that are not Feature Group A or Specials. Detail 811s The Detail 811 formats provide supporting information for many charges. The key advantage of these full detail formats is more billing information to analyze. While summary information is provided within HLs 1 - 4, full detail information is provided at HLs 5 - 9. The Detail 811 without Customer Servi ce Record provides the same level of billing detail that is currently provided on a paper bill. The Detail 811 with Customer Service Record provides additional detail in support of monthly service charges. It is estimated that the additional Customer Service Record adds approximately 40% to the size of each 811. Note: This format is the only option for Feature Group A or Special CABS accounts.


April 2004 8

1.5 Referencing Charges When Contacting SBC Operating Companies

The information provided in the 811 is used in place of the paper bill. Since the information provided will be used to both pay bills and resolve billing discrepancies, key fields and reference numbers from the 811 should be passed to the customer's internal applications. The following data elements are required to reference an account: Bill Date BIG Segment - BIG01 Account Number REF Segment - REF02 when REF01 = “12” Accounts Payable Number REF Segment - REF02 when REF01 = “AP” Billing System (CRIS/CABS) REF Segment - REF02 when REF01 = “VR” Bill reference numbers, which can be used to reference charges when making billing inquiries, are provided in each loop where charge information is provided. (The TXI segment does not contain a reference number.) The formation of the reference number is Page Number.Item Number (when an item number or page number is not available, a zero will be passed). Data elements ITA05, IT101, SLN01, USD02, and TCD01 contain bill reference numbers. Data elements in the summary area (TDS01 and BAL03) also contain important information, but there is not a data element available to hold a reference number. Charges provided in the summary area generally appear on page 2 of a paper bill.


April 2004 9

1.6 Taxes, Surcharges and Fees Taxes, surcharges and fees which are assessed by a service provider on behalf of a third party (e.g., state or local government) and make up a portion of the monthly telephone bill. Like amounts are aggregated and provided at the service provider level of the 811. Taxes by jurisdiction are also provided for each charge shown at the group level so customers can more accurately track costs associated with each service. If you have any question about whether a charge is a tax, surcharge, or fee, please resolve the issue during the parallel testing phase of your conversion to EDI billing. Reference the charge on the respective paper bill and discuss the issue with your billing representative.

1.7 Data Element Separator and Segment Terminator When displaying mapping examples in this guide, the tilde ( “~” ) is used as the data element separator and the exclamation point ( “ ! ” ) is used as the segment terminator. In live production data, the SBC operating companies will work with the customer to set up the data element separator, segment terminator and sub-element separator. The X12 recommended data element separator of the tilde ( “~” HEX A1), segment terminator of the exclamation point ( “ ! ” HEX 5A) and sub-element separator of the double vertical bar ( “ ¦ “ HEX 6A) are preferred.


April 2004 10

1.8 Functional Group Information All 811 transaction sets provided will be enveloped within a functional group. The purpose of the functional group is to provide control information for the business document being exchanged. The functional group consists of a functional group header (GS segment) and a functional group trailer (GE segment). GS segment Example: GS*CI*006968523CRI*123456XYZ*19990901*1527*128*X*004010! D.E. Data Use Reference Element # Valid Values/Description M GS01 479 Valid Value: CI - Consolidated Invoice M GS02 142 Valid Values: 006968523CRI 006968523CAB 006968523CRW M GS03 124 Application Receiver's Code M GS04 373 Data Interchange Date M GS05 337 Data Interchange Time M GS06 28 Data Interchange Control Number Matches value in GE02 at end of

functional group. M GS07 455 Valid Value: X - Accredited Standards Committee

X12 M GS08 480 Valid Value: 004010 - Version 4, Release 1 GE segment Example: GE*337*128! D.E. Data Use Reference Element # Valid Values/Description M GE01 97 Number of transaction sets M GE02 28 Data Interchange Control Number Matches value in GS06 at beginning of

functional group.


April 2004 11

1.9 Understanding Hierarchical Level (HL) Segments In order to understand the 811, it is important to understand the use of the HL segment. The HL segment indicates the structure of the 811. The HL segment contains the following information: HL*Hierarchical ID Number*Hierarchical Parent ID Number*Hierarchical Level Code* Hierarchical Child Code! HL01 (Hierarchical ID Number) is a unique number assigned by the provider to identify a particular data segment in a hierarchical structure. HL02 (Hierarchical Parent ID Number) is the HL01 value of the parent HL loop. HL03 (Hierarchical Level Code) identifies the hierarchical level (1 – 9). HL04 (Hierarchical Child Code) indicates if there are additional subordinate (or child) HL segments associated with the hierarchical level. Although HL04 is not a mandatory element according to X12 syntax, it is required by ETB. The value of ‘1’ indicates that the hierarchical level has children (additional subordinate HL data segments in the hierarchical structure). The value of ‘0’ indicates that the hierarchical level has no children (no subordinate HL segment in the hierarchical structure). This provides positive confirmation of subordinate HL loops. Summary page charges are provided at HL 4. All charges which are stand-alone (no supporting detail provided) will be grouped together in one HL loop. Each charge which has supporting detail (e.g., itemized calls) will be provided in a separate HL loop. Below and on the next page are examples which illustrate the use of the HL segment in the 811. The HL01 data element always contains the sequential number of the respective HL loop. HL~1~~1~1! HL02 is not provided. This means the information provided does not have a parent

HL loop. HL03 signifies HL 1, the service provider level. HL04 indicates that there is supporting detail at a lower level.

HL~2~1~4~0! HL02 indicates that this information supports and is related to the information

provided in HL loop number 1. HL03 signifies HL 4, the group level. HL04 indicates that there is no supporting detail for the charges at this level. Several IT1 loops can appear under the same HL loop when HL04 = “0”.


provided in HL loop number 1. HL03 signifies HL 4, the group level. HL04 indicates that there is supporting detail at a lower level. When HL04 = “1”, only one IT1 loop will appear within this HL loop.


April 2004 12


provided in HL loop number 3. HL03 signifies HL 5, the Category level. HL04 indicates that there is supporting detail at a lower level.


provided in HL loop number 4. HL03 signifies HL 9, the Line Detail level. HL04 indicates that there is no supporting detail for the charges.

Electronic Commerce Customer Guide 811 Implementation Guide Heading Area

December 2002 13

2 Heading Area

The purpose of the heading area of the 811 is to provide information about the bill being rendered (i.e., account number, type of bill, due date, and tax status of bill), the entity receiving the bill (the trading partner), and the entity providing the bill (SBC operating company).

2.1 Structure Max Segment Segment Description Loop Use O/M ST Transaction Set Header N/A 1 M BIG Beginning Segment for Invoice N/A 1 M NTE Note/Special Instruction N/A 100 O REF Reference Number N/A 3 M ITD Terms of Sale/Due Date N/A 1 O DTM Service From/Through Dates N/A 2 O TXI Tax Exemption information N/A 3 O Loop N1 2 M N1 Name and DUNS Number N1 1 M N3 Address N1 2 O N4 City, State, ZIP N1 1 O REF Reference Number N1 1 O

2.2 Sample Mapping ST~811~000000001! BIG~19990901~314555121299919990901~~~~~DI! REF~EH~773! REF~12~3145551212999! REF~AP~3145551212999! ITD~18~3~~~~19990914! DTM~186~19990901! DTM~187~19990930! TXI~FD~~~~~1~O! N1~PE~SBC! N3~PO BOX 940012! N4~DALLAS~TX~753940012! REF~VR~CRIS! N1~PR~XYZ CORPORATION~1~123456789! N3~PO BOX 2323! N4~HOUSTON~TX~7752022323!

Electronic Commerce Customer Guide 811 Implementation Guide Detail Area

June 2002 14

3 Detail Area The purpose of the detail area of the 811 is to provide information about the services that are being billed for a given account. The activity reflected is either since the last bill, or over a specified period of time (generally specified in the DTM segments in the heading area of the 811). As previously discussed, the 811 is provided in either a summary format or a detail format. For simplicity, a single account is used in discussing the two bill formats. The two summary bill formats will be discussed first and then used as a starting point for the discussion on the detail format.

3.1 Summary 811 A summary 811 should not be confused with the summary area of the 811. A summary 811 provides all charges at a summary level only. As previously discussed, an Accounts Payable 811, a Carrier Summary 811, a CBA Summary 811, or a CABS Summary 811 is provided. The summary 811 formats provide high level account information. The advantages of these formats are a less complex programming effort and lower VAN charges. Summary information is provided within HLs 1 - 4.

3.1.1 Accounts Payable 811 (CRIS billing system only)

The Accounts Payable 811 provides a break out of taxes by jurisdiction and a single charge amount for all current charges. Charges and taxes are not broken out by carrier. This is the smallest and simplest 811 that is provided.

3.1.2 Carrier Summary 811 (CRIS billing system only)

The Carrier Summary 811 provides a break out of charges by carrier. It also provides a break out of taxes by jurisdiction within each carrier. The billing information provided is very similar to the carrier summary pages of a paper bill. While this option does not provide as much information as a Detail 811, it provides more information than the Accounts Payable 811.

3.1.3 Consolidated Billing Account Summary 811 (CRIS billing system only) The Consolidated Billing Account (CBA) Summary 811 provides the bill for the master consolidated account. ‘Memo’ bills are not provided for each of the subordinate accounts.

3.1.4 CABS Summary 811 (CABS billing system only) The CABS Summary 811 provides high level charges. It also provides a break out of taxes by jurisdiction. Note: This format is the only option for CABS accounts that are not Feature Group A or Specials.


June 2002 15

3.1.5 Structure (HL 1)

Max Segment Segment Description Loop Use O/M Loop HL >1 M HL Service Provider - HL 1 HL 1 M Loop HL/LX 1 O LX Sequential Designator HL/LX 1 O SI Class of Service HL/LX 2 O AMT Carrier Totals HL/LX 3 O DTM Activity Dates HL/LX 2 O Loop HL/N1 1 M NM1 Service Provider Code HL/N1 1 M REF Service Provider Numbers HL/N1 2 O PER Inquiry Telephone Numbers HL/N1 2 O TXI Aggregate Taxes HL/N1 10 O Loop HL/ITA 20 O ITA Surcharges/Allowances HL/ITA 1 M

3.1.6 Structure (HL 4) Max Segment Segment Description Loop Use O/M Loop HL >1 M HL Group - HL 4 HL 1 M Loop HL/IT1 >1 M IT1 Summary Charge HL/IT1 1 M PID Charge Explanation HL/IT1 1 O TXI Taxes HL/IT1 3 O DTM Service Dates HL/IT1 2 O Loop HL/IT1/QTY 1 O QTY Number of Lines In Service HL/IT1/QTY 1 O SI Rate State HL/IT1/QTY 1 O Loop HL/IT1/ITA 2 O ITA Surcharges/Allowances HL/IT1/ITA 1 M


June 2003 16

3.1.7 Sample Mappings

Accounts Payable 811 HL~1~~1~1! LX~1! SI~TI~BT~1FB! AMT~SC~4036.95! NM1~SJ~2~SBC Local Services~~~~~42~SBCMO! PER~BI~~TE~3145557333! PER~OC~~TE~3145557300! PER~BI~~UR~WWW.SBC.COM! TXI~FD~92.41~~~~2~A! TXI~LS~280.74~~~~2~A! ITA~C~TI~~06~4.0~~28740~~~~~~~MUS~~A! ITA~C~TI~~06~4.0~~33915~~~~~~~ACF~~O! HL~2~1~4~0! IT1~4.0~1~M4~3376.4~~SV~2050~ZZ~4! CABS Summary 811 HL~1~~1~1! LX~1! SI~TI~BT~OHD! AMT~SC~506.49! NM1~SJ~2~~~~~~91~5170! PER~BI~~TE~3145552545! TXI~LS~6.17~~~~2~A! TXI~FD~5.26~~~~2~A! HL~2~1~4~0! IT1~6~1~M4~484.9~~SV~0700~ZZ~2! TXI~LS~6.17~~~~~O! TXI~FD~5.26~~~~~O! IT1~7~1~M4~9.5~~SV~0300~ZZ~1! TXI~LS~.43~~~~~O! TXI~FD~.23~~~~~O!


June 2003 17

Carrier Summary 811 (SBC operating company plus one carrier) HL~1~~1~1! LX~1! SI~TI~BT~1FB! AMT~SC~4034.97! NM1~SJ~2~SBC Local Services~~~~~42~SBCMO! PER~BI~~TE~3145557333! PER~OC~~TE~3145557300! PER~BI~~UR~WWW.SBC.COM! TXI~FD~92.35~~~~2~A! TXI~LS~280.74~~~~2~A! ITA~C~TI~~06~4.0~~28740~~~~~~~MUS~~A! ITA~C~TI~~06~4.0~~33915~~~~~~~ACF~~O! HL~2~1~4~0! IT1~4.0~1~M4~3371.4~~SV~0200~ZZ~1! TXI~FD~92.15~~~~~O! TXI~LS~280.44~~~~~O! IT1~4.0~1~M4~3.08~~SV~0500~ZZ~2! TXI~FD~.2~~~~~O! TXI~LS~.3~~~~~O! HL~10~~1~1! LX~2! AMT~SC~1.98! NM1~SJ~2~HEARTLINE, INC.~~~~~41~0009! PER~BI~~TE~8005552200! TXI~FD~.06~~~~2~A! HL~11~10~4~0! IT1~7.0~1~M4~1.92~~SV~0500~ZZ~2! TXI~FD~.06~~~~~O!


April 2003 18

3.2 Detail 811 As previously noted, the structure at levels 1 through 4 of the detail 811s is identical to that of the summary 811s. The key difference in the two formats is that the detail 811s provide detail usage and billing information at levels 5 through 9 for many services, such as itemized call usage. In discussing the detail 811s, the information about levels 1 through 4 is repeated, even though it is identical to the summary 811s. After level 4 is discussed, each billing structure that is provided is discussed. In many cases the same billing structure will be used to provide supporting detail for different summary level charges. This should simplify coding efforts on the receiving side of the 811.


April 2003 19

3.2.1 Structure (HL 1)

Max Segment Segment Description Loop Use O/M Loop HL >1 M HL Service Provider - HL 1 HL 1 M Loop HL/LX 1 O LX Sequential Designator HL/LX 1 O SI Class of Service HL/LX 2 O AMT Carrier Totals HL/LX 3 O DTM Activity Dates HL/LX 2 O Loop HL/N1 1 M NM1 Service Provider Code HL/N1 1 M REF Service Provider Numbers HL/N1 2 O PER Inquiry Telephone Numbers HL/N1 2 O TXI Aggregate Taxes HL/N1 10 O Loop HL/ITA 20 O ITA Surcharges/Allowances HL/ITA 1 M

3.2.2 Structure (HL 4) Max Segment Segment Description Loop Use O/M Loop HL >1 M HL Group - HL 4 HL 1 M Loop HL/IT1 >1 M IT1 Summary Charge HL/IT1 1 M PID Charge Explanation HL/IT1 1 O TXI Taxes HL/IT1 3 O DTM Service Dates HL/IT1 2 O Loop HL/IT1/QTY 1 O QTY Number of Lines In Service HL/IT1/QTY 1 O SI Rate State HL/IT1/QTY 1 O Loop HL/IT1/ITA 2 O ITA Surcharges/Allowances HL/IT1/ITA 1 M


June 2003 20

3.2.3 Sample Mapping

HL~1~~1~1! LX~1! SI~TI~BT~1FB! AMT~SC~4034.97! NM1~SJ~2~SBC Local Services~~~~~42~SBCMO! PER~BI~~TE~3145557333! PER~OC~~TE~3145557300! PER~BI~~UR~WWW.SBC.COM! TXI~FD~92.35~~~~2~A! TXI~LS~280.74~~~~2~A! ITA~C~TI~~06~4.0~~28740~~~~~~~MUS~~A! ITA~C~TI~~06~4.0~~33850~~~~~~~ACF~~O! ITA~C~TI~IR~06~4.1~~155~~~~~~~ACH~~O! HL~2~1~4~0! IT1~4.0~1~M4~3371.4~~SV~0200~ZZ~1! TXI~FD~92.15~~~~~O! TXI~LS~280.44~~~~~O! IT1~4.0~1~M4~3.08~~SV~0500~ZZ~2! TXI~FD~.2~~~~~O! TXI~LS~.3~~~~~O!


April 2003 21

3.2.4 Billing Structures (Levels 5 - 9)

Because of the diverse nature of the supporting detail associated with the various services that are billed, several billing structures are necessary. In order to simplify coding efforts on the receiving side of the 811, the same billing structure is used to provide supporting detail for several different services. The supporting detail for a summary level charge can be provided in one or more different formats. This is usually a result of different regulatory bodies requesting the billing detail to be structured according to rigid specifications. An example of this is measured service, which is billed in an itemized call format in some states and in a band summary format in other states. The billing structures (with their associated billing system identified) are described below: Structure 1 - Itemized Calls / Itemized Charges (CRIS Billing System) This structure is used to provide supporting detail on Itemized Calls and Itemized

Charges. Structure 2 - Band Usage (CRIS Billing System) This structure is used to provide supporting detail on services which are billed in a

band summary format. Summary billed measured service usage for example. Structure 3 - WATS Usage (CRIS Billing System) This structure is used to provide WATS supporting detail. Structure 4 - Directory Assistance (CRIS Billing System) This structure is used to provide Directory Assistance (DA) supporting detail. Structure 5 - Other Charges and Credits (Both Billing Systems) This structure is used to provide Other Charges and Credits (OC&C) supporting

detail. Structure 6 - Optional Calling Plan Usage (CRIS Billing System) This structure is used to provide Optional Calling Plan (OCP) supporting detail. OCP

detail is usually provided at HL 8 in support of an itemized call total. Structure 7 - Common Line 800 Usage (CRIS Billing System) This structure is used to provide Common Line 800 (Maximizer) supporting detail. Structure 8 – Customer Service Record (CSR) (Both Billing Systems) This structure is used to provide CSR supporting detail.


April 2003 22

Structure 9 - Feature Group A Information (CABS Billing System) This structure is used to provide Feature Group A (CSR) supporting detail. Structure 10 – Contracts and Discounts (CRIS Billing System) This structure is used to provide Contracts and Discounts supporting detail.


June 2003 23

3.3 Structure 1 - Itemized Calls / Itemized Charges This structure is used to provide supporting detail (by station number) for itemized calls and itemized charges. For Itemized Calls / Itemized Charges, detail is provided for long distance usage (IT107 = “0500”), Measured Service Usage (IT107 = “0705”), MicroLink I Usage (IT107 = “1605”), 976 Usage (IT107 = “1850”), and Itemized Charges (IT107 = “0520”). The structure consists of HL 5, HL 6 (where needed to show the billing party for a particular itemized call), HL 8 (for sub-line item detail when applicable) and HL 9.

3.3.1 Structure Max Segment Segment Description Loop Use O/M Loop HL >1 M HL Category - HL 5 HL 1 M Loop HL/LX 1 M LX Sequential Designator HL/LX 1 M SI Station Number HL/LX 1 M REF Account Number HL/LX >1 O Loop HL/LX/QTY 4 O QTY Quantity of DA Calls HL/LX/QTY 1 M SI Type of DA Calls HL/LX/QTY 1 M Loop HL >1 O HL Category - HL 6 HL 1 O Loop HL/NM1 1 O NM1 Name of Secondary Biller HL/NM1 1 M PER Contact # of Secondary Biller HL/NM1 2 O Loop HL >1 O HL Charge Detail - HL 8 HL 1 O Loop HL/SLN >1 O SLN Subline Item Detail HL/SLN 1 M SI USOC Code HL/SLN 1 O PID Phrase Text HL/SLN 1 O ITA Allowance, Charge, or Service HL/SLN 1 O REF Service Order Number HL/SLN >1 O DTM Date/Time Reference HL/SLN 10 O Loop HL >1 O QTY Qty of Usage HL/SLN/QTY 1 M


June 2003 24

Max Segment Segment Description Loop Use O/M Loop HL >1 M HL Line Detail - HL 9 HL 1 M Loop HL/TCD >1 M TCD Call Information HL/TCD 1 M SI Additional information HL/TCD 2 O TXI Tax status information HL/TCD 1 O ITA Surcharges/Credits HL/TCD 3 O Loop HL/USD >1 M USD Usage Detail HL/USD 1 M SI Additional information HL/USD 2 O


June 2003 25


Long Distance Usage (IT107 = ‘0500’) HL~3~2~5~1! LX~1! SI~TI~TN~3145551212! HL~4~3~9~0! TCD~4.1~19990826~0812~CI~OTTAWA~KS~~~~22~~3.02~~~~I! SI~TI~TM~9135551111~RP~03~SD~IR! TCD~4.2~19990827~2325~CI~OMAHA~NE~CI~DUKE~KS~12~~7.58~~~~I! SI~TI~TM~4025553333~FN~9135559999~RP~05~MT~TN~SD~IR! TXI~ST~~~~~1~O! HL~5~3~6~1! NM1~SJ~2~WORLD COMMUNICATIONS! PER~BI~~TE~8005551212! HL~6~5~9~0! TCD~4.3~19990804~1747~CI~KANSASCITY~MO~~~~15~~6.72~~~~I! SI~TI~TM~8165551111~RP~03~SD~IA! TXI~ST~~~~~1! TCD~4.4~19990822~0808~CI~DUKE~KS~CI~TIDE~KS~5~~7.77~~~~I! SI~TI~TM~9135552222~FN~9135559999~RP~03~MT~CL~SD~IA! Itemized Charges (IT107 = ‘0520’) HL~3~2~5~1! LX~1! REF~11~3145551212! HL~4~3~8~0! SLN~6.0~~I~1~M4~50~~I! SI~TI~CN~01.XXXX.000000..SUV~OC~G01! PID~F~~~~FR ACC LNK 128K! PID~F~~~~1 OF 12 INSTALLMNTS ON $600.00! PID~F~~~~ORD# 123456! REF~OW~123456! DTM~007~20030601! HL~5~2~5~1! LX~2! REF~11~3145551213! HL~6~5~8~0! SLN~6.0~~I~1~M4~75.5~~I! SI~TI~CN~01.XXXX.000000..SUV! PID~F~~~~ FRS 1.536MB ACCESS LINK! DTM~007~20030511! HL~7~2~5~1! LX~3! SI~TI~BN~3145551214999! HL~8~7~8~0! SLN~5.0~~I~1~M4~5.35~I! PID~F~~~~TX INFRASTRU FUND REIMB! DTM~007~20030423!


June 2003 26

HL~9~2~5~1! LX~4! SI~TI~TN~3145551215! HL~15~14~8~0! SLN~5.2~~I~1~M4~.09~~I! PID~F~~~~FEDERAL UNIVERSAL SERVICE FEE! DTM~007~20030410! Measured Service Usage (IT107 = ‘0705’) HL~5~4~8~1. SLN~5.0~~I~1~M4~0~~I~SV~0705. HL~6~5~9~0. USD~O~5.0~~~C0~33~~0. SI~TI~RP~03~BA~A. USD~O~5.0~~~C0~5~~0. SI~TI~RP~04~BA~A. USD~O~5.0~~~C0~1~~0. SI~TI~RP~05~BA~A. HL~7~4~8~1. SLN~5.0~~I~1~M4~0~~I~SV~0705. HL~8~7~9~0. USD~O~5.0~~~AH~5~~0. SI~TI~RP~03~BA~A. HL~9~4~8~1. SLN~5.0~~I~1~M4~.04~~I~SV~0705. HL~10~9~9~0. USD~O~5.0~.04~~C0~1~~.04. SI~TI~RP~03~BA~A. HL~11~4~8~1. SLN~5.0~~I~1~M4~.52~~I~SV~0705. HL~12~11~9~0. USD~O~5.0~.04~~C0~9~~.36. SI~TI~RP~03~BA~A. USD~O~5.0~.032~~C0~1~~.032. SI~TI~RP~04~BA~A. USD~O~5.0~.026~~C0~5~~.13. SI~TI~RP~05~BA~A.


June 2002 27

3.4 Structure 2 - Band Usage This structure is used to provide detail on services which are billed in a band summary format. The band summary format includes charges for Measured Service Band Usage (IT107 = “0705”).This structure consists of HL 5, HL 8 and HL 9.

3.4.1 Structure Max Segment Segment Description Loop Use O/M Loop HL >1 M HL Category - HL 5 HL 1 M Loop HL/LX 1 M LX Sequential Designator HL/LX 1 M SI Station Number HL/LX 1 M Loop HL >1 M HL Charge Detail - HL 8 HL 1 M Loop HL/SLN 1 M SLN Charge information HL/SLN 1 M Loop HL 1 M HL Line Detail - HL 9 HL 1 M Loop HL/USD >1 M USD Usage information HL/USD 1 M SI Usage Characteristics HL/USD 2 O


June 2002 28


HL~3~2~5~1! LX~1! SI~TI~TN~3145551212! HL~4~3~8~1! SLN~5.0~~I~1~M4~11.85~~I~SV~0705! HL~5~4~9~0! USD~O~5.0~.025~~C0~106~~2.65! SI~TI~RP~03~BA~A! USD~O~5.0~.02~~C0~95~~1.9! SI~TI~RP~04~BA~A! USD~O~5.0~.01~~C0~55~~.55! SI~TI~RP~05~BA~A! USD~O~5.0~.02~~AH~146~~2.92! SI~TI~RP~03~BA~A! USD~O~5.0~.015~~AH~140~~2.1! SI~TI~RP~04~BA~A! USD~O~5.0~.005~~AH~96~~.48! SI~TI~RP~05~BA~A! USD~O~5.0~.05~~C0~25~~1.25! SI~TI~RP~03~BA~B! HL~6~2~5~1! LX~2! SI~TI~BN~3145551213! HL~7~6~8~1! SLN~5.0~~I~1~M4~11.25~~I~SV~0705! HL~8~7~9~0! USD~O~5.0~.025~~C0~202~~5.05! SI~TI~RP~03~BA~A! USD~O~5.0~.02~~C0~310~~6.2! SI~TI~RP~04~BA~A!


June 2002 29

3.5 Structure 3 - WATS Usage This structure is used to provide WATS (IT107 = “1000”) supporting detail. Due to the amount and diversity of information being provided, this structure is complex. The Category level (HL 5) contains general information about the WATS number. Under HL 5, up to three billing structures can provide supporting detail for a given WATS number. The first structure provides supporting charge detail; the second structure provides supporting line usage information for each working number under the main WATS number; and the third structure provides supporting itemized call detail for each of the working numbers. Not all WATS accounts will provide all levels of detail, therefore the documentation will discuss each structure individually. A WATS comprehensive mapping example is provided after all the structure tables.

3.5.1 Structure (WATS Line Information) Max Segment Segment Description Loop Use O/M Loop HL >1 M HL Category - HL 5 HL 1 M Loop HL/LX 1 M LX Sequential Designator HL/LX 1 M SI WATS Number HL/LX 1 M


June 2002 30

3.5.2 Structure (WATS Charge Information)

Max Segment Segment Description Loop Use O/M Loop HL >1 M HL Charge Detail - HL 8 HL 1 M Loop HL/SLN 1 M SLN Charge Information HL/SLN 1 M SI Additional Information HL/SLN 1 O ITA Adjustment Information HL/SLN 1 O DTM Rate Change Date HL/SLN 1 O Loop HL/SLN/QTY >1 O QTY Monthly Overflow Count HL/SLN/QTY 1 O Loop HL 1 M HL Line Detail - HL 9 HL 1 M Loop HL/USD >1 M1 USD Charge/Rate Information HL/USD 1 M SI Charge Characteristics HL/USD 2 O TRF Rating factor (MATR) HL/USD 1 O Loop HL/USD/QTY 5 O QTY Quantity HL/USD/QTY 1 M 1 This loop is used to provide both charge information and the taper table.


June 2002 31

3.5.3 Structure (WATS Working Number Usage)

Max Segment Segment Description Loop Use O/M Loop HL >1 M HL Category - HL 5 HL 1 M Loop HL/LX 1 M LX Sequential Designator HL/LX 1 M SI Translated Telephone Number HL/LX 1 M Loop HL/LX/QTY 6 M QTY Quantity Used HL/LX/QTY 1 M SI Rate Period HL/LX/QTY 1 M

3.5.4 Structure (WATS Itemized Call Detail) Max Segment Segment Description Loop Use O/M Loop HL >1 O HL Category - HL 5 HL 1 M Loop HL/LX 1 M LX Sequential Designator HL/LX 1 M SI Station Number HL/LX 1 M Loop HL >1 M HL Line Detail - HL 9 HL 1 M Loop HL/TCD >1 M TCD Call Information HL/TCD 1 M SI Additional Information HL/TCD 2 O TXI Tax Information HL/TCD 1 O ITA Surcharge/Credit HL/TCD 3 O This structure is similar to structure 1.


June 2002 32


HL~3~2~5~1! LX~1! SI~TI~WN~3145551111! HL~4~3~8~1! SLN~7.0~~I~1~M4~675.1~~I~SV~1950~ZZ~2! SI~TI~BA~0~SD~IA! ITA~A~TI~~04~14.0~~-54.32~~~~~~~PMC~~A! QTY~98~53~C0! HL~5~4~9~0! USD~I~7.0~~~HR~23.1~~432.3! SI~TI~RP~03! TRF~AE~MJ~1~C0~1! QTY~99~28.2~HR! QTY~99~756~C0! QTY~AE~20~HR! QTY~94~2~UB! QTY~94~60.2~UF! USD~O~9.0~20~~~~~~0~HR~~25! SI~TI~RP~03! USD~O~9.0~17.5~~~~~~0~HR~25.1~45! SI~TI~RP~03! USD~O~9.0~15~~~~~~0~HR~45.1~60! SI~TI~RP~03! USD~O~9.0~12.5~~~~~0~HR~60.1! SI~TI~RP~03! USD~I~7.0~~~HR~3.42~~242.8~~~~~TI~RP~04! TRF~AE~MJ~1~C0~1! QTY~99~28.2~HR! QTY~99~756~C0! QTY~AE~20~HR! QTY~94~2~UB! QTY~94~60.2~UF! USD~O~9.0~17~~~~~~0~HR~~25! SI~TI~RP~04! USD~O~9.0~14.5~~~~~~0~HR~25.1~45! SI~TI~RP~04! USD~O~9.0~12~~~~~~0~HR~45.1~60! SI~TI~RP~04! USD~O~9.0~9.5~~~~~0~HR~60.1! SI~TI~RP~04! HL~6~3~5~0! LX~2! SI~TI~WN~4095551111~TX~4095552222! QTY~99~10~HR! SI~TI~RP~03! QTY~99~210~C0! SI~TI~RP~03! QTY~99~4.1~HR! SI~TI~RP~04! QTY~99~104~C0! SI~TI~RP~04!


June 2002 33

3.6 Structure 4 - Directory Assistance This structure is used to provide supporting detail for the Directory Assistance charges (IT107 = “0900”).

3.6.1 Structure Max Segment Segment Description Loop Use O/M Loop HL 1 M HL Category - HL 5 HL 1 M Loop HL/LX 1 M LX Sequential Designator HL/LX 1 M SI Billing Number HL/LX 1 M Loop HL 1 M HL Charge Detail - HL 8 HL 1 M Loop HL/SLN >1 M SLN Usage and charge information HL/SLN 1 M SI Type of DA HL/SLN 1 M ITA DA Credits HL/SLN 1 O Loop HL/SLN/QTY 1 O QTY Calls at no charge HL/SLN/QTY 1 M

3.6.2 Sample Mapping HL~7~1~4~1! IT1~3.0~1~M4~1.44~~SV~0900~ZZ~3! HL~8~7~5~1! LX~4! SI~TI~BN~8155551111! HL~9~8~8~0! SLN~3.1~~I~0~C0~.48~~I! SI~TI~DA~10! SLN~3.1~~I~1~C0~0~~I! SI~TI~DA~09! SLN~3.1~~I~3~C0~.48~~I! SI~TI~DA~09!


April 2003 34

3.7 Structure 5 - Other Charges and Credits

This structure is used to provide supporting detail for all other types of OC&C charges (IT107 = “0400”).

3.7.1 Structure

Max Segment Segment Description Loop Use O/M Loop HL 1 M HL Category - HL 5 HL 1 M Loop HL/LX 1 M LX Sequential Designator HL/LX 1 M SI Type of Charge HL/LX 1 O REF Charge Reference Number HL/LX 3 O DTM Completion Date HL/LX 1 O Loop HL/NM1 1 O NM1 Order Contact Information HL/NM1 1 M N3 Street Address HL/NM1 1 O N4 City, State, Zip HL/NM1 1 O Loop HL >1 M HL Sub-Category - HL 6 HL 1 M Loop HL/LX 1 M LX Sequential Designator HL/LX 1 M SI Telephone/Circuit Number HL/LX 1 M Loop HL 1 M HL Charge Detail - HL 8 HL 1 M Loop HL/SLN >1 M SLN Usage and Charge Information HL/SLN 1 M SI Type of Charge HL/SLN 1 M PID Description of Charge HL/SLN 10 O INC Payment Status HL/SLN 1 O TXI Tax Information HL/SLN 3 O REF Charge Reference Number HL/SLN 1 O DTM Service Dates HL/SLN 2 O AMT Monthly Rate HL/SLN 2 O Loop HL/SLN/NM1 >1 O NM1 Carrier Information HL/SLN/NM1 1 M


April 2003 35


HL~2~3~5~1! LX~1! REF~PO~PO23456! DTM~007~19990821! NM1~OB~2~JOE SMITH! HL~3~2~6~1! LX~2! SI~TI~TN~3145551111! HL~4~3~8~0! SLN~6.0~~I~1~M4~111.5~~I! SI~TI~OC~A01! TXI~FT~.17~~~~~O! REF~CT~12345678-1234! DTM~150~19990821! DTM~151~19990830! AMT~AP~242!


October 2002 36

3.8 Structure 6 - Optional Calling Plan Usage

This structure is used to provide supporting detail for optional calling plans. Optional calling plan detail is provided under the itemized call total (IT107 = “0500”), but is distinguished with a SLN loop where SLN10 = “0800”. Optional calling plan detail is provided in one of two formats depending on the type of plan. One format involves a Block of Time Allowance which could include additional calling time being applied against a set rate. The block of time allowance and the actual amount of calling time used will be provided within a SLN loop. If a set rate for additional calling time is included in the plan and the actual amount of calling time is greater than the block of time allowance, the billed amount associated with the additional calling time will be provided within a USD segment. Within the USD segment, USD03 will provide the rate information, USD05 will provide the unit of measure, USD06 will provide the additional calling time and the product of USD03 x USD06 will provide the billed amount in USD08. The second format involves a Percentage Discount being applied to a group of qualifying calls. The billed amount after discount is provided in a SLN loop. The USD loop is always present for this format and provides the billed amount before discount in USD08 and an ITA segment will follow to provide the discount amount.


October 2002 37

3.8.1 Structure

Max Segment Segment Description Loop Use O/M Loop HL 1 M HL Category - HL 5 HL 1 M Loop HL/LX 1 M LX Sequential Designator HL/LX 1 M SI Billing Number HL/LX 1 M Loop HL 1 M HL Charge Detail - HL 8 HL 1 M Loop HL/SLN >1 M SLN Plan Charge Information HL/SLN 1 M SI USOC HL/SLN 2 O PID Description of Calling Plan HL/SLN 1 O Loop HL/SLN/QTY 1 O QTY Plan Time Information HL/SLN/QTY 1 O Loop HL 1 M HL Line Detail - HL 9 HL 1 M Loop HL/USD >1 M USD Usage and Charge Information HL/USD 1 M SI Usage Characteristics HL/USD 2 O ITA Discounts and Credits HL/USD 1 O


October 2002 38


Block of Time with Allowance HL~5~4~5~1! LX~3! SI~TI~TN~3145551111! HL~6~5~8~1! SLN~7.0~~I~1~M4~1.19~~I~SV~0800! SI~TI~SC~OLKBX! PID~F~~~~SWBT 1+SAVER INTRALATA OCP - 60 MIN BLOCK OF! PID~F~~~~TIME AT0D - RES/BUS - INTRASTATE! QTY~92~1~HR! QTY~99~1.18~HR! HL~7~6~9~0! USD~I~7.0~6.6~~HR~.18~~1.19! Percentage Discount HL~9~4~5~1! LX~4! SI~TI~BN~3145551111! HL~10~9~8~1! SLN~3.0~~I~1~M4~1.82~~I~SV~0800! PID~F~~~~SWBT -1+ SAVER -INTRALATA OCP -10% DISCOUNT ATOD! PID~F~~~~BUSINESS –INTRASTATE! HL~11~10~9~0! USD~I~3.0~~~~~~2.02! SI~TI~SC~OS4! ITA~A~TI~~04~3.0~~-20~~~~~~~DSC~~A!


June 2002 39

3.9 Structure 7 - Common Line 800 Usage This structure is used to provide Common Line 800 (IT107 = “1880”) supporting detail. Due to the diversity of information being provided in the service, this structure is very complex. The Category level (HL 5) contains general information about the Common Line 800 number. Under HL 5, up to three sub-billing structures can provide supporting detail for a given Common Line 800 number. The first structure provides a summary of usage for each Point of Billing (POB) number under an 800 number. The second structure provides a summary of usage for the 800 number. The last structure provi des itemized call detail for each POB number under the 800 number. Not all Common Line 800 accounts are provided with this level of detail, therefore the documentation will discuss each structure individually. Accounts with more than one 800 number should note that the Itemized Call Detail structures are provided after all 800 Number Point of Billing Summary and 800 Number Summary structures. A Common Line 800 comprehensive mapping example is provided after all the structure tables.

3.9.1 Non-Postalized Rates: Structure (800 Number Point of Billing Summary)

Max Segment Segment Description Loop Use O/M Loop HL >1 M HL Category - HL 5 HL 1 M Loop HL/LX 1 M LX Sequential Designator HL/LX 1 M SI 800 Number HL/LX 1 M Loop HL >1 M HL Category - HL 6 HL 1 M Loop HL/LX >1 M LX Sequential Designator HL/LX 1 M SI Point of Billing Number HL/LX 1 M PID Plan Name HL/LX 1 O DTM Rate Change Date HL/LX 1 O Loop HL/LX/QTY >1 O QTY Quantity HL/LX/QTY 1 M SI Rate Period HL/LX/QTY 1 M


June 2002 40

Structure (800 Number Point of Billing Summary) - continued Max Segment Segment Description Loop Use O/M Loop HL >1 O HL MATR Application - HL 6 HL 1 M Loop HL/LX >1 O LX Sequential Designator HL/LX 1 M SI Rate Period and USOC HL/LX 1 O PID Plan Name HL/LX 1 O Loop HL >1 O HL MATR - HL 9 HL 1 M Loop HL/USD >1 O USD Charge Information HL/USD 1 M SI Charge Characteristics HL/USD 1 O TRF Rating Factor (MATR) HL/USD 1 O Loop HL/USD/QTY >5 O QTY Quantity HL/USD/QTY 1 M


June 2002 41

3.9.2 Structure (800 Number Summary)

Max Segment Segment Description Loop Use O/M Loop HL >1 M HL Category - HL 5 HL 1 M Loop HL/LX 1 M LX Sequential Designator HL/LX 1 M SI 800 Number HL/LX 1 M Loop HL >1 M HL Usage Summary - HL 8 HL 1 M Loop HL/SLN >1 O SLN Charge Information HL/SLN 1 M SI Rate Change Information HL/SLN 1 O PID Plan Name HL/SLN 1 O DTM Relevant Plan Date HL/SLN 2 O Loop HL/SLN/QTY >1 O QTY Quantity HL/SLN/QTY 1 O Loop HL >1 M HL Detail - HL 9 HL 1 M Loop HL/USD >1 O USD Charge/Rate Information HL/USD 1 M SI Charge/Rate Characteristics HL/USD 1 O QTY Quantity HL/USD/QTY 1 M Loop HL >1 O HL Discounts - HL 8 HL 1 M Loop HL/SLN >1 O SLN Discount Information HL/SLN 1 M PID Plan Name HL/SLN 1 O ITA Discount HL/SLN 1 O


June 2002 42

3.9.3 Structure (Common Line 800 Itemized Call Detail)

Max Segment Segment Description Loop Use O/M Loop HL >1 O HL Category - HL 5 HL 1 M Loop HL/LX 1 M LX Sequential Designator HL/LX 1 M SI Station Number HL/LX 1 M Loop HL >1 M HL Line Detail - HL 9 HL 1 M Loop HL/TCD >1 M TCD Call Information HL/TCD 1 M SI Additional Information HL/TCD 2 O TXI Tax Information HL/TCD 1 O ITA Surcharge/Credit HL/TCD 3 O


June 2002 43

3.9.4 Structure (Common Line 800 – Postalized Rates)

Max Segment Segment Description Loop Use O/M Loop HL >1 M HL Category - HL 5 HL 1 M Loop HL/LX 1 M LX Sequential Designator HL/LX 1 M SI 800 Number HL/LX 1 M Loop HL 1 M HL Category - HL 6 HL 1 M Loop HL/LX 1 M LX Sequential Designator HL/LX 1 M SI Point of Billing Number HL/LX 1 M Loop HL/LX/QTY >1 M QTY Quantity HL/LX/QTY 1 M SI USOC HL/LX/QTY 1 O Loop HL 1 M HL Line Detail - HL 9 HL 1 M Loop HL/TCD >1 M TCD Call Information HL/TCD 1 M SI Additional Information HL/TCD 2 O

Loop HL 1 M HL Discounts - HL 8 HL 1 O Loop HL/SLN 1 M SLN Discount Information HL/SLN 1 M SI USOC HL/SLN 1 O ITA Discount HL/SLN 1 O

Loop HL 1 M HL Detail - HL 9 HL 1 M Loop HL/USD 1 M USD Charge/Rate Information HL/USD 1 M


June 2002 44

3.9.5 Sample Mappings

Common Line 800 – Non-Postalized Rates: HL~11~10~5~1! LX~5! SI~TI~WN~8005551111! HL~12~11~6~0! LX~6! SI~TI~TN~5015552222! PID~F~~~~PER MINUTE PLAN! QTY~99~301.4~MJ! SI~TI~RP~01! QTY~99~232~C0! SI~TI~RP~01! QTY~99~43.7~MJ! SI~TI~RP~02! QTY~99~28~C0! SI~TI~RP~02! HL~13~10~5~1! LX~7! SI~TI~WN~8005553333! HL~14~13~8~1! SLN~7.0~~I~1~M4~60.4~~I~SV~1880! PID~F~~~~PER MINUTE PLAN! HL~15~14~9~0! USD~I~7.0~.2~~MJ~~~60.4! SI~TI~RP~01! QTY~99~302~MJ! HL~16~13~8~1! SLN~7.0~~I~1~M4~7.92~~I~SV~1880! PID~F~~~~PER MINUTE PLAN! HL~17~16~9~0! USD~I~7.0~.18~~MJ~~~7.92! SI~TI~RP~02! QTY~99~44~MJ!

Common Line 800 - Postalized Rates: HL~20~19~5~1! LX~11! SI~TI~WN~8005551111! HL~21~20~6~1! LX~12! SI~TI~TN~5015552222! QTY~94~3.7~MJ! SI~TI~SC~O8ZJ5! QTY~99~1~C0! SI~TI~SC~O8ZJ5! HL~22~21~9~0! TCD~3.0~20010910~1826~~~~CI~OKLACY~~3.7! SI~TI~FN~5015553333!


June 2002 45

HL~23~20~8~1! SLN~3.0~~I~1~M4~.4~~I! SI~TI~SC~O8ZKX! ITA~A~TI~~04~~~-45~~~~~~Total Distance Learning Discount~DSC~~A! HL~24~23~9~0! USD~O~3.0~.1~~MJ~4! HL~25~19~5~1! LX~13! SI~TI~WN~8005554444! HL~26~25~6~1! LX~14! SI~TI~TN~5015556666! QTY~94~3.7~MJ! SI~TI~SC~O8ZJ5! QTY~99~1~C0! SI~TI~SC~O8ZJ5! HL~27~26~9~0! TCD~3.0~20010910~1826~~~~CI~OKLACY~~3.7! SI~TI~FN~5015557777! HL~28~25~6~1! LX~15! SI~TI~TN~5015558888! QTY~94~3.7~MJ! SI~TI~SC~O8ZJ5! QTY~99~1~C0! SI~TI~SC~O8ZJ5! HL~29~28~9~0! TCD~3.0~20010910~1826~~~~CI~OKLACY~~3.7! SI~TI~FN~5015559999! HL~30~25~8~1! SLN~3.0~~I~1~M4~.4~~I! SI~TI~SC~O8ZKX! HL~31~30~9~0! USD~O~3.0~.1~~MJ~4!


June 2002 46

3.10 Structure 8 - Customer Service Record

This structure is used to provide information about CRIS monthly service charges (IT107 = “0200”) or CABS monthly access charges (IT107 = “0300”).

3.10.1 Structure

Max Segment Segment Description Loop Use O/M Loop HL 1 M HL Category - HL 5 HL 1 M Loop HL/LX 1 M LX Sequential Designator HL/LX 1 M SI Telephone/Circuit Number HL/LX 1 M PID Circuit Location Information HL/LX 10 O Loop HL 1 M HL Charge Detail - HL 8 HL 1 M Loop HL/SLN >1 M SLN Charge Information HL/SLN 1 M SI Type of Charge HL/SLN 2 M PID Circuit Location Information HL/SLN 10 O ITA Allowance, Charge or Service HL/SLN 10 O REF Reference Identification HL/SLN >1 O DTM Service Dates HL/SLN 2 O MSG Informational Text HL/SLN >1 O Loop HL/SLN/QTY >1 O QTY Quantity HL/SLN/QTY 1 O Loop HL/SLN/NM1 >1 O NM1 Name and Address Information HL/SLN/NM1 1 M Loop HL 1 M HL Line Detail - HL 9 HL 1 M Loop HL/USD >1 M USD Usage (mileage) information HL/USD 1 M SI Usage Characteristics HL/USD 1 O


June 2002 47


HL~2~3~5~1! LX~1! SI~TI~TN~3145551111! HL~3~2~8~0! SLN~0.1~~I~1~EA~45.5~~I! SI~TI~SC~1FB! DTM~007~19990805! SLN~0.2~~I~2~EA~5.45~~I! SI~TI~SC~4GH! SLN~0.3~~I~1~EA~3.67~~I! SI~TI~SC~R3T!


June 2002 48

3.11 Structure 9 - Feature Group A

This structure is used to provide information about CABS Feature Group A usage charges (IT107 = “0700”). This information is given at a summary level with charges broken down by Recording Number and Office.

3.11.1 Structure

Max Segment Segment Description Loop Use O/M Loop HL 1 M HL Category - HL 5 HL 1 M Loop HL/LX 1 M LX Sequential Designator HL/LX 1 M SI Recording Number/Office HL/LX 1 M Loop HL 1 M HL Charge Detail - HL 8 HL 1 M Loop HL/SLN >1 M SLN Charge Information HL/SLN 1 M

3.11.2 Sample Mapping HL~2~3~5~1! LX~1! SI~TI~TN~3145551111~LO~STLSMO01DSA! HL~3~2~8~0! SLN~54~~I~1~M4~91.97~~I! HL~4~3~5~1! LX~2! SI~TI~TN~3145552222~LO~STLSMO01DSA! HL~5~4~8~0! SLN~55~~I~1~M4~44.56~~I!


June 2002 49

3.12 Structure 10 – Contracts and Discounts

This structure is used to provide supporting detail for Contracts and Discounts (IT107 = “2110”).

3.12.1 Structure

Max Segment Segment Description Loop Use O/M Loop HL 1 M HL Charge Detail - HL 8 HL 1 M Loop HL/SLN >1 M SLN Charge Information HL/SLN 1 M SI Type of Charge HL/SLN 1 M PID Discount Plan Information HL/SLN 2 O DTM Effective Date HL/SLN 1 O


HL~2~3~8~0! SLN~54~~I~1~M4~11.97~~I! SI~TI~OC~H01! PID~F~~~~Reward for ValueLink for bill period June 29,2001! DTM~007~20010805!

Electronic Commerce Customer Guide 811 Implementation Guide Summary Area

June 2002 50

4 Summary Area

The purpose of the summary area of the 811 is to provide a summary of the amount charged for services rendered (TDS segment) and to give an account status (ITA and BAL loops). This area also provides check numbers for the transaction set.

4.1 Structure Max Segment Segment Description Loop Use O/M TDS Charge for Services Rendered N/A 1 M Loop ITA 5 O ITA Refund and Transfer Amounts ITA 1 M Loop BAL 6 M BAL Account Status BAL 1 O Loop N1 >1 O N1 Service Provider N1 1 M BAL Essential (Deniable) Charges N1 1 O Loop N1/ITA 1 O1 ITA Adjustment Amounts N1/ITA 1 M DTM Adjustment Date N1/ITA 1 O CTT Transaction Totals N/A 1 M SE Transaction Set Trailer N/A 1 M 1 This loop is mandatory when the N1 loop is provided.

4.2 Sample Mapping TDS~8482! BAL~P~PB~88.2! BAL~A~NA~-2.05! BAL~M~TP~-85! BAL~A~BT~10! BAL~M~TT~95.97! N1~SJ~SBC Local Services~42~SBCMO! ITA~A~TI~~04~2.0~~-184~~~~~~~AAJ~~O! N1~SJ~AT&T~41~0288! ITA~A~TI~~04~2.0~~-21~~~~~~~AAJ~~O! N1~87~SBC Local Services~42~SBCMO! BAL~M~MD~12.35! CTT~6! SE~67~000000001!

Electronic Commerce Customer Guide 811 Implementation Guide Consolidated 811

October 2002 51

5 Consolidated 811 The Consolidated 811 is very similar to single account 811. The exceptions are noted below: • The Consolidated Billing Account (CBA) number (from the consolidated 811) is

used for payment. Subordinate account information is provided in a Subordinate 811 Invoice (this is also referred to as a “Memo 811”).

• For a Consolidated 811 Invoice, BIG07 may have the value of “CD” (Consolidated

Debit Invoice), “CE” (Consolidated Credit Invoice), “FD” (Consolidated Invoice, Final Bill), “CF” (Consolidated Debit Memo) or “CG” (Consolidated Credit Memo).

• For a Subordinate 811 Invoice, BIG07 may have the value of “DR” (Debit Memo),

“CR” (Credit Memo), “FE” (Memorandum, Final Bill) or “ME” (Memorandum (indicates a zero balance)).

• The ITD segment (to convey terms of sale and the due date) will be produced as

normal for the Consolidated 811 Invoice. It is not provided for the Subordinate 811 invoice.

• DTM segments are not provided for the Consolidated 811 Invoice. The invoice

period dates are provided in the Heading Area of each Subordinate 811 Invoice. • TXI segments depicting the tax exempt status of an account will not be provided in

the Heading Area of the Consolidated 811 Invoice. These segments are provided in the Heading Area of each Subordinate 811 Invoice if needed.

• There will be a REF segment in the Heading Area of the Consolidated 811 Invoice

with REF01 = “12” to provide the Billing Account Number. This is consistent with all other 811 formats provided by the SBC operating companies.

• A Consolidated Billing Account Summary is provided at HL2 of the Consolidated

811 Invoice. § If there is detailed billing information associated with the Consolidated 811 Invoice

itself (late payment charges or other charges, credits and information), a REF segment at HL 2 with REF01 = “14” will uniquely indicate the Consolidated Billing Account (CBA) number. Similarly, a REF segment at HL 2 with REF01 = “11” will indicate a Subordinate Account number within the Consolidated 811 Invoice.

• For each Subordinate 811 Invoice, there will be a REF segment in the Heading

Area with REF01 = “12” to indicate the Subordinate Account number. • The Consolidated 811 Invoice will provide summary information for each

Subordinate 811 Invoice as shown in the structure table that follows. The only three values provided in IT107 are “0110”, “0400”, and “0500”.

Electronic Commerce Customer Guide 811 Implementation Guide Consolidated 811

October 2002 52

5.1 Structure - Consolidated Account Summary Max Segment Segment Description Loop Use O/M Loop HL >1 M HL Billing Arrangement - HL 2 HL 1 M Loop HL/LX 1 M LX Sequential Designator HL/LX 1 M SI Site ID HL/LX 1 O REF Account Number HL/LX 1 M AMT Account Total HL/LX 1 M TXI Tax Information HL/LX 2 O Loop HL/LX/ITA 1 O ITA Account Adjustment HL/LX/ITA 1 M Loop HL 1 M HL Group - HL 4 HL 1 M Loop HL/IT1 >1 M IT1 Summarized Charges HL/IT1 1 M

5.2 Sample Mapping - Consolidated Account Summary HL~2~1~2~1! LX~1! REF~14~314A999999202! TXI~FD~2.56~~~~~O! TXI~LS~1.23~~~~~O! ITA~A~TI~~04~3.0~~-3423~~~~~~~AAJ~~O! HL~3~2~4~0! IT1~3.0~1~M4~23~~SV~0400~ZZ~3! HL~4~1~2~1! LX~2! REF~11~3145551234123! TXI~FD~5.26~~~~~O! TXI~LS~3.33~~~~~O! HL~5~4~4~0! IT1~3.0~1~M4~67.23~~SV~0110~ZZ~1! IT1~3.0~1~M4~34.78~~SV~0400~ZZ~3! IT1~3.0~1~M4~123.87~~SV~0500~ZZ~2!

Electronic Commerce Customer Guide 811 Implementation Guide Auditing the 811

April 2004 53

6 Auditing the 811 To help ensure that both the SBC operating company and the customer are interpreting the charges and credits in the 811 in a consistent manner, the 811 that is sent to customers is audited. The audits performed are detailed in this section. Each transaction set is balanced using the rules outlined in this section before it is sent to the customer. • Please note that the Heading Area does not contain any charge amounts. • The Detail Area contains the current charges. Note that a late payment charge is

considered as a current charge, and as such, the late payment charge will appear in the detail area of the 811.

• The summary area contains total amounts (i.e., total current charges, total payments, total net adjustment, total payments, and total amount due).

This section will convey how to “audit” supporting detail charges to the appropriate summary level charge.

6.1 Rules of Extended Pricing When processing certain segments which contain a quantity and a unit price, the total amount being provided by that segment must be derived. This involves multiplying quantity by unit price to determine the total charge or credit. As is normally the case there is an exception to this rule. If the segment contains a Unit of Measurement Code (DE355) and that data element contains the value “M4” (Monetary Value), then rules of extended pricing do not apply for that segment. This means that when the “M4” value is used, the unit price is the total charge or credit for the segment. The “M4” value is used in the IT1 and SLN segments.

6.2 Determining Segment Amount For ease of reference the term segment amount is used to designate the monetary amount that a segment provides after:

1) Extended pricing rules have been applied. 2) Relational checks have been performed to ensure that the monetary amount is

not being supplied for informational purposes only. Certain segments contain both an amount and a code value identifying whether the amount is a credit or a charge. The ETB 811 Implementation Guide states that within the detail area of the 811, the sign of the amount field will control the monetary value (positive or negative). The code values should be treated as informational only; they have no impact on the sign interpretation. The following pages discuss how to determine the segment amount of each “money” segment.


April 2004 54

6.2.1 BAL Segment

The amount in BAL03 is the segment amount.

6.2.2 IT1 Segment If IT103 = “M4”, then the amount in IT104 is the segment amount. If IT103 ≠ “M4”, then the product of IT102 and IT104 is the segment amount.

6.2.3 ITA Segment The amount in ITA07 is the segment amount. If ITA16 = “O”, then the segment amount is for information purposes only.

6.2.4 SLN Segment If SLN05 = “M4”, then the amount in SLN06 is the segment amount. If SLN05 ≠ “M4”, then the product of SLN04 and SLN06 is the segment amount. If SLN08 = “O”, then the segment amount is for information purposes only.

6.2.5 TXI Segment The amount in TXI02 is the segment amount. If TXI07 = “O”, then the segment amount is for information purposes only. The TXI segment can be used in the heading area to show that an account is exempt from certain types of taxes. It can also be also used in the detail area to show that an itemized call is tax exempt. In each of these uses, TXI07 would equal “O”.

6.2.6 TDS Segment The amount in TDS01 is the segment amount.

6.2.7 TCD Segment The amount in TCD12 is the segment amount. If TCD16 = “O”, then the segment amount is for information purposes only.


April 2004 55

6.2.8 USD Segment

If USD08 is populated, then the amount in USD08 is the segment amount. If USD08 is not populated, then the following determination is made to determine the segment amount: If USD05 = “M4”, then the amount in USD06 is the segment amount. If USD05 ≠ “M4”, then the product of USD03 and USD06 is the segment amount. If USD01 = “O”, then the segment amount is for information purposes only. The USD segment can be used to provide taper table information for WATS billing. In this use, USD01 would equal “O”. Note 1: When both USD03 and USD08 are populated, the amount in USD08 takes

precedence and becomes the segment amount. Note 2: In order to verify amount in USD08, it is necessary to multiply USD03 * USD06

* USD07 * Percent of Interstate Usage. The Percent of Interstate Usage can be found in an SI pair (DE 1000 = ‘PU’) within the SLN loop, when it is present.


April 2004 56

6.3 Auditing the Detail and Summary Area The summing rules that can be used to audit the detail and summary areas of the 811 can be found within the ETB Telephone Billing Guideline at the following website: http://www.atis.org/atis/tcif/edi/tbwg/5tc54hom.htm Select “Guidelines” and view the Issue 9 documents. Section 7 is a Business Model overview which provides the summing rules for balancing the 811 transaction set.


Electronic Commerce Customer Guide 811 Implementation Guide Technical Specifications

April 2004 57

7 Technical Specifications 811 Consolidated Service Invoice/Statement

Functional Group ID=CI Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Consolidated Service Invoice/Statement Transaction Set (811) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set provides for the billing or reporting of complex and structured service invoice/statement detail. This standard can be used by organizations who are interested in sending or receiving either consolidated or standalone invoices for service arrangements which require processing other than that done for the typical product invoice. The Consolidated Service Invoice/Statement can be used as a credit/debit memo to differentiate between payable invoice items and information-only memo items. This transaction set should not be used as a standalone notification of a credit/debit adjustment. Notes: Only the segments and data elements that are provided by our implementation of this transaction set are printed. While we do provide all X12 syntax notes and semantic notes associated with segments we generate in this documentation, notes about unused data elements do not impact our implementation. Please ignore any notes or comments related to data elements that are not provided.


April 2004 58

Heading: Pos. Seg. Req. Loop Notes and No. ID Name Des. Max.Use Repeat Comments M 010 ST Transaction Set Header M 1 M 020 BIG Beginning Segment for Invoice M 1 030 NTE Note/Special Instruction O 100 Not Used 040 CUR Currency O 1 050 REF Reference Identification O >1 Not Used 060 PER Administrative Communications Contact O 3 070 ITD Terms of Sale/Deferred Terms of Sale O 5 080 DTM Date/Time Reference O 10 090 TXI Tax Information O >1 LOOP ID - N1 >1 100 N1 Name O 1 Not Used 110 N2 Additional Name Information O 2 120 N3 Address Information O 2 130 N4 Geographic Location O 1 140 REF Reference Identification O 12 Not Used 150 PER Administrative Communications Contact O 3 Not Used 155 DMG Demographic Information O 1 LOOP ID - FA1 >1 Not Used 170 FA1 Type of Financial Accounting Data O 1 Not Used 180 FA2 Accounting Data M >1


April 2004 59

Detail: Pos. Seg. Req. Loop Notes and No. ID Name Des. Max.Use Repeat Comments

LOOP ID - HL >1 M 010 HL Hierarchical Level M 1 n1 LOOP ID - LX >1 020 LX Assigned Number O 1 Not Used 025 VEH Vehicle Information O 1 030 SI Service Characteristic Identification O 8 040 PID Product/Item Description O 200 Not Used 045 MEA Measurements O 20 050 REF Reference Identification O >1 060 AMT Monetary Amount O 5 070 DTM Date/Time Reference O 8 080 TXI Tax Information O >1 LOOP ID - QTY 10 090 QTY Quantity O 1 100 SI Service Characteristic Identification O 1 LOOP ID - NM1 1 110 NM1 Individual or Organizational Name O 1 n2 Not Used 120 N2 Additional Name Information O 2 130 N3 Address Information O 2 140 N4 Geographic Location O 1 150 REF Reference Identification O 2 160 PER Administrative Communications Contact O >1 170 TXI Tax Information O >1 Not Used 175 DMG Demographic Information O 1 LOOP ID - ITA >1 180 ITA Allowance, Charge or Service O 1 Not Used 190 DTM Date/Time Reference O 1 Not Used 200 TXI Tax Information O >1 LOOP ID - IT1 999999 210 IT1 Baseline Item Data (Invoice) O 1 n3 Not Used 220 SI Service Characteristic Identification O 2 230 PID Product/Item Description O 200 Not Used 235 MEA Measurements O 20 Not Used 240 INC Installment Information O 1 250 TXI Tax Information O >1 Not Used 260 REF Reference Identification O 8 270 DTM Date/Time Reference O 10 Not Used 280 MSG Message Text O >1 Not Used 285 AMT Monetary Amount O 1


April 2004 60

LOOP ID - QTY >1 290 QTY Quantity O 1 300 SI Service Characteristic Identification O 1 LOOP ID - ITA 10 310 ITA Allowance, Charge or Service O 1 Not Used 320 DTM Date/Time Reference O 1 Not Used 330 TXI Tax Information O >1 LOOP ID - NM1 >1 Not Used 340 NM1 Individual or Organizational Name O 1 Not Used 350 N2 Additional Name Information O 2 Not Used 360 N3 Address Information O 2 Not Used 370 N4 Geographic Location O 1 Not Used 380 PER Administrative Communications Contact O 3 Not Used 385 NX2 Location ID Component O >1 n4 Not Used 387 DMG Demographic Information O 1 LOOP ID - SLN >1 390 SLN Subline Item Detail O 1 n5 400 SI Service Characteristic Identification O 2 410 PID Product/Item Description O 200 Not Used 415 MEA Measurements O 20 Not Used 420 CUR Currency O 1 430 INC Installment Information O 1 440 ITA Allowance, Charge or Service O 10 450 TXI Tax Information O >1 460 REF Reference Identification O >1 Not Used 470 PER Administrative Communications Contact O 3 480 DTM Date/Time Reference O 10 490 AMT Monetary Amount O 15 500 MSG Message Text O >1 LOOP ID - QTY >1 510 QTY Quantity O 1 520 SI Service Characteristic Identification O 1 LOOP ID - NM1 >1 530 NM1 Individual or Organizational Name O 1 Not Used 540 N2 Additional Name Information O 2 550 N3 Address Information O 2 560 N4 Geographic Location O 1 Not Used 570 REF Reference Identification O 8 Not Used 580 PER Administrative Communications Contact O 3 Not Used 585 DMG Demographic Information O 1


April 2004 61

LOOP ID - TCD >1 590 TCD Itemized Call Detail O 1 n6 600 SI Service Characteristic Identification O 2 610 TXI Tax Information O >1 615 ITA Allowance, Charge or Service O >1 LOOP ID - QTY >1 Not Used 617 QTY Quantity O 1 Not Used 618 SI Service Characteristic Identification O 1 LOOP ID - USD >1 620 USD Usage Sensitive Detail O 1 n7 625 SI Service Characteristic Identification O 2 630 ITA Allowance, Charge or Service O 2 640 TRF Rating Factors O 18 LOOP ID - QTY >1 650 QTY Quantity O 1 Not Used 660 SI Service Characteristic Identification O 1 LOOP ID - III >1 Not Used 670 III Information O 1 Not Used 680 DTP Date or Time or Period O 5 Not Used 690 AMT Monetary Amount O 5 Not Used 700 PCT Percent Amounts O 5 LOOP ID - LQ >1 Not Used 710 LQ Industry Code O 1 Not Used 720 AMT Monetary Amount O 5 Not Used 730 PCT Percent Amounts O 5 LOOP ID - FA1 >1 Not Used 740 FA1 Type of Financial Accounting Data O 1 Not Used 750 FA2 Accounting Data M >1


April 2004 62

Summary: Pos. Seg. Req. Loop Notes and No. ID Name Des. Max.Use Repeat Comments M 010 TDS Total Monetary Value Summary M 1 LOOP ID - ITA >1 020 ITA Allowance, Charge or Service O 1 030 DTM Date/Time Reference O 1 Not Used 035 REF Reference Identification O 5 LOOP ID - BAL >1 040 BAL Balance Detail O 1 Not Used 050 DTM Date/Time Reference O 1 LOOP ID - N1 >1 060 N1 Name O 1 LOOP ID - BAL >1 070 BAL Balance Detail O 1 Not Used 080 DTM Date/Time Reference O 1 LOOP ID - ITA >1 090 ITA Allowance, Charge or Service O 1 Not Used 100 DTM Date/Time Reference O 2 Not Used 102 AMT Monetary Amount O 1 Not Used 103 SI Service Characteristic Identification O 2 Not Used 105 REF Reference Identification O 5 Not Used 106 CUR Currency O 1 LOOP ID - LX >1 Not Used 107 LX Assigned Number O 1 Not Used 108 REF Reference Identification O 1 LOOP ID - AMT >1 Not Used 109 AMT Monetary Amount O 1 Not Used 110 DTM Date/Time Reference O 1 LOOP ID - ITA >1 Not Used 111 ITA Allowance, Charge or Service O 1 Not Used 112 DTM Date/Time Reference O 1 115 CTT Transaction Totals O 1 n8 M 120 SE Transaction Set Trailer M 1

Transaction Set Notes 1. Valid codes for HL03 to define levels for this transaction set are given below: 1 - Service/Billing

Provider (Identifies the Company Providing the Service/Billing) 2 - Billing Arrangement (Identifies a Specific Billing Arrangement) 3 - Sub-billing Arrangement (Identifies a More Detailed Billing Arrangement) 4 - Group (Identifies a Group of Charges on the Bill) 5 - Category (Identifies the Subdivision of the Group) 6 - Subcategory (Identifies a Further Breakdown of the Category) 7 - Type (Identifies a Further Breakdown of the Subcategory) 8 - Charge Detail (Identifies the Lowest Level of Charges within a Billing Arrangement) 9 - Line Detail (Identifies the Supporting Detail Associated with


April 2004 63

the Charge or Group Level) They must be used in the (hierarchical) order in which they are listed; however, certain levels are optional and may be omitted. At least one occurrence each of the service/billing provider level and group level is required.

2. When used for telecommunications billing, the service/billing provider level is defined by the NM1 loop. 3. The group level is defined by at least one occurrence of the IT1 loop which may only appear at the

group level. 4. The NX2 segment is used to convey parsed address information. 5. The SLN loop may only appear at the charge detail level. 6. The TCD loop may only appear at the line detail level. 7. The USD loop may only appear at the line detail level. 8. The number of line items (CTT01) is the accumulation of the number of IT1 segments.


June 2002 64

Segment: ST Transaction Set Header

Position: 010 Loop: Level: Heading Usage: Mandatory Max Use: 1 Purpose: To indicate the start of a transaction set and to assign a control number Syntax Notes: Semantic Notes: 1 The transaction set identifier (ST01) is used by the translation routines of the

interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).

Comments:

Data Element Summary Ref. Data Des. Element Name Attributes M ST01 143 Transaction Set Identifier Code M ID 3/3 Code uniquely identifying a Transaction Set 811 Consolidated Service Invoice/Statement M ST02 329 Transaction Set Control Number M AN 4/9 Identifying control number that must be unique within the transaction set

functional group assigned by the originator for a transaction set


June 2002 65

Segment: BIG Beginning Segment for Invoice

Position: 020 Loop: Level: Heading Usage: Mandatory Max Use: 1 Purpose: To indicate the beginning of an invoice transaction set and transmit identifying

numbers and dates Syntax Notes: Semantic Notes: 1 BIG01 is the invoice issue date. 2 BIG03 is the date assigned by the purchaser to purchase order. 3 BIG10 indicates the consolidated invoice number. When BIG07 contains code

CI, BIG10 is not used. Comments: 1 BIG07 is used only to further define the type of invoice when needed.

Data Element Summary Ref. Data Des. Element Name Attributes M BIG01 373 Date M DT 8/8 Date expressed as CCYYMMDD M BIG02 76 Invoice Number M AN 1/22 Identifying number assigned by issuer Not Used BIG03 373 Date O DT 8/8 Date expressed as CCYYMMDD Not Used BIG04 324 Purchase Order Number O AN 1/22 Identifying number for Purchase Order assigned by the orderer/purchaser Not Used BIG05 328 Release Number O AN 1/30 Number identifying a release against a Purchase Order previously placed

by the parties involved in the transaction Not Used BIG06 327 Change Order Sequence Number O AN 1/8 Number assigned by the orderer identifying a specific change or revision

to a previously transmitted transaction set


June 2002 66

BIG07 640 Transaction Type Code O ID 2/2 Code specifying the type of transaction CD Consolidated Debit Invoice CE Consolidated Credit Invoice CF Consolidated Debit Memo CG Consolidated Credit Memo CN Credit Invoice CR Credit Memo DI Debit Invoice DR Debit Memo FB Final Bill FD Consolidated Invoice, Final Bill FE Memorandum, Final Bill ME Memorandum Not Used BIG08 353 Transaction Set Purpose Code O ID 2/2 Code identifying purpose of transaction set Not Used BIG09 306 Action Code O ID 1/2 Code indicating type of action Not Used BIG10 76 Invoice Number O AN 1/22 Identifying number assigned by issuer


June 2002 67

Segment: NTE Note/Special Instruction

Position: 030 Loop: Level: Heading Usage: Optional Max Use: 100 Purpose: To transmit information in a free-form format, if necessary, for comment or special

instruction Syntax Notes: Semantic Notes: Comments: 1 The NTE segment permits free-form information/data which, under ANSI X12

standard implementations, is not machine processable. The use of the NTE segment should therefore be avoided, if at all possible, in an automated environment.

Notes: This segment only provided to CheckFree.

Data Element Summary Ref. Data Des. Element Name Attributes NTE01 363 Note Reference Code O ID 3/3 Code identifying the functional area or purpose for which the note applies INV Invoice Instruction M NTE02 352 Description M AN 1/80 A free-form description to clarify the related data elements and their

content


June 2002 68

Segment: REF Reference Identification

Position: 050 Loop: Level: Heading Usage: Optional Max Use: >1 Purpose: To specify identifying information Syntax Notes: 1 At least one of REF02 or REF03 is required. 2 If either C04003 or C04004 is present, then the other is required. 3 If either C04005 or C04006 is present, then the other is required. Semantic Notes: 1 REF04 contains data relating to the value cited in REF02. Comments:

Data Element Summary Ref. Data Des. Element Name Attributes M REF01 128 Reference Identification Qualifier M ID 2/3 Code qualifying the Reference Identification 12 Billing Account 14 Master Account Number 6R Provider Control Number AP Accounts Receivable Number EH Financial Classification Code REF02 127 Reference Identification X AN 1/30 Reference information as defined for a particular Transaction Set or as

specified by the Reference Identification Qualifier Not Used REF03 352 Description X AN 1/80 A free-form description to clarify the related data elements and their

content Not Used REF04 C040 Reference Identifier O To identify one or more reference numbers or identification numbers as

specified by the Reference Qualifier Not Used C04001 128 Reference Identification Qualifier M ID 2/3 Code qualifying the Reference Identification Not Used C04002 127 Reference Identification M AN 1/30 Reference information as defined for a particular Transaction Set or as

specified by the Reference Identification Qualifier


June 2002 69

Not Used C04003 128 Reference Identification Qualifier X ID 2/3 Code qualifying the Reference Identification Not Used C04004 127 Reference Identification X AN 1/30 Reference information as defined for a particular Transaction Set or as

specified by the Reference Identification Qualifier Not Used C04005 128 Reference Identification Qualifier X ID 2/3 Code qualifying the Reference Identification Not Used C04006 127 Reference Identification X AN 1/30 Reference information as defined for a particular Transaction Set or as



October 2002 70

Segment: ITD Terms of Sale/Deferred Terms of Sale

Position: 070 Loop: Level: Heading Usage: Optional Max Use: 5 Purpose: To specify terms of sale Syntax Notes: 1 If ITD03 is present, then at least one of ITD04 ITD05 or ITD13 is required. 2 If ITD08 is present, then at least one of ITD04 ITD05 or ITD13 is required. 3 If ITD09 is present, then at least one of ITD10 or ITD11 is required. Semantic Notes: 1 ITD15 is the percentage applied to a base amount used to determine a late

payment charge. Comments: 1 If the code in ITD01 is "04", then ITD07 or ITD09 is required and either ITD10 or

ITD11 is required; if the code in ITD01 is "05", then ITD06 or ITD07 is required.

Data Element Summary Ref. Data Des. Element Name Attributes ITD01 336 Terms Type Code O ID 2/2 Code identifying type of payment terms 03 Fixed Date 10 Instant 18 Fixed Date, Late Payment Penalty Applies ITD02 333 Terms Basis Date Code O ID 1/2 Code identifying the beginning of the terms period 3 Invoice Date 5 Invoice Receipt Date Not Used ITD03 338 Terms Discount Percent O R 1/6 Terms discount percentage, expressed as a percent, available to the

purchaser if an invoice is paid on or before the Terms Discount Due Date Not Used ITD04 370 Terms Discount Due Date X DT 8/8 Date payment is due if discount is to be earned expressed in format

CCYYMMDD Not Used ITD05 351 Terms Discount Days Due X N0 1/3 Number of days in the terms discount period by which payment is due if

terms discount is earned


October 2002 71

ITD06 446 Terms Net Due Date O DT 8/8 Date when total invoice amount becomes due expressed in format

CCYYMMDD Not Used ITD07 386 Terms Net Days O N0 1/3 Number of days until total invoice amount is due (discount not applicable) Not Used ITD08 362 Terms Discount Amount O N2 1/10 Total amount of terms discount Not Used ITD09 388 Terms Deferred Due Date O DT 8/8 Date deferred payment or percent of invoice payable is due expressed in

format CCYYMMDD Not Used ITD10 389 Deferred Amount Due X N2 1/10 Deferred amount due for payment Not Used ITD11 342 Percent of Invoice Payable X R 1/5 Amount of invoice payable expressed in percent Not Used ITD12 352 Description O AN 1/80 A free-form description to clarify the related data elements and their

content Not Used ITD13 765 Day of Month X N0 1/2 The numeric value of the day of the month between 1 and the maximum

day of the month being referenced ITD14 107 Payment Method Code O ID 1/2 Code identifying type of payment procedures AC Credit Card E Electronic Payment System Not Used ITD15 954 Percent O R 1/10 Percentage expressed as a decimal Late Payment Percentage.


June 2002 72

Segment: DTM Date/Time Reference

Position: 080 Loop: Level: Heading Usage: Optional Max Use: 10 Purpose: To specify pertinent dates and times Syntax Notes: 1 At least one of DTM02 DTM03 or DTM05 is required. 2 If DTM04 is present, then DTM03 is required. 3 If either DTM05 or DTM06 is present, then the other is required. Semantic Notes: Comments:

Data Element Summary Ref. Data Des. Element Name Attributes M DTM01 374 Date/Time Qualifier M ID 3/3 Code specifying type of date or time, or both date and time 186 Invoice Period Start 187 Invoice Period End DTM02 373 Date X DT 8/8 Date expressed as CCYYMMDD Not Used DTM03 337 Time X TM 4/8 Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS,

or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

Not Used DTM04 623 Time Code O ID 2/2 Code identifying the time. In accordance with International Standards

Organization standard 8601, time can be specified by a + or - and an indication in hours in relation to Universal Time Coordinate (UTC) time; since + is a restricted character, + and - are substituted by P and M in the codes that follow

Not Used DTM05 1250 Date Time Period Format Qualifier X ID 2/3 Code indicating the date format, time format, or date and time format Not Used DTM06 1251 Date Time Period X AN 1/35 Expression of a date, a time, or range of dates, times or dates and times


June 2002 73

Segment: TXI Tax Information

Position: 090 Loop: Level: Heading Usage: Optional Max Use: >1 Purpose: To specify tax information Syntax Notes: 1 At least one of TXI02 TXI03 or TXI06 is required. 2 If either TXI04 or TXI05 is present, then the other is required. 3 If TXI08 is present, then TXI03 is required. Semantic Notes: 1 TXI02 is the monetary amount of the tax. 2 TXI03 is the tax percent expressed as a decimal. 3 TXI07 is a code indicating the relationship of the price or amount to the

associated segment. Comments:

Data Element Summary Ref. Data Des. Element Name Attributes M TXI01 963 Tax Type Code M ID 2/2 Code specifying the type of tax FT Federal Excise Tax LS State and Local Sales Tax MP Municipal Tax Not Used TXI02 782 Monetary Amount X R 1/18 Monetary amount Not Used TXI03 954 Percent X R 1/10 Percentage expressed as a decimal Not Used TXI04 955 Tax Jurisdiction Code Qualifier X ID 2/2 Code identifying the source of the data used in tax jurisdiction code Not Used TXI05 956 Tax Jurisdiction Code X AN 1/10 Code identifying the taxing jurisdiction TXI06 441 Tax Exempt Code X ID 1/1 Code identifying exemption status from sales and use tax 1 Yes (Tax Exempt) TXI07 662 Relationship Code O ID 1/1 Code indicating the relationship between entities O Information Only


June 2002 74

Not Used TXI08 828 Dollar Basis For Percent O R 1/9 Dollar basis to be used in the percent calculation of the allowance,

charge or tax Not Used TXI09 325 Tax Identification Number O AN 1/20 Number assigned to a purchaser (buyer, orderer) by a taxing jurisdiction

(state, county, etc.); often called a tax exemption number or certificate number

Not Used TXI10 350 Assigned Identification O AN 1/20 Alphanumeric characters assigned for differentiation within a transaction

set


June 2002 75

Segment: N1 Name

Position: 100 Loop: N1 Optional Level: Heading Usage: Optional Max Use: 1 Purpose: To identify a party by type of organization, name, and code Syntax Notes: 1 At least one of N102 or N103 is required. 2 If either N103 or N104 is present, then the other is required. Semantic Notes: Comments: 1 This segment, used alone, provides the most efficient method of providing

organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.

2 N105 and N106 further define the type of entity in N101.

Data Element Summary Ref. Data Des. Element Name Attributes M N101 98 Entity Identifier Code M ID 2/3 Code identifying an organizational entity, a physical location, property or

an individual PE Payee PR Payer N102 93 Name X AN 1/60 Free-form name N103 66 Identification Code Qualifier X ID 1/2 Code designating the system/method of code structure used for

Identification Code (67) 1 D-U-N-S Number, Dun & Bradstreet 91 Assigned by Seller or Seller's Agent N104 67 Identification Code X AN 2/80 Code identifying a party or other code Not Used N105 706 Entity Relationship Code O ID 2/2 Code describing entity relationship Not Used N106 98 Entity Identifier Code O ID 2/3 Code identifying an organizational entity, a physical location, property or

an individual


June 2002 76

Segment: N3 Address Information

Position: 120 Loop: N1 Optional Level: Heading Usage: Optional Max Use: 2 Purpose: To specify the location of the named party Syntax Notes: Semantic Notes: Comments:

Data Element Summary Ref. Data Des. Element Name Attributes M N301 166 Address Information M AN 1/55 Address information N302 166 Address Information O AN 1/55 Address information


June 2002 77

Segment: N4 Geographic Location

Position: 130 Loop: N1 Optional Level: Heading Usage: Optional Max Use: 1 Purpose: To specify the geographic place of the named party Syntax Notes: 1 If N406 is present, then N405 is required. Semantic Notes: Comments: 1 A combination of either N401 through N404, or N405 and N406 may be

adequate to specify a location. 2 N402 is required only if city name (N401) is in the U.S. or Canada.

Data Element Summary Ref. Data Des. Element Name Attributes N401 19 City Name O AN 2/30 Free-form text for city name N402 156 State or Province Code O ID 2/2 Code (Standard State/Province) as defined by appropriate government

agency N403 116 Postal Code O ID 3/15 Code defining international postal zone code excluding punctuation and

blanks (zip code for United States) Not Used N404 26 Country Code O ID 2/3 Code identifying the country Not Used N405 309 Location Qualifier X ID 1/2 Code identifying type of location Not Used N406 310 Location Identifier O AN 1/30 Code which identifies a specific location


June 2002 78


Position: 140 Loop: N1 Optional Level: Heading Usage: Optional Max Use: 12 Purpose: To specify identifying information Syntax Notes: 1 At least one of REF02 or REF03 is required. 2 If either C04003 or C04004 is present, then the other is required. 3 If either C04005 or C04006 is present, then the other is required. Semantic Notes: 1 REF04 contains data relating to the value cited in REF02. Comments:

Data Element Summary Ref. Data Des. Element Name Attributes M REF01 128 Reference Identification Qualifier M ID 2/3 Code qualifying the Reference Identification VR Vendor ID Number REF02 127 Reference Identification X AN 1/30 Reference information as defined for a particular Transaction Set or as

specified by the Reference Identification Qualifier CABS Customer Access Billing System Bill CRIS Customer Records Information System Bill Not Used REF03 352 Description X AN 1/80 A free-form description to clarify the related data elements and their





June 2002 79





June 2002 80

Segment: HL Hierarchical Level

Position: 010 Loop: HL Mandatory Level: Detail Usage: Mandatory Max Use: 1 Purpose: To identify dependencies among and the content of hierarchically related groups of

data segments Syntax Notes: Semantic Notes: Comments: 1 The HL segment is used to identify levels of detail information using a

hierarchical structure, such as relating line-item data to shipment data, and packaging data to line-item data.

The HL segment defines a top-down/left-right ordered structure. 2 HL01 shall contain a unique alphanumeric number for each occurrence of the

HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.

3 HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.

4 HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.

5 HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.

Data Element Summary Ref. Data Des. Element Name Attributes M HL01 628 Hierarchical ID Number M AN 1/12 A unique number assigned by the sender to identify a particular data

segment in a hierarchical structure HL02 734 Hierarchical Parent ID Number O AN 1/12 Identification number of the next higher hierarchical data segment that the

data segment being described is subordinate to


June 2002 81

M HL03 735 Hierarchical Level Code M ID 1/2 Code defining the characteristic of a level in a hierarchical structure 1 Service/Billing Provider 2 Billing Arrangement 4 Group 5 Category 6 Sub-Category 8 Charge Detail 9 Line Detail HL04 736 Hierarchical Child Code O ID 1/1 Code indicating if there are hierarchical child data segments subordinate

to the level being described 0 No Subordinate HL Segment in This Hierarchical

Structure. 1 Additional Subordinate HL Data Segment in This

Hierarchical Structure.


June 2002 82

Segment: LX Assigned Number

Position: 020 Loop: LX Optional Level: Detail Usage: Optional Max Use: 1 Purpose: To reference a line number in a transaction set Syntax Notes: Semantic Notes: Comments:

Data Element Summary Ref. Data Des. Element Name Attributes M LX01 554 Assigned Number M N0 1/6 Number assigned for differentiation within a transaction set


June 2002 83

Segment: SI Service Characteristic Identification

Position: 030 Loop: LX Optional Level: Detail Usage: Optional Max Use: 8 Purpose: To specify service characteristic data Syntax Notes: 1 If either SI04 or SI05 is present, then the other is required. 2 If either SI06 or SI07 is present, then the other is required. 3 If either SI08 or SI09 is present, then the other is required. 4 If either SI10 or SI11 is present, then the other is required. 5 If either SI12 or SI13 is present, then the other is required. 6 If either SI14 or SI15 is present, then the other is required. 7 If either SI16 or SI17 is present, then the other is required. 8 If either SI18 or SI19 is present, then the other is required. 9 If either SI20 or SI21 is present, then the other is required. Semantic Notes: Comments: 1 SI01 defines the source for each of the service characteristics qualifiers.

Notes: The SI segment actually contains 21 data elements. SI01 provides an Agency Qualifier Code and the other 20 data elements are matched pairs, which will be referred to SI02/SI03 pairs. Each matched pair provides DE-1000 and DE-234 codes/values. There can be up to ten pairs on each SI segment.

Data Element Summary

Ref. Data Des. Element Name Attributes M SI01 559 Agency Qualifier Code M ID 2/2 Code identifying the agency assigning the code values TI Telecommunications Industry M SI02 1000 Service Characteristics Qualifier M AN 2/2 Code from an industry code list qualifying the type of service

characteristics One or more of the following DE1000 values and it’s associated DE234

value may be present within the SI segment. CH Charge/Usage Status Code RP Rate Period SP Special Billing/Payment Commitment Plan M SI03 234 Product/Service ID M AN 1/48 Identifying number for a product or service For a list of valid DE234 values associated with the preceeding DE1000

values, see 10.4 Additional Code Lists Used by ETB within the ETB Telephone Billing Guideline at the following website: http://www.atis.org/atis/tcif/edi/tbwg/5tc54hom.htm



June 2002 84

SI04 1000 Service Characteristics Qualifier X AN 2/2 Code from an industry code list qualifying the type of service


value may be present within the SI segment. BN Billing Telephone Number BT Basic Service Type CC Calling Card Number CI Circuit Drop Location Code CN Circuit Number DI Department Code FC Facility Complement Code FI Facility Interface Code LO Local Exchange Carrier Serving Office PU Percent of Interstate Usage SG Service Group SI Circuit Number Special ID TK Trunk Number TN Telephone Number TX Translated Telephone Number WN Wide Area Telephone Service (WATS) Line Number SI05 234 Product/Service ID X AN 1/48 Identifying number for a product or service This element will contain a locally defined code associated with one of

the preceeding DE1000 values. Examples of a locally defined value include a telephone number, Class of Service USOC, calling card number,circuit number, etc.


characteristics SI07 234 Product/Service ID X AN 1/48 Identifying number for a product or service SI08 1000 Service Characteristics Qualifier X AN 2/2 Code from an industry code list qualifying the type of service

characteristics SI09 234 Product/Service ID X AN 1/48 Identifying number for a product or service


June 2002 85









June 2002 86

Segment: PID Product/Item Description

Position: 040 Loop: LX Optional Level: Detail Usage: Optional Max Use: 200 Purpose: To describe a product or process in coded or free-form format Syntax Notes: 1 If PID04 is present, then PID03 is required. 2 At least one of PID04 or PID05 is required. 3 If PID07 is present, then PID03 is required. 4 If PID08 is present, then PID04 is required. 5 If PID09 is present, then PID05 is required. Semantic Notes: 1 Use PID03 to indicate the organization that publishes the code list being

referred to. 2 PID04 should be used for industry-specific product description codes. 3 PID08 describes the physical characteristics of the product identified in PID04.

A "Y" indicates that the specified attribute applies to this item; an "N" indicates it does not apply. Any other value is indeterminate.

4 PID09 is used to identify the language being used in PID05. Comments: 1 If PID01 equals "F", then PID05 is used. If PID01 equals "S", then PID04 is

used. If PID01 equals "X", then both PID04 and PID05 are used. 2 Use PID06 when necessary to refer to the product surface or layer being

described in the segment. 3 PID07 specifies the individual code list of the agency specified in PID03.

Data Element Summary Ref. Data Des. Element Name Attributes M PID01 349 Item Description Type M ID 1/1 Code indicating the format of a description F Free-form X Semi-structured (Code and Text) Not Used PID02 750 Product/Process Characteristic Code O ID 2/3 Code identifying the general class of a product or process characteristic PID03 559 Agency Qualifier Code X ID 2/2 Code identifying the agency assigning the code values AS Assigned by Seller PID04 751 Product Description Code X AN 1/12 A code from an industry code list which provides specific data about a

product characteristic CI Circuit Drop Location DP Different Premises Address


June 2002 87

PID05 352 Description X AN 1/80 A free-form description to clarify the related data elements and their

content Not Used PID06 752 Surface/Layer/Position Code O ID 2/2 Code indicating the product surface, layer or position that is being

described Not Used PID07 822 Source Subqualifier O AN 1/15 A reference that indicates the table or text maintained by the Source

Qualifier Not Used PID08 1073 Yes/No Condition or Response Code O ID 1/1 Code indicating a Yes or No condition or response Not Used PID09 819 Language Code O ID 2/3 Code designating the language used in text, from a standard code list

maintained by the International Standards Organization (ISO 639)


June 2002 88


Position: 050 Loop: LX Optional Level: Detail Usage: Optional Max Use: >1 Purpose: To specify identifying information Syntax Notes: 1 At least one of REF02 or REF03 is required. 2 If either C04003 or C04004 is present, then the other is required. 3 If either C04005 or C04006 is present, then the other is required. Semantic Notes: 1 REF04 contains data relating to the value cited in REF02. Comments:

Data Element Summary Ref. Data Des. Element Name Attributes M REF01 128 Reference Identification Qualifier M ID 2/3 Code qualifying the Reference Identification 11 Account Number 14 Master Account Number CR Customer Reference Number IV Seller's Invoice Number OW Service Order Number PO Purchase Order Number TF Transfer Number VN Vendor Order Number REF02 127 Reference Identification X AN 1/30 Reference information as defined for a particular Transaction Set or as

specified by the Reference Identification Qualifier EDI999 Default vendor number Not Used REF03 352 Description X AN 1/80 A free-form description to clarify the related data elements and their


specified by the Reference Qualifier


June 2002 89

Not Used C04001 128 Reference Identification Qualifier M ID 2/3 Code qualifying the Reference Identification Not Used C04002 127 Reference Identification M AN 1/30 Reference information as defined for a particular Transaction Set or as





June 2002 90

Segment: AMT Monetary Amount

Position: 060 Loop: LX Optional Level: Detail Usage: Optional Max Use: 5 Purpose: To indicate the total monetary amount Syntax Notes: Semantic Notes: Comments:

Data Element Summary Ref. Data Des. Element Name Attributes M AMT01 522 Amount Qualifier Code M ID 1/3 Code to qualify amount 5 Total Invoice Amount (for Consolidated Bills only) KO Committed Amount PB Billed Amount SC Total Service Charge (for a Service Provider) M AMT02 782 Monetary Amount M R 1/18 Monetary amount Not Used AMT03 478 Credit/Debit Flag Code O ID 1/1 Code indicating whether amount is a credit or debit


June 2002 91


Position: 070 Loop: LX Optional Level: Detail Usage: Optional Max Use: 8 Purpose: To specify pertinent dates and times Syntax Notes: 1 At least one of DTM02 DTM03 or DTM05 is required. 2 If DTM04 is present, then DTM03 is required. 3 If either DTM05 or DTM06 is present, then the other is required. Semantic Notes: Comments:

Data Element Summary Ref. Data Des. Element Name Attributes M DTM01 374 Date/Time Qualifier M ID 3/3 Code specifying type of date or time, or both date and time 007 Effective 193 Period Start 194 Period End DTM02 373 Date X DT 8/8 Date expressed as CCYYMMDD Not Used DTM03 337 Time X TM 4/8 Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS,






June 2002 92


Position: 080 Loop: LX Optional Level: Detail Usage: Optional Max Use: >1 Purpose: To specify tax information Syntax Notes: 1 At least one of TXI02 TXI03 or TXI06 is required. 2 If either TXI04 or TXI05 is present, then the other is required. 3 If TXI08 is present, then TXI03 is required. Semantic Notes: 1 TXI02 is the monetary amount of the tax. 2 TXI03 is the tax percent expressed as a decimal. 3 TXI07 is a code indicating the relationship of the price or amount to the


Notes: Utilized in Consolidated Bill mapping.

Data Element Summary Ref. Data Des. Element Name Attributes M TXI01 963 Tax Type Code M ID 2/2 Code specifying the type of tax FT Federal Excise Tax LS State and Local Sales Tax TXI02 782 Monetary Amount X R 1/18 Monetary amount Not Used TXI03 954 Percent X R 1/10 Percentage expressed as a decimal Not Used TXI04 955 Tax Jurisdiction Code Qualifier X ID 2/2 Code identifying the source of the data used in tax jurisdiction code Not Used TXI05 956 Tax Jurisdiction Code X AN 1/10 Code identifying the taxing jurisdiction Not Used TXI06 441 Tax Exempt Code X ID 1/1 Code identifying exemption status from sales and use tax TXI07 662 Relationship Code O ID 1/1 Code indicating the relationship between entities A Add O Information Only


June 2002 93





set


June 2002 94

Segment: QTY Quantity

Position: 090 Loop: QTY Optional Level: Detail Usage: Optional Max Use: 1 Purpose: To specify quantity information Syntax Notes: 1 At least one of QTY02 or QTY04 is required. 2 Only one of QTY02 or QTY04 may be present. Semantic Notes: 1 QTY04 is used when the quantity is non-numeric. Comments:

Data Element Summary Ref. Data Des. Element Name Attributes M QTY01 673 Quantity Qualifier M ID 2/2 Code specifying the type of quantity 94 Billable Quantity 99 Quantity Used QTY02 380 Quantity X R 1/15 Numeric value of quantity QTY03 C001 Composite Unit of Measure O To identify a composite unit of measure M C00101 355 Unit or Basis for Measurement Code M ID 2/2 Code specifying the units in which a value is being expressed, or manner

in which a measurement has been taken C0 Calls (Messages) HR Hours MJ Minutes Not Used C00102 1018 Exponent O R 1/15 Power to which a unit is raised Not Used C00103 649 Multiplier O R 1/10 Value to be used as a multiplier to obtain a new value Not Used C00104 355 Unit or Basis for Measurement Code O ID 2/2 Code specifying the units in which a value is being expressed, or manner

in which a measurement has been taken


June 2002 95

Not Used C00105 1018 Exponent O R 1/15 Power to which a unit is raised Not Used C00106 649 Multiplier O R 1/10 Value to be used as a multiplier to obtain a new value Not Used C00107 355 Unit or Basis for Measurement Code O ID 2/2 Code specifying the units in which a value is being expressed, or manner

in which a measurement has been taken Not Used C00108 1018 Exponent O R 1/15 Power to which a unit is raised Not Used C00109 649 Multiplier O R 1/10 Value to be used as a multiplier to obtain a new value Not Used C00110 355 Unit or Basis for Measurement Code O ID 2/2 Code specifying the units in which a value is being expressed, or manner


in which a measurement has been taken Not Used C00114 1018 Exponent O R 1/15 Power to which a unit is raised Not Used C00115 649 Multiplier O R 1/10 Value to be used as a multiplier to obtain a new value Not Used QTY04 61 Free-Form Message X AN 1/30 Free-form information


June 2002 96


Position: 100 Loop: QTY Optional Level: Detail Usage: Optional Max Use: 1 Purpose: To specify service characteristic data Syntax Notes: 1 If either SI04 or SI05 is present, then the other is required. 2 If either SI06 or SI07 is present, then the other is required. 3 If either SI08 or SI09 is present, then the other is required. 4 If either SI10 or SI11 is present, then the other is required. 5 If either SI12 or SI13 is present, then the other is required. 6 If either SI14 or SI15 is present, then the other is required. 7 If either SI16 or SI17 is present, then the other is required. 8 If either SI18 or SI19 is present, then the other is required. 9 If either SI20 or SI21 is present, then the other is required. Semantic Notes: Comments: 1 SI01 defines the source for each of the service characteristics qualifiers.





value may be present within the SI segment. DA Directory Assistance RP Rate Period ST Message Service Type M SI03 234 Product/Service ID M AN 1/48 Identifying number for a product or service For a list of valid DE234 values associated with the preceeding DE1000




June 2002 97



value may be present within the SI segment. SC Service Category Code TL To/Terminating Location TM To/Terminating Station Telephone Number SI05 234 Product/Service ID X AN 1/48 Identifying number for a product or service This element will contain a locally defined code associated with one of

the preceeding DE1000 values. Examples of a locally defined value include a USOC, telephone number, etc.







June 2002 98

Not Used SI14 1000 Service Characteristics Qualifier X AN 2/2 Code from an industry code list qualifying the type of service

characteristics Not Used SI15 234 Product/Service ID X AN 1/48 Identifying number for a product or service Not Used SI16 1000 Service Characteristics Qualifier X AN 2/2 Code from an industry code list qualifying the type of service



characteristics Not Used SI21 234 Product/Service ID X AN 1/48 Identifying number for a product or service


August 2003 99

Segment: NM1 Individual or Organizational Name

Position: 110 Loop: NM1 Optional Level: Detail Usage: Optional Max Use: 1 Purpose: To supply the full name of an individual or organizational entity Syntax Notes: 1 If either NM108 or NM109 is present, then the other is required. 2 If NM111 is present, then NM110 is required. Semantic Notes: 1 NM102 qualifies NM103. Comments: 1 NM110 and NM111 further define the type of entity in NM101.

Data Element Summary Ref. Data Des. Element Name Attributes M NM101 98 Entity Identifier Code M ID 2/3 Code identifying an organizational entity, a physical location, property or

an individual 9D New Service Provider EN End User OB Ordered By SJ Service Provider M NM102 1065 Entity Type Qualifier M ID 1/1 Code qualifying the type of entity 1 Person 2 Non-Person Entity 3 Unknown NM103 1035 Name Last or Organization Name O AN 1/35 Individual last name or organizational name Not Used NM104 1036 Name First O AN 1/25 Individual first name Not Used NM105 1037 Name Middle O AN 1/25 Individual middle name or initial Not Used NM106 1038 Name Prefix O AN 1/10 Prefix to individual name Not Used NM107 1039 Name Suffix O AN 1/10 Suffix to individual name


August 2003 100

NM108 66 Identification Code Qualifier X ID 1/2 Code designating the system/method of code structure used for

Identification Code (67) 41 Telecommunications Carrier Identification Code 42 Telecommunications Pseudo Carrier Identification

Code 91 Assigned by Seller or Seller’s Agent NM109 67 Identification Code X AN 2/80 Code identifying a party or other code Not Used NM110 706 Entity Relationship Code X ID 2/2 Code describing entity relationship Not Used NM111 98 Entity Identifier Code O ID 2/3 Code identifying an organizational entity, a physical location, property or

an individual


June 2002 101

Segment: N3 Address Information

Position: 130 Loop: NM1 Optional Level: Detail Usage: Optional Max Use: 2 Purpose: To specify the location of the named party Syntax Notes: Semantic Notes: Comments:



June 2002 102

Segment: N4 Geographic Location

Position: 140 Loop: NM1 Optional Level: Detail Usage: Optional Max Use: 1 Purpose: To specify the geographic place of the named party Syntax Notes: 1 If N406 is present, then N405 is required. Semantic Notes: Comments: 1 A combination of either N401 through N404, or N405 and N406 may be


Data Element Summary Ref. Data Des. Element Name Attributes N401 19 City Name O AN 2/30 Free-form text for city name N402 156 State or Province Code O ID 2/2 Code (Standard State/Province) as defined by appropriate government

agency N403 116 Postal Code O ID 3/15 Code defining international postal zone code excluding punctuation and

blanks (zip code for United States) Not Used N404 26 Country Code O ID 2/3 Code identifying the country Not Used N405 309 Location Qualifier X ID 1/2 Code identifying type of location Not Used N406 310 Location Identifier O AN 1/30 Code which identifies a specific location


June 2002 103


Position: 150 Loop: NM1 Optional Level: Detail Usage: Optional Max Use: 2 Purpose: To specify identifying information Syntax Notes: 1 At least one of REF02 or REF03 is required. 2 If either C04003 or C04004 is present, then the other is required. 3 If either C04005 or C04006 is present, then the other is required. Semantic Notes: 1 REF04 contains data relating to the value cited in REF02. Comments:

Data Element Summary Ref. Data Des. Element Name Attributes M REF01 128 Reference Identification Qualifier M ID 2/3 Code qualifying the Reference Identification 6R Provider Control Number CR Customer Reference Number IV Seller's Invoice Number REF02 127 Reference Identification X AN 1/30 Reference information as defined for a particular Transaction Set or as






June 2002 104





June 2002 105

Segment: PER Administrative Communications Contact

Position: 160 Loop: NM1 Optional Level: Detail Usage: Optional Max Use: >1 Purpose: To identify a person or office to whom administrative communications should be

directed Syntax Notes: 1 If either PER03 or PER04 is present, then the other is required. 2 If either PER05 or PER06 is present, then the other is required. 3 If either PER07 or PER08 is present, then the other is required. Semantic Notes: Comments:

Data Element Summary Ref. Data Des. Element Name Attributes M PER01 366 Contact Function Code M ID 2/2 Code identifying the major duty or responsibility of the person or group

named BI Bill Inquiry Contact IC Information Contact MA Maintenance Contact OC Order Contact PER02 93 Name O AN 1/60 Free-form name PER03 365 Communication Number Qualifier X ID 2/2 Code identifying the type of communication number TE Telephone UR Uniform Resource Locator (URL) PER04 364 Communication Number X AN 1/80 Complete communications number including country or area code when

applicable Not Used PER05 365 Communication Number Qualifier X ID 2/2 Code identifying the type of communication number Not Used PER06 364 Communication Number X AN 1/80 Complete communications number including country or area code when

applicable


June 2002 106

Not Used PER07 365 Communication Number Qualifier X ID 2/2 Code identifying the type of communication number Not Used PER08 364 Communication Number X AN 1/80 Complete communications number including country or area code when

applicable Not Used PER09 443 Contact Inquiry Reference O AN 1/20 Additional reference number or description to clarify a contact number


June 2002 107


Position: 170 Loop: NM1 Optional Level: Detail Usage: Optional Max Use: >1 Purpose: To specify tax information Syntax Notes: 1 At least one of TXI02 TXI03 or TXI06 is required. 2 If either TXI04 or TXI05 is present, then the other is required. 3 If TXI08 is present, then TXI03 is required. Semantic Notes: 1 TXI02 is the monetary amount of the tax. 2 TXI03 is the tax percent expressed as a decimal. 3 TXI07 is a code indicating the relationship of the price or amount to the


Data Element Summary Ref. Data Des. Element Name Attributes M TXI01 963 Tax Type Code M ID 2/2 Code specifying the type of tax CP County/Parish Sales Tax CS City Sales Tax FT Federal Excise Tax GR Gross Receipts Tax LO Local Tax (Not Sales Tax) LS State and Local Sales Tax LT Local Sales Tax (All Applicable Sales Taxes by

Taxing Authority Below the State Level) MP Municipal Tax OT Occupational Tax SE State Excise Tax ST State Sales Tax SU Sales and Use Tax TD Telecommunications Device for the Deaf (TDD)

Service Excise Tax TT Telecommunications Tax ZB 911-County Tax ZC 911-Excise Tax ZD 911-State Tax ZE 911-Tax ZZ Mutually Defined


June 2002 108

TXI02 782 Monetary Amount X R 1/18 Monetary amount Not Used TXI03 954 Percent X R 1/10 Percentage expressed as a decimal Not Used TXI04 955 Tax Jurisdiction Code Qualifier X ID 2/2 Code identifying the source of the data used in tax jurisdiction code Not Used TXI05 956 Tax Jurisdiction Code X AN 1/10 Code identifying the taxing jurisdiction Not Used TXI06 441 Tax Exempt Code X ID 1/1 Code identifying exemption status from sales and use tax TXI07 662 Relationship Code O ID 1/1 Code indicating the relationship between entities A Add O Information Only Not Used TXI08 828 Dollar Basis For Percent O R 1/9 Dollar basis to be used in the percent calculation of the allowance,



TXI10 350 Assigned Identification O AN 1/20 Alphanumeric characters assigned for differentiation within a transaction

set


April 2003 109

Segment: ITA Allowance, Charge or Service

Position: 180 Loop: ITA Optional Level: Detail Usage: Optional Max Use: 1 Purpose: To specify allowances, charges, or services Syntax Notes: 1 If ITA02 is present, then at least one of ITA03 ITA13 or ITA14 is required. 2 If ITA08 is present, then ITA09 is required. 3 If either ITA10 or ITA11 is present, then the other is required. 4 If ITA15 is present, then ITA02 is required. 5 If ITA17 is present, then ITA12 is required. Semantic Notes: 1 ITA09 is the allowance or charge percent. 2 ITA10 is the quantity basis when the allowance or charge quantity is different

from the purchase order or invoice quantity. 3 ITA12 is the quantity of free goods. Comments: 1 If ITA01 equals "A" - allowance or "C" - charge, then at least one of ITA06,

ITA07, or ITA08 must be present. 2 ITA02 identifies the source of the code value in ITA03 or ITA15. 3 If ITA07 is present with either ITA06 or ITA08, then ITA07 takes precedence. 4 ITA13 is used to clarify the allowance, charge, or service. 5 ITA15 specifies the individual code list of the agency specified in ITA02. 6 ITA16 describes the relationship of ITA06, ITA07 or ITA09 to an associated

segment.

Data Element Summary Ref. Data Des. Element Name Attributes M ITA01 248 Allowance or Charge Indicator M ID 1/1 Code which indicates an allowance or charge for the service specified A Allowance C Charge ITA02 559 Agency Qualifier Code X ID 2/2 Code identifying the agency assigning the code values TI Telecommunications Industry


April 2003 110

ITA03 560 Special Services Code X ID 2/10 Code identifying the special service CA City CY County FD Federal FS Federal & State IR Interstate

LO Local MP Municipal SL State & Local ST State TOL Toll Charge M ITA04 331 Allowance or Charge Method of Handling Code M ID 2/2 Code indicating method of handling for an allowance or charge 04 Credit Customer Account 06 Charge to be Paid by Customer ITA05 341 Allowance or Charge Number O AN 1/16 The number assigned by a vendor referencing an allowance, promotion,

deal or charge Not Used ITA06 359 Allowance or Charge Rate O R 1/15 Allowance or Charge Rate per Unit ITA07 360 Allowance or Charge Total Amount O N2 1/15 Total dollar amount for the allowance or charge ITA08 378 Allowance/Charge Percent Qualifier O ID 1/1 Code indicating on what basis allowance or charge percent is calculated 9 Late Payment Charge Base Amount ITA09 332 Percent X R 1/6 Percent expressed as a percent ITA10 380 Quantity X R 1/15 Numeric value of quantity ITA11 355 Unit or Basis for Measurement Code X ID 2/2 Code specifying the units in which a value is being expressed, or manner

in which a measurement has been taken M4 Monetary Value


April 2003 111

Not Used ITA12 380 Quantity X R 1/15 Numeric value of quantity ITA13 352 Description X AN 1/80 A free-form description to clarify the related data elements and their

content ITA14 150 Special Charge or Allowance Code X ID 3/3 Code identifying type of special charge or allowance AAJ Adjustments ACF Access Charge - Federal ACH Access Charges

ANB Adjustment for Minimum Charges Billing DDS Deaf and Disabled Surcharge DSC Discount ECL Expanded Local Calling Surcharge ESC Emergency Service FFA Franchise Fee FUS Federal Universal Service GRS Gross Receipts Surcharge LAE One-Time License Fee LNP Long Term Number Portability Surcharge LPC Late payment charge LSS Lifeline Surcharge MSG Miscellaneous Charge MUS Municipal Surcharge NPF No PIC federal charge PAD Premium Charge PCC Poison Control Surcharge REE Regulatory Fee ROW Rights of Way Use Fee SAP Service Assistance Program Surcharge SER Service Charge SMS State/Metropolitan Transit Authority Surcharge STC State Surcharge SUR Surcharge

SUS State Universal Service Surcharge VAB Volume Discount ZZZ Mutually Defined


April 2003 112

Not Used ITA15 822 Source Subqualifier O AN 1/15 A reference that indicates the table or text maintained by the Source

Qualifier ITA16 662 Relationship Code O ID 1/1 Code indicating the relationship between entities A Add O Information Only Not Used ITA17 355 Unit or Basis for Measurement Code O ID 2/2 Code specifying the units in which a value is being expressed, or manner



October 2002 113

Segment: IT1 Baseline Item Data (Invoice)

Position: 210 Loop: IT1 Optional Level: Detail Usage: Optional Max Use: 1 Purpose: To specify the basic and most frequently used line item data for the invoice and

related transactions Syntax Notes: 1 If any of IT102 IT103 or IT104 is present, then all are required. 2 If either IT106 or IT107 is present, then the other is required. 3 If either IT108 or IT109 is present, then the other is required. 4 If either IT110 or IT111 is present, then the other is required. 5 If either IT112 or IT113 is present, then the other is required. 6 If either IT114 or IT115 is present, then the other is required. 7 If either IT116 or IT117 is present, then the other is required. 8 If either IT118 or IT119 is present, then the other is required. 9 If either IT120 or IT121 is present, then the other is required. 10 If either IT122 or IT123 is present, then the other is required. 11 If either IT124 or IT125 is present, then the other is required. Semantic Notes: 1 IT101 is the purchase order line item identification. Comments: 1 Element 235/234 combinations should be interpreted to include products

and/or services. See the Data Dictionary for a complete list of IDs. 2 IT106 through IT125 provide for ten different product/service IDs for each item.

For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.

Notes: The group level is defined by at least one occurrence of the IT1 loop which may only appear at the group level.


Ref. Data Des. Element Name Attributes IT101 350 Assigned Identification O AN 1/20 Alphanumeric characters assigned for differentiation within a transaction

set IT102 358 Quantity Invoiced X R 1/10 Number of units invoiced (supplier units) IT103 355 Unit or Basis for Measurement Code X ID 2/2 Code specifying the units in which a value is being expressed, or manner

in which a measurement has been taken When IT103 = "M4" - Rules of extended pricing do not apply. M4 Monetary Value


October 2002 114

IT104 212 Unit Price X R 1/17 Price per unit of product, service, commodity, etc. Not Used IT105 639 Basis of Unit Price Code O ID 2/2 Code identifying the type of unit price for an item IT106 235 Product/Service ID Qualifier X ID 2/2 Code identifying the type/source of the descriptive number used in

Product/Service ID (234) SV Service Rendered IT107 234 Product/Service ID X AN 1/48 Identifying number for a product or service 0110 Recurring (Consolidated Bills Only) 0200 Monthly Service Charge 0300 Access 0400 OIther Charges and Credits 0500 Itemized Calls 0520 Itemized Charges/Credits 0600 Directory Advertising 0700 Usage 0705 Measured Service 0900 Directory Assistance 1000 WATS 1460 Customer Owned Pay Telephone 1605 Packet Switching (MicroLink) 1650 Video Services 1830 Extended Area 1850 976 1870 Additional Calls 1880 800 Common Line 1990 Other Line Charge (Reserve Line) 2050 Total Amount Billed (for Summary/Consolidated

Billing Only) 2110 Contracts/Discounts


October 2002 115

IT108 235 Product/Service ID Qualifier X ID 2/2 Code identifying the type/source of the descriptive number used in

Product/Service ID (234) ZZ Mutually Defined Used in place of Telecom Service Type - WJ IT109 234 Product/Service ID X AN 1/48 Identifying number for a product or service 1 Recurring Charge 2 Other Charges 3 Usage 4 Summary/Combined Charges Not Used IT110 235 Product/Service ID Qualifier X ID 2/2 Code identifying the type/source of the descriptive number used in

Product/Service ID (234) Not Used IT111 234 Product/Service ID X AN 1/48 Identifying number for a product or service Not Used IT112 235 Product/Service ID Qualifier X ID 2/2 Code identifying the type/source of the descriptive number used in



Product/Service ID (234) Not Used IT117 234 Product/Service ID X AN 1/48 Identifying number for a product or service


October 2002 116

Not Used IT118 235 Product/Service ID Qualifier X ID 2/2 Code identifying the type/source of the descriptive number used in




Product/Service ID (234) Not Used IT125 234 Product/Service ID X AN 1/48 Identifying number for a product or service


June 2002 117


Position: 230 Loop: IT1 Optional Level: Detail Usage: Optional Max Use: 200 Purpose: To describe a product or process in coded or free-form format Syntax Notes: 1 If PID04 is present, then PID03 is required. 2 At least one of PID04 or PID05 is required. 3 If PID07 is present, then PID03 is required. 4 If PID08 is present, then PID04 is required. 5 If PID09 is present, then PID05 is required. Semantic Notes: 1 Use PID03 to indicate the organization that publishes the code list being






Data Element Summary Ref. Data Des. Element Name Attributes M PID01 349 Item Description Type M ID 1/1 Code indicating the format of a description F Free-form Not Used PID02 750 Product/Process Characteristic Code O ID 2/3 Code identifying the general class of a product or process characteristic Not Used PID03 559 Agency Qualifier Code X ID 2/2 Code identifying the agency assigning the code values Not Used PID04 751 Product Description Code X AN 1/12 A code from an industry code list which provides specific data about a

product characteristic


June 2002 118







June 2002 119


Position: 250 Loop: IT1 Optional Level: Detail Usage: Optional Max Use: >1 Purpose: To specify tax information Syntax Notes: 1 At least one of TXI02 TXI03 or TXI06 is required. 2 If either TXI04 or TXI05 is present, then the other is required. 3 If TXI08 is present, then TXI03 is required. Semantic Notes: 1 TXI02 is the monetary amount of the tax. 2 TXI03 is the tax percent expressed as a decimal. 3 TXI07 is a code indicating the relationship of the price or amount to the


Data Element Summary Ref. Data Des. Element Name Attributes M TXI01 963 Tax Type Code M ID 2/2 Code specifying the type of tax FT Federal Excise Tax LS State and Local Sales Tax TXI02 782 Monetary Amount X R 1/18 Monetary amount Not Used TXI03 954 Percent X R 1/10 Percentage expressed as a decimal Not Used TXI04 955 Tax Jurisdiction Code Qualifier X ID 2/2 Code identifying the source of the data used in tax jurisdiction code Not Used TXI05 956 Tax Jurisdiction Code X AN 1/10 Code identifying the taxing jurisdiction Not Used TXI06 441 Tax Exempt Code X ID 1/1 Code identifying exemption status from sales and use tax TXI07 662 Relationship Code O ID 1/1 Code indicating the relationship between entities O Information Only


June 2002 120





set


June 2002 121


Position: 270 Loop: IT1 Optional Level: Detail Usage: Optional Max Use: 10 Purpose: To specify pertinent dates and times Syntax Notes: 1 At least one of DTM02 DTM03 or DTM05 is required. 2 If DTM04 is present, then DTM03 is required. 3 If either DTM05 or DTM06 is present, then the other is required. Semantic Notes: Comments:

Data Element Summary Ref. Data Des. Element Name Attributes M DTM01 374 Date/Time Qualifier M ID 3/3 Code specifying type of date or time, or both date and time 150 Service Period Start 151 Service Period End DTM02 373 Date X DT 8/8 Date expressed as CCYYMMDD Not Used DTM03 337 Time X TM 4/8 Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS,






June 2002 122



Data Element Summary Ref. Data Des. Element Name Attributes M QTY01 673 Quantity Qualifier M ID 2/2 Code specifying the type of quantity 94 Billable Quantity 99 Quantity Used QTY02 380 Quantity X R 1/15 Numeric value of quantity QTY03 C001 Composite Unit of Measure O To identify a composite unit of measure M C00101 355 Unit or Basis for Measurement Code M ID 2/2 Code specifying the units in which a value is being expressed, or manner

in which a measurement has been taken C0 Calls (Messages) T0 Telecommunications Lines in Service Not Used C00102 1018 Exponent O R 1/15 Power to which a unit is raised Not Used C00103 649 Multiplier O R 1/10 Value to be used as a multiplier to obtain a new value Not Used C00104 355 Unit or Basis for Measurement Code O ID 2/2 Code specifying the units in which a value is being expressed, or manner

in which a measurement has been taken Not Used C00105 1018 Exponent O R 1/15 Power to which a unit is raised


June 2002 123

Not Used C00106 649 Multiplier O R 1/10 Value to be used as a multiplier to obtain a new value Not Used C00107 355 Unit or Basis for Measurement Code O ID 2/2 Code specifying the units in which a value is being expressed, or manner





June 2002 124






characteristics RT Rate State M SI03 234 Product/Service ID M AN 1/48 Identifying number for a product or service This element will contain a locally defined code associated with one of

the preceeding DE1000 values. Examples of a locally defined value include a state used as basis for rate calculation.


June 2002 125









June 2002 126






October 2003 127


Position: 310 Loop: ITA Optional Level: Detail Usage: Optional Max Use: 1 Purpose: To specify allowances, charges, or services Syntax Notes: 1 If ITA02 is present, then at least one of ITA03 ITA13 or ITA14 is required. 2 If ITA08 is present, then ITA09 is required. 3 If either ITA10 or ITA11 is present, then the other is required. 4 If ITA15 is present, then ITA02 is required. 5 If ITA17 is present, then ITA12 is required. Semantic Notes: 1 ITA09 is the allowance or charge percent. 2 ITA10 is the quantity basis when the allowance or charge quantity is different



segment.

Data Element Summary Ref. Data Des. Element Name Attributes M ITA01 248 Allowance or Charge Indicator M ID 1/1 Code which indicates an allowance or charge for the service specified A Allowance C Charge ITA02 559 Agency Qualifier Code X ID 2/2 Code identifying the agency assigning the code values TI Telecommunications Industry ITA03 560 Special Services Code X ID 2/10 Code identifying the special service TOL Toll Charge M ITA04 331 Allowance or Charge Method of Handling Code M ID 2/2 Code indicating method of handling for an allowance or charge 04 Credit Customer Account 06 Charge to be Paid by Customer


October 2003 128

ITA05 341 Allowance or Charge Number O AN 1/16 The number assigned by a vendor referencing an allowance, promotion,

deal or charge Not Used ITA06 359 Allowance or Charge Rate O R 1/15 Allowance or Charge Rate per Unit ITA07 360 Allowance or Charge Total Amount O N2 1/15 Total dollar amount for the allowance or charge Not Used ITA08 378 Allowance/Charge Percent Qualifier O ID 1/1 Code indicating on what basis allowance or charge percent is calculated Not Used ITA09 332 Percent X R 1/6 Percent expressed as a percent Not Used ITA10 380 Quantity X R 1/15 Numeric value of quantity Not Used ITA11 355 Unit or Basis for Measurement Code X ID 2/2 Code specifying the units in which a value is being expressed, or manner

in which a measurement has been taken Not Used ITA12 380 Quantity X R 1/15 Numeric value of quantity ITA13 352 Description X AN 1/80 A free-form description to clarify the related data elements and their

content ITA14 150 Special Charge or Allowance Code X ID 3/3 Code identifying type of special charge or allowance CCR Concession Credit DSC Discount ECL Expanded Local Calling Surcharge

SUR Surcharge Not Used ITA15 822 Source Subqualifier O AN 1/15 A reference that indicates the table or text maintained by the Source

Qualifier


October 2003 129

ITA16 662 Relationship Code O ID 1/1 Code indicating the relationship between entities A Add I Included O Information Only Not Used ITA17 355 Unit or Basis for Measurement Code O ID 2/2 Code specifying the units in which a value is being expressed, or manner



October 2002 130

Segment: SLN Subline Item Detail

Position: 390 Loop: SLN Optional Level: Detail Usage: Optional Max Use: 1 Purpose: To specify product subline detail item data Syntax Notes: 1 If either SLN04 or SLN05 is present, then the other is required. 2 If SLN07 is present, then SLN06 is required. 3 If SLN08 is present, then SLN06 is required. 4 If either SLN09 or SLN10 is present, then the other is required. 5 If either SLN11 or SLN12 is present, then the other is required. 6 If either SLN13 or SLN14 is present, then the other is required. 7 If either SLN15 or SLN16 is present, then the other is required. 8 If either SLN17 or SLN18 is present, then the other is required. 9 If either SLN19 or SLN20 is present, then the other is required. 10 If either SLN21 or SLN22 is present, then the other is required. 11 If either SLN23 or SLN24 is present, then the other is required. 12 If either SLN25 or SLN26 is present, then the other is required. 13 If either SLN27 or SLN28 is present, then the other is required. Semantic Notes: 1 SLN01 is the identifying number for the subline item. 2 SLN02 is the identifying number for the subline level. The subline level is

analogous to the level code used in a bill of materials. 3 SLN03 is the configuration code indicating the relationship of the subline item

to the baseline item. 4 SLN08 is a code indicating the relationship of the price or amount to the

associated segment. Comments: 1 See the Data Element Dictionary for a complete list of IDs. 2 SLN01 is related to (but not necessarily equivalent to) the baseline item

number. Example: 1.1 or 1A might be used as a subline number to relate to baseline number 1.

3 SLN09 through SLN28 provide for ten different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.

Notes: The SLN loop may only appear at the charge detail level.

Data Element Summary Ref. Data Des. Element Name Attributes M SLN01 350 Assigned Identification M AN 1/20 Alphanumeric characters assigned for differentiation within a transaction

set Not Used SLN02 350 Assigned Identification O AN 1/20 Alphanumeric characters assigned for differentiation within a transaction

set


October 2002 131

M SLN03 662 Relationship Code M ID 1/1 Code indicating the relationship between entities I Included SLN04 380 Quantity X R 1/15 Numeric value of quantity SLN05 C001 Composite Unit of Measure X To identify a composite unit of measure M C00101 355 Unit or Basis for Measurement Code M ID 2/2 Code specifying the units in which a value is being expressed, or manner

in which a measurement has been taken C0 Calls (Messages) EA Each M4 Monetary Value Not Used C00102 1018 Exponent O R 1/15 Power to which a unit is raised Not Used C00103 649 Multiplier O R 1/10 Value to be used as a multiplier to obtain a new value Not Used C00104 355 Unit or Basis for Measurement Code O ID 2/2 Code specifying the units in which a value is being expressed, or manner


in which a measurement has been taken Not Used C00108 1018 Exponent O R 1/15 Power to which a unit is raised Not Used C00109 649 Multiplier O R 1/10 Value to be used as a multiplier to obtain a new value


October 2002 132

Not Used C00110 355 Unit or Basis for Measurement Code O ID 2/2 Code specifying the units in which a value is being expressed, or manner


in which a measurement has been taken Not Used C00114 1018 Exponent O R 1/15 Power to which a unit is raised Not Used C00115 649 Multiplier O R 1/10 Value to be used as a multiplier to obtain a new value SLN06 212 Unit Price X R 1/17 Price per unit of product, service, commodity, etc. Not Used SLN07 639 Basis of Unit Price Code O ID 2/2 Code identifying the type of unit price for an item SLN08 662 Relationship Code O ID 1/1 Code indicating the relationship between entities I Included O Information Only SLN09 235 Product/Service ID Qualifier X ID 2/2 Code identifying the type/source of the descriptive number used in

Product/Service ID (234) SV Service Rendered


October 2002 133

SLN10 234 Product/Service ID X AN 1/48 Identifying number for a product or service 0205 Basic Service 0225 Mileage Charge 0305 Service and Equipment Information

0705 Measured Service 0800 Optional Call Plan/Discount Plan 0900 Directory Assistance 1400 Other Voice Services 1460 Customer Owned Pay Telephone 1610 Electronic Mail/Messaging Service

1740 Miscellaneous 1820 Voice Mail

1880 800 Common Line 1950 InWATS/800 Service 1960 OutWATS 1990 Other Line Charge 2110 Contracts/Discounts Not Used SLN11 235 Product/Service ID Qualifier X ID 2/2 Code identifying the type/source of the descriptive number used in

Product/Service ID (234) Not Used SLN12 234 Product/Service ID X AN 1/48 Identifying number for a product or service Not Used SLN13 235 Product/Service ID Qualifier X ID 2/2 Code identifying the type/source of the descriptive number used in


Product/Service ID (234) Not Used SLN16 234 Product/Service ID X AN 1/48 Identifying number for a product or service


October 2002 134

Not Used SLN17 235 Product/Service ID Qualifier X ID 2/2 Code identifying the type/source of the descriptive number used in






Product/Service ID (234) Not Used SLN28 234 Product/Service ID X AN 1/48 Identifying number for a product or service


February 2004 135


Position: 400 Loop: SLN Optional Level: Detail Usage: Optional Max Use: 2 Purpose: To specify service characteristic data Syntax Notes: 1 If either SI04 or SI05 is present, then the other is required. 2 If either SI06 or SI07 is present, then the other is required. 3 If either SI08 or SI09 is present, then the other is required. 4 If either SI10 or SI11 is present, then the other is required. 5 If either SI12 or SI13 is present, then the other is required. 6 If either SI14 or SI15 is present, then the other is required. 7 If either SI16 or SI17 is present, then the other is required. 8 If either SI18 or SI19 is present, then the other is required. 9 If either SI20 or SI21 is present, then the other is required. Semantic Notes: Comments: 1 SI01 defines the source for each of the service characteristics qualifiers.



Ref. Data Des. Element Name Attributes M SI01 559 Agency Qualifier Code M ID 2/2 Code identifying the agency assigning the code values TI Telecommunications Industry


February 2004 136

M SI02 1000 Service Characteristics Qualifier M AN 2/2 Code from an industry code list qualifying the type of service


value may be present within the SI segment. CH Charge/Usage Status Code DA Directory Assistance IA Service Disconnect/Interruption Indicator MP Meet Point Billing OC Other Charges and Credits Category Code RY Local/Toll Indicator SA Service Activity Code SD Settlement Code SP Special Billing/Payment Commitment Plan ST Message Service Type TS Type of Signaling M SI03 234 Product/Service ID M AN 1/48 Identifying number for a product or service For a list of valid DE234 values associated with the preceeding DE1000




February 2004 137



value may be present within the SI segment. BA Band CI Circuit Drop Location Code CN Circuit Number

CT Common Language Segment Number (SFN) CU Channel Pair Number D7 Multiple Data Mounting Address Code DT Dialed Telephone Number FX Pricing Flex Band LO Local Exchange Carrier Serving Office Code LS Local Serving Office (LSO) NC Network Channel Code NI Network Channel Interface Code PQ Major Product Code PU Percent of Interstate Usage (PIU) PV Percent of Facility Subject to Ratchet (RP) RT Rate State SC Service Category Code SI Circuit Number Special ID SX Two-Six Code TE Transmission Speed

TK Trunk Number TN Telephone Number

TX Translated Telephone Number XR Cross-Reference Number (Drop Location) SI05 234 Product/Service ID X AN 1/48 Identifying number for a product or service This element will contain a locally defined code associated with one of

the preceeding DE1000 values. Examples of a locally defined value include a telephone number, central office unit, network channel code, percent, USOC, circuit information, etc.


February 2004 138


characteristics FD Feature Data SI07 234 Product/Service ID X AN 1/48 Identifying number for a product or service CMP Component PKG Package SI08 1000 Service Characteristics Qualifier X AN 2/2 Code from an industry code list qualifying the type of service

characteristics OD Other Charges and Credits Desciption Code SI09 234 Product/Service ID X AN 1/48 Identifying number for a product or service 3875 Contracted Discount For Non-Direct Dialed Intralata 4205 Contracted Discount For Vertical Service Usage 4206 Contracted Discount For Operator Handled Charges 4207 Contracted Discount For AIN Usage 4208 Contracted Discount For Directory Assistance 4209 Contracted Discount for ISDN Usage 4210 Contracted Discount For Private Line Usage 4211 Contracted Discount For Line Service Usage 4212 Contracted Discount For MTS Usage 4213 Contracted Discount For Digline Usage 4280 Incollects B&C Refund 4285 Contracted Discount For Multipoint Video Usage 4286 Contracted Discount For Microlink II Usage 4287 Contracted Discount For FX Usage 4288 Contracted Discount For Other Usage Charges SI10 1000 Service Characteristics Qualifier X AN 2/2 Code from an industry code list qualifying the type of service




February 2004 139







June 2002 140


Position: 410 Loop: SLN Optional Level: Detail Usage: Optional Max Use: 200 Purpose: To describe a product or process in coded or free-form format Syntax Notes: 1 If PID04 is present, then PID03 is required. 2 At least one of PID04 or PID05 is required. 3 If PID07 is present, then PID03 is required. 4 If PID08 is present, then PID04 is required. 5 If PID09 is present, then PID05 is required. Semantic Notes: 1 Use PID03 to indicate the organization that publishes the code list being






Data Element Summary Ref. Data Des. Element Name Attributes M PID01 349 Item Description Type M ID 1/1 Code indicating the format of a description F Free-form X Semi-structured (Code and Text) Not Used PID02 750 Product/Process Characteristic Code O ID 2/3 Code identifying the general class of a product or process characteristic PID03 559 Agency Qualifier Code X ID 2/2 Code identifying the agency assigning the code values AS Assigned by Seller PID04 751 Product Description Code X AN 1/12 A code from an industry code list which provides specific data about a

product characteristic CI Circuit Drop Location DP Different Premises Address


June 2002 141







April 2002 142

Segment: INC Installment Information

Position: 430 Loop: SLN Optional Level: Detail Usage: Optional Max Use: 1 Purpose: To specify installment billing arrangement Syntax Notes: Semantic Notes: 1 INC02 is the installment period (e.g., months). 2 INC03 is the total number of installments. 3 INC04 is the number of the current installment. 4 INC05 is the installment balance after the current installment is applied. Comments:

Data Element Summary Ref. Data Des. Element Name Attributes M INC01 336 Terms Type Code M ID 2/2 Code identifying type of payment terms 04 Deferred or Installment M INC02 C001 Composite Unit of Measure M To identify a composite unit of measure M C00101 355 Unit or Basis for Measurement Code M ID 2/2 Code specifying the units in which a value is being expressed, or manner

in which a measurement has been taken MO Months Not Used C00102 1018 Exponent O R 1/15 Power to which a unit is raised Not Used C00103 649 Multiplier O R 1/10 Value to be used as a multiplier to obtain a new value Not Used C00104 355 Unit or Basis for Measurement Code O ID 2/2 Code specifying the units in which a value is being expressed, or manner



April 2002 143




in which a measurement has been taken Not Used C00114 1018 Exponent O R 1/15 Power to which a unit is raised Not Used C00115 649 Multiplier O R 1/10 Value to be used as a multiplier to obtain a new value M INC03 380 Quantity M R 1/15 Numeric value of quantity Indicates the total number of installments.

M INC04 380 Quantity M R 1/15 Numeric value of quantity Indicates number of current installment.

INC05 782 Monetary Amount O R 1/18 Monetary amount Balance remaining after this installment is billed.


April 2004 144


Position: 440 Loop: SLN Optional Level: Detail Usage: Optional Max Use: 10 Purpose: To specify allowances, charges, or services Syntax Notes: 1 If ITA02 is present, then at least one of ITA03 ITA13 or ITA14 is required. 2 If ITA08 is present, then ITA09 is required. 3 If either ITA10 or ITA11 is present, then the other is required. 4 If ITA15 is present, then ITA02 is required. 5 If ITA17 is present, then ITA12 is required. Semantic Notes: 1 ITA09 is the allowance or charge percent. 2 ITA10 is the quantity basis when the allowance or charge quantity is different



segment.

Data Element Summary Ref. Data Des. Element Name Attributes M ITA01 248 Allowance or Charge Indicator M ID 1/1 Code which indicates an allowance or charge for the service specified A Allowance C Charge N No Allowance or Charge

ITA02 559 Agency Qualifier Code X ID 2/2 Code identifying the agency assigning the code values TI Telecommunications Industry ITA03 560 Special Services Code X ID 2/10 Code identifying the special service CY County ST State M ITA04 331 Allowance or Charge Method of Handling Code M ID 2/2 Code indicating method of handling for an allowance or charge 04 Credit Customer Account 06 Charge to be Paid by Customer


April 2004 145




content ITA14 150 Special Charge or Allowance Code X ID 3/3 Code identifying type of special charge or allowance 230 Credit DSC Discount PMC Prior Month Credit Not Used ITA15 822 Source Subqualifier O AN 1/15 A reference that indicates the table or text maintained by the Source




June 2002 146


Position: 450 Loop: SLN Optional Level: Detail Usage: Optional Max Use: >1 Purpose: To specify tax information Syntax Notes: 1 At least one of TXI02 TXI03 or TXI06 is required. 2 If either TXI04 or TXI05 is present, then the other is required. 3 If TXI08 is present, then TXI03 is required. Semantic Notes: 1 TXI02 is the monetary amount of the tax. 2 TXI03 is the tax percent expressed as a decimal. 3 TXI07 is a code indicating the relationship of the price or amount to the


Data Element Summary Ref. Data Des. Element Name Attributes M TXI01 963 Tax Type Code M ID 2/2 Code specifying the type of tax FT Federal Excise Tax LS State and Local Sales Tax MP Municipal Tax TXI02 782 Monetary Amount X R 1/18 Monetary amount Not Used TXI03 954 Percent X R 1/10 Percentage expressed as a decimal Not Used TXI04 955 Tax Jurisdiction Code Qualifier X ID 2/2 Code identifying the source of the data used in tax jurisdiction code Not Used TXI05 956 Tax Jurisdiction Code X AN 1/10 Code identifying the taxing jurisdiction Not Used TXI06 441 Tax Exempt Code X ID 1/1 Code identifying exemption status from sales and use tax TXI07 662 Relationship Code O ID 1/1 Code indicating the relationship between entities O Information Only


June 2002 147





set


April 2004 148


Position: 460 Loop: SLN Optional Level: Detail Usage: Optional Max Use: >1 Purpose: To specify identifying information Syntax Notes: 1 At least one of REF02 or REF03 is required. 2 If either C04003 or C04004 is present, then the other is required. 3 If either C04005 or C04006 is present, then the other is required. Semantic Notes: 1 REF04 contains data relating to the value cited in REF02. Comments:

Data Element Summary Ref. Data Des. Element Name Attributes M REF01 128 Reference Identification Qualifier M ID 2/3 Code qualifying the Reference Identification CIR Circuit Number CT Contract Number

F8 Original Reference Number OW Service Order Number PO Purchase Order Number

REF02 127 Reference Identification X AN 1/30 Reference information as defined for a particular Transaction Set or as






April 2004 149





June 2002 150


Position: 480 Loop: SLN Optional Level: Detail Usage: Optional Max Use: 10 Purpose: To specify pertinent dates and times Syntax Notes: 1 At least one of DTM02 DTM03 or DTM05 is required. 2 If DTM04 is present, then DTM03 is required. 3 If either DTM05 or DTM06 is present, then the other is required. Semantic Notes: Comments:

Data Element Summary Ref. Data Des. Element Name Attributes M DTM01 374 Date/Time Qualifier M ID 3/3 Code specifying type of date or time, or both date and time 007 Effective 150 Service Period Start 151

152 Service Period End

Effective Date of Change DTM02 373 Date X DT 8/8 Date expressed as CCYYMMDD Not Used DTM03 337 Time X TM 4/8 Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS,






June 2002 151

Segment: AMT Monetary Amount

Position: 490 Loop: SLN Optional Level: Detail Usage: Optional Max Use: 15 Purpose: To indicate the total monetary amount Syntax Notes: Semantic Notes: Comments:

Data Element Summary Ref. Data Des. Element Name Attributes M AMT01 522 Amount Qualifier Code M ID 1/3 Code to qualify amount AP Amount Prior to Fractionalization AX Previous Price M AMT02 782 Monetary Amount M R 1/18 Monetary amount Not Used AMT03 478 Credit/Debit Flag Code O ID 1/1 Code indicating whether amount is a credit or debit


June 2002 152

Segment: MSG Message Text

Position: 500 Loop: SLN Optional Level: Detail Usage: Optional Max Use: >1 Purpose: To provide a free-form format that allows the transmission of text information Syntax Notes: 1 If MSG03 is present, then MSG02 is required. Semantic Notes: 1 MSG03 is the number of lines to advance before printing. Comments: 1 MSG02 is not related to the specific characteristics of a printer, but identifies

top of page, advance a line, etc. 2 If MSG02 is "AA - Advance the specified number of lines before print" then

MSG03 is required. Notes: The segment used to pass free-form information stored on billing system data

base.

Data Element Summary Ref. Data Des. Element Name Attributes M MSG01 933 Free-Form Message Text M AN 1/264 Free-form message text Not Used MSG02 934 Printer Carriage Control Code X ID 2/2 A field to be used for the control of the line feed of the receiving printer Not Used MSG03 1470 Number O N0 1/9 A generic number


June 2002 153



Data Element Summary Ref. Data Des. Element Name Attributes M QTY01 673 Quantity Qualifier M ID 2/2 Code specifying the type of quantity 01 Discrete Quantity 92 Allotted Usage Quantity 94 Billable Quantity 96 Non-Billable Quantity 98 Overflow Quantity 99 Quantity Used QTY02 380 Quantity X R 1/15 Numeric value of quantity QTY03 C001 Composite Unit of Measure O To identify a composite unit of measure M C00101 355 Unit or Basis for Measurement Code M ID 2/2 Code specifying the units in which a value is being expressed, or manner

in which a measurement has been taken C0 Calls (Messages) HR Hours HT Half Hour MJ Minutes Not Used C00102 1018 Exponent O R 1/15 Power to which a unit is raised Not Used C00103 649 Multiplier O R 1/10 Value to be used as a multiplier to obtain a new value


June 2002 154







June 2002 155







value may be present within the SI segment. CH Charge/Usage Status Code QT Quantity Qualifier M SI03 234 Product/Service ID M AN 1/48 Identifying number for a product or service For a list of valid DE234 values associated with the preceeding DE1000




June 2002 156


characteristics SI05 234 Product/Service ID X AN 1/48 Identifying number for a product or service Not Used SI06 1000 Service Characteristics Qualifier X AN 2/2 Code from an industry code list qualifying the type of service







June 2002 157






December 2003 158

Segment: NM1 Individual or Organizational Name

Position: 530 Loop: NM1 Optional Level: Detail Usage: Optional Max Use: 1 Purpose: To supply the full name of an individual or organizational entity Syntax Notes: 1 If either NM108 or NM109 is present, then the other is required. 2 If NM111 is present, then NM110 is required. Semantic Notes: 1 NM102 qualifies NM103. Comments: 1 NM110 and NM111 further define the type of entity in NM101.

Data Element Summary Ref. Data Des. Element Name Attributes M NM101 98 Entity Identifier Code M ID 2/3 Code identifying an organizational entity, a physical location, property or

an individual CA Carrier IA Installed At P9 Primary Interexchange Carrier (PIC) M NM102 1065 Entity Type Qualifier M ID 1/1 Code qualifying the type of entity 1 Person 2 Non-Person Entity 3 Unknown NM103 1035 Name Last or Organization Name O AN 1/35 Individual last name or organizational name Not Used NM104 1036 Name First O AN 1/25 Individual first name Not Used NM105 1037 Name Middle O AN 1/25 Individual middle name or initial Not Used NM106 1038 Name Prefix O AN 1/10 Prefix to individual name Not Used NM107 1039 Name Suffix O AN 1/10 Suffix to individual name


December 2003 159

NM108 66 Identification Code Qualifier X ID 1/2 Code designating the system/method of code structure used for

Identification Code (67) 41 Telecommunications Carrier Identification Code 91 Assigned by Seller or Seller’s Agent

ZY Temporary Identification Number NM109 67 Identification Code X AN 2/80 Code identifying a party or other code Not Used NM110 706 Entity Relationship Code X ID 2/2 Code describing entity relationship Not Used NM111 98 Entity Identifier Code O ID 2/3 Code identifying an organizational entity, a physical location, property or

an individual


April 2004 160

Segment: N3 Address Information Position: 550 Loop: NM1 Optional Level: Detail Usage: Optional Max Use: 2 Purpose: To specify the location of the named party Syntax Notes: Semantic Notes: Comments:



April 2004 161

Segment: N4 Geographic Location Position: 560 Loop: NM1 Optional Level: Detail Usage: Optional Max Use: 1 Purpose: To specify the geographic place of the named party Syntax Notes: 1 If N406 is present, then N405 is required. Semantic Notes: Comments: 1 A combination of either N401 through N404, or N405 and N406 may be


Data Element Summary Ref. Data Des. Element Name Attributes N401 19 City Name O AN 2/30 Free-form text for city name N402 156 State or Province Code O ID 2/2 Code (Standard State/Province) as defined by appropriate

government agency X N403 116 Postal Code O ID 3/15 Code defining international postal zone code excluding punctuation and

blanks (zip code for United States) X N404 26 Country Code O ID 2/3 Code identifying the country X N405 309 Location Qualifier X ID 1/2 Code identifying type of location Refer to 004010TCIF Data Element Dictionary for acceptable code

values. X N406 310 Location Identifier O AN 1/30 Code which identifies a specific location


June 2002 162

Segment: TCD Itemized Call Detail

Position: 590 Loop: TCD Optional Level: Detail Usage: Optional Max Use: 1 Purpose: To specify detail information for itemized calls Syntax Notes: 1 If either TCD04 or TCD05 is present, then the other is required. 2 If either TCD07 or TCD08 is present, then the other is required. Semantic Notes: 1 TCD12 is an undiscounted amount. 2 TCD13 is a net amount after the discount has been applied to the amount in

TCD12. 3 TCD14 is an undiscounted amount. 4 TCD15 is a net amount after the discount has been applied to the amount in

TCD14. 5 TCD16 is a code indicating the relationship of the price or amount to the

associated segment. Comments: 1 TCD01 is the detail information. 2 TCD02 is the date of the call. 3 TCD03 is the connect time of the call. 4 TCD04, TCD05, and TCD06 are the "TO'' location of the call. 5 TCD07, TCD08, and TCD09 are the "FROM" location of the call. 6 TCD10 and TCD11 are the total duration of the call. TCD10 is the time

measured in minutes or minutes and tenths of minutes. TCD11 is time measured in seconds or seconds and tenths of seconds.

Notes: The TCD loop may only appear at the line detail level.

Data Element Summary Ref. Data Des. Element Name Attributes TCD01 350 Assigned Identification O AN 1/20 Alphanumeric characters assigned for differentiation within a transaction

set TCD02 373 Date O DT 8/8 Date expressed as CCYYMMDD TCD03 337 Time O TM 4/8 Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS,



June 2002 163

TCD04 309 Location Qualifier X ID 1/2 Code identifying type of location Code identifying the type of "TO" location provided in TCD05 and TCD06.

A value of "ZZ" indicates any point of origination/termination or service for a call that cannot be qualified by traditional geographic qualifiers (i.e., City or Country). The point of origination/termination or service that this code qualifies could be the name of an aircraft, vessel, vehicle, or service where a call originated/terminated or the service was provided.

CC Country CI City ZZ Mutually Defined TCD05 310 Location Identifier X AN 1/30 Code which identifies a specific location TCD06 156 State or Province Code O ID 2/2 Code (Standard State/Province) as defined by appropriate government

agency TCD07 309 Location Qualifier X ID 1/2 Code identifying type of location Code identifying the type of "FROM" location in TCD08 and TCD09.

A value of "ZZ" indicates any point of origination/termination or service for a call that cannot be qualified by traditional geographic qualifiers (i.e., City or Country). The point of origination/termination or service that this code qualifies could be the name of an aircraft, vessel, vehicle, or service where a call originated/terminated or the service was provided.

CC Country CI City ZZ Mutually Defined TCD08 310 Location Identifier X AN 1/30 Code which identifies a specific location TCD09 156 State or Province Code O ID 2/2 Code (Standard State/Province) as defined by appropriate government

agency


June 2002 164

TCD10 739 Measurement Value O R 1/20 The value of the measurement The measurement is in minutes as related to the length of the call. This

field can be whole minutes OR whole and tenths of minutes, separated by the decimal point.

Duration of call measured in minutes and tenths of minutes. TCD11 739 Measurement Value O R 1/20 The value of the measurement The measurement is in seconds as related to the length of the call. This

field can be used in conjunction with the TCD10 field of minutes. TCD12 782 Monetary Amount O R 1/18 Monetary amount Not Used TCD13 782 Monetary Amount O R 1/18 Monetary amount Not Used TCD14 782 Monetary Amount O R 1/18 Monetary amount Not Used TCD15 782 Monetary Amount O R 1/18 Monetary amount TCD16 662 Relationship Code O ID 1/1 Code indicating the relationship between entities I Included O Information Only


June 2002 165


Position: 600 Loop: TCD Optional Level: Detail Usage: Optional Max Use: 2 Purpose: To specify service characteristic data Syntax Notes: 1 If either SI04 or SI05 is present, then the other is required. 2 If either SI06 or SI07 is present, then the other is required. 3 If either SI08 or SI09 is present, then the other is required. 4 If either SI10 or SI11 is present, then the other is required. 5 If either SI12 or SI13 is present, then the other is required. 6 If either SI14 or SI15 is present, then the other is required. 7 If either SI16 or SI17 is present, then the other is required. 8 If either SI18 or SI19 is present, then the other is required. 9 If either SI20 or SI21 is present, then the other is required. Semantic Notes: Comments: 1 SI01 defines the source for each of the service characteristics qualifiers.



Ref. Data Des. Element Name Attributes M SI01 559 Agency Qualifier Code M ID 2/2 Code identifying the agency assigning the code values TI Telecommunications Industry


June 2002 166

M SI02 1000 Service Characteristics Qualifier M AN 2/2 Code from an industry code list qualifying the type of service


value may be present within the SI segment. DA Directory Assistance IA Service Disconnect/Interruption Indicator MC Mesage/Rate Class MI Special Message Information Code Qualifier ML Message Delivery MT Message Type PS Packet Switching Category Code RP Rate Period RW Regulation Indicator RY Local/Toll Indicator SD Settlement Code ST Message Service Type TJ Terminating User M SI03 234 Product/Service ID M AN 1/48 Identifying number for a product or service For a list of valid DE234 values associated with the preceeding DE1000




value may be present within the SI segment. BA Band DI Department Code DJ Sub-Department Code ET Electronic Serial Number FN From Number SC Service Category Code TE Transmission Speed TM To/Terminating Station Telephone Number SI05 234 Product/Service ID X AN 1/48 Identifying number for a product or service This element will contain a locally defined code associated with one of

the preceeding DE1000 values. Examples of a locally defined value include a telephone number, transmission speed, USOC, etc.



June 2002 167









June 2002 168





June 2002 169


Position: 610 Loop: TCD Optional Level: Detail Usage: Optional Max Use: >1 Purpose: To specify tax information Syntax Notes: 1 At least one of TXI02 TXI03 or TXI06 is required. 2 If either TXI04 or TXI05 is present, then the other is required. 3 If TXI08 is present, then TXI03 is required. Semantic Notes: 1 TXI02 is the monetary amount of the tax. 2 TXI03 is the tax percent expressed as a decimal. 3 TXI07 is a code indicating the relationship of the price or amount to the


Data Element Summary Ref. Data Des. Element Name Attributes M TXI01 963 Tax Type Code M ID 2/2 Code specifying the type of tax ST State Sales Tax Not Used TXI02 782 Monetary Amount X R 1/18 Monetary amount Not Used TXI03 954 Percent X R 1/10 Percentage expressed as a decimal Not Used TXI04 955 Tax Jurisdiction Code Qualifier X ID 2/2 Code identifying the source of the data used in tax jurisdiction code Not Used TXI05 956 Tax Jurisdiction Code X AN 1/10 Code identifying the taxing jurisdiction TXI06 441 Tax Exempt Code X ID 1/1 Code identifying exemption status from sales and use tax 1 Yes (Tax Exempt) TXI07 662 Relationship Code O ID 1/1 Code indicating the relationship between entities O Information Only


June 2002 170





set


June 2002 171


Position: 615 Loop: TCD Optional Level: Detail Usage: Optional Max Use: >1 Purpose: To specify allowances, charges, or services Syntax Notes: 1 If ITA02 is present, then at least one of ITA03 ITA13 or ITA14 is required. 2 If ITA08 is present, then ITA09 is required. 3 If either ITA10 or ITA11 is present, then the other is required. 4 If ITA15 is present, then ITA02 is required. 5 If ITA17 is present, then ITA12 is required. Semantic Notes: 1 ITA09 is the allowance or charge percent. 2 ITA10 is the quantity basis when the allowance or charge quantity is different



segment.

Data Element Summary Ref. Data Des. Element Name Attributes M ITA01 248 Allowance or Charge Indicator M ID 1/1 Code which indicates an allowance or charge for the service specified A Allowance C Charge ITA02 559 Agency Qualifier Code X ID 2/2 Code identifying the agency assigning the code values TI Telecommunications Industry Not Used ITA03 560 Special Services Code X ID 2/10 Code identifying the special service M ITA04 331 Allowance or Charge Method of Handling Code M ID 2/2 Code indicating method of handling for an allowance or charge 04 Credit Customer Account 06 Charge to be Paid by Customer


June 2002 172




content If charge is a transfer state tax, this data element will contain the

appropriate state abbreviation code. If code = 'MX', then it is a Mexican surcharge.

ITA14 150 Special Charge or Allowance Code X ID 3/3 Code identifying type of special charge or allowance 230 Credit OLM Other Line Charge-Mexican Portion PSP Payphone Service Provider Surcharge

TRT Transfer State Tax


June 2002 173

Not Used ITA15 822 Source Subqualifier O AN 1/15 A reference that indicates the table or text maintained by the Source




June 2002 174

Segment: USD Usage Sensitive Detail

Position: 620 Loop: USD Optional Level: Detail Usage: Optional Max Use: 1 Purpose: To specify usage-sensitive details which qualify for discounts or are subject to

special rates Syntax Notes: 1 Only one of USD03 or USD04 may be present. 2 If USD03 is present, then at least one of USD06 USD07 or USD08 is required. 3 If USD04 is present, then at least one of USD08 or USD09 is required. 4 If either USD05 or USD06 is present, then the other is required. 5 If USD07 is present, then both USD05 and USD06 are required. 6 If USD10 is present, then at least one of USD11 or USD12 is required. 7 If USD11 is present, then USD10 is required. 8 If USD12 is present, then USD10 is required. Semantic Notes: 1 USD01 is a code indicating the relationship of the price or amount to the

associated segment. 2 USD03 is the allowance or charge rate per unit. 3 USD04 is the discount percentage. 4 USD06 is the quantity of usage. 5 USD07 is a quantity of usage different than the quantity in USD06. When

USD07 is present, it is used in conjunction with USD06, and then the rate USD03 is applied.

6 USD09 is the total amount of terms discount. Comments: 1 If both USD03 and USD08 are present, then USD08 takes precedence. 2 If USD11 is present and USD12 is not present, then the range is open ended. 3 If USD12 is present and USD11 is not present, then the minimum is zero.

Notes: The USD loop may only appear at the line detail level.

Data Element Summary Ref. Data Des. Element Name Attributes M USD01 662 Relationship Code M ID 1/1 Code indicating the relationship between entities A Add I Included O Information Only USD02 350 Assigned Identification O AN 1/20 Alphanumeric characters assigned for differentiation within a transaction

set


June 2002 175

USD03 118 Rate X R 1/9 Rate expressed in the standard monetary denomination for the currency

specified Not Used USD04 954 Percent X R 1/10 Percentage expressed as a decimal USD05 C001 Composite Unit of Measure X To identify a composite unit of measure M C00101 355 Unit or Basis for Measurement Code M ID 2/2 Code specifying the units in which a value is being expressed, or manner

in which a measurement has been taken AH Additional Minutes C0 Calls (Messages) DH Miles HR Hours MJ Minutes Not Used C00102 1018 Exponent O R 1/15 Power to which a unit is raised Not Used C00103 649 Multiplier O R 1/10 Value to be used as a multiplier to obtain a new value Not Used C00104 355 Unit or Basis for Measurement Code O ID 2/2 Code specifying the units in which a value is being expressed, or manner




June 2002 176



in which a measurement has been taken Not Used C00114 1018 Exponent O R 1/15 Power to which a unit is raised Not Used C00115 649 Multiplier O R 1/10 Value to be used as a multiplier to obtain a new value USD06 380 Quantity X R 1/15 Numeric value of quantity USD07 380 Quantity X R 1/15 Numeric value of quantity Used to adjust the quantity of usage. If charge is on a "ratchet USOC"

(USD14 = CA and USD15 = 3), then this data element contains the ratchet factor. If charge is related to a USOC with a "Border Interconnect Percentage (BIP)", then this data element contains the BIP. When USD07 is present, it is multipled by USD06. The resulting "quantity" is applied to rate in USD03.

USD08 782 Monetary Amount X R 1/18 Monetary amount Not Used USD09 610 Amount X N2 1/15 Monetary amount USD10 C001 Composite Unit of Measure X To identify a composite unit of measure


June 2002 177

M C00101 355 Unit or Basis for Measurement Code M ID 2/2 Code specifying the units in which a value is being expressed, or manner

in which a measurement has been taken HR Hours Not Used C00102 1018 Exponent O R 1/15 Power to which a unit is raised Not Used C00103 649 Multiplier O R 1/10 Value to be used as a multiplier to obtain a new value Not Used C00104 355 Unit or Basis for Measurement Code O ID 2/2 Code specifying the units in which a value is being expressed, or manner





June 2002 178


in which a measurement has been taken Not Used C00114 1018 Exponent O R 1/15 Power to which a unit is raised Not Used C00115 649 Multiplier O R 1/10 Value to be used as a multiplier to obtain a new value USD11 740 Range Minimum X R 1/20 The value specifying the minimum of the measurement range If USD11 is present and USD12 is not present, then the range is open-

ended. USD12 741 Range Maximum X R 1/20 The value specifying the maximum of the measurement range If USD12 is present and USD11 is not present, the minimum is zero.


June 2002 179


Position: 625 Loop: USD Optional Level: Detail Usage: Optional Max Use: 2 Purpose: To specify service characteristic data Syntax Notes: 1 If either SI04 or SI05 is present, then the other is required. 2 If either SI06 or SI07 is present, then the other is required. 3 If either SI08 or SI09 is present, then the other is required. 4 If either SI10 or SI11 is present, then the other is required. 5 If either SI12 or SI13 is present, then the other is required. 6 If either SI14 or SI15 is present, then the other is required. 7 If either SI16 or SI17 is present, then the other is required. 8 If either SI18 or SI19 is present, then the other is required. 9 If either SI20 or SI21 is present, then the other is required. Semantic Notes: Comments: 1 SI01 defines the source for each of the service characteristics qualifiers.





value may be present within the SI segment. CA Carrier Access Line Charge Code DC Directional Code IA Service Disconnect/Interruption Indicator MT Message Type RP Rate Period SD Settlement Code M SI03 234 Product/Service ID M AN 1/48 Identifying number for a product or service For a list of valid DE234 values associated with the preceeding DE1000




June 2002 180



value may be present within the SI segment. BA Band PV Ratchet Percent SC Service Category TL To/Terminating Location TM To/Terminating Station Telephone Number SI05 234 Product/Service ID X AN 1/48 Identifying number for a product or service This element will contain a locally defined code associated with one of

the preceeding DE1000 values. Examples of a locally defined value include a telephone number, percent, USOC, etc.


characteristics BS Billing Structure Code SI07 234 Product/Service ID X AN 1/48 Identifying number for a product or service TA Tapererd Rating TI Tiered Rating SI08 1000 Service Characteristics Qualifier X AN 2/2 Code from an industry code list qualifying the type of service





June 2002 181







June 2002 182


Position: 630 Loop: USD Optional Level: Detail Usage: Optional Max Use: 2 Purpose: To specify allowances, charges, or services Syntax Notes: 1 If ITA02 is present, then at least one of ITA03 ITA13 or ITA14 is required. 2 If ITA08 is present, then ITA09 is required. 3 If either ITA10 or ITA11 is present, then the other is required. 4 If ITA15 is present, then ITA02 is required. 5 If ITA17 is present, then ITA12 is required. Semantic Notes: 1 ITA09 is the allowance or charge percent. 2 ITA10 is the quantity basis when the allowance or charge quantity is different



segment.



June 2002 183


deal or charge Not Used ITA06 359 Allowance or Charge Rate O R 1/15 Allowance or Charge Rate per Unit ITA07 360 Allowance or Charge Total Amount O N2 1/15 Total dollar amount for the allowance or charge Not Used ITA08 378 Allowance/Charge Percent Qualifier O ID 1/1 Code indicating on what basis allowance or charge percent is calculated ITA09 332 Percent X R 1/6 Percent expressed as a percent Not Used ITA10 380 Quantity X R 1/15 Numeric value of quantity Not Used ITA11 355 Unit or Basis for Measurement Code X ID 2/2 Code specifying the units in which a value is being expressed, or manner


content ITA14 150 Special Charge or Allowance Code X ID 3/3 Code identifying type of special charge or allowance 230 Credit DSC Discount Not Used ITA15 822 Source Subqualifier O AN 1/15 A reference that indicates the table or text maintained by the Source

Qualifier ITA16 662 Relationship Code O ID 1/1 Code indicating the relationship between entities A Add Not Used ITA17 355 Unit or Basis for Measurement Code O ID 2/2 Code specifying the units in which a value is being expressed, or manner



June 2002 184

Segment: TRF Rating Factors

Position: 640 Loop: USD Optional Level: Detail Usage: Optional Max Use: 18 Purpose: To specify rating information used to calculate usage-sensitive charges Syntax Notes: Semantic Notes: Comments: 1 TRF01 defines the rating basis (e.g., acknowledged calls, minimum period,

etc.) for the segment. 2 TRF02 and TRF03 define equivalent units per standard unit. 3 TRF04 and TRF05 define the standard unit.

Data Element Summary Ref. Data Des. Element Name Attributes M TRF01 673 Quantity Qualifier M ID 2/2 Code specifying the type of quantity Code specifying the rating basis (e.g., acknowledged calls) for charge.

AE Minimum Average Time Requirement (MATR) Units M TRF02 C001 Composite Unit of Measure M To identify a composite unit of measure M C00101 355 Unit or Basis for Measurement Code M ID 2/2 Code specifying the units in which a value is being expressed, or manner

in which a measurement has been taken 03 Seconds MJ Minutes Not Used C00102 1018 Exponent O R 1/15 Power to which a unit is raised Not Used C00103 649 Multiplier O R 1/10 Value to be used as a multiplier to obtain a new value Not Used C00104 355 Unit or Basis for Measurement Code O ID 2/2 Code specifying the units in which a value is being expressed, or manner



June 2002 185

Not Used C00105 1018 Exponent O R 1/15 Power to which a unit is raised Not Used C00106 649 Multiplier O R 1/10 Value to be used as a multiplier to obtain a new value Not Used C00107 355 Unit or Basis for Measurement Code O ID 2/2 Code specifying the units in which a value is being expressed, or manner



in which a measurement has been taken Not Used C00114 1018 Exponent O R 1/15 Power to which a unit is raised Not Used C00115 649 Multiplier O R 1/10 Value to be used as a multiplier to obtain a new value M TRF03 380 Quantity M R 1/15 Numeric value of quantity M TRF04 C001 Composite Unit of Measure M To identify a composite unit of measure


June 2002 186

M C00101 355 Unit or Basis for Measurement Code M ID 2/2 Code specifying the units in which a value is being expressed, or manner

in which a measurement has been taken C0 Calls (Messages) Not Used C00102 1018 Exponent O R 1/15 Power to which a unit is raised Not Used C00103 649 Multiplier O R 1/10 Value to be used as a multiplier to obtain a new value Not Used C00104 355 Unit or Basis for Measurement Code O ID 2/2 Code specifying the units in which a value is being expressed, or manner





June 2002 187


in which a measurement has been taken Not Used C00114 1018 Exponent O R 1/15 Power to which a unit is raised Not Used C00115 649 Multiplier O R 1/10 Value to be used as a multiplier to obtain a new value M TRF05 380 Quantity M R 1/15 Numeric value of quantity


June 2002 188



Data Element Summary Ref. Data Des. Element Name Attributes M QTY01 673 Quantity Qualifier M ID 2/2 Code specifying the type of quantity 94 Billable Quantity 99 Quantity Used AE Minimum Average Time Requirement (MATR) Units QTY02 380 Quantity X R 1/15 Numeric value of quantity QTY03 C001 Composite Unit of Measure O To identify a composite unit of measure M C00101 355 Unit or Basis for Measurement Code M ID 2/2 Code specifying the units in which a value is being expressed, or manner

in which a measurement has been taken C0 Calls (Messages) HR Hours HT Half Hour MJ Minutes UB Telecommunications Lines in Service - Average UF Usage per Telecommunications Line - Average Not Used C00102 1018 Exponent O R 1/15 Power to which a unit is raised Not Used C00103 649 Multiplier O R 1/10 Value to be used as a multiplier to obtain a new value


June 2002 189







June 2002 190

Segment: TDS Total Monetary Value Summary

Position: 010 Loop: Level: Summary Usage: Mandatory Max Use: 1 Purpose: To specify the total invoice discounts and amounts Syntax Notes: Semantic Notes: 1 TDS01 is the total amount of invoice (including charges, less allowances)

before terms discount (if discount is applicable). 2 TDS02 indicates the amount upon which the terms discount amount is

calculated. 3 TDS03 is the amount of invoice due if paid by terms discount due date (total

invoice or installment amount less cash discount). 4 TDS04 indicates the total amount of terms discount. Comments: 1 TDS02 is required if the dollar value subject to discount is not equal to the

dollar value of TDS01.

Data Element Summary Ref. Data Des. Element Name Attributes M TDS01 610 Amount M N2 1/15 Monetary amount Not Used TDS02 610 Amount O N2 1/15 Monetary amount Not Used TDS03 610 Amount O N2 1/15 Monetary amount Not Used TDS04 610 Amount O N2 1/15 Monetary amount


June 2002 191


Position: 020 Loop: ITA Optional Level: Summary Usage: Optional Max Use: 1 Purpose: To specify allowances, charges, or services Syntax Notes: 1 If ITA02 is present, then at least one of ITA03 ITA13 or ITA14 is required. 2 If ITA08 is present, then ITA09 is required. 3 If either ITA10 or ITA11 is present, then the other is required. 4 If ITA15 is present, then ITA02 is required. 5 If ITA17 is present, then ITA12 is required. Semantic Notes: 1 ITA09 is the allowance or charge percent. 2 ITA10 is the quantity basis when the allowance or charge quantity is different



segment.

Data Element Summary Ref. Data Des. Element Name Attributes M ITA01 248 Allowance or Charge Indicator M ID 1/1 Code which indicates an allowance or charge for the service specified A Allowance C Charge ITA02 559 Agency Qualifier Code X ID 2/2 Code identifying the agency assigning the code values TI Telecommunications Industry Not Used ITA03 560 Special Services Code X ID 2/10 Code identifying the special service M ITA04 331 Allowance or Charge Method of Handling Code M ID 2/2 Code indicating method of handling for an allowance or charge 03 Vendor Check to Customer 04 Credit Customer Account 06 Charge to be Paid by Customer


June 2002 192


deal or charge Not Used ITA06 359 Allowance or Charge Rate O R 1/15 Allowance or Charge Rate per Unit ITA07 360 Allowance or Charge Total Amount O N2 1/15 Total dollar amount for the allowance or charge Not Used ITA08 378 Allowance/Charge Percent Qualifier O ID 1/1 Code indicating on what basis allowance or charge percent is calculated ITA09 332 Percent X R 1/6 Percent expressed as a percent Not Used ITA10 380 Quantity X R 1/15 Numeric value of quantity Not Used ITA11 355 Unit or Basis for Measurement Code X ID 2/2 Code specifying the units in which a value is being expressed, or manner


content ITA14 150 Special Charge or Allowance Code X ID 3/3 Code identifying type of special charge or allowance DAB Deposit ISD Interest on security deposit RFD Refund TR1 Transferred charge or credit amount from another

account TR2 Transferred charge or credit amount to another

account Not Used ITA15 822 Source Subqualifier O AN 1/15 A reference that indicates the table or text maintained by the Source

Qualifier


June 2002 193

ITA16 662 Relationship Code O ID 1/1 Code indicating the relationship between entities A Add Not Used ITA17 355 Unit or Basis for Measurement Code O ID 2/2 Code specifying the units in which a value is being expressed, or manner



June 2002 194


Position: 030 Loop: ITA Optional Level: Summary Usage: Optional Max Use: 1 Purpose: To specify pertinent dates and times Syntax Notes: 1 At least one of DTM02 DTM03 or DTM05 is required. 2 If DTM04 is present, then DTM03 is required. 3 If either DTM05 or DTM06 is present, then the other is required. Semantic Notes: Comments:

Data Element Summary Ref. Data Des. Element Name Attributes M DTM01 374 Date/Time Qualifier M ID 3/3 Code specifying type of date or time, or both date and time 007 Effective DTM02 373 Date X DT 8/8 Date expressed as CCYYMMDD Not Used DTM03 337 Time X TM 4/8 Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS,






June 2002 195

Segment: BAL Balance Detail

Position: 040 Loop: BAL Optional Level: Summary Usage: Optional Max Use: 1 Purpose: To identify the specific monetary balances associated with a particular account Syntax Notes: Semantic Notes: Comments:

Data Element Summary Ref. Data Des. Element Name Attributes M BAL01 951 Balance Type Code M ID 1/2 Code indicating the type of balance A Adjustment M Current Month P Previous Month M BAL02 522 Amount Qualifier Code M ID 1/3 Code to qualify amount BT Bank Reject Total NA Net Adjustment PB Billed Amount TP Total payment amount TT Total Transaction Amount M BAL03 782 Monetary Amount M R 1/18 Monetary amount


August 2003 196

Segment: N1 Name

Position: 060 Loop: N1 Optional Level: Summary Usage: Optional Max Use: 1 Purpose: To identify a party by type of organization, name, and code Syntax Notes: 1 At least one of N102 or N103 is required. 2 If either N103 or N104 is present, then the other is required. Semantic Notes: Comments: 1 This segment, used alone, provides the most efficient method of providing

organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.

2 N105 and N106 further define the type of entity in N101.

Data Element Summary Ref. Data Des. Element Name Attributes M N101 98 Entity Identifier Code M ID 2/3 Code identifying an organizational entity, a physical location, property or

an individual 87 Pay-to Provider SJ Service Provider N102 93 Name X AN 1/60 Free-form name N103 66 Identification Code Qualifier X ID 1/2 Code designating the system/method of code structure used for

Identification Code (67) 41 Telecommunications Carrier Identification Code 42 Telecommunications Pseudo Carrier Identification

Code 91 Assigned to Seller or Seller’s Agent N104 67 Identification Code X AN 2/80 Code identifying a party or other code


August 2003 197

Not Used N105 706 Entity Relationship Code O ID 2/2 Code describing entity relationship Not Used N106 98 Entity Identifier Code O ID 2/3 Code identifying an organizational entity, a physical location, property or

an individual


June 2002 198

Segment: BAL Balance Detail

Position: 070 Loop: BAL Optional Level: Summary Usage: Optional Max Use: 1 Purpose: To identify the specific monetary balances associated with a particular account Syntax Notes: Semantic Notes: Comments:

Data Element Summary Ref. Data Des. Element Name Attributes M BAL01 951 Balance Type Code M ID 1/2 Code indicating the type of balance M Current Month M BAL02 522 Amount Qualifier Code M ID 1/3 Code to qualify amount MD Minimum Due M BAL03 782 Monetary Amount M R 1/18 Monetary amount


June 2002 199


Position: 090 Loop: ITA Optional Level: Summary Usage: Optional Max Use: 1 Purpose: To specify allowances, charges, or services Syntax Notes: 1 If ITA02 is present, then at least one of ITA03 ITA13 or ITA14 is required. 2 If ITA08 is present, then ITA09 is required. 3 If either ITA10 or ITA11 is present, then the other is required. 4 If ITA15 is present, then ITA02 is required. 5 If ITA17 is present, then ITA12 is required. Semantic Notes: 1 ITA09 is the allowance or charge percent. 2 ITA10 is the quantity basis when the allowance or charge quantity is different



segment.



June 2002 200




content ITA14 150 Special Charge or Allowance Code X ID 3/3 Code identifying type of special charge or allowance AAJ Adjustments Not Used ITA15 822 Source Subqualifier O AN 1/15 A reference that indicates the table or text maintained by the Source

Qualifier ITA16 662 Relationship Code O ID 1/1 Code indicating the relationship between entities O Information Only Not Used ITA17 355 Unit or Basis for Measurement Code O ID 2/2 Code specifying the units in which a value is being expressed, or manner



June 2002 201

Segment: CTT Transaction Totals

Position: 115 Loop: Level: Summary Usage: Optional Max Use: 1 Purpose: To transmit a hash total for a specific element in the transaction set Syntax Notes: 1 If either CTT03 or CTT04 is present, then the other is required. 2 If either CTT05 or CTT06 is present, then the other is required. Semantic Notes: Comments: 1 This segment is intended to provide hash totals to validate transaction

completeness and correctness. Notes: The number of line items (CTT01) is the accumulation of the number of IT1

segments.


Ref. Data Des. Element Name Attributes M CTT01 354 Number of Line Items M N0 1/6 Total number of line items in the transaction set Number of IT1 segments in this transaction set. Not Used CTT02 347 Hash Total O R 1/10 Not Used CTT03 81 Weight X R 1/10 Numeric value of weight Not Used CTT04 355 Unit or Basis for Measurement Code X ID 2/2 Code specifying the units in which a value is being expressed, or manner

in which a measurement has been taken Not Used CTT05 183 Volume X R 1/8 Value of volumetric measure


June 2002 202

Not Used CTT06 355 Unit or Basis for Measurement Code X ID 2/2 Code specifying the units in which a value is being expressed, or manner

in which a measurement has been taken Not Used CTT07 352 Description O AN 1/80 A free-form description to clarify the related data elements and their

content


June 2002 203

Segment: SE Transaction Set Trailer

Position: 120 Loop: Level: Summary Usage: Mandatory Max Use: 1 Purpose: To indicate the end of the transaction set and provide the count of the transmitted

segments (including the beginning (ST) and ending (SE) segments) Syntax Notes: Semantic Notes: Comments: 1 SE is the last segment of each transaction set.

Data Element Summary Ref. Data Des. Element Name Attributes M SE01 96 Number of Included Segments M N0 1/10 Total number of segments included in a transaction set including ST and

SE segments M SE02 329 Transaction Set Control Number M AN 4/9 Identifying control number that must be unique within the transaction set

functional group assigned by the originator for a transaction set

electronic commerce customer guide - at&tw_sbct_ig.pdflevel , service provider level, contains...

Documents