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
Date expressed as CCYYMMDD
- BIG01 is the invoice issue date.
Invoice Issue Date
Date expressed as CCYYMMDD
- BIG03 is the date assigned by the purchaser to purchase order.
Purchase Order date from original order.
Identifying number for Purchase Order assigned by the orderer/purchaser
Purchase Order number from 850 order received.
Number identifying a release against a Purchase Order previously placed by the parties involved in the transaction
Note/Special Instruction
To transmit information in a free-form format, if necessary, for comment or special instruction
Reference Identification
To specify identifying information
REF Segment with “VR” in REF01 from the 850 Purchase Order is required to be returned in documents to Motor State Distributing.
Code qualifying the Reference Identification
- VR
- Vendor ID Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Name
To identify a party by type of organization, name, and code
Vendor N1 segment is optional.
Code identifying an organizational entity, a physical location, property or an individual
- BT
- Bill-to-Party
- RE
- Party to receive commercial invoice remittance
- ST
- Ship To
- 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.
Address Information
To specify the location of the named party
Geographic Location
To specify the geographic place of the named party
Free-form text for city name
- A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
Code (Standard State/Province) as defined by appropriate government agency
- N402 is required only if city name (N401) is in the U.S. or Canada.
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
Terms of Sale/Deferred Terms of Sale
To specify terms of sale
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)
Detail
Baseline Item Data (Invoice)
To specify the basic and most frequently used line item data for the invoice and related transactions
Alphanumeric characters assigned for differentiation within a transaction set
- IT101 is the purchase order line item identification.
The value in PO101 element from the 850 Purchase Order is required in IT101 element.
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
- BX
- Box
- CS
- Case
- EA
- Each
- FT
- Foot
- GA
- Gallon
- HR
- Hour
- IN
- Inch
- PR
- Pair
- QT
- Quart
Price per unit of product, service, commodity, etc.
Code identifying the type of unit price for an item
- PE
- Price per Each
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.
- BP
- Buyer's Part Number
Identifying number for a product or service
Buyer Part Number requested to be sent in returning documents if received in 850 Purchase Order.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- VP
- Vendor's (Seller's) Part Number
Identifying number for a product or service
Vendor Part Number required to be sent in returning documents if received in 850 Purchase Order.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Product/Item Description
To describe a product or process in coded or free-form format
Code indicating the format of a description
- If PID01 equals "F", then PID05 is used. If PID01 equals "S", then PID04 is used. If PID01 equals "X", then both PID04 and PID05 are used.
- F
- Free-form
Summary
Total Monetary Value Summary
To specify the total invoice discounts and amounts
For all data elements within this segment, the decimal point is assumed and should not be included in the amount.
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
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
- B210
- Co-op Credit
- B310
- Commission Amount
- B610
- Container Service Charge USA and Canada
- B750
- Core Charge
- C030
- Delivery Surcharge (Drop Ship)
- C350
- Promo Discount/Allowance
- D240
- Freight
- D270
- Fuel Surcharge
- D360
- Goods and Services Tax Charge (GST)
- D500
- Handling
- D890
- Installation and Warranty
- G360
- Repair Charges
- G970
- Minimum Order Charge
- H220
- Specification Review
- H750
- Sales Tax (State and Local)
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.
This segment is intended to provide hash totals to validate transaction completeness and correctness.
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
Invoice for a Drop Ship Order
GS*IN*SENDERGS*RECEIVERGS*20240427*181146*000000001*X*004010~
ST*810*0002~
BIG*20140530*InvoiceNum*20140528*PONumber***DI~
REF*VR*Vendor ID~
N1*ST*Drop Ship Name~
N3*1234 Drop Ship Address*Drop Ship Address2~
N4*Drop Ship City*ZZ*12345~
N1*BT*Motor State Distributing~
N3*8300 Lane Drive~
N4*Watervliet*MI*49098~
ITD*01*3*0*20140609*10*20140630~
IT1*1*1*EA*69.25**BP*Lane Prod ID*VP*Vendor Prod ID*UP*696969696969~
PID*F****Product Description~
TDS*5925~
SAC*C*C350***10~
CTT*1~
SE*16*0002~
GE*1*000000001~
IEA*1*000000001~
Invoice for a Stock Order
GS*IN*SENDERGS*RECEIVERGS*20240427*180906*000000001*X*004010~
ST*810*0001~
BIG*20140530*InvoiceNum*20140528*PONumber***DI~
NTE**This note affects the entire invoice if utilized in translation!~
REF*VR*VendorID~
N1*ST*Motor State Distributing*92*MAIN~
N3*8300 Lane Drive~
N4*Watervliet*MI*49098~
N1*BT*Motor State Distributing~
N3*8300 Lane Drive~
N4*Watervliet*MI*49098~
ITD*01*3*2*20140609*10*20140630**1600~
IT1*1*40*EA*10.00*PE*BP*Lane Product ID*VP*Vendor Product ID*UP*999999999999~
PID*F****Product Description~
IT1*2*200*BX*1.00*PE*BP*Motor State Part 1*VP*Vendor Part 1*UP*123456987321~
PID*F****This part number’s description~
IT1*3*2*EA*100.00*PE*BP*Allstar Part Number*VP*Vendor Part Number*UP*123456789123~
PID*F****Part description~
TDS*880~
SAC*C*D240***80~
CTT*3~
SE*21*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.