Event revenue recognition answers a question your registration platform cannot: what the event
earned in this period under your accounting policy. The platform reports what had been sold on
the day someone ran the report, so the two figures almost never agree, and the gap is a set of
known adjustments: refunds, comps, offline payments, currency, and deferral. Agree on the
definitions before registration opens, then reconcile with a bridge that names every difference
on its own line.

Suppose your registration platform says the event sold $1.4M and your general ledger recognizes
something else. Both can be right. The reconciliation is short work when the definitions exist
and a long argument when they do not. The recognition policy itself belongs to your controller
and auditor, and this page covers the reconciliation only.

## Why don't the registration report and the general ledger ever match?

Because they answer different questions. The registration report answers "what has been sold",
at the moment you ran it. The ledger answers "what has been earned in this period, under our
accounting policy". Those differ even when every transaction is recorded correctly in both
systems.

Four structural differences drive most of the gap:

- **Timing.** A report is a snapshot and the ledger is a period.
- **Basis.** The platform tends to think in bookings and cash, the ledger in recognition.
- **Scope.** The platform holds only what passed through it, which excludes checks, wire
  transfers, and invoiced corporate registrations. See
  [event data silos](https://eventiq.io/md/blog/event-data-silos) for the wider problem.
- **Presentation.** Platforms often show what was deposited, net of fees, while the ledger
  shows revenue gross with fees as an expense.

The arithmetic is the small cost of leaving this unmanaged. The larger one is that the result
becomes contestable, and the board discussion turns to which number is right.

## What are the seven differences you should expect to find?

All seven are normal. What matters is knowing which reduce revenue, which move it between
periods, and which are not revenue items at all.

**1. Refunds and cancellations after the snapshot.** A revenue reduction, in the period the
refund occurs under your policy. The trap is a report run before the refund window closes and
then quoted for months.

**2. Comped and zero-value registrations.** No revenue. A comp is a headcount, and the platform
may display it at list price in some views. Count comps separately and keep them visible
outside every revenue line.

**3. Partial payments, deposits, and installment plans.** A timing difference. A registration
with a deposit taken and a balance due is one booking, part cash and part receivable, and
possibly split across periods. Decide whether you recognize at the event or as installments are
earned.

**4. Payment processor fees.** An expense, which leaves revenue unchanged. Netting fees against
revenue understates both revenue and cost, so they belong in the cash tie-out and stay out of
the revenue bridge.

**5. Offline and invoiced payments.** These increase recognized revenue above the platform
figure, because the platform never saw them: checks, wires, purchase orders, and corporate
group invoices.

**6. Currency translation.** A revenue adjustment, small until it is not. International
registrations recognized at a different rate than they were booked create a real difference, so
state the rule: booking-date rate, receipt-date rate, or a period average.

**7. Revenue deferred across fiscal periods.** A period difference, and often the largest
single item. Registrations sold in one fiscal year for an event held in the next are a
liability until the event happens.

## Which definitions must be agreed in writing before the event?

These eight. Each takes a line to write now and far longer to argue about after the event.
| # | Definition | What you write down |
| --- | --- | --- |
| 1 | Recognition point | Event date, service delivery, or installment as earned |
| 2 | Gross or net | Revenue gross of processor fees, with fees as an expense (recommended) |
| 3 | Refund treatment | Period of the refund, and the reserve method for the open refund window |
| 4 | Comp treatment | Zero revenue, counted and reported as a separate headcount line |
| 5 | Discount treatment | Revenue at the amount charged, with discount value reported as a memo figure |
| 6 | Currency rule | The rate used and its source |
| 7 | Deferral rule | Which fiscal period an event's revenue belongs to, and the treatment of multi-year passes |
| 8 | Cut-off date | The date the revenue report is run and frozen for the close |
Two of these decide most arguments. Gross versus net, because it changes both the revenue line
and the cost line, and therefore every ratio built on them, [event ROI](https://eventiq.io/md/event-roi) included.
And the cut-off date, because without one there is no such thing as "the" registration number.

## What does a reconciliation that finance will accept look like?

A bridge: one starting figure, one ending figure, and every difference named on its own line
with a source.

**Recognized registration revenue = Gross bookings per registration platform, at the cut-off date**

**− Refunds and cancellations processed to cut-off**

**− Revenue deferred to the next fiscal period**

**− Discounts shown at list price on the summary view**

**− Reversed, failed, and duplicate transactions**

**+ Offline payments not recorded in the platform**

**± Currency translation adjustment**

The cash tie-out is a separate statement, outside the bridge.

**Cash deposited per bank statement = Recognized registration revenue**

**+ Deferred revenue collected in cash**

**− Amounts invoiced and unpaid at close (receivables)**

**− Payment processor fees (expense line)**

Two rules keep a bridge usable. Every line names the system it came from, so a reviewer can
check one line without re-running the whole exercise. And a line that cannot be explained is
shown as "unexplained difference" with a value, never absorbed into the nearest plausible line.
An unexplained $3,000 that is disclosed is a minor item. The same $3,000 hidden inside a refund
line is a credibility problem when someone finds it.

## Who owns each step?

One named person per line, with the evidence they are signing against.
| Step | Owner | Evidence |
| --- | --- | --- |
| Freeze the registration report at cut-off | Registration manager | Timestamped export |
| Confirm the refund list to cut-off | Controller | Processor log |
| Identify comps by category | Event director | Comp register |
| Confirm discounts and memo value | Registration manager | Price schedule |
| List offline and invoiced payments | Accounts receivable clerk | Invoice ledger |
| Apply the currency rule | Finance | Rate source |
| Calculate deferral by event date | Controller | Event calendar |
| Tie cash to bank deposits | Controller | Bank statement |
| Sign recognized revenue | CFO | Completed bridge |
Sign-off means the owner has seen the named evidence, whether or not the figure looks about
right.

## How do you handle revenue that spans fiscal periods?

By deciding on event date, not on sale date, and applying it without exception. Registrations
collected in March for a September event held in the next fiscal year are deferred revenue: a
liability when the money arrives, revenue when the event happens.

Registration has moved late, which changes where the deferral sits. The Maritz Registration
Insights Report analyzed more than 360,000 registration records across 30 trade shows and found
that in 2023, 45% of registrants signed up in the final 4 weeks before the event and 9% on site
([PCMA Convene](https://www.pcma.org/rethinking-early-bird-pricing-other-event-registration-strategies/)).
Those are registration records from trade shows, not a survey and not association conferences,
so check the shape against your own curve. A late curve concentrates revenue near the event
date, which usually simplifies deferral and makes any
[early bird](https://eventiq.io/md/blog/early-bird-pricing) cohort sold in a prior period the exception to flag.

Three cases need a stated rule:

- **Multi-year passes and bundled memberships.** Set the split in advance, not case by case.
- **Sponsorship with deliverables spanning periods.** Recognition may follow delivery in place
  of the event date.
- **An event that moves after registrations are sold.** The move changes the recognition period
  for revenue already collected, and teams handle it worst under time pressure.

## Example: from the registration report to the recognized number

Take an association annual meeting with 1,800 badges issued, of which 1,602 are paid and 198
are comped. The meeting is held one month after the fiscal year end, so registrations sold
before year end sat in deferred revenue at that close and are recognized now, on the event
date. The same platform account also took advance registrations for next year's meeting. All
figures are hypothetical.
| Line | Amount | Running total |
| --- | --- | --- |
| Gross bookings per platform, at cut-off | $1,412,000 | $1,412,000 |
| − Refunds and cancellations to cut-off | ($38,500) | $1,373,500 |
| − Deferred: advance registrations for next year's meeting | ($96,000) | $1,277,500 |
| − Discounts shown at list price on the summary view | ($21,000) | $1,256,500 |
| − Reversed and duplicate transactions | ($7,400) | $1,249,100 |
| + Offline payments: checks, wires, and invoiced corporate group registrations | $63,000 | $1,312,100 |
| − Currency translation on international registrations | ($4,900) | $1,307,200 |
| Recognized registration revenue |  | $1,307,200 || Line | Amount | Running total |
| --- | --- | --- |
| Recognized registration revenue | $1,307,200 | $1,307,200 |
| + Deferred revenue collected in cash | $96,000 | $1,403,200 |
| − Invoiced and unpaid at close | ($28,900) | $1,374,300 |
| − Payment processor fees | ($41,600) | $1,332,700 |
| Cash deposited per bank statement |  | $1,332,700 || Line | Figure |
| --- | --- |
| Badges issued | 1,800 |
| − Comped: speaker 41, board 22, press 18, sponsor allocation 84, staff 33 | (198) |
| Paid registrations | 1,602 |
| Average net paid registration: $1,307,200 ÷ 1,602 | $816 |
The recognized number is $104,800 below the registration report, 7.4% of the platform figure,
and every dollar of the gap sits on a named line. Five points are worth drawing out.

The $96,000 deferral is the largest single item and has nothing to do with accuracy. It is a
period question, and the only wrong answer is an unstated one. The $63,000 of offline payments
moves the number up, which surprises teams who assume every adjustment is a deduction. The
$41,600 of processor fees never enters the revenue bridge, because netting them would
understate both revenue and cost.

The 198 comps produce no revenue and are reported as a headcount, which keeps the average net
paid registration honest: $816 across 1,602 paid registrations, against $726 across all 1,800
badges. The first figure is 12% higher than the second, and whichever one is reported gets
quoted for a year. If a residual difference had remained after every line, it would appear as
an unexplained difference with a value on it, outside the refund line.

## What to do this quarter

- Write the eight definitions, and have the CFO and the events lead sign the same page before
  registration opens.
- Set the cut-off date in advance and freeze a timestamped export on it.
- Move processor fees out of any revenue line they are currently netted against, and restate
  the prior year on the same basis so the comparison holds.
- Build the bridge template with a named owner and required evidence for each line.
- Identify every route by which money arrives outside the registration platform, and agree who
  lists them at close.
- State the deferral rule, including multi-year passes and what happens if an event date moves.

## Common questions

### Should the registration platform or the ledger be the source of truth?

The ledger, for revenue. The platform is the system of record for registrations, ticket types,
and headcount. Most reconciliation arguments come from treating one system as authoritative for
something it was not built to hold.

### How large a difference is acceptable?

Agree on a materiality threshold with your controller in advance and apply it consistently. The
size matters less than whether each difference is named: a fully explained 8% difference is a
clean reconciliation, and an unexplained 0.5% is not.

### Do we need to reconcile before the wrap report?

Yes, and it is one of the reasons the [post-event report](https://eventiq.io/md/blog/post-event-report-template)
arrives late. Tying the platform total to the ledger rarely works on the first attempt, so
schedule a full day for it.

### What about sponsorship and exhibit revenue?

Same bridge, different sources: contracts and the invoice ledger in place of the registration
platform, with recognition sometimes following delivery. Give it its own written definition,
because its place in the revenue mix is shifting: in Naylor's 2026 benchmarking report of 665
senior association professionals in North America, sponsorship's share of
[non-dues revenue](https://eventiq.io/md/blog/non-dues-revenue) slipped from 29.7% to 25.3%
([Naylor](https://www.prweb.com/releases/2026-association-benchmarking-report-reveals-associations-are-getting-more-intentional-about-data-ai-and-revenue-302842546.html)).

## Where EventIQ fits

EventIQ replaces nothing. It connects on top of the platforms you already run: event platforms
(Cvent, Zoom, Swapcard), CRM (Salesforce, HubSpot, GoHighLevel), and marketing (Google Ads, Meta
Ads, LinkedIn Ads, Mailchimp, Google Analytics). Platforms with an API outside that list are
connected on request.

The finance side of this page sits outside the product. EventIQ has no connection to an
accounting or finance system, so the general ledger, the processor and bank records, and the
recognition policy stay where they are, and EventIQ has no view of them. It does not convert
currencies either: the currency stays on each source record. The bridge and the cash tie-out
are your finance team's work.

What it holds is the registration side. Registrations from Cvent carry their date, ticket type,
and price where the platform provides them, so the ticket type mix and the average price per
type are figures you can read on the event and set beside your frozen export.

The budget and revenue figures on an event are ones your team enters: the budget lines and a
revenue target. The ROI shown is arithmetic on those entries, so it does not stand in for the
recognized number that comes out of your ledger.

[Book a demo](https://eventiq.io/#early-access) to see registrations by ticket type and price beside the budget
you enter on a sample event, in a 20-minute demo.

---

HTML version: https://eventiq.io/blog/reconciling-event-revenue