811 Transaction Set (Version/Release 004010)€¦ · services. As a member of ETB, the SBC...

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: August 2003

© BY SBC - All Rights Reserved

Electronic Commerce Customer Guide811 Implementation Guide

Table of Contents

June 2003 1

Table of Contents1 Overview ........................................................................................... 21.1 Schedule of 811 Versions .................................................................. 21.2 Structure of the 811 ........................................................................... 31.3 Format of Guide.................................................................................. 51.4 Bill and Transaction Formats Provided .............................................. 61.5 Referencing Charges When Contacting SBC Operating Company in Missouri, Oklahoma, Kansas, Arkansas and Texas ...................... 81.6 Taxes, Surcharges, and Fees ............................................................ 91.7 Data Element Separator and Segment Terminator ........................... 91.8 Functional Group Information............................................................. 101.9 Understanding Hierarchical Level (HL) Segments ............................ 11

2 Heading Area..................................................................................... 132.1 Structure ........................................................................................... 132.2 Sample Mapping................................................................................. 13

3 Detail Area ......................................................................................... 143.1 Summary 811 .................................................................................... 143.2 Detail 811 ........................................................................................... 183.3 Structure 1 - Itemized Calls / Itemized Charges ................................ 233.4 Structure 2 - Band Usage................................................................... 273.5 Structure 3 - WATS Usage................................................................. 283.6 Structure 4 - Directory Assistance ..................................................... 333.7 Structure 5 - Other Charges and Credits Explanation ....................... 343.8 Structure 6 - Optional Calling Plan Usage ......................................... 363.9 Structure 7 - Common Line 800 Usage ............................................. 393.10 Structure 8 - Account Service Information........................................ 463.11 Structure 9 - Feature Group A .......................................................... 483.12 Structure 10 - Contracts and Discounts............................................ 49

4 Summary Area .................................................................................. 504.1 Structure ........................................................................................... 504.2 Sample Mapping................................................................................. 50

5 Consolidated 811.............................................................................. 515.1 Structure ........................................................................................... 525.2 Sample Mapping................................................................................. 52

6 Auditing the 811................................................................................ 536.1 Rules of Extended Pricing .................................................................. 536.2 Defining and Determining Segment Amount ..................................... 536.3 Auditing the Detail and Summary Area ............................................. 56

7 Technical Specifications ................................................................. 57811 TS - Segment and Data Element Use............................................... 57


Overview

April 2003 2

1 OverviewThe information in this section reflects the implementation of the Consolidated ServiceInvoice/Statement Transaction Set (811) by the SBC operating companies in Missouri,Oklahoma, Kansas, Arkansas and Texas.

EDI Telecommunications Billing (ETB), author of the 811, develops "standardstructures” for providing detail bill information about service offerings. EDITelecommunications Billing (ETB), author of the Issue 9 Telephone Billing Guidelines,has developed business models for providing detail bill information for commonservices. As a member of ETB, the SBC operating companies in Missouri, Oklahoma,Kansas, Arkansas and Texas 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 explainthe implementation of the 811 by the SBC operating companies in Missouri, Oklahoma,Kansas, Arkansas and Texas. Each section provides a comprehensive discussion ofthe information being provided for a particular area of the bill, the format of thesegments 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 DraftVersion 4 Release 1 standards, and the TCIF Telephone Billing Guideline Issue 9 forthe 811. The TCIF Telephone Billing Guideline can be found onthe World Wide Web within the TCIF home at:http://www.atis.org/atis/tcif/edi/tbwg/5tc54hom.htm.

The file format documented applies to all files that the SBC operating companies inMissouri, Oklahoma, Kansas, Arkansas and Texas provide with a value of “004010” inGS08 to signify release 4 version 1 of the transaction set. The format of this file will beupdated as billing changes impact the structure.

Trading partners receiving the 811 will be given at least 30 days notice to reviewpending changes before a new format is delivered. The intention is to provide a stabletransaction set for trading partners while working toward consistency of implementationin the telecommunications industry.

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


Overview

April 2003 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 billBilling 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 theHeading Area.

The Detail Area (Table 2) contains service usage and charge information. The detailarea provides 9 hierarchical levels for data presentation.

Level 1, Service Provider level, contains information about the provider of theservice. Note that while the information contained in the heading area refers to theprovider of the bill (i.e., SBC operating company in Missouri, Oklahoma, Kansas,Arkansas or Texas), information contained in Table 2/Level 1 refers to the actualentity providing the service. It is very common to have charges from several serviceproviders for a given account (e.g., SBC operating company, AT&T, Sprint, andWorldcom charges can all appear on a bill provided by a SBC operating company inMissouri, Oklahoma, Kansas, Arkansas or Texas). Aggregate tax information is alsoprovided at this level.

Level 2, Billing Arrangement level, contains information about the billingarrangement. This level is used to provide Consolidated Billing Account (CBA)information.

Level 3, Sub-Billing Arrangement level, can also contain information about the billingarrangement. SBC operating companies in Missouri, Oklahoma, Kansas,Arkansas and Texas 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 6are used to organize charges within the 811. For example, most itemized chargesare sorted by station number at Level 5, while the OC&C section is sorted byPurchase 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. SBC operating companies inMissouri, Oklahoma, Kansas, Arkansas and Texas do not use level 7.

Level 8, Charge Detail level, contains supporting charge detail for charges providedat the Level 4.


Overview

April 2003 4

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

Section 3 of this implementation guide provides further detail on the data provided in theDetail Area.

The Summary Area (Table 3) contains summary information about the 811. Thesummary 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 providedwhen the applicable amount is not equal to zero. Below is the equation that can beused 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)


Overview

April 2003 5

1.3 Format of Guide

Section 2 of this implementation guide will provide a detailed description of theHeading Section within the 811 transaction set.

Section 3 of this implementation guide will provide a detailed description of the DetailArea of the 811 transaction set, and the structure of various billed services.

Section 4 of this implementaton guide will provide a detailed description of theSummary Area of the 811 transaction set.

Section 5 discusses the Consolidated Billing Arrangement, a billing arrangementthat consolidates bills into a single payable bill.

Section 6 discusses the Audit Procedures followed to insure the accuracy of the EDI811 transaction set.

The Technical Specifications provide a comprehensive listing of segments, dataelements, 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 differentinformation, it is important to review the sample mapping associated with each area ofthe transaction set. An example of different uses of a segment can be demonstratedwith the TXI segment. In the heading area, this segment is used to provide informationabout the tax exempt status of the billed party; while in the detail area at HL 1, the samesegment is used to provide a taxable amount to the billed party.


Overview

April 2003 6

1.4 Bill and Transaction Formats Provided

Several different bill formats and several different 811 formats are provided. It isimportant 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 SystemThis billing arrangement produces one bill per telephone number.

• Group Billing Account - CRIS Billing SystemThis billing arrangement combines several single accounts under one main accountnumber and produces one large bill.

• Consolidated Billing Account (CBA) - CRIS Billing SystemThis billing arrangement can be used in conjunction with both Single Accounts andGroup Billing Accounts. Single Accounts and/or Group Billing Accounts areconsolidated under a single CBA number. This produces a special summary 811 ofall accounts in the arrangement (see chapter 5), followed by a separate 811 for eachsubordinate account.

• Bill Account Number (BAN) - CABS Billing SystemThis is the only billing arrangement for bills out of the CABS billing system. Like theGroup Billing Account, this billing arrangement can combine several single numbersunder 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 811Accounts 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

Detail 811Without Account Service InformationWith Account Service Information

While the heading and summary areas of these formats are identical, the detail areasdiffer in the level of detail provided.

Summary 811s

The summary 811 formats provide high level account information. The advantages ofthese formats are a less complex programming effort and lower VAN charges. Summary information is provided within HLs 1 - 4.


Overview

April 2003 7

The Accounts Payable 811 provides a break out of taxes by jurisdiction and a singlecharge 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 abreak out of taxes by jurisdiction within each carrier. The billing information provided isvery similar to the carrier summary pages of a paper bill. While this option does notprovide as much information as a Detail 811, it provides more information than theAccounts Payable 811.

The Consolidated Billing Account (CBA) Summary 811 provides the bill for the Masterconsolidated account, but does not provide the ‘memo’ bills for each of the subordinateaccounts.

The CABS Summary 811 provides high level charges. It also provides a break out oftaxes by jurisdiction. Note: This format is the only option for CABS accounts that arenot Feature Group A or Specials.

Detail 811s

The Detail 811 formats provide supporting information for many charges. The keyadvantage of these full detail formats is more billing information to analyze. Whilesummary information is provided within HLs 1 - 4, full detail information is provided atHLs 5 - 9.

The Detail 811 without Account Service Information provides the same level of billingdetail that is currently provided on a paper bill.

The Detail 811 with Account Service Information provides additional detail in support ofmonthly service charges. It is estimated that the additional Account Service Informationadds approximately 40% to the size of each 811. Note: This format is the only optionfor Feature Group A or Special CABS accounts.


Overview

April 2003 8

1.5 Referencing Charges When ContactingSBC Operating Companies in Missouri, Oklahoma,Kansas, Arkansas and Texas

The information provided in the 811 is used in place of the paper bill. Since theinformation provided will be used to both pay bills and resolve billing discrepancies, keyfields and reference numbers from the 811 should be passed to the customer's internalapplications. The following data elements are required to reference an account:

Bill Date BIG Segment - BIG01Account 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 billinginquiries, are provided in each loop where charge information is provided. (The TXIsegment does not contain a reference number.) The formation of the reference numberis 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 TCD01contain bill reference numbers. Data elements in the summary area (TDS01 andBAL03) also contain important information, but there is not a data element available tohold a reference number. Charges provided in the summary area generally appear onpage 2 of a paper bill.


Overview

April 2003 9

1.6 Taxes, Surcharges and Fees

Taxes, surcharges and fees which are assessed by a service provider on behalf of athird party (e.g., state or local government) and make up a portion of the monthlytelephone bill. Like amounts are aggregated and provided at the service provider levelof the 811. Taxes by jurisdiction are also provided for each charge shown at the grouplevel 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, pleaseresolve 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 billingrepresentative.

1.7 Data Element Separator and Segment Terminator

When displaying mapping examples in this guide, the tilde ( “~” ) is used as the dataelement separator and the exclamation point ( “ ! ” ) is used as the segment terminator.

In live production data, the SBC operating companies in Missouri, Oklahoma, Kansas,Arkansas and Texas will work with the customer to set up the data element separator,segment terminator and sub-element separator. The X12 recommended data elementseparator of the tilde ( “~” HEX A1), segment terminator of the exclamation point ( “ ! ”HEX 5A) and sub-element separator of the double vertical bar ( “ ¦ “ HEX 6A) arepreferred.


Overview

April 2003 10

1.8 Functional Group Information

All 811 transaction sets provided will be enveloped within a functional group. Thepurpose of the functional group is to provide control information for the businessdocument 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. DataUse Reference Element # Valid Values/DescriptionM GS01 479 Valid Value:

CI - Consolidated InvoiceM GS02 142 Valid Values:

006968523CRI006968523CAB

006968523CRWM GS03 124 Application Receiver's CodeM GS04 373 Data Interchange DateM GS05 337 Data Interchange TimeM GS06 28 Data Interchange Control Number

Matches value in GE02 at end offunctional group.

M GS07 455 Valid Value:X - Accredited Standards Committee

X12M GS08 480 Valid Value:

004010 - Version 4, Release 1

GE segment

Example: GE*337*128!

D.E. DataUse Reference Element # Valid Values/DescriptionM GE01 97 Number of transaction setsM GE02 28 Data Interchange Control Number

Matches value in GS06 at beginning offunctional group.


Overview

April 2003 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 thefollowing 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 aparticular 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) HLsegments associated with the hierarchical level. Although HL04 is not a mandatoryelement according to X12 syntax, it is required by TCIF. The value of ‘1’ indicates thatthe hierarchical level has children (additional subordinate HL data segments in thehierarchical structure). The value of ‘0’ indicates that the hierarchical level has nochildren (no subordinate HL segment in the hierarchical structure). This providespositive confirmation of subordinate HL loops.

Summary page charges are provided at HL 4. All charges which are stand-alone (nosupporting detail provided) will be grouped together in one HL loop. Each charge whichhas 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 inthe 811. The HL01 data element always contains the sequential number of therespective HL loop.

HL~1~~1~1!HL02 is not provided. This means the information provided does not have a parentHL loop. HL03 signifies HL 1, the service provider level. HL04 indicates that thereis supporting detail at a lower level.

