The June gap
Tripleseat says $412K of events happened in June. The P&L says $391K. Nobody can explain the difference in under an hour, so nobody asks anymore.
Worked example
This is an illustrative model. We built a realistic composite venue to show what the monthly work looks like — the numbers, the problems, and the decisions. Your venue will differ; the pattern rarely does.

A good business. Full calendar, strong reputation, waitlist Saturdays. And every meaningful financial decision — pricing, hiring, packages, the line of credit — made from instinct and a bank balance.

Six things, each familiar on its own. Together they mean the venue is being run on instinct.
Tripleseat says $412K of events happened in June. The P&L says $391K. Nobody can explain the difference in under an hour, so nobody asks anymore.
The integration is mapped to a single Tripleseat income account — weddings, corporate, service charges, all indistinguishable on the ledger.
Deposits land in revenue the month they’re paid, so booking-heavy February looks like the best month of the year and event-heavy June looks mediocre.
Labor sits in one bucket, COGS in another, bar activity in Square’s own reports — none of it mapped to event types. What does a wedding actually earn? No answer.
Every winter the venue draws on the line of credit. Every winter it’s a surprise, even though the deposit schedule made it inevitable back in September.
The books close, eventually. The reports arrive. Nothing changes. Pricing gets set once a year, by feel.
Not a software problem, and not a bookkeeper problem. A structural one.
Tripleseat runs the calendar. QuickBooks keeps the ledger. Omniboost moves payments between them. None of the three was designed to answer what a wedding earned — that’s a finance question, and it’s nobody’s job until it’s someone’s job.
Venues sell the future: money arrives before the event, costs arrive after. Without deliberate deposit and deferred-revenue treatment, the P&L describes the sales calendar, not the business.
A chart of accounts either answers owner questions or it doesn’t. A single Tripleseat income line answers none.
Here’s what June looks like in the owner’s packet once the close is disciplined and the mapping is rebuilt.
Revenue by event type
Contribution by event type
Ties to the ledger — and the gap to the $412K booked total is boring, which is the point: tax and service-charge pass-throughs sit on the balance sheet, and deposits are held until the event date. The reveal: corporate looked like easy money and is the margin laggard once AV costs and setup labor are mapped to it.
Weeks 1–13 · trough highlighted
The January trough is now visible in September, with the driver named: the 50/25/25 schedule concentrates final payments in peak months and starves the winter.
Booking pace: fall is pacing +9% over last year, but the mix is quietly shifting toward social events. Revenue up, profit quality down — caught while it’s still a choice.
Four decisions left June’s owner meeting. Each with a name and a date. This is what the monthly work is for — not the reports, the decisions.
Reprice the Saturday wedding package +4% for next season. Lead-time data says demand supports it.
Owner: GM — decide by Oct 1
Move new contracts to a 60/25/15 deposit schedule to pull the January trough up.
Owner: Sales lead — effective immediately
Stop discounting social events into Saturday slots. Saturdays are wedding inventory.
Owner: Sales lead
Rebuild corporate AV as a pass-through with margin.
Owner: GM — next three proposals
Decisions · owners · due dates · reviewed at the next monthly meeting
The math, stated plainly.
The CFO Partnership for a venue like this runs $8,500–$11,000 a month. The point of the table isn’t that the fee pays for itself. It’s that the venue was already paying it — invisibly, every year.
Foundation. Close standards and a close deadline. Consistent deposit and deferred-revenue treatment. A chart of accounts rebuilt around owner questions. Monthly tie-outs between Tripleseat, the ledger, Square, payroll, and the bank. It’s not glamorous, and it’s the reason every number above can be trusted.
It's the norm. Foundation exists because almost nobody's starting point is clean. The close standards, deposit treatment, and category work come first, precisely so the numbers above can be trusted.
No. They are the most common pair and we know them deeply, but the requirement is clean, exportable data and a consistent monthly close. Other booking and accounting systems can work.
Ranges vary by market, service model, and F&B structure. The spread between event types — and the surprise about which type lags — shows up almost everywhere.
Every venue has its own symptom list. The Diagnostic puts yours in writing — close quality, deposit handling, event-level margins, cash risk, and a prioritized 90-day roadmap. $7,500, fully credited toward Foundation, and the roadmap is yours to keep either way.