Point in time revenue recognition puts a whole show into one reporting period

A show director changes the dates. The venue offered a better week, the competing event moved, the hall was cheaper. The show goes from opening 28 June to opening 4 July, and the commercial logic is sound.

Six months later the group reports a first half with 7.6 million less revenue in it than the plan, and nobody outside the events team understands why. Point in time revenue recognition is the reason, and the change was decided by an operations conversation that never included finance.

What the standard requires

IFRS 15, issued by the IFRS Foundation in 2014, sets a two step test that decides this. Paragraph 32 requires an entity to determine at contract inception whether it satisfies the performance obligation over time, under paragraphs 35 to 37, or at a point in time, under paragraph 38. Paragraph 38 then states: "If a performance obligation is not satisfied over time in accordance with paragraphs 35 to 37, an entity satisfies the performance obligation at a point in time." It directs you from there to the control requirements in paragraphs 31 to 34.

The first of the over time criteria in paragraph 35 is the one that decides an exhibition, and it asks whether the customer simultaneously receives and consumes the benefits provided by the entity's performance as the entity performs. Hold that against a booth contract signed in October for a show in June. Through those eight months the organiser is selling other stands, running the marketing campaign and building the floor plan. The exhibitor consumes none of it. There is no partially delivered exhibition sitting in the customer's hands in February.

So the over time criteria fail, the performance obligation is satisfied at a point in time, and the point is when the show runs.

What a filed accounting policy looks like

The abstraction becomes concrete in a filing. Emerald Holding's Form 10-Q for the quarter ended 30 June 2025 states that customers generally receive the benefit of the company's services upon the staging of each trade show or conference event, and, a few lines later, that the company recognises revenue in the period the trade show occurs.

That second sentence is the whole policy in ten words. The same filing puts a scale on it: trade show and other events revenues represented approximately 90.4 per cent of total revenues for the three months ended 30 June 2025, and 92.3 per cent for the six months. When nine tenths of revenue lands on show dates, the event calendar is the revenue calendar.

Under United States generally accepted accounting principles the analysis runs through the same logic in different numbering. The FASB set the over time criteria in ASC 606-10-25-27 when it issued Accounting Standards Update 2014-09, and the criteria are the same three, so an organiser reporting under either framework reaches the same answer for a trade show.

Why does one date move an entire show's revenue?

Because the recognition event has no width. There is no mechanism in the standard for a show to be 40 per cent delivered on 30 June. The obligation is either satisfied or it is not, so the revenue is either in the period or it is not, and a date change of six days can move the whole balance.

This is unlike almost every other business model a group finance team deals with. A subscription that renews on 28 June recognises a few days of revenue in the first half. A construction contract measures progress. A trade show behaves like neither. It behaves like a delivery that happens on one morning, and the accounting follows.

The consequence is that the event calendar deserves the same status in the planning cycle as the budget. A date decision is a revenue phasing decision, and it should be signed off as one.

What it does to a half year

Take a portfolio reporting halves. Six shows, full year revenue of 41.8 million. Four shows fall in the first half, delivering 24.3 million of revenue and 12.1 million of contribution. Two fall in the second, delivering 17.5 million and 8.4 million.

Now move one show. The 7.6 million show that opened 28 June opens 4 July instead, carrying 4.9 million of contribution. First half revenue becomes 24.3 less 7.6, which is 16.7 million. First half contribution becomes 12.1 less 4.9, which is 7.2 million. Second half becomes 25.1 million and 13.3 million.

Full year revenue is 41.8 million either way and full year contribution is 20.5 million either way. Nothing about the business changed. But first half revenue fell 31.3 per cent and first half contribution fell 40.5 per cent, and the contribution fell harder because the show that moved was more profitable than the portfolio average, at 64.5 per cent contribution margin against 49.0 per cent overall.

Anyone reading that half year without the calendar in front of them concludes the business is in trouble. Anyone reading the second half concludes it is booming. Both readings are artefacts. Reporting around this is a presentation discipline of its own, and the fix starts with publishing the event calendar by half next to the results.

How should the internal reporting handle it?

Statutory accounts have to follow the standard. Internal management reporting does not, and the two most common responses to that freedom are both wrong.

The first is to mirror the statutory treatment exactly in the monthly pack. That gives a management report where a show contributing 4.9 million appears as a single spike in one month and eleven months of nothing, so every month before the show reports a loss and the month of the show reports an implausible profit. Management then stops reading the monthly pack, which is the actual cost.

The second is to smooth the revenue across the campaign on a straight line, which produces a comfortable monthly report that reconciles to nothing and quietly trains the team to expect revenue that has not been earned. When the show underdelivers, the smoothed months have to be unwound, and the unwind lands in the same period as the bad news.

What works is reporting the edition as the unit and the period as a roll up of editions. Each show gets a profit and loss for its own edition, opened when the first cost is committed and closed when the last invoice settles, which for a June show might run from the previous September to the following August. The monthly pack then reports two things: the editions that closed this month at their full result, and the forward position of every open edition measured as contracted revenue against target. Neither number pretends a show was 8 per cent delivered in February.

The reconciliation to statutory reporting stays clean because the edition result and the recognised revenue are the same figure, just filed under a different date. The one discipline this needs is that an edition keeps its identity when dates move. If the June show becomes a July show, the edition keeps its number and moves, and the comparative moves with it.

The parts of the show that do not follow the rule

Point in time recognition applies to the exhibition. A show is rarely only an exhibition, and the other revenue streams can behave differently.

Sponsorship of a year round content programme, where the sponsor's logo runs on a website and in newsletters for twelve months with a show week inside it, has a genuine over time component. Splitting that package between the period and the show week is a real allocation exercise. Digital advertising and publications follow their own issue dates. Emerald's filing treats content revenues separately for that reason, and notes that revenue on publications is generally recognised in the period in which the publications are issued.

Registration fees for a conference running inside the exhibition usually follow the show, since the delegate consumes the conference during the event. Where the fee includes twelve months of on demand access to recordings, part of it does not, and the allocation matters more than teams expect once the on demand element is priced.

The practical rule is to test each revenue stream against paragraph 35 separately and to document the answer once, so the split does not get re-argued every close.

Where this stops

Point in time recognition is clean when the show sits inside one period. It settles nothing about a show that straddles a period end, which is the harder case and the one auditors actually ask about. A three day show opening on the last day of a quarter forces a judgement about whether control transfers on day one, across the run, or on the final day, and that judgement is a separate question with its own tests.

The second limit is that the recognition rule tells you nothing about cash. Money for a June show has usually been collected by March, and it sits as a contract liability the whole time, which means an organiser can be flush with cash and showing no revenue at all. The balance sheet line that holds it is the one to watch if you want an early read on the year, because it moves months before the profit and loss does.

Take next year's event calendar and mark each show with the reporting period it falls in and the revenue you expect from it. Then flag any show opening within ten days of a period end, because those are the ones where an operational date change, a venue swap or a public holiday can move a whole show's revenue across the line. Circulate that list to whoever approves date changes, since it costs nothing and it is the single most useful piece of event finance housekeeping available before a planning cycle starts.