Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Erp Implementation topic
No spam. Unsubscribe anytime.
UT System updates DASH ERP rollout, flags material weakness and payroll risks
Summary
System finance officials reported progress on the DASH Oracle implementation but identified continuing risks — off‑cycle payroll processing, pace of change and limited bench strength — and warned of a material weakness to be discussed in the audit committee.
Get email alerts on the Erp Implementation topic
No spam. Unsubscribe anytime.
System finance leaders gave trustees an update on DASH, the Oracle‑based enterprise resource planning system that replaced legacy tools, highlighting recent functionality, user feedback, and continuing operational risk.
David Miller summarized accomplishments since October, including closing FY25 and early FY26 periods, rolling out a principal investigator dashboard and budget‑to‑actual reporting, issuing payroll forms and implementing an integrated ADP biweekly timekeeping solution tied to DASH. He said the team produced a baseline user survey (5,548 responses) that showed a range of usability across modules; sponsored projects and PI tools trended more positively while general ledger reconciliation needed work.
Miller warned of operational risks: "off cycle payroll request is a real problem" because DASH previously made off‑cycle payrolls difficult and the team is designing a solution with Oracle; he also cited the continued pace of change and a lack of bench strength in critical roles as items requiring mitigation. Chair Rhodes told trustees they would hear more about "a material weakness" in the audit committee.
Why it matters: the system's ability to close accounting periods promptly and to handle payroll and reconciliation affects staff pay cycles, financial controls and audit outcomes. Committee members pressed for timelines and contingency plans.
Next steps: Miller outlined a DASH applications roadmap for 2026 focused on the highest‑value improvements, cross‑training to reduce single‑point dependencies, and implementing additional internal controls reported to the audit committee.
