Overstock
/
Invoice
  • Specification
  • EDI Inspector
Import guide into your account
Stedi maintains this guide based on public documentation from Overstock. Contact Overstock for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
Overstock logo

X12 810 Invoice

X12 Release 4010

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.

Delimiters
  • ~ Segment
  • * Element
  • > Component
EDI sample
  • Sample
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/overstock/invoice/01GYW6XB0X1AH2PAT7ZY484E2X
Powered by
Build EDI implementation guides at stedi.com
Overview
ISA
-
Interchange Control Header
Max use 1
Required
GS
-
Functional Group Header
Max use 1
Required
heading
ST
010
Transaction Set Header
Max use 1
Required
BIG
020
Beginning Segment for Invoice
Max use 1
Required
CUR
040
Currency
Max use 1
Required
REF
050
Retailer Name
Max use 12
Optional
REF
050
Seller Invoice Number
Max use 12
Optional
Bill To
ITD
130
Terms of Sale/Deferred Terms of Sale
Max use 1
Optional
DTM
140
Date/Time Reference
Max use 10
Optional
summary
TDS
010
Total Monetary Value Summary
Max use 1
Required
SAC Loop
CTT
070
Transaction Totals
Max use 1
Required
SE
080
Transaction Set Trailer
Max use 1
Required
GE
-
Functional Group Trailer
Max use 1
Required
IEA
-
Interchange Control Trailer
Max use 1
Required
ISA

Interchange Control Header

RequiredMax use 1

To start and identify an interchange of zero or more functional groups and interchange-related control segments

Example
ISA-01
I01
Authorization Information Qualifier
Required

Code to identify the type of information in the Authorization Information

00
No Authorization Information Present (No Meaningful Information in I02)
ISA-02
I02
Authorization Information
Required
String (AN)
Min 10Max 10

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)

ISA-03
I03
Security Information Qualifier
Required

Code to identify the type of information in the Security Information

00
No Security Information Present (No Meaningful Information in I04)
ISA-04
I04
Security Information
Required
String (AN)
Min 10Max 10

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)

ISA-05
I05
Interchange ID Qualifier
Required
Identifier (ID)
Min 2Max 2

Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

Codes
ISA-06
I06
Interchange Sender ID
Required
String (AN)
Min 15Max 15

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

ISA-07
I05
Interchange ID Qualifier
Required
Identifier (ID)
Min 2Max 2

Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

Codes
ISA-08
I07
Interchange Receiver ID
Required
String (AN)
Min 15Max 15

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

ISA-09
I08
Interchange Date
Required
YYMMDD format

Date of the interchange

ISA-10
I09
Interchange Time
Required
HHMM format

Time of the interchange

ISA-11
I10
Interchange Control Standards Identifier
Required

Code to identify the agency responsible for the control standard used by the message that is enclosed by the interchange header and trailer

U
U.S. EDI Community of ASC X12, TDCC, and UCS
ISA-12
I11
Interchange Control Version Number
Required

This version number covers the interchange control segments

00401
Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1997
ISA-13
I12
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9

A control number assigned by the interchange sender

ISA-14
I13
Acknowledgment Requested
Required
Identifier (ID)
Min 1Max 1

Code sent by the sender to request an interchange acknowledgment (TA1)

0
No Acknowledgment Requested
1
Interchange Acknowledgment Requested
ISA-15
I14
Usage Indicator
Required
Identifier (ID)
Min 1Max 1

Code to indicate whether data enclosed by this interchange envelope is test, production or information

I
Information
P
Production Data
T
Test Data
ISA-16
I15
Component Element Separator
Required
String (AN)
Min 1Max 1

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

RequiredMax use 1

To indicate the beginning of a functional group and to provide control information

Example
GS-01
479
Functional Identifier Code
Required

Code identifying a group of application related transaction sets

IN
Invoice Information (810,819)
GS-02
142
Application Sender's Code
Required
String (AN)
Min 2Max 15

