Invoice Image Processing Architecture in Fusion Payables

Fusion Payables is tightly integrated with Oracle Document Capture (ODC), Oracle Imaging and Process Management (IPM), Oracle Content Management and Oracle BPEL process Manager to provide a seamlessly integrated solution supporting the entire payables cycle starting from scanning of physical invoices, invoice image recognizition using OCR to pre-populate invoice header, routing of the scanned invoices to AP entry specialists and subsequent approval and payment of invoices. Oracle is the only vendor in the market today offering a fully integrated solution without the use of third party bolt-on solutions.

Once the invoice arrives in a centralized mail room, the imaging specialist would sort and prepare the invoices based on parameters like invoice amount, due date, supplier, etc. and then scan these invoices using ODC. Next the images are automatically sent to Forms Recognition for intelligent recognition to extract key invoice header data like PO number, Supplier, Invoice Number, Invoice Amount and Invoice Date from scanned images using Optical Character Recognition (OCR) capabilities. Once the key header data recognition is completed, the invoice images are sent to Oracle Imaging and Process Management for storage and subsequent routing to accounts payable invoice entry specialists using Oracle BPEL Process Manager workflows. The BPEL process is generated whenever an invoice image is saved successfully in Imaging and Process Management, and this image is then routed to the AP invoice entry operator based on pre-configured rules like invoice amount, supplier, etc. The AP specialist views the scanned image and then fills up the remaining fields of the invoice to kick-off the subsequent process of invoice validation, approval, accounting and payment.

Reference Data Set

This is a new concept that has come in Fusion. Reference Data sets are logical groups which provides the enterprise to decide which business unit access the reference data groups, such as grades, locations, AR & AP payment terms, departments, and jobs. Oracle provides a default Reference Data set which can be used across all Business units. However, we can define our own Reference data sets, to partition the data from effectively.
E.g. in R12 we had to live with the entire list AR payment irrespective to the fact whether one OU was using it or not. however, in Fusion we can restrict payment terms across BU's, so only the relevant ones will be accessible to the BU.

Google map in Fusion Apps

Now we can locate all our employees, suppliers, customers addresses in Fusion through Google Maps.