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

Syntra Standard Oracle Test Library

Oracle Fusion Create Supplier Payment Test Cases

Validate creation of a supplier payment for an eligible, validated Oracle Fusion Payables invoice using a valid supplier, invoice, payment method, disbursement bank account, currency and payment date, and confirm the resulting payment and invoice status are correct.

Test ID	ORCL.P2P.AP.PAY.CREATE
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 34 underlying Oracle Fusion UI actions to complete it.

Test Objective

This test validates that Oracle Fusion Payables can create a supplier payment for an eligible, validated invoice using a valid supplier, invoice, payment method, disbursement bank account, currency and payment date.

The scenario should confirm that:

the correct supplier, supplier site and invoice are selected for payment
the payment method and disbursement bank account are valid and accepted for the transaction
the payment amount, currency and payment date are correctly applied
Oracle Fusion creates the payment and returns a unique payment identifier
the source invoice's payment status is updated to reflect the new payment
the resulting payment record is available for subsequent validation, processing and accounting steps

This scenario validates creation of the payment itself. Downstream payment validation, processing (including electronic payment file generation), void handling and payment accounting are covered by separate test scenarios within the same AP Payment lifecycle.

When to Use This Test

Functional testing of supplier payment creation for a new Oracle Fusion Payables implementation
Regression testing of payment creation after an Oracle quarterly update affecting Payments
UAT sign-off for AP payment processing controls before go-live
Baseline case referenced by the validation, processing, void and accounting scenarios within the same AP Payment lifecycle

Where This Test Fits in the AP Payment Process

Eligible Invoice

→

Open Payment

→

Select Supplier/Invoice

→

Select Payment Method

→

Select Bank Account

→

Enter Payment Details

→

Create Payment

→

Verify Status

This test covers creating a payment for an eligible, validated invoice and confirming the resulting payment and invoice status. It depends on the invoice already being validated and, where required, approved, and it is a prerequisite for the subsequent validation, processing, void and accounting scenarios in the same AP Payment lifecycle.

Next Stage →

Payment Process Request

Preconditions

The invoice exists in Oracle Fusion Payables and has been validated.
The invoice satisfies any required approval status before it can be paid.
The invoice is not subject to an applicable payment hold.
The supplier and supplier site are active and configured for payment.
Supplier payment information — such as banking details and payment method — is valid and complete.
A disbursement bank account is configured for the business unit and payment method.
The applicable payment method and, where required, payment process profile are available.
The accounting date and payment date fall within a valid, open period.

Exact preconditions and field requirements vary by Oracle Fusion implementation, payment method and business unit configuration.

Sample Test Data

Business Unit	${BUSINESS_UNIT}
Supplier	${SUPPLIER}
Supplier Site	${SUPPLIER_SITE}
Invoice Number	${INVOICE_NUMBER}
Invoice Amount	${INVOICE_AMOUNT}
Payment Amount	${PAYMENT_AMOUNT}
Payment Method	${PAYMENT_METHOD}
Payment Currency	${PAYMENT_CURRENCY}
Disbursement Bank Account	${DISBURSEMENT_BANK_ACCOUNT}
Payment Date	${PAYMENT_DATE}
Payment Process Profile	${PAYMENT_PROCESS_PROFILE} — where applicable

Sample values are illustrative. Replace them with valid supplier, invoice, banking and currency data from the target Oracle Fusion environment; not every field applies to every payment method or configuration.

Test Steps

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

