Billing and Payment Information | Back

GXS
ANSI X.12 Version 4010 Transaction Set 811 Consolidated Invoice

Implementation Guide

VERSION: 1.0 DRAFT

 

Author: GXS - W. Lin

Publication Date: 3/23/01

 

811

Consolidated Service Invoice/Statement

 

Functional Group=CI

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.

Heading:

 

Pos

Id

Segment Name

Req

Max Use

Repeat

Notes

Usage

                   
   

ISA

Interchange Control Header

M

1

   

Must use

                   
   

GS

Functional Group Header

M

1

   

Must use

                   
 

010

ST

Transaction Set Header

M

1

   

Must use

                   
 

020

BIG

Beginning Segment for Invoice

M

1

   

Must use

                   
 

040

CUR

Currency

O

1

   

Used

                   
 

050

REF

Reference Identification

O

>1

   

Used

                   
 

060

REF

Reference Identification

O

>1

   

Used

                   
 

070

REF

Reference Identification

O

>1

   

Used

                   
 

080

DTM

Date/Time Reference

O

10

   

Used

                   
 

090

DTM

Date/Time Reference

O

10

   

Used

                   
                                     

LOOP ID - N1 Bill To

   

1

                       
 

120

N1

Name

O

1

   

Used

                   
 

130

N2

Additional Name Information

O

2

   

Used

                   
 

140

N3

Address Information

O

2

   

Used

                   
 

150

N4

Geographic Location

O

1

   

Used

                   
                                     

LOOP ID - N1 Remit to

   

1

                       
 

170

N1

Name

O

1

   

Used

                   
 

180

N2

Additional Name Information

O

2

   

Used

                   
 

190

N3

Address Information

O

2

   

Used

                   
 

210

N4

Geographic Location

O

1

   

Used

                   

Detail:

 

Pos

Id

Segment Name

Req

Max Use

Repeat

Notes

Usage

                   
                                     

LOOP ID - HL1 Consld Invoice

   

1

                       
 

010

HL

Hierarchical Level

M

1

 

N2/010

Must use

                   
                                     

LOOP ID - HL4 Invoice Level

   

>1

                       
 

020

HL

Hierarchical Level

M

1

   

Must use

                   
                                     

LOOP ID - LX

   

>1

                       
 

030

LX

Assigned Number

O

1

   

Used

                   
 

050

REF

Reference Identification

O

>1

   

Used

                   
 

060

AMT

Monetary Amount

O

15

   

Used

                   
 

070

ITA

Allowance, Charge or Service

O

10

   

Used

                   
 

080

ITA

Allowance, Charge or Service

O

10

   

Used

                   
 

090

ITA

Allowance, Charge or Service

O

10

   

Used

                   
 

110

TXI

Tax Information

O

>1

   

Used

                   
                                     

LOOP ID - HL9 Line Detail

   

>1

                       
 

120

HL

Hierarchical Level

M

1

   

Must use

                   
                                     

LOOP ID - SLN line items

   

>1

                       
 

130

SLN

Subline Item Detail

O

1

 

N2/130

Used

                   
 

140

PID

Product/Item Description

O

200

   

Used

                   
 

150

ITA

Allowance, Charge or Service

O

10

   

Used

                   

Summary:

Pos

Id

Segment Name

Req

Max Use

Repeat

Notes

Usage

                   
 

010

TDS

Total Monetary Value Summary

M

1

 

N3/010

Must use

                   
 

020

CTT

Transaction Totals

O

1

 

N3/020

Used

                   
 

030

SE

Transaction Set Trailer

M

1

   

Must use

                   
   

GE

Functional Group Trailer

M

1

   

Must use

                   
   

IEA

Interchange Control Trailer

M

1

   

Must use

                   

Notes:

2/010 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)

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)

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.

2/130 The SLN segment will only appear in Line Detail Level, and each SLN represents one item detail.

3/010 The amount of TDS_01 is the total amount due of consolidated invoice.

3/020 The number of line items (CTT_01) is the accumulation of the number of HL.

Trading Partner:

CONSOLIDATED INVOICE STRUCTURE

------------------------------------------------------------------

In compliance with the ANSI X12 Version 4010 - 811 Transaction Set, the GXS electronic consolidated invoice is structured in hierarchical levels. Hierarchical level 1 is the consolidated invoice level. The hierarchical level 4 provides invoice level data including an individual invoice amount, invoice id, invoice adjustment, etc. The line items of each invoice is presented at the Line Detail level 9.

Since this document uses hierarchical levels, the document translator can choose which level of detail is required and can ignore all lower levels. For example, to receive the invoice level data, only hierarchical level 1 and 4 need to be translated. Line detail can be ignored. For those simply wishing a total amount to pay from, the TDS is the only amount segment that needs to be translated.

 

CONSOLIDATED INVOICE CALCULATION

---------------------------------------------------------------------

The total amount due for GXS 811 invoice is reflected within the TDS segment (trailer level) of the invoice document. This amount is obtained by summing the invoice amount AMT_01 of all invoices (where HL_03 = '4').

TDS_01 = sum of AMT_01 at invoice level (where HL_03 = '4')

The invoice AMT_01 is derived by summing item details, spending adjustment, volume adjustment, account charges and taxes and subtract any discounts.

AMT_01 (invoice amount)

= sum of SLN_04 x SLN_06 (item level)

+/- price factor adjustment (ITA_07 of item level)

+ sum of taxes TXI_02 (invoice level)

+/- Volume Adjustment, Spending Adjustment and Account Charges (ITA_07 of invoice level)

The following sample output will provide a basic guidance on how GXS transmitted its consolidated invoice as per ANSI X12 Version 4010 - 811.

 

SAMPLE OUTPUT:

--------------------------------

ISA~00~ ~00~ ~ZZ~GXSINV ~ZZ~TP TEST PROD ID~010327~1601~U~00401~000000090~0~P~~

GS~CI~GXSINV~TEST PROD ID~20010327~1601~90~X~004010

