Lodge cards for corporate travel: centralise air and rail bookings without issuing a card to every traveller

A lodge card or central travel account is a card credential held by a travel-management company or booking platform rather than carried by one employee. Businesses use it to centralise airfare, rail and other travel costs while receiving enhanced booking data for reconciliation.

The credential stays with the booking channel

Unlike an employee card, a lodge card is normally stored by the travel-management company or approved booking system. Employees book travel while the central account funds the transaction.

This reduces the need to issue high-limit cards to every traveller and can improve consistency in how tickets are purchased.

Travel transactions can carry enhanced traveller data

Commercial travel-card programmes can capture employee name, route, ticket number, cost centre and other booking information.

That data helps finance allocate spend without asking employees to identify every airline charge manually after the trip.

Booking policy still matters

A central payment credential does not prevent employees choosing expensive or out-of-policy travel. Combine the card with booking-platform controls on cabin class, route, hotel or advance-purchase rules.

Travel approval should happen before the booking where policy requires it, not after the monthly lodge-card statement arrives.

Set agency and transaction controls

Restrict the credential to approved travel merchants or the travel-management company where the provider supports it.

High-value international travel can create large statement balances, so treasury should forecast payment dates and statement cycles.

Track ticket refunds and credits

Cancelled flights can produce card refunds, airline credits or vouchers. Keep those benefits attached to the correct traveller or business unit.

A credit sitting with an airline is still company value even if it never appears as cash in the bank. Review unused travel credits regularly.

Match the statement to bookings and employee cost centres

Use booking references and traveller data to reconcile the lodge-card statement. The final bank debit settles many underlying journeys.

Do not code the monthly card payment as one generic travel expense. Allocate each ticket, refund and fee to the correct employee, project or department.

Worked example: a consultancy has 200 employees who travel but only one approved travel-management company. A lodge card lets the agency charge flights centrally while travellers avoid using personal cards or waiting for reimbursement. Finance receives one statement enriched with booking references and cost-centre data.

Keep emergency travel outside the normal lodge workflow controlled as well. If employees can book directly during disruption, define which corporate card or payment link they should use and how those purchases re-enter the central travel ledger.

Review agency access when contracts change. A travel-management company that no longer serves the business should lose the credential, and any outstanding refunds or credits should be transferred or reconciled before closure.

Set a rule for unused ticket credits. Travel agencies and airlines can hold substantial residual value after cancellations, and those credits can expire. A monthly report should identify credit owner, value, expiry and whether the next booking reused it.

Separate central travel spend from employee incidental expenses. Flights can sit on a lodge card while meals, taxis and hotels are paid through employee cards or expenses. The travel policy should make that split clear so employees do not assume the lodge account covers everything.

Where the booking agency charges service fees, reconcile those fees separately from tickets. Otherwise the business can overstate travel cost by route and miss the true cost of the agency relationship.

Use policy data to negotiate travel suppliers. A lodge-card programme can reveal which airlines, routes and booking windows drive spend. Procurement can use that information to negotiate corporate fares or preferred-carrier terms instead of relying on employee expense samples.

Keep traveller identity accurate for duty-of-care purposes. Centralised payment should not strip away passenger data needed during disruptions or emergencies. The travel-management system should preserve who is travelling, where and on which booking even though one central card funded the transaction.

Worked example: a consulting firm books 120 flights in one month through one travel agency. The lodge-card statement can carry traveller name, route and ticket number so finance allocates spend without 120 employee reimbursements. That efficiency depends on the booking system sending clean cost-centre data; otherwise centralisation merely shifts manual work from employees to finance.

Review foreign-currency conversion on international tickets. The agency can bill in sterling even when the airline fare is foreign currency, or the card can process in the original currency. Treasury should understand where FX cost sits before comparing the lodge programme with direct booking.

Set a monthly review of traveller names that no longer belong to current employees. Historic profiles can remain active in travel systems and create booking or fraud risk. Travel offboarding should remove booking access as well as corporate card permissions.