Bills
Bills arrive as CSV, XLSX, PDF or structured e-invoice files, or are typed in by hand. Each line is bound to its service only by an identifier, and the lines must add up to the bill’s total.
Every bill line, checkedPlatform
What you pay, what you signed, what exists
Every capability reads one record of the group’s services, each company in its own currency. The platform opens on the Overview: what needs you, the money, and the network and estate.
Capabilities
One record, read every way
Inventory
Every service the group pays for, in one record and on one map, priced from the latest billed month.
Contracts
Prices held as dated lines, never edited; notice deadlines worked out and rolled forward; rebates worked out from billed spend.
Findings
Each company’s latest billed months checked again against the inventory and the contract every night. A finding is worked on its own page, and a dispute cites it.
Group view
The whole group, one division or one company: spend by the group’s own structure, and budgets against actuals.
Bandwidth
Each link measured from the device, from your monitoring system or from the reports you upload. Cost per megabit, subscribed and delivered.
Orders
Every add, move, change and disconnect, through the group’s own approval policies, then handed to the provider and recorded.
Intelligence
Ask the assistant about the data you can see: it reads as you and changes nothing. No bill reaches a model until its personal identifiers are masked.
Integrations
Bills in every form they arrive, your monitoring on a read-level key, and provider mail through your own mailbox.
The desk
The Overview opens on what needs you
The Overview opens on three bands: Needs you, Money, and Network and estate. Each card opens the page behind its figure.
- Needs you
- To do, what waits for approval, bills to review and provider replies waiting, each counted for the people who may act on it.
- Money
- Budget against actual, the spend at stake in open findings, disputes and credits, and rebates due beside billed spend. The spend under review is counted once per service.
- Network and estate
- The estate map, link health now, contracts entering notice, orders in flight, and mobile lines with no activity or roaming. A coverage card holds the monitoring gaps.
- In detail
- Under the bands sits the spend in detail, and no figure appears twice on the page.
- Nothing to count
- A card says so in a sentence instead of showing a zero. If one band cannot be read, it says so and the rest still loads.
- Your own dashboards
- A person builds dashboards from a catalogue of widgets, beside the Overview, and can share one with the whole group.
To do
One list of what waits on you
To do gathers work items, open findings, disputes due a follow-up and bills marked wrong into one list.
Each row says why
What it is, why it waits, who holds it and when it is due. Each row opens the record’s own page.
Filter to what matters
What is yours, what nobody holds yet and what is due soon.
Assign, take, date
A work item can be assigned, taken and given a due date, and one past its due date is marked.
A finding counts once
An open finding counts once for its subject, however many months it has been flagged.
The bell
It counts what is new or assigned to you, and names unread alerts beside that count. Mark all read brings it down to the items you hold.
Notifications
Marks unread by the bell’s rule, so the two always agree.
Alike alerts, folded
A run of alike alerts about contracts, disputes or links folds into one line with its true count.
Support
A form inside the product, for a problem, a feature or a question. It reaches Riopex by email, and the reply goes to the person who sent it.
Connections
It reads the systems you run
Your providers’ bills in every form they arrive, your monitoring on a read-level key, and the mail you already send.
- Bills
- CSV, XLSX, PDF and structured e-invoice (UBL 2.1) files, or typed in by hand.
- Devices
- Polled directly over SNMP v3, reading traffic counters only from interfaces bound to a service.
- Monitoring systems
- Utilisation history read from the monitoring system you already run, or exported from PRTG or Zabbix and uploaded.
- Provider mail sent and read through a mailbox in your own mail system.
- Provider ordering
- A request handed to the provider by email, portal, phone or the provider’s ordering API, each handoff recorded.
- Your own AI engine
- Once a group administrator switches MCP access on, it reads your Riopex instance through its MCP server.
Questions
Questions about the platform
What does a card show when there is nothing to count?
It says so in a sentence instead of showing a zero.
What if part of the Overview cannot be read?
That band says so, and the rest of the Overview still loads.
Where is a finding worked?
A finding is worked on its own page, never as a work item.
An open finding counts once for its subject, however many months it has been flagged.
How do we ask Riopex for help?
Support is a form inside the product that asks whether you are reporting a problem, asking for a feature or asking a question.
A support request reaches Riopex by email, and the reply goes to the person who sent it.
Underneath
Between groups the boundary is the instance itself; inside it, the company.
Each group has a dedicated instance, with its own database, file store, credentials and processes. Inside it, the database keeps each company’s data apart.
SecurityStart with one company’s invoices
Three invoices, as the provider sent them, show what Riopex reads.
Request a pilot