Federal implementation guideline for electronic data interchange · 2015. 11. 18. · Introduction:...

60
NIST I PUBLICATIONS NIST Special Publication 881-10 4 m III iiiiiiikiiiiii lliliiiliiilirlillilhilil liililililllllllllllllillll P ^ NBT QC 100 .U57 NO.881-10 1997 Federal Implementation Guideline for Electronic Data Interchange ASC X12 003040 Transaction Set 810 Invoice (Commercial Invoice) Implementation Convention U.S. DEPARTMENT OF COMMERCE Technology Administration National Institute of Standards and Teclinology

Transcript of Federal implementation guideline for electronic data interchange · 2015. 11. 18. · Introduction:...

Page 1: Federal implementation guideline for electronic data interchange · 2015. 11. 18. · Introduction: This Draft Standard forTrial Use containsthe formatand establishesthedatacontents

NIST

I PUBLICATIONS

NIST Special Publication 881-10

4mIII

iiiiiiikiiiiii lliliiiliiilirlillilhilil

liililililllllllllllllillll

P ^

NBTQC

100

.U57

NO.881-10

1997

Federal Implementation Guideline

for Electronic Data Interchange

ASC X12 003040 Transaction Set 810

Invoice (Commercial Invoice)

Implementation Convention

U.S. DEPARTMENT OF COMMERCETechnology Administration

National Institute of

Standards and Teclinology

Page 2: Federal implementation guideline for electronic data interchange · 2015. 11. 18. · Introduction: This Draft Standard forTrial Use containsthe formatand establishesthedatacontents
Page 3: Federal implementation guideline for electronic data interchange · 2015. 11. 18. · Introduction: This Draft Standard forTrial Use containsthe formatand establishesthedatacontents

NIST Special Publication 881-10

Federal Implementation Guideline

for Electronic Data Interchange

ASC X12 003040 Transaction Set 810

Invoice (Commercial Invoice)

Implementation Convention

Electronic Commerce Acquisition Program Management Office

Standard Management Committee - Secretariat

National Institute of Standards and Technology

Gaithersburg, MD 20899-0001

Editor: Dr. Jean-Philippe Favreau

March 1997

U.S. DEPARTMENT OF COMMERCEWilliam M. Daley, Secretary

Technology Administration

Mary L. Good, Under Secretary for Technology

National Institute of Standards and Technology

Arati Prabhakar, Director

Page 4: Federal implementation guideline for electronic data interchange · 2015. 11. 18. · Introduction: This Draft Standard forTrial Use containsthe formatand establishesthedatacontents

Reports on Information Technology

The National Institute of Standards and Technology (NIST)'s Information Technology Laboratory (ITL)

develops standards and guidelines, provides technical assistance, and conducts research for computers

and resources. As part of the overall federal effort to establish a single face to industry for conducting

electronic commerce, ITL has been designated as the organization responsible for coordinating the

development of Federal Implementation Conventions (ICs) for Electronic Data Interchange (EDI). ICs are

defined by functional-area experts who create and select options from standard EDI Transaction Sets to

yield the implementations to be used for practical EDI. These ICs are made available to federal agencies

and industry by electronic means and this Special Publication Series.

National Institute of Standards and Technology Special Publication 881-10Natl. Inst. Stand. Technol. Spec. Publ. 881-10, 56 pages (March 1997)

CODEN: NSPUE2

U.S. GOVERNMENT PRINTING OFFICEWASHINGTON: 1997

For sale by the Superintendent of Documents, U.S. Government Printing Office, Washington, DC 20402

Page 5: Federal implementation guideline for electronic data interchange · 2015. 11. 18. · Introduction: This Draft Standard forTrial Use containsthe formatand establishesthedatacontents

810 Invoice

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.

Notes:

1. Use tliis transaction set to transmit commercial invoices to a Federal Govenmient activity responsible for

initiating the payment.

2. Use a single occurrence of this transaction to invoice or provide adjustments for one or more deliveries or

service performances, provided to the Federal Goverrunent on one or more shipments.

3. Use to transmit commercial invoice data only from one invoice preparing party to one invoice receiving party.

4. Use to send a replacement invoice when a previously submitted invoice is incorrect. When used, cite code 05 in

BIG08.

Heading:

Pos.

No.

010

Seg.

IDST

NameTransaction Set Header

Req.

Des.

MMax.Use

1

Loop Notes and

Repeat Comments

020 BIG Beginning Segment for Invoice M 1

Not Used 030 NTE Note/Special Instruction F 100

040 CUR Currency O 1

Not Used 050 REF Reference Numbers O 12

Not Used 060 PER Administrative Communications Contact

UXi}> {f>.Ml

o 3

070 Nl Name o 1

080 N2 Additional Name Information o 2

090 N3 Address Information o 2

100 N4 Geographic Location o 1

110 REF Reference Numbers o 12

120 PER Administrative Communications Contact o 3

130 ITD Terms of Sale/Deferred Terms of Sale o 5

140 DTM Date/Time Reference o 10

150 FOB F.O.B. Related Instructions o 1

Not Used 160 PID Product^tem Description o 200

Not Used 170 MEA Measurements o 40

Not Used 180 PWK Paperwork o 25

Not Used 190 PKG Marking, Packaging, Loading 0 25

RELEASE - 003040FED01A August 31, 1994

Page 6: Federal implementation guideline for electronic data interchange · 2015. 11. 18. · Introduction: This Draft Standard forTrial Use containsthe formatand establishesthedatacontents

810 - Invoice (Commercial Invoice)

Not Used 200 L7 Tariff Reference O 1

210 AT Financial Accounting O 3

Not Used 212 BAL Balance Detail o 2 nl

Not Used 220 LM Code Source Information o 1

Not Used 230 LQ Industry Code M 100

Not Used 240 N9 O 1

Not Used 250 MSG M 1 A10

Detail:

Pos.

No.

Seg.

ID NameReq.

Des.

LoopMax.Use Repeat

Notes and

Comments

010 ITl Baseline Item Data ^Invoice) o 1

Not Used 012 CRC Conditions Indicator o 1

Not Used 015 OTY Quantity o 5 n2

Not Used 020 CUR Currency o 1

Not Used 030 IT3 Additional Item Data o 5

040 TXI Tax Information o 10

Not Used 050 CTP Pricing Information o 25

Not Used 059 MEA Measurements o

•. s

40

JOOQ

060 PID Product/Item Description

% \ V N s \ s

o 1

^^^^^^^^^^^

Not Used 070 MEA Measurements o 10

Not Used 080 PWK Paperwork. o 25

Not Used 090 PKG Marking, Packaging, Loading o 25

Not Used 100 P04 Item Physical Details 0 1

110 ITD Terms of Sale/Deferred Terms of Sale 0 2

120 REF Reference Numbers o >1

Not Used 130 PER Administrative Communications Contact o 5

Not Used 140 SDQ Destination Quantity o 500

150 DTM Date/Time Reference o 10

160 CAD Carrier Detail o >1

Not Used 170 L7 Tariff Reference o >1

Not Used 175 SR Advertising Schedule Requested 0

s • S %\ % A

1

. - ^ ^ iS, % ^ %\ ^ ^ i \

180

190

SAC

TXI

Service, Promotion, Allowance, or Charge

Information

Tax Information

o

o

1

10

. % Sa V

Not Used 200 SLN Sublme Item Detail o 1

Not Used 210 REF Reference Numbers o >1

Not Used 220 PID Product/Item Description o 1000

Not Used 230 SAC Service, Promotion, Allowance, or Charge

Information

o 25

RELEASE - 003040FED01A 2 August 31, 1994

Page 7: Federal implementation guideline for electronic data interchange · 2015. 11. 18. · Introduction: This Draft Standard forTrial Use containsthe formatand establishesthedatacontents

810 - Invoice (Commercial Invoice)

Not Used 235 TC2 Commodity O 2

MliN 1 Name f\\j 1

250 N2 Additional Name Information O 2

Address Information KJ 2

270 N4 Geographic Location o 1

Not Used 280 REF Reference Numbers o 12

Not Used 290 PER Administrative Communications Contact o 3

Not Used 300 LM Code Source Iivformaiion o \

Not Used 310 LQ Industry Code M 100

Summary:

Pos.

No.

010

Ses.

IDTDS

NameTotal Monetary Value Summary

Req.

Des.

M 1

Loop Notes and

Repeat Comments

020 TXI Tax Information O 10

030 CAD Carrier Detail O 1

040

050

SAC

TXI

Service, Promonon, Allowance, or Charge

Information

Tax Information

o

o

1

10

Not Used 060 ISS Invoice Shipment Summary o 5

070 CTT Transaction Totals M 1 n3

080 SB Transaction Set Trailer M 1

Transaction Set Notes

1. The BAL segment is to be used only if the code in BIG07 indicates that the transaction is a ^Monthly

Adjustinent"or"

' Special Handling Adjustment" invoice.

2. The QTY segment is used to specify a quantity of units which are expected as payments, e.g., trade-ins or

returns.

3. Number of line items (CTTOl) is the accumulation of the number of ITl segments. If used, hash total

(CTT02) is the sum of the value of quantities invoiced (IT 102) for each ITl segment.

RELEASE - 003040FED01A 3 August 31, 1994

Page 8: Federal implementation guideline for electronic data interchange · 2015. 11. 18. · Introduction: This Draft Standard forTrial Use containsthe formatand establishesthedatacontents

810 - Invoice (Commercial Invoice)

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Notes:

Syntax Notes:

Semantic Notes:

Comments:

ST Transaction Set Header

010

Heading

Mandatory

1

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

1 The transaction set identifier (STOl) used by the translation routines of the

interchange partners to select the appropriate transaction set definition (e.g., 810

selects the invoice transaction set).

Data Element SummaryRef.

Pes.

» STOl

» ST02

Data

Element

143

329

Attributes

M ID 3/3

NameTransaction Set Identifier Code

Code uniquely identifying a Transaction Set.

810 X12.2 Invoice

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

Use to transmit a unique number assigned by the originator ofthe transaction

set. This number may be system generated.

RELEASE - 003040FED01A 4 August 31, 1994

Page 9: Federal implementation guideline for electronic data interchange · 2015. 11. 18. · Introduction: This Draft Standard forTrial Use containsthe formatand establishesthedatacontents

810 - Invoice (Commercial Invoice)

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Notes:

Syntax Notes:

Semantic Notes:

Comments:

BIG Beginning Segment for Invoice

020

Heading

Mandatory

1

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

numbers and dates.

1 BIG10 indicates the consolidated invoice niunber. When BIG07 contains code CI,

BIG10 is not used.

1 BIG07 is used only to further define the type of invoice when needed.

Ref.

Pes.

» BIGOl

» BIG02

Data

Element

245

76

Attributes

M DT 6/6

Data Element Summary

NameInvoice Date

Invoice Issue Date.

Use to identify the date the transaction set was created. In the context ofa

commercial invoice, this date will represent the date ofthe invoice.

Invoice Number M AN 1/22

Identifying number assigned by issuer.

Use to uniquely identify the invoice transaction to an issuer. The invoice

number may not be duplicated by an issuer in an original transaction (BIG08,

code 00) within a 12 month period. Same number can be used ifissuing an

amended invoice (BIG08 is code 02, 03, or 04).

BIG03

» BIG04

BIG05

BIG06

» BIG07

323 Purchase Order Date O DT 6/6

Date assigned by the purchaser to Purchase Order.

When BIG05 is used, cite the date ofthe delivery order, call or release. When

BIG05 is not used, cite the date ofthe procurement instrument in BIG04.

324 Purchase Order Number O AN 1/22

Identifying number for Purchase Order assigned by the orderer/purchaser.

Use to identify the procurement instrument identification number (PIIN) other

than an order against a basic procurement instrument, e.g., delivery order,

release, or call. For purchase orders, cite the order number. For delivery, cite

the basic procurement instrument identification number (e.g., the contract,

grant, cooperative agreement, etc., number) and cite the delivery order or call

number in BIG05.

328 Release Number O AN 1/30

Number identifying a release against a Purchase Order previously placed by the

