What is life like with your car? Let us know and win £500 in John Lewis vouchers | No thanks
My insurer won't remove a no fault claim from their system - what can I do?
I had two misfuel incidents in 2015 and 2017. On the first I asked advice from L&V on the viability of making a claim. The response was: do not claim as the renewal premium will increase. I paid £200 each time to the RAC to solve the problem. L&V have entered on their records "no fault claims". Though this does not affect their quotations it certainly does for all other providers to the extent of almost doubling of the premium. Saga tell me that L&V can remove their entries but it may take a few weeks because other parties are involved. L&V are adamant that it cannot be removed. This leaves me tethered to L&V. Can you advise if this future recurring problem can be corrected?
Asked on 15 December 2017 by Vic Queen
Answered by
Honest John
Contact LV and raise a complaint. Unless you actually made a claim, they should remove it from their history. Tell them they need to remove it from MIAFTA. It is not an accident and there is no requirement to contact or update your insurer. Contact the financial ombudsman and raise a complaint with them as well.
We give you the low down on how to save on insurance, little-known tricks and tips, what insurance groups mean and how to use insurance aggregators to beat insurers.
Insurance group finder and how to save on insuranceSimilar questions
My partner hit a deer at one time, but there was minimal damage (a cracked bumper) and so didn't claim any costs on her insurance. She did however inform her insurance company and they have logged the...
Since my wife died, I am the sole driver on my insurance policy. I was thinking of getting a second car, but some insurance quotes say I can’t use my accident free record on a second car. I thought it...
I was reverse parking when a car came out of a side road and caused damage to my vehicle rear bumper. It has been registered as a no-fault accident, and while I have 9+ years protected NCD, I suspect that...
.jpg)
