convention - defense technical information center · department of defense bi0 ivoic ... di1irr...

DEPARTMENT OF DEFENSE INVOICE (PROGPESS PAYMENT)DRAFT IMPLEMENTATION CONVENTION 810.00301ODoD_

* AD-A263 455 Draft

I oDepartmentS ofDefense DTIC

S ELECTEAPR2 6 1993 11

DoD EUElectronic DataInterchange (EDI)

* ConventionASC X 12 Transaction Set 810Invoice (Progress Payment)(Version 003010)

00

This document was prepared by the Logislcs Managesment Intitute for the Defense Logilatc Agency under- Task DL2(3" The task was perfovred under Contrac MDA903-9"0C-0 with the Departnvt ofDef "e.

Permndion to quote or reproduce any part of this document except for Governnent purpose muir be( ) obtained forn the Depamnent of Defense Executive Agent for Electronic Corm Frcfeectmnlc Data

Inter•asnge/Protection of Logistics Undassified /Sensitive Systens.

Executive Agent for EC/EDI/PLUSDefense Logistics AgencyCameron StationAlexandria, VA 22304-6100

'"ASELINeAS OF: JANUARY 29. 1993

fAppoe o pbcrje~leasw

DEPARTMENT OF DEFENSE BI0 IVOIC (PEm m PmummDMFAr NOPLEMEATATION CONVENTION ANOSI AC X12 VEMO EASE 001 0000

* 10.0 DoD EDI CONVENTION

ASC X12 TRANSACTION SET 810 INVOICE(PROGRESS PAYMENT)(VERSION O03010)

FORMATTING INVOICE INFORMATION FOR THE DOD PAY-MENT SYSTEM USING THE ASC X12 TRANSACTION SET 810INVOICE (PROGRESS PAYMENT).

Accesion For

NTIS CRA&MDTIC TABU:.a .;,ou i icedJa,.ti cat .on .................

KBy...Di:,t ibi tion I

Availability Codes

Avail andlorDist Special

BASEUNE AS OF: JANUARY 29 1111 10,0.1

DEPARTUME OF DEFENSE No uIIVOICE fmu imDRAFT WLMNMMTAION CONVENioN ANN SI MX12 WEUWEIM VO

(BLANK PAGE)

§AZNE*F-MU0~l

DEPARTMENT OF DEFENSE 310wvoim u

DRAFT RMPLEMWETATION COMEMON ANSN C X12 VLERSIOWAME 6OMOO_

Contents

FORMATTlNG INVOICE INFORMATION FOR THE DOD PAY-MENT SYSTEM USING THE ASC X12 TRANSACTION SET 810INVOICE (PROGRESS PAYMENT).

10.1 Introduction

10.1 Reserved

10.2 Control Segments

10.3 Reserved

10.4 Reserved

10.5 Data Element Cross-Reference Matrix

10.6 Reserved

10.7 DoD Convention

IOA Reserved

10.B Reserved

10.C Examples - Invoice Information From InvoicingParty to DoD Using ASC X12 810

10.D Reserved

10.E Reserved

10.F Reserved

9AEUNE AS OF: JANUARY 2133 109W

DEPARTMENT OF DEENE $60 INOICE P iDRAFT PrEMENTANON CONVENTION ANN ABC X12 VE l W----OO_-

f{BLANK PAGE)

10.OA BASEItNE AS OF: JNUARY M INU

DEPARUMENT OF DEFENSE 610 IVOICE (Proes. 1wmWQ

DRAFT .PLEMENTATION CONVENTION ANSI AC X12 VERSION/ELEAS mIoo_

-* 10.i INTRODUCTION

This is an Electronic Data Interchange (EDI) systems designdocument that describes the standard or 'convention' theDepartment of Defense (DoD) will use to accept an invoiceusing the ASC X12 Transaction Set 810 Invoice (003010). Itcontains information for the design of interface computerprograms that serve to link systems application computerprograms and an EDI translator computer program.

Who Needs to Use This DocumentComputer programmers can use this document to identify thedata in a populated EDI transaction with data requirements oftheir specific application database. Convenely, programmerscan identify where their applications data requirement shouldbe carried in an EDI transaction.

Why Use a ConventionThere are more ways to populate an EDI transaction than thereare ways to fill out a blank form. A convention defines the rulesfor filling in or "populating' an EDI transaction with a specificdata set. Following a convention ensures the integrity of datathat is produced and processed by EDI capable computer sys-tems.

ContentsFour sections are included in this document.

"* Section 10.2, Control Segments, identifies the specific datarequirements for formatting the EDI interchange controlsegments when sending and receiving EDI transactions.

"* Section 10.5, Data Element Cross-Reference Matrix, liststhe data requirements of DoD and specifies where each dataelement should be carried in the transaction set. This sectioncan be used to map an existing application database into thetransaction set.

"* Section 10.7, DoD Conventions, lists the layout of the targettransaction set by segment and data element. Identifiedalong side each transaction set data element is the cross-ref-erence data element from Section 10.5. This section can beused to interpret segments and data elements of a populatedtransaction set.

"* The Appendix contains an example of a populated transac-tion set.

SAlEUNE AS OF: JANUARY 291083 10J.1

OVARTUMN OF DEPUMU 610 VWOIC! (r~u PipnyinDRAFT IMPEMIENTATION CONVENTION AMAMC X12 VENON/fLEAUh MMODOO

f{BLANK PAGE)

1012Z MEKUNEAS OP: *AMWWU 136

DEPARTMENT OF DEPENGE 10 WoVOICE (Pvomm Pneg.Q

DAIAFT IPLEMENTATION CONVENTION ANNI AC XI2 VERIOWI.•EME IDO0

p 10.2 Control Segments

OverviewThis chapter describes the Electronic Data Interchange (EDI)control segments (interchange control segments and functionalgroup segments). The control segment information was derivedfrom the ASC X12 Standards Draft Version 3 Release 1(003010).

PurposeThis chapter identifies specific data requirement for formattingthe EDI control segments when transmitting and receiving EDItransactions. The format and data content of the control seg-ments is usually managed by EDI translation software. The datarequirement described herein should be used to set controlsegment format when installing or initializing translationsoftware for transmission and reception of EDI transaction.

ContentsTwo items are included in this chapter.

"* Table 10.2-1, Interchange Control Segment Hierarchydescribes the control segments in their order of occurrencein an EDI communications interchange.

"* Table 10.2-2, DoD Convention ASC X12 Control Segmentsis a detailed description of the Department of Defense dataconventions for formatting EDI standard control segments.All segments identified in Table 10.2-1 are broken down anddescribed by their discrete data elements.

IUSEU.LNE AS OF: JANUARY U IlUS 10,11

DWPANTMENT OF DUENE61 MNOICI (Pow.Um PrmDMPT OPCOMEfAIIO CONVOJIION £IW CXII amONLE en061

f{BLANK PAGE)

14A2.2MLIMO:MSW O

DEPARTMENT OF DEFENSE 610 INVOICE (Pm.sp Pym.p

IDAFTrr wPLEMENATION CONVENTION AMU ABC X12 VEIIION L 0EAE eMO 600

TABLE 10.2-1

Control Segment Hierarchy

UE ALNEA JANMAIW U1163 10.3

DEPAKTMENT OF owEIU 110 WouCE ""n"~s Pm"siDRAFT PLE!MENTATION CONVENTION ANN AMC X12 OEUWL M O 0U100

f BLANK PAGE)

102A §SAULNEAS OP:JANUARY2U 136

DEPARTMEN OF DEFENSE $10 INVOIE P"rogrss PGyMeuDRAF'T 11MAEMNTATION CONVENTION ANSi ASC X12 VER~bJoMMELEASE 00M01000

Interchange Control EnvelopeControl Segments

Poesag R*qNo. ID Nams D Un Loop

USE 10 IMA Interchanp Control Header M I

USE 20 08 Functional Group Header M 1

* Grouped Transactions

USE 30 GE Functional Group Trailer M 1

USE 40 lEA Interchange Control Trailer M 1

ASELUNE AS OF: JANUARY20 1063 10.2io

DEPARTME14r OF DEPMIS 616 WvOSC vvpmý P"Mws4DRAFT IMPEMENATION CONVENTION ANSI AC X12 o~uOfLAE0U61 000

{ BLANK PAGE}

10*.U BELINE MSOP: JANUAW M Ina

DEPARTMIENT OF DEMNUS 410 INVOICE(u Prim=*

DMF~T IMPLEMENATAION CONVENTION ANM MC X12 VERUON/LEMEA UUIODOO..

* TABLE 10.2-2

DoD Convention

ASC X12 Control Segments

&MIEEUNAS OP:JANUARYUIUS 19.L7

DEPARTMENT OF DEFENSE 415 UWFOOCE lPp.. PaYMu4DRAFT PPLENEN~rTMIO CONVENTION ANNI 8C X12 -EUNSLM -b-DO.

{BLANK PAGE)

10.2. MSEUE AS OP. JWAMN aU Iw

oEpARTMEN oF OEFENs SE InoWocICn( og.se PuIMu4DRAFT IMPL.MENTATION CONVENTION ANM ASC X12 V!SION/WREL.EAE SOM80ooo

seqmwit ISA Interchange C~ontrol HeaderUsage: M

Purpose: To start and identify an interchange of oneor more functional groups and interchange-related control segments. The actual valuesof the data element separator and the seg-ment terminator for this interchange areset by the interchange control header. Fora particular interchange, the value at thefourth character position is the data ele-ment separator, and the value of the latcharacter position is the value of the seg-men terminator.

Nots: The interchange control number value in thisheader must match the value in the samedata element in the correspon inter-change control trailer.

Dat Element SummaryRet. Dam

1SAOI 101 A owhr jn korn on M ID 2/2

Code to identify the type of information in theAuthorization Information.

Authorization Qualifier[001 1 Cod. Definition

00 No kAuftoalon Abwirww Mreeast

LSA02 102 Aha-rluton -nloonvtlon U AN 10/10Information used for additional identificatn orauthorization of the sender or the data in the inter-change.

Authorization hrdo[002 1

N no aumtho•rzlon t 11om Isagreed to by Udrnog paurtier. 9

fkdd wih zomee

t8A03 103 Securlty WnornsUon uefller H ID 2(2Code to identify the type of information in thesecurity information.

BAEUINE AS OF: JANUARY 2 II 1MIQ

DEPARTMENT OF DEFENSE 8i1 .NVoCE (Pr uss PNOU"DRAFT IMPLEMENTATION CONVENTION ANW AC X12 VERMIONLEAE 0161 OD0

Security Quaiuler[003 J Code Definition

00 No secrity Wnformadon present.

ISA04 104 Security Infornation M AN 10/10This is used for identifying the security informationabout the sender or the data in the interchange.

security Into(004 ]

If no security informaton is agreedto by trading pIrtneo, fill field with

zeIses.

ISA06 106 Interchange Id Ouuilfer M ID 2/2Oualifier to designate the system/method of codestrucure used to designate the sender 1)D elmbeing qualified.

Sender OualIfier[005 1

Urns authorized X12 code list

ISA06 1IN Interchange Sender's Id M ID 15/15

Identification code published by the sender forother parties to use as the receiver ID to route datato them.

Sender Id1006 1

DoD activities un Department ofOsfonm Activity Address Cods(DoDAAC) or other cods coor-

dinated with the value-added net-work (VAN). Non-DoD actities un

Identification cods qualifild byMA05 and ordtnasd wlit ths VAN.

Im07 06 Interhne Id mQuo•r U IDCode to identify the type of information in theAuthorization Information.

Interchange Qualier[oo7 I

ULn authorized X12 Code st.

10.2.10 UELUNE AS OF: JANUARY 29119M

DEPATMENT OF DEN=SE 410 svoeca (Progress Pa-u'DPAFT IMP2EMENTATION CONVENTION AS AIC X12 VENSIOW LEA SEM M0G6100_

ISA08 107 Intrcldnge Mole M ID 1W5I/Identi••cation code publisbed by the receiver of thedata.

Receiver Id1008 1

DoD activitie um Department ofDosine Activity Address Cods(DoDAAC) or olter code cowr-

diCuted with the valuehadded net-work (VAN). Nan-OaD tivitles use

ldenthfloatlon code qualid byISA05 and coordinated with the VAN.

ISA9 106 Interchange Date M DT 6/WDate of the interchange.

Date[009 1

Assigned by tranatiton oftwre.

ISAIO 10 Intercdange Time M TM 4/4Tume of the interciange.

S~Time

1010 1Assigned by tarmitlon sowar.

1OAll 110 Inrdarmnge Conlolt Mandard M ID 1/1IdentwCode to identify the agency responsible for the con-trol standard used by the message that is enclosedby the interchange header and trailer.

Standards Id[011 ]

ISA12 Ill Inerwhnge Conroi Verson M ID 5/5This version number covers the interchange controlsements and the functional group control segments.

Version Id[012 ]

V'rsion IDtw defined or agreedupon by the tading pitners

Code Dearkmo0O310 Oa - fdrd • Tr Ue Appfoe hr

fubloeao by ASC X12 Prooedurs bvlswbeow Through Ostbw aINO

9AEJN AS OF: JANUANY n 1993 1OJL11

DEPARTMENT OF DEFNUSE 810 wvoca4ri PamuwDI1Irr iPLEMENTATION CONVENTION ANSIA DC X12 INJHELEASE 01010000D

ISA13 112 Inelncdhenge CoMol Number I NO 9/9

This number uniquely identifies the interchangedata to the sender.

Interchange Control Number[013 1

Assigned by ansliaion software.

ISA14 113 AcknowledgmntM RequeLsed H ID 1/1Code sent by the sender to request an interchange

Acknoowledgment Request[014 1

Code value agreed upon by trading

Code Definition0 No n I sinemnt Flques.dI brmmm e nen P•U0

ISA1I 114 Test Indkiceor M ID 1/1Code to indicate whether data enclosed by this inter-change envelope is test or productio.

Tea Indicator[015 1 0

Code value agreed upon by tfrding

Cad. DefinitionP ProduolDtT Ted Deft

ISA16 115 Subl.enea Sepenltor M AN 1/1This is a field reserved for future expansion inseparating data element subgroups.

Subeleert Sepwarao[016

Use ASCII oOara:er 5111, colon

10.L.12 UABELJNE AS Oft JANUARY 291192

DWoTMN OP , WEDU me mvoe (Progess Pum•DMAFl iMNLEMUTA1ION COOENION AN mA WR5IoSLE~h• 00 0Mo0o0

Segment: GS Functional Group HeaderUsge: M

Purpose: To indicate the beginning of a functionalgroup and to provide control information

Commsto A. A functional group of related transac-ton sets, within the scope of X12 stand-ards, consists of a collection of similartransaction sets enclosed by a function-al group header and a functional grouptrailer.

SYntax Nolm' 01 The data interchange control number(GS06) in this header must be identicalto the same data element in the as-sociated Functional Group Trailer(GE02).

Data Ehenwnt Summryw DowDO& ElmmNie AOMMbS

GS01 479 Funcional Id Code M ID 212Code identifying a group of application relatedTransaction Sets.

Functional Id1020) Code Deflnhlon

IN 810-hMwoloekwnnltmi

ChooW the Code vako appmpd.ato Vo Insmawco cofidot of the

funlonal group. See X12 Oldonayfar eoauoe code let

GM2 142 Applatlon Sender's Code H ID 2/12Code identifying party sending transmission Codesagreed to by trading partners.

SenderVs Code

[0211

DoD eatM• es use DepekwnK ofDenmse Aovk* Addrme CGdo

(DCO ). Non4b00 s ete usedenlfleameon code mselied by 0ooaSoU. ommeNdM for b

Nourfthet nOn-D00 code dierfrom toi used in M ILS

0S03 124 ApplicatIon ReI• ver's Code M ID 2/12

Code identifying party receiving transmission. Codes

BSM5EJEA OP: JANUMNYWI 00105 5±

DWPARrIMENT OF DEP3J11 meo WO0CE Fpn P yImIIDRAT IMPLEMENTATION CONVENION AM ABC X2 V N-NE O 000

agreed to by trading partners.Receiver's Code

[0221

DOD activitiee u Departrent ofDefense Activity Addrew Code

(DoDA). Non-OoD aOtNl useIdentiflatlon ode assigned by DoD

activity. Pommrnend for Iresedsecurtty that non-OD code differ

from "it used In 151•A.

G804 29 Group Date H DT 4ViDate sender generated a functional group of transac-tion sets.

Date[0231

Assigned by tanelation software.

GS0 30 Group Time M 7M 4/4Tine (HHMM) when the sender generated a func-tional group of transaction sets (local time atsender's location).

Time[024 O

Assigned by Vanslataon software.

GS06 28 Group Coalro" Number M NO 1/9Assigned number originated and maintained by thesender.

Group Contro Number(0251

Assigned by tanslation sotware.

GS07 456 Resposbie Agency Code M ID 1/2Code used in conjunction with Data Element 480 toiden* the issuer of the standard.

Agny Code

Indicts Miat an ANSI X12 stadardIs being Vanemnittsd.

Code DefinitonX Accredited Stedmlarde Comnmilte X12

G0M0 460 Veulon/Re*le/nduey Id

10.2.14 BASEUNE AS OF: JANUARY 9 Iam

DEPARTMWN OF DEFENSE s1 mogVOC110480U PammouDPAFTr ON4MENTAYMO CONVENTION AMASICX12 OMOOLESE0U O 00

H ID 1/12

Code indicatin the version, release, sxcubrles andindustz identifier of the EDI standard being used&(See X12 Dkctosary)

Veru~orVRekaIem(027 1

Cods value eard 1o by ftadinpaimrorn See X12 WOlcmnay for

sourns cod* NaLCode DodU0O10 Imft Shndu* Appoved By ASC X12 Thruouh

June low

BASELINE AS OP: JANUARY 0 IM5 10A±15

DEPAR NT OF DEFENSE vc (Prge P-sjegDIAFTI IMPI.MENTATION CONVENTION AN ASC X12 VESOIEEAM 0M900OO_

Segment: GE Functional Group TrailerUage: M

Purpose: To indicate the end of a functional groupand to provide control information

Comneet A. The use of identical data interchangecontrol numbers in the associated func-tional group header and trailer isdesigned to maimize functional groupintegrity. The control number is thesame as that used in the correspondingheader.

Syntax Notes 01 The data interchange control number(GE02) in this trailer must be identicalto the same data element in the as-sociated Functional Group Header(GS06).

Data Element SummaryReL D.D Elemnt Name NWbufte

GE01 97 Number of Included Sets M NO 1/4Total number of transaction sets included in thefunctional group or interchange (transmission)group terminated by the trailer containing this dataelement.

Number of Segments[028 ]

Assigned by Oe tranealancsoftuwar.

GE02 28 Group Control Number M NO 1/9

Assigned number originated and maintained by thesender.

Group Control Number[029 1

Assigned by #we tVwwesoftware. This control number mut

matc h the contrl number of thepreceding GS0S cont=M number.

10.1e MAlLIEN AS OF: JANAW U IM1

DEPARTMENT OF DEFENSE 0 WOSE (Fmu PuWOuWDrAFT WLAEMETAION ,ONVEUTO ANSI C X12 VOMMO0000

Segmeut lEA Interchange Cotrol TrailerUsa": M

Pupoes: To define the end of an interchua of oneor more functional groups and interchangerelated control segments.

Note: The interchanp control number in thistraier must match the value in the same dataelement intheO coreponding interchangeheader.

Data EInunt SummaryNif. DabDo& 1esmei Nm MWIsts

IEAOI 116 Number of Inckxded Funcetonel A NO 1/5GomupsA count of the number of functional giroups in-cluded in a trmmniuon.

FunctVonal Group Court[040)

Aasd by trwaeaon oft~wro.

IEA02 112 Interchange Conlrol Number M NO 9/This number uniquely identifies the interchangedata to the sender.

Interchange Control Number[041 ]

Agrnod by tle~adon software.Tise number must matoh tas num-

ber toat ooous In ISAI&

ASELUE AM OF: JANUARY 190 ILL17

DEPARTMEN OF DEFES W10 INVOICE (proýa PsORNODRAFT PAPLEMENTATION CONVENTION ANWSI CXII VERUONLEAWE OhM 00..

{BLANK PAGE)

10±13 NASEUNE AS OF. JANUARY 0 106M

DEPAMENT OF DEFENGE aie m oeCZ (Pum• P-m1muDRAFT BMP4,MENTATnO COWVENTI AI AC X12 VERONJMLEME GUM ool k

10.5 DATA ELEMENT CROSS-REFER-ENCE MATRIX

OverviewThis chapter lists the data element cross-reference between theDepartment of Defense (DoD) ASC X12 Transaction Set 810Invoice (003010). We derived the cross-reference from the fol-lowing:

"* Examination of DoD invoice information data requirements.

"* Analysis of ASC X12 Transaction Set 810 Invoice.

"* Comments submitted by DoD activities involved in the DoDelectronic data interchange effort.

PurposeThis chapter identifies specific data in an application and theircorresponding EDI mapping into the Transaction Set 810. Dataelements from an existing application database can be identifiedwith elements in this cross-reference. If no application exists,the cross-reference provides enough information to develop adatabase design to automate the application. With an applicationin place, this cross-reference will expedite mapping of thedatabase into a commercial EDI translation package. All tradingpartners who plan to exchange the 810 with DoD can use thisdocument as a reference for the development of theirdatabase/ED! translator interface program.

ContentsOne table is included in this chapter. Table 10.5-1, Data ElementCross-Reference lists all the discrete data elements of the DoDinvoice data i quirements and their corre-sponding segment anddata element of the ASC X12 Transaction Set 810 Invoice.

BUStELJINE AS OF: JAUR U0 1Ut3 IWL

DEPARTMEN OF DEFENSIE 810 WVOICE (Piega pwDRtAFT 094EMMNATION CONVENTION AMNSI C X12 VENSSOW/IELEAS WMU1 OOD

f{BLANK PAGE)

WAS. SASEUN AS OF: JANUARY U9 135

DEPARmMEN OF DEFENUE 610 IVOICE (PU Pom sInM

DRAFT IPLEMENTATION CONVENTION ANN1 ASC X12 VEBION LEASE OOOMO.

TABLE 10.5-

DATA ELEMENT CROSS-REFERENCE

DoD Invoice Data Using ASC X12 Transaction Set810 Invoice.

How To Read This TableTable 10.5-1 cross-references discrete DoD invoice data require-ments to the corresponding segment and data elements of theTransaction Set 810. The following definitions explain how table10.5-1 is organized. Understanding the information in this tablerequires familiarity with EDI standards.

Govenmeont ReferencoeThe first three columns on the left in Table 10-5-1 identify thespecific invoice data element.

* INVOICE DATA NAME: Lists individual data elementsrequired to send an invoice. The user should identify theseelements with a data name in their internal database system.

* INDEX: Three entries may appear in this column and rep-resent various levels of indexing used to sort the data namesin a data dictionary.

* Q: An asterisk (*) in this column identifies the data as aqualifier code.

EDI ReferencesThe remaining seven columns identify the detailed mapping ofeach data name into Transaction Set 810. Using these referencesis explained below in "How To Use This Table'.

"* AREA: The area of the transaction set where the data ismapped. A - header, B - detail, C - summary.

"* POS: The sequential position of a specific segment withinthe area of the transaction set.

"* REF DES: The first two or three alphanumeric charactersidentify a transaction set segment; the last two numericcharacters in the column identify a data element position inthe segment.

"* DE #: The EDI data element number that appears at thatposition in the segment.

"* VALUE: The recommended code value(s) that should beA:1used.

@MWSEIJ AS OF: JANUARY U166 0.

DEPARMENT OF DEFENSE 616 INVOICE (P.lem op w P"OMRFr 00EM rMAIO CONVENTION ANN AC X12 VERIeIONERRE M ODO.

* DoD CONVENTIONS: Additional information about thedata as they apply to Department of Defense use.

How To Use This TableThis table maps a data element to a specific data element in anEDI transaction set.

1. Select any data element from the INVOICE DATA NAMElist,

2. Identify the AREA, POS, and REF DES for that DATA

NAME,

3. Go to Table 10.7-2 DoD Segment Hierarchy,

4. Find the AREA (Table A - header, etc.) in the hierarchy,

5. Locate the segment that corresponds to the POS and the REFDES. NOTE: The POS may not appear in some hierarchy tables.In this case, use the segment id identified by the first 2-3characters in the REF DES,

6. In the left-hand column, identify the page number of thesegment Id,

7. Turn to that page number in Table 10.7-3,

8. Now in the conventio, table 10.7-3, find the REF DES fromstep, 2 under the Ref. Des. column on the right hand side ofthe page,

9. You have now mapped a data element from table 10.5-1 intothe convention table 10.7-3.

The INVOICE DATA NAME from Table 10.5-1 appears in theright hand column along with its INDEX and the DoD CON-VENTION. The EDI standard definition of the data elementappears in the right hand column of the page.

Each INVOICE DATA NAME from Table 10.5-1 can bemapped into the transaction set in this manner.

10, MSIIJ@NE AS 1OF: JANUARY 136M

DEPARTMENT OF DEFENSE 810 WOSCE (PWums PumyýDRAFT PLMENTATION CONVErN)iN ANS ASC XI 2 VERSIN/RLEASE 0001kO

{BLANK PAGE)

KASEUNE AS OF: JANUARY 29 MUS .

E*

8 c

0 LI I E

1 8

Iai1: 1:

C.- Vaf

-as a iON' Its;.

E cC E uzzi's c~a -aa-

'a.z SV OfA~ AEIl .o 0 co S S *

- - ----- ......

d- I !I6 ! I I I

i Jfi

Ii l I i I m l l l l lII

*11 . ,S

II I I ,

2iii i~iti

-! f!,llall

I.I ,-•-. II IE

J ii Ili I

L -. b- 0j1-

. . . .. . .

* I I i

liii ta Inil I f - - ii I

o- -� I.

!jIS I S� a.

1� i IU a

I I i*g� -

0 -

0 8 2 *1 II I � I

IA a I

IS S

I* 3 Cu

I I I I5 5 5

a e a a

p - -

4 Cu Cu Cu Cu Cu Cu Cu Cu

a 0 0

1'11111 ii

ii I Ii'Ii, IiI; If II

I ii' .1SI .

I I w

* p I

I I _ S C

S U I__ _i

-I 2 2 IJ

DEPARTMENT OF DEFENS SG~, iWVoWE (p opm PmymuoDRAFT IMPLEMENTATION CONVENTION ANN A*C Xli VERNfIOW ASE OS1OOO.

f{BLANK PAGE)

10.5.12 ~ASEJJNEAS OF: JAJIIMMV im

oE.PWARM OF DEFENS# MOMOCE(Pr.. Pmwo

DAFT ALEMETAT1'N CONVENnO A A AISC XMCI VERION/FAMAE O 10000*

p 10.7 DoD CONVENTIONS

OverviewThis chapter is the convention for the ASC X12 Transaction Set810 (Version 003010) as used by the Department of Defense foraccepting an invoice. It was derived from:

"* Table 10.5-1, Data Element Cros-Reference Matrix that

describes the discrete DoD data requirements for invoices.

"* ASC X12 Transaction Set 810 Invoice.

A relational database management system was used to mergpthe Data Element Cross-Reference Matrix and a TransactionSet 810 database into the subset of 810 segments described intable 10.7-3 of this chapter.

PurposeThis chapter contains all necessary information for a DoD trad-ing partner to map and translate a Transaction Set 810. Alltrading partners who plan to exchange the Transaction Set 810can use this document as a reference for the development oftheir EDI database/translator interface program.

ContentsThree tables are included in this chaptr.

"* Table 10.7-1, ASC X12 Transaction Set 810 Segment Hierar-chy describes the 810 segments as they appear in the ASCX12 Standards Dictionary.

"* Table 10.7-2, DoD Model Transaction Set 810 SegmentHierarchy describes the subset of 810 segments used forsending Progress Payment invoices.

"* Table 10.7-3, Conventions is a detailed description of theDepartment of Defense conventions for transmitting Trans-action Set 810. All segments identified in Table 10.7-2 aredetailed in Table 10.7-3 by segment, position, and codevalue.

AMAIEUINE A.8 OF: JANUARY U IlUS 10.7.1

DEPARTMENT OF fhwhJU 810 NsWoE pou. P.wuuoOMPYT 11MEANWTAION CONVENTION AWAI C X12 VErONIVLEJA UHft0OO_

{BLANK PAGE)

10.7.2 BASEUNE AS OF: JMNIMRY U ImIK

DEPARTMENT OF DEFENSE 810 IONOICE (pvepm Ps#MuN

DPAIFT IPLEMENTANN COwNVENTO ANSI MSC X12 VEMIOLEAAE OMiODOCL

TABLE 10.7-1

SEGMENT HIERARCHY

ASC X12 TRANSACTON SET 810

INOICE (Version 003010)

BAEUNE AS OP: JANUARY U 1I6 16W7.3

DEPARTMENT OF DEFENSEiEOSE(r9s.PynnD.(,T 1111EJMENTATION CONVENTION ANM ASMC VEION/RELEMSE 11hh08 DOD

f BLANK PAGE}

10.7A LASEUINE AS OF: ANLUAM 39 IW

DE, ,nMENT OF DEFENSE 610 WVOICE (pU Pn. U.ODRAFT RAPLEMEDITATMO CONVENTION AIM MSC X12 VERSIMMMLEASE MW 0000

ASC X12.mx Transaction Set8l0V310Transaction Set Name and Version

Segment Hierarchy

Table 1 - Header Area

PoeSeg RsqNo. ID Nins Dae Use Loop

USE 10 ST Transaction Set Header M 1

USE 20 on Begins* Segment for Invoice M 1

30 NTM NoberSpecial lastruction F 100

40 CUR Currency 0 1

USE 50 REP Reference Numbers 0 12

60 PER Administrative Communication 0 3Contact

USE 70 N1 Name 0 1 NI\200

USE 10 N2 Additional Name Information 0 2

USE 60 N3 Address Information 0 2

USE 100 N4 Geographic Location 0 1110 REF Reference Numbers 0 12

USE 120 PER Administrative Communications 0 3* Contact

USE 130 T10 Terms of Sale/Deferred Terms of 0 5Sole

USE 140 DTM Dete/Time Reference 0 10

150 FOS F.O.B. Related Instructions 0 1

140 PID Product/Item Description 0 200

170 MEA Measurements 0 40

160 PWK Papework 0 25

190 PKO Marking, Packaging. Loading 0 25

200 L7 Tariff Reference 0 1

Table 2 - DeOW Ares

Poe Soo ReqNo. ID Nm Den Urn Loop

USE 10 M Baseline Item Dota (Invoice) 0 1 IT1\00000

2 CUR Currency 0 1

30 IT3 Additional Item Data 0 a

40 TxE Tax Iaformation 0 1060 CTP Pricing Information 0 25

MIASELINE AS OF: JANUARY 2 1190 10.7.5

DEPARMTEK OF OVIEM tie NVasE oplopm prom.OMPFT__PLUAMENATION CONVENTION AWACXII - -u UUIOWM4OD-

I0.7A MEUNE AS OF- JANUARY 2 ION

DEPARTIMENT OF DEFENSE 1110 INVOICE QVIOW0101 PinymaiDRAFT 11IPL.EUENTATION CONVENTION ANSI AMC X12 VRINLES m 00MD00

so MEA Measurements 0 40

so POD Product/Item Description 0 1 PIU\1000

70 MEA Measuremsents 0 10

60 PWK Paperwork 0 25

00 PKG Marking. Packngap. Loading 0 25100 PW Iteim Ph,.ical Details 0 1110 TTD Terms of Sale/Deferred Terms of 0 2

Sale120 RPf Reference Numbers0130 PER Administrative Comtmunications 0 5

contact140 $00 Destination Quantity 0 a00150 DTM DatefMse Reference 0 10

160 CAD Carrier Detail 0 1170 L7 Tariff Reference 0 1

130 TTA Allowance, Chargeor Servce 0 1 FTA\10130 120 Tax Information 0 10

USE 200 SLN Subline Item Detail 0 1 SLN'1000210 REP Reference Numbers 0 1220 PIC Product/Item Description 0 1l00

220 TTA Allowance, Charge or Servwce 0 10

240 N1 Name 0 1 N1\20025 H2 Additional Name Informastion 0 2

2110 N3 Address Informsation 0 2

270 N4 Geographic Location 0 1=0 MY? Reference Numbers 0 12

200 PER Administrative Commsunications 0 3Contact

Table 3 - Summasy AreaPos S"agmNo. ID Noms one U"n Loop

USE 10 TOG Total Monetalry Value Sumtmary M I20 10 Tax Informastion 0 1030 CAD Carrier Detail 0 1

40 TTA Allowance, Charge or Service 0 1 ffA\10

BASEUNE AS OF: JANUARY *919103 10.7.7

DEPARTMENT OF DEFENSE s10 bwvasc Pem m sDMPA__PLMER NTAIION COW49NTMO AMU AC X12 -E iL - -sM 000

10.7. LASEUNE M OF., JANUARY M ISIS

DEPARTMENT OF DEFENU m 0 INVOICE (Pr.gems Puymu"DRAFT IMPLEMENTATION CONVENTION ANI A•C X12 MA 0010000

S0 TXM Tax lforomatiom 0 10

so = Imeao Skipmat Summary 0 5

USE 70 CTI Transaction Totals M 1

USE 50 W Ttam•tiom Set Trailer M 1

EASEUNE All OF: JANUARY 2 13 1M.7.

DEPARIUENr OF DOW=N 310 EVOSCE (P op'. PqinnlDRAFT NAPLMENTATDW cowiYNTDom ANN ASC X12 WalSYMMLME OU310000

{BLANKPAGE}

10.7.10 BAOUN AS OF: MANIMRY n IM

DEPARTUMETOP DEFENSE 860 WdCOME 04pmos Puymm"

DRAFT IMPLEMENTATMO CONVENTION ANSI MSC X12 VERSIONIMELEASE 162010000L

TABLE 10.7-2

SEGMIENT HIERARCHY

DoD MODEL FOR TRANSACI'ON SET 810INVOICE

EASEINE AS OF: JANUARYM2006 10.7.11

DEPARTHME OPDFES 810W s wYOam (ping.. PavmoDMAFT PLEMENATON CONYEDION A9WMACXII VUOMON/LASE OMMO~O

{BLANK PAGE)

10.7.12 LASEUN AS OF: MANIMH m im

DEPARMENT OP DEFENSE si oYOSCE (pmgusI P1,111DRAFT RAPLEAMEIATMO CONfVENTMO AN AW CX12 WRMM-RELEAS 06 M1C00

ASC X12=r Transaction Set81V31OTransaction Set Name and Version

Segment Hierarchy

Table I - Heeder Arm

PMs sag RsqNo. 0 Nwam Doe U"e Loop

USE 10 ST Tranaction Set Header U I

USE U III Besizning Segment for Invoice M I

USE 80 NO Reference Number 0 12

USE 70 M Name 0 1 N1I\2

USE 90 N2 Additional Name Information 0 2

USE 90 NS Address Information 0 2

USE 100 N4 Geographic Location 0 1USE 120 PER Administrative Communcatios 0 3

Contact

USE 130 ITD Term of Sale/Deferred Terms of 0 5Sale

USE 140 DYE Date/Tame Reference 0 10

Table 2 - Dea Are

No. IDam Doe Lse Loop

USE 10 M Baseline Item Data (Invoice) 0 1 Tfl\UOOOO

USE 200 SLN Sublime Item Detail 1 SuN10

Table 3- Sumwr Area

oeDe Urn Loop

USE 10 TD Total Monetaty Value Summary M 10

USE 70 CTI Tnsaoction Totals M I

USE SO Se Transaction Set Trailer M I

MASEUNE AM OF: JANUARY 20 1•93 10.7.13

DEPARTIAENT OF DEENSE 610 WvOSCa Iv~ PiluDRAFT ANPLEMENTrATMO CONVENTION ANM ABC X12VRSNLAS 1660

{BLANKPAGE}

10.7.14 USEUJNE AS OF: JANUARY U 1663

DEPARTmENT O, DEN 510 WooCE OM(Prm PaWmu*

DRArl I MP t ATON COW4ETO AM ASC X12 V 003MOO1

TABLE 10.7.3

DoD 810 CONVENTION

How To Read This TableThis table contains two sets of references. ASC X12 referencesare contained in the right-hand column. Government referencesare contained in the left-hand column except for codes listswhich are included in the right-hand column.

Government ReerencesThe left-hand and middle columns in Table 10.7-3 describeDepartment of Defense conventions.

"* Left-hand column contains two general references.

> INDEX: is enclosed in brackets and corresponds to aspecific INDEX from Table 10.5-1.

> INVOICE DATA NAME: Appears above the INDEXand corresponds to a specific DATA NAME from Table10.5-L

"* Middle column: Contains a less-than sip to indicate whereDepartment of Defense conventions vary from the ASC X12convention.

To help the user determine the source data, the INDEX can beused to trace data elements back to Table 10.5-1.

ASC X12 RefeWenThe right-hand column describes the ASC X12 convntions. Theinformation included at the beginning of a segment descriptionis standard ASC X12 information. The subheadings listed underData Element Summary describe conventions for each dataelement in the segment.

> Ref Des, Data Element, Atributes: Three subheadingsdescribe the format of the segment as prescribed byASC X12.

> Name: Describes the ASC X12 data element and offersthe standard definition. It also lists the specific codevalues the Department of Defense prescrimb and mayprovide other Department of Defense information.

How To Use This TableThis table can be used to identify the data contained in popu-lated Transaction Set 810.

S

MEUEAS CU: JANUARY3 21003 10.7.15

DEPA•ANENT OF DOW= m omeVoSC (Pawn oDRAFT iMPLEMENTATION CONVENTONN ANA )C X VERlIONMMLEAM UMSOU 0000

1. Identify a segment from a populated transaction set (SeeAppendix 10.C for examples of the 810).

2. Look up the segment in table 10.7-3.

3. Read the right-hand column to identify the Reference Desig-nator (Ref.Des.). The Reference Designator combines the seg-ment id and the data element position to form a single identifier.

4. Read Ae left-hand column immediately adjacent to the Ref-erence Designator to find the discrete DATA NAME, INDEX,and DoD CONVENTION from Table 10.5-1 that is mapped tothat Reference Designator. When multiple DATA NAMEs ap-pear for a single Reference Designator, there is usually a codequalifier somewhere in the same segment that identifies the data.

10.7.16 SASEUN AS OF: JANUARY 2 IS

DEPARTMENT OF DEFENSE w@ IVOE (Pwee PqmuuDPAFT IIIMMENTATION CONVENTION AN•S AC XlI VEMIOW .LEAS m 0oo00

Segment ST Transaction Set HeaderTable: 1

Sequence: 10Usage: M

Max Us: 1Loop:

Purpose: To indicate the start of a transaction setand to assign a control number

Comment A. The transaction set identifier (ST0M) isintended for use by the translationroutines of the interchange partners toselect the appropriate transaction setdefinition (e€•., 810 selects the invoicetransaction set).

Data Element SummaryRet. 0atone. Bemnw NHame Abldmw

ST01 143 Transaction Sgletk lew Code M ID 3/MCode Uniquely identifying a Transaction SCL

Transaction Set Identifier Code

[001 A *]SThe iollowing commenr provie

vmapping Inwrucdons for estab.Nehing a reque fo a Progrm Pay.

merit

Code Definiton810 X12-2kwolo

ST02 32M TraneacUtonlSetConr Number M AN 4/9Idcntifyi*g control number assigned by theoriginator for a transaction set.

Transaction Set ControNumber[002 A I

Conrol No, (0ame number wil befound in SE2 In Summary).

LAEUNE AS OF: 21 MAY 19M 10.7.17

DEPARTMENT OF DEFENSE In0 IVOICE (Pm"res PqftmyDRAFT IPLEMENTATION CONVENTION ANSI ASC X12 VEMION/PRELEAE 60MO1OO0

Segmes: BIG Bqgnning Segment for InvoiceTable: 1


Max Use: 1Loop:

Purpose: To indicate the beginning of an invoicetransaction set and to transmit identifyingnumbers and dates.

Comment: A. BIGO7 is used only to further define thetype of invoice when needed.

Data Element SummaryRtef. DaelDes. SWemn Nori AftW5S

BIG01 245 Invoice Date M DT 6/6

Invoice Issue Date.Invoice Date

1003 A IIvIoie Dab, xprWesed as YY-

MDD. BLOCK 6b. The date of therequest for progress payment.

BG02 76 Invoice Number U AN 1/22

Identifying number assignld by issuer.Invoice Number

[004A IA unique number aussgned by theBilling Patty where required to do

so by company or DoD. BLOCK Se.

BIG03 323 Puchaee Order Date 0 DT 6/6

Date ausgned by the purchaser to Purchase Order.Purchase Order Date

1006 A IIf no Invoice numbnr, Inle a zero

(0). See REF segmem for ProgessPayment Number. BLOCKS 7a end

7b.

10.7.18 SASEUNE AS OF: 21 MAY 1I3M

DEPARTMENT OF ODEFENE `10 IVOICE 4P,,oe0 P11u10DAFT 'PLErUNTATION CONVENTION AIM ADC X12 VUWEMS dEAM oUto 6000_

BIG04 324 Putme Order Nu e 0 AN 1/22Identifying number for Purchase Order asiged bythe orderer/purchaser.

Purchase Order Number[006A•

Procurement Instrumen kecdfca-dion Number. (PUN). BLOCK 4.

BIG06 328 Release Numnbr AN 1/30Number identifying a release aaist a PurchaseOrder previously placed by the parties involved inthe transaction.

Release Number(007A A

Call/order number. BLOCK 4.

B1006 327 Chong* Order Sequene Nunder 0 AN 1/8Number assigned by the orderer idestifft aspecfic chMae or revision to a previouy trms-mitted transaction set.

Change Order SequenceNumber(00o A I

Moxdlicatio Number. (SPUN).BLOCK 4.

0IG07 640 Trnection Type Code 0 ID 2Code specfying the type of transactiom.

Transaction Type Code1009A *1

Use code FE for a sellig petygeneraad request to withdraw,

wihout prooeng. a prucudy sub-nmited reques for a pogrem pay.

Code Derkltio.CO CofwfnsdPA Pl• orsPaymntRE Ral

BASELINE AS OF: 2! MAY IM 10.7.10

DEPARMIEN'r OF DEFENSE ar0 invOICE (Pmesm Ptwy lqDRAFT IMi.EMENTATION CoNvENTION ANSI MC X12 VERSIOWNIILEASE OWl DOC

Segmet: REF Reference Numbers"Table: 1

Sequence: 50Usage: 0

Max Use: 12

Loop:Purpoee: To specify identifying numbers.

Syntax Notes: 02 Either REFO2 or RER)3 is required.

Data Element Summaryneo. DeOM

REFOI 128 Reference Number Ouslfier M ID 2/2Code qualifying the Reference Number.

Reference Number Qualifier[010 A -1

Use code VR In, anry th seller's uni-cque kIenofkastion number. Code

PX maps o Oie blank apses In theorfkaion peragraph.

Code DefintonPX Previous Invoi-e NirmberVR Vandr ID Number

REF02 127 Refterece Number C AN 1/30Reference number or identification number asdefined for a particular Transaction Set, or asspecified by the Reference Number Qualifier.

Reference Number[011 A I

REF03 352 Description C AN 1/S0

10.7.20 ASELINE AS OF: IL MAY IIU

DEPARTMENT OP DEFENSE 610 INVOICE (PieUesi Pinom4DRAFT PLEMENTATION CONENTION ANS AMC X12 VERUGOMNLEASE Ioomoo.

Segnent: N1 NameTable: 1


max U: ILoop:

Pupome: To identify a party by type of organization,nam and €ode

Commet: A. Thissegment used alone, provides theaoe efficient method of providing or-ganizatimal identification. To otainthis efficiency the "ID Code' (N104)must provide a key to the table main-tained by the transaction procesmingparty.

Syntax NOeW: 01 At least one of N02 or N1a3 must bepresent.

02 If either N103 or N104 is present, thenthe other is required.

Data EBNMwt SumnmryRO. Deft

De,. EmmU mm Allbate• -_ ___N101 90 EnUty denWlr Code U ID 212

Code identifying an ruiationual entt•y or a physi-cal location.

Entity Icwentier Code[012A *]

se code SE whem the eing9 partyIs a large business. Use code 21when the slno pwtty is a mal

un. BLOCK &Code DeOnAWe21 saim 0aumsBy 0,WAn Pett (PwhmsaesrPR %"WSE SslV P"

BASELINE MOF: 21 MAY I0M 16.721

DEPARTMENT OF DEFENSE 310 SWCE OPe PwiffmleDRAFT 1rIMPLEMENTATION cO n O ANN ASC Xl2 VER.SIO1WNELEAS OI3RDOO.

N102 93 Name C AN 1/32Free-form name.

Name[013A I

Use only when addres of the Sell.Ing PWty (N101 code SE) cannot be

scribed using that pa"rs CAGECode (N103 code 33 an N104, the

acta CAGE Code). BLOCKS I(codes BY and PR) ad 2 (code

SE).

N103 66 klenff atlon Code Qwusl C ID 1/2

Code designating the system/method of code struc-ture used for Identification Code (67).

ldentfcatlon Code OualMer[014A *1

Use code 10 when N101 Is codePR, use code 33 when N101 is ode

21 or SE, use code f when N101Is code BY. Code ZZ Is Ohe DFARSAppendix G Code of the BuWA Ol-

fice.CoD.t Deflndon10 Dep Waun nt of -eee clity Code MDOAC)33 Comnwmnecand Go•• mmn Enly (CEZZ Mutualy Dfined

N104 67 kkdnhcou, Code C ID 2117

Code identifying a party.krication Code

015 A I

The acual DOWAC of P@yfng Of-flao, CAGE Code of Selling Paty, crDoeees Federal Acqulesiton Regula.on Supplement (DFARS), Appendix

N Code f te tbylng Ofie.NOTE: DFARS Appendix N Is now

Appendix M

10.7.22 MEULMASOP. 2 MAY 1h0

DEPARTMENT OF DEFENSE 1110 INVOICE (Progress POymm4DRAFT IMPLEMENTATION CONVENTION ANIM ABC X12 BUS0MLU 1M G L0000

&*am*t N2 Additional Name InformationTable: 1


Max Use: 2Loop:

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

Data Element SummaryRd. DateDes. ement Name AMulsms

N201 93 Name U AN 1/35Free-form name.

Name[016A I

Uis only when address cannot bedescribed using a code In the NI

segment.

N202 93 Name 0 AN 1/35Free-form name.

Name1017A I

Use only when address cannot bedescribed using a code In the NI

segment.

BASEUNE AS OF: 21 MAY 1 M 10.7.23

DEPARTMENT OF OFvNS Ina INVOwCK (Poue PSeYMsDRAFT IMPLEMENTATION CONVENTION AN= ASC XI1 VEMIO1fRELEASE 013IODOO.

Segment N3 Address InformationTable: 1


Max Use," 2Loop:

Purpoee: To specify the location of the named party

Data Element SummaryROL DateDos. Berne Name AtWbutls

N301 186 Address Informailon M AN 1/35Address information

Address Informatlon[OlBA I

Us. only when addres cannot bedecdlbed using a code In 9h NI

segment. (If used, arry home suchas building number, skeot name,

sufts, appar•ment or office number.For example: 10 Main Street, Suite300.).

N302 166 Address Infor•mlon 0 AN 1/35

Address informationAddress Information

[019A IIK needed, an additional 2d line of

address, use only when addres can.not be described using a code in

the N1 segment

10.7.24 BASEUNE AS OF: 21 MAY IMI

DEPARTME• T OF DEFENSE 410 INVOICE (Prgesm Ps'mssDRAT *PLEMENTAT1ON CONVENTION ANA ScMxVERUIOFNELEASE 00 o0000._

Segment N4 Geographic LocaticnTable: I


Max Use: I

Loop:Purpoee: To specify the gographic place of the

named partyComMuIt: k A combination of either N401 through

N404 (or N405 and N406) may be ade-quate to specify a location.

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

Syntax Notes: 01 At least one of N401 or N405 must bepresent.

02 If N401 is present, then N402 is re-quired.

03 If either N405 or N406 is present, thenthe other is required.

Data Element SummaryM Re Dot sOw~ Gwruw Name rb

N401 19 City Name C AN 2119

Free-form text for city name.CIty Name

[020 A ICity Name, use only when addresscannot be desclbed using a code

In the N1 segment

N402 156 State or Province Code C ID 2/2Code (Stawdard State/Province) defined by ap-proplate governmental agencies.

State or Province Code

[021 A ]Two-chwacter code for Stte.

BASEUNE AS OF: 21 MAY1952 10.7.I5

61 I|OC

DEPARTMENT OF DEFENSE 610 EVOICE (Progras PwimsoDRAFT NAPLEMENTATION CONVENTION ANSI AMC XVIO E MUmSoWoo

N403 116 Postal Code 0 ID 4/SCode dcfniwg internat;oal posal rone code cziud-ing punctuation and blanks (zap code for UnitedStte).

Postal Code[022A

2p Code.

N404 26 CountryCode 0 ID 2f2

N405 300 Location Qualifier 0 ID 1/2

N406 310 Location dentMer C AN 1/25

10.7.26 BASE.UNE AS OF: 21 MAY 1IW

DEPARTMENT OF DEFENSE GIG UIVOICE (PI~wsUSftDRAFT IMPLEMENTATION CONVENTIO ANSiMXI AC12VEROKONLEASE0011000.

Segment: PER Administativ COnmunICAtIOflContact

Table: ISequen=: 120

usage: 0Mtax Use: 3

Loop:Purpose: To identify a person or office to whom ad-

ministrative communications should bedirected

Syntax Notes: 01 If PER03 is present, then PER04 is re-quired.

Data Element SummaryRed. DOMaDeoc Eiemeet Name AUMN0100

PER01 366 Contact Function Code M ID 2/2

Code identifying the major duty or responsibility ofthe person or group named.

Contact Function Code[023 A *1

Us. code CE for the name of thecontractr representative and code

AC for tOe contracting officer. Trans-mit names as last name, first name,

middle inhial.Code DefinltionAC Administrative Contacltin OffierCE Cermiie

PER02 03 Name 0 AN 1/35Free-form name.

Namew[024 AI

BASEUNE AS OF: 21 MAY 1992 10.1.27

DEPARTMENT OF DEFENSE 61 IWVOICE (Ptgrm PmDRAFT INPLEMENTATION CONVENT3ON ASI MI WSIOI.VASE WIO OD.

0PER03 366 CWmmunca Number 0 ID 2/2

Qualer

Code dentifying the type of communication number.Communic-tion Number

Ousier1025 A 1 Code Definimon

NJ MJTOVONEM Aeo mnR MelFT -er Tefeoanwnw Mne Systm (FTS)FX FacskfifT hWnsgew TelephonePS Pedtw &**kTE TeephomTL TelexTM TeleMelTX TWS

PER04 364 Communication Number C AN 7/21Complete communications number includingcountry or area code when applicable.

Communication Number[026A A

0

10.7,23 DASEUNE AS OF: 21 MAY 1992

DEPARTMENT OF DEFENSE 1e0 INVoIcE (POgue Pawm sDRAFT IMPLEMENTATION CONVENTION ANSI A*C X12 VEIO$iJSEA OUIODODO

Segmoet lTD Terms of Salec lerred Termsof Sale

Table: 1


Max Use: 5Loop:

Purpoee: To specify terms of sale.

Conmer A. If the code in ITDO1 is 04, then ITDO9is required and either ITDII or ITD12is required. If the code in ITD01 equals05, then ITDO6 or ITD07 is required.

Syntax Notes: 01 If ITD03 is present, then at least one ofITD04, ITDOS, ITD13 is required.

02 If ITDO8 is present, then at least one ofITD04, ITD05 or ITD13 is required.

03 If ITDO9 is present, then ITDO orTD11 is required.

Data Element SummaryRe. DamaDes. BEmem Name AmtHmn

=TD01 336 Term Type Code 0 ID 2/2Code identifying type of payment terms.

Terms Type Code[027 A *1

Use code 14 for the liquidation rate,BLOCK Ob and code 0 for the

progress payment rate, BLOCK Sa.Code Definitlon08 Basic Diecscut Oflred14 Pre y Agreed UpLn

ITD02 333 Terms Bash Date Code 0 ID 1/2


DEPARTMENT OF DEFENSE 410 INVOICE (P IftymDRAFT IMPLEMENTATION CONVENTION ANSI ASC Xl2 VERSIONI0ELEAGE Is1ODO..

ITDO3 338 TermsDiscount Percent 0 R 1/ITerms discount percentage, expressed as a percent,available to the purchaser if an invoice is paid on obefore the Terms Discount Due Date.

Terms Discount Percent1028 A ]

DIscount Percent. When ITDOI IsGOde 14, Insert the liquidation rate;when code 0S. insert the progress

payment rate.

ITD04 370 Terms Discount Due Oate C DT 6/6

ITDO5 351 Terms Discount Days Due C NO 1/3Number of days in the terms discount period bywhich payment is due if terms discount is earned.

Terms Discount Days Due[029 A )

Discount Days. When ITD03 Isfilled, insert a zero (0) In 1T105 to

satisfy syntax requirement

ITDO6 446 Terms Net Due Date 0 DT 6(6

ITDO7 386 Terms Net Days 0 NO 1/3

ITDOO 362 Terms Discount Amount 0 N2 1/10

ITDO9 388 Terms Deferred Due Date 0 DT 6/6

ITD1O 369 Deferred Amount Due C N2 1/10

ITD11 342 Percent of Invoice Payable C R 1/5

ITD12 352 Description 0 AN 1/80

ITD13 765 Day of Month C NO 1/2

ITD14 107 Payment Method Code 0 ID 1/1

10.7.30 BASEUNE AS OF: 21 MAY lI5M

DEPARTMENT OF DEFENSE 610 INVOICE (Prop'er Pf qDRAFT IMPLEMENTATION CONVENTION ANSI ASC X12 VERSIGNRELEASE 01OOOOD_

Segment: DTM Daterinuw ReferenceTable: I


Max Use: 10Loop:

Purpose: To specify pertinent dates and timesSyntax Notes: 01 Az Ieast one of DTMO2 or DTM03

mug be present.

Data Element SummaryRAf. DafaDeL .ewnt Name M~hoe

DTM01 374 Date/lime Qualifier M ID 3/3Code specifying type of date or t , or both dateand time.

Dat*eTme Qualffler[030 A *1

Use co&. 041 Io reprsent the aeo.thon II date rofeoed to as statementof costs under this cone•ad through

S. e code 152 to represent theCertficatbon dafte foro which therehas been no rnworially adverschange In financial condftlon.

Code Definitlon

041 Status (Pfo and kwkdhi)152 Effecthoe DWt Of Chang

DTM02 373 Date C DT 6/6

Date (YYMMDD).Date

[031 A ]

DTM03 337 Time C TU 4/4

DTM04 623 Tlime Code 0 ID 2/2


DEPARTMENT OF DEFENSE 610 INVOICE (Proven PaymusDRAFT IMPLAEMENTATION CONVENTION ANSI ABC X12 VERSION/RELEASE 002100O00

Segmeut rF1 Baseline Item Data (Invoice)Table: 2

Sequence: 10Useg: 0

Max Use: ILoop:

Purpose: To specify the basic and most frequentlyused line item data for the invoice and re-lated transactions.

Comment: A. Element 235/234 combinations shouldbe interpreted to include productsand/or services. See the Data Diction-ary for a complete list of ID's.

B. IT101 is the purchase order line itemidentification.

C. IT106 through 1T125 provides for ten(10) different product/service ID's foreach item. For example: Case, Color,Drawing No., UPC No., ISBN No.,Model No., SKU.

Syntax Notes: 01 If IT106 is present, then 1T107 is re-quired.

02 If ITI(8 is present, then IT109 is re-quired. 0

03 If ITllO is present, then ITlll is re-

quired.04 If ITl12 is present, then ITl13 is re-

quired.05 If IT114 is present. then ITI75 is re-

quired.06 If IT116 is present, then IT117 is re-


quired.08 If IT120 is present. then IT121 is re-



quired.

Data Element SummaryReF. DatDW& Eeme Nam Att'ibutN

IT101 350 Assigned Identification 0 AN 16

Alphanumeric characters assigned for differentia-

10.7.32 BASEUNE AS OF: 21 MAY 1002

DEPTMENT OF DEFENSE N0 INVOCE (IFope Paymmm

DRAFT IMPLEMEWTATION CONVENTION Am Ac Xi2 VSIO RELESE lo0g

tiOo within a transaction set.Assaigned Ideonticatlon

1032A I <FEQUIRED

The number of ft line of costsbeing rpo"td. BLOCS 1Ot o 26.

ue the number 29 lor outlays 1odate and the number 29 for ew-

timaled next quarter oulays. WoenITIO contins "FMS., the amount in

IT"104 Is Ve FMS total amount

IT102 356 Quontfty Invoiced M R 1/10

Number of units invoiced (supplier units).

Quantty Invoiced[033 A I

Use the number I to satisfy syntaxrsqulremenL

IT103 355 Unit of Measurement Code M ID 2/2

Code identifying the basic unit of measurement.Unit of Measurement Code

[034A *1Use code EA to safy the syntax re-

quirement. Cods,.• Delinlto

EA Eh

IT104 212 Unit Price M R 1/14

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

Unit Price[035 A I

The amount for fte in* or FMStotal cited In rrlol.

ITIOS 630 Basis of Unit Price Code 0 ID 2/2

IT106 235 Product/ServIce ID Qualifier 0 ID 2/2

IT107 234 Product/Service ID C AN 1/30

MIcO 235 Product/ServIce ID Qualifier 0 ID 2/2


DEPARTMENT OF DEFE.NSE 6NSI wVOIC XlZ 1 P11e0

DPA.F -PLE•• -UTATION CONVENI1ON ANSI.SC X12 VEM----

ITmoo 234 ProductServilC ID C AN 1/30

ITIIo 23s ProductdervicS ID QuIMWe 0 ID 212

ITll 234 Produc/SrvWO ID C AN 1/30

ITl12 235 Produot/ervioc ID Qualifier 0 ID 2M2

mT13 234 ProducVSwflCID C AN 1/30

IT 14 235 Product/Servic@ ID Qu*fliler 0 ID 2/2

IT115 234 ProduclSrYic ID C AN 1/30

ITm1m 235 ProduclServIC ID Oualifie 0 ID 2/2

IT117 234 ProductlService ID C AN 1/30

IT118 235 ProductServC ID Qualifier 0 ID 2/2

IT119 234 Product/SMervice ID C AN 1/30

1T120 235 Product/ServIC ID Qualifier 0 ID 2/2


IT122 235 Product/Service ID Qualifier 0 ID 2/2


IT124 235 Product/Service ID Qualifier 0 ID 2/2

IT125 234 Product/Servlc ID C AN 1/30

10.7.34 ASEUNE AS OF: 21 MAY 1902

DEPA•TrENT Of DEFENSE &10 SIVO1C= (Progm PssVs4.DRAFT PIPLEMETAnON CONVENTION ANIN ASC X12 VEMOWNELEME 00M2 oOo.

Segment: SLN Subline Item DetailTable: 2


Max Use: 1Loop:

Purpose: To specify product subline deta item dataComment A. See the Data Dictionary for a complete

list of ID's.B. SLN01 is the identifying number for the

subline item. It is related to (but notnecessarily equivalent to) the baselineitem number. Example: 11 or 1A mightbe used as a subline number to relate tobaseline number L

C. SLN02 is the identifying number for thesubline leveL The subline level isanalogous to the level code used in abill of materials.

D. SLN09 through SLN28 provide for ten(10) different product/service ID's foreach item. For example: Case, Color,Drawing No., UPC No., ISBN No,Model No, SKU.

Syntax Notes: 01 If SLN06 is present, then SLN08 is re-quired.

02 If SLN07 is present, then SLN06 is re-quired.



05 If SLNI3 is present, then SLN14 is re-quired.









DEPARTMENT OF DEFENSE 610 INVOICE QProW'.Pe- 4DRAFT IMPLEMENTATION CONVENTION ANN ASC XII VERMIOHMLEME 111S100

Data Element SummaryRe6. DetsDes, 0ee Nine _

SLNOI 350 Assigned IdentlactIon M AN 1/6Alphanumeric characters assigned for differetia-tion within a transaction set.

Assigned Idenlflatlon(036A I

Rapeat the number or alpha oode inITIOI.

SLN02 350 Asslged ld OMficatlM 0 AN 1/6Alphanumeric characters assigned for differentia.tion within a transaction set.

Assigned Identification1037A ] <

REQUIRED

The number of the line beingreported; 9 through 25 Iess lines 19and 26, or a twoecharacter Country

Code when SLN01 is FMS.

SLN03 661 Configuration Code M ID 1/1Code indicating the relationship of the subline itemto the baseline item.

Configuration Code,038 A *1

Always use code 1.Code DefinitionI hWduded

SLN04 380 Quantity M R 1/10Numeric value of quantity.

QuantiyI039 k I

Use the number I1" to satisfy thesyntax requirement.


DEPARTMENT OF DEFENSE 610 INVOICE (PVmPO PaymsnDRAFT IMPLEMENT'ATION CONVENTION ANSI ADCX112 VERWOON/1LEASE U351 0000.

SLN05 355 Unit of Memauremeet Code M ID 2/2Code identifying the basic unit of measuremeat

Unit of Meesu remfent Code[040 A *1

Use code EA to satisfy fte syntax re-quirenient.

Code DefinitioEA Esh

SLNOS 212 Unit Price C R 1/14Price per unit of product, service, commodity, etc.

Unit Price[041 A 1

The amount of ftlie 1mg cItenSLNO1.

sLNo7 6e* Basis of Unit Price Code 0 ID 2/2

SINGS 662 Subine Pricm Change Code ID C ID 1/1

SLN09 235 Product/Service ID Qualifier 0 ID 212

SLN1O 234 Product/Service ID C AN 1/30

SLN1I 235 Product/ServIce ID Qualifier 0 ID 212

SLN12 234 Product/ServIce ID C AN 1/30

SIN 13 235 Product/Service ID Qualifier 0 ID 2/2

SLN 14 234 Product/Service ID C AN 1/30

SINIS 235 Product/ServlclID Qualifier 0 ID 2/2

SLNiS 234 Producl/Service ID C AN 1/30

SINI? 236 Product/ServIce ID Qualifier 0 ID 2/2

SASEUNE AS OF: 21 MAY I M 10.7.37

DEPARMENT OF DEFENSE 61 PONOICE (Pmusm Pu"mAsDRAFT IUPtEMENTATION CONVENTION ANWASCX12 VESINLAI UHoo-

SI.NIU 234 Produc/Service ID C AN 1/30

SLN19 235 PrOductServlc ID OumilMi 0 10 =/

SLN20 234 Product/Sevice 10 C AN 1130

SLN21 235 ProductSwrvlce ID Quslfflr 0 10 =/

SLN22 234 Product/SevIce ID C AN 1/30

SLN23 235 ProductServ~c ID Qual~fie 0 ID 212

SLN24 234 Product/Servike ID C AN 1/30

SLNd25 235 Product/Servlc ID Qual~fie 0 ID 921

SLN2S 234 Product/Servic 1D C AN 1/30

SLN27 235 Product/Service ID Qualifir 0 ID 2/2

SLN2S 234 ProductServlc ID C AN 1/30

10.7.36 DASEUNE AS OF: 21 MAY 1992

DEPARTMENT OF DEFENSE 8110 INVO0CE (progre nm4DRAFT IMPLEMENTATION CONVENTION ANSI ACXI2 VERSIONXAW O6100000

Segment: TDS Total Monetary Value SummaryTable: 3


Max Use: ILoop:

Purpose: To specify the total invoice discounts andamounts

Comment: A. TDS02 is required if the dollar valuesubject to discount is not equal to thedollar value of TDSOL

Data Element SummaryRef. DataDes. Ehnemm Name A___llo

TDS01 361 Total Invoice Amount U N2 1/10Amount of invoice (including charges, less allowan-ces) before terms discount (if discount is applicable).

Total Invoice Amount1042 A I

The amount of the request forprogress payment BLOCK 26

repeated here.

TDS02 390 Amount Subject to Term C N2 1/10DiscountAmount upon which the terms discount amount iscalculated.

Amount Subject to TermsDiscount1043A I

An entry In TDS02 indicates that theamount requested Is less than themathematical total of the request

for progress payment.

TDS03 391 Discounted Amount Due 0 N2 1/10Amount of invoice due if paid by terms discountdue date (total invoice or installment amount lesscash discount.)

Discounted Amount Due[044A I

The amount allowed by the contract-lng officer. BLOCK 27.

BASEUNE AS OF: 21 MAY 1 M2 10.7.31

DEPARTMENT OF DEU 10 IdVOMC (Pm-WrS fpanUq

DPAFT IMPLEMEATMO CONVENTMO ANU MCXII VENSIWNLEASS WS0000

MDS04 362 Term Dlsoow AffMu 0NU2 1/10TOWl amouat of terms dlisount.

Termse Dbcoount Amount(045 A I

Total amount of the contract.BL=C &.

10.7.40 BASELINE AS OF: 21 MAY 1992

DEPARTMENT OF DEFENSE 1110 INVOICE (Prres Pwymus4DRAFT IMPLEMENTATION CONVENTION ANNI ASC X12 VERS.O EL.AUSE 0OMO0o00

0 Segment CTr Transaction TotalsTable: 3


Max Use: ILoop:

Purpose: To transmit a hash total for a specfic ele-ment in the transaction set

Comnenm A 7i segment is intended to providehash totals to validate transaction oom-pleteness and correctness.

Syntax Notes: 01 If c'rr is present, thenc rO is re-quired.

02 If CTTIO is present, then CTT06 is re-quired.

Data Element SummaryRef. DeatDe Ekmeom Name Athbufte

CTT01 364 Number of Lne Items M NO 1/6Total number of line items in the transaction set.

Number df Line Items[046A I

CTT01 wlg cany the accurmultlonof the number of IT1 sgments con-

tained In the trwason et.

Crr02 347 Hsh Total 0 R 1/10

CTr03 81 Weight 0 R 1/8

C1T04 355 Unit of Measurement Code C ID 2/2

CiT0S 163 Volume 0 R 1/8

CTT06 355 Unit of Masurement Code C ID 2/2

CTT07 352 Description 0 AN i/so

BASEUNE AS OF: 21 MAY IM 10,7AI

DEPARTMENT OF DEFENSE l0 WINVOICE (Ptogr aDRAFT IMPLEMENTATION CONVENTION ANSI ASC X12 VERS14*01ELEE mIODOO...

Segmwt SE Transaction Set TrailerTable: 3

Sequence: soUsage: M

Max Use: ILoop:

Purpose: To indicate the end of the transaction setand provide the count of the transmittedsegments (including the beginning (ST)and ending (SE) segments).

Comment A. SE is the last segment of each transac-tion set.

Data Element SummaryFRe. DataDes. Element Name Awtrxbut

SEOI 96 Number of Included Segments M NO 1/STotal number of segments included in a transactionset including ST and SE segments.

Number of Included Segments[047A I

SE02 329 Transaction Set Control Number U AN 419Identifying control number assigned by theoriginator for a transaction set.Transaction Set Control

Number[048A )

Control No. (same number will befound In ST02 In Header).


DEPARTMENT OF DEFENSE 10 a(P gSn P

DRAFT IMPLEMENTATION CONVENTION ANSI ASC X1I VElION/RiEASE 2m 0000.

* 10.C Example - X12 Transaction Set 810Invoice

This appendix contains an example of Transaction Set 810 as itis used to transmit invoice information to a DoD payment center.

BASEUNE AS OF: JANUARY 29 1993 10.C.1

DEPARTMENT OF DEFENSE 810 INVOICE (r Pm -eyWIMI

DRAFT IPLEMENTAT1ON CONVEMTON ANN AMC X12 vERSIWM/KLEAWEOOIODOOO

{BLANK PAGE)

IO.C.2 BASEUNE AS OF: JANUARY 29 193

DEPARTMENT OF DEFENSE *10 INVOICE (ogs P -V IN

DRAFT IMPLEMENTATION CONVENTION ANSI MC X12 VERIWON/RELEASE @OD10000_

Example - Invoice information from Billing Party to DoD using ANSI X12 810

ST*810*00001 n/i Trnaction act identifer code and tramnction adcontrol number

BIG*920623*12345*920530*DAAZ99-92-C-2468***PA 0I/ Invoke date sad number, cnstract date and mber,and pograms pigment Indicator

REFPPX*13579 n/A previom invois -umber

REF*VR*24680 n/I Vendier's ldeturlctn number

NI*SE**33*23456 n/l Selling par•s CAGE code

Nl*BY**ZZ*65432 n/l Buying party's DFARS appendix G coda

N1*PR**10*33445 n/I DODAAC of paying office

PER*AC*SUE SMITH*ALL*998-8888 n/ AUTOVON telephone number of ACO point of con-tact

PER*CE*JOHN DOE*TE*123-456-7890 n/I Commercial telephone number .1 party certifying

the request for progrem payment

S ITD14*"8O0 RI Liquidation rate

ITD*08"'85*0 n/ Pr pres payment rute

DTM*041*920630 n/W Stalement of costa muder this contract through date

DTM*I<2*910101 n/I Certification date from whic there has been nmaterially adverse chag In financial condtlloi

ITle19*:eEA*16.25 n/I Maximum balance eligible for progras payment

SLN* 19"9I'1"EA010.00 n/i Prad costs eligible

SLN*19"10*I*I*EA*20.00 n/ Incurmd costs eligible

SLN*19*'11i**1EA*30.00 n/I Total costs ellgible

SLN*19*12Al*l*EA*50.00 n/! Total coos ncuumd to date

SLN*19*12B*I*l*EA*200.00 n/I Estumated ,ddiU oal cost to complete

SLN*19*13*I*i*EA*25.50 n/l Total coats eligible times progres payment rule

SLN*19*14A P*I*EA*5.00 n/I Progress payments paid to subcontractors

SLN"19"14B I* 1EA*4.25 -0/i Liquidated progress payments to subcontractors

SASEUNE AS OF: JANUARY 29 1993 1O.C.3

DEPARTMENT OF DEFENSE 310 INVOICE (PrOgrSs PayMss4DRAFT IMPLEMENTATION CONVENTION ANSI MC X12 VEMSIOWIRELEASE Ia OmUOO

SLN*19014COPPE.A.75 n/l Uflquidstod peaora payments to subcontractors

SLN*19*14D*I*EA*0.00 n/1 Subcontract pirogm bIlIIap approvd for uremenpayment

SLN*19*14E*P1IEA*.75 n/I Eligible subcontractor protress payments

SLN*1915P1*1EA*26.25 n/1 Total dollar amuount

SLN*19*16*I*EA*240.00 n/1 Contract pita. tlnes the tiquldam rafte

SLN*1917I1*EAM26.25 n/i Laou of total dollsr amount or contract primcUessrthe lUquUdaton rate

SLN*190 18*1 PEA*10.00 n/l Total &meunt of previous progress payments re-quiested

ITIP26*1*1EAM .00 n/I Amount of current Invokce for progress payment

SLN*26*2OAPPIEA*3O.00 n/I Costs included In total costs eligible for programpayments, applicable to Items delivered, Invoke, andaccepted to date

SLN276*20B*I*EAO0.00 n/I Costa eligibe for prowl"m payments applicable toundelivered Items

SLN*26*20C 0 P1IEA*0.00 n/I Costs eligble for progress payments applicabl toundelivered Items lims the progress payment rate

SLN*26*20D*1*PEA.75 n/I Eligible subcontractor progres payments

SLN*26*20OEPP*EA.75 n/I Limitation

SLN*26*2LMPPIEAM3O.00 n/1 Contract price of Items delivered, stcepled, and In-vokced

SLN*621B*I'P EA*270.00 n/1 Contract price of News not delivered

SLN*26*21C*1*1EA*216.00 n/1 Contract price of Items mot delivered tsmes the III.uldation rate

SLN*26*21DPP*1EA*0.00 n/I Unhlquidated advance payments

SLN*26*21E*1P1EA216.00 n/I Lumtation

SLN*2622PP*1EA.75 n/I Maximuam unliquidatad progress payments

SLN*26*23*1*EA*.75 n/l Total amount applied and to he applied to reduceprogress payments

SLN*26*24*11*EA9.75 il/ Unliquidaed progress payments

SLN*2625*1*1EA*0.00 n/I Maximum permissible progress payment

TDSO0.00*0.00*300.0 n/I Amount or progress payment requested, allowed bythe contracting officer, and total amount of the con-tract

1 O.C.4 BASEUNE AS OF: JANUARY 29 1103

DEPARTMENT OF DEFENSE $10 INVOCE (Proge PalmDRAFT NPLEMENTATION CONVENTION ANSI ASC X12 VERSION/RELE0M 0 00mI OO...CTT*2 Dal Num~er of M mgummiea In Ow buacdm eti

$E*47*0(001 n/I Number of included semena and tramee setcon" ta nmer

NOTE: ALL NUMBERS ARE NOTIONAL AND USED FOR ILLUSTRATION PURPOSES ONLY.

BASLUNE AS OF: JANUARY 29 1993 10.C.S

DEPARTMENT OF DEFENSE 61O INVOICE (Pregmme nDPIAFT WPLEMENTATION CONVENTION ANSI AC X12 VERS eSo oo.

{BLANK PAGE)

10.C.s BASELINE AS OF: JANUARY 29 19ON3

Form Approved

REPORT DOCUMENTATION PAGE opMNo.o 070-0ol8

Pubic reporting burden for this collection of information is estimated to average I hour per response. including the time for reviewing mstructions. searching existing data sources

gathering, and maintaining the data needed. and reviewing the collection of information. Send comments regarding this burdenwt estimate or any other aspect of this collection of

information. including suggestions for reducing this burden, to Washington Headquarters Services. Directorate for nfWormnation Operations and Reports. 1215 Jefferson Davis Highway. SuiteS Z10, Arlingtan. VA 222024302. end to the Office of Information and Regulatory Affairs, Office of Management and Budget, Washington. DC 20503.

1. AGENCY USE ONLY (Leave Blank) 2. REPORT DATE 3. REPORT TYPE AND DATES COVEREDJan 93 Draft

4. TITLE AND SUBTITLE S. FUNDING NUMBERS

DoD Electronic Data Interchange (EDD) Convention: C MDA903-90-C-0006

ASC X12 Transaction Set 810 Invoice (Progress Payment) (Version 003010) PE 0902198D

6. AUTHOR(S)

Stephen LusterRichard ModrowskiWilliam T. James

7. PERFORMING ORGANIZATION NAME(S) AND ADDRESS(ES) 8. PERFORMING ORGANIZATION

Logistics Management Institute REPORT NUMBER

6400 Goldsboro Road LMI-DL203LN4

Bethesda, MD 20817-5886

9. SPONSORING/MONITORING AGENCY NAME(S) AND ADDRESS(ES) 10. SPONSORING/MONITORING

DoD Executive Agent for EC/EDI/PLUS AGENCY REPORT NUMBER

Defense Logistics AgencyDLA-ZIE, Cameron StationAlexandria, VA 22304

11. SUPPLEMENTARY NOTES

Prepared in cooperation with Data Interchange Standards Association, the Secretariat and administrative arm of the Accredited StandardsCommittee X12.

12a. DISTRIBUTION/AVAILABILITY STATEMENT 12b. DISTRIBUTION CODE

A: Approved for public release; distribution unlimited

13. ABSTRACT (Maximum 200 words)

This is an Electronic Data Interchange (EDI) systems design document that describes the standard or "convention" the Department of

Defense (DoD) will use to accept a contractor's request for progress payment using the ASC X12 Transaction Set 810 Invoice (003010).

14. SUBJECT TERMS 15. NUMBER OF PAGES

Electronic Data Interchange; EDI; DoD EDI Convention: Electronic Commerce; ANSI X12; X122; electronic 84

standards; electronic business standards, computer-to-computer exchange of data; electronic documents; 16. PRICE CODEelectronic records: paperless environment; conventions

17. SECURITY CLASSIFICATION 18. SECURITY CLASSIFICATION 19. SECURITY CLASSIFICATION 20. LIMITATION OF ABSTRACTOF REPORT OF THIS PAGE OF ABSTRACTI UL

L nclassified Unclassified Unclassified

NSN 7540-01-280-5500 Standard Form 298, (Rev. 2-89)iremcribed b1 ANSI Sid 2W t629941

convention - defense technical information center · department of defense bi0 ivoic ... di1irr...

Documents