OFFICE OF THE ASSISTANT SECRETARY OF DEFENSE

3500 DEFENSE PENTAGON

WASHINGTON, DC 20301-3500

 SUSTAINMENT

MEMORANDUM FOR FINANCE PROCESS REVIEW COMMITTEE

SUBJECT: Approved Defense Logistics Management Standards Change 1465, G-Invoicing Federal 

Intragovernmental Data Standards (Finance)

The Defense Logistics Management Standards change, as outlined in the attachment, is approved 

for implementation.

Addressees may direct questions to Nolan Davis, e-mail: DEDSO.FINANCE@dla.mil. Others 

must contact their designated Process Review Committee representative available at 

https://www.dla.mil/Defense-Data-Standards/Committees/Contacts/.

 Leigh E. Method, SES

Deputy Assistant Secretary of Defense 

 for Logistics

Attachments:

As stated

cc:

OUSD(C)

DLA J6DS
Attachment, ADC 1465

Page 1

Approved DefenseLogistics Management Standards Change 1465 

G-Invoicing FederalIntragovernmental Data Standards(FIDS)

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION: Eric Flanagan,

Defense Logistics Agency (DLA), Planning and Order Fulfillment Division (J341), 

Eric.Flanagan@dla.mil, Phone (571) 363-9291

2. REASON FOR CHANGE:

a. Bottom Line Up-Front: This proposed change adds G-Invoicing Federal 

Intragovernmental Data Standards (FIDS) elements to DLMS transactions with financial 

implications. This information will allow G-Invoicing trading partners to exchange the data 

needed to generate the 7600EZ Invoice and comply with Treasury financial reporting 

requirements. Substantive changes from PDC 1465 are highlighted in green.

b. Background:

(1) G-Invoicing is the long-term solution for federal program agencies (FPAs) to 

manage their intragovernmental transaction (IGT) Buy/Sell activity. G-Invoicing is not an 

accounting or procurement system; instead, it is a web platform that FPAs use to agree on the 

funding terms and the accounting treatment of their reimbursable activity for consistent financial 

reporting. The U.S. Treasury Bureau of the Fiscal Service requires FPAs to use G-Invoicing 

under the authority of 31 U.S.C. 3512(b) and 3513 (References 10.a and 10.b). FPAs must 

implement G-Invoicing for new orders by October 1, 2022. The G-Invoicing Program Guide 

(Reference 10.c) provides an overview of the overall process.

(2) The Treasury Financial Manual (TFM) Volume 2, Chapter 4700, Appendix 8 

(Reference 10.d) defines the IGT Buy/Sell process as reimbursable activity in which goods or 

services are transferred between two FPAs. The IGT Buy/Sell process begins when a requesting 

agency and servicing agency (i.e., trading partners) use the Fiscal Service (FS) Form 7600A 

General Terms & Conditions (GT&C) (Reference 10.e) to define the terms, conditions, scope, 

and responsibilities that will set the parameters for subsequent orders. The 7600A is in “Open 

for Orders” status after both trading partners approve the GT&C.

(3) The requesting agency submits an FS Form 7600B Order (Reference 10.f) to 

the servicing agency to acquire goods or services after both trading partners approve a GT&C. 

The 7600B is the funding section of the standard interagency agreement (IAA) that specifies the 

terms, quantities, prices, accounting data, and actions of the servicing and requesting agency 

under the overarching GT&C. Together, the 7600A and 7600B comprise the two sections of the 

standard G-Invoicing IAA. The 7600B is in “Open” status after program and funding officials 

from both trading partners approve the order. At this stage the trading partners can exchange 

performance data to record the receipt and acceptance of goods or services ordered or performed. 

The servicing agency cannot provide any goods or services not covered by an open 7600B.

(4) The standard IAA is appropriate for contractual type transactions and is not 

the solution for all intragovernmental buy/sell activity, such as high-volume or low-dollar 

transactions.
Attachment, ADC 1465

Page 2

(5) In response to concerns raised by the General Services Administration (GSA), 

the Fiscal Service established a streamlined process flow called the “7600EZ” to accommodate 

low dollar value/high-volume activity. The 7600EZ process will allow requesting agencies to 

use existing order procedures to requisition goods or services under without a 7600B. Upon 

fulfilling the order, the servicing agency will generate a 7600EZ Invoice.

(6) The Fiscal Service created the FIDS to enhance the exchange of IGT 

Buy/Sell information. These standards aim to capture the crucial information that trading 

partners rely upon for accurate accounting of IGT Buy/Sell events, from initiation to settlement. 

G-Invoicing data standards, FIDS, system interface specifications, and more, are available on the 

G-Invoicing Resources Page (Reference 10.g).

(7) Each G-Invoicing application program interface (API) includes the following 

subset of the FIDS elements:

(a) GT&C

(b) Orders

(c) Performance

(d) Organization

(e) Low Dollar Purchases (7600EZ)

(8) To generate the 7600EZ, the servicing agency must obtain the 7600EZ FIDS 

data from the requesting agency:

(a) FS 7600A GT&C Number

(b) Requesting Agency Component Treasury Account Symbol (TAS)

(c) Requesting Agency Business Event Type Code (BETC)

(d) Requesting Agency Location Code (ALC)

(9) To allow DoD Components and Federal agencies to transition supply 

transactions to G-Invoicing, DLA analyzed DLMS transactions that have financial impacts to 

include the minimum required 7600EZ FIDS elements. Approved DLMS Change (ADC) 1043 

(Reference 10.h), which incorporated the DoD Standard Line of Accounting (SLOA), already 

added the Component TAS, BETC, and ALC. The DoD SLOA is comprised of the Standard 

Financial Information Structure (SFIS) data elements (Reference 10.). However, these DLMS 

notes will need to reference their applicability to G-Invoicing and to use the appropriate FIDS 

terminology. For example, a “Department Regular” code in the SFIS library is the “Agency 

Identifier” in G-Invoicing. Additionally, the change adds a qualifier to allow the Requesting 

Agency to identify the GT&C number and Group Name Description.
Attachment, ADC 1465

Page 3

(10) DoD Components and Federal agencies can utilize these DLMS 

enhancements to enable their ordering applications to send necessary 7600EZ FIDS data to the 

supply source. The supply source will use this data to create the 7600EZ Invoice. DLA plans to 

implement this change to enable its e-commerce ordering applications to capture the 

requisitioner's FIDS data and transmit its enterprise resource planning (ERP) system.

(11) Once implemented, the 7600EZ will replace or supplement the DLMS 810L

Logistics bill for non-Interfund (Intragovernmental Payment and Collection - IPAC) bills in 

accordance with the G-Invoicing mandate. The 7600EZ could potentially replace or supplement

the DLMS 810L for Interfund bills when the DoD is ready for full G-Invoicing implementation.

3. CHANGE IN DETAIL:

a. Technical Details:

(1) Revise DLMS ICs. This change revises the notes in the following DLMS 

implementation conventions (ICs) to reference the G-Invoicing requirement to identify the 

Component TAS and other FIDS data elements, such as the ALC and BETC. This change also 

adds a new qualifier to identify the G-Invoicing GT&C number.

(a) 511R Requisition. The DLMS 511R includes original requisitions, 

referral orders, and passing orders (to include image transactions and other DLMS 511R 

variants).

(b) 511M Requisition Modification. The DLMS 511M derives 

information from the original requisition due to the MILSTRIP requirement to use the 

modification as if the original requisition is not received.

(c) 869F Requisition Follow-Up. The DLMS 869F is a transaction 

generated by a requisitioner when the source of supply indicates that it never received the 

original requisition when responding to an inquiry.

(d) 517M Materiel Obligation Validation (MOV). The DLMS 517M 

transaction derives information from the original requisition due to the MILSTRIP requirement 

to reinstate requisitions cancelled by the source of supply, when requested by the requisitioner.

(e) 180M Materiel Returns Reporting. The DLMS 180M is a transaction 

that reporting activities use to sell back unneeded materiel to the source of supply or 

automatically return reparable items.

(f) 940R Disposal Release Order. The DLMS 940R (with transaction 

type code ‘NE’) is a transaction that DLA uses to initiate disposal release orders for hazardous 

materiel/hazardous waste.

(g) 867I Post-Post Materiel Issue. In this instance, the DLMS 867I 

identifies transactions that occur after the initial posting, specifically noting cases where the 

source of supply had not previously recorded the data.
Attached, ADC 1465

Page 4

(2) Revise Supply Status Code ‘CF’. This change revises Supply Status Code 

‘CF’ to allow the source of supply to reject a transaction if one or more FIDS elements are 

missing or invalid.

(3) Revise DLMS Note for Qualifier AN – Associated Purchase Orders. This 

change revises the subject DLMS Note to support Federal Civilian agencies that use an internal 

reference number, other than the requisition document number, to reconcile obligation data with 

the invoices received from the servicing agency. This field will allow the customer to input their 

agency’s internal reference number. The servicing agency (by agreement) will pass this number 

on subsequent transactions (e.g., materiel release orders) and return it to the customer in the 

supply/shipment status and the 7600EZ.

b. Revised Transaction Flow:

(1) This change does not change existing DLMS transaction flows. However, the 

7600EZ will replace or supplement the DLMS 810L Logistics Bill for IPAC bills, and 

potentially, after analysis, Interfund bills once the Department of Defense is ready to implement 

it. The 7600EZ does not support summary billing, so each invoice contains item and funding 

source information at the detail level, which could allow the 7600EZ to serve as both “bills” and 

“notices” to a customer that its funds have been charged and the “bill” paid.

(2) The 7600EZ Overview (Reference 10.j) provided by the Fiscal Service 

contains high-level transaction flows and business rules.

4. IMPLEMENTATION TARGET: DLA’s actual implementation date is unknown but 

would like to implement this change as of December 2023 or as soon as the PDC becomes 

an approved change.

5. TECHNICAL IMPACT:

a. Additions or Changes to Data Elements:

(1) As shown in the Enclosure, this change adds the following DLMS data 

elements (identified by X12 data element (DE) and code/qualifier).

(a) DE 98: Qualifier BG - Buying Group

(b) DE 128: Qualifier GTC - General Terms and Conditions Identifier

(2) As shown in the Enclosure, this change revises DE 128: Qualifier AN -

Associated Purchase Orders to support Federal Civilian agencies that use an internal reference 

number, other than the requisition document number, to reconcile obligation data with the invoices 

received from the servicing agency.

(3) As shown in the Enclosure, this change revises the DLMS Notes for the 

Coordination Response Requirement: PRC Representatives, include, with your response, an 

estimated timeline and estimated completion date to implement this change for each impacted 

system.
Attached, ADC 1465

Page 5

following data elements. These codes correspond with the DoD Standard SFIS data elements

(Reference 10.i), but this PDC adds new DLMS Notes to reference the FIDS standard and linkage to 

G-Invoicing financial reporting requirements. The Low-Dollar Purchases FIDS (7600EZ) data

dictionary (Reference 10.j) contains the data element definitions and attributes.

ASC X12 Data 

Element Code SFIS Name FIDS Name

DE 1196 A1 Department Indicator Department Regular Component TAS Agency Identifier 

(AID)

DE 1196 A2 Department Transfer Department Transfer Component TAS ATA

(Allocation Transfer Agency Identifier)

DE 1196 A4 Basic Symbol Number Main Account Agency Component TAS Main 

(Main Account Code)

DE 1196 A5 Sub-Level Prefix Sub Class Component TAS SP 

(Sub-Level Prefix Code)

DE 1196 A6 Sub-Account Symbol Sub Account Component TAS SUB 

(Sub-Account Code)

DE 1196 BE Business Event Type 

Code Business Event Type Code Business Event Type Code (BETC)

DE 1196 C3 Budget Restriction Availability Type Component TAS A 

(Availability Type Code)

DE 1196 P1 Disbursing Station 

Number

Agency Dispersing Identifier 

Code

Agency Location Code 

(ALC)

DE 1196 YB Beginning Period of 

Availability

Beginning Period of 

Availability Fiscal Year Date

Component TAS BPOA 

(Beginning Period of Availability)

DE 1196 YE Ending Period of 

Availability

Ending Period of Availability 

Fiscal Year Date

Component TAS EPOA 

(Ending Period of Availability)