HL~2~1~4~0!HL02 indicates that this information supports and is related to the informationprovided in HL loop number 1. HL03 signifies HL 4, the group level. HL04indicates that there is no supporting detail for the charges at this level. Several IT1loops can appear under the same HL loop when HL04 = “0”.

HL~3~1~4~1!HL02 indicates that this information supports and is related to the informationprovided in HL loop number 1. HL03 signifies HL 4, the group level. HL04indicates that there is supporting detail at a lower level. When HL04 = “1”, only oneIT1 loop will appear within this HL loop.


Overview

April 2003 12

HL~4~3~5~1!HL02 indicates that this information supports and is related to the informationprovided in HL loop number 3. HL03 signifies HL 5, the Category level. HL04indicates that there is supporting detail at a lower level.

HL~5~4~9~0!HL02 indicates that this information supports and is related to the informationprovided in HL loop number 4. HL03 signifies HL 9, the Line Detail level. HL04indicates that there is no supporting detail for the charges.


Heading Area

December 2002 13

2 Heading AreaThe purpose of the heading area of the 811 is to provide information about the bill beingrendered (i.e., account number, type of bill, due date, and tax status of bill), the entityreceiving the bill (the trading partner), and the entity providing the bill (SBC operatingcompany in Missouri, Oklahoma, Kansas, Arkansas or Texas).

2.1 Structure

MaxSegment Segment Description Loop Use O/M

ST Transaction Set Header N/A 1 MBIG Beginning Segment for Invoice N/A 1 MNTE Note/Special Instruction N/A 100 OREF Reference Number N/A 3 MITD Terms of Sale/Due Date N/A 1 ODTM Service From/Through Dates N/A 2 OTXI Tax Exemption information N/A 3 O

Loop N1 2 MN1 Name and DUNS Number N1 1 MN3 Address N1 2 ON4 City, State, ZIP N1 1 OREF 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!


Detail Area

June 2002 14

3 Detail AreaThe purpose of the detail area of the 811 is to provide information about the servicesthat 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 theheading area of the 811). As previously discussed, the 811 is provided in either asummary format or a detail format. For simplicity, a single account is used in discussingthe two bill formats. The two summary bill formats will be discussed first and then usedas 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 summary811 provides all charges at a summary level only. As previously discussed, anAccounts Payable 811, a Carrier Summary 811, a CBA Summary 811, or a CABSSummary 811 is provided.

The summary 811 formats provide high level account information. The advantages ofthese 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 singlecharge 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 abreak out of taxes by jurisdiction within each carrier. The billing information provided isvery similar to the carrier summary pages of a paper bill. While this option does notprovide as much information as a Detail 811, it provides more information than theAccounts 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 masterconsolidated account. ‘Memo’ bills are not provided for each of the subordinateaccounts.

3.1.4 CABS Summary 811

The CABS Summary 811 provides high level charges. It also provides a break out oftaxes by jurisdiction. Note: This format is the only option for CABS accounts that arenot Feature Group A or Specials.


Detail Area

June 2002 15

3.1.5 Structure (HL 1)


Loop HL >1 MHL Service Provider - HL 1 HL 1 M

Loop HL/LX 1 OLX Sequential Designator HL/LX 1 OSI Class of Service HL/LX 2 OAMT Carrier Totals HL/LX 3 ODTM Activity Dates HL/LX 2 O

Loop HL/N1 1 MNM1 Service Provider Code HL/N1 1 MREF Service Provider Numbers HL/N1 2 OPER Inquiry Telephone Numbers HL/N1 2 OTXI Aggregate Taxes HL/N1 10 O

Loop HL/ITA 20 OITA Surcharges/Allowances HL/ITA 1 M



Loop HL >1 MHL Group - HL 4 HL 1 M

Loop HL/IT1 >1 MIT1 Summary Charge HL/IT1 1 MPID Charge Explanation HL/IT1 1 OTXI Taxes HL/IT1 3 ODTM Service Dates HL/IT1 2 O

Loop HL/IT1/QTY 1 OQTY Number of Lines In Service HL/IT1/QTY 1 OSI Rate State HL/IT1/QTY 1 O

Loop HL/IT1/ITA 2 OITA Surcharges/Allowances HL/IT1/ITA 1 M


Detail Area

June 2003 16

3.1.7 Sample Mappings

Accounts Payable 811HL~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 811HL~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!


Detail Area

June 2003 17

