HomeHelpCorporate PortalPolicy Compliance

Policy Compliance

Where travel policy rules are actually evaluated, what a rule is, and where compliance is reported.

Org UserOrg AdminSuper AdminLast reviewed 03 Aug 2026

Was this article helpful?

Related Articles

Submitting Travel Requests

Complete the six-step travel request wizard: trip details, booking method, travellers, requirements, budget, and review.

Approval Workflows

Follow a request through its approval chain, and approve or reject requests from the Approvals inbox.

Budget Tracking

Maintain budget codes and department budgets, read the request-form budget bar, and find real spend figures.

Previous

Approval Workflows

Next

Budget Tracking

Travel policy in TravelFlow has two separate parts: the policy documents your organization publishes for employees to read, and the rule engine that can block an approval. They are configured in different places and behave differently. This article explains both so you know what is actually enforced.

Where to Read Your Policies

Published policy documents live at Documents > Policies. You can search them, filter by category (Travel, Accommodation, Expenses, Approval, Compliance), open a policy for the full detail page, and download any attached files. See the Travel Policy Library article for the details.

When Policy Rules Are Evaluated

Policy rules are checked at one point only: when an approver approves a request. Nothing is evaluated while you fill in the travel-request wizard, while you search in the GDS portal, or at checkout, and no policy warning banner is shown to the traveller anywhere in the product.

  • A rule set to blocking stops the approval. The approver sees "Approval blocked by policy violations" with the list of rules that failed, and the violations are logged.
  • A rule set to advisory or audit only does not stop anything; it is recorded against the request for reporting.

What a Rule Looks Like

A rule is a generic comparison — a field on the request, an operator, a value, and the message to show. There are no built-in categories such as cabin class, advance-booking windows, or preferred suppliers; whatever you want to enforce has to be expressed as a field comparison.

Important: The Travel Policies tab in Administration > Admin Dashboard only captures a name, code, description, and department — it has no rule editor and always saves an empty rule list. Policies created there therefore produce no enforcement. Treat the rule engine as configuration that has to be provisioned outside the app, and do not rely on it for day-to-day control.

Exemptions

There is no exemption box on a travel request. Exemptions are managed on their own screen at Administration > Exemptions, where you raise a request for a user, a department, or the whole organization for a fixed period. See the article on requesting and managing policy exemptions.

Where Compliance Is Reported

Recorded violations feed two admin-area surfaces: the Policy Compliance tile on Administration > Analytics (compliance rate and violation count for the selected period) and the Policy Compliance Audit report type on Reports. There is no per-employee repeat-violation view.