We’d like to remind Forumites to please avoid political debate on the Forum.
This is to keep it a safe and useful space for MoneySaving discussions. Threads that are – or become – political in nature may be removed in line with the Forum’s rules. Thank you for your understanding.
📨 Have you signed up to the Forum's new Email Digest yet? Get a selection of trending threads sent straight to your inbox daily, weekly or monthly!
Hargreaves Lansdown poor service
Comments
-
There is only one number in my post code area…..[Removed by Forum Team] was fine but , Upper [Removed by Forum Team] is what a computer check didn't like. Upper [Removed by Forum Team] is a historical reference differentiating from Lower [Removed by Forum Team] which is a mile away in a different postcode……. strange thing is, my wifes ISA account is still listed under the offending "[Removed by Forum Team]" address and they haven't even mentioned it. My adjusted address is now 1[Removed by Forum Team].
I don't have a problem with having to allign things so all addresses are exactly the same…..my concern was with the way it was done and the respect that I felt was lacking in my interaction.
0 -
If you call your property by a name not in the LLPG it is likely to be highlighted as anomalous and may trigger this type of problem. People often have their property incorrectly named as something flattering e.g. Garden Flat when the LLPG has it registered as Basement Flat, and this alone may trigger this sort of anally-retentive KYC exercise. Or you could have simply put in the wrong postcode on your original application, HL have subsequently used a new version of PAF, identified your data as anomalous and the kafka-machine taken over from there.
The "Upper H…." bit added to the OP's address is a historic name for the area, not a house name the OP has chosen.
The Royal Mail address checker confirms the address for the postcode is [house number] ["Upper H…."] [streetname] [placename] - and the neighbouring properties have the same address apart from the number.
OP, it looks like someone has mucked up your address in the official database. If the "Upper H…." bit is meant to be included then it should be [house number] [streetname] ["Upper H…."] [placename].
Street naming and numbering is a local authority (district council) function - you might want to check with them whether there has been a renaming request (you should have been consulted) or if something else has happened. You can explain to them the problems the mash-up is causing you.
Posting your address on the forum is also against the forum rules, so you should delete it from your post. I've avoided referencing your address in this reply, except for "Upper H…." - which on its own isn't sufficient to identify your address, so hopefully will be OK as the post won't make sense without it.
0 -
It's unusual to have a district name before a street name, but my experience is that there are examples to prove the rule in most towns.
That isn't quite the issue in the OP's case. They have a locale name inserted between the house number and the street name, and since the locale name could represent a street name (for example https://www.google.com/search?q=upper+ground ) it means HL's systems have probably gone into meltdown thinking the OP doesn't live at the address they said they lived at.
A broadly equivalent example would be if 188-196 Regent St., London W1B 5BT were modified to 188-196 Soho, Regent St., London W1B 5BT instead of 188-196 Regent St., Soho, London W1B 5BT.
"188-196 Soho" could be a valid property address somewhere, but you won't find it within the W1B 5BT postcode.
From what I can see I think the LLPG is wrong and the poster is correct. Hence them needing to speak to the local council to clarify.
I'm not sure about the link between the poll tax and NLPG/LLPG. The authority I was working for at the time (an early adopter) was doing work on LLPG because it was a fundamental requirement to implement GIS. Prior to that each department maintained its own card indexes or databases of addresses which were full of errors and were virtually impossible to cross-reference. Two of which were the Electoral Register and the list of chargeable properties for Domestic Rates. The key issue with poll tax wasn't identifing properties (domestic rates were being paid on them already), it was identifying who was living in each property. It was an example though of where different datasets recorded postal addresses differently, and how using UPRNs was the only way forward as more services went digital.
0 -
Royal Mail don't use LLPG in determining postal addresses. Postal addresses and postcodes long predate LLPG.
LLPG was introduced to standardise identification of land for the purpose of land registration and planing in 1999, and it obliged local authorities to keep a register that covered their area. It records the postal address that Royal Mail has created - it does not determine postal addresses.
Local authorities pick street names and allocate numbers to houses, but the rest of an address - such as locality and post town - is decided by Royal Mail. LLPG then simply records the address that Royal Mail has constructed.
Post towns can sometimes be completely different from the local authority in which a place is located, e.g.:
Addresses in Ringley, Stoneclough and Prestolee in postcode M26 have a locality and post town address of Radcliffe, Manchester, even though they are not in Radcliffe locality or in Manchester but in Kearsley, Bolton; and addresses with the address Radcliffe, Manchester that are actually in Radcliffe are all in Bury. And none of M26 is actually in Manchester, so the LLPGs for M26 are maintained by Bury Council and Bolton Council.
0
Confirm your email address to Create Threads and Reply
Categories
- All Categories
- 355.8K Banking & Borrowing
- 254.9K Reduce Debt & Boost Income
- 456.2K Spending & Discounts
- 248.3K Work, Benefits & Business
- 606K Mortgages, Homes & Bills
- 179K Life & Family
- 263.8K Travel & Transport
- 1.5M Hobbies & Leisure
- 16.2K Discuss & Feedback
- 37.7K Read-Only Boards