X12 811 Consolidated Service Invoice/Statement
This Draft Standard for Trial Use contains the format and establishes the data contents of the Consolidated Service Invoice/Statement Transaction Set (811) for use within the context of an Electronic Data Interchange (EDI) environment.
This transaction set provides for the billing or reporting of complex and structured service invoice/statement detail.
This standard can be used by organizations who are interested in sending or receiving either consolidated or standalone invoices for service arrangements which require processing other than that done for the typical product invoice.
The Consolidated Service Invoice/Statement can be used as a credit/debit memo to differentiate between payable invoice items and information-only memo items.
This transaction set should not be used as a standalone notification of a credit/debit adjustment.
- ~ Segment
- * Element
- > Component
- None included
Interchange Control Header
To start and identify an interchange of zero or more functional groups and interchange-related control segments
Code to identify the type of information in the Authorization Information
- 00
- No Authorization Information Present (No Meaningful Information in I02)
Information used for additional identification or authorization of the interchange sender or the data in the interchange; the type of information is set by the Authorization Information Qualifier (I01)
Code to identify the type of information in the Security Information
- 00
- No Security Information Present (No Meaningful Information in I04)
This is used for identifying the security information about the interchange sender or the data in the interchange; the type of information is set by the Security Information Qualifier (I03)
Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified
Identification code published by the sender for other parties to use as the receiver ID to route data to them; the sender always codes this value in the sender ID element
Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified
Identification code published by the receiver of the data; When sending, it is used by the sender as their sending ID, thus other parties sending to them will use this as a receiving ID to route data to them
Code to identify the agency responsible for the control standard used by the message that is enclosed by the interchange header and trailer
- U
- U.S. EDI Community of ASC X12, TDCC, and UCS
This version number covers the interchange control segments
- 00401
- Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1997
A control number assigned by the interchange sender
Code sent by the sender to request an interchange acknowledgment (TA1)
- 0
- No Acknowledgment Requested
- 1
- Interchange Acknowledgment Requested
Code to indicate whether data enclosed by this interchange envelope is test, production or information
- I
- Information
- P
- Production Data
- T
- Test Data
Type is not applicable; the component element separator is a delimiter and not a data element; this field provides the delimiter used to separate component data elements within a composite data structure; this value must be different than the data element separator and the segment terminator
- >
- Component Element Separator
Functional Group Header
To indicate the beginning of a functional group and to provide control information
Code identifying a group of application related transaction sets
- CI
- Consolidated Service Invoice/Statement (811)
Code identifying party sending transmission; codes agreed to by trading partners
Code identifying party receiving transmission. Codes agreed to by trading partners
Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)
Assigned number originated and maintained by the sender
Code used in conjunction with Data Element 480 to identify the issuer of the standard
- T
- Transportation Data Coordinating Committee (TDCC)
- X
- Accredited Standards Committee X12
Code indicating the version, release, subrelease, and industry identifier of the EDI standard being used, including the GS and GE segments; if code in DE455 in GS segment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 are the release and subrelease, level of the version; and positions 7-12 are the industry or trade association identifiers (optionally assigned by user); if code in DE455 in GS segment is T, then other formats are allowed
- 004010
- Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1997
Heading
Transaction Set Header
To indicate the start of a transaction set and to assign a control number
Code uniquely identifying a Transaction Set
- The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
- 811
- Consolidated Service Invoice/Statement
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Beginning Segment for Invoice
To indicate the beginning of an invoice transaction set and transmit identifying numbers and dates
Date expressed as CCYYMMDD
- BIG01 is the invoice issue date.
Code specifying the type of transaction
- BIG07 is used only to further define the type of invoice when needed.
Reference Identification
To specify identifying information
Code qualifying the Reference Identification
- IK
- Invoice Number
- IT
- Internal Customer Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Terms of Sale/Deferred Terms of Sale
To specify terms of sale
Date when total invoice amount becomes due expressed in format CCYYMMDD
Date/Time Reference
To specify pertinent dates and times
Name
To identify a party by type of organization, name, and code
Address Information
To specify the location of the named party
Geographic Location
To specify the geographic place of the named party
Free-form text for city name
- A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
Code (Standard State/Province) as defined by appropriate government agency
- N402 is required only if city name (N401) is in the U.S. or Canada.
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
Detail
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
- Valid codes for HL03 to define levels for this transaction set are given below:
1 - Service/Billing Provider (Identifies the Company Providing the Service/Billing)
2 - Billing Arrangement (Identifies a Specific Billing Arrangement)
3 - Sub-billing Arrangement (Identifies a More Detailed Billing Arrangement)
4 - Group (Identifies a Group of Charges on the Bill)
5 - Category (Identifies the Subdivision of the Group)
6 - Subcategory (Identifies a Further Breakdown of the Category)
7 - Type (Identifies a Further Breakdown of the Subcategory)
8 - Charge Detail (Identifies the Lowest Level of Charges within a Billing Arrangement)
9 - Line Detail (Identifies the Supporting Detail Associated with the Charge or Group Level)
They must be used in the (hierarchical) order in which they are listed; however, certain levels are optional and may be omitted. At least one occurrence each of the service/billing provider level and group level is required.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
- HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
Code defining the characteristic of a level in a hierarchical structure
- HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
- 1
- Service/Billing Provider
Code indicating if there are hierarchical child data segments subordinate to the level being described
- HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
- 0
- No Subordinate HL Segment in This Hierarchical Structure.
- 1
- Additional Subordinate HL Data Segment in This Hierarchical Structure.
Assigned Number
To reference a line number in a transaction set
Number assigned for differentiation within a transaction set
Product/Item Description
To describe a product or process in coded or free-form format
Code indicating the format of a description
- If PID01 equals "F", then PID05 is used. If PID01 equals "S", then PID04 is used. If PID01 equals "X", then both PID04 and PID05 are used.
Code identifying the general class of a product or process characteristic
Code identifying the agency assigning the code values
- Use PID03 to indicate the organization that publishes the code list being referred to.
A code from an industry code list which provides specific data about a product characteristic
- PID04 should be used for industry-specific product description codes.
A free-form description to clarify the related data elements and their content
Reference Identification
To specify identifying information
Code qualifying the Reference Identification
- ZZ
- Mutually Defined
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
A free-form description to clarify the related data elements and their content
Quantity
To specify quantity information
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
- Valid codes for HL03 to define levels for this transaction set are given below:
1 - Service/Billing Provider (Identifies the Company Providing the Service/Billing)
2 - Billing Arrangement (Identifies a Specific Billing Arrangement)
3 - Sub-billing Arrangement (Identifies a More Detailed Billing Arrangement)
4 - Group (Identifies a Group of Charges on the Bill)
5 - Category (Identifies the Subdivision of the Group)
6 - Subcategory (Identifies a Further Breakdown of the Category)
7 - Type (Identifies a Further Breakdown of the Subcategory)
8 - Charge Detail (Identifies the Lowest Level of Charges within a Billing Arrangement)
9 - Line Detail (Identifies the Supporting Detail Associated with the Charge or Group Level)
They must be used in the (hierarchical) order in which they are listed; however, certain levels are optional and may be omitted. At least one occurrence each of the service/billing provider level and group level is required.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
- HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
- HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
Code defining the characteristic of a level in a hierarchical structure
- HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
- 2
- Billing Arrangement
Code indicating if there are hierarchical child data segments subordinate to the level being described
- HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
- 0
- No Subordinate HL Segment in This Hierarchical Structure.
- 1
- Additional Subordinate HL Data Segment in This Hierarchical Structure.
Assigned Number
To reference a line number in a transaction set
Number assigned for differentiation within a transaction set
Service Characteristic Identification
To specify service characteristic data
Code identifying the agency assigning the code values
- SI01 defines the source for each of the service characteristics qualifiers.
Code from an industry code list qualifying the type of service characteristics
Product/Item Description
To describe a product or process in coded or free-form format
Code indicating the format of a description
- If PID01 equals "F", then PID05 is used. If PID01 equals "S", then PID04 is used. If PID01 equals "X", then both PID04 and PID05 are used.
Code identifying the agency assigning the code values
- Use PID03 to indicate the organization that publishes the code list being referred to.
A code from an industry code list which provides specific data about a product characteristic
- PID04 should be used for industry-specific product description codes.
A free-form description to clarify the related data elements and their content
Monetary Amount
To indicate the total monetary amount
Date/Time Reference
To specify pertinent dates and times
Tax Information
To specify tax information
Monetary amount
- TXI02 is the monetary amount of the tax.
Code indicating the relationship between entities
- TXI07 is a code indicating the relationship of the price or amount to the associated segment.
Individual or Organizational Name
To supply the full name of an individual or organizational entity
- When used for telecommunications billing, the service/billing provider level is defined by the NM1 loop.
Code identifying an organizational entity, a physical location, property or an individual
Code qualifying the type of entity
- NM102 qualifies NM103.
Individual last name or organizational name
Code designating the system/method of code structure used for Identification Code (67)
Reference Identification
To specify identifying information
Code qualifying the Reference Identification
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Allowance, Charge or Service
To specify allowances, charges, or services
Code which indicates an allowance or charge for the service specified
- If ITA01 equals "A" - allowance or "C" - charge, then at least one of ITA06, ITA07, or ITA08 must be present.
Code identifying the agency assigning the code values
- ITA02 identifies the source of the code value in ITA03 or ITA15.
Code indicating method of handling for an allowance or charge
Total dollar amount for the allowance or charge
- If ITA07 is present with either ITA06 or ITA08, then ITA07 takes precedence.
Code indicating on what basis allowance or charge percent is calculated
Numeric value of quantity
- ITA10 is the quantity basis when the allowance or charge quantity is different from the purchase order or invoice quantity.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
A free-form description to clarify the related data elements and their content
- ITA13 is used to clarify the allowance, charge, or service.
Code identifying type of special charge or allowance
Code indicating the relationship between entities
- ITA16 describes the relationship of ITA06, ITA07 or ITA09 to an associated segment.
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
- Valid codes for HL03 to define levels for this transaction set are given below:
1 - Service/Billing Provider (Identifies the Company Providing the Service/Billing)
2 - Billing Arrangement (Identifies a Specific Billing Arrangement)
3 - Sub-billing Arrangement (Identifies a More Detailed Billing Arrangement)
4 - Group (Identifies a Group of Charges on the Bill)
5 - Category (Identifies the Subdivision of the Group)
6 - Subcategory (Identifies a Further Breakdown of the Category)
7 - Type (Identifies a Further Breakdown of the Subcategory)
8 - Charge Detail (Identifies the Lowest Level of Charges within a Billing Arrangement)
9 - Line Detail (Identifies the Supporting Detail Associated with the Charge or Group Level)
They must be used in the (hierarchical) order in which they are listed; however, certain levels are optional and may be omitted. At least one occurrence each of the service/billing provider level and group level is required.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
- HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
- HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
Code defining the characteristic of a level in a hierarchical structure
- HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
- 4
- Group
Code indicating if there are hierarchical child data segments subordinate to the level being described
- HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
- 0
- No Subordinate HL Segment in This Hierarchical Structure.
- 1
- Additional Subordinate HL Data Segment in This Hierarchical Structure.
Baseline Item Data (Invoice)
To specify the basic and most frequently used line item data for the invoice and related transactions
- The group level is defined by at least one occurrence of the IT1 loop which may only appear at the group level.
Alphanumeric characters assigned for differentiation within a transaction set
- IT101 is the purchase order line item identification.
Number of units invoiced (supplier units)
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
Price per unit of product, service, commodity, etc.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- IT106 through IT125 provide for ten different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
Identifying number for a product or service
Product/Item Description
To describe a product or process in coded or free-form format
Code indicating the format of a description
- If PID01 equals "F", then PID05 is used. If PID01 equals "S", then PID04 is used. If PID01 equals "X", then both PID04 and PID05 are used.
Code identifying the agency assigning the code values
- Use PID03 to indicate the organization that publishes the code list being referred to.
A code from an industry code list which provides specific data about a product characteristic
- PID04 should be used for industry-specific product description codes.
A free-form description to clarify the related data elements and their content
Quantity
To specify quantity information
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
- Valid codes for HL03 to define levels for this transaction set are given below:
1 - Service/Billing Provider (Identifies the Company Providing the Service/Billing)
2 - Billing Arrangement (Identifies a Specific Billing Arrangement)
3 - Sub-billing Arrangement (Identifies a More Detailed Billing Arrangement)
4 - Group (Identifies a Group of Charges on the Bill)
5 - Category (Identifies the Subdivision of the Group)
6 - Subcategory (Identifies a Further Breakdown of the Category)
7 - Type (Identifies a Further Breakdown of the Subcategory)
8 - Charge Detail (Identifies the Lowest Level of Charges within a Billing Arrangement)
9 - Line Detail (Identifies the Supporting Detail Associated with the Charge or Group Level)
They must be used in the (hierarchical) order in which they are listed; however, certain levels are optional and may be omitted. At least one occurrence each of the service/billing provider level and group level is required.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
- HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
- HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
Code defining the characteristic of a level in a hierarchical structure
- HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
- 8
- Charge Detail
Code indicating if there are hierarchical child data segments subordinate to the level being described
- HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
- 0
- No Subordinate HL Segment in This Hierarchical Structure.
- 1
- Additional Subordinate HL Data Segment in This Hierarchical Structure.
Subline Item Detail
To specify product subline detail item data
- The SLN loop may only appear at the charge detail level.
Alphanumeric characters assigned for differentiation within a transaction set
- SLN01 is the identifying number for the subline item.
- SLN01 is related to (but not necessarily equivalent to) the baseline item number. Example: 1.1 or 1A might be used as a subline number to relate to baseline number 1.
Code indicating the relationship between entities
- SLN03 is the configuration code indicating the relationship of the subline item to the baseline item.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
Price per unit of product, service, commodity, etc.
Code indicating the relationship between entities
- SLN08 is a code indicating the relationship of the price or amount to the associated segment.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- SLN09 through SLN28 provide for ten different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
Identifying number for a product or service
Service Characteristic Identification
To specify service characteristic data
Code identifying the agency assigning the code values
- SI01 defines the source for each of the service characteristics qualifiers.
Code from an industry code list qualifying the type of service characteristics
Product/Item Description
To describe a product or process in coded or free-form format
Code indicating the format of a description
- If PID01 equals "F", then PID05 is used. If PID01 equals "S", then PID04 is used. If PID01 equals "X", then both PID04 and PID05 are used.
Code identifying the agency assigning the code values
- Use PID03 to indicate the organization that publishes the code list being referred to.
A code from an industry code list which provides specific data about a product characteristic
- PID04 should be used for industry-specific product description codes.
A free-form description to clarify the related data elements and their content
Measurements
To specify physical measurements or counts, including dimensions, tolerances, variances, and weights
(See Figures Appendix for example of use of C001)
Date/Time Reference
To specify pertinent dates and times
Monetary Amount
To indicate the total monetary amount
Message Text
To provide a free-form format that allows the transmission of text information
Quantity
To specify quantity information
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
- Valid codes for HL03 to define levels for this transaction set are given below:
1 - Service/Billing Provider (Identifies the Company Providing the Service/Billing)
2 - Billing Arrangement (Identifies a Specific Billing Arrangement)
3 - Sub-billing Arrangement (Identifies a More Detailed Billing Arrangement)
4 - Group (Identifies a Group of Charges on the Bill)
5 - Category (Identifies the Subdivision of the Group)
6 - Subcategory (Identifies a Further Breakdown of the Category)
7 - Type (Identifies a Further Breakdown of the Subcategory)
8 - Charge Detail (Identifies the Lowest Level of Charges within a Billing Arrangement)
9 - Line Detail (Identifies the Supporting Detail Associated with the Charge or Group Level)
They must be used in the (hierarchical) order in which they are listed; however, certain levels are optional and may be omitted. At least one occurrence each of the service/billing provider level and group level is required.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
- HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
- HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
Code defining the characteristic of a level in a hierarchical structure
- HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
- 9
- Line Detail
Code indicating if there are hierarchical child data segments subordinate to the level being described
- HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
- 0
- No Subordinate HL Segment in This Hierarchical Structure.
Baseline Item Data (Invoice)
To specify the basic and most frequently used line item data for the invoice and related transactions
- The group level is defined by at least one occurrence of the IT1 loop which may only appear at the group level.
Alphanumeric characters assigned for differentiation within a transaction set
- IT101 is the purchase order line item identification.
Number of units invoiced (supplier units)
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
Price per unit of product, service, commodity, etc.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- IT106 through IT125 provide for ten different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
Identifying number for a product or service
Product/Item Description
To describe a product or process in coded or free-form format
Code indicating the format of a description
- If PID01 equals "F", then PID05 is used. If PID01 equals "S", then PID04 is used. If PID01 equals "X", then both PID04 and PID05 are used.
Code identifying the agency assigning the code values
- Use PID03 to indicate the organization that publishes the code list being referred to.
A code from an industry code list which provides specific data about a product characteristic
- PID04 should be used for industry-specific product description codes.
A free-form description to clarify the related data elements and their content
Quantity
To specify quantity information
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
Itemized Call Detail
To specify detail information for itemized calls
- The TCD loop may only appear at the line detail level.
Alphanumeric characters assigned for differentiation within a transaction set
- TCD01 is the detail information.
Date expressed as CCYYMMDD
- TCD02 is the date of the call.
Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)
- TCD03 is the connect time of the call.
Code identifying type of location
- TCD04, TCD05, and TCD06 are the 'to' location of the call.
The value of the measurement
- TCD10 and TCD11 are the total duration of the call. TCD10 is the time measured in minutes or minutes and tenths of minutes. TCD11 is time measured in seconds or seconds and tenths of seconds.
Monetary amount
- TCD12 is an undiscounted amount.
Monetary amount
- TCD13 is a net amount after the discount has been applied to the amount in TCD12.
Monetary amount
- TCD14 is an undiscounted amount.
Monetary amount
- TCD15 is a net amount after the discount has been applied to the amount in TCD14.
Code indicating the relationship between entities
- TCD16 is a code indicating the relationship of the price or amount to the associated segment.
Service Characteristic Identification
To specify service characteristic data
Code identifying the agency assigning the code values
- SI01 defines the source for each of the service characteristics qualifiers.
Code from an industry code list qualifying the type of service characteristics
Code from an industry code list qualifying the type of service characteristics
Code from an industry code list qualifying the type of service characteristics
Code from an industry code list qualifying the type of service characteristics
Code from an industry code list qualifying the type of service characteristics
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
- Valid codes for HL03 to define levels for this transaction set are given below:
1 - Service/Billing Provider (Identifies the Company Providing the Service/Billing)
2 - Billing Arrangement (Identifies a Specific Billing Arrangement)
3 - Sub-billing Arrangement (Identifies a More Detailed Billing Arrangement)
4 - Group (Identifies a Group of Charges on the Bill)
5 - Category (Identifies the Subdivision of the Group)
6 - Subcategory (Identifies a Further Breakdown of the Category)
7 - Type (Identifies a Further Breakdown of the Subcategory)
8 - Charge Detail (Identifies the Lowest Level of Charges within a Billing Arrangement)
9 - Line Detail (Identifies the Supporting Detail Associated with the Charge or Group Level)
They must be used in the (hierarchical) order in which they are listed; however, certain levels are optional and may be omitted. At least one occurrence each of the service/billing provider level and group level is required.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
- HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
- HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
Code defining the characteristic of a level in a hierarchical structure
- HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
- 3
- Sub-Billing Arrangement
Code indicating if there are hierarchical child data segments subordinate to the level being described
- HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
- 0
- No Subordinate HL Segment in This Hierarchical Structure.
- 1
- Additional Subordinate HL Data Segment in This Hierarchical Structure.
Assigned Number
To reference a line number in a transaction set
Number assigned for differentiation within a transaction set
Service Characteristic Identification
To specify service characteristic data
Code identifying the agency assigning the code values
- SI01 defines the source for each of the service characteristics qualifiers.
Code from an industry code list qualifying the type of service characteristics
Product/Item Description
To describe a product or process in coded or free-form format
Code indicating the format of a description
- If PID01 equals "F", then PID05 is used. If PID01 equals "S", then PID04 is used. If PID01 equals "X", then both PID04 and PID05 are used.
Code identifying the agency assigning the code values
- Use PID03 to indicate the organization that publishes the code list being referred to.
A code from an industry code list which provides specific data about a product characteristic
- PID04 should be used for industry-specific product description codes.
A free-form description to clarify the related data elements and their content
Reference Identification
To specify identifying information
Code qualifying the Reference Identification
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
A free-form description to clarify the related data elements and their content
Code qualifying the Reference Identification
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Monetary Amount
To indicate the total monetary amount
Date/Time Reference
To specify pertinent dates and times
Quantity
To specify quantity information
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
Individual or Organizational Name
To supply the full name of an individual or organizational entity
- When used for telecommunications billing, the service/billing provider level is defined by the NM1 loop.
Code identifying an organizational entity, a physical location, property or an individual
Code qualifying the type of entity
- NM102 qualifies NM103.
Individual last name or organizational name
Code designating the system/method of code structure used for Identification Code (67)
Additional Name Information
To specify additional names or those longer than 35 characters in length
Tax Information
To specify tax information
Monetary amount
- TXI02 is the monetary amount of the tax.
Code indicating the relationship between entities
- TXI07 is a code indicating the relationship of the price or amount to the associated segment.
Allowance, Charge or Service
To specify allowances, charges, or services
Code which indicates an allowance or charge for the service specified
- If ITA01 equals "A" - allowance or "C" - charge, then at least one of ITA06, ITA07, or ITA08 must be present.
Code identifying the agency assigning the code values
- ITA02 identifies the source of the code value in ITA03 or ITA15.
Code indicating method of handling for an allowance or charge
Total dollar amount for the allowance or charge
- If ITA07 is present with either ITA06 or ITA08, then ITA07 takes precedence.
Numeric value of quantity
- ITA10 is the quantity basis when the allowance or charge quantity is different from the purchase order or invoice quantity.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
A free-form description to clarify the related data elements and their content
- ITA13 is used to clarify the allowance, charge, or service.
Code identifying type of special charge or allowance
Code indicating the relationship between entities
- ITA16 describes the relationship of ITA06, ITA07 or ITA09 to an associated segment.
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
- Valid codes for HL03 to define levels for this transaction set are given below:
1 - Service/Billing Provider (Identifies the Company Providing the Service/Billing)
2 - Billing Arrangement (Identifies a Specific Billing Arrangement)
3 - Sub-billing Arrangement (Identifies a More Detailed Billing Arrangement)
4 - Group (Identifies a Group of Charges on the Bill)
5 - Category (Identifies the Subdivision of the Group)
6 - Subcategory (Identifies a Further Breakdown of the Category)
7 - Type (Identifies a Further Breakdown of the Subcategory)
8 - Charge Detail (Identifies the Lowest Level of Charges within a Billing Arrangement)
9 - Line Detail (Identifies the Supporting Detail Associated with the Charge or Group Level)
They must be used in the (hierarchical) order in which they are listed; however, certain levels are optional and may be omitted. At least one occurrence each of the service/billing provider level and group level is required.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
- HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
- HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
Code defining the characteristic of a level in a hierarchical structure
- HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
- 4
- Group
Code indicating if there are hierarchical child data segments subordinate to the level being described
- HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
- 0
- No Subordinate HL Segment in This Hierarchical Structure.
- 1
- Additional Subordinate HL Data Segment in This Hierarchical Structure.
Baseline Item Data (Invoice)
To specify the basic and most frequently used line item data for the invoice and related transactions
- The group level is defined by at least one occurrence of the IT1 loop which may only appear at the group level.
Alphanumeric characters assigned for differentiation within a transaction set
- IT101 is the purchase order line item identification.
Number of units invoiced (supplier units)
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
Price per unit of product, service, commodity, etc.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- IT106 through IT125 provide for ten different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
Identifying number for a product or service
Product/Item Description
To describe a product or process in coded or free-form format
Code indicating the format of a description
- If PID01 equals "F", then PID05 is used. If PID01 equals "S", then PID04 is used. If PID01 equals "X", then both PID04 and PID05 are used.
Code identifying the agency assigning the code values
- Use PID03 to indicate the organization that publishes the code list being referred to.
A code from an industry code list which provides specific data about a product characteristic
- PID04 should be used for industry-specific product description codes.
A free-form description to clarify the related data elements and their content
Quantity
To specify quantity information
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
- Valid codes for HL03 to define levels for this transaction set are given below:
1 - Service/Billing Provider (Identifies the Company Providing the Service/Billing)
2 - Billing Arrangement (Identifies a Specific Billing Arrangement)
3 - Sub-billing Arrangement (Identifies a More Detailed Billing Arrangement)
4 - Group (Identifies a Group of Charges on the Bill)
5 - Category (Identifies the Subdivision of the Group)
6 - Subcategory (Identifies a Further Breakdown of the Category)
7 - Type (Identifies a Further Breakdown of the Subcategory)
8 - Charge Detail (Identifies the Lowest Level of Charges within a Billing Arrangement)
9 - Line Detail (Identifies the Supporting Detail Associated with the Charge or Group Level)
They must be used in the (hierarchical) order in which they are listed; however, certain levels are optional and may be omitted. At least one occurrence each of the service/billing provider level and group level is required.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
- HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
- HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
Code defining the characteristic of a level in a hierarchical structure
- HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
- 8
- Charge Detail
Code indicating if there are hierarchical child data segments subordinate to the level being described
- HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
- 0
- No Subordinate HL Segment in This Hierarchical Structure.
- 1
- Additional Subordinate HL Data Segment in This Hierarchical Structure.
Subline Item Detail
To specify product subline detail item data
- The SLN loop may only appear at the charge detail level.
Alphanumeric characters assigned for differentiation within a transaction set
- SLN01 is the identifying number for the subline item.
- SLN01 is related to (but not necessarily equivalent to) the baseline item number. Example: 1.1 or 1A might be used as a subline number to relate to baseline number 1.
Code indicating the relationship between entities
- SLN03 is the configuration code indicating the relationship of the subline item to the baseline item.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
Price per unit of product, service, commodity, etc.
Code indicating the relationship between entities
- SLN08 is a code indicating the relationship of the price or amount to the associated segment.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- SLN09 through SLN28 provide for ten different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
Identifying number for a product or service
Service Characteristic Identification
To specify service characteristic data
Code identifying the agency assigning the code values
- SI01 defines the source for each of the service characteristics qualifiers.
Code from an industry code list qualifying the type of service characteristics
Product/Item Description
To describe a product or process in coded or free-form format
Code indicating the format of a description
- If PID01 equals "F", then PID05 is used. If PID01 equals "S", then PID04 is used. If PID01 equals "X", then both PID04 and PID05 are used.
Code identifying the agency assigning the code values
- Use PID03 to indicate the organization that publishes the code list being referred to.
A code from an industry code list which provides specific data about a product characteristic
- PID04 should be used for industry-specific product description codes.
A free-form description to clarify the related data elements and their content
Measurements
To specify physical measurements or counts, including dimensions, tolerances, variances, and weights
(See Figures Appendix for example of use of C001)
Date/Time Reference
To specify pertinent dates and times
Monetary Amount
To indicate the total monetary amount
Message Text
To provide a free-form format that allows the transmission of text information
Quantity
To specify quantity information
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
- Valid codes for HL03 to define levels for this transaction set are given below:
1 - Service/Billing Provider (Identifies the Company Providing the Service/Billing)
2 - Billing Arrangement (Identifies a Specific Billing Arrangement)
3 - Sub-billing Arrangement (Identifies a More Detailed Billing Arrangement)
4 - Group (Identifies a Group of Charges on the Bill)
5 - Category (Identifies the Subdivision of the Group)
6 - Subcategory (Identifies a Further Breakdown of the Category)
7 - Type (Identifies a Further Breakdown of the Subcategory)
8 - Charge Detail (Identifies the Lowest Level of Charges within a Billing Arrangement)
9 - Line Detail (Identifies the Supporting Detail Associated with the Charge or Group Level)
They must be used in the (hierarchical) order in which they are listed; however, certain levels are optional and may be omitted. At least one occurrence each of the service/billing provider level and group level is required.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
- HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
- HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
Code defining the characteristic of a level in a hierarchical structure
- HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
- 9
- Line Detail
Code indicating if there are hierarchical child data segments subordinate to the level being described
- HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
- 0
- No Subordinate HL Segment in This Hierarchical Structure.
Baseline Item Data (Invoice)
To specify the basic and most frequently used line item data for the invoice and related transactions
- The group level is defined by at least one occurrence of the IT1 loop which may only appear at the group level.
Alphanumeric characters assigned for differentiation within a transaction set
- IT101 is the purchase order line item identification.
Number of units invoiced (supplier units)
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
Price per unit of product, service, commodity, etc.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- IT106 through IT125 provide for ten different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
Identifying number for a product or service
Product/Item Description
To describe a product or process in coded or free-form format
Code indicating the format of a description
- If PID01 equals "F", then PID05 is used. If PID01 equals "S", then PID04 is used. If PID01 equals "X", then both PID04 and PID05 are used.
Code identifying the agency assigning the code values
- Use PID03 to indicate the organization that publishes the code list being referred to.
A code from an industry code list which provides specific data about a product characteristic
- PID04 should be used for industry-specific product description codes.
A free-form description to clarify the related data elements and their content
Quantity
To specify quantity information
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
Itemized Call Detail
To specify detail information for itemized calls
- The TCD loop may only appear at the line detail level.
Alphanumeric characters assigned for differentiation within a transaction set
- TCD01 is the detail information.
Date expressed as CCYYMMDD
- TCD02 is the date of the call.
Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)
- TCD03 is the connect time of the call.
Code identifying type of location
- TCD04, TCD05, and TCD06 are the 'to' location of the call.
The value of the measurement
- TCD10 and TCD11 are the total duration of the call. TCD10 is the time measured in minutes or minutes and tenths of minutes. TCD11 is time measured in seconds or seconds and tenths of seconds.
Monetary amount
- TCD12 is an undiscounted amount.
Monetary amount
- TCD13 is a net amount after the discount has been applied to the amount in TCD12.
Monetary amount
- TCD14 is an undiscounted amount.
Monetary amount
- TCD15 is a net amount after the discount has been applied to the amount in TCD14.
Code indicating the relationship between entities
- TCD16 is a code indicating the relationship of the price or amount to the associated segment.
Service Characteristic Identification
To specify service characteristic data
Code identifying the agency assigning the code values
- SI01 defines the source for each of the service characteristics qualifiers.
Code from an industry code list qualifying the type of service characteristics
Code from an industry code list qualifying the type of service characteristics
Code from an industry code list qualifying the type of service characteristics
Code from an industry code list qualifying the type of service characteristics
Code from an industry code list qualifying the type of service characteristics
Summary
Total Monetary Value Summary
To specify the total invoice discounts and amounts
Monetary amount
- TDS01 is the total amount of invoice (including charges, less allowances) before terms discount (if discount is applicable).
Balance Detail
To identify the specific monetary balances associated with a particular account
Transaction Totals
To transmit a hash total for a specific element in the transaction set
- The number of line items (CTT01) is the accumulation of the number of IT1 segments.
Total number of line items in the transaction set
Transaction Set Trailer
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
Total number of segments included in a transaction set including ST and SE segments
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Functional Group Trailer
To indicate the end of a functional group and to provide control information
Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element
Assigned number originated and maintained by the sender
Interchange Control Trailer
To define the end of an interchange of zero or more functional groups and interchange-related control segments
Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on this page are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.