What is an Online Booking Tool (OBT)? Complete Guide to Corporate Booking Platforms
TL;DR: An online booking tool (OBT) is corporate travel self-booking software that lets employees reserve flights, hotels, rail, and ground transport within a managed program. It enforces travel policy in real time, surfaces negotiated and NDC content, routes trips through approval workflows, and feeds structured data to finance and duty-of-care systems. Leading OBTs sit alongside a travel management company (TMC) or a BYOD overlay and are measured by adoption, leakage, and cost per transaction.
Defining the Online Booking Tool
An online booking tool is the self-service front end of a managed corporate travel program. Instead of emailing an agent, a traveler logs into a web or mobile application, searches live inventory, and confirms a trip that already respects company rules. The Global Business Travel Association (GBTA 2025 BTI Outlook) estimates that roughly two-thirds of transactions in mature North American programs now originate inside an OBT rather than through an agent. Drawing from 8+ years building AI-powered corporate travel platforms, the patterns that hold up are consistent: policy at the point of search, structured data on the other side, and a human escalation path when the booking is non-standard.
Three categories dominate deployments today: full-featured OBTs licensed by a TMC (SAP Concur Travel, Cytric by Amadeus, Deem by Enterprise Mobility), integrated TMC-native platforms (Navan, TravelPerk), and emerging BYOD overlay models that keep the existing booking workflow intact and layer analytics, re-shopping, and duty of care on top. Choosing between them is primarily a question of content strategy, finance integration, and traveler behavior — not of features in isolation.
What an OBT Does Inside a Managed Program
A corporate-grade OBT performs eight functions: shop for multi-source air, hotel, rail, and car inventory; apply dynamic travel policy; display negotiated rates and preferred suppliers; route exceptions through approval; capture structured PNR and expense data; push itineraries to duty-of-care feeds; reconcile unused ticket credits; and report on adoption and savings. The U.S. Department of Transportation 24-hour rule (14 CFR 259.5) still governs ticket cancellation on flights originating or ending in the United States, and compliant OBTs enforce that window at voiding. For hotels, the Airlines Reporting Corporation (ARC) and the Hotel Electronic Distribution Network Association (HEDNA) set the data standards that let an OBT compare a GDS rate with a direct-connect rate line by line. These integration primitives are what separate an OBT from a consumer OTA.
Inventory: GDS, NDC, and Direct Connects
Content is the hardest part of an OBT buying decision. Traditional booking tools pull from one of the three global distribution systems — Amadeus, Sabre, or Travelport — which still carry the majority of corporate air volume. However, IATA's New Distribution Capability (NDC) now covers all three major U.S. network carriers (American, Delta, United) and most European majors, and IATA reports that NDC accounts for a growing double-digit share of indirect air transactions in 2025. NDC exposes continuous pricing, ancillaries (bags, seats, lounge), and merchandising offers that GDS EDIFACT cannot render natively. A credible OBT in 2026 supports NDC where the carrier requires it, direct-connect APIs for hotel chains (Marriott, Hilton, Accor), and traditional GDS for rail and long-tail air — then normalizes the output so policy and approval logic see a single schema.
Policy, Approval, and Duty of Care
Travel policy sits inside the OBT as a rules engine: fare caps indexed to GSA per diem rates for U.S. domestic travel, advance-purchase windows (typically 14 or 21 days), class-of-service ceilings by flight duration, and preferred-supplier logic. Non-compliant selections can be soft-blocked (warning plus justification field), hard-blocked (no booking without override), or auto-routed through an approval workflow. Duty-of-care integration is non-negotiable in 2026 — ISO 31030:2021 "Travel Risk Management: Guidance for Organizations" sets the framework that most legal teams now reference, and OBT itinerary data is the primary input to traveler-tracking platforms. Buyers evaluating tools should ask whether the OBT pushes itineraries to risk feeds within 60 seconds of confirmation and whether cancellation events propagate automatically.
Pricing Models for Corporate Booking Platforms
OBT pricing has fragmented over the last five years. The three dominant models are per-transaction fees (bundled with TMC servicing), per-active-user SaaS subscription, and savings-share overlays. A corporate buyer should compare total cost of ownership across all booked, canceled, and re-shopped transactions — not just the headline number.
| Platform Type | Typical Pricing | Content Model | Who It Fits |
|---|---|---|---|
| Traditional OBT via TMC (Concur Travel, Cytric) | $6–$18 per transaction, plus TMC fees ($25–$50 agent-assisted) | GDS primary, NDC emerging, direct-connect hotel | Mid-market and enterprise with established TMC |
| TMC-native platforms (Navan, TravelPerk) | $0 base + $0–$25 per booking, or $15–$25 per active user/month | Blended GDS, NDC, and aggregator inventory | SMB and tech-forward mid-market |
| BYOD overlay (Travel Code) | 25% of validated savings (RateGuard); keep existing booking workflow | Overlay — leaves current OBT/TMC inventory intact | Programs with existing OBT/TMC, high leakage, or multi-TMC footprints |
| Direct-to-supplier booking | No OBT fee; loyalty-driven | Supplier.com only | Very small firms, <$250K annual travel spend |
Measuring an OBT: Adoption, Leakage, and Savings
Four metrics tell you whether an OBT is working. Adoption rate — the share of eligible transactions booked online versus offline — is the headline number; GBTA benchmarks place best-in-class programs above 85% for domestic air and 70% for hotel. Leakage — bookings made outside the managed channel entirely — typically runs 15–30% in large programs per Festive Road and BTN Group research (2024–2025), and it is the single biggest driver of lost duty-of-care coverage. Cost per transaction (CPT) combines OBT and agent fees against total booked volume. Realized savings compares booked fares against the lowest-logical-fare at time of booking; a credible program re-shops post-booking to capture rate drops before ticketing, which is where a BYOD overlay such as Travel Code's RateGuard (priced at 25% of validated savings) typically sits alongside the OBT rather than replacing it.
Implementation Timeline and Pitfalls
A standard OBT implementation runs 12–20 weeks. Weeks 1–4 handle discovery, policy design, and integration scoping with HRIS (Workday, UKG) and expense platforms. Weeks 5–12 cover configuration, SSO (SAML/OIDC), approval routing, and content loading (GDS PCC, hotel programs, negotiated air). Weeks 13–16 pilot with a single business unit; weeks 17–20 roll out globally with change management. The two pitfalls that recur across implementations are under-scoping NDC enablement (carriers require per-airline certification) and skipping a leakage baseline — without a pre-launch measurement, finance cannot prove the business case. For procurement teams scoping an RFP, the procurement hub covers scorecard templates, SOC 2 Type II evidence requests, and reference-call questions.
Where OBTs Fit Alongside TMCs and BYOD Overlays
An OBT is one layer in a modern travel stack. A TMC provides human servicing, after-hours support, VIP handling, and consolidated billing. The OBT provides self-service and policy enforcement. A BYOD overlay — including Travel Code — keeps the existing OBT and TMC in place and adds continuous rate re-shopping, real-time duty of care across all channels (including direct-to-supplier bookings the OBT never sees), and a unified analytics layer across fragmented booking sources. The trade-off is explicit: OBT consolidation drives adoption upward; overlay strategies accept fragmentation and recapture value downstream. Most mid-market and enterprise programs end up running both. For a side-by-side view, see Corporate Travel Booking Platforms Compared: BYOD, OBT & TMC Models.
Frequently Asked Questions
What is the difference between an OBT and a TMC?
An OBT (online booking tool) is self-service software that a traveler uses to book a trip within policy. A TMC (travel management company) is a service organization that provides human agents, after-hours support, duty-of-care protocols, and consolidated billing. An OBT is typically licensed or resold by the TMC and sits inside the TMC's servicing envelope, though TMC-native platforms (Navan, TravelPerk) and standalone OBTs (SAP Concur) also exist.
How much does an online booking tool cost?
Transaction-based OBTs billed through a TMC typically run $6–$18 per online booking, with agent-assisted transactions adding $25–$50. TMC-native platforms often use per-active-user SaaS pricing in the $15–$25 per user per month range, or a zero-base model with per-booking fees. Total cost of ownership should include implementation ($15K–$75K for mid-market, higher for enterprise), ongoing configuration, and the cost of unmanaged leakage.
Can an OBT integrate with my existing travel management company?
Yes. Most enterprise OBTs — SAP Concur Travel, Cytric, Deem — are TMC-agnostic and are routinely deployed with any ARC-accredited TMC via GDS PCC configuration, mid-office automation (Compleat, Quatrro), and shared SSO. The integration work is typically scoped jointly by the OBT vendor and the TMC during the 12–20 week implementation. Confirm that the TMC supports post-booking re-shopping and NDC servicing before contracting.
What is NDC and why does it matter for OBTs?
New Distribution Capability (NDC) is an XML-based IATA standard that lets airlines sell fares, ancillaries, and merchandised offers through indirect channels with the same richness as their own websites. In 2026, major carriers increasingly surcharge or withhold content from EDIFACT-only channels, so an OBT that lacks NDC support will show inflated or incomplete fares. Buyers should verify NDC coverage carrier by carrier, including seat selection, bag pricing, and refund servicing.
Is an OBT the same as a self-booking tool (SBT)?
Yes — the terms are used interchangeably in the industry. "Self-booking tool" was the dominant term through the 2000s; "online booking tool" has become standard since GBTA shifted terminology in the 2010s. Both describe the same category: corporate self-service travel reservation software with policy, approval, and reporting built in. Some legacy RFPs still use SBT; the functional requirements are identical.
Can OBTs handle international and multi-stop corporate itineraries?
Enterprise OBTs handle multi-city, multi-passenger, and multi-currency itineraries, though complex international trips (open-jaw fares, around-the-world tickets, visa-dependent routings) are still frequently escalated to a TMC agent. Policy engines can gate international bookings on advance approval, visa verification, and risk-category routing (per ISO 31030:2021). For programs with high international complexity, measure agent-escalation rate as a quality metric, not a failure metric.
Sources and Further Reading
- Global Business Travel Association (GBTA) — 2025 Business Travel Index Outlook
- International Air Transport Association (IATA) — NDC Program Updates, 2025
- U.S. Department of Transportation — 14 CFR 259.5 (24-hour reservation rule)
- U.S. General Services Administration (GSA) — FY2026 Per Diem Rates
- ISO 31030:2021 — Travel Risk Management: Guidance for Organizations
- Airlines Reporting Corporation (ARC) — Corporate Travel Trends, Q3 2025
- Festive Road and BTN Group — Managed Travel Program Benchmarks, 2024–2025
This guide was reviewed by the Travel Code editorial team in November 2026. Pricing and feature information reflects publicly disclosed data from vendors as of the review date; verify current terms directly with each supplier.
