Executive Summary

Release 26.8.1 delivers updates across AP Invoices, AR Collections, and SmartResearch.

The AP Invoices updates focus on data accuracy and workflow protection: automated population of the Remit-to Connection field for Workday, an expanded set of business rule capabilities, a safeguard that prevents Auditoria from overwriting documents already resolved in the enterprise resource planning (ERP) system, and standardized SmartVendor Templates behavior for field extraction and field ordering.

The AR Collections update corrects Open Accounts Receivable (AR) calculations for customer hierarchies, so that parent and child customer balances resolve accurately in the Data Navigator.

The SmartResearch updates let finance users create and edit key performance indicators (KPIs) and metrics using natural language, and add Oracle Fusion Accounts Payable as a supported data source.

• AP Invoices – Automatic Population of Remit-to Connection Field (Workday): The system populates the Remit-to Connection field using a three-step cascade, reducing manual selection of supplier addresses.
• AP Invoices – Business Rules Enhancements: Business rules now include new field options, target-field labeling, case-insensitive matching, and clearer handling of rules referencing inactive fields.
• AP Invoices – Pre-Write Draft Status Check for Validation-Failed Documents: A status check verifies a document's Workday status before a retry write, preventing Auditoria from overwriting documents that have already been resolved in the ERP.
• AP Invoices – Field Extraction Eligibility and Field Ordering in SmartVendor Templates: Templates define which fields are eligible for extraction from the bill file and ensure fields are displayed in a standardized, persistent order across all tenants.
• AR Collections – Open AR with Customer Hierarchies: Open AR values correctly reflect parent and child customer relationships.
• SmartResearch – Metrics Studio: Users can create and edit KPIs and metrics with natural language and track a validated or not-validated status per metric.
• SmartResearch – Oracle Fusion AP Data Source: SmartResearch supports natural language questions against Oracle Fusion Accounts Payable data, alongside existing sources.

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

1. New and Updated Features

AP Invoices: Automatic Population of Remit-to Connection Field (Workday)

This release introduces automatic population of the Remit-to Connection field for AP Invoices in Workday. Auditoria matches invoice data against Workday supplier profiles to determine where payments should be routed, reducing manual selection.

Population Cascade

Auditoria uses a three-step cascade to populate the Remit-to Connection field. The system proceeds to the next step only if the previous step does not return a result.

1. Default Supplier Connection: The system checks for a Supplier Connection marked as Default in Workday.
2. Single Supplier Connection fallback: If no Default Supplier Connection is set in Workday and the vendor has exactly one Supplier Connection, Auditoria selects that Supplier Connection.
3. Address matching fallback: If the vendor has multiple Supplier Connections, Auditoria extracts the remit address from the invoice and matches it against the Remit-to Addresses stored for that vendor. Matching accounts for variations in abbreviation (for example, "St." and "Street"), word order, missing or extra address components, and formatting.

If the cascade does not produce a match, the field remains blank for manual selection, unless Predictive Coding applies. See Predictive Coding Fallback below.

Configuration

• Setting location: Enable this feature in SmartFlow Configurations → AP Invoices using the Validation and Auto-population of Supplier Connections setting.
• Required: The Remit-to Connection field is visible on the Document Details page and auto-population runs during SmartBot processing.
• Not Required: The Remit-to Connection field is not shown and no auto-population runs.
• Defaults: Existing tenants already using this field default to Required. New tenants default to Not Required.

On-Screen Messages

Auditoria displays a banner when the Remit-to Connection field is not populated automatically:

• No match: "Supplier Connection(s) for Vendor doesn't match with document" The user must select a value manually before Write to SoR.
• Ambiguous match: "Multiple Supplier Connections matches found. Manual selection required"
• No remit address detected: "No remit address detected - Manual selection required"
• No Supplier Connections in Workday: "No Supplier Connections available for this vendor" This message is shown when both the remit address and the Supplier Connections are missing.

Predictive Coding Fallback

Predictive Coding is configured per field in SmartVendor Templates and is disabled by default for the Remit-to Connection field.

• When Predictive Coding is enabled, the cascade runs first. If the cascade does not produce a match, Predictive Coding populates the field using historical data. Values populated this way display the standard information-icon tooltip used for other Predictive Coding fields.
• When Predictive Coding is disabled, the field remains blank if the cascade does not produce a match.
• If the vendor has no Supplier Connections in Workday, Predictive Coding does not run, because no values are available in the dropdown.

Audit History

Each automated action is logged in the document's Audit History as an AI Agent action. The Determined By entry identifies the cascade step that populated the field: Default Supplier Connection, Single Supplier Connection, or Remit to Address Validation. Manual changes are recorded separately as user edits with the action Modify, showing both the previous and updated values.

Notes

• Workday only: This feature is available only in Workday ERP tenants.
• Autonomous write: Auditoria does not perform an autonomous write if a match is missing, if the match is ambiguous, or if no remit address was detected. If a vendor has no Supplier Connections in Workday, autonomous writing proceeds as normal.
• Manual override: Users can select or change a Supplier Connection from the dropdown at any time. The dropdown lists all Supplier Connection Names available for the matched vendor, with no restriction on manual selection.

