Excel Automation: A Partner, Not a Project

The search for an Excel automation partner in Switzerland is a priority for many finance departments in Swiss SMEs. Critical processes in month-end closing, reporting, or planning are based on Excel files. The pressure on finance teams is high. The closing must be on time, while management and the board of directors demand new analyses at short notice. The desire is therefore clear: recurring procedures should become faster, more secure, and less dependent on individuals. However, the idea of what such a partner should provide is often incomplete. It involves more than the one-time creation of a macro or script.

The Search for a Provider is Often Misleading

Many finance managers view automation as a one-off project. The task is assigned to the internal IT department or an external developer. A script or a small application is created. The problem seems to be solved, and the task is handed back to the finance team.

The difference in perspectives is fundamental. For the finance team, the reporting process is a recurring, critical responsibility. For a project-based developer, it is a completed task. Once the solution works and is handed over, they move on to new projects. However, the long-term responsibility for its function and data quality remains with the finance team, which is not equipped for maintenance.

However, this project-based approach carries significant risks. Financial processes are not static. They evolve with the company. The ERP system receives updates, legal requirements change, or the structure of the reporting system is adjusted. A solution created once can quickly become unusable due to such changes or, worse, deliver incorrect results without being noticed.

After the handover, the responsibility for control and maintenance lies once again with the finance department. They often lack the technical resources and time to understand the code, adapt it, and ensure it functions correctly. The external developer may no longer be available. The internal IT department has other priorities. The supposed solution thus becomes a technical debt that makes the process more fragile than before.

The Challenge of Ongoing Maintenance

Modern business software is subject to constant change. Providers like Microsoft continuously update their cloud services, such as Microsoft 365. New features, for example for Copilot, are rolled out gradually and at different times for different user groups (Microsoft 2026). A stable, unchanging software environment does not exist in the cloud. This continuous development is necessary for security and innovation but creates a challenge for automations built upon it.

An update to Excel, Windows, or a connected database can disrupt an existing automation without warning. A process that ran flawlessly last month fails this month. The error message is cryptic. For subject-matter experts without deep programming knowledge, troubleshooting is difficult and time-consuming. The month-end closing is at risk.

Concrete examples of disruptions are numerous. The ERP system starts exporting a CSV file with a semicolon instead of a comma as the delimiter. A new company security policy blocks the execution of VBA macros from untrusted sources. A column in a data export is renamed or moved. In themselves, these are minor changes. For a rigid, unmaintained automation, however, they can lead to a complete failure.

But the changes don't just come from the software. The business itself also evolves. A new cost centre is introduced, the structure of the chart of accounts changes, or an acquisition needs to be integrated. Each of these changes may require an adjustment to the automation logic. The finance team's priority is a correct and timely closing, not debugging a script. Dependence on a solution that is not actively maintained creates a new, incalculable operational risk.

What Makes a True Partner

A partnership goes beyond the one-time delivery of a file. It is a service that focuses on the outcome. It's not about the tool — be it a script, a macro, or an application — but about the reliably functioning process.

A true partner takes responsibility for the result: the correct and timely report, month after month. This includes ongoing monitoring of the automation, proactive adaptation to system changes, and ensuring its operability. The partner ensures that the automation continues to work even after a software update or a change in the chart of accounts.

The metaphor of a chain illustrates this. The process chain extends from data export from the ERP, through data transformation and enrichment, calculations and validations, to the creation of the final report. A project approach might deliver one strong link in the chain. A partnership approach ensures that the entire chain holds — today and in the future. It monitors the interfaces, validates the results, and ensures that the information reaches the recipient correctly.

This approach creates stability. This is crucial, especially in an unstable business environment. Research shows that digital transformation has a positive and statistically significant effect on the quality of accounting information, particularly under volatile conditions (Accounting, Finance and Computational Intelligence 2024). A maintained automation is a building block for this stability. It delivers reliable figures, even when the market environment or the company structure changes rapidly.

The Risks of Complex and Flawed Reports

Manual Excel processes are often not only slow but also complex and confusing. This complexity is a risk factor in itself. It leads to errors that are difficult to find. It also creates a strong dependency on the few employees who understand the file. If such a key person leaves the company, the process is at risk.

Studies also indicate a link between the complexity of financial reporting and the risk of irregularities (Journal of Management and Business Solutions 2024). An opaque process complicates internal and external audits.

Automation reduces this complexity. It replaces manual steps with a standardised, documented procedure. Essential processing steps are traceable and auditable. An auditor's question — 'Where does this number come from?' — can be answered clearly in a well-documented, automated process. The data flow from the source system to the report is transparent. This shortens audit times and increases security.

Good automation can also include built-in controls. Such plausibility checks can automatically detect anomalies in the data. Examples include variance analyses against the previous month or budget that monitor specific thresholds. Research in fraud detection shows that machine learning methods like neural networks can achieve high accuracy in identifying patterns and anomalies (Journal of Management and Business Solutions 2024). A partner can implement such checks as part of the automation, thereby strengthening internal control.

At the same time, reporting requirements are increasing. A current example is sustainability reporting (ESG). Disclosure rates worldwide rose from 89.2% to 97.1% between 2019 and 2024 (Delgado Sanchez 2027). This data often comes from various systems, not just the ERP. Collecting and preparing it manually in Excel is laborious and error-prone. A robust, maintainable automation becomes a necessity here to manage the growing workload.

What You Can Do This Month

Instead of looking for a developer or a tool, you can define your requirements from the perspective of a service. This changes the basis for discussions with potential providers.

• Document the most important, recurring Excel process in your closing. Which report is the most laborious and error-prone? Note the data sources, the manual steps, and the estimated time you and your team spend on it each month.
• Define the desired outcome. Which report is needed, when, in what format, and with what degree of accuracy? Who are the recipients, and what decisions are based on the report?
• Formulate your expectations of a partner. Are you looking for someone to build and hand over a solution? Or are you looking for a partner who will ensure ongoing operation and maintenance throughout its entire service life?
• With potential providers, check how they handle maintenance and adaptation to system and business requirements. Ask about the process for upkeep, not just the cost of creation.

This change in perspective — from a one-off project to a continuous service — is a crucial step. It helps to find a sustainable solution for automating your financial processes that will function reliably in the future.

Microsoft, Excel, Microsoft 365, Power BI, Dynamics and Copilot are registered trademarks of Microsoft Corporation. SAP is a registered trademark of SAP SE. Abacus is a registered trademark of Abacus Research AG. bexio is a registered trademark of bexio AG. Sage is a registered trademark of The Sage Group PLC. Odoo is a registered trademark of Odoo S.A.