Executive Summary

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

1. New and Updated Features

Platform: Audit Logs Filtering Enhancements

This release improves the Audit Logs experience by adding new filtering options that help users find relevant activity more quickly and efficiently.

Users can now narrow audit log results by time range and by one or more action types, making it easier to review specific user and system events within large datasets. This release also includes performance improvements to support faster loading of system activity logs at scale.

Key Benefits

• Find relevant audit events faster
• Filter by common time ranges or a custom date range
• Select multiple action types in a single search
• Improved performance for large audit log datasets

What’s New

New time range filters

Audit Logs now include additional time-based filtering options:

• Last 30 days
• Last 60 days
• Last 90 days
• Custom date range (The custom date range filter allows users to select any custom 90-day date range only.)

These options help users quickly focus on the period most relevant to their investigation or review.

New multi-select action filter

Users can now filter Audit Logs by selecting multiple action types at once.

This makes it easier to search across related events in a single query, rather than filtering one action at a time.

Examples of supported action types include:

• AP Invoice Template Edited
• Logged In
• Logged Out

SmartVendor & SmartCustomer: Multi‑currency filtering across remaining tabs

In this release, you can filter by multiple currencies in more SmartVendor and SmartCustomer views. This makes it easier to focus on transactions in specific currencies without exporting data or applying manual filters.

What’s New

• SmartVendor – Bills tab

  • Currency is now a standard field on the Bills tab.

  • Currency appears in the Edit columns selector so you can add, remove, or reorder it like other standard columns.

  • You can apply multi‑select currency filters on the Bills tab to view bills for one or more currencies at the same time.

• SmartVendor – Item Receipts (NetSuite)

  • Added support for multi‑select currency filters on the Item Receipts tab for NetSuite.

  • Enables focused views of item receipts across specific currencies in a single grid.

• SmartCustomer – Internal Documents (all ERPs)

  • Added support for multi‑select currency filters on the Internal Documents tab for all supported ERPs.

  • Helps you quickly narrow internal documents to the currencies that matter for analysis or review.

SmartVendor / SmartCustomer / AP Accruals: Support for Date Filters across all business objects

This release introduces date filters across all standard date fields across all business objects in SmartVendor, SmartCustomer, and AP Accruals.

This enhancement is available for all supported ERP integrations, including Workday, NetSuite, Coupa, Sage, and Universal.

Key Benefits

• More consistent filtering experience across products and tabs
• Easier list refinement using standard date-based criteria
• Improved usability with familiar date operators
• Designed to support performance by focusing on standard date fields

What’s New

Standard date filters added across key tabs

Date filters are now available for standard date fields in:

• SmartVendor
• SmartCustomer
• AP Accruals

The filtering experience matches the existing date filter behavior already used in the Documents tab in SmartVendor and SmartCustomer.

Supported date filter types

Users can now filter supported date fields using:

• On or After
• On or Before
• Between

These options allow users to quickly narrow records to a specific date or date range.

SmartVendor

Date filters are now available on the following Business Objects and Standard Date Fields:

• Bills
  • Date
  • Due Date
• Purchase Orders
  • Date
• Credit Memos
  • Date
• Contracts
  • Date
• Payments
  • Payment Date
• Item Receipts
  • Date
• Tasks
  • Added

SmartCustomer

Date filters are now available on the following Business Objects and Standard Date Fields:

• Invoices
  • Due Date
  • Invoice Date
  • Scheduled Payment Date
• Payments
  • Payment Date
• Credit Memos
  • Credit Memo Date
• Disputes
  • Dispute Date
  • Invoice Date
• Tasks
  • Added

AP Accruals

Date filters are now available on the following Business Objecs and Standard Date Fields:

• Journal Entries
  • Complete By AI Agent
• Bills
  • Date
  • Due Date
• Purchase Orders
  • Date

AP Invoices: Hyperlinks to Purchase Orders and Supplier Contracts in the Documents Tab

This release adds direct hyperlinks to related Purchase Orders and Supplier Contracts in the Documents tab for AP Invoices.

Users can now open linked source records directly from invoice and credit memo documents, making it easier to review supporting information without leaving their current workflow. This enhancement helps reduce manual navigation and speeds up validation and review activities.

Key Benefits

