ILR Compliance Report

Introduction 

The ILR Compliance Report is part of our Enterprise offering, for more detail, please contact your customer success manager.

This report helps MIS Managers and ILR Controllers identify potential ILR data issues before submission to the DfE.
It highlights validation and audit risks early, allowing you to review, correct, and confirm data directly in Bud rather than discovering issues after submission.

By surfacing common data errors and compliance checks in advance, this report supports a more proactive approach to ILR preparation, reducing last-minute fixes, rework, and delays during month-end submission.

 

User Role 

  • All users with a reporter - ILR Compliance Report turned on

 

How to use the ILR Compliance Report

The ILR Compliance report is split into two sections, each focusing on a different type of compliance check used in the ILR submission process. Each section is detailed below.

 

ILR Validation Rules

This section surfaces data that may fail ILR validation rules if submitted in its current state. These rules are defined and maintained by the DfE and are applied during ILR submission and validation.

The ILR Compliance report currently covers a subset of ILR validation rules, with additional rules planned to be introduced over time. As a result, this report should be used as an early indicator of potential issues, rather than a complete replacement for DfE validation tools.

Use this section to:

  • Review learners and records that may trigger validation errors

  • Investigate and correct data issues before generating your ILR file

  • Reduce reliance on post-submission validation tools

For full details of validation rules and comprehensive validation outcomes, refer to the guidance and tools provided by the DfE.

The report page includes key slicers to help you manage your ILR Validation Rules, along with a top-level visualisation showing the number of errors associated with each rule. This makes it easy to spot common issues at a glance.

The detailed data below shows all individual errors that have been identified. Alongside basic learner details, each record includes the rule name and description, as well as aim details to pinpoint exactly where the error occurred. An Error value is also displayed, which changes depending on the error triggered and can help you identify the cause. For example, an error on the achievement date will display the specific achievement date in question.

 

 

Whilst we continually implement more rules, detail on the rules we are running can be found here, whereas detail on all the validation rules the DfE currently monitor can be found in their guidance pages here.

 

FRM Reports

This section highlights data relevant to Funding Rules Monitoring (FRM) reports. FRM reports are used by the DfE to identify potential funding and compliance risks and may be reviewed as part of audit activity.

The report highlights learners who have been identified as queries against the DfE published FRMs for the current academic year. The rules are run within your tenancy's ILR data and will only show issues identified against your data. This may be a subset of the issues shown in the DfE reports, where they have full visibility across all Training Providers.

Use this section to:

  • Identify records that may require further review or supporting evidence

  • Understand potential funding risks earlier in the process

  • Support audit readiness by addressing issues proactively

Further information on FRM reports and how they are used can be found in DfE guidance.

The report page includes key slicers to help you manage FRMs identified within your data, along with a top-level table showing the count of issues for each FRM. This allows you to quickly spot common issues and monitor changes across each area over time.

The detailed table below shows individual learner records associated with FRM issues. For each record, you’ll see key learner information and the specific FRM that has been triggered, along with an Error value. This value varies depending on the error and helps you identify its cause. For example, an error on FRM37 related to Off-The-Job Training (OTJT) hours will display the Planned or Actual Hours field from the ILR.

Use this data to investigate specific issues, understand potential funding risks early, and support proactive audit readiness.