810 Invoice 
 
   
Functional Group ID=IN
 
 
Introduction: 
 
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. Seg. Req. Loop Notes and
  No. ID Name Des. Max.Use Repeat Comments
 
Must Use 010 ST Transaction Set Header M 1
Must Use 020 BIG Beginning Segment for Invoice M 1
  050 REF Reference Identification O 12
  LOOP ID - N1 200  
  070 N1 Name O 1  
  071 N3 Address Information O 1  
  071 N4 Geographic Location O 1  
  071 N1 Name O 1  
  072 N3 Address Information O 1  
  072 N4 Geographic Location O 1  
  072 N1 Name O 1  
  073 N3 Address Information O 1  
  073 N4 Geographic Location O 1  
  073 N1 Name O 1  
  090 N3 Address Information O 2  
  100 N4 Geographic Location O 1  
 
  130 ITD Terms of Sale/Deferred Terms of Sale O >1
  140 DTM Date/Time Reference O 10
  150 FOB F.O.B. Related Instructions O 1
 
Detail:
 
 
  Pos. Seg. Req. Loop Notes and
  No. ID Name Des. Max.Use Repeat Comments
 
  LOOP ID - IT1 200000  
  010 IT1 Baseline Item Data (Invoice) O 1  
  LOOP ID - PID 1000    
  060 PID Product/Item Description O 1    
 
  LOOP ID - SAC 25    
  180 SAC Service, Promotion, Allowance, or Charge Information O 1    
 
 
Detail:
 
 
  Pos. Seg. Req. Loop Notes and
  No. ID Name Des. Max.Use Repeat Comments
 
Must Use 010 TDS Total Monetary Value Summary M 1
  030 CAD Carrier Detail O 1
 
Summary:
 
 
  Pos. Seg. Req. Loop Notes and
  No. ID Name Des. Max.Use Repeat Comments
 
  LOOP ID - ISS >1  
  060 ISS Invoice Shipment Summary O 1  
 
  070 CTT Transaction Totals O 1 n1
Must Use 080 SE Transaction Set Trailer M 1
 
Transaction Set Notes 
 
       
1. 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.
 

           
Segment: ST Transaction Set Header
Position: 010
Loop:
Level: Heading
Usage: Mandatory
Max Use: 1
Purpose: To indicate the start of a transaction set and to assign a control number
Syntax Notes:
Semantic Notes: 1 The transaction set identifier (ST01) is used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
Comments:
 
 
 
Data Element Summary 
                               
  Ref. Data
  Des. Element Name Attributes
>> ST01 143 Transaction Set Identifier Code M ID 3/3
  Code uniquely identifying a Transaction Set
  Refer to 004010 Data Element Dictionary for acceptable code values.
>> ST02 329 Transaction Set Control Number M AN 4/9
  Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

           
Segment: BIG Beginning Segment for Invoice
Position: 020
Loop:
Level: Heading
Usage: Mandatory
Max Use: 1
Purpose: To indicate the beginning of an invoice transaction set and transmit identifying numbers and dates
Syntax Notes:
Semantic Notes: 1 BIG01 is the invoice issue date.
  2 BIG03 is the date assigned by the purchaser to purchase order.
  3 BIG10 indicates the consolidated invoice number. When BIG07 contains code CI, BIG10 is not used.
Comments: 1 BIG07 is used only to further define the type of invoice when needed.
Notes: BIG07 is used only to further define the type of invoice when needed. 
Segment Example: BIG*19980327*M02293767**OZKC0001943***PR^ 
 
Data Element Summary 
                               
  Ref. Data
  Des. Element Name Attributes
>> BIG01 373 Date M DT 8/8
  Date expressed as CCYYMMDD
  Please Note that the Date has increased by two char's (digits) with the addition of the "Century" positions (from 6/6 to 8/8, as in the 003030 version.
>> BIG02 76 Invoice Number M AN 1/22
  Identifying number assigned by issuer
  BIG03 373 Date O DT 8/8
  Date expressed as CCYYMMDD
  BIG04 324 Purchase Order Number O AN 1/22
  Identifying number for Purchase Order assigned by the orderer/purchaser
  BIG07 640 Transaction Type Code O ID 2/2
  Code specifying the type of transaction
  Suggested Codes for the Aftermarket usage. Any ASC X12 approved code may be used. 
CR Credit Memo 
DR Debit Memo 
PR Product (or Service) 
  Refer to 004010 Data Element Dictionary for acceptable code values.

           
