Replies
No one has replied to this post.
I find it unbelievable that the ULN issue isn't fixable any other way, I also find it shocking that it's not possible to undo a stopped record (though only the employer should be able to do that). It makes everything 100 times harder, and can even negatively impact on the apprentice if they have to have a new start date, and then potentially end date to meet minimum duration. What if the employer won't extend their contract? All because of an admin error. My team who approve the DAS records really carefully double check everything before they approve, as we've had things like this bite us before. It's such a high price for a simple mistake.
Hi Ruth
My sentiments exactly! I've replied to the helpdesk with a response that pretty much echoes everything you've said and I've asked for it to be escalated, though I'm not holding out much hope! There really has to be an easier way to mitigate for simple data-entry errors.....surely!
Helen Bryant
Incorrect ULN on DAS
Created
Hi
We have a DLOCK 02 error where the ULN on the DAS doesn't match the ULN in the ILR. The one in the ILR is correct so I've emailed the helpdesk asking how the ULN can be amended in the DAS. The response I've received is this:
'the employer must backdate the apprentice and nullify their record, then add the apprentice again with the correct information. Please note before you do this that non-levy employers are not able to add a start date for a month that has passed. This means that when the apprentices details are re-added the apprentice will have to be added as a March 2022 start and the ILR will need to be amended to match this.'
Has anyone else come across this issue and if so, did you resolve it in this way? It seems crazy to me that we would have to go through such an admin-heavy process just to correct a ULN number!
Many thanks
Helen