#	User Action	Expected Result
1	Sign In to Oracle Fusion Sign in to Oracle Fusion Cloud with a user account that has Accounts Payable payment processing access.	The Oracle Fusion Cloud home page loads successfully for the authenticated user.
2	Navigate to Payables Navigate to the Payables work area.	The Payables work area opens successfully.
3	Open Payments Open the Payments task within Payables to begin creating a new payment.	The Create Payment page opens.
4	Select Eligible Supplier/Invoice Select the supplier, supplier site and eligible validated invoice to be paid. ${SUPPLIER} / ${SUPPLIER_SITE} / ${INVOICE_NUMBER} This single business step replaces multiple technical actions such as searching for the supplier, selecting the site, filtering eligible invoices and selecting the invoice line.	The selected supplier, site and invoice are accepted, and invoice details are displayed.
5	Enter Payment Details Enter the payment amount, currency and payment date for the selected invoice. ${PAYMENT_AMOUNT} / ${PAYMENT_CURRENCY} / ${PAYMENT_DATE}	Payment details are accepted without validation errors.
6	Select Payment Method Select the payment method to be used for the payment. ${PAYMENT_METHOD}	The selected payment method is accepted and applicable payment process profile options are updated accordingly.
7	Select Disbursement Bank Account Select the disbursement bank account from which the payment will be issued. ${DISBURSEMENT_BANK_ACCOUNT}	The selected bank account is accepted as a valid disbursement account for the payment method and business unit.
8	Review Payment Amount Review the calculated payment amount against the invoice amount and any applicable discount before submitting. ${INVOICE_AMOUNT} / ${PAYMENT_AMOUNT}	The payment amount displayed matches the expected amount for the selected invoice.
9	Create Payment Submit the payment for creation.	Oracle Fusion creates the payment and returns a confirmation.
10	Confirm Payment Status Review the resulting payment status.	The payment status reflects successful creation, consistent with the customer's payment status configuration.
11	Capture Payment Identifier Capture the system-generated payment number for traceability.	A unique payment identifier is generated and retrievable.
12	Verify Invoice Payment StatusBusiness assertion Navigate to the source invoice and confirm its payment status has been updated to reflect the new payment. This is the main business assertion for the scenario — the test does not stop merely because the payment was created; the source invoice must correctly reflect the resulting payment.	The invoice payment status and applied amount correctly reflect the created payment rather than remaining unpaid.

Expected Results

A payment is created successfully for the selected supplier and invoice using a valid payment method, bank account, currency and date.
The correct payment amount is applied against the invoice.
The payment method and disbursement bank account match the selected values.
Payment status reflects successful creation.
A unique payment identifier is generated.
Invoice payment status updates correctly to reflect the new payment.
The payment record is retrievable for subsequent validation, processing and accounting scenarios.

Key Validation Checkpoints

Payment created successfully.
Correct supplier used.
Correct invoice referenced.
Correct payment amount.
Correct payment method.
Correct bank account.
Correct payment date.
Invoice payment status updated appropriately.
Payment identifier generated.
Payment record retrievable.

Core Business Scenario

Create Payment

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 Create Payment scenario. Jarvis AI can extend this scenario by generating additional positive and negative payment variations across suppliers, supplier sites, business units, payment methods, bank accounts, currencies and payment dates using customer-specific test data and configuration available through Syntra DataVault.

Teams do not need to manually build a separate payment-creation test for every supplier, bank account, currency and payment method combination. Jarvis uses the standard Create Payment scenario as the foundation and generates relevant variations for the customer's environment.

From Standard Test to Executed Regression Pack

Eligible Invoice

A validated invoice satisfying approval and hold requirements is available for payment.

Select Payment Details

Supplier, invoice, payment method, disbursement bank account, currency and payment date are selected.

Create Payment

The payment is submitted and created in Oracle Fusion Payables.

Confirm Payment

Payment status and the generated payment identifier are confirmed.

Update Invoice Status

The source invoice's payment status is updated to reflect the new payment.

Regression Pack

Selected payment-creation variations can be grouped into an executable suite.

On-Demand / Scheduled / Batch Execution

Execute immediately or schedule the regression pack for unattended batch execution.

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

AI-Generated Test Variations

The same Create Payment 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

Basic supplier payment
Different suppliers
Different supplier sites
Different Business Units
Different payment methods
Different bank accounts
Different currencies
Different payment dates
Multiple invoice selection where applicable
High-value payment
Payment with configured discount where applicable

Negative Scenarios

Invoice on payment hold
Inactive supplier
Invalid supplier site
Invalid payment method
Invalid disbursement bank account
Missing required payment information
Invalid currency
Closed accounting period
Invalid payment date
Invoice already paid
Invoice not eligible for payment or invalid bank/payment configuration

These are representative examples only. Negative scenarios and expected behavior can depend on the customer's Oracle Fusion configuration, payment methods, banking setup and security — not every Oracle configuration behaves identically.

Generated Using Your DataVault Test Data

Generic test data rarely reflects the suppliers, bank accounts, currencies and payment methods configured in a real Oracle Fusion environment. Where connected, Jarvis can use approved test data available through Syntra DataVault to construct payment-creation scenarios relevant to the customer's actual implementation.

