Automate Invoice Processing: Leverage OCI AI Text Extraction with Oracle Integration

Automate Invoice Processing: Leverage OCI AI Text Extraction with Oracle Integration

Table of Contents:

1. Introduction
2. Leveraging OCI AI Text Extraction Using Oracle Integration
   1. Use Case
   2. Integration Cloud as the Orchestrator
   3. Parsing Logic and Invoice Number Extraction
   4. File Renaming and Moving
   5. Error Handling and Manual Process
3. Prerequisites
   1. Building OCI Signature
   2. Enabling OIC File Server
   3. Testing in OCI Vision UI
4. Setting Up the Integration
   1. Configuring REST Adapter
   2. Integration Flow Overview
   3. Renaming Invoices with OCI Vision
   4. File Structure and Renaming Results
5. Conclusion

🔍 Introduction: In this article, we will explore the concept of leveraging OCI AI Text Extraction using Oracle Integration. We will delve into the use case, the integration cloud's role as an orchestrator, the parsing logic involved in extracting the invoice number, file renaming, and moving. Additionally, we will discuss error handling and the possibility of a manual process. Let's dive in!

🚀Automatic invoice processing streamlines the accounts payable process by using software to capture, validate, and approve invoices. It reduces manual errors, speeds up approvals, ensures compliance, and improves financial visibility, ultimately saving time and reducing administrative costs.  

🚀 Leveraging OCI AI Text Extraction Using Oracle Integration: The process revolves around analyzing distinct invoices in PDF format stored on an SFTP server. The aim is to extract the invoice number from each PDF file and rename it accordingly. Oracle Integration Cloud (OIC) plays a central role in orchestrating the entire flow.

📝 Use Case: The use case is relatively simple. We begin by fetching the list of invoices from the SFTP server. For each invoice, we make use of the Analyze Document REST API provided by the OCI Vision Service. This API call returns a JSON array list of lines and words present in the invoice PDF.

🔧 Integration Cloud as the Orchestrator: Integration Cloud's file server is utilized in this process. At the core of the integration flow, we initiate the retrieval of the list of invoices via Integration Cloud.

⚙️ Parsing Logic and Invoice Number Extraction: Using the JSON lines and words, a parsing logic is employed to search for the invoice number within the extracted data. Once the invoice number is identified, we proceed to rename the PDF file to the invoice number format (i.e., "invoicenumber.pdf"). The files are then moved to another folder on the SFTP server.

❗ Error Handling and Manual Process: Due to the raw nature of the parsing logic in step three, there is a possibility of issues and potential failures. In such cases, it is advisable to incorporate an additional process within Integration Cloud to kick off a human task for manual intervention. This would entail notifying the concerned individual to check the problematic PDF and manually rename the file accordingly. However, for the purpose of this demo, we will solely focus on the Integration Cloud piece.

📋 Prerequisites:

1. Building OCI Signature: Before connecting to the OCI Vision Service via the REST adapter, it is necessary to build the OCI signature. Numerous videos and resources are available online that explain the process in detail.

2. Enabling OIC File Server: By default, the file server within OCI is not enabled. Consequently, it is crucial to navigate to the OCI console and enable the feature. Additionally, users, files, and folder structures need to be set up accordingly.

3. Testing in OCI Vision UI: To gain a better understanding of the raw logic involved in the parsing process, upload invoices to the OCI Vision UI. Here, you can examine the request and response payloads, as well as explore the words and lines extracted from the invoices.

🔧 Setting Up the Integration:

1. Configuring REST Adapter: To connect to the OCI Vision Service, configure the REST adapter within Integration Cloud. The necessary URL can be obtained from the REST API documentation. Furthermore, refer to the OCI console for details on creating the fingerprint.

2. Integration Flow Overview: The integration flow we will be working with is titled "Rename Invoices with OCI Vision." It is a scheduled integration that retrieves files from the SFTP server and iterates through each file using a loop.

3. Renaming Invoices with OCI Vision: For every file, the Analyze Document API is called, passing the file data as an input. This API call returns a list of lines and words extracted from the invoice. In our example, we iterate over the lines to locate the invoice number. Upon finding the invoice number, we rename the file accordingly.

4. File Structure and Renaming Results: Before running the integration, it is important to review the files within the designated folder on the OIC file server. Once the integration is executed, the files will be moved to the processed folder with their corresponding invoice numbers.

🔚 Conclusion: In conclusion, leveraging OCI AI Text Extraction using Oracle Integration provides a versatile solution for extracting invoice numbers from PDF files. By utilizing the power of Integration Cloud and the OCI Vision Service, organizations can automate the invoice processing workflow effectively. Error handling mechanisms can be implemented to cater to potential failures and notify stakeholders for manual intervention. By following the prerequisites and setting up the integration flow, organizations can streamline their invoice management processes and enhance operational efficiency.

🌐 Resources:

• OCI Vision UI: [link]
• OCI Console: [link]

Highlights:

• Leveraging OCI AI Text Extraction using Oracle Integration
• Integration Cloud as the orchestrator
• Parsing logic and invoice number extraction
• Error handling and manual process notification
• Streamlining invoice management processes

FAQ: Q: What is OCI AI Text Extraction? A: OCI AI Text Extraction is a service provided by Oracle Cloud Infrastructure that enables the extraction of text data from various sources, such as invoices, documents, and images.

Q: How does Oracle Integration Cloud (OIC) fit into the process? A: Oracle Integration Cloud acts as the orchestrator in the workflow, connecting with the OCI Vision Service and coordinating the parsing logic and file renaming operations.

Q: Can the integration be customized to handle additional processes or notifications? A: Absolutely! The integration can be extended to include various functionalities, such as error handling mechanisms and notifications for manual intervention in case of failures.

Q: What are the prerequisites for implementing this solution? A: Prerequisites include building the OCI signature, enabling the OIC file server, and familiarizing oneself with the OCI Vision UI for testing purposes.

Q: How does this solution contribute to operational efficiency? A: By automating the extraction of invoice numbers and file renaming process, organizations can streamline their invoice management workflows, saving time and reducing manual errors.

Q: Can this solution be integrated with existing systems? A: Yes, the solution can be integrated with existing systems by leveraging the capabilities of Oracle Integration Cloud, which supports seamless integration with various applications and platforms.