Medverkande

Jonny Norr
Key Account Manager Dynamics
Karin Hult
Expert Consultant, Dynamics
Maja Wennstig
Integration Consultant

Summary:

Automating bank flows in Microsoft Dynamics 365 doesn’t have to mean a large and complicated project. The most important thing is to start by mapping today’s processes, identifying manual steps, and prioritizing the improvements that provide the greatest benefit.

A functional bank integration is not just about transferring files between the ERP system and the bank. It also requires clear areas of responsibility, secure information transfer, and traceability when something goes wrong.

“Don’t start with the technology. Start by identifying where manual work costs the most time and creates the greatest risk.”
Karin Hult, Expert Consultant Dynamics at Implema

Participants

Jonny Norr
Key Account Manager Dynamics
Karin Hult
Expert Consultant, Dynamics
Maja Wennstig
Integration Consultant

In this episode of Implema Talks, Jonny Norr, Key Account Manager Dynamics, speaks with Karin Hult, specialist in finance processes in Dynamics 365, and Maja Wennstig from Implema’s integration team about how companies can get started with bank integrations, why it is often enough to start with a single payment flow, and how the solution can then be developed step-by-step.

Insights

  • Start by mapping existing bank flows and identifying manual steps, wait times, discrepancies, and risks.

  • Prioritize the parts of the process where improvements can create the most value.

  • It is often enough to start with a single flow, such as accounts payable, and then build from there.

  • Security and traceability are crucial for the integration to function reliably.

  • Clear areas of responsibility and routines for exception handling are needed for automation to work in everyday operations.

  • A review of bank flows can also reveal other opportunities to streamline finance processes.


Where do you start with bank integrations in Dynamics 365?

For a CFO or finance manager looking to reduce manual work between the ERP system and the bank, bank integrations can seem like an extensive technical project. But it doesn’t have to be.

The first step is understanding how existing bank flows work.

“We start by looking at what the bank flow looks like today. Where are the manual steps, discrepancies, wait times, and risks? Then we look at which parts we need to prioritize and where it is most relevant to start improving,” says Karin Hult.

By mapping the entire process, it becomes easier to identify where automation can make the biggest difference. This could involve reducing manual file transfers, simplifying payment handling, or improving reporting back from the bank.

The point is to start from the needs of the business, rather than starting with the technology.


What needs to be in place to build a bank integration?

Once the most important areas for improvement have been identified, the technical solution needs to be designed. This is where the integration team comes in.

First, the company needs to clarify which banks, entities, and bank accounts should be included. It also needs to be clear which payment types will be sent and what information the finance function needs to receive back.

“We need to understand what the information looks like when it leaves Dynamics 365, what the bank wants to receive, and how the communication should take place. We also need to ensure that the transfer is secure, so that no one can change the files along the way,” explains Maja Wennstig.

It is therefore about both creating a functional exchange of information and ensuring that the transfer takes place in a controlled manner.


Do you have to automate all bank flows at once?

No. On the contrary, it can be wise to start with a defined flow and then develop the solution step-by-step.

For example, a company can start by automating the transfer of payments between Dynamics 365 and the bank.

Once the first flow is working, the solution can be expanded with additional payment types, accounts, or other parts of the banking process.

“Often it’s enough to start with one flow, for example payments, and then build further from there,” says Maja.

A step-by-step approach makes it possible to prioritize the improvements that are most relevant to the business and gradually develop the automation.


How do you ensure the bank integration works in daily operations?

A technically functional integration is not necessarily the same as a well-functioning finance process.

For automation to create real value, it needs to be clear which steps are handled automatically and which still require human intervention.

This is especially true when something deviates from the normal flow.

“It is important that we start from the customer’s processes and responsibilities. It should be clear what happens automatically and what you need to do if something deviates,” says Karin.

This means that ways of working, distribution of responsibility, and routines for exception handling need to be part of the solution from the very beginning.


Why is traceability so important in bank integrations?

When payments are sent automatically between the ERP system and the bank, it must also be possible to follow what happens to the information.

If a payment does not reach the bank, it must be possible to identify where in the process it was stopped and who is responsible for fixing the problem.

“For us, traceability is central. If a payment doesn’t reach the bank, you should be able to see where in the chain it stopped. It should also be clear who needs to take action,” says Maja.

Without that control, there is a risk that automation won’t reduce manual work, but simply move it to another part of the process.

It is therefore important from the start to ensure that the solution provides sufficient insight into the information flow and support for handling exceptions.


How can bank integrations evolve over time?

A mapping of bank flows can provide more insights than those forming the basis for the initial integration project.

When the company goes through the process, other manual steps often become visible. This can open up further improvements that were not obvious from the start.

“The review often makes other manual steps visible as well. Then you can choose which improvements provide the most value to take further,” says Karin.

In this way, work with bank integrations can become part of a broader development of finance processes in Dynamics 365.

The important thing is to start where the need is greatest, create a functional flow, and then build further based on business priorities.

 

Share your experience:

Karin Hult

Karin Hult

Expert Constultant Dynamics

Whether you have a question, want to learn more about our solutions, or are simply curious how we can support your business – we’d love to hear from you.

Contact us directly using the form below!