Carpenter Invoice Example

g GE Information Services
Electronic Commerce Service Center
810 Invoice/Garden Ridge-Trading Partner Specification
Functional Group ID= IN

Introduction:
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.
Heading:
Pos. Seg. Req. Loop Notes and
No. ID Name Des. Max.Use Repeat Comments
M 010 ISA Interchange Control Header M 1
M 005 GS Functional Group Header M 1
Detail:
M 010 ST Transaction Set Header M 1
M 020 BIG Beginning Segment for Invoice M 1
LOOP ID - N1 200
M 070 N1 Name M 1
LOOP ID - N1 200
M 070 N1 Name M 1
130 ITD Terms of Sale/Deferred Terms of Sale O >1
Detail:
LOOP ID - IT1 200000
M 010 IT1 Baseline Item Data (Invoice) M 1
LOOP ID - PID 1000
060 PID Product/Item Description O 1
Summary:
M 010 TDS Total Monetary Value Summary M 1
070 CTT Transaction Totals O 1 n1
M 080 SE Transaction Set Trailer M 1
M 085 GE Functional Group Trailer M 1
M 100 IEA Interchange Control Trailer M 1
sf810gmu_tp1.doc Page 1 of 19 Date Printed: 12/13/2010 4:47:00 PM

Last Updated: 12/13/2010 4:47:00 PM by: Richard A. Carpenter Revision: 2
Transaction Set Notes
1. 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.

Segment: ISA Interchange Control Header

Position: 010
Loop:
Level: Heading
Usage: Mandatory
Max Use: 1
Purpose: To start and identify an interchange of zero or more functional groups and interchange-related control
segments
Syntax Notes:
Semantic Notes:
Comments:
Data Element Summary

Ref. Data
Des. Element Name Attributes
M ISA01 I01 Authorization Information Qualifier M ID 2/2
Code to identify the type of information in the Authorization Information
00 No Authorization Information Present (No Meaningful
Information in I02)
M ISA02 I02 Authorization Information M AN 10/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)
M ISA03 I03 Security Information Qualifier M ID 2/2
Code to identify the type of information in the Security Information
00 No Security Information Present (No Meaningful
Information in I04)
M ISA04 I04 Security Information M AN 10/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)
M ISA05 I05 Interchange ID Qualifier M ID 2/2
Qualifier to designate the system/method of code structure used to designate
the sender or receiver ID element being qualified
M ISA06 I06 Interchange Sender ID M AN 15/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
M ISA07 I05 Interchange ID Qualifier M ID 2/2
Qualifier to designate the system/method of code structure used to designate
the sender or receiver ID element being qualified
12 Phone (Telephone Companies)
M ISA08 I07 Interchange Receiver ID M AN 15/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
2815797901T - for testing

2815797901 - for production

M ISA09 I08 Interchange Date M DT 6/6
Date of the interchange
M ISA10 I09 Interchange Time M TM 4/4
Time of the interchange
M ISA11 I10 Interchange Control Standards Identifier M ID 1/1
Code to identify the agency responsible for the control standard used by the
message that is enclosed by the interchange header and trailer
Refer to 004010 Data Element Dictionary for acceptable code values.
M ISA12 I11 Interchange Control Version Number M ID 5/5
This version number covers the interchange control segments
00400 Standard Issued as ANSI X12.5-1997
M ISA13 I12 Interchange Control Number M N0 9/9
A control number assigned by the interchange sender
M ISA14 I13 Acknowledgment Requested M ID 1/1
Code sent by the sender to request an interchange acknowledgment (TA1)
0 No Acknowledgment Requested
M ISA15 I14 Usage Indicator M ID 1/1
Code to indicate whether data enclosed by this interchange envelope is test,
production or information
P Production Data
T Test Data
M ISA16 I15 Component Element Separator M AN 1/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

Segment: GS Functional Group Header

