X12 810 Invoice
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.
- ~ Segment
- * Element
- > Component
Interchange Control Header
To start and identify an interchange of zero or more functional groups and interchange-related control segments
Code to identify the type of information in the Authorization Information
- 00
- No Authorization Information Present (No Meaningful Information in I02)
Information used for additional identification or authorization of the interchange sender or the data in the interchange; the type of information is set by the Authorization Information Qualifier (I01)
Code to identify the type of information in the Security Information
- 00
- No Security Information Present (No Meaningful Information in I04)
This is used for identifying the security information about the interchange sender or the data in the interchange; the type of information is set by the Security Information Qualifier (I03)
Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified
Identification code published by the sender for other parties to use as the receiver ID to route data to them; the sender always codes this value in the sender ID element
Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified
Identification code published by the receiver of the data; When sending, it is used by the sender as their sending ID, thus other parties sending to them will use this as a receiving ID to route data to them
Code to identify the agency responsible for the control standard used by the message that is enclosed by the interchange header and trailer
- U
- U.S. EDI Community of ASC X12, TDCC, and UCS
This version number covers the interchange control segments
- 00401
- Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1997
A control number assigned by the interchange sender
Code sent by the sender to request an interchange acknowledgment (TA1)
- 0
- No Acknowledgment Requested
- 1
- Interchange Acknowledgment Requested
Code to indicate whether data enclosed by this interchange envelope is test, production or information
- I
- Information
- P
- Production Data
- T
- Test Data
Type is not applicable; the component element separator is a delimiter and not a data element; this field provides the delimiter used to separate component data elements within a composite data structure; this value must be different than the data element separator and the segment terminator
- >
- Component Element Separator
Functional Group Header
To indicate the beginning of a functional group and to provide control information
Code identifying a group of application related transaction sets
- IN
- Invoice Information (810,819)
Code identifying party sending transmission; codes agreed to by trading partners
Code identifying party receiving transmission. Codes agreed to by trading partners
Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)
Assigned number originated and maintained by the sender
Code used in conjunction with Data Element 480 to identify the issuer of the standard
- T
- Transportation Data Coordinating Committee (TDCC)
- X
- Accredited Standards Committee X12
Code indicating the version, release, subrelease, and industry identifier of the EDI standard being used, including the GS and GE segments; if code in DE455 in GS segment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 are the release and subrelease, level of the version; and positions 7-12 are the industry or trade association identifiers (optionally assigned by user); if code in DE455 in GS segment is T, then other formats are allowed
- 004010
- Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1997
Heading
Transaction Set Header
To indicate the start of a transaction set and to assign a control number
Code uniquely identifying a Transaction Set
- The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
- 810
- Invoice
Beginning Segment for Invoice
To indicate the beginning of an invoice transaction set and transmit identifying numbers and dates
Sample EDI:
BIG20070606999999999920070410999999900~
Date expressed as CCYYMMDD
- BIG01 is the invoice issue date.
Date expressed as CCYYMMDD
- BIG03 is the date assigned by the purchaser to purchase order.
Identifying number for Purchase Order assigned by the orderer/purchaser
Number identifying a release against a Purchase Order previously placed by the parties involved in the transaction
This is the Release Number from the 850 Purchase Order Transaction or 860 Purchase Order Change Transaction. The Vendor must send this number back in the 810 Invoice in order to identify the correct Release version. Default is '0'.
Number assigned by the orderer identifying a specific change or revision to a previously transmitted transaction set
This is the Revision Number from the 850 Purchase Order Transaction or 860 Purchase Order Change Transaction. The Vendor must send this number back in the 810 Invoice in order to identify the correct revision. Default is '0'.
Currency
To specify the currency (dollars, pounds, francs, etc.) used in a transaction
Sample EDI:
CURBYUSD~
Code identifying an organizational entity, a physical location, property or an individual
- BY
- Buying Party (Purchaser)
PO Type
To specify identifying information
AT&T Mobility Notes:
The REF*ZZ must be returned with the same value sent on the Purchase Order.
Sample EDI:
REFZZHandset Device Accessory~
Code qualifying the Reference Identification
- ZZ
- PO Type
Supplier Number
To specify identifying information
Sample EDI:
REFZA99999999~
Code qualifying the Reference Identification
- ZA
- Supplier
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
Sample EDI:
PERSUFirstName LastName~
Code identifying the major duty or responsibility of the person or group named
- SU
- Supplier Contact
Code identifying the type of communication number
- TE
- Telephone
Complete communications number including country or area code when applicable
Code identifying the type of communication number
- FX
- Facsimile
Complete communications number including country or area code when applicable
Code identifying the type of communication number
- EM
- Electronic Mail
Name
To identify a party by type of organization, name, and code
Sample EDI:
N1RIREMIT TO929999999~
Code identifying an organizational entity, a physical location, property or an individual
- RI
- Remit To
Code designating the system/method of code structure used for Identification Code (67)
- 92
- Assigned by Buyer or Buyer's Agent
Code identifying a party or other 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.
Name
To identify a party by type of organization, name, and code
Sample EDI:
N1STSHIP TO929999999~
Code identifying an organizational entity, a physical location, property or an individual
- ST
- Ship To
Code designating the system/method of code structure used for Identification Code (67)
- 92
- Assigned by Buyer or Buyer's Agent
Code identifying a party or other 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.
Name
To identify a party by type of organization, name, and code
Sample EDI:
N1VNVENDOR NAME~
Code identifying an organizational entity, a physical location, property or an individual
- VN
- Vendor
Code designating the system/method of code structure used for Identification Code (67)
- 92
- Assigned by Buyer or Buyer's Agent
Code identifying a party or other 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.
Terms of Sale/Deferred Terms of Sale
To specify terms of sale
Sample EDI:
ITD013*2007070530***Up to 02/08/2007 without deduction~
Code identifying type of payment terms
- 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.
- 01
- Basic
Code identifying the beginning of the terms period
- 3
- Invoice Date
Terms discount percentage, expressed as a percent, available to the purchaser if an invoice is paid on or before the Terms Discount Due Date
Date payment is due if discount is to be earned expressed in format CCYYMMDD
Number of days in the terms discount period by which payment is due if terms discount is earned
Date when total invoice amount becomes due expressed in format CCYYMMDD
Number of days until total invoice amount is due (discount not applicable)
Date deferred payment or percent of invoice payable is due expressed in format CCYYMMDD
Amount of invoice payable expressed in percent
A free-form description to clarify the related data elements and their content
Date/Time Reference
To specify pertinent dates and times
Sample EDI:
DTM01120070530~
F.O.B. Related Instructions
To specify transportation instructions relating to shipment
Sample EDI:
FOB*PC~
Detail
Baseline Item Data (Invoice)
To specify the basic and most frequently used line item data for the invoice and related transactions
Sample EDI:
IT10000031EA772*SKRTL.12345~
Alphanumeric characters assigned for differentiation within a transaction set
- IT101 is the purchase order line item identification.
The Assigned Identification must match the Original Purchase Order Line Number.
Number of units invoiced (supplier units)
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- BG
- Bag
- BX
- Box
- CA
- Case
- CT
- Carton
- DA
- Days
- DZ
- Dozen
- EA
- Each
- FT
- Foot
- HR
- Hours
- HU
- Hundred
- LB
- Pound
- LO
- Lot
- MO
- Months
- PD
- Pad
- PF
- Pallet (Lift)
- PK
- Package
- Q1
- Quarter (Time)
- RL
- Roll
- RM
- Ream
- ST
- Set
- SY
- Square Yard
- TH
- Thousand
- YR
- Years
Price per unit of product, service, commodity, etc.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- IT106 through IT125 provide for ten different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
- SK
- Stock Keeping Unit (SKU)
Pricing Information
To specify pricing information
Sample EDI:
CTP*EST42400100EA~
Code identifying pricing specification
- EST
- Estimated Price
Price per unit of product, service, commodity, etc.
- See Figures Appendix for an example detailing the use of CTP03 and CTP04.
- See Figures Appendix for an example detailing the use of CTP03, CTP04 and CTP07.
Extended Unit Price
Calculated as Line Item Quantity x Item Unit Price = Extended Unit Price
Numeric value of quantity
This should match the Item Invoiced Quantity for the item in the matching IT1 segment
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- BG
- Bag
- BX
- Box
- CA
- Case
- CT
- Carton
- DA
- Days
- DZ
- Dozen
- EA
- Each
- FT
- Foot
- HR
- Hours
- HU
- Hundred
- LB
- Pound
- LO
- Lot
- MO
- Months
- PD
- Pad
- PF
- Pallet (Lift)
- PK
- Package
- Q1
- Quarter (Time)
- RL
- Roll
- RM
- Ream
- ST
- Set
- SY
- Square Yard
- TH
- Thousand
- YR
- Years
Product/Item Description
To describe a product or process in coded or free-form format
Sample EDI:
PIDF***ITEM DESCRIPTION~
Code indicating the format of a description
- If PID01 equals "F", then PID05 is used. If PID01 equals "S", then PID04 is used. If PID01 equals "X", then both PID04 and PID05 are used.
- F
- Free-form
Name
To identify a party by type of organization, name, and code
Ship To Location information must match line item Ship To Location information from the Purchase Order or Purchase Order Change.
Sample EDI:
N1STMEMPHIS DISTRIBUTION CENTER9210107048~
Code identifying an organizational entity, a physical location, property or an individual
- ST
- Ship To
Code designating the system/method of code structure used for Identification Code (67)
- 92
- Assigned by Buyer or Buyer's Agent
Code identifying a party or other 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.
Distribution List
To specify identifying information
Sample EDI:
REFKA1~
Code qualifying the Reference Identification
- KA
- Distribution List
Qualifies a list of addresses to which the distribution of something should be made
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Distribution Number is sent with the PO Line Item and is required for return on the EDI 810 Invoice. Default Distribution Number cannot be null.
Shipper's Identifying Number for Shipment (SID)
To specify identifying information
Sample EDI:
REFSI1~
Code qualifying the Reference Identification
- SI
- Shipper's Identifying Number for Shipment (SID)
A unique number (to the shipper) assigned by the shipper to identify the shipment
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Shipment Number is sent with the PO Line Item and is required for return on the EDI 810 Invoice. Default Shipment Number cannot be null.
Summary
Total Monetary Value Summary
To specify the total invoice discounts and amounts
Sample EDI:
TDS*42400~
Carrier Detail
To specify transportation details for the transaction
Sample EDI:
CAD***ABCDfree-form notes~
Service, Promotion, Allowance, or Charge Information
To request or identify a service, promotion, allowance, or charge; to specify the amount or percentage for the service, promotion, allowance, or charge
Sample EDI:
SACCD240***12300~
Code which indicates an allowance or charge for the service specified
- If SAC01 is "A" or "C", then at least one of SAC05, SAC07, or SAC08 is required.
- A
- Allowance
- C
- Charge
Code identifying the service, promotion, allowance, or charge
- D240
- Freight
- H850
- Tax
Transaction Totals
To transmit a hash total for a specific element in the transaction set
- 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.
Sample EDI:
CTT*1~
Transaction Set Trailer
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
Total number of segments included in a transaction set including ST and SE segments
Functional Group Trailer
To indicate the end of a functional group and to provide control information
Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element
Interchange Control Trailer
To define the end of an interchange of zero or more functional groups and interchange-related control segments
Sample
GS*IN*SENDERGS*RECEIVERGS*20231120*040730*000000001*X*004010~
ST*810*0001~
BIG*20070606*9999999999*20070410*9999999*0*0~
CUR*BY*USD~
REF*ZZ*Handset Device Accessory~
REF*ZA*99999999~
PER*SU*FirstName LastName~
N1*RI*REMIT TO*92*9999999~
N1*ST*SHIP TO*92*9999999~
N1*VN*VENDOR NAME~
ITD*01*3****20070705*30*****Up to 02/08/2007 without deduction~
DTM*011*20070530~
FOB*PC~
IT1*000003*1*EA*772**SK*RTL.12345~
CTP**EST*42400*100*EA~
PID*F****ITEM DESCRIPTION~
N1*ST*MEMPHIS DISTRIBUTION CENTER*92*10107048~
REF*KA*1~
REF*SI*1~
TDS*42400~
CAD****ABCD*free-form notes~
SAC*C*D240***12300~
CTT*1~
SE*23*0001~
GE*1*000000001~
IEA*1*000000001~
Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on this page are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.