Release Notes: March 11, 2026 This release includes a security update to password requirements in Emburse Enterprise, flexible mobile authentication options with Microsoft Intune and One-Time Passcode (OTP), a new AI-powered enhancement to car rental FOLIO capture, and expanded AI receipt capture for travel expenses. Together, these updates strengthen security, improve mobile access control, reduce manual entry, and enhance overall accuracy and audit readiness to deliver a more seamless customer experience.HighlightsUpdated Password Requirements: Strengthens account security with modern password standards and annual reset cadenceCar Rental FOLIO Capture: Automatically extracts and itemizes car rental charges using Emburse AI to reduce manual entryTravel Confirmation Data Autofill: Captures hotel confirmation numbers and airfare PNR from receipts to improve audit readiness and reduce manual entryFlexible Mobile Authentication: Configure Intune enforcement and OTP access for managed and unmanaged devices to align mobile security with your organization’s policiesPlans for ChangeSECURITYUpdated Password Requirements for Emburse EnterpriseAs part of our ongoing commitment to system security, we are updating our login password requirements to align with modern best practices. If you log in to Emburse Enterprise using a username and password (not single sign-on), the following password standards will apply when you reset your password: Passwords must be reset once every 365 days (previously 90 days) Password must contain at least 16 characters Password must contain at least one uppercase character Password must contain at least one lowercase character Password must contain at least one whole number (0–9) Password must contain at least one special character 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 These changes apply only when a user resets their password. Existing passwords are not affected.EXPENSEAI-Powered Car Rental FOLIO Capture and ItemizationEmburse is extending FOLIO capture, powered by Emburse AI, to support car rental folios. This upcoming enhancement builds on the existing Hotel FOLIO experience and will automatically extract and itemize car rental charges from uploaded folios.Eligible customers will be able to validate extracted line items before expense submission, reducing manual data entry and improving accuracy and consistency. After processing, the itemized folio will appear in the Receipt Gallery, and expenses created from these folios will follow the existing Hotel Folio workflow, including parent and child line item creation and required field population.Who Is Affected?Customers who already have a Car Rental FOLIO subscription with the feature enabled. If you have a Hotel FOLIO subscription but do not yet have Car Rental FOLIO enabled, you will be able to request activation. Contact your Emburse account executive, Customer Success Manager, or Emburse Solution Advisor to request activation. What Action Is Required? No action is required at this time. Eligible customers will receive an in-product announcement inviting them to begin testing once the capability becomes available in QA/UAT over the next few weeks. Deployment Schedule This capability will first be made available for testing in QA/UAT for customers with Car Rental FOLIO enabled. Customers with a Hotel FOLIO subscription may request Car Rental FOLIO enablement in QA/UAT if they would like to participate in testing. After the validation period, this capability will be rolled out to all eligible customers in Production in a future release.FeatureADMINFlexible Mobile Authentication With Intune and One-Time Passcode (OTP)The Emburse Enterprise mobile app now supports flexible authentication configurations for organizations using Microsoft Intune and/or One-Time Passcode (OTP). This enhancement allows you to align mobile access with your organization’s security and device management policies.Your organization can configure the app to support:Managed (corporate) devices secured with Microsoft Intune Unmanaged (personal or BYOD) devices using Single Sign-On (SSO) Unmanaged devices using One-Time Passcode (OTP) with receipt capture-only functionality A hybrid approach that combines these optionsSupported configuration scenarios include:Require Intune for all devices (managed and unmanaged)Use Intune for managed devices and SSO for personal devicesUse Intune for managed devices and OTP for personal devicesAllow unmanaged personal device users to choose between SSO and OTPEnable unmanaged devices to use OTP with a receipt-capture-only experienceAuthentication behavior is determined by your organization’s configured mobile security policy.Who Is Affected?Organizations using the Emburse Enterprise mobile app who require differentiated authentication controls for managed and unmanaged devices.Action RequiredNo action is required for end users. All configuration is handled by Emburse Support.To update your mobile authentication configuration, contact your Customer Success Manager or submit a Support ticket.ImprovementEXPENSEAI-Enhanced Receipt Capture: Additional Travel Identifiers AutofilledEmburse Enterprise now captures and autofills hotel confirmation numbers and airfare Passenger Name Records (PNR) directly from uploaded receipts. This enhancement improves travel expense tracking, strengthens audit readiness, and reduces the need for manual entry of critical booking identifiers.Emburse AI extracts structured data during receipt upload and populates available expense fields automatically. This helps ensure greater consistency across reports and minimizes submission errors.This update introduces AI-based autofill for the following travel identifiers:Hotel Confirmation NumberAirfare Passenger Name Record (PNR)AvailabilityThese AI enhancements are live for most customers. If these fields are not yet visible in your organization’s interface, contact your Emburse representative or submit a Support request for enablement. Was this article helpful? Yes No