Code identifying party sending transmission; codes agreed to by trading partners

GS-03
124
Application Receiver's Code
Required
String (AN)
Min 2Max 15

Code identifying party receiving transmission. Codes agreed to by trading partners

GS-04
373
Date
Required
CCYYMMDD format

Date expressed as CCYYMMDD

GS-05
337
Time
Required
HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

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)

GS-06
28
Group Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender

GS-07
455
Responsible Agency Code
Required
Identifier (ID)
Min 1Max 2

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
GS-08
480
Version / Release / Industry Identifier Code
Required

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

004010
Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1997

Heading

ST
010
Heading > ST

Transaction Set Header

RequiredMax use 1

To indicate the start of a transaction set and to assign a control number

Example
ST-01
143
Transaction Set Identifier Code
Required

Code uniquely identifying a Transaction Set

  • The transaction set identifier (ST01) 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
ST-02
329
Transaction Set Control Number
Required
Numeric (N)
Min 4Max 9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

BIG
020
Heading > BIG

Beginning Segment for Invoice

RequiredMax use 1

To indicate the beginning of an invoice transaction set and transmit identifying numbers and dates

Example
BIG-01
373
Date
Required
CCYYMMDD format

Date expressed as CCYYMMDD

  • BIG01 is the invoice issue date.
BIG-02
76
Invoice Number
Required
String (AN)
Min 1Max 22

Identifying number assigned by issuer

BIG-04
324
Supplier Oasis Order Number
Required
String (AN)
Min 1Max 22

Identifying number for Purchase Order assigned by the orderer/purchaser

Usage notes

Supplier Oasis Order Number

BIG-05
328
Retailer Order Number
Required
String (AN)
Min 1Max 30

Number identifying a release against a Purchase Order previously placed by the parties involved in the transaction

Usage notes

Retailer Order Number

CUR
040
Heading > CUR

Currency

RequiredMax use 1

To specify the currency (dollars, pounds, francs, etc.) used in a transaction

Example
CUR-01
98
Entity Identifier Code
Required

Code identifying an organizational entity, a physical location, property or an individual

BT
Bill-to-Party
CUR-02
100
Currency Code
Required
Identifier (ID)
Min 3Max 3

Code (Standard ISO) for country in whose currency the charges are specified

REF-01
128
Reference Identification Qualifier
Required

Code qualifying the Reference Identification

RN
Run Number
REF-02
127
Reference Identification
Required
String (AN)
Min 1Max 30

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

REF
050
Heading > REF

Seller Invoice Number

OptionalMax use 12

To specify identifying information

Example
Variants (all may be used)
REFRetailer Name
REF-01
128
Reference Identification Qualifier
Required

Code qualifying the Reference Identification

IV
Seller's Invoice Number
REF-02
127
Reference Identification
Required
String (AN)
Min 1Max 30

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

N1 Bill To
RequiredMax >1
Variants (all may be used)
Remit To
N1
070
Heading > Bill To > N1

Name

RequiredMax use 1

To identify a party by type of organization, name, and code

Example
N1-01
98
Entity Identifier Code
Required

Code identifying an organizational entity, a physical location, property or an individual

BT
Bill-to-Party
N1-02
93
Name
Required
String (AN)
Min 1Max 60

Free-form name

N3
090
Heading > Bill To > N3

Address Information

RequiredMax use 2

To specify the location of the named party

Example
N3-01
166
Address Information
Required
String (AN)
Min 1Max 55

Address information

N3-02
166
Address Information
Optional
String (AN)
Min 1Max 55

Address information

N4
100
Heading > Bill To > N4

Geographic Location

RequiredMax use 1

To specify the geographic place of the named party

Example
N4-01
19
City Name
Required
String (AN)
Min 2Max 30

Free-form text for city name

  • A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
N4-02
156
State or Province Code
Required
Identifier (ID)
Min 2Max 2

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.
N4-03
116
Postal Code
Required
Identifier (ID)
Min 3Max 15

