Executive Summary

This release delivers functional and usability enhancements across the Auditoria platform, including AP Invoices, AP/AR Helpdesk, and AR Helpdesk:

• Platform – Filter and grid view persistence across SmartVendor, SmartCustomer, and AP Accruals: The platform now automatically preserves each user’s last-used filters and grid (table) configurations per tab and SmartFlow, restoring them when users return—even across logouts and session timeouts—until filters are explicitly cleared.

• AP Invoices – Composite SoR support for Document Audit History and Credit Memos: Tenants using Composite SoR configurations now have access to full Document Audit History for AP Invoices SmartFlows, as well as end‑to‑end Credit Memo processing (classification, extraction, and write‑back) for Workday-based Composite SoR setups.

• AP Invoices – Freight-inclusive invoice total reconciliation: Invoice total validation during write to the system of record now incorporates freight/shipping amounts in line with each tenant’s freight configuration (no freight, header-level, or line-level). This reduces false mismatch warnings and clarifies remaining discrepancies with an updated soft warning message.

• AP/AR Helpdesk – Macro intent detection for emails without business intents: When no business intent is detected, AP/AR Helpdesk now assigns exactly one macro intent (Request, Inquiry, Update, Acknowledgement, Unclear, or Unintelligible). This improves reporting, search, filtering, ATD-based routing, and reduces overuse of the NeedsHumanAttention label by reserving it for true exception outcomes.

• AR Helpdesk – Document request support for custom business entity names: Internal Documents now support Custom Entity Names so document requests can match on both SoR business entity names and commonly used alternates or abbreviations. Validation prevents conflicting reuse, and new columns in the Internal Documents list and Audit Log improve visibility into configured custom entity names.

Bugs Fixed: None reported in this release. New Known Bugs: None reported in this release.

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

1. New and Updated Features

Platform: Filter and grid view persistence across SmartVendor, SmartCustomer, and AP Accruals

Filter and grid view settings now automatically persist across sessions in SmartVendor, SmartCustomer, and AP Accruals. Last-used filters and grid configurations are retained when you log out, log back in, or navigate away and return to the same tab.

What's New

• Automatic Persistence
  • Filters and grid configurations are now saved and restored when:
    • Navigating away and returning to the same tab
    • Logging out, session expiration, or logging back in
• Scope of Persistence
  • Per tab: Each tab (such as Documents, Vendors, or Bills) maintains its own settings.
  • Per SmartFlow: Switching between SmartFlows loads the selected SmartFlow's saved settings.
  • Per browser/system: Settings are stored locally. Logging in from a different browser or system, or clearing browser cache, loads the default view.

Clear Filter Behavior

• Using "Clear Filter" removes all applied filters, returns the tab to the default view, and resets the persisted filter state.

Limitations

• Only one persisted view is stored per tab or SmartFlow.
• This feature does not apply to Dashboard tabs.
• Persistence is browser and system-specific; settings do not sync across browsers or devices.

AP Invoices: New Support Added for Composite SoR

Document Audit History and Credit Memo support have been extended to tenants using Composite SoR configurations.

What's New

• Document Audit History

  • SmartFlows configured with Composite SoR now support Document Audit History, enabling users to track SmartBot actions and user edits throughout the document lifecycle.

• Credit Memo Support (Workday Only)

  • Composite SoR configurations using Workday now support Credit Memos as a document type and the entire document processing lifecycle: classification, extraction, and writing to SoR.

To enable Credit Memos for your tenant, contact your Customer Success Manager or reach out to our support team (support@auditoria.ai).

AP Invoices: Freight-Inclusive Invoice Total Reconciliation

This release refines the document reconciliation logic when a document is being written to the system of record (SoR).

Previously, the total amount reconciliation logic only checked that the extracted total equaled the sum of line amounts plus tax. Freight or shipping amounts were not included in this check. As a result, invoices with valid freight charges could trigger soft warnings that the total did not match, even when the math was correct.