ST~811~900001

BIG~20001130~0378711-C

CUR~SE~USD

REF~DUN~10-392-8552~D-U-N-S Number

REF~TJ~52-1865641~Federal Tax Identification Number

REF~2F~0378711-C~Consolidated Invoice Number

DTM~003~20001130

DTM~814~20001220

N1~BT~IM Electronic Inc~92~03787-2399103-781

N2~Mgr. Edi Invoicing

N3~321 31TH ST

N4~ST. Knowwhere~FL~33711~US

N1~RI~GE INFORMATION SERVICES, INC.~01~10-392-8552

N2~P. O. BOX 640371

N4~PITTSBURGH, PA 15264-0371~~~US

HL~1~~1~1 <---- Consolidated Invoice HL

HL~2~1~4~1 <---- Invoice Level HL

LX~1

REF~IK~348008 <----- Invoice #1

AMT~5~3308.64 <----- Total Amount for Invoice #1

TXI~ZZ~73.2~6~CD~FLORIDA <---- Tax

TXI~ZZ~12.2~1~CD~PINELLAS <---- Tax

HL~3~4~8~0 <------ Line Items Detail

SLN~1~~I~1~EA~25~UM~~PD~EDI*EXPRESS MAILBOX FEE, PER USER#, PER MONTH

PID~F~~~~Charge ID CK02872 11/01/00-11/30/00 GEIS Internal KU81872

SLN~2~~I~2~EA~0~UM~~PD~THIRD-PARTY INTERCONNECT, PER NETWORK, PER MONTH

PID~F~~~~Charge ID CK02872 11/01/00-11/30/00 GEIS Internal KU81872

SLN~3~~I~1~EA~1978.24~UM~~PD~WO# 0010Z8-10/00 MONTHLY MINIMUM ADJ

PID~F~~~~Charge ID CK02872 11/01/00-11/30/00 GEIS Internal KU81872

SLN~4~~I~1~EA~450~UM~~PD~WO#0010G07 64K F/R PORT

PID~F~~~~Charge ID CK02872 11/01/00-11/30/00 GEIS Internal KU81872

SLN~5~~I~1~EA~100~UM~~PD~WO#0010G06 ISDN DBU SERVICE

PID~F~~~~Charge ID CK02872 11/01/00-11/30/00 GEIS Internal KU81872

SLN~6~~I~1~EA~670~UM~~PD~WO# 9810H FRAME RELAY INTERCONNECT SVC

PID~F~~~~Charge ID CK02872 11/01/00-11/30/00 GEIS Internal KU81872

TDS~346369 <-------- Total Consolidated Invoice Amount Due

CTT~3 <------- Represents 3 total HL segments

SE~38~900001

GE~1~90

IEA~1~000000090

 

 

 

ISA

Interchange Control Header

Pos: Max: 1

Heading - Mandatory

Loop: N/A Elements: 16

To start and identify an interchange of zero or more functional groups and interchange-related control segments

Element Summary:

 

Ref _

Id_

Element Name _

Req

Type

Min/Max

Usage_

 
 

ISA01

I01

Authorization Information Qualifier

Description: Code to identify the type of information in the Authorization Information

All valid standard codes are used.

M

ID

2/2

Must use

 
 

ISA02

I02

Authorization Information

Description: 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)

M

AN

10/10

Must use

 
 

ISA03

I03

Security Information Qualifier

Description: Code to identify the type of information in the Security Information

All valid standard codes are used.

M

ID

2/2

Must use

 
 

ISA04

I04

Security Information

Description: 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)

M

AN

10/10

Must use

 
 

ISA05

I05

Interchange ID Qualifier

Description: Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

Code Name _

ZZ Mutually Defined

M

ID

2/2

Must use

 
 

ISA06

I06

Interchange Sender ID

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

Trading Partner: PRODUCTION ID:

===============

GXS PROD ID QUAL: ZZ

GXS PROD ID: GXSINV

 

TEST ID:

=======

GXS TEST ID QUAL: ZZ

GXS TEST ID: GXSINVT

 

 

M

AN

15/15

Must use

 
 

ISA07

I05

Interchange ID Qualifier

Description: Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

M

ID

2/2

Must use

 
 

ISA08

I07

Interchange Receiver ID

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

M

AN

15/15

Must use

 
 

ISA09

I08

Interchange Date

Description: Date of the interchange

M

DT

6/6

Must use

 
 

ISA10

I09

Interchange Time

Description: Time of the interchange

M

TM

4/4

Must use

 
 

ISA11

I10

Interchange Control Standards Identifier

Description: Code to identify the agency responsible for the control standard used by the message that is enclosed by the interchange header and trailer

All valid standard codes are used.

M

ID

1/1

Must use

 
 

ISA12

I11

Interchange Control Version Number

Description: This version number covers the interchange control segments

Code _ Name _

00401 Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1997

M

ID

5/5

Must use

 
 

ISA13

I12

Interchange Control Number

Description: A control number assigned by the interchange sender

M

N0

9/9

Must use

 
 

ISA14

I13

Acknowledgment Requested

Description: Code sent by the sender to request an interchange acknowledgment (TA1)

All valid standard codes are used.

M

ID

1/1

Must use

 
 

ISA15

I14

Usage Indicator

Description: Code to indicate whether data enclosed by this interchange envelope is test, production or information

Code Name _

P Production Data

T Test Data

M

ID

1/1

Must use

 
 

ISA16

I15

Component Element Separator

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

M

 

1/1

Must use

 

 

 

GS

Functional Group Header

Pos: Max: 1

Heading - Mandatory

Loop: N/A Elements: 8

To indicate the beginning of a functional group and to provide control information

Element Summary:

 

Ref _

Id_

Element Name _

Req

Type

Min/Max

Usage_

 
 

GS01

479

Functional Identifier Code

Description: Code identifying a group of application related transaction sets

Code Name _

CI Consolidated Service Invoice/Statement (811)

M

ID

2/2

Must use

 
 

GS02

142

Application Sender's Code

