Platform reference

Legacy, Custom, Treasury, and Analytics Platforms

How status-of-funds legacy systems differ from a transaction-level general ledger, what is public about CEFMS, MOCAS, the disbursing systems, and PIEE, and how the Treasury systems and Advana fit around the ERPs.

8

Numbered tables

1 diagram

1. Two kinds of accounting system

The SAP and Oracle ERPs post a balanced debit and credit for every business event. Most legacy DoD accounting systems do something different. They keep a record per obligation document and update stage amounts on it. That design answers the question of how much of an allotment is left. It does not produce a general ledger.

Table L-1Transaction-level general ledger compared with a status-of-funds system
TopicERP general ledgerStatus-of-funds system
Unit of recordA balanced document with debit and credit linesA document record with stage amounts: committed, obligated, accrued, paid
USSGL accountsPosted on every line when the event occursNot stored. Derived later by crosswalk.
Proprietary accountsPosted with the budgetary entryPartly or not captured
Trial balanceSum of posted linesBuilt in DDRS-B from feeder file totals
Drill-downBalance to line to source document inside one databaseBalance to feeder file to source record, across systems
FFMIA statusCan complyCannot comply at the transaction level, per DoD IG
Typical technologyRelational database with a commercial applicationMainframe or rehosted batch programs with fixed-format records
Figure L-1Logical model of a status-of-funds system and its conversion to a USSGL trial balance
1 : N1 : NsummarizeLegacy status-of-funds systemConversion in DDRS-BResultFUND_CITEappropriation, limit,fiscal year, allotmentauthority receivedauthority distributedDOCUMENT_RECORDdocument numberfund cite, object classvendor or payeecommitment amountobligation amountaccrued expenditure unpaidaccrued expenditure paidTRANSACTION_HISTORYdocument number, sequencetransaction type codeamount, date, batchinput sourceSTATUS_SUMMARYfund cite, periodstage totals byReport Data Type orGeneral Ledger Account CodeFeeder fileOne record per fund cite and RDTor GLACCrosswalkEach stage becomes a budgetaryaccount and, where needed, aproprietary pairEdits and journal vouchersAbnormal balances and missingattributes are corrected byadjustmentUSSGL trial balanceDerived in DDRS. Not posted at thetransaction level in the sourcesystem.

This is a logical pattern drawn from DoD IG descriptions of feeder files, Report Data Types, and General Ledger Account Codes. It is not the schema of any one system.

Table L-2Illustrative crosswalk from accounting stage to USSGL accounts
Stage reported by the legacy systemBudgetary accountProprietary effect
Allotment received4610 Allotments, realized resourcesNone
Commitment outstanding4700 CommitmentsNone
Obligation, undelivered4801 Undelivered orders, unpaidNone
Accrued expenditure, unpaid4901 Delivered orders, unpaid6100 expense and 2110 accounts payable
Accrued expenditure, paid4902 Delivered orders, paid2110 cleared against 1010 Fund Balance with Treasury

Illustrative only. The actual DDRS-B crosswalk rules are maintained by DFAS and are not public.

2. Legacy general ledger systems still in the reporting chain

Table L-3Legacy systems named by DoD IG, with reported balances and retirement dates
SystemOwnerFund Balance with TreasuryTransactionsPlanned retirement
GAFS-RAir Force$222.7 billion5,326,910September 30, 2031
STANFINSArmy$57.2 billion2,058,106September 30, 2031
SOMARDSArmy$16.6 billion18,290September 30, 2025
STARSNavyRetired December 2022Data moved to three systemsRetired

Source: DODIG-2024-047, Table 1 and related text, using fiscal year 2023 data. Dates were plans as of that report. Other pages on this site carry different retirement information for some systems from other sources. Check the current DoD system inventory before relying on a date.

  • DoD IG counted five outdated general ledger systems in fiscal year 2023. They track status of funds and do not post to all accounts with the needed attributes.
  • DoD relied on at least 405 systems and micro-applications outside the general ledger systems, with more than 2,000 interfaces.
  • At least 109 feeder systems were scheduled to remain after fiscal year 2028 or had no retirement date.
  • When a system retires, its balances can remain in DDRS. See the DDRS deep dive, section 8.
  • For system-by-system history, see the research paper appendix, Section 3.
Table L-4Legacy and custom systems in this suite
SystemWhat is public about the platformData it holdsHow it reaches the statements
GAFS-BL, GAFS-RLegacy Air Force accounting. GAFS-R is the rehosted central system.Fund, document, and stage records. Journal vouchers for adjustments.Feeder files to DDRS-B. Runs alongside DEAMS.
ABSSAir Force document preparation and commitment systemRequests, commitments, funding certificationsFeeds commitment and obligation documents to Air Force accounting
SABRSMarine Corps legacy accounting, budgeting, and reporting systemFund control, document records, reimbursablesMigrating to DAI
STARSNavy legacy mainframe family. Retired.Historical balancesResidual balances carried in DDRS
FAMISLegacy accounting family with general fund and working capital fund variantsFund, cost, and billing recordsFeeder to DDRS
CEFMSCustom Army Corps of Engineers system. GAO described two processing centers with a database per Corps site in 2002.Corps general ledger, project cost, and funds controlTrial balance to DDRS
MOCASLegacy contract administration and payment system used by DCMA and DFASContract, line item, accounting classification, shipment, invoice, and payment recordsSends disbursement data to accounting systems. Holds no general ledger.

