Plan an event budget and break-even
Everything about the event's money in one place: the results so far, the budget and how it compares with the books, what's still to come in or go out, tickets, overhead and closing.
Financial summary: at the top, gross revenue by source, direct costs, the net result and margin, paid and complimentary attendance and cost per attendee, from the event's entries in the books. Indirect costs (overhead shares) and hidden costs (complimentary tickets at list price and coupon discounts) are shown apart. The margin sits beside last year's edition (same series or name, 10 to 14 months earlier) or an earlier event you choose.
Budget: each line is fixed (a room rental) or per attendee (a meal, a ticket price). Break-even is how many attendees it takes for their contributions to cover the fixed costs left after sponsorships and other fixed income.
Budget vs actual vs expected: actual comes from the books (ticket payments, Stripe fees, refunds and sponsorships are linked to the event automatically; tag other expenses to it when you record them). Expected final adds what's still pending: commitments, unpaid tickets and pledged sponsorships. Each line off budget can carry a note on why: write it yourself, or use Draft notes with AI, which works only from the figures and saves nothing until you review it.
Commitments and tickets: commitments are costs agreed but not paid; paying one posts the expense. Those above the approval limit (Settings → Event finance) wait for an approver, never their own author. Tickets shows revenue by ticket type, free tickets by reason, and the event credit and donations taken at registration (donations are gifts, not ticket revenue).
Overhead and closing: overhead rules propose the event's share of shared costs; confirm them here. When everything is settled, the owner or an admin closes the event: a checklist shows what's still open, including online payments missing from the books or not yet paid out, and bank entries not matched; an admin can close anyway with a reason, and close the books for the event's month. Closing locks the event's finances and keeps a final snapshot; an admin can reopen it, with a reason.