Description: Code identifying party sending transmission; codes agreed to by trading partners

M

AN

2/15

Must use

 
 

GS03

124

Application Receiver's Code

Description: Code identifying party receiving transmission. Codes agreed to by trading partners

M

AN

2/15

Must use

 
 

GS04

373

Date

Description: Date expressed as CCYYMMDD

M

DT

8/8

Must use

 
 

GS05

337

Time

Description: 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)

M

TM

4/8

Must use

 
 

GS06

28

Group Control Number

Description: Assigned number originated and maintained by the sender

M

N0

1/9

Must use

 
 

GS07

455

Responsible Agency Code

Description: Code used in conjunction with Data Element 480 to identify the issuer of the standard

Code Name _

X Accredited Standards Committee X12

M

ID

1/2

Must use

 
 

GS08

480

Version / Release / Industry Identifier Code

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

Code _ Name _

004010 Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1997

M

AN

1/12

Must use

 

Semantics:

1. GS04 is the group date.

2. GS05 is the group time.

3. The data interchange control number GS06 in this header must be identical to the same data element in the associated functional group trailer, GE02.

 

Comments:

1. A functional group of related transaction sets, within the scope of X12 standards, consists of a collection of similar transaction sets enclosed by a functional group header and a functional group trailer.

 

 

 

ST

Transaction Set Header

Pos: 010 Max: 1

Heading - Mandatory

Loop: N/A Elements: 2

To indicate the start of a transaction set and to assign a control number

Element Summary:

 

Ref _

Id_

Element Name _

Req

Type

Min/Max

Usage_

 
 

ST01

143

Transaction Set Identifier Code

Description: Code uniquely identifying a Transaction Set

Code Name _

811 Consolidated Service Invoice/Statement

M

ID

3/3

Must use

 
 

ST02

329

Transaction Set Control Number

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

M

AN

4/9

Must use

 

Semantics:

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

 

 

 

BIG

Beginning Segment for Invoice

Pos: 020 Max: 1

Heading - Mandatory

Loop: N/A Elements: 2

To indicate the beginning of an invoice transaction set and transmit identifying numbers and dates

Element Summary:

 

Ref _

Id_

Element Name _

Req

Type

Min/Max

Usage_

 
 

BIG01

373

Date

Description: Date expressed as CCYYMMDD

Trading Partner: Invoice Processing Date

 

 

M

DT

8/8

Must use

 
 

BIG02

76

Invoice Number

Description: Identifying number assigned by issuer

M

AN

1/22

Must use

 

Semantics:

1. BIG01 is the invoice issue date.

2. BIG03 is the date assigned by the purchaser to purchase order.

3. BIG10 indicates the consolidated invoice number. When BIG07 contains code CI, BIG10 is not used.

 

Comments:

1. BIG07 is used only to further define the type of invoice when needed.

 

 

 

CUR

Currency

Pos: 040 Max: 1

Heading - Optional

Loop: N/A Elements: 2

To specify the currency (dollars, pounds, francs, etc.) used in a transaction

Element Summary:

 

Ref _

Id_

Element Name _

Req

Type

Min/Max

Usage_

 
 

CUR01

98

Entity Identifier Code

Description: Code identifying an organizational entity, a physical location, property or an individual

Code Name _

SE Selling Party

M

ID

2/3

Must use

 
 

CUR02

100

Currency Code

Description: Code (Standard ISO) for country in whose currency the charges are specified

Trading Partner: Will be 'USD', which is abbreviation for US Dollars.

 

 

M

ID

3/3

Must use

 

Comments:

1. See Figures Appendix for examples detailing the use of the CUR segment.

 

 

 

REF

Reference Identification

Pos: 050 Max: >1

Heading - Optional

Loop: N/A Elements: 3

To specify identifying information

Element Summary:

 

Ref _

Id_

Element Name _

Req

Type

Min/Max

Usage_

 
 

REF01

128

Reference Identification Qualifier

Description: Code qualifying the Reference Identification

Trading Partner: GXS DUNS number

Code Name _

DUN D-U-N-S Number Dun & Bradstreet

M

ID

2/3

Must use

 
 

REF02

127

Reference Identification

Description: Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

Trading Partner: DUNS number

 

 

C

AN

1/30

Used

 
 

REF03

352

Description

Description: A free-form description to clarify the related data elements and their content

Trading Partner: Will be 'D-U-N-S Number'

 

 

C

AN

1/80

Used

 

 

Syntax:

R0203 -- At least one of REF02 or REF03 is required.

 

Semantics:

1. REF04 contains data relating to the value cited in REF02.

 

Trading Partner:

DUNS Number Info

 

 

REF

Reference Identification

Pos: 060 Max: >1

Heading - Optional

Loop: N/A Elements: 3

To specify identifying information

Element Summary:

 

Ref _

Id_

Element Name _

Req

Type

Min/Max

Usage_

 
 

REF01

128

Reference Identification Qualifier

Description: Code qualifying the Reference Identification

Code Name _

TJ Federal Taxpayer's Identification Number

M

ID

2/3

Must use

 
 

REF02

127

Reference Identification

Description: Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

Trading Partner: GEIS Federal tax identification number

 

 

C

AN

1/30

Used

 
 

REF03

352

Description

Description: A free-form description to clarify the related data elements and their content

Trading Partner: Will be 'Federal Tax Identification Number'

 

 

C

AN

1/80

Used

 

 

Syntax:

1. REF02 R0203 -- At least one of REF02 or REF03 is required.

 

Semantics:

1. REF04 contains data relating to the value cited in REF02.

 

Trading Partner:

GXS Federal Tax Identification Number

 

 

REF

Reference Identification

Pos: 070 Max: >1

Heading - Optional

Loop: N/A Elements: 3

To specify identifying information

Element Summary:

 

Ref _

Id_

Element Name _

Req

Type

Min/Max

Usage_

 
 

REF01

128

Reference Identification Qualifier

Description: Code qualifying the Reference Identification

Code Name _

