Executive Summary

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

1. New and Updated Features

AP Invoices: Document Language Detection and Translation

Auditoria now automatically detects the language of incoming documents during processing and displays the detected language in the Documents list views and on the document details page. For documents detected as non-English, users can translate the document to English directly from the document preview and switch between the original and translated versions. This is particularly useful in the document preview section, where users can translate a document arriving in a non-English language to support manual review and updates on the document details page.

What's New

• Automatic language detection: The system detects the language of incoming documents during processing. For single-language documents, the primary language is displayed. For multi-lingual documents, the dominant language (the language with the highest word or character count) is displayed.
• Language column in list views: A filterable Language column is added to the Active Data, Written to SoR, and Dismissed Documents list views. The column supports "In" and "Not In" filters populated from the languages present in the current list view.
• Configurable Language column visibility: The Language column can be shown or hidden via the Edit Columns panel on each list view.
• Language field in document details: The detected language is displayed in the document information header on the document details page.
• New document preview toolbar: A new toolbar is available at the top of the document preview with quick-access controls including Rotate, Maximise, Download, and Translation.
• Translate to English via language dropdown: For non-English documents only, a language dropdown appears on the new preview toolbar showing the detected language of the document. Clicking the dropdown reveals an "English" option; selecting it initiates translation. Once translation completes, the preview automatically switches to the translated document. Users can toggle between the original and translated versions from the same dropdown.
• One-time translation: Translation runs once per document. If a translation fails, a message is displayed and the document cannot be retried in the same session.
• Translation scope by document type:
  • PDF files: For PDFs where extraction-page support exists, translation is applied to the extracted pages only.
  • Other document types (for example, doc, spreadsheet, images): Extraction pages are not detected, so translation is applied to the entire document.
• Documents classified as "Others": When a document is classified as "Others," the language is shown as "Unknown." If the user manually reclassifies the document to Invoice or Credit Memo, language detection runs automatically. For non-English documents, the translation option then becomes available as usual.
• Unknown language handling: If the system cannot determine the language, the Language field displays "Unknown."
• Audit log entries: Language-related updates, including detection and user-initiated translation, are captured in the document-level audit log.

Notes

• Language detection and translation apply to documents processed after this feature is enabled. Documents processed before enablement may not have language data populated. For existing documents classified as "Others," reclassifying them to Invoice or Credit Memo triggers language detection automatically.
• Auditoria has validated support for 49 predominantly used languages. Since the AI is continuously evolving, languages outside these 49 may also be detected and translated; users should manually review output for any language that falls outside the validated set.
• Translation accuracy: There may be instances where the full document does not translate properly. Auditoria does not guarantee 100% accuracy in translation; users should verify translated content before acting on it.
• When autonomous processing is enabled, documents in unsupported languages do not qualify for autonomous processing and continue to require user review.

AP Invoices/AP Helpdesk: Unified Distribution Policy for Documents and Tasks

When AP Invoices and AP Helpdesk are active in the same SmartFlow instance, distribution policies now support both Document Rules and Task Rules within a single policy. Each rule type is evaluated independently and maintains its own round-robin assignment mechanism. Enabling or disabling one product does not affect the distribution rules of the other.

This update enables combined policies so document assignment and task assignment can coexist without interference — including scenarios where a single email creates both a document and a task, which may be assigned to different users based on their respective rules.

What's New

• Combined distribution policy: When both AP Invoices and AP Helpdesk are active in the same SmartFlow instance, the Assignment Rules area within a policy is split into Document Rules and Task Rules, each with its own rule count.

• Policy Rules column: On the distribution policy landing page, the Policy Rules column displays separate counts for Document Rules and Task Rules when both products are active. Each count is displayed as a visually distinct label (for example, "2 Doc Rule(s)" and "3 Task Rule(s)").

• Add Rule modal with type selector: A single Add Rule button opens a modal with a radio selector for Document or Task. Users select the rule type before entering rule details. Only one rule type can be created per modal interaction.

• Independent rule evaluation: Document Rules and Task Rules are evaluated independently. Each rule type maintains its own round-robin assignment mechanism and its own incrementing rule numbers.

• Rule archiving on product deactivation: When a product is turned off in SmartFlow configuration, its associated rules (Document or Task) are archived in the database and stop executing. Archived rules are not deleted.

