Tasks move forward
An agreed event starts the workflow: a request, document or change. Employees do not need to pass every step along manually.
Power Automate
Less manual work.
With Power Automate.
Forwarding the same emails, chasing approvals or saving documents? Radorfa turns recurring steps into a clear Power Automate workflow, with explicit handling of exceptions.
Start with your question. We agree the work and costs before starting.
Power Automate Process example
- Invoice receivedEmail starts the flow
- Check informationSupplier, amount and reference
- Request approvalThe responsible colleague decides
- Process and storeAdministration, SharePoint and confirmation
Incomplete or rejected? Route to a colleague for review.
What this means for your team
The right person approves
Approvals reach the responsible colleague. Rejections, missing data and exceptions remain visible.
Manageable after delivery
We document connections and permissions, test changes and agree who follows up failed runs and notifications.
A concrete workflow example
From incoming invoice to checked processing.
An invoice arrives by email. The workflow retrieves data and checks supplier, amount and reference. An employee handles missing information. Valid invoices proceed to approval, processing in administration and storage in SharePoint.
Document recognition and posting depend on the source documents, selected integrations and licences. This is not a ready-made integration with every accounting package.
- Request
A colleague provides the required information in Microsoft 365.
- Review
Power Automate routes the request to the responsible person.
- Complete
Approval triggers registration and feedback; failed steps stay visible.
Missing information and rejections return to the appropriate colleague.
View exceptions and controls
Missing supplier, amount or reference: finance reviews the invoice. A complete invoice goes to the responsible manager. Rejected invoices return to administration with a notification. Approved invoices are processed through the agreed accounting integration, saved in SharePoint and confirmed to the requester.
We test duplicate messages, connection failures, missing permissions and retries. A failed step must remain visible to the person responsible for the process.
Connect Microsoft 365
We connect Outlook, Teams and SharePoint where relevant, for requests, approvals, notifications and data capture. Access rights are specified for each step.
Choose suitable automation
Cloud flows connect online services. Desktop flows can automate desktop application actions. We first check whether an API or existing integration offers a reliable route. Human decisions remain explicit when required.
Test and maintain
We test valid and incomplete input, rejections, duplicate messages and unavailable connections. Configuration and connections are documented, using separate development, test and production environments where appropriate.
From setup to everyday use
Automation with control
Approvals and exceptions remain with the right employee. We test what happens when information is missing or a later step fails.
Our approach
A clear next step, at every stage.
Walk through one task
Show us the employee actions, systems and common problems.
Build and test exceptions
We build the workflow and verify roles, information and unusual situations.
Handover and monitor
We explain usage, document management and agree who handles failures and changes.
Before we start
Your questions, answered.
Is Power Automate included in Microsoft 365?
Some capabilities may be included. Premium connectors, document recognition and unattended desktop automation may need additional licences or usage charges. We assess this for your chosen workflow.
Can it connect other systems?
Often through an existing connector or API. We check available information and actions, permissions and licensing requirements.
What happens if a step fails?
We design notifications, retries or manual handling and assign responsibility. Where necessary, we prevent retries from producing duplicate transactions.
Must we automate a large process immediately?
No. A small, defined task is often a useful starting point. After testing and practical use, we assess whether expanding is worthwhile.
Tell us about your situation
Discuss your recurring task
Choose one repetitive task as an example. We walk through the steps and discuss options, required integrations and licensing.