Your entity, your carriers.
You already know your sites and your services. Riopex puts the same list in a form group finance can read, with evidence behind every charge.
Request a pilot
The fit
- The reader
- Regional CIOs and IT directors running connectivity for one or several operating companies.
- The question
- What does my operating company actually run, and what evidence sits behind every charge on it?
- The constraint
- You see the operating companies you hold a membership in, and the group decides when that widens. The daily work stays the same: new sites, upgrades, disconnects, disputed charges and a carrier who changed the invoice layout again.
- Where it starts
- Onboarding a group is months of human effort, so budget for it as you would any data migration. The machinery that makes month two cheaper than month one is treated as product.
Outcomes
One list you can trust
Services arrive from invoices, carrier portals, contracts, the CMDB, router configs and an engineer's memory, reconciled with the conflicts left visible. Every field says where it came from, and a correction supersedes rather than overwrites, so the earlier claim survives.
Local formats, handled locally
Bilingual invoices, Arabic-Indic numerals, Hijri issue dates and three-decimal currencies are first-class cases. A saved mapping is keyed to the shape of a specific header row, so two formats from the same carrier each keep their own.
Changes with a paper trail
Requests run from draft to install with the approval, the budget check and the carrier handoff reference recorded. When a disconnect fails to stick, the acknowledgement you sent is already attached to the case.
The first month
Your operating company first, your carriers first, your invoices first.
- Your listYour services are entered from your three invoices and whatever you already hold: a spreadsheet, a portal export, the CMDB. Each row shows where every field came from.
- Your formatsEach carrier's invoice layout is learned once as a saved mapping keyed to its header row. Bilingual labels and Arabic-Indic digits are handled on the way in.
- Your queueAmbiguous identifiers and unclassified charges wait in the review queue, ranked, so you pick rather than type. Every decision is recorded with your name on it.
- Your changesThe first MACD request is raised against a service on the list, and it runs from request to install with the approval and the handoff recorded. Month two starts with the mappings already saved.
Capabilities that serve this role
Questions from regional IT
How much of my team's time will this take?
Most of it in the first month, in the review queue, deciding rather than typing. After that the saved mappings do the work, and the stance below says how we measure it.
Will group finance see my entity's data?
Through the audited group path, yes, consolidated in the presentation currency and with the same evidence you see. Corrections stay in the entity, with the actor recorded.
My carrier changes its invoice layout every year.
Then the new layout becomes a second saved mapping, keyed to its own header row, and the old one keeps working for the older documents. A changed layout opens a review item rather than a wrong figure.
Can I keep using my own circuit references?
Yes. Your identifiers are stored exactly as written, beside a normalised copy used for matching, and a service carries as many aliases as your sources give it.
Month two costs less than month one
- Stance
- That is a mechanical claim, not an aspiration. Mappings are saved against the fingerprint of the header row, bilingual labels are learned as synonyms, candidates are ranked so a person picks rather than types, and a bad batch is undone in one move. Import cleanup fixes placeholder IDs, cells holding several IDs and 100M/20M bandwidth pairs in the import, and carrier confirmation has each carrier check what you hold for it. If the second month is not cheaper than the first, the onboarding machinery is not doing its job.
