PROCESSIT Exception Handling

Purpose

Get familiar with the exception workflows.

How to correct invoice validation discrepancies using the Modify Invoice window.

Correct invoice discrepancies found during standard Oracle validation using the Payables Interface Maintenance window.

Learning about handling holds in PROCESSIT.

Audience: End-users and workflow supervisors that require a more thorough look at the PROCESSIT workflows, features and functionality for handling discrepancies and exceptions.

Invoice Data Modification

  1. Open the modify invoice task
  2. Correct the appropriate value(s)
  3. Click Save data
  4. Select Action
  5. Click Submit

Invoice Rejection Workflow

Invoices can be rejected during accounting, matching or exception flows. The user rejecting an invoice must supply a comment.

A Superuser receives notifications for all rejections.

  1. Rejected invoice are handled in the Modify invoice window.
  2. Invoice data is corrected and the invoice flow is either retried or cancelled.
  3. When a Superuser finalizes the rejection of an invoice, a reject reason must be supplied for further clarification of the rejection.

Check out the workflow diagram.

Maintain Payables Scenarios

Invalid currency: The invoice currency code is invalid.

Invalid date: The invoice date is invalid.

Exploration: Enter Maintain payables and get familiar with the invoice header data and line data correction possibilities.

In each case, you must correct the data via Payables Interface Maintenance and follow the invoice flow.

Exception Configuration Options

Supplier Bank Account

You can configure PROCESSIT to check if the scanned supplier bank account number or IBAN matches the primary bank account number for the supplier site in Oracle E-Business Suite.

If a match is found, validation is passed and the workflow continues normally without placing a hold.

If the vendor site's bank account number or IBAN is different or does not exist, a bank account hold is placed on the invoice and a superuser is notified for issue resolution.

If no bank account is transferred, the invoice workflow follows the standard process.

User Defined Invoice Rejection Reasons

User Defined Rejection Codes and Reasons are applied at the final invoice rejection dialog box, and trigger sending information about rejected invoices to the supplier.

The rejection codes and reasons are defined in Configuration Manager.

The description text associated with the code is sent to the added supplier email as the reject reason.

Messages can be customized when selected.

THANK YOU!