We use cookies to collect
information about how you use ‘Get help with DfE services’. We use this information to make the
website work as well as possible and improve government services.
You will be able to post, reply and subscribe once DfE approves your account for this community.
Darren Vidler
Non-levy identification in funding reports
Edited
None
I know this has been raised previously but has anyone identified a foolproof way of identifying non-levy learners within the apps indicative report yet?
Trying to enhance my monthly forecasting by making allowances for the 5% co-investment from the employer within the indicative payment values but, without a clear way of identifying who is and isn't a levy payer, this is proving difficult.
Thoughts welcome, if someone has solved this issue then well done! In an ideal world what I'd love to see introduced is an FM36 summary generated for any uploaded file on the Submit Learner Data portal, that would solve the problem.
0
Replies
No one has replied to this post.
Steve Bowler
Hi,
Certainly not a 'foolproof' way but I tag all non-levy learners (and levy-transfer) on the ILR using one of the 'Provider specified delivery monitoring' fields so that we can monitor it for the purposes you mentioned along with other stats...
Thanks Steve, I've actually used those fields to identify subsets of learners previously so should have considered them as an option. Appreciate the response.
Darren Vidler
Non-levy identification in funding reports
Edited
I know this has been raised previously but has anyone identified a foolproof way of identifying non-levy learners within the apps indicative report yet?
Trying to enhance my monthly forecasting by making allowances for the 5% co-investment from the employer within the indicative payment values but, without a clear way of identifying who is and isn't a levy payer, this is proving difficult.
Thoughts welcome, if someone has solved this issue then well done! In an ideal world what I'd love to see introduced is an FM36 summary generated for any uploaded file on the Submit Learner Data portal, that would solve the problem.