Oracle ERP Testing Tool > Test Library > Financials > Accounts Payable > Payments

Syntra Standard Oracle Test Library

Oracle Fusion Payment Process Request Test Cases

Validate creation and execution of an Oracle Fusion Payment Process Request to select eligible invoices and process supplier payments according to configured selection criteria and payment processing rules, including exception handling for invoices and suppliers that should be excluded.

Test ID	ORCL.P2P.AP.PAY.PPR
Application	Oracle Fusion Cloud
Product	Financials
Module	Accounts Payable
Process	Payments
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 12 business-readable test steps; SyntraFlow's automation executes approximately 44 underlying Oracle Fusion UI actions to complete it.

Test Objective

The objective of this test is to verify that an authorised Accounts Payable user can create and submit a Payment Process Request that correctly selects eligible invoice installments and processes them into payments according to the configured selection criteria and payment processing rules.

The scenario should confirm that:

invoices matching the configured selection criteria are correctly identified as eligible
invoices and suppliers that should be excluded are correctly excluded from selection
proposed payments are grouped and calculated correctly by supplier, currency and payment method
exceptions raised during selection or build are surfaced clearly rather than silently dropped
the request progresses through its expected lifecycle to a completed status
created payments are consistent with the invoices selected and the configured payment process profile

This scenario validates selection, exception handling and payment build within Oracle Fusion. It does not claim that SyntraFlow transmits real funds or performs an actual bank transaction — testing is performed against Oracle Fusion TEST/UAT environments.

When to Use This Test

Functional testing of Payment Process Request selection and build for a new Oracle Fusion implementation
Regression testing of selection criteria, exception handling and payment build after an Oracle quarterly update
UAT sign-off for AP payment run processing across suppliers, bank accounts and payment methods
Baseline case referenced by the create, electronic payment and validation scenarios within the same AP payment lifecycle

Where This Test Fits in the AP Payment Lifecycle

Create Payment Process Request

→

Define Selection Criteria

→

Select Eligible Installments

→

Review Proposed Payments

→

Resolve Exceptions

→

Build Payments

→

Format/Transmit Where Applicable

→

Complete Process

Not every Oracle Fusion implementation uses exactly the same stages in the same order — formatting and transmission, for example, may sit outside the scope tested here depending on customer configuration. This scenario covers request creation through to a completed Payment Process Request and the resulting payments.

Preconditions

Oracle Fusion Accounts Payable and Payments access is available to the test user.
Eligible, validated and approved invoices exist for the test payment business unit and supplier.
A payment process profile is configured and available for selection.
A disbursement bank account and payment method are configured and available.
Supplier banking information required for the selected payment method is valid and complete.
The relevant accounting period is open for payment processing.

Exact selection criteria fields, payment process profile options and available payment methods may vary by Oracle Fusion implementation and payables configuration.

Sample Test Data

Payment Business Unit	${PAYMENT_BUSINESS_UNIT}
Payment Process Profile	${PAYMENT_PROCESS_PROFILE}
Disbursement Bank Account	${DISBURSEMENT_BANK_ACCOUNT}
Payment Method	${PAYMENT_METHOD}
Supplier	${SUPPLIER}
Supplier Site	${SUPPLIER_SITE}
Invoice Number	${INVOICE_NUMBER}
Due Date	${DUE_DATE}
Pay Through Date	${PAY_THROUGH_DATE}
Payment Currency	${PAYMENT_CURRENCY}
Payment Priority	${PAYMENT_PRIORITY}
Payment Group	${PAYMENT_GROUP}

Sample values are illustrative. Replace them with valid data from the target Oracle Fusion environment.

Test Steps

12 business-readable steps. SyntraFlow's automation executes ~44 underlying UI actions to complete these steps — see How SyntraFlow Automates This Test.

