Release Notes: June 11, 2025 Note: We may roll out certain changes iteratively through our customer base. As a result, you may experience a few days’ delay (no more than one week) before you see new functionality in your Production environment.New Feature AvailableINVOICECustomer Address Enhancement for the Default Invoice TemplateCustomers who serve multiple billing or shipping locations under the same customer entity (CustomerAddress1) but need to distinguish among them using CustomerAddress2 (e.g., suite numbers, department names, or internal routing codes) may now use the Default Invoice Template to create templates with the same CustomerAddress1 but a unique CustomerAddress2. This allows your organization more flexibility in managing invoice templates for customers with multiple sub-addresses. If your organization is interested in taking advantage of this new feature, please open a support ticket.EnhancementsUSER INTERFACENew Login Password Requirements for Non-SSO UsersAs part of our ongoing commitment to system security, we are updating our login password requirements to align with modern best practices. For customers whose users log in to Emburse Enterprise with a username and password instead of using Single Sign-On, the following new password standards will apply the next time users reset their password. Minimum of 8 characters Username cannot be included in the password No character may repeat more than 3 times in a row Commonly breached passwords are not allowed Any form of the word password (e.g., p@ssword, passw0rd) is prohibited Users’ existing passwords will not be affected; they will only need to comply with the new requirements the next time they reset their password. We will also review custom password policies currently in use. If your organization’s configuration does not meet the new minimum standard, our team may contact you to assist with updates.EMBURSE ANALYTICSEmburse Connect for Analytics Snowflake Client Driver DeprecationFor Emburse Enterprise customers who extract data directly out of the Emburse Data Warehouse into their own reporting environments, our data warehouse vendor, Snowflake, will be deprecating older clients for connecting to the warehouse at the end of July 2025. Based on the Snowflake Support policy, any client driver version lower than those listed below will no longer be supported beginning August 1, 2025. Snowflake SnowSQL 1.2.32 Snowflake Python Connector 3.1.0 Snowflake JDBC Driver 3.14.0 Snowflake ODBC Driver 3.0.2 Snowflake Node.JS Driver 1.7.0 Snowflake Go Driver 1.6.23 Snowflake .NET Driver 2.1.0 Snowflake SQLAlchemy Driver 1.4.7 Snowflake PHP PDO 1.2.7 Snowflake Kafka 2.0.0 Snowflake Spark 2.12.0 We recommend all customers upgrade to the latest version of the relevant Snowflake driver to take advantage of important fixes and enhancements to security, performance, and other functions. Snowflake will not be able to assist with any issues related to versions that are no longer supported. To check the driver version in use, you may now view the driver version information on the Query History tab under the Client Info column. Further details can be found on the Snowflake Client Version & Support Policy page.Emburse Connect for Analytics: Multi-Factor Authentication EnabledWe have rolled out an important security update to Emburse Connect for Analytics. Multi-factor authentication (MFA) is now mandatory for all users accessing the application with a password. Service accounts are exempt from this requirement. Snowflake utilizes Duo Security for MFA, which requires setup on a mobile device. For details on Duo setup, please visit https://guide.duo.com/. Please note an additional security change coming up on September 16th, 2025: Key-pair authentication will become mandatory for all service accounts on this date. We will coordinate with you directly to configure existing service accounts for this authentication method. Additional information can be found here.New Open Button in Content Action MenuUsers may now open a folder, dashboard or report by selecting Open from the action menu next to the item. You may still open any item by double-clicking on it; the Open action is just another way to get to the same content.Exported By Person Fields Added to Enterprise Expense ModelsUsers may now report on the Exported By Person fields, which track who initiated the export process. When creating or editing a report, you will find the new fields in the Expense Line Allocation Export folder.PO Line Person Fields Added to Enterprise Purchase Order ModelsIf your organization has configured a person selector on PO line items, users may now report on the person selected. When creating or editing a report, you will find the new fields in the PO Line Person folder.Role Description Field Added to Enterprise Person Reference ModelUsers may now include the Role Description field when reporting against the Person model. Depending on your organization’s unique configuration, the Role Description field can sometimes provide a better context than the Role Name field. When creating or editing a report using the Person model, you will find the new field in the Person Entities folder.ADMINChangeset Manager Validation EnhancementOver the next few weeks we will be rolling out enhancements to the Changeset Manager. When changesets are published, we will now perform a number of validations to ensure that your configuration does not contain issues that may result in unexpected behavior. Admins will not be allowed to complete the publish until any validation issues identified are resolved. For a complete list of validations, see Create and Publish Changesets in the Emburse Enterprise Help Center. Was this article helpful? Yes No