Executive Summary

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

1. New and Updated Features

Universal ERP Connector: SAP ECC Accounts Receivable Support

This release enhances the Universal ERP Connector with new support for ingesting Accounts Receivable (AR) data from SAP ECC and transforming invoice, payment, and credit memo data into an Auditoria-readable format, providing clear visibility into invoice status, including open, paid, and partially paid balances, as well as applied payments and credit memo activity.

What’s New

• SAP ECC AR support: Added support for transforming AR data in the SAP ECC environment, including entities, customers, invoices, credit memos, and payments.
• Reconstruction of invoice lifecycle statuses Supports identification of:
  • Open invoices
  • Fully paid invoices
  • Partially paid invoices using the Residual Payment Method.
• Payment application visibility: Payments are traced through SAP accounting records to determine:
  • Amount received
  • Amount applied to invoices
  • Unapplied Payments.
• Withholding tax support: Handles invoice reconciliation when withholding tax affects the net payment amount, while preserving visibility into the full original invoice amount.
• Credit memo reconstruction: Supports the identification of both applied and unapplied credit memos and their impact on invoice settlement and reconciliation.

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 feature, please contact your Customer Success Manager or our support team at support@auditoria.ai.

AP Invoices: Automated Document Assignment 

This release introduces a unified set of enhancements for document ownership, automatic document assignment, and team management in AP Invoices.

A new Assignee field has been added across key document views to improve workload distribution, accountability, and visibility for AP teams. This release also introduces automatic document assignment rules that route documents to individual users or teams based on configurable business logic. In addition, users can now use the existing Team Management capabilities to create teams for document distribution.

These enhancements are available when your SmartFlow Skill operates only with AP Invoices as a standalone feature.

What’s New

Assignee Field Across Documents

A new Assignee field is now available across key AP Invoices document views to provide clear document ownership and support more efficient processing. This field allows users to manually assign documents and is automatically populated when assignment rules are configured.

Key capabilities

• Assignee field in document details
  • Displayed prominently in the document header section.
• Role-based assignment controls
  • SuperAdmins and ProcureToPay Managers can assign, reassign, or unassign any document.
  • ProcureToPay Agents can self-assign documents and unassign documents they are currently assigned to.
  • Manually created documents are automatically assigned to the creator.
• Assignee column in document list views
  • Available in the Active Data, Written to SoR, and Dismissed Documents tabs.
  • Users can show or hide the column using Edit Columns.
  • Displays:
    • [None] for unassigned documents
    • AI Agent for autonomous assignments
    • Team name for team-assigned documents
    • Assigned user name for manually assigned documents
• Default filtering
  • The Active Data and Dismissed Documents tabs display, by default, documents assigned to the current user and unassigned documents.
  • Written to SoR shows documents written to SoR by the current user.
  • Note: The default filters are applied automatically to show user-specific results. Clearing these filters allows users to view documents assigned to all users within the selected tab.
• Assignment required before processing
  • Key change in document processing behavior: a document must now be assigned before any actions can be taken on it.
  • Documents must be assigned before actions such as Edit, Attach, Reprocess, Write to SoR, or Dismiss can be performed.
  • Disabled action buttons display a tooltip indicating that an assignment is required.
• Bulk operations
  • Bulk assignment is supported for unassigned documents.
  • Bulk actions such as Write to SoR and Dismiss are available only when all selected documents are assigned to the current user.
  • When selected documents are unassigned, a message is displayed indicating that an assignment is required.
  • Bulk operations are not available for documents assigned to other users.
  • If a user attempts a bulk action on documents assigned to others, a message is displayed accordingly.
• Reporting and filtering
  • The Assignee field is included in downloadable reports.
  • New assignee filters support In and Not In operators.

Automated Document Assignment

SmartVendor – AP Invoices now supports automatic document assignment through configurable distribution policies and rules. The section under Administration settings, where users can now configure rules, is called “Automatic Task and Document Distribution”. 

Key capabilities

• Ability to create Document Assignment Rules
  • Documents can be automatically assigned to individual users or teams. Team assignments use a round-robin mechanism based on the order in which members are added to the list.
