Employee and organisation data, ready for policy and approvals

This page describes that foundation honestly. GTOS, the Global Travel Operating System from Voraal, does not publish a list of certified HRIS connectors on this site. We do not claim a live, named sync with a particular human resources platform. How employee data will move between your HRIS and GTOS is scoped during implementation and discussed in a demo, against the systems you actually use.

Why employee data sits at the centre of GTOS

In the Client Portal, admins work with:

- Employees, roles and the organisation chart.

- Travel policy by designation, department and destination.

- Approval chains taken from that chart, by role and limit.

If that data is stale, the programme breaks in visible ways. A leaver still appears as an approver. A new joiner cannot book. A promotion still carries an old fare class. A department change sends a request to the wrong manager. Keeping the organisation structure current is therefore a travel-operations task, not only an HR task.

GTOS is built so those records are the same ones the booking path uses. When a traveller searches in My Mobility, the policy check can use their designation and department. When a request needs approval, the chain can follow the chart. That is already true inside the product, whether the names were entered in GTOS or later connected from an HR system as part of an agreed implementation.

What we will and will not claim

Buyers are right to ask whether GTOS “integrates with our HRIS.” The accurate answer is:

- The product already holds employee, role and organisation data and uses it for policy and approvals.

- A connection from an HRIS, including the direction of the sync, the fields involved, and the cadence, is an implementation topic. It is not a public catalogue of pre-certified connectors.

- We will not invent a partner badge, a field-level mapping, or a go-live method on this page.

If you need that connection, bring the name of your HR system, a sample of the fields you care about, and your identity requirements to a demo. We will describe only the path that is actually available.

Access remains by role. Each company sees only its own data. Two-step sign-in is available on the GTOS app. Employee data used for travel is still company travel data; see Security and security questions. We do not claim certifications we do not hold.

How this relates to finance systems and the wider stack

People data and finance data often arrive from different source systems. Cost centres may originate in an ERP even when names originate in an HRIS. The companion page ERP and finance systems covers spend, invoices and the finance handover in the same conservative way. There is no requirement to read these as already-completed, named integrations.

Voraal products around GTOS remain distinct. Rezencia is a reservations platform. Folio6 is travel accounting. Avunzo is designed to connect travel content and booking flows to your own channels and is not yet live on production; early access is available on request. None of those pages is a substitute for an HRIS conversation.

GTOS is built on operating experience across 100,000+ trips and is designed to scale to 1,000+ employees per client, which is exactly why stale employee data becomes a programme risk. USD is the main currency on this site. Pricing is in USD and available on request.