parties involved in the transaction.

Use to identify a delivery or task order, call or release number, (e.g., the

Supplemental PIIN) against the basic procurement instrument cited in BIG04.

327 Change Order Sequence Number O AN 1/8

Number assigned by the orderer identifying a specific change or revision to a

previously transmitted transaction set.

Use, as applicable, to identify a modification number to the instrument in

BIG05. IfBIG05 is blank, use the PIIN in BIG04.

640 Transaction Type Code O ID 2/2

RELEASE - 003040FED01A 5 August 31, 1994

Page 10: Federal implementation guideline for electronic data interchange · 2015. 11. 18. · Introduction: This Draft Standard forTrial Use containsthe formatand establishesthedatacontents

810 - Invoice (Commercial Invoice)

Code specifying the type of transaction.

CI Consolidated Invoice

CN Credit Invoice

CR Credit MemoDI Debit Invoice

DR Debit Memo» BIG08 353 Transaction Set Purpose Code O ID 2/2

Code identifying purpose of transaction set.

00 Original

Use to indicate the initial submission ofan original

invoice.

01 Cancellation

Use to indicate the cancellation ofa previously

submitted invoice.

02 Add

Use to indicate an amended invoice that contains only

additions to a previously transmitted invoice.

03 Delete

Use to indicate an amended invoice that contains only

deletionsfrom a previously transmitted invoice.

04 Change

Use to indicate an amended invoice that contains a

combination ofadditions and deletions to a previously

transmitted invoice. This code is also used to indicate

data in a previously transmitted invoice has changed,

e.g., the quantity invoiced and the total invoiced

amount. In effect the old quantity and invoiced amount

are deleted and the new quantity and invoiced amount

are added.

05 Replace

07 Duplicate

Use to indicate a duplicate submission. Use only when

informed that the original invoice was not received.

BIG09 306 Action Code O ID 1/2

Code indicating type of action.

F Final

Use to indicate the final invoice. Leave blankfor

partial invoices.

X BIGIO 76 Invoice Number O AN 1/22

Identifying number assigned by issuer.

RELEASE - 003040FED0 1A 6 August 3 1 , 1 994

Page 11: Federal implementation guideline for electronic data interchange · 2015. 11. 18. · Introduction: This Draft Standard forTrial Use containsthe formatand establishesthedatacontents

810 - Invoice (Commercial Invoice)

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Notes:

Syntax Notes:

Semantic Notes:

Comments:

CUR Currency

040

Heading

Optional

1

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

Use this l/CUR/040 segment to identify the currency in which payment will be made if

in other than U.S. dollars.

1

2

3

4

5

6

7

8

9

10

If CUR08 is present, then CUR07 is required.

If CUR09 is present, then CUR07 is required.

IfGURU is present, then CURIO is required.

If CURI2 is present, then CURIO is required.

If CURI4 is present, then CURI3 is required.

If CURI5 is present, then CUR13 is required.

If CUR17 is present, then CUR16 is required.

IfCUR 18 is present, then CUR 16 is required.

If CUR20 is present, then CUR 1 9 is required.

If CUR2I is present, then CUR19 is required.

1 See Figures Appendix for examples detailing the use of the CUR segment.

»Ref.

Pes.

CUROl

Data

Element

98

Data Element Summary

Name Attributes

Entity Identifier Code M ID 2/2

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

BY Buying Party (Purchaser)

Use to indicate that the purchasing office (e.g., in the

contract or order), authorizedpayment in the currency

cited in CUR02.

PR Payer

Use to indicate that the paying office authorized

payment in the currency cited in CUR02.

»

X

X

X

X

X

CUR02 100 Currency Code M ID 3/3

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

Use the appropriate code to specify the currency that will be used to make

payment.

CUR03 280 Exchange Rate O R 4/6

Value to be used as a multiplier conversion factor to convert monetary value

from one currency to another.

CUR04 98 Entity Identifier Code O ID 2/2

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

CUR05 100 Currency Code O ID 3/3

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

CUR06 669 Currency Market/Exchange Code O ID 3/3

Code identifying the market upon which the currency exchange rate is based.

CUR07 374 Date/Time Qualifier X ID 3/3

RELEASE - 003040FED01A 7 August 31, 1994

Page 12: Federal implementation guideline for electronic data interchange · 2015. 11. 18. · Introduction: This Draft Standard forTrial Use containsthe formatand establishesthedatacontents

810 - Invoice (Conmiercial Invoice)

X

X

CUR08

CUR09

O DT 6/6

X CURIO

X CURll

X CUR12

X CUR13

X CUR14

X CUR15

X CUR16

X CUR17

X CUR18

X CUR19

X CUR20

X CUR21

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

373 Date

Date (YYMMDD).

337 Time O 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)

374 Date/Time Qualifier X ID 3/3

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

373 Date O DT 6/6

Date (YYMMDD).

337 Time O 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)

374 Date/Time Qualifier X ID 3/3

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

373 Date O DT 6/6

Date (YYMMDD).

337 Time O 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)

374 Date/Time Qualifier X ID 3/3

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

373 Date

Date (YYMMDD).

337 Time

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)

374 Date/Time Qualifier X ID 3/3

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

373 Date O DT 6/6

Date (YYMMDD).

337 Time O 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)

O DT 6/6

O TM 4/8

RELEASE - 003040FED01A 8 August 31, 1994

Page 13: Federal implementation guideline for electronic data interchange · 2015. 11. 18. · Introduction: This Draft Standard forTrial Use containsthe formatand establishesthedatacontents

810 - Invoice (Commercial Invoice)

Segment: Nl Name

Position: 070

Loop: NlLevel: Heading

Usage: Optional

Max Use: 1

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

Notes: 1. Whenever possible, address information should be transmitted using code values

contained in a combination of the NlOl and N103/4 data elements. Use N102 and N2-

N4 segments only when it is necessary to transmit the fiill address. For example, if a

vendor can be identified by a DUNs number, it is not necessary to transmit the vendor's

full address since the relationship between the DUNs number and the vendor's address

can be established by accessing a data base in which the information is stored, having

been put there at the time the vendor electronically registered as a federal government

trading partner.

2. At least 2 iterations of this l/Nl/070 loop are required using codes PE and PO.

3. Use to identify a ship-to-addressee when the invoice contains multiple line items and

the address is applicable to all line items. Use the 2/N 1/240 loop when the invoice or

the ship-to address varies among the line items.

Syntax Notes:

Semantic Notes:

Comments:

4. Use the l/Nl/070 loop to identify organizations or people that apply to all of the line

items, or are not applicable at the line item level. When the addresses vary by line item,

use the 2/N1/240 loop.

1 At least one of N102 or N103 is required.

2 If either N103 or N104 is present, then the other is required.

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 NlOl.

»Ref.

Pes.

NlOl

Data Element SummaryData

Element

98

Name Attributes

Entity Identifier Code M ID 2/2

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

MQ Metering Location

Use to indicate the location ofthe meter applicable to

the invoice.

PE

PO

RI

Payee

Use to indicate the party submitting the invoice.

Party to Receive Invoice for Goods or Services

Use to indicate where the invoice should be mailed.

Remit To

Use to indicate a specific remit-to address when

multiple remit-to addresses were provided as a part of

the trading partner registration process. Do not use

when only a single remit-to address was provided as a

RELEASE - 003040FED01A 9 August 31, 1994

Page 14: Federal implementation guideline for electronic data interchange · 2015. 11. 18. · Introduction: This Draft Standard forTrial Use containsthe formatand establishesthedatacontents

810 - Invoice (Commercial Invoice)

part ofthe registration process.

N102

» N103

»

X

X

N104

N105

N106

ST Ship To

Use to indicate the ship-to address when the invoice

contains multiple line items and the address is the same

for all. When the invoice varies by line item, use the

2/N1/240 loop.

SV Service Performance Site

When services are contracted for, this describes the

organization for whom or location address at which

those services will be performed

Use to indicate a location where a service, (e.g., data

entry) was performed.

93 Name X AN 1/35

Free-form name.

Use only when NlOl is either code ST or code SV to provide a text name. Donot use when the ship-to address can be identified by a code in N103/04.

66 Identification Code Qualifier X ID 1/2

Code designating the system/method of code structure used for Identification

Code (67).

1 D-U-N-S Number, Dun & Bradstreet

Use in all transmissions to identify the DUNS number

ofthe invoicing party and Federal Facility.

10 Department of Defense Activity Address Code

(DODAAC)Use to indicate either a Department ofDefense Activity

Address Code or a Civilian Agency Activity Address

Code.

33 Commercial and Govenmient Entity (CAGE)

Use to indicate vendors with CAGE codes.

A2 Military Assistance Program Address Code (MAPAC)

Contained in the Military Assistance Program Address

Directory (MAPAD); represents the location of an

entity

Use to indicate aMAPAC address.

FA Facility Identification

Use to indicate a vendorfacility that cannot be

identified by either a CAGE code or a DUNs number.

67 Identification Code X AN 2/17

Code identifying a party or other code.

706 Entity Relationship Code O ID 2/2

Code describing entity relationship.

98 Entity Identifier Code O ID 2/2

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

RELEASE - 003040FED01A 10 August 31, 1994

Page 15: Federal implementation guideline for electronic data interchange · 2015. 11. 18. · Introduction: This Draft Standard forTrial Use containsthe formatand establishesthedatacontents

810 - Invoice (Conunercial Invoice)

Segment: N2 Additional Name Information

Position: 080

Loop: NlLevel: Heading

Usage: Optional

Max Use: 2

Purpose: To specify additional names or those longer than 35 characters in length

Notes: 1. This segment is not necessary when the cited party can be identified by a code value

in NlOl/03/04.

Syntax Notes:

Semantic Notes:

Comments:

2. Use, as needed, only when NlOl is code ST or SV and that party cannot be identified

by coded means.

»Ref.

Pes.

N201

N2G2

Data

Element

93

93

Data Element Summary

NameNameFree-form name.

Name

Free-form name.

Use only when NlOl is either code ST or code SV to provide a text name,

not use when the ship-to address can be identified by a code in N103/04

Attributes

M AN 1/35

O AN 1/35

Do

RELEASE - 003040FED01A 11 August 31, 1994

Page 16: Federal implementation guideline for electronic data interchange · 2015. 11. 18. · Introduction: This Draft Standard forTrial Use containsthe formatand establishesthedatacontents

810 - Invoice (Commercial Invoice)

Segment: N3 Address Information

Position: 090

Loop: NlLevel: Heading

Usage: Optional

Max Use: 2

Purpose: To specify the location of the named party

Notes: 1. This segment is not necessary when the cited party can be identified by a code value

in NIO 1/03/04.

Syntax Notes:

Semantic Notes:

Comments:

2. Use, as needed, only when NlOl is code ST or SV and that party caimot be identified

by coded means.

»Ref.

Pes.

N301

N302

Data

Element

166

166

Data Element Summary

NameAddress Information

Address information

Address Information

Address information

Attributes

M AN 1/35

O AN 1/35

RELEASE - 003040FED01A 12 August 31, 1994

Page 17: Federal implementation guideline for electronic data interchange · 2015. 11. 18. · Introduction: This Draft Standard forTrial Use containsthe formatand establishesthedatacontents

810 - Invoice (Commercial Invoice)

Segment: N4 Geographic Location

Position: 100

Loop: NlLevel: Heading

Usage: Optional

Max Use: 1

Purpose: To specify the geographic place of the named party

Notes: 1. This segment is not necessary when the cited party can be identified by a code value

in NIG 1/03/04.

2. Use, as needed, only when NlOl is code ST or SV and that party cannot be identified

by coded means.

3. When identifying a APO/FPO, N401 carries the APO/FPO city name and N403carries the ZIP code of the city.

Syntax Notes:

Semantic Notes:

Comments:

1 If N406 is present, then N405 is required.

1 A combination of either N401 through N404 (or N405 and N406) may be adequate

to specify a location.

2 N402 is required only if city name (N401) is in the USA or Canada.

Data Element Summary

X

X

Ref.

Pes.

N401