• Distribution policies
  • A distribution policy allows users to create document assignment rules for a SmartFlow Skill when document or task distribution is required.
  • Only one distribution policy can be created for each SmartFlow Skill.
  • Each policy supports a unique name and an optional description.
  • Policies can be added, edited, or disabled.
• Assignment rules
  • Assignment rules can be created under a distribution policy for a specific workflow type.
  • Rules are processed in the order they are configured.
  • If no rule applies, the document is created without an assignee.
  • A default assignee can be configured using a final rule with no conditions.
  • Rules accommodate various input attributes, including email from/domain, vendor, entity, address, and some specific fields from Workday ERP, such as Supplier Group and Default Payment Method.
  • Documents can be assigned to:
    • An individual user
    • A team using a round-robin assignment
  • Within a rule:
    • Different attributes use AND logic
    • Multiple values for the same attribute use OR logic
  • Rules can be reordered as needed.
• Role-Based Access and Policy Management
  • SuperAdmins can create, search, and filter distribution policies.
  • The policy list displays key details, including:
    • Name – The name of the distribution policy.
    • Description – A brief summary of the purpose of the policy.
    • SmartFlow Skill – The SmartFlow for which the distribution policy was created.
    • Policy Rules – The number of rules configured in the policy.
    • Distributed Tasks – The number of tasks distributed using the policy.
    • Distributed Documents – The number of documents distributed using the policy.
    • Created Date – The date on which the policy was created.
    • Modified Date – The date on which the policy was last updated.
    • Status – The current state of the policy.
• Auditability
  • User actions and configuration changes are tracked.
  • Audit logs are available for Automatic Task and Distribution Policy configurations, as well as for individual distribution policies.

Team Management for Document Distribution

This release extends existing Team Management capabilities to support shared ownership models and team-based document distribution rules.

What's New:

• Team Management now shows Open Documents counts at both the team and team member levels.
• Users can click the Open Documents count to open the filtered document view (to be viewed in active data) for the corresponding document.

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 feature, please contact your Customer Success Manager or our support team at support@auditoria.ai.

AP Invoices: Ability to Reprocess Documents

This release introduces the ability to reprocess documents on demand in AP Invoices. Users can now re-run extraction, matching, and classification logic on invoices, credit memos, and documents misclassified as "Others" in Auditoria using the most up-to-date system-of-record (SoR) data and current configurations in the Auditoria platform. This feature makes it easier to correct document classification or refresh processing when source records or configuration settings change.

What’s New

• Reprocess Button
  • Location: Located in the top action bar on the Document Details page, alongside Edit, Attach, and Write to SoR. The Reprocess button is available for supported documents in the Active Data tab, regardless of document classification.
  • Availability: Enabled for documents in the Active Data tab, unless the document is already being reprocessed or restricted due to a failed write-back.
  • Button States:
    • Enabled: When the document is in the Active Data tab and not currently being reprocessed.
    • Disabled: When the document is being reprocessed, or if written to SoR but failed due to attachment upload or additional data write errors. In the disabled state, a tooltip displays: “Reprocessing not available for this document.”
• Reprocess Modal
  • How It Works: Clicking the Reprocess button opens a confirmation modal that warns manual edits will be lost and asks the user to confirm before reprocessing begins.
  • Ability to Override Classification: Users can optionally override the document classification, where applicable. For customers using support only for Invoices, the option to override a document to Credit Memo is not available; in such cases, the classification defaults to Invoice.
  • Cancel or Confirm: Users can cancel or confirm. Confirm starts reprocessing, and any manual edits are overwritten.
• Reprocessing Workflow
  • In Progress: The Document Details page is locked with a status overlay while reprocessing is underway. Other actions are temporarily disabled, but users can return to the Active Data tab to continue working.
  • Bulk/List Actions: Write to SoR and Dismiss actions are disabled on documents being reprocessed. Bulk actions provide clear error messages if affected documents are included.
