Deduct commute - route used by google maps and cannot be changed

[Maz]

Hi, just wondered if anyone else is finding it frustrating that the map uses the shortest and the fastest route determined by Google Maps at the time the route is calculated?

We have found quite often our employees use a different route but we are unable to tell Concur to ignore that route so that we can add our own.

I raised a customer influencer request but it wasn't voted on! 🙃

The workaround we received from Concur Support was to include the commute distance as separate waypoints to mark the commute distance as Personal (so that it will not be included in the business mileage total) instead of using the Deduct Commute. 

Usual waypoints (blue lines) can be dragged, but deduct commute routes (red lines) cannot.

It would be nice to have the option to override this

[KevinD]

@Maz this one is a bit tricky since the mileage calculator is powered by Google, so we don't really have control over the behavior of the map. 

[gstevens]

Google Map functionality can identify both the shortest and quickest routes which may not be the same.  Often Concur appears to be defaulting to the quickest whereas users would prefer it to be shortest to ensure they don't lose out on the mileage reimbursement they are entitled to

Within the Google maps API, the route selection can be determined considering vehicle type, tolls, time of day and even live traffic information for example, and it would be interesting to know which have been applied to the default for the Commute deduction.

Selecting the shortest route is an option within Google Map functionality but it doesn't look like this is configured in Concur's application of the API.

Concur does already identify route options when adding a trip manually and allows the user to click and drag the route to reflect the actual trip taken.  Beyond changing the defaults, replicating this functionality would allow users to correct the commute if it is calculated incorrectly.