Carrier Summary 811 (SBC operating company in Missouri, Oklahoma,Kansas, Arkansas or Texas 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!


Detail Area

April 2003 18

3.2 Detail 811

As previously noted, the structure at levels 1 through 4 of the detail 811s is identical tothat of the summary 811s.

The key difference in the two formats is that the detail 811s provide detail usage andbilling 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, eventhough it is identical to the summary 811s.

After level 4 is discussed, each billing structure that is provided is discussed. In manycases the same billing structure will be used to provide supporting detail for differentsummary level charges. This should simplify coding efforts on the receiving side of the811.


Detail Area

April 2003 19



Loop HL >1 MHL Service Provider - HL 1 HL 1 M

Loop HL/LX 1 OLX Sequential Designator HL/LX 1 OSI Class of Service HL/LX 2 OAMT Carrier Totals HL/LX 3 ODTM Activity Dates HL/LX 2 O

Loop HL/N1 1 MNM1 Service Provider Code HL/N1 1 MREF Service Provider Numbers HL/N1 2 OPER Inquiry Telephone Numbers HL/N1 2 OTXI Aggregate Taxes HL/N1 10 O

Loop HL/ITA 20 OITA Surcharges/Allowances HL/ITA 1 M



Loop HL >1 MHL Group - HL 4 HL 1 M

Loop HL/IT1 >1 MIT1 Summary Charge HL/IT1 1 MPID Charge Explanation HL/IT1 1 OTXI Taxes HL/IT1 3 ODTM Service Dates HL/IT1 2 O

Loop HL/IT1/QTY 1 OQTY Number of Lines In Service HL/IT1/QTY 1 OSI Rate State HL/IT1/QTY 1 O

Loop HL/IT1/ITA 2 OITA Surcharges/Allowances HL/IT1/ITA 1 M


Detail Area

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!


Detail Area

April 2003 21

3.2.4 Billing Structures (Levels 5 - 9)

Because of the diverse nature of the supporting detail associated with the variousservices that are billed, several billing structures are necessary. In order to simplifycoding efforts on the receiving side of the 811, the same billing structure is used toprovide supporting detail for several different services.

The supporting detail for a summary level charge can be provided in one or moredifferent formats. This is usually a result of different regulatory bodies requesting thebilling detail to be structured according to rigid specifications. An example of this ismeasured service, which is billed in an itemized call format in some states and in a bandsummary format in other states. The billing structures (with their associated billingsystem 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 ItemizedCharges.

Structure 2 - Band Usage (CRIS Billing System)

This structure is used to provide supporting detail on services which are billed in aband 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 Explanation (Both)

This structure is used to provide Other Charges and Credits (OC&C) supportingdetail.

Structure 6 - Optional Calling Plan Usage (CRIS Billing System)

This structure is used to provide Optional Calling Plan (OCP) supporting detail. OCPdetail 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 - Account Service Information (ASI) (Both Billing Systems)

This structure is used to provide ASI supporting detail.


Detail Area

April 2003 22

Structure 9 - Feature Group A Information (CABS Billing Systems)

This structure is used to provide Feature Group A (ASI) supporting detail.

Structure 10 – Contracts and Discounts (CRIS Billing System)

This structure is used to provide Contracts and Discounts supporting detail.


Detail Area

June 2003 23

3.3 Structure 1 - Itemized Calls / Itemized Charges

This structure is used to provide supporting detail (by station number) for itemized callsand 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”). Thestructure consists of HL 5, HL 6 (where needed to show the billing party for a particularitemized call), HL 8 (for sub-line item detail when applicable) and HL 9.

3.3.1 StructureMax

Segment Segment Description Loop Use O/M

Loop HL >1 MHL Category - HL 5 HL 1 M

Loop HL/LX 1 MLX Sequential Designator HL/LX 1 MSI Station Number HL/LX 1 MREF Account Number HL/LX >1 O

Loop HL/LX/QTY 4 OQTY Quantity of DA Calls HL/LX/QTY 1 MSI Type of DA Calls HL/LX/QTY 1 M

Loop HL >1 OHL Category - HL 6 HL 1 O

Loop HL/NM1 1 ONM1 Name of Secondary Biller HL/NM1 1 MPER Contact # of Secondary Biller HL/NM1 2 O

Loop HL >1 OHL Charge Detail - HL 8 HL 1 O

Loop HL/SLN >1 OSLN Subline Item Detail HL/SLN 1 MSI USOC Code HL/SLN 1 OPID Phrase Text HL/SLN 1 OITA Allowance, Charge, or Service HL/SLN 1 OREF Service Order Number HL/SLN >1 ODTM Date/Time Reference HL/SLN 10 O

Loop HL >1 OQTY Qty of Usage HL/SLN/QTY 1 M


Detail Area

June 2003 24


Loop HL >1 MHL Line Detail - HL 9 HL 1 M

Loop HL/TCD >1 MTCD Call Information HL/TCD 1 MSI Additional information HL/TCD 2 OTXI Tax status information HL/TCD 1 OITA Surcharges/Credits HL/TCD 3 O

Loop HL/USD >1 MUSD Usage Detail HL/USD 1 MSI Additional information HL/USD 2 O


Detail Area

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!


Detail Area

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!


Detail Area

June 2002 27

3.4 Structure 2 - Band Usage

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

3.4.1 Structure



Loop HL/LX 1 MLX Sequential Designator HL/LX 1 MSI Station Number HL/LX 1 M

Loop HL >1 MHL Charge Detail - HL 8 HL 1 M

Loop HL/SLN 1 MSLN Charge information HL/SLN 1 M

Loop HL 1 MHL Line Detail - HL 9 HL 1 M

Loop HL/USD >1 MUSD Usage information HL/USD 1 MSI Usage Characteristics HL/USD 2 O


Detail Area

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!


Detail Area

June 2002 29

3.5 Structure 3 - WATS Usage

This structure is used to provide WATS (IT107 = “1000”) supporting detail. Due to theamount and diversity of information being provided, this structure is complex. TheCategory level (HL 5) contains general information about the WATS number. Under HL5, up to three billing structures can provide supporting detail for a given WATS number. The first structure provides supporting charge detail; the second structure providessupporting line usage information for each working number under the main WATSnumber; and the third structure provides supporting itemized call detail for each of theworking numbers. Not all WATS accounts will provide all levels of detail, therefore thedocumentation will discuss each structure individually.

A WATS comprehensive mapping example is provided after all the structure tables.

3.5.1 Structure (WATS Line Information)



Loop HL/LX 1 MLX Sequential Designator HL/LX 1 MSI WATS Number HL/LX 1 M


Detail Area

June 2002 30

3.5.2 Structure (WATS Charge Information)


Loop HL >1 MHL Charge Detail - HL 8 HL 1 M

Loop HL/SLN 1 MSLN Charge Information HL/SLN 1 MSI Additional Information HL/SLN 1 OITA Adjustment Information HL/SLN 1 ODTM Rate Change Date HL/SLN 1 O

Loop HL/SLN/QTY >1 O QTY Monthly Overflow Count HL/SLN/QTY 1 O


Loop HL/USD >1 M1

USD Charge/Rate Information HL/USD 1 MSI Charge Characteristics HL/USD 2 OTRF Rating factor (MATR) HL/USD 1 O

Loop HL/USD/QTY 5 OQTY Quantity HL/USD/QTY 1 M

1 This loop is used to provide both charge information and the taper table.


Detail Area

June 2002 31

3.5.3 Structure (WATS Working Number Usage)



Loop HL/LX 1 MLX Sequential Designator HL/LX 1 MSI Translated Telephone Number HL/LX 1 M

Loop HL/LX/QTY 6 MQTY Quantity Used HL/LX/QTY 1 MSI Rate Period HL/LX/QTY 1 M

3.5.4 Structure (WATS Itemized Call Detail)


Loop HL >1 OHL Category - HL 5 HL 1 M



Loop HL/TCD >1 MTCD Call Information HL/TCD 1 MSI Additional Information HL/TCD 2 OTXI Tax Information HL/TCD 1 OITA Surcharge/Credit HL/TCD 3 O

This structure is similar to structure 1.


Detail Area

June 2002 32

3.5.5 Sample MappingHL~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!


Detail Area

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


Loop HL 1 MHL Category - HL 5 HL 1 M

Loop HL/LX 1 MLX Sequential Designator HL/LX 1 MSI Billing Number HL/LX 1 M

Loop HL 1 MHL Charge Detail - HL 8 HL 1 M

Loop HL/SLN >1 MSLN Usage and charge information HL/SLN 1 MSI Type of DA HL/SLN 1 MITA DA Credits HL/SLN 1 O

Loop HL/SLN/QTY 1 OQTY Calls at no charge HL/SLN/QTY 1 M


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!


Detail Area

April 2003 34

3.7 Structure 5 - Other Charges and Credits Explanation

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

3.7.1 Structure



Loop HL/LX 1 MLX Sequential Designator HL/LX 1 MSI Type of Charge HL/LX 1 OREF Charge Reference Number HL/LX 3 ODTM Completion Date HL/LX 1 O

Loop HL/NM1 1 ONM1 Order Contact Information HL/NM1 1 MN3 Street Address HL/NM1 1 ON4 City, State, Zip HL/NM1 1 O

Loop HL >1 MHL Sub-Category - HL 6 HL 1 M

Loop HL/LX 1 MLX Sequential Designator HL/LX 1 MSI Telephone/Circuit Number HL/LX 1 M


Loop HL/SLN >1 MSLN Usage and Charge Information HL/SLN 1 MSI Type of Charge HL/SLN 1 MPID Description of Charge HL/SLN 10 OINC Payment Status HL/SLN 1 OTXI Tax Information HL/SLN 3 OREF Charge Reference Number HL/SLN 1 ODTM Service Dates HL/SLN 2 OAMT Monthly Rate HL/SLN 2 O

Loop HL/SLN/NM1 >1 ONM1 Carrier Information HL/SLN/NM1 1 M


Detail Area

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!


Detail Area

October 2002 36

3.8 Structure 6 - Optional Calling Plan Usage

This structure is used to provide supporting detail for optional calling plans. Optionalcalling plan detail is provided under the itemized call total (IT107 = “0500”), but isdistinguished with a SLN loop where SLN10 = “0800”. Optional calling plan detail isprovided in one of two formats depending on the type of plan.

One format involves a Block of Time Allowance which could include additional callingtime being applied against a set rate. The block of time allowance and the actualamount of calling time used will be provided within a SLN loop. If a set rate foradditional calling time is included in the plan and the actual amount of calling time isgreater than the block of time allowance, the billed amount associated with theadditional 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, USD06will provide the additional calling time and the product of USD03 x USD06 will providethe billed amount in USD08.

The second format involves a Percentage Discount being applied to a group ofqualifying calls. The billed amount after discount is provided in a SLN loop. The USDloop is always present for this format and provides the billed amount before discount inUSD08 and an ITA segment will follow to provide the discount amount.


Detail Area

October 2002 37

3.8.1 Structure



Loop HL/LX 1 MLX Sequential Designator HL/LX 1 MSI Billing Number HL/LX 1 M


Loop HL/SLN >1 MSLN Plan Charge Information HL/SLN 1 MSI USOC HL/SLN 2 OPID Description of Calling Plan HL/SLN 1 O

Loop HL/SLN/QTY 1 OQTY Plan Time Information HL/SLN/QTY 1 O


Loop HL/USD >1 MUSD Usage and Charge Information HL/USD 1 MSI Usage Characteristics HL/USD 2 OITA Discounts and Credits HL/USD 1 O


Detail Area

October 2002 38


Block of Time with AllowanceHL~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 DiscountHL~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!


Detail Area

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 verycomplex. The Category level (HL 5) contains general information about the CommonLine 800 number. Under HL 5, up to three sub-billing structures can provide supportingdetail for a given Common Line 800 number. The first structure provides a summary ofusage for each Point of Billing (POB) number under an 800 number. The secondstructure provides a summary of usage for the 800 number. The last structure providesitemized call detail for each POB number under the 800 number.

Not all Common Line 800 accounts are provided with this level of detail, therefore thedocumentation will discuss each structure individually.

Accounts with more than one 800 number should note that the Itemized Call Detailstructures are provided after all 800 Number Point of Billing Summary and 800 NumberSummary structures.

A Common Line 800 comprehensive mapping example is provided after all the structuretables.

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



Loop HL/LX 1 MLX Sequential Designator HL/LX 1 MSI 800 Number HL/LX 1 M


Loop HL/LX >1 MLX Sequential Designator HL/LX 1 MSI Point of Billing Number HL/LX 1 MPID Plan Name HL/LX 1 ODTM Rate Change Date HL/LX 1 O

Loop HL/LX/QTY >1 OQTY Quantity HL/LX/QTY 1 MSI Rate Period HL/LX/QTY 1 M


Detail Area

June 2002 40

Structure (800 Number Point of Billing Summary) - continued


Loop HL >1 OHL MATR Application - HL 6 HL 1 M

Loop HL/LX >1 OLX Sequential Designator HL/LX 1 MSI Rate Period and USOC HL/LX 1 OPID Plan Name HL/LX 1 O

Loop HL >1 OHL MATR - HL 9 HL 1 M

Loop HL/USD >1 OUSD Charge Information HL/USD 1 MSI Charge Characteristics HL/USD 1 OTRF Rating Factor (MATR) HL/USD 1 O

Loop HL/USD/QTY >5 OQTY Quantity HL/USD/QTY 1 M


Detail Area

June 2002 41

3.9.2 Structure (800 Number Summary)




Loop HL >1 MHL Usage Summary - HL 8 HL 1 M

Loop HL/SLN >1 OSLN Charge Information HL/SLN 1 MSI Rate Change Information HL/SLN 1 OPID Plan Name HL/SLN 1 ODTM Relevant Plan Date HL/SLN 2 O

Loop HL/SLN/QTY >1 OQTY Quantity HL/SLN/QTY 1 O

Loop HL >1 MHL Detail - HL 9 HL 1 M

Loop HL/USD >1 OUSD Charge/Rate Information HL/USD 1 MSI Charge/Rate Characteristics HL/USD 1 OQTY Quantity HL/USD/QTY 1 M

Loop HL >1 OHL Discounts - HL 8 HL 1 M

Loop HL/SLN >1 OSLN Discount Information HL/SLN 1 MPID Plan Name HL/SLN 1 OITA Discount HL/SLN 1 O


Detail Area

June 2002 42

3.9.3 Structure (Common Line 800 Itemized Call Detail)


Loop HL >1 OHL Category - HL 5 HL 1 M



Loop HL/TCD >1 MTCD Call Information HL/TCD 1 MSI Additional Information HL/TCD 2 OTXI Tax Information HL/TCD 1 OITA Surcharge/Credit HL/TCD 3 O


Detail Area

June 2002 43

3.9.4 Structure (Common Line 800 – Postalized Rates)





Loop HL/LX 1 MLX Sequential Designator HL/LX 1 MSI Point of Billing Number HL/LX 1 M

Loop HL/LX/QTY >1 MQTY Quantity HL/LX/QTY 1 MSI USOC HL/LX/QTY 1 O


Loop HL/TCD >1 MTCD Call Information HL/TCD 1 MSI Additional Information HL/TCD 2 O

Loop HL 1 MHL Discounts - HL 8 HL 1 O

Loop HL/SLN 1 MSLN Discount Information HL/SLN 1 MSI USOC HL/SLN 1 OITA Discount HL/SLN 1 O

Loop HL 1 MHL Detail - HL 9 HL 1 M

Loop HL/USD 1 MUSD Charge/Rate Information HL/USD 1 M


Detail Area

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!

HL~23~20~8~1! SLN~3.0~~I~1~M4~.4~~I!


Detail Area

June 2002 45

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!


Detail Area

June 2002 46

3.10 Structure 8 - Account Service Information

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

3.10.1 StructureMax



Loop HL/LX 1 MLX Sequential Designator HL/LX 1 MSI Telephone/Circuit Number HL/LX 1 MPID Circuit Location Information HL/LX 10 O


Loop HL/SLN >1 MSLN Charge Information HL/SLN 1 MSI Type of Charge HL/SLN 2 MPID Circuit Location Information HL/SLN 10 OITA Allowance, Charge or Service HL/SLN 10 OREF Reference Identification HL/SLN >1 O DTM Service Dates HL/SLN 2 OMSG Informational Text HL/SLN >1 O

Loop HL/SLN/QTY >1 OQTY Quantity HL/SLN/QTY 1 O

Loop HL/SLN/NM1 >1 ONM1 Name and Address Information HL/SLN/NM1 1 M


Loop HL/USD >1 MUSD Usage (mileage) information HL/USD 1 MSI Usage Characteristics HL/USD 1 O


Detail Area

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!


Detail Area

June 2002 48

3.11 Structure 9 - Feature Group A

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

3.11.1 Structure



Loop HL/LX 1 MLX Sequential Designator HL/LX 1 MSI Recording Number/Office HL/LX 1 M


Loop HL/SLN >1 MSLN Charge Information HL/SLN 1 M


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!


Detail Area

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



Loop HL/SLN >1 MSLN Charge Information HL/SLN 1 MSI Type of Charge HL/SLN 1 MPID Discount Plan Information HL/SLN 2 ODTM 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!


Summary Area

June 2002 50

4 Summary AreaThe purpose of the summary area of the 811 is to provide a summary of the amountcharged for services rendered (TDS segment) and to give an account status (ITA andBAL loops). This area also provides check numbers for the transaction set.

4.1 StructureMax


TDS Charge for Services Rendered N/A 1 M

Loop ITA 5 OITA Refund and Transfer Amounts ITA 1 M

Loop BAL 6 MBAL Account Status BAL 1 O

Loop N1 >1 ON1 Service Provider N1 1 MBAL Essential (Deniable) Charges N1 1 O

Loop N1/ITA 1 O1

ITA Adjustment Amounts N1/ITA 1 MDTM Adjustment Date N1/ITA 1 O

CTT Transaction Totals N/A 1 MSE 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!


Consolidated 811

October 2002 51

5 Consolidated 811The Consolidated 811 is very similar to single account 811. The exceptions are notedbelow:

• The Consolidated Billing Account (CBA) number (from the consolidated 811) isused for payment. Subordinate account information is provided in a Subordinate811 Invoice (this is also referred to as a “Memo 811”).

• For a Consolidated 811 Invoice, BIG07 may have the value of “CD” (ConsolidatedDebit 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 asnormal for the Consolidated 811 Invoice. It is not provided for the Subordinate 811invoice.

• DTM segments are not provided for the Consolidated 811 Invoice. The invoiceperiod 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 inthe Heading Area of the Consolidated 811 Invoice. These segments are provided inthe Heading Area of each Subordinate 811 Invoice if needed.

• There will be a REF segment in the Heading Area of the Consolidated 811 Invoicewith REF01 = “12” to provide the Billing Account Number. This is consistent with allother 811 formats provided by the SBC operating companies in Missouri,Oklahoma, Kansas, Arkansas and Texas.

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

§ If there is detailed billing information associated with the Consolidated 811 Invoiceitself (late payment charges or other charges, credits and information), a REFsegment at HL 2 with REF01 = “14” will uniquely indicate the Consolidated BillingAccount (CBA) number. Similarly, a REF segment at HL 2 with REF01 = “11” willindicate a Subordinate Account number within the Consolidated 811 Invoice.

• For each Subordinate 811 Invoice, there will be a REF segment in the HeadingArea with REF01 = “12” to indicate the Subordinate Account number.

• The Consolidated 811 Invoice will provide summary information for eachSubordinate 811 Invoice as shown in the structure table that follows. The onlythree values provided in IT107 are “0110”, “0400”, and “0500”.


Consolidated 811

October 2002 52

5.1 Structure - Consolidated Account Summary


Loop HL >1 MHL Billing Arrangement - HL 2 HL 1 M

Loop HL/LX 1 MLX Sequential Designator HL/LX 1 MSI Site ID HL/LX 1 OREF Account Number HL/LX 1 MAMT Account Total HL/LX 1 MTXI Tax Information HL/LX 2 O

Loop HL/LX/ITA 1 OITA Account Adjustment HL/LX/ITA 1 M

Loop HL 1 MHL Group - HL 4 HL 1 M

Loop HL/IT1 >1 MIT1 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!


Auditing the 811

June 2002 53

6 Auditing the 811To help ensure that both the SBC operating company in Missouri, Oklahoma, Kansas,Arkansas or Texas and the customer are interpreting the charges and credits in the 811in a consistent manner, the 811 that is sent to customers is audited. The auditsperformed are detailed in this section. Each transaction set is balanced using the rulesoutlined 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 inthe detail area of the 811.

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

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

6.1 Rules of Extended Pricing

When processing certain segments which contain a quantity and a unit price, the totalamount being provided by that segment must be derived. This involves multiplyingquantity 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 Unitof Measurement Code (DE355) and that data element contains the value “M4”(Monetary Value), then rules of extended pricing do not apply for that segment. Thismeans that when the “M4” value is used, the unit price is the total charge or credit forthe 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 monetaryamount that a segment provides after:

1) Extended pricing rules have been applied.

2) Relational checks have been performed to ensure that the monetary amount isnot being supplied for informational purposes only.

