Email-stalled PO approvals to Slack/Teams + DocuSign with SAP audit trail

Overview

A global retailer’s purchase orders were stuck in inboxes waiting for managerial sign-off, causing missed production windows and last-minute escalations. Intelligex implemented an approvals orchestration that surfaced purchase orders (POs) in chat with live budget and supplier risk context, captured e-signatures, and wrote approvals back to SAP. The flow reduced handoffs, made status visible to buyers and Finance, and created an auditable trail without replacing existing systems.

Client Profile

• Industry: Multinational retail (general merchandise and private label)
• Company size: Global footprint with regional buying offices and distributed approvers
• Stage: Mature procurement function modernizing approval controls and cycle time
• Department owner: Procurement, Supply Chain & Logistics
• Other stakeholders: Finance/Controllership, Merchandising, Legal, Supplier Risk/Compliance, IT/SAP Basis, Internal Audit, Regional Operations

The Challenge

POs were generated in SAP and routed by email to managers based on spend thresholds, category, and region. Approvers received PDF attachments without consistent context: budget availability, open commitments, supplier risk flags, and exceptions were scattered across different systems. Many managers worked on mobile or in time zones that made follow-ups slow. Buyers chased approvals across threads, forwarded reminders, and re-attached revised POs when changes were made. Production slots were allocated on a first-confirmed basis by suppliers, so delays translated into constrained capacity and emergency re-sourcing.

The company’s controls relied on SAP release strategies, but the last-mile experience was brittle. A single missing detail—cost center, product hierarchy, or tax treatment—stalled approvals. Supplier risk checks were performed separately, so approvers often escalated questions to compliance mid-process. When approvals finally arrived, the audit trail was a patchwork of emails and saved PDFs. Finance needed reliable evidence for period close and audits; Procurement needed predictable cycle time and a clear line of sight to bottlenecks.

Replacing SAP or introducing a new approval system was off the table. The retailer needed to keep its ERP as the system of record, preserve existing release thresholds and segregation of duties, and make the process easier for managers without weakening controls. The solution had to meet managers in their daily tools, capture signatures, and write back to SAP reliably.

Why It Was Happening

Email was doing the work of a workflow engine. SAP generated approval requirements, but the documents left the system as attachments with minimal context. Approvers lacked the information needed to make a quick decision, so they replied-all to ask for budget position, GL coding, or supplier status. Each back-and-forth reset the clock. Changes to a PO required resending the entire package and reconciling which version had been approved.

Policy rules were encoded in SAP release strategies, but related checks lived elsewhere. Budget status resided in controlling reports, supplier diligence sat in a separate risk tool, and exception policies were documented in playbooks. Approvers could not see the whole picture in one place, and buyers could not see where a PO was waiting or what was blocking it. Internal Audit had the authority to review approvals, but not a cohesive trail that tied signatures to specific PO versions and rule checks.

The Solution

Intelligex implemented a lightweight orchestration layer that listened for POs entering approval in SAP, assembled the relevant context, and presented a single approval card in chat and email. Approvers reviewed budget position, coding, and supplier risk signals at a glance, approved or rejected with comments, and applied a compliant e-signature. The service then updated SAP, advanced the release, and attached signed artifacts and an approval log to the PO. All steps were tracked, and exceptions required a named rationale. The experience sat inside Slack or Microsoft Teams for speed, while SAP remained the authoritative system of record.

• SAP integration using standard APIs to read POs, release strategies, and statuses, and to post approval outcomes and attachments. Reference: SAP S/4HANA Purchase Order API.
• Chat delivery through interactive cards in Slack or Microsoft Teams so managers approve from desktop or mobile. References: Slack APIs and Microsoft Graph for Teams.
• E-signature integration to bind approvals to PO versions and approver identity, with signed PDFs stored against the PO in SAP. Reference: DocuSign Developer Center.
• Context pack for approvers: budget and commitment status from controlling, GL/cost center coding, tax treatment indicators, and supplier risk signals summarized in the card.
• Policy engine to enforce business rules such as split purchase detection, exception routing, and secondary approvals for flagged suppliers. Rules were versioned and testable before activation.
• Role and permission mapping aligned to SAP release strategies and SSO groups to maintain segregation of duties.
• Escalation and delegation: time-based nudges, out-of-office delegation, and escalation paths that respected thresholds and regions.
• Write-back to SAP with a durable audit record: approval decision, timestamp, approver identity, policy checks passed/failed, and linked signature artifact.
• Dashboards for Procurement and Finance showing aging by stage, bottlenecks by approver and category, and exceptions with reasons.
• Fallback to email approvals with the same signed artifact path for managers not active in chat.

Implementation

