Skip to content
Blog

What a corporate travel booking account actually changes

Tekravel Editorial
Written with the help of AI

It is the third working day of the month and someone in finance is reconciling travel. There are fourteen confirmation emails forwarded from eleven inboxes, three personal credit cards, a hotel folio in a currency nobody expected, and one flight to Riyadh that appears twice — once booked by the traveller, once by their assistant, both refunded, at different rates. Nobody did anything wrong. The company simply never had one place where its trips lived.

That is the problem a corporate travel booking account is meant to fix, and it is worth being precise about what it changes, because a shared login to a booking site is not the same thing. A shared login gives everyone the same password. An account gives the company a record.

One record per trip, instead of a pile of personal confirmations

When staff book on their own, each booking belongs to the person who made it. The confirmation goes to their email, the ticket carries their payment, the change history sits in their account. If they are on leave when the airline moves the flight, the company finds out from the traveller at the airport.

Under a business account the booking belongs to the company and is attached to the traveller. That sounds like a filing detail. In practice it decides three things: who can see the trip, who can change it, and who gets the schedule-change message at two in the morning. It also means the booking reference — the PNR, in airline terms — is somewhere the office can find it without asking anyone to search their inbox.

The useful test, whatever provider you are looking at, is to ask them to show you one trip for one traveller and everything attached to it: the ticket, the hotel, the payment, the invoice line, every change since. If that takes four screens and an email, it is not one record.

Who can book for whom, and who has to say yes

This is where most companies get the design wrong, usually by making it either too loose or so tight that people go back to booking on their own cards.

There are really three roles to separate. The traveller, who is the name on the ticket. The booker, who may be the traveller, an assistant, or an office manager booking for a whole team. And the approver, who signs off on the cost before it is committed. A five-person company might have all three in one person. A company sending a sales team to Dubai every month should not.

Questions worth answering before you set anything up:

  • Can an assistant book for named colleagues only, or for anyone in the company?
  • Does a booking above a certain amount, or in a certain cabin, need someone else's approval — and what happens to the fare while it waits? Airline fares are not held indefinitely, and an approval step that takes two days can cost more than the saving it was meant to protect.
  • Can the approver see the options the booker turned down, or only the one they picked?
  • Who can cancel? Cancelling is where money is lost fastest.

Booking systems do not all handle approvals the same way, and some do not handle them at all; in that case the agency running your account may enforce them by process instead — a call, an email, a named person who confirms. Ask which it is. Both can work. What does not work is assuming there is a control when there is not one.

Central settlement instead of expense claims

The financial change is the one finance teams notice first. With staff paying personally, every trip produces an expense claim, a receipt that may or may not match it, a reimbursement, and a card statement in somebody else's name. With a business account, the company is billed directly — either it pays at booking with a company card, or it books against a credit line and settles against an invoice.

The second model is the one that removes the paperwork, and it helps to know how it works on the provider's side. On booking systems built for the trade, a business customer can be given a credit limit, and each booking draws it down until the company settles. Settlement invoicing — one invoice covering a period's bookings rather than a receipt per ticket — is a built-in part of such systems, not a spreadsheet someone keeps next to them.

Staff book and claimBusiness account, company cardBusiness account on credit
Who pays at bookingThe travellerThe companyNobody yet — it is drawn against the limit
What finance receivesA claim per trip, receipts attachedCard lines plus booking confirmationsOne settlement invoice per period
Where it goes wrongMissing receipts; staff out of pocket for weeksCard limit hit mid-trip; matching card lines to bookingsLimit set too low and bookings stop; settlement paid late
Who it suitsA handful of trips a yearRegular travel, companies that prefer not to take supplier creditFrequent travel and a finance team that settles on schedule

You can disagree with the last row. Some companies that travel heavily stay on cards on purpose, because they do not want a supplier holding a credit relationship with them. That is a reasonable choice. The point is to make it, rather than drift into the first column because nobody set up the third.

What getting this wrong actually costs

Rarely a disaster. Usually a slow leak.

The duplicate booking that was refunded at a lower rate than it was paid. The non-refundable hotel nobody cancelled because nobody knew the meeting had moved. The traveller who paid a change fee on their own card at the airport counter and claimed it three months later, after the budget was closed. The employee who left the company with the airline login their trips were booked under. And the cost nobody puts on a report: finance staff spending the first days of every month matching emails to card lines instead of doing their actual job.

The opposite failure is over-control. An approval chain that holds a booking until the fare has gone up, or a policy so narrow that half the trips need an exception, sends people straight back to their own cards. Then you have the account and the expense claims, which is worse than either on its own.

What to have ready before opening a corporate travel booking account

Opening one is usually quick. On most trade booking sites a business customer registers online and the agency may check the company by hand before it can book. What takes time is the information you are asked for — and the decisions behind it, which are yours, not the provider's.

  1. Company registration details exactly as they should appear on invoices, plus the tax number if your invoices need to carry one.
  2. A list of travellers with names spelt as they are in their passports. A misspelt name on a ticket means a change fee, or a new ticket.
  3. Who books for whom. Write it as a list of names, not as a principle.
  4. Approval rules, if you want any, and the person who covers when the approver is the one travelling.
  5. The payment model — company card or credit — and, if credit, the limit you actually need, which is set by your busiest month of travel, not your average one.
  6. The invoice contact in finance, and the currency you want to be billed in.
  7. The out-of-hours contact on the provider's side. Ask for it before you need it, not at the gate.

If a provider cannot tell you how each of these is handled, that tells you most of what you need to know about the account.

More and more agencies that look after companies take these bookings on their own booking site, with business sign-in and credit handled there, rather than by email and phone. Some of them run it on a platform like ours; the corporate side of it is described here. If you are the agency, weighing whether to offer business accounts to your own corporate clients, that conversation starts with our team.

Either way, the test is the one from the start: one trip, one traveller, one record. Everything else on the account is there to keep it that way.

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.