2

ADC 350 

NAVY BUDGET PROJECT FOR BILLING (MILSBILLS/FINANCE) 

1. ORIGINATOR: 

a. Service/Agency: Naval Supply Systems Command (NAVSUP)

b. Originator: NAVSUP, Code 141, DSN 430-5712

2. FUNCTIONAL AREA: Finance

3. REFERENCE:

a. DoD 4000.25-7-M, Military Standard Billing System (MILSBILLS)

4. REQUESTED CHANGE: 

a. Title: Navy Budget Project for Billing 

b. Description of Change: The purpose of this change is to map the Navy’s current MILS 

billing transactions for the Summary Bill to the DLMS Supplement 810L, Logistics Bill by including a 

DLMS qualifier called “budget project identifier” for Navy “budget project”. This change will support 

the Navy migration to DLMS, and will support mapping in a mixed DLMS/MILS environment. 

c. Background. 

(1)The Navy, within the Interfund Billing process, uses an data element called the budget 

project to determine the budget control number (BCN) that is passed between the bill processing system 

(DFAS/VISTA) and the expenditure processing system (DCAS) and the processing of the expenditure 

within Navy ERP. VISTA uses the budget project to populate the BCN and pass it to DCAS for 

processing. The budget control number is contained in the MILS Summary Bill “Internal Use” field, rp 

22-27, but there is no comparable qualifier in DLMS. 

(2)The Navy’s ERP project currently under development will replace the Navy ICP’s 

DLSS/MILSBILLS billing system with a DLMS-based system. Currently, there is no mapping of where 

this element should be placed by middleware into the DLMS 810L outbound billing transaction. This 

change will allow the element to continue to be passed between DLMS and MILS based systems for 

Navy Billing. This change does not impact other Component procedures. 

(3)Procedures. 

(a) Revise DLMS Supplements and DAASC Mappings for 810L as follows:

Item 

# 

Location Revision to 

810L, Logistics Bill 

Reason Federal 

Update 
3

1. DLMS 

Introductory 

Note: 

Added ADC 350 to DLMS Introductory 

note 8.

- ADC 350, Navy Budget Project for 

Billing (MILSBILLS/Finance) 

To identify DLMS 

changes included in 

the DS 

No Update 

Required 

2. 1/FA201/300 Add qualifier “C2” with the following 

DLMS Note:

C2 Project Task or Budget Subline 

DLMS Note: Use to identify the budget 

project identifier for Navy transactions.

Adds Navy use of 

C2 qualifier for 

budget project 

 

Update 

Required 

DLSS/DLMS Mapping 

Field Name DLSS 

Position 

Conditions Revision to 810L 

Mapping 

810L 

Position/Loo

p 

Project Task or 

Budget Subline 

26-27 If rp 1-3 = FS1 or FS2, 

AND 

If rp 19-21 = NRP

FA201=C2 

FA202 = rp 25-27 

1/FA201/300 

5. REASON FOR CHANGE: Allows Navy to continue billing under DLMS with indicators 

currently used in MILS for creating financial transactions.

6. ADVANTAGES AND DISADVANTAGES: 

a. Advantages: Supports billing for Navy under DLMS in a mixed DLMS/MILS 

environment.

b. Disadvantages: None

7. IMPACT/IMPLEMENTATION: 

a. Impacts: 

(1) Update appropriate documentation. 

(2) Revise DAAS DLMS to DLSS mapping. 

b. Implementation: Phase I of Navy ERP is currently planned for implementation in Feb 

2010. 

8. NEW DLMS DATA ELEMENTS. This change adds DLMS Data Element “Budget Project 

Identifier”.