3815398 - Why wasn’t my booking ticketed after being made in Concur?

Concur functions solely as a booking tool, it does not have the automation or processes required to issue tickets. Once a reservation is completed, the booking information (PNR) is sent to the organization’s Travel Management Company (TMC), which handles ticketing.

If no ticket was issued, there are typically two possible scenarios:

1. The booking did not reach the TMC’s ticketing queue:
   In some cases, the PNR may not be transmitted correctly from Concur to the TMC’s ticketing system. When this happens, the booking never reaches the TMC for ticketing. In such situations, it is Concur’s responsibility to investigate why the PNR was not sent to the TMC’s ticketing queue.

2. The booking reached the TMC:
   Once Concur has successfully placed the booking to the TMC's configured ticketing queue, Concur's role in the booking process is complete. From that point onward, it is the TMC's responsibility to investigate any ticketing issues and to communicate any changes made to the PNR outside of Concur to the traveler.

You may find that your booking in Concur was successfully created but no ticket was issued afterward. This article explains how the ticketing process works, why Concur itself does not issue tickets, and how certain configuration or transmission issues in Concur could prevent your booking from reaching the Travel Management Company (TMC) for ticketing. , KBA , CON-CA , Cross Applications , Problem