Executive Summary

Release 26.9.1 delivers updates across the platform, AP Invoices, AP Helpdesk, and SmartResearch.

The platform moves data exports into the background and reports them through an in-app notification center.

In AP Invoices, purchase order (PO) line matching on Workday now matches invoice lines to PO lines on the supplier's item number, so fewer lines fall to manual review when descriptions or prices differ. NetSuite is unchanged, and other systems of record continue to match on description and price.

In AP Helpdesk, email triage moves into the mailbox, and a new analysis of a connected mailbox during agent setup proposes email categories for the mail the standard set does not already cover. SmartResearch becomes available to every user at a subscribed customer rather than to two roles only, and asks what you want where a question has no clear ask.

• Platform – Notification Center for Data Exports: Exports run in the background and appear in a Downloads list, each as a single row that updates in place and offers the file when it is ready.
• AP Invoices – PO Line Matching by Item Number (Workday): Invoice lines match to PO lines on the supplier's item number, ahead of description, unit price, and amount, with formatting differences tolerated.
• AP Helpdesk – Mailbox and Email Triage: Email triage moves into the mailbox view, with By Threads and By Incoming Messages views and sender type filters, so all email is worked from one screen.
• AP Helpdesk – Mailbox Onboarding Analysis: An analysis run during agent setup samples the mail a team actually receives and proposes email categories for the mail the standard set does not already cover.
• SmartResearch – Access for All Roles: Every user at a subscribed customer can open SmartResearch with the role they already hold.
• SmartResearch – Clarification Questions: Where a question has no clear ask, SmartResearch asks what you want before answering, and the answer follows your choices.

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

1. New and Updated Features

Platform: Notification Center for Data Exports

This release moves data exports into the background and reports them through an in-app notification center.

Large exports previously ran while the user waited on the page, which produced long waits and, for the largest exports, timeouts. An export now starts, the user carries on working, and the file is offered when it is ready.

What's New

• Background exports: An export runs in the background. Users can move to other parts of the application while the file is generated.
• A Downloads list: A bell in the top bar opens a panel titled Notifications holding a Downloads tab, which lists exports and report downloads from across the product, including the download options on dashboard cards and the report download on the Documents tab. Each entry shows the file name, its size, and when it was created. The bell carries a count of unread entries.
• A single row per export: An export occupies one row that updates in place rather than adding an entry at each step. The row names the file: while it is being prepared it reads Preparing Bills.csv for download, and once ready it reads Bills.csv is ready to download, gives the size and how long ago it was created, and offers Download, which saves the file. A row for an export that failed or was cancelled offers Retry.
• The file: The export is a CSV named after the tab it was started from, so an export from Bills produces Bills.csv.
• Toasts: Starting an export shows a toast headed Export started naming the file being prepared. A second toast reports the file is ready and offers Download.
• Read filters: The list offers All and Unread, and the tab carries the unread count. An entry that has not been read is tinted and carries its file name in bold, so unread entries stand out under All.
• Before any export runs: A tenant that has produced no exports shows the panel with the Downloads tab, the search box, and the filters in place, over the message No downloads yet.
• Mark all as read: Where unread entries are present, Mark all as read marks them all read in one action, including entries not yet loaded into the list.
• Search and paging: A Search notifications… box finds an entry by name, and Load more brings in older entries. Search, the read filter, and mark all as read apply to the whole list, not only the loaded part.
• An export with no rows: Where the filters match no rows, no file is produced. The row reads No data to export and reports that no data was available for the criteria selected. This row offers no Retry, because the same criteria would return nothing again.
• Starting the same export twice: Starting the same export again, with the same filters, while the first is still being prepared opens a dialog headed Export already in progress. It states that the export is already being prepared, that you will be notified when it is ready, and that changing the filters exports a different set of rows.

Note

• Each export notification goes to the user who started it, and is not filtered by the role that user is currently working in.

AP Invoices: PO Line Matching by Item Number

This release extends item number matching to Workday, so invoice lines match to purchase order (PO) lines on the supplier's item number.

When an invoice arrives, Auditoria matches it to a PO and links each invoice line to the correct PO line. Each candidate line is scored against several criteria, and the highest score wins. Item number matching was previously available for NetSuite only, so on other systems of record, lines were matched on description and price alone, and invoices dropped to manual review whenever a supplier's wording differed, or several lines shared a price.

What's New