Code defining international postal zone code excluding punctuation and blanks (zip code for United States)

N4-04
26
Country Code
Required
Identifier (ID)
Min 2Max 3

Code identifying the country

N1 Bill To end
N1 Remit To
RequiredMax >1
Variants (all may be used)
Bill To
N1
070
Heading > Remit To > N1

Name

RequiredMax use 1

To identify a party by type of organization, name, and code

Example
N1-01
98
Entity Identifier Code
Required

Code identifying an organizational entity, a physical location, property or an individual

RI
Remit To
N1-02
93
Name
Required
String (AN)
Min 1Max 60

Free-form name

N3
090
Heading > Remit To > N3

Address Information

RequiredMax use 2

To specify the location of the named party

Example
N3-01
166
Address Information
Required
String (AN)
Min 1Max 55

Address information

N3-02
166
Address Information
Optional
String (AN)
Min 1Max 55

Address information

N4
100
Heading > Remit To > N4

Geographic Location

RequiredMax use 1

To specify the geographic place of the named party

Example
N4-01
19
City Name
Required
String (AN)
Min 2Max 30

Free-form text for city name

  • A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
N4-02
156
State or Province Code
Required
Identifier (ID)
Min 2Max 2

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.
N4-03
116
Postal Code
Required
Identifier (ID)
Min 3Max 15

Code defining international postal zone code excluding punctuation and blanks (zip code for United States)

N4-04
26
Country Code
Required
Identifier (ID)
Min 2Max 3

Code identifying the country

N1 Remit To end
ITD
130
Heading > ITD

Terms of Sale/Deferred Terms of Sale

OptionalMax use >1

To specify terms of sale

Example
ITD-01
336
Terms Type Code
Required

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
ITD-02
333
Terms Basis Date Code
Required

Code identifying the beginning of the terms period

3
Invoice Date
ITD-06
446
Terms Net Due Date
Required
CCYYMMDD format

Date when total invoice amount becomes due expressed in format CCYYMMDD

ITD-07
386
Terms Net Days
Optional
Numeric (N0)
Min 1Max 3

Number of days until total invoice amount is due (discount not applicable)

ITD-12
352
Description
Optional
String (AN)
Min 1Max 80

A free-form description to clarify the related data elements and their content

DTM
140
Heading > DTM

Date/Time Reference

OptionalMax use 10

To specify pertinent dates and times

Example
DTM-01
374
Date/Time Qualifier
Required

Code specifying type of date or time, or both date and time

011
Shipped
DTM-02
373
Date
Required
CCYYMMDD format

Date expressed as CCYYMMDD

Heading end

Detail

IT1 Loop
RequiredMax >1
IT1
010
Detail > IT1 Loop > IT1

Baseline Item Data (Invoice)

RequiredMax use 1

To specify the basic and most frequently used line item data for the invoice and related transactions

Example
IT1-01
350
Assigned Identification
Required
String (AN)
Min 1Max 20

Alphanumeric characters assigned for differentiation within a transaction set

  • IT101 is the purchase order line item identification.
IT1-02
358
Quantity Invoiced
Required
Decimal number (R)
Min 1Max 10

Number of units invoiced (supplier units)

IT1-03
355
Unit or Basis for Measurement Code
Required

Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

EA
Each
IT1-04
212
Unit Price
Required
Decimal number (R)
Min 1Max 15

Price per unit of product, service, commodity, etc.

IT1-05
639
Basis of Unit Price Code
Optional

Code identifying the type of unit price for an item

PE
Price per Each
IT1-06
235
Product/Service ID Qualifier
Required

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.
SK
Stock Keeping Unit (SKU)
IT1-07
234
Product/Service ID
Required
String (AN)
Min 1Max 48

Identifying number for a product or service

Usage notes

Vendor SKU

PID Loop
RequiredMax >1
PID
060
Detail > IT1 Loop > PID Loop > PID

Product/Item Description

