IFS Cloud is an enterprise platform designed for organisations with complex operational, asset and service requirements. It brings ERP, enterprise asset management, supply chain and field service capabilities together within one environment, making it particularly relevant for asset-intensive and project-based industries.
Typical users include organisations in aerospace and defence, energy and utilities, construction, transport, telecommunications and engineer-to-order or configure-to-order manufacturing. These companies often need to manage far more than financial transactions alone. They may be dealing with long asset lifecycles, serialised equipment, project delivery, maintenance, regulatory requirements and detailed audit trails across multiple parts of the business.
For finance teams, that operational complexity ultimately flows into cash. Payments, supplier activity, customer receipts, projects, assets and service operations all affect the financial position of the organisation. As companies expand across entities, banks and countries, connecting that operational core with the wider banking environment therefore becomes increasingly important.
One of the partners working in this ecosystem is Addovation, an IFS specialist supporting customers across implementation, integration, application development and ongoing managed services.
We spoke with Fredrik Wingren, CRO at Addovation, about the organisations best suited to IFS Cloud, what successful ERP programmes get right and why banking connectivity increasingly needs to be considered as part of the wider enterprise architecture.
What type of companies are the best fit for IFS, and what makes the platform stand out from other cloud ERP solutions?
“IFS Cloud is particularly well suited to asset-intensive and project-based organisations where operational complexity is a defining part of the business.
That includes industries such as aerospace and defence, energy and utilities, construction, transport, telecommunications and engineer-to-order or configure-to-order manufacturing. These organisations often need to manage serialised assets, complex projects, service activities and strong regulatory or audit-trail requirements alongside their financial processes.
What differentiates IFS is that ERP, enterprise asset management, supply chain and field service are brought together natively on one platform rather than treated as separate capabilities around the core.
The platform is also designed around what IFS calls the ‘moment of service’: the point where the organisation delivers value to its customer. That creates a broader operational perspective than an ERP environment focused mainly on back-office transactions.
IFS is also investing significantly in industrial AI and in an architecture that allows customers to evolve the platform over time without treating every major upgrade as a new implementation.”
As an implementation partner, where do you add the most value and what do successful ERP projects tend to get right from the start?
“Our role extends across the full lifecycle of the IFS environment rather than ending when the implementation goes live.
That starts with the ERP programme itself, but it also includes integrations with specialist platforms such as Cobase, AI-based applications built around IFS Cloud and the ongoing operation and development of the environment.
Through Addovation Engage, for example, we support customers after go-live with application lifecycle management, service desk capabilities, integration monitoring and structured governance. The idea is that customers should not experience a handover from one project team to another organisation as soon as the system launches.
At the same time, successful ERP projects still depend on getting the fundamentals right.
Strong executive sponsorship, a realistic scope, good-quality data and a dedicated customer team make a significant difference. We also see better results where organisations stay close to standard processes, phase the rollout sensibly and take change management seriously.
Technology can be implemented relatively quickly. Adoption, ownership and process discipline usually determine whether the value lasts.”
How are customer expectations around finance and treasury changing, and what does that mean for the role of the ERP?
“Customers increasingly expect core financial processes to work without requiring large amounts of manual intervention or specialist technical knowledge.
Bank connectivity is a good example. From the user’s perspective, sending payments and receiving banking information should increasingly feel like a standard part of the finance environment rather than a separate technical project.
At the same time, treasury teams want a much broader view of liquidity. They need to understand cash positions and cash flows across the organisation rather than looking at individual accounts or entities in isolation.
That changes the role of the ERP. It remains the core system for financial and operational processes, but it also needs to participate in a wider ecosystem where information moves efficiently between the business, treasury and the banks.
The expectation is increasingly that those connections should already be part of the architecture rather than something finance has to manage manually outside the ERP.”
Where does ERP-to-bank connectivity typically become challenging, particularly for companies operating across multiple banks and countries?
“Banking becomes difficult to standardise as soon as an organisation operates internationally.
Different banks and countries can introduce different connectivity methods, file formats, payment requirements and operational processes. It is not realistic for an ERP platform to accommodate every variation in the global banking landscape directly.
The challenge becomes greater as the number of banks and entities increases. If every banking relationship requires its own connection and its own maintenance, the ERP environment can gradually become surrounded by a large number of bank-specific interfaces.
That is where a specialist connectivity provider can simplify the architecture.
Instead of expecting the ERP to understand every individual bank requirement, a platform such as Cobase can provide a more standardised layer towards the banking landscape. The ERP can then continue to work with a consistent process while the bank-specific complexity is managed elsewhere.”
What does a strong ERP-to-bank setup look like to you, and what should companies consider when designing it?
“A strong setup should create a reliable electronic flow in both directions.
Payments need to move from the ERP towards the banks, while bank account transactions should return into the system without significant delay.
But receiving a bank statement is only part of the process. The real value comes from understanding what each transaction represents.
The system needs to determine whether a movement relates to a supplier payment, a customer receipt, a bank fee, interest or another type of financial transaction and then route that information into the appropriate accounting and reconciliation process.
That translation between raw banking information and the underlying business transaction is where much of the operational value sits.
There is also potential to take that further. Certain cash flows may eventually need to connect more closely with areas such as foreign-exchange exposure and hedging. That creates an opportunity for banking information to contribute not only to reconciliation, but also to broader treasury decision-making.”
Why do you like working with Cobase, and what does combining your ERP expertise with Cobase’s banking connectivity bring to customers?
“What works well about the combination is that each platform can concentrate on the role it is designed to perform.
IFS can remain the core business platform, supporting the organisation’s financial and operational processes. Cobase provides a standardised interface towards the banking landscape, while Addovation makes sure the complete environment works together from both a business and technical perspective.
For customers, that means they do not need to turn the ERP itself into a banking connectivity platform.
It is also representative of how we see the future of ERP more broadly. The strongest architecture is not necessarily one system attempting to do everything.
It is a strong core platform combined with selected specialist solutions, integrated into one coherent ecosystem.”
