Earlier this month, I had the pleasure of hosting a roundtable webinar on a topic that’s sparking more client conversations than almost anything else right now: Full User Equivalent (FUE) licensing in SAP.
As someone who works closely with clients across Europe and the Middle East in the SAP GRC freelance space, I’ve seen firsthand how confusing - and costly -this licensing shift can be. That’s why I brought together some of the smartest minds I know in the SAP risk, compliance, and authorisations world to help break it all down.
Together, we explored what FUE really means, where companies are going wrong, and - importantly - how they can flip this challenge into a cost-saving opportunity.
Meet the Panel
I was joined by an exceptional group of experts:
Each brought unique insights, war stories, and actionable advice - from both the consulting side and real-world enterprise delivery.
So, what exactly is FUE – and why now?
If you’re just getting up to speed: FUE licensing changes the game. You’re no longer just charged for what a user does - you’re charged for what they could do.
This sounds minor, but it has far-reaching implications. Broad technical roles, “just in case” access, and poorly designed permissions structures can all inflate your licence count - and your costs.
We talked through how organisations often find themselves over-licensed without realising, especially after moving to RISE or consolidating into centralised S/4HANA systems. One panellist shared a client example where £500,000 in unnecessary FUE spend was uncovered and corrected - just by getting intentional about role design and usage analysis.
From Compliance Goal to Cost Strategy
A key theme that emerged was the growing power of Least Privileged Access (LPA). For years, it’s been considered best practice for compliance. Now, it’s also a clear commercial lever.
We discussed how this shift is helping teams finally win internal support - from CFOs, audit leads, and transformation sponsors - because they can make a compelling business case, not just a technical one.
From a recruitment and resourcing perspective, I’m also seeing increasing demand for professionals who understand FUE deeply. It’s no longer a niche skill - it’s a must-have for project-critical teams.
Tactical Fixes & Lessons Learned
Our panel shared practical ways to start fixing inflated FUE counts:
- Audit underused roles and remove “just in case” permissions- Use task-based role design to modularise and simplify access
- Leverage tools like the STAR Report and GRC Access Control to identify cost drivers
- Centralise expensive licence types where possible
Branko made a great point about usage tracking: many users don’t use 90% of the roles assigned to them. That’s a huge opportunity to clean up and save.
Want the full breakdown?
This blog is just the headline summary. We’ve pulled together all of the webinar insights, panellist quotes, and tactical advice into a downloadable takeaway doc.
Download the full webinar PDF here
Let’s connect at SAP Sapphire
Trillion will be attending SAP Sapphire, and I’ll be there too. If you’d like to chat more about licensing strategy, GRC, or access optimisation - or just connect - I’d love to meet you.
Book time with us at Sapphire → HERE
Thanks again to our brilliant panel, and to everyone who joined us live. Let’s keep the conversation going - and keep access strategy where it belongs: at the heart of transformation.