811 transaction set (x12 version 004010) - granite guard€¦ · 1 overview _____ 4 1.1 schedule of...

811 Transaction Set (X12 Version 004010)

Beta Revision 1.05

Mar 01, 2004

1 Overview ____________________________________________________________ 4

1.1 Schedule of 811 Versions ___________________________________________ 4

1.2 Structure of the 811 _______________________________________________ 4

1.3 Format of Guide __________________________________________________ 6

1.4 Bill and Transaction Formats Provided _______________________________ 6

1.5 Referencing Charges When Contacting Granite ________________________ 7

1.6 Taxes, Surcharges and Fees _________________________________________ 7

1.7 Data Element Separator and Segment Terminator______________________ 7

1.8 Functional Group Information ______________________________________ 7

1.9 Understanding Hierarchical Level (HL) Segments ______________________ 8

2 Heading Area _______________________________________________________ 10

2.1 Structure _______________________________________________________ 10

2.2 Sample Mapping _________________________________________________ 10

3 Detail Area__________________________________________________________ 11

3.1 Summary 811____________________________________________________ 11 3.1.1 Accounts Payable 811 __________________________________________ 11 3.1.2 Consolidated Billing Account Summary 811 ________________________ 11 3.1.5 Structure (HL1) _______________________________________________ 12 3.1.6 Structure (HL4) _______________________________________________ 12 3.1.7 Structure (HL5) _______________________________________________ 12 3.1.8 Structure (HL8) _______________________________________________ 13 3.1.8 Structure (HL9) _______________________________________________ 13 3.1.9 Sample Mappings______________________________________________ 14

4 Summary Area_______________________________________________________ 15

4.1 Structure _______________________________________________________ 15

4.2 Sample Mapping _________________________________________________ 15

5 Consolidated 811_____________________________________________________ 16

5.1 Structure - Consolidated Account Summary __________________________ 17

5.2 Complete Example - Consolidated Account___________________________ 18

6 Auditing the 811 _____________________________________________________ 21

6.1 Rules of Extended Pricing _________________________________________ 21

6.2 Determining Segment Amount _____________________________________ 21 6.2.1 BAL Segment_________________________________________________ 21 6.2.2 IT1 Segment__________________________________________________ 21

6.2.3 ITA Segment _________________________________________________ 21 6.2.4 SLN Segment _________________________________________________ 21 6.2.5 TXI Segment _________________________________________________ 22 6.2.6 TDS Segment _________________________________________________ 22 6.2.7 TCD Segment_________________________________________________ 22 6.2.8 USD Segment_________________________________________________ 22

6.3 Auditing the Detail and Summary Area ______________________________ 22

7 File Size Estimation __________________________________________________ 22

8 Appendices__________________________________________________________ 23

1 Overview This Document details Granite telecommunication’s implementation of the Consolidated Service Invoice/Statement Transaction Set (811). For ease of reference, the implementation guide is broken into several sections. This section gives an overview of this guide and the 811 transaction set. Subsequent sections explain the implementation of the 811. Each section provides a comprehensive discussion of the information provided for in a particular area of the bill, the format of the segments being used to provide information, and a sample mapping.

1.1 Schedule of 811 Versions This Implementation Guide should be used in conjunction with the ASC X12 Draft Version 4 Release 1 standards, and the TCIF Telephone Billing Guideline Issue 9 for the 811. The TCIF Telephone Billing Guideline can be found on the World Wide Web within the TCIF home at: http://www.atis.org/atis/tcif/edi/tbwg/5tc54hom.htm. The TCIF 811 guideline, issue 9 revision 1, has been included with this document as an addendum.

1.2 Structure of the 811 The 811 is divided into three areas: The Heading Area The heading contains information about the parties exchanging the bill. Some of the common data elements passed in the heading area are: • Account number • The billing party (Granite Telecommunications) • The billed party (Customer) • Invoice Date Due date for payment Section 2 of this guide provides further detail on the data provided in the Heading Area. The Detail Area The detail area contains service usage and charge information. The detail area provides 9 hierarchical levels for data presentation. Granite provides the consolidated 811 invoice in the summary format using the first four HL1-HL4 levels. • Level 1, Service Provider level, contains information about the provider of the service. Note

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

• Level 2, Billing Arrangement level, contains information about the billing arrangement. Granite Telecommunications uses this level to provide Consolidated Billing Account (CBA)

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

arrangement. • Level 4, Group level, provides summary charge information for services rendered. • Level 5, Category level, provides segregation of Level 4 charges, and is included in detailed

billing. • Level 6, Sub-Category level, provides further segregation of Level 4 charges and is not

included in the Granite EDI. • Level 7, Type level, is similar to levels 5 and 6 and is not included in the Granite EDI. • Level 8, Charge Detail level, contains supporting charge detail for charges at level 4. Level 8

information is included in the detailed Granite EDI for service charge detail. • Level 9, Line Detail level, contains supporting usage and charge detail for charges at either

Level 4 or Level 8. Level 9 is only included in detailed EDI for call detail information.

Section 3 of this implementation guide provides further detail on the data provided in the Detail Area. The Summary Area The summary area contains summary information about the 811. The summary area contains several key amounts that 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. • 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 sum of the net adjustment

amount and applied payments for the entire 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 Granite Telecommunications

calculated amount due on the account. In the subordinate, or memo invoices for the child accounts the BAL03 field will be 0.

Below is the equation that can be used to calculate the amount due for the responsible party (Consolidated 811 master account) BAL TT amount (Amount Due to Granite Telecommunications) =

TDS amount (Current Charges) + BAL PB amount (Previous Balance Amount) + BAL NA amount (Net Adjustment) + BAL BT amount (Dishonored Check Total)

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

1.4 Bill and Transaction Formats Provided There are several different 811 formats. Granite Telecommunications provides the 811 in the Consolidated Billing Account, Account Summary format. The account summary formats provide high-level account information. Summary information is provided within HLs 1 - 4. • Single Account Billing This billing arrangement produces one bill per telephone number. • Group Billing Account This billing arrangement combines several single accounts under one main account number and produces one large bill. • Consolidated Billing Account (CBA) Single Accounts and/or Group Billing Accounts are consolidated under a single account number. This produces a special summary 811 of all accounts in the arrangement (see chapter 5), followed by a separate 811 for each subordinate account.

1.5 Referencing Charges When Contacting Granite The information provided in the 811 is used in conjunction with the traditional bill. Since the information provided may be used to both pay bills and resolve billing discrepancies, key fields and reference numbers from a the 811 document should be passed to the customer's internal applications. The following data elements are required to reference an account: Bill Date BIG Segment - BIG01 Account Number - REF02 when REF01 = “12” or REF=”14” Bill reference numbers, which can be used to reference charges when making billing inquiries, are provided in each loop where charge information is provided. (The TXI segment does not contain a reference number.)

1.6 Taxes, Surcharges and Fees Taxes, surcharges and fees which are assessed by Granite on behalf of a third party (e.g., state or local government) may make up a portion of the certain monthly telephone bills. Granite aggregates like amounts and provides them at the service provider level of the 811. If you have any question about whether a charge is a tax, surcharge, or fee, please resolve the issue during the parallel testing phase. Reference the charge on the respective paper bill and discuss the issue with your Granite Telecommunications representative. 1.7 Data Element Separator and Segment Terminator When displaying mapping examples in this guide, the tilde ( “~” ) is used as the data element separator and the exclamation point ( “ ! ” ) is used as the segment terminator. In live production data Granite Telecommunications will use the X12 recommended data element separator of the tilde ( “~” HEX 7E), segment terminator of the exclamation point ( “ ! ” HEX 21) and sub-element separator of the double vertical bar ( “ ¦ “ HEX 7C).

1.8 Functional Group Information All 811 transaction sets provided will be enveloped within a functional group. The purpose of the functional group is to provide control information for the business document being exchanged. The functional group consists of a functional group header (GS segment) and a functional group trailer (GE segment). GS segment Example: GS*CI*GRANITEDUN*0140100*20030501*1527*128*X*004010! D.E. Data Use Reference Element # Valid Values/Description M GS01 479 CI - Consolidated Invoice M GS02 142 Application Sender’s Code M GS03 124 Application Receiver's Code M GS04 373 Data Interchange Date M GS05 337 Data Interchange Time M GS06 28 Data Interchange Control Number M GS07 455 X - Accredited Standards Committee M GS08 480 004010 - Version 4, Release 1

GE segment Example: GE*337*128! D.E. Data Use Reference Element # Valid Values/Description M GE01 97 Number of transaction sets M E02 28 Data Interchange Control Number

1.9 Understanding Hierarchical Level (HL) Segments In order to understand the 811, it is important to understand the use of the HL segment. The HL segment indicates the structure of the 811. The HL segment contains the following information: HL* ID Number* Parent ID Number* Level Code* Child Code!

• HL01 (Hierarchical ID Number) is a unique number assigned by the provider to identify a particular data segment in a hierarchical structure.

• HL02 (Hierarchical Parent ID Number) is the HL01 value of the parent HL loop. • HL03 (Hierarchical Level Code) identifies the hierarchical level (1 – 9). • HL04 (Hierarchical Child Code) indicates if there are additional subordinate (or child) HL

segments associated with the hierarchical level. Although HL04 is not a mandatory element according to X12 syntax, it is required by TCIF. The value of ‘1’ indicates that the hierarchical level has children (additional subordinate HL data segments in the hierarchical structure). The value of ‘0’ indicates that the hierarchical level has no children (no subordinate HL segment in the hierarchical structure). This provides positive confirmation of subordinate HL loops.

Granite Telecommunications provides summary charges at HL 4. All charges which are standalone (no supporting detail provided) will be grouped together in one HL loop. If any charge has supporting detail (e.g., itemized calls) it will be provided in a separate HL loop. The following are examples that illustrate the use of the HL segment in the 811. The HL01 data element always contains the sequential number of the respective HL loop. HL~1~~1~1! HL02 is not provided. This means the information provided does not have a parent HL loop. HL03 signifies HL 1, the service provider level. HL04 indicates that there is supporting detail at a lower level. HL~2~1~4~0! HL02 indicates that this information supports and is related to the information provided in HL loop number 1. HL03 signifies HL 4, the group level. HL04 indicates that there is no supporting detail for the charges at this level. Several IT1 loops can appear under the same HL loop when HL04 = “0”. HL~3~1~4~1! HL02 indicates that this information supports and is related to the information provided in HL loop number 1. HL03 signifies HL 4, the group level. HL04 indicates that there is supporting detail at a lower level. When HL04 = “1”, only one IT1 loop will appear within this HL loop. HL~4~3~5~1! HL02 indicates that this information supports and is related to the information provided in HL loop number 3. HL03 signifies HL 5, the Category level. HL04 indicates 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 information provided in HL loop number 4. HL03 signifies HL 9, the Line Detail level. HL04 indicates that there is no supporting detail for the charges.

2 Heading Area The purpose of the heading area of the 811 is to provide information about the bill being rendered (i.e., account number, type of bill, due date, and tax status of bill), the entity receiving the bill (the Granite partner), and the entity providing the bill (Granite Telecommunications).

