3818067 - PNR Acquisition - Why is a booking not syncing to Concur Travel? - Hub Article

This is a hub (main) article about issues (unexpected behavior) with PNR Acquisition. It shows available knowledge articles about this topic.
Before using this article we suggest reviewing What is PNR Acquisition? 

Examples of PNR Acquisition issues could be:
- offline PNR does not appear in Concur Travel (reports, user's trip library)
- offline PNR appears in Concur Travel, but has wrong or missing data (tickets, costs, names, remarks)
- offline PNR was changed by travel agency, but changes are not visible in Concur Travel
- PNR does not have expected status (Ticketed, Withdrawn etc.)
- offline trip does not show in traveler's trip library, but show in trip library of another user
- PNR import doesn't start, takes too long or is delayed
- single or multiple PNR fail to be imported
- unexpected queuing done by Concur Travel

Hub article about unexpected behavior of PNR Acquisition process , KBA , CON-SRV-TRV-SUP-PAC , PNR Acquisition , Problem