What is the most common ILR data error?

Date errors are the most frequent, particularly start and planned end dates that do not match the signed apprenticeship agreement or that imply an implausible duration for the standard. They are also among the easiest to prevent by cross-checking the ILR against your enrolment paperwork before submission.

Can I correct ILR errors after submitting the return?

Yes. The ILR is cumulative and submitted monthly, so most errors can be corrected in a later return by fixing the record in your MI system and re-exporting. The R14 return at the close of the funding year is the final opportunity to correct that year's data, so aim to resolve issues well before then.

Why do I have duplicate learner records in the ILR?

Duplicates usually arise when a learner is re-enrolled after a break in learning, when they are registered twice under slightly different details, or when two staff create records independently. Always search for an existing ULN before creating a new record, and supersede or remove the erroneous entry if a duplicate has already been submitted.

How do I check my ILR before submission?

Run your MI system's validation reports, use the ESFA Funding Information System (FIS) to model your funding, and reconcile expected payments against the monthly funding reports. A short pre-submission review involving MI, curriculum and quality staff helps catch anomalies that automated checks miss.

Do off-the-job training hours need to be in the ILR?

Yes. Planned off-the-job hours are a required part of apprenticeship records and are scrutinised in both funding audits and Ofsted inspections. Record planned hours accurately at enrolment and capture actual off-the-job activity as delivery progresses, keeping it consistent with the learner's contracted hours.

Common ILR Data Errors and How to Fix Them

Why ILR data quality matters so much

The Individualised Learner Record (ILR) is the mechanism through which the ESFA and DfE calculate your funding, and it forms a significant part of the evidence base Ofsted and auditors draw on when they assess your provision. Every learning aim, start date, planned end date and funding indicator you return feeds a payment or a compliance check somewhere down the line.

Because the ILR is submitted on a monthly cycle, errors compound quickly. A single mis-keyed field left unchecked can suppress a monthly payment, trigger a data-mismatch query, or leave you unable to reconcile your funding claim against your actual delivery. The good news is that the overwhelming majority of ILR errors fall into a handful of predictable categories, and most are entirely avoidable with disciplined checking.

The most common ILR data errors

Across the sector, the same issues recur month after month. Recognising the pattern is the first step to preventing them.

Incorrect or missing start dates that do not align with the apprenticeship agreement or the actual first day of learning.
Planned end dates that are inconsistent with the funding band, the standard's typical duration, or the learner's genuine timeline.
Duplicate learner records, often caused by a learner being enrolled twice or a re-registration under a slightly different Unique Learner Number (ULN).
Invalid or missing ULNs, which prevent the record from validating against the Learning Records Service.
Incorrect Standard Occupational Code, standard code or funding model, leading to the wrong funding rate being applied.
Missing or incorrect employer identifiers, including the wrong employer reference number or an apprenticeship service account mismatch.
Prior attainment and prior learning fields left blank or entered inaccurately, which can affect eligibility and funding.
Off-the-job training hours that are absent, implausible or inconsistent with the learner's planned hours.
Break-in-learning records that are not opened or closed correctly, distorting both funding and achievement data.
Withdrawals and completions returned in the wrong month, or with the wrong completion status, affecting achievement rates.

Start and end date errors

Date errors are the single most frequent source of funding disruption. A start date that predates the signed apprenticeship agreement, or that does not match the commitment statement, will attract audit attention. Similarly, if the planned end date implies a duration shorter than the minimum expected for the standard, the record may fail validation or generate a rule violation.

To fix these, cross-check the ILR start date against the signed training plan, the enrolment record and, where relevant, the apprenticeship service. If a genuine error has been keyed, correct it in your management information system and re-export the record for the next submission. If the learner genuinely started later, ensure the change is reflected consistently across your paperwork, not just in the ILR, so your evidence remains coherent for audit.

ULN and duplicate record errors

Every learner must have a valid ULN that resolves against the Learning Records Service. Invalid ULNs usually stem from transposed digits or a learner being enrolled before their ULN has been verified. Always verify the ULN at enrolment rather than relying on a self-declared number.

Duplicates typically occur when a learner is re-enrolled after a break, or when two staff members create records independently. Before creating any new record, search your MI system for an existing ULN. If a duplicate has already been submitted, you will normally need to delete or supersede the erroneous record and ensure only the correct learning aim continues into the next return.

Funding model, standard and off-the-job errors

Selecting the wrong standard code or funding model applies the wrong funding band and can silently under- or over-claim. Verify that the standard, its version and the associated funding band match the current published information for that apprenticeship before the first submission.

Off-the-job training is both a funding and a compliance requirement. Missing or implausible off-the-job hours are a common Ofsted and audit flag. Ensure planned hours are recorded, that they are consistent with the learner's contracted hours, and that actual off-the-job activity is logged as delivery progresses. Keeping this evidence current — rather than reconstructing it at audit — is far less painful, and a good apprenticeship management platform such as Journey can help by capturing off-the-job hours as they happen alongside the learner record.

A practical process for catching errors early

The most resilient providers treat data quality as a continuous discipline, not a monthly panic. Build checking into your routine rather than relying on the funding team to catch everything at deadline.

A workable monthly rhythm looks like this:

Run your MI system's validation and data-quality reports well before the submission window closes.
Use the ESFA's Funding Information System (FIS) and the monthly funding reports to reconcile expected against actual payments, investigating any variance.
Review the report of learners with no recorded activity, no off-the-job hours, or missing evidence.
Check that all starts, withdrawals, breaks in learning and completions from the period are reflected accurately.
Hold a short pre-submission review between MI, curriculum and quality staff so anomalies are queried by people who know the learners.
Keep an audit trail of corrections so you can explain any changes between returns.

Fixing errors after submission

Because the ILR is cumulative, most errors can be corrected in a subsequent return — the R14 close of the funding year is the final opportunity to lock down the year's data. Correct the underlying record in your MI system, re-export, and confirm the fix has flowed through in the next funding report.

Where an error has led to an overpayment, address it proactively rather than waiting for a clawback. Where it has suppressed a legitimate payment, the correction should release the funding once resubmitted. Throughout, keep your supporting evidence — agreements, training plans, off-the-job logs and eligibility documents — aligned with what the ILR states, because the record and the evidence are judged together.