• Processing Logic
  • Full Logic Re-execution: Extraction, fuzzy matching, PO matching, contract matching, predictive coding, and auto-population are re-executed. Reprocessing uses the latest SoR data (vendors, bills, POs, contracts) and current Auditoria configurations.
  • Manual Override: If classification is changed, all relevant logic is re-applied, and the fields associated with the selected document type are updated accordingly.
  • Document Handling: The existing document is updated—no duplicate or new record is created.
• Completion and Indicators
  • Status Update: Document status updates based on results (for example, Record Needs Review).
  • Visual Indicators: Upon completion of reprocessing, a reprocessing icon appears alongside the document’s current status in the Document Status column on the Active Data, Written to SoR, and Dismissed Documents tabs. Hovering over the icon displays a message indicating that the document was reprocessed. On the Document Details page, a [Reprocessed] label appears in the Document Status field. This indicator appears only after the reprocessing cycle is complete.
  • Editable Again: All actions are re-enabled upon completion; users can then review or write the document to SoR.
• Audit History
  • All reprocessing activities are recorded in the document’s audit history, including user, timestamp, old and new classifications (if changed), and the fields updated.
• Additional Notes
  • Manual Review Required: All reprocessed documents require manual review and Write to SoR. Autonomous processing is not available after reprocessing.
  • Duplicate Handling: Duplicates arriving via email during reprocessing are detected; the first to complete is kept as primary.
  • Supported File Types: PDF (including single and multi-document attachments), Excel, and image files are supported. Reprocessing applies only when a single document is identified per attachment. If file type support configurations are changed after a document is created and that document’s file type is later disabled, reprocessing is not supported for that document.
  • No Partial Updates: If reprocessing fails for any reason, the document simply reverts to its last saved state.
  • Non-cancellable: Reprocessing cannot be canceled once started.

At this time, reprocessing may take several minutes to complete. During this period, actions on the document are temporarily disabled until processing finishes. Reprocessing large attachments, such as documents with 50 pages or more, may take longer for the AI Agent to complete.

AP/AR Helpdesk: Configurable Task Priorities

This release introduces configurable task priorities across the AP/AR Helpdesk Task Details and SmartFlow Management.

Task assignees, managers, and administrators can now set and update task priority directly in the user interface using the following values:

• High
• Medium
• Low

What’s New

• Configurable default priorities in SmartFlow Management
  • Administrators can set a Default Task Priority for each business intent in SmartFlow Management.
  • To configure the default priority, follow these steps:
    • Expand the "Add Tasks" section for the selected intent from the Intents and Outcomes page.
    • Use the "Default Task Priority" dropdown menu.
    • Choose from the options: High, Medium, or Low.
  • The current selection will be displayed in bold.
  • The dropdown will close automatically after you make a selection, and no additional confirmation is needed.

• Multiple intent matches
  • When a task matches multiple intents, the system applies the highest-priority intent.
• Configuring Task Priorities in the AP/AR Helpdesk Tasks Tab
  • Users can update task priorities in bulk from the Actions menu. Task assignees, managers, and administrators can select one or more tasks by checking the checkboxes in each row, then choose "Edit Task Priority."
  • The "Edit Task Priority" modal includes the following:
    • Modal label: Edit Task Priority
    • Dropdown label: Select Task Priority
    • Dropdown options: High, Medium, Low
    • Buttons: Cancel and Save
  • When the user clicks "Save," the selected priority will be applied to all chosen tasks.
  • Additionally, users can update the priority directly from the Priority column in the AP/AR Helpdesk Tasks Tab. Each task row includes a Priority dropdown with options: High, Medium, and Low. The current priority value is displayed in bold.
  • Selecting a new value will immediately update the task priority and close the dropdown, with no further confirmation required.

• Task audit logging
  • Task history now records every change to task priority, including the source of the change.
  • Priority updates are logged when set through:
    • AI Agent action
    • Manual update in AP/AR Helpdesk Tasks Tab
    • Manual update in AP/AR Helpdesk Task Details
    • Bulk update in AP/AR Helpdesk Tasks Tab
    • ATD rule
    • High Importance flag
