System-by-System Profiles

3.1 GFEBS — General Fund Enterprise Business System (U.S. Army)

Interconnections

• Receives logistics/supply obligation data from GCSS-Army and LMP via the Army Enterprise Systems Integration Program (AESIP) enterprise hub.
• Feeds real-time obligation, disbursement, and GL data to CDAO's Advana platform via SAP SLT (SAP Landscape Transformation) streaming-replication pipelines established in 2023, landing in Advana's MySQL/S3 and, subsequently, an SAP HANA data layer.
• Interfaces with DFAS disbursing systems, the Defense Civilian Pay System (DCPS), the Defense Travel System (DTS), and Treasury's Fund Balance with Treasury reporting chain.

3.2 Navy ERP (N-ERP)

3.3 STARS Family — Standard Accounting and Reporting System (Navy legacy)

3.4 DEAMS — Defense Enterprise Accounting and Management System (U.S. Air Force / USTRANSCOM)

3.5 ABSS — Automated Business Services System (U.S. Air Force)

See Section 9.8–9.9 for a full technical trace of how an ABSS-originated obligating document becomes a GAFS-BL budgetary posting, then a GAFS-R USSGL entry, then a DDRS trial balance line — and specifically where trading-partner detail needed for intragovernmental elimination gets lost along the way.

3.6 DAI — Defense Agencies Initiative (4th Estate Defense Agencies)

Interconnections

• Serves as the shared accounting-system-of-record for organizations that would otherwise each need a bespoke ERP — conceptually the Defense Agency analogue to GFEBS (Army) and DEAMS (Air Force).
• DLA's separate SAP-based Enterprise Business System (EBS, see 3.7) provides DLA's supply-chain/logistics execution and interfaces to DAI for DLA's own financial accounting.
• Feeds Advana and DFAS reporting chains; participates in the DoD-wide Standard Financial Information Structure (SFIS) chart-of-accounts standard shared with GFEBS, Navy ERP, and DEAMS.

3.7 DLA EBS — Enterprise Business System (Defense Logistics Agency)

3.8 GCSS-Army — Global Combat Support System-Army

3.9 LMP — Logistics Modernization Program (U.S. Army)

3.10 GCSS-MC — Global Combat Support System-Marine Corps

3.11 SABRS — Standard Accounting, Budgeting, and Reporting System (U.S. Marine Corps)

3.12 Recently Retired / Legacy Predecessor Systems (Reference Summary)

The systems below are not current systems of record but are frequently referenced because their data, terminology, or residual open-year balances persist, or because they were formally retired within roughly the last five years.

3.13 VERIFIED FINDING: The DDRS General-Ledger Feeder Landscape Is 20+ Systems

This section directly addresses and confirms a specific completeness check: whether more than 20 general-ledger-bearing systems currently host or continue to send GL records into the Defense Departmental Reporting System (DDRS), DFAS's consolidation platform for Component and DoD Agency-Wide Financial Statements. The finding is confirmed — and the authoritative source is new: DoD Inspector General Report No. DODIG-2026-013, “Audit of the DoD's Management of Data Remaining After the Retirement of DoD Financial Management Systems” (November 19, 2025), the most current unclassified accounting of DoD's financial-systems inventory available as of this paper's research.

3.13.1 The department-wide scale, per DoD IG (Nov 2025)

• As of February 2025, DoD used 415 total financial management (FM) systems. Of those, 268 are DoD-owned “major” FM systems; the remaining 147 are owned by other federal/commercial organizations or are gap-filling applications.
• DoD's systems environment as a whole is not compliant with the Federal Financial Management Improvement Act (FFMIA) — a condition DoD has acknowledged since FY2001 — and DoD plans to retire 62 FM systems between FY2025 and FY2031 as part of its path to FFMIA compliance.
• Separately, the DoD OIG's FY2024 financial-statement audit report (DODIG-2025-040) found “Financial Management Systems Modernization” to be a standing material weakness, noting DoD uses “thousands of systems, hundreds of which were relevant to internal controls over financial reporting.”

3.13.2 GL-bearing systems specifically confirmed active in or feeding DDRS

