Revenue Recognition Across a Group: When Each Entity Plays by Different Rules

Every entity in your group recognises revenue. The question is whether they recognise it the same way. In a group assembled through acquisition or multi-model expansion, the answer is almost always no - and the consequences compound month after month in a consolidated P&L that overstates or understates revenue relative to economic reality by amounts that nobody in the group can quantify with confidence.

The compliance trap: why IFRS 15 adherence is not enough

IFRS 15 brought welcome rigour to revenue recognition at entity level. What it did not solve - and was not designed to solve - is the group-level consistency problem that emerges when entities operating under different business models are consolidated under the same P&L. Each entity may be fully IFRS 15 compliant. Together, they may be producing a group revenue figure that means nothing coherent.

The distinction matters because IFRS 15 provides a framework, not a prescribed outcome. Two entities applying the same standard to similar transactions can legitimately reach different conclusions about recognition timing, performance obligation completion, and variable consideration estimates. These differences are defensible individually. Aggregated without reconciliation, they produce a consolidated revenue line that reflects the sum of different interpretations rather than a consistent measure of economic activity.

PwC's 2023 survey of finance leaders in multi-entity European groups found that 67% of CFOs at companies with five or more entities reported that their consolidated revenue recognition policy differed in at least one material respect from the policy applied by an acquired entity. In 38% of cases, the CFO was not aware of the difference until it was identified during an audit or due diligence process.

Three manifestations of recognition inconsistency in group P&Ls

Intercompany revenue recognised at different points in time. When an entity charges a sibling entity for services - intragroup management services, shared platform fees, central function costs - both entities need to recognise these transactions consistently for the elimination to work cleanly. If the charging entity recognises revenue monthly and the receiving entity accrues the cost quarterly, the elimination produces timing mismatches that appear as unexplained variances in the consolidated view. These variances are not random. They recur every quarter at the same magnitude. Finance teams learn to expect them without understanding their source.

Subscription and project revenue in the same consolidated P&L. A group that contains a SaaS entity alongside a professional services entity has two fundamentally different recognition timelines in the same P&L. If the SaaS entity defers and amortises annual subscription revenue over 12 months while the services entity recognises project revenue on completion, the consolidated revenue line moves in ways that reflect portfolio timing and recognition methodology rather than underlying commercial momentum. A board receiving these numbers without clear disclosure of the recognition basis cannot distinguish a genuine revenue acceleration from a favourable timing effect.

Performance obligations defined differently across jurisdictions. In some markets, local commercial practice around what constitutes a completed performance obligation differs from the group's standard interpretation. Entities that operate primarily in local contexts may have developed recognition practices calibrated to local norms - and continued using them after acquisition because no group policy existed to supersede them. The result is a group where the same type of transaction is recognised at different points in the contract lifecycle in different markets, with no disclosure to the reader of the consolidated accounts.

Using IFRS 15 as a cross-entity consistency audit

The Group CFO who has confirmed that each entity is individually IFRS 15 compliant has confirmed that the standard is being followed. They have not confirmed that it is being followed consistently across the group. The five-step model is the diagnostic tool for the consistency question - but the question at each step changes from entity-level compliance to group-level consistency.

At Step 1: does every entity define what constitutes a contract using the same criteria, including for intragroup arrangements? At Step 2: for similar types of customer engagement across entities, does every entity identify the same performance obligations? At Step 4: when contracts bundle multiple obligations - software plus implementation plus support, for example - does every entity apply the same allocation methodology? At Step 5: for equivalent transactions across entities, does revenue recognition occur at the same point in the delivery cycle?

The output of this audit is a matrix of policy differences by step and by entity. Typically, two or three differences are immaterial. One or two are material enough to distort the consolidated P&L in ways that require harmonisation. The audit identifies which differences fall into which category - and produces the evidence base for the harmonisation decisions that follow.

What harmonisation actually involves: a post-M&A services group

A post-M&A professional services group, EUR 90M revenue, 5 entities across three countries, discovered during a pre-exit data room review that two acquired entities recognised revenue on project completion while the parent entity recognised on percentage of completion. Both treatments were defensible under IFRS 15 for the transaction types in question. Together, they made the group quarterly revenue fluctuate by EUR 4-6M depending on project completion timing - fluctuations that reflected accounting methodology rather than commercial performance.

The buyer's due diligence team identified the inconsistency and required harmonisation as a condition of the transaction. The harmonisation took 11 weeks. It involved agreeing a group-level revenue recognition policy, reconfiguring ERP revenue recognition rules in two entities, retraining the relevant finance teams, and restating two years of entity-level results on a consistent basis. The EUR 4-6M quarterly variance narrowed to EUR 0.8M on a restated basis. The seller's multiple was maintained. The cost of not having harmonised the policy before the process was estimated at EUR 1.2M in additional professional fees and delayed close.

The Group CFO's ownership responsibility

Revenue recognition policy is one of the most consequential accounting decisions a group makes. It determines how economic activity is reported, how periods compare, and how entities within the group appear relative to each other. It cannot be owned at entity level and assumed to be consistent at group level. The Group CFO must define the group policy, communicate it explicitly to entity finance teams, and verify that ERP configuration and month-end process reflects the policy that has been decided.

Policy harmonisation is not primarily an accounting project. It is a systems project. A revenue recognition policy that exists in a document but has not been implemented in ERP configuration is not an operating policy. It is an aspiration. The Group CFO's ownership of the group revenue recognition policy means owning the decision, the communication, the ERP implementation, and the verification that the policy is producing consistent results at month-end. Each of these steps requires different skills and different tools. Done correctly, the result is a consolidated revenue line that means the same thing across all entities and can be presented to a board or an acquirer without qualification.

If your consolidated revenue line requires a footnote explaining methodology differences across business units, or if your intercompany revenue eliminations produce timing variances that recur without explanation - talk to us about a group revenue recognition policy review before the next close or the next diligence process.