• Discovery: Mapped SAP release strategies by spend threshold, category, and region. Collected the context approvers needed to make decisions without follow-up. Identified risk signals, exception policies, and the specific SAP objects to update after approval. Documented audit requirements with Finance and Internal Audit.
• Design: Defined the approval state machine from “awaiting approval” to “released,” including resubmission on PO change. Designed the approval card layout and minimal fields approvers must see. Specified rules for exceptions, secondary approvals, and supplier flags. Planned identity mapping between SAP roles and chat identities.
• Build: Implemented listeners for POs entering approval in SAP and services to assemble context from controlling and supplier risk sources. Built interactive approval cards for Slack and Teams, integrated DocuSign for signature capture, and created connectors to write outcomes and attachments back to SAP.
• Testing and QA: Ran in shadow mode, generating approval cards without enabling actions, and compared outcomes to the current email-based process. Simulated changes to POs mid-approval to confirm resubmission behavior. Verified that audit artifacts attached correctly and that permissions blocked unauthorized approvals.
• Rollout: Started with a single category and region, enabling chat approvals for a pilot group while keeping email as a fallback. Expanded to additional categories and regions once audit and Finance signed off on the artifact trail. Feature flags controlled e-signature enforcement and exception routing during the transition.
• Training and hand-off: Delivered short sessions for approvers demonstrating chat approvals on desktop and mobile, and for buyers on monitoring status and resubmission. Provided one-page playbooks for exceptions and delegations. Set up a shared channel for real-time support during early cycles.
• Human-in-the-loop review: Approvers remained accountable for each decision. The orchestration surfaced context and enforced rules; humans approved, rejected, or requested changes, with reasons captured. Exception grants required named approvers and time-bounded validity.

Results

Approvals moved from fragmented email threads to a single, governed flow. Managers made faster, better decisions because budget, coding, and supplier status were visible in one place. Buyers tracked every PO’s status without chasing, and resubmissions after edits were handled predictably. Finance trusted the audit trail: each release linked to a signature, a policy check summary, and the exact PO version approved.

Production scheduling stabilized with suppliers because approval timing became more reliable. The retailer avoided last-minute scrambles to reclaim capacity or rebook shipments. Internal conversations shifted from locating the latest PDF to discussing exceptions, vendor performance, and lead-time risk. Audit reviews proceeded smoothly because evidence lived on the PO, not in scattered inboxes.

What Changed for the Team

• Before: PO PDFs emailed for approval; After: Interactive approval cards in chat with live budget and risk context.
• Before: Unclear status and manual chasing; After: Real-time visibility and nudges with predictable escalations.
• Before: Sign-offs stored in personal inboxes; After: E-signed artifacts attached to the PO with a complete audit log.
• Before: Policy checks performed ad hoc; After: Versioned rules enforced consistently with documented exceptions.
• Before: Re-approvals after edits were error-prone; After: Automatic resubmission and history tied to specific PO versions.
• Before: Approvals blocked when managers were traveling; After: Mobile-friendly approvals in Slack or Teams with email fallback.

Key Takeaways

• Keep SAP as the system of record and bring approvals to where managers work, rather than pushing documents into inboxes.
• Bundle budget, coding, and supplier risk context into the approval moment to reduce back-and-forth and rework.
• Use e-signatures to bind decisions to PO versions and approver identity, then write artifacts back to ERP for audit.
• Encode exception policies and escalation paths so rules are enforced consistently while leaving room for human judgment.
• Run in shadow mode and pilot by category or region to build trust before scaling enforcement.
• Maintain clear segregation of duties by mapping chat identities to SAP roles and release strategies.

FAQ

What tools did this integrate with?
SAP S/4HANA for purchase order data, release strategies, and attachment storage; Slack or Microsoft Teams for interactive approval cards; and DocuSign for e-signature binding. SAP connectivity followed standard APIs such as the Purchase Order API, chat integrations used Slack APIs or Microsoft Graph, and signatures were captured via the DocuSign API.

How did you handle quality control and governance?
Policies were encoded and versioned, with pre-checks for budget availability, coding completeness, and supplier risk flags. Approvals required authenticated identities mapped to SAP roles, and every decision produced a signed artifact attached to the PO. Exceptions needed a named rationale and time-bounded approval. Internal Audit had dashboards and direct access to the artifact trail in SAP.

How did you roll this out without disruption?
We ran the orchestration in shadow mode first, generating approval cards without enabling actions to validate context and routing. A pilot group handled real approvals with email fallback intact. Feature flags controlled enforcement, and SAP remained the sole system of record. Training was brief and role-based, and we expanded by category and region after sign-off from Finance and Audit.

How did you maintain segregation of duties and prevent unauthorized approvals?
Chat identities were mapped to SAP users and release roles. Only approvers designated by SAP release strategies received actionable cards. The orchestration verified permissions before presenting actions, and SAP rejected any write-back attempt that did not match the release configuration. Delegations were explicit, time-bounded, and logged.

What happens if the chat platform or e-signature service is unavailable?
Approvals can fall back to email with the same signature and artifact path. The orchestration queued approval events and retried writes to SAP. If needed, SAP-native approval screens remained available to authorized users. All fallbacks were logged so the audit record stayed complete.