2.1 Structure

ST Transaction Set Header N/A 1 M BIG Beginning Segment for Invoice N/A 1 M NTE Note/Special Instruction N/A 100 O REF Reference Number N/A 3 M ITD Terms of Sale/Due Date N/A 1 O DTM Service From/Through Dates N/A 2 O TXI Tax Information N/A 3 O

Loop N1 2 M N1 Name and DUNS Number N1 1 M N3 Address N1 2 O N4 City, State, ZIP N1 1 O REF Reference Number N1 1 O

2.2 Sample Mapping ST~811~000000001! trx set header BIG~20030501~123456~~~~~CD! beginning segment REF~12~0140101! billing account DTM~186~20030401! service begin date DTM~187~20030501! service end date N1~PE~GRANITETELECOMMUNICATIONS! payee N3~234 COPELAND ST! payee address N4~QUINCY~MA~02169! payee address N1~PR~CUUSTOMERNAME~91~01401001! payer N3~PO BOX 2323! payer address N4~BOSTON~MA~02122! payer address

Max Seg Segment Description Loop Use O/M

3 Detail Area The purpose of the detail area of the 811 is to provide information about the services that are being billed for a given account. The activity reflected is either since the last bill, or over a specified period of time (generally specified in the DTM segments in the heading area of the 811). As previously discussed, Granite Telecommunications provides the 811 in summary format and with supporting detail. 3.1 Summary 811 A summary 811 should not be confused with the summary area of the 811. A summary 811 provides all charges at a summary level only. The summary 811 formats provide high level account information. The advantages of these formats are a less complex programming effort and lower VAN charges. Summary information is provided within HLs 1 - 4. 3.1.1 Accounts Payable 811 The Accounts Payable 811 provides a single tax amount, and charge amounts for all current charges, and an usage charge. This is the smallest and simplest 811 that Granite Telecommunications provides. 3.1.2 Consolidated Billing Account Summary 811 The Consolidated Billing Account (CBA) Summary 811 provides the bill for the master, consolidated account. ‘Memo’ bills are provided within the same transaction set for each of the subordinate accounts.

3.1.5 Structure (HL1)

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

Loop HL/LX 1 O LX Sequential Designator HL/LX 1 O

Loop HL/N1 1 M NM1 Service Provider Code HL/N1 1 M REF Service Provider Numbers HL/N1 2 O PER Inquiry Telephone Numbers HL/N1 2 O TXI Aggregate Taxes HL/N1 10 O

Loop HL/ITA 20 O ITA Surcharges/Allowances HL/ITA 1 M 3.1.6 Structure (HL4)

Loop HL >1 M HL Group - HL4 HL 1 M

Loop HL/IT1 >1 M IT1 Summary Charge HL/IT1 1 M PID Charge Explanation HL/IT1 1 O TXI Taxes HL/IT1 3 O DTM Service Dates HL/IT1 2 O

Loop HL/IT1/QTY 1 O

QTY Number of Lines In Service HL/IT1/QTY 1 O SI Rate State HL/IT1/QTY 1 O

Loop HL/IT1/ITA 2 O ITA Surcharges/Allowances HL/IT1/ITA 1 M 3.1.7 Structure (HL5)

Loop HL >1 O HL Group – HL5 HL 1 M

Loop HL/LX >1 O LX Sequential Designator HL/LX 1 M SI Service (TN) Identification HL/LX 1 O




3.1.8 Structure (HL8)


Loop HL/SLN >1 O SLN Subline Item detail HL/SLN 1 M SI Service (TN) Identification HL/SLN 1 O PID Charge Explanation HL/SLN 1 O 3.1.8 Structure (HL9)


Loop HL/TCD >1 O TCD Itemized Call Detail HL/TCD 1 M SI Service (Call) Identification HL/TCD 1 O



3.1.9 Sample Mappings Accounts Payable 811 HL~1~~1~1! LX~1! NM1~SJ~2~GRANITETELECOMMUNICATIONS! service Provider PER~BI~~TE~8668471500! contact Information TXI~TX~5.22~~~~2~A! total Tax HL~2~1~4~0! IT1~1~1~M4~67.23~~SV~0110~ZZ~1! recurring charges IT1~2~1~M4~123.87~~SV~0400~ZZ~2! adjustments IT1~3~250~M4~34.78~~SV~0700~ZZ~3! usage charges (250 m) Account Detail 811 HL~1~~1~1! LX~3! NM1~SJ~2~GRANITETELECOMMUNICATIONS! PER~BI~~TE~8668471500! TXI~TX~192.92~~~~2~A! HL~2~1~4~1! IT1~1~1~M4~301.50~~SV~0110~ZZ~1! recurring charges HL~3~1~4~0! IT1~2~1~M4~0.00~~SV~0400~ZZ~2! adjustments IT1~3~22980~M4~1172.99~~SV~0700~ZZ~3! usage charges HL~4~2~5~1! LX~4! LX/SI once per TN SI~TI~TN~6175550000! HL~5~4~8~0! SLN~1~~I~1~M4~11.25~~O! usoc charge SI~TI~SC~USOC1! PID~F~~~~USOC1 DESCRIPTION! SLN~2~~I~1~M4~10.50~~O! usoc charge SI~TI~SC~USOC2! PID~F~~~~USOC2 DESCRIPTION! LX~5! LX/SI once per TN SI~TI~TN~6175550001! HL~6~4~8~0! SLN~1~~I~1~M4~11.25~~O! usoc charge SI~TI~SC~USOC1! PID~F~~~~USOC1 DESCRIPTION! SLN~2~~I~1~M4~10.50~~O! usoc charge SI~TI~SC~USOC2! PID~F~~~~USOC2 DESCRIPTION! HL~7~5~9~0! Call detail loop TCD~4.5~20030725~0835~ZZ~NATL411SVC~~~~~1~~1.5~~~~I! Call detail SI~TI~DA~25~TM~5014110000~FN~6175550000! Supporting Info TCD~4.6~20030731~0949~ZZ~NATL411SVC~~~~~1~~1.5~~~~I! Call detail SI~TI~DA~25~TM~5014110000~FN~6175550000! Supporting Info

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

4.1 Structure

TDS Charge for Services Rendered N/A 1 M

Loop ITA 5 O ITA Refund and Transfer Amounts ITA 1 M

Loop BAL 6 M

BAL Account Status BAL 1 O Loop N1 >1 O

N1 Service Provider N1 1 M SE Transaction Set Trailer N/A 1 M

4.2 Sample Mapping TDS~8482! current charges BAL~P~PB~88.2! previous bal amt BAL~A~NA~-2.05! net adjustment BAL~M~TP~-85! payments applied BAL~A~BT~10! dishonored check total BAL~M~TT~95.97! amount due N1~SJ~GRANITE TELECOMMUNICATIONS! service provider N1~87~ GRANITE TELECOMMUNICATIONS! remit to SE~37~000000001! transaction set trailer


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

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

• For a Consolidated 811 Invoice, BIG07 may have the value of “CD” (Consolidated Debit Invoice), “CE” (Consolidated Credit Invoice), “FD” (Consolidated Invoice, Final Bill), “CF” (Consolidated Debit Memo) or “CG” (Consolidated Credit Memo).

• For a Subordinate 811 Invoice, BIG07 may have the value of “DR” (Debit Memo), “CR” (Credit Memo), “FE” (Memorandum, Final Bill) or “ME” (Memorandum (indicates a zero balance)).

• The ITD segment (to convey terms of sale and the due date) will be produced as normal for the Consolidated 811 Invoice. It is not provided for the Subordinate 811 invoice.

• DTM segments are not provided for the Consolidated 811 Invoice. The invoice period dates are provided in the Heading Area of each Subordinate 811 Invoice.

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

• There will be a REF segment in the Heading Area of the Consolidated 811 Invoice with REF01 = “12” to provide the Billing Account Number. This is consistent with all other 811 formats provided by Granite Telecommunications.

• A Consolidated Billing Account Summary is provided at HL2 of the Consolidated 811 Invoice. • If there is detailed billing information associated with the Consolidated 811 Invoice itself (late

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

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

• The Consolidated 811 Invoice will provide summary information for each Subordinate 811 Invoice as shown in the structure table that follows. The only three values provided in IT107 are “0110”, “0400”, and “0700”.

5.1 Structure - Consolidated Account Summary

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

Loop HL/LX 1 M LX Sequential Designator HL/LX 1 M SI Site ID HL/LX 1 O REF Account Number HL/LX 1 M TXI Tax Information HL/LX 2 O

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

Loop HL 1 M HL Group - HL 4 HL 1 M

Loop HL/IT1 >1 M

IT1 Summarized Charges HL/IT1 1 M


5.2 Complete Example - Consolidated Account Interchange Control Header ISA~00~ ~00~ ~01~107212169 ~01_1234567890123 ~030607~1124~U~04010~0000000037~0~P~¦! Functional Group Heading GS*CI*GRANITEDUN*0140100*20030501*1527*128*X*004010! Consolidated Invoice ST~811~000000001! trx set header BIG~20030501~123456~~~~~CD! beginging seg REF~12~0140101! billing account ITD~03~3~~~~20030501! terms of sale N1~PE~GRANITE TELECOMMUNICATIONS! payee N3~234 COPELAND ST! payee address N4~QUINCY~MA~02169! payee address N1~PR~CUUSTOMERNAME~91~01401001! payer N3~PO BOX 2323! payer address N4~BOSTON~MA~02122! payer address HL~1~~1~1! LX~1! NM1~SJ~2~GRANITETELECOMMUNICATIONS! service provider PER~BI~~TE~8668471500! contact into Consolidated Billing Account Summary (Appears if the master account itself has charges, etc independent of subordinate accounts) HL~2~1~2~1! LX~1! seq no REF~14~0140100! account no TXI~TX~2.56~~~~~O! total tax HL~3~2~4~0! IT1~~1~M4~50.25~~SV~2050~ZZ~1! total amt billed Subordinate Account Summaries HL~4~1~2~1! LX~2! REF~11~0140101! sub acct no TXI~TX~5.26~~~~~O! sub acct taxes HL~5~4~4~0! IT1~~1~M4~100.50~~SV~2050~ZZ~1! total amt billed … … … HL2 loops for other subordinate accounts …

TDS~150.75! current charges BAL~P~PB~88.2! previous bal amt BAL~A~NA~-2.05! net adjustment BAL~M~TP~-85! payments applied BAL~A~BT~10! bad check total BAL~M~TT~161.90! amount due N1~87~ GRANITE TELECOMMUNICATIONS! remit to SE~37~000000001! transaction set trailer Subordinate Invoices ST~811~000000002! trx set header BIG~20030501~123456~~~~~ME! beginning segment REF~14~0140100! master account REF~12~0140101! billing account DTM~186~20030401! service begin date DTM~187~20030501! service end date N1~PE~GRANITE TELECOMMUNICATIONS! payee N3~234 COPELAND ST! payee address N4~QUINCY~MA~02169! payee address N1~PR~CUUSTOMERNAME~91~01401001! payer N3~PO BOX 2323! payer address N4~BOSTON~MA~02122! payer address HL~1~~1~1! LX~1! assigned seq. no. NM1~SJ~2~GRANITETELECOMMUNICATIONS! service Provider PER~BI~~TE~8668471500! contact Information TXI~TX~5.22~~~~2~A! total Tax HL~2~1~4~0! IT1~1~1~M4~67.23~~SV~0110~ZZ~1! recurring charges IT1~2~1~M4~34.78~~SV~0400~ZZ~2! adjustments IT1~3~250~M4~123.87~~SV~0700~ZZ~3! usage charges (250 m) Supporting Charge Detail Information for Detailed EDI TDS~23110! current charges BAL~P~PB~0! previous bal amt BAL~A~NA~-0! net adjustment BAL~M~TP~-0! payments applied BAL~A~BT~0! bad check total BAL~M~TT~0! amount due N1~SJ~GRANITE TELECOMMUNICATIONS! service provider SE~37~000000002! transaction set trailer … … Other accounts … Functional Group Trailer

GE*337*128! Interchange Control Trailer IEA~1~0000000037!

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

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

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

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

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

6.2 Determining Segment Amount For ease of reference the term segment amount is used to designate the monetary amount that a segment provides after: 1) Extended pricing rules have been applied. 2) Relational checks have been performed to ensure that the monetary amount is not being supplied for informational purposes only. Certain segments contain both an amount and a code value identifying whether the amount is a credit or a charge. The TCIF 811 Implementation Guide states that within the detail area of the 811, the sign of the amount field will control the monetary value (positive or negative). The code values should be treated as informational only; they have no impact on the sign interpretation. The following pages discuss how to determine the segment amount of each “money” segment. 6.2.1 BAL Segment The amount in BAL03 is the segment amount. 6.2.2 IT1 Segment If IT103 = “M4”, then the amount in IT104 is the segment amount. If IT103 ≠ “M4”, then the product of IT102 and IT104 is the segment amount. 6.2.3 ITA Segment The amount in ITA07 is the segment amount. If ITA16 = “O”, then the segment amount is for information purposes only. 6.2.4 SLN Segment If SLN05 = “M4”, then the amount in SLN06 is the segment amount.

