Funding stream
Cross-cutting
Subjects that apply across every funding stream, including the ILR itself, returns, data quality, evidence, audit and performance measures.
Understand it
How further education funding actually works
Colleges are not paid a block grant for teaching. They are funded through several separate streams, each with its own rules, and each earned by recording delivery in the ILR.
Read itBuilding a funding map for your college
A funding map sets out every stream a college receives, how each is earned, when it reconciles and what data drives it. It is the fastest way for a finance or leadership newcomer to become useful.
Read itQuestions to ask MIS, and what a good answer looks like
A set of questions that a finance or senior leader can ask without being an ILR technician, each with the answer that should reassure you and the answer that should not.
Read itThe anatomy of the ILR
What is actually inside the Individualised Learner Record: the entities, how they nest, and which fields carry the funding.
Read itFrom a learner walking in to funding arriving
The full chain: a learner event, the operational action it triggers, the source data it creates, the ILR fields it populates, validation, funding, reports, evidence, performance and audit.
Read itWhat validation does, and what it does not do
Validation checks that the data is internally consistent and conforms to the specification. It does not check that the data is true, that the learner was eligible, or that the funding is correct.
Read itFIS and Submit Learner Data: the submission workflow
When to validate locally, when an actual submission is needed, what each report tells you, and how resubmission works within a collection window.
Read itThe collection year: what each return is for
Fourteen returns, each restating the whole year. Three of them matter more than the others, and knowing which is most of the job.
Read itWithdrawals, breaks and restarts
How leaving is recorded, why the date matters as much as the fact, and where the line falls between a break in learning and a withdrawal.
Read itThe data quality routine that prevents most problems
A small number of checks, run every month without exception, prevent the majority of funding, performance and audit problems in further education.
Read itWhat good evidence looks like
Evidence is not paperwork for its own sake. It is the demonstration that a funded activity genuinely happened as recorded, and it has three properties.
Read itBeing ready for a funding audit
What an audit tests, how sampling turns a few errors into a large adjustment, and the preparation that actually helps.
Read itWorking data quality and funding monitoring reports
Reports that flag records for investigation are the most useful assurance tool available, and the most commonly misread. A flag is a question, not a finding.
Read itQualification achievement rates: how your data becomes your results
Achievement rates are calculated from the ILR. Understanding the cohort is what turns an unexplained rate into an explainable one.
Read itClosing the funding year properly
At the final return the funding, the achievement rates and the audit population are all fixed at once. Everything that will be corrected has to be corrected before it.
Read itReconciling funding month by month
How to compare what the return earned against what you expected, explain the movement, and stop year-end surprises before they form.
Read itGetting it right at the front door
Most funding-critical data is captured at enrolment. Front-door quality is the cheapest data quality there is, and the only kind that scales.
Read itWhere Academy concepts appear in your MIS
How the concepts in this Academy map onto the student record systems colleges actually run, and why we do not publish unverified screen paths.
Read itThe rules in one place
Each statement is labelled so you can tell an official requirement from our explanation of one.
In further education, funding is not paid simply because a college says it taught someone. It is earned by recording what was delivered in the Individualised Learner Record, and that record is what the funding calculation, the performance measures and any audit all read from.
The Individualised Learner Record is the data return through which providers record the learners they enrol and the learning they deliver, and it is the basis on which funding is calculated and performance is measured.
Every provider is identified by a UK Provider Reference Number, and the UKPRN is what ties an ILR submission, an allocation and a funding report to a single organisation.
The further education funding year runs from 1 August to 31 July, and funding rules, rates and the ILR specification are set for that year.
A funding rule is only ever true for a stated funding year. Carrying an answer from one year into another, without checking, is one of the most common causes of an incorrect claim.
The ILR is structured hierarchically: a provider header, then one record per learner, and within each learner one record per learning delivery, with further entities for employment status, destination and outcome, learner funding and monitoring, and learning delivery funding and monitoring.
The Unique Learner Number identifies a learner across providers and across years, which is how prior attainment, prior learning and cross-provider activity can be recognised.
The funding model recorded against a learning delivery determines which funding rules, which calculation and which reports apply to it.
A learning delivery carries both a planned end date and, once the learner finishes or leaves, an actual end date. The planned date describes the intention at the start; the actual date records what happened.
Completion status records whether a learner is continuing, has completed, has withdrawn or has temporarily withdrawn. Outcome records what the learner achieved. They answer different questions and both are needed.
Funding and monitoring records, held at both learner and learning-delivery level, carry the eligibility, entitlement, support and monitoring information that the funding calculation and assurance reports depend on.
Each ILR return is a complete restatement of the funding year to date, not an increment. Every return replaces the last, which is why an error introduced late can change earnings already reported.
An ILR file is validated against the published validation rules for the funding year. Records that fail a validation rule are rejected or excluded from funding until the underlying data is corrected.
Passing validation means the data is internally consistent and structurally acceptable. It does not mean the data is true, that the learner is eligible, or that the funding claimed is correct.
Appearing on a data-quality or funding-monitoring report usually means a record has been flagged for investigation, not that it is confirmed wrong. Some flagged records are entirely correct and simply need evidence.
Corrections should be made in the source system that owns the data, then regenerated into the ILR. Editing an ILR file directly leaves the source system wrong and the error returns at the next generation.
The final return of the funding year is the last opportunity to amend that year's data. After it closes, the funding position, the performance measures and the audit population for the year are all fixed.
Qualification achievement rates are calculated from submitted ILR data. Data-quality problems in the return become published performance problems.
When a withdrawal is recorded changes both the funding earned and whether the aim counts in the achievement rate. Recording a withdrawal late is not a neutral administrative delay.
Evidence is strongest when it is created at the time of the event it describes and is retrievable without reconstruction. Evidence assembled after a query is asked is weaker and takes longer to produce.
When learner data is changed after it has been reported, the reason for the change and the authority for it should be recorded. An unexplained change between returns is a common audit query.
The ILR is generated from the student record system. It is an output of the college's own data, which is why almost every ILR problem is really a problem in enrolment, curriculum or registry data.
Screen paths and menu locations in a student record system differ by version and by local configuration. Steps should be confirmed against the supplier's documentation for the version in use before being followed as instructions.
When it goes wrong
A large number of validation errors appeared suddenly
Validation has produced a large number of failures that were not there before. A sudden change in volume almost always has one cause rather than many.
The achievement rate is lower than the college expected
The published or modelled achievement rate is lower than the college's own view of how well learners did. The difference is usually in the data rather than in the teaching.
The same learner appears twice
One person has been recorded twice, usually with two different learner reference numbers, and sometimes with two different ULNs. The system treats them as two people.
A learner is flagged on a data quality or funding monitoring report
A record meets the criteria of a report that identifies data worth checking. That is a request to investigate, not a statement that the record is wrong. Some flagged records are entirely correct and simply need their evidence to be locatable.
See it play out
Results arrive after the final return has closed
A batch of awarding organisation results for last year arrives in November, after the final return closed. What can be done?
A returning learner is enrolled as a new person
A learner returns after two years. The enrolment search does not find them, so a new record and a new ULN are created.
The first return of a new funding year fails badly
The first validation run of the new funding year produces hundreds of failures. What is the fastest route to a clean file?
An adult learner is recorded under the wrong funding model
An aim has been recorded under a funding model that does not match the provision. Everything downstream is assessed against the wrong rulebook.
A flagged record turns out to be entirely correct
A learner appears on a monitoring report every period. Each time, investigation shows the record is correct.
Earnings fall sharply after a bulk data update
A bulk update is applied to a cohort and the next funding report shows a material fall. Where do you look?
Evidence for subcontracted delivery cannot be produced
A subcontractor delivers provision the college claims for. When evidence is requested, the subcontractor is slow to provide it.
An achievement is recorded before the result is confirmed
A tutor is confident a learner has passed and asks for the achievement to be recorded before the awarding organisation confirms it.
Working in two funding years at the same time
It is September. The new year's first return is due and last year's final return has not closed. Two rulesets, two datasets, one team.
The same records appear on a report every single period
A monitoring report returns the same cluster of records month after month. Each time they are worked and each time they return.
A governor asks what the funding risk actually is
At a board meeting, a governor asks what would have to go wrong for the funding position to be materially misstated. What is a good answer?
A new finance director asks why income moved
A finance director new to further education sees earnings fall in a month where recruitment was strong. The explanation is in the mechanism.
The only person who knows where the evidence is has left
Eligibility evidence for a cohort was filed by a member of staff who has since left. Nobody can find it.
Check and evidence it
Monthly return readiness
The checks to run before every ordinary return. Short, repeatable, and the reason the consequential returns are manageable.
R14 final return readiness
Preparation for the final hard close, where the funding, the achievement rates and the audit population are all fixed at once.
Year-end close readiness
The wider close programme that runs from the spring, of which the final return is the last step.
Funding audit readiness
What to have in place before an audit, across every stream. Most of it is the routine you should be running anyway.
Enrolment quality review
A front-door review, which is where most funding-critical data is captured and where errors are cheapest to prevent.
Monthly data quality review
The standing data quality review, separate from the return checks, focused on trends rather than individual records.
New funding year setup
What to do before the first enrolments of a new funding year, rather than before the first return.
Governance assurance pack
What a governing body should see about funding, so assurance rests on measures rather than on reassurance.
New MIS starter induction
What a new member of an MIS team should be able to do, and by when. Not a funding control, but the thing that most often goes missing.
Terms you will meet
Official sources for this stream
These are the documents that govern this stream for the funding year. Rates, thresholds and exact conditions come from them, not from here.
Content reused from GOV.UK is Crown copyright, used under the Open Government Licence. FEFunding is not endorsed by the Department for Education.