Certain segments contain both an amount and a code value identifying whether theamount is a credit or a charge. The TCIF 811 Implementation Guide states that withinthe 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; theyhave no impact on the sign interpretation.

The following pages discuss how to determine the segment amount of each “money”segment.


Auditing the 811

June 2002 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 exemptfrom certain types of taxes. It can also be also used in the detail area to show that anitemized 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.


Auditing the 811

June 2002 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 thesegment 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. Inthis use, USD01 would equal “O”.

Note 1: When both USD03 and USD08 are populated, the amount in USD08 takesprecedence 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 befound in an SI pair (DE 1000 = ‘PU’) within the SLN loop, when it is present.


Auditing the 811

June 2002 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 811can be found within the TCIF 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 Modeloverview which provides the summing rules for balancing the 811 transaction set.



Technical Specifications

June 2002 57

7 Technical Specifications

811 Consolidated Service Invoice/Statement

Functional Group ID=CIIntroduction:

This Draft Standard for Trial Use contains the format and establishes the data contents of theConsolidated Service Invoice/Statement Transaction Set (811) for use within the context of an ElectronicData Interchange (EDI) environment. This transaction set provides for the billing or reporting of complexand structured service invoice/statement detail. This standard can be used by organizations who areinterested in sending or receiving either consolidated or standalone invoices for service arrangementswhich require processing other than that done for the typical product invoice. The Consolidated ServiceInvoice/Statement can be used as a credit/debit memo to differentiate between payable invoice items andinformation-only memo items. This transaction set should not be used as a standalone notification of acredit/debit adjustment.

Notes:

Only the segments and data elements that are provided by our implementation of this transaction set areprinted. While we do provide all X12 syntax notes and semantic notes associated with segments wegenerate 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.



June 2002 58

Heading:

Pos. Seg. Req. Loop Notes andNo. 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 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



June 2002 59

Detail:


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


060 AMT Monetary Amount O 5



LOOP ID - QTY 10

090 QTY Quantity O 1


LOOP ID - NM1 1

110 NM1 Individual or Organizational Name O 1 n2


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



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



Not Used 240 INC Installment Information O 1


Not Used 260 REF Reference Identification O 8


Not Used 280 MSG Message Text O >1

Not Used 285 AMT Monetary Amount O 1



June 2002 60

LOOP ID - QTY >1



LOOP ID - ITA 10



Not Used 330 TXI Tax Information O >1

LOOP ID - NM1 >1

Not Used 340 NM1 Individual or Organizational Name O 1


Not Used 360 N3 Address Information O 2

Not Used 370 N4 Geographic Location O 1


Not Used 385 NX2 Location ID Component O >1 n4


LOOP ID - SLN >1

390 SLN Subline Item Detail O 1 n5





430 INC Installment Information O 1






490 AMT Monetary Amount O 15

500 MSG Message Text O >1

LOOP ID - QTY >1



LOOP ID - NM1 >1

530 NM1 Individual or Organizational Name O 1


Not Used 550 N3 Address Information O 2

Not Used 560 N4 Geographic Location O 1






June 2002 61

LOOP ID - TCD >1

590 TCD Itemized Call Detail O 1 n6



615 ITA Allowance, Charge or Service O >1

LOOP ID - QTY >1

Not Used 617 QTY Quantity O 1


LOOP ID - USD >1

620 USD Usage Sensitive Detail O 1 n7



640 TRF Rating Factors O 18

LOOP ID - QTY >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 700 PCT Percent Amounts O 5

LOOP ID - LQ >1

Not Used 710 LQ Industry Code O 1


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



June 2002 62

Summary:


M 010 TDS Total Monetary Value Summary M 1

LOOP ID - ITA >1




LOOP ID - BAL >1

040 BAL Balance Detail O 1


LOOP ID - N1 >1

060 N1 Name O 1

LOOP ID - BAL >1

070 BAL Balance Detail O 1


LOOP ID - ITA >1







LOOP ID - LX >1

Not Used 107 LX Assigned Number O 1


LOOP ID - AMT >1



LOOP ID - ITA >1

Not Used 111 ITA Allowance, Charge or Service 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/BillingProvider (Identifies the Company Providing the Service/Billing) 2 - Billing Arrangement (Identifies aSpecific Billing Arrangement) 3 - Sub-billing Arrangement (Identifies a More Detailed BillingArrangement) 4 - Group (Identifies a Group of Charges on the Bill) 5 - Category (Identifies theSubdivision 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 ofCharges within a Billing Arrangement) 9 - Line Detail (Identifies the Supporting Detail Associatedwith the Charge or Group Level) They must be used in the (hierarchical) order in which they arelisted; however, certain levels are optional and may be omitted. At least one occurrence each of theservice/billing provider level and group level is required.



June 2002 63

2. When used for telecommunications billing, the service/billing provider level is defined by the NM1loop.

3. The group level is defined by at least one occurrence of the IT1 loop which may only appear at thegroup 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 HeaderPosition: 010

Loop:Level: Heading

Usage: MandatoryMax Use: 1Purpose: 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 SummaryRef. DataDes. Element Name Attributes

M ST01 143 Transaction Set Identifier Code M ID 3/3Code uniquely identifying a Transaction Set

811 Consolidated Service Invoice/StatementM ST02 329 Transaction Set Control Number M AN 4/9

Identifying control number that must be unique within the transaction setfunctional group assigned by the originator for a transaction set



June 2002 65

Segment: BIG Beginning Segment for InvoicePosition: 020

Loop:Level: Heading

Usage: MandatoryMax Use: 1Purpose: To indicate the beginning of an invoice transaction set and transmit identifying

numbers and datesSyntax 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.


M BIG01 373 Date M DT 8/8Date expressed as CCYYMMDD

M BIG02 76 Invoice Number M AN 1/22Identifying number assigned by issuer

NotUsed

BIG03 373 Date O DT 8/8

Date expressed as CCYYMMDDNotUsed

BIG04 324 Purchase Order Number O AN 1/22

Identifying number for Purchase Order assigned by theorderer/purchaser

NotUsed

BIG05 328 Release Number O AN 1/30

Number identifying a release against a Purchase Order previouslyplaced by the parties involved in the transaction

NotUsed

BIG06 327 Change Order Sequence Number O AN 1/8

Number assigned by the orderer identifying a specific change or revisionto a previously transmitted transaction set



June 2002 66

BIG07 640 Transaction Type Code O ID 2/2Code specifying the type of transaction

CD Consolidated Debit InvoiceCE Consolidated Credit InvoiceCF Consolidated Debit MemoCG Consolidated Credit MemoCN Credit InvoiceCR Credit MemoDI Debit InvoiceDR Debit MemoFB Final BillFD Consolidated Invoice, Final BillFE Memorandum, Final BillME Memorandum

NotUsed

BIG08 353 Transaction Set Purpose Code O ID 2/2

Code identifying purpose of transaction setNotUsed

BIG09 306 Action Code O ID 1/2

Code indicating type of actionNotUsed

BIG10 76 Invoice Number O AN 1/22

Identifying number assigned by issuer



June 2002 67

Segment: NTE Note/Special InstructionPosition: 030

Loop:Level: Heading

Usage: OptionalMax Use: 100Purpose: To transmit information in a free-form format, if necessary, for comment or

special instructionSyntax 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 NTEsegment should therefore be avoided, if at all possible, in an automatedenvironment.

Notes: This segment only provided to CheckFree.


NTE01 363 Note Reference Code O ID 3/3Code identifying the functional area or purpose for which the noteapplies

INV Invoice InstructionM NTE02 352 Description M AN 1/80

A free-form description to clarify the related data elements and theircontent



June 2002 68

Segment: REF Reference IdentificationPosition: 050

Loop:Level: Heading

Usage: OptionalMax Use: >1Purpose: 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:


M REF01 128 Reference Identification Qualifier M ID 2/3Code qualifying the Reference Identification

12 Billing Account14 Master Account Number6R Provider Control NumberAP Accounts Receivable NumberEH Financial Classification Code

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

NotUsed

REF03 352 Description X AN 1/80


NotUsed

REF04 C040 Reference Identifier O

To identify one or more reference numbers or identification numbers asspecified by the Reference Qualifier

NotUsed

C04001 128 Reference Identification Qualifier M ID 2/3

Code qualifying the Reference IdentificationNotUsed

C04002 127 Reference Identification M AN 1/30

Reference information as defined for a particular Transaction Set or asspecified by the Reference Identification Qualifier



June 2002 69

NotUsed

C04003 128 Reference Identification Qualifier X ID 2/3


C04004 127 Reference Identification X AN 1/30


NotUsed







October 2002 70

Segment: ITD Terms of Sale/Deferred Terms of SalePosition: 070

Loop:Level: Heading

Usage: OptionalMax Use: 5Purpose: 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 latepayment charge.

Comments: 1 If the code in ITD01 is "04", then ITD07 or ITD09 is required and either ITD10or ITD11 is required; if the code in ITD01 is "05", then ITD06 or ITD07 isrequired.

Data Element SummaryRef. DataDes. Element Name AttributesITD01 336 Terms Type Code O ID 2/2

Code identifying type of payment terms03 Fixed Date10 Instant18 Fixed Date, Late Payment Penalty Applies

ITD02 333 Terms Basis Date Code O ID 1/2Code identifying the beginning of the terms period

3 Invoice Date5 Invoice Receipt Date

NotUsed

ITD03 338 Terms Discount Percent O R 1/6

Terms discount percentage, expressed as a percent, available to thepurchaser if an invoice is paid on or before the Terms Discount DueDate

NotUsed

ITD04 370 Terms Discount Due Date X DT 8/8

Date payment is due if discount is to be earned expressed in formatCCYYMMDD

NotUsed

ITD05 351 Terms Discount Days Due X N0 1/3

Number of days in the terms discount period by which payment is due ifterms discount is earned



October 2002 71

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

NotUsed

ITD07 386 Terms Net Days O N0 1/3

Number of days until total invoice amount is due (discount notapplicable)

NotUsed

ITD08 362 Terms Discount Amount O N2 1/10

Total amount of terms discountNotUsed

ITD09 388 Terms Deferred Due Date O DT 8/8

Date deferred payment or percent of invoice payable is due expressedin format CCYYMMDD

NotUsed

ITD10 389 Deferred Amount Due X N2 1/10

Deferred amount due for paymentNotUsed

ITD11 342 Percent of Invoice Payable X R 1/5

Amount of invoice payable expressed in percentNotUsed

ITD12 352 Description O AN 1/80


NotUsed

ITD13 765 Day of Month X N0 1/2

The numeric value of the day of the month between 1 and the maximumday of the month being referenced

ITD14 107 Payment Method Code O ID 1/2Code identifying type of payment procedures

AC Credit CardE Electronic Payment System

NotUsed

ITD15 954 Percent O R 1/10

Percentage expressed as a decimalLate Payment Percentage.



June 2002 72

Segment: DTM Date/Time ReferencePosition: 080

Loop:Level: Heading

Usage: OptionalMax Use: 10Purpose: 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:


M DTM01 374 Date/Time Qualifier M ID 3/3Code specifying type of date or time, or both date and time

186 Invoice Period Start187 Invoice Period End

DTM02 373 Date X DT 8/8Date expressed as CCYYMMDD

NotUsed

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)

NotUsed

DTM04 623 Time Code O ID 2/2

Code identifying the time. In accordance with International StandardsOrganization standard 8601, time can be specified by a + or - and anindication in hours in relation to Universal Time Coordinate (UTC) time;since + is a restricted character, + and - are substituted by P and M inthe codes that follow

NotUsed

DTM05 1250 Date Time Period Format Qualifier X ID 2/3