Standard Library Definition

Business Unit            ${BUSINESS_UNIT}
Supplier                 ${SUPPLIER}
Supplier Site            ${SUPPLIER_SITE}
Invoice Number           ${INVOICE_NUMBER}
Payment Amount           ${PAYMENT_AMOUNT}
Payment Method           ${PAYMENT_METHOD}
Payment Currency         ${PAYMENT_CURRENCY}
Disbursement Bank Acct   ${DISBURSEMENT_BANK_ACCOUNT}
Payment Date             ${PAYMENT_DATE}
Accounting Period        ${ACCOUNTING_PERIOD}

DataVault

Business Units
  Configured Business Units and payment calendars
Suppliers
  Active suppliers and sites with valid payment terms
Invoices
  Eligible, validated invoices per supplier
Payment Methods
  Check, EFT, Wire and configured payment process profiles
Bank Accounts
  Disbursement accounts per Business Unit and payment method
Currencies
  USD, GBP, EUR + unconfigured pairs
Accounting Periods
  Open and closed periods per ledger

Jarvis AI Generates

Scenario 01 — Standard Supplier + EFT + USD
Scenario 02 — Alternate Supplier Site + Check
Scenario 03 — Multiple Invoices, Single Payment
Scenario 04 — High-Value Payment
Scenario 05 — Invoice on Payment Hold
Scenario 06 — Inactive Supplier
...

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

Example Test Variations

Representative examples of Create Payment scenarios Jarvis can generate from this business scenario, spanning supplier, invoice, payment method, bank account, currency and date 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	Basic Supplier Payment	Positive	Standard supplier, invoice, method, bank account, currency and date	Syntra Ready
VAR-002	Different Supplier	Positive/Supplier	Alternate eligible supplier used for payment creation	Syntra Ready
VAR-003	Different Supplier Site	Positive/Supplier	Alternate supplier site for the same supplier	Syntra Ready
VAR-004	Different Business Unit	Positive	Payment created under a different Business Unit	Syntra Ready
VAR-005	Different Payment Method	Positive/Method	Alternate payment method, e.g. EFT vs Check	Syntra Ready
VAR-006	Different Bank Account	Positive/Bank	Alternate disbursement bank account	Syntra Ready
VAR-007	Different Currency	Positive/Currency	Payment created in a different currency	Syntra Ready
VAR-008	Different Payment Date	Positive/Date	Payment created with a different valid payment date	Syntra Ready
VAR-009	Multiple Invoice Selection	Positive/Invoice	Multiple eligible invoices selected for a single payment	Syntra Ready
VAR-010	High-Value Payment	Positive	Payment amount at or near a high-value threshold	Syntra Ready
VAR-011	Payment With Configured Discount	Positive/Invoice	Early-payment discount applied where configured	Syntra Ready
VAR-012	Invoice on Payment Hold	Negative/Invoice	Selected invoice carries an active payment hold	Syntra Ready
VAR-013	Inactive Supplier	Negative/Supplier	Supplier record is inactive	Syntra Ready
VAR-014	Invalid Supplier Site	Negative/Supplier	Supplier site is invalid or inactive for payment	Syntra Ready
VAR-015	Invalid Payment Method	Negative/Method	Payment method not enabled for the supplier or business unit	Syntra Ready
VAR-016	Invalid Disbursement Bank Account	Negative/Bank	Bank account not valid for the selected payment method	Syntra Ready
VAR-017	Missing Required Payment Information	Negative	Required payment field left blank	Syntra Ready
VAR-018	Invalid Currency	Negative/Currency	Currency not configured for the bank account or supplier	Syntra Ready
VAR-019	Closed Accounting Period	Negative/Date	Payment or accounting date falls in a closed period	Syntra Ready
VAR-020	Invalid Payment Date	Negative/Date	Payment date is outside a valid or open range	Syntra Ready
VAR-021	Invoice Already Paid	Negative/Invoice	Selected invoice has already been paid in full	Syntra Ready
VAR-022	Invoice Not Eligible / Invalid Bank-Payment Configuration	Negative/Invoice/Bank	Invoice fails eligibility check, or bank/payment configuration is invalid	Syntra Ready

Positive and Negative Payment Testing

Positive Testing

