Quarterly Reporting Manual Automation on Power Platform
European insurance and reinsurance group
In short
How can a risk team stop chasing quarterly report data by email?
Every quarter, the client's Group Risk team collected data from each business unit, about 40 sources per unit, by email and tracked it in one large spreadsheet. Chasing, version confusion and reliance on a few people put the deadline at risk. We replaced both with a model-driven app where every requirement has an owner, a stage and a due date.
Results in numbers
- sources per business unit
- c. 40
- quarterly reminders
- 120-160
At a glance
- About 40 data sources per unit in one app
- Four roles across four process stages
- Spreadsheet and email chasing replaced
The client
The client is a European insurance and reinsurance group that grows by acquiring companies in other countries. The project served its Group Risk function, which collects Quarterly Reporting Manual data from business units that map to countries, including Belgium, the Netherlands and Italy.
What it was costing them
- Time: each quarter Group Risk built a source list with every unit, then chased files one by one.
- Errors: statuses lived in a spreadsheet that drifted away from the email trail.
- Key-person risk: the process relied on email, phone calls and a few people who knew who owed what.
- Growth ceiling and audit exposure: every new country added more chasing, and there was no single record of who supplied and approved what.
What we built
We built a model-driven Power Apps app on Dataverse that walks each reporting requirement from setup to supply, approval and read-only sharing, with files held in SharePoint.
- Familiar structure: every column of the tracking spreadsheet went into Dataverse as a text field.
- A fast start each quarter: Group Risk creates a repository per entity and quarter, and a Copy button reuses the last quarter's setup.
- A clear owner at every step: a business process flow moves each requirement through configuration, provider, approver and subscriber, and ownership changes with each stage.
- Controlled approval: approvers choose Approved, Accepted or Update Required, and an update request needs a comment that appears in the timeline.
- Clean resubmission: files sit in SharePoint and close after submission, and a Resubmit button restarts the provider stage while old files move to an archive.
- Security by country, less chasing: people see only their own business unit, and three notification flows send daily assignment notices, a Monday reminder and daily reminders from two days before the due date.
Results
- The tracking spreadsheet and email chains were replaced by one app covering four roles and four process stages.
- The solution was built in three waves: administrator and provider, approvers, then subscribers and reporting.
- Result: with about 40 sources per unit and three to four units, roughly 120 to 160 requirements per quarter now carry automatic reminders instead of manual chase emails.
The risk most teams miss
The month-three risk is permissions drift. People change roles and countries, a file reaches the wrong business unit, or a flow tied to a personal account stops sending reminders. We used security roles by business unit, a SharePoint permission level for providers and a service account for connections. Flow failures after go-live were fixed, so on a repeat build we add run monitoring from day one.
What we would add today
Improvements we would add on top of what is live.
- Use AI Builder document processing or Azure Document Intelligence to check submitted PDFs and spreadsheets against the template before an approver opens them.
- Add a Copilot Studio agent in Teams so providers can ask what is due this week.
- Link Dataverse to Fabric so Group Risk reports on completeness by quarter and country.
Technology
Power Apps model-driven app, Dataverse, SharePoint Online, Power Automate, Outlook and Teams, .NET and TypeScript extensions.
Tell us how many data sources you chase by email each quarter, and we will tell you what a tracked, approved and archived process would look like.
Products and capabilities
- Power Apps
- Dataverse
- Power Automate
- SharePoint
- model-driven app
- business process flow
- risk reporting
- automatic reminders
The service behind this work
Power Platform developmentThe service behind this work
Power BIMore on this industry
Banking and finance
Related use cases
Risk, legal and complianceBranch Audit Questionnaire App for 180 Branches
The client collected branch audit feedback from 180 branches on a Word template: 180 files to send, chase, read and file, and no single view of what was done. We built a Power Apps audit app where each branch answers, attaches evidence and submits, and head office sees the status of every audit.
- 180
- branches off Word templates
Legal Letter Automation for Trade Disputes
In a trade dispute, a lawyer reads a stack of contract, correspondence and shipping papers before writing a line. That reading and the first draft of the letter take hours that senior lawyers would rather spend on strategy. We built a solution that reviews the dispute documents, builds the case summary and drafts the letter to the counterparty, with a lawyer approving every step.
- 14
- days to proof of concept
- 36
- days, full solution
On-Site Health and Safety Audit Mobile App
A safety audit on paper is seen only when someone types it up. At a quarry or plant a missing guard or blocked walkway can wait days before the person who can fix it hears about it. We built a mobile audit app that records findings on site and sends actions to the right owner.
Have a Microsoft project in mind?
Tell us what you need built, fixed or supported. A senior consultant replies within one business day.