Code indicating the date format, time format, or date and time formatNotUsed

DTM06 1251 Date Time Period X AN 1/35

Expression of a date, a time, or range of dates, times or dates andtimes



June 2002 73

Segment: TXI Tax InformationPosition: 090

Loop:Level: Heading

Usage: OptionalMax Use: >1Purpose: 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:


M TXI01 963 Tax Type Code M ID 2/2Code specifying the type of tax

FT Federal Excise TaxLS State and Local Sales TaxMP Municipal Tax

NotUsed

TXI02 782 Monetary Amount X R 1/18

Monetary amountNotUsed

TXI03 954 Percent X R 1/10

Percentage expressed as a decimalNotUsed

TXI04 955 Tax Jurisdiction Code Qualifier X ID 2/2

Code identifying the source of the data used in tax jurisdiction codeNotUsed

TXI05 956 Tax Jurisdiction Code X AN 1/10

Code identifying the taxing jurisdictionTXI06 441 Tax Exempt Code X ID 1/1

Code identifying exemption status from sales and use tax1 Yes (Tax Exempt)

TXI07 662 Relationship Code O ID 1/1Code indicating the relationship between entities

O Information Only



June 2002 74

NotUsed

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

NotUsed

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 certificatenumber

NotUsed

TXI10 350 Assigned Identification O AN 1/20

Alphanumeric characters assigned for differentiation within a transactionset



June 2002 75

Segment: N1 NamePosition: 100

Loop: N1 OptionalLevel: Heading

Usage: OptionalMax Use: 1Purpose: 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 processingparty.

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


M N101 98 Entity Identifier Code M ID 2/3Code identifying an organizational entity, a physical location, property oran individual

PE PayeePR Payer

N102 93 Name X AN 1/60Free-form name

N103 66 Identification Code Qualifier X ID 1/2Code designating the system/method of code structure used forIdentification Code (67)

1 D-U-N-S Number, Dun & Bradstreet91 Assigned by Seller or Seller's Agent

N104 67 Identification Code X AN 2/80Code identifying a party or other codeIf N103 = "91" - Use Telecordia CIC list.

NotUsed

N105 706 Entity Relationship Code O ID 2/2

Code describing entity relationshipNotUsed

N106 98 Entity Identifier Code O ID 2/3

Code identifying an organizational entity, a physical location, property oran individual



June 2002 76

Segment: N3 Address InformationPosition: 120


Usage: OptionalMax Use: 2Purpose: To specify the location of the named party

Syntax Notes:Semantic Notes:

Comments:


M N301 166 Address Information M AN 1/55Address information

N302 166 Address Information O AN 1/55Address information



June 2002 77

Segment: N4 Geographic LocationPosition: 130


Usage: OptionalMax Use: 1Purpose: 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 beadequate to specify a location.

2 N402 is required only if city name (N401) is in the U.S. or Canada.

Data Element SummaryRef. DataDes. Element Name AttributesN401 19 City Name O AN 2/30

Free-form text for city nameN402 156 State or Province Code O ID 2/2

Code (Standard State/Province) as defined by appropriate governmentagency

N403 116 Postal Code O ID 3/15Code defining international postal zone code excluding punctuation andblanks (zip code for United States)

NotUsed

N404 26 Country Code O ID 2/3

Code identifying the countryNotUsed

N405 309 Location Qualifier X ID 1/2

Code identifying type of locationNotUsed

N406 310 Location Identifier O AN 1/30

Code which identifies a specific location



June 2002 78



Usage: OptionalMax Use: 12Purpose: To specify identifying information





VR Vendor ID NumberREF02 127 Reference Identification X AN 1/30


CABS Customer Access Billing System BillCRIS Customer Records Information System Bill

NotUsed



NotUsed



NotUsed







June 2002 79

NotUsed





NotUsed







June 2002 80

Segment: HL Hierarchical LevelPosition: 010

Loop: HL MandatoryLevel: Detail

Usage: MandatoryMax Use: 1Purpose: To identify dependencies among and the content of hierarchically related groups

of data segmentsSyntax 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, andpackaging 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 theHL segment in the transaction set. For example, HL01 could be used toindicate the number of occurrences of the HL segment, in which case thevalue of HL01 would be "1" for the initial HL segment and would beincremented by one in each subsequent HL segment within the transaction.

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

4 HL03 indicates the context of the series of segments following the current HLsegment up to the next occurrence of an HL segment in the transaction. Forexample, HL03 is used to indicate that subsequent segments in the HL loopform a logical grouping of data referring to shipment, order, or item-levelinformation.

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


M HL01 628 Hierarchical ID Number M AN 1/12A unique number assigned by the sender to identify a particular datasegment in a hierarchical structure

HL02 734 Hierarchical Parent ID Number O AN 1/12Identification number of the next higher hierarchical data segment thatthe data segment being described is subordinate to



June 2002 81

M HL03 735 Hierarchical Level Code M ID 1/2Code defining the characteristic of a level in a hierarchical structure

1 Service/Billing Provider2 Billing Arrangement4 Group5 Category6 Sub-Category8 Charge Detail9 Line Detail

HL04 736 Hierarchical Child Code O ID 1/1Code indicating if there are hierarchical child data segmentssubordinate to the level being described

0 No Subordinate HL Segment in This HierarchicalStructure.

1 Additional Subordinate HL Data Segment in ThisHierarchical Structure.



June 2002 82

Segment: LX Assigned NumberPosition: 020

Loop: LX OptionalLevel: Detail

Usage: OptionalMax Use: 1Purpose: To reference a line number in a transaction set


Comments:


M LX01 554 Assigned Number M N0 1/6Number assigned for differentiation within a transaction set



June 2002 83

Segment: SI Service Characteristic IdentificationPosition: 030


Usage: OptionalMax Use: 8Purpose: 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 AgencyQualifier Code and the other 20 data elements are matched pairs, which will bereferred to SI02/SI03 pairs. Each matched pair provides DE-1000 and DE-234codes/values. There can be up to ten pairs on each SI segment.


M SI01 559 Agency Qualifier Code M ID 2/2Code identifying the agency assigning the code values

TI Telecommunications IndustryM SI02 1000 Service Characteristics Qualifier M AN 2/2

Code from an industry code list qualifying the type of servicecharacteristicsOne or more of the following DE1000 values and it’s associated DE234value may be present within the SI segment.

CH Charge/Usage Status CodeRP Rate PeriodSP Special Billing/Payment Commitment Plan

M SI03 234 Product/Service ID M AN 1/48Identifying number for a product or serviceFor a list of valid DE234 values associated with the preceeding DE1000values, see 10.4 Additional Code Lists Used by TCIF within the TCIFTelephone 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/2Code from an industry code list qualifying the type of servicecharacteristicsOne or more of the following DE1000 values and it’s associated DE234value may be present within the SI segment.

BN Billing Telephone NumberBT Basic Service TypeCC Calling Card NumberCI Circuit Drop Location CodeCN Circuit NumberDI Department CodeFC Facility Complement CodeFI Facility Interface CodeLO Local Exchange Carrier Serving OfficePU Percent of Interstate UsageSG Service GroupSI Circuit Number Special IDTK Trunk NumberTN Telephone NumberTX Translated Telephone NumberWN Wide Area Telephone Service (WATS) Line Number

SI05 234 Product/Service ID X AN 1/48Identifying number for a product or serviceThis element will contain a locally defined code associated with one ofthe preceeding DE1000 values. Examples of a locally defined valueinclude a telephone number, Class of Service USOC, calling cardnumber,circuit number, etc.

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

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





June 2002 85















June 2002 86

Segment: PID Product/Item DescriptionPosition: 040


Usage: OptionalMax Use: 200Purpose: 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 beingreferred 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.


M PID01 349 Item Description Type M ID 1/1Code indicating the format of a description

F Free-formX Semi-structured (Code and Text)

NotUsed

PID02 750 Product/Process Characteristic Code O ID 2/3

Code identifying the general class of a product or process characteristicPID03 559 Agency Qualifier Code X ID 2/2

Code identifying the agency assigning the code valuesAS Assigned by Seller

PID04 751 Product Description Code X AN 1/12A code from an industry code list which provides specific data about aproduct characteristic

CI Circuit Drop LocationDP Different Premises Address



June 2002 87

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

NotUsed

PID06 752 Surface/Layer/Position Code O ID 2/2

Code indicating the product surface, layer or position that is beingdescribed

NotUsed

PID07 822 Source Subqualifier O AN 1/15

A reference that indicates the table or text maintained by the SourceQualifier

NotUsed

PID08 1073 Yes/No Condition or Response Code O ID 1/1

Code indicating a Yes or No condition or responseNotUsed

PID09 819 Language Code O ID 2/3

Code designating the language used in text, from a standard code listmaintained by the International Standards Organization (ISO 639)



June 2002 88








11 Account Number14 Master Account NumberCR Customer Reference NumberIV Seller's Invoice NumberOW Service Order NumberPO Purchase Order NumberTF Transfer NumberVN Vendor Order Number


EDI999 Default vendor numberNotUsed



NotUsed





June 2002 89

NotUsed





NotUsed





NotUsed







June 2002 90

Segment: AMT Monetary AmountPosition: 060


Usage: OptionalMax Use: 5Purpose: To indicate the total monetary amount


Comments:


M AMT01 522 Amount Qualifier Code M ID 1/3Code to qualify amount

5 Total Invoice Amount (for Consolidated Bills only)KO Committed AmountPB Billed AmountSC Total Service Charge (for a Service Provider)

M AMT02 782 Monetary Amount M R 1/18Monetary amount

NotUsed

AMT03 478 Credit/Debit Flag Code O ID 1/1

Code indicating whether amount is a credit or debit



June 2002 91








007 Effective193 Period Start194 Period End


NotUsed



NotUsed



NotUsed







June 2002 92







Notes: Utilized in Consolidated Bill mapping.



FT Federal Excise TaxLS State and Local Sales Tax

TXI02 782 Monetary Amount X R 1/18Monetary amount

NotUsed






Code identifying the taxing jurisdictionNotUsed

TXI06 441 Tax Exempt Code X ID 1/1

Code identifying exemption status from sales and use taxTXI07 662 Relationship Code O ID 1/1

Code indicating the relationship between entitiesA AddO Information Only



June 2002 93

NotUsed



NotUsed



NotUsed





June 2002 94

Segment: QTY QuantityPosition: 090

Loop: QTY OptionalLevel: Detail

Usage: OptionalMax Use: 1Purpose: 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:


M QTY01 673 Quantity Qualifier M ID 2/2Code specifying the type of quantity

94 Billable Quantity99 Quantity Used

QTY02 380 Quantity X R 1/15Numeric value of quantity

QTY03 C001 Composite Unit of Measure OTo identify a composite unit of measure

M C00101 355 Unit or Basis for Measurement Code M ID 2/2Code specifying the units in which a value is being expressed, ormanner in which a measurement has been taken

C0 Calls (Messages)HR HoursMJ Minutes

NotUsed

C00102 1018 Exponent O R 1/15

Power to which a unit is raisedNotUsed

C00103 649 Multiplier O R 1/10

Value to be used as a multiplier to obtain a new valueNotUsed

C00104 355 Unit or Basis for Measurement Code O ID 2/2

Code specifying the units in which a value is being expressed, ormanner in which a measurement has been taken



June 2002 95

NotUsed

C00105 1018 Exponent O R 1/15






NotUsed

C00108 1018 Exponent O R 1/15






NotUsed

C00111 1018 Exponent O R 1/15






NotUsed

C00114 1018 Exponent O R 1/15




QTY04 61 Free-Form Message X AN 1/30

Free-form information



June 2002 96











DA Directory AssistanceRP Rate PeriodST Message Service Type





June 2002 97


SC Service Category CodeTL To/Terminating LocationTM To/Terminating Station Telephone Number

SI05 234 Product/Service ID X AN 1/48Identifying number for a product or serviceThis element will contain a locally defined code associated with one ofthe preceeding DE1000 values. Examples of a locally defined valueinclude a USOC, telephone number, etc.











June 2002 98

NotUsed

SI14 1000 Service Characteristics Qualifier X AN 2/2

Code from an industry code list qualifying the type of servicecharacteristics

NotUsed

SI15 234 Product/Service ID X AN 1/48

Identifying number for a product or serviceNotUsed



NotUsed





NotUsed





NotUsed


Identifying number for a product or service



August 2003 99

Segment: NM1 Individual or Organizational NamePosition: 110

Loop: NM1 OptionalLevel: Detail

