1. New and Updated Features
AR Helpdesk: Ability to Self-Assign/Claim and Re-Assign/Transfer Tasks
AR Helpdesk console supports user self-assignment or claiming and manually changing task assignees of tasks. This functionality adds compatibility with SOPs involving tracking of work per user, task handoffs, task escalations between users, and helps minimize risk of multiple users processing the same AR Helpdesk task.
Vendor Invoice Data Extraction: Ability to search on item name when selecting item
For customers using Vendor Invoice Data Extraction where the Master Item List is in scope, users can now search on the Master Item ID and the Master Item Name when matching Vendor Bill Lines to Master Items.
AP Helpdesk: SmartBot replies to requests lacking unique identifiers
Emails missing one or more unique identifiers (“slots”) needed to process business intent matched emails will invoke SmartBot replies informing senders additional information is needed to fulfill their requests or inquiries. Reply templates are fully customizable and aid in communicating and reinforcing best practices for suppliers and vendors engaging with AP Helpdesk connected mailboxes. The new reply feature supports the following AP Helpdesk business intents:
- Payment Status Requests (from internal senders)
- PO Status Requests (from internal senders)
- Remittance Advice Requests (from external and internal senders)
AR Helpdesk (Standalone version) and AP Helpdesk: Reply Template Editor w/ Support for Multiple Intents
AP Helpdesk and standalone AR Helpdesk now support self-service customization of SmartBot reply templates for all, reply enabled business intents. Accessed via SmartFlow skill setup wizard, users can navigate between intent-specific templates via an intent navigation dropdown. This enables users to customize messaging for all SmartBot sent replies to the specific needs of their businesses.
2. Fixed Bugs
None.
3. New Known Bugs
AP Helpdesk and Vendor Invoice Data Extraction: These two SmartFlow Skills cannot run concurrently on the same mailbox [12014]
Symptom: Emails and documents attached may not be processed correctly by SmartBots if AP Helpdesk SmartBots and Vendor Invoice Data Extraction SmartBots operate on the same mailbox.
Impact: The two SmartFlow Skills will operate incorrectly.
Workaround: Use separate mailboxes, one for Vendor Invoice Data Extraction, and another one for AP Helpdesk.
Vendor Invoice Data Extraction: "Downloaded" status is shown twice in the status dropdown on the dashboard (with Coupa) [12652]
Symptom: Downloaded option displaying twice in ‘Status’ column filter on Active Data tab of ‘Document’ screen of Vendor Invoice Data Extraction console.
Impact: No result available for one of the Downloaded status option.
Workaround: User will have to manually check which one of the Downloaded status option returns the result
Vendor Invoice Data Extraction: Issue with password required pop-up for password protected file [12607]
Symptom: Cancel button of “Password” Pop-up is not working for password-protected invoice that reached ‘Document’ tab in 'Vendor Invoice Data Extraction' console
Impact: 'Password' Pop-up wont dismiss until valid password is not provided
Workaround: Close the tab and relaunch Auditoria application
Vendor Invoice Data Extraction: Vendor Hints not considering Billing Address [12543]
Symptom: Vendor hints do not consider Billing address and hence when the same document is sent, it remains unmatched
Impact: Vendor name won’t be matched even though billing address hints are added for that vendor
Workaround: User will have to manually match the vendor name from ‘Document’ screen of VIDE console
Vendor Invoice Data Extraction: API account invalid error shown for bill default classification scenario when Write to SOR is triggered (with Coupa) [12461]
Symptom: Failure in ‘Write to SOR’ due to API Account invalid error for some of the accounts selected in Bill Default classification section.
Impact: Write To SOR fails with API Account invalid error
Workaround: Select any other Account value from the drop down and then try writing to SOR