Year-end conference and event season: controlling deposits and room inventory across multiple properties

Part 1: What advance receipts look like at portfolio level

Before discussing what to do, let us describe the current situation accurately. In a multi-property portfolio without a shared convention, the single idea of "money guests have paid in advance" usually exists in at least five different forms.

Five ways of taking and recording money that run side by side

• Room deposits from individual guests, usually one night's room rate, by bank transfer or as a pre-authorisation on a credit card, handled by the front desk.
• Security deposits under event contracts, calculated as a percentage of the contract value, handled by the sales team and usually kept in that team's own tracking file.
• Deposits on group room blocks, calculated by the number of rooms held, with a schedule for reducing the number of rooms at set dates.
• Full prepayments for advance-sale programmes, holiday packages or gift vouchers — money that can be used for several nights, at several times, sometimes at another property in the same portfolio.
• Guarantees placed by agents or tour operators, usually with their own payment terms and not always tied to a specific booking from the start.

Three consequences when these five forms do not follow one convention

• Nobody can answer within a minute: how much guest money is the portfolio holding? This is a liability, and it is a figure you need before every major spending decision of the quarter — not a figure you look up after several days of consolidation.
• Revenue lands in the wrong period. When one property records advance receipts in the month the money arrives and another records them in the month the guest stays, the consolidated revenue picture for the final quarter is inflated in some places and short in others, and the cause cannot be traced.
• Legal risk and customer-relationship risk pile up in the same place. An event-contract deposit that has not been properly reconciled is exactly what resurfaces in a difficult conversation with a corporate client, usually at the worst possible moment.

Part 2: One deposit convention shared by the whole portfolio

The solution is not to tighten control property by property but to issue one single convention, so that the five forms described above are recorded in the same way. This is what hotel booking deposit management means at portfolio scale, and it has four components.

The four components of the shared convention

• 1. One shared classification of advance receipts. Individual room deposit, event-contract deposit, group block deposit, full prepayment, agent guarantee — one code per type, shared across the whole portfolio, with no "other" box. Only with this classification can the reports of all properties be stacked on top of each other.
• 2. Every receipt must be attached to a specific object. A booking, a group room block or an event contract — no amount is left floating at property level. An amount that cannot yet be attached is a suspense item, and the list of suspense items must be reviewed every day during the peak, not every month.
• 3. One single point at which an advance receipt becomes revenue. That point is the night the guest actually stays, or the day the event actually takes place — not the day the money reaches the bank account. This convention must be issued in writing for the whole portfolio and must allow no exceptions by property, because every exception is a mismatch at consolidation. The link from here to the books is covered in the article on hotel chain accounting under Circular 99.
• 4. A rule for flagging amounts used across properties. When a prepaid voucher is sold at one property and used at another in the same portfolio, the amount must be identifiable at both ends — otherwise the portfolio will record the same money twice at consolidated level.

When all properties run on the same multi-property hotel management software, the classification lives in one place and is enforced automatically: front-desk staff at every property can only choose from the exact set of codes that has been issued, and every receipt must be attached to an object before it can be saved. When properties run on different systems, the convention can still be built, but it has to be maintained by human discipline — and discipline wears thin fastest exactly when the house is full.

Part 3: Conference and event contracts — many instalments, one tracking schedule

A contract to host a year-end conference or event differs from an individual booking in three basic ways: its value is high, the time between signing and the event is long, and the money arrives in several instalments. Together, these three create a risk of their own — the risk of forgetting.

Four things every contract must have in the system, not just on paper

• An instalment schedule with specific due dates. Holding deposit, the instalment on confirming numbers, the instalment before the event date, final settlement after the event — one line per instalment, with a due date and an expected amount. Only if this schedule lives in the system can it generate alerts; if it lives in the account manager's own file, it depends on whether that person opens the file.
• The conditions attached to each instalment. Many contracts require a minimum number of rooms and covers to be confirmed before a certain date, and the amounts of later instalments depend on that confirmed figure. If the condition is not recorded next to the payment line, it will only be remembered once the date has passed.
• A person responsible for tracking each contract. A specific name, not a department. During the peak, anything that belongs to "a department" usually belongs to nobody.
• A link between the contract and the room block being held. This is the link that breaks most often: the contract sits in the sales file, the room block sits in the operations system, and when the contract changes size the room block does not change with it. The result is rooms held for an event that has already shrunk, in the middle of peak week.

Three situations to settle in advance, not while they are happening

• The client postpones the event. Whether the money already received can be moved to the new date, how many times it can be moved, whether there is a time limit on using it, and whether it can be moved to another property in the portfolio. A property-transfer clause is worth having, because it keeps the revenue inside the portfolio instead of losing it altogether.
• The actual size is smaller than committed. How the shortfall is calculated must be clear in the contract and must be configured as a charge line in the system, rather than left to be negotiated at settlement.
• The event is cancelled outright. The part of the advance receipt that is retained and the part that is refunded must be clear-cut; just as important, the room block must be released on the same day the cancellation is decided. Every day of delay in releasing it during the peak means room nights that can no longer be sold.

Part 4: Groups holding many rooms — release deadlines and cut-off schedules

Group room blocks are a necessary sales tool and also the place where inventory is locked up the most during the peak. The key point is very simple: a room block with no deadline and no cut-off schedule is, in essence, an open-ended promise — exactly like a promise to hold a room made over the phone at a small property, only many times larger.

