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 Review Center 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:

  • Invoice type cannot be determined
  • Related Purchase Orders (PO) are already costed
  • User verification is required
  • Invoice is already registered
  • PO API error
  • Invoice number exceeds 15 characters

• Pending Process: This tab displays invoices with PONOTRECEIVED status. An invoice is set to this status when the automation detects that the purchase order status on the invoice is not Received.

  Note: 

  The invoices with the PONOTRECEIVED status are registered based on the receivedPOCheckEnabled field value. Possible values:

  • True: Registers invoices during every run, only when the associated PO is in the Received stage.
  • False: Registers invoices regardless of whether the associated PO is in the Received or Not Received stage.

• 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:

  • Scanned invoice status is Costed or Closed
  • EDI mismatch
  • Session time out
  • Scanned document is not a Trade invoice