Master Thesis · SAP S/4HANA Cloud Public Edition · UX Design

Reactive to Proactive
Project Billing

Transforming project billing workflows in SAP S/4HANA using AI-powered situation handling — shifting billing specialists from reactive firefighting to proactive, guided decision-making.

Author Ritvik Kolhe
University Technische Hochschule Ingolstadt
Industry Partner SAP SE, Business Suite UX
Degree M.Sc. User Experience Design
Date June 2026
7
Moderated usability
test participants
22
Customer Council
responses
4.42/5
Perceived value
rating
−5.7
NASA-TLX time
pressure reduction

What is this project about?

A Human-Centered Design thesis conducted in collaboration with SAP SE, applying ISO 9241-11 methodology to redesign how billing specialists interact with SAP S/4HANA.

⚠️

The Problem

Billing specialists discover critical errors — invoice splits, missing cost centres, price discrepancies — only after submitting billing document requests, triggering costly rework loops with Billing Clerks.

Proactive Issue Detection using SAP Joule & Situation Handling

SAP Joule's Situation Handling framework is embedded directly into the billing workflow — proactively detecting risks at the data-review stage, before they escalate into BDR rejections. Specialists receive prioritised situation cards with AI-generated context, one-click resolution, and guided actions — all without leaving the workflow.

📈

The Outcome

A validated high-fidelity prototype with measurably improved hedonic quality (+1.14 UEQ-S), lower time pressure, and a 4.42/5 value rating from 22 enterprise customers at SAP Customer Council.

Meet the Billing Specialist

Developed through day-in-the-life sessions, user interviews, and Customer Council workshops across SAP S/4HANA Cloud Public Edition enterprise customers.

👨‍💼

Bill Now, 30

Billing Specialist  ·  SAP S/4HANA Cloud Public Edition
"My job is to bill as much as possible — accurately and on time — regarding the project situation."

Main Goals

  • Bill correctly and on time
  • Maximise revenue and cash flow
  • Avoid rework and invoice rejection

Needs

  • One place for all billing information
  • Early detection of risks and issues
  • Clear guidance on what to fix
  • Faster, more confident decisions

Pain Points

  • Issues found too late in the process
  • Manual checks across multiple systems
  • High rework due to rejected invoices
  • Lack of clear overview and guidance

Six Core Pain Points

Discovered through day-in-the-life sessions, user interviews, Customer Councils, and Qualtrics surveys with billing specialists in SAP S/4HANA Cloud Public Edition.

🎯

Lack of Prioritisation

High-value and overdue billing items are not highlighted — specialists struggle to determine what to work on first.

🔀

Fragmented App Switching

The billing process spans multiple applications with no clear starting point, creating confusion and redundant steps.

Late Issue Discovery

Critical billing errors surface only after submission, forcing cancellations and full reprocessing of the billing cycle.

🔍

Limited Transparency

Figures, warnings and aggregated values are unexplained — users don't understand calculations or required actions.

🔁

Manual Repetitive Work

Specialists repeat the same data inputs and checks across different steps and apps, adding effort with little value.

📋

No Billing Preview

No early visibility into billing readiness — approved time and expenses can remain unbilled for extended periods.

Current vs. Proposed Workflow

Moving issue detection from the rejection loop to the data-review stage eliminates costly rework and lowers BDR rejection rates.

Current Workflow — Reactive
Review Billing Data
Edit Billing Items
Submit BDR
Billing Clerk Reviews & Validates
⚡ Issues surface here — BDR Rejected
↩ Rework Loop: Re-edit & Resubmit
Proposed Workflow — Proactive
✦ Joule surfaces risks at data review
Guided issue resolution in context
Billing summary before submission
Submit BDR — clean first pass
Billing Clerk Reviews & Validates
Invoice Generated & Sent ✓
💡

Key Insight: In the current workflow, issues only surface when the Billing Clerk rejects the BDR — triggering a costly rework cycle. Joule moves issue detection to the data-review step, eliminating the rejection loop and reducing BDR rejection rates before they occur.

Project Billing as a Joule Workflow

SAP Joule's situation handling framework proactively surfaces billing risks, ranked by urgency and financial impact — directly within the specialist's workflow.

🃏

Proactive Situation Cards

Billing risks and overdue items surface with priority badges, financial context, and one-click actions — before the user begins their workflow.

🤖

AI-Powered Risk Analysis

Joule detects invoice split risks, price discrepancies, and missing cost centres before PBR creation — explaining its reasoning inline.

🗺️

Guided End-to-End Resolution

From billing readiness check through issue resolution to invoice submission — one guided experience within Joule, no app switching required.

🔄

Human-in-the-Loop Control

A persistent "View in App" option preserves specialist authority. Users verify edge cases in S/4HANA and return without losing context.

Watch the Joule Billing Workflow

A walkthrough of the high-fidelity Joule prototype — from the situation card on the S/4HANA launchpad through risk analysis and billing request creation.

Lab Preview Only — High-fidelity research prototype for academic evaluation. Does not represent a released or committed SAP product feature.

Quantitative Analysis

7 moderated usability sessions + 21 Customer Council responses using UEQ-S, NASA-TLX, PSAT, and UX Lite instruments.

User Experience Quality — UEQ-S (scale −3 to +3)

