20 July 2024

Haringey overdo it and then do the right thing.

 

Errors jump off the page at Mr Mustard. The addition error above was obvious and so was how the error had occurred. Mr Mustard decided to find out how many times this had happened so he asked questions of the council.

For all PCN Orders for Recovery issued by the council since 1 April 2023 please provide me with a spreadsheet which lists the values of any sum indicated as payable on the Order for recovery which was not £204 or £129 (the expected amounts based upon unpaid PCNs which were issued for the standard amounts of £80 and £130).

You will gather than what I am looking for is any case in the current council year where the amount demanded is unexpected/unusual/wrong as it was in a case I dealt with recently.

The reply was a complete one.

There was only one batch of PCNs affected by this incorrect value; the PCNs were registered at TEC with the correct amount; the batch became stuck halfway through the process and before we were successfully able to create the Notice of Debt Registration batch there were two more attempts to resolve the matter which led to the  adding up the 3 x £9.00 charge. Once this error was identified the PCNs were cancelled and any payments received were refunded accordingly.

Mr Mustard will reproduce below the spreadsheet he was sent. If your PCN is listed and you have not been repaid in full as per the council response, you need to contact the council for a refund.

512 PCNs at £204 (Mr Mustard presumes the council did not pay the fees to the Court three times) gives a maximum loss of £104,448 although the probable loss is likely to be lower, c £50,000 as lots of PCNs never get recovered.

Well done to Haringey Council for refunding in this situation. Mr Mustard doesn't know the trigger for that but doesn't need to be credited with being the driving force, even if he was.

The end.

 

No comments:

Post a Comment

I now moderate comments in the light of the Delfi case. Due to the current high incidence of spam I have had to turn word verification on.