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
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
EXAMPLE: BIG2000042512351199**1999999999
Identifying number assigned by issuer
This element contains a unique invoice number assigned by the party sending the document. The invoice number cannot be greater than 10 digits in length. Invoice numbers greater than 10 digits will be truncated from the left during the payment process.
Identifying number for Purchase Order assigned by the orderer/purchaser
This element contains The Home Depot purchase order number.
Returning an invalid purchase order number will result in a failure to process the message.
Name
To identify a party by type of organization, name, and code
Example: N1RICOMPANY 1239269035
The Home Depot will not make payment on invoices that lack this segment.
Suppliers are required to know their 'P' number or remit id in The Home Depot accounts payable system and must report that ID in this 'RI' qualified N1 loop at the N104 element.
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.
This element contains the suppliers 'P' number.
Terms of Sale/Deferred Terms of Sale
To specify terms of sale
EXAMPLE: ITD013*102130
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
- 09
- Proximo
Code identifying the beginning of the terms period
- 2
- Delivery Date
- 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
This element should only be populated if there is a discount available.
Number of days in the terms discount period by which payment is due if terms discount is earned
This element should only be populated if there is a discount available.
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
Example: IT1011EA263.94*VN000215
Alphanumeric characters assigned for differentiation within a transaction set
- IT101 is the purchase order line item identification.
This element contains The Home Depot's purchase order line number.
Returning an invalid line number will result in a failure to process the message.
Number of units invoiced (supplier units)
This element contains the number of units being invoiced for. The following rules apply to this element:
- The quantity contained here cannot be greater than the quantity that has been reported shipped.
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.
This element contains the unit cost (the amount being invoiced per unit) for the 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.
- VN
- Vendor's (Seller's) Item Number
This qualifier indicates that the IT107 contains the vendor SKU for the product.
Identifying number for a product or service
This element contains the vendor SKU for the product.
Date/Time Reference
To specify pertinent dates and times
EXAMPLE: DTM01120130715
Code specifying type of date or time, or both date and time
- 011
- Shipped
Date expressed as CCYYMMDD
This element contains the Ship date.
The Home Depot requires separate invoices when fulfillment is accomplished with separate shipments (i.e. shipments on different dates), so only one shipment date can be reported per 810.
Code specifying the method or type of transportation for the shipment
- ZZ
- Mutually defined
Free-form description of the routing or requested routing for shipment, or the originating carrier's identity
Contact CommerceHub for a complete list of codes. This element must contain a value from this list.
Code qualifying the Reference Identification
- CN
- Carrier's Reference Number (PRO/Invoice)
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
This should be the same tracking number that is sent in the MAN CP12345678 segment of the corresponding Shipment Confirmation
Summary
Total Monetary Value Summary
To specify the total invoice discounts and amounts
EXAMPLE: TDS*12575
Monetary amount
- TDS01 is the total amount of invoice (including charges, less allowances) before terms discount (if discount is applicable).
This element contains the total invoice 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
Examples:
SACCG830*525
SACA*B800325
SACCD500*525
SACCH850***525
Any difference between the TDS-01 amount and the extended merchandise
amount (i.e. Sum of IT1-02 * IT1-04 for all IT1 loops) must be accounted for in
the SAC segments that follow the TDS segment
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
For other available codes please refer to your retailer-specific addendum.
- B800
- Credit
This qualifier indicates that the SAC05 contains a credit allowance.
- D500
- Handling
This qualifier indicates that the SAC05 contains a handling charge.
- G830
- Shipping and Handling
Shipping charges should be zero.
All shipping charges should be prepaid with The Home Depot 'approved' shipping partners. No reimbursement will be made for shipping done through non-approved shippers.
- H850
- Tax
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.
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
Sample
BIG*20000425*12351199**1999999999
N1*RI*COMPANY 123*92*69035
ITD*01*3*10**21**30
IT1*01*1*EA*263.94**VN*000215
DTM*011*20130715
CAD*ZZ****FDEG**CN*024066930500171
TDS*12575
SAC*C*G830***525
SAC*A*B800***325
SAC*C*D500***525
SAC*C*H850***525
SE*11*0001
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.