• Item number criterion: Invoice lines are matched to purchase order lines on the supplier's item number, carrying the highest weight of any single criterion, ahead of description, unit price, and amount.
• Exact and close matches: An exact item number match scores highest. Where the values differ, the system compares them and matches when the comparison passes its threshold.
• Precedence: A line is matched on its total score across all criteria, so a strong item number match decides the link in most cases, including where the description or the unit price differs from the PO line.
• Label recognition: The item number is read, whatever the supplier calls the column, including Part #, Supplier Part #, Item #, Item, Item Number, Material, Material Number, Model #, Product #, Product, Product Number, and P/N#.
• Formatting tolerance: Hyphens, leading zeros, punctuation, and case differences are disregarded, so an invoice reading 123456 matches a PO line reading 12-3456, and one reading 004567 matches a line reading 4567.
• Consolidated PO lines: Where several invoice lines carry the same item number and one PO line carries that item number with an open balance, all of those invoice lines map to that PO line.
• Lines with no item number: An invoice line carrying no item number matches on description and rate or amount, as it did before this release.
• Item numbers that match more than one line: A line whose item number matches more than one PO line is flagged for review, and the document is set to PO needs review.
• Item numbers that match no line: Where an item number matches no PO line, the Supplier Item Identifier on that invoice line is cleared, and the document is set to PO needs review. The line is not matched on description and rate; instead, an analyst confirms it before the document is written to the system of record.
• Selecting a line by hand: Where matching finds no line on any criterion, an analyst selects the line in the PO Line Number field. The pop-up shows the Supplier Item Identifier for each candidate line.
• Field availability: The Supplier Item Identifier is a standard field for Workday on bills and purchase orders, so Workday tenants see it on the invoice line and on the Document Details page.

Notes

• Where the item number comes from: Matching reads the item number from the supplier's invoice. On Workday, the Supplier Item Identifier field on the invoice line is read-only and is filled from the matched PO line, so after a match, the field carries that line's value, and where nothing matches, it is cleared. The value read from the invoice is not lost: the audit history on the Document Details page records it, together with the reason the field changed. The field is free text entered on the requisition or purchase order line, and applies to goods lines only.
• Item number matching for NetSuite is unchanged.

AP Helpdesk: Mailbox and Email Triage

This release brings email triage into the mailbox view, so that all email is worked from one screen.

What's New

• Triage in the mailbox: Email triage is presented within the mailbox rather than as a separate area. Triage opens from a message inside a thread.
• Two named views: A control above the list switches between By Threads, one row per thread, and By Incoming Messages, one row per incoming message. Each option shows its own row count.
• Where the control appears: The view control appears on the Inbox. Selecting Sent, Drafts, Archived, Blocked, or a label shows the thread list only, and the control returns on going back to the Inbox.
• Sender type chips: External, Internal, System, and Unknown chips sit above the list. One applies at a time, and selecting the active chip again clears it.
• Read and processing state: An unread row carries a dot and shows its subject in bold. On By Incoming Messages each row also carries a status badge, alongside badges for priority and sender type, and a message that was interrupted is marked as such. Status and priority are held per message, so they are not shown on By Threads, which shows a message count instead.
• Triage on request: Opening an email does not start AI triage on its own. An email that has not been triaged shows Run AI Triage, and a run takes about 10 to 30 seconds.
• Following a message: Opening AI triage on a message inside a thread switches the list to By Incoming Messages and selects that message, so the list and the triage pane show the same message.

This feature is available in Early Availability (EA) 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 Helpdesk: Mailbox Onboarding Analysis

This release adds an analysis of a connected mailbox during agent setup. It samples real mail and proposes email categories for the mail the standard set does not already cover, so the agent is tuned before it goes live.

What's New