• Open related Purchase Orders and Supplier Contracts directly from the Documents tab
• Reduce manual navigation between records
• Review source details more quickly while processing invoices and credit memos
• Improve efficiency across both view and edit workflows

What’s New

Hyperlinks for line-level PO and Supplier Contract Number

The PO and Supplier Contract Number at the line level now appears as a hyperlink.

• Available in both view mode and edit mode
• In edit mode, a redirection icon appears next to the dropdown when a PO or Supplier Contract is selected. The hyperlink updates dynamically when the PO or Supplier Contract is selected, allowing users to open the linked PO or Supplier Contract in a new tab.

Available Across Document States

This hyperlink behavior is available throughout the Documents tab, including:

• Active Data
• Dismissed Documents
• Written to System of Record (SoR) documents

Support for Credit Memos

This enhancement also applies to Credit Memos.

Header-level Contract hyperlink

The Contract field in the document header is now hyperlinked. 

Users can click the redirection button to open the related Supplier Contract in a new browser tab.

AP/AR Helpdesk: Language-Matched AI Agent Reply Templates

This release adds support for language-matched AI Agent reply templates in SmartCustomer (Accounts Receivable Helpdesk) and SmartVendor (Accounts Payable Helpdesk).

With this enhancement, admins and authorized users can configure reply templates by intent and language, giving teams more control over how AI Agent responds to non-English emails. If no language-specific template is configured, AI Agent will continue to use the default template and generate a translated reply automatically. Default Templates use English as the default language (unless explicitly modified by users).

Key Benefits

• Create more natural, localized AI Agent responses
• Manage templates by intent and language
• Continue using existing default templates when no language-specific version is available
• Improve consistency for multilingual customer and vendor communications

What’s New

Language-specific template configuration by intent

A new Language Match option is now available for each intent.

• Language Match checkbox: Enables language-specific reply templates for the selected intent.
• Language Match dropdown: Let users choose from 48 supported languages when Language Match is enabled.

Smarter language selection experience

• The language dropdown is searchable
• Languages with configured templates appear at the top of the list
• Languages with saved templates display a count badge indicating the number of templates configured in that language. For example, Spanish (3) would mean that a total of 3 Spanish templates have been configured across all available intents and business outcomes.

Template Configuration

Language-matched templates can be configured within the existing AI Agent reply setup:

• In SmartVendor (AP Helpdesk), templates are managed by category
• In SmartCustomer (AR Helpdesk), templates are managed by the configured customer record field

For each intent, templates can now be maintained across:

• the relevant category or customer field
• the reply outcome or use case
• the selected language

This allows teams to tailor responses more precisely for different scenarios and audiences.

Runtime Behavior

When AI Agent detects a supported intent for a non-English email:

• If a language-specific template exists, AI Agent picks that particular template to generate the reply draft
• If Language Match is enabled but no template exists for that language, AI Agent uses the default template and generates a translated reply draft
• If Language Match is not enabled for that intent, AI Agent continues to use the default template and generates a translated reply draft

This ensures the AI Agent can always generate a response, while allowing organizations to provide custom localized content where required.

Template Count Badges

Each language in the dropdown can display a badge showing how many templates are already configured in the current setup.

For example:

• Spanish (3) means three reply templates have already been created for Spanish

This helps users quickly identify:

• which languages are already in use
• how much coverage exists across intents and reply outcomes

Supported Languages

Language Match supports 48 languages, including:

English, Chinese, Japanese, German, French, Spanish, Arabic, Portuguese, Hindi, Russian, Korean, Italian, Dutch, Turkish, Swedish, Thai, Danish, Polish, Hebrew, Czech, Indonesian, Norwegian, Finnish, Hungarian, Greek, Romanian, Malay, Bulgarian, Vietnamese, Slovak, Croatian, Lithuanian, Latvian, Estonian, Serbian, Bosnian, Slovenian, Albanian, Macedonian, Maltese, Irish, Welsh, Basque, Catalan, Galician, Armenian, Azerbaijani, and Georgian.

This feature is available in Limited Availability (LA) and may not be enabled by default in all environments.

If you are interested in enabling this capability, please contact your Customer Success Manager or our support team (support@auditoria.ai).

AR Helpdesk: Follow-Up Tasks for Confirmed Payment Not Received (Payment Made Intent)