Usage: OptionalMax Use: 1Purpose: 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.


M NM101 98 Entity Identifier Code M ID 2/3Code identifying an organizational entity, a physical location, property oran individual

9D New Service ProviderEN End UserOB Ordered BySJ Service Provider

M NM102 1065 Entity Type Qualifier M ID 1/1Code qualifying the type of entity

1 Person2 Non-Person Entity3 Unknown

NM103 1035 Name Last or Organization Name O AN 1/35Individual last name or organizational name

NotUsed

NM104 1036 Name First O AN 1/25

Individual first nameNotUsed

NM105 1037 Name Middle O AN 1/25

Individual middle name or initialNotUsed

NM106 1038 Name Prefix O AN 1/10

Prefix to individual nameNotUsed

NM107 1039 Name Suffix O AN 1/10

Suffix to individual name



August 2003 100

NM108 66 Identification Code Qualifier X ID 1/2Code designating the system/method of code structure used forIdentification Code (67)

41 Telecommunications Carrier Identification Code42 Telecommunications Pseudo Carrier Identification

Code91 Assigned by Seller or Seller’s Agent

NM109 67 Identification Code X AN 2/80Code identifying a party or other codeIf NM108 = "41" - Use Telecordia CIC list.If NM108 = "42" - See 10.4 Additional Code Lists, Appendix B Pseudo-CICs provided within the TCIF Telephone Billing Guideline at thefollowing website: http://www.atis.org/atis/tcif/edi/tbwg/5tc54hom.htmIf NM108 = "91" - Use Telecordia CIC list.

NotUsed

NM110 706 Entity Relationship Code X ID 2/2


NM111 98 Entity Identifier Code O ID 2/3





June 2002 101

Segment: N3 Address InformationPosition: 130


Usage: OptionalMax Use: 2Purpose: To specify the location of the named party


Comments:


M N301 166 Address Information M AN 1/55Address information

N302 166 Address Information O AN 1/55Address information



June 2002 102

Segment: N4 Geographic LocationPosition: 140


Usage: OptionalMax Use: 1Purpose: 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 beadequate to specify a location.

2 N402 is required only if city name (N401) is in the U.S. or Canada.

Data Element SummaryRef. DataDes. Element Name AttributesN401 19 City Name O AN 2/30

Free-form text for city nameN402 156 State or Province Code O ID 2/2

Code (Standard State/Province) as defined by appropriate governmentagency

N403 116 Postal Code O ID 3/15Code defining international postal zone code excluding punctuation andblanks (zip code for United States)

NotUsed

N404 26 Country Code O ID 2/3

Code identifying the countryNotUsed

N405 309 Location Qualifier X ID 1/2

Code identifying type of locationNotUsed

N406 310 Location Identifier O AN 1/30

Code which identifies a specific location



June 2002 103



Usage: OptionalMax Use: 2Purpose: To specify identifying information





6R Provider Control NumberCR Customer Reference NumberIV Seller's Invoice Number


NotUsed



NotUsed



NotUsed







June 2002 104

NotUsed





NotUsed







June 2002 105

Segment: PER Administrative Communications ContactPosition: 160


Usage: OptionalMax Use: >1Purpose: To identify a person or office to whom administrative communications should be

directedSyntax 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.



M PER01 366 Contact Function Code M ID 2/2Code identifying the major duty or responsibility of the person or groupnamed

BI Bill Inquiry ContactIC Information ContactMA Maintenance ContactOC Order Contact

PER02 93 Name O AN 1/60Free-form name

PER03 365 Communication Number Qualifier X ID 2/2Code identifying the type of communication number

TE TelephoneUR Uniform Resource Locator (URL)

PER04 364 Communication Number X AN 1/80Complete communications number including country or area code whenapplicable

NotUsed

PER05 365 Communication Number Qualifier X ID 2/2

Code identifying the type of communication numberNotUsed

PER06 364 Communication Number X AN 1/80

Complete communications number including country or area code whenapplicable



June 2002 106

NotUsed

PER07 365 Communication Number Qualifier X ID 2/2

Code identifying the type of communication numberNotUsed

PER08 364 Communication Number X AN 1/80

Complete communications number including country or area code whenapplicable

NotUsed

PER09 443 Contact Inquiry Reference O AN 1/20

Additional reference number or description to clarify a contact number



June 2002 107









CP County/Parish Sales TaxCS City Sales TaxFT Federal Excise TaxGR Gross Receipts TaxLO Local Tax (Not Sales Tax)LS State and Local Sales TaxLT Local Sales Tax (All Applicable Sales Taxes by

Taxing Authority Below the State Level)MP Municipal TaxOT Occupational TaxSE State Excise TaxST State Sales TaxSU Sales and Use TaxTD Telecommunications Device for the Deaf (TDD)

Service Excise TaxTT Telecommunications TaxZB 911-County TaxZC 911-Excise TaxZD 911-State TaxZE 911-TaxZZ Mutually Defined



June 2002 108


NotUsed









Code indicating the relationship between entitiesA AddO Information Only

NotUsed



NotUsed



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



April 2003 109

Segment: ITA Allowance, Charge or ServicePosition: 180

Loop: ITA OptionalLevel: Detail

Usage: OptionalMax Use: 1Purpose: 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.


M ITA01 248 Allowance or Charge Indicator M ID 1/1Code which indicates an allowance or charge for the service specified

A AllowanceC Charge

ITA02 559 Agency Qualifier Code X ID 2/2Code identifying the agency assigning the code values

TI Telecommunications Industry



April 2003 110

ITA03 560 Special Services Code X ID 2/10Code identifying the special service

CA CityCY CountyFD FederalFS Federal & StateIR InterstateLO LocalMP MunicipalSL State & LocalST StateTOL Toll Charge

M ITA04 331 Allowance or Charge Method of Handling Code M ID 2/2Code indicating method of handling for an allowance or charge

04 Credit Customer Account06 Charge to be Paid by Customer

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

NotUsed

ITA06 359 Allowance or Charge Rate O R 1/15

Allowance or Charge Rate per UnitITA07 360 Allowance or Charge Total Amount O N2 1/15

Total dollar amount for the allowance or chargeITA08 378 Allowance/Charge Percent Qualifier O ID 1/1

Code indicating on what basis allowance or charge percent is calculated9 Late Payment Charge Base Amount

ITA09 332 Percent X R 1/6Percent expressed as a percent

ITA10 380 Quantity X R 1/15Numeric value of quantity

ITA11 355 Unit or Basis for Measurement Code X ID 2/2Code specifying the units in which a value is being expressed, ormanner in which a measurement has been taken

M4 Monetary Value



April 2003 111

NotUsed

ITA12 380 Quantity X R 1/15

Numeric value of quantityITA13 352 Description X AN 1/80


ITA14 150 Special Charge or Allowance Code X ID 3/3Code identifying type of special charge or allowance

AAJ AdjustmentsACF Access Charge - FederalACH Access ChargesANB Adjustment for Minimum Charges BillingDDS Deaf and Disabled SurchargeDSC DiscountECL Expanded Local Calling SurchargeESC Emergency ServiceFFA Franchise FeeFUS Federal Universal ServiceGRS Gross Receipts SurchargeLAE One-Time License FeeLNP Long Term Number Portability SurchargeLPC Late payment chargeLSS Lifeline SurchargeMSG Miscellaneous ChargeMUS Municipal SurchargeNPF No PIC federal chargePAD Premium ChargePCC Poison Control SurchargeREE Regulatory FeeROW Rights of Way Use FeeSAP Service Assistance Program SurchargeSER Service ChargeSMS State/Metropolitan Transit Authority SurchargeSTC State SurchargeSUR SurchargeSUS State Universal Service SurchargeVAB Volume DiscountZZZ Mutually Defined



April 2003 112

NotUsed

ITA15 822 Source Subqualifier O AN 1/15


ITA16 662 Relationship Code O ID 1/1Code indicating the relationship between entities

A AddO Information Only

NotUsed

ITA17 355 Unit or Basis for Measurement Code O ID 2/2




October 2002 113

Segment: IT1 Baseline Item Data (Invoice)Position: 210

Loop: IT1 OptionalLevel: Detail

Usage: OptionalMax Use: 1Purpose: To specify the basic and most frequently used line item data for the invoice and

related transactionsSyntax 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., ModelNo., or SKU.

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

Data Element SummaryRef. DataDes. Element Name AttributesIT101 350 Assigned Identification O AN 1/20


IT102 358 Quantity Invoiced X R 1/10Number of units invoiced (supplier units)

IT103 355 Unit or Basis for Measurement Code X ID 2/2Code specifying the units in which a value is being expressed, ormanner in which a measurement has been takenWhen IT103 = "M4" - Rules of extended pricing do not apply.

M4 Monetary Value



October 2002 114

IT104 212 Unit Price X R 1/17Price per unit of product, service, commodity, etc.

NotUsed

IT105 639 Basis of Unit Price Code O ID 2/2

Code identifying the type of unit price for an itemIT106 235 Product/Service ID Qualifier X ID 2/2

Code identifying the type/source of the descriptive number used inProduct/Service ID (234)

SV Service RenderedIT107 234 Product/Service ID X AN 1/48

Identifying number for a product or service0110 Recurring (Consolidated Bills Only)0200 Monthly Service Charge0300 Access0400 OIther Charges and Credits0500 Itemized Calls0520 Itemized Charges/Credits0600 Directory Advertising0700 Usage0705 Measured Service0900 Directory Assistance1000 WATS1460 Customer Owned Pay Telephone1605 Packet Switching (MicroLink)1650 Video Services1830 Extended Area1850 9761870 Additional Calls1880 800 Common Line1990 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/2Code identifying the type/source of the descriptive number used inProduct/Service ID (234)

ZZ Mutually DefinedUsed in place of Telecom Service Type - WJ

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

1 Recurring Charge2 Other Charges3 Usage4 Summary/Combined Charges

NotUsed

IT110 235 Product/Service ID Qualifier X ID 2/2


NotUsed

IT111 234 Product/Service ID X AN 1/48




NotUsed





NotUsed





NotUsed





October 2002 116

NotUsed



NotUsed





NotUsed





NotUsed





NotUsed





June 2002 117













F Free-formNotUsed


Code identifying the general class of a product or process characteristicNotUsed

PID03 559 Agency Qualifier Code X ID 2/2

Code identifying the agency assigning the code valuesNotUsed

PID04 751 Product Description Code X AN 1/12

A code from an industry code list which provides specific data about aproduct characteristic



June 2002 118


NotUsed



NotUsed



NotUsed







June 2002 119









FT Federal Excise TaxLS State and Local Sales Tax


NotUsed









Code indicating the relationship between entitiesO Information Only



June 2002 120

NotUsed



NotUsed



NotUsed





June 2002 121








150 Service Period Start151 Service Period End


NotUsed



NotUsed



NotUsed







June 2002 122








94 Billable Quantity99 Quantity Used




C0 Calls (Messages)T0 Telecommunications Lines in Service

NotUsed

C00102 1018 Exponent O R 1/15






NotUsed

C00105 1018 Exponent O R 1/15

Power to which a unit is raised



June 2002 123

NotUsed





NotUsed

C00108 1018 Exponent O R 1/15






NotUsed

C00111 1018 Exponent O R 1/15






NotUsed

C00114 1018 Exponent O R 1/15








June 2002 124











RT Rate StateM SI03 234 Product/Service ID M AN 1/48

Identifying number for a product or serviceThis element will contain a locally defined code associated with one ofthe preceeding DE1000 values. Examples of a locally defined valueinclude a state used as basis for rate calculation.



June 2002 125

NotUsed



NotUsed





NotUsed





NotUsed





NotUsed





NotUsed





NotUsed





June 2002 126

NotUsed



NotUsed





NotUsed





NotUsed





June 2002 127


Loop: ITA OptionalLevel: Detail







segment.



A AllowanceC Charge


TI Telecommunications IndustryITA03 560 Special Services Code X ID 2/10

Code identifying the special serviceTOL Toll Charge





June 2002 128


NotUsed



Total dollar amount for the allowance or chargeNotUsed

ITA08 378 Allowance/Charge Percent Qualifier O ID 1/1

Code indicating on what basis allowance or charge percent is calculatedNotUsed

ITA09 332 Percent X R 1/6

Percent expressed as a percentNotUsed


Numeric value of quantityNotUsed

ITA11 355 Unit or Basis for Measurement Code X ID 2/2


NotUsed





