Please can we have the ability for the ERN to be optional and accept older format ERNs
CompletedThe complusory nature of the ERN is causing us no end of problems. 90% of the time a broker does not know the ERN when submitting a quote but is unable to get a quote unless entering an invalid number.
This is probably more dangerous than adding no number at all.
Of the brokers we have had go live and/or in the process of testing they have ALL had an issue with the ERN.
PLEASE can you make this field optional. The layout and validation is great, but only if you have the ERN at the time of the quote. This is our biggest headache to date.
-
Hi Natalie,
I'm sorry this is causing you problems, we'll investigate possible solutions and keep you updated on future releases.
We are aware that the mandatory and non-mandatory nature of questions created in the Questions Editor is an area that many users would like us to review.
Best wishes,
Adam
-
We have now been gathering ERN's for some time and it has become apparent that there is no real "rule" to follow when checking their validity. There seems to always be a number to start followed by a slash but after that it seems that anything goes. I think the ERN validation needs some looking at before this vield type is viable for use.
-
This is really urgent now, we need to give to be able to ask for the ERN when the broker/client clicks On Cover. We also need to ask if they are a Parent or Child company.
We keep getting people going on cover without putting the ERN in the system which means we have to chase. It breaks the conditions of one of our binders as we have to get the information before the inception of the policy.
-
Adam,
I have been speaking to insurers on this and most agree on the ERN format being as follows:
- All have 3 numbers in the first part
- All have a / after the 3 numbers
- They must contain at least 6 characters including the /
If the ERN formatting is not changed we will not be able to use this field.
Cheers.
Mark
Please sign in to leave a comment.
Comments
9 comments