1. New and Updated Features
Sage Intacct Integration: Multiple Email Addresses in Customer Record Supported [4984]
Multiple email addresses in the Customer Record email field used in Sage Intacct are now supported in the Auditoria Collections SmartFlow and can be used to send dunning notices and receive responses.
Accounts Payable Helpdesk SmartFlow is enabled [4139]
The Accounts Payable (AP) Helpdesk SmartFlow connects to your ERP and retrieves a list of all vendors who have sent a vendor payment inquiry. For more information about the AP Helpdesk SmartFlow, see Accounts Payable Helpdesk Process.
2. Fixed Bugs
Resolved: Customer categories added are displayed in the Autonomous Collector page. [5292]
Resolved: Collections SmartFlow: Default Classifications blank if regular category removed. [5291]
Resolved: Vendor Onboarding SmartFlow: Hippo bot misread Approver response as a rejection. [5281]
Resolved: Collections SmartFlow run and active but still appears in Start sequence. [5257]
Resolved: Collections SmartFlow: order of Key and Regular Accounts reversed so Key is first. [5151]
Resolved: Sage Intacct Integration: Kibana error getting AR Aging from Sage. [3889]
Resolved: Collections SmartFlow: Customer email has wrong label. [5404]
3. New Known Bugs
Vendor Invoice Data Extraction SmartFlow: Otto test emails Prioritized Worklists not appearing in Data Management page. [5146]
Symptom: Test emails are received by Otto during Vendor Invoice Data Extraction SmartFlow, but the Prioritized Worklists not appearing in the Data Management page.
Impact: Customer cannot view Prioritized Worklists.
Workaround: None.
Vendor Onboarding SmartFlow: Domain Name considered as Company Name if invoice is missing a name. [5412]
Symptom: During Vendor Onboarding, if a Company Name is missing from an invoice, the Domain Name of the email addresses is used instead.
Impact: Customer views an incorrect Company Name.
Workaround: None.
Collections SmartFlow: Customers receiving unexpected email labels. [5407]
Symptom: During the Collections SmartFlow, customers have received emails with unexpected labels.
Impact: Customers receiving unexpected email labels.
Workaround: None.
Vendor Onboarding SmartFlow: Different bot email address selected during a Smartflow not saved. [5397]
Symptom: During the Vendor Onboarding and Vendor Invoice Data Extraction SmartFlows, when a different bot email address is selected, the new address is not saved.
Impact: Customer cannot change a bot email address during a SmartFlow.
Workaround: None.
Collections SmartFlow: Email to bot email address has wrong label. [5362]
Symptom: During the Collections SmartFlow when an unsolicited email is sent to the bot email address, the email is mislabeled Email Needs Attention.
Impact: Unsolicited email to bot mislabeled.
Workaround: None.
Vendor Onboarding SmartFlow: Consero Vision Helpdesk test emails not detected by Vendor Onboarding bots. [5361]
Symptom: During the Vendor Onboarding SmartFlows, Consero Vision Helpdesk test emails not detected by Vendor Onboarding bots.
Impact: Vendor Onboarding process cannot be completed.
Workaround: None.
Auditoria Notification email does not include remediation. [5347]
Symptom: Customer email generated by Auditoria does not include the remedy to the issue acknowledged.
Impact: Customer does not receive remediation step in Auditoria email.
Workaround: None.
Collections SmartFlow: Consero received a Notification email citing an Invalid Argument but no issue is detected. [5346]
Symptom: During a Collections SmartFlow, using Sage Intacct as an ERP, Consero received an Auditoria email notification citing an Invalid Argument when no issue is detected.
Impact: Customer receives unexplained Notification.
Workaround: None.