Payment scheduling

Why it matters in travel

Travel booking lifecycles are long enough that almost every customer payment story has a scheduled component. Tour bookings made nine months before departure carry a balance schedule. Group and school travel bookings carry per-payer instalment schedules. Cruise bookings carry a low-deposit-large-balance schedule tied to the cruise-line cancellation curve. Without scheduling, finance and operations spend significant time chasing payments by hand, and a missed balance can cascade into supplier-side problems.

The hidden risk in payment scheduling is the consent regime. A scheduled card payment relies on a valid tokenisation event with the right MIT (merchant-initiated transaction) framing; a scheduled open-banking payment relies on a variable-recurring-payment or future-dated payment mandate; a direct debit relies on a DDI under the BACS rules. Get the consent wrong and the customer can dispute, the issuer can decline as a soft decline at the SCA layer, or the regulator can take a view. Travel businesses that treat payment scheduling as a finance operation rather than a compliance operation tend to learn this the hard way.

Done well, payment scheduling moves work from inbox to ledger. Customers know what is happening, finance can see what is collected versus what is queued and what is overdue, and operations can plan supplier payments against expected arrivals rather than guesses. Done badly, it produces a backlog of failed schedules, manual rescheduling and customer-service queries that finance teams spend hours unpicking.

How felloh helps

felloh handles payment scheduling as a first-class part of the booking-level ledger, so each scheduled payment is attached to the booking, traveller and travel date it relates to — and finance can see at any point what is scheduled, what has been collected, what has failed and what is queued for the next attempt.

In the dashboard, Payment Plans and Scheduled Payments expose the schedule against the booking with the right consent evidence captured at setup, so the audit trail behind every scheduled charge is available without rebuilding it. Soft declines surface as actionable exceptions and retry automatically against the schedule rather than disappearing into a finance inbox. Approval links let agents capture customer consent for a new schedule without rebuilding the booking from scratch.

The practical effect for finance is that the cash-position picture stays honest. Scheduled payments show up as committed-but-not-yet-collected cash on the right side of the ledger, with the right consent evidence behind them, and reconciliation matches the schedule to the bank arrival the same way it does for any other payment.