Restricting the count to systems that hold or held general-ledger trial-balance data specifically (as opposed to the broader universe of travel, payroll, disbursing, and other subsidiary systems), the following 22 systems are individually documented in DFAS/DoD IG source material as either (a) a current system of record actively posting GL trial balances into DDRS, or (b) a retired system whose GL balances DFAS confirmed are still being reported and adjusted within DDRS as of Q1 FY2025 — exceeding the 20-system threshold:

Not counted in the 22 above, but part of the same DDRS data ecosystem, are 57 separate “obsolete DFAS files” (non-system data files DFAS historically used to report or adjust DDRS balances, e.g., TTBCASH for Fund Balance with Treasury) that DoD IG separately identified as still contributing reportable and/or adjusted data into DDRS as of Q1 FY2025 — meaning the true count of distinct “things” feeding or having fed GL-relevant data into DDRS, systems plus files, is closer to 80 when both categories are combined. This paper counts only genuine systems (not files) against the “20+” threshold, which the systems list alone clears.

3.13.3 Why the number matters: DoD IG's core finding

The November 2025 DoD IG audit's central finding is not merely that many systems have fed DDRS over the years — it is that DoD has not cleanly separated “active, Treasury-reportable” data from “dead” data left behind by retirement. Specifically, for Q1 FY2025:

• DDRS reported and adjusted balances associated with the 10 retired FM systems and 57 obsolete files identified above, totaling $4.2 trillion (net) in balances — 96.6% of which were not required for Treasury reporting and had no financial-reporting purpose, yet were still being carried and adjusted.
• DDRS processed over 490,000 accounting adjustments to these retired systems/files in the quarter alone; 65% of them (about 320,000) were unnecessary because they touched balances with no Treasury-reporting requirement.
• A further 2.2 million DDRS accounting adjustments in the same quarter did not identify which system or file they affected at all, making later cleanup materially harder — the STARS example above is the report's own illustration of this problem.
• A DFAS system-change request to archive these unneeded legacy balances was originally developed in FY2017 and, as of July 2025, still had not been implemented — OUSD(Comptroller)/CFO's own management response in the report now targets completion around September 30, 2027.

The practical upshot for anyone doing DoD FM system-architecture work: the “20+ systems feeding DDRS” framing is accurate and probably conservative once obsolete files are included, and it is a live audit-remediation issue, not merely historical trivia — it is explicitly cited by DoD IG as an obstacle to the department's legally mandated goal of an unmodified (clean) audit opinion by FY2028 (per the FY2024 National Defense Authorization Act).

3.13.4 Detailed accounting of the “closer to 80” figure