b. Automated Information Systems (AIS):

(1) Defense Logistics Agency

(a) Impacted DLA Applications

1. Enterprise Business System

2. Defense Medical Logistics Standard System – Wholesale

3. Federal Mall

c. Defense Automatic Addressing System (DAAS): Update the translation maps for 

the affected DLMS ICs as shown in the Enclosure.
Attached, ADC 1465

Page 6

6. PUBLICATION/POLICY IMPACT:

a. Defense Logistics Manual (DLM) 4000.25: Revise DLM 4000.25, Volume 2, 

AP7.16 Appendix 7.16, Status Codes.

CF Rejected. Failed validation with SFIS Fund Code to Fund Account 

Conversion Table or G-Invoicing Federal Intragovernmental Data 

Standards (FIDS) validation.

(1) Discrete values for the Standard Line of Accounting data elements in the 

transaction do not match data elements from the SFIS Fund Code to Fund 

Account Conversion Table for the Fund Code in the transaction. If still 

required, submit a new requisition with valid data entries.

(2) Invalid/missing fund code

Note: Issues with content of the SFIS Fund Code to Fund Account 

Conversion Table are to be communicated to the Fund Code Monitor of the 

cognizant Component.

(3) One or more G-Invoicing FIDS data elements are missing or invalid.

b. Non-DLM 4000.25 Publications: Participating agencies should update Agency 

publications as needed.

7. ASSUMPTIONS:

a. This change assumes that G-Invoicing trading partners that sign a 7600A GT&C that 

authorizes the 7600EZ will implement the Low Dollar Purchases (7600EZ) API in their 

enterprise resource planning (ERP) system(s).

b. This change also assumes that the requesting agency ERP system will provide the 

7600EZ FIDS elements in all outbound transactions that trigger 7600EZ invoicing, or that their 

personnel will use an e-commerce application offered by the source of supply capable of 

providing the FIDS elements.

8. FINANCIAL IMPROVEMENT AND AUDIT REMEDIATION (FIAR), MATERIAL 

WEAKNESS, AND AUDIT-RELATED INFORMATION:

a. Notices of Findings and Recommendations (NFR): N/A

b. Corrective Action Plan (CAP) References: N/A

c. Other FIAR, Material Weakness, and Audit-Related Information: Since 1997,

the U.S. Government Accountability Office (GAO) has issued a disclaimer of opinion on the 

Financial Report of the U.S. Government. In its report, GAO cited the government's difficulty to 

"adequately account for and reconcile intra-governmental activity and balances between federal 

entities" as a material weakness and a major impediment to expressing an opinion. Refer to 

Government Accountability Office, Actions Needed to Improve Accounting of Intradepartmental 

Transactions (GAO), GAO-21-84 Reference 10.l).

9. END-TO-END TESTING REQUIREMENTS: G-Invoicing trading partners should 

perform end-to-end testing when ready, or on an intra-agency basis as needed.
Attached, ADC 1465

Page 7

10. REFERENCES:

a. Federal Managers Financial Integrity Act of 1982, 31 U.S.C. § 3512(b)

b. Budget and Accounting Procedures Act of 1950, 31 U.S.C. § 3513

c. G-Invoicing Program Guide for Basic Accounting and Reporting

d. Treasury Financial Manual (TFM), Volume 1: Federal Agencies, Part 2 Central 

Accounting and Reporting, Chapter 4700, Appendix 8 – Intra-Governmental Transaction (IGT)

Buy/Sell

e. United States Government General Terms & Conditions (GT&C) FS Form 7600A

f. United States Government Order Form FS 7600B

g. G-Invoicing Resources Website: https://fiscal.treasury.gov/ginvoice/resources.html

h. ADC 1043, DLMS Revisions for Department of Defense (DoD) Standard Line of 

Accounting (SLOA)/Accounting Classification (Finance/Supply)

i. DoD Standard Financial Information Structure (SFIS) Website: 

https://comptroller.defense.gov/odcfo/sfis.aspx

j. Low Dollar Purchases (7600EZ) Overview: https://fiscal.treasury.gov/files/ginvoice/low-dollar-purchases-(7600EZ)-overview.pdf

k. Low Dollar Purchases (7600EZ) FIDS: https://fiscal.treasury.gov/files/ginvoice/7600EZ-federal-intragovernmental-data-standards(current).xlsx

l. Government Accountability Office, Actions Needed to Improve Accounting of 

Intradepartmental Transactions (GAO), GAO-21-84
Attached, ADC 1465

Page 8

11. PROPOSED DLMS CHANGE (PDC) 1465 RESPONSE/COMMENT RESOLUTION:

Component Response/Comment Disposition

1. US Air Force Concur with comments: See responses below. 

US Air Force 

(continued)

Regarding paragraph 2.b.6:

1. The paragraph is unnecessarily complex and risks confusing or 

confounding the reader. The proposed change uses an active voice 

presentation of the information and reduces the reading difficulty

complexity level (as measured by Flesch-Kincaid Grade Level).

Recommendation:

(6) The Fiscal Service created the Federal Intra-governmental Data 

Standards (FIDS) to enhance the exchange of IGT Buy/Sell information. 

These standards aim to capture the crucial information that trading 

partners rely upon for accurate accounting of IGT Buy/Sell events, from 

initiation to settlement. G-Invoicing data standards, FIDS, system 

interface specifications, and more, are available on the G-Invoicing 

Resources Page (Reference 10.g).

Concur.

Regarding paragraph 2.b.10:

2. The paragraph is unnecessarily complex and further complicated by 

punctuation and the use of latin words that focuses the reader's attention 

on its technical and specialized language, acronyms, complicated terms. 

The proposed change improves readability by rephrasing and 

simplifying the paragraph, which results in reducing its Flesch-Kincaid 

Reading Ease measurement by nearly 40% (53.6 before, 33 after).

Recommendation:

(10) DoD Components and Federal agencies can utilize these DLMS 

enhancements to enable their ordering applications to send necessary 

7600EZ FIDS data to the supply source. The supply source will use this 

data to create the 7600EZ Invoice. DLA plans to implement this change 

to enable its e-commerce ordering applications, such as FedMall and 

Medical Electronic Catalog - ECAT, to capture the requisitioner's FIDS 

data and transmit it to the Enterprise Business System (EBS), which is 

DLA's enterprise resource planning (ERP) system.

Concur.

Regarding paragraph 3.a.1.d.:

3. This paragraph uses a word that is nonstandard American English. 

Since this PDC is intended for use by readers of standard American 

English this change will improve readability.

Recommendation:

(d) 517M Materiel Obligation Validation (MOV). The DLMS 517M 

transaction derives information from the original requisition due to the 

MILSTRIP requirement to reinstate requisitions canceled by the source 

of supply, when requested by the requisitioner.

Noted.

Regarding paragraph 3.a.1.g:

4. While technically accurate in every detail, the presentation of the 

information is confusing and technically complex to the point where it 

could baffle readers not intimately familiar with the body DLMS 

standards. The proposed change aims to improve readability and 

understandability of the passage without sacrificing any of the technical 

accuracy of the information presented.

Concur.
Attached, ADC 1465

Page 9

US Air Force 

(continued) Recommendation:

(g) 867I Post-Post Materiel Issue. In this particular instance, the DLMS 

867I identifies transactions that occur after the initial posting, 

specifically noting cases where the source of supply had not previously 

recorded the data.

Regarding paragraph 3.b.1:

5. This part of the revised transaction flow points to "potential, after 

analysis" use case that is very compelling, in my opinion. The issue here 

is that something is missing in the text that could explain to a general 

audience why the potential for replacing Interfund bills (the use case) is 

so interesting. Interfund bills are both “bills” and “notices” to a 

customer that its funds have been charged and the “bill” paid. Since the 

7600EZ is a detailed invoice, it contains the complete record of items 

involved in the transaction, really a combination of order and 

performance data. When considered with the fact that the 7600EZ also 

includes the FS 7600A GT&C Number, there is a connection to the 

billed account in the document. Without this complete set of facts being 

communicated to the reader, the last sentence in the text as written has 

the potential to confuse or mislead the reader.

Recommendation:

(1) This change does not change existing DLMS transaction flows. 

However, the 7600EZ will replace the DLMS 810L Logistics Bill for 

IPAC bills, and potentially, after analysis, Interfund bills once the 

Department of Defense is ready to implement it. The 7600EZ does not 

support summary billing, so each invoice contains item and funding 

source information at the detail level, which could allow the 7600EZ to 

serve as both “bills” and “notices” to a customer that its funds have been 

charged and the “bill” paid.

Concur.

2. Army Concur as written Noted.

3. DAAS Concur as written Noted.

4. DLA Concur with comments: See responses below. 

DLA 

(continued)

DLA 

1. The URL Link for G-Invoicing resolves to Page Not Found. The 

second portion of the link is cutoff.

Corrected the hyperlink.

2. Concur, will need to reach out to J341 Planning and Order

Management if the PDC is approved, to make sure the Sales Order is 

updated to accommodate the new fields inbound on the 511R.

J6 is working on an approved 

capability request submitted by 

J8G to update the sales order and 

DLA ordering applications to 

accommodate the new fields in the 

relevant transactions.

3. Per Sustainment Manager, has implications for FedMall Correct. J6 and J8G will initiate 

meetings with FedMall PMO to 

support this change.

4. The Low Dollar Threshold is limited to $10,000 or less according to 

US Treasury for the 7600EZ, is the presumption that any dollar amount 

over $10,000 will go through the 7600B?

Treasury removed the Low Dollar 

Threshold limit for supply-related 

DLA orders. The Services will 

request similar removal once they 

are ready to implement the 

7600EZ as a Seller.

5. The Requesting Agency will provide the 7600EZ FIDS data 

elements, how will this interface with a Front-End System i.e. EEBP?

J6 and J8G are working with DLA 

Energy and the EEBP program 

manager to modify the relevant 
Attached, ADC 1465

Page 10

(continued)

DLA 

interfaces to allow the customer to 

provide the 7600EZ FIDS data 

elements.

6. We are again advised that no energy products or services can be 

provided to a customer without a signed 7600B. This will have a major 

impact on those customers submitting 7600Bs. Shouldn’t this say that no 

goods or services can be provided without a 7600B or EZ?

That is not DLA guidance. 

However, the 7600EZ would 

require a separate 7600A that 

specifically authorizes the 

7600EZ. In that case, the customer 

would order as normal (i.e., no 

7600B), and DLA use the 7600EZ 

to initiate funds settlement.

7. Why can’t Energy get generally grouped with GSA in some of these 

scenarios? We have the same level of low dollar sales, like GSA.

DLA now has the same 

authorization as GSA to use the 

7600EZ without a dollar 

threshold.

8. So, the question remains, how is GSA collecting the required FIDS 

data elements to enable EZ? Shouldn't DLA's process be consistent with 

GSA to benefit both sets of customers?

GSA is still determining how they 

will capture the required FIDS 

data elements. DLA includes GSA 

in the discussions we have with 

OSD and the Services as we 

determine the best method to 

capture the data.

9. Whose API is this? Is this what G- Inv sends? Is this supposed to be 

in what the servicing agency sends to G-Inv?

Treasury owns the API 

specification. The Servicing 

Agency uses the API to send the 

7600EZ data to the Requesting 

Agency. The Requesting Agency 

uses the same API to respond.

10. Is US Treasury creating the APIs or is this a DLA responsibility to 

collect the data with other means? Will this data create a customer 

profile in EBS?

Treasury created and will maintain

the API. 

11. What data elements are provided within each of these data sets? Section 5.a. of the PDC identifies 

the data elements that will be 

added to each transaction set.

12. This data is very limited. The TAS consists of eight data elements. 

However, there are critical elements missing here and in the remainder 

of the document. Those include the DODAAC or equivalent, PO number 

if appropriate, and many more.

Per the February 27-29 GInvoicing Supply Transactions 

Working Group (STWG), the 

proposed options to address this 

issue include:

1. Develop an SCR for Treasury 

to update G-INV FIDS.

2. OSD to work with Treasury on 

implementation of this SCR.

3. Internal alternate resolutions to 

obtaining data (810L as potential 

alternative).

13. Is this the agency Order Tracking Number (7600B block 1) or PO

