_HOSPITALITY/

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.

Book a demo Start building

deposit

liability

split

payout

_TRUSTED BY TEAMS MOVING MONEY/

_THE PROBLEM/

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.

_FLOW OF FUNDS/

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.

booking liability

depositguest prepays

liabilityheld until stay

splitOTA · tax · property

payoutproperty settled

_CAPABILITIES/

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.

_BOOKING LIABILITIES/

Deposits and prepayments tracked as explicit liabilities per booking, converting to revenue at stay, restated cleanly on every modification.

liability-aware

_CHANNEL SPLITS/

OTA commissions, city taxes, and platform fees declared per channel and market, applied atomically at settlement.

per-channel logic

Read the Numscript docs

_MULTI-CURRENCY/

Guest currency in, property currency out: FX conversions posted as explicit transactions with the spread accounted.

explicit FX

_PSP & OTA RECONCILIATION/

PSP settlements and OTA statements normalize and match continuously against per-booking ledger state.

per-booking matching

_BY THE NUMBERS/

Hospitality-grade, by design

money traceabilityper bookingdeposit → payout

channel splitanyOTA · direct · corporate

currency settlementmultiguest in · property out

PSP reconciliationcontinuousper booking · per property

_NUMSCRIPT/

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.

checkin.num

// Settle a prepaid booking at check-in
vars {
  account $booking
  account $property
  monetary $stay_total
}

send $stay_total (
  source = @liability:$booking
  destination = {
    15% to @ota:commission
    5% to @tax:city
    remaining to @payable:$property
  }
)

_VOICES/

Trusted 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

_TRUST/

Built for regulated money.

Enterprise controls, the certifications auditors ask for, and an immutable record, out of the box.

See our trust center

THE COMPLIANCE STACK

IAM, RBAC & SSO

Non-repudiation

Audit logs

Observability & monitoring

Real-time events

Admin console

_AUDIT-LOG/ NON-REPUDIATION

09:41:07Z AUDIT gateway POST /api/ledger/v2/main/transactions 200 sub:ops@acme.io

09:41:09Z LOG id:4093 NEW_TRANSACTION ledger:main

09:41:12Z LOG id:4094 SET_METADATA ledger:main

09:41:15Z LOG id:4095 REVERTED_TRANSACTION ledger:main

09:41:18Z AUDIT gateway GET /api/ledger/v2/main/logs 200 sub:audit@acme.io

CERTIFICATIONS

AICPA SOC IICERTIFIED

ISO 27001CERTIFIED

DORACOMPLIANT

REGULATORY FRAMEWORKS

EMIFCAMTLNYDFS Trust CharterOCC CharterMiCAGENIUS

_ATTESTED/

_RESOURCES/

Keep going

Everything you need to evaluate and build on Formance.

_DOCS/

Read the documentation

Architecture guides, the Ledger and Connectivity references, and step-by-step quickstarts to ship in days.

_NUMSCRIPT/

Try Numscript

Model any flow of funds as deterministic, auditable transactions. Experiment live in the playground.

_STORIES/

Customer stories

See how fintechs, marketplaces and platforms run money movement on Formance in production.

FAQ

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.

_GET STARTED/

Money flows as smooth as check-in

See how Formance fits your hospitality platform: book a demo or start building.

Book a demo Start building