Invoice total reconciliation now includes freight/shipping amounts in the validation logic, eliminating false mismatch warnings for invoices with freight charges.

What’s New

• Updated Reconciliation Formula
  • The system now validates invoice totals with: Total Amount = Net Amount (sum of lines) + Tax + Freight
  • The calculation respects your freight configuration settings:
    • Don’t write to system of record: Freight excluded from calculation (no change).
    • Write at header level: Header freight amount included in calculation.
    • Write at line level: Freight line included in net amount; header freight is considered 0.
• Updated Warning Message
  • When a reconciliation mismatch occurs, the warning message now reads: “The extracted total does not equal the sum of line amounts, tax, and freight”.

Benefits

• Eliminates false mismatch warnings on invoices with applicable freight charges.
• Reduces unnecessary manual review of correctly reconciled invoices.
• Aligns reconciliation logic with how freight is written to the system of record.

Configuration

• No additional configuration required. The feature automatically uses your existing freight or shipping settings.

Note: This update only applies to tenants with shipping or freight enabled. Shipping/freight functionality is currently available for Workday only.

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

AP/AR Helpdesk: Macro intent detection for emails without business intents

This release introduces macro intent detection for AP/AR Helpdesk.

When an email received in an AP or AR mailbox does not match any business intent, AP Helpdesk and AR Helpdesk now assigns a single macro intent representing the message’s primary purpose. Macro intents enhance reporting, search, and routing for emails that previously lacked intent classification, improving visibility and operational handling of these messages.

What’s New

• Macro intent classification when no business intent is detected

  • When an AP/AR Helpdesk email has no business intents detected, it is classified into exactly one macro intent.

  • Available macro intents:

    • Request – Sender wants something done (for example, process, approve, fix, send, forward, route).

    • Inquiry – Sender wants information or clarification (for example, status, timing, confirmation, explanation).

    • Update – Sender provides information or a status update, without asking for action.

    • Acknowledgement – Sender confirms receipt, agreement, or expresses thanks, with no new information or action requested.

    • Unclear – Content is intelligible but the main purpose is ambiguous.

    • Unintelligible – Content has too little or malformed information to determine intent.

  • A message qualifies for a macro intent only when a business intent is not detected.

  • A message can have one or more business intents or one macro intent; it cannot have both at the same time.

• Detected intent and Task Details behavior

  • The assigned macro intent appears as the detected intent on the Helpdesk email and its task (for example, Request, Inquiry, Update, Acknowledgement, Unclear, Unintelligible).

  • When business intents are added by reprocessing, the macro intent is automatically removed and replaced by the detected business intent(s).

  • When all business intents are removed via Task Details and the message is reprocessed, a macro intent is applied.

  • Manual editing rules in Task Details:

    • Request / Inquiry / Update / Acknowledgement can be changed between one another.

    • Request / Inquiry / Update / Acknowledgement cannot be changed to Unclear or Unintelligible.

    • Unclear / Unintelligible can be changed to Request / Inquiry / Update / Acknowledgement.

• Dashboard and reporting updates

  • Macro intents are included in Tasks by Detected Intent tables.

  • A new SmartBot Processing – Macro Intents Detected chart is available.

  • The existing Intents Detected chart has been renamed to Business Intents Detected.

  • Macro outcomes Request / Inquiry / Update / Acknowledgement count toward the Emails Processed (single intent) metric.

  • Dashboard report CSV exports now include macro intent classifications alongside business intents.

• Search and filtering

  • Macro intents (Request, Inquiry, Update, Acknowledgement, Unclear, Unintelligible) are searchable and filterable wherever intent-based filters are available (for example, in the Tasks tab).

  • This allows operations teams to group and analyze tasks based on macro intent when no business intent exists.

• Automatic Task Distribution (ATD) routing by macro intent

  • Automatic Task Distribution (ATD) now supports assigning tasks based on macro intent classification.

  • Routing rules can consider macro intents to distribute tasks when business intents are not available.