number that is often in block 75 of the 7600B?

This would map to the Requesting 

Agency Internal Reference 

Number.

14. This data is the Agency Location Code, Treasury Account Symbol

data (8 elements) and period of performance start and end. Is this the 

ONLY data needed to be collected in advance of transactions to enable 

G-Invoice EZ collections?

No, the buyer must provide the 

GT&C number, ALC, and Bill-To 

DoDAAC.
Attached, ADC 1465

Page 11

(continued) 15. Our customers will need to use an application capable of providing 

the FIDS elements. We certainly do not expect the customer to initiate 

fuel delivery orders through G- Invoicing.

DLA initiated system change 

requests to modify each fuel card 

program. This capability change is 

still in the early phases.

16. We must know which DODAACs are covered by which 7600A/EZ 

to tie the filled requisition to the appropriate billing data.

Noted.

17. This is another situation where we must know the DODAACs 

associated with the buyer's group description.

OSD has advised using the 

DoDAAC + Requesting Agency 

Group Name Description

18. The remainder of the document repeats the need for the ALC, TAS 

and period of performance information in multiple data segments 

depending on the purpose of the data segment. No further comment.

Noted.

19. Isn’t a 7600B or EZ an accounting process though? The 7600EZ is a Treasury 

transaction that initiates or 

reverses funds settlement.

20. Are we talking about an EDI 810 ANSI X12 here? Generated by 

who and sent to who?

The 7600EZ will replace or 

supplement the current EDI 810 

transactions. The seller sends the 

7600EZ, and the buyer can accept 

or reject it.

21.J62H has no comment, however, DPAS is affected by this PDC 

POC: Joseph Stossel (Joseph.stossel@dla.mil) Implementation Date: 12 

to 16 months after approval and ICs are released Publications: no official 

publications, Management Description for SSAE 18 Audit and DPAS 

Training Material and System Documentation

Noted.

5. Marine Corps Concur with comments:

1. Our concurrence is currently limited to those DLMS processes 

which result in non-Interfund bills (i.e., DLMS transactions processed 

via Intragovernmental Payment and Collection (IPAC)). As such, the 

PDC response only speaks to those Marine Corps systems and processes 

that result in DLMS non-Interfund bills. 

- Systems impacted by this change: Marine Corps Food Management 

Information System, Kenneth Barnes, kenneth.barnes2@usmc.mil.

- Estimated timeline and estimated completion date to implement this 

change: Subject to DLA STORES modernization efforts. 

- List of additional publications that will require revision: None 

Noted.

6. Navy Concur with comments: See responses below.

Navy 

(continued)

1. Previously addressed in PDC-1442, a fund code-based solution is 

still needed to provide a path to TFM 4700 Appendix 8 compliance for 

non-DLMS based ordering, where non-DLMS ordering represents the 

bulk of Navy materiel ordering.

Correct. The scope of the PDC 

includes IPAC transactions (nonInterfund). For DoD customers, 

this is a small portion of materiel 

ordering. However, the fund code 

functionality mentioned in PDC 

1442 could be revitalized in a 

separate PDC to legacy and 

offline ordering scenarios. 

The intent of this change is to 

revise applicable DLMS 

transactions to support DLMScompliant systems and processes.

DLA is also initiating system 

change requests to update its nonDLMS ordering applications.
Attached, ADC 1465

Page 12

2. DLA may need to track individual fuel card programs since each fuel 

card program uses different systems which include government off the 

shelf (GOTS) software, commercial off the shelf (COTS) software and 

commercial services. 

DLA initiated system change 

requests to modify each fuel card 

program. This capability change is 

still in the early phases.

3. Navy provides suggestions to maintain item level detail on invoices 

where 7600ez is a header level document and customers will need item 

level detail for manual and programmatic reconciliations.

Per the Feb 27-29 G-Invoicing 

Supply Transactions Working 

Group (STWG), the proposed 

options to address this issue are:

1. Develop an SCR for Treasury 

to update G-INV FIDS.

2. OSD to work with Treasury on 

implementation of this SCR.

3. Internal alternate resolutions to 

obtaining data (810L as potential 

alternative).

4. PDC-1465 should specify how an order that was submitted to a 

specific source of supply with a specific GT&C is updated when the 

source of supply refers the order to another source of supply that may 

require citing a different GT&C. Are there additional integrations or 

logic required given frequency of order referrals or passing orders from 

one source of supply to another? 

Per the February 27-29 GInvoicing Supply Transactions 

Working Group (STWG), the 

proposed options to address this 

issue include: 

1. Policy Working Group: 

Establish a policy working group 

including OUSD(C) and 

OUSD(A&S)* to determine inputs 

required for a potential DoD 

Instruction for the EZ process. 

Determine the ability to utilize 

“interim guidance” while DoDI is 

in development. Guidance should 

include roles/responsibilities, 

business rules (i.e. FOB Source), 

preferred/required GT&C Level 

(agency-level or lower-echelon) 

and policy requirements. 

2. Agreement Working Group: 

Start an agreement working group 

with trading partners to determine 

the scope/content of 7600EZ 

GT&Cs, and “way forward” for 

negotiating agreements between 

trading partners. 

3. Develop realistic timeline to 

resolve policy gaps (when can we 

start writing EZ GT&Cs?)

5. Given PDC-1442 was rescinded, PDC-1465 does not appear to 

address how DLA plans to manage post-post sales like DD-1348 or DD1149 form-based orders, call center, fuel and other point of sale 

transactions which are not submitted via DLMS. Navy recommends a 

fund code-based solution to map existing order data to G-Invoicing 

FIDS.

The fund code functionality in 

PDC 1442 could be revitalized in 

a separate PDC to legacy and 

offline ordering scenarios. The 

intent of this PDC was to revise 

applicable transactions to support 

DLMS-compliant processes. 
Attached, ADC 1465

Page 13

6. PDC-1465 does not address non-DLMS systems. Navy legacy 

MILSTRIP 80-card column systems cannot result in a 7600ez given 

PDC-1442 was rescinded. Navy recommends including fund code-based 

solution to map existing order data to G-Invoicing FIDS.

Per the February 27-29 GInvoicing Supply Transactions 

Working Group (STWG), the 

proposed options to address this 

issue include:

1. Establish DLMS systems 

compliance baseline and timeline 

for non-compliant systems to 

become compliant.

7. DLA DEDSO or OSD, should advocate for MILSBILLS 7600ez as a 

Treasury exception in lieu of MILSBILLS participants individually 

requesting Treasury exceptions which may result in a Navy 7600ez, 

Army 7600ez, Air Force 7600ez, TRANSCOM 7600ez, NOAA 7600ez, 

FAA 7600ez. 

Per the February 27-29 GInvoicing Supply Transactions 

Working Group (STWG)), this 

need is to be addressed as follows:

1. OSD to prepare a request for a 

waiver for all DoD.

2. OSD to coordinate this waiver 

with Treasury for approval

8. If 7600ez FIDS cannot include item level detail then: 

a. DEDSO should consider an 810L could still represent a 

courtesy copy of an invoice in order to provide item detail not 

transmittable on a 7600ez including units, quantity, and unit 

price. 

b. DEDSO should consider mapping item level detail into the 

7600ez comments. 

c. DEDSO should consider providing order history data in an 

attachment or providing order history data in a 7600ez FIDS 

fields. 

Per the February 27-29 GInvoicing Supply Transactions 

Working Group (STWG)), the 

proposed options to address this 

issue include:

1. Develop an SCR for Treasury 

to update G-INV FIDS.

2. OSD to work with Treasury on 

implementation of this SCR.

3. Internal alternate resolutions to 

obtaining data (810L as potential 

alternative).

9. It appears that billing would only include summary level for NSN 

and total cost, for example, JP-5 $14,000.

Per the February 27-29 GInvoicing Supply Transactions 

Working Group (STWG), the 

proposed options to address this 

issue include:

1. Develop an SCR for Treasury 

to update G-INV FIDS.

2. OSD to work with Treasury on 

implementation of this SCR.

3. Internal alternate resolutions to 

obtaining data (810L as potential 

alternative).

10. 7600ez data appears to be insufficient information to conduct threeway matches between what was ordered, what was received and what 

was billed for. For example, a fuel purchase would not include units of 

gallons, gallons purchased, price per gallon. This leaves a gap for 

manual or programmatic efforts to reconcile 7600ez transactions or key 

supporting documents.

Per the February 27-29 GInvoicing Supply Transactions 

Working Group (STWG), the 

proposed options to address this 

issue include:

1. Develop an SCR for Treasury 
Attached, ADC 1465

Page 14

to update G-INV FIDS.

2. OSD to work with Treasury on 

implementation of this SCR.

3. Internal alternate resolutions to 

obtaining data (810L as potential 

alternative).

11. DLA DEDSO should consider requesting that 7600ez FIDS include 

item level detail. 

Per the February 27-29 GInvoicing Supply Transactions 

Working Group (STWG), the 

proposed options to address this 

issue include:

1. Develop an SCR for Treasury 

to update G-INV FIDS.

2. OSD to work with Treasury on 

implementation of this SCR.

3. Internal alternate resolutions to 

obtaining data (810L as potential 

alternative).

12. PDC-1465 does not address how order level detail could be used to 

verify summary level billing details provided by the 7600ez.

Per the February 27-29 GInvoicing Supply Transactions 

Working Group (STWG), the 

proposed options to address this 

issue include:

1. Develop an SCR for Treasury 

to update G-INV FIDS.

2. OSD to work with Treasury on 

implementation of this SCR.

3. Internal alternate resolutions to 

obtaining data (810L as potential 

alternative).
Enclosure, ADC 1465

Page 1

Enclosure, DLMS IC Revisions

# Location DLMS 511R Requisition Reason

1. Introductory 

Notes

Add ADC 1465 to DLMS Introductory Note

- ADC 1465, G-Invoicing Federal Intragovernmental Data Standards

To identify 

changes made to

the IC

2. 2/N901/020 Add New Qualifier and DLMS Notes:

GTC General Terms and Conditions Identifier

DLMS Note:

1. Use to identify the Fiscal Service (FS) Form 7600A General 

Terms and Conditions (GT&C) number in G- Invoicing related 

transactions. Refer to ADC 1465.

2. DLMS enhancement; see introductory DLMS note 3a.

3.At this time a local code GTC is established for use in 511R version 4010. 

A data maintenance action will be submitted to ASC X12 to establish GTC,

General Terms and Conditions Identifier, in a future version.

The DLMS 511R

must reference the 

GT&C number to

allow the source 

of supply to 

generate the

7600EZ Invoice.

3. 2/N901/020 Revise DLMS Note:

AN Associated Purchase Orders 

DLMS Note:

1. Use for cross-reference to the customer’s internal Purchase Order (PO) 

Number (one PO Number per requisition document number) or other 

internal reference number. When submitted, this value will be perpetuated 

to subsequent transactions. Authorized for DLA interface with the 

Exchange, NEXCOM, MCX, and non-DoD customers as required. (See 

ADC 473A and ADC 1465)

2. Use to identify the FEMA Logistics Supply Chain Management System 

(LSCMS) Distribution Order Number. Refer to ADC 1306.

To allow Federal 

Civilian agencies 

to input their 

internal reference 

number when 

using external 

ordering 

applications.

4. 2/N101/180 Add Code and DLMS Note:

BG Buying Group 

DLMS Note:

1. Use to identify the G-Invoicing Group Name Description. Refer ADC 

1465.

2. DLMS enhancement; see introductory DLMS note 3a.

To identify the 

Group 

Description 

Name Field.
Enclosure, ADC 1465

Page 2

# Location DLMS 511R Requisition Reason

5. 2/N102/180 Add DLMS Note:

Name

DLMS Note:

1. Use with N101 code MF to identify the manufacturer's name and address 

(including ZIP code) when the CAGE is not available.

2. Use with N101 code DA to identify the exception ship-to organization. 

Also use 2/N2/190 if additional information is required.

3. Use with N101 Code Z7 to identify the recipient of materiel. Total field 

length is restricted to 24 clear text characters, when not used in 

combination with a DoDAAC or RIC characters. If combined with a Markfor DoDAAC, restrict clear text to 17 characters. If combined with a Markfor RIC, restrict clear text to 20 characters. Authorized DLMS 