If SLN05 ≠ “M4”, then the product of SLN04 and SLN06 is the segment amount. If SLN08 = “O”, then the segment amount is for information purposes only. 6.2.5 TXI Segment The amount in TXI02 is the segment amount. If TXI07 = “O”, then the segment amount is for information purposes only. The TXI segment can be used in the heading area to show that an account is exempt from certain types of taxes. It can also be also used in the detail area to show that an itemized call is tax exempt. In each of these uses, TXI07 would equal “O”. 6.2.6 TDS Segment The amount in TDS01 is the segment amount. 6.2.7 TCD Segment The amount in TCD12 is the segment amount. If TCD16 = “O”, then the segment amount is for information purposes only. 6.2.8 USD Segment If USD08 is populated, then the amount in USD08 is the segment amount. If USD08 is not populated, then the following determination is made to determine the segment amount: If USD05 = “M4”, then the amount in USD06 is the segment amount. If USD05 ≠ “M4”, then the product of USD03 and USD06 is the segment amount. If USD01 = “O”, then the segment amount is for information purposes only. The USD segment can be used to provide taper table information for WATS billing. In this use, USD01 would equal “O”. Note 1: When both USD03 and USD08 are populated, the amount in USD08 takes precedence and becomes the segment amount. Note 2: In order to verify amount in USD08, it is necessary to multiply USD03 * USD06 * USD07 * Percent of Interstate Usage. The Percent of Interstate Usage can be found in an SI pair (DE 1000 = ‘PU’) within the SLN loop, when it is present.

6.3 Auditing the Detail and Summary Area The summing rules that can be used to audit the detail and summary areas of the 811 can be found within the 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 Model Overview “ which provides the summing rules for balancing the 811 transaction set.

7 File Size Estimation File size is a function of the type of EDI selected, the number of features per line and the volume of traffic, and the number of memo invoices per file. Though these numbers will vary across customers, the following estimates can be safely made:

• For Summary EDI, estimate 3k per account. • For extended EDI with just line feature charges estimate 8k per account • For extended EDI with line feature charges and call detail estimate 250k per account.

As an example, for a billing account with 250 child accounts, estimate 750k for the summary EDI, 2 meg for the extended EDI with just line charges and 62.5 meg for the extended EDI with call detail. Or, as a further example, for a billing account with 1000 child accounts, estimate 3 meg for the summary EDI, 8 meg for the extended EDI with just line charges and 250 meg for the extended EDI with call detail.

8 Appendices

ISSUE 6.003040••811 A TCIF GUIDELINE FORCONSOLIDATED SERVICE INVOICE/STATEMENT ELECTRONIC DATA INTERCHANGE

JUNE 1995 811-1

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 Services Invoice/Statement Transaction Set (811) for use within the context of an ElectronicData Interchange (EDI) environment. This transaction set provides for the billing of complex andstructured service invoice detail. This standard can be used by organizations who are interested insending or receiving either consolidated or standalone invoices for service arrangements which requireprocessing other than that done for the typical product invoice. The Consolidated ServicesInvoice/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:

This guideline is formatted only with segments, data elements, and codes that the telecommunicationsindustry has recommended for use. When a data element is defined as mandatory by X12, it is flaggedwith '>>' for convenience.

If TCIF does not recommend the use of a data element within a segment, that data element is not listed.Similarly, only the code values that TCIF recommends for use with individual data elements will be listed.

TCIF approved codes for each occurrence of a data element have been listed throughout this section.Although a code value may be listed, recommended usage may be restricted at a given hierarchical levelas noted.

A '-->' will highlight key notes about code values.

Heading:

Pos. Seg. Req. Loop Notes andNo. ID Name Des. Max.Use Repeat Comments010 ST Transaction Set Header M 1

020 BIG Beginning Segment for Invoice M 1

030 NTE Note/Special Instruction O 100

040 CUR Currency O 1

050 REF Reference Numbers O >1

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

110 N2 Additional Name Information O 2

120 N3 Address Information O 2

130 N4 Geographic Location O 1

140 REF Reference Numbers O 12

A TCIF GUIDELINE FOR ISSUE 6.003040••811ELECTRONIC DATA INTERCHANGE CONSOLIDATED SERVICE INVOICE/STATEMENT

811-2 JUNE 1995


Detail:

Pos. Seg. Req. Loop Notes andNo. ID Name Des. Max.Use Repeat Comments

LOOP ID - HL >1

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 2

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 - N1 1

110 N1 Name O 1 n2





160 PER Administrative Communications Contact O >1


LOOP ID - ITA >1

180 ITA Allowance, Charge or Service O 1



LOOP ID - IT1 999999

210 IT1 Baseline Item Data (Invoice) O 1 n3




240 INC Installment Information O 1




280 MSG Message Text O >1

Not Used 285 AMT Monetary Amount O 1

LOOP ID - QTY >1



JUNE 1995 811-3


LOOP ID - ITA 10




LOOP ID - N1 >1

340 N1 Name O 1





LOOP ID - SLN >1

390 SLN Subline Item Detail O 1 n4




420 CUR Currency O 1

430 INC Installment Information O 1






490 AMT Monetary Amount O 10

500 MSG Message Text O >1

LOOP ID - QTY >1



LOOP ID - N1 >1

530 N1 Name O 1






LOOP ID - TCD >1

590 TCD Itemized Call Detail O 1 n5




LOOP ID - QTY >1



LOOP ID - USD >1


811-4 JUNE 1995

620 USD Usage Sensitive Detail O 1 n6


640 TRF Rating Factors O 18

LOOP ID - QTY >1



Summary:

Pos. Seg. Req. Loop Notes andNo. ID Name Des. Max.Use Repeat Comments010 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



110 CTT Transaction Totals O 1 n7

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 LowestLevel of Charges within a Billing Arrangement) 9 - Line Detail (Identifies the Supporting DetailAssociated with the Charge or Group Level) They must be used in the (hierarchical) order in whichthey are listed; however, certain levels are optional and may be omitted. At least one occurrenceeach of the service/billing provider level and group level is required.

2. The service/billing provider level is defined by the N1 loop.3. The group level is defined by at least one occurrence of the IT1 loop which may only appear at the

group level.4. The SLN loop may only appear at the charge detail level.5. The TCD loop may only appear at the line detail level.6. The USD loop may only appear at the line detail level.7. The number of line items (CTT01) is the accumulation of the number of IT1 segments.


JUNE 1995 811-5

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

Notes:Syntax Notes:

Semantic Notes: 1 The transaction set identifier (ST01) used by the translation routines of theinterchange partners to select the appropriate transaction set definition (e.g.,810 selects the invoice transaction set).

Comments:

Data Element SummaryRef. DataDes. Element Name Attributes

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

811 X12.39 Consolidated Service Invoice/Statement>> 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


811-6 JUNE 1995

Segment: BIG Beginning Segment for InvoicePosition: 020

Loop:Level: Heading

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

numbers and dates.Notes:

Syntax Notes:Semantic Notes: 1 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.


>> BIG01 245 Invoice Date M DT 6/6Invoice Issue Date.

>> BIG02 76 Invoice Number M AN 1/22Identifying number assigned by issuer.TCIF recommends that this number be unique. One method that may beused to make this number unique is to join the account number and theinvoice date.

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

CD Consolidated Debit InvoiceCE Consolidated Credit Invoice

Indicates that the invoice is a consolidation ofseveral detailed credit invoices. The detail, ifprovided, will be contained in debit memos

CF Consolidated Debit MemoIndicates that the invoice is a consolidated memo.All actual billing invoices are summarized by thisconsolidated memo

CG Consolidated Credit MemoIndicates that the invoice is a consolidated memo.All actual billing invoices are summarized by thisconsolidated memo

CI Consolidated InvoiceCM Call Detail Memo

Indicates that the invoice contains details oftelecommunications usage that is for informationand not payable

CN Credit InvoiceCR Credit MemoDI Debit InvoiceDR Debit MemoFB Final BillFD Consolidated Invoice, Final Bill

The final (last) bill for a consolidated account


JUNE 1995 811-7

FE Memorandum, Final BillThe final (last) bill for a non-payable invoice(memo)

ME MemorandumRG Revised Final Bill

Code to indicate that the last bill has beenrecalculated due to the receipt of delayed usage, orcredits. To identify unpaid overdue final accounts,which are reissued each month


811-8 JUNE 1995

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 instructionNotes:

Syntax Notes:Semantic Notes:

Comments: 1 The NTE segment permits free-form information/data which,under ANSI X12standard implementations, is not machine processable. The use of the "NTE''segment should therefore be avoided, if at all possible, in an automatedenvironment.


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

GEN Entire Transaction SetINV Invoice InstructionOTH Other InstructionsPRI PriorityTIL Tariff IndexTLF Tariff RuleTRF Tariff Rate FootnotesTSF Tariff Section Footnotes

>> NTE02 3 Free Form Message M AN 1/60Free-form text.


JUNE 1995 811-9

Segment: CUR CurrencyPosition: 040

Loop:Level: Heading

Usage: OptionalMax Use: 1Purpose: To specify the currency (dollars, pounds, francs, etc.) used in a transaction

