Skip to Content

Connect Medius and InRiver

Connecting Medius and InRiver could enable a company to transfer product information and related financial data between the two platforms. This integration could support better coordination between product management and accounts payable processes, reduce manual data entry, and provide more accurate and timely information for business operations and decision making.

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

Contact us

Why connect Medius and InRiver?

A company operating both Medius and InRiver could benefit from allowing these systems to exchange data to improve efficiency and accuracy across business processes. Connecting the two could reduce the need for manual data re-entry, which often leads to errors, inconsistencies, and wasted time. Without integration, teams might have to update product or financial information separately in each system, resulting in records that drift apart over time. This misalignment could lead to decisions being made based on outdated or incomplete data, undermining operational effectiveness. Common types of data that could be exchanged between systems like Medius, known for spend management and invoice automation, and InRiver, known for product information management, include product data, supplier information, pricing details, and invoice records. The exact nature and scope of data that can be exchanged depends on the APIs and data models each system provides, and should be determined for each specific 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 Medius and InRiver 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.

About these systems

Read more about each system and what it can be connected to

Looking to connect these systems?

Talk to us about what your setup needs. No obligation.

Contact us