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

1. New and Updated Features

AP Invoices: Predictive Coding Alignment for PO vs. Non‑PO Invoices

This release introduces a clear separation between PO‑driven and non‑PO invoices. PO‑driven invoices auto‑populate only the fields available in the matched PO (no predictive coding). Non‑PO invoices continue to use predictive coding for supported dropdown fields. This change prevents unexpected field population and reduces processing errors.

What's New

• Distinct behavior by invoice type:
  • PO‑Driven: Only PO fields are auto‑populated; fields not present in the PO remain blank for user entry. No predictive coding runs.
  • Non‑PO: Predictive coding auto‑populates supported dropdown fields; users can adjust or remove predictions.
• Multi‑vendor PO handling:
  • When the vendor changes, existing PO‑populated fields are cleared; no values are carried over to the new vendor.
  • PO Number and PO Line clear automatically; new PO selection replaces prior PO‑driven fields after validation.

Note

• No changes were made to predictive coverage for non‑PO invoices.
• Users may need to manually fill fields that were previously (incorrectly) predicted on PO‑driven invoices.

AP Invoices: Workday Related Worktags

This release introduces automatic population of related Workday worktags in AP Invoices. When a driving worktag (for example, Employee or Contingent Worker) is selected, the system fills dependent tags such as Cost Center, Business Unit, and Location using relationships synced from Workday. This reduces manual entry and keeps values aligned with ERP configurations. Header‑ and line‑level worktag configurations are supported.

What's New

• Automatic worktag relationships: Selecting a driving worktag auto-populates related tags per Workday relationships.
• Driver selection rules: Employee and Contingent Worker are mutually exclusive; selecting one sets the driver.
• PO vs. non‑PO handling:
  • Non‑PO invoices: Related tags populate based on the selected driving worktag.
  • PO‑driven invoices: PO values take precedence; related tags are populated from any driving worktags present in PO data.
• Validations: Required tags (for example, Cost Center, Business Unit) must exist in Workday; invalid or missing values are flagged.
• Write-to-SoR flow: Populated header and line worktags are written to SoR and reflected in status updates.
• Manual control: Users can override populated values where allowed.

For more information, contact your Customer Success Manager or reach out to our support team (support@auditoria.ai).

AP Invoices: Dismissed By and Dismissed On columns in Dismissed documents view

The Dismissed tab now surfaces who last dismissed a document and when. These columns reflect the most recent dismissal after any reopen/move-back-to-active cycles, improving traceability and review efficiency.

What's New

• Dismissed By: Shows the user who most recently dismissed the document, updating after each new dismissal.
• Dismissed On: Shows the date/time of the most recent dismissal, updating after each new dismissal.
• UI coverage:
  • Documents list view in the Dismissed tab includes both columns.
  • Document details view displays the same fields.
  • Invoice activity report updated to include Dismissed By and Dismissed On.

Enhanced Visibility & Control

• Clear audit trail for dismissal actions across reopen cycles.
• Consistent “last action” semantics to avoid confusion when documents move between Active and Dismissed.

Note: Values represent the latest dismissal event, not the initial dismissal.

AP Helpdesk: Automatic Task Distribution: Supplier Default Payment Type condition

Automatic Task Distribution (ATD) now supports routing based on the Supplier Default Payment Type from matched supplier records. Admins can add this field as an Input Attribute in ATD rules to assign tasks to specific teams or users according to the supplier’s default payment configuration synced from the ERP.

What's New

• Supplier Default Payment Type available as an Input Attribute in ATD rule conditions.
• Searchable Values dropdown populated from synced ERP values.
• Supports single or multiple selections with OR semantics.
• Works for both new and existing ATD rules.

Notes:

• The Input Attribute labeled Supplier Default Payment Type maps to the Supplier Default Payment Method field on the supplier record in the ERP.
• Supplier Group values are sourced from the ERP via SoR sync. Only synced groups appear in the Values dropdown.

AP/AR Helpdesk: System Sender Management

