Skip to content

Integrations

Work crosses boundaries. Information should too.

A good connection begins with understanding what needs to flow between systems. Let's map it together.

Let your systems talk to each other.

Examples of system areas you can map. The specific connection depends on your tools and needs.

Finance

Accounting system

Chart of accounts, receipts and relevant master data. Begin by agreeing on what should be read and what should be updated.

Map the data flow

Discuss integrations

Information

Document archive

Bring document access together. Agree on formats, access and where information should follow the task.

Agree on sources and formats

Discuss integrations

Insight

Analysis and reporting

Make clear which information the team needs next and who owns the definitions.

Describe needs and responsibilities

Discuss integrations

Three points to clarify before connecting.

Good preparation makes the direction clear.

  1. Map the sources

    Which systems hold the information and who is responsible for it?

  2. Describe the need

    What should be read, updated and followed up between systems?

  3. Clarify operations

    Who is notified when something goes wrong and how do you follow up changes?

Questions about connections.

The specific answer depends on your systems.

Do we have to change accounting systems?

We clarify this during the mapping stage. Begin with an overview of your systems, available interfaces and the information the workflow needs.

What does the system owner need to contribute?

An overview of data sources, access and technical prerequisites is a good starting point. Include requirements for operations and follow-up too.

Can we start with one system?

A focused use case can be a useful starting point. Establish which dependencies need to be in place before you can try the workflow.

What do you use today?

Bring your systems overview. We'll discuss how the tasks can connect.

Discuss integrations