Attachment, ADC 435

Page 1

ADC 435

DLMS Revisions for Standard Financial Information Structure (SFIS) 

1. ORIGINATING SERVICE/AGENCY: Business Transformation Agency (BTA) –

Transformation Priorities & Requirements (TP&R FM/SCM); commercial 

703.607.3544.

2. FUNCTIONAL AREA: Joint Supply and Finance

3. REFERENCE:

a. DoD 4000.25-7M (MILSBILLS)

 

b. DoD 4000.25-M, Defense Logistics Management System (DLMS) Volume 5 

(Finance), Chapter 5 - Interfund Billing System Procedures.

c. Approved DLMS Change (ADC) 328, “Off-Line” Requisition Processing: 

Internet Ordering Application Request for Component Verification of Funds 

Availability and Recording of the Financial Obligation 

d. Finance Process Review Committee Meeting 13 - 14 Nov 2007

e. Finance Process Review Committee Meeting 20 May 2008

d. Finance Process Review Committee Meeting 13 Nov 2008

f . Supply Process Review Committee Meeting 28 – 29 October 2009

g . Finance Process Review Committee Meeting 19 Nov 2009

4. REQUESTED CHANGE:

a. This change approves exchanging SFIS accounting data elements using 

referential data and approves modifying specified DLMS transactions to add 

Business Partner Number as an authorized DLMS enhancement. Under the 

current SFIS concept, the requirement to pass the BPN for Non-DoD buyers 

and sellers may have significant impact. This includes Special Program 

DoDAACs identified in ADC 384 and 384A. Staggered implementation is 

authorized.

b. The original proposal described two concepts for exchanging SFIS data: an

approach to carry all SFIS data in DLMS as discrete data elements, and an

alternative approach to use referential data exchange as the primary method for 

acquiring SFIS data elements. Components/Agencies were to provide a 

coordinated response regarding their preferred implementation technique, along 

with the supporting rationale for their preferred solution. Components and 
Attachment, ADC 435

Page 2

Agencies selected referential data, as discussed in paragraph 6.k, for exchange 

of SFIS data elements in the “Target To-Be” environment and selected adding 

Business Partner Number to selected DLMS transactions. This approach is 

adopted for the DoD Logistics Enterprise. Comments Resolution is at enclosure 

(7). Substantive changes from PDC 365 are noted in bold italics.

c. This Approved DLMS Change is intended to provide guidance for “Target” 

Enterprise Resource Planning (ERP) Automated Information Systems (AISs) to 

allow them to transform and modernize with the capability to be both Standard 

Financial Information Structure (SFIS) and DLMS compliant as mandated by 

current DoD policies. The focus for this change is engineered toward the 

modernizing ERP and “Target” AIS that have been identified to migrate toward 

both SFIS and DLMS compliance through the Financial Management Investment 

Review Board Certification (Authority USD Comptroller) and the Weapon 

Systems & Material Supply Management IRB Certification (Authority USD 

AT&L). BTA envisions that the “To-Be” systems of the future will leverage a 

Master Data Capability (MDC) that will enable a DoD Net-Centric Strategy to be 

realized for Financial Master Data, and in the future, enable the DoD to achieve 

clean audits. 

d. Staggered implementation will be required as systems modernize. 

Components/Agencies must ensure that the approved transactions will not fail 

because of the inclusion of Business Partner Number in the transactions.

5. BACKGROUND

a. Standard Financial Information Structure SFIS is a common business 

language that enables budgeting, performance-based management, and the 

generation of financial statements. SFIS is a comprehensive data structure that 

supports requirements for budgeting, financial accounting, cost/performance, and 

external reporting needs across the Department of Defense (DoD) enterprise1

 1

. 

SFIS standardizes financial reporting across the DoD and allows revenues and 

expenses to be reported by programs that align with major goals, rather than 

basing reporting primarily by appropriation categories. It also enables decisionmakers to efficiently compare programs and their associated activities and costs 

across DoD, as well as provides a basis for common valuation of DoD programs, 

assets, and liabilities. Further, SFIS is a replacement for the current version of the 

Line of Accounting used today. The SFIS data elements are to be discrete pieces

of data and neither concatenated nor strung together in a single data field. BTA 

assumes that in the “Target” environment for this change Defense Finance and 

Accounting Service legacy systems will be retired and that Component 

SFIS/DLMS compliant Enterprise Resource Planning (ERPs) will be used for bill 

processing using SFIS data elements. In the Target environment, the SFIS 

http://www.bta.mil/products/sfis.html
Attachment, ADC 435

Page 3

accounting classification data elements will be used by Target systems for 

processing financial transactions. 

b. Intent of the transaction. The purpose of this change is to identify SFIS data 

elements to be included in DLMS logistics business process/data exchange to 

support associated billing. The intent is to identify changes to DLMS now, so that 

DoD Component ERPs and “Target” Automated Information Systems (AISs) can 

program for the business process/data exchange and development of the 

infrastructure required to support financial processes in the future. It is understood

that many current DoD and DoD-trading-partner financial systems are not DLMS 

compliant and have no current plans to migrate. Signal code and fund code (which 

are used in conjunction with the bill-to DoD Activity Address Code (DoDAAC)) 

will continue to be carried in the DLMS transactions. The original proposal 

acknowledged that carrying all SFIS data in DLMS as discrete data elements was 

not supported for orders placed outside of component ERPs, including “Off-Line” 

internet ordering systems such as DoD eMALL, General Services Administration 

(GSA) Advantage and GSA Global, STORES, FFAVORS, current FMS systems, 

some Tailored Vendor Relationship (TVR)/ Prime Vendor (PV) systems or orders 

received via fax, email or telephone and entered manually into catalogue systems 

at DLA Emergency Call Centers. 

c. Procedures, transactions, data elements, processing details in use today: In 

the current environment, the appropriation chargeable for MILSTRIP/DLMS 

Interfund logistics transaction is derived from database tables updated by the 

Components and maintained at DLA Transaction Services (formerly DAASC). 

These tables use the bill-to DODAAC, signal code and fund code, which are 

carried in both MILS and DLMS logistics and financial transactions. These data 

elements will be retained. Using the Service Code, which is the first position of 

the bill-to DoDAAC, Signal Code, and the Fund Code, the Fund Code to 

Appropriation Conversion Table provides the concatenated Department Code (2 

digits), Fiscal Year Chargeable (1 digit), Basic Appropriation (4 digits) and 

Limit/Subhead (4 digits). The fiscal year chargeable may be the last digit of the 

fiscal year or may contain the symbol “#” to denote that the fiscal year chargeable 

is the fiscal year of requisition Julian date, the symbol “*” to denote the fiscal

year of the billing date, or the symbol “X” to denote no-year funding. The Fund 

Code to Billed DoDAAC Conversion Table provides the billed DoDAAC to 

support third party billing when needed. Interfund detail billing records are 

grouped together by sellers according to the buyer’s fund code in the Summary 

Billing Record, and are transmitted together via the DLMS 810L Logistics Bill to 

the seller’s Central Accounts Office (CAO). The Summary Billing Record

contains the concatenated Department Code (2 digits), Fiscal Year Chargeable (1 

digit), Basic Appropriation (4 digits) and Limit/Subhead (4 digits). The format of 

the 810L Logistics Bill will be retained. The seller’s CAO forwards the billing 

information to Treasury for collection on a Statement of Transactions, and 

forwards a copy of the DLMS 810L Logistics Bill to the buyer’s CAO. Note that 

DFAS CAOs are neither DLMS nor SFIS compliant today. ADC 328 (reference 
Attachment, ADC 435

Page 4

c), establishes procedures for an interface between various internet ordering 

applications (such as DoD eMALL, GSA Global, and GSA Advantage) to verify 

funds availability, using the fund code, signal code, and bill-to DoDAAC, before 

allowing a requisition to be processed, and as a separate, subsequent action 

establishes the associated obligation in the applicable Component financial 

system. In the Target environment, SFIS data elements Business Partner Number

(BPN) may be added to this interface. This may be addressed in a separate, future 

DLMS change proposal.

6. APPROVED CHANGE: 

a. Concept. This change will update the DLMS transactions below to carry SFIS 

data elements BPN. Specific DLMS Supplement updates are identified in 

Enclosure 4. The approved approach is to obtain SFIS financial data elements for

all the transactions that trigger a financial action (debit/credit bill) via referential 

data through the SFIS Fund Code to Fund Account Conversion Table, and to 

identify the initiating activity’s BPN (in addition to the DoDAAC) in DLMS. The 

initiating activity may be either a party to receive credit or a party to receive the 

bill, depending upon the business process. Use of a BPN without the 

corresponding DoDAAC is not authorized at this time.

b. Implementation Strategy:

1) Any SFIS data content Business Partner Number passed in DLMS 

transactions is adopted an “authorized DLMS enhancement.” This means that 

an SFIS-compliant application may incorporate the new data content at any 

time subsequent to the Approved Change implementation date without prior 

coordination. Staffing Note: All DLMS trading partners were to ensure 

that the inclusion of the new data elements will not cause currently 

processed transactions to fail pending the receiving application’s 

transition to SFIS.

2) Per reference g, the following information was requested during staffing

i) BTA clarify the relationship (if any) to initiatives by the procurement 

community to employ standard SFIS data. The procurement 

community approach is at OSD Memo Mar 18 2009 - Linking 

Financial Data to Contract Documents http://www.dla.mil/j6/dlmso/Archives/Finance/documents/SFIS/USA002246-09-

DPAP.pdf

ii) OSD Comptroller: 

A. Provide guidance on the uses of the character “*” in the fund code 

table, which identifies the fiscal year of the billing date. Staffing 

Note: This current practice is not clearly defined and may 

impact future development. Status: Guidance still pending. This 
Attachment, ADC 435

Page 5

character is still approved for use in the SFIS Fund Code to 

Fund Account Conversion Table.

B. Provide guidance on the proposed use of ANSI X12 qualifiers for 

SFIS for the FA2 segment that are managed by the Financial 

Management Regulation under code source 529. Status: 

Qualifiers not needed under the approved approach.

c Scope of Transaction Impact. DLA Logistics Management Standards office has 

identified the transactions below as requiring modification to support SFIS. 

Staffing Note: Component financial and logistics experts were to validate 

this list and provide corrections. No corrections were provided.

1) Requisitioning Process: 

i) 511R Requisition. Communicates the BPN of the party to receive the 

bill. and any applicable SFIS elements. 

ii) 511M Requisition Modification. Repeats information from original 

requisition due to MILSTRIP requirement to support capability to use 

modification as original requisition if original requisition is not on file. 

DLA Logistics Management Standards office proposes that all 

additional elements will be modifiable.

iii) 869F Requisition Follow-Up. Communicates buyer BPN and SFIS 

elements. Repeats information from original requisition due to 

MILSTRIP requirement to support capability to use follow-up as 

original requisition if original requisition is not on file.

2) Materiel Obligation Validations:

i) 517M Material Obligation Validation (MOV). Use in requisition 

re-instatement only. Repeats information from original requisition due 

to MILSTRIP requirement to support capability to re-instate a 

requisition cancelled by the supply source during MOV.

3) Materiel Returns Program - Lateral Redistribution under Total Asset 

Visibility Program (TAV) (retail reporting activity sells materiel to ICP so 

that ICP may re-sell this materiel to satisfy a customer’s requirement):

i) 856S Shipment Status. Communicates seller (retail reporting 

activity) BPN. (MILSTRIP AS6 only (shipment status to ICP from 

reporting activity for lateral redistribution order shipments of retail 

assets).

4) Materiel Returns Program – Automatic Returns:
Attachment, ADC 435

Page 6

i) 180M Material Returns Reporting. Communicates the BPN of the 

party to receive credit (returning activity) and any applicable SFIS 

elements with offer of assets (MILSTRIP FTA, Automatic Return 

Notification)

5) Materiel Returns Program – Asset/Excess Return (retail reporting activity 

offers to sell back unneeded materiel to the ICP; depending upon the ICP’s

asset position, the ICP may provide credit):

i) 180M Material Returns Reporting. Communicates the BPN of the 

party to receive credit (returning activity) and any applicable SFIS 

elements with offer of assets (MILSTRIP FTE/FTG (Customer Asset 

Report/Customer Asset Report for part-numbered items)). 

6) Turn-In to DLA Disposition Services Field Office of Hazardous Waste: 

i) 940R Material Release. Communicates the BPN of the party to 

receive the bill for hazardous waste disposal service and any 

applicable SFIS elements (MILSTRIP A5J, Disposal Release Order). 

The 940R may also be used to identify the party to receive credit for 

reimbursable turn-in.

7) Supply Discrepancy Reporting:

i) 842A/W SDR. Communicates the BPN of the party to receive the bill 

or credit and any applicable SFIS elements. This is applicable only to 

DLMS enhancement capability to facilitate proper construct of the 

debit/credit billing where the original requisition document number is 

not known to the submitter. Submitter uses constructed document 

number when reporting discrepancy. Staffing Note: Components

were to evaluate and confirm this as an enhancement to automated 

processing. Comments, where provided, are at enclosure (7).

8) Post-Post Issues: Facilitates DLA’s National Inventory Management

Strategy (NIMS) and Army Medical Materiel Agreement (AMMA) 

Support Scenarios as well as Issues of Materiel relative to 

Emergency/Expedite Off-line Requisition Support Procedures. Under 

NIMS and AMMA support techniques the wholesale activity retains 

ownership of their materiel, which has been pushed-to or pulled-by the retail 

supply activity, until the materiel is requisitioned by the consumer level 

customer, which becomes the point of sale. Consumer level requisitions are 

fulfilled by the retail supply activity using the wholesale activity owned 

inventory and concurrently, the retail activity notifies the wholesale activity of 

the issue/sale of their materiel via the issue transaction. Upon receipt of the 

issue transaction, the wholesale site debits its inventory balance and bills the 

customer. Similarly, emergency requisitions are sometimes filled by storage 
Attachment, ADC 435

Page 7

sites prior to receiving transactional release direction by the materiel owner. 

Subsequently, the materiel owner is notified of the issue/sale via the issue 

transaction.

i) 867I Issue Transaction: Repeats/Communicates the BPN of the party 

to receive the bill and any applicable SFIS elements from the 

consumer level requisition.

9) Billing.

i) 810L Logistics Bill. Communicates the bill issuing activity BPN.

d. BPN will be carried in applicable DLMS transactions. The original proposal also 

identified the data elements below to be carried in DLMS; however, these data 

elements will be available via referential data. The original proposal contained

Period of Availability Fiscal Year Date. Subsequent to staffing “Period of 

Availability Fiscal Year Date was split into two data elements “Beginning 

Period of Availability” and “Ending Period of Availability”. See BEA 8.0 

Standard Financial Information Structure (SFIS), March 2011 (.XLS). 

STAFFING NOTE: Components were to evaluate the proposed data 

elements relative to processing of logistics bills. While some data elements 

were questioned, they were deemed to be needed to support the BTA vision 

of the Target To-Be” environment. See Comment Resolution at enclosure (7). 

Enclosure (1) provides SFIS data element descriptions. SFIS Data elements in 

addition to BPN include:

1) Department Regular Code

2) Department Transfer Code

3) Beginning Period of Availability

4) Ending Period of Availability

5) Main Account Code 

6) Sub-Account Code

7) Treasury Sub Class

Limit/Subhead is also needed in the early phase of SFIS compliance within the 

target systems until phased out. Limit/Subhead will be available via referential 

data. Limit/Subhead is discussed in enclosure (2).

e. The following SFIS data elements are comparable to existing DLMS data 

elements and are discussed at enclosure (3):
Attachment, ADC 435

Page 8

1) Transaction Amount 

2) Transaction Quantity 

3) Unit of Measure Code 

4) Project Identifier (when used for Project Code). Staffing Note: Evaluation of 

this SFIS element determined that a separate Project identifier will not be 

carried in DLMS at this time.

f. The SFIS data elements below will not be included in DLMS transactions. These 

SFIS data elements are discussed in enclosure (4). It is envisioned that the below 

Cost Accounting data elements will be captured by the Buyer’s ERP 

(Component/Agency ERP) and internal to their Logistics and Financial systems.

There is not a requirement at this time for the Buyer to communicate this 

information to the Seller. It is envisioned that the Buyer’s ERP will capture these 

data elements in association with the commitment and obligation:

1) Budget Line Item Identifier

2) Transaction Effective Date

3) Funding Center Identifier

4) Cost Center Identifier

5) Activity Identifier

6) Work Order Number (except as specifically addressed in DLA and industrial 

activity support procedures)

7) Federal/Non-Federal Indicator

8) Trading Partner Indicator Code

9) Agency Accounting Identifier

g. BTA has identified the following additional SFIS data elements to potentially be 

carried in DLMS, which may be covered by a future DLMS change. A concept of 

operations is outlined in enclosure (6). STAFFING NOTE:

Components/Agencies comments on the addition of these data elements, 

including their relevance to the seller in processing the logistics bill are 

included in Comments Resolution at enclosure (7). Potential additional data 

elements include:
Attachment, ADC 435

Page 9

1) One of the following Cost Objects:

i) Budget Line Item Identifier

ii) Cost Center Identifier

iii) Project Identifier

iv) Activity Identifier

v) Work Order #

2) Budget Program Information

i) Budget Line Item Identifier 

ii) Funding Center Identifier

3) Accounting System Routing/Organizational Information

i) Agency Accounting Identifier (AAI) 

h. Other DLMS Transactions With Fund Code. The following transactions 

currently include the Fund Code as perpetuated from the original MILSTRIP 

transaction. However, neither the BTA nor the DLA Logistics Management 

Standards office has identified a need to modify these transactions to carry SFIS 

data (BPN). The fund code will not be removed from these DLMS transactions at 

this time. STAFFING NOTE: Components were to requested to validate this 

list. No current requirements were noted.

1) 517G Government Furnished Material (GFM) Validation

2) 527D Due-in/Advance Receipt/Due Verification

3) 527R Receipt, Inquiry, Response and MRA

4) 812L Logistics Bill Adjustment Request Reply

5) 812R Logistics Bill Adjustment Request 

6) 842A/R Standard Supply Discrepancy Report Reply

7) 856R Shipment Status Material Returns

8) 867D Demand Reporting 

9) 869A Requisition Inquiry/Supply Assistance Request 

10) 869C Requisition Cancellation 
Attachment, ADC 435

Page 10

11) 870S Supply Status

12) 945A Material Release Advice

13) 947I Inventory Adjustment

i. This change removes many unused X12 qualifiers from transactions, for which 

DLA Logistics Management Standards Office has identified no current need. 

STAFFING NOTE; Components were to comment on the qualifiers being 

removed. See Comments resolution at enclosure 7.

j. Financial Traceability Gaps: It is understood that some DoD process, to include 

Tailored Vendor Relationship/Direct Vendor Delivery (TVR/DVD) Programs, 

post-post transactions, and the Government Purchase Card Program will need 

further analysis to fully address any financial traceability gaps. These processes

may be addressed in separate, future DLMS change proposals.

k. Approved Approach - Referential Data. 

1) This approach will use referential data to convey SFIS line of accounting data 

elements to Component applications and others from an authoritative database

based on fund code, signal code and bill-to DoDAAC, which are already carried 

in logistics and financial transactions. The data elements below will be added to 

the fund code table maintained by DLA Transaction Services (formerly DAASC) 

as discrete data elements. This will be in addition to the current concatenated 

fund account field. This new table will be named SFIS Fund Code to Fund 

Account Conversion Table. Component ERPs and others will be able to link to 

the DLA Transaction Services database via synchronized database replication to 

retrieve the data elements in near real time or they may retrieve the file via 

download. This is the same process used for the DoD Address Activity Directory 

(DoDAAD) for DoDAACs. Examples of other referential data elements include 

National Stock Number (NSN), Routing Identification Number (RIC), Military

Assistance Program Address Code MAPAC, Agency Accounting Installation 