• Where it runs: Select the mailbox in the work scope step of the agent co-worker wizard, then open Define capabilities, the AP Helpdesk tab, and the Email Categories capability. The panel is headed Mailbox analysis. A later run uses Run analysis again, at the top right of the panel.
• What it reads: The analysis samples the most recent 30 days of inbound email from the connected mailbox, up to 500 emails, and reads the system of record over the same period. It is read only, and no email is sent, changed, or forwarded.
• What it reports: A completed run opens a Mailbox & SOR analysis summary holding five figures:
• Emails sampled, the number the run drew on.
• High-confidence classification, the share whose intent was detected above the confidence threshold, which the tile names.
• Known-sender share, the share classified as an internal, vendor, or system sender.
• Business emails, the share falling into actionable helpdesk request categories.
• Non-business, covering marketing, events, and system noise. This mail is counted in the sample but does not carry a category.
• What it concludes: The run ends with a line naming the outcome and the number of business emails behind it, such as Done, no new categories found in 11 business emails.
• Choosing an autonomy level: The summary sits directly above the question of how much of the helpdesk processing work the agent should attempt on its own, and is offered as the basis for answering it.
• While it runs: A progress bar reports the stage, from sampling through classification to discovering new categories. Stop analysis ends the run and changes no categories.
• How long it takes: A run at the 500 email cap typically completes in under 10 minutes. The sample is capped, so a larger mailbox does not make the run slower.
• What the review list shows: The list holds the standard categories alongside the ones the analysis suggested, each with a message count. Selecting the count opens the emails behind it. A suggested category can be confirmed, which adds it, or dismissed, which discards it, and a category of your own can be added.
• Saving the review: Confirm and dismiss choices are held until the wizard reaches its last step, Activate, and are saved when Run is selected there. Leaving the wizard before then discards them.
• Turning a category off: Standard categories can be turned off but not deleted. A category that is off records who turned it off and when, and states which broader category its mail now routes to. Only categories you add yourself, or confirm from a suggestion, can be edited and deleted.
• Running it again: A new run replaces the previous run's suggestions and counts. Categories already turned on stay as they are.

Notes

• Email that matches no active category is assigned by the distribution rules. Set up a distribution rule for who receives those tasks before the agent goes live.

This feature is available in Early Availability (EA) 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.

SmartResearch: Access for All Roles

This release makes SmartResearch available to every user at a customer whose subscription includes it, regardless of their role.

SmartResearch was previously visible only to users with the SuperAdmin or SmartResearch Analyst role, so granting an accounts payable (AP) or accounts receivable (AR) user access meant assigning them a second role solely to unlock it. Access now follows the customer's subscription.

What's New

• Access by subscription: The customer's subscription determines who can see SmartResearch. Where it is included, every user at that customer can open it. Where it is absent, the menu entry, the page, and the underlying data are unavailable to everyone at that customer.
• Any role: A user reaches SmartResearch with the role they already hold, including AP, AR, Collections, General Ledger (GL), and Procure-to-Pay.

Notes

• Because access follows the subscription and cannot be limited by role, every user in a subscribed tenant can ask SmartResearch about anything the tenant's connections and SmartResearch instances expose, including data outside their own function. It cannot be turned off for a single user or role in this release, so review your connections and SmartResearch instances before it reaches your users.
• The SmartResearch Analyst role remains available as an analytics-only seat, for people such as a VP Finance or CFO who need analytical access without an operational role. It is no longer what grants access.

SmartResearch: Clarification Questions

This release adds a short form of choices that SmartResearch shows when a question has no clear ask, so it can find out what you want before it answers.

A question such as "do an analysis" gives SmartResearch nothing to act on, and the answer that follows reads as a limitation of the product rather than of the question.

What's New

• A form of choices: Where a question has no clear ask, SmartResearch asks what you want before answering, for example What would you like to analyze?
• Short by design: The form asks at most two questions and appears at most once per question.
• Your own wording: Every question on the form includes an Other option. Selecting it opens a box with the placeholder Type your own answer… for a value of your own.
• Ambiguous names: Where a name in the question matches more than one value in your data and none exactly, SmartResearch asks which one you meant.
• Submit or cancel: Submit & start analysis runs the question with the selections made. Cancel runs the question as originally asked, and stops SmartResearch from offering the form again for the rest of that chat. Start a new chat to get it back.
• Nothing happens on its own: The form waits. SmartResearch does not answer until you submit or cancel.
• Selections read back: After Submit & start analysis, the conversation restates the selections in one short sentence. Canceling shows the original question unchanged.
• Selections are kept: Once submitted, the form locks and folds away under Questions submitted. Select it to see the choices again, including after a reload.
• Keyboard: Arrow keys move between options, Enter selects, Shift and Enter submit, and Esc cancels.

Notes

• The form cannot be turned off in Settings or User Preferences.
• Chats opened from Metrics Studio do not show the form. Where a Metrics Studio request is unclear, the agent asks partway through the answer instead.

2. Fixed Bugs

No fixed bugs were reported in this release.

3. New Known Bugs