• Rule restoration on product re-enablement: When a previously deactivated product is re-enabled, its archived rules are restored and resume execution.

• Automatic migration of existing policies: When a second product is activated in an existing SmartFlow instance, existing rules are preserved, and the new rule section (Document Rules or Task Rules) is added automatically. Administrators do not need to re-create existing rules.

• Single-product compatibility: When only one product is active in the SmartFlow instance, only the applicable rule type appears. Existing standalone AP Invoices or AP Helpdesk behavior is unchanged.

Notes

• Single-product behavior is unchanged: if only one product is active, only the applicable rule section is shown (Document Rules for AP Invoices standalone; Task Rules for AP Helpdesk standalone).

• The combined experience applies whether AP Invoices is added to an existing AP Helpdesk setup or AP Helpdesk is added to an existing AP Invoices setup.

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 Invoices/AR Remittances: Customizable Line Item Column Ordering

Users can now reorder columns in the Line Items table within the document details page. This applies to both AP Invoices (SmartVendor) and AR Remittances (SmartCustomer). A Reorder Columns button in the table header opens a panel where users drag and drop columns into their preferred order.

This update allows users to position frequently referenced columns at the top of the table, reducing the need for horizontal scrolling when reviewing line-item data.

What's New

• Reorder Columns panel: A Reorder Columns button is available in the top-right corner of the Line Items table header. Clicking it opens a panel listing all columns in their current order.

• Drag-and-drop reordering: Users drag column names up or down in the panel to change the display order. Visual feedback is provided during the drag operation.

• Apply, Cancel, and Restore to Default:

  • Apply updates to |the column order immediately (no page refresh).

  • Cancel closes the panel without saving changes.

  • Restore to Default resets the column order to the system default.

• Edit mode compatibility: Column reordering is available in both read-only and edit modes. When reordering columns in edit mode, in-progress edits are preserved.

• Persistent column order: The custom column order persists across browser sessions, including after logout and login. The order is stored per user account and persists when the user logs in from a different browser or device.

Notes

• Column reordering applies to the Line Items table on the document details page for AP Invoices (SmartVendor) and AR Remittances (SmartCustomer).

• All columns remain visible in the reorder panel. Columns cannot be hidden or removed from the table view through this feature.

AP Helpdesk: Unknown-to-System Sender Bulk Conversion

System Sender Management now includes an Unknown Sender Email Addresses table that helps super administrators and managers review email addresses currently classified as Unknown and add trusted sources to the System Sender List in bulk.

This update streamlines sender classification by providing a consolidated view of unknown sender activity and a bulk conversion mechanism, replacing the previous process of adding system sender addresses one at a time.

What's New

• Unknown Sender Email Addresses table: A new table in System Sender Management lists all unknown sender email addresses that are not yet configured as system senders. Columns include Unknown Sender Email Address, Total Messages, and Last Received.

• Sorting and search: The table supports sorting by email address (alphabetical), Total Messages (highest or lowest, the default sort), and Last Received (newest or oldest). The table is searchable.

• Pagination: The table is paginated with a default of 25 rows per page.

• Bulk selection and conversion: Users select one or more rows using checkboxes. When at least one row is selected, the Add button becomes active. Clicking Add converts the selected email addresses to system senders, removes them from the table, and updates the Configured System Senders count.

• Sample email preview: Clicking the Total Messages value for a given email address opens a pre-filtered mailbox view showing emails from that sender. This allows administrators to review sample emails before converting the address.

• Status messages: Success, failure, and partial failure messages are displayed after a conversion attempt, indicating how many addresses were successfully added.

Notes

• Email addresses with public domains (e.g., gmail.com) are excluded from the Unknown Sender Email Addresses table because they represent personal email addresses rather than system senders.

• This feature is available to super administrators and managers in System Sender Management.

AP/AR Helpdesk: Tasks for System Sender Emails with Record Link

Helpdesk now supports creating tasks for system sender emails and on-demand task creation for unknown and system sender emails across both AP Helpdesk and AR Helpdesk. In addition, AP Helpdesk (SmartVendor) supports linking system sender emails to vendor records, enabling system-generated communications to be associated with specific vendor records.

