The DfE chart of accounts is the Department for Education's standard for recording and reporting financial data in academy trusts. It maps directly to the academies accounts return and the budget forecast return, which is the whole point of it. And it is not mandatory — DfE encourages adoption rather than requiring it.
What it is
It is a standard set of nominal codes, running in ranges from 10000 to 99999, that underpins the academies accounts return and the budget forecast return. Because the codes map directly to those returns, a trust using the chart can feed financial data into them directly rather than remapping its own ledger each time.
The current version is the 2026 to 2027 chart of accounts, last updated 20 August 2026. The 2025 to 2026 version remains available on the same page, which matters for a trust mid-transition.
It is encouraged, not required
This is the point to be precise about, because getting it wrong is a compliance-advice error rather than a presentational one.
DfE's own language is that it will "continue to encourage trusts to adopt the standard chart of accounts, to improve the efficiency of completing financial returns and data quality". The Academies Accounts Direction is framed the same way: trusts that have adopted, or are considering adopting, the chart "may find the structure and mappings worksheet helpful".
Contrast that with the Direction itself and the Coketown model accounts, both of which carry contractual status through the funding agreement. Nothing in the chart of accounts material, or in the Direction, makes adoption a requirement of the funding agreement. A trust that maintains its own coding structure and maps to the returns manually is fully compliant.
No date has been announced on which DfE intends to make it mandatory.
What it covers, and what it deliberately does not
The chart lays out a structure for nominal codes only — the "what": what the trust received income for and spent money on. It does not dictate the "where". Cost centre headings are each trust's own choice, so a trust can keep its existing departmental, phase or site analysis and still adopt the standard nominals.
There is also room built in for local variation. DfE has left the last digit free under each ledger code, which gives up to nine local codes beneath each standard one. That is the release valve for a trust with genuinely unusual income streams — it can analyse them locally without breaking the mapping.
The benefits DfE claims
- Efficiency in completing the financial returns, since the codes map directly and data can be input without a translation step;
- Data quality, for the same reason — fewer manual mappings means fewer mapping errors;
- Comparability. DfE's stated position is that the chart "reduces subjectivity across the academies sector and so develops the reliability of benchmarking data comparisons";
- Automation. The Direction notes that using the chart enables trusts to use automation technology for the accounts return and the draft financial statements.
That last point is the one with the clearest payback. A trust whose ledger already speaks the return's language can generate a substantial part of both the return and the draft accounts mechanically, which removes the annual reconciliation exercise that most finance teams treat as unavoidable.
The trap in the accounts return
One thing to understand before assuming the chart solves everything. The accounts return uses a different accounting framework from the financial statements, so figures can legitimately differ between the two. That is not an error to be reconciled away.
The Direction's advice is practical: trusts should check their accounts against the accounts return guidance and validation rules before the annual accounts are finalised, to minimise validation errors. Doing it in that order is the difference between a clean submission and a round of corrections after the accounts have been signed.
Whether to adopt it
For a trust reviewing its finance systems anyway — a new finance package, a merger, a growing MAT standardising across schools — adopting the chart is close to a free decision, because the structure has to be chosen and this one comes with the mapping already built.
For a trust with a working chart, a stable system and a finance team that knows it, the case is weaker. The benefit is real but incremental, and a mid-year migration of nominal codes is disruptive out of proportion to it. The sensible middle path is to adopt at a natural break — a year end, or a system change — rather than as a project in its own right.
What is worth doing either way is checking the mappings worksheet. Even a trust that keeps its own codes benefits from mapping them to the standard once, properly, and reusing that mapping each year instead of rebuilding it.
Our guides to the Academies Accounts Direction and the Academy Trust Handbook cover the reporting requirements the chart feeds into.
Acumon works with academy trusts on financial reporting, the accounts return and the systems behind them through education audit, school and academy accounting and cloud accounting setup. If you are changing finance system this year, that is the moment to decide on the chart of accounts rather than after.