N402

N403

N404

N405

N406

Data

Element Name Attributes

O AN 2/3019 City Name

Free-form text for city name.

156 State or Province Code O ID 2/2

Code (Standard State/Province) as defined by appropriate government agency.

116 Postal Code O ID 3/9

Code defining international postal zone code excluding punctuation and blanks

(zip code for United States).

26 Country Code O ID 2/3

Code identifying the country.

A conversion table may be required to convert agency codes to ASCX12 codes.

309 Location Qualifier X ID 1/2

Code identifying type of location.

310 Location Identifier O AN 1/30

Code which identifies a specific location.

RELEASE - 003040FED01A 13 August 31, 1994

Page 18: Federal implementation guideline for electronic data interchange · 2015. 11. 18. · Introduction: This Draft Standard forTrial Use containsthe formatand establishesthedatacontents

810 - Invoice (Commercial Invoice)

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Notes:

Syntax Notes:

Semantic Notes:

Comments:

REF Reference Numbers

110

Nl

Heading

Optional

12

To specify identifying numbers.

This 1/REF/l 10 segment can be used to identify numbers that apply to either the cited

party or all of the line items. When the reference number does not apply to a cited party,

or varies by line item, use the 2/REF/120 segment.

1 At least one ofREF02 or REF03 is required.

Data Element SummaryRef. Data

Des» Element Name Attributes

» REFOl 128 Reference Number Qualifier M ID 2/2

Code qualifying the Reference Number.

1. Use, as applicable, to identify the shipment number, replacement shipment

number andfinal shipment indicator.

2. Use, as applicable, to identify reference numbers such as the shipment

number, customer reference number, etc., applicable to the cited party.

45 Old Account Number

Identifies accounts being changed

Use only when applicable, and only when agreed to by

the trading partners.

46 Old Meter Number

Identifies meters being removed

Use only as applicable, and only when agreed to by the

trading partners.

55 Sequence Number

Use to indicate the suffix letter associated with a

replacement shipment (i.e., when transmitting the letter

A to indicate the first replacement shipment).

(Applicable to DoD invoice only.)

AA Accounts Receivable Statement Number

BL Government Bill of Lading

CR Customer Reference Number

Use to indicate a customer's internal reference number.

FS Final Sequence Number

Use to indicate the suffix letter associated with afinal

shipment number, (i.e., when transmitting the letter Z

to indicate a final shipment( (Applicable to DoDinvoice only.)

MG Meter Number

RELEASE - 003040FED01A 14 August 31, 1994

Page 19: Federal implementation guideline for electronic data interchange · 2015. 11. 18. · Introduction: This Draft Standard forTrial Use containsthe formatand establishesthedatacontents

810 - Invoice (Commercial Invoice)

Ul Original Invoice Number

PQ Payee Identincation

RB Rate code number

SE Serial Number

SI Shipper's Identifying Number for Shipment (SID)

A unique number (to the shipper) assigned by the

shipper to identify the shipment

Use to identify the shipment number.

» REF02 127 Reference Number X AN 1/30

Reference number or identification number as defined for a particular

Transaction Set, or as specified by the Reference Number Qualifier.

X REF03 352 Description X AN 1/80

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

RELEASE - 003040FED01A 15 August 31, 1994

Page 20: Federal implementation guideline for electronic data interchange · 2015. 11. 18. · Introduction: This Draft Standard forTrial Use containsthe formatand establishesthedatacontents

810 - Invoice (Commercial Invoice)

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Notes:

Syntax Notes:

Semantic Notes:

Comments:

PER Administrative Communications Contact

120

NlHeading

Optional

3

To identify a person or office to whom administrative communications should be

directed

1 If either PER03 or PER04 is present, then the other is required.

2 If either PER05 or PER06 is present, then the other is required.

Data Element SummaryRef.

Pes.

» PEROl

Data

Element

366

X PER02

PER03

93

365

PER04

PER05

364

365

PER06 364

Name Attributes

M ID 2/2

ID 2/2

Contact Function CodeCode identifying the major duty or responsibility of the person or group named.

AF Authorized Financial Contact

Use to indicate the communication number to be

contacted with questions arisingfrom the submission of

this invoice. Use only when the contact differsfrom

one provided as a part ofthe registration process.

Name O AN 1/35

Free-form name.

Communication Number Qualifier

Code identifying the type of communication number.

EM Electronic Mail

EX Telephone Extension

FX Facsimile

IT International Telephone

TE Telephone

Communication Number

Complete communications number including country or area code when

applicable.

Communication Number Qualifier

Code identifying the type of communication number.

EM Electronic Mail

EX Telephone Extension

FX Facsimile

IT International Telephone

TE Telephone

Communication Number

Complete communications number including country or area code when

applicable.

X AN 1/80

ID 2/2

X AN 1/80

RELEASE - 003040FED01A 16 August 31, 1994

Page 21: Federal implementation guideline for electronic data interchange · 2015. 11. 18. · Introduction: This Draft Standard forTrial Use containsthe formatand establishesthedatacontents

1

810 - Invoice (Commercial Invoice)

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Notes:

ITD Terms of Sale/Deferred Terms of Sale

130

Heading

Optional

5

To specify terms of sale.

1. Use this l/ITD/130 segment when the discount terms apply to all of the line items. If

the discoimt terms vary by line item, use the 2/ITD/l 10 segment.

2. Payment method was provided at time of registration. Changes to that data must be

made by submitting a registration data change using the 838 transaction set.

3. Use only when a discount is applicable. Do not transmit this segment when a

discount is not applicable.

Syntax Notes:

Semantic Notes:

Comments:

1 If ITD03 is present, then at least one of ITD04 ITD05 or ITD 1 3 is required.

2 If ITD08 is present, then at least one of ITD04 ITD05 or ITD 1 3 is required.

3 If ITD09 is present, then at least one of ITD 10 or ITD 1 1 is required.

1 ITD 15 is the percentage applied to a base amount used to determine a late payment

charge.

1 If the code in ITDOl is 04, then 1TD07 or ITD09 is required and either ITDIO or

ITDl 1 is required; if the code in ITDOI is 05, then ITD06 or ITD07 is required.

Ref.

Pes.

ITDOl

Data Element SummaryData

Element Name Attributes

O ID 2/2336 Terms Type Code

Code identifying type of payment terms.

21 Fast Pay

Code indicating that an invoice is subject to accelerated

payment

Use to indicate FASTPAYprocedures are applicable

only when thatprocedure has been authorized in the

contract or orderfor which this invoice is being

submitted.

ITD02

ITD03

X ITD04

ITD05

333 Terms Basis Date Code O ID 1/2

Code identifying the beginning of the terms period.

Use the same code as the one indicated in ITD02 ofthe Contract Solicitation

Response (843 transaction set). Use ofthis segment shall not override the

terms and conditions ofthe contract, order, or Prompt Payment Act.

Refer to 003040 Data Element Dictionary for acceptable code values.

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.

The amount shown is in percent, e.g., two and a halfpercent should be shown

as 2.5 (two pointfive). Do not write the percent as . 025.

370 Terms Discount Due Date X DT 6/6

Date payment is due if discount is to be earned.

351 Terms Discount Days Due X NO 1/3

RELEASE - 003040FED01A 17 August 31, 1994

Page 22: Federal implementation guideline for electronic data interchange · 2015. 11. 18. · Introduction: This Draft Standard forTrial Use containsthe formatand establishesthedatacontents

810 - Invoice (Commercial Invoice)

X

X

X

X

X

X

X

ITD06

ITD07

ITD08

ITD09

ITDIO

ITDll

ITD12

ITD13

ITD14

ITD15

Number of days in the terms discount period by which payment is due if terms

discount is earned.

446 Terms Net Due Date O DT 6/6

Date when total invoice amount becomes due.

386 Terms Net Days O NO 1/3

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

362 Terms Discount Amount O N2 1/10

Total amount of terms discount.

Use, ifneeded, to prevent differences that can resultfrom rounding off

methods.

388 Terms Deferred Due Date

Date deferred payment or percent of invoice payable is due.

389 Deferred Amount DueDeferred amount due for payment.

342 Percent of Invoice Payable

Amount of invoice payable expressed in percent.

352 Description

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

765 Day of Month X NO 1/2

The numeric value of the day of the month between 1 and the maximum day of

the month being referenced.

107 Payment Method Code O ID 1/1

Code identifying type ofpayment procedures.

954 Percent O R 1/10

Percentage expressed as a decimal

O DT 6/6

X N2 1/10

X R 1/5

O AN 1/80

RELEASE - 003040FED01A 18 August 31, 1994

Page 23: Federal implementation guideline for electronic data interchange · 2015. 11. 18. · Introduction: This Draft Standard forTrial Use containsthe formatand establishesthedatacontents

810 - Invoice (Conunercial Invoice)

Segment: DTM Date/Time Reference

Position: 140

Loop:

Level: Heading

Usage: Optional

Max Use: 10

Purpose: To specify pertinent dates and times

Notes: 1. Use this l/DTM/140 segment to specify dates if they apply to all of the line items in

the invoice. When the dates vary by line item, use the 2/DTM/150 segment.

2. Use two iterations of the segment when a range of dates (expressed as period start -

period end, is required).

Syntax Notes:

Semantic Notes:

Comments:

1 At least one ofDTM02 DTM03 or DTM06 is required.

2 If either DTM06 or DTM07 is present, then the other is required.

»Ref.

Pes.

DTMOl

Data

Element

374

DTM02

DTM03

Data Element Summary

NameDate/Time Qualifier

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

Attributes

M ID 3/3

Oil Shipped

035 Delivered

135 Booking

Use to indicate a billing revenue period. When used,

cited the last day ofthe period.

150 Service Period Start

Use to indicate the performance commencement date

for a line item that is ordering a service.

151 Service Period End

Use to indicate the performance completion datefor a

line item that is ordering a service.

186 Invoice Period Start

When the billing period covered by an invoice begins

187 Invoice Period End

When the billing period covered by an invoice ends

266 Base

The start of base date for a calendar reference - all

dates fall after it

Use to indicate a billing demand month. When used,

cite the last day ofthe applicable month.

373 Date X DT 6/6

Date (YYMMDD).

337 Time X 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)

RELEASE - 003040FED01A 19 August 31, 1994

Page 24: Federal implementation guideline for electronic data interchange · 2015. 11. 18. · Introduction: This Draft Standard forTrial Use containsthe formatand establishesthedatacontents

810 - Invoice (Commercial Invoice)

DTM04

X DTM05

X DTM06

X DTM07

623 Time Code O ID 2/2

Code identifying the time. In accordance with International Standards

Organization standard 8601, time can be specified by a + or - and an indication

in hours in relation to Universal Time Coordinate (UTC) time. Since + is a

restricted character, + and - are substituted by P andM in the codes that follow.

624 Century O NO 2/2

The first two characters in the designation of the year (CCYY).

1250 Date Time Period Format Qualifier X ID 2/3

Code indicating the date format, time format, or date and time format.

1251 Date Time Period X AN 1/35

Expression of a date, a time, or range of dates, times or dates and times.

RELEASE - 003040FED01A 20 August 31, 1994

Page 25: Federal implementation guideline for electronic data interchange · 2015. 11. 18. · Introduction: This Draft Standard forTrial Use containsthe formatand establishesthedatacontents

810 - Invoice (Commercial Invoice)

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Notes:

Syntax Notes:

Semantic Notes:

FOB F.O.B. Related Instructions

150

Heading

Optional

1

To specify transportation instructions relating to shipment

This segment is not necessary when the order is for service.

1

2

3

4

1

2

3

4

IfFOB03 is present, then FOB02 is required.

IfFOB04 is present, then FOB05 is required.

IfFOB07 is present, then FOB06 is required.

IfFOB08 is present, then FOB09 is required.

FOBOI indicates which party will pay the carrier.

FOB02 is the code specifying transportation responsibility location.

FOB06 is the code specifying the title passage location.

FOB08 is the code specifying the point at which the risk of loss transfers. This maybe different than the location specified in FOB02/FOB03 and FOB06/FOB07.

Comments:

»Ref.

Pes.

FOBOI

Data

Element

146

X

X

X

X

X

X

FOB02

FOB03

FOB04

FOB05

FOB06

FOB07

309

352

334

335

309

352

Attributes

M ID 2/2

Data Element Summary

NameShipment Method of Payment

Code identifying payment terms for transportation charges.

BP Paid by Buyer

The buyer agrees to the transportation payment term

requiring the buyer to pay transportation charges to a

specified location (origin or destination location)

Use to indicate that the FOB point is origin.

PE Prepaid and Summary Bill

Use to indicate that the contract or order authorizes

the selling party to prepay and add transportation

charges to the invoice.

PS Paid by Seller

The seller agrees to the transportation payment term

requiring the seller to pay transportation charges to a

specified location (origin or destination location)

Use to indicate that the FOB point is destination.

Location Qualifier X ID 1/2

Code identifying type of location.

Description O AN 1/80

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

Transportation Terms Qualifier Code O ID 2/2

Code identifying the source of the tiansportation terms.

Transportation Terms Code X ID 3/3

Code identifying the tiade terms which apply to the shipment tiansportation

responsibility.

Location Qualifier X ID 1/2

Code identifying type of location.

Description O AN 1/80

RELEASE - 003040FED01A 21 August 31, 1994

Page 26: Federal implementation guideline for electronic data interchange · 2015. 11. 18. · Introduction: This Draft Standard forTrial Use containsthe formatand establishesthedatacontents

810 - Invoice (Commercial Invoice)

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

X FOB08 54 Risk of Loss Qualifier O ID 2/2

Code specifying where responsibility for risk of loss passes.

X FOB09 352 Description X AN 1/80

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

RELEASE - 003040FED01A 22 August 31, 1994

Page 27: Federal implementation guideline for electronic data interchange · 2015. 11. 18. · Introduction: This Draft Standard forTrial Use containsthe formatand establishesthedatacontents

810 - Invoice (Commercial Invoice)

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Notes:

AT210

Financial Accounting

Syntax Notes:

Semantic Notes:

Comments:

Heading

Optional

3

To transmit financial accoimting data

1. Use this l/AT/210 segment to identify the appropriation reimbursed and disbursed

when the cited appropriation data applies to all line items. When the appropriation data

varies by line item use the 2/REF/120 segment.

2. Only use when the purchase order has appropriation data in the l/REF/050 segment,

code AT.

1 AT09 identifies unique local activity financial accounting information

»

Ref.

Pes.

ATOl

AT02

AT03

AT04

AT05

AT06

AT07

AT08

AT09

Data

Element

1281

1282

1283

1284

1285

1286

1287

1288

Data Element Summary

Name Attributes

352

Fund Code O ID 2/2

Code identifying a specific appropriation or fund account to be charged or

credited

Treasury Symbol Number O AN 7/21

Number identifying a department, fiscal year, and appropriation limit for a

standard accounting classification coding structure

Budget Activity Number O AN 1/16

Number identifying an administrative subdivision of funds against which a

transaction is to be charged for a standard accoimting classification coding

structure

Object Class Number O AN 3/12

Number identifying the nature of the goods or services acquired and a specific

office or organization using resources for a standard accounting classification

coding structure

Reimbursable Source Number O AN 1/3

Number identifying the source of an appropriation or fund reimbursement for a

standard accounting classification coding structure

Transaction Reference Number O AN 4/20

Number identifying an original request for goods and services to the matching

financial transaction for a standard accounting classification coding structure

Accountable Station Number O AN 3/8

Number identifying an office responsible for entering a financial transaction

into the applicable accounting system for a standard accounting classification

coding structure

Paying Station Number O AN 8/14

Number identifying an office responsible for making a payment or collection

and the corresponding voucher number under which the action was taken for a

standard accounting classification coding structure

Description O AN 1/80

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

RELEASE - 003040FED01A 23 August 31, 1994

Page 28: Federal implementation guideline for electronic data interchange · 2015. 11. 18. · Introduction: This Draft Standard forTrial Use containsthe formatand establishesthedatacontents

810 - Invoice (Commercial Invoice)

Segment: ITl Baseline Item Data (Invoice)

Position: 010

Loop: ITl

Level: Detail

Usage: Optional

Max Use: 1

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

transactions.

Notes: 1. Use multiple iterations of this 2/ITl/OlO loop to provide invoice data for a specific

line item. Allowances or charges identifiable to a line item will be included in that

line's 2/SAC/180 loop. Invoice level of allowances or charges, that is, allowances or

charges not identifiable to a specific item or line of billing, will be included in the

3/SAC/040 loop.

2. Use as many 235/234 pairs as necessary to describe the item being invoiced.

Syntax Notes:

Semantic Notes:

Comments:

3. When billing for metered services, on accounts with more that one meter, each meter

charge should be detailed in a separate iteration of the ITl loop.

1 If IT106 is present, then IT107 is required.

2 If IT108 is present, then IT109 is required.

3 If ITl 10 is present, then ITl 1 1 is required.

4 If ITl 12 is present, then ITl 13 is required.

5 If ITl 14 is present, then ITl 15 is required.

6 If ITl 16 is present, then ITl 17 is required.

7 If ITl 18 is present, then ITl 19 is required.

8 If IT 120 is present, then ITl 21 is required.

9 If IT122 is present, then IT123 is required.

10 If IT124 is present, then IT125 is required.

1 ITIOI is the purchase order line item identification.

1 Element 235/234 combinations should be interpreted to include products and/or

services. See the Data Dictionary for a complete list of ID's.

2 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.

Ref.

Pes.

ITIOI

»

»

IT102

IT103

Data

Element

350

358

355

Data Element Summary

Name Attributes

Assigned Identification O AN 1/11

Alphanumeric characters assigned for differentiation within a transaction set.

Use to identify the CLIN, SUBCLIN, or ELIN or other number identifying the

line item.

Quantity Invoiced M R 1/10

Number of units invoiced (supplier units).

When billingfor metered services, the quantity invoiced is the number ofunits

ofmeter usage, (e.g., 1,000 kilowatts).

Unit or Basis for Measurement Code M ID 2/2

Code specilying the units in which a value is being expressed, or maimer in

which a measurement has been taken

7. Use to identify the unit ofissuefor the quantity listed in IT] 02.

