Data Panda brings your TravelPerk data together with the data from the rest of your business. From one place, we turn it into dashboards, automations, AI workflows and custom apps your finance, HR and operations teams use every day.
TravelPerk was founded in Barcelona in 2015 by Avi Meir, Javier Suarez and Ron Levin, with Meir bringing a Booking.com background to the corporate-travel market. The company raised more than 700 million dollars across seven rounds and rebranded to Perk in 2025 after the Yokoy acquisition broadened the product into wider spend management. Most customers still know the platform under the TravelPerk name, and the connector is built on the same data model.
For finance, HR and operations leaders, TravelPerk is the system of record for almost everything attached to a business trip: trip requests and approvals, flight, hotel, train and car bookings, traveller profiles and loyalty numbers, cost centres and project codes, travel-policy rules and the breaches against them, FlexiPerk cancellation events, invoices and credit notes. The built-in dashboards answer the obvious questions. The harder ones, like which department is paying the last-minute booking premium, what FlexiPerk saves against what it costs, or how travel spend lands per project in the GL, sit across TravelPerk and the systems around it. Pulling TravelPerk into a warehouse is how those answers stop being a quarterly export the finance controller stitches by hand.
Spend per cost centre, project and traveller in one place, with policy and lead time attached.
Turn TravelPerk trips and invoices into the postings and pings your team would otherwise do by hand.
Use trip, policy and booking history to score risk and forecast travel demand.
Small finance and HR tools that sit on TravelPerk data instead of another tab.
A list of concrete reports, automations and AI features we have built on TravelPerk data. Pick the one that matches your situation.
What does our last-minute booking premium cost us per quarter?
Average ticket price for trips booked inside seven days against the same routes booked four weeks out, multiplied by the volume of late bookings per business unit. The number tells the COO whether to push for earlier trip approval cycles or to budget the premium where it keeps recurring.
Which departments are quietly bypassing the travel policy?
Out-of-policy booking rate per cost centre and per booker, with the policy rule that was breached attached. Finance sees which team's exception list has become the rule, and HR or the team lead has a concrete conversation instead of a quarterly reminder email.
Is the FlexiPerk premium paying for itself?
Refunds recovered through FlexiPerk against the premium paid for it, split per booker and per department. The teams that book and rarely cancel show negative ROI on FlexiPerk; the ones with last-minute schedule changes get a defensible case to keep paying for it.
Travel spend allocated to cost centre and project before invoicing, FlexiPerk premium booked as the cost line it is, and last-minute booking impact visible per business unit. Month-end no longer needs a TravelPerk PDF reconciled against the GL by hand.
Travel spend per account executive set against the pipeline they cover, so client-visit budget is steered by what closed and not by who shouted loudest in QBR. Top-revenue accounts get a visible travel envelope, not a one-off approval thread.
Duty-of-care view of who is travelling where this week, plus the contact and policy data attached to each trip. When a strike or weather event hits a city, ops knows in minutes who needs rebooking instead of asking around.
TravelPerk invoices and credit notes land in Exact Online as the right journal entries, split by traveller, cost centre and project code. The travel category in the GL no longer needs a controller to recode each line manually after a PDF download.
Trip cost from TravelPerk lands on the Business Central project the trip belongs to, with the right job task and category. Project managers see real travel cost on their job card before month-end, instead of a billable surprise the controller flags weeks later.
Sales trips booked in TravelPerk are matched to HubSpot companies and open deals on traveller and destination. Cost-of-sale per account becomes a real number, and the deals where the AE flew out three times without a closed-won show up next to the deals that closed on email.
New hires in BambooHR get a TravelPerk profile with the right cost centre, manager and travel-policy group on day one, and leavers are deactivated when their BambooHR record closes. No more orphan accounts booking flights against a department that no longer employs the traveller.
These are the 8 tables we currently pull from TravelPerk into your warehouse. Query them directly in SQL, join them to the rest of your stack, or build reports on top.
Missing a table you need? We can extend the sync. Tell us what is missing and we will build it for you.
You keep the reporting tool you already have. We connect it to the warehouse where your TravelPerk data lives.
OAuth authentication. Read-only by default. We sign a DPA and your admin keeps the keys.
Data flows into your warehouse on your schedule. Near real time or nightly, your call. You own the data.
We build the first dashboard, workflow or AI feature with you, then hand over the keys. Or we stay on for ongoing delivery.
We set up the foundation. Your team builds on top.
Best fit Teams that already have a BI analyst or data engineer and want to own the build.
We build the whole thing, end to end.
Best fit Teams without in-house BI or dev capacity. You tell us what you need and we deliver it.
You do. It lands in your warehouse, on your cloud account. We don't resell or aggregate it. If you stop working with us, the warehouse stays yours and keeps running.
Near real time for most operational systems. For heavier sources we schedule hourly or nightly. You pick based on what the reports need.
No. If you don't have one, we help you pick one and set it up as part of the first delivery. Common starting points are Snowflake, Microsoft Fabric, or a small Postgres start.
Yes. The cost-centre, project-code and policy-group attributes on every trip and traveller are first-class fields in the warehouse. Travel spend can be sliced by the same dimensions finance already uses in the GL, without a manual lookup table.
FlexiPerk-eligible bookings, the premium charged on them and any refund collected after a cancellation come across as their own events linked to the trip. The savings calculation is the recovered refund minus the premium paid, ready to roll up per department or per booker.
Yes. The product, API and underlying data model continued under the Perk brand after the rebrand and the Yokoy acquisition. We track the connector under the slug travelperk because that is what most customers and the Peliqan catalog still use, and the schema in your warehouse is the same either way.
We review your TravelPerk setup and the systems around it. Together we pick the first thing worth building.