Executive Summary
Release 26.7.1 delivers changes across AP Invoices, AP Helpdesk, SmartResearch, and Connectors. The main themes are stronger invoice validation and rule configuration in AP Invoices, entity-based routing in AP Helpdesk, more accurate default query behavior and reusable workflows in SmartResearch, and reconciliation and sync improvements in Connectors.
In AP Invoices, this release documents the full Business Rules capability and adds new date-comparison operators, calculated-amount fields, keyword-based document rules, rule copying, and a blocking validation before writing to the System of Record (SoR). AP Helpdesk adds entity-based invoice forwarding. SmartResearch now returns active records by default and introduces Skills. Connectors add an hourly Workday Purchase Order (PO) and Contract sync, and two reconciliation email notifications.
AP Invoices – Business Rules: A configurable IF-THEN rule engine lets Superadministrators define organization-specific field population logic that runs automatically during invoice processing. This release adds relative date operators, a Calculate As operator for amount formulas, and rule copying, and documents the full set of rule-creation and management capabilities.
AP Invoices – Keyword Matching in Business Rules: Business rules can now match a keyword and value in a document header or footer, allowing rules to act on identifiers such as an account number that are beyond the standard extracted fields.
AP Invoices – Invoice Total Validation: A total-amount mismatch now blocks the Write to SoR action, ensuring invoices reconcile before they reach the Enterprise Resource Planning (ERP) system.
AP Helpdesk – Forward Invoices by Entity: Invoices are forwarded to different email addresses based on the invoice entity, with a default address fallback.
SmartResearch – Active Records by Default: Vendor, customer, and invoice queries return active records by default, aligning SmartResearch counts with the dashboards.
SmartResearch – Skills: Users can define reusable workflows once and run them again from chat or the app.
Connectors – Hourly PO and Contract Sync for Workday: Purchase Order and Contract records sync approximately every hour, so invoice processing automatically uses current data.
Connectors – Sync Success Email: A confirmation email is sent after each clean sync, so recipients receive positive confirmation of a successful run.
Connectors – Mismatch Report Attached to Email: The existing mismatch report is attached to the reconciliation error email, so the full distribution list can review it immediately.
Bugs Fixed: Included in this release. New Known Bugs: None reported in this release.
1. New and Updated Features
AP Invoices: Business Rules
This release introduces Business Rules, a configurable IF-THEN rule engine in SmartVendor Settings that lets Superadministrators define organization-specific logic for populating fields on invoices without engineering involvement. Rules run automatically at the end of document processing, after standard extraction and configuration have been applied, and act as the final population step.
What's New
- Is Within / Is Beyond operators: Adds two IF operators for date fields that compare two date fields on the same document (for example, Service Period End against Service Period Start) across a selected period. Period options are 1 month, 3 months, 6 months, 1 year, or a custom duration in years, months, and days. Is Within is true when the difference is within the period; Is Beyond is true when the difference exceeds the period. Evaluation uses the extracted date values from the document, not the system date.
- Calculate As operator: Populates amount fields using arithmetic formulas with +, -, *, and /, referencing other amount fields with the @ symbol (for example, Net Amount = Total Amount - Tax - Freight). The standard order of operations applies; division by zero yields no value.
- Copy rule: Duplicates a rule from the rule list or from the rule setup page. The copied rule is assigned the last order of execution, which the user can change during setup. Existing duplicate-rule validation continues to apply.
Rule creation and management
- Business Rules tab: Adds a Business Rules section to SmartVendor Settings, where Superadministrators can create, edit, enable, disable, and delete rules. P2P Managers and Agents have read-only access.
- IF-THEN rule structure: Builds each rule from IF conditions (field, operator, value) and one or more THEN actions. Supported IF operators include Equals, Not Equals, Contains, Is Blank, Exists, and numeric comparisons. THEN actions support Set to Value and Copy from Field.
- Header and line-level fields: Supports both header-level and line-level fields in conditions. When a line-level field is used, the rule evaluates each line individually and applies actions only to matching lines.
- Apply-to-all rules: Creates rules without an IF condition that apply to every document processed through the configuration.
- Select All for value lists: Selects all available values for Vendor and Entity fields in one action. Values added to the ERP later are automatically included at runtime without resaving the rule.
- Boolean field population: Sets a Yes/No field based on whether another field is blank or populated (for example, set PO Invoice to Yes when a PO Number exists).
- Copy header values to lines: Copies a header-level field value to all line items (for example, applying a header Tax Code to every line).
- Cross-type value copying: Copies values into text fields from other field types, with the value converted to text. Amount fields copy between amount fields with decimal precision preserved; date fields copy between date fields.
- Text concatenation: Builds a text field value by combining other fields (for example, populating a blank invoice number from the invoice date and account number).
- Order of execution: Runs enabled rules top-down in a defined order. Users reorder rules by dragging or by entering an order number directly. Rules are organized in Enabled, Disabled, and All views.
- Rule administration: Includes search, filtering with persistence across navigation, bulk enabling, disabling, and deleting, and exporting rules to a CSV file.
- Audit trail: Records each rule execution in the document audit trail, showing the field, the extracted value, the value assigned by the rule, and the rule as the source.
Notes
- Business Rules apply to invoices in this release.
- A rule targeting a field that is active in the tenant configuration runs during processing; a rule targeting an inactive field remains saved for later use.
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: Keyword Matching in Business Rules
This release adds keyword matching to Business Rules, supporting keywords in a document beyond the standard field set. When configuring a business rule, a user can specify a keyword and its value, and the rule checks whether the document contains that pair. This supports cases where rules act on identifiers, such as an account number, that are beyond the standard extracted fields.
The search runs against the invoice's header and footer sections, which keeps processing costs, accuracy, and latency predictable.
What's New
- Document field group: Adds a new "Document" section in the IF condition dropdown with a "Document" sub-selection.
- Contains operator: Matches a keyword and its value within a document as part of an IF condition.
- Alphanumeric values: Accepts alphanumeric input in the value field.
- Header and footer scope: Searches the header and footer sections of the invoice.
- Synonym handling: Automatically matches label variations, so a search for "Account Number" also matches forms such as "Acct #" and "Reference Acc No."
Notes
- This capability is verified for account number rules in this release. Support for additional keyword types is validated progressively.
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: Invoice Total Validation
This release introduces a blocking total validation for Write to System of Record (SoR). When a user triggers Write to SoR, the system confirms that Net Amount plus Tax plus Freight equals the Total Amount before the invoice is written, and the user resolves any mismatch first. This keeps invoice totals consistent between Auditoria and the ERP.
What's New
- Blocking validation: Requires the invoice total to reconcile with the sum of the line amounts before Write to SoR proceeds.
- Validation sequencing: Evaluates the total check first; upon passing, soft warnings follow.
- Freight-aware check: Validates Net + Tax + Freight = Total when freight handling is on, and Net + Tax = Total when it is off (default).
- Blocking error modal: Displays an error modal with a single "OK" action, allowing the user to return to the document and correct the total.
- Bulk write support: Validates each document independently during a bulk Write to SoR and lists the invoice numbers that need correction.
- Soft warnings retained: Continues to show remaining soft warnings in the existing modal after the total check passes.
Notes
- The validation pattern is configurable and can be extended to other warnings on request.
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 Helpdesk: Forward Invoices by Entity
This release enables AP Helpdesk to forward submitted invoices to different email addresses based on the invoice entity. AP Operations can map entity values to forwarding addresses so invoices route to the correct recipient automatically. When no entity value is extracted, set, or matched, the invoice is forwarded to the default address.
What's New
- Entity-based forwarding: Enables forwarding by entity in the Transfer Invoice action.
- Multiple mapped addresses: Maps multiple forwarding email addresses to synced entity values.
- Entity extraction: Extracts the entity value from the Bill To and Billing Address for non-duplicate invoices.
- Entity field in task details: Surfaces the extracted or matched entity value and allows manual setting or editing.
- Fuzzy matching: Matches extracted entity values against synced entities to handle format variation.
- Default address fallback: Forwards to the default address when no entity value is extracted, set, or matched.
- Review task on low confidence: Routes the invoice to a review task instead of an autonomous transfer when no entity match or a low-confidence match occurs.
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.
SmartResearch: Active Records by Default
This release updates SmartResearch (SR) to return active records by default for vendors, customers, and invoices. This aligns SR counts with the dashboards, which show active records. As a result, SR answers and dashboard values report the same counts.
What's New
- Active vendors default: Returns active vendors only by default for vendor queries.
- Active customers default: Returns active customers only by default for customer queries.
- Active invoices default: Returns active, non-canceled, non-voided invoices by default for invoice queries.
- Explicit inactive requests: Includes inactive records when the user asks explicitly (for example, "include inactive," "show all," or "inactive vendors").
- Consistent behavior: Applies the same default across vendors, customers, and invoices.
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.
SmartResearch: Skills
This release introduces Skills in SmartResearch — reusable workflows that a user defines once and runs again. A Skill captures what the analysis does, when to run it, how it runs, and what the output looks like. Users describe the workflow in plain language through the Skill Builder form; no code is required.
What's New
- Skill Builder form: Opens beside the conversation to capture Name, Purpose, Trigger phrases, Defaults, Steps, and Output.
- Chat and app triggers: Starts every Skills action from chat, with an app button for most actions.
- Automatic draft saving: Saves progress automatically and keeps unsaved work as a draft.
- Saved and draft states: Marks each Skill as Saved (runnable) or Draft (finish before running).
- Automatic and on-demand runs: Runs automatically when a request matches a Skill's trigger phrases, or on demand from the library or chat.
- Skills Library: Lists all Skills with search, sort (Recent or A–Z), and filter (All, Saved, Draft).
- Edit and delete: Reopens a Skill in the Skill Builder to change it, or removes it permanently.
- Suggestion chips: Offers ready-made field values that can be inserted and adjusted.
Notes
- Skills are private to the user who creates them.
- Skills run when invoked in a conversation or from the library.
- Skills are saved to the user's account and are available in future conversations.
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.
Connectors: Hourly PO and Contract Sync for Workday
This release introduces an automatic hourly sync of Purchase Order (PO) and Contract records from Workday, providing near-real-time data updates. The sync keeps PO and Contract data current when changes occur during processing—for example, when funds are added to a PO—so invoice processing automatically uses the latest data. All users can confirm data freshness using the last-sync timestamp displayed in the PO & Contracts tab.
What's New
- Hourly incremental sync: Pulls PO and Contract records changed since the last successful sync, per enrolled Workday source.
- Last-sync timestamp: Displays a read-only timestamp of the last PO and Contract sync in the user interface.
- Concurrency handling: Defers to the main scheduled sync when it is already running on that source.
Notes
- Sync timing is approximate. Although the sync frequency is one hour, it runs through a queued system and does not occur at exact one-hour intervals.
- Applies to Workday PO and Contract objects. The main scheduled sync continues unchanged.
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.
Connectors: Sync Success Email for Universal Connector
This release adds a success email for Universal Connector sync reconciliation. The email is sent each time a sync completes successfully, giving recipients confirmation that the run completed as expected. This feature is available only to Universal Connector users.
What's New
- Success email: Sends a confirmation email after each sync run that reconciles cleanly.
- Existing recipients: Uses the alert email distribution list already configured for failure notifications.
- Distinct content: Uses a subject and body that differ from the failure alert.
- One per run: Fires once per sync run, on confirmed clean completion.
Note: The notification uses the existing configuration.
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.
Connectors: Mismatch Report Attached to Email for Universal Connector
This release updates the reconciliation error notification email for Universal Connector users. The email now includes the existing CSV mismatch report as an attachment, allowing the full distribution list to review mismatches immediately and make faster dunning decisions.
What’s New
- Report attachment: Attaches the existing CSV mismatch report to the reconciliation error notification email.
- Same file: Attaches the same file written to storage without reformatting.
- Consistent delivery: Keeps the existing recipient list, subject, body, and storage behavior unchanged.
Note: This update applies only to reconciliation error emails for Universal Connector users.
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.
2. Fixed Bugs
SmartResearch: Canceled and voided invoices inflated query results
- Symptom: Invoice-related questions returned counts and dollar amounts that included canceled and voided invoices, producing inflated AP aging, outstanding invoices, and other invoice metrics.
- Impact: Reported invoice counts and amounts were overstated and did not align with dashboard values, undermining confidence in AP aging and related figures.
- Workaround: Users could explicitly ask to exclude canceled invoices in each query. With the fix, canceled and voided invoices are excluded by default and included only when a question explicitly requests them.
SmartResearch: Task assignee not returned in task breakdowns
- Symptom: When asked for a breakdown of task assignments per person, SmartResearch reported that no assignee field existed and instead returned the task's sender or vendor.
- Impact: Per-person task reporting was not usable, because vendor labels appeared where people's names were expected.
- Workaround: No workaround was available. With the fix, task breakdowns return the actual assignee from the task record.
SmartResearch: Amount filter results are inconsistent with the selected criteria
- Symptom: Questions that filtered documents by amount (for example, totals by currency, or invoices above a threshold) could return values that did not match system records, depending on how the question was phrased.
- Impact: Results for amount-based questions could differ from dashboard values, requiring users to verify figures manually.
- Workaround: Specify the exact amount field (for example, "total amount") and the intended filters in the question to return values that match the dashboard.
SmartResearch: Responses did not match system records in some queries
- Symptom: Certain questions returned values that differed from the corresponding records displayed in the application.
- Impact: Users could receive figures that did not match system records, reducing confidence in results.
- Workaround: No workaround was available. Users could verify values against the application pages.
SmartResearch: Instance panel missing connection details
- Symptom: The instance panel showed only the referenced SmartFlow instances and did not display the System of Record connection or mailbox associated with the instance.
- Impact: Users could not confirm from the panel which data source the instance was connected to.
- Workaround: No workaround was available. With the fix, the panel displays the System of Record connection and mailbox information when SmartFlow instances are selected during instance creation.
SmartResearch: Clarifying questions displayed in an unclear format
- Symptom: When SmartResearch rephrased a request to confirm scope, the rephrased text was presented as a statement rather than as a single, clear question.
- Impact: Users found it harder to confirm what the AI Agent was about to answer.
- Workaround: No workaround was available.
SmartResearch: Sidebar width adjustment
- Symptom: The sidebar width did not present content at a comfortable size.
- Impact: Reduced readability of the sidebar content.
- Workaround: No workaround was available.
Super Administration: ERP connection count showed zero for SmartResearch instances
- Symptom: On the system connections page, a connection used by a SmartResearch instance displayed a "Used by" count of 0 even when active instances were using it.
- Impact: The connection appeared unused, and the delete action was incorrectly available on connections that were in use. No data loss occurred.
- Workaround: No workaround was available.
3. New Known Bugs
No new known bugs were reported in this release.