enhancement; see introductory DLMS note 3f. Refer to ADC 1009A.

4. Use for Requisition Exception Data Transaction (DLA DIC YRZTransaction Codes ST, MA, NA and MF) with N101 code DA, IAD, IF and 

Z7 to identify the exception address line 1. For Codes DA, IAD and IF a 

maximum of 35 positions (including spaces) is allowed. For code Z7 a 

maximum of 30 positions (including spaces) is allowed. See introductory 

DLMS notes 3e.

5. Use to identify the delivery location (Qualifier DZ, 2/N101/180). Field 

length is 30 positions maximum.

6. Use with N101 Code BG to identify the G-Invoicing Group Name

Description. The format for DoD Components is the DoDAAC followed 

by a hyphen; followed by the DoDAAC description. Refer to ADC 1465.

To identify the 

Group 

Description 

Name.

6. 2/FA2/286 Revise Segment- Level DLMS Note:

DLMS Note:

1. Use this 2/FA2/286 segment to identify the various 

components of the line of accounting.

2. Use thissegment to identify G-Invoicing 7600EZ Federal 

Intragovernmental Data Standards (FIDS) data elements.

3.2. Use this segment to comply with the DoD SLOA/Accounting 

Classification. Cost object elements Project Identifier, Funding Center 

Identifier, Functional Area, Cost Element Code, Cost Center Identifier,

Activity Identifier, and Work Order Number are used as appropriate for 

the system.

The FA2 segment 

will include the 

FIDS data 

elements.

7. 2/FA201/286 Revise DLMS Note:

A1 DepartmentIndicator 

Name

DLMS Note:

1. Use to identify the Requesting Agency Component TAS AID (Agency 

Identifier) in G-Invoicing related transactions. Refer to ADC 1465.

2.1. For DoD SLOA/Accounting Classification use to identify, or to modify, 

“Department Regular”. Refer to ADC 1043.

3.2. Authorized DLMS enhancement;see introductory DLMS note 3f.

To identify the 

Component TAS 

AID in the 

DLMS 511R.
Enclosure, ADC 1465

Page 3

# Location DLMS 511R Requisition Reason

8. 2/FA201/286 Revise DLMS Note:

A2 Department Transfer 

DLMS Note:

1. Use to identify the Requesting Agency Component TAS ATA 

(Allocation Transfer Agency Identifier) in G-Invoicing related 

transactions. Refer to ADC 1465.

2.1. For DoD SLOA/Accounting Classification use to identify, 

or to modify, “Department Transfer”. Refer to ADC 1043.

3.2. Authorized DLMS enhancement;see introductory DLMS note 3f.

To identify the 

Component TAS 

ATA in the 

DLMS 511R.

9. 2/FA201/286 Revise DLMS Note:

A4 Basic Symbol Number 

DLMS Note:

1. Use to identify the Requesting Agency Component TAS Main (Main 

Account Code) in G-Invoicing related transactions. Refer to ADC 1465.

2.1. For DoD SLOA/Accounting Classification use to identify, or to modify,

“Main Account”. Refer to ADC 1043.

3.2. Authorized DLMS enhancement;see introductory DLMS note 3f.

To identify the 

Component TAS 

MAIN in the 

DLMS 511R.

10. 2/FA201/286 Revise DLMS Note:

A5 Sub-Class 

DLMS Note:

1. Use to identify the Requesting Agency Component TAS SP (SubLevel Prefix Code) in G-Invoicing related transactions. Refer to ADC 

1465.

2.1. Reserved for DoD SLOA/Accounting Classification use to identify, 

or to modify, “Sub Class”. Refer to ADC 1043.

3.2. Sub Class is a potential future DLMS enhancement; see introductory

DLMS note 3a.

To identify the 

Component TAS 

SP in the DLMS 

511R.

11. 2/FA201/286 Revise DLMS Note:

A6 Sub-Account Symbol 

DLMS Note:

1. Use to identify the Requesting Agency Component TAS SUB (SubAccount Code) in G-Invoicing related transactions. Refer to ADC 1465.

2.1. For DoD SLOA/Accounting Classification use to identify, or to modify, 

“Sub Account”. Refer to ADC 1043.

3.2. Authorized DLMS enhancement;see introductory DLMS note 3f.

To identify the 

Component TAS 

SUB in the 

DLMS 511R.
Enclosure, ADC 1465

Page 4

# Location DLMS 511R Requisition Reason

12. 2/FA201/286 Revise DLMS Note:

BE Business Event Type Code 

DLMS Note:

1. Use to identify the Business Event Type Code (BETC) in GInvoicing related transactions. Refer to ADC 1465.

2.1. For DoD SLOA/Accounting Classification use to identify, or to 

modify, “Business Event Type Code”. Refer to ADC 1043.

3.2. Authorized DLMS enhancement;see introductory DLMS note 3f.

4.3. Qualifier BE is a migration code approved for use in X12 version 7020.

To add a DLMS 

Note to the 

DLMS 511R.

13. 2/FA201/286 Revise DLMS Note:

C3 Budget Restriction 

DLMS Note:

1. Use to identify the Requesting Agency Component TAS A (Availability 

Type Code) in G-Invoicing related transactions. Refer to ADC 1465.

2.1. For DoD SLOA/Accounting Classification use to identify, or to modify, 

“Availability Type”. Refer to ADC 1043.

3.2. Authorized DLMS enhancement;see introductory DLMS note 3f.

To identify the 

Component TAS 

A in the DLMS 

511R.

14. 2/FA201/286 Revise DLMS Note:

P1 Disbursing Station Number 

DLMS Note:

1. Use to identify the Agency Location Code (ALC) in G- Invoicing related 

transactions. Refer to ADC 1465.

2.1. For DoD SLOA/Accounting Classification use to identify, or to modify, 

“Agency Dispersing Identifier Code”. Refer to ADC 1043.

3.2. Authorized DLMS enhancement;see introductory DLMS note 3f.

To identify the 

ALC in the 

DLMS 511R.

15. 2/FA201/286 Revise DLMS Note:

YB Beginning Period of Availability 

DLMS Note:

1. Use to identify the Requesting Agency Component TAS BPOA 

(Beginning Period of Availability) in G-Invoicing related transactions. 

Refer to ADC 1465.

2.1. For DoD SLOA/Accounting Classification use to identify, or to modify, 

“Beginning Period of Availability Fiscal Year Date”. Refer to ADC 1043.

3.2. Use as appropriate to represent Program Year. Availability Type 

Code must be “X”. Refer to ADC 1043B.

4.3. Authorized DLMS enhancement;see introductory DLMS note 3f.

5.4. Qualifier YB is a migration code approved for use in X12 version 7020.

To identify the 

TAS BPOA in 

the DLMS 511R.
Enclosure, ADC 1465

Page 5

# Location DLMS 511R Requisition Reason

16. 2/FA201/286 Revise DLMS Note:

YE Ending Period of Availability 

DLMS Note:

1. Use to identify the Requesting Agency Component TAS EPOA (Ending 

Period of Availability) in G-Invoicing related transactions. Refer to ADC 

1465.

2.1. For DoD SLOA/Accounting Classification use to identify, or to 

modify, “Ending Period of Availability Fiscal Year Date”. Refer to ADC 

1043.

3.2. Authorized DLMS enhancement;see introductory DLMS note 3f.

4.3. Qualifier YE is a migration code approved for use in X12 version 7020.

To identify the 

TAS EPOA in 

the DLMS 511R.

# Location DLMS 511M Requisition Modification Reason

1. Introductory 

Notes

Add ADC 1465 to DLMS Introductory Note

- ADC 1465, G-Invoicing Federal Intragovernmental Data Standards

To identify

changes made to 

the IC

2. 2/N901/020 Add Qualifier and DLMS Note:

GTC, General Terms and Conditions Identifier

DLMS Note:

1. Use to identify the Fiscal Service (FS) Form 7600A General 

Terms and Conditions (GT&C) number in G- Invoicing related 

transactions. Refer to ADC 1465.

2. DLMS enhancement; see introductory DLMS note 3a.

3.At this time a local code GTC is established for use in 511M version 

4010. A data maintenance action will be submitted to ASC X12 to establish 

GTC, General Terms and Conditions Identifier, in a future version.

The DLMS

511M must 

reference the 

GT&C number to 

allow the source 

of supply to 

generate the

7600EZ Invoice.

3. 2/N901/020 Revise DLMS Note:

AN Associated Purchase Orders 

DLMS Note:

1. Use for cross-reference to the customer’s internal Purchase Order (PO) 

Number (one PO Number per requisition document number) or other 

internal reference number. When submitted, this value will be perpetuated 

to subsequent transactions. Authorized for DLA interface with the

