Exception Handling
When Expense Invoice Processing automation fails due to an error, RPA sets the Expense invoice status based on the error type. The failed Expense invoice record is moved to Data Lake and is displayed on these tabs of the Review Center screen in the RPA Management application:
- Missing Information: This tab displays Expense invoices with the MISSINGINFORMATION status. A Expense invoice is set to this status when the automation process is unable to extract any of the mandatory fields from the Expense invoice, such as Invoice Number, Invoice Date, or Sub Total.
-
Needs Verification: This tab displays Expense invoices with the NEEDSVERIFICATION status. A Expense invoice is set to this status if one of these conditions is met:
- Invoice type cannot be determined
- User verification is required
- Invoice is already registered
- Vendor not found
- Invoice number exceeds 15 characters
- There are no vendor details on the invoice
-
Failure: This tab displays Expense invoices with the FAILURE status. A Expense invoice is set to this status if one of these conditions is met:
- Scanned invoice status is Entered, Updated, or Closed
- EDI mismatch
- Session time out
- Scanned document is not an Expense invoice.
Note:
- If these records are corrected by the user, RPA reprocesses the Expense invoices in the next workflow run.
- Users can switch between the automations on this screen to view the related exceptions.