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
- None included
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
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Beginning Segment for Invoice
To indicate the beginning of an invoice transaction set and transmit identifying numbers and dates
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.
Date expressed as CCYYMMDD
- BIG01 is the invoice issue date.
Invoice Issue Date
Identifying number assigned by issuer
Vendor's assigned invoice number
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 for purchase order assigned by Medline
Number identifying a release against a Purchase Order previously placed by the parties involved in the transaction
Number assigned by the orderer identifying a specific change or revision to a previously transmitted transaction set
Code specifying the type of transaction
- BIG07 is used only to further define the type of invoice when needed.
- CN
- Credit Invoice
- DI
- Debit Invoice
Code identifying purpose of transaction set
Identifying number assigned by issuer
- BIG10 indicates the consolidated invoice number. When BIG07 contains code CI, BIG10 is not used.
Currency
To specify the currency (dollars, pounds, francs, etc.) used in a transaction
1 If CUR08 is present, then CUR07 is required.
2 If CUR09 is present, then CUR07 is required.
3 If CUR10 is present, then at least one of CUR11 or CUR12 is required.
4 If CUR11 is present, then CUR10 is required.
5 If CUR12 is present, then CUR10 is required.
6 If CUR13 is present, then at least one of CUR14 or CUR15 is required.
7 If CUR14 is present, then CUR13 is required.
8 If CUR15 is present, then CUR13 is required.
9 If CUR16 is present, then at least one of CUR17 or CUR18 is required.
10 If CUR17 is present, then CUR16 is required.
11 If CUR18 is present, then CUR16 is required.
12 If CUR19 is present, then at least one of CUR20 or CUR21 is required.
13 If CUR20 is present, then CUR19 is required.
14 If CUR21 is present, then CUR19 is required.
Code identifying an organizational entity, a physical location, property or an individual
- VN
- Vendor
Code (Standard ISO) for country in whose currency the charges are specified
Value to be used as a multiplier conversion factor to convert monetary value from one currency to another
Code identifying an organizational entity, a physical location, property or an individual
Code (Standard ISO) for country in whose currency the charges are specified
Code identifying the market upon which the currency exchange rate is based
Code specifying type of date or time, or both date and time
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)
Code specifying type of date or time, or both date and time
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)
Code specifying type of date or time, or both date and time
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)
Code specifying type of date or time, or both date and time
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)
Code specifying type of date or time, or both date and time
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)
Name
To identify a party by type of organization, name, and code
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 N10
3 Any of the below segments are expected in EDI 810 file.
N1_01 and N1_02 are required and it would be great if N1_03 and N1_04
are sent in 810 file.
N1VN Vendor
N1SF Ship From
N1*RE Remit to (Party to receive invoice remittance)
Code identifying an organizational entity, a physical location, property or an individual
- RE
- Party to receive commercial invoice remittance
- SF
- Ship From
- ST
- Ship To
- VN
- Vendor
Code designating the system/method of code structure used for Identification Code (67)
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.
Code describing entity relationship
- N105 and N106 further define the type of entity in N101.
Code identifying an organizational entity, a physical location, property or an individual
Geographic Location
To specify the geographic place of the named party
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.
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)
Date/Time Reference
To specify pertinent dates and times
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.
Code specifying type of date or time, or both date and time
- 011
- Shipped
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)
Code identifying the time. In accordance with International Standards Organization standard 8601, time can be specified by a + or - and an indication in hours in relation to Universal Time Coordinate (UTC) time; since + is a restricted character, + and - are substituted by P and M in the codes that follow
Code indicating the date format, time format, or date and time format
Expression of a date, a time, or range of dates, times or dates and times
Detail
Baseline Item Data (Invoice)
To specify the basic and most frequently used line item data for the invoice and related transactions
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.
4 If either IT110 or IT111 is present, then the other is required.
5 If either IT112 or IT113 is present, then the other is required.
6 If either IT114 or IT115 is present, then the other is required.
7 If either IT116 or IT117 is present, then the other is required.
8 If either IT118 or IT119 is present, then the other is required.
9 If either IT120 or IT121 is present, then the other is required.
10 If either IT122 or IT123 is present, then the other is required.
11 If either IT124 or IT125 is present, then the other is required.
Semantic Notes: 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.
Alphanumeric characters assigned for differentiation within a transaction set
- IT101 is the purchase order line item identification.
Identifies the PO line number sent by Medline in purchase order (IT101 must
match exactly with PO101) Example shown below –
Data in PO - PO1^00010^43^CA^153.04^^VC^12345^IN^67890~
Data in Invoice - IT10001043CA153.04*VC12345IN67890~
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
Price per unit of product, service, commodity, etc.
Code identifying the type of unit price for an item
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.
- VC
- Vendor's (Seller's) Catalog Number
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- IN
- Buyer's Item Number
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- UK
- U.P.C./EAN Shipping Container Code (1-2-5-5-1)
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
Identifying number for a product or service
Summary
Total Monetary Value Summary
To specify the total invoice discounts and amounts
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.
Monetary amount
- TDS01 is the total amount of invoice (including charges, less allowances) before terms discount (if discount is applicable).
Monetary amount
- TDS02 indicates the amount upon which the terms discount amount is calculated.
- TDS02 is required if the dollar value subject to discount is not equal to the dollar value of TDS01.
Monetary amount
- TDS03 is the amount of invoice due if paid by terms discount due date (total invoice or installment amount less cash discount).
Monetary amount
- TDS04 indicates the total amount of terms discount.
Tax Information
To specify tax information
1 At least one of TXI02 TXI03 or TXI06 is required.
2 If either TXI04 or TXI05 is present, then the other is required.
3 If TXI08 is present, then TXI03 is required.
Semantic Notes: 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.
Carrier Detail
To specify transportation details for the transaction
1 At least one of CAD05 or CAD04 is required.
2 If CAD07 is present, then CAD08 is required.
Code specifying the method or type of transportation for the shipment
Prefix or alphabetic part of an equipment unit's identifying number
Sequencing or serial part of an equipment unit's identifying number (pure numeric form for equipment number is preferred)
Free-form description of the routing or requested routing for shipment, or the originating carrier's identity
Code indicating the status of an order or shipment or the disposition of any difference between the quantity ordered and the quantity shipped for a line item or transaction
Code qualifying the Reference Identification
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Code indicating the level of transportation service or the billing service offered by the transportation carrier
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
1 At least one of SAC02 or SAC03 is required.
2 If either SAC03 or SAC04 is present, then the other is required.
3 If either SAC06 or SAC07 is present, then the other is required.
4 If either SAC09 or SAC10 is present, then the other is required.
5 If SAC11 is present, then SAC10 is required.
6 If SAC13 is present, then at least one of SAC02 or SAC04 is required.
7 If SAC14 is present, then SAC13 is required.
8 If SAC16 is present, then SAC15 is required.
Semantic Notes: 1 If SAC01 is "A" or "C", then at least one of SAC05, SAC07, or SAC08 is required.
2 SAC05 is the total amount for the service, promotion, allowance, or charge. If
SAC05 is present with SAC07 or SAC08, then SAC05 takes precedence.
3 SAC08 is the allowance or charge rate per unit.
4 SAC10 and SAC11 is the quantity basis when the allowance or charge quantity
is different from the purchase order or invoice quantity.
SAC10 and SAC11 used together indicate a quantity range, which could be a
dollar amount, that is applicable to service, promotion, allowance, or charge.
5 SAC13 is used in conjunction with SAC02 or SAC04 to provide a specific reference
number as identified by the code used.
6 SAC14 is used in conjunction with SAC13 to identify an option when there is
more than one option of the promotion.
7 SAC16 is used to identify the language being used in SAC15.
Comments: 1 SAC04 may be used to uniquely identify the service, promotion, allowance, or charge.
In addition, it may be used in conjunction to further the code in SAC02.
2 In some business applications, it is necessary to advise the trading partner of the actual
dollar amount that a particular allowance, charge, or promotion was based on to
reduce ambiguity. This amount is commonly referred to as "Dollar Basis Amount". It
is represented in the SAC segment in SAC10 using the qualifier "DO" - Dollars in
SAC09.
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.
Required by Medline if freight charges apply
- A
- Allowance
- C
- Charge
Code identifying the service, promotion, allowance, or charge
Required by Medline if freight charges apply
- D240
- Freight
- G830
- Shipping and Handling
- H750
- Tax - Sales Tax (State and Local)
- H850
- Tax
- H940
- Terminal Charge
Code identifying the agency assigning the code values
Agency maintained code identifying the service, promotion, allowance, or charge
- SAC04 may be used to uniquely identify the service, promotion, allowance, or charge. In addition, it may be used in conjunction to further the code in SAC02.
Monetary amount
- SAC05 is the total amount for the service, promotion, allowance, or charge.
- If SAC05 is present with SAC07 or SAC08, then SAC05 takes precedence.
Amount of charge or allowance - Required by Medline if freight charges apply
Code indicating on what basis allowance or charge percent is calculated
Rate expressed in the standard monetary denomination for the currency specified
- SAC08 is the allowance or charge rate per unit.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
Numeric value of quantity
- SAC10 and SAC11 is the quantity basis when the allowance or charge quantity is different from the purchase order or invoice quantity.
- SAC10 and SAC11 used together indicate a quantity range, which could be a dollar amount, that is applicable to service, promotion, allowance, or charge.
- In some business applications, it is necessary to advise the trading partner of the actual dollar amount that a particular allowance, charge, or promotion was based on to reduce ambiguity. This amount is commonly referred to as "Dollar Basis Amount". It is represented in the SAC segment in SAC10 using the qualifier "DO" - Dollars in SAC09.
Code indicating method of handling for an allowance or charge
- 02
- Off Invoice
- 06
- Charge to be Paid by Customer
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
- SAC13 is used in conjunction with SAC02 or SAC04 to provide a specific reference number as identified by the code used.
A unique number identifying available promotion or allowance options when more than one is offered
- SAC14 is used in conjunction with SAC13 to identify an option when there is more than one option of the promotion.
A free-form description to clarify the related data elements and their content
Code designating the language used in text, from a standard code list maintained by the International Standards Organization (ISO 639)
- SAC16 is used to identify the language being used in SAC15.
Invoice Shipment Summary
To specify summary details of total items shipped in terms of quantity, weight, and volume
1 At least one of ISS01 ISS03 or ISS05 is required.
2 If either ISS01 or ISS02 is present, then the other is required.
3 If either ISS03 or ISS04 is present, then the other is required.
4 If either ISS05 or ISS06 is present, then the other is required.
Semantic Notes: 1 ISS07 is the quantity of third party pallets.
2 ISS08 is the gross weight of third party pallets in pounds.
Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
Numeric value of weight
Total invoices shipment weight
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
Numeric value of quantity
- ISS07 is the quantity of third party pallets.
Numeric value of weight
- ISS08 is the gross weight of third party pallets in pounds.
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.
1 If either CTT03 or CTT04 is present, then the other is required.
2 If either CTT05 or CTT06 is present, then the other is required.
Semantic Notes:
Comments: 1 This segment is intended to provide hash totals to validate transaction completeness
and correctness.
Total number of line items in the transaction set
Sum of values of the specified data element. All values in the data element will be summed without regard to decimal points (explicit or implicit) or signs. Truncation will occur on the left most digits if the sum is greater than the maximum size of the hash total of the data element.
-.0018 First occurrence of value being hashed.
.18 Second occurrence of value being hashed.
1.8 Third occurrence of value being hashed.
18.01 Fourth occurrence of value being hashed.
1855 Hash total prior to truncation.
855 Hash total after truncation to three-digit field.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
A free-form description to clarify the related data elements and their content
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
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
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
Assigned number originated and maintained by the sender
Interchange Control Trailer
To define the end of an interchange of zero or more functional groups and interchange-related control segments
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.