When you book travel months in advance, you often pay right away. The trip itself is still a long time away, but the money has already moved. It’s been collected and sits in the system until your travel actually happens.

A Skift analysis by Rafat Ali, “Who Really Holds Your Travel Money Before You Travel and What Are They Doing With It”, describes that gap as float. It’s a useful lens, but the more important question for hospitality is not whether float is good or bad:

Does money reliably end up where it needs to go, when it needs to go, and is everyone paid in full?

Float exists not only in travel but also in several other industries. However, hospitality is where incentives and plumbing get especially tangled, with unproductive capital/liquidity tied up in clogged pipes across many parties and borders.

If we want to modernize how money moves in hospitality, especially in an agentic future, the angle cannot be “float vs. no float.” It has to be whether settlement actually works.

Float, in hotel-finance terms

In hospitality, float is the time between when a guest pays for a booking and when the hotel actually receives, reconciles, and can use those funds.

They typically remain as a customer deposit liability or deferred revenue until the reservation is fulfilled, canceled, forfeited due to a no-show, or otherwise settled.

Float exists because hotels (or a third party) sell a product with a long gap between booking and service delivery, and the final shape of the transaction is often unknown until very late in the lifecycle, when the following changes can occur:

• cancellations and partial cancellations

• date changes and rate re-pricing

• no-shows and late cancellation penalties

• post-stay adjustments (folios, taxes/fees, incidentals, disputes)

• chargebacks and card-present vs card-not-present timing differences

So float isn’t inherently a trick, but is a structural feature of hospitality, required to ensure that any late changes or fees are factored in to ensure a smooth guest experience.

The real question is whether the money is traceable, paid on time, and fully reconciled during that gap. If even some of these changes and risks were known about or mitigated up front, this float could be used more effectively.

Where float sits depends on the merchant of record

An important component of understanding float is that whoever acts as the merchant of record (MoR), or controls the payment model, usually determines where the traveler’s money sits until the booking is finalized.

If the hotel collects directly, the float sits with the property or operating entity. If an online travel agent (OTA), travel management company (TMC), or marketplace collects payment from the traveler and pays the hotel later, the float remains with that platform until settlement.

In other words, after the consumer pays, that money is now the travel agent’s money, but they have a liability/obligation to fulfill the end booking to the hotel.

If the booking is pay-at-hotel, there may be little or no pre-stay float. And if an AI agent or new checkout layer becomes the party collecting payment, float could shift again to a new balance sheet.

That is why MoR matters. It is not just a commercial label; it defines the flow of funds, the risk owner, and the timing of settlement.

The more fragmented or unclear that model is, the harder it becomes for hotels, platforms, and travel agents to know exactly where the money is, when it will move, and how exceptions will be reconciled.

Hospitality is different: deposits fragment across thousands of balance sheets

Hotel prepayments don’t typically pool into a small number of highly visible corporate balance sheets, such as those of an online travel agent (OTA), an airline, or a cruise line.

As Skift notes, most major hotel brands operate an asset-light model. They do not own most of the properties that carry their flag.

So prepaid guest deposits can land on the balance sheets of whoever owns or operates the property: franchisees, real estate investment trusts (REITs), private equity portfolios, management companies, or independents.

The money is still the same: a traveler paying in advance for a stay that hasn’t happened yet. The difference is that the float doesn’t form one big pile.

It fragments across thousands of entities with varying liquidity profiles, leverage, and operational maturity, with limited visibility into how those funds are held between collection and check-in. In other words, there are several different inflows, all with different outflow timelines.

This fragmentation is one reason hotel payments and settlements have historically been inconsistent:

• Different properties accept different payment methods

• Reconciliation requirements vary

• Folios and invoices are not standardized

• Exceptions are constant (cancellations, modifications, no-shows, post-stay adjustments, etc.)

• Finance teams on both sides end up resolving mismatches manually

In hospitality, float isn’t only a capital story. It’s also an operations story.

It is also a travel-agent story. Agents and advisors often get paid only after the stay is completed, and even then, commissions can be delayed, disputed, or missed entirely.

ASTA’s hotel commission reporting process, for example, focuses on hotels that have not paid commissions 45 days or more after a client’s stay and gives properties 30 days to resolve the issue before they can be added to a public watch list.

TravelAge West described the same threshold in its coverage of ASTA’s late-commission reporting tool.

That matters because a delayed commission is not just an admin nuisance. For the agent, it means earned money is being held back. For the hotel, it can damage preferred-supplier relationships.

