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
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
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
- BIG01 is the invoice issue date.
Identifying number assigned by issuer
If invoice number contains more than 16 characters, only 16 characters will be accepted, starting from right most character.
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.
Identifying number for Purchase Order assigned by the orderer/purchaser
If invoice contains a single purchase order, this value is MANDATORY. If invoice contains multiple purchase orders, please see IT1 segment for information on sending multiple purchase order numbers. The BIG04 element is not used for sending purchase order numbers for an invoice containing multiple purchase orders.
Code specifying the type of transaction
- BIG07 is used only to further define the type of invoice when needed.
This value is used to define the type of invoice. Acceptable values for invoices against a valid ConAgra purchase order are:
DR = Debit Invoice
CR = Credit Invoice
DS = Subsequent Debit (Subsequent debit invoice is to be used for invoicing unplanned freight charges for a previously invoiced purchase order. This is not to be used for sending multiple invoices against a line of a purchase order.)
CS = Subsequent Credit (Subsequent credit invoice is to be used for crediting unplanned freight charges for a previously invoiced purchase order. This is not to be used for sending multiple invoices against a line of a purchase order.)
(These values may also be used by a vendor ConAgra has approved for non-PO invoice processing.)
- CR
- Credit Memo
- CS
- Cash Surrender Distribution
- DR
- Debit Memo
- DS
- Disposition
Currency
To specify the currency (dollars, pounds, francs, etc.) used in a transaction
Code identifying an organizational entity, a physical location, property or an individual
- BY
- Buying Party (Purchaser)
Code (Standard ISO) for country in whose currency the charges are specified
"USD" for US Dollars.
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
ConAgra Foods buyer contact for invoice. Providing this data will help with invoice issue resolution. If both the PER segment and the purchase order number are missing, the invoice will be rejected with an 824 notification.
The PER segment is MANDATORY for a vendor ConAgra Foods has approved for non-PO invoice processing
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
- BT
- Bill-to-Party
- 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.
Both the BT and VN qualifiers with the associated bill to and vendor numbers provided by ConAgra Foods on the purchase order are required back on the invoice.
The ConAgra Foods BT value in the N1_04 should be 208595574. The VN values for the vendor will be provided by ConAgra.
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 line item identification.
MANDATORY for all invoices (DR, CR, DS and CS) containing a purchase order. The line item number must match the line item number on the ConAgra purchase order. For a Subsequent Debit (DS) and Subsequent Credit (CS) invoice, the IT101 is the only element to be sent in the IT1 segment
Number of units invoiced (supplier units)
MANDATORY for DR and CR invoice types. Do not send for DS and CS
invoice types.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
MANDATORY for DR and CR invoice types. The value must match the purchase order. DO NOT send for DS and CS invoice types.
All valid standard codes are used
- BA
- Bale
- CA
- Case
- EA
- Each
- GA
- Gallon
- KG
- Kilogram
- LB
- Pound
- SM
- Square Meter
Price per unit of product, service, commodity, etc.
MANDATORY for DR and CR invoice types. Do not send for DS and CS
invoice types.
Code identifying the type of unit price for an item
MANDATORY for DR and CR invoice types. The value must match the
purchase order. DO NOT send for DS and CS invoice types.
The Basis of Unit Price Code sent on the order in the PO1_05 or the PO3_05 is required back on DR and CR invoice types. As an example, when pricing is per 100, the IT1_05 should contain HP. When pricing is per 1 of the unit of measure, the IT1_05 should contain UM.
Additional codes will be added as needed.
- HP
- Price per Hundred
- HT
- Price Per 100,000
- PN
- Price per Ten
- TP
- Price per Thousand
- TT
- Price Per 10,000
- UM
- Price per Unit of Measure
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.
DO NOT send for DS and CS invoice types
- BP
- Buyer's Part Number
Identifying number for a product or service
DO NOT send for DS and CS invoice types.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
DO NOT send for DS and CS invoice types.
- VP
- Vendor's (Seller's) Part Number
Identifying number for a product or service
DO NOT send for DS and CS invoice types.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
DO NOT send for DS and CS invoice types.
- MG
- Manufacturer's Part Number
Identifying number for a product or service
DO NOT send for DS and CS invoice types.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- PO
- Purchase Order Number
Identifying number for a product or service
MANDATORY for invoice containing multiple purchase orders
Tax Information
To specify tax information
To be used for taxes other than State and Local Tax. Please see Summary TXI segment for State and Local Tax.
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
To be used for Charges other than Freight, Storage and Accessorial related charges. Please see Summary SAC segment for Freight, Storage and Accessorial related charges.
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.
- C
- Charge
Code identifying the service, promotion, allowance, or charge
- F050
- Other (See related description)
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.
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).
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
This segment may be used for DR and CR invoice types and is MANDATORY for Subsequent Debit (DS) and Subsequent Credit (CS) invoice types. Segment may only be used once.
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.
- C
- Charge
Code identifying the service, promotion, allowance, or charge
- D240
- Freight
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
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.