FousSubmit learner data
Get your ILR reports from Submit learner data by API
Read the validation results, the Apprenticeship Data Match Report and the Funding Summary Report for your latest ILR file with one API call each. A workflow can read the Data Match Report each weekday at 8:00 and email you the DLOCK rows that are new.
Works with your own Submit learner data account. Fous is an independent product.
What you can build on Submit learner data
Get the Apprenticeship Data Match Report
Build thisDownloads the Apprenticeship Data Match Report for a collection period and reads each mismatch between your ILR and the apprenticeship service.
- Takes
- Collection year, return (such as R04)
- Returns
- Learner reference number, rule name, description, ILR value, apprenticeship service value
Check the latest ILR file's validation results
Build thisReads the validation reports for the most recent ILR file submitted in a return: what was accepted, what was rejected and why.
- Takes
- Collection year, return
- Returns
- File name, learners accepted, learners rejected, each error or warning with rule name, learner reference number and message
Get the Funding Summary Report
Build thisDownloads the Funding Summary Report (Excel) for a return, or the version produced at period end, and reads its funding lines.
- Takes
- Collection year, return, period-end version (yes or no)
- Returns
- Funding line, amounts by period, totals
Upload an ILR file
Build thisUploads an ILR XML file, or a .zip holding one XML file of the same name, for the open return and reads the result once it has processed.
- Takes
- Collection year, ILR file (.xml or .zip)
- Returns
- File name, uploaded at, learners accepted, learners rejected, errors, warnings
Automate Submit learner data with a workflow
A workflow runs your methods as one process, with nobody at the screen. A schedule or a call from your own system starts it, the steps run in order, and the result arrives in your inbox or in the systems you already use.
New DLOCK mismatches each weekday morning
Build this- Starts
- Every weekday at 8:00 Europe/London
- Step 1
- Get the Apprenticeship Data Match Report for the open return.
- Step 2
- Keep the mismatches that were not there on the last run.
- Step 3
- Email you the list grouped by learner reference number, with each ILR value and apprenticeship service value.
Validation errors sent to your MIS team after each ILR upload
Build this- Starts
- When your system calls the workflow's webhook with the collection year and return
- Step 1
- Check the validation results of the latest ILR file for that return.
- Step 2
- Keep the errors, and stop when there are none.
- Step 3
- Post each error with its rule name, learner reference number and message to your MIS team's webhook.
Funding Summary Report handed to finance when it changes
Build this- Starts
- Every weekday at 9:00 Europe/London
- Step 1
- Get the Funding Summary Report produced at period end for the latest closed return.
- Step 2
- Keep the funding lines that changed since the last run, and stop when none did.
- Step 3
- Post the funding lines, with their amounts and totals, to your finance system's webhook.
You can run a workflow by hand on every plan, Free included. Schedules and webhook triggers come with the paid plans, from $29 a month.
Once built, one call from your code
Once you have built a method, it is one POST to /v1/runs from your backend, or a tool an AI agent calls over MCP. This is what “Get the Apprenticeship Data Match Report” would look like.
curl https://api.fous.com/v1/runs \
-H "Authorization: Bearer $FOUS_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"method": "submit-learner-data.service.gov.uk/get_apprenticeship_data_match_report",
"input": {
"collection_year": "2026 to 2027",
"return": "R03"
}
}'
{
"status": "completed",
"data": {
"collection_year": "2026 to 2027",
"return": "R03",
"mismatches": [
{
"learner_reference_number": "ACME000412",
"rule_name": "DLOCK_07",
"description": "No matching negotiated cost of training and assessment found",
"ilr_value": "9000",
"apprenticeship_service_value": "8500"
}
],
"count": 1
}
}
An example with invented data, not a ready-made endpoint. The method exists in your organization once you build it, and its name, inputs and fields follow your request.
Submit learner data’s own options
The Department for Education's guidance describes no API for Submit learner data. You create the ILR as an XML file in your MI system and upload it to the service, which validates it and makes reports available to download after each submission. The department also offers desktop tools: FileMerge to combine ILR files and the Funding Information Service to produce indicative funding reports.
| Option | What it covers | What it takes |
|---|---|---|
| Funding Information Service (FIS) | A desktop tool that produces funding reports from an ILR file before you submit. Its funding figures are indicative only. | A download from Submit learner data. |
| ILR FileMerge tool | Combines separate ILR files into one, since each upload overwrites all your earlier records. | A download from Submit learner data. |
| Learner Entry Tool and Enter Learning Data | Create an ILR file without an MI system that can export XML: manage your courses and learners, then export the ILR file. | The Enter Learning Data role in DfE Sign-in, for Enter Learning Data. |
| Submit learner data by hand | Upload the ILR XML file each return, check the validation reports and download the funding and apprenticeship reports. | A DfE Sign-in account with the Standard Submissions role. |
Read on November 12, 2026: How do I send data? (ILR provider support manual), DfE Sign-in roles for Submit learner data, 2026 to 2027 ILR funding reports.
Signing in to Submit learner data
Submit learner data signs you in with a DfE Sign-in account, which starts with your email address, and what you can do depends on your roles: Standard Submissions to submit data and view reports, Enter Learning Data to build an ILR in the service. With Fous you sign in once through DfE Sign-in with your own account, and the login is sealed with AES-256.
Worth knowing
- Every upload replaces the last one
- Each ILR file must hold all learners and learning deliveries for the year to date, across all funding models, because each upload overwrites all your earlier records. A submitted file cannot be deleted, only replaced by a newer one.
- Returns close at 18:00
- Each return closes at 6pm on its close date, for example R04 on 4 December 2026 and R05 on 7 January 2027. The last file submitted before the close is the one loaded nationally.
- Some reports come only after the close
- Reports are ready to download after each submission has processed. The Apps Monthly Payment Report comes only after the window closes, and the Data Match Report is produced again just after the collection period ends.
- Rejections happen at three levels
- A schema stage 1 failure rejects the whole file, a schema stage 2 failure rejects that learner's records, and a failed validation rule rejects the learner and all their learning deliveries, which then earn no funding.
More in Education, research and nonprofit
- Slate
- Naviance
- Common App for Recommenders
- National Student Clearinghouse secure site
- AQA Centre Services
- Edexcel Online
- FSA Partner Connect
- VA Enrollment Manager
- Sponsorship Management System
- Infinite Campus
- PowerSchool SIS
- EDOF
- Arbor MIS
- SLC HEP Services
- Parchment
- UCAS adviser portal
- Benevity Causes Portal
Other industries: PG&E online account, DoorDash Merchant Portal, BB Digital PJ, Elavon Payments Insider, 自然人电子税务局(扣缴端), Income Tax e-Filing Portal.
Frequently asked questions
Not one that the Department for Education documents. You upload the ILR as an XML file and download the validation and funding reports from the service. The department offers desktop tools around it: FileMerge to combine ILR files and the Funding Information Service for indicative funding reports before you submit.
The Standard Submissions role in DfE Sign-in. It lets you submit data and view reports for ILR, EAS and Funding Claims and open the Understand Your Funding dashboards. Building an ILR inside the service needs the Enter Learning Data role instead.
Not if the only correction is on the apprenticeship service side. The department refreshes apprenticeship service data hourly while the ILR window is open and produces the Data Match Report again after the period ends, though it still recommends resubmitting.
No. A submitted file cannot be deleted. Correct the data and submit another file, which overwrites it. The last file submitted before the return closes at 6pm is the one loaded nationally.
No. Fous is an independent product. You use it with your own DfE Sign-in account, and a method reads and does only what that account can in Submit learner data.
Put Submit learner data behind an API call
Describe one job in Studio and see the method it builds, with 100 credits a month and no credit card, or book a demo and bring the sites your team signs in to.

Read nextVA Enrollment ManagerSponsorship Management SystemInfinite CampusPG&E online accountHow methods workHow workflows run
Fous is an independent product: it is not affiliated with, endorsed by or sponsored by the operator of Submit learner data (Department for Education). The name is used only to say which system this page is about. Something here wrong or out of date? Write to legal@fous.com.