DEAMS is the Defense Enterprise Accounting and Management System, modeled here as the Department of the Air Force Oracle-based financial-management environment.
DEAMS blueprint for Air Force and Space Force financial management
DEAMS / Defense Enterprise Accounting and Management System Blueprint
Explore DEAMS as a representative Oracle-based Department of the Air Force financial-management system, connecting DAF source systems, procure-to-pay, reimbursables, cost accounting, assets, SLA, GL, Treasury reporting, and statement support.
6
Core DEAMS lineage scenarios
Source -> SLA -> GL -> GTASSystem profile
What it is, who uses it, and why it matters
Air Force and Space Force financial managers, resource advisors, budget users, acquisition/payment partners, DFAS and reporting stakeholders, and auditors rely on DEAMS outputs.
It supports budget execution, procure-to-pay, travel accounting, reimbursables, cost accounting, assets, SLA, GL, Treasury reporting, and statement support.
Operational DAF financial-management system; this page uses public information and Oracle federal-financial process patterns rather than claiming exact DEAMS configuration.
It standardizes DAF accounting, connects source events to GL/reporting, and supports auditability across Air Force and Space Force financial operations.
The blueprint models 7 major DEAMS feeder/source categories.
DTSWAWF / PIEESPS / EDADCPS / PayrollMission / Logistics SourcesG-Invoicing / IPACTreasury / Disbursing
Clickable architecture map
End-to-end flow: business event to financial statement
Cards in the selected DEAMS scenario path are highlighted. Click any card to inspect fields, T-codes, audit questions, and risks.
Source
DAF Source / Feeder Systems
Air Force, Space Force, DFAS, contracting, travel, payroll, logistics, and Treasury-facing systems where financial business events originate.
DEAMS
DEAMS Core Business Processes
Oracle-based federal financial management processes for budget execution, procure-to-pay, reimbursables, cost accounting, assets, and close.
Detail
Detailed Transaction Objects
Document, subledger, interface, and reconciliation records that preserve Universe of Transactions evidence before GL summarization.
Accounting
Accounting Layer
Oracle SLA, USSGL budgetary/proprietary accounting, GL journal lines, account derivation, and drillback controls.
Reporting
Reporting / Treasury Layer
DEAMS reporting, DDRS, GTAS, CARS/FBwT, USSGL crosswalks, G-Invoicing/IPAC, and external reporting outputs.
Statements
DAF / DoD Financial Statements
Department of the Air Force and DoD statement outputs supported by reconciled trial balances, note schedules, and audit evidence.
Scenario lineage explorer
Requisition -> Award -> Receipt -> Invoice -> Payment
Shows how DAF procurement activity moves from demand and award evidence through DEAMS purchasing, AP, SLA, GL, reporting, and statement support.
->
->
->
->
->
->
->
->
->
->
->
Business flow
- Requisition demand and contract award/modification evidence establish the procurement requirement.
- DEAMS creates PO/agreement lines, shipments, distributions, and budgetary control records.
- PIEE/WAWF provides receipt, acceptance, and invoice evidence.
- AP validation, matching, holds, approvals, and payment-ready processing create accounting events for SLA.
- SLA creates subledger journal entries and transfers supported accounting to GL.
- Trial balance, GTAS, and statement lines rely on supported AP, expense, asset, and outlay populations.
AI / audit exception tests
- award without obligation
- invoice without receipt or acceptance
- SLA event not accounted
- payment without AP support
- subledger-to-GL transfer mismatch
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
Oracle Master Data
Suppliers, customers, organizations, projects, programs, funds, accounts, assets, and DAF accounting strings.
Interfaces & Controls
Batch files, APIs, accepted/rejected records, control totals, suspense/error queues, and source-to-target reconciliation.
Workflow & Approvals
Requisition, purchase, invoice, journal, travel, reimbursable, asset, and close-adjustment approval routing.
Security & Access
Role-based access, segregation of duties, privileged access, system audit logs, and sensitive transaction monitoring.
Period Close
Interface resolution, subledger close, GL close, reconciliations, trial-balance extracts, and reporting package controls.
Data Governance
Authoritative sources, data definitions, SFIS/USSGL attributes, lineage, validation rules, stewardship, and issue remediation.
Modernization
Cloud hosting, integration modernization, reporting automation, audit analytics, and AI-enabled UoT testing.