Kasematt - Corporate Travel, Duty of Care and Expenses Console

Dashboard, trips, trip detail with 4 tabs, traveller map and finance review queue, with trip quick view, booking detail, traveller and flag detail panels.

The traveller map places people from their flight, hotel and rail bookings. Live location shows only for a traveller who opted in during an incident, and every phone number reveal is logged.

Duplicate receipts across travellers, hotels already billed centrally, per diem and meal overlaps, split receipts under the €25 threshold, blocked merchant categories and FX rate outliers, each with its evidence.

24 trips to 13 destinations from the Greater Region to the Gulf and West Africa, 18 bookings, 16 expense reports with 14 flags, 4 risk alerts, 3 incidents and 21 staff across 4 entities.

Duty of Care Without Surveillance

An employer must protect staff travelling for work, but tracking an employee's location is monitoring under Article L.261-1 of the Luxembourg Labour Code, which requires prior information to staff and the staff delegation. The design had to answer "who is in the storm area?" without tracking anyone's phone by default.

Allowances and VAT Differ by Country

Each employing entity has its own tax-free per diem and mileage rules, and each country limits which VAT is recoverable. Foreign EU VAT is reclaimed under Directive 2008/9/EC and only with an invoice in the company's name, so nothing can be assumed recoverable.

Policy Exceptions Nobody Saw

Hotel caps vary by city and grade, cabin and rail class depend on journey time, and some trips need a project director or partner to approve. Out-of-policy bookings and their reasons were invisible until the card statement arrived.

Sensitive Data in Every Trip

Ticketing needs passport numbers and dates of birth, the safety team needs phone numbers and emergency contacts, and finance needs IBANs. Under the GDPR each has its own purpose, and Mielerbach's policy is to mask them by default and log every reveal.