DEFENSE LOGISTICS AGENCY

HEADQUARTERS

8725 JOHN J. KINGMAN ROAD

FORT BELVOIR, VIRGINIA 22060-6221

August 3, 2023 

MEMORANDUM FOR DISTRIBUTION

SUBJECT: Joint Finance and Supply Process Review Committees Meeting, July 19, 2023 

 This memorandum forwards the attached minutes of the joint meeting of the Finance 

Process Review Committee and Supply Process Review Committee providing updates on DoD 

and GSA progress on integrating into G-Invoicing. 

The Defense Enterprise Data Standards Office point of contact is Mr. Edward (Nolan)

Davis, e- mail dedso.finance@dla.mil. 

Sarah Winegardner

Director, Defense Enterprise Data Standards 

Office 

Attachment

As stated,

DISTRIBUTION:

ODASD(Logistics)

OUSD Comptroller

FPRC

SPRC

Attendees
Minutes from Finance Process Review Committee Meeting 23-01, July 19, 2023 

1 

1. Purpose: The Defense Enterprise Data Standards Office (DEDSO) convened a virtual joint 

Finance Process Review Committee (PRC) and Supply PRC meeting via Microsoft Teams on 

July 19, 2023. Specific discussion topics are noted below. The meeting agenda and briefing 

materials are available on the Finance PRC web page archive: www.dla.mil/FinancePRC.

2. Brief Summary of Discussion: Mr. Nolan Davis, DEDSO Chair of the Finance PRC, 

facilitated discussions during the meeting. Overview presentations on G-Invoicing efforts were 

provided by Ms. Fatimoh Ajadi from the Office of Undersecretary of Defense (OUSD) 

(Comptroller), Ms. Gail Bruss of the General Services Agency (GSA), and Ms. Wendy Villaman 

of Defense Logistics Agency (DLA) Finance (DLA J8G). The final presenter was Mr. Eric 

Flanagan (DLA J341), covering the history and status of Proposed Defense Logistics 

Management Standard (DLMS) Change (PDC) 1442, G-Invoicing 7600EZ Order Information. 

3. Opening Remarks: Mr. Davis briefed the group on today’s agenda and introduced Ms. Sarah 

Winegardner, DEDSO Director, who welcomed participants and special guests, Ms. Stephanie 

Lopez and Ms. Lisa Kelly of Deputy Assistant Secretary of Defense (DASD) (Logistics) and Ms. 

Ajadi. 

4. Meeting Topics:

a. OUSD(Comptroller) G-Invoicing Update

Ms. Ajadi began by acknowledging the opportunity to present to the joint finance and supply

communities, as the input and support from both communities is important to the success of GInvoicing. Ms. Ajadi leads a team that monitors DoD-wide G-Invoicing implementations, with 

quarterly reviews of Component implementation plans. Regular meetings are held with Treasury, 

Components, other Federal agencies, and supporting vendors to disseminate information, as well 

as bi-weekly stakeholder working groups to discuss and resolve targeted topics. As appropriate, 

her team will draft policy recommendations and action plans based on input from the working 

groups. The presentation shows the current working groups and their focuses.

Ms. Ajadi covered Treasury’s G-Invoicing platform for intragovernmental buy/sell transactions 

which addresses legacy issues with balancing accounts on both sides of the transaction. This 

includes data standardization to ensure proper sharing of data to facilitate eliminations. DoD has 

been working within the G-Invoicing construct to resolve long-standing material weaknesses 

with intragovernmental transactions where past trading partner data has not aligned and/or lacked

in completeness. G-Invoicing provides a consistent, complete, real-time data set for 

transparency.

Treasury’s mandate for G-Invoicing started establishing General Terms & Conditions (GT&C) 

entries in 2018. New orders started going into the system in October 2022, and orders for legacy 

agreements are to transition to G-Invoicing by October 2023. Ms. Ajadi’s team is tracking DoD 

systems progress towards implementing G-Invoicing data sharing requirements for each of the 

key buy/sell areas (i.e., GT&C, Orders, Receipt & Acceptance, and Invoicing). The 

intragovernmental buy/sell activities align with DoD standards for Procure to Pay, Order to 

Cash, and Budget to Report. This is why success depends on cross-functional collaboration 

among procurement, supply, and finance communities. DoD has published G-Invoicing 
Minutes from Finance Process Review Committee Meeting 23-01, July 19, 2023

2

