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

Syntra Standard Oracle Test Library

Oracle Fusion Pay Invoice in Full Test Cases

Validate full settlement of an eligible supplier invoice in Oracle Fusion Accounts Payable, confirming the payment amount matches the outstanding balance, the remaining balance drops to zero, and the invoice payment status updates correctly.

Test ID	ORCL.P2P.AP.PAY.FULL
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

The objective of this test is to verify that an eligible, unpaid supplier invoice in Oracle Fusion Accounts Payable can be settled in full — with the payment amount matching the outstanding balance, the remaining balance dropping to zero, and the invoice payment status correctly reflecting settlement.

The scenario should confirm that:

the invoice selected for payment is eligible — validated, approved where required, not on hold, and not already fully paid
the full outstanding balance is correctly identified before payment is initiated
the payment amount created equals the eligible outstanding balance, satisfying Original Invoice Amount − Payment = Remaining Balance (0)
the selected payment method and disbursement bank account are accepted
the payment is created without unexpected errors
the invoice's remaining balance updates to zero after the payment is confirmed
the invoice payment status updates to Paid, or an equivalent fully-paid status
the created payment is correctly linked to the source invoice for later validation and accounting scenarios

This scenario validates the standard full-settlement path within the Create/Select stage of the AP Payment lifecycle. It does not attempt to validate downstream payment validation, electronic payment processing or payment accounting — those are addressed by separate test scenarios within the same lifecycle.

When to Use This Test

Functional testing of full invoice settlement for a new Oracle Fusion Payables implementation
Regression testing of payment method, bank account and currency combinations after an Oracle quarterly update
UAT sign-off for the standard full-payment path within Accounts Payable
Baseline case referenced by the create-payment, partial-payment, validation and accounting scenarios within the same AP Payment lifecycle

Where This Test Fits in the Full Payment Process

Open Invoice

→

Outstanding Balance

→

Pay in Full

→

Create/Confirm Payment

→

Remaining Balance = 0

→

Verify Paid Status

This test covers the standard flow of opening an eligible invoice, reviewing its outstanding balance, selecting full payment, creating and confirming the payment, and verifying the balance settles to zero with the correct paid status. Exact screen behavior and available payment options depend on the customer's Oracle Fusion payables configuration.

Preconditions

The invoice exists in Oracle Fusion Accounts Payable and has been validated.
The invoice is approved where an approval workflow is required.
The invoice is not already fully paid.
The invoice is not on hold.
The supplier, disbursement bank account and payment method are configured for the test business unit.
The accounting period intended for the payment is open.

Exact eligibility rules, hold types and required approvals vary by Oracle Fusion implementation and payables configuration. Testing is performed against Oracle Fusion TEST/UAT environments — SyntraFlow automation does not transmit real bank payments or execute actual financial transactions.

Sample Test Data

