T&E Approval Automation — Policy-Governed Travel & Expenses

Finance and Shared Services were spending too much time chasing managers for approvals and clarifications. Travel and expense data existed in SAP/D365 — but the approval story lived in Outlook.

• Travel requests raised over email or legacy portal; every BU had its own template.
• Managers approved “Looks fine” without seeing policy impact or budget consumption.
• Finance teams re-typed approved amounts into ERP, often with missing cost centers.
• Policy exceptions (non-preferred hotels, last-minute flights) surfaced only during audits.
• Month-end close was delayed by late submissions and unclear approval trails.

T&E was viewed as an “admin chore” instead of a governed, insight-rich process that protects margin.

Leadership gave Sapnity a clear brief:

• Design a policy-governed T&E experience that feels lighter than email, not heavier.
• Give approvers a single screen with purpose: policy score, budget impact, key exceptions.
• Ensure every approved item lands in SAP/D365 with the right cost center, GL and tax code.
• Reduce back-and-forth with finance by turning policy rules into checklists, not PDFs.
• Build a reusable approval engine pattern that can later power vendor and CAPEX workflows.

We followed one T&E request from initiation to posting. The story looked like this:

• Employee forwarded old email chain and attached an Excel template “from last year”.
• Manager replied “Approved” but missed that the flight class breached policy.
• Travel desk booked tickets in a separate system and updated a shared spreadsheet.
• Employee submitted expenses weeks later, referencing a different cost center.
• Finance had to reconcile three sources and call the BU controller for clarification.

Every exception required a human to remember policy, interpret context and take a risk. Nothing about this flow was scalable, auditable or analytics-ready.

Sapnity didn’t just digitize a form. We implemented a T&E approval engine that elevates every decision with context, policy rules and finance-ready data.

This pattern now underpins not only T&E, but also CAPEX approvals and vendor onboarding for the same client — one approval brain, many workflows.

Phase 1 — Shadowing & Policy Discovery

• Shadowed Shared Services to map real-life exception patterns, not just written policy.
• Identified top 10 reasons why requests bounced between BU, approver and finance.
• Translated policy PDFs into rule tables with clear conditions and outcomes.

Phase 2 — T&E Request & Approval Apps

• Built a model-driven app for finance and a clean canvas-style request form for employees.
• Designed manager view showing policy score, spend-to-budget and key exception flags.
• Embedded comments, attachments and audit timeline for each decision.

Phase 3 — Policy Engine & Orchestration

• Implemented a rule-based scoring engine in Dataverse and Power Automate.
• Configured dynamic approval paths (single, dual, or finance review) based on score.
• Introduced SLA tracking, reminders and escalation to BU heads for stuck items.

Phase 4 — SAP / D365 Integration

• Mapped cost centers, GL codes and tax logic between Dataverse and ERP.
• Ensured only validated, approved lines could be posted to SAP/D365.
• Created reconciliation views so finance could see request → approval → posting in one place.

Phase 5 — Rollout, Governance & Extensions

• Rolled out to two pilot BUs, then scaled to global Shared Services within a quarter.
• Set up monthly governance to adjust policy rules without code changes.
• Extended the pattern to CAPEX approvals and vendor onboarding with minimal rework.

For leadership, the biggest shift was cultural: approvals went from “click to clear inbox” to data-backed decisions with traceable rationale.

Sapnity turned T&E from a noisy email problem into a governed approval fabric that finance, Shared Services and business leaders can all trust.