Position: 005
Loop:
Level: Heading
Usage: Mandatory
Max Use: 1
Purpose: To indicate the beginning of a functional group and to provide control information
Syntax Notes:
Semantic Notes: 1 GS04 is the group date.
2 GS05 is the group time.
3 The data interchange control number GS06 in this header must be identical to the same data
element in the associated functional group trailer, GE02.
Comments: 1 A functional group of related transaction sets, within the scope of X12 standards, consists of a
collection of similar transaction sets enclosed by a functional group header and a functional
group trailer.

Ref. Data
M GS01 479 Functional Identifier Code M ID 2/2
Code identifying a group of application related transaction sets
IN Invoice Information (810,819)
M GS02 142 Application Sender's Code M AN 2/15
Code identifying party sending transmission; codes agreed to by trading
partners
M GS03 124 Application Receiver's Code M AN 2/15
Code identifying party receiving transmission; codes agreed to by trading
partners
2815797901T - for testing
2815797901 - for production
M GS04 373 Date M DT 8/8
Date expressed as CCYYMMDD
M GS05 337 Time M TM 4/8
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)
M GS06 28 Group Control Number M N0 1/9
Assigned number originated and maintained by the sender
M GS07 455 Responsible Agency Code M ID 1/2
Code used in conjunction with Data Element 480 to identify the issuer of the
standard
M GS08 480 Version / Release / Industry Identifier Code M AN 1/12
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

Segment: ST Transaction Set Header

Position: 010
Loop:
Level: Detail
Usage: Mandatory
Max Use: 1
Purpose: To indicate the start of a transaction set and to assign a control number
Syntax Notes:
Semantic Notes: 1 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).
Comments:

Ref. Data
M ST01 143 Transaction Set Identifier Code M ID 3/3
Code uniquely identifying a Transaction Set
'810'
810 Invoice
M ST02 329 Transaction Set Control Number M AN 4/9
Identifying control number that must be unique within the transaction set
functional group assigned by the originator for a transaction set

Segment: BIG Beginning Segment for Invoice

Position: 020
Loop:
Level: Detail
Usage: Mandatory
Max Use: 1
Purpose: To indicate the beginning of an invoice transaction set and transmit identifying numbers and dates
Syntax Notes:
Semantic Notes: 1 BIG01 is the invoice issue date.
2 BIG03 is the date assigned by the purchaser to purchase order.
3 BIG10 indicates the consolidated invoice number. When BIG07 contains code CI, BIG10 is not
used.
Comments: 1 BIG07 is used only to further define the type of invoice when needed.

Ref. Data
M BIG01 373 Date M DT 8/8
Date expressed as CCYYMMDD
Invoice-Date
M BIG02 76 Invoice Number M AN 1/22
Identifying number assigned by issuer
M BIG04 324 Purchase Order Number M AN 1/22
Identifying number for Purchase Order assigned by the orderer/purchaser
Manditory field for Garden Ridge - from the Purchase Order - BEG03
BIG07 640 Transaction Type Code O ID 2/2
Code specifying the type of transaction
Mandatory field for Garden Ridge - 'CN'
CN Credit Invoice

Segment: N1 Name
Position: 070
Loop: N1 Mandatory
Level: Detail
Usage: Mandatory
Max Use: 1
Purpose: To identify a party by type of organization, name, and code
Syntax Notes: 1 At least one of N102 or N103 is required.
2 If either N103 or N104 is present, then the other is required.
Semantic Notes:
Comments: 1 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.
2 N105 and N106 further define the type of entity in N101.
Notes: Manditory segment for Garden Ridge

Ref. Data
M N101 98 Entity Identifier Code M ID 2/3
Code identifying an organizational entity, a physical location, property or an
individual
'VN'
VN Vendor
>> N103 66 Identification Code Qualifier X ID 1/2
Code designating the system/method of code structure used for Identification
Code (67)
'ZZ'
ZZ Mutually Defined
>> N104 67 Identification Code X AN 2/80
Code identifying a party or other code
Manditory field for Garden Ridge from Purchase Order - N104(when N101 =
'VN')