AR Helpdesk now supports Follow-Up Tasks when a customer has confirmed that a payment was made, but the invoice still has an outstanding balance after a configurable number of days. This functionality is configured through the Create Task AI Agent Action and is available for Collaborative Mode–enabled AR Helpdesk.

When a Payment Made email is processed and the invoice remains unpaid (Amount Remaining greater than 0.00) after the configured delay, SmartCustomer automatically creates a Follow-Up task for collections. If the invoice is fully resolved before that time, the queued follow-up task is canceled.

What’s New

• Payment Made follow-up task creation
  • AI Agent “Create Task” action now supports follow-up tasks for the “Customer has confirmed a payment is made” intent.
  • When a Payment Made email is processed and Invoice Amount Remaining is greater than 0.00 after the configured delay, SmartCustomer creates a Follow-Up task.
  • If Invoice Amount Remaining is 0.00 after the configured delay, no Follow-Up task is created.
• Configurable delay for task creation
  • In AI Agent Actions > Create Task, there is a new checkbox:
    • “Create Task When Confirmed Payment Not Received”
  • When this checkbox is selected, users can choose:
    • Next Day
      • Task is added on the calendar day after the email received date (or Task DONE date when later).
    • After ___ Days
      • Task is added after a configurable number of days to account for payment processing delays.
      • Supported range: 2–99 days after the email received date.

• Conditions to create or cancel Payment Made Follow-Up Tasks
  • A Payment Made Follow-Up Task is queued when:
    • A Payment Made intent is detected on an email and marked as DONE.
  • A queued Payment Made Follow-Up Task is created when:
    • The configured delay (Next Day or X Days) has passed, and
    • Invoice Amount Remaining is greater than 0.00.
  • A queued Payment Made Follow-Up Task is canceled when any of the following are true before the creation time:
    • Invoice Amount Remaining is 0
    • Invoice Status is Canceled
    • Invoice Status is Paid
    • Invoice is deleted or missing
• Task assignment behavior
  • For invoices linked to a Customer record that has a designated collections agent (with SmartCustomer access):
    • The follow-up task is assigned to that collections agent by default.
  • When no collections agent is specified on the Customer record:
    • The follow-up task is assigned according to Automatic Task Distribution policy, when configured, or
    • Is left unassigned if no distribution rule applies.
• Task access, type, and filtering
  • Payment Made follow-up tasks:
    • Are visible in the Tasks tab.
    • Are added with Task Type = “Follow-Up” (also referred to as Category).
    • Can be filtered by Task Type “Follow-Up”.
  • On the Tasks tab:
    • Detected Intents column displays “Confirmed Payment Not Received” for these follow-up tasks.

• Task details and email context
  • When a Payment Made email is processed and Invoice ID is extracted:
    • Task Details include:
      • Invoice ID
      • Payment Date (using Confirmed Payment Date)
      • Payment Amount (if available)
    • The email thread for the original Payment Made email message is displayed in Task Details.
    • Task Metadata is added to the Payment Made email message for traceability.
• Reply template support
  • A dedicated Reply Template is available for this scenario:
    • “Confirmed Payment Not Received Follow-Up”
      Example:
      Hi ${firstName},   Payment confirmation was given for Invoice ${invoiceNumber} on ${invoice.ConfirmedPaymentDate} and payment has not been received.   Take Care!
  • Templates support inserting:
    • Confirmed Payment Date: ${invoice.ConfirmedPaymentDate}
      • Uses the extracted date when present, or the email received date.
• Customer and Invoice record notes
  • When a Payment Made Follow-Up Task is added, SmartCustomer writes a note to the Customer/Invoice record, for example:
    • “Confirmed Payment Not Received” Follow-Up Task <Task Link> added (next day); invoice <invoice number>; scheduled date <date>; scheduled amount <amount> <View Email link>.
    • “Confirmed Payment Not Received” Follow-Up Task <Task Link> added (next day); invoice <invoice number>; scheduled date <date>; scheduled amount <amount> <View Email link>.
  • When a Payment Made Follow-Up Task is completed, another note is recorded, for example:
    • “Confirmed Payment Not Received” Follow-Up Task <Task Link> completed by <user>; invoice <invoice number>; scheduled date <date>; scheduled amount <amount>; reply sent <View Email link>.
