Growth should generate revenue, not paperwork.

When matching numbers are not enough

Not because vehicles need to charge constantly, but because being connected creates valuable flexibility. On sunny, windy days, such as May 1st 2026 in the Netherlands, wholesale electricity prices turned negative, reaching -48 cents per kWh. Drivers on dynamic contracts could literally get paid to charge their cars. Yet evening peak demand remains a serious challenge.Consider a relatively ordinary scenario. An MSP receives an invoice from a CPO for €50,000, accompanied by a CSV containing 5,000 charging transactions. Finance checks the specification against the invoice, the totals match and everything appears to be correct.

But there are other questions that need answering. Did the MSP actually receive all 5,000 transactions operationally? Does the invoice and its specification reflect the tariffs that should have been applied? And have the MSP’s own tariff rules been applied correctly when billing its customers?

The number of missing or incorrect transactions may be less than 1%, but at scale, even a small percentage can represent serious money. Across hundreds of thousands or millions of charging sessions, relatively small discrepancies can quickly add up to meaningful lost revenue or unnecessary costs.

The challenge is therefore not simply making sure the totals on an invoice match. It is verifying that the transactions, tariffs and resulting charges are correct throughout the financial journey. An invoice can look perfectly correct from the finance department’s perspective while discrepancies still exist in the underlying operational data.

This is where manual processes start multiplying. Finance asks operations to verify an invoice. Operations exports information from another system. Transactions and tariffs are checked, files are compared, discrepancies are investigated and information travels backwards and forwards until the numbers can be explained. With a handful of transactions, that might be manageable.

Across thousands or millions of charging sessions and multiple roaming relationships, it becomes an expensive way to operate.

New business models are already emerging, including fixed monthly subscriptions where operators intelligently manage charging based on price, forecasts, and grid conditions.

Small discrepancies can mean serious money

Problems do not have to involve large numbers of transactions to have a meaningful financial impact. A CDR might be missing, a tariff may have been applied incorrectly or the information received by an MSP may not match what appears on the CPO’s invoice. Any of these discrepancies can affect what the MSP pays, what it charges its own customers and ultimately the revenue it retains.

The particularly difficult part is that these issues do not necessarily announce themselves. A missing CDR may mean a customer is never billed for a charging session, while an incorrect tariff or transaction value can pass through the process unnoticed if there is nothing automatically checking it against what was expected. At scale, even a relatively small percentage of discrepancies can add up to serious money.

These situations can also contribute to payment delays. A CPO understandably wants to be paid for electricity already supplied, while an MSP needs to verify that the transactions and tariffs it is being charged for are correct. When the information between them does not align, both sides can end up stuck. More manual checking might eventually resolve the disagreement, but identifying and preventing those discrepancies earlier is far more valuable.

Automation is not about generating a PDF faster

Automated invoicing is often presented as though the end goal is an invoice that magically creates itself. That is useful, but it misses most of the opportunity. If the information underneath an invoice is wrong, generating it automatically simply allows you to be wrong more efficiently.

The real value comes from connecting the financial process to what actually happened operationally. With TandemDrive, outgoing invoicing can follow the underlying charging information rather than depending on operations to create data dumps that are passed to finance and processed separately. When something changes operationally, such as a charging session requiring a correction or credit, that change can remain connected to the financial process.

Incoming invoices require their own checks and balances. An MSP needs to know whether the transactions a CPO is charging for correspond with the sessions it received and whether the expected tariffs were applied. Moving an invoice automatically into an accounting system does not answer those questions. Connecting it with the operational information behind the charging sessions does.

This is an important distinction. Digitising a manual process is not necessarily the same as improving it. Smarter automation should reduce work while increasing the business's ability to understand and verify what is happening.

People should investigate exceptions, not search for them

Manual checking is sometimes mistaken for control. In reality, asking skilled employees to inspect thousands of transactions just to find the small number that require attention is not a particularly effective use of either their time or expertise.

A smarter operational model turns that around. Transactions that match expectations should be able to move through the process automatically, while discrepancies are surfaced for investigation. People remain essential, but their time is concentrated on the exceptions where judgement is actually valuable rather than on repeatedly proving that normal transactions are normal.

The scalability benefit is significant. Manual processes can work surprisingly well at lower volumes, which can make them difficult to challenge. The spreadsheet works, somebody understands the process and problems can be fixed through a few emails. But a process that works for 10,000 transactions will not necessarily work for one million. If doubling transaction volume eventually requires doubling the number of people checking and reconciling transactions, the business is not really scaling. It is simply scaling its manual workload.

From efficiency to control

Reducing that workload has obvious value, but there is a bigger benefit: knowing what is actually happening to your money.

An MSP can see how much it paid CPO partners and how much it received from customers. What those totals alone cannot necessarily show is where money was made, where it was lost or whether transactions disappeared somewhere between the two.

TandemDrive connects incoming and outgoing information so the financial journey around charging transactions can be audited. That gives businesses the ability to understand what came in, what went out, what changed and where something does not match. Instead of assuming that the final numbers must be correct because they look plausible, companies gain the checks and balances needed to verify them.

That is what the tangible value of smarter EV charging operations looks like. It is less time spent moving files and manually checking transactions, greater financial accuracy, the ability to handle increasing volumes more efficiently and much clearer control over what is happening across the business.

The EV charging industry has spent years connecting chargers, networks and businesses. The next step is making sure the operations behind those connections can scale just as effectively. More charging transactions should mean more business, not more administration.