One trip for the traveller.Five records for finance.
A train ticket, a parking session, a tank of fuel. For the traveller it is one moment. Behind it sit a booking, a payment provider, the partner who delivered the trip, a bank and a ledger. Each has its own logic and its own timing.
“Every system holds part of the truth. None of them hold the whole story.”
Press the button to put the five records back together.
Illustrative trip and amounts, not a customer record.
Three ways to move
Rail, parking and fuel cards. Three transaction shapes, one problem.
Order
Payment
Refund
Settlement
Tax per country
Ledger
Meter or app
Several PSPs
Parking partner
Own backend
New country
Ledger
Authorisation
Supplier invoice
Client invoice
Oracle invoicing
Twinfield
A · Rail and travel · Interrail
Millions of orders, each with its own refund, settlement and tax rule.
By 2024 Interrail was processing millions of transactions a year. Reconciliation lived in Excel and took weeks at month end. It was hard to tell whether an issue was a one-off or a pattern across thousands of orders.
“Differences stopped hiding inside totals and became visible immediately.”
Several payment providers, parking partners and countries, one backend.
With Actuals, each payment is verified and matched against Flowbird’s own backend. Operations and finance see the non-matching transactions every day, and a new country does not need workarounds or extra headcount.
“Without Actuals, reconciliation would be extremely labour-intensive and simply not scalable.”
Fuel, EV charging and public transport on one card, matched to every supplier invoice.
Millions of mobility transactions a month, followed from authorisation to invoice. With Actuals between Oracle invoicing and Twinfield, all transaction data has one source of truth.
“We use Actuals to track all transactions from initiation to our general ledger, ensuring they match with supplier invoices and remain balanced. A paradigm shift to be in control.”
Keep scrolling to switch from rail to parking to fuel cards.
Exceptions, not everything
Stop reviewing every transaction. Handle the few that break.
“The focus shifted from reviewing every transaction to proactively handling exceptions as they arose.”
From the MultiTankCard case, about working with Actuals
With Actuals, Interrail saw issues surface early, audits got easier and month end grew calmer. At Flowbird, the output of Actuals triggers alerts when payments fail.
Switch to Exceptions only, then open one to see what it is.
The same supplier transactions appear on two invoices. With Actuals, MultiTankCard found double invoicing early this way, before it was paid.
A supplier charged it, but it never reached a client invoice. MultiTankCard identified unclaimed supplier transactions by working from the exceptions in Actuals.
At Flowbird the output of Actuals triggers an alert when a payment fails, so operations can act on the day, not at month end.
Illustrative list. The kinds of exception come from the MultiTankCard and Flowbird cases.
From the customer files
Three operators, one live conversation. Each one closes on its own data.