RequiredMax use 1

To describe a product or process in coded or free-form format

Example
PID-01
349
Item Description Type
Required

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
PID-05
352
Description
Required
String (AN)
Min 1Max 80

A free-form description to clarify the related data elements and their content

PID Loop end
IT1 Loop end
Detail end

Summary

TDS
010
Summary > TDS

Total Monetary Value Summary

RequiredMax use 1

To specify the total invoice discounts and amounts

Example
TDS-01
610
Amount
Required
Numeric (N2)
Min 1Max 15

Monetary amount

  • TDS01 is the total amount of invoice (including charges, less allowances) before terms discount (if discount is applicable).
TDS-02
610
Amount
Required
Numeric (N2)
Min 1Max 15

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.
SAC Loop
OptionalMax >1
SAC
040
Summary > SAC Loop > SAC

Service, Promotion, Allowance, or Charge Information

RequiredMax use 1

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-01
248
Allowance or Charge Indicator
Required

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
P
Promotion
S
Service
SAC-02
1300
Service, Promotion, Allowance, or Charge Code
Required
Identifier (ID)
Min 4Max 4

Code identifying the service, promotion, allowance, or charge

SAC-05
610
Amount
Required
Numeric (N2)
Min 1Max 15

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.
SAC-12
331
Allowance or Charge Method of Handling Code
Required
Identifier (ID)
Min 2Max 2

Code indicating method of handling for an allowance or charge

SAC-15
352
Description
Required
String (AN)
Min 1Max 80

A free-form description to clarify the related data elements and their content

SAC Loop end
CTT
070
Summary > CTT

Transaction Totals

RequiredMax use 1

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.
Example
CTT-01
354
Number of Line Items
Required
Numeric (N0)
Min 1Max 6

Total number of line items in the transaction set

SE
080
Summary > SE

Transaction Set Trailer

RequiredMax use 1

To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)

Example
SE-01
96
Number of Included Segments
Required
Numeric (N0)
Min 1Max 10

Total number of segments included in a transaction set including ST and SE segments

SE-02
329
Transaction Set Control Number
Required
Numeric (N)
Min 4Max 9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

Summary end

Functional Group Trailer

RequiredMax use 1

To indicate the end of a functional group and to provide control information

Example
GE-01
97
Number of Transaction Sets Included
Required
Numeric (N0)
Min 1Max 6

Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element

GE-02
28
Group Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender

Interchange Control Trailer

RequiredMax use 1

To define the end of an interchange of zero or more functional groups and interchange-related control segments

Example
IEA-01
I16
Number of Included Functional Groups
Required
Numeric (N0)
Min 1Max 5

A count of the number of functional groups included in an interchange

IEA-02
I12
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9

A control number assigned by the interchange sender

EDI Samples

Sample

ISA*00* *00* *ZZ*SENDER *ZZ*RECEIVER *231120*0418*U*00401*000000001*0*T*>~
GS*IN*SENDERGS*RECEIVERGS*20231120*041832*000000001*X*004010~
ST*810*3569~
BIG*20170803*11037436**123456-1*162345789~
CUR*BT*USD~
REF*RN*OSTK~
REF*IV*11037436~
N1*RI*Supplier Name~
N3*1234 S Anywhere Ave~
N4*Bloomington*IL*61701*US~
N1*BT*Overstock.com~
N3*799 Coliseum Way,~
N4*Midvale*UT*84047*US~
ITD*01*3****20170902*30*****NET 30~
DTM*011*20170802~
IT1*1*2*EA*98.95*PE*SK*F524-ABD~
PID*F****52IN ROTO CEILING FAN 2014~
IT1*2*1*EA*98.95*PE*SK*F524-ORB~
PID*F****52IN ROTO CEILING FAN 2014~
TDS*31471*29685~
SAC*C*H850***1286*******06***TAX CHARGES~
SAC*C*D500***500*******06***HANDLING~
CTT*1~
SE*22*3569~
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.