STARS is modeled as the Navy legacy Standard Accounting and Reporting System family used for accounting, reporting, consolidation, suspense, and historical transaction support before or alongside Navy ERP transition paths.
STARS blueprint for Navy legacy accounting and reporting
STARS Family / Standard Accounting and Reporting System Blueprint
Explore the STARS family as a Navy legacy accounting and reporting environment for field-level accounting, central consolidation, obligation and expenditure detail, suspense, journal vouchers, trial balances, Navy ERP transition support, and source-to-statement audit evidence.
4
Core STARS lineage scenarios
Legacy source -> STARS -> TB -> StatementSystem profile
What it is, who uses it, and why it matters
Legacy Navy accounting users, DFAS/reporting support teams, DON financial managers, migration and archive teams, close teams, JV preparers/reviewers, suspense cleanup owners, and auditors may rely on STARS data or outputs.
It supports field-level accounting, central consolidation, obligation and expenditure tracking, vendor pay impacts, payroll/travel accounting, suspense/reject processing, JVs, trial balances, DDRS/GTAS support, and archive lookup.
Modeled as legacy and transition-oriented. Public technical detail is limited, so exact variants, interface names, archive status, and system boundaries require authoritative Navy or DFAS documentation.
It preserves legacy Navy accounting history and supports audit, beginning balances, UoT reconstruction, suspense cleanup, JV support, and reconciliation between historical activity and Navy ERP/reporting outputs.
The blueprint models 6 STARS source/partner categories; authoritative interface counts require Navy/DFAS records.
Field Activity InputsVendor Pay / Contract SourcesPayroll / Labor / TravelDisbursing / Treasury / IPACNavy ERP / Archive Transition PartnerManual JV / Suspense Inputs
Clickable architecture map
End-to-end flow: business event to financial statement
Cards in the selected STARS scenario path are highlighted. Click any card to inspect fields, T-codes, audit questions, and risks.
Source
Legacy Source / Interface Events
Field activity, vendor pay, travel, payroll, disbursing, collections, Navy ERP transition, and reporting partner events tied to legacy STARS accounting.
STARS
STARS Family Processing
Legacy Navy Standard Accounting and Reporting System processing for field-level accounting, central consolidation, suspense, edits, and close support.
Detail
Legacy Transaction Detail
Document, obligation, expenditure, JV, suspense, archive, and migration detail needed to reconstruct the legacy Universe of Transactions.
Accounting
Accounting and Control Layer
Budgetary, proprietary, JV, suspense, trial-balance, and Navy ERP transition controls.
Reporting
Reporting and Reconciliation
Legacy reports, trial balances, DDRS/GTAS support, crosswalks, tie-outs, archive extracts, and audit packages.
Statements
DON / DoD Statement Support
Budgetary resources, net cost, balance-sheet, note, ULO, suspense, and transition assertions supported by STARS history.
Scenario lineage explorer
Legacy Obligation to SBR and ULO Review
Traces a STARS obligation from field or vendor source through field/central processing, obligation detail, budgetary control, reporting, and SBR support.
->
->
->
->
->
Business flow
- A field activity or contract source creates an obligation with document, fund, organization, object class, and amount.
- STARS field-level processing edits the transaction and passes supported activity toward central consolidation.
- Obligation detail preserves changes, liquidations, deobligations, and open balance aging.
- Budgetary controls classify the activity for authority, obligations, expenditures, outlays, and ULO review.
- Trial balance and SBR support trace reported amounts back to the legacy obligation population.
AI / audit exception tests
- invalid fund/classification
- stale ULO
- modification not reflected
- trial balance not tied to detail
- deobligation unsupported
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 Accounting Governance
Document-number control, field-to-central reconciliation, accounting classification validation, period close, balance roll-forward, and report reproducibility.
Suspense and Reject Control
Reject queues, unmatched disbursements, invalid LOA/accounting edits, suspense aging, owner assignment, clearing evidence, and root-cause tracking.
JV and Close Controls
Manual adjustment support, preparer/reviewer/approver trail, debit/credit validation, accruals, reclasses, reversals, and close-package tie-outs.
Archive and Transition Support
Legacy UoT extracts, Navy ERP balance bridge, conversion batches, beginning-balance evidence, historic lookup, and retained sample packages.
Reporting Crosswalks
Legacy account-to-USSGL/TAS mapping, trial balance support, DDRS/GTAS reconciliation, Treasury/IPAC tie-outs, and statement-line mapping.
Audit Evidence
Source documents, transaction detail, obligation/expenditure history, payment and collection support, archive extracts, reconciliations, and note schedules.