810
	Invoice
	Functional Group=IN
This Draft Standard for Trial Use contains the format and establishes the data contents of the Invoice Transaction Set (810) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide for customary and established business and industry practice relative to the billing for goods and services provided.         Heading:   Pos Id Segment Name Req Max Use Repeat Notes Usage                                           010 ST Transaction Set Header M 1       020 BIG Beginning Segment for Invoice M 1       030 NTE Note/Special Instruction 100     X 040 CUR Currency O 1       050 REF Reference Identification O 12       050 REF Reference Identification O 12       050 REF Reference Identification O 12     X 055 YNQ Yes/No Question 10     X 060 PER Administrative Communications Contact 3     Loop ID - N1 200           070 N1 Name O 1           X 080 N2 Additional Name Information 2             090 N3 Address Information O 2             100 N4 Geographic Location O 1           X 110 REF Reference Identification 12           X 120 PER Administrative Communications Contact 3           X 125 DMG Demographic Information 1           Loop ID - N1 200               070 N1 Name O 1               X 080 N2 Additional Name Information 2                 090 N3 Address Information O 2                 100 N4 Geographic Location O 1               X 110 REF Reference Identification 12               X 120 PER Administrative Communications Contact 3               X 125 DMG Demographic Information 1                 130 ITD Terms of Sale/Deferred Terms of Sale O >1       140 DTM Date/Time Reference O 10       140 DTM Date/Time Reference O 10     X 150 FOB F.O.B. Related Instructions 1     X 160 PID Product/Item Description 200     X 170 MEA Measurements 40     X 180 PWK Paperwork 25     X 190 PKG Marking, Packaging, Loading 25     X 200 L7 Tariff Reference 1     X 212 BAL Balance Detail >1     X 213 INC Installment Information 1     X 214 PAM Period Amount >1     Loop ID - LM 10         X 220 LM Code Source Information 1           X 230 LQ Industry Code 100           Loop ID - N9 1           240 N9 Reference Identification O 1             250 MSG Message Text M 10           Loop ID - V1 >1         X 260 V1 Vessel Identification 1           X 270 R4 Port or Terminal >1           X 280 DTM Date/Time Reference >1           Loop ID - FA1 >1         X 290 FA1 Type of Financial Accounting Data 1           X 300 FA2 Accounting Data >1             Detail:   Pos Id Segment Name Req Max Use Repeat Notes Usage                                         Loop ID - IT1 200000           010 IT1 Baseline Item Data (Invoice) O 1           X 012 CRC Conditions Indicator 1           X 015 QTY Quantity 5 N2/015         X 020 CUR Currency 1           X 030 IT3 Additional Item Data 5           X 040 TXI Tax Information 10           X 050 CTP Pricing Information 25           X 055 PAM Period Amount 10           X 059 MEA Measurements 40           Loop ID - PID 1000               060 PID Product/Item Description O 1               X 070 MEA Measurements 10               X 080 PWK Paperwork 25           X 090 PKG Marking, Packaging, Loading 25           X 100 PO4 Item Physical Details 1           X 110 ITD Terms of Sale/Deferred Terms of Sale 2             120 REF Reference Identification O >1           X 125 YNQ Yes/No Question 10           X 130 PER Administrative Communications Contact 5           X 140 SDQ Destination Quantity 500             150 DTM Date/Time Reference O 10           X 160 CAD Carrier Detail >1           X 170 L7 Tariff Reference >1           X 175 SR Requested Service Schedule 1           Loop ID - SAC 25             X 180 SAC Service, Promotion, Allowance, or Charge Information 1               X 190 TXI Tax Information 10               Loop ID - SLN 1000               200 SLN Subline Item Detail O 1               X 205 DTM Date/Time Reference 1               X 210 REF Reference Identification >1               X 220 PID Product/Item Description 1000               X 230 SAC Service, Promotion, Allowance, or Charge Information 25               X 235 TC2 Commodity 2               X 237 TXI Tax Information 10               Loop ID - N1 200             X 240 N1 Name 1               X 250 N2 Additional Name Information 2               X 260 N3 Address Information 2               X 270 N4 Geographic Location 1               X 280 REF Reference Identification 12               X 290 PER Administrative Communications Contact 3               X 295 DMG Demographic Information 1               Loop ID - LM 10             X 300 LM Code Source Information 1               X 310 LQ Industry Code 100               Loop ID - V1 >1             X 320 V1 Vessel Identification 1               X 330 R4 Port or Terminal >1               X 340 DTM Date/Time Reference >1               Loop ID - FA1 >1             X 350 FA1 Type of Financial Accounting Data 1               X 360 FA2 Accounting Data >1                 Summary:   Pos Id Segment Name Req Max Use Repeat Notes Usage                                           010 TDS Total Monetary Value Summary M 1     X 020 TXI Tax Information 10     X 030 CAD Carrier Detail 1       035 AMT Monetary Amount O >1     Loop ID - SAC 25         X 040 SAC Service, Promotion, Allowance, or Charge Information 1           X 050 TXI Tax Information 10           Loop ID - ISS >1           060 ISS Invoice Shipment Summary O 1           X 065 PID Product/Item Description 1             070 CTT Transaction Totals O 1 N3/070     080 SE Transaction Set Trailer M 1