2. While any appropriate code, may be used, code SX is preferred

RELEASE - 003040FED01A 24 August 31, 1994

Page 29: Federal implementation guideline for electronic data interchange · 2015. 11. 18. · Introduction: This Draft Standard forTrial Use containsthe formatand establishesthedatacontents

810 - Invoice (Conunercial Invoice)

SX Shipment

Use this code when IT101 is a line itemfor prepaid transportation charges.

Use the 2/SAC/180 segment when not prepaid and add.

3. A conversion table may be required to convert agency codes to codes use by

ASCX12.

Refer to 003040 Data Element Dictionary for acceptable code values.

» IT104 212 Unit Price M R 1/14

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

Cite the contract or order unit price. In those cases where the line item was

purchased without charge, cite the number "0". Use a decimal point to indicate

amounts that are not in whole dollars.

X IT105 639 Basis of Unit Price Code O ID 2/2

Code identilying the type of unit price for an item.

» IT106 235 Product/Service ro Qualifier O ID 2/2

Code identifying the type/source of the descriptive number used in

Product/Service ID (234).

I. Use only codes that were contained in the contract or order. For example,

ifthe item being invoiced was ordered by its National Stock Number, (code FS),

use code FSfollowed by the National Stock Number ofthe item. Descriptions

should be kept to a minimum essential to identify the item for payment

purposes. While any code may be used, thefollowing codes are preferred:

A8 Exhibit Line Item NumberAK Refined Product Code

CG Commodity Grouping

Use to indicate a commodity code

CL Color

CN Commodity NameFS National Stock Number

The NSN shall be transmitted as a continuous set ofnumbers, and without

dashes

FT Federal Supply Classification

See Code Source 27 in the ASCX12 standardsfor the FSC codes

KA Engineering Data List

KB Data Category Code

LT Lot Number

MF Manufacturer

Use to indicate the manufacturer ofthe cited line item

MG Manufacturer's Part Number

Use, as applicable, to indicate the manufacturer's part number assigned to the

invoiced item

MM Motor Equipment Manufacturing Association (MEMA) Product Type

Code

MN Model Number

Nl National Drug Code in 4-4-2 Format

RELEASE - 003040FED01A 25 Augusts!, 1994

Page 30: Federal implementation guideline for electronic data interchange · 2015. 11. 18. · Introduction: This Draft Standard forTrial Use containsthe formatand establishesthedatacontents

810 - Invoice (Commercial Invoice)

N2 National Drug Code in 5-3-2 Format

N3 National Drug Code in 5-4-1 Format

N4 National Drug Code in 5-4-2 Format

ND National Drug Code (NDC)

PD Part Number Description

Use to indicate a clear text description ofan item

PU Part Reference Number

RC Returnable Container No.

SN Serial NumberSV Service Render

Use to indicate a clear text description ofa service being invoiced

SW Stock Number

Use to indicate a local stock number

SZ Vendor Alphanumeric Size Code (NRMA)UK U.P.C./EAN Shipping Code Container Code (1-2-5-5-1)

VP Vendor'r (Selller's) Part Number

ZB Commercial and Government Entity (CAGE) Code

2. IT106 through IT125 are used in pairs. For Example, IT106 will contain a

qualifier code and IT107 will contain information related to the qualifying

code. So, ifIT106 is code FS then IT107 would carry the National Stock

Number.

IT107

IT108

IT109

ITllO

ITlll

IT112

IT113

IT114

Refer to 003040 Data Element Dictionary for acceptable code values.

234 Product/Service ID X ANIdentifying number for a product or service.

235 Product/Service ID Qualifier O ID

Code identifying the type/source of the descriptive number used in

Product/Service ID (234).

Refer to 003040 Data Element Dictionary for acceptable code values.

234 Product/Service ID X ANIdentifying number for a product or service.

235 Product/ServicelD Qualifier O ID

Code identifying the type/source of the descriptive number used in

Product/Service ID (234).

Refer to 003040 Data Element Dictionary for acceptable code values.

234 Product/Service ID X ANIdentifying number for a product or service.

235 Product/Service ID Qualifier O ID

Code identifying the type/source of the descriptive number used in

Product/Service ID (234).

Refer to 003040 Data Element Dictionary for acceptable code values.

234 Product/Service ID X ANIdentifying number for a product or service.

235 Product/Service ID Qualifier O ID

Code identifying the type/source of the descriptive number used in

Product/Service ID (234).

1/30

2/2

1/30

2/2

1/30

2/2

1/30

2/2

RELEASE - 003040FED01A 26 August 31, 1994

Page 31: Federal implementation guideline for electronic data interchange · 2015. 11. 18. · Introduction: This Draft Standard forTrial Use containsthe formatand establishesthedatacontents

810 - Invoice (Commercial Invoice)

IT115

IT116

IT117

IT118

IT119

IT120

IT121

IT122

IT123

IT124

IT125

Refer to 003040 Data Element Dictionary for acceptable code values.

234 Product/Service ID X AN 1/30

Identifying number for a product or service.

235 Product/Service ro Qualifier O ID 2/2

Code identifying the type/source of the descriptive number used in

Product/Service ID (234).

Refer to 003040 Data Element Dictionary for acceptable code values.

234 Product/Service ID X AN 1/30

Identifying number for a product or service.

235 Product/Service ID Qualifier O ID 2/2

Code identifying the type/source of the descriptive number used in

Product/Service ID (234).

Refer to 003040 Data Element Dictionary for acceptable code values.

234 Product/Service ID X AN 1/30

Identifying number for a product or service.

235 Product/Service ID Qualifier O ID 2/2

Code identifying the type/source of the descriptive number used in

Product/Service ID (234).

Refer to 003040 Data Element Dictionary for acceptable code values.

234 Product/Service ID X AN 1/30

Identifying number for a product or service.

235 Product/Service ID Qualifier O ID 2/2

Code identifying the type/source of the descriptive number used in

