This content from the SAP Concur Community was machine translated for your convenience. SAP does not provide any guarantee regarding the correctness or completeness of this machine translated text. View original text custom.banner_survey_translated_text
We're only a couple of months into Concur deployment, but are seeing a few queries from front-end users on the 'Deduct Commute' tick box in the Mileage Calculator pulling through incorrect addresses.
Our set up is that the home/office address of each employee should be stored in their Concur record, having been passed across via interface from our SAP HR system on SFTP Employee file (350 records) for which changes are sent daily.
I have at least two documented cases where when I checked the employee's profile in Concur the address is correct and matches the HR system, but when they open the mileage calculator and click the 'Deduct Commute' button, it pulls through a completely different address with the same street number/name and city, but completely different postcode.
I've tested manually inputting the address stored in Concur into the mileage calculator and the correct address is recognised, so it can't be an issue with Google Maps not recognising the address, since it is recognised when input (as opposed to being pulled through when the 'Deduct Commute' button is ticked).
It seems like the issue is with how the Mileage Calculator 'reads' the address data, so it's finding a match with the street number/name and city, but not validating against the postcode and therefore returning an address that doesn't actually match what's stored in Concur.
Has anyone else experienced this issue, or know of any workarounds that would fix? We are trying to avoid telling employees to manually overwrite addresses in the Mileage Calculator if possible, as we're trying to ensure a good user experience and with a large user base would rather avoid telling people to manually edit their addresses.
This content from the SAP Concur Community was machine translated for your convenience. SAP does not provide any guarantee regarding the correctness or completeness of this machine translated text. View original text custom.banner_survey_translated_text
@LukeWood when a user ticks the Deduct Commute checkbox, is the route from the user's home to one of your company's offices? I'm trying to get the full picture here.
This content from the SAP Concur Community was machine translated for your convenience. SAP does not provide any guarantee regarding the correctness or completeness of this machine translated text. View original text custom.banner_survey_translated_text
Hi Kevin
Yes - the relevant home and office address is sourced within our HR System and passed across via the 350 record into Concur (which I can view and validate via User Admin - but only if I put a temporary tick in the 'Travel Wizard User' box).
When an employee makes a mileage expense entry they should open the 'Mileage Calculator' and tick the 'Deduct Commute' tickbox, which should populate the address values into the Home/Office fields and calculate the commute, to be removed from the total mileage in line with our policy.
We've had a couple of issues where the addresses are not recognised within Google Maps, so understand the workaround for that (add the missing place in Google directly), but in the two documented cases the addresses stored in our HR system and the user's profile in Concur are recognised when input directly into Google Maps via browser. It's only when they are auto-populated via clicking the 'Deduct Commute' box where the user's address is coming through as a different address location (like I say - seems to be if a city/town has two different addresses where the street name/number is the same, but the postcode is different, it is picking the 'wrong' one, rather than using the postcode to validate and pick the 'right' one).
Hopefully that makes sense but let me know if you need any other info.
Thanks
Luke