FRS 102 Has Changed Revenue Recognition, Here's What It Means for Your Xero Month-End
- Simon Hancott
- Jun 2
- 5 min read
From January 2026, the amended FRS 102 standard requires UK businesses to apply a new revenue recognition model based on the five-step framework originally introduced under IFRS 15. For businesses preparing statutory accounts under UK GAAP, this is the most significant change to how revenue is recognised in years.
For accounting practices and finance teams using Xero, the practical consequence is straightforward: more revenue timing adjustments, more documentation requirements, and more scrutiny from auditors on how you've determined when income was actually earned.
If your current process for managing deferred revenue involves a spreadsheet, a set of recurring journals, and a prayer that nothing's been missed, the new standard makes that approach harder to defend.
What Has Actually Changed
The FRS 102 amendments replace the previous revenue recognition guidance with a model built around five steps:
Identify the contract with the customer
Identify the performance obligations within that contract
Determine the transaction price
Allocate the transaction price to each performance obligation
Recognise revenue when each performance obligation is satisfied
For many businesses, step two and step five are where the complexity lies. A single invoice to a customer may contain multiple performance obligations, an implementation fee, a software licence, a subscription period, each of which should be recognised differently and at a different pace.
Under the previous model, many UK businesses were applying a broadly reasonable but loosely documented approach. Under the amended standard, you need to be able to demonstrate at audit how you've identified the performance obligations, how you've allocated the transaction price, and how you've determined when each obligation was satisfied.
That is a documentation problem as much as an accounting problem. And Xero, by itself, does not solve it.
Why Xero Creates a Timing Problem
Xero records revenue when an invoice is raised. If a customer pays £12,000 upfront for an annual subscription in January, Xero books the full £12,000 in January. Under FRS 102, only £1,000 belongs in January, the remaining £11,000 is deferred income sitting on the balance sheet until it is earned month by month.
This gap between when Xero records income and when it is actually earned is not a new problem. What is new is the level of scrutiny that auditors will now apply to how that gap is managed.
Finance teams who have been handling this with a spreadsheet, a schedule that tracks each contract, applies the recognition split manually, and feeds journals back into Xero at month-end, will find that auditors increasingly want to understand the process behind that spreadsheet.
How was the service period determined?
How were multi-element contracts allocated?
What happens when a contract is cancelled mid-term?
Is the balance sheet reconciliation tied back to individual invoices?
These are questions that a well-structured manual spreadsheet can answer. But in practice, most finance teams do not have the time at month-end to document the process thoroughly alongside doing the work itself.
The Specific Scenarios That Become More Complex
Annual and multi-year subscriptions
The simplest case, a customer pays upfront for twelve months of service. Under the new model, you need to demonstrate that the performance obligation is satisfied evenly over time and that your recognition schedule reflects that. If the service period is embedded in the invoice description or the contract attached in Xero, automation can do this reliably. If it is not, the process defaults to manual judgement at every month-end.
Multi-element contracts
A business selling a software licence with an implementation service bundled into one invoice now needs to consider whether these are separate performance obligations and whether the transaction price should be allocated between them. In practice, many businesses applying the simplified FRS 102 model will treat time-based recognition as sufficient for most elements, but auditors will want to see that the question was asked and answered.
One finance controller we spoke to recently described their existing revenue process: "We have it per customer, 50 different deferred revenue accounts, and each month based on our revenue recognition model we post the journals from that. It works, but we're looking for something where it's a click of a button rather than spreadsheet uploads and downloads." Under the new FRS 102 requirements, that process needs to be not just functional but auditable.
Mid-contract changes and cancellations
When a subscription is cancelled mid-term, the deferred revenue balance needs to unwind correctly. Revenue already recognised stays recognised. Future periods are reversed. The balance sheet clears. In theory this is straightforward. In practice, with a spreadsheet, it requires someone to remember to update the schedule, void the future entries, and verify that the resulting balance sheet position is correct. The audit trail for that process is often thin.
What Auditors Will Be Looking For
The ICAEW has highlighted that preparers and auditors should pay particular attention to how performance obligations are identified within customer contracts and how the recognition pattern is determined and documented.
In practical terms, this means auditors will increasingly expect to see:
A clear record of how the service period for each contract was determined
Evidence that the deferred revenue balance sheet account ties back to individual invoices and schedules
Documentation that shows what has been recognised in each period and what remains deferred
An auditable process that does not rely entirely on one person's working knowledge of a spreadsheet
This last point matters more than it is often given credit for. A process that works perfectly when one person manages it, but would fail if they were absent, is a control weakness. Under the new standard, that weakness is more exposed.
Where Spread Fits In
Spread connects directly to Xero and reads every sales invoice as it is posted, including line descriptions and attached contracts. Where the service period is present in the description or attachment, Spread detects it automatically, builds the recognition schedule, and posts the monthly journals directly to Xero.
The resulting audit trail is a balance sheet reconciliation export that shows every deferred revenue entry by invoice number, supplier, service period, opening balance, and closing balance, tied directly back to the source transaction in Xero. Every period's recognised revenue and every remaining deferred balance is visible in a single file.
This is not a replacement for accounting judgement on how to classify performance obligations or allocate transaction prices. That is a decision that needs to be made by the finance team or their accountants based on the specifics of each contract. What Spread handles is the execution; once the policy decision has been made, Spread applies it consistently, automatically, and with a complete audit record.
For businesses where deferred revenue recognition is primarily time-based, annual subscriptions, multi-year licences, membership income, service retainers, Spread handles the process end to end.
For businesses with more complex revenue arrangements, Spread handles the mechanical posting layer while the finance team retains control over the judgement calls.
A Practical Note on Implementation Timing
The FRS 102 amendments are effective for accounting periods commencing on or after 1 January 2026. For businesses with a December year-end, this means the amended standard applies to accounts being prepared right now.
For businesses that have not yet reviewed their revenue recognition process under the new model, the best time to address it is before the year-end close, not after.
Implementing Spread at the beginning of a new management period, rather than mid-period, creates the cleanest transition. Existing schedules maintained in spreadsheets can be imported into Xero as recurring journals with defined end dates, and Spread takes over for all new invoices from the implementation date forward. There is no need to unpick historical entries or recreate past periods.
There's a free trial, and it connects to Xero in under five minutes.
Further reading:
This post discusses the practical implications of FRS 102 amendments for businesses using Xero. It is not accounting or legal advice. The correct application of FRS 102 to your specific contracts and circumstances should be reviewed with a qualified accountant.
Comments