RiOS vs spreadsheets

For checking revenue, a spreadsheet is the quickest start: export the CRM, export the invoices, put them side by side with VLOOKUP and you see differences. RiOS makes that same comparison continuously, across more systems at once, without exports, and turns every difference into a finding with an amount and an owner. A spreadsheet is a snapshot that someone has to build, maintain and read. RiOS is connected to the sources and keeps watching. For a first check, Excel is fine. For a check that has to be right every month, it is the weakest link.

Why so much revenue checking runs in Excel

In almost every B2B company there is a spreadsheet that holds revenue together. A list of contracts and their end dates. A tab with indexation per customer. A monthly reconciliation between order administration and the accounts. An overview of additional work per project kept by the project manager.

Those spreadsheets exist for a good reason. They fill the gap between systems that do not talk to each other. They are quick to make, everyone can read them, and they cost nothing extra. For a EUR 3M company with twenty contracts, a well-kept spreadsheet is often exactly enough.

The problem starts when the company grows and the spreadsheet does not change with it.

Where do spreadsheets leak?

Spreadsheets make mistakes in predictable places. None of these mistakes is foolish. They come with the tool.

• Stale exports. The comparison is only as current as the last export. An order that was changed yesterday is not in it.
• Keys that do not match. "Jansen Construction Ltd" in the CRM, "Jansen Constr." in the accounts. VLOOKUP finds no match, the row drops out, nobody notices.
• Formulas that do not follow. A new row below the range, a column someone inserts, a filter still switched on. The total is no longer right, but looks normal.
• One person who understands it. The spreadsheet was built by someone who knows why tab 4 has a manual correction. When that person leaves or is on holiday, the check stops.
• Versions. "Contracts_2025_final_v3_JB.xlsx" in the email, "Contracts_2025_final.xlsx" on the shared drive. Which one is leading?
• No follow-up. A difference in a spreadsheet is a coloured cell. Who calls the customer, who raises the invoice, and when is it resolved? That is recorded nowhere.

There is one more point that is often forgotten: exports containing customer data that go round by email, stay in download folders and are kept on laptops. Besides a control problem, that is also a privacy question. More on how manual work leads to leakage is in revenue leakage from manual administration.

What RiOS does differently

RiOS is a platform, currently in beta, that connects to the systems you already use, such as your CRM, billing, support and advertising platforms. The difference from a spreadsheet lies in five things:

1. No exports. RiOS reads the sources itself, with read-only access wherever possible. The comparison is as current as the systems.
2. Continuous. Not once a month at close, but over and over, so a new difference stands out as it arises.
3. Linking records. Deals, invoices, tickets and campaigns are linked together. Duplicates, orphan records and fields that contradict each other surface as findings in their own right, instead of silently dropping out of a VLOOKUP.
4. An amount per difference. Every finding gets a euro amount and a level of certainty, so you know where to start.
5. Follow-up. A finding becomes a task with an owner and a status. The euro amount stays attached until it is resolved.

Side by side

When a spreadsheet is enough

Do not reach for software too quickly. A spreadsheet is sufficient when:

• the number of customers, contracts or orders is small enough to review line by line;
• the data rarely changes, for example a handful of annual contracts with a single indexation date;
• one person is responsible for it and genuinely has time for it;
• you want to run the check once to see whether there is anything there.

A first CRM-to-billing comparison in Excel is in fact an excellent start. How to set it up is explained step by step in how to check CRM against billing. If you start that way, you know afterwards whether there is anything to recover and where.

When it stops working

The turning point usually comes with one of these signs:

• The monthly reconciliation takes more than a day, and the outcome is "roughly right".
• There are several spreadsheets on the same subject, and they contradict each other.
• A leak that was found and fixed earlier comes back without anyone noticing.
• A check stops when one person goes on holiday or leaves.
• You want to compare more than two systems: CRM, billing and support or usage.

At that point the spreadsheet costs more than it returns; it just does not show on an invoice. It shows in hours and in leaks that go unseen. How automatic detection takes over that work is covered in how do you detect revenue leakage automatically?.

Worked example: the cost of the monthly reconciliation

Worked example: suppose a company with EUR 9M in revenue has a financial controller reconcile CRM and the accounts in Excel every month. That takes a day and a half a month, 18 days a year. The check finds four differences a month on average, two of which are real leaks.

What the spreadsheet does not find, because it is not in the export or does not match:

• differences at customers whose name is spelled differently in the two systems;
• contracts with an indexation clause, because the contracts are not in the CRM;
• customers buying less, because the spreadsheet looks month by month and not across a year.

Suppose those three together come to EUR 60,000 a year. Then the spreadsheet costs 18 days and misses EUR 60,000. The amounts are an example. The question you ask yourself is the same: what does my current check not find, and how would I know?

Step by step: reviewing your spreadsheets

1. Take stock. Which spreadsheets are needed to make revenue add up? Contracts, indexation, additional work, reconciliations, forecast.
2. Note the owner and frequency of each spreadsheet. Who updates it, how often, and what happens when that person is not there?
3. Note the sources. Which system does the data come from, and how old is the export on average?
4. Test the key. How many rows do not match between the two sources? Count them. That number says a lot.
5. Check the follow-up. Take the differences from three months ago. Have they been resolved? Where is that recorded?
6. Decide what needs to be structural. Whatever changes often and sits between systems deserves a continuous solution. Whatever rarely changes can stay in Excel.

On data and security

One difference that is often underestimated: a spreadsheet with customer data is a copy outside your systems. It travels by email, sits on laptops and in shared folders, and after a year nobody knows where all the versions are. A platform that reads directly from the sources makes those copies unnecessary. How RiOS handles data, from read access to tokenising personal data before anything reaches an AI model, is set out on the security page.

For the broad comparison between Revenue Intelligence and other kinds of software, see the pillar Revenue Intelligence vs Business Intelligence.

Frequently asked questions

Should I throw away my spreadsheets if I use RiOS?

No. Spreadsheets for your own analyses and one-off questions stay useful. What disappears are the spreadsheets that exist only to put systems side by side by hand.

Is Excel not simply cheaper?

In licences, yes. In hours and missed leaks, often not. Count the days the check takes and estimate what it misses. Only then can you compare.

What if my contracts only exist in a spreadsheet?

Then that is the first place to look. Contract information that only lives in Excel is visible to no system at all. An audit or a first inventory shows which fields need to go into the CRM or ERP.

How do I know whether my spreadsheet contains errors?

Count how many rows do not match between two sources, and check a handful of rows by hand against the source system. If that turns up more than you expected, that is your answer.