The most expensive word in venue software is “also”

Twenty-five years in this industry, and there’s one slide I’ve seen in almost every vendor deck, including a few I’ve presented myself. It’s the architecture diagram: a ring of modules around a central hub. CRM, enquiries, space bookings, orders, staffing, reporting, and sitting on that ring, just like all the others, the same size and the same colour: accounting.

For most of my career, that box was a selling point. It was the thing that won the room, and I used it to win a few myself. But somewhere along the way, it became harder to make that argument. Not because the box changed, but because everything around it did.

Why it made sense in 1996

To understand why that accounting box ended up there in the first place, think about what building venue software looked like 30 years ago, or even 20 years ago. There were no APIs, no webhooks and no integration platforms. If your booking system needed to raise an invoice, you had two options: build a ledger yourself, or hand the customer a CSV export and a shrug.

So vendors built ledgers. All of them. It wasn’t empire-building. It was the only practical way to give a venue a working day. For a long time, it was the right call: one database, one login and a finance team that didn’t have to rekey anything.

I want to be fair about this, because the people making those decisions were solving a real problem with the tools they had. Every serious platform in this category carries some version of that choice in its foundations. The trouble is that the world that decision was made for no longer exists, and the software built for that world hasn’t necessarily evolved with it.

Compliance stopped standing still

Here’s the change I don’t think our industry has fully priced in. Financial compliance used to move slowly. Tax rules changed every few years, your auditor wanted broadly the same reports they wanted the year before, and a ledger written in 2004 could still be fit for purpose in 2014.

That’s no longer the world we operate in.

Venues operating in Singapore need to plan for a phased “InvoiceNow” schedule. Others in Malaysia are navigating LHDN’s staged e-invoicing rollout. Across Europe, ViDA has put structured digital reporting on a published timetable running to the end of the decade. Australia has been pushing PEPPOL for years, while the US has taken a more fragmented, business-driven approach to e-invoicing.

The important point is not simply that these requirements are changing. It’s that software vendors need to keep up with them, market by market, year after year. So ask a practical question: how many people does your venue platform vendor have working on its finance capabilities? How much focus and priority do those capabilities get compared with everything else the vendor is building?

Now compare that with a dedicated finance platform, where teams of specialists are focused on finance, automation and statutory compliance across the markets they serve. A specialist can dedicate its resources to keeping up with financial requirements because finance is its core business. A generalist has to divide its resources across venue management, CRM, finance and everything else it promises to do.

When compliance keeps changing, that difference can have a direct impact on the efficiency of your finance team and the compliance of the organisation as a whole.

And everything is moving faster, not slower

Compliance isn’t the only thing moving faster. Technology itself is accelerating, with almost every software category now investing heavily in AI. Forecasting, anomaly detection, natural-language reporting and agents that do the work rather than simply display it are becoming part of the conversation across the industry.

This creates another challenge for generalist platforms. When you focus on one domain, you can put your resources into making that product better. Try to be a venue system and a CRM and an accounting package, and those same resources have to be spread across three different disciplines.

That word, “also”, is where the money goes. Every “we do that too” means resources that could have been spent making the core product better are being spread somewhere else.

“But using a single vendor is simpler”

This is the obvious counter-argument, and I’ve made it myself. One contract, one database and fewer integrations. On paper, that sounds simpler. But what are you giving up in return?

You’re accepting a single roadmap that you don’t control, where every part of your operation depends on the pace of the same vendor. You’re also relying on that vendor to keep up with statutory changes in every jurisdiction you operate in, indefinitely.

And you’re accepting a ledger that was built to support a venue system, at a time when specialist finance platforms were not yet doing everything they can do today.

Modern finance platforms do far more than record transactions. They can capture and code supplier invoices automatically, keep up with changing regulations, provide ready-made reporting templates per country and per state, automatically link up to financial institutions, chase outstanding payments, flag unusual transactions, consolidate multiple entities and support open banking standards.

None of that came from a single release. It came from years of investment and specialist teams focused on finance.

The accounting module inside a venue platform was built to support the venue platform. Its job was to record transactions and connect them to the rest of the operation. Thirty years ago, that may have been enough. Today, specialist finance platforms can do much more.

So fewer suppliers does not necessarily mean a simpler operation. It can also mean less capability and less flexibility. And if your accounting system has no clean way out, you’ve bought something else as well: the difficulty of ever moving away from that solution, no matter how much technology evolves.

So what’s the right answer?

Of course, I’m not arguing that your venue should be using 15 disparate systems and a spreadsheet to integrate the data. That’s a different disaster, and I’ve watched venues live through it for years.

The question shouldn’t be “how many systems do I need?” It should be “where should I connect them to make them all perform at their best?”

Some parts of the venue operation should stay connected. An enquiry becoming an opportunity, a booking becoming a live event, and a live event becoming a repeat customer are all part of one story about one relationship. Break that flow, and you create work for humans that software should be doing.

But statutory accounting is different. It isn’t part of the same operational process as managing enquiries, bookings and events. It has different regulations, different requirements and specialist expertise. That is where integration matters.

Connect your venue platform to a specialist finance system, and you create a clear handover between two systems that are each doing what they are built to do best. Your venue teams get a connected operational workflow, while your finance team gets the specialist capabilities they need to manage compliance and financial processes effectively.

That is a very different proposition from simply putting everything under one roof. Putting both systems on one platform isn’t necessarily true integration. It can simply mean having them side by side.

The goal isn’t fewer systems. It’s better systems, connected in the right places.