Reservations of funds by non-levy - Summary of changes

Yes, I spotted this! I don't know why they are bothered about this, as no funding will be pulled down until there is a DAS record that matches. We are in the habit of just returning everything we enrol in the ILR, even if we're still just finalising the DAS bit. We know they cause DLOCKS, but we're not worried. Now, we're going to have to find some mechanism by which we can have the enrolment in our systems, but not include in the ILR return until the DAS record has been fully confirmed. Mildly annoying, but not a big issue, and I suspect lots of providers already do it that way. We definitely won't be waiting to do the data entry until the DAS record is done, as then we have no sight of them and can't chase them up as easily (I do know some providers won't even key them to internal systems until the DAS record is ready).

It won't be a validation error, as the validation rules don't look up Apprenticeship Service data. It'll just be a DLOCK as normal. I'm not sure they'll actually police this, but we'll attempt to follow this rule anyway.

It’s utter drivel. Employers ask us to do the work for them. Now we ask them to create a reservation first. More bureaucracy for the employer just to keep their ‘reservation’ part of the system. How is this even going to be enforceable and how much stress will be added to staff who accidentally submit and ILR and it’s not in the das first. No discussion about this in the technical user group either.

At times we have to chase employers to 'approve' in their DAS accounts which can run on for weeks. We have always managed the DLOCKS so why the need to change? 

We dont submit the learner in the ILR until DAS is approved, just to cut down on DLOCKs really, we use Aptem and can tick 'exclude from batch' until we know that DAS is approved we then approve the ILR and add to batch 

Thank you everyone for your feedback and thoughts!!!!