Automating Travel Expenses: True Cost per Report

$58 per report - the number nobody tracks

Most finance departments know their travel costs. They know how much the organisation spends annually on flights, hotels and per diem allowances. What they rarely know: what does it cost to process a single expense report?

The answer comes from the GBTA Foundation in partnership with HRS: $58 per transaction when processed manually. The error rate stands at 19 percent. The correction cost per error is $52 (Source: GBTA Foundation / HRS, “Expense Reporting: Global Practices and Pain Points”, 2015).

These three numbers shift the perspective. Travel expenses are not just a spend category - they are a process cost problem. And for enterprises with tens of thousands or hundreds of thousands of transactions per year, that problem adds up to millions.

The anatomy of the $58

Visible costs: capture and approval

The employee photographs the receipt, enters the data into SAP Concur or a comparable tool, assigns a cost centre and submits. The manager reviews, approves or rejects. The clerk in the Shared Service Center checks again, validates against policy and posts.

Three people, three steps, one receipt. That is the visible part of the $58.

Hidden costs: corrections and queries

A 19 percent error rate means nearly one in five transactions requires rework. Wrong per diem rate applied, meal deduction missed, incorrect collective agreement rate used, cost centre misassigned. Each correction costs $52 - the transaction goes through the entire process a second time.

Then come the queries: the clerk contacts the employee because information is missing. The employee searches for a receipt that is three weeks old. The manager is asked to approve a second time. These loops consume time that never appears in any cost accounting.

Systemic costs: audit risk and compliance

When 19 percent of transactions contain errors and only samples are reviewed, systematic mistakes accumulate undetected. The risk materialises during a tax audit: the auditor does not ask about individual receipts but about the system behind them. Is there documented decision logic? Can it be traced why this per diem allowance was calculated at this rate?

In most enterprises, the answer is no. The decision logic resides in the clerk’s head, not in the system. That is not audit-ready procedural documentation - it is an audit risk.

Projections: what travel expenses really cost the enterprise

Scenario A: 10,000 transactions per year (upper midmarket)

At 10,000 transactions, expense processing occupies the equivalent of 3 to 4 full-time employees in the Shared Service Center. Correction costs alone account for half an FTE.

Scenario B: 100,000 transactions per year (enterprise)

Nearly $7 million per year - for processing alone, not for the actual travel spend. On top of that: at 100,000 transactions and a 19 percent error rate, 19,000 transactions are faulty. That is not residual risk - it is a systemic problem.

Scenario C: 500,000+ transactions per year (logistics, airline)

$34 million in processing costs per year. For airlines and logistics enterprises, where every employee inevitably travels (crew flies, drivers drive), this is not optional - these transactions are a by-product of the core business.

Why OCR and approval workflows are not enough

The obvious answer to the cost problem: digitalisation. OCR for receipt capture, workflows for approval, apps for submission. This reduces manual effort in capture - but not in decision-making.

OCR captures the receipt. A workflow routes it to the right person. But who decides:

• Which per diem rate applies when the employee travelled through three countries?
• Whether the collective agreement overrides the statutory rate - and if so, which collective agreement?
• How the meal provision should be deducted when the hotel includes breakfast but the employee did not use it?
• Whether entertainment expenses are deductible at 70 percent (Germany) or 50 percent (Austria) - or follow entirely different rules in other jurisdictions?

These are not capture problems. They are rule application problems. And no OCR system and no approval workflow solves rule application problems.

The difference between capture and governance

What is missing is the layer between receipt capture and posting: a governance layer that documents, for every transaction, which rule was applied and why.

The Decision Layer breaks down every expense transaction into its micro-decisions and defines for each step: the applicable rule set, the hierarchy (statute before collective agreement before company policy) and the documentation. The decision is not made by a person acting on experience but by a versioned rule set that is traceable, reproducible and audit-ready.

This also changes the operating model: instead of submit, approve, post (three manual steps), the transaction is processed automatically. The employee sees the result and has the right to object - the veto approach. Instead of manually reviewing every transaction, only exceptions are handled. That is the difference between zero percent and 85 to 95 percent zero-touch processing.

Four industries, four ROI profiles

The Travel Decision Layer works across industries. The automation rate varies by sector because input data is structured differently:

The highest zero-touch rates are achieved by industries with machine-readable input data: GPS tracks in logistics, crew rotations in aviation. Consulting sits at 85 percent because multi-client weeks may require manual allocation.

The decisive factor for ROI is not just per-transaction cost reduction but the elimination of the correction loop: moving from a 19 percent error rate to below 2 percent means the $52 correction cost effectively disappears.

The veto approach: automation without losing control

A common objection to automation: “We lose control.” The veto approach reverses the logic.

Today: the employee submits. The manager approves. The clerk posts. Three manual steps, each one error-prone.

With the Decision Layer: the system calculates the transaction automatically based on the stored rules. The employee sees the result and can raise an objection - within a defined period. Without objection, the transaction is posted automatically.

This is not less control. It is more control - documented, traceable, reproducible control. Instead of a subjective approval by a manager who may not know the collective agreement in detail, a rule set decides that can be inspected by employee representation bodies and verified by external auditors.

When it pays off - and when it does not

Not every enterprise needs fully automated expense processing. The investment pays off when at least two of the following criteria apply:

• Volume: More than 10,000 expense transactions per year
• Rule complexity: Collective agreements, multi-jurisdiction operations or industry-specific rules
• Audit requirements: Audit trail-ready procedural documentation, tax audit preparedness
• Shared Service Center: Centralised processing with documented process quality

When the organisation only processes domestic travel without collective agreements, SAP Concur or a comparable tool is sufficient. The governance layer becomes relevant where the rules are complex enough that a clerk makes errors - precisely where the GBTA numbers show their full impact.

Gosign implements the Travel Decision Layer on an industry-specific basis - from evaluation through a 3-month pilot to production operation. On your infrastructure, without external SaaS dependency, with full source code access.