#	User Action	Expected Result
1	Navigate to Payment Process Requests Navigate to the Payment Process Requests work area within Oracle Fusion Payables.	The Payment Process Requests work area opens successfully.
2	Create a New Request Create a new Payment Process Request.	A new Payment Process Request is opened and ready for selection criteria entry.
3	Select Payment Business Unit Select the payment business unit for the request. ${PAYMENT_BUSINESS_UNIT}	The selected payment business unit is applied to the request.
4	Select Payment Process Profile Select the payment process profile that determines how selected invoices will be processed into payments. ${PAYMENT_PROCESS_PROFILE} / ${DISBURSEMENT_BANK_ACCOUNT} / ${PAYMENT_METHOD}	The selected payment process profile, bank account and payment method are applied to the request.
5	Enter Selection Criteria Enter the selection criteria that determine which invoice installments are eligible for this request, including supplier, due date range and pay-through date. ${SUPPLIER} / ${SUPPLIER_SITE} / ${DUE_DATE} / ${PAY_THROUGH_DATE} / ${PAYMENT_CURRENCY} / ${PAYMENT_PRIORITY} / ${PAYMENT_GROUP} This single business step replaces multiple technical actions such as opening the selection criteria panel, entering each individual field and confirming the entry.	Selection criteria are accepted and applied to the request.
6	Submit Request Submit the Payment Process Request for processing.	Oracle Fusion accepts the request and begins selecting eligible installments.
7	Review Selected Installments Review the list of invoice installments selected against the configured criteria. ${INVOICE_NUMBER}	Installments matching the selection criteria are listed, and ineligible installments are correctly excluded.
8	Resolve Applicable Exceptions Review and, where applicable, resolve exceptions raised during selection, such as invoices or suppliers on hold or missing banking information. Not every exception is expected to be resolvable within this scenario — some are expected to remain excluded, such as a supplier on payment hold.	Exceptions are clearly identified and, where resolvable within scope, are addressed before the request proceeds to build.
9	Build Payments Initiate the payment build step to convert the reviewed installments into proposed payments.	Oracle Fusion builds proposed payments grouped by supplier, currency and payment method for the selected installments.
10	Complete Payment Processing Complete the Payment Process Request, including formatting and transmission where those stages are part of the tested scope.	The request progresses to a completed status without unexpected errors.
11	Verify Request StatusBusiness assertion Confirm the final status of the Payment Process Request.	The request status correctly reflects a completed run, or clearly reflects any unresolved exceptions.
12	Validate Created PaymentsBusiness assertion Review the payments created by the request and confirm they are consistent with the selected invoices, supplier grouping, currency and amounts. This is the main business assertion for the scenario — the test does not stop merely because the request completed without error.	Created payments match the selected invoices and configured processing rules, with correct supplier grouping, amounts and bank account.

Expected Results

Eligible invoice installments matching selection criteria are correctly selected.
Excluded invoices and suppliers, such as those on hold, are correctly handled and not selected.
Proposed payments are grouped correctly by supplier, currency and payment method.
Payment amounts on created payments match the selected invoices.
The correct bank account and payment process profile are applied to created payments.
The request progresses through its lifecycle to a completed status without unexpected errors.
Exceptions raised during selection or build are clearly identified rather than silently dropped.
The final Payment Process Request status accurately reflects the outcome of the run.

Key Validation Checkpoints

Correct invoices are selected against the configured criteria.
Excluded invoices are correctly handled and not selected.
Supplier and payment grouping on proposed payments is correct.
Payment amounts match the selected invoice installments.
The correct bank account and payment process profile are applied.
Payment status progresses correctly through the request lifecycle.
Exceptions are clearly identified during selection or build.
Final Payment Process Request status is correct and consistent with the outcome.

Core Business Scenario

Payment Process Request

Business Steps

Test Variations

AI-Generated

Test Data

DataVault-Driven

Execution

On-Demand / Scheduled / Batch

Automation

SyntraFlow Ready

Jarvis AI

Go Beyond the Standard Test with Jarvis AI

The Syntra Standard Test Library defines the core Payment Process Request scenario. Jarvis AI can extend this scenario by generating additional selection, supplier, bank, profile and exception variations using customer-specific test data and configuration available through Syntra DataVault.

Teams do not need to manually build a separate test for every combination of supplier, bank account, payment method, currency and exception condition. Jarvis uses the standard scenario as the foundation and generates relevant variations, including high-volume batch scenarios, for the customer's environment.

From Standard Test to Executed Regression Pack

Syntra Standard Test

Reusable Payment Process Request scenario and automation logic.

Customer DataVault

Provides approved customer-specific test data and configuration required for scenario generation — Payment Business Units, Suppliers, Bank Accounts, Payment Methods, Process Profiles and Currencies.

Jarvis AI

Analyses the standard scenario together with available test data and generates relevant selection, supplier, bank, profile and exception variations.

Positive + Negative Test Variations

Successful selection and build scenarios alongside exception and rejection scenarios.

Regression Pack

Selected variations can be grouped into an executable suite.

On-Demand / Scheduled / Batch Execution

Execute immediately or schedule the regression pack for unattended batch execution, including high-volume payment batches.

Results + Evidence + Exceptions

Capture execution results, business assertions, screenshots/evidence and exception classification.

Rather than maintaining a separate test for every combination of supplier, bank account, payment method and exception condition, SyntraFlow maintains one core Payment Process Request scenario and allows Jarvis AI to generate relevant variations using the customer's available test data.

