What back-office means in travel operations

This definition is written by the team behind GTOS, the Global Travel Operating System from Voraal, and is built on operating experience across 100,000+ trips. The agency view sits on the back-office solution page. We do not publish prices, and we do not claim a certified list of accounting connectors.

The file has to arrive clean

Mid-office quality and change work is what makes back-office possible at a decent standard. A passenger list that still does not match the ticket, a hotel date that was moved only in email, or a missing tax line will all surface as exceptions in settlement. Those exceptions are expensive because they are discovered late. The operating discipline is therefore shared: mid-office keeps the file current; back-office bills and reconciles that file; neither team should keep a private version of the trip.

In a corporate programme the same logic holds. Invoices should attach to the booking. Month-end reporting should be a view of the trip record, not a reconstruction. Travel spend management starts before the invoice exists — at search, approval and ticket — and finishes when the invoice and the booking agree.

What back-office software should show

A product in this category should open the trip and show the commercial picture: what was booked, what was changed, what is billable, and what is still outstanding. It should not require a side spreadsheet to explain a discrepancy to a client or to finance. Where an agency runs many corporate accounts, the back office also has to respect account boundaries — one client’s figures cannot leak into another client’s file. Data separation and role design are part of that promise, not an afterthought.

Accounting still sits next to this layer. Figures have to reach the ledger the organisation actually uses. GTOS does not pretend to be a general ledger. Folio6 is the Voraal family accounting product, and a handoff toward other accounting tools is a scoped conversation, not a published connector list. See accounting integrations. What can be stated here is the rule: the numbers that leave travel should already be tied to a trip.

Edges that are often blurred

Back-office is not mid-office, even when one vendor sells both and one person does both jobs on a small desk. Quality and amendments are mid-office work. Settlement is back-office work. Blurring the language usually blurs the queues, and then nobody owns a broken file. Back-office is also not a travel operating system on its own. An operating system holds the trip from request to close; back-office is one band of that life, at the end.

Payments, cards and expense tools sit on nearby edges. They can feed or follow the trip, but they should not become a second source of truth for what was booked. If a payment view and a booking view disagree, the organisation will trust neither during a difficult close. The test in a demo is ordinary and strict: pick a changed trip and show the invoice still pointing at the current file.

Why clients feel this layer

Clients rarely ask for “back-office software.” They ask why the invoice does not match the itinerary they approved, or why a cancelled sector is still on the bill. Those questions are back-office questions with mid-office roots. A TMC or agency that can open the trip and walk the charges earns trust at the point where programmes are usually lost — in finance, at month end, on a file that should have been quiet.