GAFS is modeled as a legacy Air Force accounting/reporting suite with GAFS-BL base-level processing and GAFS-R central/rehost reporting.
GAFS blueprint for legacy Air Force accounting and reporting
GAFS Suite / GAFS-BL and GAFS-R Full Profile Blueprint
Explore GAFS as a legacy Air Force accounting suite, not a SAP or Oracle ERP, connecting GAFS-BL base-level processing, GAFS-R central reporting, source feeds, suspense, journal vouchers, Treasury reporting, and statement support.
4
Core GAFS lineage scenarios
Source -> GAFS-BL -> GAFS-R -> StatementSystem profile
What it is, who uses it, and why it matters
Legacy Air Force finance organizations, base-level accounting users, central reporting support, DFAS/DAF financial managers, and audit teams may rely on historical or transition data.
It handles base-level accounting intake, funds control, suspense/reject resolution, central consolidation, JVs, trial balance, Treasury reporting, and statement support.
Legacy/historical and transition-oriented in this model; public technical detail is limited, so exact current operational footprint requires authoritative DAF/DFAS confirmation.
It preserves legacy accounting history and supports source-to-reporting reconciliation where GAFS activity remains relevant to close, audit, or modernization paths.
The blueprint models 5 GAFS feeder/source categories; this is not a certified interface inventory.
DTS / Travel FeedsContract / Vendor Pay SourcesPayroll / Labor SourcesDisbursing / CollectionsManual Requests / Exception Inputs
Clickable architecture map
End-to-end flow: business event to financial statement
Cards in the selected GAFS scenario path are highlighted. Click any card to inspect fields, T-codes, audit questions, and risks.
Source
Source / Feeder Events
Travel, contract, payroll, disbursing, collection, reimbursable, logistics, and manual source events that create Air Force accounting demand before GAFS processing.
GAFS-BL
GAFS-BL Base-Level Accounting
Base-level legacy accounting intake, editing, funds control, posting, suspense, and local close activity. Public information does not support calling this SAP or Oracle ERP.
GAFS-R
GAFS-R / Central Profile
Central/rehost/reporting profile that consolidates base-level accounting activity, produces trial-balance and status reporting, and supports transition or reconciliation to enterprise reporting.
Accounting
Accounting / Journal Voucher Layer
Budgetary and proprietary accounting, standard general ledger classification, manual journal vouchers, reversals, accruals, eliminations, and close adjustments.
Reporting
Reporting / Treasury Layer
DDRS, GTAS, USSGL crosswalks, CARS/FBwT reconciliation, IPAC/G-Invoicing settlement evidence, management reports, and audit populations.
Statements
Financial Statement Support
Statement of Budgetary Resources, Balance Sheet, Statement of Net Cost, note schedules, and audit support tied back to GAFS source, posting, and reporting evidence.
Scenario lineage explorer
GAFS Journal Voucher Control Path
Shows how a GAFS correction, accrual, reclass, or reversal should move from a real source exception to a controlled JV package, posting, reporting, and audit evidence.
->
->
->
->
->
Business flow
- A source exception, period-end estimate, reconciliation difference, or classification error is identified and documented.
- The preparer assembles source evidence, reason code, accounting classification, debit/credit lines, and reversal instructions when needed.
- Review and approval verify authority, segregation of duties, accounting validity, and period cutoff.
- GAFS-BL accepts or rejects the JV input; exceptions are corrected through controlled resubmission.
- GAFS-R and trial-balance extracts reflect the accepted posting and support DDRS, GTAS, or statement reporting.
- Auditors trace from statement line to trial balance, JV record, approval package, and original source condition.
AI / audit exception tests
- JV without source exception
- debits do not equal credits
- invalid TAS/USSGL
- missing approval
- reversal not posted
- late close adjustment not in reporting package
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
Legacy Platform Profile
Public sources do not support treating GAFS as SAP or Oracle ERP. This blueprint models it as a legacy Air Force accounting/reporting suite with base-level and central/rehost profiles, batch/file interfaces, reports, and reconciliation controls.
Interface Control
Accepted/rejected batch totals, source-to-target reconciliations, suspense queues, load reports, edit reports, and resubmission evidence.
Journal Voucher Governance
Preparer, reviewer, approver, reason code, source support, debit/credit balancing, period controls, reversal tracking, and SoD monitoring.
Reference Data & Crosswalks
TAS, USSGL, fund citation, organization, program, object class, trading partner, GTAS attributes, and legacy-to-modernization mappings.
Close & Reporting
Base-level close, central consolidation, adjusted trial balance, DDRS/GTAS edit resolution, Treasury reconciliation, and statement support packages.
Audit Evidence
Source documents, batch logs, edit reports, JV packages, reconciliations, trial-balance extracts, reporting submissions, and management review sign-offs.