Professional Documents
Culture Documents
Oracle Integrated Invoice Imaging Issues: March 2 0 1 8
Oracle Integrated Invoice Imaging Issues: March 2 0 1 8
MARCH 2 0 1 8
Oracle Integrated Invoice Imaging Solution Overview
Paper invoices are still prevalent in today’s business world, prompting most organizations to implement some form of imaging
capability for their Payables department, to help reduce the receipt-to-payment cycle and meet audit requirements. This
involves implementing multiple point solutions with the following challenges:
Components from different vendors specializing in scanning, data extraction, storage and workflow, based on proprietary
technology, require dedicated IT staff to set up, integrate, and maintain, resulting in higher implementation and maintenance
costs.
Disparate platforms, operating systems, and release or certification cycles increase the risk of incompatibility and maintenance
overhead. When the ERP system is patched, re-implementation of some or all components may even be required.
Given this a la carte selection process, the result is a disjointed, bolt-on solution footprint that is truly unique to each
implementation and cannot leverage native ERP capabilities and efficiencies. Such implementations often rely on either
custom user interfaces and direct import of raw data via open interfaces or both. Therefore completely bypassing native ERP
transaction entry and validation.
Oracle is the only vendor in the market today offering a fully integrated invoice imaging solution that provides a seamless
user experience, supporting the entire invoice lifecycle from scanning, recognition, and routing, to invoice entry, approval,
and payment – all based on a unified security model. This end-to-end solution is certified and supported by Oracle on a
common provisioning framework, with minimal setup and configuration required, thereby reducing the total cost of
ownership.
Getting Started
Set up the Payables imaging solution using the following 3 steps.
Step 1 Confirm the designated e-mail accounts
Verify you have e-mail accounts, one for each pod within 20 days of signing up for the Automated Invoice Processing service.
Set up the scanners to produce TIFF images with International Telegraph and Telephone Consultative Committee (CCIT) Group
IV compression at 300 dpi.
Invoices in a printed physical format must be scanned and then sent by e-mail. Invoices in a digital format can be sent directly
by e-mail.
Confirm the printed and digital invoices were sent and received to complete your imaging solution.
Its recommended not to enter BU while running Its recommended to leave BU blank Customer
import process while running import process
Mark Suppliers as Internal or Intercompany to avoid Define appropriate set ups Customer
incorrect supplier Recognition.
When Scanning Multiple Invoices in 1 PDF please Customer to Use a Blank Clean Customer
make sure to use a clean blank paper in between Sheet of Paper for a page
each invoice such that blank page separator is less Separator when Scanning multiple
than 3 KB. Invoices into 1 PDF
Make sure that PO information has been created Customer to confirm and create PO Customer
before sending images for PO Matched invoices in Environment prior to Testing to
avoid incomplete invoice
Know how to make setup roles for users to view Doc ID Customer
Images on the Invoice UI 2366622.1
FAQs
Provisioning FAQ's:
1. How do I get the cloud e-mail account where I need to send the scanned invoices?
The e-mail account is in the welcome kit mail that was sent when the imaging environment was provisioned. If you do not find
the welcome e-mail, log a Service Request for the invoice e-mail address.
2. How do I find an invoice sent to a designated e-mail account but can’t be found under the Scanned infotile?
Recommendation:
5. How do I reconcile between the invoice images e-mailed to the designated imaging e-mail address and the invoices
created in the payables system?
NOTE: Refer to note 2210741.1 and install the imaging auditability report.
Recognition FAQ's
11. Can I use other document types such as pdf and jpg? Yes, the following image formats are supported: .TIF; .TIFF; .PNG;
.JPG; .DOC; .DOCX; and .PDF.
12. Why are we using e-mail to get the image to the imaging solution? Can we use a scanner or fax?
Cloud customers are given an e-mail address which they send their invoices to be processed. An on premise customer would
have more options such as direct scanning or fax.
13. What are best practices to be followed for high image recognition rate?
• Image file with multiple 1 page invoices should be separated by blank page separator of size 3KB or less.
• Image Quality : o Set up the scanners to produce TIFF images with International Telegraph and Telephone Consultative
Committee (CCIT) Group IV compression at 300 dpi.
o Avoid hand written content and stamp marks as it impacts recognition rate. o Invoice Image should have
supplier address on it. Lines section should have proper column headings o Supplier address defined in Fusion
Supplier module should exactly match with the address printed on the invoice. o Non invoices such as cab
receipts do not get recognized.
• If you are not using PO matched invoices, log a service request to disable PO recognition for imaging. If you are using PO matched
invoices then log a service request to update the image configuration with the PO formats used in the Purchasing module.
• Employees should not be created as suppliers in Fusion Applications. If the employees are already created in Fusion Application
either they need to be deactivated or log an SR to exclude certain supplier types. This exclusion will work only if all employees
are assigned same supplier type.
Sample invoice where attributes are not recognized as invoice line data is unorganized.
15. What should be done for an intercompany supplier whose address appears as a bill-to address on the invoice
image? Generally Payables invoices have 2 addresses where one is the physical location of the supplier and the other is the
address of the bill-to party. Some customers configure suppliers with a bill-to address, for suppliers created for intercompany
transaction purposes. It is recommended that the address of the intercompany supplier is set differently from the bill-to address
as the intercompany supplier address is generally not used for any specific purpose. The regular supplier address is used for
sending checks and other reports whereas intercompany suppliers are not used for such purposes. Having a different address
for an intercompany address does not impact any business flow.
17. Why isn’t new supplier information recognized after adding them?
To be recognized, any new supplier must be created in the application at least a day before the invoice is to be created. Also the
pay site flag should be enabled on at least one supplier site.
For suppliers that typically have purchase orders created, the supplier is added prior to the invoice being created. In the
case of unmatched invoices, you must create the suppliers at least a day in advance. This ensures you are able to scan
and create the invoices automatically with the supplier information being recognized.
If you need to scan the invoice image immediately after creating a supplier, you can create a service request for
manual supplier synchronization after the supplier is created. Once the supplier synchronization is complete, the
supplier information is recognized when you scan and create the invoice.
If the supplier still cannot be recognized after supplier synchronization, check the supplier site address setup.
NOTE: The application recognizes the supplier by comparing the supplier site address with any addresses shown on
the invoice images.
19. Why are lines not getting recognized for unmatched invoices?
There is a likelihood that some number on the invoice image is being recognized as the PO number. Check for any kind of colored
border on the identifying PO field in the invoice UI. If yes, then it means that some number on the invoice image is getting
recognized as PO number. For such an issue, log a service request(be consistent in using either service request or service
request in the document.) to update the configuration of PO numbering in imaging setup.
20. What are the best practices recommended for me if I am not using Oracle Fusion Procurement?
You must log a service request to update the configuration setting of PO numbering in imaging setup to ensure that none of the
fields on the invoice image get recognized as PO numbers. Additionally, check your business process to determine whether the
business unit information is provided by the user when sending the invoice image or they want it to be defaulted from the users
default org profile option. Depending on the decision, make the required setups.
21. Why do I see the Identifying PO field highlighted in orange on the Invoice page when an unmatched invoice is
sent?
The application is set up to recognize a purchase order on every invoice. The recognition is based on the configuration
defined for the purchase order in the configuration file of the imaging server. If any formats matching the defined
22. Why aren’t the invoice lines matching to the purchase orders for invoices that include multiple purchase order
numbers?
Make sure each line of the invoice references it’s respective purchase order so that the relevant PO number is reflected on each
invoice line. If the invoice line does not have a PO number, it will not be matched.
Log a service request to ask support to enable multiple PO recognition.
Other FAQ's
23. How do I scan and send utility bills?
Utility bills are generally posted to a single account with a single invoice line. However the utility invoices run into several pages
as they have detailed itemization. The recommendation for utility bills is to use the manual approach to create the invoice and
add the scanned image using the attachments functionality. This is because reading the detailed itemized lines does not serve
any purpose and the recommendation is to create the invoices manually.
25. Is there are way to review all my scanned invoices in the scanned queue?
There is a profile option on incomplete invoices. When this option is turned on then all the images appear as incomplete status
and appear in the scanned queue where user can review each invoice and then mark them as complete.
26. Why is the tax information missing from the invoice page when the paper invoice has a tax amount? Tax information
isn’t recognized from the invoice image. It’s calculated automatically by a robust tax engine with predefined tax rules. If the tax is
missing from the invoice page, check your tax rules setup.
27. Does it matter what I enter as the e-mail subject when sending invoice?
In general it doesn’t matter what you enter as the e-mail subject except you must not include the underscore (_) in the
subject because the application treats that symbol as your intent to populate routing attributes on the invoice.
For details on routing attributes, see Advanced Topics: Attributes Recognized by Invoice Image - Routing Attributes 1 to 4.
28. What if I want to route incomplete invoices based on attributes not specified in the invoice?
The application provides 4 additional routing attributes that you can use to define routing rules according to your business
requirements.
For details on routing attributes, see Advanced Topics: Attributes Recognized by Invoice Image - Routing Attributes 1 to 4.
29. Why do I see a TIFF format attachment in the application when I sent it as a PDF invoice?
The application supports invoices with the following file extensions: *.tif, *.tiff, *.png, *.jpg, *.doc, *.docx, and *.pdf. However
to produce the best recognition results, the application converts the other document types into the TIFF format.
30. Why do I see a black and white invoice images in the application when I sent a color image invoice?
The application converts the color image invoice into a black and white one. The black and white image provides optimal optical
character recognition accuracy and a reduced image size.
31. Why do I see scanned invoices that aren’t supposed to be routed to me based on the defined routing rules?
The defined routing rules are used to route incomplete invoices, which are invoices created from an invoice image that
have invalid or missing data to users for review and completion. These invoices can be seen only by the user to whom the
invoices are assigned. However the invoices with a status of Not validated or Needs revalidation appears in the Scanned
infotile for all users based on their business unit security.
Users with Accounts Payable Supervisor and Accounts Payable Manager job role can see all the scanned invoices. They
are categorized into the following aging buckets: 0-7 days, 8-14 days, and 15+ days.
32. Why can’t I delete invoice lines from some of the scanned invoices?
If the invoice has a status of Incomplete, you can delete the line by selecting it and clicking Delete. If the invoice has a
status of Not validated, you cannot delete an invoice line by default because tax is calculated. You can follow the
instructions to disable tax calculation during import process or you can cancel the line.
33. Can I update or delete invoices in the Webcenter Image Process Management (IPM)?
It is recommended that user access IPM only during the active testing phase for troubleshooting purposes. At all other times,
they should access the image invoices in the application only. Also, updating or deleting invoices in IPM has no effect on
those image invoices in the Payables application.
Advanced Topics
How to Schedule the Import Payables Invoices Process
1. Sign in to the application and navigate to the Invoices work area.
2. Click the tasks icon to open the panel drawer.
4. Enter the Ledger and Business Unit (optional), and select Invoice Image as the Source.
5. Click Advanced.
6. Select the Schedule tab and enter the frequency. The recommended frequency is 1 hour. 7. Click Submit to complete the
scheduling.
Note:
The application requires an end date so make sure it is far enough out.
In the Test phase, to import the invoices immediately for testing, you can submit the process immediately
by selecting: As soon as possible.
3. Click on the Name link to open the Manage Administrator Profile Values page.
4. In the Profile Option Code field, enter DEFAULT_ORG_ID (case sensitive) and click Search.
5. In the Search Results: Profile Options section, click the DEFAULT_ORG_ID row.
6. In the DEFAULT_ORG_ID: Profile Values section, click the New button to add a row.
7. Select the Profile Level of User, enter the User Name that will process the invoices, and select the default business unit in the
Profile Value field.
8. Repeat steps 6 and 7 to set up a default business unit for all of the users that process invoices.
9. Click Save and Close when you have completed the setup for all users.
Follow these steps to enable and use business unit defaulting from the routing attribute:
1. Sign in to the application and navigate to the Setup and Maintenance landing page.
8. If you don’t know the business unit ID, you can find the ID using the Manage Business Unit task under Financials Setup.
4. Check the Enabled and Updateable checkbox at Site level, click Save and Close.
8. In the AP_IMAGING_DISABLE_TAX: Profile Values section, click the New button to add a row.
9. Select the Profile Level of Site, enter ‘Y’ in the Profile Value field.
List Builder Resource Determines the resource to which the invoice is routed.
Response Type Required Indicates that the routing notification requires a response.
Rule Name "JobRoleAssignmentRule" Identifies the approval reason to display in the approval history
diagram.
4. Click the Save icon in the Tasks to be configured pane to save the changes.
5. Click the Commit task icon in the Tasks to be configured pane to activate the changes.
Here’s an example of how to modify a rule set to route incomplete invoices to a specific user group, starting from the Task Configuration
page in the BPM Worklist:
1. Select the FinApIncompleteInvoiceHold task.
2. Click the Edit task icon to edit the rule.
3. Select the Assignees tab.
4. Click IncompleteInvoicePayablesUser.
5. Click on the business rule IncompleteInvoiceRuleSet.
11. Validate the rule to ensure that there are no errors in the rule definition.
12. Save and commit the task to ensure that the new rule is functional.
Level Attributes
Routing Attributes 1 to 4
The imaging solution can support up to four attributes in an e-mail subject, which can be recorded on the invoice or used
to route the incomplete invoices to accounts payable personnel for review and completion. Use the underscore (_) as a
separator to indicate the start of routing attribute information. Each attribute can contain up to 40 characters by default.
For example, if you have a specific business requirement to record categories on the invoice, such as invoice priority, supplier category,
manufacturing plant number, storage bin number, you can specify the categories in the e-mail subject.
This table lists the categories, their possible values, and how they are mapped to Routing Attributes 1 to 4.
A supplier sends an invoice with the e-mail subject: Invoice-1234 attached. The imaging specialist reviews the e-mail
and provides additional routing information in the e-mail subject. The revised e-mail subject is: Invoice-1234
attached_Urgent_Supply chain related_Plant-1_Bin#1.
Also please note that Routing Attribute 5 is reserved for image auditing purposes and will not be used for routing incomplete invoices.
You can also use routing attribute 1 to manually record the business unit if your supplier sites have multiple business unit assignments.
For details on defaulting business unit based on routing attribute 1, see Business Unit Defaulting.
CONNECT WITH US
blogs.oracle.com/oracle Copyright © 2016, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only, and the contents hereof are
subject to change without notice. This document is not warranted to be error-free, nor subject to any other
warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability
or facebook.com/oracle fitness for a particular purpose. We specifically disclaim any liability with respect to this document, and no contractual obligations are formed either directly or
indirectly by this document. This document may not be reproduced or transmitted in any form or by any
twitter.com/oracle means, electronic or mechanical, for any purpose, without our prior written permission.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective
owners.
oracle.com
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license
and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron
logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
0616