Notes:

2/015	The QTY segment is used to specify a quantity of units which are expected as payments, e.g., trade-ins or returns.
3/070	Number of line items (CTT01) is the accumulation of the number of IT1 segments. If used, hash total (CTT02) is the sum of the value of quantities invoiced (IT102) for each IT1 segment.

 

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:

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

User: Generated by translator.

 

BIG
	Beginning Segment for Invoice	.	Pos: 020 Max: 1 Heading - Mandatory Loop: N/A Elements: 10	.

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

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.

 

NTE
	Note/Special Instruction	.	Pos: 030 Max: 100 Heading - Loop: N/A Elements: 2	.

To transmit information in a free-form format, if necessary, for comment or special instruction Element Summary:

Comments:

1.	The NTE segment permits free-form information/data which, under ANSI X12 standard implementations, is not machine processable. The use of the NTE segment should therefore be avoided, if at all possible, in an automated environment.

User: To provide non-warranty statement comments. If invoice has no comments other than warranty statement, do not map this segment.

 

REF
	Reference Identification	.	Pos: 050 Max: 12 Heading - Optional Loop: N/A Elements: 4	.

To specify identifying information Element Summary:

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

Semantics:

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

User: To provide network information. This segment is mandatory for TECC mapping structure. Use only one occurence of this REF segment. Only one selling network per invoice is allowed.

 

REF
	Reference Identification	.	Pos: 050 Max: 12 Heading - Optional Loop: N/A Elements: 4	.

To specify identifying information Element Summary:

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

Semantics:

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

User: To provide advertiser information. This segment is mandatory for TECC mapping structure.

 

REF
	Reference Identification	.	Pos: 050 Max: 12 Heading - Optional Loop: N/A Elements: 4	.

To specify identifying information Element Summary:

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

Semantics:

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

User: To provide media type information. This segment is mandatory for TECC mapping structure.

 

N1
	Name	.	Pos: 070 Max: 1 Heading - Optional Loop: N1 Elements: 6	.

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

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.

User: To provide agency information. This segment is mandatory for TECC mapping structure.

 

N3
	Address Information	.	Pos: 090 Max: 2 Heading - Optional Loop: N1 Elements: 2	.

To specify the location of the named party Element Summary:

User: Agency street address information for billing. Do not use for city, state or zip code. These elements to follow in the N4 segment.

 

N4
	Geographic Location	.	Pos: 100 Max: 1 Heading - Optional Loop: N1 Elements: 6	.

To specify the geographic place of the named party Element Summary:

Syntax:
C0605 -- If N406 is present, then N405 is required

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.

User: Agency location for billing.

 

N1
	Name	.	Pos: 070 Max: 1 Heading - Optional Loop: N1 Elements: 6	.

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

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.

User: To provide remittance information. This segment is mandatory for TECC mapping structure.

 

N3
	Address Information	.	Pos: 090 Max: 2 Heading - Optional Loop: N1 Elements: 2	.

To specify the location of the named party Element Summary:

User: Remit street address information. Do not use for city, state or zip code. These elements to follow in the N4 segment.

 

N4
	Geographic Location	.	Pos: 100 Max: 1 Heading - Optional Loop: N1 Elements: 6	.

To specify the geographic place of the named party Element Summary:

Syntax:
C0605 -- If N406 is present, then N405 is required

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.

User: Remit location information.

 

ITD
	Terms of Sale/Deferred Terms of Sale	.	Pos: 130 Max: >1 Heading - Optional Loop: N/A Elements: 15	.

To specify terms of sale Element Summary:

Syntax:
1. ITD03 L03040513 -- If ITD03 is present, then at least one of ITD04, ITD05 or ITD13 is required.
2. ITD08 L08040513 -- If ITD08 is present, then at least one of ITD04, ITD05 or ITD13 is required.
3. ITD09 L091011 -- If ITD09 is present, then at least one of ITD10 or ITD11 is required.

Semantics:

1.	ITD15 is the percentage applied to a base amount used to determine a late payment charge.

Comments:

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

User: Invoice due date.

 

DTM
	Date/Time Reference	.	Pos: 140 Max: 10 Heading - Optional Loop: N/A Elements: 6	.

To specify pertinent dates and times Element Summary:

Syntax:
1. DTM02 R020305 -- At least one of DTM02, DTM03 or DTM05 is required.
2. DTM04 C0403 -- If DTM04 is present, then DTM03 is required
3. DTM05 P0506 -- If either DTM05 or DTM06 are present, then the others are required.

User: Invoice period start date.

 

DTM
	Date/Time Reference	.	Pos: 140 Max: 10 Heading - Optional Loop: N/A Elements: 6	.

To specify pertinent dates and times Element Summary:

Syntax:
DTM02 R020305 -- At least one of DTM02, DTM03 or DTM05 is required.
DTM04 C0403 -- If DTM04 is present, then DTM03 is required
DTM05 P0506 -- If either DTM05 or DTM06 are present, then the others are required.

User: Invoice period end date.

 

N9
	Reference Identification	.	Pos: 240 Max: 1 Heading - Optional Loop: N9 Elements: 7	.

To transmit identifying information as specified by the Reference Identification Qualifier Element Summary:

Syntax:
R0203 -- At least one of N902 or N903 is required.
C0605 -- If N906 is present, then N905 is required

Semantics:

1.	N906 reflects the time zone which the time reflects.
2.	N907 contains data relating to the value cited in N902.

User: To provide invoice warranty statement. X12 requires that an N9 segment be mapped in order to use the MSG segment at this position in the heading area. If no warranty statement exists at this level, do not transmit this segment.

 

MSG
	Message Text	.	Pos: 250 Max: 10 Heading - Mandatory Loop: N9 Elements: 3	.

To provide a free-form format that allows the transmission of text information Element Summary:

Syntax:
C0302 -- If MSG03 is present, then MSG02 is required

Semantics:

1.	MSG03 is the number of lines to advance before printing.

Comments:

1.	MSG02 is not related to the specific characteristics of a printer, but identifies top of page, advance a line, etc.
2.	If MSG02 is "AA - Advance the specified number of lines before print" then MSG03 is required.

User: To provide invoice warranty statement. Repeat as necessary.

 

IT1
	Baseline Item Data (Invoice)	.	Pos: 010 Max: 1 Detail - Optional Loop: IT1 Elements: 22	.

To specify the basic and most frequently used line item data for the invoice and related transactions Element Summary:

Syntax:
P020304 -- If either IT102, IT103 or IT104 are present, then the others are required.
P0607 -- If either IT106 or IT107 are present, then the others are required.
P0809 -- If either IT108 or IT109 are present, then the others are required.
P1011 -- If either IT110 or IT111 are present, then the others are required.
P1213 -- If either IT112 or IT113 are present, then the others are required.
P1415 -- If either IT114 or IT115 are present, then the others are required.
P1617 -- If either IT116 or IT117 are present, then the others are required.
P1819 -- If either IT118 or IT119 are present, then the others are required.
P2021 -- If either IT120 or IT121 are present, then the others are required.
P2223 -- If either IT122 or IT123 are present, then the others are required.
P2425 -- If either IT124 or IT125 are present, then the others are required.

Semantics:

1.	IT101 is the purchase order line item identification.

Comments:

1.	Element 235/234 combinations should be interpreted to include products and/or services. See the Data Dictionary for a complete list of IDs.
2.	IT106 through IT125 provide for ten different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.

User: To provide invoice detail.

 

PID
	Product/Item Description	.	Pos: 060 Max: 1 Detail - Optional Loop: PID Elements: 9	.

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

Syntax:
C0403 -- If PID04 is present, then PID03 is required
R0405 -- At least one of PID04 or PID05 is required.
C0703 -- If PID07 is present, then PID03 is required
C0804 -- If PID08 is present, then PID04 is required
C0905 -- If PID09 is present, then PID05 is required

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.

User: To provide additional program information.

 

REF
	Reference Identification	.	Pos: 120 Max: >1 Detail - Optional Loop: IT1 Elements: 4	.

To specify identifying information Element Summary: