HI Sally,

We use the legal name only - they can put preferred name in the nickname field. However, I feel switching it back and forth leaves too much room for ticketing with an incorrect name and issues if the traveler doesn't check until the day of travel. If a travel agent is assisting - it could be too much back and forth. We require that the name in Concur must match the name of the traveler's government issued ID used when traveling.

Hope this helps,

Sabrina

Hi Sally~
We use SSO for Concur login and the legal first, last, and middle name is pre-populated into the name fields in Concur. They are greyed out so the user is unable to change them. They can add a nickname, but for all official purposes and ticketing in the Concur system and any interaction with the traditional agent, the default is the legal name that is pre-populated. We also have this verbiage as an alert on the page:

**Your Name and Airport Security: Please make certain that the first, middle, and last names shown below are identical to those on the photo identification that you will be presenting at the airport. Due to increased airport security, you may be turned away at the gate if the name on your identification does not match the name on your ticket. Changes to your legal name must be routed through HR/Workday for approval.**

Best,

Tresa

Sally,

We are only populating First and Last names in our HR feed because we know that the name on file with HR does not always exactly match the traveler's name as it appears on the photo ID which they use for travel (especially if the name is different between their Drivers License and Passport). We have the same message in our Profiles that Tresa does except we currently have name fields open for editing. Since we're still in the implementation phase, we've left the fields open for now but will likely change that over time. As Sabrina mentioned, we also recommend using the Nickname field for preferred names.

Thanks,
Rebecca

We also have that message, but we allow them to add the middle name and save one time. This is because the information is often incorrect from the HR feed. We don't use preferred names in Travel profiles, that is only noted on their central profile.

We also have that message, but we allow them to add the middle name and save one time. This is because the information is often incorrect from the HR feed. We don't use preferred names in Travel profiles, that is only noted on their central profile.

To add, the reason we don't allow them to change their first and last name, is because, if that is wrong it needs to be corrected formally. When certain HR feeds happen, it's possible the changed name can be overwritten and changed back. When this has happened, the traveler is usually unaware and it causes problems. This hasn't happened recently and the middle name was not affected.

Update on this topic: a slated Concur release beginning in Q1 2022 to their displayed name in the system to factor in the "Nickname" field in the profile: http://www.concurtraining.com/customers/tech_pubs/RN_shared_planned/2022/Shared_RN_2022_1(Jan)_all_Client_FINAL.pdf See pages 11-12.