Zetadocs Expenses

The Zetadocs Expenses service is now accessible again from all locations.

The Zetadocs Expenses service is currently unavailable.  Attempting to display the Zetadocs Expenses client site or admin site from a desktop browser fails with an error similar to "Site expenses.zetadocs.com cannot be reached".  Expenses can still be created using the mobile app, but any changes will not be saved to the server and the app will indicate that there are unsaved changes.

The issue was caused by a system failure at the company which manages the Internet DNS records for the expenses.zetadocs.com domain.  They are working urgently to rectify the issue, and we will update this status as soon as we have more information about the likely resolution time.

Once the site is available any changes made using the Zetadocs Expenses mobile app or the desktop browser client will be saved automatically when the app is next used, provided the user has not signed out of the mobile app or closed the browser window in the meantime.  However we recommend that users do not create expenses until the fault is corrected.

We have corrected an issue which caused export to fail on systems using multiple companies.

The issue affected reports which were queued for export between 7th March and 9th March.  If you are using a Zetadocs Expenses system which is connected to two or more Business Central companies we recommend that you check whether any reports have been affected by this issue then export them again. 

To check for any affected reports, sign into the desktop client app as a user with the finance processor role, display the Status page, then set the filter to show approved reports awaiting export.  To export the reports, select all reports on the page then choose Export from the three-dots menu in the top right hand corner of the page.

We apologise for any inconvenience that this issue has caused for you or your organisation.

There is an issue with exporting reports to Business Central which affects systems with two or more companies.  Reports which only include expenses for the master company are exported correctly.  However if a report includes expenses for any other company the export operation fails and the report history shows an error similar to the following:

• Error exporting expense ID xxx.  Unexpected failure during export.  Unable to parse export code '' into Shortcut index and Code.  [ERR_ParseShortIndCode]

We have identified the cause of the issue, and we are working on a fix which we expect to release by 1700 GMT / 1200 EST on Thursday 10th March.