Exchange, NEXCOM, MCX, and non-DoD customers as required. (See 

ADC 473A and ADC 1465.

2.Use to identify the FEMA Logistics Supply Chain Management System 

(LSCMS) Distribution Order Number. Refer to ADC 1306.

To allow Federal 

Civilian agencies 

to input their 

internal reference 

number when 

using external 

ordering 

applications.
Enclosure, ADC 1465

Page 6

# Location DLMS 511M Requisition Modification Reason

4. 2/N101/180 Add Code and DLMS Note:

BG Buying Group 

DLMS Note:

1. Use to identify the G-Invoicing Group Name Description. 

Refer ADC 1465.

2. DLMS enhancement; see introductory DLMS note 3a.

To identify the 

Group 

Description 

Name Field.

5. 2/N102/180 Add DLMS Note:

Name

DLMS Note:

1. Use with 2/N1/180 N101 code MF to identify the manufacturer's name 

when the CAGE code is not available. When the CAGE code is

available use N103 and N104.

2. Use with 2/N1/180 N101 code DA to identify the exception ship-to 

organization.

3. Use with N101 Code Z7 to identify the recipient of materiel. Total field 

length is restricted to 24 clear text characters, when not used in 

combination with a DoDAAC or RIC. If combined with a Mark-for 

DoDAAC, restrict clear text to 17 characters. If combined with a Mark-for 

RIC, restrict clear text to 20 characters. Authorized DLMS enhancement; 

see introductory DLMS note 3g. Refer to ADC 1009A.

4. Use for Requisition Exception Data Transaction (DLA DIC YRZTransaction Codes ST, MA, NA and MF) with N101 code DA, IAD, IF and 

Z7 to identify the exception address line 1. For Codes DA, IAD and IF a 

maximum of 35 positions (including spaces) is allowed. For code Z7 a 

maximum of 30 positions (including spaces) is allowed. See introductory 

DLMS notes 3f.

5. Use to identify the delivery location (Qualifier DZ, 2/N101/180). Field 

length is 30 positions maximum.

6. Use with N101 Code BG to identify the G-Invoicing Group Name

Description. The format for DoD Components is the DoDAAC followed 

by a hyphen; followed by the DoDAAC description. Refer to ADC 1465.

To identify the 

Group 

Description 

Name.

6. 2/FA2/286 Revise Segment- Level DLMS Note:

DLMS Note:

1. Use this 2/FA2/286 segment to identify the various 

components of the line of accounting.

2. Use thissegment to identify G-Invoicing 7600EZ Federal 

Intragovernmental Data Standards (FIDS) data elements.

3.2. Use this segment to comply with the DoD SLOA/Accounting 

Classification. Cost object elements Project Identifier, Funding Center 

Identifier, Functional Area, Cost Element Code, Cost Center Identifier, 

Activity Identifier, and Work Order Number are used as appropriate for

the system.

The FA2 segment 

will include the 

FIDS data 

elements.
Enclosure, ADC 1465

Page 7

# Location DLMS 511M Requisition Modification Reason

7. 2/FA201/286 Revise DLMS Note:

A1 DepartmentIndicator 

Name

DLMS Note:

1. Use to identify the Requesting Agency Component TAS AID (Agency 

Identifier) in G-Invoicing related transactions. Refer to ADC 1465.

2.1. For DoD SLOA/Accounting Classification use to identify, or to modify, 

“Department Regular”. Refer to ADC 1043.

3.2. Authorized DLMS enhancement;see introductory DLMS note 3g.

To identify the 

Component TAS 

AID in the

DLMS 511M.

8. 2/FA201/286 Revise DLMS Note:

A2 Department Transfer 

DLMS Note:

1. Use to identify the Requesting Agency Component TAS ATA 

(Allocation Transfer Agency Identifier) in G-Invoicing related 

transactions. Refer to ADC 1465.

2.1. For DoD SLOA/Accounting Classification use to identify, or to modify, 

“Department Transfer”. Refer to ADC 1043.

3.2. Authorized DLMS enhancement;see introductory DLMS note 3g.

To identify the 

Component TAS 

ATA in the 

DLMS 511M.

9. 2/FA201/286 Revise DLMS Note:

A4 Basic Symbol Number 

DLMS Note:

1. Use to identify the Requesting Agency Component TAS Main (Main 

Account Code) in G-Invoicing related transactions. Refer to ADC 1465.

2.1. For DoD SLOA/Accounting Classification use to identify, or to modify, 

“Main Account”. Refer to ADC 1043.

3.2. Authorized DLMS enhancement;see introductory DLMS note 3g.

To identify the 

Component TAS 

MAIN in the 

DLMS 511M.

10. 2/FA201/286 Revise DLMS Note:

A5 Sub-Class 

DLMS Note:

1. Use to identify the Requesting Agency Component TAS SP (SubLevel Prefix Code) in G-Invoicing related transactions. Refer to ADC 

1465.

2.1. Reserved for DoD SLOA/Accounting Classification use to identify, 

or to modify, “Sub Class”. Refer to ADC 1043.

3.2. Sub Class is a potential future DLMS enhancement; see

introductory DLMS note 3a.

To identify the 

Component TAS 

SP in the DLMS 

511M.
Enclosure, ADC 1465

Page 8

# Location DLMS 511M Requisition Modification Reason

11. 2/FA201/286 Revise DLMS Note:

A6 Sub-Account Symbol 

DLMS Note:

1. Use to identify the Requesting Agency Component TAS SUB (SubAccount Code) in G-Invoicing related transactions. Refer to ADC 1465.

2.1. For DoD SLOA/Accounting Classification use to identify, or to modify, 

“Sub Account”. Refer to ADC 1043.

3.2. Authorized DLMS enhancement;see introductory DLMS note 3g.

To identify the 

Component TAS 

SUB in the 

DLMS 511M.

12. 2/FA201/286 Revise DLMS Note:

BE Business Event Type Code 

DLMS Note:

1. Use to identify the Business Event Type Code (BETC) in GInvoicing related transactions. Refer to ADC 1465.

2.1. For DoD SLOA/Accounting Classification use to identify, or to 

modify, “Business Event Type Code”. Refer to ADC 1043.

3.2. Authorized DLMS enhancement;see introductory DLMS note 3g.

4.3. Qualifier BE is a migration code approved for use in X12 version 7020.

To add a DLMS 

Note to the 

DLMS 511M.

13. 2/FA201/286 Revise DLMS Note:

C3 Budget Restriction 

DLMS Note:

1. Use to identify the Requesting Agency Component TAS A (Availability 

Type Code) in G-Invoicing related transactions. Refer to ADC 1465.

2.1. For DoD SLOA/Accounting Classification use to identify, or to modify, 

“Availability Type”. Refer to ADC 1043.

3.2. Authorized DLMS enhancement;see introductory DLMS note 3g.

To identify the 

Component TAS 

A in the DLMS 

511M.

14. 2/FA201/286 Revise DLMS Note:

P1 Disbursing Station Number 

DLMS Note:

1. Use to identify the Agency Location Code (ALC) in G- Invoicing related 

transactions. Refer to ADC 1465.

2.1. For DoD SLOA/Accounting Classification use to identify, or to modify, 

“Agency Dispersing Identifier Code”. Refer to ADC 1043.

3.2. Authorized DLMS enhancement;see introductory DLMS note 3g.

To identify the 

ALC in the 

DLMS 511M.
Enclosure, ADC 1465

Page 9

# Location DLMS 511M Requisition Modification Reason

15. 2/FA201/286 Revise DLMS Note:

YB Beginning Period of Availability 

DLMS Note:

1. Use to identify the Requesting Agency Component TAS BPOA 

(Beginning Period of Availability) in G-Invoicing related transactions. 

Refer to ADC 1465.

2.1. For DoD SLOA/Accounting Classification use to identify, or to modify, 

“Beginning Period of Availability Fiscal Year Date”. Refer to ADC 1043.

3.2. Use as appropriate to represent Program Year. Availability Type 

Code must be “X”. Refer to ADC 1043B.

4.3. Authorized DLMS enhancement;see introductory DLMS note 3g.

5.4. Qualifier YB is a migration code approved for use in X12 version 7020.

To identify the 

TAS BPOA in

the DLMS 511M.

16. 2/FA201/286 Revise DLMS Note:

YE Ending Period of Availability 

DLMS Note:

1. Use to identify the Requesting Agency Component TAS EPOA (Ending 

Period of Availability) in G-Invoicing related transactions. Refer to ADC 

1465.

2.1. For DoD SLOA/Accounting Classification use to identify, or to 

modify, “Ending Period of Availability Fiscal Year Date”. Refer to ADC 

1043.

3.2. Authorized DLMS enhancement;see introductory DLMS note 3g.

4.3. Qualifier YE is a migration code approved for use in X12 version 7020.

To identify the 

TAS EPOA in

the DLMS 511M.

# Location DLMS 869F Requisition Follow-Up Reason

1. Introductory 

Notes

Add ADC 1465 to DLMS Introductory Note

- ADC 1465, G-Invoicing Federal Intragovernmental Data Standards

To identify 

changes made to

the IC.

2. 2/REF01/105 Add Qualifier and DLMS Note:

GTC General Terms and Conditions Identifier

DLMS Note:

1. Use to identify the Fiscal Service (FS) Form 7600A General 

Terms and Conditions (GT&C) number in G- Invoicing related 

transactions. Refer to PDC1465.

2. DLMS enhancement; see introductory DLMS note 3a.

3. At this time a local code GTC is established for use in 869F version 4010. 

A data maintenance action will be submitted to ASC X12 to establish GTC, 

General Terms and Conditions Identifier, in a future version.

The DLMS

869F must 

reference the 

GT&C number to 

allow the source 

of supply to 

generate the

7600EZ Invoice.
Enclosure, ADC 1465

Page 10

# Location DLMS 869F Requisition Follow-Up Reason

3. 2/REF01/105 Revise DLMS Note:

AN Associated Purchase Orders 

DLMS Note:

1. Use for cross-reference to the customer’s internal Purchase Order (PO)

Number (one PO Number per requisition document number) or other

internal reference number. When submitted, this value will be 

perpetuated to subsequent transactions. Authorized for DLA interface with 

the Exchange, NEXCOM, MCX, and non-DoD customers as required. 

(See ADC 473A and ADC 1465)

2. Use to identify the FEMA Logistics Supply Chain Management System

(LSCMS) Distribution Order Number. Refer to ADC 1306.

To allow Federal 

Civilian agencies 

to input their 

internal reference 

number when 

using external

ordering 

applications.

4. 2/N101/110 Add Code and DLMS Note:

BG Buying Group 

DLMS Note:

1. Use to identify the G-Invoicing Group Name Description. Refer ADC 

1465.

2. DLMS enhancement; see introductory DLMS note 3a.

To identify the 

Group 

Description 

Name Field.

5. 2/N102/110 Add DLMS Note:

Name

DLMS Note:

1. Use with 2/N1/110 N101 code DA to identify the ship-to organization. 

Also use 2/N2/120 if additional information is required.

2. Use in 2/HL/010 transaction loops with N101 code MF to identify the 

manufacturer's name when the CAGE code is not available. When the 

CAGE code is available, use N103 and N104.

3. Use with N101 Code Z7 to identify the recipient of materiel. Total field 

length is restricted to 24 clear text characters, when not used in 

combination with a DoDAAC or RIC. If combined with a Mark-for 

DoDAAC, restrict clear text to 17 characters. If combined with a Mark-for 

RIC, restrict clear text to 20 characters. Authorized DLMS enhancement; 

see introductory DLMS note 4g. Refer to ADC 1009A.

4. Use for Requisition Exception Data Transaction (DLA DIC YRZTransaction Codes ST, MA, NA and MF) with N101 code DA, IAD, IF 

and Z7 to identify the exception address line 1. For Codes DA, IAD and IF 

a maximum of 35 positions (including spaces) is allowed. For code Z7 a 

maximum of 30 positions (including spaces) is allowed. See introductory 

DLMS notes 4f.

5. Use to identify the delivery location (Qualifier DZ, 2/N101/110). Field 

length is 30 positions maximum.

6. Use with N101 Code BG to identify the G-Invoicing Group Name

Description. The format for DoD Components is the DoDAAC followed 

by a hyphen; followed by the DoDAAC description. Refer to ADC 1465.

To identify the 

Group 

Description 

Name.
Enclosure, ADC 1465

Page 11

# Location DLMS 869F Requisition Follow-Up Reason

6. 2/FA2/200 Revise Segment- Level DLMS Note:

DLMS Note:

1. Use thissegment to identify G-Invoicing 7600EZ Federal 

Intragovernmental Data Standards (FIDS) data elements.

2.1. Use this segment to identify the various components of the line of 

accounting.

3.2. Use this segment to comply with the DoD SLOA/Accounting 

Classification. Cost object elements Project Identifier, Funding Center, 

Identifier, Functional Area, Cost Element Code, Cost Center Identifier, 

Activity Identifier, and Work Order Number are used as appropriate for the

system. Refer to ADC 1043.

The FA2 

segment will 

include the FIDS 

data elements.

7. 2/FA201/200 Revise DLMS Note:

A1 DepartmentIndicator Name 

DLMS Note:

1. Use to identify the Requesting Agency Component TAS AID 

(Agency Identifier) in G-Invoicing related transactions. Refer to ADC 

1465.

2.1 For DoD SLOA/Accounting Classification use to identify “Department 

Regular”. Refer to ADC 1043.

3.2. Authorized DLMS enhancement; see introductory DLMS 

note 4g.

To identify the 

Component TAS 

AID in the 

DLMS 869F.

8. 2/FA201/200 Revise DLMS Note:

A2 Department Transfer 

DLMS Note:

1. Use to identify the Requesting Agency Component TAS ATA (Agency 

Allocation Transfer Agency Identifier) in G- Invoicing related 

transactions. Refer to ADC 1465.

2.1. For DoD SLOA/Accounting Classification use to identify 

“Department Transfer”. Refer to ADC 1043.

3.2. Authorized DLMS enhancement;see introductory DLMS note 4g.

To identify the 

Component TAS 

ATA in the 

DLMS 869F.

9. 2/FA201/200 Revise DLMS Note:

A4 Basic Symbol Number 

DLMS Note:

1. Use to identify the Requesting Agency Component TAS Main (Main 

Account Code) in G-Invoicing related transactions. Refer to ADC 1465.

2.1. For DoD SLOA/Accounting Classification use to identify “Main 

Account”. Refer to ADC 1043.

3.2. Authorized DLMS enhancement;see introductory DLMS note 4g.

To identify the 

Component TAS 

MAIN in the 

DLMS 869F.
Enclosure, ADC 1465

Page 12

# Location DLMS 869F Requisition Follow-Up Reason

10. 2/FA201/200 Revise DLMS Note:

A5 Sub-Class 

DLMS Note:

1. Use to identify the Requesting Agency Component TAS SP (SubLevel Prefix Code) in G-Invoicing related transactions. Refer to ADC 

1465.

2.1. Reserved for DoD SLOA/Accounting Classification use to identify 

“Sub Class”. Refer to ADC 1043.

3.2. Sub Class is a potential future DLMS enhancement; see introductory 

DLMS note 4a.

To identify the 

Component TAS 

SP in the DLMS 

869F.

11. 2/FA201/200 Revise DLMS Note:

A6 Sub-Account Symbol 

DLMS Note:

1. Use to identify the Requesting Agency Component TAS SUB (SubAccount Code) in G-Invoicing related transactions. Refer to ADC 1465.

2.1. For DoD SLOA/Accounting Classification use to identify “Sub 

Account”. Refer to ADC 1043.

3.2. Authorized DLMS enhancement;see introductory DLMS note 4g.

To identify the 

Component TAS 

SUB in the 

DLMS 869F.

12. 2/FA201/200 Revise DLMS Note:

BE Business Event Type Code 

DLMS Note:

1. Use to identify the Business Event Type Code (BETC) in GInvoicing related transactions. Refer to ADC 1465.

2.1. Reserved for DoD SLOA/Accounting Classification use to identify 

“Business Event Type Code”. Refer to ADC 1043.

3.2. Business Event Type Code is a potential future DLMS enhancement; 

see introductory DLMS note 4a.

4.3. Qualifier BE is a migration code approved for use in X12 version

7020.

To add a DLMS 

Note to the 

DLMS 869F.

13. 2/FA201/200 Revise DLMS Note:

C3 Budget Restriction 

DLMS Note:

1. Use to identify the Business Event Type Code (BETC) in GInvoicing related transactions. Refer to ADC 1465.

2.1. For DoD SLOA/Accounting Classification use to identify 

“Availability Type”. Refer to ADC 1043.

3.2. Authorized DLMS enhancement;see introductory DLMS note 4g.

To identify the 

Component TAS 

A in the DLMS 

869F.
Enclosure, ADC 1465

Page 13

# Location DLMS 869F Requisition Follow-Up Reason

14. 2/FA201/200 Revise DLMS Note:

P1 Disbursing Station Number 

DLMS Note:

1. Use to identify the Agency Location Code (ALC) in G- Invoicing 

related transactions. Refer to ADC 1465.

2.1. For DoD SLOA/Accounting Classification use to identify “Agency 

Disbursing Identifier Code”. Refer to ADC 1043.

3.2. Authorized DLMS enhancement;see introductory DLMS note 4g.

To identify the 

ALC in the 

DLMS 869F.

15. 2/FA201/200 Revise DLMS Note:

YB Beginning Period of Availability 

DLMS Note:

1. Use to identify the Requesting Agency Component TAS BPOA 

(Beginning Period of Availability) in G-Invoicing related transactions. 

Refer to ADC 1465.

2.1. For DoD SLOA/Accounting Classification use to identify 

“Beginning Period of Availability Fiscal Year Date”. Refer to ADC 1043.

3.2. Use as appropriate to represent Program Year. Availability Type 

Code must be “X”. Refer to ADC 1043B.

4.2. Authorized DLMS enhancement; see introductory DLMS not 4g.

5.3. Qualifier YB is a migration code approved for use in X12 

version 7020.

To identify the 

TAS BPOA in 

the DLMS 869F.

16. 2/FA201/200 Revise DLMS Note:

YE Ending Period of Availability 

DLMS Note:

1. Use to identify the Requesting Agency Component TAS EPOA 

(Ending Period of Availability) in G-Invoicing related transactions. 

Refer to ADC 1465.

2.1. For DoD SLOA/Accounting Classification use to identify “Ending 

Period of Availability Fiscal Year Date”. Refer to ADC 1043.

3.2. Authorized DLMS enhancement;see introductory DLMS note 4g.

4.3. Qualifier YE is a migration code approved for use in X12 version 

7020.

To identify the 

TAS EPOA in 

the DLMS 869F.

# Location DLMS 517M Materiel Obligation Validation Reason

1. Introductory 

Notes

Add ADC 1465 to DLMS Introductory Note

- ADC 1465, G-Invoicing Federal Intragovernmental Data Standards

To identify 

changes made to

the IC.
Enclosure, ADC 1465

Page 14

# Location DLMS 517M Materiel Obligation Validation Reason

2. 1/N101/60 Add Code and DLMS Note:

BG Buying Group 

DLMS Note:

1. Use to identify the G-Invoicing Group Name Description. Refer PDC 

1465.

2. DLMS enhancement; see introductory DLMS note 3a.

To identify the 

Group 

Description 

Name Field.

3. 1/N102/60 Open N102 and Add DLMS Note:

Name

DLMS Note:

Use with N101 Code BG to identify the G-Invoicing Group Name

Description. The format for DoD Components is the DoDAAC followed 

by a hyphen; followed by the DoDAAC description. Refer to ADC 1465.

To identify the 

Group 

Description 

Name.

4. 2/N901/20 Add Qualifier and DLMS Note:

GTC General Terms and Conditions Identifier

DLMS Note:

1. Use to identify the Fiscal Service (FS) Form 7600A General 

Terms and Conditions (GT&C) number in G- Invoicing related 

transactions. Refer to PDC 1465.

2. DLMS enhancement; see introductory DLMS note 3a.

3.At this time a local code GTC is established for use in 517M version 4010. 

A data maintenance action will be submitted to ASC X12 to establish GTC, 

General Terms and Conditions Identifier, in a future version.

The DLMS

517M must 

reference the 

GT&C number to 

allow the source 

of supply to 

generate the

7600EZ Invoice.

5. 2/FA2/136 Revise Segment- Level DLMS Note:

DLMS Note:

1. Use thissegment to identify G-Invoicing 7600EZ Federal 

Intragovernmental Data Standards (FIDS) data elements.

2.1. Must use this segment to identify the various components of the line 

of accounting and numbers associated with a line of accounting.

3.2. Use this segment to comply with the DoD SLOA/Accounting 

Classification. Cost object elements Project Identifier, Funding Center, 

Identifier, Functional Area, Cost Element Code, Cost Center Identifier, 

Activity Identifier, and Work Order Number are used as appropriate for the

system.

The FA2 

segment will 

include the FIDS 

data elements.
Enclosure, ADC 1465

Page 15

# Location DLMS 517M Materiel Obligation Validation Reason

6. 2/FA201/136 Revise DLMS Note:

A1 DepartmentIndicator Name 

DLMS Note:

1. Use to identify the Requesting Agency Component TAS AID (Agency 

Identifier) in G-Invoicing related transactions. Refer to ADC 1465.

2.1. For DoD SLOA/Accounting Classification use to identify 

“Department Regular”. Refer to ADC 1043.

3.2. Authorized DLMS enhancement; see introductory note 3f.

To identify the 

Component TAS 

AID in the 

DLMS 517M.

7. 2/FA201/136 Revise DLMS Note:

A2 Department Transfer 

DLMS Note:

1. Use to identify the Requesting Agency Component TAS ATA 

(Allocation Transfer Agency Identifier) in G-Invoicing related 

transactions. Refer to ADC 1465.

2.1. For DoD SLOA/Accounting Classification use to identify 

“Department Transfer”. Refer to ADC 1043.

3.2. Authorized DLMS enhancement; see introductory note 3f.

To identify the 

Component TAS 

ATA in the 

DLMS 517M.

8. 2/FA201/136 Revise DLMS Note:

A4 Basic Symbol Number 

DLMS Note:

1. Use to identify the Requesting Agency Component TAS Main (Main 

Account Code) in G-Invoicing related transactions. Refer to ADC 1465.

2.1. For DoD SLOA/Accounting Classification use to identify “Main 

Account”. Refer to ADC 1043.

3.2. Authorized DLMS enhancement; see introductory DLMS note 3f.

To identify the 

Component TAS 

MAIN in the 

DLMS 517M.

9. 2/FA201/136 Revise DLMS Note:

A5 Sub-Class 

DLMS Note:

1. Use to identify the Requesting Agency Component TAS SP (SubLevel Prefix Code) in G-Invoicing related transactions. Refer to ADC 

1465.

2.1. Reserved for DoD SLOA/Accounting Classification use to identify 

“Sub Class”. Refer to ADC 1043.

3.2. Sub Class is a potential future DLMS enhancement; see introductory 

DLMS note 3a.

To identify the 

Component TAS 

SP in the DLMS 

517M.

10. 2/FA201/136 Revise DLMS Note:

A6 Sub-Account Symbol 

DLMS Note:

1. Use to identify the Requesting Agency Component TAS SUB (SubAccount Code) in G-Invoicing related transactions. Refer to ADC 1465.

2.1. For DoD SLOA/Accounting Classification use to identify “Sub 

Account”. Refer to ADC 1043.

3.2. Authorized DLMS enhancement; see introductory DLMS note 3f.

To identify the 

Component TAS 

SUB in the 

DLMS 517M.
Enclosure, ADC 1465

Page 16

# Location DLMS 517M Materiel Obligation Validation Reason

11. 2/FA201/136 Revise DLMS Note:

BE Business Event Type Code 

DLMS Note:

1. Use to identify the Business Event Type Code (BETC) in GInvoicing related transactions. Refer to ADC 1465.

2.1. Reserved for DoD SLOA/Accounting Classification use to identify 

“Business Event Type Code”. Refer to ADC 1043.

3.2. Business Event Type Code is a potential future DLMS enhancement; 

see introductory DLMS note 3a.

4.3. Qualifier BE is a migration code approved for use in X12 version

7020.

To add a DLMS 

Note to the 

DLMS 517M.

12. 2/FA201/136 Revise DLMS Note:

C3 Budget Restriction 

DLMS Note:

1. Use to identify the Requesting Agency Component TAS A (Availability 

Type Code) in G-Invoicing related transactions. Refer to ADC 1465.

2.1. For DoD SLOA/Accounting Classification use to identify 

“Availability Type”. Refer to ADC 1043.

3.2. Authorized DLMS enhancement; see introductory DLMS note 3f.

To identify the 

Component TAS 

A in the DLMS 

517M.

13. 2/FA201/136 Revise DLMS Note:

P1 Disbursing Station Number 

DLMS Note:

1. Use to identify the Agency Location Code (ALC) in G- Invoicing 

related transactions. Refer to ADC 1465.

2.1. For DoD SLOA/Accounting Classification use to identify 

“Availability Type”. Refer to ADC 1043.

3.2. Authorized DLMS enhancement; see introductory DLMS note 3f.

To identify the 

ALC in the 

DLMS 517M.

14. 2/FA201/136 Revise DLMS Note:

YB Beginning Period of Availability 

DLMS Note:

1. Use to identify the Requesting Agency Component TAS BPOA 

(Beginning Period of Availability) in G-Invoicing related transactions. 

Refer to ADC 1465.

2.1. For DoD SLOA/Accounting Classification use to identify “Beginning 

Period of Availability Fiscal Year Date”. Refer to ADC 1043.

3.2. Use as appropriate to represent Program Year. Availability Type Code 

must be “X”. Refer to ADC 1043B.

4.3. Authorized DLMS enhancement; see introductory DLMS note 3f.

5.4. Qualifier YB is a migration code approved for use in X12 version 

7020.

To identify the 

TAS BPOA in

the DLMS 

517M.
Enclosure, ADC 1465

Page 17

# Location DLMS 517M Materiel Obligation Validation Reason

15. 2/FA201/136 Revise DLMS Note:

YE Ending Period of Availability 

DLMS Note:

1. Use to identify the Requesting Agency Component TAS EPOA 

(Ending Period of Availability) in G-Invoicing related transactions. 

Refer to ADC 1465.

2.1. For DoD SLOA/Accounting Classification use to identify “Ending 

Period of Availability Fiscal Year Date”. Refer to ADC 1043.

3.2. Authorized DLMS enhancement; see introductory DLMS note 3f.

4.3. Qualifier YE is a migration code approved for use in X12 version 

7020.

To identify the 

TAS EPOA in

the DLMS 

517M.

# Location DLMS 180M Materiel Returns Reporting Reason

1. Introductory 

Notes

Add ADC 1465 to DLMS Introductory Note

- ADC 1465, G-Invoicing Federal Intragovernmental Data Standards

To identify 

changes made to

the IC.

2. 2/N901/11 Add Qualifier and DLMS Note:

GTC General Terms and Conditions Identifier 

DLMS Note:

1. Use to identify the Fiscal Service (FS) Form 7600A General 

Terms and Conditions (GT&C) number in G- Invoicing related 

transactions. Refer to ADC 1465.

2. DLMS enhancement; see introductory DLMS note 3a.

3. At this time a local code GTC is established for use in 180M version 

4010. A data maintenance action will be submitted to ASC X12 to 

establish GTC, General Terms and Conditions Identifier, in a future 

version.

The DLMS

180M must 

reference the 

GT&C number to 

allow the source 

of supply to 

generate the

7600EZ Invoice.

3. 2/N101/60 Add Code and DLMS Note:

BG Buying Group 

DLMS Note:

1. Use to identify the G-Invoicing Group Name Description. Refer ADC 

1465.

2. DLMS enhancement; see introductory DLMS note 3a.

To identify the 

Group 

Description 

Name Field.

4. 2/N102/60 Open N102 and Add DLMS Note:

Name

DLMS Note:

1. Use with N101 Code BG to identify the G-Invoicing Group Name

Description. The format for DoD Components is the DoDAAC followed 

by a hyphen; followed by the DoDAAC description. Refer to ADC 1465.

To identify the 

Group 

Description 

Name.
Enclosure, ADC 1465

Page 18

# Location DLMS 180M Materiel Returns Reporting Reason

5. 2/FA2/226 Revise Segment- Level DLMS Note:

DLMS Note:

1. Use thissegment to identify G-Invoicing 7600EZ Federal 

Intragovernmental Data Standards (FIDS) data elements.

2.1. Must use this segment to identify the various components of the line 

of accounting and numbers associated with a line of accounting.

3.2. Use this segment to comply with the DoD SLOA/Accounting 

Classification. Cost object elements Project Identifier, Funding Center, 

Identifier, Functional Area, Cost Element Code, Cost Center Identifier, 

Activity Identifier, and Work Order Number are used as appropriate for the

system.

The FA2 

segment will 

include the FIDS 

data elements.

6. 2/FA201/226 Revise DLMS Note:

A1 DepartmentIndicator Name 

DLMS Note:

1. Use to identify the Requesting Agency Component TAS AID (Agency 

Identifier) in G-Invoicing related transactions. Refer to ADC 1465.

2.1. For DoD SLOA/Accounting Classification use to identify 

“Department Regular”. Refer to ADC 1043.

3.2. Authorized DLMS enhancement; see introductory DLMS note 2f.

To identify the 

Component TAS 

AID in the 

DLMS 180M.

7. 2/FA201/226 Revise DLMS Note:

A2 Department Transfer 

DLMS Note:

1. Use to identify the Requesting Agency Component TAS ATA 

(Allocation Transfer Agency Identifier) in G-Invoicing related 

transactions. Refer to ADC 1465.

2.1. For DoD SLOA/Accounting Classification use to identify 

“Department Transfer”. Refer to ADC 1043.

3.2. Authorized DLMS enhancement; see introductory DLMS note 2f.

To identify the 

Component TAS 

ATA in the 

DLMS 180M.

8. 2/FA201/226 Revise DLMS Note:

A4 Basic Symbol Number 

DLMS Note:

1. Use to identify the Requesting Agency Component TAS Main (Main 

Account Code) in G-Invoicing related transactions. Refer to ADC 1465.

2.1. For DoD SLOA/Accounting Classification use to identify “Main 

Account”. Refer to ADC 1043.

3.2. Authorized DLMS enhancement; see introductory DLMS note 2f.

To identify the 

Component TAS 

MAIN in the 

DLMS 180M.
Enclosure, ADC 1465

Page 19

# Location DLMS 180M Materiel Returns Reporting Reason

9. 2/FA201/226 Revise DLMS Note:

A5 Sub-Class 

DLMS Note:

1. Use to identify the Requesting Agency Component TAS SP (SubLevel Prefix Code) in G-Invoicing related transactions. Refer to ADC 

1465.

2.1. Reserved for DoD SLOA/Accounting Classification use to identify 

“Sub Class”. Refer to ADC 1043.

3.2. Sub Class is a potential future DLMS enhancement; see introductory 

DLMS note 2a.

To identify the 

Component TAS 

SP in the DLMS 

180M.

10. 2/FA201/226 Revise DLMS Note:

A6 Sub-Account Symbol 

DLMS Note:

1. Use to identify the Requesting Agency Component TAS SUB (SubAccount Code) in G-Invoicing related transactions. Refer to ADC 1465.

2.1. For DoD SLOA/Accounting Classification use to identify “Sub 

Account”. Refer to ADC 1043.

3.2. Authorized DLMS enhancement; see introductory DLMS note 2f.

To identify the 

Component TAS 

SUB in the

DLMS 180M.

11. 2/FA201/226 Revise DLMS Note:

BE Business Event Type Code 

DLMS Note:

1. Use to identify the Business Event Type Code (BETC) in GInvoicing related transactions. Refer to ADC 1465.

2.1. Reserved for DoD SLOA/Accounting Classification use to identify 

“Business Event Type Code”. Refer to ADC 1043.

3.2. Business Event Type Code is a potential future DLMS enhancement; 

see introductory DLMS note 2a.

4.3. Qualifier BE is a migration code approved for use in X12 version

7020.

To add a DLMS 

Note to the 

DLMS 180M.

12. 2/FA201/226 Revise DLMS Note:

C3 Budget Restriction 

DLMS Note:

1. Use to identify the Requesting Agency Component TAS A (Availability 

Type Code) in G-Invoicing related transactions. Refer to ADC 1465.

2.1. For DoD SLOA/Accounting Classification use to identify 

“Availability Type”. Refer to ADC 1043.

3.2. Authorized DLMS enhancement; see introductory DLMS note 2f.

To identify the 

Component TAS 

A in the DLMS 

180M.
Enclosure, ADC 1465

Page 20

# Location DLMS 180M Materiel Returns Reporting Reason

13. 2/FA201/226 Revise DLMS Note:

P1 Disbursing Station Number 

DLMS Note:

1. Use to identify the Agency Location Code (ALC) in G- Invoicing 

related transactions. Refer to ADC 1465.

2.1. For DoD SLOA/Accounting Classification use to identify “Agency 

Dispersing Identifier Code”. Refer to ADC 1043.

3.2. Authorized DLMS enhancement; see introductory DLMS note 2f.

To identify the 

ALC in the 

DLMS 180M.

14. 2/FA201/226 Revise DLMS Note:

YB Beginning Period of Availability 

DLMS Note:

1. Use to identify the Requesting Agency Component TAS BPOA 

(Beginning Period of Availability) in G-Invoicing related transactions. 

Refer to ADC 1465.

2.1. For DoD SLOA/Accounting Classification use to identify “Beginning 

Period of Availability Fiscal Year Date”. Refer to ADC 1043.

3.2. Use as appropriate to represent Program Year. Availability Type Code 

must be “X”. Refer to ADC 1043B.

4.3. Authorized DLMS enhancement; see introductory DLMS note 2f.

5.4. Qualifier YB is a migration code approved for use in X12 version 

7020.

To identify the 

TAS BPOA in

the DLMS 

180M.

15. 2/FA201/226 Revise DLMS Note:

YE Ending Period of Availability 

DLMS Note:

1. Use to identify the Requesting Agency Component TAS EPOA 

(Ending Period of Availability) in G-Invoicing related transactions. 

Refer to ADC 1465.

2.1. For DoD SLOA/Accounting Classification use to identify “Ending 

Period of Availability Fiscal Year Date”. Refer to ADC 1043.

3.2. Authorized DLMS enhancement; see introductory DLMS note 2f.

4.3. Qualifier YE is a migration code approved for use in X12 version 

7020.

To identify the 

TAS EPOA in

the DLMS 

180M.

# Location DLMS 940R Materiel Release Order Reason

1. Introductory 

Notes

Add ADC 1465 to DLMS Introductory Note

- ADC 1465, G-Invoicing Federal Intragovernmental Data Standards

To identify 

changes made to

the IC.
Enclosure, ADC 1465

Page 21

# Location DLMS 940R Materiel Release Order Reason

2. 1/N901/0900 Add Qualifier and DLMS Note:

GTC General Terms and Conditions Identifier

DLMS Note:

1. Use to identify the Fiscal Service (FS) Form 7600A General 

Terms and Conditions (GT&C) number in G- Invoicing related 

transactions. Refer to PDC 1465.

2. DLMS enhancement; see introductory DLMS note 3a.

3.At this time a local code GTC is established for use in 940R version 4030. 

A data maintenance action will be submitted to ASC X12 to establish GTC, 

General Terms and Conditions Identifier, in a future version.

The DLMS 940R

must reference 

the GT&C 

number to allow 

the source of 

supply to 

generate the

7600EZ Invoice.

3. 2/N101/1100 Add Code and DLMS Note:

BG Buying Group 

DLMS Note:

1. Use to identify the G-Invoicing Group Name Description. Refer ADC 

1465.

2. DLMS enhancement; see introductory DLMS note 3a.

To identify the 

Group 

Description 

Name Field.

4. 2/N102/1100 Add DLMS Note:

Name

DLMS Note:

1. Use when transaction includes Component-unique MRO exception data 

with N101 Code DA, IAD, and IF to identify the exception activity name 

(this equates to address line1). See introductory DLMS notes 4a and 4e.

2. Use to identify the delivery location (used with Qualifier MQ above). 

Field length is 30 positions maximum.

3. Use with N101 Code Z7, Mark-for Party, to identify the DLA 

Disposition Services public sales customer by first and last name. Refer to 

ADC 463.

4. Use with N101 Code Z7 to identify the recipient of materiel. Total field 

length is restricted to 24 characters. If combined with a Mark-for 

DoDAAC, restrict clear text to 17 characters. If combined with a Mark-for 

RIC, restrict clear text to 20 characters. Authorized DLMS enhancement;

see introductory DLMS note 4f. Refer to ADC 1009A.

5. Use with N101 Code CA to identify the carrier by name. (Field length 

for DLMS is 60 positions.)

6. Use with N101 Code BG to identify the G-Invoicing Group Name 

Description. The format for DoD Components is the DoDAAC followed

by a hyphen; followed by the DoDAAC description.

To identify the 

Group 

Description 

Name.
Enclosure, ADC 1465

Page 22

# Location DLMS 940R Materiel Release Order Reason

5. 2/FA2/3000 Revise Segment- Level DLMS Note:

DLMS Note:

1. Use thissegment to identify G-Invoicing 7600EZ Federal 

Intragovernmental Data Standards (FIDS) data elements.

2.1. Use this 2/FA2/3000 segment to identify the various components of 

the line of accounting.

3.2. Use this segment to comply with the DoD SLOA/Accounting 

Classification. Cost object elements Project Identifier, Funding Center 

Identifier, Functional Area, Cost Element Code, Cost Center Identifier, 

Activity Identifier, and Work Order Number are used as appropriate for 

the system. This information is applicable to the disposal release order for

hazardous materiel/waste and creditable turn-in only. Refer to ADC 1043.

The FA2 

segment will 

include the FIDS 

data elements.

6. 2/FA201/3000 Revise DLMS Note:

A1 DepartmentIndicator Name 

DLMS Note:

1. Use to identify the Requesting Agency Component TAS AID (Agency 

Identifier) in G-Invoicing related transactions. Refer to ADC 1465.

2.1. For DoD SLOA/Accounting Classification use to identify, or to 

modify, “Department Regular”. Refer to ADC 1043.

3.2. Authorized DLMS enhancement; see introductory DLMS note 4f.

To identify the 

Component TAS 

AID in the 

DLMS 940R.

7. 2/FA201/3000 Revise DLMS Note:

A2 Department Transfer 

DLMS Note:

1. Use to identify the Requesting Agency Component TAS ATA 

(Allocation Transfer Agency Identifier) in G-Invoicing related 

transactions. Refer to ADC 1465.

2.1. For DoD SLOA/Accounting Classification use to identify, or to 

modify, “Department Transfer”. Refer to ADC 1043.

3.2. Authorized DLMS enhancement; see introductory DLMS note 4f.

To identify the 

Component TAS 

ATA in the 

DLMS 940R.

8. 2/FA201/3000 Revise DLMS Note:

A4 Basic Symbol Number 

DLMS Note:

1. Use to identify the Requesting Agency Component TAS Main (Main 

Account Code) in G-Invoicing related transactions. Refer to ADC 1465.

2.1. For DoD SLOA/Accounting Classification use to identify, or to 

modify, “Main Account”. Refer to ADC 1043.

3.2. Authorized DLMS enhancement; see introductory DLMS note 4f.

To identify the 

Component TAS 

MAIN in the 

DLMS 940R.
Enclosure, ADC 1465

Page 23

# Location DLMS 940R Materiel Release Order Reason

9. 2/FA201/3000 Revise DLMS Note:

A5 Sub-Class 

DLMS Note:

1. Use to identify the Requesting Agency Component TAS SP (SubLevel Prefix Code) in G-Invoicing related transactions. Refer to ADC 

1465.

2.1. Reserved for DoD SLOA/Accounting Classification use to identify, or 

to modify, “Sub Class”. Refer to ADC 1043.

3.2. Sub Class is a potential future DLMS enhancement; see introductory 

DLMS note 4a.

To identify the 

Component TAS 

SP in the DLMS

940R.

10. 2/FA201/3000 Revise DLMS Note:

A6 Sub-Account Symbol 

DLMS Note:

1. Use to identify the Requesting Agency Component TAS SUB (SubAccount Code) in G-Invoicing related transactions. Refer to ADC 1465.

2.1. For DoD SLOA/Accounting Classification use to identify, or to 

modify, “Sub Account”. Refer to ADC 1043.

3.2. Authorized DLMS enhancement; see introductory DLMS note 4f.

To identify the 

Component TAS 

SUB in the 

DLMS 940R.

11. 2/FA201/3000 Revise DLMS Note:

BE Business Event Type Code 

DLMS Note:

1. Use to identify the Business Event Type Code (BETC) in GInvoicing related transactions. Refer to ADC 1465.

2.1. Reserved for DoD SLOA/Accounting Classification use to identify, or 

to modify, “Business Event Type Code”. Refer to ADC 1043.

3.2. Business Event Type Code is a potential future DLMS enhancement; 

see introductory DLMS note 4a.

4.3. Qualifier BE is a migration code approved for use in X12 version

7020.

To add a DLMS 

Note to the 

DLMS 940R.

12. 2/FA201/3000 Revise DLMS Note:

C3 Budget Restriction 

DLMS Note:

1. Use to identify the Requesting Agency Component TAS A (Availability 

Type Code) in G-Invoicing related transactions. Refer to ADC 1465.

2.1. For DoD SLOA/Accounting Classification use to identify, or to 

modify, “Availability Type”. Refer to ADC 1043.

3.2. Authorized DLMS enhancement; see introductory DLMS note 4f.

To identify the 

Component TAS 

A in the DLMS 

940R.
Enclosure, ADC 1465

Page 24

# Location DLMS 940R Materiel Release Order Reason

13. 2/FA201/3000 Revise DLMS Note:

P1 Disbursing Station Number 

DLMS Note:

1. Use to identify the Agency Location Code (ALC) in G- Invoicing 

related transactions. Refer to ADC 1465.

2.1. For DoD SLOA/Accounting Classification use to identify, or to 

modify, “Agency Disbursing Identifier Code”. Refer to ADC 1043.

3.2. Authorized DLMS enhancement; see introductory DLMS note 4f.

To identify the 

ALC in the 

DLMS 940R.

14. 2/FA201/3000 Revise DLMS Note:

YB Beginning Period of Availability 

DLMS Note:

1. Use to identify the Requesting Agency Component TAS BPOA 

(Beginning Period of Availability) in G-Invoicing related transactions. 

Refer to ADC 1465.

2.1. For DoD SLOA/Accounting Classification use to identify, or to 

modify, “Beginning Period of Availability Fiscal Year Date”. Refer to 

ADC 1043.

3.2. Use as appropriate to represent Program Year. Availability Type Code 

must be “X”. Refer to ADC 1043B.

4.3. Authorized DLMS enhancement; see introductory DLMS note 4f.

5.4. Qualifier YB is a migration code approved for use in X12 version 

7020.

To identify the 

TAS BPOA in 

the DLMS 940R.

15. 2/FA201/3000 Revise DLMS Note:

YE Ending Period of Availability 

DLMS Note:

1. Use to identify the Requesting Agency Component TAS EPOA 

(Ending Period of Availability) in G-Invoicing related transactions. 

Refer to ADC 1465.

2.1. For DoD SLOA/Accounting Classification use to identify, or to 

modify, “Ending Period of Availability Fiscal Year Date”. Refer to ADC 

1043.

3.2. Authorized DLMS enhancement; see introductory DLMS note 4f.

4.3. Qualifier YE is a migration code approved for use in X12 version 

7020.

To identify the 

TAS EPOA in 

the DLMS 940R.

# Location DLMS 867I Issue Reason

1. Introductory 

Notes

Add ADC 1465 to DLMS Introductory Note

- ADC 1465, G-Invoicing Federal Intragovernmental Data Standards

To identify 

changes made to 

the IC.
Enclosure, ADC 1465

Page 25

# Location DLMS 867I Issue Reason

2. 2/REF01/30 Add Qualifier and DLMS Note:

GTC, General Terms and Conditions Identifier

DLMS Note:

1. Use to identify the Fiscal Service (FS) Form 7600A General 

Terms and Conditions (GT&C) number in G- Invoicing related 

transactions. Refer to PDC 1465.

2. DLMS enhancement; see introductory DLMS note 3a.

3.At this time a local code GTC is established for use in 867I version 4010. 

A data maintenance action will be submitted to ASC X12 to establish GTC, 

General Terms and Conditions Identifier, in a future version.

The DLMS 867I

must reference 

the GT&C 

number to allow 

the source of 

supply to 

generate the

7600EZ Invoice.

3. 2/N101/50 Add Code and DLMS Note:

BG Buying Group 

DLMS Note:

1. Use to identify the G-Invoicing Group Name Description. Refer ADC 

1465.

2. DLMS enhancement; see introductory DLMS note 3a.

To identify the 

Group 

Description 

Name Field.

4. 2/N102/50 Open N102 and Add DLMS Note:

Name

DLMS Note:

1. Use with N101 Code BG to identify the G-Invoicing Group Name

Description. The format for DoD Components is the DoDAAC followed 

by a hyphen; followed by the DoDAAC description. Refer to ADC 1465.

To identify the 

Group 

Description 

Name.

5. 2/FA2/350 Revise Segment- Level DLMS Note:

DLMS Note:

1. Use thissegment to identify G-Invoicing 7600EZ Federal 

Intragovernmental Data Standards (FIDS) data elements.

2.1. Use this 2/FA2/350 segment to identify the various components of the 

line of accounting.

3.2. Use this segment to comply with the DoD SLOA/Accounting 

Classification. Cost object elements Project Identifier, Funding Center, 

Identifier, Functional Area, Cost Element Code, Cost Center Identifier, 

Activity Identifier, and Work Order Number are used as appropriate for

the system. Refer to ADC 1043.

The FA2 

segment will 

include the FIDS 

data elements.

6. 2/FA201/350 Revise DLMS Note:

A1 DepartmentIndicator Name 

DLMS Note:

1. Use to identify the Requesting Agency Component TAS AID (Agency 

Identifier) in G-Invoicing related transactions. Refer to ADC 1465.

2.1. For DoD SLOA/Accounting Classification use to identify 

“Department Regular”. Refer to ADC 1043.

3.2. Authorized DLMS enhancement; see introductory note 5e.

To identify the 

Component TAS 

AID in the 

DLMS 867I.
Enclosure, ADC 1465

Page 26

# Location DLMS 867I Issue Reason

7. 2/FA201/350 Revise DLMS Note:

A2 Department Transfer 

DLMS Note:

1. Use to identify the Requesting Agency Component TAS ATA 

(Allocation Transfer Agency Identifier) in G-Invoicing related 

transactions. Refer to ADC 1465.

2.1. For DoD SLOA/Accounting Classification use to identify 

“Department Transfer”. Refer to ADC 1043.

3.2. Authorized DLMS enhancement; see introductory note 5e.

To identify the 

Component TAS 

ATA in the 

DLMS 867I.

8. 2/FA201/350 Revise DLMS Note:

A4 Basic Symbol Number 

DLMS Note:

1. Use to identify the Requesting Agency Component TAS Main (Main 

Account Code) in G-Invoicing related transactions. Refer to ADC 1465.

2.1. For DoD SLOA/Accounting Classification use to identify “Main 

Account”. Refer to ADC 1043.

3.2. Authorized DLMS enhancement; see introductory DLMS note 5e.

To identify the 

Component TAS 

MAIN in the 

DLMS 867I.

9. 2/FA201/350 Revise DLMS Note:

A5 Sub-Class 

DLMS Note:

1. Use to identify the Requesting Agency Component TAS SP (SubLevel Prefix Code) in G-Invoicing related transactions. Refer to ADC 

1465.

2.1. Reserved for DoD SLOA/Accounting Classification use to identify 

“Sub Class”. Refer to ADC 1043.

3.2. Sub Class is a potential future DLMS enhancement; see introductory 

DLMS note 5a.

To identify the 

Component TAS 

SP in the DLMS 

867I.

10. 2/FA201/350 Revise DLMS Note:

A6 Sub-Account Symbol 

DLMS Note:

1. Use to identify the Requesting Agency Component TAS SUB (SubAccount Code) in G-Invoicing related transactions. Refer to ADC 1465.

2.1. For DoD SLOA/Accounting Classification use to identify “Sub 

Account”. Refer to ADC 1043.

3.2. Authorized DLMS enhancement; see introductory DLMS note 5e.

To identify the 

Component TAS 

SUB in the 

DLMS 867I.
Enclosure, ADC 1465

Page 27

# Location DLMS 867I Issue Reason

11. 2/FA201/350 Revise DLMS Note:

BE Business Event Type Code 

DLMS Note:

1. Use to identify the Business Event Type Code (BETC) in GInvoicing related transactions. Refer to ADC 1465.

2.1. Reserved for DoD SLOA/Accounting Classification use to identify 

“Business Event Type Code”. Refer to ADC 1043.

3.2. Business Event Type Code is a potential future DLMS enhancement; 

see introductory DLMS note 5a.

4.3. Qualifier BE is a migration code approved for use in X12 version 

7020.

To add a DLMS 

Note to the 

DLMS 867I.

12. 2/FA201/350 Revise DLMS Note:

C3 Budget Restriction 

DLMS Note:

1. Use to identify the Requesting Agency Component TAS A (Availability 

Type Code) in G-Invoicing related transactions. Refer to ADC 1465.

2.1. For DoD SLOA/Accounting Classification use to identify 

“Availability Type”. Refer to ADC 1043.

3.2. Authorized DLMS enhancement; see introductory DLMS note 5e.

To identify the 

Component TAS 

A in the DLMS 

867I.

13. 2/FA201/350 Revise DLMS Note:

P1 Disbursing Station Number 

DLMS Note:

1. Use to identify the Agency Location Code (ALC) in G- Invoicing 

related transactions. Refer to ADC 1465.

2.1. For DoD SLOA/Accounting Classification use to identify “Agency 

Disbursing Identifier Code”. Refer to ADC 1043.

3.2. Authorized DLMS enhancement; see introductory DLMS note 5e.

To identify the 

ALC in the 

DLMS 867I.

14. 2/FA201/350 Revise DLMS Note:

YB Beginning Period of Availability 

DLMS Note:

1. Use to identify the Requesting Agency Component TAS BPOA 

(Beginning Period of Availability) in G-Invoicing related transactions.

Refer to ADC 1465.

2.1. For DoD SLOA/Accounting Classification use to identify “Beginning 

Period of Availability Fiscal Year Date”. Refer to ADC 1043.

3.2. Use as appropriate to represent Program Year. Availability Type Code 

must be “X”. Refer to ADC 1043B.

4.3. Authorized DLMS enhancement; see introductory DLMS note 5e.

5.4. Qualifier YB is a migration code approved for use in X12 version 

7020.

To identify the 

TAS BPOA in 

the DLMS 867I.
Enclosure, ADC 1465

Page 28

# Location DLMS 867I Issue Reason

15. 2/FA201/350 Revise DLMS Note:

YE Ending Period of Availability 

DLMS Note:

1. Use to identify the Requesting Agency Component TAS EPOA 

(Ending Period of Availability) in G-Invoicing related transactions. 

Refer to ADC 1465.

2.1. For DoD SLOA/Accounting Classification use to identify “Ending 

Period of Availability Fiscal Year Date”. Refer to ADC 1043.

3.2. Authorized DLMS enhancement; see introductory DLMS note 5e.

4.3. Qualifier YE is a migration code approved for use in X12 version 

7020.

To identify the 

TAS EPOA in 

the DLMS 867I.