Sloa Attribute Completion Anomaly Detection
Description
Detect unusual patterns in SLOA attribute completion using transaction features, user behavior, timing, amount, fund/account, and historical peer benchmarks. The MVP would connect GFEBS, Navy ERP, DEAMS, DAI, DDRS, Advana, USSGL/SLOA/SFIS attributes and produce read-only recommendations for DFAS, OUSD(C) Financial Reporting, Service ERP owners.
AI / analytics pattern
ML anomaly detection
Automation level / stage
human-in-the-loop alert triage
Expected benefit
Higher detection coverage, fewer missed exceptions, better prioritization of high-risk items.
Audit / financial statement impact
All statements; GL-to-trial-balance accuracy
Controls / human review
Human review for unusual/high-dollar items; policy citations; audit logs; role-based access; periodic accuracy testing. Do not use alerts as sole basis for adverse action; require sampled validation and feedback loop.
Data needed
GFEBS, Navy ERP, DEAMS, DAI, DDRS, Advana, USSGL/SLOA/SFIS attributes; master/reference data; audit logs; policy/control requirements; prior exceptions; relevant document evidence.
Possible metrics
precision/recall of alerts; dollars reviewed; false-positive rate; high-risk exception closure time
MVP scope
Start with one Component/reporting entity and one subprocess (SLOA attribute completion) for two close/audit cycles; read-only outputs first.
Related material weakness / control objective
Financial reporting internal controls; USSGL/SFIS compliance