
Centralized inventory, visibility and billing for multi-entity groups.
Built for large enterprises holding multiple operating companies. Unify your telecom inventory across the group, manage billing in each entity's own currency, and gain total visibility into your network.
Request a pilot

One join, in two steps
- What you payStep one, from files. Bills as CSV, XLSX or PDF become checked lines in their billed currency, with a human review queue for anything uncertain.
- What you signedContract price lines per service, site and country. A bill line priced above or below its contract opens a finding.
- What existsOne inventory across the group, with provenance on every field. Billed but not held, or held but never billed, opens a finding.
- What was deliveredStep two, once your monitoring system is connected: cost per megabit delivered. Until then, cost per megabit subscribed works from bills.
Inside the platform
Built today, each on the capability page that carries it.
Contracts and pricing
Price lines, amendments and notice deadlines, with alerts.
Findings and disputes
Each gap the files show, and disputes that carry their evidence.
Bundles
One charge split to its member services, counted once.
Carrier confirmation
The carrier checks what you hold; its answers become evidence.
Budgets
Budgets against actuals, and a budget check on every order.
Group dashboards
The cost flow from group to carrier, and the estate on a map.
Identity
SSO, SCIM, MFA, country-scoped grants and an append-only audit trail.
The assistant
Answers over your own data, with your permissions, on your AI key.
Who it is for
Multi-entity groups
Several legal entities, each with its own carriers, currency and books.
Regional IT
Local carriers and local invoice formats, per operating company.
Network operations
A cost against the traffic your monitoring system already records.
By the numbers
Each figure can show its working. The catalogue counts come from open reference data and reproduce from the same query; the carriers and monitoring systems counted here are named below.
- 2,231
- operators in the carrier catalogue
- 228
- countries and territories the catalogue covers
- 10
- carriers we build for first, where the invoices are hardest
- 7
- monitoring systems named, each with its status label
- 1
- read-level key is the whole ask of your network team
- 3
- currency layers on every converted figure: as billed, functional, presentation
Carriers
The catalogue indexes 228 countries and territories · 2,231 operators, so an invoice matches a carrier and its parent group. The marks name operators in the catalogue to identify them: no carrier endorses Riopex or partners with us, and we earn zero carrier commission.
Global carriers
Regional carriers · Americas
Regional carriers · EMEA
Bilingual invoices, Arabic-Indic numerals, Hijri dates, three-decimal currencies: the ten formats the parser work starts with.
Regional carriers · Asia-Pacific
Type two letters of a carrier's name, its brand or its country. Each match shows its country and region.
Monitoring systems, and where each stands
Step two of the join starts once one of these is connected, over one read-level key. None is read in the product yet: PRTG is in progress, tested against recorded fixtures, and six more are planned.
Seven systems, one connector interface
- PRTGIn progress
- SolarWindsPlanned
- ManageEngine OpManagerPlanned
- ZabbixPlanned
- LibreNMSPlanned
- Cisco MerakiPlanned
- Fortinet FortiAnalyzerPlanned
The argument, on Why Riopex
Three bets
Group hierarchy first, regional carrier depth, and cost per megabit delivered.
Our commitments
Six of them, from a read-only monitoring key to zero carrier commission.
Two numbers worth knowing
What surfaces once an inventory exists, and how many invoice formats a group meets.
Questions we hear
What do you need from us to start?
Three invoices from one operating company, as the carrier sent them, and how your entities are arranged. A person replies with what they show.
What does Riopex show before the monitoring system is connected?
Everything the files prove: bills reconciled against contracts and the inventory, per operating company, with cost per megabit subscribed. Cost per megabit delivered follows the read-level key.
How long does onboarding take?
Months rather than weeks, budgeted openly. Month two costs less: saved mappings read each carrier's next spreadsheet invoice without being set up again, import cleanup fixes placeholder IDs once, and carriers confirm your inventory for you.