Jarvis generates scenarios designed to confirm that Oracle Fusion Payables successfully creates a payment when the supplier, invoice, payment method, bank account, currency and date are all valid.

Eligible Invoice + Valid Supplier/Method/Bank/Currency → Payment Created Successfully

Negative Testing

Jarvis can also generate scenarios designed to exercise Oracle's validations around holds, eligibility, banking configuration and period status during payment creation.

Invoice on Payment Hold → Expected Hold Validation
Inactive Supplier → Expected Supplier Validation
Invalid Bank Account → Expected Banking Validation
Closed Accounting Period → Expected Period Validation
Invoice Already Paid → Expected Duplicate Payment Validation

A negative test passes when Oracle produces the expected validation, not when it silently accepts invalid data.

Scenario	Oracle Outcome	Test Result
Eligible invoice	Payment proceeds	PASS
Invoice on hold	Payment prevented	PASS
Missing supplier bank details	Banking validation occurs	PASS
Invalid payment method	Configuration validation occurs	PASS
Unexpected system exception	Unexpected failure	FAIL

Turn AI-Generated Variations into a Regression Pack

Users can select generated payment-creation scenarios and group them into reusable execution packs.

AP Create Payment Regression Pack

Basic Supplier Payment
Different Supplier
Different Payment Method
Different Bank Account
Different Currency
Multiple Invoice Selection
High-Value Payment
Invoice on Payment Hold
Inactive Supplier
Invalid Disbursement Bank Account
Closed Accounting Period
Invoice Already Paid

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-creation scenarios individually or as a batch. Users can schedule regression packs according to their testing cycle.

Once scheduled, SyntraFlow executes the selected payment-creation scenarios unattended and records the outcome of each test and business assertion.

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

Pack	AP Create Payment Regression Pack
Schedule	Nightly Regression
Tests	22 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

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 Create Payment scenario, available DataVault test data and expected business outcomes to generate additional payment-creation 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 — Create Payment, 12 Business Steps

↓

DataVault — Customer-Specific Test Data

↓

Jarvis AI — Generate Positive + Negative 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

Select Eligible Supplier/Invoice

May internally include

Open Supplier Search → Enter Supplier → Select Site → Filter Eligible Invoices → Select Invoice → Confirm

Business Step

Create Payment

May internally include

Validate Form → Submit Payment → Poll Confirmation → Capture Payment Number

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 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
Create Payment	Pass	—
Confirm Payment Status	Pass	—
Verify Invoice Payment Status	Pass	Pass

Related AP Payment Tests

Creating a payment is the first stage of the same Invoice → Payment lifecycle — explore the related full-payment, partial-payment, processing, electronic-payment and accounting scenarios below.

Pay Invoice in Full Partial Payment Payment Process Request Electronic Payment Invoice Accounting

Turn This Standard Test into Your Oracle AP Payment Regression Suite

Start with the Syntra Standard Create Payment test, use DataVault to provide environment-specific supplier, bank account and payment method data, let Jarvis generate additional positive and negative 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 Accounts Payable AP Payments Invoice Processing Syntra DataVault

Frequently Asked Questions

What does the Create Payment test validate?

It validates that Oracle Fusion Payables can create a supplier payment for an eligible, validated invoice using a valid supplier, invoice, payment method, disbursement bank account, currency and payment date, and that the resulting payment and invoice status are correct.

How does this differ from Pay Invoice in Full?

Create Payment focuses on the underlying mechanics of creating a payment — selecting a supplier, invoice, payment method, bank account, currency and date. Pay Invoice in Full is a related scenario that specifically confirms an invoice is paid for its complete outstanding amount in a single payment.

Can SyntraFlow use our own supplier and bank data for this test?

Where DataVault is connected, Jarvis can use approved customer-specific suppliers, supplier sites, bank accounts, payment methods and currencies to construct payment-creation variations relevant to the customer's environment, subject to DataVault's data policies.

Do all these payment variations need separate library pages?

No. Jarvis AI generates supplier, site, business unit, method, bank account, currency and date variations from this single standard scenario rather than requiring a separate indexable page for each combination.

Does SyntraFlow send a real payment to a bank when running this test?

No. SyntraFlow automates the Oracle Fusion Payables user interface within a test or UAT environment; it is a test automation product and does not initiate real bank transfers or move funds.