Corporate travel is built for the traveller. Finance inherits the mess

Every tool built for business travel is built to make one person's life easier: the traveller. Search the fares, compare the hotels, book in a few taps, carry the itinerary in your pocket and change your flight in a couple of clicks. On that job the market has done brilliantly. Booking and managing a business trip has never been easier.

The person who books the trip is not the person who has to account for it, and almost nothing in the travel stack is built for the second job. For the finance team the difficulty starts after the trip is booked and does not end until month-end, and no amount of booking polish touches it.

Travel is often the least controlled major spend category in a business, which is strange given how much of it there is. It gets booked outside the finance systems, paid across a mix of methods, from a corporate card to a personal card to a hotel invoiced directly, and then reconstructed by hand weeks later from whatever evidence can be gathered. The booking was the easy part. The control was never designed in.

The trouble lives in the space between systems. A single trip usually scatters across several of them: the travel provider books the flight, a card pays for it, an app captures some of the receipts, a supplier invoices for the hotel, and the ledger eventually receives whatever survives the journey. Finance is left to thread a needle through all of it, working out what the trip actually was, who took it, which budget it belonged to and what it cost from start to finish. That stitching appears in nobody's job description, yet it takes a real share of the finance team's month.

A common assumption is that corporate cards and an expense tool already solve this. They solve half of it. Cards and expenses give a finance team visibility, not control. A card line shows an airline and an amount, but it does not know the flight was for a sales trip, approved by a particular manager and charged against a particular budget. The expense tool sees scattered receipts with no approval flow and no budget link unless someone assembles all of it after the event. Visibility that lands after the money has gone is not the same as control.

For Australian and New Zealand businesses there is a sharper edge, and its name is Fringe Benefits Tax. The instinct is to treat travel as a tax problem waiting to happen. Mostly it isn't. Genuine business travel does not incur FBT at all, under the otherwise deductible rule. The catch is that the exemption is only ever as good as the records behind it. FBT attaches to the parts that fall outside pure business - the couple of private days tacked onto a work trip, the client dinner that is really meal entertainment, the partner who came along for the ride, the long trip with no travel diary to back it up. Those are exactly the details that go missing when spend is scattered across several systems. Get them wrong and a business either overpays to stay safe or underpays and invites an uncomfortable conversation with the ATO. The organisations that handle FBT calmly are not the ones with the best year-end spreadsheet. They are the ones whose travel data is clean, in one place, as it happened, so the position they are taking can actually be proven.

The fix is structural, not another policy document. Policing travel policy after the trip, and flagging the over-limit hotel once it has already been paid, changes nothing. The opportunity sits earlier, in treating the trip as a single record rather than a scatter of transactions. The request, the approval, the booking, the card it was paid on, the invoices, the expenses and the budget it draws down all belong together from the start. When the trip is the unit, the story assembles itself as it happens instead of being reconstructed at month-end, and approval means something again, because it happens while there is still a decision to make.

This is the job ProSpend's Travel Manager module was built for. It connects directly to the travel management company and pulls the enriched trip data through every day - not just an amount, but the traveller's details, the flight path, the ticket number, the hotel check-in and check-out dates, the full itinerary and the reason for travel. The receipt arrives with the trip, generated from the TMC feed rather than chased from the traveller. Each card transaction is matched automatically to its receipt, the expense line is coded with the financial and trip data, and the reconciled travel statement flows straight into the ERP. The manual matching that takes so much of finance's month largely disappears, and the FBT-relevant detail - who travelled, where, for how many nights and why - is captured as it happens rather than pieced together before the deadline. It is a connected system doing the second job the booking tools were never built to do.

It also changes what a return looks like. Ask most travel vendors about return on investment and they start with cheaper fares and negotiated rates, which are real but the bigger return sits in the hours finance and travellers lose to reconciliation every month. A business can negotiate excellent hotel rates and still hand the savings back in the days its team spends matching invoices to card statements.

None of this means ripping out the booking experience employees like. Keep it. The traveller should still get the easy search, the tap to book, the itinerary in their pocket. The question is not whether travel is built for the traveller, but whether it is only built for the traveller. It comes down to deciding where travel is owned.

If the stack ends at the booking screen, finance inherits the mess and clears it up in arrears. If it runs all the way to the ledger, with the trip reconciled against the provider feed, policy and budget checked up front, and FBT-relevant spend captured as it happens, the control is designed in and the close takes care of itself.

There is a simple test for any travel setup, and it is not the booking screen. Ask what the month-end looks like. If the honest answer involves chasing missing invoices, matching card transactions to trips by hand and hoping the FBT data is complete, the tool was built for the traveller, and finance is paying for it every month. If trips are already reconciled, receipts already attached and the data already coded for the ledger, then travel has been built for the people who have to account for it. Business travel was never really a booking problem. It has always been a control problem, and it is solved long before anyone gets on a plane.