Exception Handling

When Trade Invoice Processing automation fails due to an error, RPA sets the trade invoice status based on the error type. The failed trade invoice record is moved to Data Lake and is displayed on these tabs of the Exception Handling screen in the RPA Management application:

• Missing Information: This tab displays trade invoices with the MISSINGINFORMATION status. A trade invoice is set to this status when the automation process is unable to extract any of the mandatory fields from the trade invoice, such as Invoice Number, PO Number, Invoice Date, or Sub Total.
• Needs Verification: This tab displays trade invoices with the NEEDSVERIFICATION status. A trade invoice is set to this status if one of these conditions is met:
  • The automation process is unable to determine the invoice type
  • Related POs are already costed
  • User verification is required for the invoice
  • The invoice is already registered
  • A PO API error occurs
  • The invoice number exceeds 15 characters
  • There is no PO on the invoice
• Failure: This tab displays trade invoices with the FAILURE status. A trade invoice is set to this status if one of these conditions is met:
  • The scanned invoice status is Costed or Closed
  • There is an EDI mismatch
  • The session has timed out
  • The scanned document is not a trade invoice.