Finance guide
Deferred ticket revenue should reconcile like a rollforward, not a mystery balance.
A practical ticket-finance workflow keeps the liability connected to the ticket activity and the recognition entries that release it.
The core rollforward
Beginning deferred revenue + new sales - refunds +/- approved adjustments - posted recognition = ending deferred revenue.
What makes this difficult in practice
Ticket activity may span seasons and accounting periods, recognition depends on the organization’s policy and event status, and refunds or corrections can change the liability after the original sale. Finance needs the movement history, not only the ending account balance.
What a controlled workflow should retain
- Event and deferred-revenue account.
- Dated source activity and opening positions.
- Refund and adjustment movements.
- The rule that determined recognition.
- Posted recognition journals and reversals.
- Supporting references and approvals.
WREKONN supports this as part of the ticket-finance subledger and close process rather than treating deferred revenue as a disconnected spreadsheet.