Multi-city business travel: how to turn five requests into just one

Let’s say your head of sales is heading out on a three-day trip; she first flies from London to Berlin on Tuesday to meet a prospective client. Then on Wednesday, she flies to Warsaw for a partner review, heading home on Thursday.

Although it’s a single trip for her, when you break it down, it’s five separate items: three flights and two hotel bookings.

And each item can turn into its own request, which then needs its own approval; then when bookings arrive, they need their own payments and invoices. So when she returns, finance has five separate records to match to one business purpose.

The trip itself isn’t the problem; it’s the extra admin that comes with multi-city business travel. We’re exploring this common issue below and showing you what a better setup can look like.

What multi-city business travel looks like today

Multi-city business travel is any trip with more than one destination before the traveller comes home. For any UK organisation with customers, entities, or partners across Europe, it’s a typical work trip.

These are the trips that carry significant commercial weight, i.e. they’re typically built around important events like revenue meetings and entity-level decisions. So one slow approval can have a direct financial impact on the business.

Europe is perfectly set up for these trips; with dense route networks and short flight times, the same person can cover a few cities in one trip while mixing airlines.

That’s where the multiplication starts. Many travel tools treat each booking as the unit of work, so each booking becomes its own request, invoice, and approval. Which means one trip has five items moving through the process separately.

What five requests cost your team

The cost comes from the process's fragmentation. Every extra request adds a handoff, and in multi-city business travel, they stack up fast. And the impact can land differently on each person involved in the process.

Approvers only see one leg at a time. A Berlin-to-Warsaw flight can look expensive on its own. However, next to the full itinerary, it can mean the difference between coming in over budget or under. Crucially, that approver lacks the context, which can lead to waving items through or holding them up with questions.

Travel managers lose the end-to-end view. With five disconnected records, it becomes harder for the travel manager to deliver on duty of care, change management, and spend tracking. Because they simply don’t know where someone is or what is coming next.

Finance has scattered payments and invoices to reconcile. Five bookings means five transactions, and five documents to code and tie back to one trip.

As Payhawk Principal Product Manager, Boris Angelov explains in our guide to travel and expense analytics that when booking sits in one place and card spend in another, finance only gets the full picture once expense reports come in.

It’s exactly the kind of admin finance leaders want to remove from their plate. In Payhawk’s survey of 1,520 senior finance and procurement leaders, 98% said they want AI to take over admin work so their teams can focus on strategic priorities.

Some trips leak off-platform. Travellers will always look for shortcuts if the itinerary becomes complex. That means one leg can get booked directly on a personal card and claimed at a later date, which lands outside your policy checks.

One change means chasing several requests. Let’s say the Warsaw meeting moves by just one day; the employee might need to change their flight or accommodation, but the approvals are tied to each other. Then ensues several conversations about one decision.

What ‘one journey, one request’ should mean

If you’re reviewing how your company handles booking multi-city business travel, use this checklist to ensure you’re judging the booking by the trip, not the ticket:

1. One request. The traveller should only have to describe the whole itinerary once and submit it for a single approval.
2. Any carrier. Low-cost and full-service airline carriers can sit inside the same trip, because the trip isn’t limited by what will fit inside one ticket.
3. One timeline. Everyone: approvers, travel managers, and finance members can see every flight and hotel in order, with the total cost visible.
4. Edit a single leg. Changing a flight shouldn’t impact the hotel booking for another night, and it certainly shouldn’t mean you restart the entire trip.
5. Per-booking policy. Every flight and hotel is checked against your specific rules, so an over-limit hotel in one city gets flagged without blocking the rest.
6. Clean attribution. Every booking, payment, and invoice links back to the same trip, traveller, and cost centre.

The policy point in particular matters a lot. As Payhawk CFO Konstantin Dzhengozov says, most travel policies don’t fail because of how they’re written. They fail because they rely on employees remembering them. Checks built into the request remove that reliance.

A practical way to start: take a recent multi-city business trip and count the touchpoints. Note how many requests, approvals, payments, and invoices it created, and how many systems finance has to open to close it out.

That number can act as your baseline, and it shows you exactly where booking multi-city business travel can get simpler.

How Payhawk turns multiple requests into one

Multi-city trips are now live in Payhawk’s Travel AI Agent, launched in our Fall ‘26 edition.

Here’s the same London trip again, step by step:

1. Describe the trip only once. The travelling employee can tell the agent where they’re going and when, in this case, London to Berlin, Berlin to Warsaw, then Warsaw to London.
2. Pick a fare for each leg of the journey. The agent will work through one leg at a time. For each flight, the employee can filter and arrange the options available and see which fares are inside your policy, and choose a different airline per leg if that’s the best option.
3. Add the hotels. Once fares are confirmed, the employee can add a hotel for the Berlin trip and another for Warsaw. Your company’s maximum nightly rate from your travel policy sits alongside the options.
4. Submit a single request. The employee then sends the whole itinerary as a single trip request. The designated approver sees the full journey and the total cost, and nothing will be booked until it’s approved.
5. Each booking stays clean underneath. Every flight and hotel is still booked, paid, and invoiced as separate bookings, which is why the agent can mix carriers effortlessly. Each booking links to a card, a trip, and an invoice. And trip costs sync to your ERP already coded to the correct cost centres.
6. Change one leg, not the whole trip. If someone moves the meeting in Warsaw, you can change just one flight, the rest of the trip remains the exact same.

If there are a few of you travelling, the same trip can cover the entire group, but still keeps each traveller’s policies, approvals, cards, and expense reports separate. This means multi-city business travel runs as one trip for the people involved, with the financial details kept intact at booking level.

And the time you save adds up quickly with Payhawk estimating you can save around 90 minutes per trip compared with typical pre-Payhawk workflows.

Farah Rouassi, VP Finance and Strategic Partnerships at Paradox, saw the difference first-hand: booking a flight and hotel used to take her over an hour, and with the AI travel agent, it took her just four minutes.

Manage multi-city business trips as one journey

To scale operations and win new business, many UK teams have to take part in multi-city business travel at some point. Managing it well means matching the process to how the traveller experiences it; i.e., as one journey.

With Payhawk’s travel AI agent, you have one request, one approval, and one view of the cost, but still have every booking clean and traceable beneath. When booking multi-city business travel works like this, the trip is smooth from request to reconciliation for everyone involved.

Planning a multi-city trip soon? Book a demo to see how Payhawk’s travel AI agent handles it, from a single request to clean reconciliation.