A billing loophole in Johannesburg is a warning for every smart meter programme.

City Power halted its prepaid conversion rollout after discovering some customers were getting free power. The fault was not in the meters, but in the data behind them, and every utility racing to deploy AMI at scale should take note.

Johannesburg's City Power has stopped converting postpaid electricity meters to prepaid after discovering that a billing error was letting some customers draw power for free. The fix is not another firmware update or a smarter meter. It is an audit of the customer database that sits underneath the whole operation.

That distinction matters more than it sounds. A smart meter does exactly what its account record tells it to do. If the tariff mapping is wrong, if a meter number is linked to the wrong customer, or if a legacy postpaid account was never properly closed out, the meter will faithfully execute the mistake at scale and at speed.

The loophole was never the meter

City Power says it needs to strengthen controls and check its customer database before resuming conversions. That is the right call, and a more common one than utilities like to admit. Smart metering programmes are usually justified on loss reduction and billing accuracy, but they inherit whatever is already broken in the systems of record. A rollout that digitises a flawed database just digitises the flaw.

The same article notes that National Treasury is planning a nationwide smart meter rollout across South Africa, alongside Eskom's own target of reaching 6.2 million homes by March 2029. Programmes at that scale cannot afford to discover data problems meter by meter, after installation. They need to find them before the trucks roll.

Africa's rollout wave has no room for do-overs

City Power's pause lands in the middle of the continent's busiest metering season in years. Several national programmes are moving from pilot to volume deployment at once, each with its own financing, timeline and technology choices.

Nigeria's programme illustrates the stakes. An additional $308 million financing package is reportedly being prepared on top of the existing $500 million, and the timeline has already been extended to May 2028. Programmes of this size cannot easily pause for a database clean-up midway through, which is exactly why the clean-up has to happen before volume installation, not after.

Where errors get caught, or missed

Industry commentary on AMI 2.0 architecture points to where this discipline should live. The meter data management system is meant to validate readings before they reach billing and grid operations, and the head-end platform manages the communication sessions that carry that data back from the field. Universal, vendor-neutral head-ends are being promoted precisely because utilities are now running multi-technology meter fleets and cannot afford integration gaps between them.

Those validation layers are only as good as the account data they check against. A meter data management system can confirm that a reading is technically plausible without knowing that the tariff code behind it was retired two years ago. That gap is a process and governance issue as much as a technical one, and it is the gap City Power fell into.

None of this is glamorous, and none of it shows up in a rollout announcement. But at the volumes now underway across Nigeria, South Africa, Ethiopia, Tunisia and Cameroon, a database error that goes unnoticed in a pilot of a few hundred meters becomes a revenue and reputational problem at a few hundred thousand.