A hotel charge has no matching agency reservation. Before labeling it off-channel spend, check whether it was booked directly, through an approved local channel, or under the colleague arranging the stay.
Missing records need investigation, authorized exceptions need approval evidence, and confirmed breaches need action under company policy.
Trace each flagged transaction to its booking decision, payment and applicable approval. Start with one travel category in one market before expanding.
Agree what each source can prove
Bring the travel manager, finance operations and reporting owner together before building a combined spend view. Agree the reporting period, covered entities, categories and treatment of taxes, fees, refunds and foreign exchange. Name the finance-approved source for actual expenditure and retain the other records as supporting evidence.
Booking data describes reservations and their changes. Payment data records charges and credits. Expense records add claimed costs, receipts and approval status. Adding their totals together can count the same purchase repeatedly.
Boston University's July 2025 Concur guidance distinguishes reservation records from card transactions and explains how corresponding records are combined.[1] This illustrates one implementation, rather than universal system behavior.
Register each feed's owner, coverage, refresh timing and exclusions. Card feeds may omit personal-card reimbursements. Keep bookings separate from expenditure and track unused ticket credits until resolved under their terms.
Match the journey without forcing the match
Link records at purchase level: an airline ticket or exchange chain, a hotel stay, or another identifiable service. Trip totals can conceal duplicates or unmatched refunds.
Retain transaction IDs, booking references, service dates, traveler identifiers, entity, currency and payment method. Document currency conversions and preserve original merchant names.
Match stable references first, then traveler, supplier, dates and amount. Allow shared bookings, multiple charges and credits. Route ambiguous matches for review.
Restrict access to traveler-level records. Category reports generally need business unit, route or city, supplier and exception reason; exclude unnecessary personal details.
Finance should reconcile the resulting expenditure view to its agreed control total for the same scope. Investigate differences before publishing a compliance score. Mark records as matched, partly matched or unresolved, and disclose missing feeds. Data completeness and traveler compliance need separate indicators.
Define a denominator that survives scrutiny
Channel adoption rates are misleading if they exclude outside-channel bookings. Unmatched card transactions require investigation before classification.
Define each metric's unit, population, exclusions, timing and owner. Separate booking-based and spend-based measures.
For example, calculate channel adoption using eligible bookings made through approved channels divided by all identified eligible bookings. Show how outside-channel bookings are identified and disclose the remaining coverage gap. A booked trip later canceled should be treated consistently on both sides of the calculation.
For policy compliance, use assessable transactions as the denominator and show the unassessable population alongside it. Separate transactions meeting the original rule from approved exceptions and confirmed breaches. Include the policy version effective when the decision was made. A later policy change should not retrospectively turn a valid booking into a breach.
Keep these categories separate so actions reach the responsible team.
Give each exception a decision and a closure test
This proposed method is not an industry standard. Agree response timing around booking urgency, feed availability and reporting deadlines. Escalate safety concerns immediately through established channels.
| Trigger | Owner and action | Evidence needed to close | Procurement consequence |
|---|---|---|---|
| Charge without a booking match | Reporting owner checks source coverage; travel operations confirms the booking route. | Linked reservation, documented authorized direct booking, or a confirmed breach classification. | Correct the feed, recognize an exception, or refer the breach under policy. |
| Price above the applicable limit | Travel manager checks the rule, available suitable options and approval at booking time. | Booking-time evidence and the authorized decision. | Resolve a content gap or route an unsupported exception to the accountable approver. |
| Potential duplicate or missing refund | Finance operations checks original charges, exchanges and supplier records. | Demonstrated separate purchases, reversal, received refund, or documented final disposition. | Pursue recovery and address recurring supplier reconciliation failures. |
| Repeated approved exceptions on a route or in a city | Category manager reviews availability and business requirements with local stakeholders. | Tested booking options and a verified improvement, or an approved continuing exception arrangement. | Adjust contracted coverage, tool configuration or the local policy module. |
Record the action owner, due date, supporting records and reviewer in an exception log. An email sent to a supplier is an open recovery action. A promised system fix remains open until a subsequent booking test verifies it.
Test the fix before reporting improvement
Consider a hypothetical hotel review. Repeated above-limit stays initially suggest traveler non-compliance. Matching the stays to booking-time records shows that some had approval because suitable contracted rooms were unavailable; other records lack enough evidence to judge.
The travel manager validates the approvals. The reporting owner investigates the missing records. Procurement tests whether the contracted hotels offer usable availability for the required dates and location before seeking new coverage. Confirmed unsupported bookings follow the company's normal accountability process.
At the next agreed review, compare equivalent populations. Fewer exceptions may reflect fewer trips or missing feeds; verify whether the underlying problem improved.
Publish what was found, who acted, verification evidence and unresolved issues alongside the metric. Use the findings to adjust supplier coverage or booking controls.
A travel dashboard earns trust when its exceptions lead to verifiable decisions and its unknowns remain visible.