Product/Service ID (234).

Refer to 003040 Data Element Dictionary for acceptable code values.

234 Product/Service ID X AN 1/30

Identifying number for a product or service.

235 Product/Service ID Qualifier O ID 2/2

Code identifying the type/source of the descriptive number used in

Product/Service ID (234).

Refer to 003040 Data Element Dictionary for acceptable code values.

234 Product/Service ID X AN 1/30

Identifying number for a product or service.

RELEASE - 003040FED01A 27 August 31. 1994

Page 32: Federal implementation guideline for electronic data interchange · 2015. 11. 18. · Introduction: This Draft Standard forTrial Use containsthe formatand establishesthedatacontents

810 - Invoice (Commercial Invoice)

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Notes:

Syntax Notes:

Semantic Notes:

Comments:

TXI Tax Information

040

ITl

Detail

Optional

10

To specify tax information.

Use this 2/TXI/040 segment only if taxes apply to a line item.

1 At least one of TXI02 TXI03 or TXI06 is required.

2 If either TXI04 or TXI05 is present, then the other is required.

3 If TXI08 is present, then TXI03 is required.

1 TXI02 is the monetary amount of the tax.

2 TXI03 is the tax percent expressed as a decimal.

3 If TXI02 is not used, then the application of the percent (TXI03) is between trading

partners.

»Ref.

Pes.

TXIOl

Data

Element

963

Data Element Summary

NameTax Type CodeCode specifying the type of tax.

Use any code. Thefollowing codes are preferred:

CA City Tax

Fl FICA Tax

FD Federal Tax

FT Federal Excise Tax

GR Gross Receipts Tax

LS State and Local Sales Tax

Attributes

M ID 2/2

X

X

X

X

X

X

X

TXI02

TXI03

TXI04

TXI05

TXI06

TXI07

TXI08

TXI09

Refer to 003040 Data Element Dictionary for acceptable code values.

782 Monetary Amount X R 1/15

Monetary amount.

954 Percent X R 1/10

Percentage expressed as a decimal

955 Tax Jurisdiction Code Qualifier X ID 2/2

Code identifying the source of the data used in tax jurisdiction code.

956 Tax Jurisdiction Code X AN 1/10

Code identifying the taxing jurisdiction.

441 Tax Exempt Code X ID 1/1

Code identifying exemption status from sales and use tax.

662 Relationship Code O ID 1/1

Code indicating the relationship of the price or amount to the associated

segment.

828 Dollar Basis For Percent O R 1/9

Dollar basis to be used in the percent calculation of the allowance, charge or tax

325 Tax Identification Number O AN 1/20

Number assigned to a purchaser (buyer, orderer) by a taxing jurisdiction (state,

county, etc.), often called a tax exemption number or certificate number.

RELEASE - 003040FED01A 28 August 31, 1994

Page 33: Federal implementation guideline for electronic data interchange · 2015. 11. 18. · Introduction: This Draft Standard forTrial Use containsthe formatand establishesthedatacontents

810 - Invoice (Commercial Invoice)

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Notes:

Syntax Notes:

PID Product/Item Description

060

PID

Detail

Optional

1

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

The use of this segment is discouraged. Use only for a clear text description when the

product/service identification in 235/234 pairs in the ITl segment is in sufficient to

describe the item or service being invoiced. Do not use when codes in IT106/107 can be

used to describe the item or service being invoiced.

Semantic Notes:

1 IfPID04 is present, then PID03 is required.

2 At least one of PID04 or PID05 is required.

3 IfPID07 is present, then PID03 is required.

4 IfPID08 is present, then PID03 is required.

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. A "N" indicates it

does not apply. Any other value is indeterminate.

Comments: 1 If FIDO 1 = T", then PID05 is used. If FIDO 1 = ' S", then PID04 is used. If PIDOl= ^ 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.

Data Element SummaryRef.

Des.

» PIDOl

X PID02

X PID03

X PID04

PID05

X PID06

X PID07

X PID08

Data

Element

349

750

559

751

352

752

822

1073

Name Attributes

M ID 1/1Item Description Type

Code indicating the format of a description.

F Free-form

Product/Process Characteristic Code O ID 2/3

Code identifying the general class of a product or process characteristic

Agency Qualifier Code X ID 2/2

Code identifying the agency assigning the code values.

Product Description Code X AN 1/12

A code from an industry code list which provides specific data about a product

characteristic.

Description X AN 1/80

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

Use to identify the item description orjob description.

Surface/Layer/Position Code O ID 2/2

Code indicating the product surface, layer or position that is being described.

Source Subqualifier O AN 1/15

A reference that indicates the table or text maintained by the Source Qualifier.

Yes/No Condition or Response Code O ID 1/1

Code indicating a Yes or No condition or response.

RELEASE - 003040FED01A 29 August 31, 1994

Page 34: Federal implementation guideline for electronic data interchange · 2015. 11. 18. · Introduction: This Draft Standard forTrial Use containsthe formatand establishesthedatacontents

810 - Invoice (Commercial Invoice)

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Notes:

Syntax Notes:

Semantic Notes:

Comments:

ITD Terms of Sale/Deferred Terms of Sale

110

ITl

Detail

Optional

2

To specify terms of sale.

1. Use this 2/ITD/llO segment when the discount terms vary by line item. If the

discomit applies to all of the line items, use the l/ITD/130 segment.

2. Use only when a discoimt is applicable. Do not transmit this segment when a

discount is not applicable.

1 If ITD03 is present, then at least one of ITD04 ITD05 or ITD 13 is required.

2 If ITD08 is present, then at least one of ITD04 ITD05 or ITD 13 is required.

3 If ITD09 is present, then at least one of ITD 10 or ITD 1 1 is required.

1 ITD 15 is the percentage applied to a base amount used to determine a late payment

charge.

1 If the code in ITDO 1 is 04, then ITD07 or ITD09 is required and either ITD 10 or

ITD 11 is required; if the code in ITDOl is 05, then ITD06 or ITD07 is required.

Ref.

Pes.

ITDOl

Data

Element

336

ITD02 333

ITD03 338

X ITD04

ITD05

ITD06

ITD07

370

351

446

386

Attributes

O ID 2/2

Data Element Summary

NameTerms Type Code

Code identifying type ofpayment terms.

21 Fast Pay

Code indicating that an invoice is subject to accelerated

payment

Use to indicate FASTPAYprocedures are applicable

only when thatpayment procedure is authorizedfor the

contract or order represented by this invoice.

Terms Basis Date Code O ID 1/2

Code identifying the beginning of the terms period.

Use the same code as the one indicated in ITD02 ofthe Contract Solicitation

Response, 843 transaction set. Use ofthis segment shall not override the terms

and conditions ofthe contract, order, or Prompt Payment Act.

Refer to 003040 Data Element Dictionary for acceptable code values.

Terms Discount Percent O R 1/6

Terms discoimt percentage, expressed as a percent, available to the purchaser if

an invoice is paid on or before the Terms Discount Due Date.

The amount shown is a percent, e.g., two and a halfpercent should be shown as

2.5 (two pointfive). Do not write the percent as . 025.

Terms Discount Due Date X DT 6/6

Date payment is due if discount is to be earned.

Terms Discount Days Due X NO 1/3

Number of days in the terms discount period by which payment is due if terms

discount is earned.

Terms Net Due Date O DT 6/6

Date when total invoice amount becomes due.

Terms Net Days O NO 1/3

RELEASE - 003040FED01A 30 August 31, 1994

Page 35: Federal implementation guideline for electronic data interchange · 2015. 11. 18. · Introduction: This Draft Standard forTrial Use containsthe formatand establishesthedatacontents

810 - Invoice (Commercial Invoice)

X

X

X

X

X

X

X

ITD08

ITD09

ITDIO

ITDll

ITD12

ITD13

ITD14

ITD15

362

388

389

342

352

765

107

954

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

O N2 1/10

O DT 6/6

N2 1/10

R 1/5

Terms Discount Amount

Total amount of terms discount.

Terms Deferred Due Date

Date deferred payment or percent of invoice payable is due.

Deferred Amount DueDeferred amount due for payment.

Percent of Invoice Payable

Amount of invoice payable expressed in percent.

Description

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

Day of Month X NO 1/2

The numeric value of the day of the month between 1 and the maximum day of

the month being referenced.

Payment Method Code O ID 1/1

Code identifying type of payment procedures.

Percent O R 1/10

Percentage expressed as a decimal

O AN 1/80

RELEASE - 003040FED01A 31 August 31, 1994

Page 36: Federal implementation guideline for electronic data interchange · 2015. 11. 18. · Introduction: This Draft Standard forTrial Use containsthe formatand establishesthedatacontents

810 - Invoice (Commercial Invoice)

Segment: REF Reference Numbers

Position: 120

Loop: mLevel: Detail

Usage: Optional

Max Use: >1

Purpose: To specify identifying numbers.

Notes: Use this 2/REF/120 segment to identify reference numbers that vary by line item. Whenthe reference numbers apply to all the line items in the invoice, use the l/REF/UOsegment.

Syntax Notes: 1 At least one ofREF02 or REF03 is required.

Semantic Notes:

Comments:

Data Element SummaryRef. Data

Des. Element Name Attributes

» REFOl 128 Reference Number Qualifier M ID 2/2

Code qualifying the Reference Number.

46 Old Meter Number

Identifies meters being removed

55 Sequence Number

Use to indicate a suffix number associated with afinal

shipment number (i.e., when transmitting the letter Z to

indicate afinal shipment). (Applicable to DoD invoices

only.)

AT Appropriation Number

Use to identify the accounting/appropriation data of

the billed activity when the data is applicable to the

cited line item.

BL Government Bill of Lading

Use to indicate the government bill oflading number.

FS Final Sequence Number

Use to indicate the suffix number ofa replacement

shipment associated with a shipment number (i.e., when

transmitting the letterA to indicate the first

replacement shipment). (Applicable to DoD invoices

only.)

K5 Task Order

MG Meter Number

RB Rate code number

SE Serial Number

Use to indicate the item's serial number.

SI Shipper's Identifying Number for Shipment (SID)

A unique number (to the shipper) assigned by the

shipper to identify the shipment

Use to indicate the vendor shipping number.

» REF02 127 Reference Number X AN 1/30

Reference number or identification number as defined for a particular

Transaction Set, or as specified by the Reference Number Qualifier.

RELEASE - 003040FED01A 32 August 31, 1994

Page 37: Federal implementation guideline for electronic data interchange · 2015. 11. 18. · Introduction: This Draft Standard forTrial Use containsthe formatand establishesthedatacontents

810 - Invoice (Commercial Invoice)

REF03 352 Description X AN 1/80

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

RELEASE - 003040FED01A 33 August 31, 1994

Page 38: Federal implementation guideline for electronic data interchange · 2015. 11. 18. · Introduction: This Draft Standard forTrial Use containsthe formatand establishesthedatacontents

810 - Invoice (Commercial Invoice)

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Notes:

Syntax Notes:

Semantic Notes:

Comments:

DTM Date/Time Reference

150

ITl

Detail

Optional

10

To specify pertinent dates and times

1. Use two iterations of the segment when a range of dates (expressed as period start -

period end, is required).

2. Use this 2/DTM/150 segment to specify the dates of the line item data for the invoice.

When the date for all items are the same, use the 1/DTM/140 segment.

1 At least one ofDTM02 DTM03 or DTM06 is required.

2 If either DTM06 or DTM07 is present, then the other is required.

»Ref.

Pes.

DTMOl

Data

Element

374

Data Element Summary

NameDate/Time Qualifier

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

Attributes

M ID 3/3

on

035

135

Shipped

Use to indicate the date the goods were shipped.

Delivered

Booking

Use to indicate a billing revenue period. When used,

cite the last day ofthe period.

150

151

Service Period Start

Use to indicate the performance commencement date

for a line item that is ordering a service.

Service Period End

Use to indicate the performance completion datefor a

line item that is ordering a service.

DTM02 373

X DTM03 337

186 Invoice Period Start

When the billing period covered by an invoice begins

187 Invoice Period End