This feature is currently in Early Availability. To enable it, contact your Customer Success Manager or Auditoria support at support@auditoria.ai.

AP Invoices: Business Rules Enhancements

This release expands how business rules are configured and managed for AP Invoices.

New Rule Capabilities

• Entity and Total Tax fields: Rules can now both evaluate and update the Entity and Total Tax fields. The Entity field can be selected in both the IF and THEN conditions of the same rule.
• Date conditions: Date fields support two operators: Is Within and Is Beyond.  
• Header and Line field labels: In the Target Fields column, each field is labeled Header or Line to indicate which part of the invoice the rule targets.
• Case-insensitive matching: The Contains operator matches text regardless of uppercase or lowercase characters.

Rules That Reference Inactive Fields

If a field used in an existing rule is set to Not Required or disabled in SmartFlow Settings or SmartVendor Templates, the system identifies the affected rule:

• Warning icon: An amber triangle appears both at the start of the rule row and next to the target field name, indicating which part of the rule is invalid.
• Tooltip: Hovering over the warning icon displays: "This rule references one or more fields that are no longer active as per the configurations. The rule will not apply to inactive fields. Re-enable the field(s) or update the rule"
• Retained display name: The display name of the field is saved when the rule is created and continues to display if the field is later disabled.

Processing Order

The processing order is updated so that business rules are applied before assignment and approver selection:

1. Business rules: Auditoria applies business rules to populate or change field values.
2. Assignment: For tenants using Document Assignment with business rules, the assignment mechanism runs after field values have been determined by the rules, so that distribution rules evaluate against the final values.
3. Approvers: Approver determination runs after the final values are populated by business rules.

This feature is currently in Early Availability. To enable it, contact your Customer Success Manager or Auditoria support at support@auditoria.ai.

AP Invoices: Pre-Write Draft Status Check for Validation-Failed Documents

Documents that fail Workday custom validations are held in Active Data with a "Validations Failed in ERP" status so that users can resolve errors and retry the write from Auditoria. In scenarios where one team resolves documents directly in Workday while another works the Auditoria queue, a retry write could overwrite values already corrected in the ERP.

This release adds a status check that runs before a retry write. If the document is no longer in Draft status in Workday, the write is canceled so that the corrected ERP state is preserved, and the document moves to the Written to SoR tab.

What's New

• Status verification: When retrying a Write to SoR on a document that previously had validation errors, Auditoria verifies the document's current status in Workday before proceeding. The existing "Writing document to ERP" overlay remains visible while the check runs.
• Overwrite prevention: If the document is no longer in Draft status in Workday, the write is skipped, and no data is sent to Workday. If the document is still in Draft, the write proceeds with no change to existing behavior.
• Queue management: Documents with skipped writes move from the Active Data tab to the Written to SoR tab, preventing further conflicting edits.
• Bulk writes: When a bulk Write to SoR is triggered, the check runs for each document in the batch. Documents that fail the check are excluded from the batch and moved to the Written to SoR tab. The remaining documents proceed with the normal write flow.
• In-session modal: If the user is on the document details page when the write is skipped, the loader is replaced by a modal:

"This document is no longer in Draft in your ERP — it may have been updated or resolved directly. The write has been cancelled to prevent overwriting the current ERP state. This document will be moved to Written to SoR. No further edits are allowed in Auditoria."

The modal has a single action, Continue. Selecting it moves the document to the Written to SoR tab and returns the user to the Active Data tab.

• User not on the document page: If the user has navigated away while the check is running, the document is moved directly to the Written to SoR tab with no intermediate status and no user action required, consistent with the existing four-hour sync auto-move behavior.
• Document status: These documents show the status "Record Updated. Resolved in ERP".
• Information banner: A blue information banner appears on these documents in the Written to SoR tab:

"Moved to Written to SoR as this document is no longer in Draft status in your ERP — it may have been updated or resolved directly. The values shown here reflect the document's last state in Auditoria. To view the final updated values, check the Bills tab."

This banner is distinct from the existing ERP sync banner, to indicate that the move was triggered by a skipped write rather than by a sync.

Audit History

Each skipped write is logged in the document's audit history:

• System action: "Write Skipped - Document No Longer in Draft in ERP" This entry includes the document's detected Workday status at the time of the check.
• User action: "Moved to Written to SoR (Write Skipped)" This entry records the user who selected Continue and the timestamp.

Notes

• This check runs only during retry writes for documents that had validation failures. It does not affect first-time writes.
• After a document moves to the Written to SoR tab through this process, it cannot be edited further in Auditoria.

AP Invoices: Field Extraction Eligibility and Field Ordering in SmartVendor Templates

This release standardizes the field order in SmartVendor Templates.

Field Group Order

The templates table displays field groups in the following order:

1. Header Fields — Standard
2. Header Fields — Extended
3. Line Fields — Standard
4. Line Fields — Extended
5. Functionalities

Functionalities, such as Bank Details Validation, always appear at the end of the table.