Business Unit	${BUSINESS_UNIT}
Supplier	${SUPPLIER}
Invoice Number	${INVOICE_NUMBER}
Invoice Amount	${INVOICE_AMOUNT}
Outstanding Balance	${OUTSTANDING_BALANCE}
Payment Method	${PAYMENT_METHOD}
Disbursement Bank Account	${DISBURSEMENT_BANK_ACCOUNT}
Payment Date	${PAYMENT_DATE}
Payment Currency	${PAYMENT_CURRENCY}

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

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	Navigate to Accounts Payable Navigate to the Oracle Fusion Accounts Payable Payments work area.	The Payments work area opens successfully.
2	Locate the Eligible Invoice Search for and open the supplier invoice to be paid. ${SUPPLIER} / ${INVOICE_NUMBER} This single business step replaces multiple technical actions such as opening invoice search, entering the supplier and invoice number, and selecting the result.	The correct invoice is located and its status confirms it is validated, approved where required, and not already fully paid.
3	Review Outstanding Balance Review the invoice's current outstanding balance. ${OUTSTANDING_BALANCE}	The displayed outstanding balance matches the expected amount for the invoice.
4	Initiate Full Payment Select the option to pay the invoice in full.	Oracle Fusion pre-populates the payment amount with the full outstanding balance.
5	Select Payment Method Select the payment method to be used for settlement. ${PAYMENT_METHOD}	The selected payment method is accepted.
6	Select Disbursement Bank Account Select the disbursement bank account the payment will be issued from. ${DISBURSEMENT_BANK_ACCOUNT}	The selected bank account is accepted for the payment.
7	Confirm Payment Date and Currency Confirm the payment date and payment currency for the transaction. ${PAYMENT_DATE} / ${PAYMENT_CURRENCY}	Payment date and currency are accepted.
8	Confirm Payment Amount Equals Outstanding Balance Confirm that the payment amount equals the full eligible outstanding balance before submitting. ${INVOICE_AMOUNT} / ${OUTSTANDING_BALANCE}	The payment amount matches the outstanding balance exactly, with no partial amount entered.
9	Create / Confirm Payment Submit the transaction to create and confirm the payment.	Oracle Fusion successfully creates the payment without unexpected errors.
10	Verify Remaining Balance Is ZeroBusiness assertion Review the invoice's remaining balance after the payment is created. This is the primary arithmetic business assertion for the scenario — the test does not stop merely because the payment was submitted successfully.	Remaining invoice balance equals zero: Original Invoice Amount − Payment = Remaining Balance (0).
11	Verify Invoice Status Is PaidBusiness assertion Confirm the invoice payment status after the payment is created.	Invoice payment status updates to Paid, or an equivalent fully-paid status.
12	Capture Payment IdentifierBusiness assertion Capture the payment reference created for the invoice and confirm it is linked to the correct invoice. Confirms the payment record exists and traces correctly back to the settled invoice.	A payment record and identifier exist and are correctly linked to the source invoice, with no unexpected outstanding balance remaining.

Expected Results

An eligible invoice's outstanding balance is settled in full.
Payment amount equals the eligible outstanding balance at time of payment.
Remaining invoice balance becomes zero after the payment is created.
Invoice payment status updates correctly to reflect full settlement.
The payment is correctly linked to the source invoice.
No unexpected outstanding balance remains on the invoice.
A valid payment record and identifier exist for the transaction.
The payment is available for subsequent validation and accounting scenarios.

Key Validation Checkpoints

Payment amount equals the eligible outstanding balance at time of payment.
Remaining balance becomes zero: Original Invoice Amount − Payment = Remaining Balance (0).
Invoice payment status is updated correctly.
Payment is linked to the correct invoice.
No unexpected outstanding balance remains after payment.
A payment record exists for the transaction.

Core Business Scenario

Pay Invoice in Full

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 full-payment 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 full-payment test dozens of times simply to cover different combinations of supplier, payment method, bank account, currency and invoice amount. 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

Syntra Standard Test

Reusable full-payment business scenario and automation logic.

Customer DataVault

Provides approved customer-specific test data and configuration required for scenario generation — Suppliers, Invoices, Outstanding Balances, Payment Methods, Bank Accounts, Currencies and Payment Dates.

Jarvis AI

Analyses the standard scenario together with available test data and generates relevant full-payment variations.

Positive + Negative Test Variations

Correctly-settled payment scenarios and edge cases where settlement should be prevented or validated.

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.

Results + Evidence + Exceptions

Capture execution results, business assertions, screenshots/evidence and exceptions.

Rather than maintaining dozens of near-duplicate copies of the same full-payment 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 Pay Invoice in Full 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

Standard full payment
Full payment in invoice currency
Full payment for different suppliers
Full payment across different business units
Full payment via different payment methods
Full payment from different disbursement bank accounts
Full payment across different invoice amount tiers
Full payment with available early-payment discount
Full payment after hold release
Full payment after required approval

Negative Scenarios

Invoice already fully paid
Invoice on payment hold
Invoice not validated
Invoice not approved where approval is required
Invalid payment method
Invalid bank account
Invalid payment date
Closed accounting period
Invalid currency or currency configuration

These are representative examples only. Negative scenarios and 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