• AI Agent task history
  • Task history reflects that AI Agent created the Follow-Up Task after X days, aligning with the configured delay in Create Task settings.

AR Helpdesk: Follow-Up Tasks for Scheduled Payment Date Passes (Payment Delayed Intent)

Follow-Up Tasks for Confirmed Payment Not Received (Payment Made Intent)

This release adds follow-up task support in AR Helpdesk for Payment Delayed emails and delayed payment updates at the invoice level. When a customer notifies that a payment will be delayed, the system can now queue and create a Follow-Up task after the scheduled payment date passes, as long as there is still an outstanding balance on the invoice.

What’s New

Follow-up task creation when scheduled payment date passes

• An optional setting in the Create Task AI Agent action to create a follow-up task when a scheduled payment date passes for an invoice.
• Trigger condition for task creation:
  • Scheduled payment date (set via AI Agent or manually on the invoice) has passed.
  • Invoice Amount Remaining is greater than 0.00 (or equivalent).
• No task is created when:
  • Invoice Amount Remaining is 0.00 (or equivalent) and no scheduled payment amount is provided.
• Intent used: “Customer has notified a payment will be delayed” (Payment Delayed intent).

Configurable delay for task creation

• Create Task When Scheduled Payment Date Passes option includes:
  • Next Day – Task is added on the calendar day after the scheduled payment date.
  • After ___ Days – Task is added after a user-defined delay to account for payment processing times.
    • Supported range: 2–99 days after the scheduled payment date.

Automatic assignment to collections agents

• When the invoice is linked to a customer record with a designated collections agent in Auditoria:
  • Follow-up tasks are assigned to that collections agent (must have SmartCustomer access).
• When no collections agent is set on the customer:
  • Follow-up tasks are unassigned or assigned via Automatic Task Distribution rules and conditions, if configured.

Task type, metadata, and task details

• Follow-up tasks created by this logic use:
  • Task Type: Follow-Up.
  • Detected Intent (Tasks tab): Scheduled Payment Date Passed.
  • Task metadata on the original Payment Delayed email message to track linkage.
• Task Details behavior:
  • If the scheduled payment date was set via AI Agent from a Payment Delayed email:
    • Task shows Invoice ID, Scheduled Payment Date, Scheduled Payment Amount (if available).
    • Task surfaces the email thread for the original Payment Delayed message.
  • If the scheduled payment date was set manually on the invoice (no email message):
    • Task surfaces Invoice Details for the affected invoice.
    • Dunning contacts are auto-populated in the To field when composing an email from the task.
    • Tasks tab columns:
      • Email column displays “N/A”.
      • Sender Type column displays “N/A”.
• Task History entry records that AI Agent created the follow-up task after X days.

Email templates and reply templates

• New / dedicated email templates for the Payment Delayed intent when slot values (dates/amounts) are present:
  • “Passed Scheduled Payment Date Follow-Up”
    • Example content:
      • “Hi ${firstName},
        Scheduled payment date ${invoice.ScheduledPaymentDate} for Invoice ${invoiceNumber} has passed and payment has not been received.
        Take Care!“
  • “Passed Scheduled Payment Date and Amount Follow-Up”
    • Example content:
      • “Hi ${firstName},
        Scheduled payment date ${invoice.ScheduledPaymentDate} for Invoice ${invoiceNumber} has passed and promised ${invoice.ScheduledPaymentAmount} payment has not been received.
        Take Care!“
• Reply template fields added:
  • [Invoice Standard > Scheduled Payment Date] – ${invoice.ScheduledPaymentDate}
  • [Invoice Standard > Scheduled Payment Amount] – ${invoice.ScheduledPaymentAmount}

Customer and invoice record notes

• When a follow-up task is added, the customer/invoice record logs a note such as:
  • “Scheduled Delayed Payment Date Passed” Follow-Up Task <Task Link> added (next day); invoice <invoice number>; scheduled date <date>; scheduled amount <amount> <View Email link>.
  • “Scheduled Delayed Payment Date Passed” Follow-Up Task <Task Link> added (after X days); invoice <invoice number>; scheduled date <date>; scheduled amount <amount> <View Email link>.
• When a follow-up task is completed, the record logs a note such as:
  • “Scheduled Delayed Payment Date Passed” Follow-Up Task <Task Link> completed by <user>; invoice <invoice number>; scheduled date <date>; scheduled amount <amount>; reply sent <View Email link>.

