500,000 people work in shared services. These are the 10 tasks they’re automating first with Power Automate

Scenario: A finance operations team under pressure

Imagine a finance operations team in a shared service centre supporting several European entities. They handle:

• Vendor onboarding and master data changes
• Recurring invoice processing
• Travel & expense (T&E) approvals
• Month‑end reconciliations and reporting

They already use:

• Microsoft 365 (Exchange Online, SharePoint Online, Teams)
• Excel-based trackers in SharePoint libraries
• A ticketing tool (often ServiceNow or Jira) and an ERP (SAP, Oracle, Dynamics)

The team lead is told: "Automate what you can, but don’t break controls." No developer headcount, just Power Automate in Microsoft 365.

Below are the 10 tasks this kind of team typically automates first, with patterns that stay within standard connectors and governance.

1. Intake triage: From shared mailbox chaos to structured queues

Problem: A shared mailbox like ap@company.com receives hundreds of emails daily: invoices, vendor queries, reminders. Analysts manually tag, forward and copy data into trackers.

Automation pattern: Outlook + SharePoint + Teams.

Typical flow (cloud flow):

1. Trigger: When a new email arrives (V3) on the shared mailbox.
2. Conditions:
   • If Has Attachments is true and Subject contains "invoice".
3. Actions:
   • Create item in a SharePoint list AP_Incoming with fields:
     • Title = Subject
     • VendorEmail = From
     • ReceivedOn = DateTimeReceived
     • Status = New
   • Save attachments to a AP-Invoices document library.
   • Post adaptive card to a Teams channel with a link to the SharePoint item.

Key technical points:

• For shared mailboxes, use the mailbox address in the Outlook connector and ensure the connection has permission to that mailbox in Exchange Online.
• Attachment size limits follow Exchange and Power Automate limits; large invoices may need a different pattern (e.g. forwarding to a dedicated mailbox or using Microsoft Graph API via the HTTP connector if allowed by governance and licensing).

Before/after:

• Before: Analysts scan emails and maintain manual Excel trackers.
• After: Every invoice becomes a list item with metadata, attachments in SharePoint, and a visible queue in Teams.

2. Approval routing for vendor onboarding and master data changes

Problem: Vendor creation and changes are controlled, but approvals are handled via email threads and Excel checklists.

Automation pattern: SharePoint list or Dataverse table as the single source of truth + Power Automate approval flows.

Typical flow:

1. Trigger: When an item is created in Vendor_Onboarding SharePoint list.
2. Actions:
   • Start and wait for an approval (built‑in Approvals connector):
     • Type: Approve/Reject – First to respond or Everyone must approve depending on policy.
     • Assigned to: AP Manager and Risk & Compliance group.
   • On approval:
     • Update item status to Approved.
     • Send email to requester with approval details.
   • On rejection:
     • Update item status to Rejected and log comments.

Key technical points:

• The Approvals connector stores approval records in Dataverse in the tenant; retention and visibility are controlled via the Power Platform admin centre.
• Approvals can be actioned from Outlook, Teams and the Power Automate portal. Licensing for Approvals depends on the user’s underlying Microsoft 365 or Power Platform licences; check your tenant’s licensing to confirm usage rights.
• For segregation of duties, use separate lists or fields to ensure the requester cannot edit the item after submission; enforce with SharePoint permissions.

Before/after:

• Before: Email chains and lost approvals.
• After: Central approval log, clear status per vendor request, auditable comments.

3. Invoice status notifications to vendors and internal stakeholders

Problem: Vendors constantly ask "Where is my payment?" and business users chase AP for invoice status.

Automation pattern: Status-driven notifications from SharePoint or ERP integration.

Typical flow:

1. Trigger: When an item is modified in AP_Incoming list.
2. Condition:
   • If Status changes to Posted or Paid.
3. Actions:
   • Send email (V3) to VendorEmail with:
     • Invoice number, posting date, expected payment date.
   • Post message in Teams to the business requester.

Key technical points:

• Use trigger conditions (configured in the flow trigger’s settings) to avoid firing on every minor change.
• For ERP integration, if a standard connector is not available, many teams use scheduled exports to SharePoint or CSV in OneDrive and drive notifications from those updates.

Before/after:

• Before: Manual email replies, inconsistent information.
• After: Consistent status updates whenever AP changes the invoice status field.

4. Daily reconciliation file preparation

Problem: Analysts manually merge multiple CSVs from bank, ERP and internal trackers into a reconciliation workbook.

Automation pattern: Scheduled cloud flow + Excel Online or Power Query in an Excel file stored in SharePoint.

Typical flow:

1. Trigger: Recurrence (every weekday at 06:00 local time).
2. Actions:
   • Get file content from a bank statements folder.
   • Get file content from ERP export folder.
   • Create file or overwrite a Reconciliation_Source.xlsx in SharePoint.

The actual merging logic is best handled in Power Query inside Excel, which refreshes when the analyst opens the file or via Office Scripts + Power Automate if allowed.

Key technical points:

• Power Automate can’t run Power Query refresh directly; Office Scripts or manual refresh is required.
• For recurring flows, be explicit about time zone in the recurrence trigger to avoid surprises across regions.

Before/after:

• Before: Copy/paste between CSVs and Excel each morning.
• After: Source file ready in SharePoint; analyst focuses on exceptions.

5. SLA monitoring and escalation for tickets

Problem: Shared services teams manage SLAs (e.g., 2 business days for AP queries), but actual tracking is done in Excel or not at all.

Automation pattern: Time-based checks with recurrence triggers + SharePoint/Jira/ServiceNow data.

Typical flow (assuming SharePoint-based ticket list):

