Executive Summary

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

1. New and Updated Features

Platform: SmartBot terminology updated to Agent / AI Agent

This update replaces user-facing references to SmartBot with Agent or AI agent across the SmartVendor and SmartCustomer interfaces.

The change aligns the product with the updated naming and branding guidance in “Product naming and brand”, while keeping existing automation behavior and workflows unchanged.

Users will now see the new terminology in dashboards, task views, email settings, activity reports, and related configuration screens, but all underlying functionality continues to operate as before.

SmartCustomer / Universal ERP Connector: S3 invoice attachment retrieval for AI Agent Processing

This release enables SmartCustomer and the Universal Connector to retrieve invoice attachments from an existing AWS S3 bucket and display them in AI agent responses and the Invoice Detail screen.

For customers whose Enterprise Resource Planning (ERP) system already exports invoice attachments (for example, Portable Document Format (PDF) copies) into the S3 /attachments folder, AI Agent can now locate and return these files for “Request for Invoice Copy” intents.

What’s New

• S3 attachment indexing for invoice records
  • A new service scans the S3 /attachments folder.
  • It links files to invoice records by matching the invoice number in the file metadata or name to the invoice number in AAI.
• AI Agent attachment retrieval for invoice copy requests
  • When a user triggers a “Request for Invoice Copy” or similar “send me a copy” intent, AI Agent queries the indexed attachments.
  • If matching invoice attachments are found (e.g., invoice PDFs), the AI Agent attaches them to the email response.
• Graceful handling of missing attachments
  • If no matching attachment is found in S3, AI Agent returns a fallback message instead of failing the request.
  • This prevents user-facing errors when an invoice copy is requested but no attachment exists.

AP Invoices: Danish and Polish description translation for document processing

This release extends support for processing Danish and Polish invoices by enabling the translation of extracted invoice descriptions.

With this release, invoice line descriptions from incoming documents in Danish or Polish are now translated during extraction, using the same translation behavior as for other supported languages. This enhancement ensures consistent language handling for Danish and Polish in line with the existing description translation workflow.

AR Helpdesk: Customer Record Field-Based Agent Reply Mapping

This release introduces a configuration option in Accounts Receivable (AR) Helpdesk that allows AI Agent replies to be drafted from templates mapped to a specific Customer record field, including both standard and custom fields.

The change supports use cases such as sending localized messages and attachments based on a Customer’s company association or membership status. When emails from customer contacts match to an enrolled Customer record and qualify for AI Agent responses, AR Helpdesk can now select reply templates based on the configured Customer field value instead of using only global defaults.

By aligning AI Agent reply templates with Customer attributes, AR operations teams can manage differentiated communications per Customer segment while retaining a fallback to standard templates when no field-based mapping applies.

What’s New

• Customer Record Field-based AI Agent reply control
  • New checkbox in SmartFlow Skills Management >> Settings >> AR Helpdesk: Customer Record Field-Based Agent Reply Mapping.

• First-time setup: When the “Customer Record Field-Based Agent Reply Mapping” option is enabled, users will see a dropdown to select a Customer Record Field.
  • The Save button is disabled until a field is chosen.
  • When a field is selected, the Save button becomes active.
  • After clicking Save, the dropdown becomes read-only, and an Edit button appears.
• Subsequent edits: When you click Edit to change the previously saved field, the dropdown is enabled, and the Save and Cancel buttons appear.
  • The Save button is only active if you select a new field.
  • When changing to a new field and clicking Save, a confirmation pop-up will appear (see screenshot), warning: “Templates mapped to <customer.record.field> will be lost when a new mapping field is designated.”
  • The user must confirm the change by clicking Save or cancel the action.

• Field-mapped AI Agent reply templates management
  • In SmartFlow Skills Management >> Agent Replies:
    • A Default tab appears at the top-left of the template management user interface.
    • A button is available at the top of the page: Add Field-Mapped Templates.

• When Add Field-Mapped Templates is clicked, a modal appears:
  • Title: “Add Field-Mapped Templates”.
  • Customer Record Field: displays the configured <customer.record.field>.
  • Field Value dropdown:
    • Lists all synced values for the configured Customer record field.
  • Buttons: Save and Cancel.
    • Save disabled when no value is selected.
    • Save active when a value is selected.

• When field-mapped templates are added:
  • A new tab is created, labeled with the selected <field.value>.
  • Each field-value tab includes a kebab menu with:
    • Duplicate.
    • Delete.

• Duplicate field-mapped templates
  • When Duplicate is clicked from a field-value tab:
    • A “Duplicate Field-Mapped Templates” modal opens.
    • The modal shows:
      • Customer Record Field: <customer.record.field>.
      • Field Value dropdown with:
        • All synced values for that field.
      • Buttons: Save and Cancel.

• Delete field-mapped templates
  • When Delete is clicked from a field-value tab’s kebab menu:
    • A confirmation modal appears:
      • Title: “Delete Field-Mapped Templates”.
      • Message: “Template deletion cannot be reversed.”
      • Buttons: Delete and Cancel.

• Runtime template selection behavior
  • When Customer Record Field-Based AI Agent Reply Mapping is enabled, and the incoming email:
    • Matches a Customer record, and
    • Qualifies for AI Agent responses,
    • Then AI Agent replies are drafted using templates mapped to the Customer record field value.
  • When the mapped Customer field has no value, AI Agent replies are drafted using default templates.
  • When the mapped Customer field value doesn’t match any configured template values, AI Agent replies are drafted using default templates.
• Audit log entries for field-mapped templates
  • The Audit Log tracks adding and deleting field-mapped templates with dedicated actions:
    • “Field-Mapped Templates Added”
      • Summary format:
        • AR Helpdesk, Source:<SOR>, Mailbox: <mailbox.address>, <customer.record.field>: <field.mapped.value>
    • “Field-Mapped Templates Deleted”
      • Summary format:
        • AR Helpdesk, Source:<SOR>, Mailbox: <mailbox.address>, <customer.record.field>: <field.mapped.value>

AR Helpdesk: Autonomous Proof of Payment Transfer Setting

This release adds a new automation setting for handling Proof of Payment content in Accounts Receivable (AR) payment status update emails. The new configuration improves efficiency and control for AR operations teams when routing Proof of Payment messages and attachments.

What’s New  

A new setting, Autonomous Proof of Payment Transfer, is now available under SmartFlow Skill Settings:

• Configuration: The setting is enabled via a simple checkbox in the SmartFlow Skill Settings page.
• Behavior When Enabled:
  • Emails (and their attachments) identified as containing proof of payment in Payment Made or Payment Scheduled payment status updates are automatically forwarded to the configured forwarding address as soon as they are detected.
  • No user or manual intervention is required for these email transfers.
• Labeling Workflow:
  • Upon detection of proof of payment, the email is immediately tagged with the label ProofOfPayment.
  • Upon forwarding, it is additionally labeled as ProofOfPaymentForwarded.
• Forwarding Criteria:
  • Forwarding occurs only if the destination is not already in the email’s To or Cc fields.
  • Applies to emails from any sender (including unknown or system accounts).
• Task Creation and Tracking:
  • For emails from unknown or system senders, the system will still automatically create review tasks, ensuring every payment is traceable and subject to review, even if the forwarding is fully automated.

2. Fixed Bugs

None.

3. New Known Bugs