Platform / How it works

One record of every pound, from payment to proof

felloh captures the payment with the booking reference attached, confirms the money against the bank and the acquirer, and keeps the whole trail auditable — for your accounts, the CAA and your bond provider.

FIG. 01 — One record of every pound, from payment to proof.

The money trail,
step by step.

// 01 — How it works
01

Capture

The customer pays by card, open banking or bank transfer through a payment link or checkout that already carries the booking reference. Apple Pay and Google Pay are supported at organisation level.

Methods — Card · Open banking · TransferReference — Attached at capture
02

Match

Because the reference travels with the payment, allocation is automatic — no bulk settlement broken down by hand, no manually typed references to mistype.

Allocation — AutomaticExceptions — Surfaced, not buried
03

Verify

The bank feed and the acquirer's settlement file confirm the money actually moved. Where the three sources disagree — a changed booking, a missed add-on, a mistyped reference — the mismatch shows as an exception with the evidence attached.

Sources — Bank · Acquirer · BookingSettlement data — Backfilled on connect
04

Sync

Reconciled movements flow to the systems that consume them — payment status back to the booking workflow, postings to Xero or Sage, the live picture to the dashboard.

Writes back — Booking statusAccounts — Xero · Sage
05

Report

The ATOL/APC return, bond-provider evidence and the audit trail all read from the same record. The quarter's filing is the current state of the ledger, not a reconstruction of it.

ATOL / APC — From live dataAudit — Figure → movement → source

Auditable back to the source.

// 02 — The drill-down

Any figure on any report opens into the movements that produced it, and every movement carries its source evidence — the booking reference, the bank line, the acquirer settlement line.

One record, every sceptic
can check.

// 03 — Who relies on it
Accounts

Your accountant

Reconciled movements post to Xero or Sage with the booking context attached. Month-end starts reconciled instead of starting with a download.

Regulator

The CAA

The ATOL/APC return reads from live booking-level data — changed bookings and add-ons are caught as they happen, not reconstructed at quarter-end.

Protection

Your bond provider

Evidence of protected funds sits on the same record as the underlying payments, so bond and insurance questions get answered from the ledger, not from a file of exports.

Assurance

Trustees & auditors

Every summary figure drills down to the movement and the source behind it — the bank line and the acquirer settlement, not someone's working file.

Retire the rebuild.

// 04 — What it replaces
Checking the bank several times a day, keying transfers in by handBank payments surface and match themselvesManualAutomatic
Bulk settlements allocated across bookings by handPayments arrive already matched to the bookingManualAutomatic
The ATOL model that lives in one person's spreadsheetThe return is a report anyone on the team can runKey-person riskShared
Quarter-end, line by line against working filesThe quarter locks when the exceptions clearRebuildReport

Questions on how it works.

// 05 — FAQ

Where does felloh get its data?

From the places the money actually moves: payment links and checkouts carrying the booking reference, open-banking bank feeds, the acquirer's settlement files, and the booking system's references and booking changes.

Does felloh change our acquirer or our rates?

No. felloh sits in front as the operating layer: your existing acquiring arrangements and rates stay as they are, and felloh reads the settlement evidence those providers already produce.

How far back does the evidence go?

Settlement data is backfilled for prior transactions when you connect, so the booking-level trail is complete from day one rather than starting empty.

Bring us one booking.

Bring us one booking, payment workflow or reporting problem. We will trace its money trail live — from the customer's payment to the return it lands on.

Book a walkthrough