X12 810 Invoice
This standard provides the format and establishes the data contents of an invoice transaction set. The invoice transaction set provides for customary and established business and industry practice relative to the billing for goods and services provided.
- ~ Segment
- * Element
- > Component
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.
Date sender generated a functional group of transaction sets.
Time (HHMM) when the sender generated a functional group of transaction sets (local time at sender's location).
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. Positions 1-3, version number; positions 4-6, release and subrelease level of version; positions 7-12, industry or trade association identifier (optionally assigned by user).
- 003010
- Draft Standards Approved By ASC X12 Through June 1990.
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 intended for use by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the invoice transaction set).
- 810
- X12.2 Invoice
Beginning Segment for Invoice
To indicate the beginning of an invoice transaction set and to transmit identifying numbers and dates.
Vendor INVOICE NUMBER is Shipment Number on ASN for non-dropship.
Examples:
Dropship BIG210215900597478501001301$5200103D$
Non-dropship BIG21032905Y72605399
Identifying number assigned by issuer.
- BIG07 is used only to further define the type of invoice when needed.
Date assigned by the purchaser to Purchase Order.
Identifying number for Purchase Order assigned by the orderer/purchaser.
Number identifying a release against a Purchase Order previously placed by the parties involved in the transaction.
Number assigned by the orderer identifying a specific change or revision to a previously transmitted transaction set.
Reference Numbers
To specify identifying numbers.
Example: REFBM0801165012$
Code qualifying the Reference Number.
- BM
- Bill of Lading Number
Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier.
- Either REF02 or REF03 is required.
Name
To identify a party by type of organization, name and code
This segment VN is MANDATORY with MMNA assigned vendor code.
Examples:
N1BTMMNA9299230$
N1STVICTORY MITSUBISHI92035189$
N1STEASTERN PDC OPERATION9299222$
N1VN DENSO PRODS & SVS AMERICAS INC9205V06$
Code identifying an organizational entity or a physical location.
- At least one of N102 or N103 must be present.
- BT
- Party to be Billed For Other Than Freight(Bill To)
- BY
- Buying Party (Purchaser)
- ST
- Ship To
- VN
- Vendor
Free-form name.
- If either N103 or N104 is present, then the other is required.
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.
- 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.
BT use 99230 Account Payable Dept Cd
ST use dealer code or PDC code
PDC codes:
99225 RS
99222 NJ
99223 AT
VN use MMNA assigned vendor code
Additional Name Information
To specify additional names or those longer than 35 characters in length
Examples:
N2ACCOUNT PAYABLE DEPT$FOUNTAIN MITSUBISHI$
N2
N2~EASTERN PDC OPERATION$
Address Information
To specify the location of the named party
Geographic Location
To specify the geographic place of the named party
Examples:
N4FRANKLINTN37067$SWEDESBORO
N4NJ08085$
Free-form text for city name.
- A combination of either N401 through N404 (or N405 and N406) may be adequate to specify a location.
- At least one of N401 or N405 must be present.
Code (Standard State/Province) defined by appropriate governmental agencies.
- N402 is required only if city name (N401) is in the USA or Canada.
- If N401 is present, then N402 is required.
Code defining international postal zone code excluding punctuation and blanks (zip code for United States).
- If either N405 or N406 is present, then the other is required.
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
Terms of Sale/Deferred Terms of Sale
To specify terms of sale.
Example: ITD~05~~~~~~30$
Code identifying type of payment terms.
- If the code in ITD01 is 04, then ITD09 is required and either ITD11 or ITD12 is required. If the code in ITD01 equals 05, then ITD06 or ITD07 is required.
- If ITD03 is present, then at least one of ITD04, ITD05, ITD13 is required.
‘05’ Sales Term Code
Date payment is due if discount is to be earned.
Date/Time Reference
To specify pertinent dates and times
F.O.B. Related Instructions
To specify transportation instructions relating to shipment
Example: FOBPPZZ~TRUCK$
Code identifying payment terms for transportation charges.
- FOB01 indicates which party will pay the carrier.
- If FOB03 is present, then FOB02 is required.
- CC
- Collect
- NC
- Service Freight, No Charge
- PP
- Prepaid (by Seller)
Code identifying type of location.
- FOB02 is the code specifying transportation responsibility location.
- If FOB04 is present, then FOB05 is required.
A free-form description to clarify the related data elements and their content.
- If FOB07 is present, then FOB06 is required.
Detail
Baseline Item Data (Invoice)
To specify the basic and most frequently used line item data for the invoice and related transactions.
Examples:
IT115100EA1.62PEBPMZ690072ON5201259D$1
IT112EA2.42PEBPZAA736TON6212S$
Alphanumeric characters assigned for differentiation within a transaction set.
- IT101 is the purchase order line item identification.
- If IT106 is present, then IT107 is required.
Number of units invoiced (supplier units).
- If IT108 is present, then IT109 is required.
Code identifying the basic unit of measurement.
- If IT110 is present, then IT111 is required.
Price per unit of product, service, commodity, etc.
- If IT112 is present, then IT113 is required.
Code identifying the type of unit price for an item.
- If IT114 is present, then IT115 is required.
- PE
- Price per Each
Code identifying the type/source of the descriptive number used in Product/Service ID (234).
- IT106 through IT125 provides for ten (10) different product/service ID's for each item. For example: Case, Color, Drawing No., UPC No., ISBN No., Model No., SKU.
- If IT116 is present, then IT117 is required.
- BP
- Buyer's Part Number
Identifying number for a product or service.
- If IT118 is present, then IT119 is required.
Code identifying the type/source of the descriptive number used in Product/Service ID (234).
- If IT120 is present, then IT121 is required.
- ON
- Customer Order Number
Additional Item Data
To specify additional item details relating to variations between ordered and shipped quantities, or to specify alternate units of measures and quantities.
Examples:
IT35100EACC0$
IT312EACC0$
Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set.
- If IT301 is present, then IT302 is required.
Code identifying the basic unit of measurement.
- At least one of IT301, IT303, IT304, or IT305 must be present.
Code indicating the status of an order or shipment or the disposition of any difference between the quantity ordered and the quantity shipped for a line item or transaction.
Product/Item Description
To describe a product or process in coded or free-form format
Example: PID~F~~~~RADIATOR ASSY $
Summary
Total Monetary Value Summary
To specify the total invoice discounts and amounts
Allowance, Charge or Service
To specify allowances, charges or services
Code which indicates an allowance or charge for the service specified.
- If ITA01 = A-Allowance or C-Charge, then at least one of ITA06, ITA07, or ITA08 must be present.
Code identifying the association assigning the code values.
- If ITA02 is present, then at least one of ITA03, or ITA13 is required.
Code identifying the special service.
- DL
- Delivery
- TX
- Sales Tax
Code indicating method of handling for an allowance or charge.
The number assigned by a vendor referencing an allowance, promotion, deal or charge.
Allowance or Charge Rate per Unit.
Total dollar amount for the allowance or charge.
- If ITA07 is present with either ITA06 or ITA08, then ITA07 takes precedence.
Code indicating on what basis allowance or charge percent is calculated.
- If ITA08 is present, then ITA09 is required.
Allowance or charge expressed as a percent.
Quantity basis when allowance or charge quantity is different from the purchase order or invoice quantity.
- If ITA10 is present, then ITA11 is required.
Code identifying the basic unit of measurement.
Numeric value of quantity.
- ITA12 is the quantity of free goods.
A free-form description to clarify the related data elements and their content.
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.
- At least one of ISS01, ISS03, or ISS05 must be present.
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.
Total number of line items in the transaction set.
- If CTT03 is present, then CTT04 is required.
Sum of values of the specified data element. All values in the data element will be summed without regard to decimal points (explicit or implicit) or signs. Truncation will occur on the left most digits if the sum is greater than the maximum size of the hash total of the data element.
-.0018 First occurrence of value being hashed.
.18 Second occurrence of value being hashed.
1.8 Third occurrence of value being hashed.
18.01 Fourth occurrence of value being hashed.
1855 Hash total prior to truncation.
855 Hash total after truncation to three-digit field.
- If CTT05 is present, then CTT06 is required.
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).
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.
Sample 1
GS~IN~SENDERGS~RECEIVERGS~240113~192150~000000001~X~003010
ST~810~0001
BIG~210125~9005912761~~02402902
REF~BM~0801112433
N1~BT~Mitsubishi Motors~92~99230
N2~ACCOUNTS PAYABLE
N3~4031 ASPEN GROVE DRIVE SUITE 7
N4~FRANKLIN~TN~37067
N1~ST~WHITE BEAR LAKE MITSUBISHI~92~24029
N3~3400 HIGHWAY 61 N
N4~White Bear Lake~MN~551105236
N1~VN~Amrep, Inc.~92~10W01
ITD~05~~~~~~30
DTM~011~210125
FOB~PP~ZZ~TRUCK
IT1~1~12~EA~2.72~PE~BP~ZAA376~ON~5088S
IT3~12~EA~CC~0
PID~F~~~~A00376 ZEP AUTO ENGINE DEGR ZAA376 20N15
TDS~3264
ISS~12~EA
CTT~1
SE~21~0001
ST~810~0002
BIG~210125~9005912762~~02100607
REF~BM~0801114918
N1~BT~Mitsubishi Motors~92~99230
N2~ACCOUNTS PAYABLE
N3~4031 ASPEN GROVE DRIVE SUITE 7
N4~FRANKLIN~TN~37067
N1~ST~OURISMAN MITSUBISHI~92~21006
N3~4404 BRANCH AVENUE
N4~Temple Hills~MD~207481802
N1~VN~Amrep, Inc.~92~10W01
ITD~05~~~~~~30
DTM~011~210125
FOB~PP~ZZ~TRUCK
IT1~1~12~EA~2.47~PE~BP~ZAA736C~ON~2001S
IT3~12~EA~CC~0
PID~F~~~~A00736 ZEP AUTO CARB SPRAY ZAA736C 16N12
TDS~2964
ISS~12~EA
CTT~1
SE~21~0002
GE~2~000000001
IEA~1~000000001
Sample 2
GS*IN*SENDERGS*RECEIVERGS*240113*193100*000000001*X*003010~
ST*810*0434~
BIG*231211*1872175**540F865~
REF*BM*0328712000~
N1*VN*BUSHWACKER INC*92*38VAF~
N1*ST*MITSUBISHI MOTORS - SEPDC- AT*92*99223~
N3*801 INTERSTATE W. PRKWY*801 INTERSTATE WEST PKWY~
N4*LITHIA SPRINGS*GA*30122~
N1*BY*MMNA*92*99230~
N2*ACCOUNT PAYABLE DEPT~
N4*FRANKLIN*TN*37067~
ITD*05******30~
DTM*011*231211~
FOB*PP~
IT1**200*EA*11.8*PE*BP*MZ315111*ON*540F865~
PID*F****OUTLANDER SPT BUMPER PROTECTOR~
TDS*236000~
ISS*200*EA~
CTT*1~
SE*19*0434~
GE*1*000000001~
IEA*1*000000001~
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.