This subsection unpacks precisely how the “close to 80” figure in this paper's earlier draft was constructed, using the full text of DODIG-2026-013 (obtained directly from media.defense.gov after the prior draft was written). The short version: DoD IG's own audit scope produces 67 legacy “items” still touching DDRS as of Q1 FY2025 (10 systems + 57 files); adding the 8 currently active GL systems of record and 4 additional historically retired systems this paper separately documents (which fall outside DoD IG's specific Q1 FY2025 data pull) brings the total distinct GL-relevant items discussed in this paper to 79 — hence “closer to 80.” The two figures answer two different questions, and it's worth being precise about which is which.

(a) DoD IG's own count: 10 systems + 57 files = 67

DoD IG drew a deliberate technical distinction that this paper initially blurred: “FM systems are owned by the DoD Components, while obsolete files are used by DFAS in the financial reporting process; therefore, the number of obsolete files is identified separately from FM systems” (DODIG-2026-013, p.6, footnote 4). In other words:

• 10 retired FM systems — full applications that a Military Department, Defense Agency, or field activity once owned and operated as its accounting system of record: DBMS, DWAS, FAS, IMPS/NRL, MSCFMS, SOMARDS, STARS, STOCK, WAAS, and STATE (this is DoD IG's Figure 4, reproduced in full in Section 3.13.2 above). DoD IG explicitly notes “STOCK” and “STATE” are proper system names, not acronyms.
• 57 obsolete DFAS files — not standalone systems at all, but individual data files DFAS itself used internally to report or adjust specific DDRS balances (for example, a Fund-Balance-with-Treasury file rather than a full accounting application). DFAS stopped actively using each file as its underlying business process changed, but never purged the balances the file had already contributed to DDRS. The report names exactly one of the 57 as a worked example — TTBCASH, a file DFAS used to report Fund Balance with Treasury balances until it stopped in FY2018 without zeroing out the balance; DFAS told the IG that one accountant worked full-time for over nine months just to research TTBCASH's remaining Defense Health Agency balances, and that unresolved research materially contributed to the FY2024 DoD Agency-Wide Fund Balance with Treasury material weakness. The other 56 files are not individually named anywhere in the public report.
• 10 + 57 = 67. This is DoD IG's own audit universe: every retired FM system and every obsolete DFAS file with data flowing into or being adjusted within DDRS in the single quarter (Q1 FY2025) that the audit examined.

(b) This paper's broader count: 22 systems (including active ones) + 57 files = 79

Section 3.13.2's system list of 22 is broader than DoD IG's 10 because it also includes systems that are outside the scope of what DoD IG's audit was measuring:

• 8 systems that are currently active systems of record (GFEBS, Navy ERP, DEAMS, DAI, DLA EBS, LMP, SABRS, CEFMS) — DoD IG's audit was specifically about retired systems and obsolete files, so active systems were never going to appear in its Figure 4, even though they are unambiguously part of the same DDRS-feeding ecosystem this paper is mapping.
• 4 additional historically retired systems this paper documents from other sources (STANFINS, DIFMS, Cabrillo, GAFS/GAFS-BQ) that do not appear in DoD IG's Figure 4. The most likely explanation, though DoD IG does not say so directly, is that these systems' final balances were already fully migrated or zeroed out via the “zero-fill” approach (see Section 3.13.5 below) before Q1 FY2025, so they simply had nothing left in DDRS for the audit to flag — unlike STARS and SOMARDS, which used the “point-forward” approach and therefore still had balances the IG's data pull could see.
• 22 (this paper's system count) + 57 (DoD IG's obsolete-file count, unchanged) = 79, which is the basis for “closer to 80.”

Two honest caveats on this reconciliation. First, this paper cannot independently confirm that STANFINS, DIFMS, Cabrillo, and GAFS truly have zero remaining DDRS balances — that is an inference from the fact that DoD IG's Figure 4 (which was built from actual DDRS data, not merely a historical systems list) does not include them, not a fact stated anywhere in the report. Second, DoD IG's 57 obsolete files are a Q1 FY2025 snapshot; the exact count could shift release to release as DFAS's planned archiving system-change request (targeted for September 30, 2027) is implemented. Treat “~80” as a well-sourced order-of-magnitude figure that combines two genuinely different countable categories (systems vs. files) rather than a single number DoD publishes anywhere as such.

3.13.5 Why systems 8–22 didn't get a full GFEBS-style profile initially — and what's added below

Section 3 profiled GFEBS, Navy ERP, DEAMS, DAI, STARS, DLA EBS, GCSS-Army, LMP, GCSS-MC, and SABRS in depth because each is (a) a current or recent primary system of record for an entire Military Department or Defense Agency, and (b) the subject of substantial public documentation — dedicated program office websites, GAO/DoD IG deep-dive reports, and vendor case studies — sufficient to responsibly populate a technology/scope/module/status profile. The 14 systems newly surfaced in Section 3.13 are almost all much narrower in scope (a single command's working-capital fund, a single Defense field activity's allotment accounting, or a category of retired data rather than a living program) and are documented mainly as line items in GAO/DoD IG appendices, DFAS acronym lists, and Privacy Impact Assessments — not as programs with their own public-facing technical architecture documentation. That is a genuine difference in source availability, not an editorial judgment that they don't matter; several of them (STARS above all) turned out to be materially important to the audit story. Section 3.14 below adds a profile for each newly identified system where enough public information exists to say something specific and sourced, and is explicit about which ones remain thinly documented in open sources.

3.14 Extended Profiles: The Newly Identified GL Systems

3.14.1 CEFMS / CEFMS II — Corps of Engineers Financial Management System

3.14.2–3.14.9 Retired Legacy GL Systems Named in DODIG-2026-013

The eight systems below are documented almost exclusively as line items in the DoD IG's November 2025 audit (Figure 4 of that report) and in scattered DFAS/DTMO acronym references. Open-source reporting does not provide the technology stack, module architecture, or user-scale figures for these the way it does for GFEBS or DEAMS — which is itself part of the DoD IG's finding (these systems are old enough, and narrow enough in scope, that even DFAS's own documentation of them is thin). Profiles below state plainly what is and is not known.

The thinness of public documentation on these eight systems is itself a data point worth taking seriously: it illustrates the DoD IG's underlying concern in DODIG-2026-013 — that DoD's institutional knowledge of exactly what these retired systems were, who owned them, and what their balances represent has eroded to the point that DFAS's own accounting adjustments against them (2.2 million in one quarter, per Section 3.13.3) frequently don't even record which system was affected. If Peter needs authoritative technical detail on any of these eight for an official work product, the appropriate next step is a direct records request to DFAS Indianapolis (which maintains DDRS) or to the OUSD(Comptroller) FM systems modernization office, rather than relying on open-source synthesis.

3.15 GAFS-BL / GAFS-BQ / GAFS-R — General Accounting and Finance System (U.S. Air Force, the DEAMS-adjacent legacy pair)

This is one of the most confusing names in this entire paper, and it deserves to be unpacked precisely: “GAFS” is not one system — it is a paired budgetary-ledger-plus-general-ledger legacy environment that still operates today, in parallel with DEAMS, at Air Force locations DEAMS has not yet reached, and it remains the Air Force's second system that feeds USSGL data directly to DDRS (DEAMS being the first).

3.15.1 “GAFS JV” — what it actually means, and why it's different from a GFEBS journal voucher

The term “GAFS JV” refers to a manual correcting/adjusting journal voucher that DFAS-DE departmental accountants post at the GAFS-R (or DDRS) level to force GAFS-R's reported balances to agree with an external control total — most commonly Treasury's reported cumulative disbursements. A documented example: in FY2004, cumulative Treasury disbursement totals for the Air Force General Fund were $591.7 million more than what GAFS-R showed. DFAS-DE researched the difference and posted a journal voucher adjustment to bring GAFS-R and DDRS into agreement with Treasury, substantially (though not completely) resolving the gap.

This is a fundamentally different kind of “JV” from the ones described in Section 9's GFEBS deep dive. A GFEBS journal voucher is system-generated at the moment a business transaction posts (Section 9.2's six-stage model) and carries the full account-assignment detail of that transaction. A “GAFS JV” in the DFAS-DE reconciliation sense is typically a summary-level, manually researched plug entry made after the fact to close a gap between two already-summarized totals (GAFS-R's trial balance versus Treasury's reported disbursements) — exactly the category of “forced-balance adjustment” that GAO's 2020 accounting-adjustments report (GAO-20-96, cited in Section 7's methodology and Section 3.13.3's DDRS-adjustment findings) singled out as a department-wide reliability concern, because a correcting entry made to agree with a control total, by construction, may not trace to any single identifiable underlying transaction.

3.15.2 The practical question: tracing a DDRS balance back to ABSS source detail for IGT elimination

This directly addresses a specific, practical problem: you are looking at a GAFS-R-sourced balance in DDRS, you need to perform an intragovernmental (IGT) elimination (Section 7.6) on it, and neither the GAFS JV nor the GL-level balance in GAFS-R carries the trading-partner information (the Federal/Non-Federal indicator and specific trading-partner agency code discussed in the SLOA/SFIS material referenced in Section 5) that GTAS needs to match it against the counterparty agency's books. Here is the traceability chain, and an honest account of what is and is not confirmed at each link:

The honest bottom line, stated plainly: this paper can confirm the chain's existence and the join mechanism at the GAFS-R→GAFS-BL layer (the Balance Identifier) with a real citation, and can confirm ABSS is the correct place to look for the original trading-partner-bearing source document based on what ABSS is documented to do — but it cannot hand you exact ABSS or GAFS-BL table/field names, because neither system's internal data dictionary is published anywhere this research could locate. GAO's own language about GAFS-R's “inconsistent interface integrity controls” (Section 3.15, GAO-22-103636) is itself indirect evidence that this exact problem — data elements not surviving cleanly from the obligating document through to the USSGL-level record — is a live, GAO-documented risk, not a hypothetical one. If Peter needs the actual field-level answer for a real elimination working paper, the right next step is a data request to DFAS-DE (GAFS-R's operator) for the GAFS-BL-to-GAFS-R interface control document (ICD) and the ABSS-to-GAFS-BL interface specification, which would be the authoritative source neither GAO nor this paper's open-source research has published.

3.16 Combatant Commands, DISA, DCSA, DeCA, and the Defense Intelligence Community: Who Actually Uses What

This section answers a question the earlier system-by-system profiles left implicit: what general ledger system does a Combatant Command, DISA, DCSA, DeCA, or a DoD intelligence agency like NSA or DIA actually run on? The short, structurally important answer, confirmed across every organization checked below: almost none of them have their own GL system. They ride on whichever system this paper has already profiled that their parent Service or the Fourth Estate's shared Defense Agency platform provides — which is itself a finding worth stating plainly, because it means the audit risks and system architecture already documented in Sections 3–9 apply directly to these organizations rather than requiring a separate technical picture.

3.16.1 Combatant Commands: no COCOM-owned GL system exists

A geographic or functional Combatant Command (CENTCOM, EUCOM, INDOPACOM, AFRICOM, SOUTHCOM, NORTHCOM, SPACECOM, CYBERCOM, SOCOM, STRATCOM, TRANSCOM) is a joint organization, not an accounting entity with its own general ledger. Each COCOM's operations and maintenance (O&M) funding runs through whichever Military Department serves as its executive or administrative agent — and that Service's own ERP (already profiled in Section 3) is the actual system of record. A Defense Security Cooperation University resource management manual gives a directly sourced, COCOM-by-COCOM breakdown for both the Security Cooperation/Foreign Military Sales administrative funding (uniformly DAI across every COCOM) and the O&M funding (which follows the administering Service):

USTRANSCOM is one partial exception, and this paper already covers it in depth (Section 3.4): rather than simply borrowing a parent Service's system, USTRANSCOM co-owns DEAMS with the Air Force as a joint program, and its Transportation Working Capital Fund is “funded predominately with customer orders” (i.e., billing other DoD organizations for airlift/sealift/surface transportation) rather than direct appropriation — consistent with the reimbursable/Order-to-Cash pattern this paper's Section 7.6 IGT framework and Section 9.5 (GFEBS Reimbursables) describe. Notably, USTRANSCOM's Transportation Working Capital Fund is also specifically named in DoD IG's FY2025 audit results (DODIG-2026-032, December 2025) as one of the DoD reporting entities that received a disclaimer of opinion — confirming this paper's Section 3.4 profile is tracking a genuinely live, current audit risk area, not a resolved one.

USSOCOM is a second, more fundamental exception, and it is the specific gap this section was expanded to close. Unlike the geographic COCOMs in the table above, USSOCOM has its own dedicated budget category — Major Force Program 11 (MFP-11), created by the FY1987 NDAA specifically to give USSOCOM direct control over funding special-operations-peculiar equipment, training, and technology, separate from any Military Department's own budget. Under 10 U.S.C. § 167, the USSOCOM commander functions as the “head of an agency” for procurement purposes — authority no other combatant commander holds — and USSOCOM prepares and reports its own audited financial statements under the CFO Act and GMRA, rather than simply having its O&M activity absorbed into a parent Service's statements the way the geographic COCOMs in the table above do. USSOCOM's own FY2023 financial statement reporting package specifically references accounting for certain USSOCOM assets “within General Fund Enterprise Business System – Sensitive Activities (GFEBS-SA)” — the same classified, hardened Army GFEBS instance this paper profiled in Section 3.1, now confirmed to also serve at least part of USSOCOM's reporting, consistent with the classified nature of much special operations activity. USSOCOM's asset accountability is further complicated by a documented MFP-11/MFP-2 (“SOF-peculiar” vs. “Service-common”) ownership-transfer process with the Military Departments and their Theater Special Operations Components — USSOCOM's FY2019 reporting package documents multi-billion-dollar asset-line reclassifications as property was formally transferred to or from the Army, Navy, and Air Force for financial-reporting purposes, and its FY2023 package documents a $373.4 million restatement for Operating Materials & Supplies that had gone unreported at an Army wholesale location entirely.

The remaining functional Combatant Commands — STRATCOM (Offutt AFB, NE), SPACECOM (Colorado Springs, CO), and CYBERCOM (Fort Meade, MD) — were not covered by the DSCU Security Cooperation resource-management manual sourced above, because that manual's COCOM-by-COCOM table is specifically built around the Security Cooperation Organization (SCO) structure geographic commands maintain at embassies, which functional commands do not have. This paper's best-supported inference, consistent with the base-of-assignment-follows-administering-Service pattern documented for the geographic COCOMs, is that STRATCOM's and SPACECOM's O&M funding likely runs through Air Force channels (DEAMS) given their historical Air Force basing and administrative heritage, and CYBERCOM's through Army channels (GFEBS) given its co-location with NSA at the Army's Fort Meade — but this paper did not locate a source with the same direct, COCOM-named specificity as the DSCU manual to confirm any of the three, and states this explicitly as an inference rather than a sourced fact.

The practical implication for anyone working COCOM-level financial issues: a finding, interface problem, or system quirk documented anywhere in this paper's GFEBS (Section 9), DEAMS (Section 3.4), or SABRS (Section 3.11) profiles applies directly and without translation to the corresponding COCOM's O&M accounting, because there is no intermediate COCOM-specific system layer to account for.

3.16.2 DISA: three systems now, not two — corrected

An earlier version of this section described DISA as running two financial systems split cleanly by fund type (WAAS for General Fund, FAMIS for Working Capital Fund). That was incomplete. DISA's property/capital-asset accounting on the General Fund side has since moved onto a dedicated FAMIS General Fund instance — confirmed by an April 2024 Defense Property Accountability System (DPAS, now rebranded Enterprise Logistics Management System/ELMS) release note, which states plainly: “The Defense Information Systems Agency (DISA) now has interface system code ‘AC’ assigned to their Financial Accounting & Management Information System (FAMIS) General Fund (GF). The DPAS to FAMIS interface is used to provide the DPAS customer with an automated feed of their Capital Asset activity to their General Ledger and Cost Accounting modules of FAMIS.” The same release note confirms DISA's capital-asset data had previously been converted through a DAI interface and was being migrated onto this new FAMIS-GF interface instead — meaning FAMIS-GF is a genuinely new (2024), not legacy, addition to DISA's architecture, running in parallel with (not replacing) WAAS.

3.16.3 DCSA: DAI for accounting, NBIS for the operational case-management feeder system that's badly behind schedule

DCSA's Working Capital Fund (one activity group: Background Investigation Services, overseen by the Under Secretary of Defense for Intelligence and Security) follows the standard Fourth Estate accounting pattern documented throughout this paper — DAI is the accounting system of record for DCSA, consistent with every other Defense Agency profiled in Section 3.6. The more operationally significant system for DCSA is not its GL platform but its case-management feeder system: the National Background Investigation Services (NBIS) system, which processes the roughly 2 million background investigations DCSA conducts annually and generates the billing data that flows into DCSA's WCF accounting.

NBIS is a genuinely current, actively tracked problem, not a historical footnote: a House Oversight Subcommittee hearing held June 18, 2026 — essentially concurrent with this paper's research — reviewed NBIS's status directly. GAO testimony at that hearing stated the government is “years late” delivering NBIS, that DoD originally planned full functionality for 2019, that DCSA paused development in 2024 to draft a recovery plan, and that DCSA now projects completion in 2027 or FY2028 — nearly a decade after the original goal — with GAO assessing the latest schedule as still not reliable. Because NBIS is DCSA's primary case-processing and billing-data-generating system, its instability is a direct, ongoing risk to the completeness and timeliness of the billing data that ultimately reaches DCSA's DAI-based accounting and DDRS reporting — the same “feeder system reliability” risk category this paper's Section 7 and Section 9 trace in detail for GFEBS/DTS and GAFS/ABSS.

3.16.4 DeCA: DAI for the general ledger, DIBS/CARTS for the actual grocery-store business

DeCA's Working Capital Fund (two activity groups: Commissary Resale Stocks and Commissary Operations) is the clearest example in this paper of DAI's Re-Sale Accounting capability — added specifically in DAI Increment 3 — being built for one named customer: DeCA. DAI is DeCA's financial accounting and general ledger system of record. Beneath that, DeCA operates its own retail-specific feeder systems that never appear in a Fourth Estate DAI discussion elsewhere in this paper because no other DAI customer runs an actual retail grocery operation:

DeCA's own recent budget justification documents describe “aging business critical systems” with “serious shortcomings,” citing heavy reliance on manual processing, repetitive data entry, and information repository silos as consequences — language that echoes this paper's Section 9.8–9.9 GAFS/ABSS traceability findings closely enough to suggest DeCA's retail-feeder-to-DAI interface is a live candidate for the same kind of trading-partner/completeness research burden documented there, though this paper did not locate a DeCA-specific IGT or trading-partner finding to confirm that directly.

3.16.5 The Defense Intelligence Community within DoD: NSA and DIA are audited as DoD reporting entities, on the same Fourth Estate pattern

A scope clarification matters here: the National Security Agency (NSA) and Defense Intelligence Agency (DIA) are DoD Combat Support Agencies / Defense Agencies that also sit within the broader U.S. Intelligence Community — unlike the Central Intelligence Agency or the Office of the Director of National Intelligence, which are not part of DoD at all and fall entirely outside this paper's scope. NSA and DIA follow the same Fourth Estate financial-management architecture as every other Defense Agency profiled in this paper, and — despite their classified missions — their unclassified financial statements are audited as DoD reporting entities through the same IPA/DoD-OIG process Annex B describes.

The most current, directly sourced evidence: DoD IG's FY2025 DoD Financial Statement Audit results (DODIG-2026-032, released December 19, 2025 — among the most recent DoD audit results available at the time of this paper's research) explicitly identify NSA and DIA, alongside the Defense Advanced Research Projects Agency (DARPA), among the DoD reporting entities that received disclaimers of opinion for FY2025. Per the same audit cycle, disclaimed entities collectively accounted for 43% of DoD's total assets and at least 64% of DoD's total budgetary resources — meaning the intelligence-community-within-DoD agencies are not a small, quarantined risk area but part of the same large-scale evidence and traceability problem this paper documents throughout.

This paper cannot confirm NSA's or DIA's specific underlying accounting platform with the same source-level confidence as the Fourth Estate agencies profiled in Section 3.6 (DAI) — no public GAO/DoD IG source located in this research explicitly names NSA's or DIA's core financial system the way DISA's or DCSA's are named above. Given that both are Defense Agencies subject to the same OUSD(Comptroller)/DLA DAI onboarding pattern documented throughout Section 3, DAI is the best-supported inference, but it should be treated as an inference — consistent with this paper's general practice of flagging confidence level explicitly — rather than a directly sourced fact. Classified elements of NSA's and DIA's financial management (e.g., any Special Access Program-related or SIPR/JWICS-resident financial tracking) are, consistent with Section 4's note on classified financial processing, outside what open-source research can responsibly document, and would require a cleared review to address.

3.16.6 What this section adds to the paper's overall picture

Two structural findings from this section are worth carrying forward into how the rest of this paper is read. First, the DoD financial-systems landscape is even more consolidated at the GL layer than Sections 3–5 alone suggest: Combatant Commands, DeCA, DCSA, and (very likely) the DoD intelligence agencies add zero new general ledger systems to the department's technical footprint — they simply add more reporting entities riding on GFEBS, DEAMS, SABRS, or DAI. Second, the specific operational feeder systems these organizations run (NBIS for DCSA, DIBS/CARTS for DeCA, FAMIS/WAAS for DISA) are exactly where this paper's Section 7 (business-event-to-GL tracing) and Section 9 (interface/traceability deep dives) methodology should be pointed next if Peter needs organization-specific detail beyond what's documented here — the pattern this paper establishes for GFEBS/DTS and GAFS/ABSS traceability research applies directly, feeder system by feeder system, to every organization in this section.

3.17 The Exhaustive Cross-Check: Every DoD Reporting Entity Category, and Whether This Paper Covers It

This section responds directly to a specific instruction: don't just add the systems named so far, go back and build a complete list of DoD entities independently, then cross-check this paper's coverage against it, rather than only reacting to gaps as they're pointed out. GAO's FY2024 balance-sheet auditability review (Section D.6.1, Annex D) confirms DoD's financial statements consolidate information from 67 separate DoD components. This paper does not have access to DoD's own Appendix A consolidation-entity list (the DoD Agency Financial Report's own exhaustive roster, which this research could not successfully retrieve in full), so the cross-check below is built from DoD's own published organizational taxonomy — Military Departments, Combatant Commands, Defense Agencies, and DoD Field Activities — cross-referenced against every entity this paper has profiled by name, with gaps flagged explicitly rather than silently left out a second time.

3.17.1 Military Departments and Services — fully covered

3.17.2 Combatant Commands — now fully covered, with the SOCOM correction

All 11 unified Combatant Commands are now addressed in Section 3.16.1–3.16.2 above: 6 geographic commands directly sourced to the DSCU manual (AFRICOM, CENTCOM, EUCOM, NORTHCOM, INDOPACOM, SOUTHCOM), USTRANSCOM and USSOCOM each covered as distinct, sourced exceptions to the “no COCOM-owned system” rule, and STRATCOM/SPACECOM/CYBERCOM covered with an explicit inference-not-fact caveat. SOCOM was the specific gap flagged, and is now the most thoroughly documented COCOM in this paper outside of USTRANSCOM — appropriately, given it is also the COCOM whose financial architecture is most genuinely distinct from the others.

3.17.3 Defense Agencies — partial coverage, gaps flagged by name

DoD organizes roughly 15–19 organizations as “Defense Agencies” (the exact count varies slightly by source and year as agencies are created, renamed, or consolidated). This paper has profiled some in depth and named others only in passing; the table below is the complete cross-check, not just the gaps:

3.17.4 DoD Field Activities — mostly uncovered, flagged directly

DoD organizes a smaller category of roughly 9 “DoD Field Activities” — generally narrower-mission organizations than full Defense Agencies. This paper's coverage here is the thinnest of any category:

3.17.5 OSD, the Joint Staff, and DoD IG

The Office of the Secretary of Defense (OSD) itself, the Joint Staff (which supports the Joint Chiefs of Staff), and DoD IG are each distinct reporting entities in DoD's consolidation, and each is referenced throughout this paper functionally (OSD via OUSD(Comptroller) as the owner of NGRMS, PBAS/EFD, and DDRS policy; the Joint Staff as an organization whose own RDT&E budget line appears in Volume 5 budget-justification materials cited in Annex C; DoD IG as the audit-oversight body central to Annex B) without ever being profiled as a financial-system owner in its own right. This paper's best inference is that OSD and the Joint Staff's own General Fund accounting runs through WAAS or a comparable Fourth-Estate-shared system (the same pattern as DISA's General Fund, per Section 3.16.2), given both are Pentagon-headquartered, Washington-Headquarters-Services-adjacent organizations — but this was not independently confirmed and is stated here as an inference, not a fact.

3.17.6 Summary: what this cross-check actually changed

Net result of this exercise: SOCOM (explicitly flagged) is now one of the most thoroughly documented COCOMs in this paper, with a genuinely new, sourced finding (GFEBS-SA usage, MFP-11's structural distinctness) rather than a placeholder. FAMIS-GF is now correctly documented as a third, newly-stood-up DISA system rather than folded incorrectly into the existing WAAS/FAMIS-WCF pair. Beyond those two corrections, this cross-check surfaced roughly a dozen additional named gaps (DHA, MDA, DTRA, NGA, NRO, DSCA, DARPA, PFPA, SDA, DCAA, DTIC, DHRA, USUHS, DPAA, DMA, Space Force, OSD/Joint Staff) that this paper is now explicit about rather than silently omitting. For nearly all of them, this paper's honest position is the same: the Defense-Agency-wide pattern documented in Section 3.6 makes DAI the best-supported inference for their underlying accounting system, but that inference was not individually confirmed for each one, and is flagged as such rather than presented with false confidence.