Notes:Syntax Notes: 1 If CUR08 is present, then CUR07 is required.

2 If CUR09 is present, then CUR07 is required.3 If CUR11 is present, then CUR10 is required.4 If CUR12 is present, then CUR10 is required.5 If CUR14 is present, then CUR13 is required.6 If CUR15 is present, then CUR13 is required.7 If CUR17 is present, then CUR16 is required.8 If CUR18 is present, then CUR16 is required.9 If CUR20 is present, then CUR19 is required.10 If CUR21 is present, then CUR19 is required.

Semantic Notes:Comments: 1 See Figures Appendix for examples detailing the use of the CUR segment.


>> CUR01 98 Entity Identifier Code M ID 2/2Code identifying an organizational entity, a physical location, or anindividual

PR Payer>> CUR02 100 Currency Code M ID 3/3

Code (Standard ISO) for country in whose currency the charges arespecified.For additional values, request ISO document 4217.

CAD Canadian DollarsUSD United States Dollars

CUR03 280 Exchange Rate O R 4/6Value to be used as a multiplier conversion factor to convert monetaryvalue from one currency to another.

CUR04 98 Entity Identifier Code O ID 2/2Code identifying an organizational entity, a physical location, or anindividual

PE PayeePM Party to receive paper Memo of InvoiceRI Remit ToSE Selling PartySJ Service Provider

Identifies name and address information aspertaining to a service provider for which billing isbeing rendered


811-10 JUNE 1995

CUR05 100 Currency Code O ID 3/3Code (Standard ISO) for country in whose currency the charges arespecified.


CUR06 669 Currency Market/Exchange Code O ID 3/3Code identifying the market upon which the currency exchange rate isbased.

IMF International Monetary FundLNF London (England) Exchange - First ClosingLNS London (England) Exchange - Second ClosingNYC New York Foreign ExchangePHI Philadelphia Foreign ExchangeZUR Zurich (Switzerland) Exchange

CUR07 374 Date/Time Qualifier X ID 3/3Code specifying type of date or time, or both date and time.

001 Cancel After003 Invoice007 Effective

Effective date of exchange.009 Process035 Delivered092 Contract Effective093 Contract Expiration102 Issue150 Service Period Start151 Service Period End152 Effective Date of Change

Date on which the change went into effect153 Service Interruption154 Adjustment Period Start155 Adjustment Period End

CUR08 373 Date O DT 6/6Date (YYMMDD).

CUR09 337 Time O TM 4/8Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, orHHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimalseconds are expressed as follows: D = tenths (0-9) and DD = hundredths(00-99)


JUNE 1995 811-11

Segment: REF Reference NumbersPosition: 050

Loop:Level: Heading

Usage: OptionalMax Use: >1Purpose: To specify identifying numbers.

Notes:Syntax Notes: 1 At least one of REF02 or REF03 is required.

Semantic Notes:Comments:


>> REF01 128 Reference Number Qualifier M ID 2/2Code qualifying the Reference Number.

11 Account NumberNumber identifies a telecommunications industryaccount

12 Billing AccountAccount number under which billing is rendered

14 Master Account NumberAccount number used to represent individual billingaccounts which have been consolidated and/orsummarized

AP Accounts Receivable NumberEH Financial Classification CodeHB Bill & Hold Invoice No.

REF02 127 Reference Number X AN 1/30Reference number or identification number as defined for a particularTransaction Set, or as specified by the Reference Number Qualifier.

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


811-12 JUNE 1995

Segment: PER Administrative Communications ContactPosition: 060

Loop:Level: Heading

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

directedNotes:

Syntax Notes: 1 If either PER03 or PER04 is present, then the other is required.2 If either PER05 or PER06 is present, then the other is required.



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

CC Computer Systems ContactPER02 93 Name O AN 1/35

Free-form name.PER03 365 Communication Number Qualifier X ID 2/2

Code identifying the type of communication number.EM Electronic MailFX FacsimileTE Telephone

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

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

EM Electronic MailFX FacsimileTE Telephone



JUNE 1995 811-13

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

Loop:Level: Heading

Usage: OptionalMax Use: 5Purpose: To specify terms of sale.

Notes: To specify due data and late payment terms.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.


ITD01 336 Terms Type Code O ID 2/2Code identifying type of payment terms.

03 Fixed Date10 Instant18 Fixed Date, Late Payment Penalty Applies

Sales terms specifying a past due date, and a latepayment percentage penalty applies to unpaidbalances past this due date

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

3 Invoice Date5 Invoice Receipt Date

ITD03 338 Terms Discount Percent O R 1/6Terms discount percentage, expressed as a percent, available to thepurchaser if an invoice is paid on or before the Terms Discount Due Date.

ITD06 446 Terms Net Due Date O DT 6/6Date when total invoice amount becomes due.Date after which Late Payment Charge applies.

ITD09 388 Terms Deferred Due Date O DT 6/6Date deferred payment or percent of invoice payable is due.

ITD10 389 Deferred Amount Due X N2 1/10Deferred amount due for payment.Put Late Payment Charge here until X12 approves addition of ITD16.

ITD11 342 Percent of Invoice Payable X R 1/5Amount of invoice payable expressed in percent.

ITD13 765 Day of Month X N0 1/2The 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/1Code identifying type of payment procedures.


811-14 JUNE 1995

C Pay By CheckE Electronic Payment System

ITD15 954 Percent O R 1/10Percentage expressed as a decimalLate Payment percentage.


JUNE 1995 811-15

Segment: DTM Date/Time ReferencePosition: 080

Loop:Level: Heading

Usage: OptionalMax Use: 10Purpose: To specify pertinent dates and times

Notes: To specify billing period.Syntax Notes: 1 At least one of DTM02 DTM03 or DTM06 is required.

2 If either DTM06 or DTM07 is present, then the other is required.Semantic Notes:

Comments:


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

186 Invoice Period StartWhen the billing period covered by an invoicebegins

187 Invoice Period EndWhen the billing period covered by an invoice ends

DTM02 373 Date X DT 6/6Date (YYMMDD).

DTM05 624 Century O N0 2/2The first two characters in the designation of the year (CCYY).


811-16 JUNE 1995

Segment: TXI Tax InformationPosition: 090

Loop:Level: Heading

Usage: OptionalMax Use: >1Purpose: To specify tax information.

Notes: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:Comments: 1 TXI02 is the monetary amount of the tax.

2 TXI03 is the tax percent expressed as a decimal.3 If TXI02 is not used, then the application of the percent (TXI03) is between

trading partners.


>> TXI01 963 Tax Type Code M ID 2/2Code specifying the type of tax.See X12 version 003040 code list for valid codes.

TXI03 954 Percent X R 1/10Percentage expressed as a decimalTax rate for this tax jurisdiction.

TXI04 955 Tax Jurisdiction Code Qualifier X ID 2/2Code identifying the source of the data used in tax jurisdiction code.

CD Customer definedVD Vendor definedVE Vertex

TXI05 956 Tax Jurisdiction Code X AN 1/10Code identifying the taxing jurisdiction.

TXI06 441 Tax Exempt Code X ID 1/1Code identifying exemption status from sales and use tax.

1 Yes (Tax Exempt)2 No (Not Tax Exempt)

TXI07 662 Relationship Code O ID 1/1Code indicating the relationship of the price or amount to the associatedsegment.

A AddD DeleteO Information Only

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

TXI09 325 Tax Identification Number O AN 1/20Number assigned to a purchaser (buyer, orderer) by a taxing jurisdiction(state, county, etc.), often called a tax exemption number or certificate


JUNE 1995 811-17

number.


811-18 JUNE 1995

Segment: N1 NamePosition: 100

Loop: N1Level: Heading

Usage: OptionalMax Use: 1Purpose: To identify a party by type of organization, name and code

Notes: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 providingorganizational 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.


>> N101 98 Entity Identifier Code M ID 2/2Code identifying an organizational entity, a physical location, or anindividual

PE PayeePR PayerRL Reporting Location

N102 93 Name X AN 1/35Free-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 & Bradstreet9 D-U-N-S+4, D-U-N-S Number with Four Character

Suffix40 Electronic Mail User Code

Identifies the Electronic Mail User locally definedand maintained between trading partners

41 Telecommunications Carrier Identification CodeIdentifies the Interexchange carrier for the chargesbeing billed

42 Telecommunications Pseudo Carrier IdentificationCodeA code similar to the standard Carrier IdentificationCode which is used to identify the local exchangeservice providers

91 Assigned by Seller or Seller's Agent92 Assigned by Buyer or Buyer's Agent

N104 67 Identification Code X AN 2/17Code identifying a party or other code.If N103 = "41" - Use Bellcore CIC list.If N103 = "42" - Use Pseudo-CIC list provided in section 10.4.


JUNE 1995 811-19

Segment: N2 Additional Name InformationPosition: 110


Usage: OptionalMax Use: 2Purpose: To specify additional names or those longer than 35 characters in length

Notes:Syntax Notes:



>> N201 93 Name M AN 1/35Free-form name.

N202 93 Name O AN 1/35Free-form name.


811-20 JUNE 1995

Segment: N3 Address InformationPosition: 120


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

Notes:Syntax Notes:



>> N301 166 Address Information M AN 1/35Address information

N302 166 Address Information O AN 1/35Address information


JUNE 1995 811-21

Segment: N4 Geographic LocationPosition: 130


Usage: OptionalMax Use: 1Purpose: To specify the geographic place of the named party

Notes:Syntax Notes: 1 If N406 is present, then N405 is required.

Semantic Notes:Comments: 1 A combination of either N401 through N404 (or N405 and N406) may be

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


N401 19 City Name O AN 2/30Free-form text for city name.

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

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

N404 26 Country Code O ID 2/3Code identifying the country.

N405 309 Location Qualifier X ID 1/2Code identifying type of location.

AC City and StateCC CountryCI CitySP State/Province

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


811-22 JUNE 1995



Usage: OptionalMax Use: 12Purpose: To specify identifying numbers.





01 American Bankers Assoc. (ABA) Transit/RoutingNumber (Including Check Digit, 9 Digits)

03 Clearing House Interbank Payment System(CHIPS) Participant Number (3 or 4 Digits)

05 Clearing House Interbank Payment System(CHIPS) User Identification (6 digits)

10 Account Managers CodeIdentifies the telecommunications managerassigned to this account

13 Horizontal CoordinatePositional address, horizontal component. Theassigned address is based upon a grid mappingscheme

15 Vertical CoordinatePositional Address, Vertical component. Theassigned address is based upon a grid mappingscheme

BC Buyer's Contract NumberCA Cost Allocation ReferenceCO Customer Order NumberCR Customer Reference NumberCT Contract NumberDP Department NumberEF Electronic Funds Transfer ID NumberEM Electronic Payment Reference NumberEU End User's Purchase Order NumberGC Government Contract NumberGT Goods and Service Tax Registration NumberIS Invoice Number SuffixIT Internal Customer NumberIV Seller's Invoice NumberLB LockboxNP Partial Payment Number


JUNE 1995 811-23