2F Consolidated Invoice Number

M

ID

2/3

Must use

 
 

REF02

127

Reference Identification

Description: Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

Trading Partner: Consolidated invoice number

 

 

C

AN

1/30

Used

 
 

REF03

352

Description

Description: A free-form description to clarify the related data elements and their content

Trading Partner: Will be 'Consolidated Invoice Number'

 

 

C

AN

1/80

Used

 

 

Syntax:

1. REF02 R0203 -- At least one of REF02 or REF03 is required.

 

Semantics:

1. REF04 contains data relating to the value cited in REF02.

 

Trading Partner:

Consolidated Invoice Number

 

 

DTM

Date/Time Reference

Pos: 080 Max: 10

Heading - Optional

Loop: N/A Elements: 2

To specify pertinent dates and times

Element Summary:

 

Ref _

Id_

Element Name _

Req

Type

Min/Max

Usage_

 
 

DTM01

374

Date/Time Qualifier

Description: Code specifying type of date or time, or both date and time

Code Name _

003 Invoice

M

ID

3/3

Must use

 
 

DTM02

373

Date

Description: Date expressed as CCYYMMDD

Trading Partner: Invoice Date

 

 

C

DT

8/8

Used

 

 

Syntax:

R020305 -- At least one of DTM02, DTM03 or DTM05 is required.

 

 

 

DTM

Date/Time Reference

Pos: 090 Max: 10

Heading - Optional

Loop: N/A Elements: 2

To specify pertinent dates and times

Element Summary:

 

Ref _

Id_

Element Name _

Req

Type

Min/Max

Usage_

 
 

DTM01

374

Date/Time Qualifier

Description: Code specifying type of date or time, or both date and time

Trading Partner: Will be '814'

Code Name _

814 Payment Due Date

M

ID

3/3

Must use

 
 

DTM02

373

Date

Description: Date expressed as CCYYMMDD

Trading Partner: Payment due date

 

 

C

DT

8/8

Used

 

 

Syntax:

R020305 -- At least one of DTM02, DTM03 or DTM05 is required.

 

 

 

N1

Name

Pos: 120 Max: 1

Heading - Optional

Loop: N1 Bill To Elements: 4

To identify a party by type of organization, name, and code

Element Summary:

 

Ref _

Id_

Element Name _

Req

Type

Min/Max

Usage_

 
 

N101

98

Entity Identifier Code

Description: Code identifying an organizational entity, a physical location, property or an individual

Code Name _

BT Bill-to-Party

M

ID

2/3

Must use

 
 

N102

93

Name

Description: Free-form name

C

AN

1/60

Used

 
 

N103

66

Identification Code Qualifier

Description: Code designating the system/method of code structure used for Identification Code (67)

Code Name _

92 Assigned by Buyer or Buyer's Agent

C

ID

1/2

Used

 
 

N104

67

Identification Code

Description: Code identifying a party or other code

Trading Partner: GXS reference number

 

 

C

AN

2/80

Used

 

 

Syntax:

R0203 -- At least one of N102 or N103 is required.

P0304 -- If either N103 or N104 are present, then the others are required.

 

Comments:

1. This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.

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

 

Trading Partner:

Bill-to loop

 

 

N2

Additional Name Information

Pos: 130 Max: 2

Heading - Optional

Loop: N1 Bill To Elements: 1

To specify additional names or those longer than 35 characters in length

Element Summary:

 

Ref _

Id_

Element Name _

Req

Type

Min/Max

Usage_

 
 

N201

93

Name

Description: Free-form name

M

AN

1/60

Must use

 

Trading Partner:

Bill-To Loop

 

 

N3

Address Information

Pos: 140 Max: 2

Heading - Optional

Loop: N1 Bill To Elements: 2

To specify the location of the named party

Element Summary:

 

Ref _

Id_

Element Name _

Req

Type

Min/Max

Usage_

 
 

N301

166

Address Information

Description: Address information

M

AN

1/55

Must use

 
 

N302

166

Address Information

Description: Address information

O

AN

1/55

Used

 

Trading Partner:

Bill-To Loop

 

 

N4

Geographic Location

Pos: 150 Max: 1

Heading - Optional

Loop: N1 Bill To Elements: 4

To specify the geographic place of the named party

Element Summary:

 

Ref _

Id_

Element Name _

Req

Type

Min/Max

Usage_

 
 

N401

19

City Name

Description: Free-form text for city name

Trading Partner: Bill-to city

 

 

O

AN

2/30

Used

 
 

N402

156

State or Province Code

Description: Code (Standard State/Province) as defined by appropriate government agency

Trading Partner: Bill-to state

 

 

O

ID

2/2

Used

 
 

N403

116

Postal Code

Description: Code defining international postal zone code excluding punctuation and blanks (zip code for United States)

Trading Partner: Bill-to zip

 

 

O

ID

3/15

Used

 
 

N404

26

Country Code

Description: Code identifying the country

Trading Partner: Bill-to country

 

 

O

ID

2/3

Used

 

Comments:

1. A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.

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

 

Trading Partner:

Bill-To Loop

 

 

N1

Name

Pos: 170 Max: 1

Heading - Optional

Loop: N1 Remit to Elements: 2

To identify a party by type of organization, name, and code

Element Summary:

 

Ref _

Id_

Element Name _

Req

Type

Min/Max

Usage_

 
 

N101

98

Entity Identifier Code

Description: Code identifying an organizational entity, a physical location, property or an individual

Code Name _

RI Remit To

M

ID

2/3

Must use

 
 

N102

93

Name

Description: Free-form name

Trading Partner: Remit To Company

 

 

C

AN

1/60

Used

 

 

Syntax:

1. N102 R0203 -- At least one of N102 or N103 is required.

2. N103 P0304 -- If either N103 or N104 are present, then the others are required.

 

Comments:

1. This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.

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

 

Trading Partner:

Remit-To Loop

 

 

N2

Additional Name Information

Pos: 180 Max: 2

Heading - Optional

