Written in September 2026. The FRS 102 point reflects the FRC's periodic review amendments to FRS 102, which apply to accounting periods beginning on or after 1 January 2026. Check the current standard before acting on it.
Every month, finance teams in professional services groups produce two sets of numbers that should tell the same story and rarely do. Utilisation and WIP come from the practice management or PSA system; revenue and margin come from the ledger. A spreadsheet sits in between, maintained by one person, understood by almost nobody, and queried by the board every single month. The fix is structural: agreed definitions, a single data flow, a shared hierarchy, and a pack that closes on the same calendar as the ledger.
The symptom: a board pack built from two irreconcilable sources
The pattern is familiar. The operations director presents utilisation from the PSA system. The financial controller presents margin from the ledger. Neither number is wrong, exactly, but they are built on different populations, different cut-offs, and different definitions of what counts as chargeable. By the time the meeting ends, the discussion has been about whose number is right rather than what the business should do. That is a structural problem, and it gets worse as the group adds entities, service lines, or geographies.
The root cause is that the join between the practice management system and the general ledger was never properly designed. Time, WIP, billing, utilisation, and realisation live in one system. Revenue recognition, accruals, and cost allocation live in another. The link between them - usually a spreadsheet export reworked at month-end - introduces timing differences, definition drift, and manual error. The board pack inherits all of those problems and presents them as a coherent picture.
A single KPI glossary agreed across every entity
Before any system or data flow conversation, the group needs one written definition of each core metric, the source system that owns it, and the person accountable for it. Without that document, every entity will apply its own interpretation and the consolidated pack will be arithmetically correct but conceptually incoherent.
The definitions that cause the most debate are usually the ones that seem obvious. Available hours is a good example: does it include bank holidays, paid leave, and non-billable training? The answer should be the same in every practice and every entity in the group. Chargeable hours should mean hours posted to a client engagement code, consistently, with no local judgement about whether a particular code qualifies. The glossary removes that discretion.
| Metric | Definition | Source system | Owner |
|---|---|---|---|
| Utilisation | Chargeable hours as a percentage of available hours, where available hours equals contracted hours less approved leave and public holidays | PSA / time recording | Practice operations |
| Realisation | Billed or revenue-recognised value of time as a percentage of the standard value at rack rate | PSA linked to billing | Finance |
| Recovery rate | Fees recognised in the period as a percentage of total cost of time incurred, including write-offs | Ledger and PSA combined | Finance |
| WIP days | Gross unbilled WIP at period end divided by average daily fee revenue, calculated on a rolling three-month basis | PSA and ledger | Finance |
| Lock-up | WIP days plus debtor days, measured at entity level and consolidated group level | PSA, ledger and AR system | Finance |
Each row in the glossary should name the system that is authoritative for the input data and the individual who owns the definition. When two entities report different utilisation figures for the same underlying population, the glossary is the referee.
Engagement profitability built from the same time data that drives revenue
Engagement-level margin is only credible if cost and revenue flow from the same source. The time entry that a consultant posts on a Thursday afternoon should, through a single feed, update both the engagement P&L and the general ledger. If finance re-keys, allocates, or adjusts that data before posting it to the ledger, engagement margin and ledger margin will diverge, and they will diverge differently each month depending on what adjustments were made.
Cost rates - the internal rate at which each grade of staff is charged to an engagement - should be held centrally and applied automatically. Maintaining separate cost rate tables in the PSA system and in the ledger is one of the most common sources of unexplained variance. A single central table, updated at the start of each financial year and for any structural change, applied consistently across all entities, eliminates that variance at source.
Write-offs and write-downs deserve particular attention. In many groups these are processed as a month-end top-side in the ledger, with no connection to the engagement from which the write-off arose. The result is that engagement P&Ls show full recovery while the ledger shows a write-off sitting in a suspense line. Write-offs should be recorded against the engagement at the point the decision is made - partner signs off the write-down, it posts against the engagement and flows to the ledger in the same journal.
One entity and practice hierarchy shared by management and statutory reporting
Multi-entity professional services groups routinely maintain two hierarchies: one for management reporting by practice or service line, and a separate legal entity tree for the statutory consolidation. When those two hierarchies are different - even slightly different - intercompany eliminations become a manual reconciliation exercise every month.
The most common problem is secondments and cross-charged staff. A consultant employed by entity A works on a client engagement billed by entity B. That gives rise to an intercompany recharge. If the management hierarchy and the statutory hierarchy slice the group differently, the recharge may eliminate in the statutory consolidation but appear as a cost in one management reporting unit and income in another, with no offsetting entry visible in the pack. The board sees a distorted picture of practice margin.
The solution is to design one hierarchy that serves both purposes, and to hold it in a single place - whether that is the consolidation platform, the chart of accounts, or a master data layer that both systems consume. Any change to the hierarchy - a new entity, a restructured practice, a rebranding - is made once and flows consistently to both the pack and the statutory consolidation.
A monthly pack that closes on the ledger calendar
WIP valuation is often the last input into the management pack and the one with the most manual intervention. If the PSA system cuts off on a different day from the ledger, or if WIP is valued using a different rate or a different population of open engagements, the pack's revenue figure and the ledger's revenue figure will not agree, and a reconciling item will accumulate over the year.
The discipline is straightforward: agree one cut-off date for the period, apply it simultaneously in the PSA system and the ledger, and include a standing reconciliation page in the pack that bridges from PSA gross WIP to recognised revenue in the ledger. That reconciliation should show write-offs, adjustments for stage of completion, and any advance billing netting. When the reconciliation is a standing page rather than an ad hoc check, it becomes self-policing - anomalies are visible to the board and to auditors without anyone having to ask for them.
The revised FRS 102 Section 23 point for UK GAAP groups
This point was written in September 2026 against the FRC's amendments to FRS 102. UK GAAP groups applying the revised standard - which applies to accounting periods beginning on or after 1 January 2026 - are now presenting unbilled work as contract assets on the balance sheet and advance billings as contract liabilities, in line with the five-step revenue model introduced by those amendments. Groups that had previously shown WIP as a current asset under an older presentation should check that the management pack's WIP definition and the pack's revenue line are consistent with how the ledger is now treating those items. A pack that still shows gross WIP against a revenue line built on billing milestones will not reconcile to a ledger that recognises revenue as each performance obligation is satisfied under the revised model. The glossary and the standing reconciliation page are the right places to make that alignment explicit.
A short checklist for group finance teams
- Produce a written KPI glossary covering at minimum utilisation, realisation, recovery rate, WIP days, and lock-up - with the source system and owner named for each metric - and distribute it to every entity finance lead.
- Confirm that cost rates used in the PSA system and those posted to the ledger are drawn from the same central table and updated on the same schedule.
- Map where write-offs and write-downs are currently recorded: if they are processed as ledger top-sides rather than against the originating engagement, redesign that flow.
- Compare the management reporting hierarchy and the statutory consolidation hierarchy entity by entity - document any difference and decide which is authoritative.
- Agree a single period cut-off date that applies to both the PSA system and the general ledger, and hold to it each month.
- Add a standing reconciliation page to the pack that bridges PSA gross WIP to ledger recognised revenue, showing write-offs, stage-of-completion adjustments, and advance billing offsets as named lines.
- For groups applying revised FRS 102, confirm that the pack's WIP and revenue definitions reflect the contract asset and contract liability treatment now in the ledger.