Every booking, every party, every currency — balanced
Deposits, OTA commissions, city taxes, no-show fees, and property payouts: one ledger for the money side of every stay.
A booking is a payment plan with five stakeholders
Deposits, modifications, and multi-party splits stress-test any payment stack.
A stay collects a deposit months ahead, modifies twice, splits across the OTA, the property, and the tax office, and might refund in another currency. PMS data, PSP events, and bank statements each tell a different story.
Deposits and prepayments sit as liabilities nobody tracks until check-in.
OTA commissions, city taxes, and platform fees split differently per channel and market.
Modifications, no-shows, and cancellations restate money already collected.
Multi-currency guests and properties make reconciliation a monthly forensic exercise.
_PROOF/ Hospitality platforms run booking-to-payout flows on Formance across properties and currencies.
From booking to property payout
Collected as a liability, earned at stay, split at settlement.
The deposit posts as a guest liability, check-in converts it to earned revenue through the channel's split (commission, taxes, property share), and the property payout pays the derived balance, in its currency.
See hospitality payments on a live ledger.
Access a demo of a hospitality payments flow of funds, on a live Formance ledger. Follow the flow step by step, and deploy the schema to your sandbox.
The primitives hospitality platforms need
Built on the open-source Formance ledger.
Liability-aware booking flows, per-channel splits, and multi-currency settlement, composed for stays at scale.
Deposits and prepayments tracked as explicit liabilities per booking, converting to revenue at stay, restated cleanly on every modification.
liability-aware
OTA commissions, city taxes, and platform fees declared per channel and market, applied atomically at settlement.
per-channel logic
Read the Numscript docsGuest currency in, property currency out: FX conversions posted as explicit transactions with the spread accounted.
explicit FX
PSP settlements and OTA statements normalize and match continuously against per-booking ledger state.
per-booking matching
Hospitality-grade, by design
Check-in settles the booking
Liability becomes revenue, split across every party.
At check-in, one Numscript transaction converts the guest's prepaid liability through the channel split (OTA commission, city tax, and the property's payable), atomically.
Try it in the PlaygroundTrusted by builders
“Formance enabled us to ship new lending products faster by providing a customizable foundation that let us reliably express the complexities of our flow of funds.”
Embedded finance · reconciliation across 14 countries
See customer story
“Formance is the foundation of our Financial OS, the open-source approach lets us retain control over this key component.”
Healthcare · Financial OS
“Formance helped us kick off our move into fintech, with robust infrastructure and intuitive developer tooling.”
Benefits · fintech infrastructure
Keep going
Everything you need to evaluate and build on Formance.
Hospitality flows, answered
01 / HOW ARE MODIFICATIONS AND CANCELLATIONS HANDLED?
Each modification posts as a restating transaction against the booking's liability: partial refunds, date changes, and no-show fees keep a complete history.
02 / CAN SPLITS DIFFER PER CHANNEL AND MARKET?
Yes: OTA terms, tax rates, and platform fees are declared per channel and market, so a new OTA contract or city tax is configuration, not code.
03 / HOW DOES MULTI-CURRENCY SETTLEMENT WORK?
The guest pays in their currency, the property settles in its own, and the conversion posts explicitly with its rate and spread; both sides reconcile in their books.
04 / CAN PROPERTIES SEE THEIR POSITION?
Yes: per-property payables derive in real time from stays, refunds, and adjustments, so owner statements come from the ledger, not a spreadsheet export.
Money flows as smooth as check-in
See how Formance fits your hospitality platform: book a demo or start building.