Platform statements are limited to what public sources say. The existing blueprint pages for each system carry the detailed process model.

3. Entitlement, disbursing, and cash systems

Table L-5Disbursing and cash systems as described by DCMA
SystemFunctionData exchanged
Automated Disbursing System (ADS)DFAS system that processes disbursements and collections and reports payments as check and EFT filesIn: advice of collection, refund acknowledgement, exchange rates. Out: IPAC, collection data, refund data.
Treasury Direct Disbursing (TDD)Sends and receives transactions directly with Treasury systems for commercial supplier disbursementsPayment requests and confirmations
Defense Cash Accountability System (DCAS)Processes and reports DoD disbursements and collections to Treasury. Used for cash management and Fund Balance with Treasury reconciliation.Cash transactions by TAS
Payment prevalidationChecks that an obligation exists before a payment is made, to prevent unmatched disbursementsPrevalidation requests and responses between entitlement and accounting systems
Deployable Disbursing System (DDS)Disbursing in deployed locationsVouchers, collections, and accountability reports

ADS, TDD, DCAS, and prevalidation descriptions follow DCMA Manual 4301-05, Volume 8. DoD IG reported that 21.4 percent of disbursements had converted to Treasury Direct Disbursing as of fiscal year 2022.

The audit significance is the same for all of them. A payment made outside the general ledger system must come back and match an obligation in that ledger. A payment that does not match is an unmatched disbursement. Cash reported to Treasury that the ledger has not recorded is an undistributed disbursement, which DDRS records with a category D journal voucher.

4. PIEE

Table L-6PIEE modules and the evidence each one holds
ModuleHoldsAudit use
WAWFVendor invoices, receiving reports, acceptanceProof of receipt and acceptance for a payment
EDAContracts, modifications, and vouchersProof of obligation
GFP moduleGovernment furnished property recordsExistence and completeness of property held by contractors
IUID registryUnique item identifiersAsset identity
myInvoiceInvoice and payment statusPayment research
MDOModifications and delivery ordersChanges to the obligation
JAMJoint Appointment Module records for contracting officer representative appointmentsAuthority of the person who accepted
SPMSurveillance and Performance Monitoring reportsEvidence that services were performed
Contract CloseoutCloseout checklist, final invoice, releaseSupport for deobligation of remaining funds

Module list follows the PIEE blueprint page on this site.

5. Treasury systems

Table L-7Treasury systems DoD reports to
SystemWhat it isWhat DoD sends or receivesKey identifiers
CARSCentral Accounting Reporting System. Treasury's record of each agency's Fund Balance with Treasury.Payments and collections classified at the time of the transactionTAS, BETC, Agency Location Code
GTASGovernmentwide Treasury Account Symbol Adjusted Trial Balance SystemAdjusted trial balance with budgetary and proprietary accountsTAS, USSGL account, attribute domain values
IPACIntragovernmental Payment and CollectionTransfers between federal trading partnersAgency Location Code, TAS, BETC, document reference
G-InvoicingTreasury system for intragovernmental buy and sell agreementsGeneral terms and conditions, orders, performance, settlement through IPACAgreement number, order number, trading partner TAS

6. Advana

  • DoD FMR Volume 1, Chapter 10 names Advana the common enterprise data repository for the Department.
  • Components use Advana workbooks for monthly feeder-to-general-ledger reconciliations and quarterly general-ledger-to-trial-balance reconciliations.
  • DoD IG describes Advana as the central repository for financial management data, including the notice of findings and recommendations database.
  • In September 2023 the Army reported two real-time replication pipelines from GFEBS and GCSS-Army into Advana using its existing SAP replication services, with plans to federate data to an SAP HANA layer.
  • The same Army article lists the Advana tool stack as Databricks, MLflow, DataRobot, C3 AI, Qlik, Tableau, SageMaker, Collibra, Apigee, and GitLab.
  • Advana does not replace DDRS or GTAS. It sits beside them as a reconciliation and analytics layer. The research paper appendix, Section 11, covers its current governance and audit status.
Table L-8What an Advana transaction universe needs from each platform
PlatformTables to replicate firstReconcile to
SAPBKPF, BSEG or ACDOCA, FAGLFLEXA, FMIOI, FMIFIIT, EKKO, EKPO, EKKN, EKBEFAGLFLEXT totals and the trial balance sent to DDRS
Oracle EBSGL_JE_HEADERS, GL_JE_LINES, GL_CODE_COMBINATIONS, GL_IMPORT_REFERENCES, XLA_AE_HEADERS, XLA_AE_LINES, XLA_TRANSACTION_ENTITIESGL_BALANCES and the trial balance sent to DDRS
LegacyDocument and transaction history files, feeder filesDDRS-B unadjusted trial balance
DDRSUnadjusted trial balance, journal voucher logs, adjusted trial balanceGTAS submission and published statements

Sources

  1. DODIG-2024-047: DoD Plans to Address Longstanding Issues with Outdated Financial Management Systems
  2. DODIG-2012-096: DDRS-Budgetary and Army General Fund feeder files
  3. DCMA Manual 4301-05, Volume 8: Financial Systems and Interfaces
  4. GAO-02-589: Corps of Engineers information security (CEFMS description)
  5. Army.mil: GFEBS and GCSS-Army replication pipelines to Advana (Sept 2023)
  6. Treasury: GTAS
  7. Treasury: intragovernmental transactions, IPAC and G-Invoicing

Educational reference. Standard product tables and public sources only. Not an official DoD, DFAS, SAP, or Oracle publication.