With task support enabled, system sender emails can participate in task assignment, Automatic Task Distribution (ATD), and additional processing workflows alongside other Helpdesk task types.

What's New

• System sender task configuration: A new "Tasks for System Senders" checkbox is available in SmartVendor and SmartCustomer SmartFlow configuration settings under the AP Helpdesk and AR Helpdesk sections. When enabled, the AI agent automatically adds a Review task for each incoming system sender email.

• ATD rule support for system senders: The Sender Type input attribute in ATD rules now supports the "System" value. Administrators can create distribution rules that apply only to system-sender emails.

• Default task display: In the Tasks tab, the Vendor Name column (AP Helpdesk) or Customer Name column (AR Helpdesk) shows "[N/A - System]" for system-sender tasks. In AP Helpdesk, when a vendor record is linked to the task, the Vendor Name column displays the linked vendor name.

• Record linking from task details (AP Helpdesk only): A Linked Record field appears in task details for system sender emails in AP Helpdesk (SmartVendor). Users can search for and select one or more vendor records via the Linked Record dropdown. The link is finalized when the user clicks Done.

• Record linking from Message Metadata (AP Helpdesk only): For system-sender emails without a task in AP Helpdesk (SmartVendor), Message Metadata shows Record Link (in place of Record Match) and provides an Add Record Link option to link vendor records directly from the message view.

• Thread-level record propagation (AP Helpdesk only): When a system sender email is linked to a vendor record in AP Helpdesk, subsequent emails in the same thread are automatically linked to the same record.

• Mailbox filtered view inclusion (AP Helpdesk only): System sender emails linked to a vendor record in AP Helpdesk are included in mailbox results when filtering by that record. Users can further refine results using the Sender Type filter.

• Audit log entries: Record link and task creation actions are captured in the task audit log, including the user who performed the action and the records involved.

• Record-level notes (AP Helpdesk only): When a system sender email is linked to a vendor record in AP Helpdesk, a note is added to the vendor details page indicating the link and the user who made it.

• On-demand task creation: An Add Task button is available for unknown and system sender emails that do not already have a task. Clicking Add Task creates a user task for that email. The task is assigned in accordance with ATD rules, if applicable. The action is recorded in the task audit log.

Notes

• System sender emails are not eligible for autonomous replies. Autonomous forwards and transfers for document submissions remain unaffected by this restriction.

• AP Helpdesk (SmartVendor): Linking a vendor record to a system sender email and then reprocessing can re-run processing using the linked vendor context and may generate a reply draft aligned to that vendor.

• The Tasks for System Senders checkbox requires system sender support to be enabled in SmartFlow configuration.

• The Add Task button is not shown for emails in the Archived folder or while reprocessing is in progress.

• For unknown-sender tasks, Helpdesk supports task-based triage and intent-based workflows. Additional record-based processing becomes available once the sender is transitioned to an appropriate known sender type.

SmartResearch: Version 2.0

SmartResearch Version 2.0 is a ground-up redesign of the research and analytics experience. This release rebuilds the chat interface for speed, clarity, and more natural interaction with the agent, and introduces improvements to intent detection, multi-currency handling, conversation context management, agent explainability, user-configurable defaults for time period and currency, interactive data visualization, persistent session management, structured message feedback, and a redesigned SmartFlow Skill wizard with two data scope options.

What's New

• Redesigned chat experience: The chat view has been rebuilt from scratch with a faster, more responsive layout, an updated landing page, an auto-resizing input area, a real-time streaming indicator that shows when the agent is generating a response, and automatic cursor focus in the chat input so users can begin typing immediately.

• Explainability: Users can ask the agent to explain its reasoning — how it arrived at an answer, what logic or calculations it applied, or why it returned specific results. Agent responses include expandable reasoning displays so users can inspect the thinking behind any answer.

• Improved intent detection: The agent is better at recognizing what users are actually asking, even when queries are ambiguous or conversational. This reduces misinterpreted questions and returns more relevant answers on the first try.

• Better multi-currency handling: The agent handles multi-currency queries more reliably — including comparisons across currencies, converted amounts, and mixed-currency datasets.

• Context management: Conversations remain coherent across longer interactions. The agent tracks what has been discussed and carries context forward, so follow-up questions work naturally without needing to re-state prior context.