OI Original Invoice NumberOP Original Purchase OrderOR Order/Paragraph NumberPO Purchase Order NumberPX Previous Invoice NumberRT Payee's Financial Institution Transit Routing

Number for Check, Draft or Wire Payments.Receiving Depository Financial Institution TransitRouting Number for ACH Transfers.

SE Serial NumberSX Service Interrupt Tracking NumberTF Transfer NumberTJ Federal Taxpayer's Identification NumberVC Vendor Contract NumberVN Vendor Order NumberVR Vendor ID Number




811-24 JUNE 1995




directedNotes:





TR Technical Marketing RepresentativePER02 93 Name O AN 1/35

Free-form name.PER03 365 Communication Number Qualifier X ID 2/2







JUNE 1995 811-25

Segment: HL Hierarchical LevelPosition: 010

Loop: HLLevel: Detail

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

of data segments.Notes:


Comments: 1 The HL Segment is used to identify levels of detail information using aHierarchical Structure, such as relating line item data to shipment data, andpackaging data to line item data.

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.


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

HL02 734 Hierarchical Parent ID Number O AN 1/12Identification number of the next higher hierarchical data segment that thedata segment being described is subordinate to.--> Not used at HL1 (Service Provider).

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

1 Service/Billing ProviderCode identifying the telecommunications companyproviding service/billing

2 Billing ArrangementCode identifying a specified billing arrangement

3 Sub-Billing ArrangementCode identifying a more detailed billingarrangement

4 GroupCode identifying a group of charges on the bill


811-26 JUNE 1995

5 CategoryCode identifying the sub-division of the group

6 Sub-CategoryCode identifying a further breakdown of thecategory

7 TypeCode identifying a further breakdown of the sub-category

8 Charge DetailCode identifying the lowest level of charges withina billing arrangement

9 Line DetailCode identifying the supporting detail associatedwith the charge or group

>> HL04 736 Hierarchical Child Code M ID 1/1Code indicating whether there are hierarchical child data segmentssubordinate to the level being described.Required by TCIF.

0 No Subordinate HL Segment in This HierarchicalStructure.

1 Additional Subordinate HL Data Segment in ThisHierarchical Structure.


JUNE 1995 811-27

Segment: LX Assigned NumberPosition: 020

Loop: LXLevel: Detail

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

Notes:Syntax Notes:



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


811-28 JUNE 1995

Segment: SI Service Characteristic IdentificationPosition: 030


Usage: OptionalMax Use: 2Purpose: To specify service characteristic data

Notes: See section 10.4 for valid values when using data element 1000/234 pairs.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.


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

TI Telecommunications Industry>> SI02 1000 Service Characteristics Qualifier M ID 2/2

Code from an industry code list qualifying the type of servicecharacteristics.

>> SI03 234 Product/Service ID M AN 1/30Identifying number for a product or service.

SI04 1000 Service Characteristics Qualifier X ID 2/2Code from an industry code list qualifying the type of servicecharacteristics.

SI05 234 Product/Service ID X AN 1/30Identifying number for a product or service.








JUNE 1995 811-29












811-30 JUNE 1995

Segment: PID Product/Item DescriptionPosition: 040


Usage: OptionalMax Use: 200Purpose: To describe a product or process in coded or free-form format

Notes: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 PID03 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. A “N''indicates it does not apply. Any other value is indeterminate.

Comments: 1 If PID01 = “F'', then PID05 is used. If PID01 = “S'', then PID04 is used. IfPID01 = “X'', then both PID04 and PID05 are used.

2 Use PID06 when necessary to refer to the product surface or layer beingdescribed in the segment.

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


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

F Free-formS Structured (From Industry Code List)X Semi-structured (Code and Text)

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

AS Assigned by SellerPID04 751 Product Description Code X AN 1/12

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

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


JUNE 1995 811-31




Notes: --> This segment is not used at HL1 (Service Provider Level).Syntax Notes: 1 At least one of REF02 or REF03 is required.




01 American Bankers Assoc. (ABA) Transit/RoutingNumber (Including Check Digit, 9 Digits)

03 Clearing House Interbank Payment System(CHIPS) Participant Number (3 or 4 Digits)

05 Clearing House Interbank Payment System(CHIPS) User Identification (6 digits)

10 Account Managers CodeIdentifies the telecommunications managerassigned to this account

11 Account NumberNumber identifies a telecommunications industryaccount

12 Billing AccountAccount number under which billing is rendered

13 Horizontal CoordinatePositional address, horizontal component. Theassigned address is based upon a grid mappingscheme

14 Master Account NumberAccount number used to represent individual billingaccounts which have been consolidated and/orsummarized

15 Vertical CoordinatePositional Address, Vertical component. Theassigned address is based upon a grid mappingscheme

BC Buyer's Contract NumberCA Cost Allocation ReferenceCO Customer Order NumberCR Customer Reference NumberCT Contract NumberDP Department NumberEF Electronic Funds Transfer ID NumberEM Electronic Payment Reference Number


811-32 JUNE 1995

