Adrasis™

Payments

Booking money flow

Booking money flow shows receipts, supplier payments, refunds and adjustments for one booking. For example, review a 720 EUR guest receipt and 580 EUR reserved for the supplier in the same view, with their current status.

What the view contains

The money-flow tab on a booking shows:

  • Movements timeline. Each row is one financial event tied to the booking, a traveller payment that posted, a virtual-card issuance still held against an upcoming supplier payout, a refund that reversed an earlier capture, a platform fee. Oldest first.
  • Per-currency summary strip. Aggregated totals grouped by currency, direction (inbound or outbound), and effect (reserved, posted, reversed). Concrete example: a 4-night booking at Hotel Sunrise in Antalya may show EUR 720 posted inbound (the traveller paid in full), EUR 580 reserved outbound (a virtual card waiting on the supplier to capture), and EUR 12 posted outbound (a booking-linked platform fee already settled).

Currency conversion context (when a movement was recorded in one currency and the booking is denominated in another) is attached to each row, so finance can always trace back why a number looks the way it does.

The three effects

Each movement carries one of three effects. Understanding them is the difference between "how much is on our books today" and "how much will be on our books once everything settles".

Effect What it means Example
Reserved The amount is committed but the money has not actually moved yet. A virtual card is issued for EUR 580; the funds are earmarked for the supplier.
Posted The money has actually moved. The traveller's EUR 720 was captured by the payment gateway and credits the operator.
Reversed A previously reserved or posted amount was undone. An unused virtual card's closure is confirmed and its transactions are reconciled; the reserved amount is released.

A booking can have multiple effects stacked over its lifetime, reserved at booking, posted on capture, reversed on partial refund. The timeline preserves every step so the booking's net position is auditable, not derived from the latest snapshot.

How direction works

  • Inbound, money flowing into the operator: traveller payments, refunds the operator received.
  • Outbound, money flowing out: supplier payouts, refunds to the traveller, platform fees, taxes the operator forwards.

The per-currency summary strip shows both directions side by side so any imbalance between "what the traveller paid" and "what we owe forward" is visible at a glance.

Agency collection and booking confirmation

For an instant-confirm booking at Hotel Sunrise, an agency may owe the hotel 10000 TRY and charge the guest 12000 TRY after adding 20% markup. Once the required guest payment succeeds, the reservation is confirmed. The agency's 12000 TRY receipt and the hotel's unpaid 10000 TRY receivable remain separate. The later supplier payment follows the commercial agreement.

Guest confirmation does not wait for supplier settlement. A genuine request-to-book still requires the property's acceptance. A cancelled or expired reservation is not reopened by a late payment.

What changes a booking's money flow

Several operator actions write to the booking's money flow:

  • The booking is finalized. If the cancellation policy charges anything at booking time, that posted amount lands here.
  • The traveller captures a payment. A traveller-side prepayment posts inbound.
  • A card hold is captured. A hold on the guest's card adds no movement, because no money has moved. Capturing it posts the captured amount inbound; releasing it adds nothing. See Card payments and payment links.
  • A recorded payment is corrected. A correction of a payment recorded by hand posts outbound and lowers what was collected. It is not counted as a refund to the guest.
  • A virtual card is issued. Its limit is recorded as reserved outbound. Completed supplier charges are recorded separately as posted outbound and reduce the remaining reserved amount.
  • A refund is issued. Either a posted reversal (the original payment was undone) or a fresh outbound posted entry (a goodwill refund on top), depending on the cancellation policy.
  • A supplier payout settles. The completed payment is recorded as posted outbound against the payment method used. Related reserved amounts are released as they are settled or reconciled; earlier movements remain in the history.
  • A reconciliation correction is recorded. A small adjusting entry when the actual amount differs from the recorded one (see Payment-provider reconciliation).

The Console also stamps who initiated each step (which operator, which automation) so the booking carries its own audit trail.

Common operator questions answered here

  • "Did the EUR 720 from this traveller actually arrive, or is the booking still pending payment?", Filter for inbound + posted on the row's currency.
  • "What do we still owe the supplier on this booking?", Filter for outbound + reserved.
  • "Why does the booking total say EUR 720 but the summary shows EUR 712 posted inbound?", The 8 EUR delta is visible as a separate movement (typically a payment gateway spread; see Payment-provider reconciliation).
  • "This booking was modified twice, what is the current net amount to the supplier?", The summary strip nets the reserved + posted + reversed entries.

What this view does not include

  • Organization subscription. The platform subscription has its own USD base and commercial agreement. A platform-fee movement on a booking records that booking's fee; it does not represent the organization's monthly or annual subscription payment.
  • Organization-wide cash position. The booking money-flow page is scoped to one reservation; the per-currency available balance across all bookings lives on the Cash position page.
  • Period reports across multiple bookings. Filtering and exporting financial events across a date range is the Financial period report job.
  • Supplier-level history. The separate supplier history report collects movements across bookings for a supplier reference and date range. See Supplier payouts.

Where to next