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.
