DDRS and GTAS Reporting

This section closes the loop on the reporting side of the ten-stage backbone (Section 7): how a Component's trial balance actually becomes DDRS output, how DDRS output becomes GTAS output, how SF-133 and the audited financial statements get produced from that chain, and — addressing the specific question asked — an honest, sourced account of where Advana currently stands and what could and could not be confirmed about OneStream.

11.1 DDRS: the business process, current state

DDRS (Defense Departmental Reporting System) is operated by DFAS Indianapolis and has two functional halves that a new employee should keep distinct, because they run on different cycles and produce different outputs:

A clarification on “1002” specifically, since it was named directly: this paper found one indirect reference to an “AR(M) 1002” report in a DoD IG audit of DFAS Indianapolis's DDRS-B import process, described there as an internal report distinct from the trial-balance feeder files DDRS-B actually accepts for processing (the audit specifically flagged that some transactions were showing up in AR(M) 1002 output rather than in the accepted trial-balance feeder files, which was itself part of the audit finding). This paper cannot confirm 1002's full name, owning Component, or current status with confidence — it appears to be a legacy Army-series management report adjacent to, but distinct from, the SF-133 that GTAS/Treasury actually requires. Treat “1002” and “SF-133” as two different things: SF-133 is the official, Treasury-mandated budget-execution report generated from GTAS-bound data; “1002” (as best this research can confirm) is an older, narrower, Component-internal report that predates or runs alongside the modern DDRS-B/GTAS pipeline. If Peter is working with a live “1002” report today, verifying its current definition directly with DFAS Indianapolis is the right move — this paper's sourcing on that specific report is thin.

11.2 GTAS: the business process, current state (per a GAO report published June 11, 2026)

GTAS (Governmentwide Treasury Account Symbol Adjusted Trial Balance System) is Treasury's Bureau of the Fiscal Service platform, and a GAO report released just weeks before this paper's research — the first in a planned GAO series specifically on how Treasury can improve GTAS — gives the most current authoritative description available:

• Submission mechanism: agencies (DoD, via DDRS/DFAS) submit a standardized bulk-file Adjusted Trial Balance (ATB) covering both budgetary and proprietary data simultaneously, generally on a monthly cycle (the GTAS Reporting Window Schedule is published annually by fiscal year).
• Validation: every submission is checked against two attribute sources — the USSGL Attribute Table (is this a valid attribute combination for this USSGL account) and the Treasury Account Symbol/Super Master Account File (SMAF, itself a consolidation of the legacy Federal Agencies' Centralized Trial-Balance Systems I and II). All validations are treated as fatal (a failed validation blocks the submission, not merely flags it).
• Reconciliation edits: beyond validation, GTAS runs edits comparing agency trial balances against USSGL rules and against data from other authoritative sources — specifically named by GAO's June 2026 report as the Central Accounting Reporting System (CARS), the DATA Act Broker, Government Invoicing (G-Invoicing, the IGT platform from Section 7.6), and OMB MAX.
• SF-133 generation: Treasury's own GTAS help documentation treats SF-133 production as something an agency runs against its already-submitted GTAS data (“What should I keep in mind when running my SF133 report?”) — confirming SF-133 is a report generated from the GTAS submission, not a separately compiled document.
• Output: Treasury and OMB use GTAS data to compile the annual Financial Report of the U.S. Government and to support the President's Budget; GAO's own annual audit of the U.S. government's consolidated financial statements (mandated by the Government Management Reform Act of 1994) relies on GTAS data quality directly.

This GAO report (GAO-26-107961) is explicitly the first of a planned multi-report GAO series specifically examining how Treasury can improve GTAS — meaning GTAS itself is a current, active area of federal (not just DoD) audit and modernization scrutiny as of mid-2026, independent of anything DoD-specific.

11.3 Advana's role in this chain — and a major, very recent change in status

Advana (Section 5.3) does not replace DDRS or GTAS in this reporting chain — it sits alongside them as a cross-system data and reconciliation layer. DoD's own Financial Management Regulation formalizes this: Volume 1, Chapter 10, “ADVANA — Common Enterprise Data Repository for the Department of Defense,” directs Components to use the Advana Feeder-to-General-Ledger Reconciliation Audit Workbooks for monthly reconciliations between disbursing/obligation/funding/entitlement systems and general ledger systems, and the General-Ledger-to-Unadjusted-Trial-Balance Reconciliation Audit Workbooks for quarterly reconciliations between GL systems and their resulting trial balances — i.e., Advana's official, current role is reconciliation support feeding into the DDRS/GTAS process described above, not replacing either system.

That said, Advana's status is genuinely in flux right now, more so than at any point since its creation, and this paper found three concrete, very recent (within roughly the last six months) developments worth flagging directly:

• Governance transfer: as of early 2026, Advana's financial-management elements are being transferred back to OUSD(Comptroller) from the Chief Digital and Artificial Intelligence Office's Research & Engineering directorate, which will retain operational control of the broader platform — a structural split between who owns Advana's financial-reporting function versus who runs the underlying platform.
• Omission from the FY2025 Agency Financial Report: for the first time since Advana's creation, DoD's FY2025 AFR does not mention Advana at all, and replaced its usual “Audit Overview” section with a new “Strategic Overview” that instead warns DoD's “failure to modernize the financial management systems environment increased the risk” of not achieving a clean audit opinion. A senior department official attributed the omission to aligning the AFR's management-discussion-and-analysis section with new Statement of Federal Financial Accounting Standards No. 64 (SFFAS 64, a 2024 accounting-standards change), but outside observers have questioned whether the omission also reflects doubts about Advana's efficacy.
• An adverse SOC-1 opinion: DoD confirmed that Advana's fiscal year 2025 System and Organization Controls 1 (SOC-1) audit — the audit that evaluates whether a service organization's controls are reliably designed and functioning to protect data and ensure accurate financial statements — came back adverse, and that officials are working to remediate the identified control deficiencies. An adverse SOC-1 opinion is the least favorable outcome possible on that audit type; the underlying report is Controlled Unclassified Information and was not made public.
• GAO's own framing: a separate May 2023 GAO report (GAO-23-105784) had already found that Advana “has not been fully implemented DOD-wide” and that, while it collects and stores feeder-system data, it “does not yet enable its users to perform effective FBWT reconciliations” department-wide (the Army specifically was cited as using Advana for its own FBWT reconciliation, implying other Components were not yet doing so as effectively); Advana received consecutive modified-opinion service organization reports for FY2020 through FY2022 as well, for access-control and segregation-of-duties deficiencies — so the FY2025 adverse opinion continues a pattern rather than representing an isolated new problem.

Net assessment, stated plainly: Advana is real, is DoD's officially designated cross-system reconciliation and data layer per the FMR, and genuinely does stream real-time data from GFEBS and GCSS-Army (Section 3.8). But as of this paper's mid-2026 research, it is simultaneously undergoing a governance transfer, was omitted from the department's own flagship annual financial report for the first time ever, and just received the worst possible outcome on the specific audit (SOC-1) that certifies whether its controls can be relied on for financial reporting. “Advana produces GL-to-TB-to-… reporting” is DoD's stated intent and official FMR-directed role, but it is not, as of mid-2026, a fully proven, department-wide-reliable replacement for the DDRS/GTAS process described in 11.1–11.2 — it is best understood right now as a reconciliation and analytics layer running alongside that process, with its own unresolved control problems, rather than a mature “one system that replaces the old pipeline.”

11.4 OneStream: what could and could not be confirmed

OneStream is a real, commercially significant corporate-performance-management (financial close, consolidation, planning, and reporting) platform, and it does have credentials relevant to federal/DoD use: it holds FedRAMP High authorization (achieved January 2025, having held FedRAMP Moderate since 2018) and DoD Impact Level 4 (IL4) authorization, and OneStream's own marketing claims more than 90 government-agency customers government-wide. Functionally, a platform like OneStream is built to do exactly the kind of thing the question describes — consolidate GL data from multiple source ERPs (its marketing specifically cites pre-built connectors to Oracle, SAP, and Microsoft Dynamics, all of which are directly relevant given GFEBS/Navy ERP/GCSS-Army run on SAP and DAI/DEAMS run on Oracle EBS) into a single trial-balance-to-financial-statement consolidation layer, with automated intercompany/intragovernmental-style eliminations.

This paper could not find a specific, sourced confirmation that DoD or DFAS has selected, piloted, or contracted for OneStream as a DDRS or GTAS replacement, or as part of the Advana modernization described in 11.3. Everything in the paragraph above is accurate about OneStream as a company and product, but the connection to DoD's specific GL-to-TB-to-financial-statement reporting chain is this paper's informed inference about platform fit, not a confirmed DoD program of record. If Peter has heard about a specific OneStream initiative at DoD/DFAS — a pilot, a task order, an RFI — that is very plausibly real and simply not yet reflected in the public GAO/DoD IG/press reporting this research could locate as of mid-2026; a targeted SAM.gov contract-award search or a direct question to OUSD(Comptroller)'s systems modernization office would be the right next step to confirm or deny it, rather than this paper asserting a connection it cannot source.

11.5 Putting it together: the honest current-state answer

To directly answer “are 1002/SF-133 being produced in Advana or OneStream”: as of mid-2026, no — SF-133 is produced from GTAS-bound data (Section 11.2), which is fed by DDRS-B (Section 11.1), which is fed by Component trial balances from the GL systems this entire paper catalogs. Advana sits alongside that chain as a reconciliation and analytics layer with an official, FMR-documented role (11.3) but is not, based on everything sourced in this paper, currently the system of record that produces SF-133 or the audited financial statements — and its own current audit status (an adverse FY2025 SOC-1 opinion) is itself a reason it would be premature to treat it as a finished replacement pipeline even if that is the direction of travel. OneStream is a plausible, credentialed commercial candidate for a future DoD consolidation layer, but this paper found no confirmed evidence it has been adopted for that role yet. The honest state of play is: DoD's leadership has publicly signaled, in the FY2025 AFR itself, that the financial-management systems environment still needs to modernize to reduce audit risk — which means this entire area (DDRS's eventual replacement, GTAS's own improvement program per GAO's new report series, and Advana's next chapter after its governance transfer) is genuinely unsettled and worth checking again in another 6–12 months rather than treated as resolved.