• Audit Logs
  • SmartFlow configuration changes for default task priority are recorded in the audit logs.
  • The logged action is SmartFlow Modified.
  • The summary format is:
    • Source: <sourceSystem> Mailbox: <mailboxAddress>; Intent: <intentNameCamelCase> Modification: defaultTaskPriority [<original.value>] >> [<new.value>]
  • Example:
    • SmartCustomer Source:sage intacct (AR)(INTACCT) Mailbox: ar.clerk.stage.aaron@supervaluecorp.com; Intent: invoiceCopyRequest Modification: defaultTaskPriority [LOW] >> [HIGH]
  • Audit log entries also show who made the change and when, following existing audit log conventions.

AR Helpdesk: Customer Linked Internal Sender Emails

This release adds support for linking internal sender emails to Customer records and working with those links across AR Helpdesk and Customer Details. The goal is to replace manual copy/paste of internal email threads into Customer notes with a structured, auditable linkage that AI Agent can reference.

These enhancements improve how AR and collections teams track and act on internal communications related to a customer’s account.

What’s New

• Linked Record field in Task Details
  • A new Linked Record field appears in task details when the Sender Type is set to Internal or Internal Cohort.
  • Users can search for and select one or more customer records using a dropdown with checkboxes, provided the task is assigned to them.
  • When Sender Type is Internal, the following fields are hidden:
    • Record Name
    • Record ID
    • Status
• For completed (DONE) tasks:
  • If no records were selected, the Linked Record shows [None].
  • If one record was selected, Task Details show:
    Customer Name.
  • If multiple records were selected, Task Details show a count and a dropdown:
    • Dropdown lists each linked record as Customer Name.
    • No checkboxes or “Select all” are available for DONE tasks (read-only view).

• New “Record Link” metadata for internal sender emails in Mailbox
  • When Sender Type is Internal or Internal Cohort, the existing Record Match metadata is replaced with Record Link:
    • Columns:
      • Customer ID
      • Customer Name
      • Linked By (shows the user who linked the email to the record)
    • The metadata area provides an Add Record Link button to manage links:
      • If no records are linked:
        • Only the Add Record Link button is shown (no table, no N/A values).
      • If one or more records are linked:
        • A Record Link table is shown with the linked records.
        • The button label is updated to Manage Record Links so users can maintain existing links (including unlinking as allowed by message metadata).

• AI Agent notes for customer-linked internal emails
  • When an internal sender email is linked to a Customer:
    • AI Agent adds a note to Customer Details for each linked Customer record.
    • The note includes:
      • Who linked the email (Linked By user).
      • Email sender.
      • Subject.
      • A link to view the email.
    • Example note text:
      Internal Sender (test@example.ai) email linked to customer record by <user.name>
  • These notes create a structured audit trail of internal communication associated with each customer.
• Customer-linked internal emails surfaced in the mailbox filtered views
  • From Customer Details:
    • Click Customer Emails to open the related mailbox view.
  • In the mailbox:
    • The Record Match filter results now include Customer-linked internal sender emails, not just external emails.
    • You can further refine results using the Sender Type filter (for example, to focus on Internal senders).
• New “Customer Link” mailbox filter for internal sender emails
  • A new Customer Link filter is available in the mailbox:
    • Works similarly to Record Match, but is limited to internal sender emails.
    • Allows AR and operations teams to quickly pull all internal emails that have been explicitly linked to Customer records.
• Thread-level linking behavior for internal sender emails
  • Once an internal sender email in a thread is linked to a Customer record:
    • Subsequent emails in the same thread are automatically linked to the same Customer record(s).
  • This ensures the entire internal conversation thread is consistently associated with the correct customer.
• Send customer-linked emails from Customer Details
  • From the Customer Details page:
    • Click Send Customer Linked Email.
    • A compose modal opens for drafting and sending an email that is automatically linked to that Customer.
  • Recipient selection:
    • TO/CC/BCC fields now suggest contact email addresses that are stored in Customer Details.
    • This addresses earlier feedback where no contacts were shown in these fields.
  • AI Agent behavior:
    • AI Agent adds a Customer-linked email note to Customer Details with updated message metadata, continuing the same structured audit trail used for internal sender emails.

2. Fixed Bugs

None.

3. New Known Bugs