Financial Protection Data

Financial protection evidence that follows the booking.

Connect payment, refund, settlement and departure data so protected-funds, ATOL, trust and finance reporting can be explained from the booking up.

ATOLreporting evidence
Trustprotected-funds context
Auditbooking-level drilldown

Protection evidence from real booking movements

Booking root
Customer payment to reporting line
BK-24018 · Departure 14 Sep · ATOL protected
£8,420Booking value
BKBooking

Booking

Travel date, lead passenger and package details

Connected
PYPayment

Payment

Customer payment matched to booking and channel

Connected
STSettlement

Settlement

Acquirer settlement and fees visible

Connected
PFProtected funds

Protected funds

Protected amount held until travel date

Connected
ATATOL

ATOL

Report line traceable back to booking movements

Connected
Explainability

Protection evidence from real booking movements

Customer money, departure dates, refunds, supplier payments and settlement records can be viewed around the booking so finance teams can evidence protected funds with less manual work.

CASHWhat has been received, settled and made available.
PROTECTEDWhat is held or restricted until travel.
REPORTINGWhat supports ATOL, APC, trust or audit reporting.

The job is proving what sits behind the number.

Travel finance teams need more than a payment total. They need to understand what money relates to which customer, trip, departure and obligation.

01

Reduce spreadsheet dependency

Give teams a clearer operating view before data is exported and reshaped by hand.

02

Drill into evidence

Move from a summary figure back to the booking, customer and payment movements behind it.

03

Support better reviews

Make internal finance, trustee, bond provider or ATOL conversations easier to evidence.

Designed around booking movement, not just transactions.

Payments only make sense in travel when they are joined to the booking lifecycle.

01

Payment timing

Deposits, balances and staged payments are seen in the context of the travel date and booking state. Money paid early sits differently against protected-funds rules than money paid close to departure — felloh keeps that timing visible at the booking level rather than aggregated into a single figure.

Deposit Early
Balance Pre-travel
Timing Booking-aware
See how we structure payment plans
02

Refund visibility

Refunds and adjustments do not disappear from the trail. Each refund stays linked to the customer payment it relates to, the booking it changes and the protected-funds split it affects — so finance can see the net position without rebuilding the picture from acquirer exports.

Refunds Linked
Adjustments Logged
Net position Live
See how we tighten financial control
03

Settlement clarity

Acquirer settlements are broken back into the bookings, fees, refunds and chargebacks behind them. Finance knows what landed, what was deducted and what still needs investigation — without manually unpacking bulk payouts each week.

Settlement Unpacked
Fees Visible
Exceptions Surfaced
See how we streamline financial operations
04

Reporting drill-down

When a trustee, ATOL, APC or insurer report shows a number, the underlying booking-level activity behind it can be drilled into without exporting workbooks. The evidence trail is the same record finance uses operationally — not a separate reporting snapshot rebuilt at month-end.

ATOL · APC Drill-down
Trustee Booking-attached
Evidence One record
See how we simplify compliance reporting

Make protected-funds evidence easier to prove.

See how booking-level payment data can support ATOL, trust and internal finance reporting.