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.
Flxpoint uses "ZZ" for our Receiver ID Qualifier.
- ZZ
- Mutually Defined
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.
Flxpoint uses either "FLXPOINT" or "FLX#####" for our Receiver ID, where ##### is the AID of the client.
FLXPOINT
FLX12345
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
- 004010VICS
- Voluntary Inter-Industry Commerce Standards; The EDI Standards maintained and utilized by the retail industry.
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.
Future dates are not valid. Dates over 17 months old are not valid.
Date expressed as CCYYMMDD
- BIG03 is the date assigned by the purchaser to purchase order.
Department Number
To specify identifying information for DP
Code qualifying the Reference Identification for DP
- DP
- Department Number
Reference Identification
To specify identifying information for IA
Code qualifying the Reference Identification for IA
- IA
- Internal Vendor Number
Reference Identification
To specify identifying information for IV
Code qualifying the Reference Identification for IV
- IV
- Seller's Invoice Number
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
- 02
- End of Month (EOM)
- 05
- Discount Not Applicable
- 08
- Basic Discount Offered
- 12
- 10 Days After End of Month (10 EOM)
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
Percentage of merchandise cost discounted if invoice is paid before the terms discount due date (ITD04).
Date payment is due if discount is to be earned expressed in format CCYYMMDD
Date payment is due to qualify for a discount.
Number of days in the terms discount period by which payment is due if terms discount is earned
Number of days from the invoice date that the discounted invoice is due.
Date when total invoice amount becomes due expressed in format CCYYMMDD
Number of days until total invoice amount is due (discount not applicable)
Total amount of terms discount
Dollar amount of invoice merchandise cost discounted if invoice is paid on or before Terms Discount Due Date (ITD04).
Date/Time Reference
To specify pertinent 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
Alphanumeric characters assigned for differentiation within a transaction set
- IT101 is the purchase order line item identification.
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
- EA
- Each
Price per unit of product, service, commodity, etc
Price per unit
$15.95 would be sent as '15.95' $29.00 would be sent as '29'
Code identifying the type of unit price for an item
- LE
- Catalog Price per Each
- QT
- Quoted
- WE
- Wholesale 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
- EN
- European Article Number (EAN) (2-5-5-1)
- SK
- Stock Keeping Unit (SKU)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Summary
Total Monetary Value Summary
To specify the total invoice discounts and amounts
Monetary amount
- TDS01 is the total amount of invoice (including charges, less allowances) before terms discount (if discount is applicable).
Total amount of the invoice plus all charges minus all allowances.
Use implied decimals: $12 -> “1200”
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.
Total amount of invoice eligible for terms discount.
Use implied decimals: $12 -> “1200”
Carrier Detail
To specify transportation details for the transaction
Code specifying the method or type of transportation for the shipment
See 850 element TD512 for list of valid codes
- D3
- Delivery scheduled third day by cartage agent
- ND
- Next Day Air
- SC
- Second Day Air
- SI
- Standard Ground Hundred Weight
- SP
- SurePost
Standard Carrier Alpha Code
If not available, do not send the CAD segment.
See 850 element TD503 for list of valid codes
Code qualifying the Reference Identification
- BM
- Bill of Lading Number
- CN
- Carrier's Reference Number (PRO/Invoice)
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
- AFEE
- Fee
- C310
- Discount
- D240
- Freight
- G740
- Service Charge
- G821
- Shipping
- H750
- Tax - Sales Tax (State and Local)
Invoice Shipment Summary
To specify summary details of total items shipped in terms of quantity, weight, and volume
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
- EA
- Each
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.
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
Max Length 6
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
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.