• Default time period and currency: Users can configure a default reporting time period (for example, last 12 months) and a default currency directly from a prompt. When a subsequent question does not specify a time range or currency, the agent automatically applies these defaults as filters. When a user explicitly specifies a time range or currency, the defaults are not applied — the user's intent always takes precedence.

• Data visualization and exploration: Agent responses that include structured data render with interactive chart components (bar, line, area, and donut charts) alongside a sortable, paginated data grid that supports filtering and export, so users can work with results directly without pulling the data into a separate tool.

• Session management: Conversations persist across page reloads. Session state, including conversation history and loaded data, is maintained per session and isolated between tenants and users. Sessions support creation, resumption, expiration, and cleanup. Browser refresh no longer causes errors in the SmartFlow Skill workflow.

• Message feedback: Users can provide thumbs-up or thumbs-down feedback on individual agent responses. Negative feedback includes issue type categorization, making it easier to route and act on user-reported problems.

• In-chat reports and summaries: Users can ask the agent to generate reports or summarise the current conversation directly within the chat.

• SmartFlow Skill data scope configuration: When a Superadmin creates a SmartResearch SmartFlow Skill, a four-step wizard presents two data scope options:

  • Agent + Financial Data: Includes data from AP and AR agents (invoices, emails, vendor and customer records, collections, accruals), mailbox data from AP and AR Helpdesk agents, System of Record (SoR) data inherited from selected SmartVendor or SmartCustomer skills, and optional third-party sources (for example, Zip, Adaptive Planning, Salesforce CRM).

  • Financial Data Only: Includes SoR data and optional third-party sources. No agent or mailbox data is included.

• SoR conflict detection: When Agent + Financial Data is selected, and a skill uses a non-Workday SoR, the system displays a warning that SoR data from that source will be excluded. The skill still contributes agent and email data.

Notes

• SmartResearch currently supports Workday as the SoR for the Financial Data Only data scope option. Other SoR systems are not yet supported for that option.

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

SmartResearch: The stop button on the SR Instances dashboard removes the wrong instance

Symptom: Clicking the Stop button on a SmartResearch instance in the dashboard stops the first instance listed, not the one the user selected.

Impact: Users unintentionally stop the wrong SmartResearch instance, interrupting ongoing research sessions and causing confusion about which instance is active.

Workaround: No manual workaround was available. The issue has been resolved, and the Stop button now removes the intended instance.

SmartResearch: Chats page fails to load after using chat search

Symptom: When a user searches chats using a query that contains a percent (%) character or certain reserved characters, the chats page fails to load, and the chat history becomes inaccessible.

Impact: Users are unable to view their chat history after performing such a search and must navigate away from the page to recover.

Workaround: Avoid using percent (%) or other special characters in search queries until you navigate away from and back to the chats page. The issue has been resolved; queries are now encoded correctly, and the page loads as expected.

SmartResearch: Feedback throws an error on new chats

Symptom: Submitting thumbs-up or thumbs-down feedback on an agent response in a new chat results in an error and the feedback is not recorded.

Impact: Users cannot provide feedback on responses in a newly created chat, limiting the signal available to improve agent quality.

Workaround: No manual workaround was available. The issue has been resolved, and feedback is now recorded correctly in new chats.

SmartResearch: Scope shows an extra comma in the SoR list

Symptom: The SmartResearch scope display shows a stray comma when rendering SoR values, and the underlying request payload contains an incorrectly formatted SoR value.

Impact: The scope appears incorrect to the user, and the malformed payload can affect how the SoR selection is interpreted downstream.

Workaround: No manual workaround was available. The issue has been resolved, and SoR values are now rendered and sent without the extra comma.

SmartResearch: Elements display a dark blue border when tabbing through the interface

Symptom: When a user clicks into the SmartResearch page and uses the Tab key to move between elements, focused elements display a dark blue outline that does not match the SmartResearch visual style.

Impact: Keyboard navigation is visually jarring and inconsistent with the rest of the interface, though functionality remains unaffected.

Workaround: No manual workaround was available. The issue has been resolved; focused elements now use a focus style consistent with the SmartResearch design.

3. New Known Bugs