CCR Concession CreditDSC DiscountECL Expanded Local Calling Surcharge

NotUsed





June 2002 129


A AddI IncludedO Information Only

NotUsed





October 2002 130

Segment: SLN Subline Item DetailPosition: 390

Loop: SLN OptionalLevel: Detail

Usage: OptionalMax Use: 1Purpose: 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 itemnumber. Example: 1.1 or 1A might be used as a subline number to relate tobaseline number 1.

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

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


M SLN01 350 Assigned Identification M AN 1/20Alphanumeric characters assigned for differentiation within a transactionset

NotUsed

SLN02 350 Assigned Identification O AN 1/20




October 2002 131

M SLN03 662 Relationship Code M ID 1/1Code indicating the relationship between entities

I IncludedSLN04 380 Quantity X R 1/15

Numeric value of quantitySLN05 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


C0 Calls (Messages)EA EachM4 Monetary Value

NotUsed

C00102 1018 Exponent O R 1/15






NotUsed

C00105 1018 Exponent O R 1/15






NotUsed

C00108 1018 Exponent O R 1/15



Value to be used as a multiplier to obtain a new value



October 2002 132

NotUsed



NotUsed

C00111 1018 Exponent O R 1/15






NotUsed

C00114 1018 Exponent O R 1/15



Value to be used as a multiplier to obtain a new valueSLN06 212 Unit Price X R 1/17

Price per unit of product, service, commodity, etc.NotUsed

SLN07 639 Basis of Unit Price Code O ID 2/2

Code identifying the type of unit price for an itemSLN08 662 Relationship Code O ID 1/1

Code indicating the relationship between entitiesI IncludedO Information Only

SLN09 235 Product/Service ID Qualifier X ID 2/2Code identifying the type/source of the descriptive number used inProduct/Service ID (234)

SV Service Rendered



October 2002 133

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

0205 Basic Service0225 Mileage Charge0305 Service and Equipment Information0705 Measured Service0800 Optional Call Plan/Discount Plan0900 Directory Assistance1400 Other Voice Services1460 Customer Owned Pay Telephone1610 Electronic Mail/Messaging Service1740 Miscellaneous1820 Voice Mail1880 800 Common Line1950 InWATS/800 Service1960 OutWATS1990 Other Line Charge2110 Contracts/Discounts

NotUsed

SLN11 235 Product/Service ID Qualifier X ID 2/2


NotUsed

SLN12 234 Product/Service ID X AN 1/48




NotUsed





NotUsed





October 2002 134

NotUsed



NotUsed





NotUsed





NotUsed





NotUsed





NotUsed





NotUsed





June 2003 135












June 2003 136

M SI02 1000 Service Characteristics Qualifier M AN 2/2Code from an industry code list qualifying the type of servicecharacteristicsOne or more of the following DE1000 values and it’s associated DE234value may be present within the SI segment.

CH Charge/Usage Status CodeDA Directory AssistanceIA Service Disconnect/Interruption IndicatorMP Meet Point BillingOC Other Charges and Credits Category CodeRY Local/Toll IndicatorSA Service Activity CodeSD Settlement CodeSP Special Billing/Payment Commitment PlanST Message Service TypeTS Type of Signaling





June 2003 137


BA BandCI Circuit Drop Location CodeCN Circuit NumberCT Common Language Segment Number (SFN)CU Channel Pair NumberD7 Multiple Data Mounting Address CodeDT Dialed Telephone NumberFX Pricing Flex BandLO Local Exchange Carrier Serving Office CodeLS Local Serving Office (LSO)NC Network Channel CodeNI Network Channel Interface CodePQ Major Product CodePU Percent of Interstate Usage (PIU)PV Percent of Facility Subject to Ratchet (RP)RT Rate StateSC Service Category CodeSI Circuit Number Special IDSX Two-Six CodeTE Transmission SpeedTK Trunk NumberTX Translated Telephone NumberXR Cross-Reference Number (Drop Location)

SI05 234 Product/Service ID X AN 1/48Identifying number for a product or serviceThis element will contain a locally defined code associated with one ofthe preceeding DE1000 values. Examples of a locally defined valueinclude a telephone number, central office unit, network channel code,percent, USOC, circuit information, etc.



June 2003 138


FD Feature DataSI07 234 Product/Service ID X AN 1/48

Identifying number for a product or serviceCMP ComponentPKG Package


OD Other Charges and Credits Desciption CodeSI09 234 Product/Service ID X AN 1/48

Identifying number for a product or service3875 Contracted Discount For Non-Direct Dialed Intralata4205 Contracted Discount For Vertical Service Usage4206 Contracted Discount For Operator Handled Charges4207 Contracted Discount For AIN Usage4208 Contracted Discount For Directory Assistance4209 Contracted Discount for ISDN Usage4210 Contracted Discount For Private Line Usage4211 Contracted Discount For Line Service Usage4212 Contracted Discount For MTS Usage4213 Contracted Discount For Digline Usage4280 Incollects B&C Refund4285 Contracted Discount For Multipoint Video Usage4286 Contracted Discount For Microlink II Usage4287 Contracted Discount For FX Usage4288 Contracted Discount For Other Usage Charges







June 2003 139











June 2002 140













F Free-formX Semi-structured (Code and Text)

NotUsed


Code identifying the general class of a product or process characteristicPID03 559 Agency Qualifier Code X ID 2/2

Code identifying the agency assigning the code valuesAS Assigned by Seller

PID04 751 Product Description Code X AN 1/12A code from an industry code list which provides specific data about aproduct characteristic

CI Circuit Drop LocationDP Different Premises Address



June 2002 141


NotUsed



NotUsed



NotUsed







June 2002 142

Segment: INC Installment InformationPosition: 430


Usage: OptionalMax Use: 1Purpose: 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:


M INC01 336 Terms Type Code M ID 2/2Code identifying type of payment terms

04 Deferred or InstallmentM INC02 C001 Composite Unit of Measure M



MO MonthsNotUsed

C00102 1018 Exponent O R 1/15






NotUsed

C00105 1018 Exponent O R 1/15






June 2002 143

NotUsed



NotUsed

C00108 1018 Exponent O R 1/15






NotUsed

C00111 1018 Exponent O R 1/15






NotUsed

C00114 1018 Exponent O R 1/15



Value to be used as a multiplier to obtain a new valueM INC03 380 Quantity M R 1/15

Numeric value of quantityIndicates the total number of installments.

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

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



June 2002 144









segment.



A AllowanceC Charge


TI Telecommunications IndustryITA03 560 Special Services Code X ID 2/10

Code identifying the special serviceCY CountyST State





June 2002 145


NotUsed












NotUsed





230 CreditDSC DiscountPMC Prior Month Credit

NotUsed





NotUsed





June 2002 146









FT Federal Excise TaxLS State and Local Sales TaxMP Municipal Tax


NotUsed









Code indicating the relationship between entitiesO Information Only



June 2002 147

NotUsed



NotUsed



NotUsed





June 2003 148








CIR Circuit NumberCT Contract NumberF8 Original Reference NumberOW Service Order Number


NotUsed



NotUsed



NotUsed







June 2003 149

NotUsed





NotUsed







June 2002 150








007 Effective150 Service Period Start151152

Service Period EndEffective Date of Change


NotUsed



NotUsed



NotUsed







June 2002 151

Segment: AMT Monetary AmountPosition: 490


Usage: OptionalMax Use: 15Purpose: To indicate the total monetary amount


Comments:


M AMT01 522 Amount Qualifier Code M ID 1/3Code to qualify amount

AP Amount Prior to FractionalizationAX Previous Price

M AMT02 782 Monetary Amount M R 1/18Monetary amount

NotUsed

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 TextPosition: 500


Usage: OptionalMax Use: >1Purpose: 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 identifiestop of page, advance a line, etc.

2 If MSG02 is "AA - Advance the specified number of lines before print" thenMSG03 is required.

Notes: The segment used to pass free-form information stored on billing system database.


M MSG01 933 Free-Form Message Text M AN 1/264Free-form message text

NotUsed

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 printerNotUsed

MSG03 1470 Number O N0 1/9

A generic number



June 2002 153








01 Discrete Quantity92 Allotted Usage Quantity94 Billable Quantity96 Non-Billable Quantity98 Overflow Quantity99 Quantity Used




C0 Calls (Messages)HR HoursHT Half HourMJ Minutes

NotUsed

C00102 1018 Exponent O R 1/15






June 2002 154

NotUsed



NotUsed

C00105 1018 Exponent O R 1/15






NotUsed

C00108 1018 Exponent O R 1/15






NotUsed

C00111 1018 Exponent O R 1/15






NotUsed

C00114 1018 Exponent O R 1/15








June 2002 155











CH Charge/Usage Status CodeQT Quantity Qualifier





June 2002 156



NotUsed



NotUsed





NotUsed





NotUsed





NotUsed





NotUsed





June 2002 157

NotUsed



NotUsed





NotUsed





NotUsed





June 2002 158

Segment: NM1 Individual or Organizational NamePosition: 530


Usage: OptionalMax Use: 1Purpose: 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.


M NM101 98 Entity Identifier Code M ID 2/3Code identifying an organizational entity, a physical location, property oran individual

CA CarrierIA Installed AtP9 Primary Interexchange Carrier (PIC)

M NM102 1065 Entity Type Qualifier M ID 1/1Code qualifying the type of entity

1 Person2 Non-Person Entity3 Unknown

NM103 1035 Name Last or Organization Name O AN 1/35Individual last name or organizational name

NotUsed

NM104 1036 Name First O AN 1/25

Individual first nameNotUsed

NM105 1037 Name Middle O AN 1/25

Individual middle name or initialNotUsed

NM106 1038 Name Prefix O AN 1/10

Prefix to individual nameNotUsed

NM107 1039 Name Suffix O AN 1/10

Suffix to individual name



June 2002 159

NM108 66 Identification Code Qualifier X ID 1/2Code designating the system/method of code structure used forIdentification Code (67)

41 Telecommunications Carrier Identification CodeZY Temporary Identification Number

NM109 67 Identification Code X AN 2/80Code identifying a party or other codeIf NM108 = "41" - Use Telecordia CIC list.

NotUsed

NM110 706 Entity Relationship Code X ID 2/2


NM111 98 Entity Identifier Code O ID 2/3




June 2002 160

Segment: TCD Itemized Call DetailPosition: 590

Loop: TCD OptionalLevel: Detail

Usage: OptionalMax Use: 1Purpose: 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 timemeasured in seconds or seconds and tenths of seconds.

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


TCD01 350 Assigned Identification O AN 1/20Alphanumeric characters assigned for differentiation within a transactionset

TCD02 373 Date O DT 8/8Date expressed as CCYYMMDD

TCD03 337 Time O TM 4/8Time 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)



June 2002 161

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

A value of "ZZ" indicates any point of origination/termination or servicefor 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 qualifiescould be the name of an aircraft, vessel, vehicle, or service where a calloriginated/terminated or the service was provided.

CC CountryCI CityZZ Mutually Defined

TCD05 310 Location Identifier X AN 1/30Code which identifies a specific location

TCD06 156 State or Province Code O ID 2/2Code (Standard State/Province) as defined by appropriate governmentagency

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

A value of "ZZ" indicates any point of origination/termination or servicefor 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 qualifiescould be the name of an aircraft, vessel, vehicle, or service where a calloriginated/terminated or the service was provided.

CC CountryCI CityZZ Mutually Defined

TCD08 310 Location Identifier X AN 1/30Code which identifies a specific location

TCD09 156 State or Province Code O ID 2/2Code (Standard State/Province) as defined by appropriate governmentagency



June 2002 162

TCD10 739 Measurement Value O R 1/20The value of the measurementThe measurement is in minutes as related to the length of the call. Thisfield can be whole minutes OR whole and tenths of minutes, separatedby the decimal point.Duration of call measured in minutes and tenths of minutes.

TCD11 739 Measurement Value O R 1/20The value of the measurementThe measurement is in seconds as related to the length of the call. Thisfield can be used in conjunction with the TCD10 field of minutes.

TCD12 782 Monetary Amount O R 1/18Monetary amount

NotUsed

TCD13 782 Monetary Amount O R 1/18





Monetary amountTCD16 662 Relationship Code O ID 1/1

Code indicating the relationship between entitiesI IncludedO Information Only



June 2002 163












June 2002 164

M SI02 1000 Service Characteristics Qualifier M AN 2/2Code from an industry code list qualifying the type of servicecharacteristicsOne or more of the following DE1000 values and it’s associated DE234value may be present within the SI segment.