When the billing period covered by an invoice ends

266 Base

The start ofbase date for a calendar reference - all

dates fall after it

Use to indicate a billing demand month. When used,

cite the last day ofthe applicable month.

Date X DT 6/6

Date (YYMMDD).

Time X 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),

RELEASE - 003040FED01A 34 August 31, 1994

Page 39: Federal implementation guideline for electronic data interchange · 2015. 11. 18. · Introduction: This Draft Standard forTrial Use containsthe formatand establishesthedatacontents

810 - Invoice (Commercial Invoice)

S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are

expressed as follows: D = tenths (0-9) and DD = hmidredths (00-99)

X DTM04 623 Time Code O BO 2/2

Code identifying the time. In accordance with International Standards

Organization standard 8601, time can be specified by a + or - and an indication

in hours in relation to Universal Time Coordinate (UTC) time. Since + is a

restricted character, + and - are substituted by P andM in the codes that follow.

X DTM05 624 Century O NO 2/2

The first two characters in the designation of the year (CCYY).

X DTM06 1250 Date Time Period Format Qualifier X ID 2/3

Code indicating the date format, time format, or date and time format.

X DTM07 1251 Date Time Period X AN 1/35

Expression of a date, a time, or range of dates, times or dates and times.

RELEASE - 003040FED01A 35 August 31, 1994

Page 40: Federal implementation guideline for electronic data interchange · 2015. 11. 18. · Introduction: This Draft Standard forTrial Use containsthe formatand establishesthedatacontents

810 - Invoice (Commercial Invoice)

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Notes:

Syntax Notes:

Semantic Notes:

Comments:

CAD Carrier Detail

160

ITl

Detail

Optional

>1

To specify transportation details for the transaction

1. Use only when a dififerent type of transportation method is used than identified in the

purchase order.

2. Use this 2/CAD/160 segment to identify the transportation data that vary by line

item. When the transportation information applies to all line items in the invoice, use

the 3/CAD/030 segment.

1 At least one of CAD05 or CAD04 is required.

2 If CAD07 is present, then CAD08 is required.

Data Element Summary

X

X

»

X

X

Ref.

Des.

CADOl

CAD02

CAD03

CAD04

CAD05

CAD06

CAD07

CAD08

CAD09

Data

Element

91

206

207

140

387

368

128

127

284

Name Attributes

Transportation Method/Type Code O ID 1/2

Code specifying the method or type of transportation for the shipment.

1. Use to indicate the transportation method/type codefor the line items.

2. A conversion table may be required to convert agency codes to codes used

byASCXn.Refer to 003040 Data Element Dictionary for acceptable code values.

Equipment Initial O AN 1/4

Prefix or alphabetic part of an equipment unit's identifying number.

Equipment Number O AN 1/10

Sequencing or serial part of an equipment unit's identifying number (pure

numeric form for equipment number is preferred).

Standard Carrier Alpha Code X ID 2/4

Standard Carrier Alpha Code

Routing X AN 1/35

Free-form description of the routing or requested routing for shipment, or the

originating carrier's identity.

Always cite the number 1. This data element is used to satisfy an X12 syntax

requirement The data, (i.e., the number 1), shall not be processed by the

receiving application program.

Shipment/Order Status Code O ID 2/2

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.

Reference Number Qualifier O ID 2/2

Code qualifying the Reference Number.

Reference Number X AN 1/30

Reference number or identification number as defined for a particular

Transaction Set, or as specified by the Reference Number Qualifier.

Service Level Code O ID 2/2

RELEASE - 003040FED01A 36 August 31, 1994

Page 41: Federal implementation guideline for electronic data interchange · 2015. 11. 18. · Introduction: This Draft Standard forTrial Use containsthe formatand establishesthedatacontents

810 - Invoice (Commercial Invoice)

Code defining service

RELEASE - 003040FED01A 37 August 3 1 . 1 994

Page 42: Federal implementation guideline for electronic data interchange · 2015. 11. 18. · Introduction: This Draft Standard forTrial Use containsthe formatand establishesthedatacontents

810 - Invoice (Commercial Invoice)

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Notes:

Syntax Notes:

Semantic Notes:

Comments:

SAC Service, Promotion, Allowance, or Charge Information

180

SACDetail

Optional

1

To request or identify a service, promotion, allowance, or charge; to specify the amountor percentage for the service, promotion, allowance, or charge

Use this 2/SAC/180 segment to identify charges that apply to a line item. Lf the charges

apply to all of the line items, use the 3/SAC/040 segment.

1 At least one of SAC02 or SAC03 is required.

2 If either SAC03 or SAC04 is present, then the other is required.

3 If either SAC06 or SAC07 is present, then the other is required.

4 If either SAC09 or SAC 10 is present, then the other is required.

5 If SACl 1 is present, then SAC 10 is required.

6 If SAC 1 3 is present, then at least one of SAC02 or SAC04 is required.

7 If SAC14 is present, then SAC13 is required.

1 If SACOl is A or C, then at least one of SAC05, SAC07, or SAC08 is required.

2 SAC05 is the total amount for the service, promotion, allowance, or charge.

If SAC05 is present with SAC07 or SAC08, then SAC05 takes precedence.

3 SAC 10 alone is used to indicate a specific quantity which could be a dollar amount,

that is applicable to service, promotion, allowance or charge.

SACIO and SACl 1 used together indicate a quantity range, which could be a dollar

amount, that is applicable to service, promotion, allowance, or charge.

4 SAC 13 is used in conjunction with SAC02 or SAC04 to provide a specific reference

number as identified by the code used.

5 SAC 14 is used in conjunction with SAC 13 to identify an option when there is more

than one option of the promotion.

1 SAC04 may be used to uniquely identify the service, promotion, allowance, or

charge. In addition, it may be used in conjunction to further the code in SAC02.

2 In some business applications, it is necessary to advise the trading partner of the

actual dollar amoimt that a particular allowance, charge, or promotion was based on

to reduce ambiguity. This amount is commonly referred to a ''Dollar Basis

Amount". It is represented in the SAC segment in SACIO using the qualifier DO -

Dollars in SAC09.

»Ref.

Pes.

SACOl

SAC02

X

X

SAC03

SAC04

Data

Element

248

1300

559

1301

Data Element Summary

Name Attributes

Allowance or Charge Indicator M ID 1/1

Code which indicates an allowance or charge for the service specified.

A Allowance

C Charge

Service, Promotion, Allowance, or Charge Code X ID 4/4

Code identifying the service, promotion, allowance, or charge

Any code may be used except those referring to taxes which should be carried

in the TXl segment. Use code F650 to indicate packing, crating and handling.

Refer to 003040 Data Element Dictionary for acceptable code values.

Agency Qualifier Code X ID 2/2

Code identifying the agency assigning the code values.

Agency Service, Promotion, Allowance, or Charge Code X AN 1/10

RELEASE - 003040FED01A 38 August 31, 1994

Page 43: Federal implementation guideline for electronic data interchange · 2015. 11. 18. · Introduction: This Draft Standard forTrial Use containsthe formatand establishesthedatacontents

810 - Invoice (Commercial Invoice)

X

X

O N2 1/15

ID 1/1

1/6

Agency maintained code identifying the service, promotion, allowance, or

charge

SAC05 610 Amount

Monetary amomit.

Use to identify the amount ofthe allowance or charge.

SAC06 378 Allowance/ Charge Percent Qualifier

Code indicating on what basis allowance or charge percent is calculated.

Refer to 003040 Data Element Dictionary for acceptable code values.

SAC07 332 Allowance or Charge Percent X RAllowance or charge expressed as a percent.

The amount shown is a percentage, e.g., two and a halfpercent should be

shown as 2.5 (two pointfive). Do not write as . 025.

SAC08 359 Allowance or Charge Rate O R 1/9

Allowance or Charge Rate per Unit.

SAC09 355 Unit or Basis for Measurement Code X D) 2/2

Code specifying the units in which a value is being expressed, or manner in

which a measurement has been taken

Refer to 003040 Data Element Dictionary for acceptable code values.

SACIO 339 Allowance or Charge Quantity X R 1/10

Quantity basis when allowance or charge quantity is different from the purchase

order or invoice quantity.

SACll 339 Allowance or Charge Quantity O R 1/10

Quantity basis when allowance or charge quantity is different from the purchase

order or invoice quantity.

SAC12 331 Allowance or Charge Method of Handling Code O ID

Code indicating method of handling for an allowance or charge.

SAC13 127 Reference Number X ANReference number or identification number as defined for a particular

Transaction Set, or as specified by the Reference Number Qualifier.

SAC14 770 Option Number O ANA unique number identifying available promotion or allowance options when

more than one is offered.

SAC15 352 Description O AN 1/80

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

Use only when additional clarification ofSAC02 is required.

2/2

1/30

1/20

RELEASE - 003040FED01A 39 August 31, 1994

Page 44: Federal implementation guideline for electronic data interchange · 2015. 11. 18. · Introduction: This Draft Standard forTrial Use containsthe formatand establishesthedatacontents

810 - Invoice (Commercial Invoice)

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Notes:

Syntax Notes:

Semantic Notes:

Comments:

TXI Tax Information

190

SACDetail

Optional

10

To specify tax information.

Use this 2/TXI/190 segment only if taxes apply.

1 At least one of TXI02 TXI03 or TXI06 is required.

2 If either TXI04 or TXI05 is present, then the other is required.

3 If TXI08 is present, then TXI03 is required.

1 TXI02 is the monetary amount of the tax.

2 TXI03 is the tax percent expressed as a decimal.

3 If TXI02 is not used, then the application of the percent (TXI03) is between trading

partners.

Ref.

Pes.

» TXIOl

Data

Element

963

Data Element Summary

NameTax Type CodeCode specifying the type of tax.

Use any code. Thefollowing codes are preferred:

CA City Tax

Fl FICA Tax

FD Federal Tax

FT Federal Excise Tax

GR Gross Receipts Tax

LS State and Local Sales Tax

Attributes

M ID 2/2

Refer to 003040 Data Element Dictionary for acceptable code values.

TXI02 782 Monetary Amount X R 1/15

Monetary amount.

X TXI03 954 Percent X R 1/10

Percentage expressed as a decimal

X TXI04 955 Tax Jurisdiction Code Qualifier X ID 2/2

Code identifying the source of the data used in tax jurisdiction code.

X TXI05 956 Tax Jurisdiction Code X AN 1/10

Code identifying the taxing jurisdiction.

X TXI06 441 Tax Exempt Code X ID 1/1

Code identifying exemption status from sales and use tax.

X TXI07 662 Relationship Code O ID 1/1

Code indicating the relationship of the price or amount to the associated

segment.

X TXI08 828 Dollar Basis For Percent O R 1/9

Dollar basis to be used in the percent calculation of the allowance, charge or tax

X TXI09 325 Tax Identification Number O AN 1/20

Number assigned to a purchaser (buyer, orderer) by a taxing jurisdiction (state,

county, etc.), often called a tax exemption number or certificate number.

RELEASE - 003040FED01A 40 August 31, 1994

Page 45: Federal implementation guideline for electronic data interchange · 2015. 11. 18. · Introduction: This Draft Standard forTrial Use containsthe formatand establishesthedatacontents

810 - Invoice (Commercial Invoice)

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Notes:

Nl Name

240

NlDetail

Optional

1

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

1. Whenever possible, address information should be transmitted using code values

contained in a combination of the NlOl and N103/4 data elements. Use N102 and N2-

N4 segments only when it is necessary to transmit the full address. For example, if a

vendor can be identified by a DUNs number, it is not necessary to transmit the vendor's

fiill address since the relationship between the DUNs number and the vendor's address

can be established by accessing a data base in which the information is stored, having

been put there at the time the vendor electronically registered as a federal government

trading partner.

Syntax Notes:

Semantic Notes:

Comments:

2. Use this 2/N1/240 loop to identify information pertaining to the line item. If the

information applies to all of the line items, use the l/Nl/070 loop.

1 At least one ofN102 or N 103 is required.

2 If either N103 or N104 is present, then the other is required.

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 NlOl.