1. Trigger: Recurrence every hour.
2. Actions:
   • Get items from AP_Tickets where:
     • Status = Open
     • Created is older than now() minus SLA threshold.
   • For each item:
     • Send Teams message to owner.
     • If over hard limit (e.g., 2x SLA): Notify manager and update EscalationLevel.

Key technical points:

• SharePoint Get items supports OData filters; use them to avoid processing the entire list each time.
• For external ticketing tools, use their connectors if available; otherwise, scheduled exports or APIs with HTTP actions (subject to licensing and governance) are common.

Before/after:

• Before: SLA breaches discovered in monthly reports.
• After: Automated nudges and escalations before SLA breaks.

6. Month‑end close checklist automation

Problem: Month‑end close relies on a checklist Excel file emailed around, with manual status updates and no real-time view.

Automation pattern: SharePoint checklist + Power Automate for reminders and status aggregation.

Typical setup:

• SharePoint list MonthEndTasks with columns:
  • TaskName, Owner, DueDate, Status, Comments.

Typical flow:

1. Trigger: When an item is created or modified.
2. Actions:
   • If DueDate is within the next day and Status != Completed:
     • Send reminder email to Owner.
   • On Status change to Completed:
     • Post message to a Teams Month-End channel.

Key technical points:

• Use calculated columns or Power Automate expressions for date comparisons (addDays(utcNow(), 1) etc.).
• Avoid circular triggers: if the flow updates the same item, use trigger conditions to ignore system‑driven changes.

Before/after:

• Before: Static Excel checklist and daily status meetings.
• After: Live checklist with automated reminders and visible progress.

7. HR and T&E approval flows

Problem: Travel requests and expense reimbursements are handled via email or basic forms, with weak audit trails.

Automation pattern: Microsoft Forms or SharePoint form + Power Automate approvals + Teams notifications.

Typical flow (Forms-based):

1. Trigger: When a new response is submitted (Microsoft Forms).
2. Actions:
   • Get response details.
   • Start and wait for an approval assigned to line manager.
   • On approval:
     • Create item in TravelRequests list.
     • Send confirmation email to employee.
   • On rejection:
     • Send rejection email with manager comments.

Key technical points:

• Manager resolution can use Azure AD attributes (e.g., manager property) via the Office 365 Users connector.
• Forms responses are stored in the Forms service; the flow should copy all required data into SharePoint or Dataverse for long‑term reporting.

Before/after:

• Before: Email approvals buried in inboxes.
• After: Standardised forms, approvals tracked centrally, easy audit.

8. Master data change notifications across systems

Problem: Vendor or customer master data changes in ERP are not communicated to all impacted teams (AP, AR, procurement, tax), causing mismatches.

Automation pattern: Change log export + Power Automate notifications.

Typical flow (ERP export to SharePoint):

1. Trigger: When a file is created in ERP_MasterDataChanges library.
2. Actions:
   • Get file content (CSV or Excel).
   • Create item in MasterDataChanges list per row (using Create item in an Apply to each loop after parsing with Excel connector or manual parsing).
   • For each item:
     • Route notifications based on ChangeType and BusinessUnit.

Key technical points:

• For CSV parsing, many teams use the Excel Online (Business) connector to load the file into a table, then iterate rows.
• Be mindful of row limits and performance; for large change logs, consider batching or filtering at source.

Before/after:

• Before: Changes visible only in ERP, discovered when something breaks.
• After: Structured change log and targeted notifications.

9. Automated documentation and audit trails

Problem: Auditors ask for evidence of approvals, SLA performance and exception handling. Evidence is scattered across emails and local files.

Automation pattern: Central logging list or Dataverse table updated by flows.

Typical flow:

1. Trigger: On completion of key flows (e.g., vendor approval, T&E approval, ticket closure).
2. Actions:
   • Create item in ProcessAuditLog with:
     • ProcessName
     • TransactionId (e.g., VendorID, TicketID)
     • PerformedBy
     • Timestamp
     • Outcome (Approved/Rejected/Completed)

Key technical points:

• Approvals connector already stores approval records; this additional log is for business-friendly reporting.
• Keep PII and sensitive data out of audit logs unless necessary, and follow internal data classification rules.

Before/after:

• Before: Manual evidence collection for audits.
• After: Queryable audit log per process, updated automatically.

10. Personal productivity flows for analysts

Problem: Individual analysts spend time on small but frequent tasks: saving attachments, creating follow‑up tasks, updating personal trackers.

Automation pattern: User-owned flows triggered from Outlook or Teams.

Examples:

• Save attachments from flagged emails to a personal OneDrive folder when the subject matches a pattern.
• Create planner tasks when a Teams message is flagged or a specific keyword appears.

These flows are simple but free up noticeable time at scale.

Key technical points:

• User-owned flows run under the user’s context and permissions; they should not be used for shared mailbox or team-wide processes.
• For shared processes, prefer solutions scoped to SharePoint lists or service accounts, managed via environments and solutions in Power Platform.

Governance and safety: What SSC/GBS teams must get right early

Before scaling any of the 10 tasks, experienced teams focus on:

• Connectors and data loss prevention (DLP): Classify connectors (e.g., ERP, ticketing) as business, and restrict mixing with personal or social connectors.
• Environments: Use at least a dedicated production environment for shared services flows, separate from default.
• Owner and support model: Critical flows (AP, HR, month‑end) need clear owners, documentation and alerting on failures.
• Change control: Use solutions and versioning for important flows to avoid breaking changes when someone edits directly in production.

These aren’t optional if you want your automations to survive audits and staff turnover.

One practical takeaway

Pick one of the 10 tasks that already has a clear data source (usually a shared mailbox or SharePoint list) and build a small, auditable flow around it this week. Once the team sees a single painful step automated end‑to‑end, it becomes much easier to standardise patterns and scale automation across the rest of the shared services portfolio.