Segment: N1 Name
Position: 070
Loop: N1 Mandatory
Level: Detail
Usage: Mandatory
Max Use: 1
Purpose: To identify a party by type of organization, name, and code
Syntax Notes: 1 At least one of N102 or N103 is required.
2 If either N103 or N104 is present, then the other is required.
Semantic Notes:
Comments: 1 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.
2 N105 and N106 further define the type of entity in N101.
Notes: Manditory segment for Garden Ridge

Ref. Data
M N101 98 Entity Identifier Code M ID 2/3
Code identifying an organizational entity, a physical location, property or an
individual
'ST'
ST Ship To
>> N103 66 Identification Code Qualifier X ID 1/2
Code designating the system/method of code structure used for Identification
Code (67)
'ZZ'
ZZ Mutually Defined
>> N104 67 Identification Code X AN 2/80
Code identifying a party or other code
Manditory field for Garden Ridge from Purchase Order - SDQ(identification
code)

Segment: ITD Terms of Sale/Deferred Terms of Sale

Position: 130
Loop:
Level: Detail
Usage: Optional
Max Use: >1
Purpose: To specify terms of sale
Syntax Notes: 1 If ITD03 is present, then at least one of ITD04 ITD05 or ITD13 is required.
2 If ITD08 is present, then at least one of ITD04 ITD05 or ITD13 is required.
3 If ITD09 is present, then at least one of ITD10 or ITD11 is required.
Semantic Notes: 1 ITD15 is the percentage applied to a base amount used to determine a late payment charge.
Comments: 1 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.

Ref. Data
ITD03 338 Terms Discount Percent O R 1/6
Terms discount percentage, expressed as a percent, available to the purchaser
if an invoice is paid on or before the Terms Discount Due Date
ITD05 351 Terms Discount Days Due X N0 1/3
Number of days in the terms discount period by which payment is due if terms
discount is earned
ITD06 446 Terms Net Due Date O DT 8/8
Date when total invoice amount becomes due expressed in format
CCYYMMDD
ITD07 386 Terms Net Days O N0 1/3
Number of days until total invoice amount is due (discount not applicable)

Segment: IT1 Baseline Item Data (Invoice)

Position: 010
Loop: IT1 Mandatory
Level: Detail
Usage: Mandatory
Max Use: 1
Purpose: To specify the basic and most frequently used line item data for the invoice and related transactions
Syntax Notes: 1 If any of IT102 IT103 or IT104 is present, then all are required.
2 If either IT106 or IT107 is present, then the other is required.
Semantic Notes: 1 IT101 is the purchase order line item identification.
Comments: 1 Element 235/234 combinations should be interpreted to include products and/or services. See the
Data Dictionary for a complete list of IDs.
2 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.
Notes: Manditory segment for Garden Ridge. Please enter VN, CB, and UP and corresponding
value in any of IT106 - IT107, IT108 - IT109, IT110 - IT111 pairs.

Ref. Data
>> IT102 358 Quantity Invoiced X R 1/10
Number of units invoiced (supplier units)
IT103 355 Unit or Basis for Measurement Code X ID 2/2
Code specifying the units in which a value is being expressed, or manner in
which a measurement has been taken
Refer to 004010 Data Element Dictionary for acceptable code values.
M IT104 212 Unit Price M R 1/17
Price per unit of product, service, commodity, etc.
Manditory field for Garden Ridge from Purchase Order - PO104
>> IT105 639 Basis of Unit Price Code O ID 2/2
Code identifying the type of unit price for an item
PE Price per Each
IT106 235 Product/Service ID Qualifier X ID 2/2
Code identifying the type/source of the descriptive number used in
Product/Service ID (234)
'VN' or 'CB' or 'UP'
CB Buyer's Catalog Number
UP U.P.C. Consumer Package Code (1-5-5-1)

VN Vendor's (Seller's) Item Number

IT107 234 Product/Service ID X AN 1/48
Identifying number for a product or service
Vendor Number or Buyers Catalog Number or UPC Code