• NeedsHumanAttention (NHA) behavior changes

  • The NeedsHumanAttention intent is no longer applied as an outcome when no business intent is detected.

  • The NeedsHumanAttention (NHA) label is not added for macro intent outcomes and is not applied concurrently with macro intents.

  • The NeedsHumanAttention (NHA) label is added only when business intent processing results in an exception.

  • Business intents such as Record Update, Customer Dissatisfaction, Cancellation Request, and ShortPay Inquiry no longer cause the NHA label to be added by default, because no processing path is defined that would result in an exception outcome for these intents.

AR Helpdesk: Document request support for custom business entity names

This release adds support for Custom Business Entity Names in the Internal Documents page of AR Helpdesk.

Previously, AR Helpdesk could match document requests to internal documents only when the business entity name in the request matched a value synced from the system of record (SoR). If a payer used a short form, abbreviation, or alternate spelling of the entity name, the request could fail to match and result in an exception.

With this change, users can define custom entity name equivalents for each internal document. Document request processing now matches on both the SoR entity name and any configured custom entity names, with support for minor differences in punctuation and capitalization.

What’s New

• Custom entity names for internal documents

  • Internal documents remain associated with a Business Entity value synced from the SoR.

  • A new Custom Entity Names field is available for all internal documents.

  • Users can define multiple alternate names that are commonly used for the same business entity (for example, a long legal name and its commonly used short form).

• Add New Document from the Internal Documents tab

  • From the Internal Documents tab, you can now configure custom entity names when you add a document:

    • Select Internal Documents from the top navigation.

    • Click Add New Document.

    • In the Add New Document panel, provide:

      • Name – The internal name of the document.

      • Type – The document type (for example, statement, invoice copy, dunning letter) from the dropdown.

      • Entity – The business entity associated with this document, from the synced SoR entity list.

      • Custom Entity Names (optional) – One or more alternate names that payers may use for this entity.

        • Use this field to store abbreviations, short forms, or alternate spellings that should map to the same entity.

        • You can add up to 20 custom entity names for a single document.

        • Helper text appears under the field: “Press ENTER, TAB, or COMMA after each value.”

      • Document – Upload the file to use as the internal document.

    • Click Save to create the internal document with its custom entity names.

• Edit Document – Custom Entity Names field

  • When you edit an existing internal document, the Custom Entity Names field is available with the same behavior:

    • You can add, remove, or change custom entity names.

    • Validation prevents using the same custom entity name in conflicting configurations (see below).

• Duplicate custom entity name validation

  • To prevent ambiguity across internal documents, AR Helpdesk validates new custom entity names when you save:

    • If a custom entity name is already used for the same document type, AR Helpdesk displays:

      • “Custom Entity Name already in use for specified document Type.”

    • If configuration also considers currency, and the same custom entity name is already used for the same document type and currency, AR Helpdesk displays:

      • “Custom Entity Name already in use for specified document Type and Currency.”

• Document request matching using custom entity names

  • The Document Request intent now uses both:

    • Document Type + SoR Business Entity Name, and

    • Document Type + Custom Entity Names.

  • When an incoming request contains:

    • A document type

    • A business entity name that matches either the SoR entity name or one of the configured custom entity names

    • Locates the matching internal document

    • Drafts a reply with the matched document attached.

  • Matching supports minor variations in punctuation and capitalization.

• Behavior when entity is not provided in the request

  • Existing behavior for document type–only requests is preserved:

    • When a document request includes only a document type (no entity name), AR Helpdesk continues to use the existing 90‑day look-back on customer invoices.

    • AR Helpdesk can return one or more versions of the requested document type across entities and currencies that appear on synced customer invoices from the previous 90 days.

• Internal Documents and Audit Log updates

  • Internal Documents list:

    • A Custom Entity Names column is added between the Entity and Currency columns.

  • Internal Documents → Audit Log:

    • A Custom Entity Names column is added between the Entity and Currency columns.

    • When custom entity names are edited, the Audit Log records an action such as:

      • Custom Entity Names Updated.

2. Fixed Bugs

None.

3. New Known Bugs