Implementation Guidance for trading partners to meet each step, and appendices advising on key 

topics derived through the working groups.

Mr. Selester Copland, OUSD(Comptroller), commented that in addition to the Treasury and DoD 

financial management reference materials shown in Ms. Ajadi’s presentation, there is a need for

guidance materials for G-Invoicing from the supply chain perspective relating to creation of 

agreements and receipt and acceptance. He recommends the supply community look at 

developing guidance to fill those gaps for DoD buyers and sellers of goods and services not 

covered by the standard ordering systems.

Ms. Jo Stump of Defense Finance and accounting Service (DFAS), noted implementation 

tracking at the enterprise resource planning (ERP) system level, and asked about legacy feeder 

systems. Ms. Ajadi explained that all systems performing intragovernmental buy/sell transactions 

are in scope of G-Invoicing, but current tracking is at the ERP level as those are the system 

identified by the Components to be performing G-Invoicing reporting.

Ms. Amy Balog of DFAS asked if G-Invoicing replacing all of Treasury’s Intra-Governmental 

Payment and Collection (IPAC), or just for the reimbursable billing process? Ms. Bruss 

answered that IPAC will still be around but buy/sell transactions will eventually be locked out of 

IPAC.

b. G-Invoicing Implementation at GSA

Ms. Bruss began her presentation with a representation of the target schedule for major GSA 

business lines to implement G-Invoicing. At the far right of the schedule is a placeholder for 

supply, which does not, yet, have a target date. GSA does have success with G-Invoicing, and 

through June has processed over 150 orders, and collected $49 million via G-Invoicing.

In the years since GSA began working to implement G-Invoicing they learned that the original 

workflow G-Invoicing was designed to does not work well for all business lines. Some 

traditionally less structured business lines did work with the initial G-Invoicing concept. 

However, heavily automated business lines with enforced rules (e.g., supply and vehicle leasing) 

would be overly burdened by inserting programming officials and funding officials to approve 

each step. Treasury developed the G-Invoicing 7600 EZ process where a Government system

will have all the details to provide G-Invoicing with data to complete the fund transfer. Ms. Buss 

recognized how Treasury worked with GSA to develop seller facilitated G-Invoicing adjustments 

which enabled easier alignment with existing business line workflows.

Ms. Bruss shared several lessons learned about working with the more manual workflows of GInvoicing. These included: having awareness of trading partner group, identify the group 

superuser for issues, don’t begin a modification until ready, check your entries since they cannot 

be edited later, and encourage patience. She encourages stakeholders to attend Treasury training 

and customize as necessary within your organization according to requirements.

In broad terms, GSA’s challenges with G-Invoicing involve timing and middleware. Because 

each business line had to be evaluated against a workflow alignment with G-Invoicing, each 

program’s system needed to work with their vendor to get the programming changes 

implemented. GSA business systems use middleware to collect information and share data with 
Minutes from Finance Process Review Committee Meeting 23-01, July 19, 2023

3

the financial system. A review of interfaces and data exchange formats needs to identify any 

gaps with the updated requirements.

Specific to supply, GSA recommends a 7600EZ process to avoid burden of additional approvals 

in the supply process. GSA assumes the eventual solution will integrate into existing order 

handling systems, avoid burdening ordering parties with additional accounting knowledge, and 

may require middleware to derive G-Invoicing data insertion into the ordering process.

GSA wants to continue supporting the warfighter with timely supplies. GSA is working with 

DoD and Treasury to identify ways to supplement requisition data with any additional GInvoicing data needed for low burden implementation. Then a timeline for implementation can 

be set.

c. DLA G-Invoicing Strategic Way Forward

Ms. Villaman explained this presentation is intended to level-set the DLA strategic view of GInvoicing as a lead-in to Mr. Flannagan’s presentation on PDC 1442. The scope of G-Invoicing 

includes all intragovernmental buy/sell transactions that have been settled in Treasury’s IPAC 

system (e.g., Military Interdepartmental Purchase Request (MIPR) and non-interfund materiel 

requisitions), and will include interfund materiel requisitions. Other than interfund, the other 

collections need to be transferred to G-Invoicing before IPAC is closed out (target date October 

2025). DoD needs a common solution around the 7600EZ process for a consistent standard all 

parties could program towards.

DLA’s vision is for a 7600EZ solution to be implemented within five years that will provide 

auditability, efficiency of a cohesive systemic process, and integrate into innovations for the 

