@
Jasmin2000
Having had a good think about all this mess, here’s my take on it…
1. You pay £80 a month fixed DD and then make manual payments if necessary to make up any shortfall when you receive a bill.
2. That should mean that your account should not build up much, if any, credit or debit balance.
3. You recently received (probably due to a mistake, glitch or a computing error) some duplicate bills covering April to September 23 inclusive. Presumably you had already paid these bills, perhaps apart from the most recent for September. You also received reversed charges covering the period January to September 23 inclusive.
4. This meant that you had charges for the duplicate bills rightly refunded. It also meant you had the charges for your January to March bills refunded even though you had not been billed twice for that period.
5. That over-payment of reverse charges (Jan - March) left you with an unexpected credit balance which you requested be refunded to you. This was agreed.
6. You were then billed again for Jan - Mar to make up for the reverse charge for that period that seemed unwarranted. This would have wiped out your unexpected credit balance. Now your refund request has been stopped as your account is back in debit.
7. Had the Jan - Mar duplicate bill come with the other duplicate bills and reverse charges then the overall effect of that statement would have been zero. It would have been a case of being billed for several months that you had already paid for and then being refunded it all back on the same statement.
8. The dates of the bill charges and the dates of the refunds may not exactly match so you currently have some debit balance that may be more than the original £4.35. You may perhaps have some balance to pay for recent usage.
9. My overall hunch is that you were mistakenly billed twice for most of this year’s consumption (perhaps apart from most recent consumption) but had all duplicate charges credited back to your account before any payments were made either way.
10. I think your account is probably currently back where it should be. I may be wrong of course. What do you think @
LeeDQ_EONNext