Executive Summary

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

AP Invoices: Freight in SmartVendor Templates

This release adds Freight support to SmartVendor Templates for AP Invoices, enabling new customers and those migrated from SmartFlow configuration to use the freight business process without extra setup.

What’s new

• Freight Amount field available in templates

  • A Freight Amount option is now available on the SmartVendor Templates page for AP Invoices.

  • SmartVendor Templates matches the configuration options of SmartFlow Configuration, allowing you to define how freight is handled for invoices through three options based on your organisation’s business process:

    • Do not write freight to SoR

    • Write freight at header level

    • Write freight at invoice line level

  • Decimal precision for Freight is consistently enforced across Templates, document details, audit logs, and audit history.

• Available only for migrated customers

  • The Freight Amount option in SmartVendor Templates is visible only for new customers and existing customers who have the Freight field enabled and migrated from SmartFlow Configuration to SmartVendor Templates.

  • Existing customers using SmartFlow Configuration with the Freight field enabled can continue their current workflow.

Both SmartVendor Templates and the Freight field have limited availability. For details, contact your Customer Success Manager or our support team (support@auditoria.ai).

AR Remittances: AR Remittance Mapper (Personalized Remittance Mapping with Preview)

The AR Remittance Mapper enables Accounts Receivable (AR) Managers to upload customer remittance files and configure personalized field mappings. This feature streamlines onboarding by automatically extracting and matching remittance fields, reducing manual setup, and improving mapping accuracy.

What's New

• AR Mapping Tab in Customers:

  • Available under the Customers section, next to Customer Emails and Invoices.

  • Provides access to configure and manage remittance mapping for each customer.

• Automated Field Mapping:

  • Upload Excel (.xlsx, .xls) remittance files up to 5 MB for new customers.

  • The system automatically detects and extracts column headers from the uploaded file.

  • Displays matched fields between the System of Record (SOR) and Auditoria.

  • Fields can be manually adjusted using dropdown selectors.

• Preview Mode for Configuration Validation:

  • Displays a side-by-side mapping of SOR fields and Auditoria fields.

  • Shows a preview of the first 3–5 mapped values in each field.

  • Preview results are grouped by Header and Payment Lines.

• Reusable Mapping Configurations:

  • Save named mapping configurations for each customer.

  • Reuse or edit existing mappings as customer remittance formats change.

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

AR Helpdesk: Multi‑Customer Replies for Invoice Copies and Account Statements

The AR Helpdesk now supports processing email requests from contacts who are linked to multiple customer records. This allows SmartBot to send consolidated replies for invoice copy and account statement requests, clearly indicating which documents belong to which customer.

What's New

• Multi-customer Email Handling: When a sender’s email address is associated with more than one customer record, SmartBot can process invoice copy and account statement requests across all records.
• Consolidated Replies: Replies contain tables listing documents by customer, with clear download links and customer names.
• Sender-based Greeting: SmartBot uses the contact’s name in the reply greeting instead of a single business name.
• Configurable Setting:
  • Setting name: Processing for Multi-Customer Record Matched Emails
  • Location: SmartCustomer AR Helpdesk settings (SmartFlow configuration)
  • Default: Off. Enable this to activate multi-customer processing.
• Dedicated Reply Templates: SmartBot uses specific templates to address multi-customer matches for:
  • Invoice copy requests (all found, some found, or summary)
  • Account statement requests (statements found, none found)
• Detailed Table Format:
  • For invoice copies: | Customer Name | Invoice Number | Download Link |
  • For account statements: | Customer Name | Download Link |
• Task Details and Record Selection Improvements:
  • Shows the number of matched records before selection (e.g., 24 Records)
  • Displays number selected versus total matched (e.g., 12 of 24 Records)
  • Reveals selected record name/ID/status with tooltips if only one record is chosen
  • "Select All" and "Select None" options are added to the record selector
  • After reprocessing, selected records appear at the top of the list
  • Task rows display [Multiple] when no selection is made, and comma-separated customer names after selection
  • Record selection can be changed and reprocessed repeatedly

How It Works

• Enable multi-customer processing in AR Helpdesk settings.
• When a sender is matched to multiple customer records, SmartBot applies multi-customer reply templates.
• Users can select one or more records for processing and adjust their selection at any time.
• Replies generated to the sender show tables that map documents to each matched customer.