DA Directory AssistanceIA Service Disconnect/Interruption IndicatorMC Mesage/Rate ClassMI Special Message Information Code QualifierML Message DeliveryMT Message TypePS Packet Switching Category CodeRP Rate PeriodRW Regulation IndicatorRY Local/Toll IndicatorSD Settlement CodeST Message Service TypeTJ Terminating User



BA BandDI Department CodeDJ Sub-Department CodeET Electronic Serial NumberFN From NumberSC Service Category CodeTE Transmission SpeedTM To/Terminating Station Telephone Number

SI05 234 Product/Service ID X AN 1/48Identifying number for a product or serviceThis element will contain a locally defined code associated with one ofthe preceeding DE1000 values. Examples of a locally defined valueinclude a telephone number, transmission speed, USOC, etc.




June 2002 165















June 2002 166







June 2002 167









ST State Sales TaxNotUsed

TXI02 782 Monetary Amount X R 1/18







Code identifying the taxing jurisdictionTXI06 441 Tax Exempt Code X ID 1/1

Code identifying exemption status from sales and use tax1 Yes (Tax Exempt)

TXI07 662 Relationship Code O ID 1/1Code indicating the relationship between entities

O Information Only



June 2002 168

NotUsed



NotUsed



NotUsed





June 2002 169



Usage: OptionalMax Use: >1Purpose: To specify allowances, charges, or services






segment.



A AllowanceC Charge


TI Telecommunications IndustryNotUsed

ITA03 560 Special Services Code X ID 2/10

Code identifying the special serviceM ITA04 331 Allowance or Charge Method of Handling Code M ID 2/2

Code indicating method of handling for an allowance or charge04 Credit Customer Account06 Charge to be Paid by Customer



June 2002 170


NotUsed












NotUsed



A free-form description to clarify the related data elements and theircontentIf charge is a transfer state tax, this data element will contain theappropriate state abbreviation code. If code = 'MX', then it is a Mexicansurcharge.


230 CreditOLM Other Line Charge-Mexican PortionPSP Payphone Service Provider SurchargeTRT Transfer State Tax



June 2002 171

NotUsed





NotUsed





June 2002 172

Segment: USD Usage Sensitive DetailPosition: 620

Loop: USD OptionalLevel: Detail

Usage: OptionalMax Use: 1Purpose: To specify usage-sensitive details which qualify for discounts or are subject to

special ratesSyntax 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 isrequired.

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 theassociated 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 rateUSD03 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.


M USD01 662 Relationship Code M ID 1/1Code indicating the relationship between entities

A AddI IncludedO Information Only

USD02 350 Assigned Identification O AN 1/20Alphanumeric characters assigned for differentiation within a transactionset



June 2002 173

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

NotUsed

USD04 954 Percent X R 1/10

Percentage expressed as a decimalUSD05 C001 Composite Unit of Measure X



AH Additional MinutesC0 Calls (Messages)DH MilesHR HoursMJ Minutes

NotUsed

C00102 1018 Exponent O R 1/15






NotUsed

C00105 1018 Exponent O R 1/15






NotUsed

C00108 1018 Exponent O R 1/15






June 2002 174

NotUsed



NotUsed

C00111 1018 Exponent O R 1/15






NotUsed

C00114 1018 Exponent O R 1/15



Value to be used as a multiplier to obtain a new valueUSD06 380 Quantity X R 1/15

Numeric value of quantityUSD07 380 Quantity X R 1/15

Numeric value of quantityUsed to adjust the quantity of usage. If charge is on a "ratchet USOC"(USD14 = CA and USD15 = 3), then this data element contains theratchet factor. If charge is related to a USOC with a "BorderInterconnect Percentage (BIP)", then this data element contains theBIP.

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/18Monetary amount

NotUsed

USD09 610 Amount X N2 1/15

Monetary amountUSD10 C001 Composite Unit of Measure X

To identify a composite unit of measure



June 2002 175


HR HoursNotUsed

C00102 1018 Exponent O R 1/15






NotUsed

C00105 1018 Exponent O R 1/15






NotUsed

C00108 1018 Exponent O R 1/15






NotUsed

C00111 1018 Exponent O R 1/15






June 2002 176

NotUsed



NotUsed

C00114 1018 Exponent O R 1/15



Value to be used as a multiplier to obtain a new valueUSD11 740 Range Minimum X R 1/20

The value specifying the minimum of the measurement rangeIf USD11 is present and USD12 is not present, then the range is open-ended.

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



June 2002 177











CA Carrier Access Line Charge CodeDC Directional CodeIA Service Disconnect/Interruption IndicatorMT Message TypeRP Rate PeriodSD Settlement Code





June 2002 178


BA BandPV Ratchet PercentSC Service CategoryTL To/Terminating LocationTM To/Terminating Station Telephone Number

SI05 234 Product/Service ID X AN 1/48Identifying number for a product or serviceThis element will contain a locally defined code associated with one ofthe preceeding DE1000 values. Examples of a locally defined valueinclude a telephone number, percent, USOC, etc.


BS Billing Structure CodeSI07 234 Product/Service ID X AN 1/48

Identifying number for a product or serviceTA Tapererd RatingTI Tiered Rating









June 2002 179











June 2002 180









segment.



A AllowanceC Charge








June 2002 181


NotUsed





Code indicating on what basis allowance or charge percent is calculatedITA09 332 Percent X R 1/6






NotUsed





230 CreditDSC Discount

NotUsed




A AddNotUsed





June 2002 182

Segment: TRF Rating FactorsPosition: 640


Usage: OptionalMax Use: 18Purpose: To specify rating information used to calculate usage-sensitive charges


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.


M TRF01 673 Quantity Qualifier M ID 2/2Code specifying the type of quantityCode specifying the rating basis (e.g., acknowledged calls) for charge.

AE Minimum Average Time Requirement (MATR) UnitsM TRF02 C001 Composite Unit of Measure M



03 SecondsMJ Minutes

NotUsed

C00102 1018 Exponent O R 1/15








June 2002 183

NotUsed

C00105 1018 Exponent O R 1/15






NotUsed

C00108 1018 Exponent O R 1/15






NotUsed

C00111 1018 Exponent O R 1/15






NotUsed

C00114 1018 Exponent O R 1/15



Value to be used as a multiplier to obtain a new valueM TRF03 380 Quantity M R 1/15

Numeric value of quantityM TRF04 C001 Composite Unit of Measure M

To identify a composite unit of measure



June 2002 184


C0 Calls (Messages)NotUsed

C00102 1018 Exponent O R 1/15






NotUsed

C00105 1018 Exponent O R 1/15






NotUsed

C00108 1018 Exponent O R 1/15






NotUsed

C00111 1018 Exponent O R 1/15






June 2002 185

NotUsed



NotUsed

C00114 1018 Exponent O R 1/15



Value to be used as a multiplier to obtain a new valueM TRF05 380 Quantity M R 1/15

Numeric value of quantity



June 2002 186








94 Billable Quantity99 Quantity UsedAE Minimum Average Time Requirement (MATR) Units




C0 Calls (Messages)HR HoursHT Half HourMJ MinutesUB Telecommunications Lines in Service - AverageUF Usage per Telecommunications Line - Average

NotUsed

C00102 1018 Exponent O R 1/15






June 2002 187

NotUsed



NotUsed

C00105 1018 Exponent O R 1/15






NotUsed

C00108 1018 Exponent O R 1/15






NotUsed

C00111 1018 Exponent O R 1/15






NotUsed

C00114 1018 Exponent O R 1/15








June 2002 188

Segment: TDS Total Monetary Value SummaryPosition: 010

Loop:Level: Summary

Usage: MandatoryMax Use: 1Purpose: 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 thedollar value of TDS01.


M TDS01 610 Amount M N2 1/15Monetary amount

NotUsed

TDS02 610 Amount O N2 1/15





Monetary amount



June 2002 189


Loop: ITA OptionalLevel: Summary







segment.



A AllowanceC Charge





Code indicating method of handling for an allowance or charge03 Vendor Check to Customer04 Credit Customer Account06 Charge to be Paid by Customer



June 2002 190


NotUsed





Code indicating on what basis allowance or charge percent is calculatedITA09 332 Percent X R 1/6






NotUsed





DAB DepositISD Interest on security depositRFD RefundTR1 Transferred charge or credit amount from another

accountTR2 Transferred charge or credit amount to another

accountNotUsed





June 2002 191


A AddNotUsed





June 2002 192








007 EffectiveDTM02 373 Date X DT 8/8

Date expressed as CCYYMMDDNotUsed



NotUsed



NotUsed







June 2002 193

Segment: BAL Balance DetailPosition: 040

Loop: BAL OptionalLevel: Summary

Usage: OptionalMax Use: 1Purpose: To identify the specific monetary balances associated with a particular account


Comments:


M BAL01 951 Balance Type Code M ID 1/2Code indicating the type of balance

A AdjustmentM Current MonthP Previous Month

M BAL02 522 Amount Qualifier Code M ID 1/3Code to qualify amount

BT Bank Reject TotalNA Net AdjustmentPB Billed AmountTP Total payment amountTT Total Transaction Amount

M BAL03 782 Monetary Amount M R 1/18Monetary amount



August 2003 194

Segment: N1 NamePosition: 060

Loop: N1 OptionalLevel: Summary

Usage: OptionalMax Use: 1Purpose: 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 processingparty.

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


M N101 98 Entity Identifier Code M ID 2/3Code identifying an organizational entity, a physical location, property oran individual

87 Pay-to ProviderSJ Service Provider

N102 93 Name X AN 1/60Free-form name

N103 66 Identification Code Qualifier X ID 1/2Code designating the system/method of code structure used forIdentification Code (67)

41 Telecommunications Carrier Identification Code42 Telecommunications Pseudo Carrier Identification

Code91 Assigned to Seller or Seller’s Agent

N104 67 Identification Code X AN 2/80Code identifying a party or other codeIf N103 = "41" - Use Telecordia CIC list.If N103 = "42" - See 10.4 Additional Code Lists, Appendix B Pseudo-CICs provided within the TCIF Telephone Billing Guideline at thefollowing website: http://www.atis.org/atis/tcif/edi/tbwg/5tc54hom.htmIf N103 = "91" - Use Telecordia CIC list.




August 2003 195

NotUsed

N105 706 Entity Relationship Code O ID 2/2


N106 98 Entity Identifier Code O ID 2/3




June 2002 196

Segment: BAL Balance DetailPosition: 070

Loop: BAL OptionalLevel: Summary

Usage: OptionalMax Use: 1Purpose: To identify the specific monetary balances associated with a particular account


Comments:


M BAL01 951 Balance Type Code M ID 1/2Code indicating the type of balance

M Current MonthM BAL02 522 Amount Qualifier Code M ID 1/3

Code to qualify amountMD Minimum Due

M BAL03 782 Monetary Amount M R 1/18Monetary amount



June 2002 197









segment.



A AllowanceC Charge








June 2002 198


NotUsed












NotUsed





AAJ AdjustmentsNotUsed




O Information OnlyNotUsed





June 2002 199

Segment: CTT Transaction TotalsPosition: 115

Loop:Level: Summary

Usage: OptionalMax Use: 1Purpose: 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.


M CTT01 354 Number of Line Items M N0 1/6Total number of line items in the transaction setNumber of IT1 segments in this transaction set.

NotUsed

CTT02 347 Hash Total O R 1/10

NotUsed

CTT03 81 Weight X R 1/10

Numeric value of weightNotUsed

CTT04 355 Unit or Basis for Measurement Code X ID 2/2


NotUsed

CTT05 183 Volume X R 1/8

Value of volumetric measure



June 2002 200

NotUsed

CTT06 355 Unit or Basis for Measurement Code X ID 2/2


NotUsed

CTT07 352 Description O AN 1/80




June 2002 201

Segment: SE Transaction Set TrailerPosition: 120

Loop:Level: Summary

Usage: MandatoryMax Use: 1Purpose: 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.


M SE01 96 Number of Included Segments M N0 1/10Total number of segments included in a transaction set including STand SE segments

M SE02 329 Transaction Set Control Number M AN 4/9Identifying control number that must be unique within the transaction setfunctional group assigned by the originator for a transaction set

Date post:	04-Aug-2020
Category:	Documents
Upload:	others
View:	2 times
Download:	0 times

811 Transaction Set (Version/Release 004010)€¦ · services. As a member of ETB, the SBC...

Documents