Loop: N1 Remit to Elements: 1

To specify additional names or those longer than 35 characters in length

Element Summary:

 

Ref _

Id_

Element Name _

Req

Type

Min/Max

Usage_

 
 

N201

93

Name

Description: Free-form name

M

AN

1/60

Must use

 

Trading Partner:

Remit To Loop

 

 

N3

Address Information

Pos: 190 Max: 2

Heading - Optional

Loop: N1 Remit to Elements: 2

To specify the location of the named party

Element Summary:

 

Ref _

Id_

Element Name _

Req

Type

Min/Max

Usage_

 
 

N301

166

Address Information

Description: Address information

M

AN

1/55

Must use

 
 

N302

166

Address Information

Description: Address information

O

AN

1/55

Used

 

Trading Partner:

Remit To Loop

 

 

N4

Geographic Location

Pos: 210 Max: 1

Heading - Optional

Loop: N1 Remit to Elements: 4

To specify the geographic place of the named party

Element Summary:

 

Ref _

Id_

Element Name _

Req

Type

Min/Max

Usage_

 
 

N401

19

City Name

Description: Free-form text for city name

O

AN

2/30

Used

 
 

N402

156

State or Province Code

Description: Code (Standard State/Province) as defined by appropriate government agency

O

ID

2/2

Used

 
 

N403

116

Postal Code

Description: Code defining international postal zone code excluding punctuation and blanks (zip code for United States)

O

ID

3/15

Used

 
 

N404

26

Country Code

Description: Code identifying the country

O

ID

2/3

Used

 

Comments:

1. A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.

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

 

Trading Partner:

Remit To Loop

 

 

HL

Hierarchical Level

Pos: 010 Max: 1

Detail - Mandatory

Loop: HL1 Consld Invoice Elements: 4

To identify dependencies among and the content of hierarchically related groups of data segments

Element Summary:

 

Ref _

Id_

Element Name _

Req

Type

Min/Max

Usage_

 
 

HL01

628

Hierarchical ID Number

Description: A unique number assigned by the sender to identify a particular data segment in a hierarchical structure

M

AN

1/12

Must use

 
 

HL02

734

Hierarchical Parent ID Number

Description: Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to

O

AN

1/12

Used

 
 

HL03

735

Hierarchical Level Code

Description: Code defining the characteristic of a level in a hierarchical structure

Trading Partner: Will always be '1'

Code Name _

9 Line Detail

M

ID

1/2

Must use

 
 

HL04

736

Hierarchical Child Code

Description: Code indicating if there are hierarchical child data segments subordinate to the level being described

Trading Partner: Will always be '1'

Code Name _

1 Additional Subordinate HL Data Segment in This Hierarchical Structure.

O

ID

1/1

Used

 

Comments:

1. The HL segment is used to identify levels of detail information using a hierarchical structure, such as relating line-item data to shipment data, and packaging data to line-item data.

2. The HL segment defines a top-down/left-right ordered structure.

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

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

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

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

 

Trading Partner:

This is consolidated invoice level HL. Only one consolidated invoice level HL will be used per document.

 

 

HL

Hierarchical Level

Pos: 020 Max: 1

Detail - Mandatory

Loop: HL4 Invoice Level Elements: 4

To identify dependencies among and the content of hierarchically related groups of data segments

Element Summary:

 

Ref _

Id_

Element Name _

Req

Type

Min/Max

Usage_

 
 

HL01

628

Hierarchical ID Number

Description: A unique number assigned by the sender to identify a particular data segment in a hierarchical structure

M

AN

1/12

Must use

 
 

HL02

734

Hierarchical Parent ID Number

Description: Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to

Trading Partner: Will always be '1' since the parents of invoice level will always be the consolidated invoice level, which is HL*1**1*1.

 

 

O

AN

1/12

Used

 
 

HL03

735

Hierarchical Level Code

Description: Code defining the characteristic of a level in a hierarchical structure

Code Name _

4 Group

M

ID

1/2

Must use

 
 

HL04

736

Hierarchical Child Code

Description: Code indicating if there are hierarchical child data segments subordinate to the level being described

Trading Partner: Will always be '1' since the invoice level will always contain item level.

Code Name _

1 Additional Subordinate HL Data Segment in This Hierarchical Structure.

O

ID

1/1

Used

 

Comments:

1. The HL segment is used to identify levels of detail information using a hierarchical structure, such as relating line-item data to shipment data, and packaging data to line-item data.

2. The HL segment defines a top-down/left-right ordered structure.

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

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

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

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

 

Trading Partner:

This is the invoice level HL, and it is possible to contain multiple invoices (HL_03 = '4') per consolidated invoice(HL_03 = '1').

 

 

LX

Assigned Number

Pos: 030 Max: 1

Detail - Optional

Loop: LX Elements: 1

To reference a line number in a transaction set

Element Summary:

 

Ref _

Id_

Element Name _

Req

Type

Min/Max

Usage_

 
 

LX01

554

Assigned Number

Description: Number assigned for differentiation within a transaction set

M

N0

1/6

Must use

 

 

 

REF

Reference Identification

Pos: 050 Max: >1

Detail - Optional

Loop: LX Elements: 2

To specify identifying information

Element Summary:

 

Ref _

Id_

Element Name _

Req

Type

Min/Max

Usage_

 
 

REF01

128

Reference Identification Qualifier

Description: Code qualifying the Reference Identification

Trading Partner: It will be 'IK', which stands for invoice number.

Code Name _

IK Invoice Number

M

ID

2/3

Must use

 
 

REF02

127

Reference Identification

Description: Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

Trading Partner: Individual invoice number

 

 

C

AN

1/30

Used

 

 

Syntax:

1. REF02 R0203 -- At least one of REF02 or REF03 is required.

 

Semantics:

1. REF04 contains data relating to the value cited in REF02.

 

Trading Partner:

Invoice Number

 

 

AMT

Monetary Amount

Pos: 060 Max: 15

Detail - Optional

Loop: LX Elements: 2

To indicate the total monetary amount