Segment: PID Product/Item Description

Position: 060
Loop: PID Optional
Level: Detail
Usage: Optional
Max Use: 1
Purpose: To describe a product or process in coded or free-form format
Syntax Notes: 1 If PID04 is present, then PID03 is required.
2 At least one of PID04 or PID05 is required.
3 If PID07 is present, then PID03 is required.
Semantic Notes: 1 Use PID03 to indicate the organization that publishes the code list being referred to.
2 PID04 should be used for industry-specific product description codes.
3 PID08 describes the physical characteristics of the product identified in PID04. A "Y" indicates
that the specified attribute applies to this item; an "N" indicates it does not apply. Any other
value is indeterminate.
4 PID09 is used to identify the language being used in PID05.
Comments: 1 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.
2 Use PID06 when necessary to refer to the product surface or layer being described in the segment.
3 PID07 specifies the individual code list of the agency specified in PID03.

Ref. Data
M PID01 349 Item Description Type M ID 1/1
Code indicating the format of a description
'F'
F Free-form
PID05 352 Description X AN 1/80
A free-form description to clarify the related data elements and their content

Segment: TDS Total Monetary Value Summary

Position: 010
Loop:
Level: Summary
Usage: Mandatory
Max Use: 1
Purpose: To specify the total invoice discounts and amounts
Syntax Notes:
Semantic Notes: 1 TDS01 is the total amount of invoice (including charges, less allowances) before terms discount
(if discount is applicable).
2 TDS02 indicates the amount upon which the terms discount amount is calculated.
3 TDS03 is the amount of invoice due if paid by terms discount due date (total invoice or
installment amount less cash discount).
4 TDS04 indicates the total amount of terms discount.
Comments: 1 TDS02 is required if the dollar value subject to discount is not equal to the dollar value of
TDS01.

Ref. Data
M TDS01 610 Amount M N2 1/15
Monetary amount

Segment: CTT Transaction Totals

Position: 070
Loop:
Level: Summary
Usage: Optional
Max Use: 1
Purpose: To transmit a hash total for a specific element in the transaction set
Syntax Notes: 1 If either CTT03 or CTT04 is present, then the other is required.
2 If either CTT05 or CTT06 is present, then the other is required.
Semantic Notes:
Comments: 1 This segment is intended to provide hash totals to validate transaction completeness and
correctness.

Ref. Data
M CTT01 354 Number of Line Items M N0 1/6
Total number of line items in the transaction set

Segment: SE Transaction Set Trailer

Position: 080
Loop:
Level: Summary
Usage: Mandatory
Max Use: 1
Purpose: To indicate the end of the transaction set and provide the count of the transmitted segments
(including the beginning (ST) and ending (SE) segments)
Syntax Notes:
Semantic Notes:
Comments: 1 SE is the last segment of each transaction set.

Ref. Data
M SE01 96 Number of Included Segments M N0 1/10
Total number of segments included in a transaction set including ST and SE
segments
M SE02 329 Transaction Set Control Number M AN 4/9
Identifying control number that must be unique within the transaction set
functional group assigned by the originator for a transaction set

Segment: GE Functional Group Trailer

Position: 085
Loop:
Level: Summary
Usage: Mandatory
Max Use: 1
Purpose: To indicate the end of a functional group and to provide control information
Syntax Notes:
Semantic Notes: 1 The data interchange control number GE02 in this trailer must be identical to the same data
element in the associated functional group header, GS06.
Comments: 1 The use of identical data interchange control numbers in the associated functional group header
and trailer is designed to maximize functional group integrity. The control number is the same as
that used in the corresponding header.

Ref. Data
M GE01 97 Number of Transaction Sets Included M N0 1/6
Total number of transaction sets included in the functional group or
interchange (transmission) group terminated by the trailer containing this data
element
M GE02 28 Group Control Number M N0 1/9
Assigned number originated and maintained by the sender

Segment: IEA Interchange Control Trailer

