Skip to content
Blog

Business travel booking software providers: what to test

Tekravel Editorial
Written with the help of AI

The shortlist is three business travel booking software providers, and the demos went the way demos go. Each one opened on a search box, typed a route, returned a tidy list and ended on a confirmation page. By the third you could not have said which was which. So the company picks the one with the cleanest screen, and the first real problem arrives six weeks later: a trip that was changed twice, a card statement that matches neither version, and a finance lead asking which booking the invoice actually refers to.

Search is the part every provider has solved well enough. What separates them sits after the confirmation page, in the weeks nobody demos. That is where this piece spends its time.

The trip is a record, not an event

A booking is not a moment. It is a record that gets edited: the date moves, a passenger is swapped, a hotel night is dropped, a ticket is reissued. Ask any provider to change a booked trip live, in front of you, and then show you what the record looks like afterwards. You want one record with a history, not the original booking plus a loose note that something happened. If the change creates a second, unlinked entry, your month-end reconciliation is a spreadsheet and always will be.

Who may book, and for whom

Most small companies start with one shared login and a spoken rule about who is allowed to use it. That works until the second person leaves. What you want is individual access with roles: someone who can book for themselves, someone who can book for the team, someone who can see everything and change nothing.

This platform gives each tenant its own admin panel with role-based staff permissions, its own bookings, customers and reports, and a storefront can require sign-in before anyone searches at all. Business customers register as such, with optional manual verification before they can transact. That is the extent of what we claim here. Approval chains and cost-centre tagging are not part of this description, and a provider who says yes to them should be asked to show the screen. The neighbouring pieces on what a business account changes and on team permissions go further into the access side; this one is about the whole evaluation.

What to test, and what it costs when it fails

Property to testA good answer looks likeWhen it is missing
Changed or cancelled tripOne record with a visible historyTwo entries that finance has to match by hand
How the company paysA credit limit and a settlement invoice, or a card per trip, chosen by youPersonal cards and expense claims that arrive late
Staff accessRoles, and a leaver loses access the day they leaveA login that outlives the contract
ReportingA report you can cut by traveller and by periodSomeone exports everything and filters it in a spreadsheet
After-hours troubleA named route to a person, in writingA ticket queue while the traveller is stuck

Read the right-hand column as a bill. Every row is a task that lands on a person in your company the moment the software does not do it. None of them are dramatic. All of them recur monthly.

Paying: card, or an account that settles

Two models exist and a company should pick one deliberately. Paying by card per trip is simple and puts the cash out immediately, with receipts to gather afterwards. Paying against a credit limit with a periodic settlement invoice means one document to approve, and one payment, for many trips. Credit limits and settlement invoicing exist here as concepts in the product, not as a spreadsheet kept by an accountant. If a provider can only describe the card route, ask what happens when your finance team refuses to chase thirty small receipts.

The leaver test

Add a made-up employee to the system, give them a booking, then remove them. Watch what happens. Does the booking stay attached to a record the company owns? Does their login stop? Is there a trail showing who removed them and when? It takes five minutes and most providers have never been asked to do it in a demo.

Questions to put in writing

Spoken answers evaporate. Send these by message and keep the replies:

  • Show a trip that was changed after booking, and show me the single record it ends up as.
  • How does our company pay, and what document do we receive?
  • What happens to a staff account the day someone leaves, and where is that visible?
  • What can I cut a report by, and can I export it?
  • Who do I contact at midnight, and in what language?

An honest answer is specific. "Yes, fully supported" is not an answer. "Here is the screen, and here is the part we do not cover" is, and it is worth more than a longer feature list.

What this platform does and does not claim

Flights, hotels, tour packages and attractions are switched on per tenant, so a company only sees the services it uses. Staff work inside role-based permissions in their own admin. Credit limits and settlement invoices are first-class. Nothing in this piece quotes a price, a saving or a response time, and we will not make that up for you. If you want to see how a setup would map to your team, the contact page is the place to start a conversation.

Run the demo yourself

Ask for a sandbox login, or at least for the mouse. A salesperson drives a demo along the path that works. You need to drive it along the path your company actually takes: the traveller who has to leave a day early, the colleague booking for a manager, the hotel night someone forgets to cancel. Write three such scenarios down before the call and refuse to leave until each has been done on screen. Two are usually fine. The third is where the provider goes quiet, and that quiet is the whole result of the evaluation.

Keep the scenarios identical across all three providers, and score them the same way afterwards. It is dull work and it beats any feature matrix.

The cost of choosing on the demo

The failure looks ordinary. Someone books on a personal card because the portal was awkward, and the trip never appears in company reporting. A contractor's login survives the end of their contract. A month closes with an unreconciled invoice and one person who remembers how it was meant to match. Individually survivable, together a quiet tax on the finance team, paid in hours. The software that avoids it rarely looks different in a demo. It looks different in week six.

Tekravel Editorial

Travel technology desk

The Tekravel travel-technology desk writes for the trade: agency owners, consolidators and the developers who integrate them. Every article is checked against the platform it describes before it is published.