SAP runs the world's most critical business processes. But its approval experience was designed for a world where everyone sat at a desk with a browser open to the SAP portal. That world doesn't exist anymore.
The Desktop-First Assumption
SAP's workflow engine is powerful. Flexible release strategies, multi-level approval chains, condition-based routing — the backend is enterprise-grade and battle-tested.
The problem isn't the engine. It's the cockpit.
SAP Fiori Inbox assumes that approvers will proactively navigate to a web application, log in, review a queue of items, and process them. This made perfect sense in 2014 when Fiori launched. Today, it's a friction point.
Where Approvers Actually Live
In 2026, knowledge workers spend their day in three places:
- Microsoft Teams (or Slack) — where collaboration happens
- Email / Outlook — where notifications land
- Mobile devices — where decisions happen outside the office
Fiori Inbox is none of these. It's a separate destination that requires a separate login and a separate mental context. Every additional step between "approval needed" and "approval complete" adds latency.
The Real Cost of Friction
Slow approvals aren't just annoying — they're expensive. Consider the downstream effects:
Procurement delays
A purchase requisition that sits for three days in an approval queue delays the entire procurement cycle. If that's a production material, you're potentially stalling a manufacturing line.
Payment term erosion
Invoices stuck in approval miss early payment discount windows. For a company processing thousands of invoices, even a 1-2% missed discount rate adds up to significant cost.
Compliance risk
When approvals take too long, people find workarounds. Someone processes a PO without approval. Someone forwards an approval to a colleague via email with "just click approve." These workarounds create compliance gaps that auditors will find.
Employee frustration
Requestors who submit a PR and wait a week for approval lose trust in the process. They start building buffer time into requests, over-ordering, or finding unofficial channels. The approval process becomes a bottleneck that people route around.
Notifications Aren't Enough
Some organizations try to solve this with email notifications. SAP sends an email when an approval is pending. The approver clicks a link, logs into Fiori, and processes the item.
This helps — but it's still two steps too many. The email notification is a pointer to the approval, not the approval itself. The approver still has to context-switch to a different application.
What if the notification was the approval? What if all the information the approver needs — document type, amount, line items, requestor — arrived in the same place they already work, with approve and reject buttons right there?
The Adaptive Card Paradigm
Microsoft Teams Adaptive Cards are the answer to this question. An Adaptive Card is a rich, interactive UI element that lives natively inside Teams. It can display structured data, collect input, and trigger actions — all without leaving the Teams window.
For SAP approvals, this means:
- The approver receives a card with full document details
- They can review line items, amounts, and requestor information
- They click approve or reject — one click, done
- The decision flows back to SAP with a full audit trail
- Works on desktop, mobile, and tablet
No new application to learn. No separate login. No context switching. The approval happens in the flow of work.
Why This Hasn't Happened Sooner
If this is such an obvious improvement, why isn't everyone doing it already? Three reasons:
1. SAP + Teams integration is hard
Connecting S/4HANA to Microsoft Teams requires expertise in SAP BTP, Azure AD, the Microsoft Graph API, Adaptive Card design, and SAP workflow configuration. That's a rare combination of skills.
2. Power Automate doesn't scale
Power Automate can technically bridge SAP and Teams, but building a production-grade approval flow with audit trails, fallback logic, delegation support, and error handling is a massive effort. Most PoCs never make it to production.
3. Nobody's built the product
The SAP ecosystem is full of platforms and toolkits, but very few opinionated products. Everyone wants to give you a canvas. Nobody wants to give you a finished painting.
Opinionated Software Wins
At OneLoop Labs, we believe the SAP integration space needs more products and fewer platforms. Our approach:
- Ship with defaults — Pre-configured Adaptive Card templates for each approval type
- Minimize configuration — Setup takes days, not months
- Handle the edge cases — Delegation, fallback, retries, audit logging are built in
- Use standard APIs — No fragile workarounds that break on the next support pack
The result is an integration that works like a product, not a project.
The Future of SAP UX
We think the future of SAP user experience lives outside of SAP. Not because SAP's UI is bad — Fiori is well-designed for what it is. But because the best UX is the one that doesn't require a separate destination.
Approvals in Teams. Reports in Power BI. Alerts in Outlook. The SAP system becomes the engine, and the interfaces people already use become the cockpit.
That's the future we're building toward.