Customer money stays customer money.

The trust ledger

Every trust-flagged payment writes a row to trust_ledger, tagged with the source booking, the supplier liability it offsets, and a reservation period. The ledger is append-only; balances are computed by direction (debit/credit) rollup.

Jurisdiction-aware release rules

The platform ships with rule sets for:

• GB-ATOL — Air Travel Organiser's Licence (UK CAA)
• AU-TCF — Travel Compensation Fund framework (Australia)
• US-CARF — Consumer Airline Refund framework (USA)
• NONE — for jurisdictions without statutory trust requirements

Each rule set defines what events permit a release: confirmed travel completion, supplier remittance, refund, or an explicit override with mandatory comment and second-step approval.

Daily reconciliation

A nightly cron compares SUM(trust_ledger.amount × direction) per bank account against bank_accounts.current_balance. Any variance beyond tolerance raises a row in trust_breach_alerts with severity and message. Alerts are visible on the trust page and are not auto-cleared.

Client money reporting

Quarterly or on-demand reports show: total trust held, per-currency breakdown, per-booking liability, per-supplier earmark, oldest unreleased reservation. Exportable for regulator submission.

What you get

• Bank-account-level trust segregation enforced in schema
• Append-only trust ledger with reservation periods
• Per-jurisdiction trust release rules
• Daily reconciliation cron with breach alerts
• Client money reporting suitable for regulator submission
• Prevents agency-funded premature refunds
• Auditable override workflow when business circumstances require

Discuss your jurisdiction