Five things every room block must have

• A final confirmation deadline. A specific date, agreed at signing, after which the unconfirmed part is automatically returned to sale.
• A staged cut-off schedule. Instead of one single date close to arrival, set several dates for gradual release — for example, release part of the block at an early date and a larger part at a later one. This returns rooms to the market sooner, while there is still time to resell them.
• A display status that differs from both available rooms and sold rooms. Whoever sets rates and whoever is on sales duty must be able to tell straight away on screen which rooms are genuinely available and which are being held for an unconfirmed block.
• Tracking the actual pick-up of each block. A partner that regularly holds more than it uses is something you need to know before signing next season's contract, and you only have that information if the system keeps it.
• A rule for released rooms. Return them to open sale immediately, or hold them for the waiting list first — decide in advance and the person on duty does not have to ask anyone in the middle of the peak.

A note on tone when working with corporate partners: deadlines and cut-off schedules are not strictness; they are the condition that allows a property to keep rooms available for those same partners in future seasons. Most corporate clients are used to this way of working and accept it when it is made clear at signing; what causes friction is only a condition that appears late.

Part 5: Shared room inventory when several properties hit peak season together

In a single-property portfolio, inventory is an in-house problem. In a portfolio where several properties are full in the same week, it becomes a coordination problem — and also the place where a portfolio has a genuine advantage over a standalone hotel, provided it can see enough.

Four things you can only do when you see inventory across the portfolio

• Move guests to another property in the portfolio instead of turning them away. When one property is full for a night and another property in the same area still has rooms, keeping the guest inside the portfolio is only feasible if the person on duty can see the other property's inventory while still talking to the guest — not after a phone call to ask.
• Split group blocks between properties. A large group can be divided between two nearby properties. That decision needs one single screen showing the inventory and the blocks already held at both places.
• See early which nights are about to sell out across the portfolio. Knowing a week ahead that three properties are about to fill up on the same night is when there is still a lot you can do — rearrange unconfirmed blocks, open additional room types, coordinate seasonal staff. Knowing after they are full leaves you only able to record it.
• Separate three kinds of unsellable rooms. Rooms out of service long term, rooms temporarily not ready, and rooms held for unconfirmed blocks are three different things and must be displayed differently. Lump them together and the portfolio's count of sellable rooms is wrong from the start, and every decision based on it is skewed.

Two pricing principles during the peak

• Set up multiple seasonal and event rate plans in advance, before the peak starts. The person on duty chooses an approved rate plan by date range, instead of deciding each case alone in the middle of a busy shift. To avoid mistaken expectations: this is about preparing and applying rate plans by date, not a feature that adjusts prices automatically to the market — that feature is on the roadmap with the label Coming soon.
• Keep the rates committed in contracts unchanged, even when the market moves. This sounds obvious, but it needs to be guaranteed by system configuration rather than by memory, because during the peak broad price changes very easily sweep across room blocks that are already under contract.

Part 6: Summary table — where things get stuck during the peak and how to handle them

Part 7: Six figures leadership should look at every day during the peak

In the busiest weeks, a monthly report is too late and a full report is too long. Below is the set of six figures we recommend looking at every day, at the level of each property and at portfolio level.

The six figures

• 1. Total guest money held for nights that have not yet taken place. This is a liability, not a source of funds — and it is the figure you need before every major spending decision in the quarter.
• 2. Number of receipts not yet attached to any object. This figure must be zero at the end of every day during the peak.
• 3. Number of contract instalments that are overdue or due within the next seven days. With the name of the person responsible on each line.
• 4. Number of rooms held for unconfirmed blocks, by each upcoming cut-off date. This is inventory that can be recovered, and it can only be recovered in time if it is seen early.
• 5. Nights about to sell out across the portfolio in the next two weeks. Look by night, not by week — because coordination happens night by night.
• 6. Number of unsellable rooms, split by the three statuses. An unusual rise in rooms temporarily not ready in the middle of the peak is a signal that calls for intervention the same day.

These six figures belong to the operational layer. For owners and boards, the right read layer is a dedicated read-only app showing exactly the agreed set of management indicators — how the roles of these two layers are divided is covered in full in the article on one dashboard for the whole chain, while the income-statement structure behind the performance indicators is in the article on the USALI standard.

Part 8: What to do before the peak begins

The order below is deliberate: the first four items are management decisions, cost almost nothing and can be done in one session; the last three are system configuration and should be started early so that the properties have time to get used to them.

Four management decisions

• Item 1 — Issue a shared classification of advance receipts for the whole portfolio, with a one-sentence definition of each type.
• Item 2 — Issue the point at which advance receipts become revenue, one single point, with no exceptions by property.
• Item 3 — Settle the postponement, downsizing and cancellation policy for event contracts for the whole season, including the clause for transferring to another property in the portfolio.
• Item 4 — Standardise confirmation deadlines and cut-off schedules for every group room block, and build these dates into the contract template instead of negotiating them again each time.

Three configuration items

• Item 5 — Put each contract's payment schedule into the system, with alerts ahead of each due date and the name of the person responsible.
• Item 6 — Turn on the portfolio-wide inventory screen for sales staff at every property, and separate the three statuses of unsellable rooms.
• Item 7 — Set up seasonal and event rate plans in advance, and lock the rates of room blocks already under contract so that broad price changes cannot sweep across them.