Element Summary:

 

Ref _

Id_

Element Name _

Req

Type

Min/Max

Usage_

 
 

AMT01

522

Amount Qualifier Code

Description: Code to qualify amount

Code Name _

5 Total Invoice Amount

M

ID

1/3

Must use

 
 

AMT02

782

Monetary Amount

Description: Monetary amount

Trading Partner: Payment due amount

 

 

M

R

1/18

Must use

 

 

 

ITA

Allowance, Charge or Service

Pos: 070 Max: 10

Detail - Optional

Loop: LX Elements: 4

To specify allowances, charges, or services

Element Summary:

 

Ref _

Id_

Element Name _

Req

Type

Min/Max

Usage_

 
 

ITA01

248

Allowance or Charge Indicator

Description: Code which indicates an allowance or charge for the service specified

Code Name _

A Allowance

C Charge

M

ID

1/1

Must use

 
 

ITA04

331

Allowance or Charge Method of Handling Code

Description: Code indicating method of handling for an allowance or charge

Code Name _

02 Off Invoice

06 Charge to be Paid by Customer

M

ID

2/2

Must use

 
 

ITA07

360

Allowance or Charge Total Amount

Description: Total dollar amount for the allowance or charge

O

N2

1/15

Used

 
 

ITA13

352

Description

Description: A free-form description to clarify the related data elements and their content

C

AN

1/80

Used

 

 

Syntax:

C0809 -- If ITA08 is present, then ITA09 is required

 

Semantics:

1. ITA09 is the allowance or charge percent.

2. ITA10 is the quantity basis when the allowance or charge quantity is different from the purchase order or invoice quantity.

3. ITA12 is the quantity of free goods.

 

Comments:

1. If ITA01 equals "A" - allowance or "C" - charge, then at least one of ITA06, ITA07, or ITA08 must be present.

2. ITA02 identifies the source of the code value in ITA03 or ITA15.

3. If ITA07 is present with either ITA06 or ITA08, then ITA07 takes precedence.

4. ITA13 is used to clarify the allowance, charge, or service.

5. ITA15 specifies the individual code list of the agency specified in ITA02.

6. ITA16 describes the relationship of ITA06, ITA07 or ITA09 to an associated segment.

 

Trading Partner:

The segment contains Total Spend Adjustment.

 

 

ITA

Allowance, Charge or Service

Pos: 080 Max: 10

Detail - Optional

Loop: LX Elements: 4

To specify allowances, charges, or services

Element Summary:

 

Ref _

Id_

Element Name _

Req

Type

Min/Max

Usage_

 
 

ITA01

248

Allowance or Charge Indicator

Description: Code which indicates an allowance or charge for the service specified

Code Name _

A Allowance

C Charge

M

ID

1/1

Must use

 
 

ITA04

331

Allowance or Charge Method of Handling Code

Description: Code indicating method of handling for an allowance or charge

Code Name _

02 Off Invoice

06 Charge to be Paid by Customer

M

ID

2/2

Must use

 
 

ITA07

360

Allowance or Charge Total Amount

Description: Total dollar amount for the allowance or charge

O

N2

1/15

Used

 
 

ITA13

352

Description

Description: A free-form description to clarify the related data elements and their content

Trading Partner: 'Account Charge'

 

 

C

AN

1/80

Used

 

 

Syntax:

C0809 -- If ITA08 is present, then ITA09 is required

 

Semantics:

1. ITA09 is the allowance or charge percent.

2. ITA10 is the quantity basis when the allowance or charge quantity is different from the purchase order or invoice quantity.

3. ITA12 is the quantity of free goods.

 

Comments:

1. If ITA01 equals "A" - allowance or "C" - charge, then at least one of ITA06, ITA07, or ITA08 must be present.

2. ITA02 identifies the source of the code value in ITA03 or ITA15.

3. If ITA07 is present with either ITA06 or ITA08, then ITA07 takes precedence.

4. ITA13 is used to clarify the allowance, charge, or service.

5. ITA15 specifies the individual code list of the agency specified in ITA02.

6. ITA16 describes the relationship of ITA06, ITA07 or ITA09 to an associated segment.

 

Trading Partner:

The segment specifies total Account Charge.

 

 

ITA

Allowance, Charge or Service

Pos: 090 Max: 10

Detail - Optional

Loop: LX Elements: 4

To specify allowances, charges, or services

Element Summary:

 

Ref _

Id_

Element Name _

Req

Type

Min/Max

Usage_

 
 

ITA01

248

Allowance or Charge Indicator

Description: Code which indicates an allowance or charge for the service specified

Code Name _

A Allowance

C Charge

M

ID

1/1

Must use

 
 

ITA04

331

Allowance or Charge Method of Handling Code

Description: Code indicating method of handling for an allowance or charge

Code Name _

02 Off Invoice

06 Charge to be Paid by Customer

M

ID

2/2

Must use

 
 

ITA07

360

Allowance or Charge Total Amount

Description: Total dollar amount for the allowance or charge

O

N2

1/15

Used

 
 

ITA13

352

Description

Description: A free-form description to clarify the related data elements and their content

Trading Partner: 'Minimum Invoice Adjustment'

 

 

C

AN

1/80

Used

 

 

Syntax:

C0809 -- If ITA08 is present, then ITA09 is required

 

Semantics:

1. ITA09 is the allowance or charge percent.

2. ITA10 is the quantity basis when the allowance or charge quantity is different from the purchase order or invoice quantity.

3. ITA12 is the quantity of free goods.

 

Comments:

1. If ITA01 equals "A" - allowance or "C" - charge, then at least one of ITA06, ITA07, or ITA08 must be present.

2. ITA02 identifies the source of the code value in ITA03 or ITA15.

3. If ITA07 is present with either ITA06 or ITA08, then ITA07 takes precedence.

4. ITA13 is used to clarify the allowance, charge, or service.

5. ITA15 specifies the individual code list of the agency specified in ITA02.