Note:

• Multi-customer processing is off by default. Enable it to use these features.
• Invoice and statement download tables can support at least 100 rows.
• Invoices generated within the last 24 hours may not appear in the tables.
• Account statements are provided only for accounts with open invoices.

AP/AR Helpdesk/Connector: Support for High-Importance Emails (O365)

This release introduces the ability to mark emails as "High Importance" in SmartCustomer’s in-console email experience. This supports urgent communication scenarios, ensuring recipients are clearly notified of email priority, especially in Outlook (O365) Mailboxes.

What's New

• Mark as High Importance on Outbound Emails

  • A red exclamation mark (!) icon is now available in the email compose toolbar, adjacent to the link icon.

  • Click the icon to toggle high importance. The active state shows a filled red icon; the inactive state shows an outlined icon.

  • Applies to all compose actions, including Reply, Forward, Edit & Compose, and emails accessed from Task Details.

  • When enabled, a red "!" icon appears at the end of the subject line in the compose view, preview, and sent email view.

• High Importance on Incoming Emails

  • For inbound emails marked as high importance (via supported O365 headers), a red "!" icon is displayed:

    • In the email list, between the sender name and the subject.

    • In the email detail view, beside the "Mark as Read" button, there is a "High Importance" label.

    • Beside the task number in the Tasks list.

  • On hover, icons display: "Marked as High Importance".

• Dunning Configuration

  • A new “Mark as High Importance” checkbox is available in dunning notification settings.

    • Default state: Unchecked (feature opt-in per dunning stage and notification type).

    • When enabled, all emails sent for that dunning rule are automatically marked as high importance.

  • This configuration can be applied at the dunning notification level, allowing you to specify high importance for individual notification types within each dunning stage.

• Compatibility

  • High-importance headers and icons will display in Outlook desktop, Outlook web app (OWA), and Outlook mobile apps.

  • Gmail does not display the high-importance indicator; it is only reliably supported in Outlook clients.

Notes

• High importance setting applies to individual emails only, not the full conversation thread.

• Replying to a high-importance email does not automatically mark the reply as high importance.

• Not applicable in Autonomous Mode.

• Visual and header-based high-importance tagging is not supported in Gmail.

AR/AP Helpdesk: Language Detection, Translation, and Language-matched SmartBot Replies

This release introduces integrated language detection and translation in AR (Accounts Receivable) and AP (Accounts Payable) Helpdesk. Users can now review, translate, and respond to emails in multiple languages within the Helpdesk interface. SmartBot drafts replies in the original email’s detected language that are consistent with the reply language.

What's New

• Automatic Language Detection:
  • All inbound emails are automatically scanned for language.
  • The detected language is stored with the message and shown in the user interface.
  • Users can manually correct the detected language if required.
• Translation of Email Content:
  • Users can translate email messages into their preferred language on demand.
  • Both the original and translated versions are viewable, with a clear visual distinction and toggle.
  • User preferences allow you to set a default translation target language and enable automatic translation for assigned task related emails.
• SmartBot Replies in Sender’s Language:
  • SmartBot drafts replies in the detected language of the inbound email, enabling responses in the customer or vendor’s language.
  • If the detected language is changed, users can regenerate the SmartBot draft in the updated language.
  • Users can also translate SmartBot drafts into their preferred language for review and editing.
  • Both the reply (in the detected language) and the translation are available in the interface.
• Supported Languages:
  • Language detection and translation are available for 48 languages, including English, Chinese, Japanese, German, French, Spanish, Arabic, Portuguese, Hindi, Russian, Korean, Italian, Dutch, Turkish, Swedish, and others.

Note:

• Attachments received from outside parties (inbound attachments) are not translated in this release.
• Proper nouns (such as personal and company names) and identifiers (such as invoice numbers and reference IDs) are not translated.
• When a message contains multiple languages, AP/AR Helpdesk selects the primary or majority language. Users may manually select a different language if needed.

No manual copying to external translation tools is required, and users can handle multilingual queues from within a single Helpdesk interface.

2. Fixed Bugs

None.

3. New Known Bugs