warfighter. Leveraging DLA’s position as the large volume processor of intragovernmental 

transactions, the agency wants to be the primary voice to internal and external stakeholders on 

issues of reimbursable work orders.

DLA is preparing for ServiceNow as an enterprise platform supporting G-Invoicing, with a 

contract expected soon for a system integrator. The agency has also leveraged SAP backend 

solutions for the Enterprise Business System (EBS) ERP. DLA will soon kick off agile 

development schedule for solution development based on major business cycles.

DLA split processes into either the G-Invoicing 7600B or 7600EZ approaches. Most service 

transactions and some materiel typically involving a MIPR will be directed to 7600B workflows. 

Most materiel processed through automated systems, though non-interfund, will be 7600EZ 

processes. Interfund based materiel still needs to be worked but DLA believes the solution is

likely a 7600EZ process. DLA needed Treasury to lift a $10K limitation on 7600EZ (competed 

July 11, 2023) and update that change in the Treasury Financial Manual (expected in November 

2023 bulletin). DLA recommends a two-phase plan for materiel businesses to approach GInvoicing: a DoD mandate for the 7600EZ as the standard solution for DoD trading partners, 

engage with venders to integrate a consensus standard for G-Invoicing support into DoD 

systems. DLA encourages partners to coordinate on an October 2025 target for G-Invoicing 

implementation.
Minutes from Finance Process Review Committee Meeting 23-01, July 19, 2023

4

Mr. Copeland appreciated the details but commented concern about system development without 

cross-Component agreement on policies and procedures in place first. Ms. Villaman believes the 

intent is to partner on the design and development of the system platform and that the next 

presentation from Mr. Flanagan is a step in that effort.

Mr. Nate Owens of U.S. Navy is interested to know which GT&Cs would need to be used for an 

order that is submitted to DLA that is referred to GSA? Ms. Villaman will take for action. 

Mr. Owens also asked if XP fund code transactions that route through IPAC for billing are able 

to occur after the planned 1 OCT FY26 IPAC shutoff for the buy/sell subcategory? If no, is there 

mitigation planning occurring together with Treasury? Ms. Villaman noted that XP fund code 

transactions will be affected by the IPAC shutoff and is why those are part of the priority group 

to be addressed. The interfund transactions are not impacted by IPAC shutdown, which is why it 

is on a to-be-determined timeline.

A third question from Mr. Owens asked if, for example, Navy is a seller, then at which point of 

the supply chain process (and who) would need to create the 7600EZ transaction? Would Navy 

need to implement its own 7600EZ creation logic? Because the 7600EZ combines the order and 

performance into one transaction the Navy would need to implement its own logic if they wanted 

to use it as a seller. 7600EZ involves seller-initiated invoices. Each seller should evaluate if the 

service line being offered best fits to the 7600B or 7600EZ approach. Though it would be 

beneficial if all trading partners followed similar processing rules for 7600EZ.

Mr. Owens asked if the Treasury’s 7600EZ permissions are specific to DLA or the whole of 

DoD? Ms. Villaman clarified that the recent permission DLA got was for lifting a $10K limit 

associated with 7600EZ. Ms. Ajadi believes the limit removal may have been universal, but it 

needs to be confirmed with Treasury as the agreement was worked in the context of DLA 

materiel.

d. PDC 1442 Update and 7600EZ Implementation Strategy

Mr. Flanagan introduced his work on PDC 1442, G-Invoicing 7600EZ Order Information, as a 

solution for DLA, GSA, and any other Federal supply source to integrate G-Invoicing into 

system ordering systems.

The PDC solution has a relationship to steps taken to implement Standard Financial Information 

Structure (SFIS)/Standard Line of Accounting (SLOA). Since 1997, Federal agencies have had 

to submit their financial statements that get consolidated into a Federal financial statement. 

Within DoD, the Components send financial statements to DFAS to be matched up in an 

eliminations process. Where DFAS cannot align the balances, DFAS creates an unsupported 

journal entry to get the numbers to line up for consolidation. The idea behind G-Invoicing is to 

guide data collection to line-up and support the eliminations. Back in 2005, DoD established 

SFIS for financial reporting, but also to make it easier to crosswalk between financial 

information and requirements for budgeting, cost and performance, and similar initiatives. A

2012 memorandum for SFIS/SLOA, sought to standardize line of accounting elements across 

Components for reducing errors, unmatched disbursements, unsupported eliminations, and high 

