Executive Summary

1. New and Updated Features
2. Fixed Bugs
3. New Known Bugs

1. New and Updated Features

AP Helpdesk: Oracle Fusion Field Mapping Implementation

This release adds support for Oracle Fusion Cloud Financials as a source ERP for AP Helpdesk. Tenants on Oracle Fusion can now use AP Helpdesk to look up and act on vendor, invoice, purchase order, and payment information sourced from their Oracle environment.

AP Helpdesk agents can respond to supplier inquiries about invoice status, payment status, purchase order details, and vendor information using live data from Oracle Fusion. Document and payment statuses are presented in standard Auditoria terminology, so users see consistent status values regardless of the source ERP.

What's New

• Vendor lookups: AP Helpdesk can retrieve supplier master data and supplier contacts from Oracle Fusion.

• Invoice lookups: AP Helpdesk can retrieve invoice headers and line-item details from Oracle Fusion.

• Purchase order lookups: AP Helpdesk can retrieve purchase order headers and line-item detail from Oracle Fusion.

• Payment lookups: AP Helpdesk can retrieve payment headers and line-item details from Oracle Fusion.

• Standardized status display: Oracle Fusion bill, purchase order, and payment statuses are presented in standard Auditoria terminology, with tenant-level configuration available for status variations.

• Derived amounts: AP Helpdesk displays Amount Remaining (Total Amount minus Amount Paid) and Net Amount (Total Amount minus Total Tax) for Oracle Fusion documents.

Note: This feature applies to tenants integrated with Oracle Fusion Cloud Financials.

This feature is available in Limited Availability (LA) and may be enabled on request. If you are interested in enabling this feature, please contact your Customer Success Manager or our support team at support@auditoria.ai.

AP/AR Helpdesk: Intent-Mapped Conditional Task Dismissal

This release adds the ability to auto-dismiss helpdesk tasks when an email has a single, high-confidence detected intent and is not flagged as high-importance by the sender. The capability applies to selected business intents and macro intents. AP Helpdesk also supports a sender-type condition for System Senders. The objective is to reduce review tasks that customers have indicated are not required, while preserving a recovery path for cases where a task needs to be reopened.

A new task status, Dismissed, is introduced. When a task is auto-dismissed, the assignee is set to None. Users can recover a dismissed task by changing its status to Open or by assigning it to a user. When Automatic Task Distribution (ATD) is configured, a dismissed task that is recovered through a status-only change is automatically assigned per ATD rules.

What's New

• Conditional Task Dismissal setting: A new Conditional Task Dismissal option in SmartFlow settings enables auto-dismissal and exposes the list of qualifying intents. Tasks are automatically added and dismissed without assignment for email messages that match the selected intents. Dismissed tasks can be assigned and reopened for additional handling.
• AR Helpdesk intents supported for auto-dismissal: Out-of-Office Response, Bounce-back Response, Acknowledgment (macro intent), and Unintelligible (macro intent).
• AP Helpdesk intents supported: Invoice Submission, Credit Memo Submission, Acknowledgment (macro intent), and Unintelligible (macro intent) can be selected for auto-dismissal.
• System Sender dismissal setting (AP Helpdesk): A separate "Dismiss system sender email message tasks with selected intents" option, available under Tasks for System Senders, conditionally dismisses tasks for Invoice Submission and Credit Memo Submission only when the sender type is System Sender.
• High-importance exclusion: Tasks are auto-dismissed only when the email has a single, high-confidence detected intent and is not flagged as high-importance by the sender.

• New Dismissed task status: Auto-dismissed tasks display a Dismissed status indicator in the Tasks tab and mailbox, and the assignee is set to None.

  

  

• Status filter support: The Task Status filter in the Tasks tab and mailbox includes Dismissed alongside New, Open, and Done, allowing users to view dismissed tasks.

  

• Task recovery from task details: An Open action is available for dismissed tasks, allowing a user to change the status from Dismissed to Open.
• Bulk recovery from Tasks tab: A Recover Dismissed Task(s) action in the Action menu changes status from Dismissed to Open for multiple selected tasks.

• Bulk assignment includes dismissed tasks: The Assign Task(s) action in the Action menu supports New, Open, and Dismissed tasks, so dismissed tasks can be assigned in bulk.

  

• Recovery through assignment: Assigning a task to an assignee changes its status from Dismissed to Open. Using Assign to Me assigns the task to the current user.
• ATD invocation on recovery: When ATD is configured, tasks recovered through a status-only change from Dismissed to Open are automatically assigned per ATD rules.
• Reporting: Dismissed task volume is included in the Agent Processing Outcomes CSV from the dashboard.

Notes

• Dismissed tasks are hidden from the Tasks tab by default. To view them, clear filters or select Dismissed under the Status column filter.
• Task suppression conditions take precedence over task dismissal. If a task is suppressed (for example, for a threaded message with outstanding tasks), no task is created, and dismissal does not apply.
• Auto-dismissal applies only to the intents listed above. Other intents do not qualify for dismissal.
• The System Sender dismissal setting and the Conditional Task Dismissal setting are independent. Customers can enable either, both, or neither.

Connectors: Workday Agent System of Record (ASOR) Connection Support

This release adds support for the Workday Agent System of Record (ASOR) framework as an alternative connection method to Workday Financials. ASOR is Workday's native framework that allows external agents to connect to Workday Financials within Workday's security model. Communication flows through an OAuth-secured Agent Gateway.

When configuring an ERP connection to Workday, administrators can now choose between two connection methods: Integration System User (ISU) or Agent System User (ASU). Existing customers default to ISU, and both connection types can coexist for the same customer when configured as separate sources. Selecting ASU exposes an additional Authorization Code field required to complete the connection.

What's New

• Connection method selector: When Workday is selected as the ERP connection in Administration → System Settings → ERP Connection, a Connection By option appears with two choices: Integration System User (ISU) or Agent System User (ASU).

• ISU as default for existing customers: Customers with existing ISU configurations continue to use ISU by default.

• Coexistence of connection types: ISU and ASU connections can coexist for the same customer when configured as two separate sources.

• Authorization Code field for ASU: Selecting ASU exposes an Authorization Code field required to establish the connection.

• OAuth-secured authentication: API requests are routed based on the customer's selected connection type, with OAuth-based authentication and token management.

• Workday security model alignment: The ASOR connection uses standard Workday security groups, preserving segregation of duties.

Note: ISU remains the default connection method for existing customers. No changes are required for customers who continue to use ISU.

This feature is available in Limited Availability (LA) and may be enabled on request. If you are interested in enabling this feature, please contact your Customer Success Manager or our support team at support@auditoria.ai.

2. Fixed Bugs

No fixed bugs were reported in this release.

3. New Known Bugs