EU End User's Purchase Order NumberF8 Original Reference NumberGC Government Contract NumberGT Goods and Service Tax Registration NumberHB Bill & Hold Invoice No.IT Internal Customer NumberIV Seller's Invoice NumberLB LockboxLI Line Item Identifier (Seller's)NP Partial Payment NumberOI Original Invoice NumberOP Original Purchase OrderOR Order/Paragraph NumberOW Service Order Number

Number assigned when a customer orders serviceand equipment and which appears on bill

PO Purchase Order NumberPX Previous Invoice NumberRT Payee's Financial Institution Transit Routing

Number for Check, Draft or Wire Payments.Receiving Depository Financial Institution TransitRouting Number for ACH Transfers.

SE Serial NumberSX Service Interrupt Tracking NumberTF Transfer NumberTJ Federal Taxpayer's Identification NumberVC Vendor Contract NumberVN Vendor Order NumberVR Vendor ID Number




JUNE 1995 811-33

Segment: AMT Monetary AmountPosition: 060


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

Notes:Syntax Notes:



>> AMT01 522 Amount Qualifier Code M ID 1/2Code to qualify amount--> '6', 'KO', 'PB' and 'SC' are the only valid codes at HL1 (ServiceProvider Level).

1 Line Item Total5 Total Invoice Amount6 Amount Subject to Total Monetary Discount8 Total Monetary Discount AmountAD Adjusted TotalAP Amount Prior to Fractionalization

Full charge amount for the service per serviceperiod, prior to pro-rated fractionalization due topartial period billing

AQ Average Price Per CallThe total amount of money associated with acategory of calls divided by the total number ofcalls within the category calculated to provide callsummary details

AS Average Price Per MinuteThe total amount of money associated with acategory of calls divided by the total number ofminutes within the category calculated to providecall summary details

AX Previous PriceBT Bank Reject TotalCH Change AmountCS Commission Sales

Those sales used to calculate commissionpayments

CT ContractIndicates the value stated in the contract

KO Committed AmountLI Line Item Unit PriceN Net


811-34 JUNE 1995

Indicates the value remaining after all deductionsand adjustments have been made

NA Net AdjustmentNO Non Commission Sales

Those sales not included for commission paymentcalculation

NS Net Savings AmountAmount of dollar saving resulting from the use ofservice, such as Optional Calling Plans

PB Billed AmountTotal amount due on the period bill

SC Total Service ChargeTP Total payment amountTS Total Sales

The total of commission and non commission salesneeded to calculate intersell amount

TT Total Transaction Amount>> AMT02 782 Monetary Amount M R 1/15

Monetary amount.


JUNE 1995 811-35




Notes:Syntax Notes: 1 At least one of DTM02 DTM03 or DTM06 is required.


Comments:



001 Cancel After003 Invoice007 Effective009 Process035 Delivered092 Contract Effective093 Contract Expiration102 Issue150 Service Period Start151 Service Period End152 Effective Date of Change

Date on which the change went into effect153 Service Interruption154 Adjustment Period Start155 Adjustment Period End193 Period Start194 Period End198 Completion

Date when the activity was completedDTM02 373 Date X DT 6/6

Date (YYMMDD).DTM05 624 Century O N0 2/2

The first two characters in the designation of the year (CCYY).


811-36 JUNE 1995








trading partners.


>> TXI01 963 Tax Type Code M ID 2/2Code specifying the type of tax.See X12 version 003040 code list for valid values.

TXI02 782 Monetary Amount X R 1/15Monetary amount.






1 Yes (Tax Exempt)2 No (Not Tax Exempt)5 Exempt (Not For Resale)8 Exempt (Sale to U.S. Govt)9 Exempt (Per State Law)C Not Taxable


A AddD Delete


JUNE 1995 811-37

O Information Only


TXI09 325 Tax Identification Number O AN 1/20Number assigned to a purchaser (buyer, orderer) by a taxing jurisdiction(state, county, etc.), often called a tax exemption number or certificatenumber.


811-38 JUNE 1995

Segment: QTY QuantityPosition: 090

Loop: QTYLevel: Detail

Usage: OptionalMax Use: 1Purpose: To specify quantity information.

Notes:Syntax Notes:



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

01 Discrete Quantity02 Cumulative Quantity27 Committed Quantity38 Original Quantity47 Primary Net Quantity90 Acknowledged Quantity

Network Recognition for message receipt91 Additional Usage Quantity

The amount of usage incurred above the alloted orallowable use for a service

92 Allotted Usage QuantityThe amount of allowable usage related to a service

93 Attendant-Handled QuantityManual Recognition for message receipt

94 Billable QuantityNumber of billable units used

95 Data Storage QuantityNumber of storage units used

96 Non-Billable QuantityNumber of non-billable units

97 Non-Urgent Delivery QuantityNumber of units delivered in non-urgent status

98 Overflow QuantityNumber of overflow messages, (Busy conditioncount for 800 service)

99 Quantity UsedQuantity of units used

AA Unacknowledged QuantityMessage received without network, or attendantrecognition

AB Urgent Delivery QuantityNumber of units delivered in urgent status


JUNE 1995 811-39

AC Voice Storage QuantityNumber of voice storage units used

AD Maintenance UnitsNumber of units of maintenance provided

AE Minimum Average Time Requirement (MATR)UnitsNumber of units calculated at a minimum usagerating basis, such as X minutes per message

AF Wide Area Telephone Service (WATS)/800 ServiceUnitsNumber of units of usage, for WATS or 800 service

AG Number of End UsersNumber of participating users

AH Number of Message RecipientsNumber of recipients

AI Number of Operator CreditsNumber of operator credits given

AJ Daily AdjustmentsNS Number of Stations

Number of stations, or terminating points, whichare in use, deleted, added, etc. for service delivery;ports or lines on a computer, for example

>> QTY02 380 Quantity M R 1/15Numeric value of quantity.

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

03 Seconds12 Packet1X Quarter MileAD Bytes

Number of bytes of data transmittedAH Additional Minutes

The minutes, usually associated with usage-sensitive pricing of telecommunication services,which are above the minutes allowed for thatparticular service

AL Access LinesNumber of lines subject to Carrier Access LineCharges

C0 CallsNumber of calls handled

DA DaysDC Disk (Disc)DH MilesDK KilometersDQ Data Records

Number of Data Records handledDY Directory Books

Number of directory books delivered to customer


811-40 JUNE 1995

EA EachEB Electronic Mail Boxes

Number of Electronic Mail Boxes established for anaccount

EV EnvelopeG7 Microfiche Sheet

A film that contains photographed documentsgreatly reduced in size

H1 Half Pages - ElectronicNumber of electronic half pages of data delivered

HR HoursHT Half HourKB Kilocharacters

Kilocharacters of data transmittedKF Kilopackets

Kilopackets of data transmittedKJ Kilosegments

Kilosegments of data transmittedM0 Magnetic Tapes

Number of Magnetic Tapes delivered with dataM4 Monetary ValueMJ MinutesMO MonthsMR MeterNF Messages

Number of Messages transmitted, or deliveredNH Message Hours

Number of hours used, calculated at some ratebasis such as Minutes/message carried

NJ Number of ScreensNumber of data screens handled, or transmitted

OT Overtime HoursP0 Pages - Electronic

Number of electronic pages of data deliveredP1 PercentQA Pages - Facsimile

Number of FAX pages transmittedQB Pages - Hardcopy

Number of printed pages deliveredQH Quarter Hours

Number of 15 minute increments of usage handledRS Resets

Number of times a transmission is reset due to linedrop, interrupt, etc.

S6 SessionsNumber of interactive sessions handled

S7 Storage UnitsNumber of storage increments used


JUNE 1995 811-41

SG SegmentT0 Telecommunications Lines in Service

Snapshot sample of lines in serviceUB Telecommunications Lines in Service - Average

Average number of lines in service specific toequal access requirements

UC Telecommunications PortsNumber of network access ports

UD Tenth MinutesNumber of 6 second increments of usage

UE Tenth HoursNumber of 6 minute increments of usage

UF Usage per Telecommunications Line - AverageUN UnitZZ Mutually Defined


811-42 JUNE 1995




Notes: See section 10.4 for valid values when using data element 1000/234 pairs.

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.














SI11 234 Product/Service ID X AN 1/30


JUNE 1995 811-43

Identifying number for a product or service.SI12 1000 Service Characteristics Qualifier X ID 2/2












811-44 JUNE 1995


Loop: N1Level: Detail







>> N101 98 Entity Identifier Code M ID 2/2Code identifying an organizational entity, a physical location, or anindividual--> 'SJ' is the only valid code at HL1 (Service Provider Level).

--> 'OB' and 'P9' are invalid at HL2 (Billing Arrangement Level) and HL3(Sub-Billing Arrangement Level).

--> 'C3', 'CT', 'GP', 'IA', 'OB', and 'P9' are the only valid codes at HL5(Category Level), HL6 (Sub-Category Level), and HL7 (Type Level).

AG Agent/AgencyAK Party to Whom Acknowledgment Should Be SentAO Account OfBS Bill and Ship ToC3 Circuit Location Identifier

Identifies the address information as that which isassigned to a circuit location address

CA CarrierCT Country of OriginEN End UserGP Gateway Provider

Identifies a gateway access providerIA Installed AtNN Network Name

Identifies the name of the telecommunicationsnetwork, e.g., Envoy

OB Ordered ByP9 Primary Interexchange Carrier (PIC)

Identifies the carrier who will handle theinterexchange calls

PE Payee


JUNE 1995 811-45

PM Party to receive paper Memo of InvoicePR PayerRI Remit ToRL Reporting LocationSE Selling PartySJ Service Provider



N103 66 Identification Code Qualifier X ID 1/2Code designating the system/method of code structure used forIdentification Code (67).--> Code values '41', '42', and '91' are the only valid values at HL1(Service Provider).







N104 67 Identification Code X AN 2/17Code identifying a party or other code.If N103 = "41" - Use Bellcore CIC list.

If n103 = "42" - Use Pseudo-CIC list provided in section 10.4.


811-46 JUNE 1995




Notes:Syntax Notes:






JUNE 1995 811-47




Notes:Syntax Notes:






811-48 JUNE 1995
















JUNE 1995 811-49







>> REF01 128 Reference Number Qualifier M ID 2/2Code qualifying the Reference Number.Refer to code list provided in the REF segment in Table 2 position 50.

--> '10', 'CR', 'EF', 'GT', 'IV', 'LB', 'RT', 'TF', and 'VC' are the only validcodes at HL1 (Service Provider).




811-50 JUNE 1995



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

directedNotes:





AD Accounting DepartmentBD Buyer Name or DepartmentBI Bill Inquiry Contact

Service Provider contact for making inquires aboutinformation on the invoice

CC Computer Systems ContactDA Directory Advertising Contact

Service Provider contact for questions about, andchanges to, directory advertising

IC Information ContactMA Maintenance Contact

Service Provider contact for requesting servicemaintainance, or reporting problems

OC Order ContactOD Order DepartmentPM Product ManagerQA Quality Assurance ContactSR Sales Representative or DepartmentTR Technical Marketing Representative

PER02 93 Name O AN 1/35Free-form name.




PER05 365 Communication Number Qualifier X ID 2/2


JUNE 1995 811-51




811-52 JUNE 1995








trading partners.




TXI03 954 Percent X R 1/10Percentage expressed as a decimalTax rate for this jurisdiction.







A AddD Delete


JUNE 1995 811-53

O Information Only




811-54 JUNE 1995

Segment: ITA Allowance, Charge or ServicePosition: 180

Loop: ITALevel: Detail

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

Notes:Syntax Notes: 1 If ITA08 is present, then ITA09 is required.

2 If ITA10 is present, then ITA11 is required.3 If ITA15 is present, then ITA02 is required.4 If ITA02 is present, then at least one of ITA03 ITA13 or ITA14 is required.

Semantic Notes: 1 ITA12 is the quantity of free goods.Comments: 1 If ITA01 = 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 ITA14.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.


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

A AllowanceC ChargeN No Allowance or Charge

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

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

Code identifying the special service.See section 10.4 for valid values.

>> 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 CustomerZZ Mutually Defined

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

ITA07 360 Allowance or Charge Total Amount O N2 1/9Total dollar amount for the allowance or charge.

ITA08 378 Allowance/ Charge Percent Qualifier O ID 1/1Code indicating on what basis allowance or charge percent is calculated.

9 Late Payment Charge Base Amount


JUNE 1995 811-55

Amount outstanding after the past due date, andsubject to a late payment charge

ITA09 332 Allowance or Charge Percent X R 1/6Allowance or charge expressed as a percent.

ITA10 339 Allowance or Charge Quantity O R 1/10Quantity basis when allowance or charge quantity is different from thepurchase order or invoice quantity.

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








Number of directory books delivered to customerEA EachEB Electronic Mail Boxes







Kilopackets of data transmitted


811-56 JUNE 1995

KJ KilosegmentsKilosegments of data transmitted

M0 Magnetic TapesNumber of Magnetic Tapes delivered with data

M4 Monetary ValueMJ MinutesMO MonthsMR MeterNF Messages



















ITA13 352 Description X AN 1/80


JUNE 1995 811-57

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

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

ITA16 662 Relationship Code O ID 1/1Code indicating the relationship of the price or amount to the associatedsegment.--> 'I' is only valid at HLs 4 - 9.

A AddD DeleteI IncludedO Information Only


811-58 JUNE 1995






Comments:








JUNE 1995 811-59








trading partners.











A AddD Delete


811-60 JUNE 1995

O Information Only




JUNE 1995 811-61

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

Loop: IT1Level: Detail

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

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

only appear at the group level.

Syntax Notes: 1 If IT106 is present, then IT107 is required.2 If IT108 is present, then IT109 is required.3 If IT110 is present, then IT111 is required.4 If IT112 is present, then IT113 is required.5 If IT114 is present, then IT115 is required.6 If IT116 is present, then IT117 is required.7 If IT118 is present, then IT119 is required.8 If IT120 is present, then IT121 is required.9 If IT122 is present, then IT123 is required.10 If IT124 is present, then IT125 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 ID's.2 IT106 through IT125 provides for ten (10) different product/service ID's for

each item. For example: Case, Color, Drawing No., UPC No., ISBN No.,Model No., SKU.


IT101 350 Assigned Identification O AN 1/11Alphanumeric characters assigned for differentiation within a transactionset.

>> IT102 358 Quantity Invoiced M R 1/10Number of units invoiced (supplier units).

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

EA EachM4 Monetary ValueMO Months

>> IT104 212 Unit Price M R 1/14Price per unit of product, service, commodity, etc.

IT105 639 Basis of Unit Price Code O ID 2/2Code identifying the type of unit price for an item.

BD Before DiscountFull amount for the service prior to application ofany appropriate discounts

CP Current Price (Subject to Change)


811-62 JUNE 1995

CT ContractPE Price per EachPM Monthly Price Per UnitTE Contract Price per Each

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

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

Identifying number for a product or service.See section 10.4 for valid values.


JUNE 1995 811-63





















811-64 JUNE 1995













JUNE 1995 811-65




















811-66 JUNE 1995

Segment: INC Installment InformationPosition: 240


Usage: OptionalMax Use: 1Purpose: To specify installment billing arrangement

Notes: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:


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

04 Deferred or Installment>> INC02 355 Unit or Basis for Measurement Code M ID 2/2

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

MO Months>> INC03 380 Quantity M R 1/15

Numeric value of quantity.Indicates the total number of installments.

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

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


JUNE 1995 811-67








trading partners.











A AddD Delete


811-68 JUNE 1995

O Information Only




JUNE 1995 811-69











811-70 JUNE 1995






Comments:



001 Cancel After003 Invoice009 Process035 Delivered092 Contract Effective093 Contract Expiration102 Issue150 Service Period Start151 Service Period End152 Effective Date of Change





JUNE 1995 811-71

Segment: MSG Message TextPosition: 280


Usage: OptionalMax Use: >1Purpose: To provide a free form format that would allow the transmission of text

information.Notes:


Comments: 1 MSG02 is not related to the specific characteristics of a printer, but identifiestop of page, advance a line, etc.


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


811-72 JUNE 1995




Notes:Syntax Notes:



>> QTY01 673 Quantity Qualifier M ID 2/2Code specifying the type of quantity.Refer to code list provided in the QTY segment in Table 2 position 90.


QTY03 355 Unit or Basis for Measurement Code O ID 2/2Code specifying the units in which a value is being expressed, or mannerin which a measurement has been takenRefer to code list provided in the QTY segment in Table 2 position 90.


JUNE 1995 811-73





















811-74 JUNE 1995













JUNE 1995 811-75








segment.










ITA06 359 Allowance or Charge Rate O R 1/9Allowance or Charge Rate per Unit.


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


811-76 JUNE 1995

Code indicating on what basis allowance or charge percent is calculated.9 Late Payment Charge Base Amount




ITA11 355 Unit or Basis for Measurement Code X ID 2/2Code specifying the units in which a value is being expressed, or mannerin which a measurement has been takenRefer to code list provided in the ITA segment in Table 2 position 180.

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

ITA14 150 Special Charge or Allowance Code X ID 3/3Code identifying type of special charge or allowance.See section 10.4 for valid values.

ITA16 662 Relationship Code O ID 1/1Code indicating the relationship of the price or amount to the associatedsegment.



JUNE 1995 811-77






Comments:



007 Effective009 Process035 Delivered092 Contract Effective093 Contract Expiration102 Issue150 Service Period Start151 Service Period End152 Effective Date of Change





811-78 JUNE 1995








trading partners.












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


JUNE 1995 811-79

or taxTXI09 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.


811-80 JUNE 1995













Identifies a gateway access providerIA Installed AtP9 Primary Interexchange Carrier (PIC)


PE PayeePM Party to receive paper Memo of InvoicePR PayerRI Remit ToRL Reporting LocationSE Selling PartySJ Service Provider


N102 93 Name X AN 1/35


JUNE 1995 811-81

Free-form name.N103 66 Identification Code Qualifier X ID 1/2

Code designating the system/method of code structure used forIdentification Code (67).







N104 67 Identification Code X AN 2/17Code identifying a party or other code.If N103 = "41" - Use Bellcore CIC list.If N103 = "42" - Use Pseudo-CIC list in section 10.4.


811-82 JUNE 1995




Notes:Syntax Notes:






JUNE 1995 811-83




Notes:Syntax Notes:






811-84 JUNE 1995
















JUNE 1995 811-85




directedNotes:


















811-86 JUNE 1995




JUNE 1995 811-87

Segment: SLN Subline Item DetailPosition: 390

Loop: SLNLevel: Detail

Usage: OptionalMax Use: 1Purpose: To specify product subline detail item data

Notes: The SLN loop may only appear at HL8 (Charge Detail Level).

Syntax Notes: 1 If SLN07 is present, then SLN06 is required.2 If SLN08 is present, then SLN06 is required.3 If SLN09 is present, then SLN10 is required.4 If SLN11 is present, then SLN12 is required.5 If SLN13 is present, then SLN14 is required.6 If SLN15 is present, then SLN16 is required.7 If SLN17 is present, then SLN18 is required.8 If SLN19 is present, then SLN20 is required.9 If SLN21 is present, then SLN22 is required.10 If SLN23 is present, then SLN24 is required.11 If SLN25 is present, then SLN26 is required.12 If SLN27 is present, then SLN28 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.Comments: 1 See the Data Dictionary for a complete list of ID's.

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 (10) different product/service ID's foreach item. For example: Case, Color, Drawing No., UPC No., ISBN No.,Model No., SKU.


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

SLN02 350 Assigned Identification O AN 1/11Alphanumeric characters assigned for differentiation within a transactionset.

>> SLN03 661 Configuration Code M ID 1/1Code indicating the relationship of the subline item to the baseline item.

I Included>> SLN04 380 Quantity M R 1/15

Numeric value of quantity.>> SLN05 355 Unit or Basis for Measurement Code M ID 2/2


03 Seconds12 Packet1X Quarter Mile


811-88 JUNE 1995

AD BytesNumber of bytes of data transmitted

AH Additional MinutesThe minutes, usually associated with usage-sensitive pricing of telecommunication services,which are above the minutes allowed for thatparticular service


















JUNE 1995 811-89

















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


811-90 JUNE 1995

SLN07 639 Basis of Unit Price Code O ID 2/2Code identifying the type of unit price for an item.

BD Before DiscountFull amount for the service prior to application ofany appropriate discounts

CP Current Price (Subject to Change)CT ContractDP Daily Price per UnitPB Annual Price Per Unit

Price changed Once per YearPE Price per EachPM Monthly Price Per UnitTE Contract Price per EachTP Price per ThousandWI Weekly Price per Unit

Price charged once per weekSLN08 662 Relationship Code O ID 1/1

Code indicating the relationship of the price or amount to the associatedsegment.


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

SV Service RenderedSLN10 234 Product/Service ID X AN 1/30

Identifying number for a product or service.See section 10.4 for valid values.


JUNE 1995 811-91





















811-92 JUNE 1995













JUNE 1995 811-93




















811-94 JUNE 1995

Segment: CUR CurrencyPosition: 420


Usage: OptionalMax Use: 1Purpose: To specify the currency (dollars, pounds, francs, etc.) used in a transaction

Notes:Syntax Notes: 1 If CUR08 is present, then CUR07 is required.

2 If CUR09 is present, then CUR07 is required.3 If CUR11 is present, then CUR10 is required.4 If CUR12 is present, then CUR10 is required.5 If CUR14 is present, then CUR13 is required.6 If CUR15 is present, then CUR13 is required.7 If CUR17 is present, then CUR16 is required.8 If CUR18 is present, then CUR16 is required.9 If CUR20 is present, then CUR19 is required.10 If CUR21 is present, then CUR19 is required.

Semantic Notes:Comments: 1 See Figures Appendix for examples detailing the use of the CUR segment.


>> CUR01 98 Entity Identifier Code M ID 2/2Code identifying an organizational entity, a physical location, or anindividual

PR Payer>> CUR02 100 Currency Code M ID 3/3

Code (Standard ISO) for country in whose currency the charges arespecified.For additional values, request ISO document 4217.


CUR03 280 Exchange Rate O R 4/6Value to be used as a multiplier conversion factor to convert monetaryvalue from one currency to another.

CUR04 98 Entity Identifier Code O ID 2/2Code identifying an organizational entity, a physical location, or anindividual

PE PayeePM Party to receive paper Memo of InvoiceRI Remit ToSE Selling PartySJ Service Provider


CUR05 100 Currency Code O ID 3/3Code (Standard ISO) for country in whose currency the charges arespecified.


JUNE 1995 811-95


CUR06 669 Currency Market/Exchange Code O ID 3/3Code identifying the market upon which the currency exchange rate isbased.

IMF International Monetary FundLNF London (England) Exchange - First ClosingLNS London (England) Exchange - Second ClosingNYC New York Foreign ExchangePHI Philadelphia Foreign ExchangeZUR Zurich (Switzerland) Exchange

CUR07 374 Date/Time Qualifier X ID 3/3Code specifying type of date or time, or both date and time.



CUR08 373 Date O DT 6/6Date (YYMMDD).

CUR09 337 Time O TM 4/8Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, orHHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimalseconds are expressed as follows: D = tenths (0-9) and DD = hundredths(00-99)


811-96 JUNE 1995

Segment: INC Installment InformationPosition: 430


Usage: OptionalMax Use: 1Purpose: To specify installment billing arrangement

Notes: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:


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

04 Deferred or Installment>> INC02 355 Unit or Basis for Measurement Code M ID 2/2


MO Months>> INC03 380 Quantity M R 1/15

Numeric value of quantity.Indicates the total number of installments.

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

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


JUNE 1995 811-97








segment.












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


811-98 JUNE 1995

Code indicating on what basis allowance or charge percent is calculated.9 Late Payment Charge Base Amount










JUNE 1995 811-99








trading partners.












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


811-100 JUNE 1995

or taxTXI09 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.


JUNE 1995 811-101











811-102 JUNE 1995




directedNotes:


















JUNE 1995 811-103




811-104 JUNE 1995






Comments:








JUNE 1995 811-105

Segment: AMT Monetary AmountPosition: 490


Usage: OptionalMax Use: 10Purpose: To indicate the total monetary amount.

Notes:Syntax Notes:



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

1 Line Item Total5 Total Invoice Amount6 Amount Subject to Total Monetary Discount8 Total Monetary Discount AmountAD Adjusted TotalAP Amount Prior to Fractionalization

Full charge amount for the service per serviceperiod, prior to pro-rated fractionalization due topartial period billing

AQ Average Price Per CallThe total amount of money associated with acategory of calls divided by the total number ofcalls within the category calculated to provide callsummary details

AS Average Price Per MinuteThe total amount of money associated with acategory of calls divided by the total number ofminutes within the category calculated to providecall summary details

AX Previous PriceBT Bank Reject TotalCH Change AmountCS Commission Sales

Those sales used to calculate commissionpayments

CT ContractIndicates the value stated in the contract

KO Committed AmountLI Line Item Unit PriceN Net

Indicates the value remaining after all deductionsand adjustments have been made

NA Net Adjustment


811-106 JUNE 1995

NO Non Commission SalesThose sales not included for commission paymentcalculation

NS Net Savings AmountAmount of dollar saving resulting from the use ofservice, such as Optional Calling Plans


SC Total Service ChargeTP Total payment amountTS Total Sales

The total of commission and non commission salesneeded to calculate intersell amount

TT Total Transaction Amount>> AMT02 782 Monetary Amount M R 1/15

Monetary amount.


JUNE 1995 811-107

Segment: MSG Message TextPosition: 500


Usage: OptionalMax Use: >1Purpose: To provide a free form format that would allow the transmission of text

information.Notes:


Comments: 1 MSG02 is not related to the specific characteristics of a printer, but identifiestop of page, advance a line, etc.


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


811-108 JUNE 1995




Notes:Syntax Notes:







JUNE 1995 811-109





















811-110 JUNE 1995













JUNE 1995 811-111













Identifies a gateway access providerIA Installed AtP9 Primary Interexchange Carrier (PIC)


PE PayeePM Party to receive paper Memo of InvoicePR PayerRI Remit ToRL Reporting LocationSE Selling PartySJ Service Provider


N102 93 Name X AN 1/35


811-112 JUNE 1995

Free-form name.N103 66 Identification Code Qualifier X ID 1/2

Code designating the system/method of code structure used forIdentification Code (67).






91 Assigned by Seller or Seller's Agent92 Assigned by Buyer or Buyer's AgentZY Temporary Identification Number

A temporary ID to be used until a permanent ID isprocessed

N104 67 Identification Code X AN 2/17Code identifying a party or other code.If N103 = "41" - Use Bellcore CIC list.

If N103 = "42" - Use Pseudo-CIC list provided in section 10.4.


JUNE 1995 811-113




Notes:Syntax Notes:






811-114 JUNE 1995




Notes:Syntax Notes:






JUNE 1995 811-115
















811-116 JUNE 1995











JUNE 1995 811-117




directedNotes:


















811-118 JUNE 1995




JUNE 1995 811-119

Segment: TCD Itemized Call DetailPosition: 590

Loop: TCDLevel: Detail

Usage: OptionalMax Use: 1Purpose: To specify detail information for itemized calls

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

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


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

TCD02 373 Date O DT 6/6Date (YYMMDD).

TCD03 337 Time O TM 4/8Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, orHHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimalseconds are expressed as follows: D = tenths (0-9) and DD = hundredths(00-99)Connect time of call.

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

A value of "ZZ" indicates any point of origination/termination or service fora call that cannot be qualified by traditional geographic qualifiers (i.e., Cityor 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.


811-120 JUNE 1995

AC City and StateCC CountryCI CitySP State/ProvinceZZ 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 location.Code identifying the type of "FROM" location in TCD08 and TCD09.

A value of "ZZ" indicates any point of origination/termination or service fora call that cannot be qualified by traditional geographic qualifiers (i.e., Cityor 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.

AC City and StateCC CountryCI CitySP State/ProvinceZZ 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.

TCD10 739 Measurement Value O R 1/10The value of the measurement.Duration of call measured in minutes and tenths of minutes.

TCD11 739 Measurement Value O R 1/10The value of the measurement.Duration of call measured in seconds and tenths of seconds.

TCD12 782 Monetary Amount O R 1/15Monetary amount.Undiscounted amount.

TCD13 782 Monetary Amount O R 1/15Monetary amount.Net amount after a discount has been applied to the amount in TCD12.


JUNE 1995 811-121

TCD14 782 Monetary Amount O R 1/15Monetary amount.Undiscounted amount.

TCD15 782 Monetary Amount O R 1/15Monetary amount.Net amount after a discount has been applied to the amount in TCD14.

TCD16 662 Relationship Code O ID 1/1Code indicating the relationship of the price or amount to the associatedsegment.



811-122 JUNE 1995





















JUNE 1995 811-123













811-124 JUNE 1995








trading partners.














JUNE 1995 811-125








segment.














811-126 JUNE 1995










JUNE 1995 811-127




Notes:Syntax Notes:







811-128 JUNE 1995





















JUNE 1995 811-129













811-130 JUNE 1995

Segment: USD Usage Sensitive DetailPosition: 620

Loop: USDLevel: Detail

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

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

Syntax Notes: 1 Only one of USD03 or USD04 may be present.2 If USD03 is present, then at least one of USD06 USD07 or USD08 is

required.3 If USD04 is present, then at least one of USD08 or USD09 is required.4 If USD06 is present, then USD05 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 USD14 is present, then USD13 is required.8 If either USD14 or USD15 is present, then the other is required.9 If USD16 is present, then USD13 is required.10 If USD16 is present, then USD17 is required.

Semantic Notes: 1 USD04 is the discount percentage.2 USD06 is the quantity of usage.3 USD07 is a quantity of usage different than the quantity in USD06. When

USD07 is present, it is used in conjuction with USD06 and then the rateUSD03 is applied.

Comments: 1 If both USD03 and USD08 are present, 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.4 USD13 defines the source for each of the Service Characteristic Qualifiers.


>> USD01 662 Relationship Code M ID 1/1Code indicating the relationship of the price or amount to the associatedsegment.


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

USD03 359 Allowance or Charge Rate X R 1/9Allowance or Charge Rate per Unit.If both USD03 and USD08 are present, then USD08 takes precendence.

USD04 954 Percent X R 1/10Percentage expressed as a decimalDiscount percentage.


JUNE 1995 811-131

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

















Number of Magnetic Tapes delivered with dataM4 Monetary ValueMJ Minutes


811-132 JUNE 1995

MO MonthsMR MeterNF Messages



















USD06 380 Quantity X R 1/15Numeric value of quantity.

USD07 380 Quantity X R 1/15Numeric value of quantity.A quantity of usage different from the quantity of usage in USD06.

When USD07 is present, it is used in conjunction with USD06 and then


JUNE 1995 811-133

the rate in USD03 is applied.

USD08 782 Monetary Amount X R 1/15Monetary amount.

USD09 362 Terms Discount Amount X N2 1/10Total amount of terms discount.

USD10 355 Unit or Basis for Measurement Code O ID 2/2Code specifying the units in which a value is being expressed, or mannerin which a measurement has been takenSee USD05 for code list.

USD11 740 Range Minimum X R 1/10The value specifying the minimum of the measurement range.If USD11 is present and USD12 is not present, then the range is open-ended.

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

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

TI Telecommunications IndustryUSD14 1000 Service Characteristics Qualifier X ID 2/2


USD15 234 Product/Service ID X AN 1/30Identifying number for a product or service.

USD16 1000 Service Characteristics Qualifier O ID 2/2Code from an industry code list qualifying the type of servicecharacteristics.

USD17 234 Product/Service ID X AN 1/30Identifying number for a product or service.


811-134 JUNE 1995








segment.














JUNE 1995 811-135










811-136 JUNE 1995

Segment: TRF Rating FactorsPosition: 640


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

Notes:Syntax Notes:

Semantic Notes:Comments: 1 TRF01 defines the rating basis (e.g., acknowledged calls, minimum period,

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


>> TRF01 673 Quantity Qualifier M ID 2/2Code specifying the type of quantity.Code specifying the rating basis (e.g., acknowledged calls, minimumperiod, etc.) for the segment.

01 Discrete Quantity02 Cumulative Quantity27 Committed Quantity38 Original Quantity47 Primary Net Quantity90 Acknowledged Quantity

Network Recognition for message receipt91 Additional Usage Quantity

The amount of usage incurred above the alloted orallowable use for a service

92 Allotted Usage QuantityThe amount of allowable usage related to a service

93 Attendant-Handled QuantityManual Recognition for message receipt

94 Billable QuantityNumber of billable units used

95 Data Storage QuantityNumber of storage units used

96 Non-Billable QuantityNumber of non-billable units

97 Non-Urgent Delivery QuantityNumber of units delivered in non-urgent status

98 Overflow QuantityNumber of overflow messages, (Busy conditioncount for 800 service)

99 Quantity Used


JUNE 1995 811-137

Quantity of units usedAA Unacknowledged Quantity

Message received without network, or attendantrecognition

AB Urgent Delivery QuantityNumber of units delivered in urgent status

AC Voice Storage QuantityNumber of voice storage units used

AD Maintenance UnitsNumber of units of maintenance provided

AE Minimum Average Time Requirement (MATR)UnitsNumber of units calculated at a minimum usagerating basis, such as X minutes per message

AF Wide Area Telephone Service (WATS)/800 ServiceUnitsNumber of units of usage, for WATS or 800 service

AG Number of End UsersNumber of participating users

AH Number of Message RecipientsNumber of recipients

AI Number of Operator CreditsNumber of operator credits given

AJ Daily AdjustmentsNS Number of Stations

Number of stations, or terminating points, whichare in use, deleted, added, etc. for service delivery;ports or lines on a computer, for example

>> TRF02 355 Unit or Basis for Measurement Code M ID 2/2Code specifying the units in which a value is being expressed, or mannerin which a measurement has been takenEquivalent units per standard unit.






DA DaysDC Disk (Disc)


811-138 JUNE 1995

DH MilesDK KilometersDQ Data Records





















JUNE 1995 811-139











>> TRF03 380 Quantity M R 1/15Numeric value of quantity.Standard unit.

>> TRF04 355 Unit or Basis for Measurement Code M ID 2/2Code specifying the units in which a value is being expressed, or mannerin which a measurement has been takenEquivalent units per standard unit.

See TRF02 for code list.

>> TRF05 380 Quantity M R 1/15Numeric value of quantity.Standard unit.


811-140 JUNE 1995




Notes:Syntax Notes:







JUNE 1995 811-141





















811-142 JUNE 1995













JUNE 1995 811-143

Segment: TDS Total Monetary Value SummaryPosition: 010

Loop:Level: Summary

Usage: MandatoryMax Use: 1Purpose: To specify the total invoice discounts and amounts

Notes:Syntax Notes:

Semantic Notes:Comments: 1 TDS02 is required if the dollar value subject to discount is not equal to the

dollar value of TDS01.


>> TDS01 361 Total Invoice Amount M N2 1/10Amount of invoice (including charges, less allowances) before termsdiscount (if discount is applicable).Total current month invoiced amount.


811-144 JUNE 1995


Loop: ITALevel: Summary






segment.








03 Vendor Check to Customer04 Credit Customer Account06 Charge to be Paid by CustomerZZ Mutually Defined





JUNE 1995 811-145

9 Late Payment Charge Base AmountAmount outstanding after the past due date, andsubject to a late payment charge









811-146 JUNE 1995






Comments:



007 Effective009 Process050 Received




JUNE 1995 811-147

Segment: BAL Balance DetailPosition: 040

Loop: BALLevel: Summary

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

Notes:Syntax Notes:



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

A AdjustmentM Current MonthP Previous Month

Balance of previous period charges prior toapplying payments and adjustments for theprevious period billing

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

5 Total Invoice Amount8 Total Monetary Discount AmountBT Bank Reject TotalC4 Prior Payment - Actual

Amount paid in reality at an earlier timeNA Net AdjustmentNS Net Savings Amount

Amount of dollar saving resulting from the use ofservice, such as Optional Calling Plans


SC Total Service ChargeTP Total payment amountTT Total Transaction Amount

>> BAL03 782 Monetary Amount M R 1/15Monetary amount.


811-148 JUNE 1995






Comments:



007 Effective009 Process050 Received




JUNE 1995 811-149


Loop: N1Level: Summary








SJ Service ProviderIdentifies name and address information aspertaining to a service provider for which billing isbeing rendered


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



91 Assigned by Seller or Seller's AgentN104 67 Identification Code X AN 2/17

Code identifying a party or other code.If N103 = "41" - Use Bellcore CIC list.

If N103 = "42" - Use Pseudo-CIC list provided in section 10.4.


811-150 JUNE 1995

Segment: BAL Balance DetailPosition: 070


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

Notes:Syntax Notes:



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

A AdjustmentM Current MonthP Previous Month

Balance of previous period charges prior toapplying payments and adjustments for theprevious period billing

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

AD Adjusted TotalC4 Prior Payment - Actual

Amount paid in reality at an earlier time>> BAL03 782 Monetary Amount M R 1/15

Monetary amount.


JUNE 1995 811-151






Comments:



003 Invoice007 Effective009 Process050 Received




811-152 JUNE 1995








segment.












ITA09 332 Allowance or Charge Percent X R 1/6


JUNE 1995 811-153

Allowance or charge expressed as a percent.ITA10 339 Allowance or Charge Quantity O R 1/10

Quantity basis when allowance or charge quantity is different from thepurchase order or invoice quantity.





O Information Only


811-154 JUNE 1995






Comments:



007 Effective009 Process




JUNE 1995 811-155

Segment: CTT Transaction TotalsPosition: 110

Loop:Level: Summary

Usage: OptionalMax Use: 1Purpose: To transmit a hash total for a specific element in the transaction set

Notes: The number of line items (CTT01) is the accumulation of the number of IT1segments.

Syntax Notes: 1 If CTT03 is present, then CTT04 is required.2 If CTT05 is present, then CTT06 is required.

Semantic Notes:Comments: 1 This segment is intended to provide hash totals to validate transaction

completeness and correctness.


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

CTT02 347 Hash Total O R 1/10Sum of values of the specified data element. All values in the dataelement will be summed without regard to decimal points (explicit orimplicit) or signs. Truncation will occur on the left most digits if the sum isgreater than the maximum size of the hash total of the data element.Example: -.0018 First occurrence of value being hashed. .18 Secondoccurrence of value being hashed. 1.8 Third occurrence of value beinghashed. 18.01 Fourth occurrence of value being hashed. ------- 1855Hash total prior to truncation. 855 Hash total after truncation to three-digitfield.If used, the specified field for the Telecommunications Industry is IT104.


811-156 JUNE 1995

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).Notes:


Comments: 1 SE is the last segment of each transaction set.


>> SE01 96 Number of Included Segments M N0 1/10Total number of segments included in a transaction set including ST andSE segments.

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

811 transaction set (x12 version 004010) - granite guard€¦ · 1 overview _____ 4 1.1 schedule of...

Documents