(AAI, SFIS data element) Business Partner Number (BPN, SFIS data element).

Since ERPs must contain the fund code, adding the SFIS data elements to the 

fund code database will ensure that the SFIS data elements and the fund code are 

always synchronized for all trading partners. This approach will support

transactions initiated through offline applications, such as call-in center 

emergency operations, and those initiated through internet ordering applications, 

such as call, eMALL, GSA Global, and GSA Advantage, which will continue to 

use the fund code. It will also allow systems that are not DLMS compliant to

retrieve discrete SFIS data elements. In addition, use of the fund code as a 

referential data element ensures that the SFIS data elements are consistent in 

every transaction, eliminating the possibility of error from manual transcription 

for data entered outside of ERPs. Under this approach, the fund code will be 

retained. The BPN will be carried in the DLMS transactions. The data elements 
Attachment, ADC 435

Page 11

that will not be carried, but would be obtained from the SFIS Fund Code to Fund 

Account Conversion Table include: 

i. Department Regular Code

ii. Department Transfer Code

iii. Main Account Code 

iv. Sub-Account Code

v. Treasury Sub Class

vi. Limit/Subhead

vii. Beginning Period of Availability

viii. Ending Period of Availability

ix. Period of Availability (Staffing Note. Components were to

comment on the availability of sufficient fund codes to 

accommodate this. A separate fund code will be needed for 

each multi-year appropriation and fund codes may not be 

reused for five years following the end of the period of 

availability for obligation. There are 1296 possible fund codes 

per Service designator/Service designator group. Components 

confirmed availability of sufficient fund codes. Components 

were to comment on whether the symbol “#” and described in 

paragraph 5c above will be needed to determine the SFIS 

beginning and ending date period of availability for single year 

appropriations. Components were to comment on the use of 

the symbol “*” and whether that symbol needs to be retained

or whether it may be eliminated. As a result of PDC staffing, 

the symbols “#” and “*” will be retained for use in determining 

the Beginning and Ending Periods of Availability. 

2) Note that BTA endorsed the approach of carrying all data elements as 

discrete data elements in DLMS. BTA responsibility has transition to Deputy 

Chief Management Officer, who reviewed this Approved Change. Should a 

need arise in the future to carry all discrete SFIS data elements in DLMS, a 

separate change proposal will be staffed. The SFIS Governance Board was 

briefed on PDC 365 on December 2, 2010 and no objections to the referential 

data approach were noted. See briefing at paragraph 9.q. 

 

l. Revise DoD 4000.25-M, Defense Logistics Management System (DLMS) 

Volume 5 (Finance), Chapter 5 - Interfund Billing System Procedures as follows:

C5.8. STANDARD FINANICIAL INFORMATION STRUCTURE

C5.8.1. SFIS is a common business language that enables budgeting, 

performance-based management, and the generation of financial statements. DLMS/SFIS 

compliant systems will carry the Business Partner Number in DLMS and will obtain 

other prescribed SFIS data elements via referential data though the authoritative DLA 

Transaction Services SFIS Fund Code Conversion Table. Refer to Approved DLMS 

Change 435.
Attachment, ADC 435

Page 12

7. REASON FOR CHANGE: To allow SFIS/DLMS compliant systems to exchange 

discrete SFIS data elements in support of the following: 

a. The Business Enterprise Architecture (BEA)

b. 

http://www.bta.mil/products/bea/html_files/home.html

The DoD Financial Management Regulation (FMR) Volume One, Chapter Four

c. 

http://www.defenselink.mil/comptroller/fmr/01/01_04.pdf

National Defense Authorization Act (NDAA) For Fiscal Year 2009

d. 

http://frwebgate.access.gpo.gov/cgibin/getdoc.cgi?dbname=110_cong_bills&docid=f:h5658rh.txt.pdf

Office of Management and Budget (OMB) Circular A-127

e. 

 

http://www.whitehouse.gov/omb/circulars/a127/a127.html

The CFO Act of 1990

f. 

http://www.dol.gov/ocfo/media/regs/CFOA.pdf

Federal Financial Management Improvement Act (FFMIA) of 1996

g. 

http://www.dol.gov/ocfo/media/regs/FFMIA.pdf

Government Performance and Results Act (GPRA) of 1993

h. 

http://www.whitehouse.gov/omb/mgmt-gpra/gplaw2m.html

OMB, Office of Federal Financial Management (OFFM)

http://www.whitehouse.gov/omb/financial/index.html

i. DOD 4000.25-7-M

j. 

http://www.dtic.mil/whs/directives/corres/pdf/40002507m.pdf

DoD 4000.25-1-M

k. 

http://www.dla.mil/j-6/dlmso/eLibrary/manuals/MILSTRIP/Default.asp

DOD 4000.25-M

http://www.dla.mil/j-6/dlmso/elibrary/Manuals/DLMS/default.asp

8. ADVANTAGES AND DISADVANTAGES:

a. Advantages (tangible/intangible): 

1) This change will allow systems to obtain discrete SFIS data elements via 

referential data regardless of whether or not they are DLMS capable. It will 

support the “Target To-Be” environment.

2) This change enables the DoD to accomplish Strategic goals as outlined by the 

OSD Comptroller office, in the Strategic Management Plan (SMP). The Strategic 

outcome is to demonstrate good stewardship of public funds, thereby increasing 

the audit readiness of individual DoD Components. The measures include 

implementing effective logistics and financial systems that are aligned to the DoD 

Financial Improvement and Audit Readiness (FIAR) strategy.

b. Disadvantages
Attachment, ADC 435

Page 13

1) The following disadvantages were identified applicable to passing discrete 

SFIS data in each of the applicable DLMS transactions. They are obviated 

by the adoption of the referential data approach:

i. DoD buyers will have to know all SFIS information and to 

accurately provide that information to sellers for logistics 

transaction initiated outside of Component ERPs. This will impact 

transactions initiated through offline applications, such as call-in 

center emergency operations, and those initiated through internet 

ordering applications, such as call, eMALL, GSA Global, and 

GSA Advantage. This may increase the opportunity for error, for 

rejected transactions, and for unmatched financial transactions. 

This may adversely impact financial eliminations. 

ii. In the “Target” environment for this change, it is assumed that 

Defense Finance and Accounting Service legacy systems will be 

retired and ERPs will be used for bill processing using SFIS data 

elements. This will require a transformation of the Interfund 

process to include ultimately changing the Summary and Detail 

bills, which rely on fund code association for linkage. These 

changes are beyond the scope of this proposed change.

iii. There is a cost to reconfiguring systems.

iv. The fund code cannot be retired until all DoD trading partners 

using are DLMS compliant in the “Target To-Be” environment. 

This will result in a dual system in the extended interim 

environment.

2) The following disadvantages are applicable to the referential data approach 

that has been adopted.

i. The scope of this change and number of impacted systems makes 

coordinated universal implementation impractical. 

ii. Only 1296 fund codes are available per Service 

Designator/Signal Code combination, so Components/Agencies 

must purge fund codes as they are no longer needed to 

accommodate that limitation.

iii. There is a cost to reconfiguring systems, but these costs are lower 

under the referential data approach.
Attachment, ADC 435

Page 14

9. APPLICABLE REGULATIONS OR GUIDANCE: 

a. The Business Enterprise Architecture (BEA)

http://www.bta.mil/products/bea/html_files/home.html

b. The DoD Financial Management Regulation (FMR) Volume One, Chapter Four

http://www.defenselink.mil/comptroller/fmr/01/01_04.pdf

c. The DoD Financial Management Regulation (FMR) Volume Eleven B, Chapter 

11, “Reimbursements and Revenue Recognition”

http://www.defenselink.mil/comptroller/fmr/11b/11b_11.pdf

d. National Defense Authorization Act (NDAA) For Fiscal Year 2009

http://frwebgate.access.gpo.gov/cgibin/getdoc.cgi?dbname=110_cong_bills&docid=f:h5658rh.txt.pdf

e. National Defense Authorization Act (NDAA) For Fiscal Year 2010 for Business 

Process Reengineering

http://frwebgate.access.gpo.gov/cgibin/getdoc.cgi?dbname=111_cong_bills&doci

d=f:h2647enr.txt.pdf

f. Office of Management and Budget (OMB) Circular A-127

http://www.whitehouse.gov/omb/circulars/a127/a127.html

g. The CFO Act of 1990

http://www.dol.gov/ocfo/media/regs/CFOA.pdf

h. Federal Financial Management Improvement Act (FFMIA) of 1996

http://www.dol.gov/ocfo/media/regs/FFMIA.pdf

i. Government Performance and Results Act (GPRA) of 1993

http://www.whitehouse.gov/omb/mgmt-gpra/gplaw2m.html

j. OMB, Office of Federal Financial Management (OFFM)

http://www.whitehouse.gov/omb/financial/index.html

k. DOD 4000.25-7-M (MILSBILLS)
Attachment, ADC 435

Page 15

http://www.dtic.mil/whs/directives/corres/pdf/40002507m.pdf

l. DoD 4000.25-1-M

http://www.dla.mil/j-6/dlmso/eLibrary/manuals/MILSTRIP/Default.asp

m. DOD 4000.25-M

http://www.dla.mil/j-6/dlmso/elibrary/Manuals/DLMS/default.asp

n. DOD Supply Chain Materiel Management Regulation

http://www.acq.osd.mil/log/sci/policy.htm

 o. SFIS Resources

www.bta.mil/SFIS/SFIS_Policy_Memorandum.pdf 

http://www.bta.mil/SFIS/sfis_resources.html

http://www.bta.mil/products/training/SFIS/index.html

n. GAO High Risk Area: Financial Management

http://www.whitehouse.gov/omb/expectmore/issue_summary/issue_11.html

o. DoD 4000.25-M, Defense Logistics Management System (DLMS) Volume 5 

(Finance), Chapter 5 - Interfund Billing System Procedures.

p. OSD Memo Mar 18 2009 - Linking Financial Data to Contract Documents

http://www.acq.osd.mil/dpap/policy/policyvault/USA002246-09-DPAP.pdf

q. Briefing to SFIS Governance Board December 2, 2010

http://www.dla.mil/j6/dlmso/archives/finance/documents/SFIS/SFIS_for_Governance_Board_201

0_12_02.ppt

r. BEA 8.0 Standard Financial Information Structure (SFIS)

http://www.bta.mil/SFIS/SFIS_resources.html

10. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: Staggered 

implementation is approved. 
Attachment, ADC 435

Page 16

11. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH 

IMPLEMENTATION OF THIS CHANGE. None noted. There will be costs 

associated with implementation.

12. IMPACT. 

a. Components and agencies comments on the impact of implementation are at 

enclosure (7).

b. The following new DLMS data elements will be obtained through referential data 

via the SFIS Fund Code to Fund Account Conversion Table. Business Partner 

Number will be carried in DLMS. Data elements are defined at enclosures (1) and 

(2):

1) Department Regular Code

2) Main Account Code 

3) Sub-Account Code

4) Treasury Sub Class

5) Limit/Subhead

6) Period of Availability 

7) Beginning Period of Availability

8) Ending Period of Availability

c. Implementation:

1) “Business Partner Number” will be added to applicable DLMS transactions 

as an authorized enhancement for staggered implementation.

i. STAFFING NOTE: Under the current SFIS concept the 

requirement to pass the BPN for Non-DoD buyers and sellers 

may have significant impact. This includes Special Program 

DoDAACs identified in ADC 384 and 384A.

ii. STAFFING NOTE: Components should be aware that the BPN 

is defined in the applicable supplements as repetition for the Billto Party, which is only distinguished by the identifying qualifier 

being a BPN instead of a DoDAAC. 

2) DLA Transaction Services will create a web-enabled update application for 

the authoritative SFIS Fund Code to Fund Account Conversion Table and 

will support data replication to external systems. The SFIS Fund 

Conversion Table will include the current concatenated accounting data 

element and will include the following data additional elements.

i) Department Regular Code

ii) Department Transfer Code

iii) Main Account Code 

iv) Sub-Account Code

v) Treasury Sub Class

vi) Limit/Subhead
Attachment, ADC 435

Page 17

vii) Beginning Period of Availability

 viii) Ending Period of Availability

3) DLA Transaction Services will replace the Logistics Report “Fund Code to 

Fund Account Conversion” report with the “SFIS Fund Code to Fund 

Account Conversion” report, which will display the SFIS data elements 

above in addition to the concatenated fund account. A corresponding 

change will be made to DoD 4000-25-M (MILSBILLS) Appendix 1.1 “Fund 

Code to Appropriation Conversion Table”.

4) Component/Agency Fund Code Monitors will review existing fund codes 

and delete fund codes as appropriate.

5) Once the Fund Code web update application has been completed, 

Component/Agency Fund Code Monitors will add the data elements above 

to the SFIS Fund Code to Fund Account Conversion Table.

6) Components/Agencies requiring SFIS data for their logistics business 

processes may coordinate with DLA Transaction Services to establish data 

replication or alternative means for obtaining fund code table changes.
Enclosure (1), ADC 435

Page 1

ENCLOSURE 1

SFIS DATA ELEMENTS TO BE EXCHANGED IN DLMS

DEFINITIONS AND BTA SFIS BUSINESS RULES 

NOTE:

The BTA business rules outlined below for the SFIS data elements are 

primarily for database storage and usage. They are included in this ADC for 

information regarding database configuration management and data element 

definitions in the Buyer/Seller’s AIS. SFIS business rules are outside the 

scope of DLMS.

(1) Department Regular Code - Department Regular is the US Treasury 

designated code representing the government agency accountable for one or more 

fund accounts established and maintained by the Treasury. The Department 

Regular element is an integral part of the Treasury Appropriation Fund Symbol 

(TAFS). 

Examples: 097 DoD, Office of the Secretary of Defense

021 Department of the Army

017 Department of the Navy

057 Department of the Air Force

096 Corps of Engineers

For a complete set of values, please visit: Treasury Financial Manual

http://fms.treas.gov/fastbook/fastbook_apr09.pdf

Legacy Equivalent Terminology - Treasury Index, Department Code

Syntax – three numeric

Business Rules –

 Department Regular Code must be 3 numeric characters. ex. 097

 A Department Regular Code must be associated with a unique or 

discrete combination of the following elements, per DoD Guidance: 

Main Account Code, Period of Availability Fiscal Year Date, Budget 

Activity Identifier, Budget Sub Activity Identifier, and Budget Line 

Item Identifier for funds control.

 All DoD accounting systems must store and maintain Department 

Regular Code values.

 A Department Regular Code must be established in the accounting 

classification structure when the appropriation is signed by the 

President and must be maintained until available funding has been 

canceled.
Enclosure (1), ADC 435

Page 2

(2) Department Transfer Code - The Department Transfer Code identifies the 

federal agency of obligation authority to the DoD or one of its components. For 

the transfer of obligation authority, the transfer agency retains responsibility for 

the fund account and the recipient agency charges against the fund account of the 

transfer agency.

Examples: 097 DoD, Office of the Secretary of Defense

021 Department of the Army

017 Department of the Navy

057 Department of the Air Force

096 Corps of Engineers

For a complete set of values, please visit: Treasury Financial Manual

http://fms.treas.gov/fastbook/fastbook_apr09.pdf

Legacy Equivalent Terminology - Transfer Department, Transfer 

Agency/Transfer To Department

Syntax – three numeric

Business Rules-

 A Department Transfer Code must be associated with only one unique or 

discrete combination of the following elements, per DoD Guidance: 

Department Regular Code, Main Account Code, Period of Availability 

Fiscal Year Date, Budget Activity Identifier, Budget Sub Activity 

Identifier, and Budget Line Item Identifier for funds control when 

transferring obligation authority. 

 Department Transfer Code must be 3 numeric characters. ex. 089

 Department Transfer Code must be used for accounting classification, 

general ledger posting, financial reporting, budgetary control, and funds 

control. 

 All DoD accounting systems must store and maintain Department 

Transfer Code values.

(3) Main Account Code - The main account is identified by a four digit numeric 

data element representing a specific appropriation or fund account established by 

the U.S. Treasury for expenditure or receipt authority issued by the U.S.

Congress.

Examples: 0740 Family Housing Construction, Air Force

2020 Operation & Maintenance, Army

2040 Research, Development, Test & Eval, Army
Enclosure (1), ADC 435

Page 3

2050 Military Construction, Army 

4557 Revolving Fund, National Defense Sealift

5095 Wildlife Conservation, Military Reservations

8097 Military Retirement Fund, Defense

For a complete set of values, please visit: Treasury Financial Manual

http://fms.treas.gov/fastbook/fastbook_apr09.pdf

Legacy Equivalent Terminology - Basic Symbol, Appropriation Symbol

Syntax – four numeric

Business Rules –

 A Main Account Code must be associated with one Fund Type Code.

 Each Main Account Code must be associated with only one Budget 

Function/Sub-Function Code.

 Each accounting system must store and maintain Department Transfer 

Code values.

 A Main Account Code must be associated with a unique or discrete 

combination of the following elements, per DoD Guidance: Department 

Regular Code, Beginning and Ending Period of Availability Fiscal Year 

Date, Budget Activity Identifier, Budget Sub Activity Identifier, and 

Budget Line Item Identifier for funds control.

 Main Account Code must be 4 numeric characters. ex. 0740

 Main Account Code must be used for accounting classification, general 

ledger posting, financial reporting, budgetary control, and funds control. 

 Each accounting system must store and maintain Main Account Code 

values.

 A Main Account Code must be established in the accounting classification 

structure when the appropriation is signed by the President and will be 

maintained until available funding has been canceled.

(4) Sub-Account Code - The Sub-Account symbol is used to specify subsidiary 

level accounts associated to the main account of the TAFS. The Sub-Account 

might indicate a series of subsidiary level receipt accounts or represent special 

subsidiary level accounts requested for use by an agency and approved by the US 

Treasury. Sub-account balances aggregate to the main account balance. The SubAccount has the potential for several relationships to the Main Account.
Enclosure (1), ADC 435

Page 4

Examples: 000 – Default

001 – Defense Working Capital Fund, Army

002 – Defense Working Capital Fund, Navy

For a complete set of values, please visit: Treasury Financial Manual

http://fms.treas.gov/fastbook/fastbook_apr09.pdf 

Legacy Equivalent Terminology – Derived off of Limit, Subhead, Receipt 

Indicator

Syntax – three numeric

Business Rules –

 A Sub-Account Code may be associated with many Main Account 

Codes.

 Every financial transaction processed must have a valid SubAccount Code. 

 Usage of the Sub-Account Code must be applicable to all DoD 

Departments.

 The Sub-Account Code must be defaulted to “000” when one of the 

Treasury Sub-Account Code conditions does not apply.

 "Sub-Account Code must be 3 numeric characters. ex. 97X4930.001 

(last 3 positions following period)

 Sub-Account Code must be used for accounting classification, 

general ledger posting, financial reporting, budgetary control, and 

funds control. 

 Each accounting system must store and maintain Sub-Account Code 

values.

(5) Beginning Period of Availability - In annual and multi-year accounts, 

identifies the first year of availability under law that an account may incur new 

obligations.

Example(s): If multi-fiscal Year Period of Availability where the initial fiscal 

year of availability is FY2006 - 2006.

No year Funding - Program Year (PPPP)

Values are updated yearly.
Enclosure (1), ADC 435

Page 5

Syntax – four alpha-numeric

Business Rules –

 If used for Annual or Multi-Year funding, Beginning Period of 

Availability must be four alpha-numeric characters.

 If used for No-Year funding, Beginning Period of Availability must 

be four alpha-numeric characters.

 If the Beginning Period of Availability is associated with a 

clearing/suspense Main Account, then it must be blank.

 If the Beginning Period of Availability is associated with an 

unavailable receipt account, then it must be blank.

 If used for Annual or Multi-Year funding, Beginning Period of 

Availability must be used for accounting classification, financial 

