From the Campus Operations edition of September 27, 2026
WSU Workday Expense Protect pilot claims $20k duplicate prevention, 160 hours saved, and six-day faster reimbursements
Washington State University (Workday customer story) · Higher education finance / accounts payable / research administration · United States (Washington State University; multi-campus R1 public research university)
- Publisher
- Workday
- Original publication
- Undated Workday customer story (retrieved 2026-09-27)
- Source retrieved
- 2026-09-28
What happened
Workday's Washington State University customer story describes a six-month pilot of Workday Expense Protect that shifted expense auditing from manual spot-checks toward AI-driven risk scoring. The page claims the system flagged two duplicate expense reports within hours of go-live, prevented over $20,000 in duplicate expenses in the first six months, achieved 100% risk-based audit coverage of every expense report, reclaimed 160 audit-team hours annually, and cut reimbursement turnaround by six days by automating lower-threshold reviews. Named WSU leaders (Executive Director Gerik Kimble; Business Systems Analyst Kelsey DeMacon) describe business-officer demand for more AI tools and a measurable drop in duplicate submissions as employees self-check. The narrative frames the work as safeguarding R1 research/grant funds without adding headcount and as a path to broader Workday HCM/Finance AI.
Why it matters
Measured campus finance-operations AI evidence for expense integrity—core administrative workload adjacent to yesterday's Fordham/Notre Dame AI spend-control theme but focused on AP/travel duplicate detection rather than consumption metering. Why now: never archived; pairs with today's Stanford agent-governance and Allure adversarial payroll lure signals.
Evidence and measured results
Opened Workday HTTPS customer story with quantified claims and named WSU staff. Marketing evidence; independent replication not provided.
Limitations and uncertainty
Vendor-claim evidence; undated page; $20k/160-hour/6-day figures unaudited; ML vs generative AI attribution unclear.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-09-27; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Manual expense spot-checks miss duplicates and delay reimbursements while consuming scarce audit capacity on low-risk volume.
- Stakeholders
- CFO/Controller
- Accounts payable
- Internal audit
- Research administration
- Business officers
- Discovery questions
- What share of expenses is manually sampled today?
- What is baseline duplicate and reimbursement cycle time?
- Are grant-funded expenses reviewed differently?
- Is Workday already the system of record?
- Value hypothesis
- AI risk scoring can raise audit coverage and reclaim auditor hours when embedded in the ERP—WSU's dollar and hour figures are vendor-reported, not guaranteed.
- Potential engagement
- Eight-week Expense Protect readiness pilot design: baseline duplicates, configure risk routing, restrict security access, and define success thresholds before threshold raises.
- Unsupported claims
- Guaranteed $20,000 savings
- Guaranteed 160 hours reclaimed
- Labor reduction promises
Pre-sales engineering
Role takeaway
- Fit
- ERP-embedded AI expense risk scoring with automated high-risk routing and adjustable manual-audit thresholds.
- Architecture and integration
- Workday Financials expense business processes; integrate grant worktags and secure notification channels for payment-related changes.
- Prerequisites
- Configured expense policies
- Pilot security role isolation
- Baseline duplicate metrics
- Appeal/override workflow
- Constraints
- Vendor-reported metrics only
- Undated case page
- Works best inside Workday ecosystem
- Security
- Least-privilege pilot access; log AI routing decisions; protect expense and grant data; dual control on payment elections remains separate from expense scoring.
- Proof of value
- Duplicate dollars prevented vs baseline
- Reimbursement cycle-time delta
- False-positive appeal rate
Delivery
Role takeaway
- Work
- Run controlled pilot, validate scoring, raise low-risk thresholds, train auditors on exceptions, and communicate self-check expectations to submitters.
- Dependencies
- Workday administrators
- Internal audit
- Research/grant compliance
- Change management
- Ownership
- Finance/AP leadership with internal audit concurrence on threshold policy.
- Skills and adoption
- Train auditors to investigate AI-flagged risk rather than re-perform full manual reviews; teach submitters to respond to immediate feedback.
- Governance checkpoints
- Pilot accuracy review before threshold raise
- Quarterly false-positive review
- Grant-compliance sampling
- Acceptance criteria
- Documented duplicate prevention on pilot population
- Measured reimbursement cycle-time change
- Override/appeal log retained
- Risks
- Unbaselined metric theater
- False negatives on grant expenses
- Over-reliance on vendor 100% coverage claims
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Embed AI risk scoring inside the ERP expense pipeline with restricted pilot security access, automated high-risk routing, and raised manual-audit thresholds only after scoring accuracy is observed.
Governance
Who approves, reviews and stays accountable for outcomes?
Document who may raise audit thresholds and how false-positive duplicate flags are appealed; treat grant-funded expense monitoring as a compliance control, not only a convenience feature.
Security and privacy
What data, permissions and controls need testing?
Expense and grant data are administrative/financially sensitive; limit pilot access, log model-driven routing decisions, and separate requester identity from approval authority.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Faster reimbursements improve staff experience; auditors shift toward complex/high-value reviews—requires retraining so capacity gains are not merely speed theater.
Procurement
What should contracts, pricing and exit terms secure?
Favor ERP-native AI controls when Workday is already licensed; still budget for pilot monitoring and audit-policy redesign beyond module checkbox pricing.
Operating model
Which teams own the service once it runs?
Moves AP from sampling to risk-based full coverage with human focus on exceptions; cultural self-checking is claimed as a secondary benefit.
Publication history
- 2026-09-27Campus Operations · Issue 204 resources
Stable resource ID: wsu-workday-expense-protect-ai-2026