Travel user update via Import file

[kimschutter]

Last year we implemented the file import in order to activate, deactivate and update a travel user. In concur itself this works great and we have little to no errors. We have a third party that connects to the concur data base and should receive all our changes automatically. 

We just found out the after we have updated a user profile, this change is not send to their system. Their feedback is that without a manual save in concur, they are not made aware of any updates. We have hundred of changes each months (with our latest reorganization it was in the thousands), which makes manually pressing a save button impossible. This is the entire reason why we have implemented the file import process. All updates have not been send to the third party which is causing incorrect approvals, incorrect invoices and bookings. 

Does any one have a similar experience and how did you solve it?

[KevinD]

@kimschutter could you maybe explain a bit more what the purpose of the third-party is? You mention incorrect approvals, invoices and bookings. Where are the these incorrect approvals, invoices and bookings occurring? Is it happening within SAP Concur or within the third-party application? I'm asking because if the updates are within the Concur system and the approvals, invoices and bookings are also taking place in the Concur system, how are the errors occurring? 

Just trying to clarify all the ways the third-party system interacts with Concur. 

[kimschutter]

The third party is used for more expensive and extended travels. They need all user data of our employees to be able to book the travels and they bill us. The sync all accounts to their database, this was a choice that was made a long time ago. 

The activation and deactivation of users via the import file are marked correctly via concur and recognized by the third party as such and imported. The updates however are not seen by their integrations and thus not updated in their database. 

They gave back that if we have made any changes to the user, we need to use the save button in the concur travel portal (per user) for the correct 'flag'.  The update we do is in line with the instruction we got from concur, and this part works smoothly (all concur data is correct). It's not feasible to manually save all users after an update, it also defeats the entire setup of automatically updating. 

[kimschutter · Accepted solution]

We got feedback from the third party partner, they missed a system update which meant they had to update some logic. They have now updated their process and it works again. Thank you for the quick response.