What auto-issue means in corporate travel

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 working sequence is in from search to ticket. We do not invent issue rates or average time-to-ticket figures.

Where it sits in the flow

The honest order is search, policy, approval, then issue. If auto-issue runs before policy has been applied, or before an approval chain has finished, the programme has automated the wrong step. Policy at search should already have narrowed the choice. An approver should already have seen the trip, where the rule requires it. Only then should auto-issue in GTOS complete a clean booking on the same trip record.

When the booking is not clean — missing data, a fare that will not issue, a group, a complex multi-city, a mid-trip change — the file should move to a person. In GTOS that person works in Control Tower or at the expert desk. The test is whether the handoff continues on the same trip, not whether the software can be forced to issue something an adviser should have reviewed.

What auto-issue is not

It is not a content path. A fare may have arrived through a GDS or an NDC offer; auto-issue does not change that source, and this page does not claim that every source can be issued automatically. It is not mid-office quality work. If documents are incomplete, issue should wait. It is not a licence to skip approval on trips the policy says must be approved. And it is not a consumer “book now” button with a corporate logo on it. The corporate version has to leave a trail: what was issued, under which rule, at which time, for which passenger.

Why programmes want it

Advisers should spend their time on the trips that need judgement, not on re-keying clean, already-approved, in-policy bookings. Travellers should receive documents without waiting in an unnecessary queue. Finance should see issue and cost on the same record they already used at approval. Those are operating reasons. They only hold if the rules that gate auto-issue are real. A setting that issues everything, including exceptions that were never approved, will create a later cleanup that costs more than the queue it removed.

How to test it in a demo

Walk an in-policy, already-approved flight from the online booking tool through to issued documents on the trip. Then walk a case that should not auto-issue — an incomplete passenger file, or a trip that still needs an approver — and show the desk queue instead. If both cases are visible on the same record, auto-issue is being treated as a controlled finish, which is what it should be. If only the happy path is shown, ask for the failure path before you treat the feature as ready for the programme.