Generic test data rarely reflects every supplier, payment method, bank account and currency configured in a real Oracle Fusion environment. Where connected, Jarvis can use approved test data available through Syntra DataVault to construct full-payment scenarios relevant to the customer's actual implementation.

Standard Library Definition

Business Unit           ${BUSINESS_UNIT}
Supplier                 ${SUPPLIER}
Invoice Number            ${INVOICE_NUMBER}
Invoice Amount            ${INVOICE_AMOUNT}
Outstanding Balance       ${OUTSTANDING_BALANCE}
Payment Method            ${PAYMENT_METHOD}
Disbursement Bank Acct    ${DISBURSEMENT_BANK_ACCOUNT}
Payment Date              ${PAYMENT_DATE}
Payment Currency          ${PAYMENT_CURRENCY}

DataVault

Suppliers
  Approved supplier master records
Invoices
  Eligible, validated and approved invoices
Outstanding Balances
  Full-balance invoices by business unit
Payment Methods
  Check, EFT, Wire per supplier setup
Bank Accounts
  Disbursement accounts by business unit
Currencies
  USD, GBP, EUR + invoice-currency pairs
Payment Dates
  Current-period payment dates

Jarvis AI Generates

Scenario 01 — Standard Full Payment + EFT
Scenario 02 — Full Payment + Invoice Currency
Scenario 03 — Full Payment + Different Supplier
Scenario 04 — Full Payment With Discount
Scenario 05 — Invoice Already Fully Paid
Scenario 06 — Invoice On Hold
...

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

Example Test Variations

Representative examples of full-payment scenarios Jarvis can generate from this business scenario. 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	Standard Full Payment	Positive	Standard full settlement of an eligible invoice	Syntra Ready
VAR-002	Full Payment in Invoice Currency	Positive/Currency	Payment currency matches invoice currency	Syntra Ready
VAR-003	Full Payment — Different Supplier A	Positive/Supplier	Full payment against a different supplier record	Syntra Ready
VAR-004	Full Payment — Different Supplier B	Positive/Supplier	Full payment against a second alternate supplier record	Syntra Ready
VAR-005	Full Payment — Payment Method Check	Positive/Method	Payment method = Check	Syntra Ready
VAR-006	Full Payment — Payment Method EFT	Positive/Method	Payment method = EFT	Syntra Ready
VAR-007	Full Payment — Payment Method Wire	Positive/Method	Payment method = Wire	Syntra Ready
VAR-008	Full Payment — Different Bank Account	Positive	Disbursement issued from an alternate bank account	Syntra Ready
VAR-009	Full Payment — Small Invoice Amount	Positive	Low-value invoice amount tier	Syntra Ready
VAR-010	Full Payment With Available Discount	Positive/Discount	Early-payment discount applied and reflected in settlement	Syntra Ready
VAR-011	Full Payment After Hold Release	Positive	Payment created only after the invoice hold is released	Syntra Ready
VAR-012	Full Payment After Required Approval	Positive	Payment created only after invoice approval is complete	Syntra Ready
VAR-013	Invoice Already Fully Paid	Negative	Attempt to pay an invoice with zero remaining balance	Syntra Ready
VAR-014	Invoice On Hold	Negative	Invoice carries an active payment hold	Syntra Ready
VAR-015	Invoice Not Validated	Negative	Invoice has not completed validation	Syntra Ready
VAR-016	Invoice Not Approved	Negative	Required approval has not been completed	Syntra Ready
VAR-017	Invalid Payment Method	Negative/Method	Selected payment method is not valid for the supplier	Syntra Ready
VAR-018	Invalid Bank Account	Negative	Disbursement bank account is invalid or not configured	Syntra Ready
VAR-019	Invalid Payment Date	Negative/Period	Payment date is invalid or out of sequence	Syntra Ready
VAR-020	Closed Accounting Period	Negative/Period	Payment date falls within a closed accounting period	Syntra Ready
VAR-021	Invalid Currency Configuration	Negative/Currency	Payment currency is not configured or not valid for the transaction	Syntra Ready