6. ITA16 describes the relationship of ITA06, ITA07 or ITA09 to an associated segment.

 

Trading Partner:

The segment specifies Minimum Invoice Adjustment.

 

 

TXI

Tax Information

Pos: 110 Max: >1

Detail - Optional

Loop: LX Elements: 5

To specify tax information

Element Summary:

 

Ref _

Id_

Element Name _

Req

Type

Min/Max

Usage_

 
 

TXI01

963

Tax Type Code

Description: Code specifying the type of tax

Code Name _

ZZ Mutually Defined

M

ID

2/2

Must use

 
 

TXI02

782

Monetary Amount

Description: Monetary amount

C

R

1/18

Used

 
 

TXI03

954

Percent

Description: Percentage expressed as a decimal

C

R

1/10

Used

 
 

TXI04

955

Tax Jurisdiction Code Qualifier

Description: Code identifying the source of the data used in tax jurisdiction code

Code Name _

CD Customer defined

C

ID

2/2

Used

 
 

TXI05

956

Tax Jurisdiction Code

Description: Code identifying the taxing jurisdiction

C

AN

1/10

Used

 

 

Syntax:

R020306 -- At least one of TXI02, TXI03 or TXI06 is required.

P0405 -- If either TXI04 or TXI05 are present, then the others are required.

C0803 -- If TXI08 is present, then TXI03 is required

 

Semantics:

1. TXI02 is the monetary amount of the tax.

2. TXI03 is the tax percent expressed as a decimal.

3. TXI07 is a code indicating the relationship of the price or amount to the associated segment.

 

Trading Partner:

Tax total per invoice

 

 

HL

Hierarchical Level

Pos: 120 Max: 1

Detail - Mandatory

Loop: HL9 Line Detail Elements: 4

To identify dependencies among and the content of hierarchically related groups of data segments

Element Summary:

 

Ref _

Id_

Element Name _

Req

Type

Min/Max

Usage_

 
 

HL01

628

Hierarchical ID Number

Description: A unique number assigned by the sender to identify a particular data segment in a hierarchical structure

M

AN

1/12

Must use

 
 

HL02

734

Hierarchical Parent ID Number

Description: Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to

O

AN

1/12

Used

 
 

HL03

735

Hierarchical Level Code

Description: Code defining the characteristic of a level in a hierarchical structure

Code Name _

9 Line Detail

M

ID

1/2

Must use

 
 

HL04

736

Hierarchical Child Code

Description: Code indicating if there are hierarchical child data segments subordinate to the level being described

All valid standard codes are used.

O

ID

1/1

Used

 

Comments:

1. The HL segment is used to identify levels of detail information using a hierarchical structure, such as relating line-item data to shipment data, and packaging data to line-item data.

2. The HL segment defines a top-down/left-right ordered structure.

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

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

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

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

 

 

 

SLN

Subline Item Detail

Pos: 130 Max: 1

Detail - Optional

Loop: SLN line items Elements: 8

To specify product subline detail item data

Element Summary:

 

Ref _

Id_

Element Name _

Req

Type

Min/Max

Usage_

 
 

SLN01

350

Assigned Identification

Description: Alphanumeric characters assigned for differentiation within a transaction set

Trading Partner: Item counter

 

 

M

AN

1/20

Must use

 
 

SLN03

662

Relationship Code

Description: Code indicating the relationship between entities

Code Name _

I Included

M

ID

1/1

Must use

 
 

SLN04

380

Quantity

Description: Numeric value of quantity

C

R

1/15

Used

 
 

SLN05

C001

Composite Unit of Measure

Description: To identify a composite unit of measure(See Figures Appendix for examples of use)

C

Comp

 

Used

 
   

355

Unit or Basis for Measurement Code

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

Code Name _

EA Each

M

ID

2/2

Must use

 
 

SLN06

212

Unit Price

Description: Price per unit of product, service, commodity, etc.

C

R

1/17

Used

 
 

SLN07

639

Basis of Unit Price Code

Description: Code identifying the type of unit price for an item

Code Name _

UM Price per Unit of Measure

O

ID

2/2

Used

 
 

SLN09

235

Product/Service ID Qualifier

Description: Code identifying the type/source of the descriptive number used in Product/Service ID (234)

Code Name _

PD Part Number Description

C

ID

2/2

Used

 
 

SLN10

234

Product/Service ID

Description: Identifying number for a product or service

C

AN

1/48

Used

 

 

Syntax:

P0405 -- If either SLN04 or SLN05 are present, then the others are required.

C0706 -- If SLN07 is present, then SLN06 is required

C0806 -- If SLN08 is present, then SLN06 is required

P0910 -- If either SLN09 or SLN10 are present, then the others are required.

 

Semantics:

1. SLN01 is the identifying number for the subline item.

2. SLN02 is the identifying number for the subline level. The subline level is analogous to the level code used in a bill of materials.

3. SLN03 is the configuration code indicating the relationship of the subline item to the baseline item.

4. SLN08 is a code indicating the relationship of the price or amount to the associated segment.

 

Comments:

1. See the Data Element Dictionary for a complete list of IDs.

2. SLN01 is related to (but not necessarily equivalent to) the baseline item number. Example: 1.1 or 1A might be used as a subline number to relate to baseline number 1.

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

 

Trading Partner:

Each SLN represents an individual line item.

 

 

PID

Product/Item Description

Pos: 140 Max: 200

Detail - Optional

Loop: SLN line items Elements: 2

To describe a product or process in coded or free-form format

Element Summary:

 

Ref _

Id_

Element Name _

Req

Type

Min/Max

Usage_

 
 

PID01

349

Item Description Type

Description: Code indicating the format of a description

Code Name _

F Free-form

M

ID

1/1

Must use

 
 

PID05

352

Description

Description: A free-form description to clarify the related data elements and their content

C

AN

1/80

Used

 

Semantics:

1. Use PID03 to indicate the organization that publishes the code list being referred to.

2. PID04 should be used for industry-specific product description codes.

