1. Fixed Bugs
AP Invoices: Invoices Getting Classified as Others
Symptoms: AP invoices are getting classified as "Others." This was not the case during UAT.
Impact: Invoices are being misclassified, which could affect downstream processing and reporting in the production environment.
Workaround: Mapping for the affected vendor has been added. The issue is now resolved, and invoices are being classified correctly.
AR Helpdesk: Results Not Displayed in Task Details Section
Symptoms: Results are not displayed in the Task Details section for Invoice Request, Request for Documents, and Request for Account Statement.
Impact: This may cause confusion for users trying to identify which values SmartBot generated drafts for (if applicable) and which intents were processed, leading to ambiguity in task tracking and follow-up.
Workaround: No defined workaround is currently available.
AR Helpdesk: Unable to Send Email Drafts
Symptoms: The saved SmartBot reply draft for a follow-up task is not being sent. Users are unable to send the SmartBot reply draft after making edits, which prevents marking the task as Done.
Impact: Users cannot send or complete follow-up emails after making edits to SmartBot reply drafts, leading to delayed task completion and potential breakdown in communication workflows.
Workaround: Users can send the SmartBot reply draft without making any edits.
AR Remittances: Not All Payments Extracted in the document details page
Symptoms: Not all payment records were extracted in the document details page, and in some cases, the payment amount was incorrect. Duplicate records were seen initially, and some payment records were missing on extraction.
Impact: This caused incomplete or inaccurate remittance information, potentially leading to manual intervention and reconciliation.
Workaround: No workaround was available; users had to manually verify and create missing payment records as needed.
AR Remittances: Not All Payment Lines Extracted from Remittance Files
Symptoms: Not all payment lines are extracted from remittance files. In several cases, only a partial set of payments were detected (e.g., only one out of three expected payments), and payment information—such as amounts and line items—was incorrect or incomplete in the document details page.
Impact: Incomplete extraction of payment lines leads to missing or inaccurate payment information, which can result in manual intervention, reconciliation errors, and unreliable reporting for downstream processes.
Workaround: No workaround was available; users had to manually extract and verify payment details if information was missing or incorrect.