AI-Generated Test Variations

The same Payment Process Request 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 Payments.

Positive Scenarios

Single supplier payment request
Multiple suppliers in one request
Single invoice selected
Multiple eligible invoices selected
Due invoices selected by due date
Pay-through-date selection
Different payment currencies
Different payment methods
Different payment priorities
Different disbursement bank accounts
High-volume payment batch
Multiple supplier sites for one supplier
Different payment process profiles

Negative Scenarios

No eligible invoices found
Invoice on hold excluded from selection
Supplier payment hold excludes supplier
Invalid bank account configured for the profile
Invalid payment method selected
Invalid payment process profile
Missing supplier banking information
Invalid payment currency
Rejected installment excluded from selection
Selection criteria validation failure
Payment build exception
Formatting or transmission exception, where in scope
Batch processing dependency failure

These are representative examples only. Selection criteria, exception conditions and payment build 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

Generic test data rarely represents every supplier, bank account, payment method and process profile combination in a real Oracle Fusion environment. Where connected, Jarvis can use approved test data available through Syntra DataVault to construct selection and exception scenarios relevant to the customer's actual implementation, including high-volume batch scenarios.

Standard Library Definition

Payment Business Unit   ${PAYMENT_BUSINESS_UNIT}
Payment Process Profile ${PAYMENT_PROCESS_PROFILE}
Bank Account            ${DISBURSEMENT_BANK_ACCOUNT}
Payment Method          ${PAYMENT_METHOD}
Supplier                ${SUPPLIER}
Supplier Site           ${SUPPLIER_SITE}
Invoice Number          ${INVOICE_NUMBER}
Due Date                ${DUE_DATE}
Pay Through Date        ${PAY_THROUGH_DATE}
Currency                ${PAYMENT_CURRENCY}
Priority                ${PAYMENT_PRIORITY}
Payment Group           ${PAYMENT_GROUP}

DataVault

Payment Business Units
  Configured per legal entity
Payment Process Profiles
  Configured formats and processing rules
Bank Accounts
  Disbursement accounts per business unit
Suppliers / Sites
  Active suppliers with valid or deliberately incomplete banking information
Currencies
  USD, GBP, EUR + unconfigured pairs

Jarvis AI Generates

Scenario 01 — Single Supplier, Single Invoice
Scenario 02 — Multiple Suppliers, Multiple Invoices
Scenario 03 — Due-Through-Date Selection
Scenario 04 — High-Volume Batch, 500+ Invoices
Scenario 05 — Supplier Payment Hold Exclusion
Scenario 06 — Missing Supplier Banking Information
...

Customer-specific test data and AI-generated variations are not published to the Syntra Standard Test Library. Where DataVault is connected, customer-specific dimensions such as suppliers, bank accounts and banking information remain within the customer's controlled SyntraFlow environment and access model.

Example Test Variations

Representative examples of Payment Process Request scenarios Jarvis can generate from this business scenario, spanning selection, supplier, due date, bank, profile, exception and batch conditions. These are illustrative, not separate indexable pages — the canonical page for all of them remains this one.

