Looply turns SAP approvals into interactive cards in Microsoft Teams. One tap — and the decision is written straight back to SAP.
SAP Clean Core certified
SAP Store
Coupa Platform Ready
AWS & Azure Marketplace
Requests sit in an SAP inbox until someone happens to check it.
Arch's estimate of what switching between Teams, email and SAP costs.
Forwarded, buried, untraceable. Nobody can say where a request stands.
A manager approving four things a month won't memorize a transaction code.
Every detail needed to decide, and two buttons. This is the whole user experience.
Invoice paymentSupplier, due date, line items
Leave requestBalance and dates, side by side
Subcontract POScope and value before you sign off
HR sign-offPeople processes, same flow
Looply is a managed cloud platform. Your team configures it — no development backlog.
One SAP event in, conditions and branches, a card out to each approver — and you change it yourself when the business changes.
Drag in fields, buttons and tables. The preview updates as you edit. No code.
Awaiting Action and Actioned in one inbox — even if the card scrolled past in a busy channel.
A custom Teams app per department. IT approves before deployment and owns the lifecycle.
Executions, completion rate, failures and recent activity — without asking anyone.
Arch ships 18 ready demonstrations. Purchase requisition, purchase order and SAP MDG approvals come as packaged services.
Requisition and PO approvals with full detail and a comment box. Packaged service.
Journal verification and supplier invoices. Coupa claims travel the same route.
SAP MDG and SimpleMDG change requests as cards, not emails. Packaged service.
Leave approvals, data validation prompts, sign-off on HR letters and contracts.
Mirror the SAP inbox into a refreshable card. A no-code place to start.
Policy acknowledgements collected automatically. MFA before sensitive cards.
A lightweight ABAP component in SAP, a managed cloud engine, and the Teams tenant you already have.
Official Looply reference architecture, published by Arch Consulting.
Time-related payments, leave and expenses all waited on someone opening a separate system. Looply delivered the existing Fiori approvals straight into Teams chat, then went mobile.
Task orders lived in personal mailboxes and individual drives. Looply moved the approval step into Teams as adaptive cards, replacing the email chain.
Arch's reference plan for a first process. DKM Ecosystem runs it with you, in your time zone.
Align stakeholders, assess the landscape, agree success criteria.
Deploy Looply, connect Entra ID, SAP and Teams. Validate mobile.
Model the flow, design the cards, configure the SAP integration.
Integration, performance, UAT with real approvers, security check.
Production deploy, user training, support route in place.
Phased go-live with hypercare, then plan the next process.
Work moves to Teams. Authority does not move out of SAP.
Recorded and audited exactly as before. Existing workflows stay where they are.
SAP users map to Entra ID identities. Teams changes the channel, not the permissions.
Looply stores no SAP data. Remove it and approvals fall back to SAP channels.
We hold the regional distribution rights for Looply, so contracting, billing, pricing and first-line support sit with us — not routed overseas.
Pay in local currency, receive compliant invoices. No more expensing an overseas subscription.
Same time zone, end to end — configuration, deployment, integration, training. We handle Arch on your behalf.
Scoped to the processes and users actually going live. Predictable as you expand.
We map the approval before building the card: who decides, on what, and where the data lands.
One approval where the delay is measurable. Prove it, then extend — including mid S/4HANA transformation.
No. Workflows stay in SAP S/4HANA, on SAP BTP or wherever they live today. Looply listens for outcomes and delivers the task into Teams. Stop using it and approvals fall back to existing SAP channels.
A lightweight ABAP component, acting as the secure access point to SAP workflows, business events and APIs. It holds SAP Clean Core certification, does not modify SAP standard objects, and is upgrade-safe.
No. Looply connects directly to SAP core or via BTP, depending on where your workflows are defined. SAP ECC and S/4HANA are both supported, including landscapes running both during a transition.
No. The action happens in Teams, but the decision is recorded, governed and audited in SAP exactly as before. Looply is not a system of record and stores no SAP data.
Those are strong at dashboards and conversation — but the user has to go and ask. Looply is push-based: the work arrives in front of the person who must decide. Arch puts a full deployment at 6–9 weeks, against 6–12 months of assembling the equivalent from separate pieces.
They act on a card in Teams that needs almost no explanation, and no special Teams client is required. SAP authorizations still decide what each person may act on; SAP user licensing remains a matter for your SAP agreement, which we work through with you when scoping.
SAP business events, API triggers, or polling for constrained and legacy systems. That last option is why older ECC landscapes without modern eventing can still be covered.
Yes. SAP authorizations are enforced, SAP stays authoritative, and cards carrying sensitive data can require multi-factor authentication first. Much of Arch's published reference base sits in UK public sector and regulated industries.
It depends on the processes in scope and the number of users, so DKM Ecosystem quotes in your local currency once we understand the requirement. Most organizations start with a single approval — purchase requisition, purchase order and SAP MDG come as packaged services.
As Arch's Master Distributor for APAC, DKM Ecosystem holds the regional distribution rights for Looply — and adds local-currency billing and compliant invoicing, Chinese-language support in your time zone, process design and integration delivery, training and ongoing vendor liaison.
Tell us, and a DKM Ecosystem consultant will scope the first Looply process with you.