Why a Prevented Full Payment Can Be a Passing Test

Positive Testing

Jarvis generates scenarios using combinations expected to successfully settle an eligible invoice in full.

Eligible Invoice + Valid Payment Method + Valid Bank Account → Invoice Paid in Full, Remaining Balance = 0

Negative Testing

Jarvis can also generate scenarios designed to exercise Oracle's payment eligibility, configuration and period validations around full settlement.

Invoice Already Fully Paid → Expected Duplicate-Payment Prevention
Invoice On Hold → Expected Hold Validation
Invoice Not Approved → Expected Approval Validation
Invalid Bank Account → Expected Configuration Validation
Closed Accounting Period → Expected Period Validation

A negative test should not be marked as failed simply because Oracle correctly prevents payment of an ineligible invoice. If the expected Oracle validation occurs, the negative test has passed.

Scenario	Oracle Outcome	Test Result
Eligible invoice	Payment settles fully, remaining balance = 0	PASS
Invoice already paid	Payment prevented or duplicate blocked	PASS
Invoice on hold	Payment prevented	PASS
Invalid bank account	Configuration validation occurs	PASS
Unexpected system error	Unexpected failure	FAIL

Turn AI-Generated Variations into a Regression Pack

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

AP Full Payment Regression Pack

Standard Full Payment
Full Payment in Invoice Currency
Full Payment — Different Supplier
Full Payment — Different Payment Method
Full Payment With Available Discount
Full Payment After Hold Release
Invoice Already Fully Paid
Invoice On Hold
Invalid Bank Account
Closed Accounting Period

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 full-payment 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.

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

Pack	AP Full Payment Regression Pack
Schedule	Quarterly Update Regression
Tests	21 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 full-payment scenario, available DataVault test data and expected business outcomes to generate additional test 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 — Pay Invoice in Full, 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

Locate the Eligible Invoice

May internally include

Open Invoice Search → Enter Supplier → Enter Invoice Number → Search → Select Invoice → Confirm Status

Business Step

Confirm Payment Amount Equals Outstanding Balance

May internally include

Open Payment Amount Field → Read Outstanding Balance → Compare Values → Validate Equality → Proceed

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 invoice was correctly settled — 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 / Confirm Payment	Pass	—
Verify Remaining Balance Is Zero	Pass	Pass
Verify Invoice Status Is Paid	Pass	Pass

Related AP Payment Tests

Pay Invoice in Full is one settlement path within the same Accounts Payable payment lifecycle — explore the related creation, partial payment, validation and accounting scenarios below.

Create Payment Partial Payment Payment Validation Payment Accounting

Turn This Standard Test into Your Oracle AP Payment Regression Suite

Start with the Syntra Standard full-payment 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.

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 AP Invoice Processing Test Library Syntra DataVault

Frequently Asked Questions

What does the Pay Invoice in Full test validate in Oracle Fusion Accounts Payable?

It validates that an eligible, unpaid invoice can be settled in full — with the payment amount matching the outstanding balance, the remaining balance dropping to zero, and the invoice payment status correctly updating to Paid.

How is Pay Invoice in Full different from Partial Payment?

Pay Invoice in Full settles the entire eligible outstanding balance in a single payment, leaving a remaining balance of zero. Partial Payment settles only a portion of the outstanding balance, leaving the invoice open for further payment — it is covered as a separate related scenario.

How are early-payment discounts handled in this test?

Where an early-payment discount is available and applied, the scenario still verifies that the resulting payment correctly reduces the outstanding balance to zero, with the discount amount reflected in the payment terms rather than left as an unresolved balance.

Does Pay Invoice in Full map to a fixed stage in the AP Payment Lifecycle?

Yes. It represents the standard full-settlement path within the Create/Select stage — the same lifecycle position shared with Create Payment and Partial Payment, which are alternative ways of creating a payment.

How are the many full-payment test variations generated?

Jarvis AI uses this standard full-payment scenario together with available DataVault test data — suppliers, invoices, payment methods, bank accounts and currencies — to generate relevant positive and negative variations for the customer's environment.