Cancellation of queued follow-up tasks

• Queued Payment Delayed follow-up tasks are canceled (not created) if any of the following become true before the task is created:
  • Invoice Amount Remaining is 0.
  • Invoice Status is Canceled.
  • Invoice Status is Paid.
  • Invoice is deleted or missing.

AR Collections: Dunning Eligibility Based on Invoice Extended Fields

This release adds support for using Invoice Extended Fields to determine which invoices are eligible for dunning notifications in AR Collections.

With this enhancement, collections teams can define eligibility rules based on invoice-specific extended field values, allowing AI Agent to include only qualifying invoices in dunning workflows. This gives organizations more flexibility to align collections automation with internal business rules, such as including only Trade invoices or excluding invoices tied to specific payment types.

Key Benefits

• Control dunning eligibility using invoice-specific business rules
• Include or exclude invoices based on configured extended field values
• Reduce manual filtering before collections workflows run
• Support a wide range of use cases with flexible, generic configuration

What’s New

Dunning eligibility filters now support Invoice Extended Fields

AR Collections AI Agent eligibility settings now allow admins to use Invoice Extended Fields as filtering criteria.

This enables collections managers to define which invoices should be included in dunning based on values stored on the invoice record.

Flexible field and value selection

When configuring eligibility rules, users can:

• select an Invoice Extended Field
• define one or more qualifying values for that field

AI Agent applies the configured rules automatically

When AR Collections AI Agent runs, it evaluates each invoice against the configured extended field criteria.

• Matching invoices are eligible for dunning notifications
• Non-matching invoices are excluded from dunning workflows

This helps ensure that dunning activity follows the organization’s defined policies without requiring manual review or filtering.

Configuration Overview

In AR Collections Settings page, the invoice eligibility settings now support:

• adding an Extended Field filter
• selecting an available Invoice Extended Field
• specifying the value or values that qualify an invoice for dunning

These rules are then applied each time the AI Agent automatically evaluates invoices for collection activity.

This feature is available as Limited Availability (LA) and may not be enabled in all environments by default.

If you are interested in enabling this capability, please contact your Customer Success Manager or our support team (support@auditoria.ai).

AR Collections: Enhanced Dunning Table Filter Configuration

This release expands Dunning Table filter configuration in SmartCustomer – AR Collections, allowing Collections Managers to define more precise invoice selection criteria using multiple invoice attributes.

Previously, Dunning Tables could be filtered primarily by status. With this enhancement, users can now combine additional filters such as Days Past Due and Payment Type to better align each Dunning Table to a specific collections scenario. This helps teams create clearer aging-based workflows and reduce overlapping outreach across tables.

Key Benefits

• Configure Dunning Tables with more precise invoice criteria
• Build aging-based tables using Days Past Due
• Include or exclude invoices by Payment Type
• Reduce overlap between Dunning Tables and improve collections targeting
• Save filter configurations for ongoing use

What’s New

Expanded filtering options for Dunning Tables

Dunning Table configuration now supports multiple filterable fields, including:

• Status
• Days Past Due
• Payment Type

This gives users more flexibility in determining which invoices appear in each table.

Field-specific operators

Available operators vary based on the selected field and can include:

• Equals
• Not equal
• Less than
• Greater than
• Less than or equal to
• Greater than or equal to
• Between
• Contains

Support for multiple filters in a single table

Users can add multiple filters to the same Dunning Table.

All configured filters are evaluated using AND logic, meaning an invoice must meet all conditions to appear in that table.

Payment Type filtering

For organizations that need to include or exclude specific invoice types, Payment Type filters can be added as part of the table definition.

This allows teams to tailor Dunning Tables to their business rules and collections processes.

Why It Matters

By combining multiple invoice filters in a single Dunning Table, collections teams can create more targeted invoice groupings and better control how invoices are worked through the collections process.

This is especially useful for:

• aging-based outreach strategies
• payment-type-specific workflows
• reducing duplicate invoice inclusion across multiple Dunning Tables

This feature is available as Limited Availability (LA) and may not be enabled in all environments by default.

If you are interested in enabling this capability, please contact your Customer Success Manager or our support team (support@auditoria.ai).

2. Fixed Bugs

None.

3. New Known Bugs