DataServD
DataServ

2026.06 Release

Product Updates Bug Fixes 🐛
  • We resolved an issue that prevented the Next button from working when a user opened multiple documents. Users should be able to navigate documents without being blocked.

  • We addressed an issue where editing a deactivated user account could unintentionally reactivate that user. The system now correctly prevents changes to deactivated accounts, ensuring user status is preserved.

If you have any questions, please reach out to your Client Success Account Manager (CSAM) and / or DataServ Support.

2026.03 Release

Product Updates Bug Fixes 🐛
  • We fixed an issue where certain coding form fields were not staying disabled when adding a new line and using lookups. Fields that should be read-only now remain correctly disabled based on the selected Coding Type and related rules.

  • We fixed an issue where some users with non‑US English browser settings (like UK English) were seeing slightly different field labels than others. Now, all English users see the same default English text, no matter which English browser language they use.

If you have any questions, please reach out to your Client Success Account Manager (CSAM) and / or DataServ Support.

2026.02 Release

Product Updates Bug Fixes 🐛
  • We resolved an issue where some system messages in the Document Viewer were not displaying correctly in German and Spanish. Users on those languages will now see the proper translated text whenever these messages appear.

  • We fixed an issue where the Auto Coding feature sometimes applied the coding to the wrong document when a user had multiple documents open. Auto coding now applies to the correct document, helping ensure invoices are pre‑coded correctly and reducing manual adjustments.

  • We addressed an issue that could cause short pay behavior to be inconsistent in certain scenarios when processing invoices. Short pay details are now handled as expected, so users can more confidently review and approve short‑paid invoices.

  • We corrected an issue where some users received duplicate email notifications for payment requests. Each payment request will now generate only the appropriate single notification, reducing inbox noise and confusion.

If you have any questions, please reach out to your Client Success Account Manager (CSAM) and / or DataServ Support.

Welcome to DataServ Updates

We're launching our public feedback board to hear directly from you.

Here's what you can do:

  • Share ideas: Tell us what features you want to see

  • Vote: Help us prioritize what matters most

  • Stay updated: Follow along as we ship improvements

Your feedback shapes what we build next. We're listening!