One Auditor Now Covers Three Hotels as Groups Cluster Finance

One finance person now covers three or more hotels at Hilton Netherlands, which clustered income audit, accounts payable and accounts receivable across five properties including Hilton Amsterdam and Waldorf Astoria Amsterdam. The ratio is real, but it is a planning reference, not a guarantee. It depends on how standardised each hotel's income audit already is and how many revenue streams each property runs.

The model answers a concrete staffing problem. A group running 20 hotels with five more opening next year must decide whether each new property needs its own finance team. The traditional answer was yes, because that is how existing hotels were set up. That default is weakening. When a property finance role sits vacant, the income audit falls to whoever covers it. Outside major cities, those vacancies fill slowly. Much of the role was keying, copying and chasing, and software now does that work.

What does each new hotel add?

Every property brings a fixed set of finance tasks:

• another income audit 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 retrieve for auditors
• another finance role to recruit, train and cover during leave

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

The largest chains solved this with shared service centres, built over multi-year projects. A lighter option exists. When finance work runs in one digital workflow, a new hotel joins the existing team rather than forming one of its own, usually within weeks, because the group's interfaces and mapping already exist.

A cluster is a team, not a building. It 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.

Why standardise before digitising?

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

The instinct is to digitise the process as it stands. That instinct is wrong. 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 version of clustering fails, and software is rarely the cause.

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

IHG properties in Singapore and Portugal used DocMX to automate 90% of income audit reporting. 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?

On-site obligations stay at the hotel, and so does accountability. The finance lead for each property still signs off its income audit. General managers approve allowances, rebates and adjustments above agreed thresholds, digitally, so the shared team and group finance see each approval as it happens.

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

Transactions matching within agreed tolerances are approved automatically, such as an invoice agreeing with its purchase order and goods receipt, a three-way match. AI's role comes earlier, reading the invoice so the data exists to match. Spend arriving without a purchase order, common in F&B and services, goes to the budget holder. In DocMX deployments, around 80% of transactions need no manual review.

The remaining 20% is where a person belongs. Someone steps in where there is an issue, and nowhere else. Approving the same supplier's matched invoice for a fourth month adds delay without adding control. Matched invoices can clear automatically, but a person releases the payment run, because it commits the group's money and is hard to unwind.

Tolerances decide where the line falls. Groups often mirror old manual thresholds, set by what one person could check in a morning, with little regard to where errors occur. The guidance is to start tighter than needed, examine the exceptions, then move the line on evidence.

What does group finance gain?

Every approval, exception and document becomes visible across the portfolio, with a full audit trail. These projects often start bottom-up: a few finance staff test a digital workflow at their own hotel, and group finance mandates a wider rollout once the impact is clear.

One caution follows the promise. As rollouts grow, groups are tempted to limit what properties do inside the workflow to keep things uniform. That pushes remaining 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 day one. For groups planning them, the practical first step comes before recruiting any finance staff: count how many versions of the income audit the existing hotels already run. That number shows how much there is to standardise, and how far one shared workflow could go.