Funded Hours Tracking and Invoicing for UK Nurseries: What Software Gets Right and Wrong
Funded hours are the single most complained-about area of nursery administration. The system is genuinely complicated: four different entitlement types, 152 local authorities with different hourly rates, deprivation supplements that vary by postcode, EYPP on top of everything else, and a reconciliation process that requires matching what you claimed against what you delivered against what the council actually paid. This article breaks down how the funding system works, what your software needs to handle, where the main platforms fall short, and when a bespoke approach makes more sense.
Speak to us about nursery software · +44 7494 618 651 · Mon to Fri, 9am to 6pm
4
Different funded entitlement types to track per child
152
Local authorities in England, each with different hourly rates
Sept 2025
30-hour entitlement expanded to working parents from 9 months
How the funding system actually works
There are four main funded entitlement types in England. Every nursery manager knows this, but the detail matters because each type has different eligibility rules, different start dates, and different rates.
Universal 15 hours: Available to all 3 and 4 year olds from the term after their third birthday. No eligibility check. 570 hours per year, typically taken as 15 hours per week over 38 weeks.
Extended 30 hours (working parents): Available to children of working parents (both parents earning at least the equivalent of 16 hours per week at minimum wage, and neither earning over £100,000). From September 2025, this extends to children from 9 months. 1,140 hours per year. Parents must reconfirm eligibility every three months via the Childcare Choices portal.
2-year-old disadvantaged funding: Available to 2 year olds from families on qualifying benefits (Universal Credit with income under £15,400, income-based JSA, ESA, etc.). 570 hours per year.
Early Years Pupil Premium (EYPP): An additional supplement for 3 and 4 year olds from disadvantaged backgrounds. Worth approximately £388 per year per eligible child (2025-26 rate). Claimed on top of the base funding.
On top of these, local authorities apply their own rates. The base rate per hour varies significantly. A nursery in one borough might receive £5.50 per hour for 3-4 year olds while a nursery ten miles away in a different authority area receives £6.20. Deprivation supplements add further variation, with rates dependent on the postcode of the child's home address, not the nursery's location.
What your software needs to do with funded hours
At minimum, nursery software that handles funded hours properly needs to do five things.
Track entitlement per child. Each child has a specific entitlement based on their age, eligibility, and start date. The system needs to know which children are on universal 15 hours, which are on extended 30 hours, which are on 2-year-old funding, and which are eligible for EYPP. Entitlements change as children age (a 2-year-old moves to universal 15 hours at 3, then potentially to extended 30 hours).
Split invoices correctly. A child attending 40 hours per week with 30 funded hours should be invoiced for 10 private hours plus any consumable charges. The funded hours should be deducted at the correct local authority rate, not at the nursery's private rate. This sounds simple. In practice, with different session structures, term-time vs all-year attendance, and stretched vs standard funding models, it is anything but.
Generate headcount data for claims. Local authorities require headcount data each term (and sometimes each month) to calculate funding payments. The software needs to produce this data in the format the authority requires, with accurate counts of funded children, hours claimed per child, and eligibility codes.
Reconcile claims against payments. After submitting a claim, the nursery receives a payment from the local authority. The amount may differ from what was claimed (children who left, eligibility changes, rate adjustments). The software needs to reconcile the payment against the claim and flag discrepancies.
Handle stretched funding. Some parents choose to "stretch" their funded hours over more weeks (typically 51 weeks instead of 38). This reduces the hours per week but spreads them over the year. The software needs to calculate the correct weekly hours for stretched funding and adjust invoices accordingly.
The September 2025 expansion changed the scale of this problem. Before September 2025, funded hours primarily affected 3 and 4 year olds (and some disadvantaged 2 year olds). The extension to working parents of children from 9 months means nurseries now track funded hours for children across almost every age group. The administrative volume has roughly doubled for many settings.
Where the main platforms handle this well
Nursery in a Box is the specialist here. The platform was built around invoicing and funding management. It automatically splits funded and private hours on invoices, tracks multiple funding streams per child, and handles bulk allocation of funded hours to eligible children. If funded hours reconciliation is your primary pain point, this is the most focused tool.
eymanage (eyworks) takes a finance-specialist approach. It supports bulk allocation of funded hours with LA-specific rates, including deprivation weighting and EYPP supplements. The occupancy and financial forecasting tools are designed around funded hours capacity planning.
Famly handles funded hours as part of its broader platform. Invoicing with in-app payments includes funded hour deductions. The depth is not as specialist as Nursery in a Box, but for settings that want one platform covering everything, it is adequate for most cases.
Connect Childcare has years of funded hours management built up. The functionality is established and covers the core requirements. However, the interface quality issues reported across the platform apply here too.
Where things go wrong
The common errors in funded hours tracking are not usually software bugs. They are configuration problems, process gaps, and edge cases that the software does not handle cleanly.
Children coded to the wrong funding stream. A child eligible for extended 30 hours is set up as universal 15 hours. The nursery invoices the parent for 15 hours that should be funded. The error is not caught until the parent queries the invoice or the local authority reconciliation flags a mismatch.
Eligibility lapses not caught in time. Parents must reconfirm their 30-hour eligibility every three months. If a parent's code lapses, the child reverts to universal 15 hours. The nursery may not discover this until the end-of-term claim is rejected for the additional hours. A system that checks eligibility codes proactively (and alerts the nursery before the grace period expires) prevents this.
LA rate changes not updated. Local authorities set new rates each April. If the software is not updated with the new rates, every invoice from April onwards is calculated incorrectly. This sounds obvious, but in practice it requires manual configuration in most platforms.
Deprivation supplement miscalculation. Deprivation rates are based on the child's home postcode, not the nursery's postcode. A nursery in an affluent area may still have children from postcodes that qualify for deprivation supplements. If the software does not check individual child postcodes against the deprivation index, the nursery underclaims.
Stretched funding calculated incorrectly. A parent stretching 570 hours over 51 weeks receives approximately 11.2 hours per week instead of 15 hours over 38 weeks. The invoice split needs to reflect the stretched weekly amount, not the standard amount. Some platforms do not handle this automatically.
The cost of getting it wrong goes both ways. Underclaiming from the local authority means the nursery absorbs costs it should not. Overclaiming means the nursery must repay the difference, sometimes months later when cash flow is least flexible. Neither is acceptable, and both happen regularly across the sector.
Specialist funded hours tools
Funding Loop is a dedicated funded hours platform that sits alongside your nursery management software. It calculates hours based on the child's attendance schedule with built-in knowledge of term times, supports most council systems for automated claim processing, and handles parental agreement forms online. If your current nursery software does everything else well but struggles with funded hours specifically, Funding Loop fills that gap without replacing your whole system.
The downside of a specialist tool is that you are running two systems. Attendance data in one, funding calculations in another. Any change to a child's sessions needs to be reflected in both. This is the fundamental trade-off between best-of-breed tools and integrated platforms.
When bespoke makes sense for funded hours
For a single-site nursery with straightforward session structures and one local authority, any of the established platforms handles funded hours well enough. The configuration takes time, but once set up, the core calculation works.
The case for bespoke emerges in three situations.
Multi-site chains across multiple local authorities. A nursery group with five settings across three different local authorities has three different rate structures, three different claim submission formats, and three different payment schedules. Off-the-shelf platforms treat each setting independently. A bespoke system consolidates funding management across sites, produces claims in the format each authority requires, and reconciles all payments from a single dashboard.
Non-standard session structures. Forest schools with flexible attendance. Settings that offer 6am-8pm care with funded hours embedded in the middle. Nurseries that allow parents to split funded hours across two providers. These edge cases break the assumptions that off-the-shelf platforms make about how sessions and funded hours align.
Direct integration with local authority systems. Some local authorities are moving toward automated data exchange for headcounts and claims. A bespoke system can integrate directly with the authority's portal or data format, eliminating the manual export-and-upload step that every off-the-shelf platform requires.