Segment: REF Reference Identification
Position: 050
Loop:
Level: Heading
Usage: Optional
Max Use: 12
Purpose: To specify identifying information
Syntax Notes: 1 At least one of REF02 or REF03 is required.
  2 If either C04003 or C04004 is present, then the other is required.
  3 If either C04005 or C04006 is present, then the other is required.
Semantic Notes: 1 REF04 contains data relating to the value cited in REF02.
Comments:
Notes: Segment Example: REF*BM*12345^ 
This is an optional segment.
 
Data Element Summary 
                               
  Ref. Data
  Des. Element Name Attributes
>> REF01 128 Reference Identification Qualifier M ID 2/3
  Code qualifying the Reference Identification
  Suggested Code for aftermarket usage. Any ASC X12 approved code may be used. (Number of Char's changed from 2/2 [003030] to 2/3 (004010). 
 
BM Bill of Lading Number 
IA Internal Vendor Number 
PK Packing List Number
  Refer to 004010 Data Element Dictionary for acceptable code values.
  REF02 127 Reference Identification X AN 1/30
  Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

           
Segment: N1 Name
Position: 070
Loop: N1 Optional
Level: Heading
Usage: Optional
Max Use: 1
Purpose: To identify a party by type of organization, name, and code
  This segment, used alone, provides the most efficient method of providing organizational identification. To provide the effeciency the ID Code (N104) must provide a key to the table maintained bt the transaction processing party.
Syntax Notes: 1 At least one of N102 or N103 is required.
  2 If either N103 or N104 is present, then the other is required.
Semantic Notes:
Comments: 1 This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
  2 N105 and N106 further define the type of entity in N101.
Notes: Segment Example: N1*SF**92*H98111A1^
 
Data Element Summary 
                               
  Ref. Data
  Des. Element Name Attributes
>> N101 98 Entity Identifier Code M ID 2/3
  Code identifying an organizational entity, a physical location, property or an individual
  Suggested Code for the Aftermarket usage. Any ASC X12 approved code may be used. (Please note this increased from 2/2 [3030] to 2/3 [4010). 
 
SF Ship From
  Refer to 004010 Data Element Dictionary for acceptable code values.
  N103 66 Identification Code Qualifier X ID 1/2
  Code designating the system/method of code structure used for Identification Code (67)
  Suggested code for the Aftermarket usage. Any ASC X12 approved code may be used. 
 
92 Assigned by Buyer or Buyer's Agent.
  Refer to 004010 Data Element Dictionary for acceptable code values.
  N104 67 Identification Code X AN 2/80
  Code identifying a party or other code
  Machine Readable Code. Please note this changed from 2/17 [3030] to 2/80 
in the 004010 version.

           
Segment: N3 Address Information
Position: 071
Loop: N1 Optional
Level: Heading
Usage: Optional
Max Use: 1
Purpose: To specify the location of the named party
Syntax Notes:
Semantic Notes:
Comments:
 
 
 
Data Element Summary 
                               
  Ref. Data
  Des. Element Name Attributes
>> N301 166 Address Information M AN 1/55
  Address information
  Suggested codes for Aftermarket usae. Any ASC X12 approved code may be used. Note. This was the ITA01 in 003030. 
 
A Allowance 
C Charge 
N No Allowance or Charge
  N302 166 Address Information O AN 1/55
  Address information
  Suggested codes for Aftermarket usage. Any ASC X12 approved code may be used. 
 
C580 Emergency Service (ITA03,EM - 3030) 
D500 Handling Service (ITA03,HC - 3030) 
H090 Special Handling Service (ITA03,SH - 3030)

           
Segment: N4 Geographic Location
Position: 071
Loop: N1 Optional
Level: Heading
Usage: Optional
Max Use: 1
Purpose: To specify the geographic place of the named party
Syntax Notes: 1 If N406 is present, then N405 is required.
Semantic Notes:
Comments: 1 A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
  2 N402 is required only if city name (N401) is in the U.S. or Canada.
 
 
 
Data Element Summary 
                               
  Ref. Data
  Des. Element Name Attributes
  N401 19 City Name O AN 2/30
  Free-form text for city name
  N402 156 State or Province Code O ID 2/2
  Code (Standard State/Province) as defined by appropriate government agency
  N403 116 Postal Code O ID 3/15
  Code defining international postal zone code excluding punctuation and blanks (zip code for United States)

           
Segment: N1 Name
Position: 071
Loop: N1 Optional
Level: Heading
Usage: Optional
Max Use: 1
Purpose: To identify a party by type of organization, name, and code
  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.
Syntax Notes: 1 At least one of N102 or N103 is required.
  2 If either N103 or N104 is present, then the other is required.
Semantic Notes:
Comments: 1 This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
  2 N105 and N106 further define the type of entity in N101.
Notes: Segment Example: N1*ST*92*123456789^
 
Data Element Summary 
                               
  Ref. Data
  Des. Element Name Attributes
>> N101 98 Entity Identifier Code M ID 2/3
  Code identifying an organizational entity, a physical location, property or an individual
  Suggested code for the Aftermarket usage. Any ASC X12 approved code may be used. 
 
ST Ship To.
  Refer to 004010 Data Element Dictionary for acceptable code values.
  N103 66 Identification Code Qualifier X ID 1/2
  Code designating the system/method of code structure used for Identification Code (67)
  Suggested code for Aftermarket usage. Any ASC X12 approved code may be used. 
 
92 Assigned by Buyer or Buyer,s Agent.
  Refer to 004010 Data Element Dictionary for acceptable code values.
  N104 67 Identification Code X AN 2/80
  Code identifying a party or other code
  Please note that the N104 has increased from 2/17 to 2/80.

           
Segment: N3 Address Information
Position: 072
Loop: N1 Optional
Level: Heading
Usage: Optional
Max Use: 1
Purpose: To specify the location of the named party
Syntax Notes:
Semantic Notes:
Comments:
 
 
 
Data Element Summary 
                               
  Ref. Data
  Des. Element Name Attributes
>> N301 166 Address Information M AN 1/55
  Address information
  N302 166 Address Information O AN 1/55
  Address information

           
Segment: N4 Geographic Location
Position: 072
Loop: N1 Optional
Level: Heading
Usage: Optional
Max Use: 1
Purpose: To specify the geographic place of the named party
Syntax Notes: 1 If N406 is present, then N405 is required.
Semantic Notes:
Comments: 1 A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
  2 N402 is required only if city name (N401) is in the U.S. or Canada.
 
 
 
Data Element Summary 
                               
  Ref. Data
  Des. Element Name Attributes
  N401 19 City Name O AN 2/30
  Free-form text for city name
  N402 156 State or Province Code O ID 2/2
  Code (Standard State/Province) as defined by appropriate government agency
  N403 116 Postal Code O ID 3/15
  Code defining international postal zone code excluding punctuation and blanks (zip code for United States)

           
Segment: N1 Name
Position: 072
Loop: N1 Optional
Level: Heading
Usage: Optional
Max Use: 1
Purpose: To identify a party by type of organization, name, and code
Syntax Notes: 1 At least one of N102 or N103 is required.
  2 If either N103 or N104 is present, then the other is required.
Semantic Notes:
Comments: 1 This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
  2 N105 and N106 further define the type of entity in N101.
Notes: Segment Example: N1*RE**92*234567890^
 
Data Element Summary 
                               
  Ref. Data
  Des. Element Name Attributes
>> N101 98 Entity Identifier Code M ID 2/3
  Code identifying an organizational entity, a physical location, property or an individual
  Suggested code for the Aftermarket usage. Any ASC X12 approved code may be used. 
 
RE Party to receive commercial invoice remittance
  Refer to 004010 Data Element Dictionary for acceptable code values.
  N103 66 Identification Code Qualifier X ID 1/2
  Code designating the system/method of code structure used for Identification Code (67)
  Suggested code for Aftermarket usage. Any ASC X12 approved code may be used. 
92 Assigned by Buyer or Buyer's Agent.
  Refer to 004010 Data Element Dictionary for acceptable code values.
  N104 67 Identification Code X AN 2/80
  Code identifying a party or other code

           
Segment: N3 Address Information
Position: 073
Loop: N1 Optional
Level: Heading
Usage: Optional
Max Use: 1
Purpose: To specify the location of the named party
Syntax Notes:
Semantic Notes:
Comments:
 
 
 
Data Element Summary 
                               
  Ref. Data
  Des. Element Name Attributes
>> N301 166 Address Information M AN 1/55
  Address information
  N302 166 Address Information O AN 1/55
  Address information

           
Segment: N4 Geographic Location
Position: 073
Loop: N1 Optional
Level: Heading
Usage: Optional
Max Use: 1
Purpose: To specify the geographic place of the named party
Syntax Notes: 1 If N406 is present, then N405 is required.
Semantic Notes:
Comments: 1 A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
  2 N402 is required only if city name (N401) is in the U.S. or Canada.
 
 
 
Data Element Summary 
                               
  Ref. Data
  Des. Element Name Attributes
  N401 19 City Name O AN 2/30
  Free-form text for city name
  N402 156 State or Province Code O ID 2/2
  Code (Standard State/Province) as defined by appropriate government agency
  N403 116 Postal Code O ID 3/15
  Code defining international postal zone code excluding punctuation and blanks (zip code for United States)

           
Segment: N1 Name
Position: 073
Loop: N1 Optional
Level: Heading
Usage: Optional
Max Use: 1
Purpose: To identify a party by type of organization, name, and code
Syntax Notes: 1 At least one of N102 or N103 is required.
  2 If either N103 or N104 is present, then the other is required.
Semantic Notes:
Comments: 1 This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
  2 N105 and N106 further define the type of entity in N101.
Notes: Segment Example: N1*VN**92*345678901^
 
Data Element Summary 
                               
  Ref. Data
  Des. Element Name Attributes
>> N101 98 Entity Identifier Code M ID 2/3
  Code identifying an organizational entity, a physical location, property or an individual
  Suggested code for the Aftermarket usage. Any ASC X12 approved code may be used. 
 
BT BILL TO
  Refer to 004010 Data Element Dictionary for acceptable code values.
  N103 66 Identification Code Qualifier X ID 1/2
  Code designating the system/method of code structure used for Identification Code (67)
  Suggested code for the Aftermarket usage. Any ASC X12 approved code may be used. 
 
92 Assigned Buyer or Buyer's Agent.
  Refer to 004010 Data Element Dictionary for acceptable code values.
  N104 67 Identification Code X AN 2/80
  Code identifying a party or other code

           
Segment: N3 Address Information
Position: 090
Loop: N1 Optional
Level: Heading
Usage: Optional
Max Use: 2
Purpose: To specify the location of the named party
Syntax Notes:
Semantic Notes:
Comments:
 
 
 
Data Element Summary 
                               
  Ref. Data
  Des. Element Name Attributes
>> N301 166 Address Information M AN 1/55
  Address information
  N302 166 Address Information O AN 1/55
  Address information

           
Segment: N4 Geographic Location
Position: 100
Loop: N1 Optional
Level: Heading
Usage: Optional
Max Use: 1
Purpose: To specify the geographic place of the named party
Syntax Notes: 1 If N406 is present, then N405 is required.
Semantic Notes:
Comments: 1 A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
  2 N402 is required only if city name (N401) is in the U.S. or Canada.
 
 
 
Data Element Summary 
                               
  Ref. Data
  Des. Element Name Attributes
  N401 19 City Name O AN 2/30
  Free-form text for city name
  N402 156 State or Province Code O ID 2/2
  Code (Standard State/Province) as defined by appropriate government agency
  N403 116 Postal Code O ID 3/15
  Code defining international postal zone code excluding punctuation and blanks (zip code for United States)

           
Segment: ITD Terms of Sale/Deferred Terms of Sale
Position: 130
Loop:
Level: Heading
Usage: Optional
Max Use: >1
Purpose: To specify terms of sale
Syntax Notes: 1 If ITD03 is present, then at least one of ITD04 ITD05 or ITD13 is required.
  2 If ITD08 is present, then at least one of ITD04 ITD05 or ITD13 is required.
  3 If ITD09 is present, then at least one of ITD10 or ITD11 is required.
Semantic Notes: 1 ITD15 is the percentage applied to a base amount used to determine a 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.
Notes: Segment Example: ITD*12*03*02**10****19981010**33333**10*R*015^
 
Data Element Summary 
                               
  Ref. Data
  Des. Element Name Attributes
  ITD01 336 Terms Type Code O ID 2/2
  Code identifying type of payment terms
  Suggested codes for aftermarket usage. Any ASC X12 approved code may be used. 
 
01 Basic 
02 End of Month (EOM) 
03 Fixed Date 
05 Discount Not Applicable 
07 Extended 
08 Basic Discount Offered 
12 10 Days After End of Month (10 EOM) 
14 Previously agreed upon 
18 Fixed Date, late Payment Penalty Applies 
Sales terms specifying a past due date, and a late 
payment percentage penalty applies to unpaid 
balances past this due date 
22 Cash Discount Terms Apply 
Contract terms specify that a crash discount is applicable 
23 payment Due Upon Receipt of Invoice
  Refer to 004010 Data Element Dictionary for acceptable code values.
  ITD02 333 Terms Basis Date Code O ID 1/2
  Code identifying the beginning of the terms period
  Suggested codes for the Aftermarket usage. Any ASC X12approved codes may be used. 
3 Invoice Date 
4 Specified Date
  Refer to 004010 Data Element Dictionary for acceptable code values.
  ITD03 338 Terms Discount Percent O R 1/6
  Terms discount percentage, expressed as a percent, available to the purchaser if an invoice is paid on or before the Terms Discount Due Date
  ITD04 370 Terms Discount Due Date X DT 8/8
  Date payment is due if discount is to be earned expressed in format CCYYMMDD
  Please note that the due date has changed from 6/6 to 8/8 char's.
  ITD05 351 Terms Discount Days Due X N0 1/3
  Number of days in the terms discount period by which payment is due if terms discount is earned
  Element is required if element ITD03 is populated.
  ITD07 386 Terms Net Days O N0 1/3
  Number of days until total invoice amount is due (discount not applicable)
  Element required if value in element ITD01 is "05."
  ITD09 388 Terms Deferred Due Date O DT 8/8
  Date deferred payment or percent of invoice payable is due expressed in format CCYYMMDD
  Please note that the due date has changed from 6/6 to 8/8 char's.
  ITD11 342 Percent of Invoice Payable X R 1/5
  Amount of invoice payable expressed in percent
  ITD13 765 Day of Month X N0 1/2
  The numeric value of the day of the month between 1 and the maximum day of the month being referenced
  ITD14 107 Payment Method Code O ID 1/2
  Code identifying type of payment procedures
  Suggested codes for Aftermarket usage. Any ASC X12 approved codes nay be used. 
 
C Pay By Check 
R Related Detail Account. Individual account that provides supporting data for a billing or summary amount. 
  Refer to 004010 Data Element Dictionary for acceptable code values.
  ITD15 954 Percent O R 1/10
  Percentage expressed as a decimal

           
Segment: DTM Date/Time Reference
Position: 140
Loop:
Level: Heading
Usage: Optional
Max Use: 10
Purpose: To specify pertinent dates and times
Syntax Notes: 1 At least one of DTM02 DTM03 or DTM05 is required.
  2 If DTM04 is present, then DTM03 is required.
  3 If either DTM05 or DTM06 is present, then the other is required.
Semantic Notes:
Comments:
Notes: This is an optional segment. 
Segment Example: DTM*011*19980910**19^
 
Data Element Summary 
                               
  Ref. Data
  Des. Element Name Attributes
>> DTM01 374 Date/Time Qualifier M ID 3/3
  Code specifying type of date or time, or both date and time
  Suggested value for the Aftermarket usage. Any ASC X12 approved code may be used. 
 
011 Shipped
  Refer to 004010 Data Element Dictionary for acceptable code values.
  DTM02 373 Date X DT 8/8
  Date expressed as CCYYMMDD

           
Segment: FOB F.O.B. Related Instructions
Position: 150
Loop:
Level: Heading
Usage: Optional
Max Use: 1
Purpose: To specify transportation instructions relating to shipment
Syntax Notes: 1 If FOB03 is present, then FOB02 is required.
  2 If FOB04 is present, then FOB05 is required.
  3 If FOB07 is present, then FOB06 is required.
  4 If FOB08 is present, then FOB09 is required.
Semantic Notes: 1 FOB01 indicates which party will pay the carrier.
  2 FOB02 is the code specifying transportation responsibility location.
  3 FOB06 is the code specifying the title passage location.
  4 FOB08 is the code specifying the point at which the risk of loss transfers. This may be different than the location specified in FOB02/FOB03 and FOB06/FOB07.
Comments:
Notes: Segment Example: FOB*CC^
 
Data Element Summary 
                               
  Ref. Data
  Des. Element Name Attributes
>> FOB01 146 Shipment Method of Payment M ID 2/2
  Code identifying payment terms for transportation charges
  Suggested codes for Aftermarket usage. Any ASC X12 approved code may be used. 
 
CC Collect 
PC Prepaid but Charged to Customer 
PP Prepaid (bt Seller) 
PS Paid by Seller (Drop Ship) 
PU Pickup
  Refer to 004010 Data Element Dictionary for acceptable code values.

           
Segment: IT1 Baseline Item Data (Invoice)
Position: 010
Loop: IT1 Optional
Level: Detail
Usage: Optional
Max Use: 1
Purpose: To specify the basic and most frequently used line item data for the invoice and related transactions
Syntax Notes: 1 If any of IT102 IT103 or IT104 is present, then all are required.
  2 If either IT106 or IT107 is present, then the other is required.
  3 If either IT108 or IT109 is present, then the other is required.