Connect Edifact and Medius

Connecting Edifact and Medius for a company could allow the structured exchange of business documents, such as invoices or purchase orders, between trading partners and financial systems. This could support automated document processing, reduce manual entry, and help ensure data consistency across procurement and accounts payable workflows.

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

Contact us

Why connect Edifact and Medius?

A company that operates both Edifact and Medius could consider connecting these systems to automate the exchange of business data and reduce manual intervention. Without such a connection, staff may need to enter the same information in both systems, which increases the risk of errors and consumes valuable time. Discrepancies can arise when records in one system are updated but not reflected in the other, leading to situations where decisions are based on outdated or incomplete information. This can impact operational accuracy and efficiency, especially when dealing with financial transactions or supply chain activities. If a connection were established, the types of data that could be exchanged would depend on the functions each system supports. For example, Edifact is widely recognized as a standard for electronic data interchange, which could be relevant for transmitting structured business documents. Medius is associated with invoice automation and accounts payable processes, so potential data flows could involve invoices, purchase orders, payment statuses, and related financial documents. The specific data that can be exchanged, and the way it is transferred, depends entirely on the technical capabilities and interfaces made available by each system’s API, and must be determined for each individual situation.

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 Edifact and Medius 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.