Position: 100
Loop:
Level: Summary
Usage: Mandatory
Max Use: 1
Purpose: To define the end of an interchange of zero or more functional groups and interchange-related control
segments
Syntax Notes:
Semantic Notes:
Comments:

Ref. Data
M IEA01 I16 Number of Included Functional Groups M N0 1/5
A count of the number of functional groups included in an interchange
M IEA02 I12 Interchange Control Number M N0 9/9
A control number assigned by the interchange sender


Carpenter Invoice Example

Uploaded by

Copyright:

Available Formats

Carpenter Invoice Example

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Carpenter Invoice Example

Uploaded by

Copyright:

Available Formats

g GE Information Services

Electronic Commerce Service Center

810 Invoice/Garden Ridge-Trading Partner Specification

Functional Group ID= IN

130 ITD Terms of Sale/Deferred Terms of Sale O >1

sf810gmu_tp1.doc Page 1 of 19 Date Printed: 12/13/2010 4:47:00 PM

Transaction Set Notes

sf810gmu_tp1.doc Page 2 of 19 Date Printed: 12/13/2010 4:47:00 PM

Segment: ISA Interchange Control Header

Data Element Summary

sf810gmu_tp1.doc Page 3 of 19 Date Printed: 12/13/2010 4:47:00 PM

2815797901 - for production

sf810gmu_tp1.doc Page 4 of 19 Date Printed: 12/13/2010 4:47:00 PM

Segment: GS Functional Group Header

Data Element Summary

sf810gmu_tp1.doc Page 5 of 19 Date Printed: 12/13/2010 4:47:00 PM

positions 7-12 are the industry or trade association identifiers (optionally

sf810gmu_tp1.doc Page 6 of 19 Date Printed: 12/13/2010 4:47:00 PM

Segment: ST Transaction Set Header

Data Element Summary

sf810gmu_tp1.doc Page 7 of 19 Date Printed: 12/13/2010 4:47:00 PM

Segment: BIG Beginning Segment for Invoice

Data Element Summary

sf810gmu_tp1.doc Page 8 of 19 Date Printed: 12/13/2010 4:47:00 PM

Data Element Summary

sf810gmu_tp1.doc Page 9 of 19 Date Printed: 12/13/2010 4:47:00 PM

Data Element Summary

sf810gmu_tp1.doc Page 10 of 19 Date Printed: 12/13/2010 4:47:00 PM

Segment: ITD Terms of Sale/Deferred Terms of Sale

Data Element Summary

sf810gmu_tp1.doc Page 11 of 19 Date Printed: 12/13/2010 4:47:00 PM

Segment: IT1 Baseline Item Data (Invoice)

Data Element Summary

sf810gmu_tp1.doc Page 12 of 19 Date Printed: 12/13/2010 4:47:00 PM

VN Vendor's (Seller's) Item Number

sf810gmu_tp1.doc Page 13 of 19 Date Printed: 12/13/2010 4:47:00 PM

Segment: PID Product/Item Description

Data Element Summary

sf810gmu_tp1.doc Page 14 of 19 Date Printed: 12/13/2010 4:47:00 PM

Segment: TDS Total Monetary Value Summary

Data Element Summary

sf810gmu_tp1.doc Page 15 of 19 Date Printed: 12/13/2010 4:47:00 PM

Segment: CTT Transaction Totals

Data Element Summary

sf810gmu_tp1.doc Page 16 of 19 Date Printed: 12/13/2010 4:47:00 PM

Segment: SE Transaction Set Trailer

Data Element Summary

sf810gmu_tp1.doc Page 17 of 19 Date Printed: 12/13/2010 4:47:00 PM

Segment: GE Functional Group Trailer

Data Element Summary

sf810gmu_tp1.doc Page 18 of 19 Date Printed: 12/13/2010 4:47:00 PM

Segment: IEA Interchange Control Trailer

Data Element Summary

sf810gmu_tp1.doc Page 19 of 19 Date Printed: 12/13/2010 4:47:00 PM

You might also like