Current System
Joule Prototype
Pragmatic Quality How well the system supports task completion
Current System
1.07 Excellent
Joule Prototype
0.89 Excellent

Both systems scored Excellent. Slight decrease with Joule, users need more practice to fully leverage AI-guided actions.

Hedonic Quality How enjoyable & stimulating the experience feels
Current System
0.25 Good
Joule Prototype
1.39 Excellent

Biggest gain (+1.14). Joule's conversational, guided experience is perceived as significantly more engaging and stimulating.

Overall UEQ-S Combined user experience score
Current System
0.66 Excellent
Joule Prototype
1.14 Excellent

Overall UX improved by +0.48. Both systems rated Excellent, Joule's score is driven primarily by its superior hedonic quality.

💡

Key Insight: Hedonic quality gains outpaced pragmatic gains, Joule's improvement is primarily experiential. Users find the AI-driven interface more enjoyable and engaging, even as task-completion efficiency continues to mature.

Cognitive Load — NASA TLX (lower = better)

Current System
Joule Prototype
Mental Demand
21.4
27.1
Time Pressure
42.8
37.1
Effort
24.2
26.4
Frustration
16.4
15.7

Pattern: faster triage, but more thinking/verification.

Perceived Usability & Satisfaction (1–5 scale)

Current System
Joule Prototype
Overall Satisfaction
3.7
Current
3.8
Joule
Does What I Need
3.8
Current
3.5
Joule
Easy to Use
3.5
Current
3.7
Joule

Joule scored higher on ease-of-use and satisfaction; current system led on "does what I need" due to missing billing summary and unclear actions.

Customer Council Sentiment (N=21, 1–5 scale)

Value for improving billing efficiency & reducing errors
4.42
Investment opportunity for SAP and customers
4.14
Comfort with AI guiding billing decisions
4.00
Likelihood of company adoption
3.90

"Billing is too complex, guiding & prompting potential issues sooner is better"

"This solution would give the chance to distribute responsibility in the future"

Refined Concept — Iteration 2

A second prototype addressing trust, clarity, and actionability gaps identified in the usability study evaluation.

🔍 Explainability

Joule now surfaces data sources and reasoning inline. A Billing Summary before BDR submission gives specialists a consolidated view of totals and expected invoice structure.

🖱️ In-Card Actions

Action buttons placed directly within the expanded issue card — no navigation away, fewer steps to resolution, reduced context-switching.

🚪 Clearer Entry Points

Joule triggers are now visible, contextual, and use plain-language labels aligned to the billing task — users no longer discover how to invoke Joule.

👤 Authorship on Notes

Notes display team member names alongside content, restoring accountability and traceability without leaving Joule.

🔄 Human-in-the-Loop

A persistent "View in App" option at any point in the workflow preserves specialist control — drop into S/4HANA, verify, and return without losing context.

📑 Billing Summary

Before final submission, Joule presents a consolidated billing summary covering totals, groupings, and expected invoice structure — closing the trust gap.

Refined Concept — Screen Recording  ·  Lab Preview Only

How Does This Project Help SAP?

Beyond the research findings, this thesis delivered concrete, strategic value to the SAP Professional Services & Billing product team — across discovery, design, and product direction.

Impact 01

Shifted Billing from Reactive to Proactive

Provided a clear blueprint for transforming Project Billing so AI can anticipate billing discrepancies and unbilled revenue before they become critical issues — not after.

Strategic Direction
Impact 02

Validated the AI Approach with Evidence

A direct comparison between the existing solution and the AI-enhanced prototype provided data-backed proof of improvements in billing accuracy, efficiency, and reduced manual effort.

Product Confidence
Impact 03

Championed Modern, User-Centric Design

Demonstrated how to build a more intuitive, guided billing process — significantly lowering the learning curve and reducing human error, especially for users new to the system.

UX Quality
Impact 04

Provided Strategic Clarity for the Roadmap

Delivered crucial insights into real user needs and pain points, giving the product team greater confidence to make informed roadmap decisions and justify an AI-first strategy.

Roadmap Clarity
Impact 05

Reduced Onboarding Time & Boosted Adoption

By intelligently guiding new users through complex billing processes, the solution helps employees become productive faster, reduces training overhead, and fosters greater adoption.

User Adoption
Also delivered:
  • Deep understanding of user expectations & interactions with Joule
  • Organisation & execution of customer and user workshops
  • Exploration of multiple solution & navigation approaches in Project Billing
  • Enhanced SAP's flagship lighthouse product — S/4HANA Cloud Public Edition

Joule Shifts Billing from Reactive to Proactive

✅ What Improved

  • Earlier identification of billing risks
  • Better prioritisation and workflow clarity
  • Higher usability, especially for less-experienced users
  • Lower time pressure during triage
  • More engaging and stimulating experience (hedonic quality)

🔭 What's Next

  • Reduce verification cognitive load — improve AI trust
  • Shift billing ownership to the front office
  • Evolve to an agentic model: AI that acts, not just guides
  • Connect time recording → approvals → billing → invoicing end-to-end
  • Scale to high-volume, multi-project month-end scenarios

AI in billing today works best as a decision-support layer, not full automation. The concept builds the foundation towards an agentic ERP experience — where Joule is not just a guide, but an agent that executes with oversight.

4.42/5 value rating · 22 enterprise customers · SAP Customer Council