Data Element Summary

»Ref.

Pes.

NlOl

Data

Element

98

»

N102

N103

93

66

Name Attributes

Entity Identifier Code M ID 2/2

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

MQST

SV

Metering Location

Sliip To

Use, when the ship-to address differs among line items,

to identify the shipped to address.

Service Performance Site

When services are contracted for, this describes the

organization for whom or location address at which

those services will be performed

Use to indicate the location where a service was

performed.

Name X AN 1/35

Free-form name.

Identification Code Qualifier X ID 1/2

Code designating the system/method of code structure used for Identification

Code (67).

1

10

33

A2

D-U-N-S Number, Dun & Bradstreet

Department of Defense Activity Address Code

(DODAAC)Commercial and Govenunent Entity (CAGE)

Military Assistance Program Address Code (MAPAC)

RELEASE - 003040FED01A 41 August 31, 1994

Page 46: Federal implementation guideline for electronic data interchange · 2015. 11. 18. · Introduction: This Draft Standard forTrial Use containsthe formatand establishesthedatacontents

810 - Invoice (Commercial Invoice)

Contained in the Military Assistance Program Address

Directory (MAPAD); represents the location of an

entity

FA Facility Identification

» N104 67 Identification Code X AN 2/17

Code identifying a party or other code.

X N105 706 Entity Relationship Code O ID 2/2

Code describing entity relationship.

X N106 98 Entity Identifier Code O ID 2/2

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

RELEASE - 003040FED01A 42 August 31, 1994

Page 47: Federal implementation guideline for electronic data interchange · 2015. 11. 18. · Introduction: This Draft Standard forTrial Use containsthe formatand establishesthedatacontents

810 - Invoice (Commercial Invoice)

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Notes:

N2 Additional Name Information

250

NlDetail

Optional

2

To specify additional names or those longer than 35 characters in length

1. This segment is not necessary when the cited party can be identified by a code value

in NIO 1/03/04.

Syntax Notes:

Semantic Notes:

Comments:

2. Use, as applicable, with codes ST and SV, to provide the necessary identification for

the payment.

»Ref.

Pes.

N201

N202

Data

Element

93

93

Data Element Summary

NameNameFree-form name.

Name

Free-form name.

Attributes

M AN 1/35

O AN 1/35

RELEASE - 003040FED01A 43 August 31, 1994

Page 48: Federal implementation guideline for electronic data interchange · 2015. 11. 18. · Introduction: This Draft Standard forTrial Use containsthe formatand establishesthedatacontents

810 - Invoice (Commercial Invoice)

Segment: N3 Address Information

Position: 260

Loop: NlLevel: Detail

Usage: Optional

Max Use: 2

Purpose: To specify the location of the named party

Notes: 1. This segment is not necessary when the cited party can be identified by a code value

in NIO 1/03/04.

Syntax Notes:

Semantic Notes:

Comments:

2. Use, as applicable, with codes ST and SV, to provide the necessary identification for

the payment.

»Ref.

Pes.

N301

N302

Data

Element

166

166

Data Element Summary

NameAddress Information

Address information

Address Information

Address information

Attributes

M AN 1/35

O AN 1/35

RELEASE - 003040FED01A 44 August 31, 1994

Page 49: Federal implementation guideline for electronic data interchange · 2015. 11. 18. · Introduction: This Draft Standard forTrial Use containsthe formatand establishesthedatacontents

810 - Invoice (Commercial Invoice)

Segment: N4 Geographic Location

Position: 270

Loop: NlLevel: Detail

Usage: Optional

Max Use: 1

Purpose: To specify the geographic place of the named party

Notes: 1. This segment is not necessary when the cited party can be identified by a code value

in NIO 1/03/04.

Syntax Notes:

Semantic Notes:

Comments:

2. Use, as applicable, with codes ST and SV, to provide the necessary identification for

the payment.

1 IfN406 is present, then N405 is required.

1 A combination of either N401 through N404 (or N405 and N406) may be adequate

to specify a location.

2 N402 is required only if city name (N401) is in the USA or Canada.

Data Element Summary

X

X

Ref.

Des.

N401

N402

N403

N404

N405

N406

Data

Element Name Attributes

O AN 2/3019 City Name

Free-form text for city name.

156 State or Province Code O ID 2/2

Code (Standard State/Province) as defined by appropriate government agency.

116 Postal Code O ID 3/9

Code defining international postal zone code excluding punctuation and blanks

(zip code for United States).

26 Country Code O ID 2/3

Code identifying the country.

A conversion table may be required to convert agency codes to codes used by

ASCX12.

309 Location Qualifier X ID 1/2

Code identifying type of location.

310 Location Identifier O AN 1/30

Code which identifies a specific location.

RELEASE - 003040FED01A 45 August 31, 1994

Page 50: Federal implementation guideline for electronic data interchange · 2015. 11. 18. · Introduction: This Draft Standard forTrial Use containsthe formatand establishesthedatacontents

810 - Invoice (Commercial Invoice)

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Notes:

Syntax Notes:

Semantic Notes:

Comments:

TDS Total Monetary Value Summary

010

Suiimiary

Mandatory

1

To specify the total invoice discounts and amounts

There is no need to transmit either the currency symbol (e.g., the dollar sign $), commasseparating thousands, or the decimal point because the amount data elements are N2types which means that there are two decimal places implied in every transmitted

number. When using, be sure to follow all whole numbers with two zeros to account for

the implied two decimal places.

1 TDS02 is required if the dollar value subject to discount is not equal to the dollar

value of TDSOl.

Ref.

Pes.

» TDSOl

Data

Element

361

TDS02 390

TDS03 391

TDS04 362

Data Element Summary

Name Attributes

M N2 1/10Total Invoice AmountAmount of invoice (including charges, less allowances) before terms discount (if

discount is applicable).

Use to identify the gross total amount ofthe invoice after addition ofcharges

and deductionsfor allowances at both the line item and summary levels, (e.g.,

this amount must equal the sum ofIT102 times IT104 plus any amounts in the

SAC and TXI segments, in the detail and summary levels, as applicable.

Amount Subject to Terms Discount O N2 1/10

Amount upon which the terms discount amount is calculated.

Use to identify the total amount ofthe invoice subject to discounts (which may

vary by line). Use is required ifthe dollar value subject to the terms discount is

not equal to the dollar value cited in TDSOl.

Discounted Amount Due O N2 1/10

Amount of invoice due if paid by terms discoimt due date (total invoice or

installment amount less cash discount.)

Use to identijy the total amount ofthe invoice minus allowances and discounts

andplus the charges, as applicable.

Terms Discount Amount O N2 1/10

Total amount of terms discoimt.

RELEASE - 003040FED01A 46 August 31, 1994

Page 51: Federal implementation guideline for electronic data interchange · 2015. 11. 18. · Introduction: This Draft Standard forTrial Use containsthe formatand establishesthedatacontents

810 - Invoice (Commercial Invoice)

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Notes:

Syntax Notes:

Semantic Notes:

Comments:

Ref.

Pes.

» TXIOl

TXI Tax Information

020

Summary

Optional

10

To specify tax information.

Use this 3/TXI/020 segment only if taxes apply.

1 At least one of TXI02 TXI03 or TXI06 is required.

2 If either TXI04 or TX105 is present, then the other is required.

3 If TXI08 is present, then TXI03 is required.

1 TXI02 is the monetary amount of the tax.

2 TXI03 is the tax percent expressed as a decimal.

3 If TXI02 is not used, then the application of the percent (TXI03) is between trading

partners.

Data

Element

963

Data Element Summary

NameTax Type Code

Code specifying the type of tax.

Use any code. Thefollowing codes are preferred:

CA City Tax

Fl FICA Tax

FD Federal Tax

FT Federal Excise Tax

GR Gross Receipts Tax

LS State and Local Sales Tax

Attributes

M ID 2/2

X

X

X

X

X

X

X

TXI02

TXI03

TXI04

TXI05

TXI06

TXI07

TXI08

TXI09

782

954

955

956

441

662

828

325

Refer to 003040 Data Element Dictionary for acceptable code values.

Monetary Amount X R 1/15

Monetary amount.

Percent X R 1/10

Percentage expressed as a decimal

Tax Jurisdiction Code Qualifier X ID 2/2

Code identifying the source of the data used in tax jurisdiction code.

Tax Jurisdiction Code X AN 1/10

Code identifying the taxing jurisdiction.

Tax Exempt Code

Code identifying exemption status from sales and use tax.

Relationship CodeCode indicating the relationship of the price or amount to the associated

segment.

Dollar Basis For Percent O RDollar basis to be used in the percent calculation of the allowance, charge or tax

Tax Identification Number O AN 1/20

Number assigned to a purchaser (buyer, orderer) by a taxing jurisdiction (state,

county, etc.), often called a tax exemption number or certificate number.

ID 1/1

O ID 1/1

1/9

RELEASE - 003040FED01A 47 August 31, 1994

Page 52: Federal implementation guideline for electronic data interchange · 2015. 11. 18. · Introduction: This Draft Standard forTrial Use containsthe formatand establishesthedatacontents

810 - Invoice (Commercial Invoice)

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Notes:

Syntax Notes:

Semantic Notes:

Comments:

CAD Carrier Detail

030

SummaryOptional

1

To specify transportation details for the transaction

1. Use only when a different type of transportation method is used than identified in the

purchase order.

2. Use this 3/CAD/030 segment to identify transportation information that applies to all

line items. When the transportation information varies by line item, use the 2/CAD/160

segment.

1 At least one of CAD05 or CAD04 is required.

2 If CAD07 is present, then CAD08 is required.

Data Element Summary

X

X

»

X

X

Ref.

Des.

CADOl

CAD02

CAD03

CAD04

CAD05

CAD06

CAD07

CAD08

CAD09

Data

Element

91

206

207

140

387

368

128

127

284

Name Attributes

Transportation Method/Type Code O ID 1/2

Code specifying the method or type of transportation for the shipment.

1. Use to indicate the transportation method/type codefor the line items.

2. A conversion table may be required to convert agency codes to codes used

byASCXn.Refer to 003040 Data Element Dictionary for acceptable code values.

Equipment Initial O AN 1/4

Prefix or alphabetic part of an equipment unit's identifying number.

Equipment Number O AN 1/10

Sequencing or serial part of an equipment unit's identifying number (pure

numeric form for equipment number is preferred).

Standard Carrier Alpha Code X ID 2/4

Standard Carrier Alpha Code

Routing X AN 1/35

Free-form description of the routing or requested routing for shipment, or the

originating carrier's identity.

Always cite the number 1. This data element is used to satisfy an X12 syntax

requirement. The data shall not be processed by the receiving application

program.

Shipment/Order Status Code O ID 2/2

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.

Reference Number Qualifier O ID 2/2

Code qualifying the Reference Number.

Reference Number X AN 1/30

Reference number or identification number as defined for a particular

Transaction Set, or as specified by the Reference Number Qualifier.

Service Level Code O ID 2/2

RELEASE - 003040FED01A 48 August 31, 1994

Page 53: Federal implementation guideline for electronic data interchange · 2015. 11. 18. · Introduction: This Draft Standard forTrial Use containsthe formatand establishesthedatacontents

810 - Invoice (Commercial Invoice)

Code defining service

RELEASE - 003040FEDO 1A 49 August 3

1

Page 54: Federal implementation guideline for electronic data interchange · 2015. 11. 18. · Introduction: This Draft Standard forTrial Use containsthe formatand establishesthedatacontents

810 - Invoice (Commercial Invoice)

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Notes:

Syntax Notes:

Semantic Notes:

Comments:

SAC Service, Promotion, Allowance, or Charge Information

040

SACSummary

Optional

1

To request or identify a service, promotion, allowance, or charge; to specify the amountor percentage for the service, promotion, allowance, or charge

Use the 3/SAC/040 segment to identify charges that apply to all of the line items. If the

charges vary by line item, use the 2/SAC/180 segment.

1 At least one of SAC02 or SAC03 is required.

2 If either SAC03 or SAC04 is present, then the other is required.

