DDRS is the Defense Departmental Reporting System, the DoD departmental reporting application that DFAS uses to produce Component and agency-wide reports. DDRS-B produces monthly budget execution reports, DDRS-AFS produces the financial statements and notes, and the Data Collection Module gathers data call amounts.
DDRS blueprint for DoD financial statement reporting
DDRS / Defense Departmental Reporting System Blueprint
Explore DDRS as the DoD financial reporting layer for component trial balance intake, USSGL/TAS validation, GTAS tie-outs, consolidation, intragovernmental eliminations, top-side adjustments, statements, notes, and audit support.
6
Core DDRS lineage scenarios
Feeder -> DDRS-B -> DDRS-AFS -> GTASSystem profile
What it is, who uses it, and why it matters
DoD reporting teams, component financial managers, DFAS/shared-service support, trial-balance owners, Treasury/GTAS reporting users, eliminations teams, statement preparers, and auditors rely on DDRS data or outputs.
It ingests SFIS trial balances and legacy feeder files, crosswalks legacy Report Data Types and General Ledger Account Codes to USSGL, applies edits and tie points, records categorized journal vouchers, and produces the SF 133, the financial statements, note schedules, and the data reported to Treasury GTAS.
Active. DoD FMR Volume 1 requires every accounting system to report to DDRS. DoD IG reported in November 2025 that DDRS still carried balances from 10 retired systems and 57 obsolete files, with an archiving change targeted for September 30, 2027.
It gives DoD a controlled statement-production path from component accounting systems to consolidated financial reports, Treasury reporting, disclosure schedules, and audit evidence.
The blueprint models 6 DDRS source/partner categories; authoritative interface counts require DoD reporting records.
Component ERP Trial BalancesLegacy Accounting SourcesWorking Capital Fund SourcesTreasury / GTAS / IPACIGT / Trading Partner DataAudit / Component Support Packages
Clickable architecture map
End-to-end flow: business event to financial statement
Cards in the selected DDRS scenario path are highlighted. Click any card to inspect fields, T-codes, audit questions, and risks.
Source
Component Trial Balance Sources
ERP, legacy accounting, WCF, general fund, Treasury, GTAS, and audit-support sources that feed DoD financial reporting.
DDRS
DDRS Processing
Trial-balance intake, validation, crosswalk, consolidation, eliminations, adjustments, statement generation, and note support.
Detail
Reporting Detail
Entity, TAS, USSGL, trading partner, statement line, adjustment, elimination, schedule, and evidence detail.
Control
Validation and Reconciliation
USSGL/TAS edits, GTAS tie-outs, IGT elimination controls, top-side adjustment controls, and audit reconciliations.
Outputs
Reporting Outputs
Component and consolidated reports, AFR/PAR statements, notes, variance analysis, audit schedules, and submission packages.
Statements
Financial Statements and Notes
SBR, SNC, balance sheet, changes in net position, custodial/activity schedules, notes, and disclosure assertions.
Scenario lineage explorer
Legacy Feeder File to SF 133 through DDRS-B
Traces a legacy feeder file through DDRS-B import, crosswalk, journal voucher control, and budget execution reporting.
->
->
->
->
->
Business flow
- A legacy accounting system submits a feeder file with records identified by Report Data Type or General Ledger Account Code.
- DDRS-B logs the file, then crosswalks each record to USSGL budgetary and proprietary accounts.
- Feeder record detail keeps the source code, attributes, and crosswalk rule behind each trial balance line.
- Edits and tie points raise differences. Journal vouchers are categorized, approved by threshold, and logged.
- DDRS-B produces the SF 133 and related budget execution reports and the export file to DDRS-AFS.
- The Statement of Budgetary Resources is reconciled to the SF 133.
AI / audit exception tests
- feeder file missing or not retained
- record count differs from source
- crosswalk rule not approved
- JV approved below threshold
- SF 133 to SBR difference unexplained
Data model and tables
Where DDRS data lives and how the pieces join
Logical records reconstructed from public process descriptions. The physical schema of this system is not public, so names below are descriptive and are not table names.
| Table or record | Area | Holds | Key fields | Links to |
|---|---|---|---|---|
| Feeder file | DDRS-B intake | One file per source system and period, with record count and control total | File, source system, period | Feeder records |
| Feeder record | DDRS-B intake | Balance by TAS and Report Data Type, General Ledger Account Code, or DoD SCOA account | File, line | Crosswalk rule |
| Crosswalk rule | DDRS-B processing | Mapping from a legacy code to budgetary and proprietary USSGL accounts | Source code, attributes | Trial balance line |
| Trial balance line | DDRS-B processing | Unadjusted ending balance | Entity, period, TAS, account, attributes | Adjusted trial balance |
| Journal voucher and lines | Adjustment | Category A to M, system or manual, root cause, preparer, approver | JV number, line | Adjusted trial balance |
| Adjustment logs | Adjustment | Journal Voucher, Feeder Trial Balance, Pre-Closing, and Undistributed logs | Log type, period | Journal vouchers |
| Data call (DCM) | DDRS-AFS input | Amounts collected outside accounting systems | Call, entity, period | Category M journal voucher |
| Elimination pair | DDRS-AFS processing | Buyer and seller balances by trading partner | Entity, partner, category | Category C journal voucher |
| Statement line map | DDRS-AFS processing | USSGL account and attributes to statement line | Statement, line, account | Statement and note amounts |
| GTAS bulk record | Treasury output | 98-character adjusted trial balance record with 33 fields | Fiscal year, period, TAS, USSGL account, attributes | Treasury GTAS |
Join paths for tracing a balance to its source
- Statement line to adjusted trial balance: statement crosswalk on USSGL account and attributes.
- Adjusted to unadjusted trial balance: same keys. The difference equals the logged journal vouchers.
- Unadjusted trial balance to source ledger: entity, TAS, DoD SCOA account, attributes.
- GTAS record to adjusted trial balance: TAS components and six-digit USSGL account.
Audit lens
Where the AI UoT analyzer should watch
These are the places where completeness, accuracy, timeliness, and traceability commonly break.
Completeness
Source events missing from the ERP, subledger items not posted to GL, or financial statement balances without supporting populations.
Traceability
Broken reference keys across feeder, interface, subledger object, GL document, trial balance, and statement line item.
Timing
Authorization, receipt, invoice, voucher, payment, and GL posting dates crossing accounting periods without appropriate accrual or adjustment.
Supportability
Transactions posted to GL without valid approval, contract, receipt, invoice, voucher, asset record, or other audit evidence.
Enterprise infrastructure
Support services that make the blueprint work
Trial Balance Governance
Component submission calendars, load batches, version control, entity coverage, source-system tie-outs, and period-end re-submission control.
Edit and Crosswalk Controls
USSGL, TAS, reporting attributes, normal balances, statement-line mapping, GTAS edits, crosswalk versioning, and override approvals.
Eliminations and IGT
Trading partner validation, buyer/seller pairing, IPAC/G-Invoicing tie-outs, elimination entries, difference aging, and disclosure support.
Adjustment Governance
Top-side adjustment rationale, support files, preparer/reviewer/approver trail, debit/credit validation, versioning, reversal, and close impact.
Statement and Note Production
AFR/PAR statements, note schedules, variance explanations, report reproducibility, leadership review, and publication tie-outs.
Audit Evidence
Statement-to-source reconciliations, trial balance populations, adjustment packages, component certifications, sample support, and evidence retention.