Skip to main content

Varicent ELT Assistant

Release notes 3.91.0

Week of April 2026

It’s still here, but it’s different.

We took the time to revamp some of the things you already love.

New Workday connector enhancement for Supplier Payee integration

We're excited to announce an enhancement to our Workday Connector, focusing on the Supplier Payee integration. This update expands our capabilities by enabling the import of supplier data via the Get_Suppliers endpoint.

Now you can seamlessly import essential supplier information, including Supplier ID, Supplier Name, Tax ID, and Payment Terms. This enhancement is particularly beneficial for scenarios involving brokers, agents, or third-party suppliers, enabling accurate commission calculations and streamlined payment processes.

Additionally, the export functionality has been improved to support the submission of supplier invoices back to Workday, ensuring a smooth financial workflow. We've also implemented robust error handling and data validation to ensure data integrity and provide clear notifications in case of any issues. This update is designed to enhance your financial management processes and improve overall efficiency. For more information, read the GET Workday Suppliers endpoint documentation.

Improved configuration guidance for the Workday RaaS connector

We've been busy! To reduce configuration errors and support requests during Workday Reports-as-a-Service (RaaS) connector setup, contextual help has been added to the Connect to your Report page.

Previously, the Workday RaaS configuration page provided no contextual guidance on which Workday credentials to enter or how to correctly format the Report URL.

What's new? Tooltip icons (ℹ) now appear next to the following fields on the Workday RaaS configuration page:

  • Username: Now displays the following guidance: "The username for the Workday account of the user who owns or created the custom report."

  • Password: Now displays the following guidance: "The password for the Workday account of the user who owns or created the custom report."

  • Report URL: Now displays the following guidance and example: "The Report URL will look like the following format:https://<host>/ccx/service/customreport2/<tenant>/<username>/<report_name>. For example: https://wd2-impl-services1.workday.com/ccx/service/customreport2/mycompany/ISU_Integration_User/My_Custom_Report

For more information, see the Workday RaaS documentation.

New tooltips and links for the Workday connector

We're on a roll! We've added tooltips with guidance to the Workday connector setup, to the Connect to your Database step of the configuration.

Previously, we found that users were unsure how to locate their Workday domain, what constitutes a tenant name, or which credentials to use, leading to failed configurations and increased support requests. The new tooltips and documentation links surface the right information directly in the UI at the point of need.

We've added the following tooltips to the following fields on the Workday configuration page:

  • Domain: Now displays the following guidance: "The base URL of your Workday environment, such as wd5-services1. To find the base URL, go to your Workday account and search for "Public Web Services".

  • Tenant: Now displays the following guidance: "Your Workday tenant name, which is the unique identifier for your organization's Workday instance. For example, mycompany."

  • Username: Now displays the following guidance: "The username of the Integration System User (ISU) that is set up in Workday for this integration. For example, ISU_Integration_User@mycompany."

  • Password: Now displays the following guidance: "The ISU account password. We recommend using a dedicated ISU with only the permissions required for this integration."

For more information, see the Workday import connector documentation.

Clearer error message for SFTP imports with missing Modification Detection Code (MDC) encryption

We've done it again! We've crafted a clearer error message for SFTP imports. When an SFTP import fails because the source file is encrypted without a Modification Detection Code (MDC), users now see a specific, actionable error message instead of a generic decryption failure message.

The original generic error message gave users no indication that the issue was MDC-related. The updated message clearly identifies the cause and tells users exactly what to do to resolve it:

Sorry, we couldn't import the encrypted file from SFTP because MDC (Modification Detection Code) wasn't enabled during encryption. Please encrypt the file with MDC enabled, and try again.

For more information, see the SFTP import connector documentation.

We crushed some bugs!

And we're so happy that we did...

Issue

Bug number

Fixed an issue where SFTP imports of PGP-encrypted files lacking Modification Detection Code (MDC) would fail with a generic decryption error instead of a descriptive message indicating the root cause.

226919

Fixed an issue in the Management Portal where domain names containing a hyphen (-) were incorrectly rejected during IDP (Identity Provider) SSO configuration creation.

224295

Fixed an issue where the password login field remained visible on the login page for organizations with SSO enabled and username/password authentication inactive.

225561