And for the industry, it reinforces the sense that travel money moves through opaque, trust-dependent workflows rather than transparent, rules-based infrastructure.

This is why timely, accurate, and predictable money flow matters on both sides of the transaction. Hotels need confidence that payouts map cleanly to bookings, folios, and exceptions.

Travel agents need confidence that commissions owed are commissions paid, without weeks of chasing or manual reconciliation. Better settlement infrastructure ultimately serves as a trust layer between hotels and agents.

Timely settlement makes float less of an operational necessity

Depending on who holds the funds (property, operator, brand-managed entity, OTA/TMC/marketplace), float can function as:

• Working capital timing: cash on hand today vs. obligations later

• A risk buffer: protecting against reversals, disputes, and supplier/guest exceptions

• Yield (sometimes): interest on balances in higher-rate environments

• A substitute for clean settlement: when remittance data isn’t booking-linked and exceptions aren’t automated, “holding longer” becomes the default control mechanism

That last point is the crux: in many hospitality flows, float persists less because it’s operationally optimal and more because settlement and reconciliation aren’t designed to handle the reservation lifecycle cleanly.

If settlement is booking-linked, exceptions are first-class, and remittance is structured, you still have float (a time gap), but you don’t have to rely on float for the system to reconcile.

From float to flow: making money move correctly

One of the points in Skift’s analysis is that travel money often sits in the system long before the service is delivered. That matters, but the core issue for hospitality is not simply who benefits from holding funds.

It is about whether the industry has a settlement architecture reliable enough to move money correctly when a booking changes, completes, cancels, or becomes payable.

While float is the gap between booking and delivery when funds are collected but not yet earned, settlement infrastructure is what determines how money moves, when it moves, and what data travels with it, so terms are met predictably and reconciliation does not depend on manual work.

The goal shouldn’t be to move float between balance sheets or debate whether float should exist. The goal should be to reduce the industry’s reliance on vague, opaque, and sometimes risky holding periods by making money movement transparent, booking-linked, and reconciled by design.

That’s the difference between a model optimized around holding money and a system optimized to ensure money reaches the right party at the right time and in the right amount.

Why that matters in hospitality:

• Less operational drag: finance teams spend less time chasing folios, matching payouts, and resolving “what happened?” cases.

• Fewer disputes and cleaner exceptions: cancellations, no-shows, and post-stay adjustments become routine workflows rather than fire drills.

• Lower counterparty risk: you don’t need long, opaque holding periods as a substitute for trust.

• Better cash-flow planning: predictable settlement timing helps hotels and travel agents plan working capital.

• More choice without more complexity: you can support pay-now, pay-at-hotel, deposits, and different MoR models without breaking reconciliation each time.

• Readiness for agentic commerce: if software is going to book and change reservations at scale, settlement has to be reliable and automated, not spreadsheet-driven.

If float is valuable, why optimize for settlement?

It’s fair to point out that float can feel like a feature for whoever holds it. If you collect funds before you pay them out, you have more cash on hand and greater flexibility to scale your business. In a higher-rate environment, you may also earn yield on that balance.

However, when you rely on holding periods as your safety net, you end up mixing together three different things:

• Working capital (legitimate cash-flow needs)

• Risk buffers (fraud, disputes, non-delivery, supplier failure)

• Operational uncertainty (manual reconciliation, inconsistent folios, unclear exceptions)

Optimizing for settlement doesn’t mean eliminating float. It means making float explicit and earned, while mitigating risk, instead of accidental and opaque.

1) Float is not free capital once you price in the costs

Holding money longer can create flexibility, but it also creates overhead and exposure:

• More time for changes, cancellations, and disputes

• Higher support and exception-handling load

• More counterparty questions (and sometimes regulatory scrutiny) about where the money is and why it’s being held

2) Strong settlement replaces time with rules and data

When settlement is booking-linked and reconciled by design, you don’t need “time” to do what the infrastructure does. You can still support prepaid programs, deposits, pay-at-hotel, and various MoR setups, but holding periods are no longer the default tool for managing uncertainty.

That is also where financing can become more precise. If a travel agent (or other merchant of record) wants to extend working-capital flexibility, the answer should not be an opaque holding period hidden inside the booking flow. It should be an explicit product with clear terms.

With Katanox Capital, the economic benefit of float can be extended by an additional month through structured financing, while still providing every party with clearer settlement data, cleaner reconciliation, and better visibility into the underlying booking. This includes faster settlement and the mitigation of chargeback risk.

3) Predictability is often more valuable than duration

