Approvals, international assignments, compensation, benefits and document workflows across Microsoft 365, SharePoint, SAP and Power BI — including payroll anomaly detection.
HR processes for more than 10,000 employees ran on email threads, shared inboxes and manual re-keying between SAP, SharePoint and Excel. Approvals stalled with no visible owner, international assignment packets were assembled by hand, and payroll errors were found after the run rather than before it.
Employees
Submit a request and see where it actually is, without chasing anyone.
HR operations
One queue per process instead of a shared inbox, with the data already validated.
Line managers & approvers
Approve from Teams or email with the full context attached, and be reminded when it is sitting on them.
Payroll & finance
Anomalies flagged before the payroll run, not reconciled after it.
Approvals, international assignments, compensation changes, benefits and document requests were pulled behind a common request record — case ID, requester, process type, state, owner. Each process differs in its fields and its approval chain, not in how it is tracked, which is what made a single dashboard possible.
Requests are enriched from SAP and HR master data at intake — grade, cost centre, entitlement. A request that cannot pass validation is returned to the requester with the specific reason, rather than dying halfway down an approval chain.
Approvals go to Teams and Outlook with the context attached. Every step is timed: a request sitting too long reminds its approver, then escalates. The audit trail is the record, so 'where is it' has an answer.
Where SAP and legacy screens offered no clean integration, UiPath robots drove them; where an API existed, n8n and Power Automate called it directly. Both paths write back to the same request record, so the automation method is an implementation detail rather than a fork in the process.
Scheduled checks compare the upcoming payroll against prior periods and expected ranges per grade and cost centre. Outliers — sudden allowance jumps, duplicated payments, missing deductions — are surfaced as an exception list before the run closes.
Power BI over the process data gives cycle time per process, volume per unit and where requests stall. Bottlenecks became a number on a dashboard instead of an anecdote.