Oracle Fusion Invoice Approval Test Cases
Confirm that Oracle Fusion Payables routes invoices for approval according to configured approval rules, and that approve, reject, and exception outcomes correctly update invoice and approval status end to end.
| Test ID | ORCL.P2P.AP.INV.APPROVAL |
| Application | Oracle Fusion Cloud |
| Product | Financials |
| Module | Accounts Payable |
| Process | Invoice Processing |
| Business Flow | Procure-to-Pay |
| Scenario Type | Positive / Functional |
| Test Usage | Functional Testing / Regression Testing / UAT |
| Priority | High |
| Automation | SyntraFlow Ready |
| Library | Syntra Standard |
Note on test design: SyntraFlow executes the detailed Oracle Fusion UI interactions automatically while presenting the scenario as business-readable test steps for documentation, review and reporting. This scenario is presented as 15 business-readable test steps; SyntraFlow's automation executes approximately 42 underlying Oracle Fusion UI actions to complete it.
Test Objective
This test validates that Oracle Fusion Payables correctly routes invoices through their configured approval workflow and that every approve, reject, and exception outcome updates the invoice's approval status and downstream eligibility as expected.
The scenario should confirm that:
- Invoice submission for approval correctly initiates an approval process instance
- Approval routing evaluates configured rules (amount, business unit, account, project) to determine the correct approver or approval chain
- Single-level approval chains route to and are actionable by exactly one designated approver
- Multi-level approval chains route sequentially through all required approvers before completion
- Approve actions update Approval Status to Approved and unlock downstream accounting and payment eligibility
- Reject actions update Approval Status to Rejected and return the invoice to the preparer with a recorded reason
- Request-information, reassignment, and escalation actions route correctly without breaking the approval chain
- Missing-approver and invalid routing configurations are surfaced as exceptions rather than stalling silently
- Approval history remains complete and auditable at every stage of the workflow
This test focuses on approval routing and outcome behavior; invoice validation (matching, tax, tolerance holds) and accounting distribution are covered in related test scenarios.
When to Use This Test
- Confirm auto-approval for invoices below the configured approval threshold or matching auto-approve rules
- Confirm single-level approval for standard, non-PO invoices routed to one designated approver
- Confirm multi-level approval chains driven by amount-based, business-unit-based, or account-based rules
- Confirm correct handling of reject, request-information, and reassignment actions during approval
- Confirm escalation behavior when an approver does not act within the configured response window
- Confirm approval exceptions are raised for missing approvers or invalid routing configuration
Where This Test Fits in the Procure-to-Pay Process
Jarvis models the customer's configured approval rule set — amount, business unit, and account-based conditions resolved against the supervisory or position hierarchy — to determine the expected approver chain before validating that Oracle Fusion routes and resolves each invoice accordingly.
Preconditions
- Business unit is enabled for invoice approval workflow (Payables Options > Approval Options > "Use Invoice Approval Workflow")
- Approval rules are configured and activated in BPM Approval Management for task type FIN_AP_INVOICE_APPROVAL against the test business unit
- The supervisory or position hierarchy referenced by approval rules is current and complete for the accounts/cost centers used in test invoices
- Test approver users exist, are provisioned with the required approval duty roles, and have active BPM Worklist access
- Invoices exist in Incomplete or ready-for-submission status with header and distribution data matching the rule conditions being tested (amount, business unit, account, project)
- DataVault approval-rule dataset (thresholds, approver lists, hierarchy levels, escalation windows) is loaded and mapped to the test business unit
- Escalation timers used by escalation rules are known so response windows can be simulated or fast-forwarded in a non-production environment
- Jarvis AI test data generation is configured to reference DataVault-defined approval rules rather than fixed universal values
- User has the Accounts Payable Invoice Approval duty role (or equivalent) required to submit invoices for approval
Exact setup and field availability may vary by Oracle Fusion implementation and security configuration.
Sample Test Data
| Invoice Number | INV-APR-1001 |
| Business Unit | US1 Business Unit |
| Supplier | Acme Industrial Supply |
| Invoice Amount | ${INVOICE_AMOUNT} (customer-configured test value) |
| Approval Amount Threshold | ${AMOUNT_THRESHOLD} (customer-configured) |
| Distribution Account | ${GL_ACCOUNT_CODE} |
| Project Number (where applicable) | ${PROJECT_NUMBER} |
| Approval Rule Name | AP Invoice Approval - Multi-Level by Amount |
| Approval Hierarchy Type | Supervisory Hierarchy |
| Primary Approver | ${APPROVER_1_USERNAME} |
| Secondary / Escalation Approver | ${APPROVER_2_USERNAME} |
| Escalation Response Window | ${ESCALATION_DAYS} days (customer-configured) |
Sample values are illustrative. Replace them with valid data from the target Oracle Fusion environment.
Test Steps
15 business-readable steps. SyntraFlow's automation executes ~42 underlying UI actions to complete these steps — see How SyntraFlow Automates This Test.
| # | User Action | Expected Result |
|---|---|---|
| 1 | Open Invoice for Approval Submission Preparer opens the completed, validated invoice in the Invoices work area. Invoice Number | Invoice is displayed in Incomplete/Ready status with the Submit for Approval action available. |
| 2 | Submit Invoice for Approval Preparer selects Actions > Submit for Approval on the invoice. Invoice Number | Approval Status changes to Initiated/Pending and an approval process instance is created. |
| 3 | Approval Rules Evaluated Oracle Fusion evaluates the configured approval rules against the invoice's attributes. Amount, Business Unit, Account, Project | The correct rule set is selected and the matching approver or approval chain is determined based on DataVault-configured thresholds and hierarchy. |
| 4 | Task Routed to First Approver The approval task is routed to the first approver, or the invoice is auto-approved if it is below the configured threshold. Approval Amount Threshold | The correct approver receives a notification in BPM Worklist and email, or the invoice moves directly to Approved if auto-approval applies. |
| 5 | Approver Reviews Invoice Approver opens the notification and reviews the invoice header, lines, distributions, and any attachments. | Invoice details, comments, and prior approval history are visible to the approver before they act. |
| 6 | Approver Approves (Positive Path) Approver selects Approve, optionally adding a comment. Primary Approver | The task is marked Approved; if additional approval levels remain, the task routes to the next approver in the chain. |
| 7 | Multi-Level Routing to Next Approver For multi-level rules, the task routes to the second or subsequent approver per the hierarchy or amount-based rule. Secondary / Escalation Approver | The next approver receives a notification, and the approval history reflects the prior approver's action. |
| 8 | Final Approval Recorded The last required approver in the chain approves the invoice. | Invoice Approval Status updates to Approved, and the invoice becomes eligible for accounting and payment processing. |
| 9 | Approver Rejects (Alternate Path) Approver selects Reject and enters a rejection reason. | Approval Status updates to Rejected, and the invoice returns to the preparer for correction with the reason recorded. |
| 10 | Approver Requests More Information Approver selects Request Information and routes a question to the preparer or another user. | The task moves to an Information Requested state; the approval clock pauses until a response is provided. |
| 11 | Approver Reassigns Task Approver reassigns or delegates the approval task to another eligible approver. | Task ownership transfers to the new approver, who is notified, while the original approver is removed from the pending list. |
| 12 | Escalation on No Action The assigned approver does not act within the configured escalation response window. Escalation Response Window | The task automatically escalates to the next-level approver or supervisor per the configured escalation rule. |
| 13 | Missing Approver Handling The system attempts to route the task but the hierarchy or rule data is incomplete (for example, no manager on file for the account owner). | The approval process raises a routing exception and flags the invoice for administrator intervention rather than stalling silently. |
| 14 | Verify Approval History Reviewer opens the invoice's Approval History or workflow tab. | All approval actions (submit, approve, reject, request information, reassign, escalate) are logged with user, timestamp, and comments. |
| 15 | Confirm Business OutcomeBusiness assertion Confirm that the invoice's status, approval status, and downstream eligibility reflect the correct end-to-end outcome for the scenario under test. | Invoice state (Approved, Rejected, or Exception) matches the expected business outcome for the configured approval rule and scenario tested. |
Expected Results
- Invoices matching auto-approval criteria bypass manual approval and reach Approved status automatically
- Single-level approvals route to and are actionable by exactly one designated approver
- Multi-level approvals route sequentially through all required approvers before reaching Approved status
- Amount-based, business-unit-based, and account-based rules correctly select the applicable approval chain
- Reject actions return the invoice to the preparer with a recorded rejection reason and Rejected approval status
- Request-information and reassignment actions do not break or duplicate the approval chain
- Escalation rules correctly forward unactioned tasks to the next-level approver within the configured window
- Missing-approver and invalid-configuration scenarios are surfaced as exceptions, not silent failures
- Approval history is complete, accurate, and available for audit on every invoice
- Only fully approved invoices become eligible for accounting and payment processing
Key Validation Checkpoints
- Approval Status field transitions correctly at each stage (Required > Initiated > Pending > Approved/Rejected)
- Correct approval rule or rule set is selected based on invoice attributes
- Correct approver(s) identified per DataVault-configured hierarchy and thresholds
- Notification is delivered to the correct approver in BPM Worklist
- Approve action updates status and advances the workflow to the next stage
- Reject action updates status, captures the reason, and returns the invoice to the preparer
- Request Information pauses the workflow without losing approval context
- Reassignment transfers task ownership without gaps in the approval chain
- Escalation triggers within the configured response window
- Missing-approver and invalid-configuration scenarios raise a visible, actionable exception
- Approval history log captures user, action, timestamp, and comments for every action
- Invoice does not become payment-eligible until fully approved
Go Beyond the Standard Test with Jarvis AI
The Syntra Standard Test Library defines the core business scenario. Jarvis AI can extend this scenario by generating additional positive and negative test variations using customer-specific test data and configuration available through Syntra DataVault.
Teams do not need to manually duplicate the same invoice approval test case dozens of times simply to cover different combinations of data and configuration. Jarvis uses the standard business scenario as the foundation and generates relevant variations for the customer's environment.
From Standard Test to Executed Regression Pack
Rather than maintaining dozens of near-duplicate copies of the same test, SyntraFlow maintains the core business scenario and allows Jarvis AI to generate relevant variations using the customer's available test data.
AI-Generated Test Variations
The same Create Standard Supplier Invoice business scenario can produce many test variations without creating separate public library pages. Below is a real slice of SyntraFlow's Build Scripts library, filtered to Accounts Payable Invoice Processing.
- Auto-Approved Invoice
- Single-Level Approval
- Multi-Level Approval
- Amount-Based Approval
- Business Unit-Based Approval
- Account-Based Approval
- Project-Based Approval
- Multiple Approvers
- Information Requested
- Escalated Approval
- Missing Approver
- Approval Routing Exception
- Rejected Invoice
- Invalid Approval Configuration
- Invoice Not Eligible for Approval
These are representative examples only. Expected behavior can depend on the customer's Oracle Fusion configuration, controls and security — not every Oracle configuration behaves identically.
Generated Using Your DataVault Test Data
A traditional test case hardcodes a single approver and ignores rule logic entirely. DataVault instead stores the customer's actual approval-rule configuration, letting Jarvis generate variations that reflect real routing behavior.
Standard Library Definition
Test Case: AP_INV_APPROVAL_01 Approval Rule: Single approver "jsmith" for all invoices in US1 Business Unit Approval Threshold: Not evaluated (fixed approver regardless of amount) Expected Approver: jsmith Expected Outcome: Approved
DataVault
DataVault: AP_Invoice_Approval_Rules
Business Unit: ${BUSINESS_UNIT}
Approval Threshold: ${AMOUNT_THRESHOLD}
Rule Type: ${APPROVAL_RULE_TYPE} // Amount-Based, BU-Based, Account-Based, Project-Based
Hierarchy: ${HIERARCHY_TYPE} // Supervisory, Position, Job-Level
Approver Chain: ${APPROVER_LIST} // ordered list resolved per hierarchy level
Escalation Window: ${ESCALATION_DAYS} days
Auto-Approve Below Threshold: ${AUTO_APPROVE_FLAG}
Jarvis AI Generates
Invoice ${INV_1}: Amount below ${AMOUNT_THRESHOLD} -> Auto-Approved, no approver action required
Invoice ${INV_2}: Amount above ${AMOUNT_THRESHOLD}, single-level rule -> routed to ${APPROVER_1}, Approved
Invoice ${INV_3}: Multi-level rule (Business Unit + Amount) -> routed to ${APPROVER_1} then ${APPROVER_2}, Approved
Invoice ${INV_4}: Account-based rule matches a restricted GL account -> routed to ${APPROVER_3}, Rejected with reason "Budget exceeded"
Invoice ${INV_5}: ${APPROVER_1} does not act within ${ESCALATION_DAYS} days -> escalated to ${APPROVER_2}
Invoice ${INV_6}: Hierarchy gap for the cost center owner -> Approval Routing Exception raised, no approver found
Customer-specific test data and AI-generated variations are not published to the Syntra Standard Test Library. They remain within the customer's controlled SyntraFlow environment and access model.
Example Test Variations
Every routing path Jarvis can generate from the customer's DataVault-configured approval rules, from straight auto-approval through multi-level chains, exceptions, and rejections.
| ID | Variation | Type | Key Difference | Execution |
|---|---|---|---|---|
| VAR-001 | Auto-approved invoice below threshold | Auto | Amount < ${AMOUNT_THRESHOLD}; no manual approver required | Syntra Ready |
| VAR-002 | Single-level approval by designated approver | Single-Level | One approver resolved from hierarchy; standard non-PO invoice | Syntra Ready |
| VAR-003 | Multi-level approval by amount tier | Multi-Level | Sequential chain across two or more amount-based tiers | Syntra Ready |
| VAR-004 | Multi-level approval by business unit and account | Multi-Level | Combined BU-based and account-based rule conditions | Syntra Ready |
| VAR-005 | Project-related approval routing | Single-Level/Multi-Level | Approver resolved from project role instead of cost center hierarchy | Syntra Ready |
| VAR-006 | Approver rejects invoice | Rejection | Invoice returned to preparer with rejection reason captured | Syntra Ready |
| VAR-007 | Approver requests more information | Single-Level | Workflow paused pending preparer response, then resumes | Syntra Ready |
| VAR-008 | Approver reassigns task | Single-Level/Multi-Level | Task delegated to a proxy approver mid-chain | Syntra Ready |
| VAR-009 | Escalation after no approver action | Exception | Response window elapses; task escalates to next-level approver | Syntra Ready |
| VAR-010 | Missing approver / routing exception | Exception | Hierarchy gap prevents approver resolution; exception raised | Syntra Ready |
No variations match this filter.
Automatically Expand Positive and Negative Test Coverage
Positive Testing
Jarvis generates scenarios using combinations expected to successfully complete the business process.
Valid data → Invoice Approval completes successfully
Negative Testing
Jarvis can generate scenarios designed to exercise validations, business rules and exception handling.
- Missing Approver → Expected Oracle validation
- Approval Routing Exception → Expected Oracle validation
- Rejected Invoice → Expected Oracle validation
A negative test should not be marked as failed simply because Oracle rejects the transaction. If the expected Oracle validation occurs, the negative test has passed.
| Scenario | Oracle Outcome | Test Result |
|---|---|---|
| Invoice below the configured approval threshold | Auto-approved without manual approver action | PASS |
| Invoice routed through a multi-level approval chain | Approved after all required approvers act in sequence | PASS |
| Approver rejects an invoice with an invalid distribution account | Invoice correctly rejected and returned to the preparer | PASS |
| Approver hierarchy missing for the cost center owner | Approval routing exception raised; invoice flagged for administrator review | PASS |
| Approval task routed to an inactive user account with no failover | Unexpected error: task delivered to an inactive approver and the approval stalls indefinitely | FAIL |
Turn AI-Generated Variations into a Regression Pack
Users can select generated scenarios and group them into reusable execution packs.
AP Invoice Approval Regression Pack
- Auto-Approval Below Threshold
- Single-Level Approval
- Multi-Level Approval Chain
- Amount-Based Routing
- Business Unit-Based Routing
- Account-Based Routing
- Rejected Invoice Returns to Preparer
- Escalation on No Approver Action
- Missing Approver Exception
- Invalid Approval Configuration Exception
Run On-Demand or Schedule Automated Batch Execution
SyntraFlow can execute selected scenarios individually or as a batch. Users can schedule regression packs according to their testing cycle.
Once scheduled, SyntraFlow executes the selected scenarios unattended and records the outcome of each test and business assertion.
| Pack | AP Invoice Approval Regression Pack |
| Schedule | Weekly Regression |
| Tests | 20 scenarios |
| Execution | Batch Mode |
| Start | 10:00 PM |
| Environment | Oracle Fusion TEST |
| Status | Scheduled |
Illustrative example — not a live schedule.
Review Results Across the Entire Test Pack
Users can drill from the regression pack into a scenario, its business steps, the underlying automation actions, and the evidence captured for each.
Illustrative example data — not actual production metrics.
Regression Pack → Scenario → Business Step → Automation Action → Evidence
From Business Scenario to Execution Evidence
Business teams get readable test documentation; automation teams retain detailed execution traceability.
Meet Jarvis — SyntraFlow's AI Testing Engine
Jarvis extends the Syntra Standard Test Library by analysing the business scenario, available DataVault test data and expected business outcomes to generate additional test coverage for the customer's environment.
How SyntraFlow Automates This Test
The Standard Test defines the scenario; DataVault, Jarvis AI and SyntraFlow's execution engine take it from a single reusable business definition to executed, evidenced regression coverage.
Business Step → Underlying UI Actions
What SyntraFlow Captures Per Run
Action Status vs. Business Validation
A successful UI interaction does not automatically prove the business outcome — this is illustrative of how SyntraFlow separates action success from business validation; it does not reflect a specific live execution.
| Step | Action Status | Business Validation |
|---|---|---|
| Submit Invoice for Approval | Pass | Pass |
| Route to First Approver | Pass | — |
| Approver Rejects Invoice | Pass | Pass (rejection reason correctly captured) |
| Escalation Triggered After No Action | Pass | Pass |
| Missing Approver Detected | Pass | Pass (exception correctly raised) |
Related Oracle Fusion AP Invoice Test Cases
Part of the same Procure-to-Pay invoice lifecycle. Linked cards are live; the rest are on the Syntra Standard Test Library roadmap.
Turn This Standard Test into Your Oracle Regression Suite
Start with the Syntra Standard Invoice Approval test, use DataVault to provide environment-specific test data, let Jarvis generate additional positive and negative variations, and execute the resulting regression pack automatically with SyntraFlow.
Use This Oracle Fusion Test Case
Add to Test Library
Save to your SyntraFlow regression suite.
Coming soonAutomate with SyntraFlow
Run this script against your own tenant today.