Pbc Request Routing Continuous Control Monitoring
Description
Monitor key control points for PBC request routing; flag missing approvals, SoD conflicts, late postings, or incomplete evidence before month-end close. The MVP would connect Advana, audit management tools, NFR repositories, CAP trackers, IPA requests, evidence stores and produce read-only recommendations for OUSD(C), DoD OIG, Service audit remediation offices, DFAS.
AI / analytics pattern
process mining + rules + ML
Automation level / stage
continuous assurance
Expected benefit
More timely control issue detection, reduced repeat findings, stronger ongoing assurance.
Audit / financial statement impact
Audit opinion; audit support; control testing; evidence sufficiency
Controls / human review
Human review for exceptions and recommendations; maintain evidence packages, lineage, source citations, model cards, data-quality checks, and periodic QA sampling.
Data needed
Advana, audit management tools, NFR repositories, CAP trackers, IPA requests, evidence stores; master/reference data; audit logs; policy/control requirements; prior exceptions; relevant document evidence.
Possible metrics
control exceptions detected before close; SoD conflicts remediated; repeat findings reduced
MVP scope
Start with one Component/reporting entity and one subprocess (PBC request routing) for two close/audit cycles; read-only outputs first.
Related material weakness / control objective
NFR remediation and auditability