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
- ^ 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
- 00403
- Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1999
A control number assigned by the interchange sender
Code indicating sender's request for an interchange acknowledgment
- 0
- No Acknowledgment Requested
- 1
- Interchange Acknowledgment Requested
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
- 004030
- Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1999
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.
Invoice Date
Identifying number assigned by issuer
Invoice Number
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
Identifying number for Purchase Order assigned by the orderer/purchaser
Purchase Order Number
Note/Special Instruction
To transmit information in a free-form format, if necessary, for comment or special instruction
A free-form description to clarify the related data elements and their content
Currency
To specify the currency (dollars, pounds, francs, etc.) used in a transaction
Internal Vendor Number
To specify identifying information
Code qualifying the Reference Identification
- IA
- Internal Vendor Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Vendor Number
Shipper's Identifying Number for Shipment (SID)
To specify identifying information
Code qualifying the Reference Identification
- SI
- Shipper's Identifying Number for Shipment (SID)
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Packing List Number
Only the Ship To repetition is required.
Name
To identify a party by type of organization, name, and code
Only the Ship To repetition is required.
Code identifying an organizational entity, a physical location, property or an individual
- ST
- Ship 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.
When N101=ST, N104 is required (Ship to DC location Code)
Address Information
To specify the location of the named party
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)
Name
To identify a party by type of organization, name, and code
Only the Ship To repetition is required.
Code identifying an organizational entity, a physical location, property or an individual
- VN
- Vendor
Code designating the system/method of code structure used for Identification Code (67)
When N101=VN, N103 is not used
- 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.
When N101=VN, N104 is not used
Address Information
To specify the location of the named party
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)
Detail
Baseline Item Data (Invoice)
To specify the basic and most frequently used line item data for the invoice and related transactions
At least one of IN,SK or UP is required back
Alphanumeric characters assigned for differentiation within a transaction set
- IT101 is the line item identification.
Number of units invoiced (supplier units)
Qty of units invoiced (EA)
Qty of Prepacks invoiced (AS)
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- AS
- Assortment
- EA
- Each
Price per unit of product, service, commodity, etc.
Unit Price (as provided on the 850).
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.
- IN
- Buyer's Item Number
Long SKU
- SK
- Stock Keeping Unit (SKU)
Short SKU
- UP
- UCC - 12
Identifying number for a product or service
- URBN Internal SKU # (LongSKU) - IN
- URBN Internal SKU # (ShortSKU) - SK
- URNN UPC - UP
One of these three other must be provided.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- VA
- Vendor's Style Number
Identifying number for a product or service
Vendor Style
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- IN
- Buyer's Item Number
Long SKU.
- SK
- Stock Keeping Unit (SKU)
Short SKU.
- UP
- UCC - 12
Identifying number for a product or service
- URBN Internal SKU # (ShortSKU) - SK
- URBN Internal SKU # (LongSKU) - IN
- URBN UPC - UP
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- IN
- Buyer's Item Number
- SK
- Stock Keeping Unit (SKU)
- UP
- UCC - 12
Identifying number for a product or service
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
A free-form description to clarify the related data elements and their content
Product Description (PID02=08).
Item Physical Details
To specify the physical qualities, packaging, weights, and dimensions relating to the item
Numeric value of gross weight per pack
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- KG
- Kilogram
- LB
- Pound
Numeric value of gross volume per pack
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- CF
- Cubic Feet
- CR
- Cubic Meter
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
- 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.
A free-form description to clarify the related data elements and their content
Summary
Total Monetary Value Summary
To specify the total invoice discounts and amounts
Urban requires the inclusion of Qty Per pack (PO401) when calculating INVOICE TOTALS.
Calculation: SUM of (IT102 * IT104) * PO401 (from 850)
Example:
Line 1
IT102 = 150PPKs (AS)
IT104 = $10.5
PO401 =7
$11,025.00
Line 2
IT102 = 100Eaches (EA)
IT104 = $10.5
PO401 =1
$1,050.00
Line 3
IT102 = 50Eaches (EA)
IT104 = $11
PO401 =1
$550
TDS01 = $12,625.00( subtract allowances or add any discounts as applicable)
TDS02 = $12,625.00
Monetary amount
- TDS01 is the total amount of invoice (including charges, less allowances) before terms discount (if discount is applicable).
The Total Amount of Invoice[including (+) charges, less (-) allowances]
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 Amount / Total(does not include allowances/charges.
Carrier Detail
To specify transportation details for the transaction
Standard Carrier Alpha Code
SCAC.
Free-form description of the routing or requested routing for shipment, or the originating carrier's identity
Routing information
Code qualifying the Reference Identification
- 2I
- Tracking Number
- BM
- Bill of Lading Number
- CN
- Carrier's Reference Number (PRO/Invoice)
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Carrier Pro (CN), Bill of Lading (BM) or Tracking # (2I).
The SAC loop at the summary is used for conveying Canadian taxes, GST (Federal), PST (Provincial) or HST (Harmonized).
- When communicating the HST tax, only one SAC should be sent
- When communicating the GST and PST tax, only two taxes should be sent. One for the GST and one for the PST.
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.
- C
- Charge
Code identifying the service, promotion, allowance, or charge
- D360
- Goods and Services Tax Charge
Used for including a GST or HST tax. SAC 15 will identify if the tax is GST or HST
- H770
- Tax - State Tax
Used for including a PST/QST 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.
A free-form description to clarify the related data elements and their content
- When SAC02 is D360 and the SAC is being used to send a Federal Goods and Service tax (GST) - SAC 15 must be populated with GST.
- When SAC02 is D360 and the SAC is being used to send a Harmonized Tax (HST) - SAC 15 must be populated with HST.
- When SAC02 is H770 and the SAC is being used to send a Provincial/Quebec tax (PST) - SAC 15 must be populated with PST.
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
Total Eaches (EA) or Total Prepacks (CA).
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- CA
- Case
- EA
- Each
Numeric value of weight
Total Gross Weight
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- KG
- Kilogram
- LB
- Pound
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.
Total number of line items in the transaction set
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.