I’ve checked 2 providers data now and they are both missing learners from the Apps Monthly Payment Report. most of the missing appear to be learners who would not generate any funding in the month, i.e leavers with an august 18 end date, breaks in learning or learners with a planned end date in August who are out of OPP’s.
Has anyone else spotted similar? i’ve logged calls with the service desk but nothing back yet.
The numbers missing are still in double figures for live and in-funding even if i try to tell myself that these reports now only show payable learners and there is not meant to be any visibility over all the learners that are submitted. I’ve only checked FM36 so far and i hope that the FM35 and trailblazer reports have been untouched.
p.s. completely clear rule violation and mismatch reports at the same time so they are not hiding in there.
Ben F.September 12, 2018 at 10:15 am #286439
yes I have also done the same as you and found that all apprentices that are not due any funding at all at period 1 are excluded from the monthly payments report. I am not sure yet in my own mind if that is helful or not.
I have however found an error which I have reported to the Service Desk. I have one apprentice who is actually a withdrawal however the actual end date is 31/08/2018. This record has also been excluded from the payments report which is inaccurate as the P1 OPP is due.
ChrisSeptember 12, 2018 at 10:20 am #286441
The guidance for this report states: If your ILR submission generates no payments for this report, this report will be blank.
I would assume where an individual learner does not generate any payments then they would also not be included.
HTHSeptember 12, 2018 at 10:29 am #286443
Hi Martin, that is correct. That is how the report looks
ChrisSeptember 12, 2018 at 10:32 am #286445
That has explained 80% of the missing learners for me and destroyed my processes for checking monthly activity against payments… looks like it’s back to the drawing board on that one.
If you have the specification for the apprenticeship mismatch report to hand, shouldn’t’ that highlight any discrepancy which would lead to non-payment of a live levy learner? If we assume the only reason a valid Levy learner record doesn’t get paid is if it doesn’t match on the apprenticeship service, and i have 10+ levy learners missing from the payments report, should they not appear on the mismatch report.
Ben F.September 12, 2018 at 10:37 am #286448
have you checked the apprenticeship service just in case an employer has stopped or paused an apprentice? These will not appear as a DAS to ILR mis-match. Just a thought.
ChrisSeptember 12, 2018 at 10:43 am #286454
doing that at the moment, but it feels insane compared to the relative simplicity of the FM35 reports that we have to go digging in every corner each month to pull together a view of what’s going on with payments. It would have been simpler to just go direct with all the employers and invoice them individually and track that way, at least there would be clarity over what has been earned and what has been received.September 12, 2018 at 10:48 am #286456
tell me about it. I have been banging my head with this stuff for 12 months!!! I seriously doubt that those behind the new methodology don’t even know what you mean by FM35!!!!! Talk about chucking the baby out.September 12, 2018 at 10:58 am #286462
Added for 2018/19
DLOCK_10, The employer has stopped payments for this apprentice
DLOCK_11, The employer is not currently a levy payer
DLOCK_12, The employer has paused payments for this apprenticeSeptember 12, 2018 at 12:08 pm #286490
Thanks for that Martin, very helpful.
ChrisSeptember 12, 2018 at 1:33 pm #286504
Is there a reason why planned end date, actual end date and completion status columns (to name a few) are missing from this months End Period reports?September 13, 2018 at 10:17 am #286670
i wish i knew, that was a delight i discovered mid way through trying to rationalize the data yesterday. It’s now impossible for me to do anything meaningful with the data without importing it in to a SQL database and joining in reference data from multiple sources including the raw ILR file that was submitted.September 13, 2018 at 10:22 am #286672
just following on from your helpful pointer about the new DAS mis-match reports, the learner I queried with the ESFA that had an actual end date at the point of withdrawal of 31/08/2018 and no OPP to be paid had been stopped by the employer dated 14/08/2018 hence the reason excluded from the payments report. There does however still appear to be a problem as the period end DAS to ILR match report had no mis-matches in it. It was blank.
ChrisSeptember 13, 2018 at 10:29 am #286676
It could be if the report has no mis-match data in it then the report is blank and would not include any DLOCK_10 to 12 data, I suspect an error with the reporting but who knows.
You do have to ask why the employer stopped at 14/08/2018.September 13, 2018 at 10:43 am #286680
I Know Martin. All fun and games! I was hoping last year’s learning curve on all sides would have sorted this year out but perhaps not?September 13, 2018 at 10:56 am #286684
Chris, that issue with the end dates in DAS cutting off payment prematurely looks to be on the Known issues list and is being worked on. let’s hope the example you logged allows them to test the fix actually works!September 13, 2018 at 11:39 am #286712
I am wondering if the employer stopped the apprentice dated 14th August but between 31st August and the 6th September submission deadlinei.e. back-dated? The problem was certtainly not seen in the DAS match report.
Something is not quite right somewhere.
ChrisSeptember 14, 2018 at 1:22 am #286903
I don’t think the DAS match reports are that sophisticated at the moment, maybe if you add in the agreement ID to the ILR (assuming you haven’t yet) then it will give you better error information?
One of the unintended issues with this whole system is that it seems the employers can fix the data from their end after our submission deadline and it still counts for the final reports. so we never truly know if the data we have submitted will stay matched until the final report comes out and providers are left in limbo over their month’s performance for days after the submission. I have seen staff get disciplinary type action against them because they haven’t hit their numbers in month and it being down to employer data not being in place.September 15, 2018 at 8:43 pm #287355
You must be logged in to reply to this topic.