Setting Up Invoice Approval
Setting Up Invoice Approval
2. Navigator > Workforce Management > Person Management > Manage Employment
• Invoice Amounts > $1K but less than $5K should be routed to Matthew Schnieder or the invoice
creator’s supervisor; in this case, the creator is Edward Mehl.
• Invoice Amounts > $5K but less than $10K should be routed to Kerry Lane or the Level 2
supervisor.
• Invoice Amounts > $10K should be routed to the Casey Brown or the Level 3 supervisor.
Note: It is very important to define the last approver that would approve amounts up to infinity, such as
Casey Brown who needs to approve any invoice greater than $10,000. Otherwise, if you enter an invoice
for $250,000, the invoice will not be routed to anyone and will stay in limbo.
Page 1 of 10
We will define the following 4 rules where the 2nd rule is used to autoapprove invoices
less than $1000.
3. Query task Define Approval Management for Financials. Expand the task and select the Go to Task icon
for Mange Task Configurations for Financials.
Note: You can also access BPM directly by updating your url and appending it with
“/integration/worklistapp,” like so: https://adc-fap0440-
fs.oracledemos.com/integration/worklistapp
Page 2 of 10
5. Leave all defaults.
6. Click the Rules tab. You will see all the rules available for invoice approval. There is no way to know
which one you defined rules for unless you open each one individually. You could uncheck the check box
to disable rules, but you should NOT need to do so because by default they all Ignore any rules.
Page 3 of 10
Modes:
• Parallel: All approvers notified at once all and all must approve
• Single: All approvers get notified but only one needs to approve
7. Click Invoice Approvers on the far left. This rule is a serial rule.
You can define rules based on different attributes of the invoices, such as the Invoice Header, Line and
Distribution and even DFF information.
8. Expand the Manager Approval Rule, the default first rule. Rename it to “Inv1Kto5K.”
Page 4 of 10
10. Select Task.payload.getInvoiceHeader1Response.result.invoiceAmount to define rules based on the
Invoice Amount at the Header Level. Just walk down the folder directory starting at Task.
Note: Do not use Line Level Amounts to drive approval rules. It is not available yet.
12. Enter from and to amounts 1000.01 – 5000 by selecting the magnifying glass icon.
Page 5 of 10
1. List Builder: Supervisory (Select Green “+” Add Approver > Supervisory.
3. Number of levels: 1 (This instructs the system to route the invoice up one supervisory level.)
Page 6 of 10
17. Click OK to close the popup.
less than
1000.
25. List Builder: Supervisory (Select Green “+” Add Approver > Supervisory.
30. Auto Action Enabled: True (This means you want to automatically approve the invoice)
Page 7 of 10
31. AutoAction: “APPROVE”
IF:
Task.payload.invoiceType is “ISP”
THEN:
This rule simply means to ignore invoice approval for ISP (iSupplier Portal Invoices) that come into AP
become they already have their own approval flow. I don’t think most customers would need to approve
these invoices twice.
36. Click the magnifying glass icon for the first IF line
39. Enter from and to amounts 5000.01 – 10000 by selecting the magnifying glass icon.
42. List Builder: Supervisory (Select Green “+” Add Approver > Supervisory).
44. Number of levels: 2 (This instructs the system to route the invoice up two levels.)
To do this, select the magnifying glass, select Get Manager, List Builder Supervisory, Reference User
= task.creator, Hierarchy type “” (double quotes)
Page 8 of 10
46. Top Participant: HierarchyBuilder.getPrincipal("casey.brown",-1,"","")
52. Click the magnifying glass icon for the first IF line
• List Builder: Supervisory (Select Green “+” Add Approver > Supervisory.
• Number of levels: 3 (This instructs the system to route the invoice up three levels.)
Page 9 of 10
58. Starting Participant: HierarchyBuilder.getManager("supervisory",Task.creator,-1,"","")
64. Save your work by pressing the Save icon on the top left.
3. Submit the invoice for approval and then log in as the appropriate supervisor(s) to approve the invoice.
Management Chain: User the Manager OIM hierarchy. And you will need to run a process to suync users from
HCM hierarchy to OIM.
Note: Task Aggregation determines how many notifications the approver receives
Additional Information:
MOS Doc ID: 1342689.1 Fusion Accounts Payables - Invoice Approval Process
https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=575061447014010&id=1342689.1&_adf.
ctrl-state=18x76vmi76_194
Page 10 of 10