1. New and Updated Features
Collections SmartFlow: Support for Multi-Currency Invoices [3597]
In the Collections SmartFlow, multi-currency invoices are supported for customer invoice generation. You can view customer invoice amounts in multiple currencies and generate invoices in your selected currency.
ERP Integrations: Support for Multiple Entities [3598]
When integrating with ERP systems such as Oracle NetSuite or Sage Intacct, you can list all the entities to be included for automation in Auditoria SmartFlows.
Collections SmartFlow: Customer invoice amount disputes can be managed and resolved. [3840]
In the Collections SmartFlow, when a customer disputes an invoice amount a new process raises a Prioritized Worklist card including the customer details, labels the message as In Dispute, replies with an acknowledgement email, and captures notes on the dispute to make resolution easier.
Collections SmartFlow: Dismiss granular elements of Prioritized Worklist cards [3247]
In the Collections SmartFlow, you can dismiss granular elements in the Prioritized Worklist cards at the element level, rather than dismissing a whole list.
Vendor Onboarding SmartFlow: Bot to seek vendor confirmation when invoice and W-9 addresses do not match [4383]
In the Vendor Onboarding SmartFlow, bots will automatically seek vendor confirmation when invoice and W-9 addresses do not match.
Vendor Onboarding SmartFlow: Vendor record created in the ERP as soon as approval is received [4114]
In the Vendor Onboarding SmartFlow, a vendor record is automatically created based on information extracted from the invoice upon Approval receipt. Vendor records can also be updated later based on the W-9 information.
2. Fixed Bugs
Resolved: Vendor Onboarding SmartFlow: Incorrect acknowledgement email from bot stating address validation. [4739]
Resolved: Vendor Onboarding SmartFlow: Unknown vendor email with invoice attachment not resolved. [4696]
Resolved: SmartFlow Management: Dashboard console and been updated with new terms. [3945]
Resolved: SmartFlow Management: Customer Invoice PDFs appear in the Collector page. [4170]
Resolved: Vendor Onboarding SmartFlow: Address confirmation email thread not displayed. [4776]
Resolved: Collections SmartFlow: DSO flag not available in Top Metrics. [4772]
Resolved: Vendor Onboarding SmartFlow: Bot must verify invoice for customer before onboarding vendor. [4112]
Resolved: Vendor Onboarding SmartFlow: Text wrapping of long business names fails. [4663]
Resolved: Collections SmartFlow: Customer reply notes not generating for invoice request. [4673]
Resolved: Integrations: No confirmation message when saving list of customer email addresses. [4679]
3. New Known Bugs
NetSuite Integration: ERP setup steps required to run SmartFlow skills. [3702]
Symptom: When integrating Auditoria with Oracle NetSuite, several key setup steps are required to run all of the Auditoria SmartFlow skills.
Impact: Customer can not run all SmartFlows without key setup steps in Oracle NetSuite.
Workaround: None.
SmartFlow Management: Pop-up window with actions in edits at SmartFlow Management > Autonomous Order to Cash > Collections difficult to view and use. [4571]
Symptom: The Collections pop-up window is difficult to read and perform the actions available. Extra scrolling is required to see important details and make edits.
Impact: Customer has difficulty reading and using the Collections pop-up window.
Workaround: None.
SmartFlow Management: Duplicate emails being sent by email scheduler. [4750]
Symptom: Auditoria email scheduler sending out duplicate email records.
Impact: Customer receives duplicate emails.
Workaround: None.
Invoice Accrual SmartFlow: Bot not sending a response to correct irrelevant replies. [4680]
Symptom: During the Invoice Accrual SmartFlow, bots aren't sending follow-up replies and stating amount information when prompted to make a correction by email.
Impact: Customer not getting correct bot responses and amounts.
Workaround: None.
Integrations: Hippo bill-to email address mistaken for a vendor/sender's email address. [4695]
Symptom: In Hippo UAT, the bill-to field has an email address that is wrongly shown as the vendor's email address.
Impact: Customer views incorrect email address.
Workaround: None.