costs to develop and maintain financial interfaces. Each Component was required to provide 
Minutes from Finance Process Review Committee Meeting 23-01, July 19, 2023

5

implementation plans to conform with SFIS/SLOA. Implementation plans focused on 

Component business systems which would be responsible for posting financial data.

When it came to supply transaction support of SFIS/SLOA, Approved DLMS Change (ADC) 

435, DLMS Revisions for Standard Financial Information Structure (SFIS)” (October 3, 2011), 

created a mechanism for legacy 80 column transactions to reference the key Treasury line of 

accounting elements. A lookup table was established at Defense Automatic Addressing System 

(DAAS) where each Component maintains records for two-character fund codes and a

corresponding line of accounting. After the 2012 SFIS/SLOA memorandum, ADC 1043, DLMS 

Revisions for DoD Standard Line of Accounting (SLOA)/Accounting Classification (September 

18, 2023) refined the lookup table at DAAS to conform to the elements and added all the SLOA

elements to DLMS variable length transactions that initiate a financial action (e.g., obligations 

and billing). With the updated lookup table, DAAS can add the line of accounting when 

converting from legacy to variable length transactions and can verify the fund code and line of 

accounting data in variable length transactions. There are ways to connect to DAAS to get an 

import of the fund code lookup table.

PDC 1442 attempts to replicate the lookup table approach from ADC 435, to map supply 

transactions to Federal Intragovernmental Data Standards (FIDS) data elements. This adds 

support for financial reporting data lookup within DAAS for Federal agencies. The existing fund 

code lookup table requires all non-interfund orders to use a fund code with no line of accounting 

(i.e., fund code = “XP”). And like ADC 1043, specific DLMS transactions would add discrete 

FIDS elements for G-Invoicing. This later part mostly, involves just changing the name of the 

SFIS/SLOA element to the FIDS name.

PDC 1442 was staffed at the beginning of 2023. Responses were received from most 

Components noting approval or approval with comments. Mr. Flanagan would like to form a 

working group to addresses stakeholder comments and hammer out details for the proposed 

lookup table, tangent scenarios (post-post orders offline orders), and eat away at unmatched 

disbursement causes.

Ms. Flanagan is considering breaking up the PDC into two tracks. One focus would be on 

developing the FIDS lookup table requirements. The other task would work through changes to 

DLMS transactions and processes.

Mr. Flanagan proposed engagement on examining G-Invoicing implications to SFIS/SLOA and 

if there is a need for tweaking the policy to align objectives.

If the direction leads to retaining fund code use only within DoD, then Mr. Flanagan believes an 

enhancement to the existing fund code table would still be beneficial in enable DoD G-Invoicing 

while legacy transition and offline ordering support continues. In relation to offline ordering 

systems, the DoD should encourage these applications to adopt a standard registration process 

for intragovernmental orders that requires FIDS information which must be attached to orders 

and linked to performance and invoicing done by these systems.

Once a solution starts to develop, DoD and GSA need to work with Treasury to establish an 

updated timeline for implementation.
Minutes from Finance Process Review Committee Meeting 23-01, July 19, 2023

6

Ms. Tamera Williams of FAA noted they often have issues identifying accounting information 

from DoD orders, and she asked if use of the fund code would solve that issue. Mr. Flanagan 

explained that the current fund code does not include all the FIDS data, and his proposal does 

seek to add that information. However, he also recommends adding the discrete elements into 

the relevant DLMS transactions, allowing the data to be conveyed directly between trading 

partners.

e. Follow-up questions:

Ms. Mia Ha from FAA requested a follow-up session soon after they have had a chance to digest 

the information and can ask questions. 

Meeting Wrap Up

Mr. Davis thanked all presenters and participants for their contributions to today’s meeting. Mr. 

Davis will work with Mr. Flanagan to get the new working group established in the coming 

weeks.

Action Item 1 Item to be addressed by DEDSO Finance: In response to a request by FAA, 

DEDSO will work with OUSD Comptroller, DLA, and FAA to arrange a follow up meeting.

DEDSO shared the following tentative schedule for upcoming PRCs:

• Supply PRC – September 13, 2023

• Supply PRC Session on ADC 1244B Implementation Progress – October TBD, 2023

• Supply Discrepancy Reporting (SDR) – November 15, 2023

• Product Quality Deficiency Reporting (PQDR) – November 15, 2023

• Finance PRC - December 6, 2023