top of page

 2 entries is 1 too many 

We assist in advising and developing your integration environment.

System or software integrations ensure a link between different software systems which allows you to share, process and update data automatically. Our systems can be integrated with financial systems, HR systems, payroll systems, student administration systems, ESDH systems and whatever system is needed and desired. We ensure a free exchange of data which thus reduces manual work as well as save your time and money.

mTIME, mTS, mDUTY, mBUDGET and TimeEdit can receive data (master data, time records) from other systems via web services or their open APIs. Data in our products can be displayed in web services to the use of other systems. 

Why integrations?

What exactly makes integrations so amazing?

We integrate with

Is your system not on the list? Let us fix that for you!

It's up to you!

Put together the systems you think can solve your tasks best, instead of using some large systems that only fulfill half of your requirements.

The following are a few examples of the process of our standard integrations.

  • Save time and resources; save money.

  • Reduces manual work.

  • Automatically transfers data between relevant systems.

  • Manually collecting and managing data from multiple systems is a slow and flawed method.

  • Increase the bottom line.

  • Get interaction and connection between your relevant systems.

  • Remove ineffective data management where data is stored and managed in a variety of systems.

  • Data integrations give you increased real-time visibility of data to handle all the tasks your organisation needs to deliver and process.

  • Avoid making decisions based on outdated data.

  • Make better decisions if all data is available through integrations.

  • Focus on the quality of work when the data processes run automatically.

  • Manual data flow does not belong in 2021.

Example 1: SLS and mTIME

Leave data is transferred to SLS FRAV from mTIME every month.
Which data to be sent to SLS will be defined during the workshops in the implementation phase. It is configured in mTIME.

Customer's task:
Obtain the necessary certificates from MODST.

Set up and maintain integration.

Example 2: STADS, SIS master data for TimeEdit

STADS/SIS sends master data regarding teachers, classes, subjects, students and their relation to a class to TimeEdit through TimeEdit's REST API or Visma timemsystem's web services.
Details with regard to which fields of master data to be transferred are decided at a workshop.

Customer's task:
Retrieves data from STADS and displays it in files/web services, or submits it into TimeEdit via Visma timemsystem's web services or TimeEdit's open API (requires certification from TimeEdit).

TIMEmSYSTEM's task: 
Provides a web service where the customer can send master data in. If Visma timemsystem is to retrieve data from exhibited files or web services, development hours would be billed.

portrait of man

Should we talk about your integration options?

Thanks! You'll hear from us ASAP.

bottom of page