For most hotels and travel agents, the biggest win is not maximizing the days of float. It’s knowing exactly when funds move, what each payout maps to, and how exceptions are handled. Predictability improves forecasting and reduces end-of-month clean-up. Companies navigate uncertainty by holding funds; greater transparency and reassurance allow them to hold onto fewer funds with greater certainty.

4) If float becomes the strategy, incentives drift

When float becomes a profit center, or at the very least a capital driver, systems tend to optimize for keeping money longer instead of settling cleanly. Over time, that can damage trust, create supplier friction, and make disputes harder to unwind.

Float can exist in a healthy system, but it shouldn’t be what the system depends on.

What modern settlement architecture should look like

If hospitality is going to reduce reliance on “pay early, reconcile later,” settlement needs to be built around the reservation lifecycle and the data needed to reconcile each booking.

In practice, “good” looks like:

• Booking-linked settlement events: payment and payout occur at the right moment (for example, tied to check-in or check-out, depending on the program), not whenever a legacy rail or manual workflow allows.

• Predictable payout timing: hotels and travel agents can plan their cashflow with certainty, without ad hoc exceptions.

• Structured remittance and audit trail: payouts are linked to bookings with the data required for reconciliation, dispute handling, and compliance, so “what happened?” is answerable immediately.

• Exception handling as a first-class feature: modifications, cancellations, no-shows, and post-stay adjustments aren’t edge cases. They are expected outcomes that must be handled without breaking reconciliation.

It’s not about romanticizing or demonizing float. The focus should be on defining and implementing explicit rules that reduce the need for extended holding periods just to keep the system functioning.

What hospitality can learn from other industries

Other industries have already moved away from treating settlement as an afterthought. Marketplaces, gig-economy platforms, fintech lenders, and parts of retail have learned that faster, more certain money movement is not only a finance function. It is a product advantage.

Sellers on modern platforms increasingly expect clear payout timing, transaction-level reporting, automated exception handling, and embedded financing options. They do not want to wait weeks to find out whether a payout matched the order, whether fees were deducted correctly, or whether an FX conversion created unexpected cost.

Hospitality should be held to the same standard. Hotels, travel agents, and platforms need infrastructure that reduces risk, cost, and uncertainty, especially when transactions cross currencies, jurisdictions, intermediaries, and settlement models.

Navigating FX should not require manual workarounds or opaque spreads. It should be part of a predictable funds-flow design. Hospitality’s financial system is being left behind and needs to modernize to keep up with an evolving world economy.

The agentic future: AI will stress-test the transaction layer

Skift’s most important forward-looking point may be that AI agents are about to probe the edges of the transaction layer. This is the moment after a recommendation, when an action must be executed.

There are multiple plausible scenarios (summarized in the Skift piece):

• AI agents remain a referral layer, and hotel payments continue to flow through today’s rails.

• AI agents become the merchant of record for hotel bookings, shifting float to new balance sheets with different norms and liquidity coverage.

• Booking windows compress through last-minute optimization, shrinking float duration for lodging.

• Pay-at-service becomes more common (“book now, pay at check-in”), reducing float but increasing the need for alternative supplier financing in hospitality.

It’s difficult to predict which arrives first. But across all scenarios, one conclusion becomes clearer:

The differentiator is shifting from who can capture travelers' attention to whoever can execute transactions.

In an agentic world, financial plumbing is no longer just back office. It becomes product: booking, payment, settlement, reconciliation, and exception handling, securely and at scale.

Where Katanox fits

Katanox is built around a simple premise: settlement should be booking-linked and reconciled by design, not an afterthought patched together with multiple payment methods and manual finance ops.

That translates into practical outcomes:

• Less reliance on commingled “booking money” as working capital by creating clearer, lifecycle-linked settlement moments and rules.

• Clear funds-flow design and compliance posture, with clear roles and obligations.

• Operational controls that function like financial infrastructure discipline, such as traceability, a booking-level audit trail, structured data for reconciliation, and scalable exception handling.

• A settlement layer that can reduce legacy payment friction and cost, so both hotels and travel agents spend less time chasing and more time executing.

• Faster, safer, cheaper access to payouts and commissions, so properties and travel agents can receive funds sooner, with stronger controls, lower operational cost, and less uncertainty around cross-border payments and FX.

• Clear accounting ensures oversight of all money moved, making it easy to trace every transaction, maintain transparency, and stay compliant.

Systems should be built to minimize uncertainty so that money can move accurately, transparently, and predictably across a fragmented hospitality landscape.