Client Situation — The Challenge
The university system is a leading public higher education institution in Massachusetts, operating multiple campuses and administrative units serving approximately 15,000 employees — faculty, administrative staff, finance teams, HR personnel, and IT administrators. SAP was the core enterprise system supporting finance, human resources, procurement, student administration, and operational reporting across all campuses.
Growing Costs With No Visibility
SAP licensing costs had been growing year-over-year with no corresponding growth in actual system usage. Each campus independently managed its own SAP user provisioning and licence allocations — creating a decentralised environment where no single team had visibility into the total licence footprint, actual usage patterns, or the relationship between purchased licence types and real user needs. The university system was paying for thousands of high-cost SAP named user licences, but without centralised analytics, leadership had no way to determine whether the spend was justified or where waste was occurring. Annual SAP maintenance fees compounded the problem: every unnecessary licence incurred 22 % annual maintenance in addition to the original licence cost.
Licence Type Misalignment
Licence types were assigned based on assumptions rather than actual usage. The most significant finding: administrative staff across multiple campuses held SAP Professional licences (the highest-cost named user type, typically $3,200–$4,600 per user) even though their actual SAP usage was limited to HR self-service tasks — checking pay stubs, updating personal information, and submitting leave requests. These users required only Employee Self-Service (ESS) licences or Limited Professional licences at a fraction of the cost ($1,500–$2,000 or less). The mismatch existed because initial provisioning had defaulted to Professional licences as a "safe" assignment, and no reclassification process had ever been implemented. Across the multi-campus system, hundreds of users were over-licensed by one or two tiers.
Duplicate Accounts Across Campuses
Employees with roles at multiple campuses had duplicate user IDs — one per campus — each consuming a separate named user licence. A finance controller who worked across two campuses, for example, had two SAP user accounts, each triggering a full Professional licence entitlement. The university system had no cross-campus identity reconciliation: each campus's IT team provisioned users independently using local naming conventions, without checking whether the individual already had an account elsewhere in the system. The audit revealed hundreds of duplicate accounts, representing a significant and entirely unnecessary licence cost that had accumulated over years of decentralised provisioning.
No Centralised Governance
The absence of centralised licence governance was the root cause of all other problems. Each campus managed SAP access independently — provisioning new users, assigning licence types, and deactivating accounts (or more commonly, not deactivating them) without reference to a central policy or shared inventory. There was no standard process for licence type assignment, no periodic usage review, no deprovisioning workflow linked to HR offboarding, and no cross-campus visibility into the total licence footprint. The result: an SAP estate that had grown organically over years, accumulating waste at every campus with no mechanism to detect or correct it. Leadership recognised the opportunity: centralising SAP licence management could reduce costs while actually improving system access for legitimate users.
Engagement Approach — Centralised Usage Review
Consolidated Usage Data Collection
Redress Compliance worked with local IT leads from each campus to extract system usage data, transaction history (SAP transaction codes executed per user over the trailing 12 months), and current licence assignments into a central dataset. This was the first time the university system had a unified view of SAP usage across all campuses. The consolidated dataset included: user ID, campus assignment, assigned licence type, last login date, transaction frequency, transaction codes executed, role assignments, and HR employment status. This single consolidated view immediately revealed patterns invisible at the campus level — including cross-campus duplicates, inactive accounts, and licence type mismatches.
Duplicate and Inactive Account Identification
The analysis identified hundreds of duplicate user accounts — the same individual with accounts at multiple campuses, each consuming a separate named user licence. Cross-referencing was performed using employee ID numbers, email addresses, and HR records to match accounts belonging to the same person. Additionally, the review identified accounts that were entirely inactive — users who had not logged into SAP for 6+ months, including departed employees whose accounts were never deactivated, retired faculty, and temporary staff whose assignments had ended. Each duplicate and inactive account represented a named user licence that could be eliminated without any impact on system access for active, legitimate users.
Role Analysis and Licence Type Mapping
Each job function across the university system was reviewed to match actual SAP usage with the appropriate licence type. The SAP licence hierarchy (Professional → Limited Professional → Employee/ESS → Test/Developer) has dramatically different costs per user — and the correct type depends on the transactions a user actually executes, not their job title. Key reclassifications: (a) registrar staff using only display transactions and basic reporting → reclassified from Professional to Limited Professional, (b) HR administrators using only ESS functions → reclassified from Professional to Employee, (c) finance controllers using full financial posting transactions → retained as Professional (correctly licensed), (d) department heads approving workflows only → reclassified from Professional to Limited Professional. The licence type mapping was validated against SAP's licence audit methodology (USMM/LAW) to ensure the reclassifications would be audit-defensible.
Licence Consolidation and Governance Framework
A unified licence management process was developed to replace the decentralised campus-level approach. The new framework established: (a) centralised licence allocation — all SAP user provisioning flows through a single SAP licence administrator who verifies licence type based on job function before granting access, (b) cross-campus identity management — employees with multi-campus roles receive a single SAP user ID with appropriate authorisations for each campus, eliminating duplicates, (c) automated deprovisioning — HR offboarding events trigger SAP account deactivation within 30 days, preventing inactive account accumulation, (d) annual usage review — scheduled review of transaction history to identify users whose actual usage no longer matches their licence type, enabling proactive reclassification, and (e) new user provisioning policy — default licence type assignment based on job function classification rather than defaulting to Professional.
Cost Modelling and Compliance Validation
The Redress team used licence optimisation modelling to simulate the impact of each change before implementation — ensuring the university could validate projected savings while confirming that reclassified users retained sufficient system access for their actual job functions. The model compared: current licence distribution (by type and cost) versus optimised distribution, quantifying savings per reclassification category. Critically, the optimised distribution was validated against SAP's USMM (User and System Measurement Message) methodology — the same tool SAP uses during licence audits to classify users. This ensured that the reclassifications would not create audit exposure: every user's assigned licence type matched or exceeded what SAP's own measurement tool would assign based on their transaction history.
Before and After — Optimisation Outcomes
| Metric | Before | After | Improvement |
|---|---|---|---|
| SAP Named User Licence Costs | Baseline (growing YoY) | 31 % reduction | Over 30 % annual savings |
| Duplicate User Accounts | Hundreds across campuses | Eliminated — single ID per user | Each duplicate = full licence cost recovered |
| Licence Type Accuracy | Assigned by assumption — widespread over-licensing | Mapped to actual transaction usage — audit-defensible | Professional→Employee/Limited reclassifications saved $1,200–$3,100 per user |
| Inactive Accounts | No deprovisioning process — accounts accumulated | Cleared; automated deprovisioning linked to HR offboarding | Ongoing waste prevention |
| Licence Governance | Decentralised — each campus independent | Centralised — single administrator, standard policies | Visibility, control, and budget accuracy |
| Audit Readiness | No USMM validation — unknown audit exposure | USMM-validated — every reclassification audit-defensible | Audit confidence established |
Savings Breakdown by Optimisation Lever
Largest Savings Driver
Reclassifying users from Professional to Limited Professional or Employee/ESS based on actual transaction usage produced the largest single savings impact. SAP Professional licences cost $3,200–$4,600 per user; Limited Professional licences cost $1,500–$2,000; Employee/ESS licences cost $200–$400. For each administrative staff member reclassified from Professional to Employee, the savings was $2,800–$4,200 per user. With hundreds of users reclassified across the multi-campus system, this lever alone delivered the majority of the 31 % cost reduction. The reclassifications were validated against USMM to ensure audit defensibility — every user's transaction history was cross-referenced against SAP's licence classification rules.
Cross-Campus Consolidation
Eliminating hundreds of duplicate accounts — employees with separate user IDs at multiple campuses — recovered one full named user licence per duplicate. At Professional licence rates, each eliminated duplicate saved $3,200–$4,600 plus 22 % annual maintenance. The consolidation to single user IDs with multi-campus authorisations preserved full system access while eliminating the redundant licence cost. This lever also simplified user management: a single account per employee means one set of role assignments, one audit trail, and one point of access control — reducing administrative overhead for campus IT teams.
Clearing Accumulated Waste
Removing inactive accounts — departed employees, retired faculty, and expired temporary staff whose accounts were never deactivated — recovered licences that were consuming entitlements with zero system usage. The automated deprovisioning workflow linked to HR offboarding ensures this waste cannot reaccumulate: when an employee leaves the university system, their SAP account is flagged for deactivation within 30 days, and their licence is returned to the available pool. This lever's financial impact was compounded by the licence type mismatch: many inactive accounts held Professional licences (the most expensive type), meaning each removal freed the highest-cost entitlement.
Higher Education SAP Licensing — Sector-Specific Insights
Universities and higher education systems face unique SAP licensing challenges that make centralised usage review particularly impactful.
| Challenge | Why It Affects Higher Education | Impact on SAP Licensing |
|---|---|---|
| Decentralised campus governance | Each campus operates semi-autonomously with its own IT team and provisioning processes | No visibility into total licence footprint; duplicate accounts proliferate; no standard policies |
| High staff turnover (temporary, adjunct, seasonal) | Large numbers of temporary faculty, adjuncts, research assistants, and seasonal administrative staff | Accounts created for short-term roles are rarely deactivated; inactive licences accumulate rapidly |
| Multi-campus roles | Faculty and administrators frequently serve across 2–3 campuses simultaneously | Duplicate user IDs created per campus; each consumes a separate named user licence |
| Broad HR self-service deployment | All employees need basic SAP access for pay stubs, leave requests, benefits enrollment | Mass provisioning defaults to Professional licences when Employee/ESS would suffice — the costliest mismatch |
| Modest IT budgets | Public universities operate under strict budget constraints with competing demands | Every dollar saved on SAP licensing is redirected to academic programmes, facilities, or student services |
Lessons Learned — SAP Licence Optimisation in Decentralised Environments
✅ Key Takeaways
- Centralised visibility is the prerequisite for optimisation: Until usage data from all campuses was consolidated into a single dataset, the waste was invisible. No individual campus IT team could see duplicates (which exist between campuses), total inactive account accumulation, or system-wide licence type mismatches. The first step in any multi-campus or multi-business-unit SAP optimisation is always data consolidation
- Licence type assignment must be based on transaction history, not job titles: Assigning SAP Professional licences to "administrators" by default is the single most expensive SAP licensing mistake in higher education. Actual transaction analysis consistently reveals that 40–60 % of Professional licence holders use only self-service or display-level functions that qualify for Employee or Limited Professional licences at 50–90 % lower cost per user
- Validate all reclassifications against SAP's USMM methodology: SAP licence audits use the USMM/LAW tool to classify users based on their transaction history. Every reclassification must be defensible under this methodology — if a user is reclassified from Professional to Employee but their transaction history includes a single Professional-level transaction, SAP's audit tool will flag the discrepancy. Run USMM validation before implementing reclassifications to ensure audit readiness
- Automate deprovisioning to prevent waste reaccumulation: Without automated HR-to-SAP offboarding workflows, inactive accounts rebuild at 5–10 % of the licence base per year in higher education environments (due to high temporary/adjunct turnover). The one-time cleanup delivers immediate savings; the automated workflow protects those savings permanently
- Cross-campus identity management eliminates structural duplicates: In multi-campus systems, a single user ID per employee with multi-campus authorisations prevents the structural creation of duplicates. This requires coordination between campus IT teams and a centralised identity management standard — but the licence cost savings and simplified administration justify the coordination effort
- Annual usage reviews maintain the optimised state: User roles change over time — an employee promoted from administrative assistant to budget controller needs a licence type upgrade; a faculty member who stops using reporting functions can be downgraded. Scheduled annual reviews (aligned with SAP USMM runs) catch these changes and maintain the optimised licence distribution
- Public-sector budget impact is significant: For a public university system with a modest IT budget, freeing up 31 % of SAP licensing costs represents a meaningful reallocation to academic programmes, student services, and facilities. SAP licence optimisation in higher education is not just an IT exercise — it is a budget management imperative with direct impact on the institution's core mission
"We were flying blind when it came to SAP usage. By unifying data across campuses, we were finally able to identify waste and make smart licensing decisions. This wasn't just an IT fix — it freed up budget that can now support academic programmes directly." — System IT Director and Chief Financial Officer