Changes to actual end date or planned end date after R14 of previous year
A funding monitoring report identifies records and patterns that DfE wants providers to investigate and be able to explain. Appearing on one does not by itself mean a record is wrong. Many flagged records are correct and simply need their evidence produced; others turn out to need a correction.
Where this comes from
Every word below is DfE’s own, read from the published guidance on 19 September 2026. Nothing in this section was written by FEFunding.
Summary
The learning planned end date must not change between funding years. You can only amend this date in the first ILR year to correct administrative errors. You must not change this date to reflect slow progress, illness or similar circumstances.
If a learning actual end date was recorded for a learning aim in the previous year’s R14 file and the aim continues to be returned in the current year, this date must not be changed.
For apprenticeship standards on a programme aim, the learning actual end date must not be changed once the end point assessment (EPA) period has been completed. You must record the date the EPA is completed in the achievement date field, regardless of the outcome.
Funding streams reviewed
- adult skills fund (formula-funded provision)
- apprenticeships (from 1 May 2017)
- advanced learner loans
What you need to do
You must reinstate the actual end date, planned end date, or both, as recorded in the previous year’s R14 return.
If you changed the learning actual end date between years:
- if the learner completed learning but failed the assessment, record a new learning aim for any new learning being delivered to achieve the qualification
- if the learner returned from a break in learning, record a new aim and record the restart indicator (Learning Delivery Funding and Monitoring Type = RES)
- if the end date was reported in error and the learner is continuing learning, change the Completion status to code 6, report a new instance of the aim and record the restart indicator
If you changed the planned end date between years, learning is continuing in the current funding year, and the planned end date has now been identified as significantly incorrect:
- change the Completion status to code 3 ‘withdrawn’
- complete the Withdrawal reason using code 40 ‘Learner has transferred to a new learning aim with the same provider’
- record a Learning actual end date of 1 August of the current year
- record a new learning aim with the same Learning aim reference and a Learning start date of 2 August of the current year
- on the new aim, record the correct planned end date and the restart indicator
- as applicable, complete the Funding adjustment for prior learning field
If you have reported a learning planned or actual end date in error, refer to the Provider Support Manual section Making changes and correcting errors for more details to record this correctly.
What we will do
We will recover any funding overclaim for errors that remain in your R14 data return.
Changes from previous funding year
None
What this means in practice
This section is FEFunding’s explanation, not DfE’s wording. It was drafted with AI assistance against the official guidance above. Its approval is pending confirmation, so it is not yet shown as reviewed by a person. Where it differs from the Department’s own words, the Department’s words are the authority.
In plain English
This report lists learning aims where an end date has changed since last year's final return. Once a funding year has closed, the dates in it are fixed. If something needs to change, DfE's answer is almost never to edit the old date. It is to put the old date back and record the new situation as new learning.
Based on FRM72 Summary; final-return-closes-the-year.
Working knowledge
Two dates are in scope. The learning planned end date must not change between funding years, and DfE says you can only amend it in the first ILR year, to correct an administrative error. It states directly that you must not change it to reflect slow progress, illness or similar circumstances. The learning actual end date is stricter still: if it was recorded in the previous year's R14 file and the aim continues to be returned this year, it must not be changed. For apprenticeship standards on a programme aim, the actual end date must not be changed once the end point assessment period is complete, and the date the assessment completed goes in the achievement date field whatever the outcome was.
Based on FRM72 Summary.
Technical detail
DfE's instruction begins by reinstating what R14 said: put back the actual end date, the planned end date, or both, as they were recorded in the previous year's R14 return. What happens next depends on which date moved and why. Where the actual end date was changed, there are three named routes: a learner who completed but failed the assessment gets a new learning aim for any new learning being delivered towards the qualification; a learner returning from a break in learning gets a new aim with the restart indicator recorded as a Learning Delivery Funding and Monitoring type of RES; and an end date reported in error for a learner who is still in learning is handled by changing the completion status to code 6, reporting a new instance of the aim and recording the restart indicator. Where the planned end date was changed, learning continues this year, and the planned end date is now identified as significantly incorrect, DfE sets out a six step pattern that closes the old aim and opens a new one on consecutive days.
Based on FRM72 What you need to do.
Why this report exists
A closed funding year is the basis on which funding was paid and reconciled. If dates inside it can move afterwards, the closed position stops being a position. This report is how DfE sees dates moving across the boundary.
Based on final-return-closes-the-year; FRM72 Summary.
What DfE is identifying
Learning aims whose actual end date, planned end date, or both, differ from what was recorded in the previous year's R14 return.
Based on FRM72 Summary.
Does appearing here mean something is wrong?
Usually yes, in the narrow sense that the date should not have moved. But the underlying situation is frequently legitimate: the learner really did come back, or really did fail an assessment and is doing more learning. What is wrong is the method, not the circumstance. The fix is to record the real situation the way DfE prescribes rather than to defend the changed date.
Based on FRM72 Summary; FRM72 What you need to do.
Legitimate reasons for appearing
- The learner genuinely returned from a break in learning, which DfE handles with a new aim and the restart indicator rather than by reopening the old one.
- The learner completed the learning but failed the assessment and is now doing further learning towards the qualification, which DfE handles as a new aim.
- An end date was reported in error last year for a learner who never actually stopped, which DfE handles through completion status code 6 and a new instance of the aim.
- The planned end date was genuinely and significantly wrong, which DfE handles through the transfer pattern rather than by amending the date.
Based on FRM72 What you need to do; break-in-learning-vs-withdrawal.
Data or process problems that can cause it
- A source system that lets a tutor or administrator edit a date on an existing record without any barrier at the year boundary.
- A learner returning after a break being reinstated on the original aim because that is the obvious thing to do in the system.
- A withdrawal entered last year that was wrong, corrected the natural way by removing the date rather than the prescribed way.
- A planned end date treated as a live estimate of when the learner will finish, rather than as a fixed record of what was planned.
Based on mis-generates-the-ilr; planned-vs-actual-end-date.
What to check first
- Compare the aim against the previous year's R14 return and identify exactly which date moved and to what.
- Establish which of DfE's four situations this is, because the correction is different in each and they are not interchangeable.
Based on FRM72 What you need to do.
Working through it
- Retrieve the previous year's R14 record for the aim and note the actual end date and the planned end date as they stood at hard close.
- Compare with what is being returned now, and identify precisely which of the two dates changed.
- Establish what actually happened to the learner, in the real world, independently of what the record says.
- Decide which of DfE's situations applies: completed but failed assessment, returned from a break in learning, an end date reported in error with learning continuing, or a planned end date now known to be significantly incorrect.
- For an apprenticeship standard, check whether the end point assessment period has completed, because after that the actual end date is fixed and the achievement date is where the assessment completion is recorded.
- Reinstate the date or dates as they were in the previous year's R14 return, which is DfE's first instruction and comes before anything else.
- Apply the correction route for the situation you identified, rather than the one that is easiest in the system.
- Establish how the change was made, because a system that permitted it once will permit it again.
Based on FRM72 What you need to do; FRM72 Summary; final-return-closes-the-year.
ILR fields involved
- LearningDelivery.LearnActEndDate
- LearningDelivery.LearnPlanEndDate
- LearningDelivery.CompStatus
- LearningDelivery.WithdrawReason
- LearningDelivery.AchDate
- LearningDelivery.LearnAimRef
- LearningDelivery.LearnStartDate
- LearningDeliveryFAM.LearnDelFAMType
Based on FRM72 What you need to do; WithdrawReason_04.
Related ILR validation rules
- CompStatus_06
- WithdrawReason_04
- AchDate_08
Based on CompStatus_06; WithdrawReason_04; AchDate_08.
Related PDSAT reports
- A-506
- A-504
- A-507
- A-509
Based on A-506; A-504; A-507; A-509.
Returns this relates to
- R14
Based on FRM72 What we will do.
Funding implications
DfE states that it will recover any funding overclaim for errors that remain in your R14 data return. That wording matters twice over: the exposure attaches to what is still wrong at R14, and R14 is also where the previous year's dates were fixed in the first place.
Based on FRM72 What we will do; final-return-closes-the-year.
Audit and assurance implications
This is a report about records changing after the year they belong to closed, which is the pattern an auditor looks for. For each aim you need to be able to say what the date was, what it is now, why it moved, who moved it and on what evidence. Where the change was legitimate, the evidence of the break, the assessment result or the error is what settles it.
Based on change-evidence-matters; evidence-must-be-contemporaneous.
Achievement rate implications
Completion and end dates are what achievement rates are built from, so moving them changes more than the funding. Where the correction opens a new aim rather than extending an old one, that is the treatment the measure is expecting.
Based on qar-is-built-from-the-ilr; completion-status-and-outcome.
Evidence to look for
- The previous year's R14 return, as the authoritative record of what the dates were.
- The evidence that the learner stopped, or did not stop, on the date originally recorded.
- For a break in learning, the record of the break being agreed and the learner returning.
- For a failed assessment, the assessment result and the plan for the further learning being delivered.
- The audit trail in the source system showing who changed the date and when.
Based on FRM72 What you need to do; change-evidence-matters.
If the data is wrong
- Reinstate the actual end date, the planned end date, or both, as recorded in the previous year's R14 return. DfE puts this first and the rest follows from it.
- Where the learner completed learning but failed the assessment, record a new learning aim for any new learning being delivered to achieve the qualification.
- Where the learner returned from a break in learning, record a new aim and record the restart indicator as a Learning Delivery Funding and Monitoring type of RES.
- Where the end date was reported in error and the learner is continuing, change the completion status to code 6, report a new instance of the aim and record the restart indicator.
- Where the planned end date was changed, learning continues this year and the planned end date is now significantly incorrect, follow DfE's pattern in full: completion status code 3 withdrawn, withdrawal reason code 40 for a transfer to a new learning aim with the same provider, a learning actual end date of 1 August of the current year, a new learning aim with the same learning aim reference and a learning start date of 2 August of the current year, the correct planned end date and restart indicator on the new aim, and the funding adjustment for prior learning field completed where it applies.
- For an apprenticeship standard where the end point assessment period has completed, leave the actual end date alone and record the date the assessment completed in the achievement date field, whatever the outcome.
- Where you have reported a planned or actual end date in error, DfE directs you to the Provider Support Manual section on making changes and correcting errors for how to record it.
- Make every one of these changes in the system that owns the data and regenerate the return, rather than editing the file.
Based on FRM72 What you need to do; FRM72 Summary; correct-the-source-not-the-return.
If the data is right
- If the dates genuinely match the previous year's R14 return, establish why the aim appeared, because that points at the comparison rather than the record.
- Keep the evidence for the situation that led to the new aim, whether that is a break in learning, a failed assessment or an error being corrected.
Based on change-evidence-matters.
Stopping it recurring
- Make dates in a closed year read only in the source system, so a correction has to be a deliberate act rather than an ordinary edit.
- Train the people who maintain learner records on the four situations DfE names, because the wrong route produces this report again next year.
- Check the aims that carry an end date in the previous R14 before the first return of the new year, rather than after.
Based on FRM72 Summary; mis-generates-the-ilr.
Questions an MIS manager should ask
- Which date changed on each of these aims, and who changed it?
- Can somebody edit a date belonging to a closed year in our system without anything stopping them?
- For each aim, which of DfE's four situations is it, and have we used that route rather than the convenient one?
- Are returning learners being put back on their original aim rather than given a new one with the restart indicator?
Based on FRM72 What you need to do; break-in-learning-vs-withdrawal.
Questions a finance director should ask
- What is the funding still attached to the aims that are wrong, given that recovery attaches to what remains wrong at R14?
- Is this a handful of records or a control weakness that will produce the same report every year?
Based on FRM72 What we will do.
What a good answer sounds like
- A good answer names the date that moved, the situation behind it, the DfE route used to correct it, and what has changed so it cannot happen the same way again.
- A weak answer is that the new date is the accurate one, which may be true and is not what DfE asked for.
Based on FRM72 What you need to do.
Related Academy learning
- withdrawals-and-breaks
- year-end-close
- ilr-lifecycle
Based on planned-vs-actual-end-date.
Funding streams this report reviews
DfE also names advanced learner loans. The Academy has no section for that stream yet, so it is listed here as published rather than mapped onto something only approximately similar.
FRM72 in other funding years
Working through it in your own system
- Read the official wording for this report and note exactly which records it identifies.
- Find those records in your own data using the fields the report names.
- For each one, decide whether the record is correct and simply needs its evidence produced, or genuinely wrong.
- Trace a wrong record back to the entry in your source system that produced it, rather than to the file it appeared in.
- Correct it at that entry, regenerate and resubmit.
- Keep the evidence and the reason for the change together, so the record is explainable at audit.
The Academy has no verified supplier guidance for this report yet. Menu locations differ between product versions and between colleges on the same version, so we do not publish navigation we have not confirmed. The steps above are what has to be true in the data, which is the same in every system.
If the record does turn out to be wrong. Correct the record in the system where the data is entered, then regenerate the ILR file and resubmit it. Editing the generated file directly removes the symptom and leaves the cause in place, so the same record returns at the next submission with nobody expecting it. Keep a note of what was changed and why: that note is what makes the correction explainable later.