Modifying Travel in Concur Travel

[Burger1950]

Currently, our travel policy directs employees to make in-flight itinerary changes through our travel agency rather than through Concur Travel. However, we have a small group of executives who occasionally need to change their return flights on short notice and would prefer to manage those changes directly instead of calling the agency.

I'm interested in how other companies handle this. Do organizations typically allow certain travelers, such as executives or frequent travelers, to make airline changes directly through the airline's app or Concur app while maintaining corporate travel compliance? Or do most companies require all itinerary changes to go through their travel management company?

[KevinD]

@Burger1950 From what I see, the ability to do post-ticketing changes is activated for a Travel Configuration and not a Travel Group/Rule class. So, this would be an all or nothing type setting. In other words, it couldn't be allowed for some travelers and not others. Now if your company has multiple travel configurations and your execs and frequent travelers were all in on configuration, this could work for you. 

[Burger1950]

Can a traveler modify the return flight in Concur? Does Concur allow that capability?

[KevinD]

@Burger1950 are you talking about modifying the return flight after the traveler has flown the outbound or are you talking about modifying the the return flight before traveling?

[Burger1950]

Both scenarios 

[KevinD]

@Burger1950 I'm not certain on changing the return within Concur Travel after having taken the outbound flight. 

We do have an option to allow for changing flights before traveling, but it is a feature that must be turned on. To see if your company allows this, you can call your company's travel agency. They should be able to tell you.

[samasuraj]

Hi @Burger1950 

Topic: Modifying Travel in Concur Travel

Please check the below. Hope this helps.

-----

SAP Concur supports post-ticketing flight changes for eligible bookings when the functionality is enabled and depends on the Travel Configuration, Airline/GDS, Ticket Status, Company Policy & TMC.

Key considerations:

• Concur Travel: Post-ticketing changes depend on airline, booking eligibility, and Travel configuration.
• Airline Apps: Direct changes may not automatically synchronize with Concur or the TMC.
• Compliance: Ensure updated itineraries, additional costs, and duty-of-care tracking are maintained.

For Executive-Only Access: SAP Concur has confirmed that post-ticketing changes are controlled at the Travel Configuration level, not by Travel Group or Rule Class. A separate Travel Configuration for executives may therefore be an option.

Important distinction:

• Before departure: Eligible ticketed flights may be changed in Concur if the feature is enabled.
• After the outbound flight: Changing only the return flight must be confirmed with the TMC, as support for this scenario is not guaranteed.
• Airline app: Changes made directly with the airline may not automatically synchronize with Concur or the TMC.

Recommendation: Keep the TMC as the default servicing channel and evaluate a separate executive configuration for supported self-service changes, ensuring itinerary updates and duty-of-care requirements are maintained.

Important: Post-ticketing changes are enabled at the Travel Configuration level, not individually through Travel Groups or Rule Classes. A separate Travel Configuration for executives may be an option.

For changes made directly through airline apps, the TMC should confirm that the revised itinerary and ticket information are updated in corporate travel systems.

This is supported by SAP Concur's TMC Setup Guide

Thanks & Regards

--

Samantha Prathikantam

SF_EC & ECP / SAP Concur Consultant