3. PID08 describes the physical characteristics of the product identified in PID04. A "Y" indicates that the specified attribute applies to this item; an "N" indicates it does not apply. Any other value is indeterminate.

4. PID09 is used to identify the language being used in PID05.

 

Comments:

1. If PID01 equals "F", then PID05 is used. If PID01 equals "S", then PID04 is used. If PID01 equals "X", then both PID04 and PID05 are used.

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

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

 

 

 

ITA

Allowance, Charge or Service

Pos: 150 Max: 10

Detail - Optional

Loop: SLN line items Elements: 7

To specify allowances, charges, or services

Element Summary:

 

Ref _

Id_

Element Name _

Req

Type

Min/Max

Usage_

 
 

ITA01

248

Allowance or Charge Indicator

Description: Code which indicates an allowance or charge for the service specified

All valid standard codes are used.

M

ID

1/1

Must use

 
 

ITA04

331

Allowance or Charge Method of Handling Code

Description: Code indicating method of handling for an allowance or charge

All valid standard codes are used.

M

ID

2/2

Must use

 
 

ITA06

359

Allowance or Charge Rate

Description: Allowance or Charge Rate per Unit

O

R

1/15

Used

 
 

ITA07

360

Allowance or Charge Total Amount

Description: Total dollar amount for the allowance or charge

O

N2

1/15

Used

 
 

ITA08

378

Allowance/Charge Percent Qualifier

Description: Code indicating on what basis allowance or charge percent is calculated

Code Name _

Z Mutually Defined

O

ID

1/1

Used

 
 

ITA09

332

Percent

Description: Percent expressed as a percent

C

R

1/6

Used

 
 

ITA13

352

Description

Description: A free-form description to clarify the related data elements and their content

C

AN

1/80

Used

 

Semantics:

1. ITA09 is the allowance or charge percent.

2. ITA10 is the quantity basis when the allowance or charge quantity is different from the purchase order or invoice quantity.

3. ITA12 is the quantity of free goods.

 

Comments:

1. If ITA01 equals "A" - allowance or "C" - charge, then at least one of ITA06, ITA07, or ITA08 must be present.

2. ITA02 identifies the source of the code value in ITA03 or ITA15.

3. If ITA07 is present with either ITA06 or ITA08, then ITA07 takes precedence.

4. ITA13 is used to clarify the allowance, charge, or service.

5. ITA15 specifies the individual code list of the agency specified in ITA02.

6. ITA16 describes the relationship of ITA06, ITA07 or ITA09 to an associated segment.

 

 

 

TDS

Total Monetary Value Summary

Pos: 010 Max: 1

Summary - Mandatory

Loop: N/A Elements: 1

To specify the total invoice discounts and amounts

Element Summary:

 

Ref _

Id_

Element Name _

Req

Type

Min/Max

Usage_

 
 

TDS01

610

Amount

Description: Monetary amount

M

N2

1/15

Must use

 

Semantics:

1. TDS01 is the total amount of invoice (including charges, less allowances) before terms discount (if discount is applicable).

2. TDS02 indicates the amount upon which the terms discount amount is calculated.

3. TDS03 is the amount of invoice due if paid by terms discount due date (total invoice or installment amount less cash discount).

4. TDS04 indicates the total amount of terms discount.

 

Comments:

1. TDS02 is required if the dollar value subject to discount is not equal to the dollar value of TDS01.

 

Trading Partner:

Total Consolidated Invoice Payment Due Amount

 

 

CTT

Transaction Totals

Pos: 020 Max: 1

Summary - Optional

Loop: N/A Elements: 1

To transmit a hash total for a specific element in the transaction set

Element Summary:

 

Ref _

Id_

Element Name _

Req

Type

Min/Max

Usage_

 
 

CTT04

355

Unit or Basis for Measurement Code

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

All valid standard codes are used.

C

ID

2/2

Used

 

 

Syntax:

P0304 -- If either CTT03 or CTT04 are present, then the others are required.

P0506 -- If either CTT05 or CTT06 are present, then the others are required.

 

Comments:

1. This segment is intended to provide hash totals to validate transaction completeness and correctness.

 

 

 

SE

Transaction Set Trailer

Pos: 030 Max: 1

Summary - Mandatory

Loop: N/A Elements: 2

To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)

Element Summary:

 

Ref _

Id_

Element Name _

Req

Type

Min/Max

Usage_

 
 

SE01

96

Number of Included Segments

Description: Total number of segments included in a transaction set including ST and SE segments

M

N0

1/10

Must use

 
 

SE02

329

Transaction Set Control Number

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

M

AN

4/9

Must use

 

Comments:

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

 

 

 

GE

Functional Group Trailer

Pos: Max: 1

Summary - Mandatory

Loop: N/A Elements: 2

To indicate the end of a functional group and to provide control information

Element Summary:

 

Ref _

Id_

Element Name _

Req

Type

Min/Max

Usage_

 
 

GE01

97

Number of Transaction Sets Included

Description: Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element

M

N0

1/6

Must use

 
 

GE02

28

Group Control Number

Description: Assigned number originated and maintained by the sender

M

N0

1/9

Must use

 

Semantics:

1. The data interchange control number GE02 in this trailer must be identical to the same data element in the associated functional group header, GS06.

 

Comments:

1. The use of identical data interchange control numbers in the associated functional group header and trailer is designed to maximize functional group integrity. The control number is the same as that used in the corresponding header.

 

 

 

IEA

Interchange Control Trailer

Pos: Max: 1

Summary - Mandatory

Loop: N/A Elements: 2

To define the end of an interchange of zero or more functional groups and interchange-related control segments

Element Summary:

 

Ref _

Id_

Element Name _

Type

Min/Max

Usage_

 
 

IEA01

I16

Number of Included Functional Groups

Description: A count of the number of functional groups included in an interchange

M

N0

1/5

Must use

 
 

IEA02

I12

Interchange Control Number

Description: A control number assigned by the interchange sender

M

N0

9/9

Must use

 

Billing and Payment Information | Back