Standard Header Field Sequence

Vendor, Chart of Accounts, Due Date, Date, Vendor Bill Ext ID, Currency, Total Amount, Total Tax, Net Amount, Payment Terms, Invoice Received Date, Entity, Freight/Shipping, Approver, Bot Confidence Level.

Standard Line Field Sequence

Description, Service Period Start, Service Period End, Prepaid, PO Number, PO Line Number, Contract, Contract Line Number, Line Entity, Cost Center, Spend Category, Quantity, Price, Amount, Account.

Fields that do not apply to the tenant's ERP do not appear in the table, and the next applicable field in the sequence takes that position.

Dependent Field Pairs

The following pairs always remain adjacent, in the order shown: PO Number and PO Line Number (Line), Contract and Contract Line Number (Line).

Extended Fields

• Extended fields are tenant-specific and may appear in any order within their group.
• New extended fields are appended to the bottom of the applicable extended field list.

Field Labels

• The Field Name column displays the tenant-configured label where one has been set, rather than the default field name.
• ERP-specific naming is handled automatically. For example, Entity displays as Subsidiary for NetSuite tenants, and Freight/Shipping displays as Freight Amount where the tenant has configured it accordingly.

Ordering Persistence

• Once field ordering is established for a tenant, fields appear at the same position across sessions and logins.
• New standard fields added in future releases are appended to the bottom of the relevant standard group, preserving the position of existing fields.

AR Collections: Open AR with Customer Hierarchies

This release improves the accuracy of the Open AR view within the Data Navigator to better support complex customer structures. Open AR is the total outstanding balance a customer owes. In customer hierarchy scenarios, the Open AR view previously showed zero for parent customers instead of the combined balance of their child customers. The calculation now reflects parent and child relationships accurately in both the Data Navigator and the Open AR view.

What's New

• Parent customer view: When viewing a parent customer, Open AR automatically includes the balances of all associated child customers.
• Child customer view: When viewing a specific child customer, Open AR shows only that child customer's balance.

SmartResearch: Metrics Studio — Create and Edit KPIs and Metrics Using Natural Language

This release introduces Metrics Studio, which lets users define and manage business performance metrics using natural language rather than code or formula syntax. Metrics Studio includes standard AP metric definitions such as Days Payable Outstanding (DPO), Payment Accuracy Rate, and AP Aging. Users can use these definitions as provided or as a starting point for custom metrics.

Creating Metrics with Natural Language

• Natural language definition: Users describe the calculation in plain language, for example "average time from invoice receipt to first approval," and the system converts the description into executable calculation logic.
• Data availability check: The system identifies the data fields required for the calculation and checks their availability in the SmartResearch instance. If required fields are missing, the system suggests available alternatives or data sources.
• Review before saving: The system displays the generated formula for review before the metric is saved to the Metrics Studio catalog. A metric name is required.

Editing Metrics

• Conversational editing: From a metric's edit screen, users describe the change in plain language, for example, "use net 30 terms instead of invoice date for DPO." The proposed formula appears at the top of the edit screen. Users can select Apply to replace the live formula or discard the proposal.
• Immediate availability: After a new or edited metric is saved, it is available immediately for SmartResearch conversational queries. No separate publish step is required, and edits propagate immediately.

Validation Status

• Validation badge: Each metric, standard, or custom displays a Validated or Not-Validated badge. No confidence score is shown.
• Default state: System and default formulas are Not-Validated until a team member signs off.
• Status reset on change: Any formula edit resets the status to Not-Validated.
• Availability is not gated by validation: A metric is usable in SmartResearch conversational queries regardless of its validation status. The badge records whether the formula has been reviewed; it does not restrict access.
• Last Updated timestamp: A Last Updated timestamp records when the metric was last modified.

SmartResearch: Oracle Fusion Accounts Payable Data Source

This release adds Oracle Fusion Accounts Payable (AP) as a supported SmartResearch data source. Tenants running Oracle Fusion can ask natural language questions against their AP data, comparable to the existing Workday AP experience. Oracle Fusion works alongside existing sources, so multi-source queries are supported.

Supported Question Areas

• Invoice management: Invoices pending approval and their age, invoices on hold and hold reasons, invoices due within a given period, total open AP liability, and duplicate invoice detection.
• Payments and cash flow: Payments issued in a period, vendors with overdue invoices, available early payment discount savings, projected cash outflow, and payments by method.
• Vendor spend analysis: Top vendors by spend, spend trend for a given vendor, vendors with the most open invoices, and spend by category or cost center.
• Exceptions and compliance: Three-way match failures, invoices processed without a purchase order, invoices paid after payment terms, and manually overridden invoices.
• AP operations: Average invoice processing cycle time, invoices received compared with invoices processed, and AP aging summary by period.

Connection Setup

An Oracle Fusion AP instance is connected through the Auditoria Connection setup flow. The connection synchronizes invoice, payment, supplier, and hold data, and is recorded in system logs. The setup flow validates the connection and returns error messaging for authentication failures.

2. Fixed Bugs

No fixed bugs were reported in this release.

3. New Known Bugs