X12 810 Invoice
This X12 Transaction Set 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
- ^ Repetition
- None included
Interchange Control Header
To start and identify an interchange of zero or more functional groups and interchange-related control segments
Code identifying 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 identifying 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)
Code indicating 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
Code indicating 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
Type is not applicable; the repetition separator is a delimiter and not a data element; this field provides the delimiter used to separate repeated occurrences of a simple data element or a composite data structure; this value must be different than the data element separator, component element separator, and the segment terminator
- ^
- Repetition Separator
Code specifying the version number of the interchange control segments
- 00501
- Standards Approved for Publication by ASC X12 Procedures Review Board through October 2003
A control number assigned by the interchange sender
Code indicating sender's request for an interchange acknowledgment
- 0
- No Interchange Acknowledgment Requested
- 1
- Interchange Acknowledgment Requested (TA1)
Code indicating 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)
Code identifying party sending transmission; codes agreed to by trading partners
Code identifying party receiving transmission; codes agreed to by trading partners
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
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 identifying the issuer of the standard; this code is used in conjunction with Data Element 480
- 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
- 005010
- Standards Approved for Publication by ASC X12 Procedures Review Board through October 2003
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) is 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 where CC represents the first two digits of the calendar year
- BIG01 is the invoice issue date.
Invoice Date
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
- BIG03 is the date assigned by the purchaser to purchase order.
Purchase Order Date
Reference Information
To specify identifying information
One iteration of the REF segment is required for the Chewy.com internal vendor ID (REF01=IA).
Either a Carrier Pro Number or Bill of Lading number is expected if available.
Code qualifying the Reference Identification
- 2I
- Tracking Number
- 12
- Billing Account
Vendor assigned account number for Chewy.com
- BM
- Bill of Lading Number
- CN
- Carrier's Reference Number (PRO/Invoice)
- IA
- Internal Vendor Number
Mandatory
- VN
- Vendor Order Number
One iteration of the N1 loop is required for the Ship To (N101=ST) name and address information.
Party Identification
To identify a party by type of organization, name, and code
Code identifying an organizational entity, a physical location, property or an individual
- RI
- Remit To
- ST
- Ship To
Code designating the system/method of code structure used for Identification Code (67)
Not used when N101 = RI.
- 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.
Additional Name Information
To specify additional names
Party Location
To specify the location of the named party
At least one iteration of the N3 segment is required.
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 where CC represents the first two digits of the calendar year
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 where CC represents the first two digits of the calendar year
Number of days until total invoice amount is due (discount not applicable)
Date/Time Reference
To specify pertinent dates and times
F.O.B. Related Instructions
To specify transportation instructions relating to shipment
Code identifying payment terms for transportation charges
- FOB01 indicates which party will pay the carrier.
- CC
- Collect
- DF
- Defined by Buyer and Seller
- PP
- Prepaid (by Seller)
Code identifying type of location
- FOB02 is the code specifying transportation responsibility location.
- DE
- Destination (Shipping)
- OR
- Origin (Shipping Point)
Extended Reference Information
To transmit identifying information as specified by the Reference Identification Qualifier
Code qualifying the Reference Identification
- L1
- Letters or Notes
Message Text
To provide a free-form format that allows the transmission of text information
If N902 = GEN - MSG01 is a General Note
Detail
Baseline Item Data (Invoice)
To specify the basic and most frequently used line item data for the invoice and related transactions
The Vendor Item # (VN) is required. However, all item identifiers are recommended.
Alphanumeric characters assigned for differentiation within a transaction set
- IT101 is the 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
- BA
- Bale
- BG
- Bag
- CA
- Case
- EA
- Each
- PH
- Pack (PAK)
Price per unit of product, service, commodity, etc.
This is the gross purchase price of 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.
- VA
- Vendor's Style Number
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- SK
- Stock Keeping Unit (SKU)
Chewy.com assigned item number
- UK
- GTIN 14-digit Data Structure
- UP
- UCC - 12
Identifying number for a product or service
Sending the Chewy.com SKU number is highly recommended.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- SK
- Stock Keeping Unit (SKU)
Sending the Chewy.com SKU number is highly recommended.
- UK
- GTIN 14-digit Data Structure
- UP
- UCC - 12
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- SK
- Stock Keeping Unit (SKU)
Sending the Chewy.com SKU number is highly recommended.
- UK
- GTIN 14-digit Data Structure
- UP
- UCC - 12
One iteration of the PID for the Product Description (PID05, when PID01=F and PID02=08) is required. TheProduct Description (PID05, when PID01=F and PID02=08) can repeat (up to 4 iterations) if needed.
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
Code identifying the general class of a product or process characteristic
- 08
- Product
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 Invoice Amount (including charges, less allowances, plus taxes) beforeterms 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.
Merchandise Total (does not includes charges/allowances/taxes) total upon which terms discount amount is calculated
Monetary amount
- TDS03 is the amount of invoice due if paid by terms discount due date (total invoice or installment amount less cash discount).
Invoice amount due if paid by terms discount due date - TDS01 less cash discount
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
- B720
- Cooperative Advertising/Merchandising Allowance (Performance)
Utilize this code for any customer satisfaction allowances
- C000
- Defective Allowance
- D240
- Freight
- D260
- Fuel Charge
- F050
- Other (See related description)
- F800
- Promotional Allowance
A description is required noting the kind of promotion program being applied.
- F970
- Rebate
A description is required noting the kind of rebate program being applied.
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.
Code indicating on what basis allowance or charge percent is calculated
Percent given in decimal format (e.g., 0.0 through 100.0 represents 0% through 100%)
2 decimal positions allowed.
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 CTT02 is the hash total of the 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
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.