July - (25/17/18)

iOS

Date: 26/07/18
Version: 1.26.0

Visit the App Store to download the latest version

Bug Fixes

  • When a claim is split between multiple Cost Code Owners, each Cost Code Owner is responsible for approving the items which are assigned to their Cost Code. This issue allowed a Cost Code Owner to view and approve the entire claim, despite being split across multiple Cost Code Owners. This only occurred when the claimant was also one of the Cost Code Owners that the claim has been sent to for approval.

  • An error occurred when a user attempted to add a vehicle if they had selected a Vehicle Journey Rate. This was caused by incorrect Vehicle Journey Rates being displayed for the set Financial Year.

    This issue only occurred when two or more Financial Years were configured.

Android

Date: 25/07/18
Version: 1.26.0

Visit the Play Store to download the latest version

New

  • Vehicle Lookup - When adding a vehicle, users can now automatically populate the vehicle details by entering the registration number, making the process as effortless as possible. This service will be available as standard Expenses functionality and will incur no charge for using it. Enjoy!

Bug Fixes

  • When a claim is split between multiple Cost Code Owners, each Cost Code Owner is responsible for approving the items which are assigned to their Cost Code. This issue allowed a Cost Code Owner to view and approve the entire claim, despite being split across multiple Cost Code Owners. This only occurred when the claimant was also one of the Cost Code Owners that the claim has been sent to for approval.

  • Expenses Mobile crashed intermittently when attempting to add and save a meal or hotel expense.

  • When adding a receipt, the image intermittently failed to attach correctly and appeared blank. This only occurred when using HTC Desire devices.

  • An error occurred when a user attempted to add a vehicle if they had selected a Vehicle Journey Rate. This was caused by incorrect Vehicle Journey Rates being displayed for the set Financial Year.

    This issue only occurred when two or more Financial Years were configured.