ID	Variation	Type	Key Difference	Execution
VAR-001	Single Supplier Payment Request	Supplier	One supplier, standard selection criteria	Syntra Ready
VAR-002	Multiple Suppliers in One Request	Supplier/Selection	Several suppliers selected within one request	Syntra Ready
VAR-003	Single Invoice Selected	Selection	Only one eligible installment matches criteria	Syntra Ready
VAR-004	Multiple Eligible Invoices Selected	Selection	Several installments match selection criteria	Syntra Ready
VAR-005	Due Invoices Selected by Due Date	Due Date	Selection restricted to invoices due within range	Syntra Ready
VAR-006	Pay-Through-Date Selection	Due Date/Selection	Selection bounded by configured pay-through date	Syntra Ready
VAR-007	Different Payment Currency — EUR	Selection	Payment currency = EUR	Syntra Ready
VAR-008	Different Payment Method — Electronic	Profile	Payment method = electronic funds transfer	Syntra Ready
VAR-009	Different Payment Priority	Selection	Higher-priority payment group selected first	Syntra Ready
VAR-010	Different Disbursement Bank Account	Bank	Secondary disbursement bank account used	Syntra Ready
VAR-011	High-Volume Payment Batch	Batch	Large number of installments processed in one request	Syntra Ready
VAR-012	Multiple Supplier Sites for One Supplier	Supplier	Supplier has invoices across multiple sites	Syntra Ready
VAR-013	Different Payment Process Profile	Profile	Alternate process profile with different processing rules	Syntra Ready
VAR-014	No Eligible Invoices Found	Selection	Selection criteria match zero installments	Syntra Ready
VAR-015	Invoice on Hold Excluded	Selection/Exceptions	Invoice on hold correctly excluded from selection	Syntra Ready
VAR-016	Supplier Payment Hold Excludes Supplier	Supplier/Exceptions	Supplier-level payment hold excludes all its invoices	Syntra Ready
VAR-017	Invalid Bank Account Configured	Bank/Exceptions	Configured bank account fails validation at build	Syntra Ready
VAR-018	Invalid Payment Method Selected	Profile/Exceptions	Payment method not valid for supplier or profile	Syntra Ready
VAR-019	Invalid Payment Process Profile	Profile/Exceptions	Selected process profile is misconfigured or inactive	Syntra Ready
VAR-020	Missing Supplier Banking Information	Supplier/Exceptions	Required banking details are absent for the payment method	Syntra Ready
VAR-021	Invalid Payment Currency	Selection/Exceptions	Currency not supported for the bank account or profile	Syntra Ready
VAR-022	Rejected Installment Excluded	Selection/Exceptions	Previously rejected installment correctly excluded	Syntra Ready
VAR-023	Selection Criteria Validation Failure	Selection/Exceptions	Incomplete or invalid selection criteria entered	Syntra Ready
VAR-024	Payment Build Exception	Exceptions	Build step raises an exception for one or more installments	Syntra Ready
VAR-025	Formatting or Transmission Exception	Exceptions	Exception raised during formatting or transmission, where in scope	Syntra Ready
VAR-026	Batch Processing Dependency Failure	Batch/Exceptions	Upstream dependency required for batch processing is not satisfied	Syntra Ready

Automatically Expand Positive and Negative Test Coverage

Positive Testing

Jarvis generates scenarios using combinations of supplier, bank account, payment method and criteria expected to successfully select and process eligible invoices into payments.

Eligible Invoices + Valid Bank Account + Active Payment Method → Payments Built Successfully

Negative Testing

Jarvis can also generate scenarios designed to exercise Oracle's selection, validation and exception handling around Payment Process Requests.

No Eligible Invoices → Expected Empty Selection Reported
Invoice on Payment Hold → Expected Exclusion from Selection
Supplier on Payment Hold → Expected Supplier Exclusion
Invalid Bank Account → Expected Build Exception
Missing Supplier Banking Information → Expected Exception Raised
Invalid Payment Process Profile → Expected Configuration Validation

Negative tests pass when Oracle correctly excludes or blocks an ineligible condition. A negative test should not be marked as failed simply because Oracle rejects or excludes it — if the expected exclusion or exception occurs, the negative test has passed.

Scenario	Oracle Outcome	Test Result
Eligible invoices selected	Payments built successfully	PASS
No eligible invoices	Empty selection correctly reported	PASS
Invoice on hold	Excluded from selection	PASS
Invalid bank account	Build exception raised	PASS
Missing supplier banking information	Exception raised	PASS
Unexpected system error	Unexpected failure	FAIL

Turn AI-Generated Variations into a Regression Pack

Users can select generated Payment Process Request scenarios and group them into reusable execution packs.

Payment Process Request Regression Pack

Single Supplier Payment Request
Multiple Suppliers in One Request
Due Invoices Selected by Due Date
Different Payment Currency — EUR
Different Disbursement Bank Account
High-Volume Payment Batch
No Eligible Invoices Found
Invoice on Hold Excluded
Supplier Payment Hold Excludes Supplier
Invalid Bank Account Configured
Missing Supplier Banking Information
Payment Build Exception

Add Selected to Regression Pack(coming soon)Run Now(coming soon)Schedule(coming soon)

Run On-Demand or Schedule Automated Batch Execution

SyntraFlow can execute selected Payment Process Request scenarios individually or as a batch. Users can schedule regression packs according to their payment run cycle.

Once scheduled, SyntraFlow executes the selected Payment Process Request scenarios unattended and records the outcome of each test and business assertion, including high-volume batch runs.

Run immediatelyNightly regressionWeekly regressionBefore releaseAfter configuration changesAfter environment refreshQuarterly Oracle update testingPre-UAT validation

Pack	Payment Process Request Regression Pack
Schedule	Quarterly Update Regression
Tests	26 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.

Total Scenarios

Passed

Failed

Exceptions

Positive Tests

Negative Tests

128

Business Assertions

Regression Pack → Scenario → Business Step → Automation Action → Evidence

AP Payment Lifecycle

