Problem
When an employee creates a GPS mileage expense, if the recorded trip has an inaccurate stop destination (e.g., forgot to stop), then they have to recreate the expense using manual mileage or a re-drawn map route, which is harder to reproduce accurately and provides weaker supporting documentation for approvers and auditors.
Solution
In one release, we will:
- Make the stop address a push row
- Show an “Edit stop” page, with a map and a slider below
- Users can drag the slider to decrease the distance, which is animated on the map
- Where ever the users stops the slider and confirms, we save that stop address when creating the expense (and updating the mileage receipt).
Further details
- We'll start saving GPS way points in the BE, which means storing the
gpsCoordinates in the commentNVPs (where we currently store existing distance data like routeImageURL and odometer readings).
- We'll also start saving any mileage decreases via
modifiedDistance, similar to modifiedCreated, modifiedAmount, modifiedMerchant and modifiedMCC.
This is an internal initiative, so we won't open it up to proposals
Issue Owner
Current Issue Owner: @GCyganek
Problem
When an employee creates a GPS mileage expense, if the recorded trip has an inaccurate stop destination (e.g., forgot to stop), then they have to recreate the expense using manual mileage or a re-drawn map route, which is harder to reproduce accurately and provides weaker supporting documentation for approvers and auditors.
Solution
In one release, we will:
Further details
gpsCoordinatesin thecommentNVPs(where we currently store existing distance data likerouteImageURLandodometerreadings).modifiedDistance, similar tomodifiedCreated,modifiedAmount,modifiedMerchantandmodifiedMCC.This is an internal initiative, so we won't open it up to proposals
Issue Owner
Current Issue Owner: @GCyganek