Executive Summary

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

1. New and Updated Features

AP Invoices: Validation Error Handling Status Banners

This update extends the Validation Error Handling capability in AP Invoices with two status banners on the Active Data tab. The first banner shows how many documents failed validation and remain in the Active Data tab. The second banner shows how many documents moved to the Written to System of Record (SoR) tab during the most recent synchronization with the Enterprise Resource Planning (ERP) system. The banners give users a running view of documents that need attention and documents that moved after validation issues were resolved in the ERP.

What's New

• Validation failure banner: Adds a banner on the Active Data tab that shows the number of documents that failed validation and remain in the tab.

  • Live count updates: Updates the validation failure count automatically as documents fail.

  • Filtered view: Provides a hyperlink on the count that filters the Active Data list to show only the documents with validation failures, regardless of their current status.

  • Conditional display: Hides the banner when no documents have validation failures.

• Auto-move banner: Adds a banner that shows the number of documents moved to the Written to SoR tab during the last data synchronization only. Moved documents are set to the status "Record Updated by ERP Sync."

  • Synchronization coverage: Reflects documents moved during both automatic and on-demand synchronizations.

  • Dismiss control: Includes a close control that keeps the banner closed until the next synchronization occurs.

  • Direct navigation: Provides a hyperlink on the count that opens the Written to SoR tab with the list pre-filtered to the moved documents.

Notes

• The banners are available on the Active Data tab.

• The auto-move banner shows only the documents moved during the last synchronization. If a later synchronization moves no new documents, the banner is removed.

The Validation Error Handling 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: Bank Details Validation in SmartVendor Templates

This update adds bank details validation to SmartVendor Templates.

What's New

• Bank details validation in templates: Adds bank details validation as a function within SmartVendor Templates.

• Validated fields: Covers three fields — Bank Name, Bank Account Number, and Bank Routing Number.

• Read-only fields: Keeps the three fields read-only on the Document Details page and in SmartVendor Templates. Users cannot change any settings for these fields. The "Extract from Bill File" checkboxes are selected and disabled because the details are extracted from the vendor bill.

• Field display: Adds the fields to the Document Details page when the function is turned on, and shows them in the Preview section of the Document Details page.

• Template visibility: Displays bank details validation on the Templates when both templates and bank details validation are enabled.

• Default state for new tenants: Turns bank details validation off by default for new tenants that have the function enabled.

• Settings migration: Makes bank details validation available to enable from SmartVendor Templates when tenants running SmartFlow configuration move to templates, with settings migrated as-is and no configuration changes required.

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: Supplier Contract Field Override

This update lets header and line-level fields populate automatically from a matched supplier contract during AI Agent processing. The function works the same way as the existing Purchase Order (PO) Override, which populates fields when a purchase order is matched to an invoice. The update reduces manual data entry and keeps invoice data consistent with contract data.

For tenants that use both purchase order matching and supplier contract matching, both functions can run on the same SmartFlow. When both are enabled and a document has both a purchase order and a supplier contract matched, the purchase order takes priority and the supplier contract override does not apply to that document.

What's New

• Supplier contract field population: Populates header and line-level fields automatically from a matched supplier contract during AI Agent processing.

• Configuration setting: Adds the setting "Override values of all Supplier Contract-driven Fields from Supplier Contract" under AP Invoices SmartFlow configuration.

• Contract number format: Adds a field to enter the supplier contract number format, which supports one format per configuration, with helper text below the field to guide the required input.

• Standard field coverage: Populates Vendor and Entity at the header level and all supplier contract-linked fields at the line level by default.

• Extended field mapping: Supports standard fields by default. Maps extended fields beyond the standard supplier contract-linked fields with the help of Auditoria Support.

• Purchase order priority: Gives priority to the purchase order for field population when both the PO Override and supplier contract override are enabled and a document has both a purchase order and a supplier contract matched.

• Coexistence: Allows PO Override and supplier contract override to be enabled together on the same SmartFlow.

• Manual matching dialog: Shows a dialog for header field population when users manually match or change supplier contract references on invoice lines and save.

• Header population choices: Lets users populate header fields from the matched supplier contract, select a specific contract when multiple are matched, select which supplier contract or purchase order to use when different lines have each, or keep existing header values, including manual edits.

Notes

