Universal Update: Country Field Optional in HR Data Integration

What's changing & how will it work?

We have updated our HR Data Management process to offer additional flexibility to tenants. If you choose to opt-in to this update, the Country field will no longer be required in HR data files when creating users via HR data load. If a user’s country is blank in your HR data file or not in your system’s country list, the user will be created without populating the Country field. If you choose to leave this option off, the Country field will remain required, and users will not be created if they do not have a country in the data file.

All other HR fields, such as manager, name, email, etc., will be loaded as normal. A user’s country can be updated manually in the Master Data or via another HR data load. If a later HR data file includes a blank or unrecognized country, the user’s country will not be updated. However, we recommend updating the country in HR data files, so they remain the source of truth.

By opting-in to this update, tenants may see users submit requests without a Country value. If your approval flow or User Access Policies rely on the Country field, this may impact approval flow triggering or access to requests, dashboards, and data. 

Why are we making this change?

This option ensures that blank or invalid country data does not block creating users. However, we recommend populating the country in HR data files whenever possible.

Who is affected?

This update is optional and does not automatically impact tenants. By default, the Country field is still required. Tenants can choose to opt-in. 

Approvals & Disclosures: Improved Campaign Reminder Email Experience 

What's changing?

Campaigns will now more consistently follow their configured end date across reminders, request access, and user interactions. Once a Campaign has ended, reminder activity will stop, and users will no longer be able to create, edit, save, or submit Campaign requests.

The update also improves the messages shown when a Campaign has expired or when a user attempts to access an invite-only Campaign to which they are not assigned. 

How will it work?

When a Campaign reaches its end date or becomes inactive:

• Campaign-related reminders will stop automatically.
• Applicable Campaign items will be removed from Action Items and the reminder set.
• Existing request records will be retained for audit, reporting, Insights, and other authorized views.
• New or Draft Campaign requests opened after expiration will be displayed as read-only. Users will not be able to edit, save as draft, or submit them.
• Users attempting to access an expired Campaign will see a clear message explaining that the Campaign is no longer active.

If a Campaign end date is later extended to a future date, eligible Action Items and reminders will automatically resume based on the Campaign’s original reminder configuration. Campaigns created with reminders disabled will continue to respect that setting when the Campaign is extended.

Administrators and other authorized users will continue to have access to expired Campaign data for review, audit, and reporting purposes. 

Why are we making this change?

Previously, Campaign reminders could continue after a Campaign expired, and users could enter request workflows even though they could no longer successfully complete the request.  

These enhancements align reminders and request interactions with the Campaign lifecycle, reduce unnecessary notifications and manual cleanup, protect Campaign data from changes after expiration, and provide clearer guidance when a Campaign is no longer available. 

Who is affected?

This change affects organizations using Campaigns within Approvals & Disclosures, including Annual Conflict of Interest (ACOI) Campaigns.

Campaign participants will see updated behavior for reminders and expired Campaign requests, while Campaign Administrators and authorized reporting users will retain access to historical Campaign information. 

Compliance Monitoring: Custom Fields in Transaction Details

What's changing?

Custom fields configured for Compliance Monitoring can now be displayed directly on the Transaction Details page. This enhancement applies across all Compliance Monitoring domains, including Employee Spend, HCX Spend, Vendor Spend, and Customer Revenue.

Please note that custom fields are not currently available in Compliance Monitoring dashboards. 

How will it work?

When custom field information is available and has been configured for display, users will see a new Custom Fields section in Transaction Details. Custom fields are organized by their associated entity and display the field name and corresponding value. If multiple records exist for the same entity, the records will be grouped separately for easier review. The Custom Fields section will only appear when populated custom field values are available for the selected transaction.

This enhancement will initially apply to customers who add new custom fields to their Compliance Monitoring data. Existing customers who already use custom fields will not see any immediate changes as part of this release. Their existing custom field data will be updated to support this functionality through a future configuration and data update. 

Why are we making this change?

Previously, customer-specific attributes could be available within the underlying Compliance Monitoring data without being readily visible when reviewing an individual transaction. Surfacing custom fields in Transaction Details gives reviewers additional business and source-system context directly within their existing review workflow. 

Who is affected?

This release initially affects Compliance Monitoring customers who add or configure new custom fields in their data. Customers who already provide custom fields will continue to use their existing configuration without change. These customers will receive the new Transaction Details functionality at a later date once the required updates have been applied to their data. 

Compliance Monitoring: Employee Spend Approver Information

What's changing?

Approver information is now displayed in the Transaction Details page for Employee Spend transactions, giving reviewers additional context about the approval of an expense in the source system. 

How will it work?

When approver information is available, the existing Approvers field in Transaction Details will display the First Approved Date along with any other available approver details, such as the Source System Approver ID, Approver Name, and Approval Type. If multiple approvers are associated with the transaction, each approver will be displayed on a separate line. If approver information is not provided for a transaction, the field will display No Approver Information.

Please note that approver information is currently available for the Employee Spend domain only. 

Why are we making this change?

Displaying approver information directly in Transaction Details gives reviewers additional context about the approval history of an expense without requiring them to reference the original source system. This can help users better understand the circumstances surrounding a transaction when conducting compliance reviews. 

Who is affected?

This change affects Compliance Monitoring customers using the Employee Spend domain. The amount of approver information displayed will depend on the information provided by the customer's source system. 

Compliance Monitoring: Data Processing Performance and Reliability Improvements

What's changing & how will it work?

We have updated a core orchestration workflow used to support Compliance Monitoring data processing. This update improves how underlying processing activities are coordinated and executed, providing greater performance, reliability, and stability across Compliance Monitoring data workflows.

These improvements occur behind the scenes and do not change how users interact with Compliance Monitoring or require any user action.

Why are we making this change?

This update modernizes the underlying infrastructure supporting Compliance Monitoring and provides a more reliable and scalable foundation for data processing. It will help improve processing efficiency and stability while better supporting growing data volumes and future enhancements.

Who is affected?

This backend update applies to all Compliance Monitoring customers. No changes to existing user workflows or configurations are required. 

Reporting Insights: New Filters in Questionnaire Explorer Dashboard

What's changing & how will it work?

We have added the Completed Date and Primary Activity Status fields as filters to the Questionnaire Explorer Dashboard. Analysts can now use these in the filter menu to filter question and response data by the questionnaire Completed Date and Primary Activity Status.

Who is affected?

This dashboard is available to all Approvals & Disclosures, Third-Party Management, or Live Monitoring customers.