reporting, budgetary control, and funds control.

 If used for Annual or Multi-Year funding, each accounting system 

must be able to store, maintain, and report the Beginning Period of 

Availability for annual and multi-year appropriations.

 When the warrant is established by Treasury according to the signed 

appropriation bill, Beginning Period of Availability must be 

established and maintained in the accounting classification structure.

(6) Ending Period of Availability - In annual and multi-year accounts, identifies 

the last year of availability under law that an account may incur new obligations.

Example(s): If multi-fiscal year Period of Availability where the ending fiscal 

year of availability is FY2008 - 2008.

No year Funding - XXXX

Values are updated yearly.

Syntax – four alpha-numeric

Business Rules –

 Ending Period of Availability must be four alpha-numeric characters.

 If the Ending Period of Availability is associated with no-year 

funding, then it must be 'XXXX'.

 If the Ending Period of Availability is associated with a 

clearing/suspense Main Account, then it must be blank.
Enclosure (1), ADC 435

Page 6

 If the Ending Period of Availability is associated with an unavailable 

receipt account, then it must be blank.

 If used for Annual or Multi-Year funding, Ending Period of 

Availability is used for accounting classification, financial reporting, 

budgetary control, and funds control.

 If used for Annual or Multi-Year funding, each accounting system 

must be able to store, maintain, and report the Ending Period of 

Availability for annual and multi-year appropriations.

 When the warrant is established by Treasury according to the signed 

appropriation bill, Ending Period of Availability must be established 

and maintained in the accounting classification structure.

(7) Treasury Sub-Class - Sub-Class Codes are assigned in certain cases for 

grouping designated disbursement and/or receipt transactions below the level of 

appropriation or fund account represented by the main account, for an 

Appropriation, Fund, or Receipt Account. Separate sub-class identification codes 

are assigned to agencies by the Treasury to be used as parenthetical prefixes to the 

main account when preparing Disbursing Officer Reports. This data element is 

included in the file layout to accommodate the transition period. In the end state, 

this element will be removed for the file layout.

Examples: 38 Interest and Profits on Investments in Participation Certificates

41 Funds Held Outside the Treasury – Impress funds

95 Borrowing from U.S. Treasury

For a complete set of values, please visit: Chapter 3100 Instructions for 

Disbursing Officers' Reports (T/L 569)