• The setting is OFF by default for all tenants.

• The feature is available for tenants that use SmartFlow configuration settings.

• To apply changes, save the configuration and re-run the SmartFlow.

• Format entry rules: For a prefix + number format, enter the prefix only (for example, SC-1234 → enter "SC-"). For a number + suffix format, replace numbers with "X" and include the suffix (for example, 2025-CON → enter "X-CON").

• In automated AI Agent matching, the purchase order takes priority when a document has both a purchase order and a supplier contract matched. In manual matching there is no automatic priority — users can match both a purchase order and a supplier contract and choose which to use for header field population through the dialog.

• The manual matching dialog appears only when the supplier contract override setting is enabled. Entity is supported by default in the dialog. Vendor is not updated through the dialog and must be matched first.

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: Oracle Fusion Cloud Financials Support

The AP Invoices feature set is now supported for Oracle Fusion Cloud Financials. Customers that use Oracle Fusion Cloud Financials as their ERP can now use the same AP Invoices extraction, matching, configuration, filtering, workflow, audit history, and reporting capabilities already available with other supported ERPs.

What's New

• Invoice data extraction: Extracts invoice data from Oracle Fusion documents, including service periods, shipping and freight, and line-item descriptions. Applies predictive coding, improves classification of documents, and includes freight in the total-amount reconciliation warning.

• Matching and field population: Resolves vendors automatically, populates header fields from a matched purchase order, applies the default entity for single-entity vendors, and provides links to purchase order and supplier contract information on the Document Info page.

• Configuration: Supports multiple date-format configurations, accepts multiple date formats in the date picker in edit mode, and refreshes entity dropdown values after each synchronization with the entity code and name.

• List views and filtering: Adds filtering on standard date and currency fields, orders the Active Data, Written to SoR, and Dismissed Documents views chronologically, shows Dismissed By and Dismissed On details, and supports document tagging on the Active Data tab.

• Workflow: Supports on-demand reprocessing, document assignment to members or teams, summary line editing at vendor and bulk level, SmartVendor Templates with filter persistence, processing of invoice images embedded in the email body, and keeping users on the document details page after Write to SoR.

• Audit and reporting: Records document-level audit history for user edits and system actions, and adds dashboard metrics for documents processed autonomously and without user edits.

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.

AR Collections and AR Helpdesk: Statement Custom Branding and Personalization

Customers that use AR Collections and AR Helpdesk can now customize the format of the AR statements that their AI agents create. AI agents use these statements with dunning emails and in responses to customer queries. The format can include a company logo, a highlight color for key items, and company information such as website, address, and tagline.

Customization is part of the configuration or reconfiguration of a SmartCustomer agent. Once configured, the format takes effect in the next applicable outgoing email message. Branding changes take effect on the next statement run without engineering intervention.

SmartResearch: Match Exception Reasons, Configurable Data Scope, and Aligned Filters

This release groups three SmartResearch updates. First, SmartResearch now returns the specific match exception reason for supplier invoices, in addition to the vendor bill number, vendor name, bill status, approver, and amount due that it already returns. Users can ask for invoices in match exception and see the reason, for example "Unit Cost Variance Exceeds 8%" or "Receipt is Required."

Second, administrators can control how much data SmartResearch ingests. They can set how many years of historical data to load and SmartResearch ingests a reduced set of invoice and bill fields. This limits the data loaded to what users need for analysis and action. Third, SmartResearch now uses data filters that match SmartVendor and SmartCustomer, so that the same query returns consistent data across these modules.

What's New

• Match exception reasons: Returns the specific match exception reason for supplier invoice queries, for example "Unit Cost Variance Exceeds 8%" or "Receipt is Required."

• Configurable historical range: Lets administrators configure how many years of historical data SmartResearch ingests, with a default of 3 years.

• Range scope: Applies the historical data range per tenant or connection at ingestion or synchronization time, and excludes data outside the window.

• Field scoping: Ingests a reduced set of invoice and bill fields.

• Filter alignment: Aligns SmartResearch data filters with SmartVendor and SmartCustomer so that cross-module comparisons return consistent results.

Note: The default historical data range is 3 years, applied at ingestion or synchronization. Data older than the configured range is not loaded.

2. Fixed Bugs

No fixed bugs were reported in this release.

3. New Known Bugs