Connect Medius and Aca

Connecting Medius and Aca for a company that uses both could enable the transfer of relevant data between the two systems, supporting more efficient workflows and reducing manual data entry. Such a connection could help ensure consistency of information and facilitate better coordination between processes managed in each system.

You can build this integration on the System2System platform. We design the connection between Medius and Aca around the way you work — not as an off-the-shelf connector, but to fit your systems.

Contact us

Why connect Medius and Aca?

A company that operates both Medius and Aca could benefit from connecting these systems to enable more efficient and accurate data exchange. Without such a connection, staff may need to enter the same information separately into each system, increasing the risk of errors and wasted effort. Over time, records in each system could diverge, with updates made in one place not reflected in the other. This situation can lead to decisions based on outdated or inconsistent information, which may affect financial accuracy, compliance, or operational effectiveness. If a connection were established, it could allow for the automated transfer of key business data between Medius and Aca. The types of information exchanged would depend on the core functions of each system. For example, if one system is used for invoice processing and the other for enterprise resource planning, data such as supplier details, invoice statuses, payment information, and purchase orders could be candidates for exchange. This could help to ensure that both platforms reflect the most current and accurate data, supporting better business processes and reporting. Ultimately, the specific data that can be exchanged between Medius and Aca depends on what each system makes available through its API, and must be determined on a case-by-case basis.

How System2System builds an integration

Connectors

We connect to each system through the interface it offers — an API, a database, a file exchange or a webhook — and handle authentication, rate limits and retries.

Mapping

Fields rarely line up one to one. We map and transform the data so both systems receive it in the shape they expect.

Workflow

We define what triggers an exchange, in which direction data flows and which system takes precedence when the two disagree.

Monitoring

Every exchange is logged. Failures are flagged and can be replayed, so nothing disappears without anyone noticing.

What can actually be exchanged?

That depends on what Medius and Aca make available through their APIs, on the licences and modules in use, and on the version each system runs. Which records are synchronised, in which direction and how often, is something we determine together before any work starts.

We are happy to look at your specific situation and tell you what is feasible — including when the answer is that it is not.