(http://fms.treas.gov/tfm/vol1/v1p2c310.pdf)

Legacy Equivalent Terminology – Not Applicable

Syntax – up to 2 numeric characters

(8) Business Partner Number - The Business Partner Network number is a 

unique, 9-character alpha-numeric identifier. It is primarily used to identify 

buying or selling entities processing intragovernmental transactions. The Federal 

Agency Registration (Fed Reg) site is the registration point and authoritative 

source for BPN numbers and associated registration data. Federal civilian 

agencies have obtained Data Universal Numbering System (DUNS) numbers 

from Dun and Bradstreet for use as BPN numbers. DoD uses the Trading Partner 

Number (TPN) as an equivalent Business Partner Number (BPN); it consists of 

the letters “DOD” and the 6-character Department of Defense Activity Address 

Code (DoDAAC). Both the DUNS and TPN are considered BPN numbers as 

they meet Fed Reg requirements and are unique identifiers.
Enclosure (1), ADC 435

Page 7

Examples: DODF28500 - HQ AFCEE/ERB

DODHC1016 - Defense Information Systems Agency

DODN31698 - Office of the Secretary of the Navy

797054660 - Federal Element Inc.

For a complete set of values, please visit: Business Partner Network

(http://www.bpn.gov/)

Syntax - nine alpha-numeric characters

Business Rules –

 BPN Number from the Business Partner Network must be used in 

conjunction with Department Regular Code, Main Account Code 

and Sub-Account Code for eliminations.

 The Business Partner Number (BPN) Number is the unique identifier 

for those engaged in buying and selling.

 The Business Partner Network (BPN) Number for each Federal 

civilian agency, or Non-government entity, must be the nine digit 

Data Universal Numbering System (DUNS).

 The Business Partner Network (BPN) Number for DoD must be 

“DoD” plus the six character DoD Activity Address Code 

(DoDAAC).

 All agencies which buy from or sell to a Federal activity must 

register with the Business partner Network (BPN) and obtain a BPN 

Number.

 "Business Partner Number must be 9 alpha-numeric characters. ex. 

DoDN31698

 Business Partner Number must be used for general ledger posting 

and financial reporting.

 Each accounting system must store and maintain Business Partner 

Number values.
Enclosure (2), ADC 435

Page 1

ENCLOSURE 2

APPROPRIATION LIMIT/SUBHEAD DEFINITION

(1) Appropriation Limit/Subhead - The limitation or subhead is a four digit suffix to the U.S. 

Treasury account number (basic symbol). The limitation is used to identify a subdivision of funds that 

restricts the amount or use of funds for a certain purpose or identifies sub-elements within the account 

for management purposes. This data element is included in the file layout to accommodate the 

transition period. In the end state, this element will be removed from the file layout.

Examples: 0010 Washington Headquarters Services Building Management Program 

0020 US. Court of Military Appeals (USCMA) 

0100 Department of the Army.0101 US Army Reserve (USAR) 

0102 Army National Guard (ARNG) 

0103 Supervision, Inspection and Overhead (SIO) 

For a complete set of values, please visit: DFAS Manual 7097.01

http://www.asafm.army.mil/secretariat/document/709701/fy2009/709701-2009.asp#WORD

Legacy Equivalent Terminology – Not Applicable

Syntax – up to 4 alpha-numeric characters
Enclosure (3), ADC 435

Page 1

ENCLOSURE 3

SFIS DATA ELEMENTS COMPARABLE TO EXISTING DLMS DATA ELEMENTS

DEFINITIONS

NOTE: The BTA business rules outlined below for the SFIS data elements are primarily for 

database storage and usage. They are included in this ADC for information regarding database 

configuration management and data element definitions in the Buyer/Seller’s AIS. SFIS business 

rules are outside the scope of DLMS.

(1) Transaction Amount - The Transaction Amount is the signed value of an accounting 

general ledger transaction, expressed in U.S. dollars.

(2) Transaction Quantity - Quantity of units involved in the transaction.

(3) Unit of Measure Code - The Unit of Measure Code indicates the count, measurement, 

container, or form of an item. Currently, the ASC X12 v4010 is acceptable. The BTA 

formed a Working Group (July 2009) to establish a DoD consistent standard for Unit of 

Measure/Unit of Issue for all DoD Components to include Procurement, Logistics and 

Finance.

(4) Project Identifier –

a. The SFIS Project Identifier is a 24-character alphanumeric code that identifies a 

planned undertaking of work to be performed or product to be produced having a finite 

beginning and end.

b. The DLMS/MILS 3 digit project code is a subset of project identifier, and is defined 

as follows: Identifies requisitions and related documentation as to special programs, 

exercises, projects, operations or other purposes; also used for the purpose of distinguishing 

requisitions and related documentation and shipments, as well as for the accumulation of 

intra-service performance and cost data related to exercises, maneuvers, and other distinct 

programs, projects and operations. Project Codes for internal use or for use between two 

trading partners may be assigned by the Components. Policy and procedures for Project 

Codes are contained in DOD 4000.25.1-M, Military Standard Requisition Issue Procedures 

(MILSTRIP) Appendix 2.13. A listing of Category C and Category D Project Codes may be 

found on the DLA Logistics Management Standards office Web site at 

http://www.dla.mil/j6/dlmso/eLibrary/Manuals/MILSTRIP/Default.asp under “Category C 

and D Project Code Master List”. 

c. The Project Code field will be retained “as is” in the requisition format and 

procedures. Only one Project Code is applicable per requisition. The Project Code will be 

the only form of Project Identifier contained in the requisition transaction exchange. The 

buyer may record additional Project Identifiers in association with the commitment/obligation 

to be retained in the buyer’s system only.
Enclosure (4), ADC 435

Page 1

ENCLOSURE 4

SFIS DATA ELEMENTS ENVISOINED TO BE RETAINED IN 

DOD COMPONENT SOURCE SYSTEMS

DEFINITIONS AND BTA SFIS BUSINESS RULES 

It is envisioned that below Cost Accounting data elements will be captured by the 

Buyer’s ERP (Military Service ERP) and internal to their Logistics and Financial 

systems (no Enterprise list of values applicable to this element exists). There is 

not a requirement for the Buyer to communicate this information to the Seller. It 

is envisioned that Buyer’s ERP will capture these data elements in association 

with the commitment and obligation.

NOTE:

The BTA business rules outlined for the below SFIS data elements are 

primarily for database storage and usage They are included in this ADC to 

further define the database configuration management and data element 

definitions in the Buyer/Seller’s AIS.

(1) Budget Line Item Identifier - Identifies further sub-divisions of the Treasury 

Account Fund Symbol appropriation, below the Budget Sub Activity Level. It is 

the lowest level of the appropriation budget (i.e. Procurement, Research and 

Development, Operations and Maintenance)

Examples: PROCUREMENT "Weapons System Code"- 8485A11000 Utility 

Fixed Wing Cargo Aircraft

RDT&E uses "OSD Program Element" - 0204136N F/A-18 

Squadrons

MILCON uses "Location & Project" - 4962 05057041

O&M uses "SAG Code"- 020 Corps Combat Forces

MILPERS uses "Pay Type" 

WCF uses "Activity" - i.e. Accounting-Navy

For a complete set of values, please visit: Defense Budget Materials Website

http://www.defenselink.mil/comptroller/defbudget/fy2009/index.html

Legacy Equivalent Terminology – Same as examples listed above

Syntax – Up to 16 alpha numeric characters

(2) Transaction Effective Date -The effective date for a business event 

represented by a transaction type/transaction code. Although, this date frequently 

equals the Transaction Post Date, it is not always equal. As an example: an 

obligation that exists at the end of a reporting period is discovered just after the 

period ends. The obligation would be posted in the general ledger on a date after 
Enclosure (4), ADC 435

Page 2

the end of the period; however, the transaction would be effective for a date prior 

to the period end, and would be included in the reports for that period.

Examples: "03142005" where 03 = Month, 14=Day, 2005 = Calendar Year

The values change based the effective date of the business event.

Legacy Equivalent Terminology - Accounting Period, Document, Contract Date, 

Report Date, Travel Start Date, Travel Date, Voucher Date, Input Date, System 

Date

Syntax - eight numeric characters 1st two characters are Month, 2nd two characters 

are Day, and last four characters are year. 

(3) Funding Center Identifier - Funding Center is a clearly defined 

responsibility area within an organizational unit to which budget authority is 

assigned.

Examples: These are user/system defined cost accounting values.

Values: These are user/system defined cost accounting values.

Legacy Equivalent Terminology – None

Syntax – up to 16 alpha numeric characters

(4) Cost Center Identifier - A Cost Center is a clearly defined responsibility 

area where costs are incurred.

Examples: These are user/system defined cost accounting values.

Values: These are user/system defined cost accounting values.

Legacy Equivalent Terminology – Cost Center, Assigned and Performing Cost 

Center, Profit Center, Assigned and Performing Profit Center, Sub Cost Center, 

Project Directed Line Item, Task Code, Element of Cost, Responsibility Cost 

Center, Organizational Responsibility Center

Syntax – up to 16 alpha numeric characters

(5) Agency Accounting Identifier - The Agency Accounting Identifier 

identifies the organization responsible for providing field level accounting support 

within DoD. This code may be the identification of Field Sites or unique 

accounting installation that support the budget execution of a specific base, post, 

camp, or station.

 Primary Steward: OUSD(C)

 Authoritative Source: http://referencetool.dfas.mil
Enclosure (4), ADC 435

Page 3

 Sample Business Rules from BEA: 

o Agency Accounting Identifier must be 6 numeric characters. 

ex. 000318

o Agency Accounting Identifier must be used for accounting 

classification and financial reporting. 

o Accounting systems must store and maintain Agency 

Accounting Identifier values. 

(6) Activity Identifier - An Activity is a series of events, tasks, or units of work 

that are linked to perform a specific objective.

Examples: These are user/system defined cost accounting values.

Values: These are user/system defined cost accounting values.

Legacy Equivalent Terminology – Ship, Ship Class, Cost Account Code, Military 

Expense Reporting System Code, Resource Pool, RID, Element of Cost

Syntax – up to 12 alpha numeric characters

(7) Work Order Number - Identifies an individual unit of work, batch, or lot of 

a distinct product or service.

Examples: These are user/system defined cost accounting values.

Values: These are user/system defined cost accounting values.

Legacy Equivalent Terminology – Job Order Number, Job Order Cost Code, 

Work Breakdown Structure, Project Task, Job Order Cost Code

Syntax – up to 16 alpha-numeric characters

NOTE: Under DLMS the work order number, the job order number and the 

work breakdown structure are carried for specific user communities as a DLMS 

enhancement to various transactions.
Enclosure (5), ADC 435

Page 1

ENCLOSURE 5

REVISIONS TO DLMS SUPPLEMENTS

# Location DS 511R Requisition Reason

1. DLMS 

Introductory 

Notes

Add ADC 435

- ADC 435, DLMS Revisions for Standard Financial 

Information Structure (SFIS) Compliance 

Identifies DLMS 

Changes included in the 

DLMS Supplement

2.

2/N101/180

2/N103/180

2/FA201/286

Revise to add new qualifiers and notes to existing 

qualifiers:

BT Bill to Party

DLMS Note:

1. Use with code ST for reimbursable material. Use to 

identify the organization to receive the billing for 

material when different form the organization receiving 

the material Use precludes the use of Code BS for the 

Bill-to DoDAAC.

2. Use for SFIS compliant systems to identify the BPN 

of the party to receive the bill. BPN may only be 

used when the corresponding DoDAAC is also 

provided. This will require a second iteration of the 

N1 loop with the same qualifier, if BT was also used 

to identify the Bill-to DoDAAC.

3. Authorized DLMS enhancement; see introductory 

DLMS note 3f.

50 Business License Number

DLMS Note:

1. Use for SFIS to map to SFIS Data element 

“Business Partner Number TP3”. Enter the 

buyer’s BPN in N104.

2. Authorized DLMS enhancement; see introductory 

DLMS note 3f.

Revise to Delete the following Qualifiers

18 Funds Appropriation

DLMS Note:

1. Use to indicate the basic appropriation number.

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

A1 Department Indicator

DLMS Note:

1. Use to identify the SFIS data element “Department 

Regular Code A1”.

2. Authorized DLMS enhancement; see introductory 

note 3f.

A2 Transfer From Department

DLMS Note:

1. Use to identify the SFIS data element “Department 

Transfer Code A2”.

2. Authorized DLMS enhancement; see introductory 

note 3f.

These qualifiers have 

been mapped to specific 

SFIS data elements.

There is no identified 

need for these qualifiers 

in this 

transaction/section.
Enclosure (5), ADC 435

Page 2

# Location DS 511R Requisition Reason

A3 Fiscal Year Indicator

DLMS Note:

1. Use to identify the SFIS data element “Period of 

Availability Fiscal Year Date A8”

2. Authorized DLMS enhancement; see introductory 

DLMS note 3f.

A4 Basic Symbol Number

DLMS Note:

1. Use to identify the SFIS data element “Main 

Account Code A3”.

2. Authorized DLMS enhancement; see introductory 

DLMS note 3f.

A5 Sub-class

DLMS Note:

1. Use to identify the SFIS data element “Treasury 

Sub Class A5”

2. Authorized DLMS enhancement; see introductory 

DLMS note 3f.

A6 Sub-Account Symbol

DLMS Note:

1. Use to identify the SFIS data element “Sub 

Account Code A4”

2. Authorized DLMS enhancement; see introductory 

DLMS note 3f.

A7 Subhead or Limit

1. Use to identify the Subhead or Limit

2. Authorized DLMS enhancement; see introductory 

DLMS note 3f.

B1 Budget Activity Number

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

B2 Budget Sub-activity Number

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

B3 Budget Program Activity

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

B4 Program Year Indicator

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

BL Billings

Federal Note:

Use to indicate the Government IMPAC card number under 

which payment for this obligation will be accomplished.

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

C1 Program Element
Enclosure (5), ADC 435

Page 3

# Location DS 511R Requisition Reason

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

C2 Project Task or Budget Subline

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

C3 Budget Restriction

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

D1 Defense Agency Allocation Recipient

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

D2 Defense Agency Sub-allocation Recipient

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

D3 Component Allocation Recipient

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

D4 Component Sub-allocation Recipient

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

D5 Allotment Recipient

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

D6 Sub-allotment Recipient

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

D7 Work Center Recipient

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

E1 Major Reimbursement Source Code

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

E2 Detail Reimbursement Source Code

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

E3 Customer Indicator

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

F1 Object Class

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

F2 Object Sub-class

DLMS Note:
Enclosure (5), ADC 435

Page 4

# Location DS 511R Requisition Reason

DLMS enhancement; see introductory DLMS note 3a.

F3 Government or Public Sector Identifier

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

F4 Country Code

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

G1 Program or Planning Code

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

G2 Special Interest Code or Special Program Cost Code

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

H1 Cost Code

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

H2 Labor Type Code

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

H3 Cost Allocation Code

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

H4 Classification Code

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

J1 Document or Record Reference Number

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

M1 Local Installation Data

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

N1 Transaction Type

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

P1 Disbursing Station Number

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

P2 International Balance of Payments (IBOP) Code

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

P3 Voucher Number

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.
Enclosure (5), ADC 435

Page 5

# Location DS 511R Requisition Reason

P5 Foreign Military Sales (FMS) Line Item Number

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

.

P6 Contract Payment Notice (CPN) Recipient Indicator

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

ZZ Mutually Defined

DLMS Note:

1. Cite supplemental accounting classification data.

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

# Location DS 511M Requisition Modifier Reason

1. DLMS 

Introductory 

Notes

Add ADC 435

- ADC 435, DLMS Revisions for SFIS Compliance 

Identifies DLMS Changes 

included in the DLMS 

Supplement

2.

2/N101/180

2/N103/180

2/FA201/286

Revise to add new qualifiers and notes to existing 

qualifiers:

BT Bill-to Party

DLMS Note:

1. Use with code ST for reimbursable material. Use to 

modify, or in the case of an unmatched modification, use 

to identify the organization to receive billing for material 

when different form the organization receiving the 

material. Use precludes the use of Code BS for the Billto DoDAAC. Modifier transactions may not be used to 

change this field for GFM requisitions.

2. Use for SFIS compliant systems to identify the BPN 

of the party to receive the bill. BPN may only be used 

when the corresponding DoDAAC is also provided.

This will require a second iteration of the N1 loop

with the same qualifier, if BT was also used to 

identify the Bill-to DoDAAC.

3. Authorized DLMS enhancement; see introductory 

DLMS note 3g.

50 Business License Number

DLMS Note:

1. Use for SFIS to map to SFIS Data element 

“Business Partner Number TP3”. Enter the buyer’s 

BPN in N104.

2. Authorized DLMS enhancement; see introductory 

DLMS note 3g.

Revise to Delete the following Qualifiers

18 Funds Appropriation

DLMS Note:

1. Use to indicate the basic appropriation number.

These qualifiers have been 

mapped to specific SFIS 

data elements.

There is no identified need 

for these qualifiers in this 

transaction/section.
Enclosure (5), ADC 435

Page 6

# Location DS 511M Requisition Modifier Reason

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

A1 Department Indicator

DLMS Note:

1. Use to identify the SFIS data element “Department 

Regular Code A1”

2. Authorized DLMS enhancement; see introductory 

note 3g.

A2 Transfer From Department

DLMS Note:

1. Use to identify the SFIS data element “Department 

Transfer Code A2”.

2. Authorized DLMS enhancement; see introductory 

note 3g.

A3 Fiscal Year Indicator

DLMS Note:

1. Use to identify the SFIS data element “Period of 

Availability Fiscal Year Date A8”

2. Authorized DLMS enhancement; see introductory 

DLMS note 3g.

A4 Basic Symbol Number

DLMS Note:

1. Use to identify the SFIS data element “Main 

Account Code A3”.

2. Authorized DLMS enhancement; see introductory 

DLMS note 3g.

A5 Sub-class

DLMS Note:

1. Use to identify the SFIS data element “Treasury Sub 

Class”

2. Authorized DLMS enhancement; see introductory 

DLMS note 3g.

A6 Sub-Account Symbol

DLMS Note:

1. Use to identify the SFIS data element “Sub Account 

Code A4”

2. Authorized DLMS enhancement; see introductory 

DLMS note 3g.

A7 Subhead or Limit

1. Use to identify the Subhead or Limit.

2. Authorized DLMS enhancement; see introductory 

DLMS note 3g.

B1 Budget Activity Number

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

B2 Budget Sub-activity Number

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.
Enclosure (5), ADC 435

Page 7

# Location DS 511M Requisition Modifier Reason

BL Billings

Federal Note:

Use to indicate the Government IMPAC card number under which 

payment for this obligation will be accomplished.

C1 Program Element

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

C2 Project Task or Budget Subline

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

C3 Budget Restriction

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

D1 Defense Agency Allocation Recipient

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

D2 Defense Agency Sub-allocation Recipient

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

D3 Component Allocation Recipient

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

D4 Component Sub-allocation Recipient

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

D5 Allotment Recipient

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

D6 Sub-allotment Recipient

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

D7 Work Center Recipient

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

E1 Major Reimbursement Source Code

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

E2 Detail Reimbursement Source Code

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

E3 Customer Indicator

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.
Enclosure (5), ADC 435

Page 8

# Location DS 511M Requisition Modifier Reason

F1 Object Class

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

F2 Object Sub-class

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

F3 Government or Public Sector Identifier

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

F4 Country Code

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

G1 Program or Planning Code

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

G2 Special Interest Code or Special Program Cost Code

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

H1 Cost Code

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

H2 Labor Type Code

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

H3 Cost Allocation Code

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

H4 Classification Code

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

J1 Document or Record Reference Number

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

N1 Transaction Type

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

P1 Disbursing Station Number

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

P2 International Balance of Payments (IBOP) Code

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

P3 Voucher Number
Enclosure (5), ADC 435

Page 9

# Location DS 511M Requisition Modifier Reason

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

ZZ Mutually Defined

DLMS Note:

1. Cite supplemental accounting classification data.

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

# Location DS 869F Requisition Follow Up Reason

1. DLMS 

Introductory 

Notes

Add ADC 435

- ADC 435, DLMS Revisions for SFIS Compliance 

Identifies DLMS Changes 

included in the DLMS 

Supplement

2. DLMS 

Introductory 

Notes

4.g Data associated with a DLMS enhancement authorized for 

implementation by modernized systems under DLMS migration. 

This data (including expanded field sizes) should be adopted 

during, or subsequent, to modernization when applicable to the 

Component’s business process. Prior coordination is not 

required. Components should ensure that inclusion of this data in 

a DLMS transaction does not cause inappropriate rejection of the 

transaction.

Identifies changes as

authorized future 

enhancement

3

2/N101/110

2/N103/110

2/FA201/200

Revise to add new qualifiers and notes to existing 

qualifiers:

BT Bill-to Party

DLMS Note:

1. Use with code ST for reimbursable material. Use to 

identify the organization to receive billing for material 

when different from the organization receiving the 

material. Use precludes the use of code BS for the Bill-to 

DoDAAC. 

2. Use for SFIS compliant systems to identify the BPN 

of the party to receive the bill. BPN may only be used 

when the corresponding DoDAAC is also provided.

This will require a second iteration of the N1 loop

with the same qualifier, if BT was also used to 

identify the Bill-to DoDAAC.

3. Authorized DLMS enhancement; see introductory 

DLMS note 4g.

50 Business License Number

DLMS Note:

1. Use for SFIS to map to SFIS Data element 

“Business Partner Number TP3”. Enter the buyer’s 

BPN in N104.

2. Authorized DLMS enhancement; see introductory 

DLMS note 4g .

Revise to delete the following qualifiers:

18 Funds Appropriation

DLMS Note:

These qualifiers have been 

mapped to specific SFIS 

data elements.

There is no identified need 

for these qualifiers in this 

transaction/section.
Enclosure (5), ADC 435

Page 10

# Location DS 869F Requisition Follow Up Reason

Use to indicate the basic appropriation number.

A1 Department Indicator

DLMS Note:

1. Use to identify the SFIS data element “Department 

Regular Code A1”

2. Authorized DLMS enhancement; see introductory 

note 4g.

A2 Transfer From Department

DLMS Note:

1. Use to identify the SFIS data element “Department 

Transfer Code A2”.

2. Authorized DLMS enhancement; see introductory 

note 4g.

A3 Fiscal Year Indicator

DLMS Note:

1. Use to identify the SFIS data element “Period of 

Availability Fiscal Year Date A8”

2. Authorized DLMS enhancement; see introductory 

DLMS note 4g.

A4 Basic Symbol Number

DLMS Note:

1. Use to identify the SFIS data element “Main 

Account Code A3”.

2. Authorized DLMS enhancement; see introductory 

DLMS note 4g.

A5 Sub-class

DLMS Note:

1. Use to identify the SFIS data element “Treasury 

Sub Class”

2. Authorized DLMS enhancement; see introductory 

DLMS note 4g.

A6 Sub-Account Symbol

DLMS Note:

1. Use to identify the SFIS data element “Sub Account 

Code A4”

2. Authorized DLMS enhancement; see introductory 

DLMS note 4g.

A7 Subhead or Limit

2. Use to identify the Subhead or Limit.

1. Authorized DLMS enhancement; see introductory 

DLMS note 4g.

B1 Budget Activity Number

B2 Budget Sub-activity Number

BL Billings

Federal Note:

Use to indicate the Government IMPAC card number under which 

payment for this obligation will be accomplished.
Enclosure (5), ADC 435

Page 11

# Location DS 869F Requisition Follow Up Reason

C1 Program Element

C2 Project Task or Budget Subline

C3 Budget Restriction

D1 Defense Agency Allocation Recipient

D2 Defense Agency Sub-allocation Recipient

D3 Component Allocation Recipient

D4 Component Sub-allocation Recipient

D5 Allotment Recipient

D6 Sub-allotment Recipient

D7 Work Center Recipient

E1 Major Reimbursement Source Code

E2 Detail Reimbursement Source Code

E3 Customer Indicator

F1 Object Class

F2 Object Sub-class

F3 Government or Public Sector Identifier

F4 Country Code

G1 Program or Planning Code

G2 Special Interest Code or Special Program Cost Code

H1 Cost Code

H2 Labor Type Code

H3 Cost Allocation Code

H4 Classification Code

J1 Document or Record Reference Number

N1 Transaction Type

P1 Disbursing Station Number

P2 International Balance of Payments (IBOP) Code

P3 Voucher Number
Enclosure (5), ADC 435

Page 12

# Location DS 869F Requisition Follow Up Reason

ZZ Mutually Defined

DLMS Note:

Cite supplemental accounting classification data.

# Location DS 180M Material Returns Reporting Reason

1. DLMS 

Introductory 

Notes

Add ADC 435

- ADC 435, DLMS Revisions for SFIS Compliance 

Identifies DLMS 

Changes included in the 

DLMS Supplement

2. DLMS 

Introductory 

Notes

2.f Data associated with a DLMS enhancement authorized for 

implementation by modernized systems under DLMS migration. 

This data (including expanded field sizes) should be adopted 

during, or subsequent, to modernization when applicable to the 

Component’s business process. Prior coordination is not 

required. Components should ensure that inclusion of this data in 

a DLMS transaction does not cause inappropriate rejection of the 

transaction.

Identifies changes as

authorized future 

enhancement.

3

2/N101/60

2/N103/60

2/FA201/226

Revise to add new qualifiers

ZB Party to Receive Credit

DLMS Note:

1. Use as needed for material availability reports and 

automatic shipment notifications to identify the 

organization to receive credit.

2. Use for SFIS compliant systems to identify the BPN 

of the party to receive credit. BPN may only be used 

when the corresponding DoDAAC is also provided.

This will require a second iteration of the N1 loop 

with the same qualifier if ZB was also used to identify 

the party to receive credit.

3. Authorized DLMS enhancement; see introductory 

DLMS note 2f.

50 Business License Number

DLMS Note:

1. Use for SFIS to map to SFIS Data element 

“Business Partner Number TP3”. Enter the seller’s

BPN in N104.

2. Authorized DLMS enhancement; see introductory 

note 2f.

Revise to delete the following qualifiers:

18 Funds Appropriation

DLMS Note:

Use to indicate the basic appropriation number.

A1 Department Indicator

DLMS Note:

1. Use to identify the SFIS data element “Department 

Regular Code A1”

2. Authorized DLMS enhancement; see introductory 

note 2f.

A2 Transfer From Department

DLMS Note:

These qualifiers have 

been mapped to specific 

SFIS data elements

There is no identified 

need for these qualifiers 

in this transaction 

segment.
Enclosure (5), ADC 435

Page 13

# Location DS 180M Material Returns Reporting Reason

1. Use to identify the SFIS data element “Department 

Transfer Code A2”.

2. Authorized DLMS enhancement; see introductory 

note 2f.

A3 Fiscal Year Indicator

DLMS Note:

1. Use to identify the SFIS data element “Period of 

Availability Fiscal Year Date A8”

2. Authorized DLMS enhancement; see introductory 

DLMS note 2f.

A4 Basic Symbol Number

DLMS Note:

1. Use to identify the SFIS data element “Main 

Account Code A3”.

2. Authorized DLMS enhancement; see introductory 

DLMS note 2f.

A5 Sub-class

DLMS Note:

1. Use to identify the SFIS data element “Treasury 

Sub Class”

2. Authorized DLMS enhancement; see introductory 

DLMS note 2f.

A6 Sub-Account Symbol

DLMS Note:

1. Use to identify the SFIS data element “Sub Account 

Code A4”

2. Authorized DLMS enhancement; see introductory 

DLMS note 2f.

A7 Subhead or Limit

3. Use to identify the Subhead or Limit.

4. Authorized DLMS enhancement; see introductory 

DLMS note 2f.

B1 Budget Activity Number

B2 Budget Sub-activity Number

BL Billings

Federal Note:

Use to indicate the Government IMPAC card number under which 

payment for this obligation will be accomplished.

C1 Program Element

C2 Project Task or Budget Subline

C3 Budget Restriction

D1 Defense Agency Allocation Recipient

D2 Defense Agency Sub-allocation Recipient
Enclosure (5), ADC 435

Page 14

# Location DS 180M Material Returns Reporting Reason

D3 Component Allocation Recipient

D4 Component Sub-allocation Recipient

D5 Allotment Recipient

D6 Sub-allotment Recipient

D7 Work Center Recipient

E1 Major Reimbursement Source Code

E2 Detail Reimbursement Source Code

E3 Customer Indicator

F1 Object Class

F2 Object Sub-class

F3 Government or Public Sector Identifier

F4 Country Code

G1 Program or Planning Code

G2 Special Interest Code or Special Program Cost Code

H1 Cost Code

H2 Labor Type Code

H3 Cost Allocation Code

H4 Classification Code

J1 Document or Record Reference Number

N1 Transaction Type

P1 Disbursing Station Number

P2 International Balance of Payments (IBOP) Code

P3 Voucher Number

ZZ Mutually Defined

DLMS Note:

Cite supplemental accounting classification data.

# Location 517M Material Obligation Validation

1. DLMS Introductory 

Notes

Add ADC 435

- ADC 435, DLMS Revisions for SFIS Compliance 

Identifies DLMS 

Changes included in the 

DLMS Supplement

2. DLMS Introductory 

Notes

3.f. Data associated with a DLMS enhancement authorized 

for implementation by modernized systems under DLMS 

Identifies changes as

authorized future 
Enclosure (5), ADC 435

Page 15

# Location 517M Material Obligation Validation

migration. This data (including expanded field sizes) 

should be adopted during, or subsequent, to modernization 

when applicable to the Component’s business process. 

Prior coordination is not required. Components should 

ensure that inclusion of this data in a DLMS transaction 

does not cause inappropriate rejection of the transaction.

enhancement.

3

1/N101/60

1/N103/60

2/FA201/136

Revise to add new qualifiers and notes to existing 

qualifiers:

BT Bill-to Party

1. Use for SFIS compliant systems to identify the 

BPN of the party to receive the bill. BPN may 

only be used when the corresponding 

DoDAAC is also provided. This will require a 

second iteration of the N1 loop with the same 

qualifier.

2. Authorized DLMS enhancement; see 

introductory DLMS note 3f.

50 Business License Number

DLMS Note:

1. Use for SFIS to map to SFIS Data element 

“Business Partner Number TP3”. Enter the 

buyer’s BPN in N104.

2. Authorized DLMS enhancement; see 

introductory DLMS note 3f.

Revise to delete the following qualifiers:

18 Funds Appropriation

DLMS Note:

Use to indicate the basic appropriation number.

A1 Department Indicator

DLMS Note:

1. Use to identify the SFIS data element 

“Department Regular Code A1”

2. Authorized DLMS enhancement; see 

introductory note 3f.

A2 Transfer From Department

DLMS Note:

1. Use to identify the SFIS data element 

“Department Transfer Code A2”.

2. Authorized DLMS enhancement; see 

introductory note 3f.

A3 Fiscal Year Indicator

DLMS Note:

1. Use to identify the SFIS data element “Period 

of Availability Fiscal Year Date A8”

2. Authorized DLMS enhancement; see 

introductory DLMS note 3f.

A4 Basic Symbol Number

DLMS Note:

1. Use to identify the SFIS data element “Main 

These qualifiers have 

been mapped to specific 

SFIS data elements

There is no identified 

need for these qualifiers 

in this transaction 

segment.
Enclosure (5), ADC 435

Page 16

# Location 517M Material Obligation Validation

Account Code A3”.

2. Authorized DLMS enhancement; see 

introductory DLMS note 3f.

A5 Sub-class

DLMS Note:

1. Use to identify the SFIS data element 

“Treasury Sub Class”

2. Authorized DLMS enhancement; see 

introductory DLMS note 3f.

A6 Sub-Account Symbol

DLMS Note:

1. Use to identify the SFIS data element “Sub 

Account Code A4”

2. Authorized DLMS enhancement; see 

introductory DLMS note 3f.

A7 Subhead or Limit

1. Use to identify the Subhead or Limit.

2. Authorized DLMS enhancement; see 

introductory DLMS note 3f.

B1 Budget Activity Number

B2 Budget Sub-activity Number

BL Billings

Federal Note:

Use to indicate the Government IMPAC card number 

under which payment for this obligation will be 

accomplished.

C1 Program Element

C2 Project Task or Budget Subline

C3 Budget Restriction

D1 Defense Agency Allocation Recipient

D2 Defense Agency Sub-allocation Recipient

D3 Component Allocation Recipient

D4 Component Sub-allocation Recipient

D5 Allotment Recipient

D6 Sub-allotment Recipient

D7 Work Center Recipient

E1 Major Reimbursement Source Code

E2 Detail Reimbursement Source Code
Enclosure (5), ADC 435

Page 17

# Location 517M Material Obligation Validation

E3 Customer Indicator

F1 Object Class

F2 Object Sub-class

F3 Government or Public Sector Identifier

F4 Country Code

G1 Program or Planning Code

G2 Special Interest Code or Special Program Cost Code

H1 Cost Code

H2 Labor Type Code

H3 Cost Allocation Code

H4 Classification Code

J1 Document or Record Reference Number

N1 Transaction Type

P1 Disbursing Station Number

P2 International Balance of Payments (IBOP) Code

P3 Voucher Number

ZZ Mutually Defined

DLMS Note:

Cite supplemental accounting classification data.

# Location 867I Issue

1. DLMS Introductory 

Notes

Add ADC 435

- ADC 435, DLMS Revisions for SFIS Compliance 

Identifies DLMS 

Changes included in the 

DLMS Supplement

2. 1/N101/80

1/N101/80

Revise the DLMS note to recognize more than one 

qualifier is approved for use with the element:

Entity Identifier Code

DLMS Note: For DLMS use, only the following codes areis

authorized.

Revise to add new qualifiers and notes to existing 

qualifiers:

BT Bill-to Party

1. Use for SFIS compliant systems to identify the 

BPN of the party to receive the bill. BPN may 

only be used when the corresponding 

These qualifiers have 

been mapped to specific 

SFIS data elements
Enclosure (5), ADC 435

Page 18

# Location 867I Issue

1/N103/80

2/FA201/136

DoDAAC is also provided. This will require a 

second iteration of the N1 loop with the same 

qualifier.

2. Authorized DLMS enhancement; see 

introductory DLMS note 5e.

50 Business License Number

DLMS Note:

1. Use for SFIS to map to SFIS Data element 

“Business Partner Number TP3”. Enter the 

buyer’s BPN in N104.

2. Authorized DLMS enhancement; see 

introductory DLMS note 5e.

Revise to delete the following qualifiers:

18 Funds Appropriation

DLMS Note:

Use to indicate the basic appropriation number.

A1 Department Indicator

DLMS Note:

1. Use to identify the SFIS data element 

“Department Regular Code A1”

2. Authorized DLMS enhancement; see 

introductory note 5e.

A2 Transfer From Department

DLMS Note:

1. Use to identify the SFIS data element 

“Department Transfer Code A2”.

2. Authorized DLMS enhancement; see 

introductory note 5e.

A3 Fiscal Year Indicator

DLMS Note:

1. Use to identify the SFIS data element “Period 

of Availability Fiscal Year Date A8”

2. Authorized DLMS enhancement; see 

introductory DLMS note 5e.

A4 Basic Symbol Number

DLMS Note:

1. Use to identify the SFIS data element “Main 

Account Code A3”.

2. Authorized DLMS enhancement; see 

introductory DLMS note 5e.

A5 Sub-class

DLMS Note:

1. Use to identify the SFIS data element 

“Treasury Sub Class”

2. Authorized DLMS enhancement; see 

introductory DLMS note 5e.

A6 Sub-Account Symbol

DLMS Note:

There is no identified 

need for these qualifiers 

in this transaction 

segment.
Enclosure (5), ADC 435

Page 19

# Location 867I Issue

1. Use to identify the SFIS data element “Sub 

Account Code A4”

2. Authorized DLMS enhancement; see 

introductory DLMS note 5e.

A7 Subhead or Limit

1. Use to identify the Subhead or Limit.

2. Authorized DLMS enhancement; see 

introductory DLMS note 5e.

B1 Budget Activity Number

B2 Budget Sub-activity Number

BL Billings

Federal Note:

Use to indicate the Government IMPAC card number 

under which payment for this obligation will be 

accomplished.

C1 Program Element

C2 Project Task or Budget Subline

C3 Budget Restriction

D1 Defense Agency Allocation Recipient

D2 Defense Agency Sub-allocation Recipient

D3 Component Allocation Recipient

D4 Component Sub-allocation Recipient

D5 Allotment Recipient

D6 Sub-allotment Recipient

D7 Work Center Recipient

E1 Major Reimbursement Source Code

E2 Detail Reimbursement Source Code

E3 Customer Indicator

F1 Object Class

F2 Object Sub-class

F3 Government or Public Sector Identifier

F4 Country Code

G1 Program or Planning Code

G2 Special Interest Code or Special Program Cost Code
Enclosure (5), ADC 435

Page 20

# Location 867I Issue

H1 Cost Code

H2 Labor Type Code

H3 Cost Allocation Code

H4 Classification Code

J1 Document or Record Reference Number

N1 Transaction Type

P1 Disbursing Station Number

P2 International Balance of Payments (IBOP) Code

P3 Voucher Number

ZZ Mutually Defined

DLMS Note:

Cite supplemental accounting classification data.

# Location 940R Material Release

1. DLMS 

Introductory Notes

Add ADC 435

- ADC 435, DLMS Revisions for SFIS Compliance 

Identifies DLMS 

Changes included in 

the DLMS 

Supplement

2. DLMS 

Introductory Notes

4.f. Data associated with a DLMS enhancement authorized 

for implementation by modernized systems under DLMS 

migration. This data (including expanded field sizes) should 

be adopted during, or subsequent, to modernization when 

applicable to the Component’s business process. Prior 

coordination is not required. Components should ensure 

that inclusion of this data in a DLMS transaction does not 

cause inappropriate rejection of the transaction.

Identifies changes as

authorized future 

enhancement.

3

2/N101/1100

Revise to add new qualifiers and notes to existing 

qualifiers:

BT Bill-to Party

DLMS Note:

1. Use with code ST for reimbursable material. Use in 

redistribution orders, material release orders, 

historical material release orders, material release 

order modifications, disposal release orders, and 

historical disposal release orders to identify the 

organization to receive the billing for the material 

when different from the organization receiving the 

material. Use precludes the use of code BS for the 

Bill-to DoDAAC

2. Use for SFIS compliant systems to identify the 

BPN of the party to receive the bill. BPN may 

only be used when the corresponding DoDAAC 

These qualifiers 

have been mapped to 

specific SFIS data 

elements
Enclosure (5), ADC 435

Page 21

# Location 940R Material Release

2/N103/1100

2/FA201/3000

is also provided. This will require a second 

iteration of the N1 loop with the same qualifier, if 

BT was also used to identify the Bill-to DoDAAC.

3. Authorized DLMS enhancement; see 

introductory DLMS note 4f.

50 Business License Number

DLMS Note:

1. Use for SFIS to map to SFIS Data element 

“Business Partner Number TP3”. Enter the 

buyer’s BPN in N104.

2. Authorized DLMS enhancement; see 

introductory DLMS note 4f.

Revise to delete the following qualifiers:

18 Funds Appropriation

DLMS Note:

Use to indicate the basic appropriation number.

A1 Department Indicator

DLMS Note:

1. Use to identify the SFIS data element 

“Department Regular Code A1”

2. Authorized DLMS enhancement; see 

introductory note 4f.

A2 Transfer From Department

DLMS Note:

1. Use to identify the SFIS data element 

“Department Transfer Code A2”.

2. Authorized DLMS enhancement; see 

introductory note 4f.

A3 Fiscal Year Indicator

DLMS Note:

1. Use to identify the SFIS data element “Period 

of Availability Fiscal Year Date A8”

2. Authorized DLMS enhancement; see 

introductory DLMS note 4f.

A4 Basic Symbol Number

DLMS Note:

1. Use to identify the SFIS data element “Main 

Account Code A3”.

2. Authorized DLMS enhancement; see 

introductory DLMS note 4f.

A5 Sub-class

DLMS Note:

1. Use to identify the SFIS data element 

“Treasury Sub Class”

2. Authorized DLMS enhancement; see 

introductory DLMS note 4f.

A6 Sub-Account Symbol

DLMS Note:

There is no 

identified need for 

these qualifiers in 

this transaction 

segment.
Enclosure (5), ADC 435

Page 22

# Location 940R Material Release

1. Use to identify the SFIS data element “Sub 

Account Code A4”

2. Authorized DLMS enhancement; see 

introductory DLMS note 4f.

A7 Subhead or Limit

3. Use to identify the Limit or Subhead

4. Authorized DLMS enhancement; see 

introductory DLMS note 4f.

5. This is a local code. A data request has been 

submitted to ANSI X12 to add this code.

B1 Budget Activity Number

B2 Budget Sub-activity Number

BL Billings

Federal Note:

Use to indicate the Government IMPAC card number under 

which payment for this obligation will be accomplished.

C1 Program Element

C2 Project Task or Budget Subline

C3 Budget Restriction

D1 Defense Agency Allocation Recipient

D2 Defense Agency Sub-allocation Recipient

D3 Component Allocation Recipient

D4 Component Sub-allocation Recipient

D5 Allotment Recipient

D6 Sub-allotment Recipient

D7 Work Center Recipient

E1 Major Reimbursement Source Code

E2 Detail Reimbursement Source Code

E3 Customer Indicator

F1 Object Class

F2 Object Sub-class

F3 Government or Public Sector Identifier

F4 Country Code

G1 Program or Planning Code
Enclosure (5), ADC 435

Page 23

# Location 940R Material Release

G2 Special Interest Code or Special Program Cost Code

H1 Cost Code

H2 Labor Type Code

H3 Cost Allocation Code

H4 Classification Code

J1 Document or Record Reference Number

N1 Transaction Type

P1 Disbursing Station Number

P2 International Balance of Payments (IBOP) Code

P3 Voucher Number

ZZ Mutually Defined

DLMS Note:

Cite supplemental accounting classification data.

2/FA201/3000 Remove DLMS note 2 from code B5

B5 Fund Code

DLMS Note: 1. Use in material release order modifications 

to identify the revised fund code.

2. Future streamlined data; see introductory DLMS note 4c

No longer applicable

# Location DS 856S Ship Notice/Manifest Reason

1. DLMS 

Introductory 

Notes

Add ADC 435

- ADC 435, DLMS Revisions for SFIS Compliance 

Identifies DLMS 

Changes included in the 

DLMS Supplement

2. 2/REF04/1500 Revise to delete the following qualifiers:

DP Department Number

DLMS Note:

1. Use to identify the SFIS data element 

“Department Regular Code A1”.

2. Authorized DLMS enhancement; see 

introductory note 2f.

93 Funds Authorization

DLMS Note:

1. Use to identify the SFIS data element 

“Department Transfer Code A2”.

2. Authorized DLMS enhancement; see 

introductory note 2f.

14 Master Account

There is no identified 

need for these qualifiers 

in this transaction 

segment.
Enclosure (5), ADC 435

Page 24

# Location DS 856S Ship Notice/Manifest Reason

2/DTM01/2000

2/N101/2200

DLMS Note:

1. Use to identify the SFIS data element “Main 

Account Code A3”.

2. Authorized DLMS enhancement; see 

introductory DLMS note 2f.

2P Subdivision Identifier

DLMS Note:

1. Use to identify the SFIS data element “Treasury 

Sub Class”

2. Authorized DLMS enhancement; see 

introductory DLMS note 2f.

11 Account Number

DLMS Note:

1. Use to identify the SFIS data element “Sub 

Account Code A4”

2. Authorized DLMS enhancement; see 

introductory DLMS note 2f.

1Z Financial Detail Code

1. Use to identify the data element “Subhead or 

Limit”

2. Authorized DLMS enhancement; see 

introductory DLMS note 2f.

283 Funds Appropriation Start

DLMS Note:

1. The date that the funds appropriation starts.

2. Required for SFIS to map to the appropriation 

start date for SFIS data element “Period of 

Availability Fiscal Year Date A8”.

3. Authorized DLMS enhancement; see 

introductory DLMS note 2f.

284 Funds Appropriation End

1. The date that the funds appropriation ends.

2. Required for SFIS to map to the appropriation end 

date for SFIS data element “Period of Availability 

Fiscal Year Date A8”.

3. Authorized DLMS enhancement; see 

introductory DLMS note 2f.

Revise to add new qualifiers and notes to existing 

qualifiers:

ZB Party to Receive Credit

DLMS Note:

1. Use to identify the party to receive credit for material 

transportation, and PC&H.

2. For conversion processing this will be the activity as 

identified by the Supplemental Address and the same 

activity identified to release the material

3. A DLMS enhancement allows specific separate 

identification of the party to receive credit and the 

party originating the LRO shipment/status/shipping 

the material. Refer to ADC 299. 

These qualifiers have 

been mapped to specific 

SFIS data elements
Enclosure (5), ADC 435

Page 25

# Location DS 856S Ship Notice/Manifest Reason

2/N103/2200

4. Use for SFIS compliant systems to identify the 

BPN of the party to receive credit. BPN may only 

be used when the corresponding DoDAAC is also 

provided. This will require a second iteration of 

the N1 loop with the same qualifier, if ZB was also 

used to identify the party to receive credit 

DoDAAC.

5. Authorized DLMS enhancement; see introductory 

DLMS note 2f.

50 Business License Number

DLMS Note:

1. Use for SFIS to map to SFIS Data element 

“Business Partner Number TP3”. Enter the 

seller’s BPN in N104.

2. Authorized DLMS enhancement; see 

introductory DLMS note 2f.

# Location 842 A/W Supply Discrepancy Report Reason

1. DLMS 

Introductory Notes

5. 6. This DLMS Supplement incorporates the Proposed DLMS 

Change and Approved DLMS Change (ADC) listed. PDC/ADCs are 

available from the DLA Logistics Management Standards Office

website: http://www.dla.mil/j6/dlmso/elibrary/Changes/processchanges.asp.

Add ADC 435

- ADC 435, DLMS Revisions for SFIS Compliance 

Identifies DLMS Changes 

included in the DLMS 

Supplement

2. DLMS 

Introductory Notes

5. This DLMS Supplement to the Federal 842A/W contains:

a. Data associated with a DLMS enhancement authorized for 

implementation by modernized systems under DLMS 

migration. This data (including expanded field sizes) should 

be adopted during, or subsequent, to modernization when 

applicable to the Component’s business process. Prior 

coordination is not required. Components should ensure that 

inclusion of this data in a DLMS transaction does not cause

inappropriate rejection of the transaction.

Identifies changes as 

authorized future 

enhancement

3. 2/REF04-01/700 Revise to delete the following qualifiers:

DP Department Number

DLMS Note:

1. Use to identify the SFIS data element 

“Department Regular Code A1”.

2. Authorized DLMS enhancement; see 

introductory note 5a.

93 Funds Authorization

DLMS Note:

1. Use to identify the SFIS data element 

“Department Transfer Code A2”.

2. Authorized DLMS enhancement; see 

introductory note 5a.

There is no identified 

need for these qualifiers 

in this transaction 

segment.
Enclosure (5), ADC 435

Page 26

# Location 842 A/W Supply Discrepancy Report Reason

2/DTM01/0600

2/N101/2800

14 Master Account Number

DLMS Note:

1. Use to identify the SFIS data element “Main 

Account Code A3”.

2. Authorized DLMS enhancement; see 

introductory note 5a.

2P Subdivision Identifier

DLMS Note:

1. Use to identify the SFIS data element “Treasury 

Sub Class”

2. Authorized DLMS enhancement; see 

introductory note 5a.

11 Account Number

DLMS Note:

1. Use to identify the SFIS data element “Sub 

Account Code A4”

2. Authorized DLMS enhancement; see 

introductory note 5a.

1Z Financial Detail Code

1. Use to identify the data element “Limit or 

Subhead

2. Authorized DLMS enhancement; see 

introductory note 5a.

283 Funds Appropriation Start

DLMS Note:

1. The date that the funds appropriation starts.

2. Required for SFIS to map to the appropriation 

start date for SFIS data element “Period of 

Availability Fiscal Year Date A8”.

3. Authorized DLMS enhancement; see 

introductory note 5a.

284 Funds Appropriation End

1. The date that the funds appropriation ends.

2. Required for SFIS to map to the appropriation 

end date for SFIS data element “Period of 

Availability Fiscal Year Date A8”.

3. Authorized DLMS enhancement; see 

introductory note 5a.

Revise to add new qualifiers and notes to existing 

qualifiers:

BT Bill-to Party

DLMS Note:

1. Use for SFIS compliant systems to identify the 

BPN of the party to receive the bill. BPN may 

only be used when the corresponding DoDAAC 

is also provided. This will require a second 

iteration of the N1 loop with the same qualifier.

2. Authorized DLMS enhancement; see 

These qualifiers have been 

mapped to specific SFIS 

data elements
Enclosure (5), ADC 435

Page 27

# Location 842 A/W Supply Discrepancy Report Reason

2/N103/2800

introductory note 5a.

ZB Party to Receive Credit

DLMS Note:

1. Use for SFIS compliant systems to identify the 

BPN of the party to receive credit. BPN may only 

be used when the corresponding DoDAAC is 

also provided. This will require a second 

iteration of the N1 loop with the same qualifier.

2. Authorized DLMS enhancement; see 

introductory note 5a.

50 Business License Number

DLMS Note:

1. Use for SFIS to map to SFIS Data element 

“Business Partner Number TP3”. Enter the 

buyer’s BPN in N104.

2. Authorized DLMS enhancement; see 

introductory note 5a.

# Location DS 810L Logistics Bill Reason

1. DLMS 

Introductory 

Notes

Add ADC 435

- ADC 435, DLMS Revisions for SFIS Compliance 

Identifies DLMS 

Changes included in the 

DLMS Supplement

2 DLMS 

Introductory 

Notes

6. This DLMS Supplement to the Federal 842A/W contains:

e. Data associated with a DLMS enhancement authorized for 

implementation by modernized systems under DLMS migration. 

This data (including expanded field sizes) should be adopted 

during, or subsequent, to modernization when applicable to the 

Component’s business process. Prior coordination is not required. 

Components should ensure that inclusion of this data in a DLMS

transaction does not cause inappropriate rejection of the 

transaction.

Identifies changes as 

authorized future 

enhancement

3. 1/N101/070

1/N103/070

Revise to add new qualifiers

II Issuer of Invoice

DLMS Note:

1. Must use to identify the billing office.

2. Use for SFIS compliant systems to identify the billing 

party’s BPN. BPN may only be used when the 

corresponding DoDAAC is also provided. This will require 

a second iteration of the N1 loop with the same qualifier,

as II must be used to identify the billing office DoDAAC.

This second iteration is an authorized DLMS enhancement; 

see introductory DLMS note 6e.

50 Business License Number

DLMS Note:

1. Use for SFIS to map to SFIS Data element “Business 

Partner Number TP3”. Enter the buyer’s BPN in N104.

2. Authorized DLMS enhancement; see introductory DLMS 

note 6e.

These qualifiers have 

been mapped to specific 

SFIS data elements
Enclosure (5), ADC 435

Page 28

# Location 517G Government Furnished Material (GFM) Validation Reason

1. DLMS 

Introductory 

Notes

Add ADC 435

- ADC 435, DLMS Revisions for SFIS Compliance 

Identifies DLMS 

Changes included in the 

DLMS Supplement

2. 2/FA201/136 Revise to delete the following qualifiers:

18 Funds Appropriation

DLMS Note:

Use to indicate the basic appropriation number.

A1 Department Indicator

A2 Transfer from Department

A3 Fiscal Year Indicator

A4 Basic Symbol Number

A5 Sub-class

A6 Sub-Account SymbolB1 Budget Activity Number

B2 Budget Sub-activity Number

BL Billings

Federal Note:

Use to indicate the Government IMPAC card number under which 

payment for this obligation will be accomplished.

C1 Program Element

C2 Project Task or Budget Subline

C3 Budget Restriction

D1 Defense Agency Allocation Recipient

D2 Defense Agency Sub-allocation Recipient

D3 Component Allocation Recipient

D4 Component Sub-allocation Recipient

D5 Allotment Recipient

D6 Sub-allotment Recipient

D7 Work Center Recipient

E1 Major Reimbursement Source Code

E2 Detail Reimbursement Source Code

E3 Customer Indicator

F1 Object Class

There is no identified 

need for these qualifiers 

in this transaction 

segment.
Enclosure (5), ADC 435

Page 29

# Location 517G Government Furnished Material (GFM) Validation Reason

F2 Object Sub-class

F3 Government or Public Sector Identifier

F4 Country Code

G1 Program or Planning Code

G2 Special Interest Code or Special Program Cost Code

H1 Cost Code

H2 Labor Type Code

H3 Cost Allocation Code

H4 Classification Code

J1 Document or Record Reference Number

N1 Transaction Type

P1 Disbursing Station Number

P2 International Balance of Payments (IBOP) Code

P3 Voucher Number

ZZ Mutually Defined

DLMS Note:

Cite supplemental accounting classification data.

# Location 527D Due in/Advance Receipt/Due Verification Reason

1. DLMS 

Introductory 

Notes

Add ADC 435

- ADC 435, DLMS Revisions for SFIS Compliance 

Identifies DLMS 

Changes included in the 

DLMS Supplement

2. 2/FA201/346 Revise to delete the following qualifiers:

18 Funds Appropriation

DLMS Note:

Use to indicate the basic appropriation number.

A1 Department Indicator

A2 Transfer from Department

A3 Fiscal Year Indicator

A4 Basic Symbol Number

A5 Sub-class

A6 Sub-Account Symbol

B1 Budget Activity Number

B2 Budget Sub-activity Number

BL Billings

Federal Note:

There is no identified 

need for these qualifiers 

in this transaction 

segment.
Enclosure (5), ADC 435

Page 30

# Location 527D Due in/Advance Receipt/Due Verification Reason

Use to indicate the Government IMPAC card number under which 

payment for this obligation will be accomplished.

C1 Program Element

C2 Project Task or Budget Subline

C3 Budget Restriction

D1 Defense Agency Allocation Recipient

D2 Defense Agency Sub-allocation Recipient

D3 Component Allocation Recipient

D4 Component Sub-allocation Recipient

D5 Allotment Recipient

D6 Sub-allotment Recipient

D7 Work Center Recipient

E1 Major Reimbursement Source Code

E2 Detail Reimbursement Source Code

E3 Customer Indicator

F1 Object Class

F2 Object Sub-class

F3 Government or Public Sector Identifier

F4 Country Code

G1 Program or Planning Code

G2 Special Interest Code or Special Program Cost Code

H1 Cost Code

H2 Labor Type Code

H3 Cost Allocation Code

H4 Classification Code

J1 Document or Record Reference Number

N1 Transaction Type

P1 Disbursing Station Number

P2 International Balance of Payments (IBOP) Code

P3 Voucher Number

ZZ Mutually Defined

DLMS Note:

Cite supplemental accounting classification data.
Enclosure (5), ADC 435

Page 31

# Location 527R Receipt, Inquiry, Response and MRA Reason

1. DLMS 

Introductory 

Notes

Add ADC 435

- ADC 435, DLMS Revisions for SFIS Compliance 

Identifies DLMS 

Changes included in the 

DLMS Supplement

2. 2/FA201/346 Revise to delete the following qualifiers:

A1 Department Indicator

A2 Transfer from Department

A3 Fiscal Year Indicator

A4 Basic Symbol Number

A5 Sub-class

A6 Sub-Account Symbol

B1 Budget Activity Number

B2 Budget Sub-activity Number

BL Billings

Federal Note:

Use to indicate the Government IMPAC card number under which 

payment for this obligation will be accomplished.

C1 Program Element

C2 Project Task or Budget Subline

C3 Budget Restriction

D1 Defense Agency Allocation Recipient

D2 Defense Agency Sub-allocation Recipient

D3 Component Allocation Recipient

D4 Component Sub-allocation Recipient

D5 Allotment Recipient

D6 Sub-allotment Recipient

D7 Work Center Recipient

E1 Major Reimbursement Source Code

E2 Detail Reimbursement Source Code

E3 Customer Indicator

F1 Object Class

F2 Object Sub-class

F3 Government or Public Sector Identifier

There is no identified 

need for these qualifiers 

in this transaction 

segment.
Enclosure (5), ADC 435

Page 32

# Location 527R Receipt, Inquiry, Response and MRA Reason

F4 Country Code

G1 Program or Planning Code

G2 Special Interest Code or Special Program Cost Code

H1 Cost Code

H2 Labor Type Code

H3 Cost Allocation Code

H4 Classification Code

J1 Document or Record Reference Number

N1 Transaction Type

P1 Disbursing Station Number

P2 International Balance of Payments (IBOP) Code

P3 Voucher Number

ZZ Mutually Defined

DLMS Note:

Cite supplemental accounting classification data.

2/FA201/346 Remove DLMS note 1 from code B5

B5 Fund Code

DLMS Note:

1. Future streamlined data; see introductory DLMS note 5c.

12. May be used with nonprocurement source receipt transactions when 

applicable in accordance with

MILSTRAP- DLMS requirement.

23. DLA uses with AMMA procurement source receipt transactions when 

applicable. Refer to ADC 351.

No longer applicable

# Location 812L Logistics Bill Adjustment Request Reply Reason

1. DLMS 

Introductory 

Notes

Add ADC 435

- ADC 435, DLMS Revisions for SFIS Compliance 

Identifies DLMS 

Changes included in the 

DLMS Supplement

2. 2/FA201/170 Revise to delete the following qualifiers:

18 Funds Appropriation

DLMS Note:

Use to indicate the basic appropriation number (department code through 

appropriation limit).

Example: 1717979818100400.

A1 Department Indicator

A2 Transfer from Department

A3 Fiscal Year Indicator

A4 Basic Symbol Number

There is no identified 

need for these qualifiers 

in this transaction 

segment.
Enclosure (5), ADC 435

Page 33

# Location 812L Logistics Bill Adjustment Request Reply Reason

A5 Sub-class

A6 Sub-Account Symbol

B1 Budget Activity Number

B2 Budget Sub-activity Number

BL Billings

Federal Note:

Use to indicate the Government IMPAC card number under which 

payment for this obligation will be accomplished.

C1 Program Element

C2 Project Task or Budget Subline

C3 Budget Restriction

D1 Defense Agency Allocation Recipient

D2 Defense Agency Sub-allocation Recipient

D3 Component Allocation Recipient

D4 Component Sub-allocation Recipient

D5 Allotment Recipient

D6 Sub-allotment Recipient

D7 Work Center Recipient

E1 Major Reimbursement Source Code

E2 Detail Reimbursement Source Code

E3 Customer Indicator

F1 Object Class

F2 Object Sub-class

F3 Government or Public Sector Identifier

F4 Country Code

G1 Program or Planning Code

G2 Special Interest Code or Special Program Cost Code

H1 Cost Code

H2 Labor Type Code

H3 Cost Allocation Code

H4 Classification Code

J1 Document or Record Reference Number

N1 Transaction Type
Enclosure (5), ADC 435

Page 34

# Location 812L Logistics Bill Adjustment Request Reply Reason

P1 Disbursing Station Number

P2 International Balance of Payments (IBOP) Code

P3 Voucher Number

ZZ Mutually Defined

DLMS Note:

Cite supplemental accounting classification data.

# Location 812R Logistics Bill Adjustment Request Reason

1. DLMS 

Introductory 

Notes

Add ADC 435

- ADC 435, DLMS Revisions for SFIS Compliance 

Identifies DLMS 

Changes included in the 

DLMS Supplement

2. 2/FA201/170 Revise to delete the following qualifiers:

18 Funds Appropriation

DLMS Note:

Use to indicate the basic appropriation number (department code through

appropriation limit). Example: 1717979818100400.

A1 Department Indicator

A2 Transfer from Department

A3 Fiscal Year Indicator

A4 Basic Symbol Number

A5 Sub-class

A6 Sub-Account Symbol

B1 Budget Activity Number

B2 Budget Sub-activity Number

BL Billings

Federal Note:

Use to indicate the Government IMPAC card number under which 

payment for this obligation will be accomplished.

C1 Program Element

C2 Project Task or Budget Subline

C3 Budget Restriction

D1 Defense Agency Allocation Recipient

D2 Defense Agency Sub-allocation Recipient

D3 Component Allocation Recipient

D4 Component Sub-allocation Recipient

There is no identified 

need for these qualifiers 

in this transaction 

segment.
Enclosure (5), ADC 435

Page 35

# Location 812R Logistics Bill Adjustment Request Reason

D5 Allotment Recipient

D6 Sub-allotment Recipient

D7 Work Center Recipient

E1 Major Reimbursement Source Code

E2 Detail Reimbursement Source Code

E3 Customer Indicator

F1 Object Class

F2 Object Sub-class

F3 Government or Public Sector Identifier

F4 Country Code

G1 Program or Planning Code

G2 Special Interest Code or Special Program Cost Code

H1 Cost Code

H2 Labor Type Code

H3 Cost Allocation Code

H4 Classification Code

J1 Document or Record Reference Number

N1 Transaction Type

P1 Disbursing Station Number

P2 International Balance of Payments (IBOP) Code

P3 Voucher Number

ZZ Mutually Defined

DLMS Note:

Cite supplemental accounting classification data.

# Location 842A/R Standard Supply Discrepancy Report Reply Reason

1. DLMS 

Introductory 

Notes

Add ADC 435

- ADC 435, DLMS Revisions for SFIS Compliance 

Identifies DLMS 

Changes included in the 

DLMS Supplement

2. 2/FA201/4670 Revise to delete the following qualifiers:

18 Funds Appropriation

DLMS Note:

Use to identify the basic appropriation number.

A1 Department Indicator

A2 Transfer from Department

There is no identified 

need for these qualifiers 

in this transaction 

segment.
Enclosure (5), ADC 435

Page 36

# Location 842A/R Standard Supply Discrepancy Report Reply Reason

A3 Fiscal Year Indicator

A4 Basic Symbol Number

A5 Sub-class

A6 Sub-Account Symbol

B1 Budget Activity Number

B2 Budget Sub-activity Number

BL Billings

Federal Note:

Use to indicate the Government IMPAC card number under which 

payment for this obligation will be accomplished.

C1 Program Element

C2 Project Task or Budget Subline

C3 Budget Restriction

D1 Defense Agency Allocation Recipient

D2 Defense Agency Sub-allocation Recipient

D3 Component Allocation Recipient

D4 Component Sub-allocation Recipient

D5 Allotment Recipient

D6 Sub-allotment Recipient

D7 Work Center Recipient

E1 Major Reimbursement Source Code

E2 Detail Reimbursement Source Code

E3 Customer Indicator

F1 Object Class

F2 Object Sub-class

F3 Government or Public Sector Identifier

F4 Country Code

G1 Program or Planning Code

G2 Special Interest Code or Special Program Cost Code

H1 Cost Code

H2 Labor Type Code

H3 Cost Allocation Code

H4 Classification Code
Enclosure (5), ADC 435

Page 37

# Location 842A/R Standard Supply Discrepancy Report Reply Reason

J1 Document or Record Reference Number

N1 Transaction Type

P1 Disbursing Station Number

P2 International Balance of Payments (IBOP) Code

P3 Voucher Number

ZZ Mutually Defined

DLMS Note:

Cite supplemental accounting classification data.

# Location 867D Demand Reporting Reason

1. DLMS 

Introductory 

Notes

Add ADC 435

- ADC 435, DLMS Revisions for SFIS Compliance 

Identifies DLMS 

Changes included in the 

DLMS Supplement

2. 2/FA201/350 Revise to delete the following qualifiers:

18 Funds Appropriation

DLMS Note:

Use to indicate the basic appropriation number.

A1 Department Indicator

A2 Transfer from Department

A3 Fiscal Year Indicator

A4 Basic Symbol Number

A5 Sub-class

A6 Sub-Account Symbol

B1 Budget Activity Number

B2 Budget Sub-activity Number

BL Billings

Federal Note:

Use to indicate the Government IMPAC card number under which 

payment for this obligation will be accomplished.

C1 Program Element

C2 Project Task or Budget Subline

C3 Budget Restriction

D1 Defense Agency Allocation Recipient

D2 Defense Agency Sub-allocation Recipient

D3 Component Allocation Recipient

D4 Component Sub-allocation Recipient

D5 Allotment Recipient

There is no identified 

need for these qualifiers 

in this transaction 

segment.
Enclosure (5), ADC 435

Page 38

# Location 867D Demand Reporting Reason

D6 Sub-allotment Recipient

D7 Work Center Recipient

E1 Major Reimbursement Source Code

E2 Detail Reimbursement Source Code

E3 Customer Indicator

F1 Object Class

F2 Object Sub-class

F3 Government or Public Sector Identifier

F4 Country Code

G1 Program or Planning Code

G2 Special Interest Code or Special Program Cost Code

H1 Cost Code

H2 Labor Type Code

H3 Cost Allocation Code

H4 Classification Code

J1 Document or Record Reference Number

N1 Transaction Type

P1 Disbursing Station Number

P2 International Balance of Payments (IBOP) Code

P3 Voucher Number

ZZ Mutually Defined

DLMS Note:

Cite supplemental accounting classification data.

# Location 869A Requisition Inquiry/Supply Assistance Request Reason

1. DLMS 

Introductory 

Notes

Add ADC 435

- ADC 435, DLMS Revisions for SFIS Compliance 

Identifies DLMS 

Changes included in the 

DLMS Supplement

2. 2/FA201/200 Revise to delete the following qualifiers:

18 Funds Appropriation

DLMS Note:

Use to indicate the basic appropriation number.

A1 Department Indicator

A2 Transfer from Department

A3 Fiscal Year Indicator

There is no identified 

need for these qualifiers 

in this transaction 

segment.
Enclosure (5), ADC 435

Page 39

# Location 869A Requisition Inquiry/Supply Assistance Request Reason

A4 Basic Symbol Number

A5 Sub-class

A6 Sub-Account Symbol

B1 Budget Activity Number

B2 Budget Sub-activity Number

BL Billings

Federal Note:

Use to indicate the Government IMPAC card number under which 

payment for this obligation will be accomplished.

C1 Program Element

C2 Project Task or Budget Subline

C3 Budget Restriction

D1 Defense Agency Allocation Recipient

D2 Defense Agency Sub-allocation Recipient

D3 Component Allocation Recipient

D4 Component Sub-allocation Recipient

D5 Allotment Recipient

D6 Sub-allotment Recipient

D7 Work Center Recipient

E1 Major Reimbursement Source Code

E2 Detail Reimbursement Source Code

E3 Customer Indicator

F1 Object Class

F2 Object Sub-class

F3 Government or Public Sector Identifier

F4 Country Code

G1 Program or Planning Code

G2 Special Interest Code or Special Program Cost Code

H1 Cost Code

H2 Labor Type Code

H3 Cost Allocation Code

H4 Classification Code

J1 Document or Record Reference Number
Enclosure (5), ADC 435

Page 40

# Location 869A Requisition Inquiry/Supply Assistance Request Reason

N1 Transaction Type

P1 Disbursing Station Number

P2 International Balance of Payments (IBOP) Code

P3 Voucher Number

ZZ Mutually Defined

DLMS Note:

Cite supplemental accounting classification data.

# Location 869C Requisition Cancellation Reason

1. DLMS 

Introductory 

Notes

Add ADC 435

- ADC 435, DLMS Revisions for SFIS Compliance 

Identifies DLMS 

Changes included in the 

DLMS Supplement

2. 2/FA201/200 Revise to delete the following qualifiers:

18 Funds Appropriation

DLMS Note:

Use to indicate the basic appropriation number.

A1 Department Indicator

A2 Transfer from Department

A3 Fiscal Year Indicator

A4 Basic Symbol Number

A5 Sub-class

A6 Sub-Account Symbol

B1 Budget Activity Number

B2 Budget Sub-activity Number

BL Billings

Federal Note:

Use to indicate the Government IMPAC card number under which 

payment for this obligation will be accomplished.

C1 Program Element

C2 Project Task or Budget Subline

C3 Budget Restriction

D1 Defense Agency Allocation Recipient

D2 Defense Agency Sub-allocation Recipient

D3 Component Allocation Recipient

D4 Component Sub-allocation Recipient

D5 Allotment Recipient

There is no identified 

need for these qualifiers 

in this transaction 

segment.
Enclosure (5), ADC 435

Page 41

# Location 869C Requisition Cancellation Reason

D6 Sub-allotment Recipient

D7 Work Center Recipient

E1 Major Reimbursement Source Code

E2 Detail Reimbursement Source Code

E3 Customer Indicator

F1 Object Class

F2 Object Sub-class

F3 Government or Public Sector Identifier

F4 Country Code

G1 Program or Planning Code

G2 Special Interest Code or Special Program Cost Code

H1 Cost Code

H2 Labor Type Code

H3 Cost Allocation Code

H4 Classification Code

J1 Document or Record Reference Number

N1 Transaction Type

P1 Disbursing Station Number

P2 International Balance of Payments (IBOP) Code

P3 Voucher Number

ZZ Mutually Defined

DLMS Note:

Cite supplemental accounting classification data.

# Location 945A Material Release Advise Reason

1. DLMS 

Introductory 

Notes

Add ADC 435

- ADC 435, DLMS Revisions for SFIS Compliance 

Identifies DLMS 

Changes included in the 

DLMS Supplement

2. 2/FA201/180 Revise to delete the following qualifiers:

18 Funds Appropriation

DLMS Note:

Use to indicate the basic appropriation number.

A1 Department Indicator

A2 Transfer from Department

A3 Fiscal Year Indicator

There is no identified 

need for these qualifiers 

in this transaction 

segment.
Enclosure (5), ADC 435

Page 42

# Location 945A Material Release Advise Reason

A4 Basic Symbol Number

A5 Sub-class

A6 Sub-Account Symbol

B1 Budget Activity Number

B2 Budget Sub-activity Number

BL Billings

Federal Note:

Use to indicate the Government IMPAC card number under which 

payment for this obligation will be accomplished.

C1 Program Element

C2 Project Task or Budget Subline

C3 Budget Restriction

D1 Defense Agency Allocation Recipient

D2 Defense Agency Sub-allocation Recipient

D3 Component Allocation Recipient

D4 Component Sub-allocation Recipient

D5 Allotment Recipient

D6 Sub-allotment Recipient

D7 Work Center Recipient

E1 Major Reimbursement Source Code

E2 Detail Reimbursement Source Code

E3 Customer Indicator

F1 Object Class

F2 Object Sub-class

F3 Government or Public Sector Identifier

F4 Country Code

G1 Program or Planning Code

G2 Special Interest Code or Special Program Cost Code

H1 Cost Code

H2 Labor Type Code

H3 Cost Allocation Code

H4 Classification Code

J1 Document or Record Reference Number
Enclosure (5), ADC 435

Page 43

# Location 945A Material Release Advise Reason

N1 Transaction Type

P1 Disbursing Station Number

P2 International Balance of Payments (IBOP) Code

P3 Voucher Number

ZZ Mutually Defined

DLMS Note:

Cite supplemental accounting classification data.

# Location 947I Inventory Adjustment (Applies to 4010 as well) Reason

1. DLMS 

Introductory 

Notes

Add ADC 435

- ADC 435, DLMS Revisions for SFIS Compliance 

Identifies DLMS 

Changes included in the 

DLMS Supplement

2. 2/FA201/206

0

Revise to delete the following qualifiers:

18 Funds Appropriation

DLMS Note:

Use to indicate the basic appropriation number.

A1 Department Indicator

A2 Transfer from Department

A3 Fiscal Year Indicator

A4 Basic Symbol Number

B1 Budget Activity Number

B2 Budget Sub-activity Number

BL Billings

Federal Note:

Use to indicate the Government IMPAC card number under which 

payment for this obligation will be accomplished.

C1 Program Element

C2 Project Task or Budget Subline

C3 Budget Restriction

D1 Defense Agency Allocation Recipient

D2 Defense Agency Sub-allocation Recipient

D3 Component Allocation Recipient

D4 Component Sub-allocation Recipient

D5 Allotment Recipient

D6 Sub-allotment Recipient

D7 Work Center Recipient

E1 Major Reimbursement Source Code

There is no identified 

need for these qualifiers 

in this transaction 

segment.
Enclosure (5), ADC 435

Page 44

# Location 947I Inventory Adjustment (Applies to 4010 as well) Reason

E2 Detail Reimbursement Source Code

E3 Customer Indicator

F1 Object Class

F2 Object Sub-class

F3 Government or Public Sector Identifier

F4 Country Code

G1 Program or Planning Code

G2 Special Interest Code or Special Program Cost Code

H1 Cost Code

H2 Labor Type Code

H3 Cost Allocation Code

H4 Classification Code

J1 Document or Record Reference Number

N1 Transaction Type

P1 Disbursing Station Number

P2 International Balance of Payments (IBOP) Code

P3 Voucher Number

ZZ Mutually Defined

DLMS Note:

Cite supplemental accounting classification data.

2/FA201/206

0

Remove DLMS note from code B5

B5 Fund Code

DLMS Note:

Future Streamlined data; see introductory DLMS note 4c.

No longer applicable
Enclosure (6), ADC 435

Page 1

ENCLOSURE 6

BTA CONCEPT FOR BUSINESS COST OBJECT

1. DoD End to End Process: Budget to Report (B2R). The DoD End-To-End (E2E) Business 

Flows are business processes that span Core Business Missions. The addition of E2E Business 

Flows enables the Business Enterprise Architecture to better support the Business Mission 

Area's move from a function-centered approach to one that looks at DoD business functions 

across the enterprise from an end-to-end process perspective.2

2. DoD Budget to Report (B2R) End to End (E2E) Process

Budget to Report encompasses 

all business functions necessary to plan, formulate, create, execute against and report on the 

budget and business activities of the entity. BTA proposed that this include updates to the 

general ledger, which is outside the scope of this ADC.

a. Appropriation Master Data Set Up in the Targeted AIS ERP Systems. In the Target 

AIS ERP systems, Appropriation master data, usually on an annual basis or if necessary as 

needed, are assigned to various Cost Objects by the Budget Officers (resource managers) 

within the DoD Components. Cost Objects (SFIS data elements) are defined as Cost 

Centers, Project Identifiers (WBS Elements, Networks or Projects) or Activity Identifiers 

(Work Orders). The Budget Officer defines what SFIS data elements (fund, fund center, 

functional area, funded program and commitment item) will be derived for each Cost 

Object. 

3. Concept of Operations

a. The proposed concept is for the Modern ERPs and Target AISs to maintain the Financial 

Master Data from the Budget to Report Process (annually or updated as needed), and for the 

warfighter to provide the Cost Object, NSN, Document # (DODAAC), and other required 

system data for Requisitioning. BTA proposed General Ledger posting be derived from 

this process, which is outside the scope of the DLMS process. As part of the AIS/ERP 

system configuration during the Budget to Report Process, the Budget Officer defines what 

SFIS data elements (fund, fund center, functional area, funded program and commitment 

item) that will be derived for each Cost Object 

b. The buyer (warfigher) needs to know who he is (his internal ID), his (DoDAAC) , what he 

is doing (Cost Object) and other applicable information to be defined (such bill-to activity, 

ship-to activity). The Cost Object is defined as one of the following SFIS data elements:

• Cost Center Identifier

• Project Identifier

• Activity Identifier

• Work Order #

c. From this information the Proposed SFIS data elements would be derived by the target 

ERP/AIS Financial Master Data that is part of the Budget to Report process highlighted 

above. BTA proposed General Ledger posting be derived from this process, which is 

outside the scope of the DLMS process. In the Target Environment, when ERP to ERP 

 2

 http://www.bta.mil/products/bea_7_0/BEA/html_files/end2end.html
Enclosure (6), ADC 435

Page 2

configuration is achieved, this eliminates the need for the ERP/AIS systems to create an 

outside interface with a referential table for Appropriation and SFIS data elements for each 

logistic transaction. Data derived from the Cost object:

 Department Regular Code

 Department Transfer Code

 Period of Availability Fiscal Year Date

 Main Account Code 

 Sub-Account Code

 Treasury Sub Class

 Business Partner Number 

 Budget Line Item Identifier 

 Funding Center Identifier

 Agency Accounting Identifier

 Limit/Subhead

d. BTA has outlined this approach and expressed BTA opinions in briefing Standard Financial 

Information Structure (SFIS) Proposed DLMS Change at (https://www.dla.mil/j6/dlmso/archives/finance/documents/SFIS_Finance_DLMS_Change_TARGET.pdf).

e. The BTA SFIS Matrix located at (https://www.dla.mil/j6/dlmso/archives/finance/documents/SFIS_Matrix_BEA7.0_DLMS.xls) is to be used as a 

referenced is sorted by the proposed data elements to include on DLMS Requisitions and 

Logistics Bills.

f. BTA has provided the briefing “SFIS in the Target Environment Financial Data in Supply” 

at (https://www.dla.mil/j6/dlmso/archives/finance/documents/SFIS_DLMS_Financial_Data_in_Supply_Demo_FIN

AL.pdf) is for the SAP Center of Excellence (COE) demonstration the BTA conducted in 

January 2010 and outlines the benefits of using the ERP inherent capability for managing 

Financial Master Data. 

g. BTA has provided the chart BTA-COE E2E Process Walk-thru for O2Cand P2P with B3R 

integration at (https://www.dla.mil/j-6/dlmso/archives/finance/documents/SFIS_BTA-COEFDIS-Demo-v1.jpg).
Enclosure (7), ADC 435

Page 1

ENCLOSURE 7

Coordination Comment Disposition

# Component/

Agency

Response/Comment Disposition

2 Army Army's preferred approach is option 2 of 

DLMS’ proposed approaches because 

option 2 (Using referential data exchange 

as the primary method for acquiring SFIS 

data element) will be less costly and 

disruptive because many ERPs have 

already programmed to the current 

business model. Option 2 also 

acknowledges that fact that Interfund is a 

mixed environment of logistics and 

finance. Option 1 (Carry all SFIS in 

DLMS as discrete data elements) would 

make translation in a mixed environment 

more complex and costly to implement.

Noted. Referential data exchange is 

approved for the DoD Logistics 

Enterprise.

3 DMLSS

(Army)

(Section 6.c, paragraph 1, Staffing Note) 

DMLSS Response: Transactions listed 

are currently utilized by DMLSS and no 

corrections are noted at this time.

Noted.

4 DMLSS

(Army)

(Section 6.c.7.i, paragraph 1, Staffing 

Note) 

DMLSS Response: Currently DMLSS 

does not use this transaction set and there 

are no plans to use it the future.

Noted.

5 DMLSS

(Army)

(Section 6.d, paragraph 1, Staffing Note) 

DMLSS Response: DMLSS is a medical 

logistics system that serves as a financial 

feeder system and does not process 

logistics bills. However DMLSS does 

currently maintain SFIS elements in 

order to interface with the General Fund 

Enterprise Business System (GFEBS).

Noted.
Enclosure (7), ADC 435

Page 2

# Component/

Agency

Response/Comment Disposition

6 DMLSS

(Army)

(Section 6.g, paragraph 1, Staffing Note) 

DMLSS Response: DMLSS does 

currently maintain the identified SFIS 

elements in order to interface with the 

General Fund Enterprise Business 

System (GFEBS) for financial utilization 

but it does not function as a seller in 

processing of a logistics bill.

Noted.

7 DMLSS

(Army)

(Section 6.h, paragraph 1, Staffing Note) 

DMLSS Response: DMLSS utilizes the 

below transactions and will not remove 

the fund code or modify the transactions 

unless instructed by BTA/DLA:

527R Receipt, Inquiry, Response and 

MRA 

812L Logistics Bill Adjustment Request 

Reply 

856R Shipment Status Material Returns

869A Requisition Inquiry/Supply 

Assistance Request 

869C Requisition Cancellation 

870S Supply Status

945A Material Release Advice

947I Inventory Adjustment

Noted. Noted. Fund Code is not being 

removed from these transactions.

8 DMLSS(Army) (Section 10, paragraph 1) DMLSS 

Response: DMLSS currently maintains 

SFIS full operation capability as of 1 Jan 

2010 for financial interfacing. Funding 

has been tentatively identified for 

possible implementation of the SFIS 

elements into the logistics EDI 

transactions in FY12 if directed by 

BTA/DLA. DMLSS will have to 

coordinate the implementation of the 

SFIS elements into the logistics EDI 

transactions with DLA Troop Support –

Medical Supply Chain.

Noted. BPN is being added to DLMS.

9 DMLSS

(Army)

(Section 11, paragraph 1) 

DMLSS Response: None at this time.

Noted.
Enclosure (7), ADC 435

Page 3

# Component/

Agency

Response/Comment Disposition

10 DMLSS

(Army)

(Section 12.a, paragraph 1) 

DMLSS Response: Sufficient time and 

closely coordinated scheduling to ensure 

interfaces will function correctly is 

critical. If DMLSS cannot coordinate 

with the systems it feeds to accept the 

SFIS elements within the logistic 

transaction it will greatly impact the 

ability of customers to order non-TVR 

type items.

Noted. BPN is the only data element 

being added to DLMS. It is an 

authorized enhancement (see notes to 

DLMS Supplements). DLMS capable 

systems will migrate over time to 

accept BPN.

11 DFAS Summary Comments and 

Recommendations

12 DFAS 1.1 DFAS supports the promulgation of 

SFIS in Department of Defense systems 

to improve the reporting architecture. 

Noted.

13 DFAS 1.2 DFAS agrees with DLA that the 

current and future Interfund process is a 

mixed environment of DLMS and MILs 

until FY 2017. 

MILS will be supported until no longer 

needed.

14 DFAS 1.3 DFAS has reviewed the PDC and 

concluded that:

15 DFAS 1.3.1 PDC does not explicitly lay out 

basic assumptions and the basis for these 

assumptions;

16 DFAS 1.3.1.1 PDC assumes that Components 

will process detailed Interfund 

transactions to Treasury directly, bipassing DFAS, however this is not 

stated.

This is not a part of this DLMS change.

17 DFAS 1.3.1.2 PDC assumes that target 

Interfund transactions will be processed 

to Treasury at detail, however this is not 

stated.

This is not a part of this DLMS change.

18 DFAS 1.3.2 PDC assumption that DFAS 

systems will not migrate to DLMS is no 

longer correct.

Noted. Removed statement from ADC.

19 DFAS 1.3.3 PDC does not crosswalk the 

Interfund business to SFIS data elements;

There are no changes to the Interfund 

process in this DLMS change.

20 DFAS 1.3.4 PDC does not contain an AS IS 

and TO BE End-To-End flow showing 

edits and whether the TO BE process is 

still a summary to detail process;

Fund Code edits remain unchanged, as 

does the summary to detail billing 

process for Interfund billing. No 

change.
Enclosure (7), ADC 435

Page 4

# Component/

Agency

Response/Comment Disposition

21 DFAS 1.3.5 PDC does not contain specific 

reporting benefits from moving the 

Interfund business to SFIS compliance 

(e.g., benefit of adding BPN);

Noted. There are no current changes to 

the Interfund process in this DLMS 

change. BTA requested this change to 

support the Target To-Be Environment.

22 DFAS 1.3.6 PDC references other documents 

not presented within the PDC; and

This is standard practice and is required 

for readability/brevity. Links to 

referenced documents are provided 

where appropriate.

23 DFAS 1.3.7 Based on the PDC, the referential 

method (the second option) seems to be 

the least costly and disruptive.

Noted. Referential data is the approved 

approach.

24 DFAS 1.3.7.1 For example, many ERPs have 

already programmed to the current 

business model.

See above.

25 DFAS 1.4 DFAS recognizes that ERPs that 

have not migrated to DLMS (e.g., 

DEAMS) and have not programmed 

using the fund code and signal code may 

prefer option 1.

A single approach is being adopted for 

the DoD Logistics Enterprise. All 

Components have selected option 2 

(referential data exchange), for 

financial data elements, supporting the 

DFAS position that "the referential 

method seems to be the least costly and 

disruptive." Additional programming 

by DLMS compliant ERP systems to 

add discrete SFIS financial data 

elements beyond BPN is not required. 

In addition, MILS transactions will be 

supported until no longer needed.

26 DFAS 1.5 DFAS would prefer not to choose 

either option 1 or 2 at this time and 

recommends that PDC 365 be referred 

back to a broad workgroup that is 

chartered to:

DFAS concurs that below issues are 

resolved and that no new working 

group is needed. 

27 DFAS 1.5.1 Identify and document the mixed 

environment for target SFIS time frame 

and how the target time-frame relates to 

FY 2017;

There is no significance to FY 2017 

associated with this change. This 

relates to the current DFAS waiver for 

DLMS compliance. MILS will be 

supported until no longer needed.
Enclosure (7), ADC 435

Page 5

# Component/

Agency

Response/Comment Disposition

28 DFAS 1.5.2 Identify benefits to the current 

business of adding SFIS data elements;

BTA requested this change to support 

the Target To-Be Environment. This 

DLMS change states that, "The intent 

is to identify changes to DLMS now, so 

that DoD Component ERP and 

“Target” AIS can program for the 

exchange of these data elements and 

development of the infrastructure 

required to support financial processes 

in the future." 

29 DFAS 1.5.3 Crosswalk the Interfund business 

to SFIS and identify local data elements 

that will need to be perpetuated outside 

of SFIS;

There are no current changes to the 

Interfund process in this DLMS 

change.

30 DFAS 1.5.4 Develop an E2E flow of AS IS 

and TO BE;

BTA provided a notional E2EConcept 

of Operations process flow for the 

Target To-Be environment at enclosure 

(6) paragraph 3.g.

31 DFAS 1.5.6 Develop a business case for the 

implied proposal that DoD move the 

Interfund process from a summary 

process to a detail process; and

There is no change to the summary to 

detail billing process.

32 DFAS 1.5.6 Specifically address the mixed 

environment and the possibility of 

continued existence of several DFAS 

legacy systems in the FY 2017 

environment in its solution.

MILS will be supported until no longer 

needed. The approved Referential Data 

approach facilitates exchange of SFIS 

financial accounting data elements with 

systems that are not DLMS capable.

33 DFAS 1.6 However, to be responsive to the 

DLA request that DFAS choose an 

option, DFAS recommends a hybrid 

answer that allows SFIS and DLMS 

compliant ERP systems to process in 

SFIS (Option 1), while providing MILS 

and non-SFIS bill processing systems 

with a referential data exchange (Option 

2) to translate back to non-SFIS. This 

hybrid recommendation is based on the 

premise that Interfund is a mixed 

logistics and finance environment and 

some form of option 2 will be necessary 

for the next 6-10 years at least where 

DFAS is concerned.

The single approach of Referential 

Data is adopted for the DoD Logistics 

enterprise, which all Components have 

selected. DFAS recognizes that “the 

referential method seems to be the least 

costly and disruptive" and defers.

34 DFAS 1.7 Detailed Comments
Enclosure (7), ADC 435

Page 6

# Component/

Agency

Response/Comment Disposition

35 DFAS 1.7.1 Preliminary SFIS research 

indicates that by adding SFIS data to the 

transaction, no new information will be 

added to the business except possibly for 

the BPN. For most business within DoD, 

the BPN is equivalent to the already 

existing DoDAAC. However, for GSA, 

the BPN might add something to the 

process. Additional research on benefits 

is needed.

Noted. BTA identified BPN as an 

SFIS data element for the Target To-Be 

Environment. It is being added to 

DLMS as an authorized enhancement. 

GSA is working the BPN issue with the 

Federal Agencies.

36 DFAS 1.7.2 DFAS would like clarification on 

what codes would still be available in the 

Target Environment understanding that 

Interfund is a mixed logistics and finance 

environment that may have non-SFIS 

logistics data elements.

Signal code, fund code and bill-to 

DoDAAC will be available in the target 

environment. There is no change to 

currently used logistics/financial date 

elements.

37 DFAS 1.7.2.1 Will non-SFIS business unique 

codes like the Signal Code and Bill To 

DODAAC remain in the target 

environment?

Signal code, fund code and bill-to 

DoDAAC will be available in the target 

environment.

38 DFAS 1.7.3 PDC asserts that the seller’s will 

send bills to Treasury directly.

See below. 

39 DFAS 1.7.3.1 DFAS is not aware of any plans 

to remove DFAS from the Interfund 

Treasury reporting business process. 

PDC should clarify authoritative source 

for this assertion.

BTA assumption stated in 5.a is:" In 

the target environment for this change, 

it is assumed that DFAS legacy 

systems will be retired and that ERPs 

will be used for bill processing in the 

target environment". This DLMS 

change is neutral on that assumption. It 

is included for background as the BTA 

vision of the Target To-Be 

Environment.

40 DFAS 1.7.4 PDC 365 would remove DCAS 

from the reporting chain for Interfund 

billing transactions executed by ERPs. If 

a business case can be made that it is 

more cost-effective to report the 

transactions to Treasury on that basis, 

there would need to be changes made to 

DCAS to turn off the flow of Interfund 

summary billing records into the DCAS 

reporting component and to revise DCAS 

reporting products, most notably, the 

Treasury SF-1219/1220 consolidated 

statement, to exclude Interfund. 

This DLMS change does not remove 

DCAS from the reporting chain nor 

does it alter Interfund billing. See 

above.
Enclosure (7), ADC 435

Page 7

# Component/

Agency

Response/Comment Disposition

41 DFAS 1.7.4.1 The PDC needs to show that 

elimination of DCAS from the reporting 

chain for these transactions will not 

eliminate the possibility that DCAS may 

need to continue to capture such 

transactions for cash reconciliation 

purposes.

See above.

42 DFAS 1.7.5 Feeder systems for Interfund 

include FAVORS, STORES, and 

Warfighter

Noted.

43 DFAS 1.7.6 If signal code is excluded in the 

target environment, DFAS would not be 

able to determine who is to be billed or 

who ordered the items if there is a third 

party involved.

Signal Code is being retained.

44 DFAS 1.8 Detailed Concerns

45 DFAS 1.8.1 Mature ERPs have already 

programmed their Interfund requisitions 

to use Fund Code, Signal Code and Bill 

to DODAAC. Changes would come with 

a cost to the more mature ERPs.

Fund Code, Signal Code, and Bill-to 

DoDAAC are being retained. 

46 DFAS 1.8.2 DFAS is concerned that the 

Interfund business process is based on 

“non-SFIS” fund code, signal code and 

bill to DODAAC, but PDC does not 

address specifically what will happen to 

these critical edits. 

Fund Code, Signal Code, and Bill-to 

DoDAAC are being retained. 

47 DFAS 1.8.2.1 There are approx. 1M lines/56K 

Summary Bills billed Interfund per 

month out of EBS. DFAS is concerned 

that the information that will be 

contained in SFIS will not be enough 

information to process these transactions. 

The data elements that are of great 

concern are the Fund Code, Signal Code, 

and the payer/bill to DoDAAC that 

match with the LOA. Without this 

information Interfund transactions will 

not process correctly or not at all.

Fund Code, Signal Code, and Bill-to 

DoDAAC are being retained. 
Enclosure (7), ADC 435

Page 8

# Component/

Agency

Response/Comment Disposition

48 DFAS 1.8.3 DFAS is not aware of an 

authority memo or guidance tying DLMS 

migration to SFIS. Accordingly, DFAS 

does not agree with the PDC assertion 

that automated information system’s that 

undergo modernization (e.g., migrating 

to DLMS) will need to be configured to 

carry SFIS data elements.

There is no authority linking DLMS 

migration to SFIS compliance. 

However, BPN has been approved as a 

DLMS data element (authorized 

enhancement). DLMS capable systems 

will need to be configured to process 

that data element.

49 DFAS 1.8.3.1 DFAS has until FY 2017 to 

migrate to DLMS. DLMS compliance is 

a discrete file format requirement with its 

own policy.

Correct. 

50 DFAS 1.8.4 PDC asserts that DFAS Central 

Accounts Offices (CAOs) are neither 

DLMS nor SFIS compliant today and 

have no plans to become so.

Noted. Removed statement from ADC.

51 DFAS 1.8.4.1 This assertion has been 

overcome by events. DFAS is beginning 

plans to migrate to DLMS by FY 2017.

Noted. DLA Logistics Management 

Standards will assist as needed to 

support DFAS DLMS migration.

52 DFAS 1.8.5 Important documentation in the 

PDC resides in links and DFAS requests 

that information contained in any 

extraneous briefing charts be added to 

the PDC so that it is complete.

Discussed with DFAS. Subject 

briefings are BTA briefings linked in 

enclosure (6). These briefings represent 

the BTA vision of the "Target To-Be" 

environment" and other BTA 

assumptions. They are included for 

background information as hyperlinks 

for brevity and readability.

53 DFAS 1.8.6 PDC does not discuss summary to 

detail operation in the target SFIS 

environment.

This change does not propose or 

approve changes to the summary to 

detail Interfund process or the Central 

Account Office (CAO) process.

54 DFAS 1.8.6.1 DFAS requests that PDC clarify 

whether the TO BE process will remain a 

Summary to Detail process with CAO 

reconciliation.

See above.

55 DFAS 1.8.6.2 DFAS requests that PDC owner 

undertake a proof of concept before 

proposing that detailed Interfund 

transactions be processed at Treasury.

Noted. See above.

56 DFAS 1.8.6.2.1 Treasury capacity is not 

proven.

Noted. See above.
Enclosure (7), ADC 435

Page 9

# Component/

Agency

Response/Comment Disposition

57 DFAS 1.8.6.2.1.1 For example, there 

currently is a 60 MB limit on GSA IPAC 

bulk items submitted

Noted. See above.

58 DFAS 1.8.6.2.2 Estimates are that there are 

about 150,000 summary bills between 

DLA and GSA each year with far more 

associated detail bills.

Noted. See above.

59 DFAS 1.8.6.2.2.1 The migration/processing 

of such large volume of transactions at 

any one time, in the IPAC Wizards; 

Historically, we have had problems with 

IPAC when a large number of 

transactions enter the system. The 

database fails and transactions are lost. 

It is a manual process to rebuild/input the 

lost transactions at the Disbursing Level. 

Noted. See above.

60 DFAS 1.8.6.2.2.1.1 The volume of billing 

details just from seller SL4701 was 

approximately 50k summary bills which 

are composed of up to 491 detailed lines. 

This totals to 2.4M detail lines. Fuels as a 

seller has been found to have at least 1M 

detailed records per month. Therefore, 

just for these two sellers there will be 

more than 3.5 million detailed records 

going to Treasury.

Noted. See above.

61 DFAS 1.8.6.2.2.1.2 Affects to IPAC would 

include all the bad data that no one 

would be able to determine/ locate. IPAC 

does not utilize the signal code and is 

ALC driven. IPAC is a very manual 

process that will create more issues with 

the increase of details. 

Noted. See above.

62 DFAS 1.8.6.2.2.1.3 IPAC is TAS (Treasury 

Account Symbol) & ALC driven. This 

required information is not in the 

Interfund feeder systems.

Noted. See above.

63 DFAS 1.8.6.2.2.1.4 IPAC is a manual preval/certification process. Additional 

manpower would be needed to handle 

such a workload. Presently, 400-500 

transactions per month = 1 IPAC person.

Noted. See above.
Enclosure (7), ADC 435

Page 10

# Component/

Agency

Response/Comment Disposition

64 DFAS 1.8.6.3 Security Cooperation 

Accounting is concerned that FMS 

(country/case/line) continue to be 

processed. 

No change.

65 DFAS 1.9 Detailed Conclusions

66 DFAS 1.9.1 PDC needs to add a crosswalk of 

the Interfund business data elements to 

SFIS (specifically showing what 

Logistics data elements will remain) and 

an E2E flow chart showing how business 

will work and documenting the AS IS 

versus TO BE.

Fund Code, Signal Code, and Bill-to 

DoDAAC are being retained, as are 

other current logistics/financial data 

elements. Logistics Bill processing and 

payment through Treasury are 

unchanged. This change provides the 

ability for exchange of SFIS data 

elements using referential data to 

support the BTA vision of the Target 

To-Be environment.

67 DFAS 1.9.2 PDC does not lay out new 

business rules needed to complement the 

change in data elements.

See above.

68 DFAS 1.9.3 PDC needs to address business 

rules that need to be adopted to process 

using SFIS data elements.

See above.

69 DLA DLA Finance and DLA Supply concurs 

with the PDC as written and prefers the 

alternative, which is the use of referential 

data to derive the SFIS data. The 

rationale for this decision is that it will 

require much less effort in redesigning 

our current transactions and interfaces 

while still meeting the intent of SFIS 

compliance. This is especially true of 

our Tailored Vendor Relationships 

(TVRs) which already have the fund 

code included, but would have to be 

opened up and heavily modified to carry 

a complete complement of SFIS data.

Noted. Referential data is the approved 

approach

70 DLA Using referential data should not cause 

any currently processed transactions to 

fail.

Noted.
Enclosure (7), ADC 435

Page 11

# Component/

Agency

Response/Comment Disposition

71 DLA We see no need to further modify the list 

of miscellaneous DLMS transactions as 

long as they continue to perpetuate the 

fund code from the original MILSTRIP 

transaction/order. Especially if the 

referential option is used.

Noted.

72 DLA DLA has a current need to retain FA201 

qualifier '18-Appropriation in the 527R 

to support legacy processes. This 

qualifier is used by DMLSS AMMA to 

assist in the communication of purchase 

card receipt data and in certain legacy 

processes supporting DLA Disposition 

Services. DLA will assess these legacy 

processes for conversion to use of SFIS 

data. 

Noted. Qualifier 18 will be retained in 

the 527R at this time to support DLA 

legacy processes during transition to 

SFIS.

73 DLA DLA Finance/Supply has no indication 

as to the number of fund codes needed to 

support a referential approach.

DLA confirmed that DLA has 

sufficient fund codes for its use to 

support referential data exchange.
Enclosure (7), ADC 435

Page 12

# Component/

Agency

Response/Comment Disposition

74 GSA 1. Preferred Approach. GSA 

processes Interfund bills for sales to DoD 

by NOAA, FAA and GSA.GSA prefers 

the approach of referential data using the 

existing fund code. GSA is not DLMS 

capable, but would endorse referential 

data even if we were. This is a 

streamlined approach to exchanging 

financial data. In addition, significant 

unnecessary costs would be incurred in 

modifying GSA Global and GSA 

Advantage to accommodate collecting 

and exchanging SFIS data elements at 

the transaction level. There would also be 

unnecessary costs in developing and 

maintaining an SFIS-compliant user 

profile within our applications, IF it 

could be done with an acceptable of 

effectiveness. We don’t fully understand 

how this concept might work. 

Alternatively, we are concerned about 

manual entry of individual SFIS data 

elements by users into our ordering 

applications being entered incorrectly, 

which might result in unmatched 

obligations and inability to process bills. 

We do not see the necessity of 

maintaining a dual system for DLMS and 

non-DLMS compliant systems, since 

referential data works for all. We feel 

that our customer support to DoD might 

be significantly impacted.

Noted. The referential data approach is 

approved.

75 GSA 2. Staffing Note – Potential 

Transaction Failure. We do not receive 

or transmit DLMS transactions and thus 

are unable to assess the impact.

Noted.

76 GSA 3. Staffing Note - Scope of 

Transaction Impact. We do not receive 

or transmit DLMS transactions and thus 

are unable to assess the validity of the 

proposed transaction set.

Noted.
Enclosure (7), ADC 435

Page 13

# Component/

Agency

Response/Comment Disposition

77 GSA 4. Proposed Data Elements 

Evaluation. We question the need for 

exchanging any financial information not 

needed for the seller to be reimbursed 

through Treasury. For example, the 

department transfer code is of no value to 

the seller. 

Noted. No changes in the Interfund 

process for treasury transfer of funding 

is proposed or approved. Department 

Transfer Code was identified by BTA 

as a needed SFIS data element in the 

Target To-Be environment

78 GSA a. Is there a future requirement for 

Sub- Account, and Treasury Sub Class 

for transfer of funds through Treasury? If 

not, they are not needed by the seller. 

Treasury Sub-Class is indicated as 

designated for removal in the “end state” 

BTA requested these data elements to 

support transition to the target 

environment.

79 GSA b. Can the period of availability be 

derived as it is done today? 

Yes.

80 GSA c. The BPN for our DoD customers is 

simply the DoDAAC prefixed with 

“DoD” Can’t that be derived? Since there 

are only three DoDAACs for GSA 

billings to DoD for NOAA, FAA and 

GSA, can’t those BPNs be derived? We 

are not DLMS capable and have no way 

to transmit that data today. Federal 

agency requisitions to DoD are not 

processed through Interfund.

BPN will be a DLMS data element as 

an authorized enhancement for DLMS 

capable systems. GSA is reviewing 

BPN process for Federal agencies.

81 GSA d. Limit/Subhead is used today. Is it 

going to be an SFIS data element?

This proposal supports Limit/Subhead. 

OSD Comptroller would lead any 

proposal to establish Limit/Subhead as 

an SFIS data element.

82 GSA 5. Staffing Note – Project 

Identifier/Project Code. We are unable 

to assess whether these should be 

separate data elements. 

Noted.

83 GSA 6. Staffing Note –BTA Proposed 

Future Data Elements. We oppose ever 

exchanging the additional data elements 

of Budget Line Item Identifier, Cost 

Center Identifier, Project Identifier 

Activity Identifier or Work Order 

Number. These data elements are of no 

value to the seller and there is no 

articulated business process to support 

their need.

These data elements are not being 

added to DLMS.
Enclosure (7), ADC 435

Page 14

# Component/

Agency

Response/Comment Disposition

84 GSA 7. Staffing Note – Transactions Not 

Requiring SFIS Data Elements. We do 

not receive or transmit DLMS 

transactions; however, we do not support 

transacting SFIS data elements in any 

transactions. We support maintaining the 

fund code in these transactions.

Fund code, signal code and bill-to 

DoDAAC are being retained Only BPN 

is being added to DLMS transactions. 

Referential data using fund code will 

be used to exchange SFIS accounting 

data elements.

85 GSA 8. Staffing Note – Unneeded DLMS 

Qualifiers. We do not receive or transmit 

DLMS transactions and are unable to 

comment.

Noted.

86 GSA 9. Staffing Note – Availability of 

Sufficient Fund Codes. Federal buyers 

do not use fund codes or reimburse DoD 

through Interfund. This is not applicable 

to us.

Noted.

87 GSA 10. General Comments.

88 GSA a. We are interested in the staffing 

note for BTA to clarify the relationship 

(if any) to initiatives by the procurement 

community to employ SFIS data. The 18 

march 2008 Memorandum, subject: 

Linking Financial Data to Contract 

Documents, signed by Under Secretary 

of Defense (AT&L) and Under Secretary 

of Defense Comptroller directs target 

system to use referential data in lieu of 

carrying financial line of accounting data 

in contracts in order to identify the 

funding source, to ensure accurate 

payment and to ensure that future 

systems with contract writing capabilities 

are compliant with the Standard 

Financial Information Structure (SFIS). 

We note that BTA has a key role in 

implementing this approved plan. How is 

this approach different from the 

referential data approach for logistics 

transactions using Interfund? Why is 

BTA not endorsing referential data for 

Interfund?

Correct, both approaches use referential 

data. See (OSD Memo Mar 18 2009 -

Linking Financial Data to Contract 

Documents) See 

http://www.acq.osd.mil/dpap/policy/pol

icyvault/USA002246-09-DPAP.pdf

89 GSA b. What is the timeframe for the 

Target Environment?

This is notional. No timeframe has 

been specified.
Enclosure (7), ADC 435

Page 15

# Component/

Agency

Response/Comment Disposition

90 Navy The preferred Navy approach is using 

referential data by adding SFIS data 

elements to the current fund code table. 

The majority of respondents are not 

utilizing DLMS transactions. NERP 

software has the capability to handle long 

lines of accounting but compliance with 

the adoption of SFIS will require 

extensive software design and 

development to serve the entire disparate 

Navy enterprise. The proposed 

standardized SFIS format in PDC365 

differs from the format that is presently 

utilized in NERP for managing 

accounting lines internal to Navy. New 

NERP modifications are estimated to be 

required for external interfaces with 

approximately 20 non NERP systems 

including Management Information 

System for International Logistics 

(MISIL). Both proposals represents an 

extensive unplanned workload and with 

unknown consequences that are difficult 

to quantify at this preliminary stage of 

analysis.

Noted. Referential data exchange is 

approved for the DoD Logistics 

Enterprise.

91 Navy (Section 6.b.2.ii.A, paragraph 1, Staffing 

Note)

Navy Response: Without the OSD 

policy it’s difficult to provide a position.

Noted.

92 Navy (Section 6.c, paragraph 1, Staffing Note)

Navy Response: Staffing to normal 

DLMS email distribution listing did not 

result in components validating the list of 

Other Miscellaneous DLMS transactions

Noted.

93 Navy (Section 6.c.7, paragraph 1, Staffing 

Note)

Navy Response: Staffing to normal 

DLMS email distribution listing did not 

produce responses to this question. 

Components did not evaluate and 

confirm this 842A/W enhancement to 

automated processing. 

Noted.
Enclosure (7), ADC 435

Page 16

# Component/

Agency

Response/Comment Disposition

94 Navy (Section 6.d, paragraph 1, Staffing Note)

Navy Response: The proposed concept 

is to send SFIS data elements 

(Department Regular Code, Department 

Transfer Code, Period of availability, 

Main Account Code, Subhead, Subaccount Code, Treasury Sub Class, and 

Business Partner Number) in all 

transactions that trigger a financial action 

(debit/credit bill). 

Correct. Only BPN will be carried in 

DLMS under the approved referential 

data approach.

95 Navy (Section 6.e.4, paragraph 1, Staffing 

Note)

Navy Response: Project identifier 

should be included but independent of 

project code. Fleet Forces Command 

wants to explore using this field for 

internal tracking purposes.

Noted. Project code will remain a 

separate DLMS data element.

96 Navy (Section 6.g, paragraph 1, Staffing 

Note)Navy Response: These additional 

DLMS data elements DoD buyers will 

have to know all SFIS information and to 

accurately provide that information to 

sellers for logistics transaction initiated 

outside of Component ERPs. This will 

impact transactions initiated through 

offline applications, such as call-in center 

emergency operations, and those initiated 

through internet ordering applications, 

such as call, eMALL, GSA Global and 

GSA Advantage. This may increase the 

opportunity for error, for rejected 

transactions and for unmatched financial 

transactions.

Noted. Referential data exchange is the 

approved approach, which obviates this 

risk.

97 Navy (Section 6.h, paragraph 1, Staffing Note)

Navy Response: Staffing to normal 

DLMS email distribution listing did not 

result in components validating the list of 

Other Miscellaneous DLMS transactions.

Noted.
Enclosure (7), ADC 435

Page 17

# Component/

Agency

Response/Comment Disposition

98 Navy (Section 6.i, paragraph 1, Staffing Note)

Navy Response: Staffing to normal 

DLMS email distribution listing did not 

result in the components commenting on 

the X12 qualifiers being removed and 

confirm that they are not required. 

Noted.

99 Navy (Section 6.k, 8th bullet point, Staffing 

Note)

Navy Response: Currently under SDC 

N, we can only establish 1,035 fund 

codes. The 1,035 is made up of the 

following:

 Alpha/Alpha 676

 Alpha/Numeric 260

 Numeric/Numeric 99

The difference between the 1295 and 

1035 is 260 which is using 

Numeric/Alpha fund codes.

We would need to have 304 fund codes if 

we do not use old fund codes. Currently, 

we have available 300 fund codes that 

can be assigned and the other 260. Most 

of the fund codes available have an "I or 

O" in the first or second position which is 

why they have not been assigned. I think 

we should be able to assign the additional 

fund codes.

Noted.

100 Navy Under SDC R and V, we have available 

1,295 fund codes. The majority of fund 

codes assigned are annual appropriations. 

There are a few multiyear appropriations. 

Under SDC R and V there are only 5 

Major Commands. We would be able to 

assign additional fund codes for the multi 

years.

Noted.
Enclosure (7), ADC 435

Page 18

# Component/

Agency

Response/Comment Disposition

101 Air Force SAF/FMP AFAFO recommends “option 

2” as we don’t see a need or the purpose 

for the extra SFIS data elements 

proposed in “option 1.” It appears the 

referential data method will be less 

costly, less prone to input errors and not 

create a band width issue in some of our 

AOR operations.

Noted. Referential data exchange is 

approved for the DoD Logistics 

Enterprise.

102 Air Force (Section 6.b.1, paragraph 1, Staffing 

Note) 

Air Force Response: AFAFO will defer 

to the Air Force ERPs (ECSS and 

DEAMS) to answer this question. 

DEAMS currently receives the old 80 

card column file, not the DLMS 

compliant transaction.

MILS transactions 80 record position 

transactions will not be affected by this 

change.

103 Air Force (Section 6.c, paragraph 1, Staffing Note) 

Air Force Response: no issues with the 

list of transactions; however, we are 

talking in a perfect world when all the 

feeder systems are DLMS compliant and 

can support sending SFIS data elements. 

In the meantime, if we’re able to process 

transactions in the current format and 

won’t be required to change for years to 

come, why make the change?

This change supports exchange of SFIS 

data in the "Target To-Be" 

environment" as envisioned by BTA. 

Establishing this capability now will 

allow transition to use SFIS data 

elements in the "Target To-Be" 

environment."

104 Air Force (Section 6.c.8.a, paragraph 1, Staffing 

Note) 

Air Force Response: Including a BNP is 

a welcome enhancement, not necessarily 

to processing, but certainly eliminations. 

When all agencies become DLMS 

compliant this will aid in the OSD 

eliminations effort.

Noted.
Enclosure (7), ADC 435

Page 19

# Component/

Agency

Response/Comment Disposition

105 Air Force (Section 6.d, paragraph 1, Staffing Note) 

Air Force Response: Again in a perfect 

world when all agencies are DLMS 

compliant and can support sending, 

storing and receiving the additional SFIS 

data elements this will work. We need to 

keep in mind that we’ll be asking nonFMers to input, correctly, these 

additional data elements in the ordering 

system. Currently we only require them 

to input the fund code, signal code and 

DoDAAC. What kind of mess will we 

be creating for ourselves by asking them 

to input these additional data elements?

Referential data using the fund code 

will eliminate the issues with entering 

the discrete data elements into 

transactions, with the resultant 

possibility for error.

106 Air Force (Section 6.g, paragraph 1, Staffing Note) 

Air Force Response: Again, we’re 

asking our war fighters out in the field to 

be responsible for providing this data 

over the phone? That aside, the seller 

doesn’t care about this data—what the 

purpose of this additional data?

Noted.

107 Air Force (Section 6.i paragraph 1, Staffing Note)

Air Force Response: Response: Not 

necessary, serves no purpose.

Noted

108 Air Force (Section 6.k, 8th bullet point, Staffing 

Note) Air Force Response: AFAFO will 

defer to DFAS-CO Accounting 

Requirements

AF Fund Code monitor confirmed 

sufficient fund codes are available for 

referential data.

109 Marine Corps 1. Section 6.b.

110 Marine Corps a. The Marine Corps receives data 

through DLA Transaction Services (DLA 

TS) and do not expect the format to 

change in the short term. If DLA TS will 

no longer plans to translate this data, the 

Marine Corps will require advance 

notification to assess the impact.

Noted.

111 Marine Corps b. The Marine Corps is unaware of any 

impacts on Defense Cash Accountability 

System (DCAS), however effects on 

DCAS may impact Marine Corps 

business processes.

Noted. No changes to DCAS are 

incorporated into this DLMS change.

112 Marine Corps 2. Section 6.c.
Enclosure (7), ADC 435

Page 20

# Component/

Agency

Response/Comment Disposition

113 Marine Corps a. This PDC lists the 511R as a 

requisition, however, during a telecom 

which included reps from HQMC, 

MCLC, and DLMSO it seemed as though 

the logistics and financial definitions of a 

requisition contain differences.

Clarified with USMC. The 511R is the 

DLMS requisition, which provides 

source data perpetuated into the 810L 

Logistics Bill. There is only one 

requisition.

114 Marine Corps i. This poses problems for organizations 

that are responsible for the 511 

transaction from these 

entities/systems/sources.

See above.

115 Marine Corps 3. Section 6.d.

116 Marine Corps a. USMC concurs with all data elements 

to be added to the DS 810L.

Clarified with USMC. Only BPN is 

being added to the DS 810L.

117 Marine Corps b. Limit/Subhead is not included as part 

of this list but is listed in the text of the 

accompanying paragraph. It is important 

that the 810L include Limit/Subhead.

Limit/Subhead will remain a part of the 

fund code table and will remain a part 

of the "Funds Appropriation" in the 

Summary Bill.

118 Marine Corps 4. Section 6.e.4.

119 Marine Corps a. If the project code and project ID are 

not the same, they should be separated at 

all times.

Noted. Project code and project 

identifier will be separate data 

elements.

120 Marine Corps 5. Section 6.f.

121 Marine Corps a. USMC does not concur with the 

assumption that SFIS elements will be 

retained in the DoD Component 

Requisition Source Systems.

Noted. This is the BTA vision of the 

Target To-Be environment. See page 8, 

paragraph 6.g.of this DLMS change.

122 Marine Corps b. These elements are captured in the 

buyer’s financial system, however, the 

Marine Corps cannot capture this data if 

the source of the requisition does not 

provide them (e.g. off line requisitioning 

systems)

See above.

123 Marine Corps c. The requirement being sent to the 

seller is not generated in the accounting 

system and therefore needs to be 

communicated to the accounting system 

so that the obligation can be recorded.

See above.

124 Marine Corps 6. Section 6.g.

125 Marine Corps a. The Marine Corps is indifferent to the 

requirement for inclusion of the “Cost 

Objects”

Noted.

126 Marine Corps b. The Marine Corps is indifferent to the 

requirement for inclusion of “Budget 

Program Information”.

Noted.
Enclosure (7), ADC 435

Page 21

# Component/

Agency

Response/Comment Disposition

127 Marine Corps 7. Section 6.h.

128 Marine Corps a. a. The Marine Corps confirms that 

these data elements are not required by 

the transactions addressed under PDC 

365. However, these elements may be 

applicable to other transactions as 

MILSBILLS is redefined.

The data elements are not used and will 

be removed from DLMS. Future data 

element requirements will be addressed 

by separate change proposals as 

needed.

129 Marine Corps 8. Section 6.k.

130 Marine Corps a. The Marine Corps concurs with the 

proposed use of referential data. 

However, the flexibility to 

modify/change/update fund codes is 

vitally important to the Marine Corps. It 

is essential that any system designed to 

centrally manage fund codes does not 

sacrifice the components’ flexibility to 

modify existing codes.

The Referential Data approach of is 

adopted for the DoD Logistics 

enterprise. Agencies will remain solely 

responsible for maintaining their fund 

codes through Components/Agency 

Fund Code Monitors.

131 Marine Corps 9. Section 6.k, 8th bullet

132 Marine Corps a. The Marine Corps concurs with the 

use of wild card characters on a 

component-by-component basis. 

Currently the Marine Corps does not 

anticipate using wild card characters.

Noted. The symbols "#" and "*" will be 

retained.

133 Marine Corps b. Under current processes the Marine 

Corps does not have sufficient fund 

codes to accommodate different fund 

codes for different years of a multi-year 

obligation. However, the Marine Corps 

will work to reduce the use of multiple 

fund codes within certain commands and 

directorates making it possible to assign 

new fund codes to each year of a multiyear obligation.

Noted.

134 USTRANSCOM If this PDC is adopted, request DLMSO 

include wording in the ADC that allows 

for a 90 day period between when the 

ADC is released and when it is effective, 

in order to provide that time to IGC PMO 

to make any necessary changes to our 

system.

Noted. Sufficient time will be allotted 

for transition.