Several scenario families share the same lifecycle position — for example, Create Payment, Pay Invoice in Full and Partial Payment are all ways of creating a payment. Exact processing depends on payment method, bank-account configuration and customer-specific Oracle Fusion setup. Stages link to a representative test scenario family.

Create / Select→Validate→

Process / Electronic Payment

→Void where required→Account

Understand Why a Test Failed

SyntraFlow execution evidence can help distinguish business-data failures, configuration issues, automation problems and potential application defects.

DataConfigurationSecurityAutomationApplicationEnvironmentExpected Validation

Jarvis Failure Intelligence — Coming Soon

From Business Scenario to Execution Evidence

Business teams get readable test documentation; automation teams retain detailed execution traceability.

Standard Business Scenario

AI-Generated Variation

Regression Pack

Business Test Step

Automation Actions

Business Assertion

Screenshot / Evidence

Execution Result

Meet Jarvis — SyntraFlow's AI Testing Engine

Jarvis extends the Syntra Standard Test Library by analysing the Payment Process Request scenario, available DataVault test data and expected business outcomes to generate additional selection, supplier, bank, profile and exception coverage for the customer's environment.

Generate

Positive and negative variations.

Parameterize

Use relevant test data from DataVault.

Assemble

Build reusable regression packs.

Execute

Run scenarios autonomously.

Schedule

Execute unattended test batches.

Validate

Evaluate expected business outcomes.

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.

Standard Library — Payment Process Request, 12 Business Steps

↓

DataVault — Customer-Specific Test Data

↓

Jarvis AI — Generate Selection, Supplier, Bank, Profile and Exception Variations

↓

Regression Pack — Select Relevant Coverage

↓

SyntraFlow Execution — Each Variation

↓

Detailed UI Actions

↓

Business Assertions

↓

Evidence

↓

PASS / FAIL

Business Step → Underlying UI Actions

Business Step

Enter Selection Criteria

May internally include

Open Selection Criteria Panel → Set Business Unit → Set Supplier/Site → Set Due Date Range → Set Pay Through Date → Set Currency/Priority/Group → Confirm

Business Step

Build Payments

May internally include

Open Build Step → Initiate Build → Poll Build Status → Capture Grouping Result → Capture Exceptions

What SyntraFlow Captures Per Run

Parameterised input valuesReusable navigationAutomation action traceScreenshots / evidence captureExecution timingPass / fail statusBusiness assertionsEnvironment-independent test data

Action Status vs. Business Validation

A successful UI interaction does not automatically prove the correct payments were created — 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 Request	Pass	—
Build Payments	Pass	—
Validate Created Payments	Pass	Pass

Related AP Payment Tests

A Payment Process Request is one stage of the same Accounts Payable payment lifecycle — explore the related creation, electronic payment and validation scenarios below.

Create Payment Electronic Payment Payment Validation

Turn This Standard Test into Your Oracle AP Payment Regression Suite

Start with the Syntra Standard Payment Process Request test, use DataVault to provide environment-specific test data, let Jarvis generate additional selection, supplier, bank, profile and exception variations, and execute the resulting regression pack automatically with SyntraFlow.

Automate with SyntraFlow Explore AP Payments Test Library

Use This Oracle Fusion Test Case

Download Test Case

Excel, CSV or JSON export.

Coming soon

Automate with SyntraFlow

Run this script against your own tenant today.

Related Oracle Testing Resources

Oracle ERP Testing Tool Test Library Financials Test Library Accounts Payable Test Library AP Payments Test Library Syntra DataVault

Frequently Asked Questions

What is an Oracle Fusion Payment Process Request?

A Payment Process Request is the Oracle Fusion Payables process that selects eligible invoice installments against configured criteria and builds them into payments according to a payment process profile, bank account and payment method.

How does the selection criteria used in this test work?

Selection criteria such as payment business unit, supplier, due date range and pay-through date determine which invoice installments are eligible. This test confirms that eligible installments are correctly selected and ineligible ones are correctly excluded.

How are exceptions such as invoices or suppliers on hold resolved?

Exceptions raised during selection or build — such as an invoice on hold, a supplier payment hold or missing supplier banking information — are reviewed as part of the scenario. Some exceptions are expected to remain excluded rather than resolved, and the test confirms these are clearly identified rather than silently dropped.

How does this differ from the Create Payment test?

Create Payment covers creating an individual payment directly. A Payment Process Request instead selects and processes a set of eligible invoices in bulk against configured criteria, which is the more common way payments are generated for a batch of suppliers.

Does this test cover payment file formatting and transmission?

Formatting and transmission are included only where they form part of the customer's tested scope and configuration. Where those stages are out of scope, this test validates request completion and the resulting payments up to the build step.