3 If either SAC06 or SAC07 is present, then the other is required.

4 If either SAC09 or SAC 10 is present, then the other is required.

5 If SAC 11 is present, then SAC 10 is required.

6 If SAC 13 is present, then at least one of SAC02 or SAC04 is required.

7 If SAC14 is present, then SAC13 is required.

1 If SACO 1 is A or C, then at least one of SAC05, SAC07, or SAC08 is required.

2 SAC05 is the total amount for the service, promotion, allowance, or charge.

If SAC05 is present with SAC07 or SAC08, then SAC05 takes precedence.

3 SAC 10 alone is used to indicate a specific quantity which could be a dollar amount,

that is applicable to service, promotion, allowance or charge.

SAC 10 and SACl 1 used together indicate a quantity range, which could be a dollar

amount, that is applicable to service, promotion, allowance, or charge.

4 SAC 13 is used in conjunction with SAC02 or SAC04 to provide a specific reference

number as identified by the code used.

5 SAC14 is used in conjunction with SAC13 to identify an option when there is more

than one option of the promotion.

1 SAC04 may be used to uniquely identify the service, promotion, allowance, or

charge. In addition, it may be used in conjunction to further the code in SAC02.

2 In some business applications, it is necessary to advise the trading partner of the

actual dollar amount that a particular allowance, charge, or promotion was based on

to reduce ambiguity. This amount is commonly referred to a "Dollar Basis

Amount". It is represented in the SAC segment in SACIO using the qualifier DO -

Dollars in SAC09.

»Ref.

Pes.

SACOl

SAC02

X

X

SAC03

SAC04

Data

Element

248

1300

559

1301

Data Element Summary

Name Attributes

Allowance or Charge Indicator M ID 1/1

Code which indicates an allowance or charge for the service specified.

A Allowance

C Charge

Service, Promotion, Allowance, or Charge Code X ID 4/4

Code identifying the service, promotion, allowance, or charge

Use any code except those that are tax related. Those codes should be carried

in the TXI segment

Refer to 003040 Data Element Dictionary for acceptable code values.

Agency Qualifier Code X ID 2/2

Code identifying the agency assigning the code values.

Agency Service, Promotion, Allowance, or Charge Code X AN 1/10

RELEASE - 003040FED01A 50 August 31, 1994

Page 55: Federal implementation guideline for electronic data interchange · 2015. 11. 18. · Introduction: This Draft Standard forTrial Use containsthe formatand establishesthedatacontents

810 - Invoice (Commercial Invoice)

X

X

O N2 1/15

ID 1/1

1/6

Agency maintained code identifying the service, promotion, allowance, or

charge

SAC05 610 Amount

Monetary amoimt.

Use to identify the amount ofthe allowance or charge.

SAC06 378 Allowance/ Charge Percent Qualifier

Code indicating on what basis allowance or charge percent is calculated.

Refer to 003040 Data Element Dictionary for acceptable code values.

SAC07 332 Allowance or Charge Percent X RAllowance or charge expressed as a percent.

The amount shown is a percent, e.g., two and a halfpercent should be shown as

2.5 (two pointfive). Do not write the percent as . 025.

SAC08 359 Allowance or Charge Rate O R 1/9

Allowance or Charge Rate per Unit.

SAC09 355 Unit or Basis for Measurement Code X ID 2/2

Code specifying the units in which a value is being expressed, or maimer in

which a measurement has been taken

Refer to 003040 Data Element Dictionary for acceptable code values.

SACIO 339 Allowance or Charge Quantity X R 1/10

Quantity basis when allowance or charge quantity is different from the purchase

order or invoice quantity.

SACll 339 Allowance or Charge Quantity O R 1/10

Quantity basis when allowance or charge quantity is different from the purchase

order or invoice quantity.

SAC12 331 Allowance or Charge Method of Handling Code O ID 2/2

Code indicating method of handling for an allowance or charge.

SAC13 127 Reference Number X AN 1/30

Reference number or identification number as defined for a particular

Transaction Set, or as specified by the Reference Number Qualifier.

SAC14 770 Option Number O AN 1/20

A unique number identifying available promotion or allowance options when

more than one is offered.

SAC15 352 Description O AN 1/80

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

Use only when additional clarification ofcodes in SAC02 is required.

RELEASE - 003040FED01A 51 August 31, 1994

Page 56: Federal implementation guideline for electronic data interchange · 2015. 11. 18. · Introduction: This Draft Standard forTrial Use containsthe formatand establishesthedatacontents

810 - Invoice (Commercial Invoice)

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Notes:

Syntax Notes:

Semantic Notes:

Comments:

TXI Tax Information

050

SACSummary

Optional

10

To specify tax information.

Use this 3/TXI/050 segment only if taxes apply at the simamary level and they caimot be

assigned to a specific line item.

1 At least one of TXI02 TXI03 or TXI06 is required.

2 If either TXI04 or TXI05 is present, then the other is required.

3 If TXI08 is present, then TXI03 is required.

1 TXI02 is the monetary amount of the tax.

2 TXI03 is the tax percent expressed as a decimal.

3 If TXI02 is not used, then the application of the percent (TXI03) is between trading

partners.

Ref.

Pes.

» TXIOl

Data

Element

963

Data Element Summary

NameTax Type Code

Code specifying the type of tax.

Use any code. The following codes are preferred:

CA City Tax

Fl PICA Tax

FD Federal Tax

FT Federal Excise Tax

GR Gross Receipts Tax

LS State and Local Sales Tax

Attributes

M ID 2/2

Refer to 003040 Data Element Dictionary for acceptable code values.

TXI02 782 Monetary Amount X R 1/15

Monetary amount.

X TXI03 954 Percent X R 1/10

Percentage expressed as a decimal

X TXI04 955 Tax Jurisdiction Code Qualifier X ID 2/2

Code identifying the source of the data used in tax jurisdiction code.

X TXI05 956 Tax Jurisdiction Code X AN 1/10

Code identifying the taxing jurisdiction.

X TXI06 441 Tax Exempt Code X ID 1/1

Code identifying exemption status from sales and use tax.

X TXI07 662 Relationship Code O ID 1/1

Code indicating the relationship of the price or amount to the associated

segment.

X TXI08 828 Dollar Basis For Percent O R 1/9

Dollar basis to be used in the percent calculation of the allowance, charge or tax

X TXI09 325 Tax Identification Number O AN 1/20

Number assigned to a purchaser (buyer, orderer) by a taxing jurisdiction (state,

county, etc.), often called a tax exemption number or certificate number.

RELEASE - 003040FED0IA 52 August 31, 1994

Page 57: Federal implementation guideline for electronic data interchange · 2015. 11. 18. · Introduction: This Draft Standard forTrial Use containsthe formatand establishesthedatacontents

810 - Invoice (Commercial Invoice)

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Notes:

Syntax Notes:

Semantic Notes:

Comments:

CTT Transaction Totals

070

SummaryMandatory

1

To transmit a hash total for a specific element in the transaction set

1 If CTT03 is present, then CTT04 is required.

2 If CTT05 is present, then CTT06 is required.

1 This segment is intended to provide hash totals to validate transaction completeness

and correctness.

»Ref.

Pes.

CTTOl

CTT02

Data

Element

354

347

Attributes

M NO 1/6

Data Element Summary

NameNumber of Line Items

Total number of line items in the transaction set.

Hash Total O R 1/10

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.

Example:

-.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.

X CTT03 81 Weight O R 1/10

Numeric value of weight.

X CTT04 355 Unit or Basis for Measurement Code X H) 2/2

Code specifying the units in which a value is being expressed, or maimer in

which a measurement has been taken

X CTT05 183 Volume O R 1/8

Value of volumetric measure.

X CTT06 355 Unit or Basis for Measurement Code X H) 2/2

Code specifying the units in which a value is being expressed, or manner in

which a measurement has been taken

X CTT07 352 Description O AN 1/80

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

RELEASE - 003040FED01A 53 August 31, 1994

Page 58: Federal implementation guideline for electronic data interchange · 2015. 11. 18. · Introduction: This Draft Standard forTrial Use containsthe formatand establishesthedatacontents

810 - Invoice (Commercial Invoice)

Segment

Position

Loop

Level

Usage

Max Use

Purpose

Notes:

Syntax Notes:

Semantic Notes:

Comments:

SE Transaction Set Trailer

080

SummaryMandatory

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).

SE is the last segment of each transaction set.

Data Element Summary

»

»

Ref.

Pes.

SEOl

SE02

Data

Element

96

329

Name Attributes

M NO 1/10Number of Included Segments

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

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

Cite the same number that is contained in ST02.

RELEASE - 003040FED01A 54 August 31, 1994

Page 59: Federal implementation guideline for electronic data interchange · 2015. 11. 18. · Introduction: This Draft Standard forTrial Use containsthe formatand establishesthedatacontents

Technical Publications

Periodical

Journal of Research of the National Institute of Standards and Technology—Reports NIST research

and development in those disciplines of the physical and engineering sciences in which the Institute is

active. These include physics, chemistry, engineering, mathematics, and computer sciences. Papers cover a

broad range of subjects, with major emphasis on measurement methodology and the basic technology

underlying standardization. Also included from time to time are survey articles on topics closely related to

the Institute's technical and scientific programs. Issued six times a year.

Nonperiodicals

Monographs—Major contributions to the technical literature on various subjects related to the

Institute's scientific and technical activities.

Handbooks—Recommended codes of engineering and industrial practice (including safety codes) devel-

oped in cooperation with interested industries, professional organizations, and regulatory bodies.

Special Publications—Include proceedings of conferences sponsored by NIST, NIST annual reports, and

other special publications appropriate to this grouping such as wall charts, pocket cards, and bibliographies.

National Standard Reference Data Series—Provides quantitative data on the physical and chemical

properties of materials, compiled from the world's literature and critically evaluated. Developed under a

worldwide program coordinated by NIST under the authority of the National Standard Data Act (Public

Law 90-396). NOTE: The Journal of Physical and Chemical Reference Data (JPCRD) is published

bimonthly for NIST by the American Chemical Society (ACS) and the American Institute of Physics (AIP).

Subscriptions, reprints, and supplements are available from ACS, 1155 Sixteenth St., NW, Washington, DC20056.

Building Science Series—Disseminates technical information developed at the Institute on building

materials, components, systems, and whole structures. The series presents research results, test methods, and

performance criteria related to the structural and environmental functions and the durability and safety

characteristics of building elements and systems.

Technical Notes—Studies or reports which are complete in themselves but restrictive in their treatment of

a subject. Analogous to monographs but not so comprehensive in scope or definitive in treatment of the

subject area. Often serve as a vehicle for final reports of work performed at NIST under the sponsorship of

other government agencies.

Voluntary Product Standards—Developed under procedures published by the Department of Commercein Part 10, Tide 15, of the Code of Federal Regulations. The standards establish nationally recognized

requirements for products, and provide all concerned interests with a basis for common understanding of

the characteristics of the products. NIST administers this program in support of the efforts of private-sector

standardizing organizations.

Order the following NIST publications—FIPS and NISTlRs—-from the National Technical Information

Service, Springfield, VA 22161.

Federal Information Processing Standards Publications (FIPS PUB)—Publications in this series

collectively constitute the Federal Information Processing Standards Register. The Register serves as the

official source of information in the Federal Government regarding standards issued by NIST pursuant to

the Federal Property and Administrative Services Act of 1949 as amended. Public Law 89-306 (79 Stat.

1 127), and as implemented by Executive Order 1 1717 (38 FR 12315, dated May 11, 1973) and Part 6 of

Title 15 CFR (Code of Federal Regulations).

NIST Interagency Reports (NISTIR)—A special series of interim or final reports on work performed by

NIST for outside sponsors (both government and nongovernment). In general, initial distribution is handled

by the sponsor; public distribution is by the National Technical Information Service, Springfield, VA 22161,

in paper copy or microfiche form.

Page 60: Federal implementation guideline for electronic data interchange · 2015. 11. 18. · Introduction: This Draft Standard forTrial Use containsthe formatand establishesthedatacontents