Skip to content
Solutions

By structure, by role.

The same platform answers four questions, because four people look at the same service for four different reasons.

Request a pilot
Orange chairs at a table in soft evening light

Each solution in one paragraph

The tiles name the reader. These paragraphs name the question each page answers and where that reader starts.

  • By structure

    Multi-entity groups

    For a group that holds several legal entities. The page explains why the hierarchy is a primitive, how currency follows the entity, and why comparison stays inside the group.

    Four levels, two legal

  • By role

    Group finance

    For the CFO, the controller and FP&A. Consolidation with the definition, coverage and currency basis carried on every figure, FX that holds still after a restatement, and allocation that conserves to the minor unit.

    A number you can defend

  • By role

    Regional IT

    For the regional CIO or IT director. One operating company's own list, its local carriers and their local invoice formats, changes tracked to install, and onboarding that gets cheaper each month.

    Your entity, your carriers

  • By role

    Network operations

    For the NOC lead who owns the monitoring system. One read-level key, coverage on every number, and circuit roles that keep a quiet DR link recognised as a circuit doing its job.

    Works with the monitoring you already run

A long meeting table beside tall windows

One platform, four questions

The same inventory, the same bills, the same utilisation. What changes is the question each page answers and the permission boundary the reader sits inside.

How the four pages fit together

One group, read from four seats.

  1. Structure firstThe multi-entity page sets the shape: HoldCo, operating company, site, service, with money denominated and permission stopping at the operating company.
  2. Finance reads the groupGroup finance consolidates across entities in the presentation currency, with the rate id on every converted figure and the review queue in view.
  3. Regional IT owns the rowsEach operating company keeps its own list, its own carriers and its own changes, inside the boundary the structure drew.
  4. Network operations supplies the denominatorDelivered megabits come from the monitoring system the network team already runs, with coverage on every number, so the figure finance presents is one the network can stand behind.

Questions about fit

We are one company with many sites. Is this for us?

Riopex is built around the group with several legal entities and several currencies. A single company with many sites has a simpler problem, and the pilot page says plainly when the fit is better elsewhere.

Request a pilot

Which reader should request the pilot?

Whoever holds the invoices. Usually that is group finance or regional IT, and the first conversation brings in the network team when the monitoring key is discussed.

Can two readers in the same group see different things?

Yes, by design. A regional IT lead sees the operating companies they hold a membership in, and a group administrator sees every entity through one audited path. The security page sets out how the boundary is enforced.

One boundary, enforced thrice

Where do group finance and regional IT overlap?

On the inventory. Regional IT owns the rows and their evidence; group finance reads the same rows consolidated in the presentation currency. Both work from one review queue, so a correction made in one seat is visible from the other.

People crossing a plaza in low sun, seen from above

Send three invoices. A person replies with what they show.

Request a pilot