Policy exception reporting

How do we capture every out-of-policy choice after booking with its reason and its approver, and report it to the travel manager?

Record the exception at the moment it happens, not from the agency's monthly file. After each booking, Callvu compares the booked itinerary with the corporate travel policy and the pre-trip authorization, classifies each deviation (the fare above the lowest logical fare, the cabin, the hotel above the cap, a non-preferred supplier, a booking inside the advance window, a trip without authorization), attaches the reason the traveler gave and the approver who allowed it from the approval record, writes the exception against the trip in the booking system, and reports to the travel manager by traveler, cost center, exception type and amount, with the unapproved exceptions flagged for follow-up.

In scopeSimpleCallvu moves: classify, write back

Talk to an expert Try it in the sandbox

Last updated November 7, 2026.

The problem today

The quarterly exception report arrived from the agency as a spreadsheet nobody could tie to an approval.

Today, without Callvu

Travel managers get exception data late and thin: a file from the agency with the fare paid and the lowest fare offered, no reason, no approver, no link to the authorization. Follow-up with a traveler about a trip two months ago is a conversation nobody wants. The policy loses its force because nobody can show who allowed what.

An exception is a comparison of the booked itinerary with the policy and the authorization, made at booking time when the reason and the approver are known. Classified by type and amount, attached to the trip, it is a record the travel manager can act on while it matters and finance can rely on at reconciliation.

The report is a by-product of recording the exception when it happens.

How it runs

From the requestto the system of record.

A booking is ticketed or confirmed in the booking tool or by an agent. Callvu runs the comparison.

Traveler or arranger: Gave the reason at booking; is asked for a missing reason.
Travel manager: Receives the report and follows up unapproved exceptions.
Finance: Uses the exception record at reconciliation.
Callvu: Compares, classifies, attaches the reason and the approver, writes and reports.

Classify the deviations
The booked itinerary is compared with the corporate travel policy for the traveler and with the pre-trip authorization: the fare against the lowest logical fare offered at booking, the cabin against the entitlement, the hotel rate against the cap, the supplier against the preferred list, the booking date against the advance window, the trip against the authorization; each deviation is classified by type and the amount over.
Attach the reason and the approver
The reason the traveler entered at booking and the approver and decision from the trip approval record are attached; a deviation without a reason is chased from the traveler with the specific question; a deviation without an approval is flagged as unapproved.
Write back
Each exception with its type, amount, reason, approver and flag is written against the trip in the booking system, the system of record, so the expense reconciliation and the audit can read it.
Report
The travel manager receives the report by traveler, cost center, exception type and amount, with the unapproved exceptions listed first for follow-up, on the schedule the policy sets and on demand; the back office report shows the exceptions by channel and supplier.

Where it ends: Every out-of-policy choice was recorded at booking with its reason and approver, written to the trip, and reported to the travel manager while follow-up is still possible. The Decision Trace shows each comparison and classification; the Audit Trace shows the chases and the report.

Runtime enforcement

What is enforcedwhile the work runs.

The regulations preloaded in Callvu Studio and the bank's own policies, applied as steps that run, not lines in a binder. A step that breaks a rule does not run, so a completed run was compliant.

Regulations

Corporate travel policy: The policy defines the comparison points (the lowest logical fare and its tolerance, the cabin entitlements, the hotel caps, the preferred suppliers, the advance purchase window, the authorization requirement), the approvers, and the reporting cadence and recipients; the classification applies each clause and the report follows the policy's schedule.
Expense policy and tax rules on business travel: An unapproved out-of-policy cost may be disallowed or treated as a taxable benefit; the exception record with the approver is the evidence finance uses at reconciliation and the auditors review.
Data protection for traveler reporting (GDPR where it applies): Reports on individual travelers are personal data processed on the employer's legitimate interest with transparency to employees; access is limited to the travel manager and finance roles.

Company policies

The comparison runs on every booking at ticketing, never from a monthly file.
Every exception carries a reason and an approver or is flagged unapproved.
The report goes to the travel manager on the policy's cadence with unapproved exceptions first.
The booking system is the system of record for the exception.

Controls

Policy and authorization comparison at ticketing.
Exception classification by type and amount.
Reason and approver attachment with chases.
Unapproved flagging.
Booking system write.
Scheduled and on-demand reporting.

Clocks and deadlines

Comparison: At ticketing or confirmation.
Reason chase: Reminders to the traveler on the policy's schedule.
Report: The policy's cadence and on demand.

Documents and checks

The comparison per booking
The exceptions with reason and approver
The report

In the Decision Trace

Each comparison point and its result.
The classification and the flag.

In the Audit Trace

The comparison with time.
The chases.
The write and the report.

The handoff

Between the front doorand the back office.

The front door

None for the traveler beyond the reason at booking and a chase for a missing one.

The back office

The travel manager works from a live report with reasons and approvers; finance reads the trip record.

The Decision Desk

An unapproved exception above the policy's threshold goes to the travel manager in the Decision Desk for follow-up with only the allowed outcomes (accept with a note, request a retroactive approval, or refer to finance).

Proof

In scope.Proof at scale, not one process at a time.

The kind of process Callvu runs in production for customers in this industry. Ask for a reference on this exact process. The results below are the industry's published proof; each claim code links to its record on agents.callvu.com.

More than 1,000 processes are live across Callvu customers.

Across Callvu customers

Questions

What buyers ask next,answered plainly.

When is an exception recorded?

At ticketing or confirmation, when the itinerary is compared with the policy and the authorization and the reason and approver are known.

What does the report show?

Exceptions by traveler, cost center, type and amount, with reason and approver, and the unapproved ones first.

What if there is no approver?

The exception is flagged unapproved and the travel manager decides the follow-up in the Decision Desk.

Related processes

Out-of-policy trip approval Pre-trip authorization Travel expense reconciliation Unused ticket tracking and reuse Try it in the sandbox All travel and ecommerce processes

Bring this process, or the one that costs you most.

We build it against your policies and your systems, train your team and stay with you through launch. You are live in weeks.