AI or automation? What really lies behind most ‘AI solutions’

Artificial intelligence is currently on everyone’s lips and is now seen as the answer to almost every challenge. However, it is worth taking a closer look at what the term actually entails. Many requirements can be met more efficiently through traditional automation. So-called ‘agents’ play a key role in bridging the gap between the two worlds.

AI or automation? What really lies behind most ‘AI solutions’

In practice, the picture is clear: an estimated 80% of solutions marketed as AI solutions are essentially based on traditional rule-based automation. In other words, they rely on predefined, logical workflows that process structured processes reliably and quickly. Only around 20% of applications utilise genuine AI capabilities, i.e. systems that can make decisions independently based on facts and patterns.

In Dynamics 365 SCM and Finance, many business processes are based on clearly defined rules and structured data. This is precisely where automation delivers its greatest benefits and achieves a high level of effectiveness and efficiency. Typical areas of application include invoice posting, triggering purchase orders, reporting, and master data reconciliation. Such workflows can be automated reliably and cost-effectively without the need for complex AI models.

Important: Automation follows clearly defined rules: if condition A is met, action B is carried out. These processes are characterised by being deterministic, which means that the outcome is predictable and reproducible. However, this requires that the underlying rules are defined fully and correctly.

AI, on the other hand, becomes relevant where data is ambiguous or decisions must be made based on patterns and probabilities. In Dynamics 365 SCM, this applies to areas such as demand forecasting, traditional MRP processing, the generation of intelligent purchasing recommendations, supply chain forecasting in procurement, dynamic pricing in sales, order matching and the execution of stock movements.

Coexistence between automation and AI expertise

In practice, automation and AI expertise are not mutually exclusive; they complement one another. Many business processes benefit from a targeted combination of both approaches: rule-based workflows are automated, whilst AI steps in where context, pattern recognition or judgement are required. The following examples illustrate how this interaction works in practice.

Example 1

MRP (Material Resource Planning)

A classic example of where the two worlds overlap.

This is classic rule-based logic: demand quantities × bill of materials × lead times = order proposal.

This is deterministic and unambiguously automation.

But what feeds the primary demand?

  • If the primary demand comes from a fixed production plan or a customer order → pure automation, MRP does the calculations.
  • If the primary requirement is determined by a demand forecast — i.e. based on historical sales data, seasonality, external market signals — then that is demand forecasting, and that is precisely where AI expertise comes into play.

Example 2

Email processing

Email processing workflow:

  • AI classifies the incoming email (complaint? enquiry? praise?)
  • Automation routes it to the correct team
  • AI suggests a response

Automation sends the approved response and archives the case.

In Dynamics 365 SCM, this is the dividing line between Master Planning (rule-based, MRP logic) and Demand Forecasting (AI/ML models that provide the input for MRP). The two worlds therefore work together sequentially: AI knowledge generates the forecast → automation processes it via MRP.

 

In Dynamics 365 Finance, for example, this includes the automatic posting of supplier invoices, cash flow forecasting, or anomaly detection in financial control or fraud detection.

Here, AI delivers real added value by identifying patterns that go beyond fixed rules.

Unlike automation, AI-driven knowledge enables systems to learn from data, assess uncertainties and make independent decisions based on facts. This also applies when the situation is not fully pre-structured.

So-called agents are playing an increasingly important role: these are software-based units that carry out tasks independently, prepare decisions and interact with other systems.

In ERP contexts, such as Dynamics 365, agents can, for example, analyse incoming queries via the MCP server, initiate appropriate processes and, in cases of uncertainty, consult AI models for decision-making. In doing so, they combine automation (for structured workflows) with AI expertise (for complex assessments). The key advantage lies in orchestration: agents control when a process is executed based on rules and when AI support is required.

Companies should therefore not only distinguish between automation and AI knowledge, but also assess where agents can be usefully deployed as a connecting layer.

A common mistake in practice is to tackle automation problems with expensive AI solutions – or, conversely, to attempt to map complex decision-making processes using rigid rule sets. Both approaches require different technologies, skills and investments. Making the correct diagnosis at the start of a project saves considerable costs and effort.

The risk of hallucinations

A term that is attracting increasing attention in the context of AI is ‘hallucination’: AI systems, particularly generative models such as Copilot in Dynamics 365, can generate information that sounds plausible but is factually incorrect. The system ‘invents’ connections because it combines patterns from training data without knowing the true facts.

It is important to make the distinction here: with pure automation, there is no hallucination. The system calculates deterministically. An error is always attributable to an incorrectly defined rule. This means that the system behaves exactly as it was programmed. With AI knowledge, however, the risk is real, though it manifests differently depending on the type of application. Predictive models (e.g. demand forecasting) produce faulty forecasts when training data is poor – this is a model error, but not a classic hallucination. Generative AI components, on the other hand, can actually generate statements that are factually incorrect when operating outside their validated knowledge domain.

The most effective protection against hallucination is not a technical feature, but an organisational approach: human validation remains essential. AI knowledge provides recommendations and forecasts – the responsibility for the final decision lies with humans. In addition, a high-quality, representative dataset and clearly defined system boundaries significantly reduce the risk.

Conclusion

Efficient ERP solutions are not created solely through the application of AI expertise, but through the interplay of automation, targeted use of AI and intelligent agents. By strategically combining these three building blocks, organisations can create business processes that are scalable, efficient and, at the same time, adaptive.

It is therefore advisable for companies to ask a clear question at the outset of any planned project: Is this a logical, rule-based process, or is it a matter of making a decision based on facts that is not entirely predictable? This distinction is the crucial first step towards successful and cost-effective implementation.

Are you interested in this topic? I would be pleased to answer any queries you have.

Andreas Pascutto, Head Sales ERP

andreas.pascutto@!ambit-group.com
+41 79 351 00 38