Duplicate Payment Detection Anomaly Detection
Description
Detect unusual patterns in duplicate payment detection using transaction features, user behavior, timing, amount, fund/account, and historical peer benchmarks. The MVP would connect ERP transactions, vendor master, travel, payroll, contract pay, public/exclusion lists, investigative data and produce read-only recommendations for DoD OIG, DFAS, Components, DCAA/DCMA where applicable.
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
Expenses, accounts payable, accounts receivable, compliance reporting
Controls / human review
Human approval required before posting, payment, denial, personnel action, or official audit response; model validation; drift monitoring; exception sampling; full prompt/data/output logging. Do not use alerts as sole basis for adverse action; require sampled validation and feedback loop.
Data needed
ERP transactions, vendor master, travel, payroll, contract pay, public/exclusion lists, investigative data; 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 (duplicate payment detection) for two close/audit cycles; read-only outputs first.
Related material weakness / control objective
Improper payment prevention; fraud risk management