Why did E.On charge £1,393?
My mother was in her 90s and I looked after her financial affairs. She did not have a gas supply and her electricity was on a day/night rate system. Her heating was storage radiators so the bulk of the usage was at night.
I managed the account online and provided regular meter readings. There was a complication as the day reading meter became stuck, but this was not acted on by E.On. The meter was replaced six months before my mother died.
A fixed-rate contract with E.On ended and I moved my mother’s supply to Scottish Power, giving final meter readings. E.On subsequently sent a final electricity statement just before my mother died showing usage charges of £1,393. DAVID PIKE, E YORKS
Following this, Scottish Power also transposed the meter readings so it started charging the day usage at the night rate and the night usage at the day rate. You raised an official complaint with the two companies.
After your mother died the house was sold and the estate finalised, with the exception of this matter.
I spoke to Scottish Power and E.On. Scottish Power pointed out that the metering information behind the scenes had been incorrect. You had spent many hours on phone calls, sent emails and written letters to no avail. You also went to the energy ombudsman but were left disenchanted. This, of course, was all happening at a time of personal loss.
Nearly a year after all this started, an E.On spokesman said: “A fault on Mr Pike’s previous meter led to incorrect final readings. We have apologised for the error and rebilled the account, returning the credit balance to Mr Pike along with a goodwill payment by way of apology.”
Two cheques have been received by you. One was for £102, which was almost exactly what you had calculated was due to you. The second was for £250 for inconvenience, rather than the £50 the ombudsman suggested. You have donated the £250 to the hospice that looked after your mother in her last few days and had previously cared for your father many years ago.
You are relieved this is now resolved.