If you run finance for a multi-academy trust that is still taking on schools, you'll know there's a point where approvals stop keeping up. Every new school brings a head, an office manager and a site team who can sign things. According to the 2026 Kreston benchmark of almost 250 trusts, the average trust in its sample has 13.6 schools, up from 11.7 the year before.
In this article we'll cover what the handbook asks of your scheme of delegation, why the usual fixes don't keep pace with conversions, and how to build the scheme into the approval process itself.
When school nine joins
Say you're the CFO of a trust that has grown from five schools to eight, with a ninth converting in January. Within weeks, the new school's office forwards a £4,800 roofing quote to central finance asking who approves it now. Your scheme of delegation answers that, but the office manager has never seen it and the head is new to the trust too.
Many other approvals happen without anyone asking. A site manager's boiler repair signed off with a reply of "fine" on a forwarded email, or a photocopier lease signed locally by three schools with the same supplier. Each is spend the trust may struggle to show was approved under its scheme, coded to the right school, or bought as procurement rules expect.
The handbook asks for the scheme on paper and in practice
The Academy Trust Handbook 2026, effective from 1 October 2026, deals with the scheme of delegation in three places. Paragraph 2.4 requires the board to approve a written scheme of delegation of financial powers, reviewed every year and again at the next board meeting after a change in management or organisational structure that affects how the scheme works. Paragraph 2.7 then requires the control framework to ensure delegated financial authorities are complied with and to keep appropriate segregation of duties, and 2.25 requires the trust to make sure internal delegation levels are applied.
The first duty is a document the board signs. The other two are about what happens every day, and they get harder with each school you add. A conversion does three things:
- It is a change in structure that should bring the scheme back to the board if it affects how the scheme works.
- It brings in heads, business managers and site staff who were never part of the old email chains.
- It adds another school's spend that the trust has to account for separately.
The handbook also requires multi-academy trusts to publish on their website, by 31 January, a summary statement alongside the annual accounts showing how funds are distributed across their schools. Between that and the monthly management accounts for the chair, every pound of spend needs to reach the ledger already attached to the right school.
Why retraining and centralising don't fix it
There are three common responses. Recirculating the scheme and training new heads relies on people remembering a document while the people keep changing. Pulling every approval back to central finance builds a queue at one desk and undoes the delegation the board approved. An approvals spreadsheet records decisions after they're made, so it can't stop the wrong person signing and won't show you that three schools are buying the same thing.
Writing the scheme into the routing
The alternative is to make the scheme decide who approves, so nobody has to remember it. In practice that means:
- each school is a cost centre, and nothing goes for approval until spend is coded to one
- the approver is chosen by school and amount, with extra steps above the thresholds in your scheme
- nobody can approve their own spend
- staff who buy regularly hold their own cards, with limits set before they pay
The roofing quote then goes to the head of the school it's coded to, and on to you if it's above your scheme's threshold, without anyone forwarding it. When the next school converts, you add its cost centre and manager to rules that already exist and take the change to the board with the revised scheme, as paragraph 2.4 expects.
Coding at the point of spend also shows who is buying what. Under the Procurement Act 2023, purchases that could reasonably be supplied under a single contract must be valued together unless there's a good reason not to, and it is the trust, as the contracting authority, that has to do the valuing. Three photocopier leases with one supplier are far easier to spot when every invoice carries its school and supplier from the start.
Where Moss fits, and where it stops
Moss does this with approval rules and cards. Rules route invoices, card transactions, reimbursements and card requests by cost centre and amount, with the cost centre manager as approver and extra steps above set thresholds. Four-eyes settings stop anyone approving their own spend, the cost centre field can be made mandatory so nothing reaches approval uncoded, and rule changes can be drafted before they go live.
Budgets notify you when they're used up without blocking anything, and card transactions are approved after the money has been spent, so there is no per-school spending cap in Moss. The hard stop at the till is the limit on each card.
Moss enforces the scheme your board writes, while the scheme itself, procurement procedures, management accounts and the summary statement stay with you and your accounting system, which receives every item with its approval history.
What changes
With the scheme written into the routing, the roofing quote and the boiler repair reach the right head without anyone forwarding them, and in January the per-school figures for the summary statement are already in the ledger, coded when the money was spent. Find out more about Moss approval rules here.






