Book a call
EVENT FINANCIALS

What was delivered
is what gets invoiced.

The event order says what happened. The charges follow it. Forecast against actuals while the event is still live, invoice from what was actually delivered, and take the money without leaving the booking.

Built for institutional AI · Powered by Salesforce · Modern and agile

Invoicing · deposits and payment plans · live revenue view per event

THE MONEY ON THE EVENT

The commercial life of the event,
from quoted to paid.

Event Financials owns the money that belongs to the event: what it was expected to make, what it cost, what was actually delivered, what was invoiced, and what has been paid. It runs on the same booking record as the sales and operations work, which is the only reason the numbers agree.

What it deliberately does not do is replace your finance platform. Statutory accounting, tax filing, consolidation and the ledger stay where they belong, and Thynk hands them a clean, complete record. You get both: a platform built for the commercial and operational life of a venue, and a finance system built to keep pace with compliance in every market you work in.

CAPABILITY

Cost Analyzer

Forecast against actuals, per event, while there is still time to do something about it.

Every event carries an expected revenue and an expected cost: space, catering, staffing, AV, external services. The Cost Analyzer holds both against what is actually being delivered, so the gap between the two is visible during the event rather than at close-out six weeks later.

Because costs sit on the same record as the work orders that generated them, a change made on the day shows up in the margin the same day. A venue can see which event types, which halls and which clients actually make money, rather than inferring it from a revenue line that never had costs attached.

CAPABILITY

Invoicing

Built from delivered services, not from the contract signed three months earlier.

The chain runs in one direction and it never leaves the record: event order → delivered service → actualized charge → invoice → payment. The forty extra covers added on the morning of the event are on the invoice because they are on the event, not because somebody remembered to add them.

Actualized charges

What was ordered, what was delivered and what is being charged, held separately and reconciled on the event. Disputes are settled by looking at the record rather than by arguing about it.

Invoice from the event

Invoices generated against the booking, in your template, with the breakdown the client expects: spaces, catering, services, equipment, per event or per day where that is how the client wants it.

Multi-currency and tax

Rates and taxes applied per venue and per client, with the tax summary visible on the booking before anything is issued.

Straight through to finance

Issued invoices flow to your finance platform through Thynk Connect, two ways, so payment status comes back without anyone rekeying it.

CAPABILITY

Proforma invoicing, payment plans, payments

The money that has to arrive before the event, tracked as carefully as the money that arrives after it.

Large events are paid in stages: a deposit to confirm, a second payment at a milestone, the balance after delivery. Proforma invoices and payment plans are set on the booking, so what is due, what has been received and what is overdue is visible on the event rather than in a separate schedule somebody maintains by hand.

Payments record against the plan, deposits offset the final invoice automatically, and the event’s financial position is one number rather than three people’s recollections.

ON EVERY BOOKING

The real-time financial view.

Revenue by category, tax summary, deposits, grand total. Live on the booking, from the first quoted line to the final payment.

Sales sees it while building the event. Operations sees the effect of a change on the day. Finance sees the same numbers, at the same moment, without a report being run. It appears as the Finance tab on the booking record in Booking & Event Management, and it is defined here.

THYNK PAY

Take the payment
where the booking already is.

A payments product built into the booking rather than bolted onto the invoice.

Online payment

Clients pay an invoice online, by card or bank transfer, from a link rather than by arranging a transfer against a reference nobody quotes correctly. The payment lands against the event, not in a suspense account waiting to be matched.

Instant booking engine payment

Payment taken inside the online booking flow, at the moment of booking. It belongs to Online Booking, and it is described in full there.

In practice:
forty covers, added at 10:15.

A conference contracted for 260 delegates turns up with 300. The coordinator adds forty covers to the lunch on the event, and F&B gets the work order. That is one action, on one record.

The Cost Analyzer updates: revenue up, food cost up, margin on the event recalculated before the plates are cleared. The event order shows the change with a timestamp, so nobody has to establish later whether it was agreed. When the invoice is raised, the forty covers are on it at the contracted per-head rate, with the change visible behind them if the client queries it.

The invoice goes to the finance platform through the integration. The payment comes back the same way. Nobody rekeyed anything, and the ledger is where the ledger belongs.

HOW IT SITS IN THE PLATFORM

Between delivery and the ledger.

WHERE IT BRINGS VALUE
  • Margin on the event visible while the event is still running
  • Invoices built from what was delivered, not what was contracted
  • Deposits and staged payments tracked on the event, not in a side schedule
  • Tax and currency handled per venue and per client
  • A clean, complete handover to your finance platform
AND CONNECTS WITH
  • SAP, Microsoft Dynamics, Oracle Financials, NetSuite and other modern finance platforms
  • E-invoicing networks, through your finance platform
  • Payment providers, through Thynk Pay
  • Banking and reconciliation, through your finance platform
  • Salesforce reporting and the open API
QUESTIONS WE GET ASKED

Frequently Asked Questions

Does Thynk replace our accounting system?
No, and that is deliberate. You get the best of both: a leading CRM and event management platform for the commercial and operational side of the venue, and a high-performing finance system for the ledger, with the compliance and localization requirements of every market you work in. Thynk owns forecast, cost, delivered services, invoices, deposits and payments. Your finance platform owns the ledger, consolidation, tax filing and statutory reporting. The two are connected both ways, so neither has to pretend to be the other.
Do you handle multiple currencies and complex tax requirements?
Yes. Quotes, bookings and invoices can be issued in the currency the client contracts in, while the venue reports in its own. Tax is applied per venue, per client and per product type, and the tax summary is visible on the booking before anything is issued. Where a market has statutory formats or e-invoicing mandates, those are handled by the finance platform Thynk connects to, which is the part of the chain built to keep pace with them.
How does a change on the day reach the invoice?
Through the record, not through a person. A change made on the event creates the work and the charge at the same time, so the invoice reflects what was delivered rather than what was contracted. The change is on the audit trail if the client queries it.
Can we track forecast against actuals per event?
Yes. That is what the Cost Analyzer does: expected revenue and cost against what is actually being delivered, live on the event rather than at close-out. Profitability by event type, hall, client and period is reported in Analytics & Reporting.

See it on your close-out.
Bring the event that was hardest to bill.

A 45-minute call with the team. Start with the event where the invoice took three weeks and two arguments, and we will show you what it looks like when billing follows delivery.

Operate hotels too? See the Thynk hotels platform →