Delegate fee revenue recognition for a conference running alongside the exhibition

The conference sells out on 14 March. The finance business partner watches 903,000 land in the bank over the following six weeks and gets asked, twice, why the March management accounts do not show any of it.

Delegate fee revenue recognition is one of the few places in an event business where the accounting answer and the commercial instinct point in opposite directions, and the gap between them is about three months wide. The money is in the account. The revenue is not earned. Both of those are true at the same time and the balance sheet is where they are reconciled.

The money arrives in March and the conference runs in June

Take the paid conference running alongside the June exhibition. It sold 1,400 delegate places at 645 each, which is 903,000. Invoices went out through February and March, most of the cash was collected by the end of April, and the sessions run on 10, 11 and 12 June.

Emerald Holding's Form 10-Q for the quarter ended 30 June 2025, filed in August 2025, states the position for a listed organiser in a single sentence: "The Company recognizes revenue in the period the trade show occurs." The same filing notes that fees are typically invoiced and collected in full before the show, and identifies registration fees alongside booth space and sponsorship as the components of that revenue.

So the March position is a receivable on one side and a contract liability on the other, with nothing in the income statement.

Why is a delegate fee not revenue when it is invoiced?

Because invoicing is a billing event and revenue is a performance event, and IFRS 15 is explicit about which one drives the entry.

IFRS 15, issued by the IFRS Foundation in 2014, says at paragraph 106 that where a customer pays consideration, or the entity has an unconditional right to consideration, before the entity transfers a good or service, the entity presents the contract as a contract liability when the payment is made or due, whichever is earlier. It then defines a contract liability as an obligation to transfer goods or services to a customer for which the entity has received consideration.

That is a precise description of a delegate booking. The delegate has paid. The organiser owes them three days of sessions. Until those days happen, the organiser holds an obligation rather than a profit.

The scale of the resulting balance is not small at portfolio level. Emerald's Form 10-K for the year ended 31 December 2025 reports current deferred revenues of 219.2 million dollars against 463.4 million of revenue for the year, which is 47.3 per cent of a full year's revenue sitting on the balance sheet at a single date. How that line behaves across a whole portfolio, and what it does and does not tell you, is deferred revenue for trade shows.

Working the 903,000 through

The three-day conference runs entirely within June, so the release is clean.

Nothing in March, April or May. On 12 June the conference has been delivered and 903,000 moves from the contract liability to revenue. The June management accounts show 903,000 of delegate fee revenue, the conference direct costs of, say, 214,000 for the rooms, the speakers, the catering and the audio-visual, and a contribution of 689,000, which is 76.3 per cent of the fee line.

Two things follow from that shape and both catch people out. The first is that every monthly report before June shows a conference with costs and no revenue, because speaker fees, venue deposits and marketing are all being spent against a revenue line that will not appear for months. The second is that June looks extraordinary, which is a feature of the business rather than a fact about performance, and it is the general case set out in point in time revenue recognition.

What happens when the conference straddles a period end?

This is where the simple rule stops working, and it happens more often than the calendar suggests, because June and December are popular show months and popular year ends.

Take the same conference and move it to 29 June, 30 June and 1 July, against a 30 June financial year end. Delegate fees of 903,000 across three days is 301,000 a day. Two days fall in the old year and one falls in the new, so the year takes 602,000 and 301,000 stays as a contract liability into July.

The per-day split is the simplest defensible measure of progress, and it is the one to use unless the days genuinely differ. If day three is a half day with two sessions against eight sessions on each of the first two days, a session count is better: 18 sessions in total, 16 before the year end, so 802,667 in the old year and 100,333 in the new. Whichever measure you choose, choose it before you know which side of the line the money lands on, and write it into the policy.

Get this wrong in the other direction and the error is worse than an accounting adjustment. An organiser that recognises the full 903,000 at the start of a straddling conference has pulled a third of a conference into a period where it was not delivered, and the same treatment applied to an exhibition opening on the last day of a quarter moves an entire show.

No-shows, transfers and the refund window

Three practical cases, and only one of them changes the number.

A delegate who paid and did not attend has still been provided with what they bought. The organiser made the sessions available and the obligation was satisfied. Conference attendance rates matter enormously for the exhibitor value story and for the audience report, and they have no effect on delegate fee revenue. If 1,400 paid and 1,232 walked through the door, the revenue is still 903,000.

A name change is an administrative event. Same contract, same fee, same performance obligation, different person in the seat.

A refund is the case that does change the number, and it changes it before the show rather than after. If your terms give a full refund up to 30 days out and a 50 per cent refund up to 7 days out, then the amount you expect to be entitled to is less than the amount invoiced, and the estimate belongs in the liability rather than in a surprise credit note in June. On 1,400 bookings with a historic 4 per cent cancellation rate at full refund and 2 per cent at half, that is 56 places at 645 and 28 at 322.50, which is 36,120 plus 9,030, or 45,150 to hold back. The recognised figure becomes 857,850 rather than 903,000, a difference of exactly 5 per cent.

The on-demand library nobody accounted for

The version of this that is growing fastest is the recorded session archive, and it usually arrives in the delegate fee without anyone noticing.

If the delegate pass includes 90 days of access to session recordings after the conference, the contract has a second promise that is satisfied after show close. Where that access is sold separately, you have an observable standalone price and a genuine allocation to make. Suppose the in-person-only pass sells at 595 and the full pass at 645, so the archive carries an observable price of 50. The relative standalone selling prices are then 595 of 645, which is 92.2 per cent, and 50 of 645, which is 7.8 per cent. Applied to the 903,000, that is 833,000 recognised at show close and 70,000 spread across the 90 days that follow.

Whether that is worth doing depends on materiality and on whether the access is genuinely separable. A recording library nobody can buy without attending, available for two weeks, is a marketing feature of the conference. One sold at a published price to people who never came is a product, and it needs the same relative standalone selling price treatment as sponsorship revenue accounting.

Where this stops

The accounting is straightforward once the questions are asked. What it will not do is tell you anything about whether the conference was any good.

A delegate fee line of 903,000 released cleanly in June is compatible with a conference that 1,232 people loved and with one that 1,232 people sat through because their employer had already paid. Revenue recognition measures delivery against a contract. It cannot measure whether delivery was worth the money, and the organisers who confuse the two tend to discover the difference in next year's booking curve rather than in this year's accounts.

The second limit is the bundle. Where an exhibition pass, a conference place and a networking dinner are sold as one price to the same buyer, the neat single-obligation story above stops being available and you are back to allocating. That is manageable, and it needs the standalone prices to exist before the season starts rather than being reconstructed in July.

This week, take the delegate booking file for your next conference and add a column for the day the obligation is satisfied. If your conference crosses a month end, a quarter end or a year end, work out the per-day figure now and agree the measure with your auditor before the event, because the event finance conversation is much shorter in April than it is in the second week of July.