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
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
EXAMPLE: BIG\20070110\43232861066\20070113\5471\\IA~
Big Lots PO # is numeric; no special characters can be added/allowed.
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
- BIG01 is the invoice issue 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.
if BIG04 is required
Identifying number for Purchase Order assigned by the orderer/purchaser
Required :
Store Drop Ships
Warehouse
Optional:
Direct Store Ships – VMI
Direct Store Delivery
Code specifying the type of transaction
- BIG07 is used only to further define the type of invoice when needed.
- CE
- Consolidated Credit Invoice
Phone Cards ONLY
- CN
- Credit Invoice
This value is to be used ONLY for Direct Store
Delivery (DSD) credit invoices unless otherwise
specified. - DR
- Debit Memo
- EP
- Expense Payment
- IA
- Inventory
- JR
- Equipment Rental
- PP
- Prepaid Invoice
- U5
- Update
VMI Mock Update
Note/Special Instruction
To transmit information in a free-form format, if necessary, for comment or special instruction
EXAMPLE: NTE\Partial Shipment ~
Note All priority or special handling documents will have a notes segment
A free-form description to clarify the related data elements and their content
Reference Information
To specify identifying information
EXAMPLE:
REF\DP\550~
REF\IA\1234567890~
REF\IV\C123456~
REF\PK\P123456789~
REF\BM\123456789~
REF\CN\PN123456789~
Code qualifying the Reference Identification
- BM
- Bill of Lading Number
Required for carrier shipment.
- CN
- Carrier's Reference Number (PRO/Invoice)
Optional
If available for carrier shipment.
- DP
- Department Number
Optional
Depending on BLI departmentalization requirements
- IA
- Internal Vendor Number
Required
- IV
- Seller's Invoice Number
Required
- PK
- Packing List Number
Required
provide order number for DSD
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
EXAMPLE:
PER\CR\JILL JONES\TE(614)278-4522~
PER\SR\BILL JONSON\TE\614-278-1234~
Code identifying the major duty or responsibility of the person or group named
- CR
- Customer Relations
- SR
- Sales Representative or Department
Code identifying the type of communication number
- TE
- Telephone
Complete communications number including country or area code when applicable
Party Identification
To identify a party by type of organization, name, and code
EXAMPLE:
N1\BT\BIG LOTS STORES INC~
N1\SF\ABC CO
N1\RI\ABC CO
Code identifying an organizational entity, a physical location, property or an individual
- BT
- Bill-to-Party
- RI
- Remit To
- SF
- Ship From
Code designating the system/method of code structure used for Identification Code (67)
Return value sent on the 850 PO
- 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.
Party Location
To specify the location of the named party
EXAMPLE: N3\1417 N BELT HWY~
Geographic Location
To specify the geographic place of the named party
EXAMPLE: N4\SAINT JOSEPH\MO\645062415~
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)
Party Identification
To identify a party by type of organization, name, and code
EXAMPLE:
N1\ST\STORE 500\92\0500~
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)
Return value sent on the 850 PO
- 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.
Party Location
To specify the location of the named party
EXAMPLE: N3\1417 N BELT HWY~
Geographic Location
To specify the geographic place of the named party
EXAMPLE: N4\SAINT JOSEPH\MO\645062415~
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
EXAMPLE:
ITD\01\3\2\20120120\10\20120209\30\57\\2%-10/NET 30~
ITD\03\4\2\20121210\10\20121231\30\98\\2%-DEC10/NET DEC31~
ITD\01\3\\20120209\30\\\NET 30~
Net term invoices require the ITD elements 01, 02, 06, 07, and 12.
Discount term invoices ALSO require the additional ITD elements 03, 04, 05 and 08.
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
recommended for “everyday” invoices, which are due based on when the order is invoiced and shipped.
- 03
- Fixed Date
recommended for “seasonal” invoices, which are due based on the month the season occurs. For example, all Christmas invoices have a discount due date of December 10 and a net due date of December 31, regardless of when the order actually shipped.
Code identifying the beginning of the terms period
- 3
- Invoice Date
recommended for “everyday” invoices, which are due based on when the order is invoiced and shipped.
- 4
- Specified Date
recommended for “seasonal” invoices, which are due based on the month the season occurs. For example, all Christmas invoices have a discount due date of December 10 and a net due date of December 31, regardless of when the order actually shipped.
Terms discount percentage, expressed as a percent, available to the purchaser if an invoice is paid on or before the Terms Discount Due Date
Provide when there is a discount.
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
Provide when there is a discount.
Number of days in the terms discount period by which payment is due if terms discount is earned
Provide when there is a discount.
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)
Ex: ‘30’ - 30 days
Total amount of terms discount
Provide when there is a discount.
A free-form description to clarify the related data elements and their content
Date/Time Reference
To specify pertinent dates and times
EXAMPLE: DTM\011\20120113~
F.O.B. Related Instructions
To specify transportation instructions relating to shipment
EXAMPLE: FOB\PP~
Required :
‘PP’ - Prepaid By Seller
‘PC’ – Prepaid Charge Customer.
‘CC’ – Collect
Optional:
(Direct Store Delivery)
Code identifying payment terms for transportation charges
- FOB01 indicates which party will pay the carrier.
- CC
- Collect
- PC
- Prepaid but Charged to Customer
- PP
- Prepaid (by Seller)
Detail
Baseline Item Data (Invoice)
To specify the basic and most frequently used line item data for the invoice and related transactions
EXAMPLE: IT1\9\EA\8.95\UP\012300319861\MG\CSG199\SK\123456789\PD\PLIERS~
Number of units invoiced (supplier units)
Value will be positive for all invoice types.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
Retail units must be provided in the PO401.
- CA
- Case
- EA
- Each
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.
Provide when applicable
- UP
- UPC Consumer
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- MG
- Manufacturer's Part Number
- VN
- Vendor's (Seller's) Item Number
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- CB
- Buyer's Catalog Number
- SK
- Stock Keeping Unit (SKU)
Identifying number for a product or service
Big Lots Article (SKU) 10 Digits Max.
Big Lots SKU values are numeric only.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
Can use alternate PID05
- PD
- Part Number Description
Pricing Information
To specify pricing information
EXAMPLE: CTP\MSR\1.99~
Code identifying pricing specification
- MSR
- Manufacturer's Suggested Retail
Price per unit of product, service, commodity, etc.
- See Figures Appendix for an example detailing the use of CTP03 and CTP04.
- See Figures Appendix for an example detailing the use of CTP03, CTP04 and CTP07.
Product/Item Description
To describe a product or process in coded or free-form format
EXAMPLE: PID\F\\FW-PHOTO WED SCENE~
If the item description is provided in the IT1 ‘PD’ qualifier this segment becomes optional.
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
A free-form description to clarify the related data elements and their content
Item Physical Details
To specify the physical qualities, packaging, weights, and dimensions relating to the item
EXAMPLE: PO4\9~
The number of inner containers, or number of eaches if there are no inner containers, per outer container
Reference Information
To specify identifying information
EXAMPLE: REF\DP\003~
Code qualifying the Reference Identification
- DP
- Department Number
depending on BLI departmentalization requirements
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Summary
Total Monetary Value Summary
To specify the total invoice discounts and amounts
EXAMPLE:
TDS\2872\2872\2815\57~
TDS\2872~ (Net Term Invoice)
Monetary amount
- TDS01 is the total amount of invoice (including charges, less allowances) before terms discount (if discount is applicable).
Value will be positive for all invoice types.
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.
Required for Discount Term Invoices.
Monetary amount
- TDS03 is the amount of invoice due if paid by terms discount due date (total invoice or installment amount less cash discount).
Required for Discount Term Invoices.
Monetary amount
- TDS04 indicates the total amount of terms discount.
Required for Discount Term Invoices.
Carrier Details
To specify transportation details for the transaction
EXAMPLE:
CAD\T\\TEXT\CN\123456789~
CAD\T\\TEXT\BM\123456789~
Segment is not required for Direct Store Delivery.
Code specifying the method or type of transportation for the shipment
- H
- Customer Pickup
- T
- Best Way (Shippers Option)
Free-form description of the routing or requested routing for shipment, or the originating carrier's identity
Code qualifying the Reference Identification
- 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
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
EXAMPLE:
SAC\C\H625\\1025\\\\06\\CRV ~
SAC\A\C310\\1135\\\\02\\DISCOUNT ~
Note allowances are permitted at the Summary level.
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
- A130
- Additional Material
- A170
- Adjustments
- C110
- Deposit
- C310
- Discount
- D240
- Freight
- F180
- Pallet
- F340
- Pick/Up
- H625
- Tax - Beverage Tax
- H630
- Tax - City Sales Tax (Only)
- H750
- Tax - Sales Tax (State and Local)
- 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.
Value will be positive for all invoice types.
Code indicating method of handling for an allowance or charge
- 02
- Off Invoice
- 06
- Charge to be Paid by Customer
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
EXAMPLE: ISS\18\EA~
Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- CA
- Case
- CT
- Carton
- EA
- Each
- PK
- Package
- TK
- Tank
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.
EXAMPLE: CTT\2~
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
DC SHIPMENT
BIG*20041004*0840286*20040629*2285475***IA~
REF*IA*000211230~
REF*PK*0840286~
REF*IV*0840286~
REF*BM*1234567890~
N1*ST*DURANT DC, LLC. 0879*92*0879~
N3*2306 ENTERPRISE BLVD~
N4*DURANT*OK*74701~
ITD*01*3****20041103*30*****NET 30 DAYS~
DTM*011*20041004~
FOB*PP~
IT1**460*EA*99**UP*011120900330*MG*1699R*SK*310002202~
PID*F****ITEM1~
PO4*1~
TDS*4554000~
CAD*T****PICK TRUCK ONE**CN*0840286~
ISS*460*EA~
CTT*1~
SE*19*290006~
Direct Store Delivery (DSD) 1
BIG*20041011*82701167*****IA~
REF*PK*82701167~
REF*IV*82701167~
REF*IA*1003357~
N1*ST*BIG LOTS 4268*92*4268~
N3*1242 COLUSA AVE*BIG LOTS PNS STORES INC~
N4*YUBA CITY*CA*959913653~
ITD*01*3****20041103*30*****NET 30 DAYS~
DTM*011*20041011~
IT1**96*CA*99.99**UP*049000055412*MG*05541~
PID*F****8PK SODA POP ~
PO4*3~
TDS*969120~
SAC*C*H625***9216*******06***CRV BEVERAGE TAX~
ISS*96*EA~
CTT*1~
SE*17*300680002~
Direct Store Delivery (DSD) 2
BIG*20041011*82701168*****CN~
REF*PK*82701168~
REF*IV*82701168~
REF*IA*1003357~
N1*ST*BIG LOTS 4268*92*4268~
N3*1242 COLUSA AVE*BIG LOTS PNS STORES INC~
N4*YUBA CITY*CA*959913653~
ITD*01*3****20041103*30*****NET 30 DAYS~
DTM*011*20041011~
IT1**10*CA*99.99**UP*049000055412*MG*05541~
PID*F****8PK SODA POP ~
PO4*3~
TDS*10215~
SAC*C*H625***216*******06***CRV BEVERAGE TAX~
ISS*10*EA~
CTT*1~
SE*17*300680002~
Sample
BIG*20120110*43232861066*20120113*5471***IA~
NTE**PARTIAL SHIPMENT ~
REF*IA*1234567890~
REF*IV*C123456~
REF*PK*P123456789~
REF*BM*1243567890~
N1*BT*BIG LOTS STORES INC.~
N3*300 PHILLIPI RD~
N4*COLUMBUS*OH*432281310~
N1*ST*STORE 500*92*0500~
N3*1417 N BELT HWY~
N4*SAINT JOSEPH*MO*645062415~
ITD*01*3*2*20120120*10*20120209*30*57****2%-10/NET 30~
DTM*011*20120113~
FOB*PP~
IT1**9*EA*8.95**UP*012300319861*MG*CSG199*SK*123456789~
CTP**MSR*1.99~
PID*F****FW-PHOTO WED SCENE~
PO4*9~
IT1**9*EA*19.76**UP*012300590413*MG*CSG439*SK*012345678~
CTP**MSR*4.39~
PID*F****RW-DOVES ~
PO4*9~
TDS*2872*2872*2815*57~
CAD*T****TEXT**BM*123456789~
SAC*C*H625***1025*******06***CRV ~
SAC*A*C310***1135*******02***DISCOUNT ~
ISS*18*EA~
CTT*2~
SE*24*000101504~
STORE DROP / DIRECT SHIPMENT
BIG*20041008*438698 *20040930*2471755***IA~
REF*IV*438698~
REF*IA*553900~
REF*PK*711004~
N1*ST*BIG LOTS FURNITURE#4238*92*4238~
N3*499 ORANGE SHOW RD~
N4*SAN BERNARDINO*CA*92408~
ITD*01*3*2.0*20041023*15*20041107*30*3044****2% 15 NET 30 DAYS~
DTM*011*20041008~
FOB*PP~
IT1**1*EA*99.00**UP*011120900330*MG*1776SF*SK*123456789~
PID*F****ITEM1~
PO4*1~
IT1**4*EA*99.00**UP*011120900330*MG*1774A*SK*123456789~
PID*F****ITEM2~
PO4*1~
IT1**2*EA*99.00**UP*011120900330*MG*1775B*SK*123456789~
PID*F****ITEM3~
PO4*1~
IT1**2*EA*99.00**UP*011120900330*MG*1774BF*SK*123456789~
PID*F****ITEM4~
PO4*1~
IT1**2*EA*99.00**UP*011120900330*MG*1777C*SK*123456789~
PID*F****ITEM5~
PO4*1~
IT1**7*EA*99.00**UP*011120900330*MG*1776CF*SK*123456789~
PID*F****ITEM6~
PO4*1~
TDS*165137*152200*149156*3044~
CAD*T****PREPAY AND ADD**BM*711004~
SAC*C*D240***12937*******06***Freight Charge~
ISS*18*EA~
CTT*6~
SE*38*0007~
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.