AP/AR Helpdesk now supports classifying inbound emails from trusted platforms and applications as sender type “System.” Administrators can maintain an allowlist of email addresses, domains, and subdomains expected to generate automated communications. When a sender email matches the configured list, the email is tagged as 'SYSTEM' in the email metadata. This addresses a current gap: important automated emails are often not read by the Smartbot. By allowlisting known system senders and tagging their messages as SYSTEM, these emails are recognized and prioritized for the bot to read and act on, while keeping human‑sent mail separate for analytics and routing. Configuration is enabled per SmartFlow instance and is accessible from the new System Sender Management page. A quick-access button is available from the Helpdesk mailbox.

What's New

• New Sender Type – SYSTEM: Applied to inbound messages that match configured email addresses, domains, or subdomains.
• System Sender Management: Dedicated page to view and manage the allowlist.
• Manual and Bulk Updates: Add single entries inline or manage the full list via CSV upload/download.
• Manual Entry Shortcuts: Enter multiple values using ENTER, TAB, or COMMA delimiters, then submit via Add.
• CSV Versioning (Bulk):
  • CSV uploads overwrite the current list and create a new version.
  • Manual additions are appended to the current configuration without creating new versions.
  • Downloads include the complete current configuration (CSV + manual entries).
  • Version selector displays the current version timestamp and supports downloading historical versions when available.
• Auto-Detect Entry Type: Email/domain/subdomain is inferred from value format; whitespace is trimmed, and duplicates are ignored.
• Inline Notifications: Clear success and error messages for add, upload, and download actions, including processed-entry counts and empty/invalid-file handling.
• Mailbox & Filters: SYSTEM appears as a sender-type badge in the Inbox and thread view and as a selectable option in the Helpdesk Mailbox sender-type filter.
• Analytics Coverage: SYSTEM is available across dashboards and drill-downs that segment by sender type, including:
  • Mailbox Intelligence (Emails Received)
  • SmartBot Processing (Emails Processed, Intents Detected, Invoice Submissions)
  • Chart drill-downs and CSV exports that include sender-type breakdowns

Enhanced Visibility & Control

• Quick Access: “System Sender Management” button is positioned to the right of the mailbox icon. 
• Configured List Overview: Displays the count of configured system senders and the current active version timestamp.
• Responsive UI: Fixed layout with reduced vertical scrolling; the CSV configuration guidance is collapsible to keep focus on list management.
• CSV Template and Guidance:
  • Required header: SystemSenderValue (one entry per row).
  • Examples supported: noreply@system.com, system-domain.com, *.system-subdomain.com.
  • Auto-detection rules: contains “@” = email; starts with “*.” = subdomain; otherwise = domain.

Notes: 

Note 1: Each CSV upload replaces the entire configuration. Values are automatically trimmed and type is auto-detected.

Note 2: SYSTEM emails do not generate AP Helpdesk tasks. Only invoice submission emails are exempt—they may create tasks using the Unknown Sender rules.

2. Fixed Bugs

AR Collections, AR Helpdesk, Workday Connector: Workday Integration: Periodic syncs not updating all data

Symptom: Incremental (delta) syncs from Workday did not capture changes for several objects and fields, including customer/vendor contact edits and “additional data”/custom fields. Updates were missing in Auditoria after scheduled delta runs.

Impact: Customer and vendor records were stale or inconsistent, affecting operations such as dunning classification checks and contact routing.

Workaround: Run a full sync for the Workday source. A scheduled full sync has been enabled for affected tenants, with an additional once‑per‑day full sync to cover “additional data” fields. On‑demand full syncs can be requested through Support.

AP Invoices: Large-attachment documents bypassed Active Data review

Symptom: Documents with large file attachments were written to SoR with status “Written to SoR with File Upload Error” and appeared directly under the Written to SoR tab instead of staying in Active Data for user review. The “Dismiss File Upload Error” action was not available.

Impact: Users could not review or dismiss the upload error within the app, leading to skipped review steps and inconsistent handling of errored documents. Some users resorted to manual uploads to the ERP.

Workaround: Prior to the fix, none in-app; users manually uploaded large files to ERP. After the fix, affected documents correctly remain in Active Data until dismissed.

3. New Known Bugs