Four processes in the administration and finance department already being automated with Microsoft 365

If your administration team is still approving invoices by email, circulating contracts in PDF without knowing which is the final version, and updating the closing Excel manually, the result is always the same. Duplicated work, lack of traceability, and audit risk. The Microsoft 365 licence already includes the tools to automate exactly that. Without contracting anything additional. Without extra Power Platform licences.

With SharePoint, Microsoft Lists, Microsoft Forms, and Power Automate (solutions included in most M365 plans) it is possible to transform the most critical processes in the finance area. When a process requires more control, complex logic, or a personalised interface, SharePoint Framework (SPFx) allows custom solutions to be built within the same tenant, without additional Power Platform licences. Here we explain which they are and how other organisations are already solving them.

1. Internal expense request management

The usual situation

Expense requests — such as per diems, materials, or one-off services — reach the manager by email, with no common structure or format. Approval is given by replying to the email. There is no centralised record of who requested what, when they requested it, or what the outcome was. As a result, the controller has no visibility of the status of requests without asking each person individually.

How is it automated?

• Standardised form in Microsoft Forms or Lists, which requires all necessary information to be included before the request reaches the manager.
• Automatic approval workflow with Power Automate, with notification to the manager, recording of the decision, and closure of the cycle without manual intervention.
• Complete history of requests, statuses, and decisions visible in real time for the whole team, without needing to ask.

How is it automated with SPFx?

An application deployed directly in Teams and built with SharePoint Framework and AI centralises the entire request cycle. A standardised form with mandatory fields, automatic routing to the relevant manager, an approval workflow with notification, recording of the decision, and closure of the cycle without manual intervention. The complete history of requests, statuses, and decisions is visible in real time for the whole team from a single panel. No need to ask. Everything runs within the Microsoft 365 tenant, without additional Power Platform licences. With AI integrated into development, this type of solution is built in days, not weeks.

When does it make sense to implement it?

When the team handles a recurring volume of internal requests and manual follow-up consumes the administration manager’s time. If the most repeated question in the department is “what is the status of my request?”, automation eliminates that friction.

2. Supplier contract tracking and expiry management

The usual situation

Contracts are scattered across network folders, the responsible person’s email inbox, and at best, an Excel spreadsheet that nobody updates regularly. Expiry dates get missed. Contracts are renewed out of inertia or identified after the deadline, when there is no longer any room for negotiation.

How is it automated?

• Centralised repository in SharePoint with structured metadata: supplier, amount, start date, expiry date, and contract status.
• Power Automate sends automatic alerts 30, 15, and 7 days before expiry to the relevant manager.
• Full visibility of the status of all contracts in a single panel, accessible to the team without depending on anyone to “update the Excel”.
• A portal built with SharePoint Framework centralises all active contracts with structured metadata. The workflows configured within the portal send automatic alerts 30, 15, and 7 days before expiry to the relevant manager. A real-time dashboard displays the status of all contracts without depending on anyone updating an Excel spreadsheet. The change history is recorded natively for any subsequent review. Everything runs within the Microsoft 365 tenant, without additional Power Platform licences. With AI integrated into development, this type of solution is built in days, not weeks.

When does it make sense to implement it?

When the organisation manages more than 10–15 active supplier contracts and expiry dates represent a real risk to operational continuity or unfavourable economic conditions.

3. Purchase approval portal with multi-level logic

The usual situation

The purchase approval process involves complex rules that email cannot handle. For example, low amounts go to the area manager, high amounts to the finance director, and certain categories require additional compliance validation. The result is an opaque process where nobody knows what stage each request is at, who needs to approve it, or how long it has been pending.

How is it automated with SPFx?

An application deployed directly in Teams, built with SharePoint Framework and AI, centralises the entire process. A request form with mandatory fields, automatic routing by amount and category, sequential or parallel approval workflows according to business rules, a real-time dashboard for the controller, and an exportable history for audits. Everything runs within the Microsoft 365 tenant, without additional Power Platform licences.

When does it make sense to implement it?

When the approval process has more than two levels, the routing rules are complex, and the volume of requests is high enough to justify a custom interface.

4. Document management portal for audits

The usual situation

When an audit arrives, the team spends days locating documentation scattered across network folders, email inboxes, and different systems. Demonstrating the traceability of a specific approval can become a task that takes hours. Giving external auditors access means sharing entire folders or sending documents by email, with no control over what has been shared or with whom.

How is it automated with SPFx?

A portal built with SharePoint Framework centralises all documentation with metadata, versions, and native audit logs. Approval workflows automatically generate an exportable history with the user, date, and decision at each step. The portal allows controlled access to be granted to external auditors — with limited permissions and an expiry date — without them needing a Microsoft 365 licence and without sharing more information than necessary. With AI integrated into development, this portal is built and deployed in days. No external infrastructure. No additional licences.

When does it make sense to implement it?

When the organisation is subject to recurring external audits or regulatory compliance requirements, and document preparation consumes significant team time. Also when staff turnover means that knowledge of where each document is depends on a specific person rather than the system.

The next step: choosing where to start

None of these four processes requires contracting additional tools or Power Platform licences. All of them run on the Microsoft 365 infrastructure the organisation already has in place. SharePoint, Microsoft Lists, Microsoft Forms, and Power Automate are available in most M365 Business and Enterprise plans.

For a CFO or controller looking to evaluate this, the most practical starting point is to identify the process that generates the most friction today — the one that consumes the most time, generates the most repeated questions, or carries the most audit risk.

At Itequia, as Microsoft partners, we help organisations configure these processes on the M365 licence they already have. Want to know where to start? We offer a free initial review of your administrative processes. Get in touch.

Frequently asked questions

Do you need to purchase additional Power Platform licences to automate processes in the administration and finance department?

No. Neither solutions built with native M365 tools — such as Microsoft Lists, Forms, and Power Automate — nor solutions built with SharePoint Framework (SPFx) require additional Power Platform licences. In both cases, everything runs within the Microsoft 365 tenant the organisation already has. The difference lies in the level of customisation: native tools handle the most common cases, and SPFx comes in when the process requires complex logic or a custom interface.

Are there other processes in the administration and finance area that can also be automated with Microsoft 365?

The four cases in this article are the most common, but not the only ones. Other processes organisations are solving on M365 include: fiscal document management with expiry alerts, budget tracking by department, travel expense management with integrated forms and approvals, and financial data reconciliation with Power Query. In all cases, the starting point is the same M365 infrastructure.

Can the administration team manage these workflows autonomously, or will they always need technical support?

Basic processes — purchase approvals, expense requests, expiry alerts — can be configured and maintained by an M365 administrator profile without development knowledge. When a process requires complex logic or a custom interface, specialist technical support is needed.

What is the starting point for an organisation that has not yet implemented any of these processes?

The usual starting point is a review of the M365 environment the organisation already has: which tools are active, which are underused, and which process generates the most friction today. From there, a scoped pilot of a few weeks is usually enough to validate the approach before scaling.