This article describes the new features and other improvements in the July 2026 update of the Zetadocs Expenses service.

Changes in this update

Feature enhancements

This release contains the following enhancements:

Require start and destination for mileage expenses

It is now possible to require users to enter a valid start and destination point on mileage expenses, rather than being optional. This means mileage is always calculated accurately using Google Maps. This new setting sits alongside the existing mileage limit settings, that all help to prevent the submission of mileage expenses that are inaccurate and/or breach company policy.

Warning if expenses have tax reclaim selected but no receipts are attached

Users are now presented with a warning against the VAT/Tax Reclaimable field if a tax amount is specified in the expense, but no corroborating evidence, in the form of a receipt, is attached.

Quality and performance improvements

This update includes various improvements including the following:

Not all bank feed transactions are fetched if multiple payment methods are updated in quick succession

Resolved an issue with concurrent bank feed fetches. Transactions are fetched from the bank feed when a payment method is updated. There was an issue where if too many payment methods are updated in quick succession, then some bank feeds do not have their transactions fetched. This has now been fixed.

Disabled users able to approve reports via email links

Fixed an issue where disabled users could still approve reports that have not yet had tasks re-assigned, if they click into the Zetadocs Expenses client from an email link.

Incorrect date format used when editing mileage rates for Canadian and US companies

Corrected display behavior on the mileage rates edit settings screen, where the date format can be displayed in UK format. This also prevented saving any changes to mileage rates in certain circumstances.

Some numeric input fields allow unlimited number of decimal places

Adjusted behaviour of input fields so that they only accept numeric input of at most 2 decimal places.

'The expense amount is greater than the transaction amount' error when matching expenses to transactions, when the transaction amount is greater

Changed the error messaging to avoid confusion. The error now reads 'The expense amount is different to the transaction amount'.

'You are not authorized to view the page you requested' error after editing reports

Fixed a bug where the error 'You are not authorized to view the page you requested' pops up on the bottom right of the screen. This would occur when certain validation checks are made on the associated expenses or report, but where users may not have permissions to edit the associated report or expense at the time.

Additional information

Extension for Business Central

This release is compatible with all previous versions of the Extension for Business Central. However, if you are using a previous version, we recommend that you upgrade to the latest version to benefit from stability and performance improvements.

NAV Server Components

This release is compatible with previous versions of the NAV Server Components (versions 3.4.24081 and later).

Mobile apps

Installed mobile apps will be updated automatically on mobile devices where this is enabled.