How growing hotel groups share finance across properties

A group running 20 hotels, with five more opening next year, faces a familiar question: does each new property need its own finance team? The default answer is usually yes, if that is how the existing hotels were set up.

That default is getting harder to justify. When a property-level finance role sits vacant, the income audit falls to whoever is covering it, and outside major cities those vacancies are slow to fill. The work itself has changed too: much of the role was keying, copying and chasing, and software now does that part.

The largest chains answered this by building shared service centres, often as multi-year projects. There is a lighter option. When finance work runs in one digital workflow, a new hotel joins the existing team instead of needing one of its own, usually within weeks, because the group's interfaces and mapping already exist.

What each new hotel adds to the finance workload

Every new hotel adds to the daily workload:

• another income audit, with a pack to compile, check and sign off each morning

• another approval chain for invoices, credit notes and adjustments

• another set of documents to file, and to find again when auditors ask

• another finance role to recruit, train and cover during leave

Run separately, each property also develops its own version of these. Group finance then struggles to compare hotels, or to confirm that yesterday's income audit at a given property was signed off.

A cluster is a team, not a building

A hotel finance cluster is a group of properties whose finance work, such as the income audit, accounts payable and accounts receivable, is handled by one shared team. The team can sit in one office or across the group's existing hotels, so a dedicated head office is optional. When several hotels operate in the same city, the team often works from one of them.

Hilton Netherlands clustered finance for five hotels, including large properties like Hilton Amsterdam and Waldorf Astoria Amsterdam. On the income audit, one person now covers three or more properties.

In the clusters we have set up, ratios like that depend on how standardised the income audit already is and how many revenue streams each property runs, so treat any one figure as a planning reference.

Clustering does reduce the number of finance roles a portfolio needs, though much of that absorbs vacancies that were hard to fill anyway. Staff who move into cluster roles can usually keep working from where they live.

Agree the process before you digitise it

Most groups start with the income audit, the daily review that confirms the previous day's revenue was captured, posted and approved correctly. It is the simplest finance process to standardise and in many hotels the biggest daily inefficiency.

The instinct is to digitise it as it stands, only faster. But making a bad process electronic does not improve the process. A siloed, time-consuming audit becomes a siloed, time-consuming audit with a login.

In a cluster, five versions of the income audit become the shared team's problem, run with fewer people. That is the version of clustering that fails, and the cause is rarely the software.

Agree the process first: the same pack contents, tolerances and approval rules at every hotel. It is the slower conversation and the one everything else depends on.

IHG properties in Singapore and Portugal used DocMX to automate 90% of their income audit reporting, and across its wider estate IHG runs group-level finance compliance checks in DocMX covering more than 500 hotels. Accounts payable and receivable usually follow once the income audit runs in one workflow.

Who still approves what

Anything that has to happen on site stays at the hotel, and so does accountability. The finance lead for each property still signs off its income audit, and general managers approve allowances, rebates and adjustments above agreed thresholds. They approve digitally, so the shared team and group finance see each approval as it happens.

Separate legal entities don't change this. Workflows are configured per property and jurisdiction, so local tax treatment and invoice formats are built into the process, and each entity's documents and approvals stay filed against the right company.

What changes is how much reaches them. Transactions matching within agreed tolerances are approved automatically, such as an invoice that agrees with its purchase order and goods receipt, known as a three-way match. The matching follows set rules; AI's role comes earlier, reading the invoice so the data is there to match. Spend arriving without a purchase order, common in F&B and services, goes to the budget holder instead. In our DocMX deployments, around 80% of transactions need no manual review.

The 20% that doesn't match

The transactions that don't match are where a person belongs. That is what a human in the loop should mean: someone steps in where there is an issue, and nowhere else. Approving the same supplier's matched invoice for the fourth month running adds delay without adding control. Control is knowing which transactions a person looked at, and why.

What reaches them is worth their time: a mismatch, a rebate that needs explaining, a write-off someone has to own. Matched invoices can be approved automatically, but the payment run is released by a person, because it commits the group's money and is hard to unwind.

Tolerances decide where the line falls. Groups often mirror the manual thresholds they had before, which were set by what one person could check in a morning, with little regard to where errors occur. Start tighter than you need, see what the exceptions turn out to be, and move the line on the evidence.

Group finance gains visibility

Shared finance gives group finance more control, because every approval, exception and document becomes visible across the portfolio, with a full audit trail. From our experience, these projects often start bottom-up: a few finance staff test a digital workflow at their own hotel, and group finance steps in to mandate a wider roll out once the impact is clear.

As a rollout grows, it is tempting to limit what properties do in the workflow to keep things uniform. That pushes the rest of their work back into email and spreadsheets, where group finance cannot see it at all. The more a property does inside the workflow, the more of its work is in view.

New openings are usually in scope from the start, so they join from day one. For a group planning them, a practical first step comes before recruiting finance staff: count how many versions of the income audit your existing hotels already run. That number shows how much there is to standardise, and how far one shared workflow could go.